9400AWY User Manual Rel2.1.1

Alcatel–Lucent 9400AWY7–8–13–15–18–23–25–28–38 GHzshort–haul low/medium capacity digital microwave radio links9400AWY Rel.2.1SWP 9400AWY R.2.1 V2.1.1

User Manual3DB 16142 EAAA

Ed.02

2 / 592 3DB 16142 EAAA Ed.02

Navigation principles

This manual is delivered to Customers in electronic format only (file Adobe Acrobat pdf) inside the specific9400AWY Customer Documentation CD–ROM: for a comfortable navigation, two hyperlink types arepresent:– those inside the text window, marked by a blue rectangle around any cross–reference to a figure,

table, part, section, chapter, paragraph, numbered list, and page: by clicking such a blue rectangle,you are led to the referenced component

– the bookmarks, present on the left side of the text window. Most of them represent the on–linehandbook “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 “full–screen” modality.For further information, refer to Acrobat reader help on–line.

If printed on paper by Users, it is suggested to divide this manual by numbered separators, for an easieraccess to the information herein contained:

CONTENTS SEPARATORQUICK GUIDETABLE OF CONTENTSLIST OF FIGURES AND TABLES

SECTION 1 : SYSTEM DESCRIPTION 1SECTION 2 : NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 2SECTION 3 : INSTALLATION AND COMMISSIONING 3SECTION 4 : MAINTENANCE AND UPGRADE 4SECTION 5 : APPENDICES 5

The standard Customer Documentation for 9400AWY Rel.2.1 SWP version V2.1.1 is in the Englishlanguage and is distributed to Customers only by the following CD–ROM:

CD–ROM TITLE Technical Code

DCP 9400AWY 2.1 V2.1.1 CD–ROM 3DB 16142 ACAA

It contains, in electronic format (ADOBE ACROBAT pdf files), the following main documents:

Document TitleDocument

Technical CodeNotes

9400AWY Rel.2.1 Installation Handbook 3DB 16142 BAAA

9400AWY Rel.2.1 Installation Guide 3DB 16142 FAAA

9400AWY Rel.2.1 V2.1.1 User Manual 3DB 16142 EAAA this manual

9400AWY Rel.2.1 TRS and SAT 3DB 16142 DAAA

For further information and additional documents, please refer to Appendix G – Documentationguide on page 567

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

3 / 5923DB 16142 EAAA Ed.02

USER MANUALFRONT MATTER

9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

QUICK GUIDE

9400AWY Rel.2.1 V2.1.1 USER MANUAL

Tab. 1. below allows to access immediately the most frequently needed operative pieces of informationcontained in this manual and in other related handbooks.

To find any other kind of information not listed in this table, please refer to the TABLE OF CONTENTS ofthis handbook, or, if you are using the pdf file of it, use the Acrobat Reader “Find” function.

Tab. 1. Quick guideIf you need immediate operative information on following matters:

have a short description of thesystem

read pages 37 to 53

know changes of this issue read para.1–1.4 on page 34

know new features of the SWPversion this handbook refers to

read para.1–1.2 on page 32

GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCEread page 4

INSTALLATION AND COMMISSIONINGread page 4

MAINTENANCEread page 5

TCO SUITEread page 5

ECT (EQUIPMENT CRAFT TERMINAL): GENERAL AND LOGIN & LOGOFFread page 5

ECT USAGE FOR EQUIPMENT MANAGEMENT AND TROUBLESHOOTINGread page 6

EQUIPMENT PROVISIONING AND ITEM PART NUMBERSread page 6

SYSTEM UPGRADEread page 7

EQUIPMENT TECHNICAL CHARACTERISTICSread page 7

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

4 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1


a ) GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCE

get information on safety, EMC,EMF, ESD norms and equipmentlabelling

read Appendix A on page 501

acknowledge cautions to avoidequipment damage


have the description of equipmentinterconnections, according to theconfigurations


for:

– IDU Main unit: read para.1–3.3 on page 70

– IDU Extension unit: read para.1–3.4 on page 77

get operative information regarding

– IDU Extension unit: read para.1–3.4 on page 77

– E1 Protection box: read para.1–3.5 on page 79get operative information regardingthe units in IDU (connectors, leds,buttons)

– E1 Protection box: read para.1–3.5 on page 79

– Services Protection box: read para.1–3.6 on page 84buttons) – Services Protection box: read para.1–3.6 on page 84

– Flash Card: read para.1–3.7 on page 93– Flash Card: read para.1–3.7 on page 93

– Cables and Distributor subracks: refer to the– Cables and Distributor subracks: refer to theInstallation HandbookInstallation Handbook

get operative information regardingODU

read chapter 1–4 on page 97 , in particular:

– para.1–4.7 on page 119

– and para.1–4.7.4 on page 123

carry out antenna fine alignment read para.3–2.9 on page 404

b ) INSTALLATION AND COMMISSIONING

carry out installation andcommissioning of equipment asdelivered from Alcatel–Lucentfactory

proceed as specified in para.1–2.6.1 on page 59

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

5 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1


c ) MAINTENANCE

know the consequences of unitextraction in IDU shelf


set and use the EOW functions ofthe equipment

read chapter 4–2 on page 413

provision and manage spare parts read para.4–3.3 on page 418

carry out First Level maintenance(system state display)

proceed as specified in chapter 4–4 on page 421

carry out preventive maintenance proceed as specified in para.4–5.3 on page 431

carry out corrective maintenance(troubleshooting and repair)

proceed as specified in para.4–5.5 on page 433

d ) TCO SUITE

know and use TCO functions read para.2–2.2 on page 146

e ) ECT: GENERAL AND LOGIN & LOGOFF

know ECT and RECT characteristics read para.1–2.4 on page 54

have the functional description ofUser Profile management

read para.2–3.6.1 on page 214

login proceed as specified in para.2–2.5.2 on page 173

logoff proceed as specified in para.2–2.5.3 on page 180

close the 1320CT application proceed as specified in para.2–2.5.4 on page 180

change own password (for all users) proceed as specified in para.2–3.6.2 on page 216

manage usernames and passwordsof all users (for administrator only)

proceed as specified in para.2–3.6.3 on page 217

set–up a remote connectionbetween CT and equipment, througha switched telephone line of thestandard Public Telephone Network.

proceed as specified in Appendix E on page 553

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

6 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1


f ) ECT USAGE FOR EQUIPMENT MANAGEMENT AND TROUBLESHOOTING

have an overview on menu treestructure

open SECTION 2 – NE MANAGEMENT on page 139 andmanage equipment configuration open SECTION 2 – NE MANAGEMENT on page 139 andthen search the information according to the listed topics

set–up parameters for maintenancethen search the information according to the listed topics

use functions for SW management

troubleshoot by ECT

proceed as specified in:



g ) EQUIPMENT PROVISIONING AND ITEM PART NUMBERS

do provisioning & know P/Ns at IDUlevel (except installation materialsand cables)

for provisioning and P/Ns of:

– IDU shelves, read para.1–3.1 on page 68

– Flash Cards & Software Labels, read para.1–3.7.1 onpage 93

– equipment accessories, read para.1–3.8 on page 96

– upgrade kits, refer to Tab. 71. on page 469

do provisioning & know P/Ns at IDUlevel for installation materials andcables

read paragraph IDU installation components of theInstallation Handbook

do provisioning at ODU level(transceivers only)


do provisioning & know P/Ns atODU level for installation materials,antennas and related matters

read suitable tables (according to configuration andfrequency bands) in paragraph Full Integrated or NotIntegrated antenna installation components of theInstallation Handbook

do provisioning of software products read para.2–1.1.2 on page 141

do provisioning of cables forPC–to–NE local connection

read para.2–2.1 point b ) on page 144

do provisioning for systemdocumentation


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

7 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1


h ) SYSTEM UPGRADE

install a plug–in on IDU Main and/orExtension unit


upgrade system configuration from(1+0) to (1+1)


replace Flash Card to improvesystem capacity


upgrade only NE with a newer SWPversion


upgrade only ECT with a newerSWP version


upgrade both ECT and NE with anewer SWP version


i ) EQUIPMENT TECHNICAL CHARACTERISTICS

know system technicalspecifications


know ODU P/Ns and relatedfrequency bands and frequencyshifters, antenna characteristics andother ODU related matters


know Ethernet port characteristics read Appendix D on page 547

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

8 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

9 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

TABLE OF CONTENTS

QUICK GUIDE 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LIST OF FIGURES AND TABLES 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 1: SYSTEM DESCRIPTION 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–1 ABOUT THIS MANUAL 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.1 Preliminary information 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.2 New features with respect to SWP Version V2.1.0 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.3 Structure of this manual 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.4 Notes on present edition 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.5 Safety–EMC–EMF–ESD norms and equipment labelling 35 . . . . . . . . . . . . . . . . . . . . . . . 1–1.6 Cautions to avoid equipment damage 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2 SYSTEM OVERVIEW 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.1 Introduction 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.2 Equipment architecture 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.2.1 Split–mount architecture 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.2.2 IDU (Indoor Unit) 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.2.3 ODU (Outdoor Unit) 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.2.4 IDU–ODU cable 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.3 System configurations 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.3.1 1+0 Unprotected configurations 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.3.2 1+1 Protected Configurations 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.4 Equipment Craft Terminal and TCO Suite 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.4.1 ECT 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.4.2 RECT 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.4.3 TCO Suite 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.5 Flash Card types and content 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6 General on equipment installation and SWP installation and management 58 . . . . . .

1–2.6.1 Main phases for 9400AWY HW and SW installation 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6.2 First SWP installation in PC and NE environments 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6.3 How to check ECT and NE versions 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6.4 Common situations requiring ECT and/or NE upgrade 64 . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6.5 Flash Card related special procedures 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6.6 Craft Terminal related special procedures 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6.7 NE configuration data change and save 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6.8 NE data save after commissioning completion 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.6.9 NE data compatibility between SWP 2.1.x versions 65 . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3 IDU PROVISIONING AND DESCRIPTION 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.1 Provisioning of IDU shelves 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.2 Labels affixed on the IDU 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.3 Description of IDU Main unit 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3.3.1 IDU Main Unit LEDs summary 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.3.2 Power Supply connector pin–out (MAIN and EXTENSION units) 74 . . . . . . . . . . . . . . . . 1–3.3.3 ECT RS232 connector pin–out 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.3.4 OS (or ECT) 10/100BaseT connector pin–out 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.3.5 Ethernet tributaries 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3.4 Description of IDU Extension unit 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.4.1 IDU Extension Unit LEDs summary 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3.5 Description of E1 Protection box 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.5.1 E1 Protection box: connector pin–out 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

10 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

1–3.6 Description of Services Protection box 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.6.1 Alarms Housekeeping (pin–out and description) 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.6.2 NMS V.11 – Audio 1 (pin–out and description) 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.6.3 NMS G.703 – Audio 2 (pin–out and description) 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.6.4 User service channels (pin–out and description) 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3.7 Provisioning and identification of Flash Cards & Software Labels 93 . . . . . . . . . . . . . . 1–3.7.1 Provisioning of Flash Cards & Software Labels 93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.7.2 Description of Flash Cards & Software Labels 94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3.8 Provisioning and description of equipment accessories 96 . . . . . . . . . . . . . . . . . . . . . . .

1–4 ODU PROVISIONING, CHARACTERISTICS AND DESCRIPTION 97 . . . . . . . . . . . . . . . . . . . . . 1–4.1 ODU mechanical design and identification 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.2 Labels affixed on the ODU 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.3 ODU configurations 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.4 ODU provisioning and layouts 101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–4.4.1 Provisioning of ODU (1+0) 101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.4.2 Provisioning, layouts and connections of ODU (1+1) 101 . . . . . . . . . . . . . . . . . . . . . . . . . .

1–4.5 ODU part lists and characteristics 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.5.1 Part lists of ODUs with external diplexer 105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.5.2 Part lists of ODUs with embedded diplexer 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–4.6 Antenna configurations 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.6.1 1+0 configuration with full integrated antenna 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.6.2 1+1 HSB configuration with coupler and full integrated antenna (13–38 GHz) 116 . . . . . 1–4.6.3 1+1 HSB configuration with coupler and full integrated antenna (7–8 GHz) 117 . . . . . . . 1–4.6.4 Configuration with separated antenna 117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–4.7 ODU operative information 119 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.7.1 Operative information on ODUs with embedded or external diplexer 119 . . . . . . . . . . . . . 1–4.7.2 ODU hardware settings 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.7.3 ODU identification 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4.7.4 Additional operative information on ODUs with external diplexer 123 . . . . . . . . . . . . . . . .

1–5 TECHNICAL SPECIFICATIONS 127 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.1 General Characteristics 128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–5.1.1 Reference system standards 129 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.1.2 RF channelling 129 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.1.3 Transmitted power at antenna port 130 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.1.4 99% power channel bandwidth and Emission Designator 131 . . . . . . . . . . . . . . . . . . . . . . 1–5.1.5 ETSI System Characteristics 132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.1.6 Protection switching system 134 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–5.2 Tributary interfaces 135 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.3 Modem 135 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.4 Maximum capacity and Modulation type 135 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.5 IDU–ODU cable 135 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.6 Man–machine interface 136 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.7 Alarms 136 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.8 Power supply 136 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.9 Mechanical characteristics 136 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.10 Environmental conditions 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–5.10.1 Operating environmental conditions 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.10.2 Electro–magnetic compatibility/safety 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.10.3 Waste from Electrical and Electronic Equipment (WEEE) 137 . . . . . . . . . . . . . . . . . . . . .

1–5.11 Dismantling & Recycling 138 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 139 . .

2–1 SWP 9400AWY R.2.1 V2.1.1 DESCRIPTION 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.1 SWP 9400AWY R.2.1 V2.1.1 general description 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

11 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

2–1.1.1 General 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.1.2 Software product list and part numbers 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1.2 SWP 9400AWY R.2.1 V2.1.1 specific information 142 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2.1 PC characteristics 142 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2.2 NE MIB Compatibility 142 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2.3 SWP version specific data and Reference Information Models 142 . . . . . . . . . . . . . . . . . .

2–2 INTRODUCTION ON TCO SUITE AND CT VIEWS AND MENUS 143 . . . . . . . . . . . . . . . . . . . . . . 2–2.1 Requirements 144 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2 TCO Suite description 146 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.2.1 TCO Suite scopes 146 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.2 Summary 147 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.3 TCO Suite start–up 148 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.4 TCO Suite Main Menu functions 149 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.5 TCO Suite Advanced Settings Page 151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.6 Note: “Direct” And “Remote” Connections 154 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.7 Warning about interface customization carried out by the Direct Connection 155 . . . . . .

2–2.3 TCO Suite Alarms & Settings functions 156 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.1 TCO Suite Alarms & Settings start–up 156 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.2 Date & Time Setting 159 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.3 Configuration Setting 160 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.4 Configuration Info 161 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.5 Get Configuration File 164 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.6 Active Alarms 165 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.7 Power Measurement 166 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.8 Licence Info 166 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.9 Modem Speed 167 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.10 NAT option 168 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.4 PC–NE physical connections 170 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.4.1 Physical interfaces for the NE management 170 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.4.2 Local connection of the Craft Terminal to the NE 171 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.5 Craft Terminal: NE supervision, login, logoff and switch off 172 . . . . . . . . . . . . . . . . . . . . 2–2.5.1 NE management states 172 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.5.2 NE supervision and login 173 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.5.3 NE Logoff or switch off 180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.5.4 Closing the 1320CT application 180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.6 9400AWY view organization 181 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.6.1 Introduction 181 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.6.2 View Area 182 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.6.3 Button Policy 183 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.6.4 Main tool bar 183 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.7 Introduction to the CT menu options 184 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.7.1 Menu organization 184 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.7.2 Views menu introduction 185 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.7.3 Configuration menu introduction 186 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.7.4 Diagnosis menu introduction 186 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.7.5 Supervision menu introduction 187 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.7.6 SW Download menu introduction 187 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3 CONFIGURATION 189 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.1 NE Time 190 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.2 Network Configuration 191 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.2.1 Local Configuration 192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.2.2 NTP Configuration 193 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.2.3 Ethernet Configuration 195 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.2.4 IP Configuration 196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

12 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

2–3.2.5 Routing information 204 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.3 Alarm Severities 205 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.3.1 How to create a new Alarm Severity Profile 207 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.4 System Settings 210 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.4.1 NE Configuration 210 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.4.2 Link Identifier 212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.4.3 Overhead 213 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.5 Quick Configuration 213 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.6 Profiles management 214 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.6.1 Functional description 214 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.6.2 Change Password procedure 216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.6.3 Users Management procedure 217 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.7 Log Switch 218 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–4 EQUIPMENT 219 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.1 IDU level 221 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–4.1.1 1+0 configuration 221 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.1.2 1+1 configuration 222 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.1.3 Board level 222 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–4.2 ODU level 223 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.3 Tab panels in the Resource Detail Area 224 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–4.3.1 Alarms 224 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.3.2 Configuration 225 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.3.3 Remote Inventory 225 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–5 LINE INTERFACE 227 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.1 Tab panels in the Resource Detail Area 228 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–5.1.1 Alarm 228 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.1.2 Configuration 228 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–6 RADIO 233 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.1 Alarms 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.2 Configuration 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–6.2.1 Local or Remote Transmitter Mute 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.2.2 ODU service kit 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.2.3 Alarm Profile 234 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–6.3 Frequency 235 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.4 RTPC & ATPC 238 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–6.4.1 ATPC 239 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.4.2 RTPC 240 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–6.5 Power Measurement 241 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.5.1 How to read a Power Measurement file 244 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–6.6 BER measure 246 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–7 EXTERNAL POINTS 247 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.1 Input External Points 247 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.2 Output External Points 248 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

2–8.1.1 Switching from the OS to the Craft Terminal access state 251 . . . . . . . . . . . . . . . . . . . . . . 2–8.1.2 Switching from the Craft Terminal access state back to the OS access state 252 . . . . .

2–8.2 Restart NE 252 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.3 MIB Management 253 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–8.3.1 Backup 254 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.3.2 Restore 255 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.3.3 Activate 255 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

13 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

2–8.3.4 Remove file 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.4 SW key 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–9 PROTECTION SCHEMES 257 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.1 Equipment Protection Management 258 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–9.1.1 Schema Parameters 258 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.1.2 Commands 259 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–9.2 Radio Protection Management 260 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.2.1 Schema Parameters 260 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.2.2 Commands 261 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–9.3 HSB Transmission Protection Management 262 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.3.1 Schema Parameters 262 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.3.2 Commands 263 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–9.4 Rx Static Delay 264 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–10 LOOPBACKS 267 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.1 Hardware implementation 267 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–10.1.1 IDU loopbacks 267 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.1.2 ODU loopbacks 268 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–10.2 Available Loopbacks 269 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.3 Loopback domain views 272 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.4 How to activate a loopback 275 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.5 How to remove a loopback 276 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11 DIAGNOSIS 277 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.1 Alarms 278 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11.1.1 Counter Summary 278 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.1.2 Alarm Sub–list 278 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11.2 Log Browsing 279 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.2.1 Alarm and Event Log 280 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.2.2 Software Trace Log 281 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11.3 Remote Inventory 282 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.3.1 General 282 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.3.2 Remote Inventory display 283 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11.4 Abnormal Condition List 284 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.5 Summary Block Diagram View 285 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.6 Current Configuration view 288 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–12 PERFORMANCE MONITORING 289 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.1 General information on the performance monitoring process 289 . . . . . . . . . . . . . . . . . 2–12.2 Performance menu 290 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.3 CD (Current Data) 292 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–12.3.1 CD parameters 292 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.3.2 CD Counters 293 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–12.4 HD (History Data) 294 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.4.1 HD Parameters 294 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–12.5 Threshold tables 295 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.5.1 How to change a threshold table 295 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.5.2 How to create a threshold table 296 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.5.3 Threshold table association 296 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–13 SW DOWNLOAD 297 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.1 Server Access Configuration 297 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.2 Init SW Download 298 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.3 SW Status 299 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

14 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

2–14 MIB MANAGEMENT 301 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14.1 Introduction 301 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14.2 MIB management at Network Element Synthesis level and examples 302 . . . . . . . . . .

2–14.2.1 MIB back–up on ECT 302 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14.2.2 MIB save to disk 302 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14.2.3 MIB load from disk 304 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14.2.4 MIB restore from ECT 306 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 3: INSTALLATION AND COMMISSIONING 307 . . . . . . . . . . . . . . . . . . . . .

3–1 SWP INSTALLATION IN PC ENVIRONMENT 309 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.1 Requirements 309 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.1.1 PC characteristics 309 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.1.2 Operator skills and privileges 310 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.2 Reference Information Model 310 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.3 Choice of the procedure and summary of SWP installation phases 311 . . . . . . . . . . . . . 3–1.4 Preliminary: installation of different SWPs in the same PC 312 . . . . . . . . . . . . . . . . . . . . . 3–1.5 1320CT Package Installation (installation of SWP components from the SWP CD–ROM) 314 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.5.1 Important warnings 314 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.2 Operations sequence 315 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.3 Next step 317 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.6 Local copy in PC environment of the TCO Suite 318 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.6.1 Operations sequence 318 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.6.2 Next step 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.7 End of SW installation from SWP CD–ROM 320 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.8 NE software downloading preparation 321 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.9 CT initial configuration 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.9.1 Craft Terminal configuration 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.9.2 Craft Terminal local connection to the NE 326 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.10 EML construction 327 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–2 LINE–UP AND COMMISSIONING 329 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.1 Introduction 329 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–2.1.1 General 329 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.1.2 Conventions 329 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.1.3 Summary of the commissioning phases 330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.1.4 Safety–EMC–EMF–ESD norms and Cautions to avoid equipment damage 330 . . . . . . .

3–2.2 Description of equipment interconnections 331 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.2.1 Configurations with 16E1 332 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.2.2 Configurations with 16E1 + Audio and User Service Channel plug–in 333 . . . . . . . . . . . . 3–2.2.3 Configurations with 16E1 + Enhanced Ethernet plug–in 334 . . . . . . . . . . . . . . . . . . . . . . . 3–2.2.4 Configurations with 16E1 + Enhanced Ethernet plug–in + Audio and User Service Channel plug–in 335 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.2.5 Configurations with 32E1 336 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.2.6 Configurations with 32E1 + Audio and User Service Channel plug–in 337 . . . . . . . . . . .

3–2.3 Commissioning of STATION A – phase 1 (Turn up) 338 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.1 Turn–on preliminary operations 338 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.2 Powering up the IDU(s) with ODU(s) connected 339 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.3 Switching off the IDU(s), and ODU(s) disconnection 339 . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.4 Powering up the IDU(s) with ODU(s) disconnected 340 . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.5 NE login 340 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.6 General on Quick Configuration Procedure 341 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.7 On–line creation, modification and save of the NE configuration (interactive) 343 . . . . . 3–2.3.8 TCO Suite Pre–Provisioning Tool: off–line creation, modification and save of a provisioning file (not interactive) 344 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

15 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

3–2.3.9 TCO Suite Set–Up Tool: on–line recover, modification and application of a provisioning file (not interactive) 345 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.10 Quick Configuration Procedure steps 346 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3.11 Powering UP the IDU(s) with the ODU(s) 369 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–2.4 Commissioning of STATION B – phase 1 (Turn up) 373 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.5 End of commissioning phase 1 (Turn up) in STATION A 374 . . . . . . . . . . . . . . . . . . . . . . .

3–2.5.1 Remote NE (station B) acquisition on craft terminal 374 . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.5.2 Testing configurations for hop quality check 376 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–2.6 Commissioning station A – phase 2 (acceptance test) 377 . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.6.1 System Installation and cabling visual inspection 377 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.6.2 Local configuration control 377 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.6.3 Channel 1 functionality tests (1+0 and 1+1) 382 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.6.4 Channel 0 functionality tests (1+1 only) 394 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.6.5 Hop stability test 396 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.6.6 NE integration tests 397 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–2.7 Commissioning station B – Phase 2 (Acceptance Test) 403 . . . . . . . . . . . . . . . . . . . . . . . . 3–2.8 Final operations 403 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.9 Annex A: fine antenna alignment 404 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.10 Annex B: light service kit cable operative information 405 . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 4: MAINTENANCE AND UPGRADE 407 . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–1 MAINTENANCE POLICY 409 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.1 Classification of maintenance levels and operators 409 . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.2 First Level Maintenance Personnel skill 410 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.3 Second Level Maintenance Personnel skill 410 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.4 Troubleshooting organization 410 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–2 USE OF EOW FUNCTIONS 413 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.1 Setting information 413 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.2 Call Set–up/End by Telephone handset connected to the IDU Main unit 414 . . . . . . . . .

4–3 MAINTENANCE TOOLS AND SPARE PARTS 415 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.1 Introduction 415 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.2 Instruments and accessories 415 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–3.2.1 Software tools 415 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.2.2 Maintenance, Installation and Station Tool Kits 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–3.3 Set of spare parts 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.3.1 Types of Spare Parts 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.3.2 ODU Spare Parts 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.3.3 IDU Spare Parts 418 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.3.4 Number of spare parts 419 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.3.5 General rules on spare parts management 419 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–4 FIRST LEVEL MAINTENANCE 421 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.1 Introduction 421 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.2 System state display by visual indications 421 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–4.2.1 LED test 421 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.2.2 Alarm LEDs on the IDU MAIN unit 421 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.2.3 Alarm LEDs on the Extension unit 421 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–4.3 TCO Suite and Craft Terminal commonly used functions for system status display and checks 423 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–4.3.1 Viewing the NE alarms by TCO Suite 423 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.3.2 Viewing the NE status by Craft Terminal 423 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–5 SECOND LEVEL MAINTENANCE 429 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.1 Introduction 429 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

16 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

4–5.2 Warnings 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.2.1 EMC norms 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.2.2 Safety rules 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.2.3 Cautions to avoid equipment damage 430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–5.3 Routine (preventive) Maintenance 431 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.3.1 Routine (preventive) Maintenance every year 431 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–5.4 Consequences of unit extraction in the IDU 432 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.5 Corrective Maintenance general flow–chart 433 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.6 Alarm acknowledgment and attending 434 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–5.6.1 Alarm acknowledgment 434 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.6.2 Alarm Attending 434 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–5.7 Troubleshooting starting with visual indications 435 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.8 Troubleshooting via Craft Terminal 436 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–5.8.1 Diagnosis 436 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.8.2 Alarm surveillance 437 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.8.3 Loopbacks 441 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.8.4 Operator’s Controls of the protection switches 441 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.8.5 Tx mute function (local and remote) 441 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.8.6 Performance Monitoring 441 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.8.7 BER measurement 441 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.8.8 Commissioning tests 441 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–5.9 Hints on the troubleshooting 442 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.1 Problems with the Craft Terminal 442 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.2 Analog measurements 446 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.3 NMS 64 kbit/s V.11 and G.703 446 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.4 Loopbacks 446 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.5 Empty USM icon in NES 447 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.6 Remote NE unreachable 447 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.7 Configuration change from 4 QAM to 16 QAM 447 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.8 Quick configuration menu correct use 447 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.9 Abnormal condition list 448 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.10 Tx Mute functionality for interferences investigation 449 . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.9.11 Tributaries 17 to 32 visible in “16E1+Ethernet” configuration 450 . . . . . . . . . . . . . . . . . .

4–5.10 IDU unit replacement 451 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.10.1 IDU MAIN unit replacement procedure (CH1) 452 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.10.2 IDU EXTENSION unit replacement procedure (CH0) 456 . . . . . . . . . . . . . . . . . . . . . . . . .

4–5.11 ODU replacement 460 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.12 Faulty unit repair and Repair Form 463 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–5.12.1 Faulty unit sending back to repair center 463 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5.12.2 Repair Form filling 463 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

4–6.2.1 Introduction 466 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6.2.2 Execution of the Flash Card replacement 467 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–7 SYSTEM HARDWARE UPGRADE 469 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7.1 Installation of plug–ins 469 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–7.1.1 Introduction 469 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7.1.2 Procedure 470 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–7.2 Upgrade from 1+0 to 1+1 configuration 476 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7.2.1 Preface 476 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7.2.2 Procedure 477 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–7.3 Flash Card upgrade 479 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7.3.1 Introduction 479 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

17 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

4–7.3.2 Summary procedure for both stations 480 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7.3.3 Ordering the new Flash Card 481 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7.3.4 Installation of a new Flash Card fully configured in factory 482 . . . . . . . . . . . . . . . . . . . . . 4–7.3.5 Installation of a new Flash Card not configured in factory 483 . . . . . . . . . . . . . . . . . . . . . .

4–8 SWP DOWNLOAD TOWARD NE 485 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8.1 Requirements 485 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–8.1.1 Craft Terminal 485 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8.1.2 NE state 485 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8.1.3 Operator skills and profile 485 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–8.2 Summary of the SWP download phases 486 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8.3 CT start–up, NE login and initial checks 486 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8.4 SW download to the NE 487 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8.5 Activation of the new Software Package on the NE 492 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8.6 Additional operations for upgrade from V2.1.0 494 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8.7 MIB save 494 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–9 ECT & NE UPGRADE FROM V2.1.0 TO V2.1.1 495 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–10 SWP DE–INSTALLATION 497 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 5: APPENDICES 499 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–1 APPENDIX A: SAFETY–EMC–EMF–ESD NORMS AND EQUIPMENT LABELLING 501 . . . . . 5–1.1 Introduction 501 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.2 Compliance with International Standards 501 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3 Safety Rules 502 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–1.3.1 General Rules 502 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3.2 Labels Indicating Danger, Forbiddance, Command 503 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3.3 Dangerous Electrical Voltages 504 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3.4 Risks of Explosions 505 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3.5 Moving Mechanical Parts 505 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3.6 Equipment connection to earth 506 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3.7 Heat–radiating Mechanical Parts 506 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3.8 Microwave radiations (EMF norms) 507 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.3.9 Specific safety rules in this Manual 508 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–1.4 Electromagnetic Compatibility (EMC norms) 509 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.4.1 EMC General Norms – Installation 509 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.4.2 EMC General Norms – Turn–on, Tests & Operation 509 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.4.3 EMC General Norms – Maintenance 509 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–1.5 Equipment protection against electrostatic discharges 510 . . . . . . . . . . . . . . . . . . . . . . . . 5–1.6 Suggestions, notes and cautions 510 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1.7 Labels affixed to the 9400AWY equipment 510 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–2 APPENDIX B: TCO SUITE START–UP SPECIAL CONDITIONS 511 . . . . . . . . . . . . . . . . . . . . . .

5–3 APPENDIX C: ADDITIONAL SW INSTALLATION OPERATIONS FOR NE MANAGEMENT THROUGH THE NE’S ECT SERIAL PORT 517 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–3.1 Foreword 517 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3.2 Installation of LLMAN from the SWP CD–ROM 519 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–3.2.1 Operations sequence 519 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3.2.2 Next step 521 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–3.3 Installation and configuration of Alcatel Virtual Network Card for Lower Layers 522 . 5–3.3.1 Important warning 522 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3.3.2 Choice of the procedure, according to Windows platform 522 . . . . . . . . . . . . . . . . . . . . . . 5–3.3.3 Windows NT 4.0 523 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3.3.4 Windows 2000 529 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

18 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

5–3.3.5 Windows XP (Professional Edition only) 537 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3.3.6 Check for the “Network Connections” order 546 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–4 APPENDIX D: GENERAL ON ETHERNET PORT CHARACTERISTICS AND MANAGEMENT 547 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–4.1 Ethernet Physical Interface 547 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4.2 MDI/MDIX crossover 547 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4.3 Frame size, Rx checksum and FCS 547 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4.4 Ethernet capacity 547 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4.5 Ethernet flow control 548 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4.6 Ethernet interface management 548 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4.7 Ethernet Switch 549 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–5 APPENDIX E: ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE NETWORK 553 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–5.1 Introduction 553 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5.2 Certified equipment 554 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5.3 Connection cables 555 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5.4 Modem setting 556 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–5.4.1 Setting of Sportster Flash Modem & 3Com 56K Faxmodem 556 . . . . . . . . . . . . . . . . . . . . 5–5.4.2 TD–32 AC Modem setting 558 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–5.5 PC laptop “Dell Latitude” setting 559 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5.6 Setting up the connection 560 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5.7 Changing the ECT–equipment connection speed 561 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–5.7.1 Introduction 561 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5.7.2 Configuration at NE side 561 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5.7.3 Configuration at PC side 562 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–6 APPENDIX F: PART LISTS OF TOOL KITS 563 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6.1 Installation Tool Kit part list 563 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6.2 Maintenance Tool Kit part list 564 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6.3 Station Tool Kit part list 565 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–7 APPENDIX G: DOCUMENTATION GUIDE 567 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7.1 Guide to this Manual 567 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–7.1.1 Applicability of this Manual 567 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7.1.2 Purpose of this Manual 568 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–7.2 Documentation set description 569 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7.2.1 9400AWY 2.1.1 Customer Documentation 569 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7.2.2 Product Release Note 571 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7.2.3 Additional documentation for 1320CT platform 571 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–7.3 General on Alcatel–Lucent Customer Documentation 572 . . . . . . . . . . . . . . . . . . . . . . . . . 5–7.3.1 Customer–Independent Standard Customer Documentation 572 . . . . . . . . . . . . . . . . . . . 5–7.3.2 Product levels and associated Customer Documentation 573 . . . . . . . . . . . . . . . . . . . . . .

5–8 APPENDIX H: LIST OF SYMBOLS AND ABBREVIATIONS, GLOSSARY OF TERMS 575 . . . 5–8.1 List of symbols 575 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8.2 List of abbreviations 575 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8.3 Glossary of terms 585 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5–9 APPENDIX I: CUSTOMER DOCUMENTATION FEEDBACK 589 . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

19 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

LIST OF FIGURES AND TABLES

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

20 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

Fig. 51. 7–8 GHz ODU’s BRANCHING box mistake–proofing 125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 52. Label affixed inside the ODU BRANCHING box 126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 53. Java installation request 148 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 54. JRE installation completion 148 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 55. TCO Suite Start.html page (CD–ROM version) 149 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 56. TCO Suite Start.html page (Local version) 149 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 57. TCO Suite AS.html page (Advanced Settings) 151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 58. Internet Explorer: .exe files management 152 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 59. ECT–NE “Direct” and “Remote” connections 154 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 60. Network Adapter selection 154 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 61. Network Adapter details 155 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 62. Direct or Remote connection by the TCO Suite 156 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 63. NE login by the TCO Suite 157 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 64. TCO Suite’s Alarms & Settings Main Menu screen 157 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 65. TCO Suite’s Alarms & Settings “Date & Time Configuration” page 159 . . . . . . . . . . . . . . . . . . . Fig. 66. TCO Suite’s Alarms & Settings “Configuration Setting” page 160 . . . . . . . . . . . . . . . . . . . . . . . . Fig. 67. TCO Suite’s Alarms & Settings “Get Report Request” 161 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 68. TCO Suite’s Alarms & Settings “Get Configuration” Request 164 . . . . . . . . . . . . . . . . . . . . . . . . Fig. 69. TCO Suite’s Alarms & Settings “Active Alarms: Static Page” 165 . . . . . . . . . . . . . . . . . . . . . . . . Fig. 70. TCO Suite’s Alarms & Settings “Active Alarms: Automatic Page” 165 . . . . . . . . . . . . . . . . . . . . Fig. 71. TCO Suite’s Alarms & Settings “Power Measurement” 166 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 72. TCO Suite’s Alarms & Settings “Reading Software License” 166 . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 73. TCO Suite’s Alarms & Settings “Changing F–Interface Speed” 167 . . . . . . . . . . . . . . . . . . . . . . Fig. 74. TCO Suite’s Alarms & Settings “NAT option” 168 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 75. NAT router 168 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 76. MAIN Unit front side: interfaces for equipment control 170 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 77. Choice of Serial or Ethernet interface for PC–NE physical connection 174 . . . . . . . . . . . . . . . . Fig. 78. Network Element Synthesis screen (NE locally connected) 175 . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 79. Network Element Synthesis screen (empty map) 175 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 80. SNMP NE creation in the Network Element Synthesis map 176 . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 81. Network Element Synthesis screen after SNMP NE creation 176 . . . . . . . . . . . . . . . . . . . . . . . . Fig. 82. Start supervision 177 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 83. NE in supervised state 177 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 84. Show Equipment 179 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 85. Login screen 179 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 86. NE Stop Supervision 180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 87. 9400AWY Main view organization 181 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 88. Main tool bar 183 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 89. NE Time dialogue box 190 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 90. Network Configuration menu 191 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 91. Local Configuration dialogue box 192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 92. NTP Configuration dialogue box 193 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 93. Map 194 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 94. Ethernet Configuration dialogue box 195 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 95. IP configuration screen 196 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 96. IP static routing configuration screen 197 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 97. Create Static routing 198 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 98. Point To Point Interface Choice 199 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 99. OSPF Area configuration screen 200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 100. Create New OSPF Area 201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 101. IP Address configuration of Point–To–Point Interfaces screen 202 . . . . . . . . . . . . . . . . . . . . . . Fig. 102. IP Address and Timeslot configuration of Point–To–Point In–Frame E1 TMN 203 . . . . . . . . . Fig. 103. Routing information screen 204 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 104. Alarm Severities Profile 206 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 105. Name of a cloned alarm profile 207 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

21 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

22 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

Fig. 161. Mux Protection 258 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 162. Mux Protection Switch (example for Main #1 selected) 259 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 163. Radio Protection View 260 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 164. Radio Protection Switch (example for Main #1 selected) 261 . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 165. Transmission Protection View 262 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 166. HSB Tx Protection Commands (example for Main #1 selected) 263 . . . . . . . . . . . . . . . . . . . . . Fig. 167. Rx Static Delay menu 264 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 168. Rx Static Delay panel – Warning message for fail 264 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 169. Rx Static Delay in auto mode 265 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 170. Near end IDU cable loopback 267 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 171. Far end IDU tributary loopback 267 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 172. Near end tributary loopback 268 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 173. Near end ODU cable loopback 268 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 174. Near end RF loopback 268 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 175. Available loopbacks 269 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 176. 1+0 Loopback types 270 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 177. 1+1 Loopback types 271 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 178. Loop–back View for PDH Tributaries (1+0) 272 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 179. Loop–back View for PDH Tributaries (1+1) 273 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 180. Loop–back View for Radio PDH 273 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 181. Loop–back CABLE 274 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 182. Loopback activation 275 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 183. Loopback removing 276 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 184. Alarm Counter Summary Window 278 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 185. Alarm Sub–list Window 279 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 186. Log Browsing Sub Menu 279 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 187. Alarm Log Display 280 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 188. Event Log Display 280 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 189. Transfer Information Box 281 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 190. SW Trace Log 281 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 191. Remote Inventory screen (example) 283 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 192. Abnormal Condition List screen 284 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 193. Summary Block Diagram View example: 1+0 16E1 without Ethernet ports 286 . . . . . . . . . . . Fig. 194. Summary Block Diagram View example: 1+1 HSB 16E1 with Ethernet ports 286 . . . . . . . . . Fig. 195. Summary Block Diagram View example: 1+1 HSB 16E1–ETH with Audio/User Service Channel Plug–In (Lockout) 287 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 196. Summary Block Diagram View example: 1+1 FD 32E1 with Audio/User Service Channel Plug–In 287 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 197. Current Configuration view screen 288 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 198. Radio sections 289 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 199. Performance View 290 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 200. Threshold table association screen 291 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 201. Current Data View 292 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 202. History Data 294 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 203. Threshold table 295 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 204. Thresholds Table creation 296 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 205. Server access configuration screen 297 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 206. Init Software Download screen 298 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 207. SW Status screen 299 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 208. SW Unit Status screen 300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 209. Allowed MIB management tasks at “NE logged–in” level 301 . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 210. Allowed MIB management tasks at “Network Element Synthesis” level 301 . . . . . . . . . . . . . . Fig. 211. Launch of MIB save to disk 302 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 212. MIB save to disk – phase 1 302 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 213. MIB save to disk – phase 2 303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

23 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

24 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

Fig. 264. Quick Configuration Procedure: EOW and Auxiliary Interface configuration (Step J) 366 . . . Fig. 265. Quick Configuration Procedure: External Input and Output Points configuration (Step K) 367 Fig. 266. Quick Configuration Procedure: Summary (Step L) 368 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 267. ODU(s) alarm status 369 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 268. Transmit power check 370 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 269. Received power check 371 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 270. Received power details 372 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 271. NES window local NE 374 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 272. Create NE in the CT map 375 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 273. NMS Radio side Remote NE acquisition 375 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 274. Test bench for tributary quality test 376 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 275. Test bench for User service channel quality test 376 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 276. 1+0 Summary block diagram view 383 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 277. 1+1 Summary block diagram view 383 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 278. Channel 0 lockout mode 384 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 279. Near End loopbacks points 385 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 280. Loopback control in the CT 386 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 281. Far End loopback point 387 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 282. Test bench for tributary functionality check 388 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 283. Tributary alarm status monitoring 389 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 284. Test bench for User Service Channel functionality check 390 . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 285. Test bench for Optional Ethernet Data Channel functionality (with 4xGigabit Ethernet plug–in) 391 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 286. Engineering order wire organization 393 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 287. Channel 1 forced mode 394 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 288. Test bench for hop stability test 396 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 289. Test bench for NMS Line side acquisition 397 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 290. NES window local NE 398 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 291. Create NMS Line side NE in the CT map 398 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 292. NMS Line side NE monitoring in the CT map 399 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 293. Test bench for EOW line side functionality test 400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 294. Light service kit cable 405 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 295. Special extractor to remove the coaxial cables 1.0/2.3 416 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 296. Lever for ODU mounting/dismounting 417 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 297. LEDs and pushbutton on IDU Extension unit for maintenance purposes 421 . . . . . . . . . . . . . Fig. 298. LEDs and pushbutton on IDU MAIN unit for maintenance purposes 422 . . . . . . . . . . . . . . . . . Fig. 299. Checks on Radio domain : Alarms 424 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 300. Checks on Radio domain : Configuration 424 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 301. Checks on Radio domain : Frequency 425 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 302. Checks on Radio domain : RTPC & ATPC 426 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 303. Checks on Radio domain : non–intrusive BER measurement 426 . . . . . . . . . . . . . . . . . . . . . . . Fig. 304. Checks on Radio domain : Power Measurement 427 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 305. Corrective Maintenance general flow–chart 433 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 306. Troubleshooting starting with visual indications 435 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 307. Alarm and status synthesis indications 437 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 308. Active alarm screen 439 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 309. Lower Layers Manager screen 444 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 310. Abnormal condition list 448 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 311. Tx Mute functionality 449 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 312. Tributaries 17 to 32 visible in “16E1+ Ethernet” configuration 450 . . . . . . . . . . . . . . . . . . . . . . . Fig. 313. Details for IDU MAIN unit or FLASH CARD replacement 452 . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 314. Details for IDU EXTENSION unit replacement 456 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 315. Repair form 464 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 316. Dismounting the fixing brackets and cover unfix 470 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 317. Release and sliding out the cover 471 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

25 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

Fig. 318. Removing the cover 472 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 319. Dismounting the metal plate 472 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 320. Connectors and columns for plug–in fixing by screws 473 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 321. Plug–in insertion and fix 474 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 322. Server Access Configuration start up 487 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 323. Server Access Configuration set–up screen 488 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 324. Init SW Download start–up 489 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 325. Init download 490 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 326. SW Status 492 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 327. Stand by SW activation 492 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 328. Forced Init download 494 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 329. Security Questions: Secure Content 511 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 330. Secure Questions: Allow Secure Content 512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 331. Execution confirmation (Security Warning) 512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 332. Security Warning (English browser on Italian System) 513 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 333. Security Warning (Italian browser on Italian System) 513 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 334. Security Warning (Java 1.4) 514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 335. Wrong Security Warning (Java 1.3) 514 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 336. Firefox browser: no JRE installed 515 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 337. Firefox plug–in search 515 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 338. Firefox plug–in installation 516 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 339. CD–ROM TCO Suite Main Menu screen 517 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 340. CD–ROM TCO Suite Advanced Settings screen 518 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 341. Alcatel Lower Layers Manager ”splash screen” 519 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 342. Alcatel Lower layers Manager language selection 519 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 343. Alcatel Lower Layers Manager Installation screens 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 344. Alcatel Lower Layers Manager setting screen 521 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 345. Windows NT installation step 1 523 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 346. Windows NT installation step 2 524 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 347. Windows NT installation step 3 524 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 348. Windows NT configuration step 1 525 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 349. Windows NT configuration step 2 526 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 350. Windows NT configuration step 3 526 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 351. Windows NT configuration step 4 527 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 352. Windows NT configuration step 5 528 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 353. Windows NT configuration step 6 528 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 354. Windows 2000 installation step 1 529 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 355. Windows 2000 installation step 2 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 356. Windows 2000 installation step 3 531 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 357. Windows 2000 installation step 4 531 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 358. Windows 2000 installation step 5 532 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 359. Windows 2000 configuration step 1 533 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 360. Windows 2000 configuration step 2 534 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 361. Windows 2000 configuration step 3 535 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 362. Windows XP installation step 1 538 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 363. Windows XP installation step 2 539 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 364. Windows XP installation step 3 540 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 365. Windows XP installation step 4 540 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 366. Windows XP installation step 5 541 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 367. Windows XP configuration step 1 542 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 368. Windows XP configuration step 2 543 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 369. Windows XP configuration step 3 544 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 370. Windows XP configuration step 4 545 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 371. Check for the “Network Connections” order 546 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 372. ECT–Equipment connection via Public Switched Telephone Network 553 . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

26 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

Fig. 373. ECT–Local external Modem cable 555 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 374. F Interface–Remote Modem cable 555 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 375. TD–32 AC modem dip–switch setting 558 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 376. Alcatel Lower Layers utility 562 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 377. Example of Product levels and associated Customer Documentation 574 . . . . . . . . . . . . . . . .

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

27 / 5923DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

28 / 592 3DB 16142 EAAA Ed.02


9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

a ) END OF SECTION

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

29 / 5923DB 16142 EAAA Ed.02

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

SECTION 1: SYSTEM DESCRIPTION

This section provides general warnings, the equipment description (at system, IDU and ODU levels),introduces the basic information regarding the 9400AWY Rel.2.1 HW and SW installation andcommissioning and those regarding the software management, and gives its technical characteristics.

SECTION CONTENT PAGE

Chapter 1–1 – About this manualIt deals with:– Preliminary information– New features with respect to SWP Version V2.1.0– Structure of this manual– Notes on present edition– Safety–EMC–EMF–ESD norms and equipment labelling (summary)– Cautions to avoid equipment damage

31

Chapter 1–2 – System overviewIt gives the 1st level description of the equipment architecture, system configurationsof the 9400AWY Rel.2.1. Moreover, it gives the basic information regarding theEquipment Craft Terminal and TCO Suite, as well those concerning the main phasesfor 9400AWY HW and SW installation, and those regarding the softwaremanagement, with particular emphasis on SWP release and versions upgradingsituations.

37

Chapter 1–3 – IDU provisioning and descriptionIt contains the whole logical and operative information on:– provisioning of equipment items (P/Ns, equipping rules)– their physical and logical position in the system– unit assembly/subassembly and front panel drawings, with the description on

the access point usage (connectors, visual indicators, buttons)– pinout description of connectors for Customer implementation– summary and operative information on characteristics of external interfaces

67

Chapter 1–4 – ODU provisioning, characteristics and descriptionIt describes in detail the ODU physical configurations, relevant provisioning andoperative information for installation, commissioning and maintenance purposes

97

Chapter 1–5 – Technical specificationsIt describes the technical characteristics of the 9400AWY Rel.2.1.

127

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

30 / 592 3DB 16142 EAAA Ed.02

USER MANUAL9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1SYSTEM DESCRIPTION

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

31 / 5923DB 16142 EAAA Ed.02


1–1 ABOUT THIS MANUAL

1–1.1 Preliminary information

a ) Warranty

Any warranty must be referred exclusively to the terms of the contract of sale of the equipment towhich this handbook refers to.

Alcatel–Lucent makes no warranty of any kind with regards to this manual, and specifically disclaimsthe implied warranties of merchantability and fitness for a particular purpose. Alcatel–Lucent will notbe 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 informationpurposes only and are subject to change without notice. They do not represent any obligation on thepart of Alcatel–Lucent.

c ) Copyright Notification

The technical information of this manual is the property of Alcatel–Lucent and must not be copied,reproduced or disclosed to a third party without written consent.

d ) Safety recommendations

The safety recommendations here below must be considered to avoid injuries on persons and/ordamage to the equipment:

1 ) Service Personnel

Installation and service must be carried out by authorized persons having appropriate technicaltraining and experience necessary to be aware of hazardous operations during installation andservice, so as to prevent any personal injury or danger to other persons, as well as preventdamaging the equipment.

2 ) Access to the Equipment

Access to the Equipment in use must be restricted to Service Personnel only.

3 ) Safety Rules

Recommended safety rules are indicated in para.5–1.3 on pages 502.

Local safety regulations must be used if mandatory. Safety instructions in this handbook shouldbe used in addition to the local safety regulations. In case of conflict between safety instructionsstated 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 inparticular on the equipment subject of this handbook.

An adequate background is required to properly install, operate and maintain equipment. The fact ofmerely reading this handbook and the associated handbooks indicated in para. 5–7.2.1 on page 569is considered as not enough.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

32 / 592 3DB 16142 EAAA Ed.02


1–1.2 New features with respect to SWP Version V2.1.0

This manual describes the 9400AWY Rel.2.1 equipment running with SWP version V2.1.1.This table sums–up the main additional features (mainly related to new HW items and new SW featuresaffecting the Graphical User Interface) of SWP version V2.1.1 with respect to previous version V2.1.0:

Tab. 2. Main additional features with respect to SWP version V2.1.0

Replacement of optional Data plug–in (with 2 Fast Ethernet ports) with the new optional Enhanced Dataplug–in (with 4 Gbit Ethernet ports):– System & HW on pages: 42 , 44 , 45 , 68 , Tab. 7. from page 70 , 76 , 282 , 331 , 334 ,

335 , 378 , 391 , 469 , 474– SW management on pages:

210 , from 231 to 232 , from 347 to 351– fully new Appendix D from page 547

New Power Measurement screen in TCO Suite Alarms & Settings functions: para.2–2.3 on pages156 to 158 , 166

New possible definition of the E1#1 Timeslot number for the TMN in–frame, on pages 89 , 203 and363

For additional information, refer to the Product Release Note (see para.5–7.2.2 on page 571 )

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

33 / 5923DB 16142 EAAA Ed.02


1–1.3 Structure of this manual

Information in this manual is divided into the following parts:

a ) FRONT MATTER• FRONT PAGE• QUICK GUIDE

The Quick guide allows to access immediately the most frequently needed operative piecesof information contained in this manual and in other related handbooks.

• TABLE OF CONTENTS• LIST OF FIGURES AND TABLES

b ) SECTION 1: SYSTEM DESCRIPTION on page 29This section provides general warnings, the equipment description, introduces the basic informationregarding the 9400AWY Rel.2.1 HW and SW installation and commissioning, and those regardingthe software management, and gives its technical characteristics.Moreover, it contains the whole logical and operative information on:• provisioning of equipment items (P/Ns, equipping rules)• their physical and logical position in the system• unit assembly/subassembly and front panel drawings, with the description on the access point

usage (connectors, visual indicators, buttons)

c ) SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL on page 139In this section, the description of the TCO suite, and the NE functionalities available in the CraftTerminal are given.

d ) SECTION 3: INSTALLATION AND COMMISSIONING on page 307This section provides the whole operative instructions for the equipment HW and SW installation andcommissioning.

e ) SECTION 4: MAINTENANCE AND UPGRADE on page 407This section contains the whole logical and operative information for the equipment maintenance andsystem SW and HW upgrade.

f ) SECTION 5: APPENDICES on page 499In this section some additional information and instructions are given:• Appendix A – Safety–EMC–EMF–ESD norms and equipment labelling• Appendix B – TCO suite start–up special conditions• Appendix C – Additional SW installation operations for NE management through the

NE’S ECT serial port• Appendix D – General on Ethernet port characteristics and management• Appendix E – ECT–Equipment connection via public switched telephone network• Appendix F – Part lists of tool kits• Appendix G – Documentation guide• Appendix H – List of symbols and abbreviations, Glossary of terms• Appendix I – Customer documentation feedback

g ) Handbook print and assembly instructions This part (after handbook last page 592 ):• is not present in the handbook paper copy, if supplied by Alcatel–Lucent 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 Alcatel–Lucent factory.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

34 / 592 3DB 16142 EAAA Ed.02


1–1.4 Notes on present edition

ED.02 is the first validated and released edition associated to SWP 9400AWY R.2.1 V2.1.1 final VersionV2.1.1 , and fully annuls and replaces previous ED.01 (same P/N), that was issued in association withpre–release V2.1.1*.

WARNING: If you have a SWP version different from final V2.1.1, use neither this manual northe CD–ROM containing it, but those specific for such a version (refer toAlcatel–Lucent).

For detailed information regarding the applicability and purpose of this manual, please refer to para.5–7.1on page 567

WARNING: Ed.02 of this manual is validated in conjunction with SWP final version V2.1.1 only.Information relevant to SWP versions different from V2.1.1 , if any, must beconsidered preliminary, subject to change and without any obligation on the partof Alcatel–Lucent.

Following information can be useful for users owing the previous edition of this manual. Other users cansimply ignore it.This edition has been made for the following major changes:

– elimination of information regarding the old–type Data plug–in (2 Fast Ethernet ports), throughoutthe whole manual

– updated information regarding the Flash Cards on pages 93 to 95– updated information regarding the Graphical User Interface, throughout the whole manual,

according to final Version V2.1.1– improved description of ECT & NE upgrade from V2.1.0 to V2.1.1 from page 495– appendix Documentation Guide from page 567 updated for new CD–ROM and handbooks

INFORMATION FOR ALCATEL–LUCENT INTERNAL USE ONLY

EDDATE

(yymmdd)CHANGE NOTE

(ECO)APPRAISAL AUTHORITY ORIGINATOR

02 080125 00000 57267 M.Nosari, C.Van Kerrebroeck E.Corradini

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

35 / 5923DB 16142 EAAA Ed.02


1–1.5 Safety–EMC–EMF–ESD norms and equipment labelling

a ) Please refer to Appendix A on page 501 to obtain details regarding following information:

• Safety rules:

TOPIC WARNING LABEL ON EQUIPMENT

General rules

Dangerous Electrical Voltages

Equipment connection to earth

Risk of explosion

Moving mechanical parts

Heat–radiating mechanical parts

Equipment emitting RF power (EMF norms)

• Other labels:

TOPIC WARNING LABEL ON EQUIPMENT

Device sensitive to electrostatic discharges

2002/96/EC WEEE (Waste Electrical andElectronic Equipment) Logo

• Electromagnetic Compatibility (EMC norms)

• Other Labels affixed to the Equipment

b ) Identical or similar information on Personal Computer, Work–Station etc., other thanAlcatel–Lucent’s, loaded with software applications described in this or other Handbooks, issupplied in the Constructor’s technical documentation.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

36 / 592 3DB 16142 EAAA Ed.02


1–1.6 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 mustbe considered an unique item from the service and maintenance points of view. Such an assemblyis supplied by Alcatel–Lucent “as it is” and must never be disassembled , with the exception ofoperations described in para.4–7.1, that must be carried out exactly as described.

b ) Antistatic protection device kit

Whenever is necessary to handle spare parts and boards out of their own box, this kit (Fig. 1. below)must be always warn and its termination must be connected to a grounded structure, to avoid thepossible damage of the electronic devices for electrostatic discharges.

ELASTICIZED BAND

COILED CORD

Fig. 1. Antistatic protection device kit

c ) Screw fixing

In normal operation conditions, all screws (for unit box closing, cable fixing, etc.) must be alwaystightened to avoid item detachment and to ensure the equipment EMI–EMC performance.The screw tightening torque must be:

2.8 kg x cm (0.28 Newton x m) � 10 %2.4317 in lb (0.2026 ft lb) � 10 %

Exceeding this value may result in screw breaking.

d ) IDU–ODU cable disconnection / connection

Before to disconnect or connect the IDU–ODU cable (at IDU or ODU side) switch off thecorresponding IDU Main Unit or IDU Extension Unit.

e ) Craft Terminal connection

To connect the CT cable (at IDU Main Unit’s F or OS Ethernet interface and/or PC side):• verify that the PC is switched off (if switched on, close all running applications, then switch off

it)• connect suitable cable to IDU Main Unit’s F or OS Ethernet interface and PC side• now the PC can be safely switched on.

f ) Craft Terminal disconnection

To disconnect the CT cable (at IDU Main Unit’s F or OS Ethernet interface and/or PC side):• perform the logoff, exiting from the CT applications (details in para.2–2.5.3 and 2–2.5.4 on page

180)• close all other running applications, if any• switch off the PC• now the cable can be safely disconnected.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

37 / 5923DB 16142 EAAA Ed.02


1–2 SYSTEM OVERVIEW

This chapter gives the 1st level description of the equipment architecture and system configurations of the9400AWY Rel.2.1; it includes the following main parts:

– Introduction, herebelow– Equipment architecture, on page 39– System configurations, on page 50– Equipment Craft Terminal and TCO Suite, on page 54– Flash Card types and content, on page 56– General on equipment installation and SWP installation and management, on page 58

1–2.1 Introduction

The 9400AWY is a family of digital Point to Point microwave PDH and Ethernet radio systems coveringthe frequency range from 7 GHz to 38 GHz, consisting of an Indoor Unit (IDU) providing the basebandprocessing and tributaries interfaces as well as service channel and supervision, and an Outdoor Unit(ODU).

IDU and ODU are connected with a single standard coaxial cable (max length specified in para.1–5.5 onpage 135 ) carrying the main traffic, the remote power supply voltage for the ODU and auxiliary information.

As shown in Fig. 2. below, one 9400AWY radio link is composed by two 9400AWY Network Elements(ULS NE), having the same hardware and software configurations, with the exception of the go and returnchannel frequencies (complementary to each other), and the supervision network’s NE specific data.

IDU

ODUODU

IDU

ETSI PDHETHERNET

SERVICE CH.

ETSI RADIO

SUPERVISIONNETWORK

9400AWYULS NE “A”

9400AWYULS NE “B”

ETSI PDHETHERNET

SERVICE CH.

Fig. 2. 9400AWY radio link

N.B. With the exception of Chapter 3–2 – Line–Up and Commissioning on page 329, this Manualdeals with the description of a single 9400AWY Network Element.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

38 / 592 3DB 16142 EAAA Ed.02


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. 3. :

Tab. 3. Tributaries and modulations

Market Max PDH TributariesMax Ethernet

TributariesRadio Modulation

2xE1 4 x GE 4QAM

4xE1 4 x GE 4QAM / 16QAM

ETSI 8xE1 4 x GE 4QAM / 16QAM

16xE1 4 x GE 4QAM / 16QAM

32xE1 0 16QAM

The main functions performed by ULS NE are the following:

– Multiplexer/DemultiplexerThe multiplexer function receives main tributaries and generates a PDH frame.The demultiplexer function receives a PDH frame and generates main tributaries.

– Signal Protection switch (if any)The function provides one protection channel for the main signal against channel–associated failuresfor both hardware failures and temporary signals degradation or losses due to propagation effects(e.g. rain) according to equipment configuration.

– Radio Physical Interface (AWY)The function converts a radio frequency signal into an internal logic level signal, and vice versa(RPPI). Specifically, the following functions are performed:• Modulation and Tx functions in the transmit side• Demodulation and Rx functions in the receive side

ULS NE can be composed by:– one radio channel (1+0 configurations);– two radio channels (1+1 configurations).

The 2+0 configuration is not supported.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

39 / 5923DB 16142 EAAA Ed.02


1–2.2 Equipment architecture

1–2.2.1 Split–mount architecture

The 9400AWY system has been designed in a split mount architecture. As shown in Fig. 3. on page 40, itconsists of three main parts.

– Indoor Unit (IDU) details in paragraph 1–2.2.2 on page 42

– Outdoor Unit (ODU) details in paragraph 1–2.2.3 on page 49

– IDU–ODU cable(s) details in paragraph 1–2.2.4 on page 46

IDU and ODU are connected with a single standard coaxial cable carrying the main traffic, the remotepower 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 fasteningsystem, 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 separateantenna.

The cabinet is a very compact and robust weatherproof (IP 67) container, designed to be compatiblewith hot and very sunny climatic zones.

The ODU can be rapidly installed on standard poles with an appropriate fastening system. The polemounting 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 alteringantenna pointing.

N.B. An IDU+ODU full–indoor configuration (obviously without antenna) is also available; its physicalimplementation is described in the Installation Handbook.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

40 / 592 3DB 16142 EAAA Ed.02


Antenna

IDU

IDU–ODU cable

ODU

NEULS

IDU MAIN UNIT Ch#1

ODU Ch#1

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

DISTRIBUTOR SHELF (optional)

IDU

ODU

NEULS

IDU–ODU cables

9400AWY R.2.1 (1+1) SPLIT–MOUNT SYSTEM

for possible ODU (1+1)configurations

see Fig. 4. on page 41

A

B

C D

Legend:D SERVICE CHANNELS PROTECTION BOXC E1 PROTECTION BOXB IDU MAIN UNIT Ch#1A IDU EXTENSION UNIT Ch#0

DISTRIBUTOR SHELF (optional)

Fig. 3. 9400AWY R.2.1 split–mount system

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

41 / 5923DB 16142 EAAA Ed.02


Antenna CH 0

ODU CH 0

Antenna CH 1

ODU CH 1

to IDU MAIN UNITto IDU EXTENSION UNIT

ODU (1+1) HSB–SD or FD–DA AP with two antennas

ANTENNA

ODU CH 0

ODU CH 1


COUPLER

ODU (1+1) HSB with one antenna

N.B. this drawing is an example referred to the coupler used in13–38 GHz configurations.Couplers used in 7–8 GHz configurations are shown inFig. 44. on page 117.

Double Polar Antenna

ODU CH 0 ODU CH 1


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

Fig. 4. Possible configurations of ODU (1+1)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

42 / 592 3DB 16142 EAAA Ed.02


1–2.2.2 IDU (Indoor Unit)

The IDU incorporates the base–band processing and offers tributaries interfaces as well as servicechannel and supervision.The IDU is frequency–independent, but capacity–dependent.

As shown in Fig. 3. on page 40, up to 2 active subracks (the Main IDU unit and the Extension IDU unit)and some additional passive boxes are used as basic elements to build the following configurations:

– 1+0: this configuration includes:• one Main IDU unit• up to two optional IDU Distributor Shelves• and necessary interconnection cables.

Fig. 7. on page 44 shows the block diagram.

– 1+1: this configuration includes:• one Main IDU unit• one Extension IDU unit• one E1 Protection Box• one Service Channels Protection Box (only if the optional “AUDIO + USER SERVICE

CHANNEL” plug–in is equipped)• up to two optional IDU Distributor Shelves• and necessary interconnection cables.

Fig. 8. on page 45 shows the block diagram.

In 1+0 and 1+1 configuration:

• both the Main and the Extension IDU units, if not equipped with plugs–in, are physically ableto support up to 16xE1 interfaces. Such capacity can be reduced according to the SoftwareLabel employed.

• it is possible to accommodate different types of tributary plug–in alternative to each other,exploiting the same mechanical space on the front panel:

– “17–32xE1 plug–in” , allowing to support the extension to 32xE1 interfaces, to be pluggedonto both Main and Extension units

– “Enhanced DATA plug–in” , implementing Ethernet functionalities, and supporting 4 x10/100/1000 baseT ports. This plug–in is plugged onto the Main IDU unit only.

• independently from the tributary plug–ins listed above, another optional plug–in, to be pluggedonto 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 (100–wiresSCSI front panel connector)

• the protection of E1 signals at line side is achieved by the E1 Protection Box

• the protection of Service Channels signals at line side is achieved by the Service ChannelsProtection Box , provided that the “AUDIO + USER SERVICE CHANNEL” plug–in is equipped.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

43 / 5923DB 16142 EAAA Ed.02


[1] Main IDU unitThis is a common item for 1+0 and 1+1 systems. It includes the Mux/Demux and the cable interfacefunctions for the main channel.Onto the main unit is plugged the microprocessor unit implementing the EC (Equipment Controller)functionalities.For details, refer to para.1–3.3 on page 70 .

[2] Extension IDU unitThis is an item specific for 1+1 systems. It includes the Mux/Demux and the cable interface functionsfor the spare channel.The Hitless Switch functionality (RPS RX) is embedded.For details, refer to para.1–3.4 on page 77 .

[3] Power supplyOne PSU is integrated in each of the Main and Extension units; the main characteristics are:• Floating (48–60) VDC nom. ± 20%N.B. No Fans Unit are foreseen inside the 9400AWY IDU units.

[4] Flash Card and Software LabelA Flash Card (containing the system software, the Software Label, and the NE configuration, evenif this configuration is almost empty ) is always plugged onto the Main unit. The Software Label allowsflexibility in choosing user interfaces and modulation.For details, refer to para.1–3.7 on page 93 .

[5] Protection BoxesThe E1 Protection Box and Service Channels Protection Box, used in 1+1 configurations, areshown in Fig. 5. and Fig. 6. below. They are passive components exploiting the splitting functionsof relevant signals from/to the Main IDU and Extension IDU units and from/to the User lines, asshown in Fig. 8. on page 45 .

equipment sideUser line side

Fig. 5. E1 Protection box

equipment sideUser line side

Fig. 6. Services Protection box

Such boxes have been designed in order to have the connectors present at User line side exactlyequal 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 9400AWYRel.2.1 IDU platform can do it without refurbishing the existing station cabling and DDF wiring.For details, refer to para.1–3.5 on page 79 (E1 Protection Box) and to para.1–3.6 on page 84(Service Channels Protection Box).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

44 / 592 3DB 16142 EAAA Ed.02


[6] Distribution shelves

For the physical connection at station DDF of the User signal cables to the main tributariesconnectors of the IDU Main and Extension units, two main solutions are envisaged:

• usage of the Customer Plant Distributor racks, connected to the IDU main tributariesconnectors by means of Customer own cables or cables supplied by Alcatel–Lucent;

• usage of Alcatel–Lucent distributor subracks, to be housed in the same rack where 9400AWYIDU shelves are installed.

For details, please refer to the Installation Handbook.

[7] IDU configurations from factory

Different IDU configurations (unprotected 1+0 or protected 1+1) are available from factory:

• 16xE1 configurations:– 16xE1 (base configuration)– 16xE1 + AUDIO & USER SERVICE CHANNEL plug–in– 16xE1 + 4 x 10/100/1000 BaseT Ethernet plug–in– 16xE1 + AUDIO & USER SERVICE CHANNEL plug–in + 4 x 10/100/1000 BaseT Ethernet

plug–in

• 32xE1 configurations:– 32xE1– 32xE1 + AUDIO & USER SERVICE CHANNEL plug–in.

All sub–equipped configurations delivered from factory can be upgraded later by means of thespecific upgrade kits, as described in chapter 4–7 on page 469.

[8] Block diagrams

ODU

Main IDU

Alarms& housekeepings

Main board(JBIDUM)

16 E1/DS1plug–in(JAIDUE1)

Audiochannels+ V11 + G703

Plug–in (JAIDUSC)

E3/DS3plug–in

Ethernetdataplug–in

PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)


Audiochannels+ ServiceChannelPlug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)




PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board

16 E1/DS1plug–in

Audiochannels+ ServiceChannelPlug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

uP

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)




PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board

16 E1/DS1plug–in

Audiochannels+ ServiceChannelPlug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

uP

ODU

Main IDU


ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDUMain board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU

Alarms& housekeepingsAlarms& housekeepings

Main board(JBIDUM)



E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU




E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDUMain IDU


Main board(JBIDUM)




PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RCAlarms& housekeepings

1–16E1

Main board(JBIDUM)




PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU




Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU

Alarms& housekeepingsAlarms& housekeepings

Main board(JBIDUM)



E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU




E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU


Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU


Service Channel (64Kbit/s)

Main board(JBIDUM)



Plug–in (JAIDUSC)

E3/DS3plug–in


PSU

MUX/DEMUX

IDU–ODUinterface

EPS

EC / RC

ODU

Main IDU

NMS_V11NMS_G703

Main IDU


ECT OS (or ECT)

10/100 BaseTRS232

Audio channels

Main board

17–32E1 plug–in

Audiochannels+ ServiceChannel

Plug–in

Ethernet plug–in

PSU

MUX/DEMUX

IDU–ODUinterface

EPS

uP

17–32E1

4 x 10/100/1000 BaseT

N.B. Ethernet and 17–32E1 plug–ins are in alternative.

Fig. 7. 9400AWY R.2.1 (1+0) IDU block diagram

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

45 / 5923DB 16142 EAAA Ed.02


OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n (J

AID

USC

)

Eth

erne

tda

tapl

ugin

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ala

rms

&A

larm

s&

hous

ekee

ping

s

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

hous

ekee

ping

s

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

hous

ekee

ping

s

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

16 E

1/D

S1P

lug

–in

–

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

16 E

1/D

S1pl

ug–i

n

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n

Eth

erne

tda

tapl

ugin

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

uP

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n (J

AID

USC

)

Eth

erne

tda

tapl

ugin

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ala

rms

&A

larm

s&

hous

ekee

ping

s

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

hous

ekee

ping

s

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

E3/

DS3

plug

–in

PSU

OD

U

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

hous

ekee

ping

s

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Mai

nbo

ard

(JB

IDU

M)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

Aud

ioch

anne

ls+

V11

+ G

703

Plu

g–i

n (J

AID

USC

)

E3/

DS3

plug

–in

Eth

erne

tda

tapl

ug–i

n

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

EC

/ R

C

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

OD

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

(JB

IDU

E)

16 E

1/D

S1pl

ug–i

n(J

AID

UE

1)

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

16 E

1/D

S1P

lug

–in

–

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ext

ensi

onID

U

Serv

ice

Cha

nnel

(64K

bit/s

)

Ext

ensi

onbo

ard

PSU

OD

U

NM

S_V

11

NM

S_G

703

Mai

nID

U

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Ala

rms

&ho

usek

eepi

ngs

EC

TO

S (o

r E

CT

)

10/1

00B

aseT

RS–

232

Aud

ioch

anne

ls

Serv

ice

Cha

nnel

(64K

bit/s

)

Mai

nbo

ard

Aud

ioch

anne

ls+

Serv

ice

Cha

nnel

Plu

g–in

PSU

MU

X/D

EM

UX

IDU

–OD

Uin

terf

ace

EP

S

IDU

–OD

Uin

terf

ace

EP

S &

RP

S

MU

X/D

EM

UX

Inte

rcon

nect

ion

cabl

e

uP

Eth

erne

t pl

ug–i

n

17–3

2E1

plug

–in

17–3

2E1

plug

–in

1–16

E1

1–16

E1

17–3

2E1

17–3

2E1

1–16

E1

17–3

2E1

E1

PR

OT

EC

TIO

N B

OX

SER

VIC

E C

HA

NN

EL

SP

RO

TE

CT

ION

BO

X

Serv

ice

Cha

nnel

s

(64K

bit/s

)

4 x

10/1

00/1

000

Bas

eT

N.B. On Main IDU unit, Ethernet and 17–32E1 plug–ins are in alternative.Fig. 8. 9400AWY R.2.1 (1+1) IDU block diagram

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

46 / 592 3DB 16142 EAAA Ed.02


1–2.2.3 ODU (Outdoor Unit)

a ) ODU type:

In 9400AWY R.2.1.1, only the 64Mb V1 ETSI ODU types can be used.

Note for 9400AWY R.2.0 Customers only:Neither the 32Mb ODU types (V1 and V2) nor the 64Mb V2 ODU types (used in 9400AWY R.2.0,from V2.0.5) can be used in 9400AWY Rel.2.1.1 environment.

b ) Air interface compatibility: frame arrangementThe Air frame is the AWY format respecting the bandwidth partitioning between traffic and dedicatedservice channels.

c ) ODU unit

The ODU consists of a cabinet including the modem + transceiver of a channel. The mechanicalstructure utilizes an outdoor IP67 cabinet.

Two mechanical solutions are adopted:

• one for all frequency bands from 13 to 38 GHz, where the branching (diplexer) is internal to theODU cabinet; the only differences among the frequency bands are related to the diplexer andthe RF section;

• another for all frequency bands from 7 to 8 GHz, where ODU is composed by two independentunits: the branching (diplexer) and the RF section (transceiver).

All configurations are available for each frequency band.

The ODU presents one output port at which a single polarization full integrated antenna (30 cm or60 cm diameter) or a waveguide for not integrated antenna connection can be connected.

The ODU consists of subunits which carry out the following main functions (see Fig. 9. on page 47):

[1] Modem: It consists of a base–band part and an IF part. The main functions are:

– Cable interface: DC splitting, echo cancellation, clock recovery– HDB3 coding/decoding– Modulation and demodulation– Digital to analog conversion– Analogue filtering– Up–conversion in Tx side in the frequency range of 1 GHz to 2.1 GHz– Down–conversion in Rx side from 675 MHz to base band– Control function for hardware configuration and dialog with the IDU.

[2] Front–End. The main functions are:

– AGC IF amplification– Up–conversion to the RF Tx channel frequency– Transmit power control range of 30 dB– RF loop–back (N.B.)– Double mixers at Rx side (the frequency of the signal sent to the modem board is 675 MHz

whatever the frequency band and shifter).

N.B. RF loopback is optional and provided only with specific configurations

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

47 / 5923DB 16142 EAAA Ed.02


[3] Synthesizer unit

– The RF LO in the overall frequency range of 3.8 GHz to 5.7 GHz– The IF LO in the frequency range of 1.0 GHz to 2.1 GHz

[4] Power Supply Unit: it is screwed on the Front End box

[5] Microwave Diplexer: it is inserted between the front end and the antenna. Its scope is to filterall interfering signals and harmonics. It consists of two band–pass filters: one for the Rx and onefor the Tx. The rejection between these two parts is more than 70 dB. The insertion losses areless than 2 dB.

Fig. 9. ODU block diagram

d ) Solar shield

Even if the ODU has been designed to work without solar shield, this one is always delivered witheach 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 300019–2–4.1). It assumes that the protection of the solar shield is 15 0C.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

48 / 592 3DB 16142 EAAA Ed.02


e ) ODU configurations

The ODU configurations available are:

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

• for the employment in 1+1 protected systems:– 1+1 HSB– 1+1 HSB SD– 1+1 FD AP– 1+1 FD DA

Tab. 4. below depicts the corresponding radio configurations.

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

Configuration ODU cabinet RF channeling Coupler Antenna

1+0 1 NO 1

1+1 HSB 2 1/10 dB asymmetric 1

1+1 HSB SD 2 NO 2

1+1 FD AP 2 NO1

(non–integratedonly)

1+1 FD DA 2 OR NO 2

Legend:AP = Alternate polarDA = Dual antenna

f ) ODU Coupler

The ODU coupler (shown in Fig. 43. on page 116 for 13–38 GHz bands, and in Fig. 44. on page 117for 7–8 GHz bands) is used in the 1+1 HSB configuration.

The 1+0 configuration is comprised of a simple diplexer inside the cabinet while the protectedconfigurations (1+1) are always comprised of two cabinets and one 1/10 dB asymmetric coupler forHSB configuration.

The couplers are connected between the cabinets and the antenna.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

49 / 5923DB 16142 EAAA Ed.02


1–2.2.4 IDU–ODU cable

The connection between the IDU and the ODU is realized with a single coaxial cable and N–50 ohmconnectors (2 cables in 1+1 configurations).On this cable the following signals are present:

– DC voltage to the remote power supply of the ODU;– HDB3 Tx signal;– HDB3 Rx signal.

The HDB3 signal is an aggregate signal including the main signal, auxiliary signal and the IDU–ODUservice channels.

The bit rate of the aggregate signal is listed in the following table.

Tab. 5. Bit rate of the IDU–ODU 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 IDU–ODU cable is a standard coaxial cable whose characteristics are specified in para.1–5.5 on page135.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

50 / 592 3DB 16142 EAAA Ed.02


1–2.3 System configurations

The configurations available are:

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

– Protected configurations (1+1)described in para.1–2.3.2 on page 51.

N.B. for the detailed description of station layouts and equipment interconnections, refer topara.3–2.2 from page 331 onwards.

1–2.3.1 1+0 Unprotected configurations

The 1+0 unprotected terminal is made up of the following elements:

– one Outdoor Unit (ODU) incorporating the complete RF transceiver (modem, RF units, branchingfilter) and an integrated or separated antenna.The ODU is capacity–independent.

– one Indoor Unit (MAIN IDU unit) incorporating the base–band processing and offering tributariesinterfacing as well as service channel and supervision.The IDU is frequency–independent.

– one optional E1 Protection Box

– one optional Service Channels Protection Box

– one/two optional IDU Distributor Shelf/ves

– one IDU–ODU coaxial cable

Fig. 10. below shows the IDU+ODU block diagram.

IDU 1+0 1 x ODU

RTIDU MAIN UNIT

DISTRIBUTOR SHELF

interconnections IDU–ODU cable

Fig. 10. 9400AWY (1+0) IDU + ODU block diagram

The possible capacities and modulations depend on:

– the (1+0) IDU equipment provisioning (see point [7] on page 44, and and Tab. 6. on page 68)

– and the employed Software Label (see Tab. 23. on page 93)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

51 / 5923DB 16142 EAAA Ed.02


1–2.3.2 1+1 Protected Configurations

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

– para.1–2.3.2.1 below: IDU (1+1) configurations– para.1–2.3.2.2 on page 52 : ODU (1+1) configurations

1–2.3.2.1 IDU (1+1) configurations

The IDU (1+1) system is implemented by:

– one Main IDU Unit (mandatory)

– one Extension IDU Unit (mandatory)

– one E1 Protection Box (mandatory)

– one optional Service Channels Protection Box (mandatory if the AUDIO + USER SERVICECHANNELS plug–in is equipped)

– one/two optional IDU Distributor Shelf/ves

– cables interconnecting IDU units, protection boxes, and Distributor Shelf/ves.

The possible capacities and modulations depend on:

– the (1+1) IDU equipment provisioning (see point [7] on page 44, and Tab. 6. on page 68)

– and the employed Software Label (see Tab. 23. on page 93)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

52 / 592 3DB 16142 EAAA Ed.02


1–2.3.2.2 ODU (1+1) Configurations

According to the ODU configurations introduced in Tab. 4. on page 48, at radio level the following systemimplementations are available:

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

– 1+1 with Frequency Diversity (FD):• FD double antenna AP see Fig. 13. on page 53• FD one antenna AP see Fig. 14. on page 53

N.B. The radio configurations are independent from the IDU (1+1) configurations described inprevious para.1–2.3.2.1 on page 51.

HDB3MODEM IF RF

ODU CH 1

HDB3MODEM IF RF

ODU CH 0IDU EXTENSION UNIT

IDU MAIN UNIT

inte

rcon

nect

ions

only one RTtransmits

IDU 1+1

DISTRIBUTOR SHELF

E1 PROTEC.BOX

SERV.CHAN. PROTEC.BOX

Fig. 11. 9400AWY (1+1 HSB SD) IDU + ODU block diagram

HDB3MODEM IF RF

ODU CH 1

HDB3MODEM IF RF

ODU CH 0

only one RTtransmits

1:10

Coupler

IDU MAIN UNIT

IDU EXTENSION UNIT

IDU 1+1

DISTRIBUTOR SHELF

E1 PROTEC.BOX


inte

rcon

nect

ions

Fig. 12. 9400AWY (1+1 HSB one antenna) IDU + ODU block diagram

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

53 / 5923DB 16142 EAAA Ed.02


HDB3MODEM IF RF

ODU CH 1

HDB3MODEM IF RF

ODU CH 0

both RTstransmit

AP

IDU MAIN UNIT

IDU EXTENSION UNIT

IDU 1+1

DISTRIBUTOR SHELF

E1 PROTEC.BOX


inte

rcon

nect

ions

Fig. 13. 9400AWY (1+1 FD Double Antenna AP) IDU + ODU block diagram

HDB3MODEM IF RF

ODU CH 1

HDB3MODEM IF RF

ODU CH 0

both RTstransmitIDU MAIN UNIT

IDU EXTENSION UNIT

IDU 1+1

DISTRIBUTOR SHELF

E1 PROTEC.BOX


inte

rcon

nect

ions

Fig. 14. 9400AWY (1+1 FD one antenna AP) IDU + ODU block diagram

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

54 / 592 3DB 16142 EAAA Ed.02


1–2.4 Equipment Craft Terminal and TCO Suite

The Local Operator can manage the Equipment software programs and most configuration data throughthe Equipment Craft Terminal 1320CT connected to the Equipment’s F or Ethernet interface.The Craft Terminal characteristics (computer configuration) are listed in para.3–1.1.1 on page 309.The Craft Terminal is a project in charge of the local management of single network elements, providingITU– compliant Information Model Interface to the Network Element.Multiple NE management up to 50 Network elements is possible obtaining a remote Craft Terminalapplication.

The general information on the Craft Terminal is presented in the:

• 1320CT Basic Craft Terminal Operator’s Handbook (see Tab. 78. on page 571)

that the operator has to read before this Handbook.In this Handbook is given the general description regarding use, navigation, rules, etc., common toall the NE using the same Craft Terminal.Furthermore, the same handbook contains the detailed description of common operations as“Installation” and common screens as “Network Element Synthesis view”.The Network Element Synthesis view is the first view presented to the operator entering theapplication.Starting from this view it is possible to login to the NE and then to enter the EML–ULS views, whichdirectly allow to manage the Network Element.

A detailed description of the 9400AWY EML–ULS screens is given in the dedicated Section of thishandbook:

• SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL on page 139

1–2.4.1 ECT

Alcatel–Lucent TMN management products 1320 CT called Craft Terminals (CT) consists of a compatiblepersonal computer and application software specially developed for monitoring transmission equipment.The CT designed to monitor a single transmission equipment is called Equipment Craft Terminal (ECT)or 1320CT.

For each 9400AWY station an Alcatel–Lucent proprietary SWP (SoftWare Package) is employed, whichdepends on the product–release and the NE (Network Element) associated to the specific configuration.

1–2.4.2 RECT

The Remote Equipment Craft Terminal is a feature only present in the Single NE Link architecture whichallows the local operator, using an ECT connected to the F or Ethernet interface of the NE, to zoom andperform a complete set of management operations on all the reachable NEs in the network.

The Remote NE can be physically reached through the NMS channels or Ethernet LAN.

RECT can be connected to any NE pertaining to the same area of the local NE and to any NE pertainingto different areas (assuming that the DCN network has been correctly designed and hence inter–areacommunication is possible from networking viewpoint).Of course, due to the limitation of the physical resources in the Equipment Controller of the NE, somenetwork design constraints must be taken into account as the total number of managed NEs (50).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

55 / 5923DB 16142 EAAA Ed.02


The following limitations must be taken into account, too:

a ) the contemporaneous presence of the RECT function and an OS is possible. The access disable flagavoids access conflict between the OS and both RECT and ECT on some operations as configurationmodification and remote control with access filtering.

b ) the NE which may be remotely controlled by a RECT must be configured and must be loaded withthe same SW version supporting the RECT function. A NE not supporting RECT function will refusethe incoming association issued by a RECT and the ECT displays only local information.

c ) only three RECTs can be active at a time over one NE. The coexistence of ECTs and RECTs in thewhole network is guaranteed since the conflict in configuring the NEs is solved locally by the NE itself.

1–2.4.3 TCO Suite

The TCO Suite is a feature that mainly allows the operator to access and configure the NE from his/herPC without the need for software installation in PC environment (i.e. running the TCO Suite directly fromthe SWP CD–ROM).

TCO Suite works through web pages with simple operations available with a single mouse click.

Please refer to para.2–2.2 on page 146 for details.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

56 / 592 3DB 16142 EAAA Ed.02


1–2.5 Flash Card types and content

Whole Equipment configuration data and programs are contained in the Flash Card, as shown inFig. 15. below:

SWCOMMITVERSION(ACTIVE)

SWSTAND–BYVERSION(not active)

MIB

NE networkrouting data

SW instances

NE Data

SOFTWARE LABELFixed Data

Fig. 15. Flash Card content

[1] Fixed Data

The Software Label stored in the Flash Card (plugged into the IDU Main board as shown inFig. 21. on page 70 and Fig. 34. on page 94) allows flexibility in choosing user interfaces andmodulation as shown in Tab. 23. on page 93The Software Label is strictly associated to the Flash Card Logistical Item, and cannot bechangeable, but with Flash Card upgrade (see para.4–7.3 on page 479).

[2] SW instances

The SW COMMIT VERSION is that used by the system.

The SW STAND–BY VERSION instance is created the first time a SW download from ECT to the NEis carried out.A new SWP download is envisaged whenever a new SWP package version or release (new withrespect to that presently loaded in the system) is supplied to Customer (*).

(*) for the meaning of SWP package version and release refer to para.5–7.3.2 on page 573.

As supplied by Alcatel–Lucent factory, unless differently required by Customer, the SWP–versiondownloaded in Factory is the most recently released at the date of Flash Card delivery to theCustomer, so that the SW instances present in the flash card are:

• the SW COMMIT VERSION

• the SW STAND–BY, loaded with the SW version immediately previous (if any) with respect tothe COMMIT one

The management of these SW instances is described in Chapter 2–13 – Software Managementon page 297.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

57 / 5923DB 16142 EAAA Ed.02


[3] NE data

N.B. as shown in Fig. 15. on page 56, differently from SW instances, NE data are present assingle instances in the Flash Card.

a ) Base configurationIt is defined by Flash Card Logistical Item.It is not changeable, but with Flash Card upgrade (see para.4–7.3 on page 479).

b ) MIBMost (but not all) configuration data set is named MIB (Management Information Base).Such data are defined by Craft Terminal and can be changed only within the limits (Baseconfiguration) implicitly defined by the employed Flash Card type.

As supplied by Alcatel–Lucent factory, the NE configuration data are set to default values

MIB can be saved as a file in the Craft Terminal (or OS) environment, as well can be restoredin the Flash Card retrieving this file from the Craft Terminal (or OS), as described in detail inChapter 2–14 – MIB Management on page 301.

c ) NE network routing dataDefined by Craft Terminal or by TCO Suite Set–Up Tool, they are:

1. Local configuration ⇒ System’s local address2. NTP server configuration3. Interface configuration ⇒ NMS configuration

⇒ Ethernet configuration4. IP configuration ⇒ IP Static Routing configuration

⇒ OSPF AREA configuration

Presently, all those listed parameter are NOT stored into the MIB file.

Nevertheless, it is possible to create, save and recover configuration files having the “.qcml”extension (for details refer to para.3–2.3.6 on page 341). Such a file contains (besides otherdata) the NE network routing data defined above.

As supplied by Alcatel–Lucent factory, the NE network routing data are set to default values.

[4] System restart and system start–up

The system restart (reloading of all RAMs present in the system with information stored in the FlashCard) is carried out:• after the activation of a new SWP• after EC/OC reset (manual of after new SWP activation)• after power off/on , with 2 to 5 minutes necessary for system start–up after the power on.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

58 / 592 3DB 16142 EAAA Ed.02


1–2.6 General on equipment installation and SWP installation andmanagement

This paragraph introduces the basic information regarding the main phases for 9400AWY HW and SWinstallation, and those regarding the software management, with particular emphasis on SWP release andversions upgrading situations.

N.B. Before reading this paragraph, it is suggested to read Flash Card types and content(para.1–2.5 on page 56 ).

N.B. Please refer to para.5–7.3.2 on page 573 for the meaning of SWP Release, Version and PatchLevel.

Information given in the following is:

– Main phases for 9400AWY HW and SW installation on page 59

– First SWP installation in PC and NE environments on page 60

– How to check ECT and NE SWP versions on page 62

– Common situations requiring ECT and/or NE upgrade on page 64

– Flash Card related special procedures on page 64

– Craft Terminal related special procedures on page 64

– NE configuration data change and save on page 65

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

59 / 5923DB 16142 EAAA Ed.02


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

The summary procedure depicted in Fig. 16. below presumes that the SWP version loaded in factoryinside the NE’s Flash Card corresponds to that of the SWP CD–ROM delivered to Customer with theequipment.

N.B. The documents with symbol are included in the same CD–ROM containing this manual.For Installation Handbook or Installation Guide choice, read the specific note in Tab. 77. on page 570

HW INSTALLATIONdescribed in:

ECT INSTALLATIONdescribed in:

9400AWYInstallation Handbook

orInstallation Guide

Chapter 3–1 – SWP installation in PCenvironment on page 309

EQUIPMENT POWER–ON AND COMMISSIONINGdescribed in:

NE DATA SAVEdescribed in

para.1–2.6.8 on page 65

Chapter 3–2 – Line–Up and Commissioningon page 329

and reporting test results in document:

TRS & SAT

CREATION OF NE OPERATOR PROFILESdescribed in

para.2–3.6 on page 214

Fig. 16. Main phases for 9400AWY HW and SW installation

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

60 / 592 3DB 16142 EAAA Ed.02


1–2.6.2 First SWP installation in PC and NE environments

Fig. 17. depicts the main phases for SW management, when it is loaded the first time in PC and NEenvironments.

SWPCD–ROM

CRAFT TERMINAL

1) SWP LOADING IN PC ENVIRONMENT

2) NEW SWPINSTALLATION

3) NE SWP LOADINGINTO EQUIPMENTCONTROLLER(if necessary)

DURATION (about): – 30 minutes with interface F– 15 minutes with Ethernet interface

5) NE CONFIG. DATA MNGT

4) AUTOMATIC SWDOWNLOAD TOSUPERVISOR UNITS(if necessary)

DURATION:some minutes

6) MIB BACK–UP

7) MIB RESTORE

Fig. 17. Software management main phases

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

61 / 5923DB 16142 EAAA Ed.02


The SW management can be distinguished into:

– program management, i.e.:

• (1) and (2) : SWP loading from CD–ROM to the Personal Computer, after which the PCbecomes and can be used as the Equipment Craft Terminal (abbreviated as ECT or CT)

• (3) NE SWP downloading from ECT toward the Network–Element’s Equipment Controller (EC),if necessary (it is necessary if the NE SW–version is lower than that of the ECT)N.B. in general, first–time system installation is carried out with the NE’s flash card loaded

in factory with the same SWP–version of the ECT, so that this phase is usually notnecessary

• (4) SW downloading from EC toward the Peripheral Units, always automatic (this phase iscarried out only whenever the SW–versions present in the Peripheral Units are lower than thoseavailable in the ECT’s SW components)

– NE configuration data management:

• (5) NE configuration data definition and equipment line–up and commissioning

• (6) NE configuration data save in Equipment Craft Terminal (MIB back–up)

• (7) NE configuration data restore from Equipment Craft Terminal (MIB restore, if necessary)

The first–time installation can be distinguished in two main procedures:

– SWP installation in PC environmentthat includes tasks (1) and (2) mentioned above.The relevant operating instructions are given in chapter 3–1 on page 309

– SWP download toward NE, if necessarythat includes tasks (3) to (4) mentioned above.The relevant operating instructions are given in chapter 4–8 on page 485

– NE configuration data definition and equipment line–up and commissioningthat includes task (5) mentioned above.The relevant operating instructions are given in chapter 3–2 on page 329

At the end of the first–time installation, the CT and NE situation is the standard one:

1 ) Network Element already configured with the more recent SWP version and CraftTerminal already available.

A.B.c

ECT

A.B.c

NE

ECT release = NE release

ECT version = NE version

This is the typical situation of new installations: the Network Element SW configuration matchesthe available Craft Terminal SWP version, so that the NE can be logged–in and the Operatorcan carry out the required operations, without any incompatibility problems.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

62 / 592 3DB 16142 EAAA Ed.02


1–2.6.3 How to check ECT and NE versions

[1] How to check ECT versionThis check can be done with ECT not connected to any NE

(1)

(2)

(3)

(4) read version

Fig. 18. How to check ECT version

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

63 / 5923DB 16142 EAAA Ed.02


[2] How to check NE versionProceed as follows:

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

2 ) From the Menu Bar of the 9400AWY Main view that opens after NE Login (Fig. 87. on page181), perform SW Download ⇒ SW Status

version committed(active)

version stand–by(not active)

V02.01.01

V02.01.00

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.1)– that stand–by is the immediately previous SW version (e.g. V2.1.0)

Fig. 19. How to check NE SW version (example)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

64 / 592 3DB 16142 EAAA Ed.02


1–2.6.4 Common situations requiring ECT and/or NE upgrade

The following situations require CT and/or NE upgrading, in order to reach the standard situation definedin point 1 ) on page 61:

1 ) Both Network Element and Craft Terminal already configured with a SWP version olderthan that made available by the a new SWP version (SAME RELEASE)

A.B.c

ECT NE

=SWP

CD–ROMA.B.d

A.B.c running version < SWP version

running release = SWP release

This could be the typical situation of installations already running with A.B SWP package(e.g.2.1.0), in the case a newer version of the same A.B SWP package has to be installed(e.g.2.1.1).

In this case, you must upgrade both ECT and NE as described in Chapter 4–9 on page 495.After that, the situation is equal to that of point 1 ) on page 61.

2 ) Network Element already configured with the more recent SWP version, but the CraftTerminal is not available or has a version older with respect to that of the NetworkElement(s).

A.B.c

ECT

A.B.d

NE

ECT release = NE release

ECT version < NE version

In this case, carry out SWP installation in Craft Terminal environment as explained in Chapter3–1 on page 309. After that, the situation is equal to that of point 1 ) on page 61.

1–2.6.5 Flash Card related special procedures

Taking into account the information contained in the Flash Card (see para.1–2.5 on page 56 forexplanations, if necessary), you could need to:

3 ) for system upgrade purposes, replace the flash card currently in use with a different typeFlash CardIn this case, please refer to para.4–7.3 on page 479.

4 ) for corrective maintenance purposes, replace the faulty flash card currently in use with aspare Flash CardIn this case, please refer to Chapter 4–6 Spare Flash Card management and replacementprocedures on page 465

1–2.6.6 Craft Terminal related special procedures

If you need to:

5 ) de–install Alcatel–Lucent SW from the PC used as Craft terminal, refer to chapter 4–10 onpage 497.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

65 / 5923DB 16142 EAAA Ed.02


1–2.6.7 NE configuration data change and save

It must be emphasized that , every time you change the equipment configuration data (see para.1–2.5 onpage 56), you must always save the relevant data:

a ) data present in Flash Card’s MIB bank [see point b ) on page 57]Data present in Flash Card’s MIB bank can be saved in a MIB back–up file as described in Chapter2–14 on page 301.The same chapter explains how to recover MIB data from the MIB back–up file.The procedures in this handbook make often reference to the MIB data restore from the MIB back–upfile. WARNING: read carefully para.1–2.6.9 below.If you change the equipment configuration data without carrying out the MIB back–up save, in caseof troubles you will have to create again the NE configuration data by means of a lot of individual ECTcommands, wasting time and with high probability of errors.

b ) data that are not saved in the MIB back–up file [see point c ) on page 57]

Only NE network routing data are not saved in the MIB back–up file.Nevertheless, it is possible to create, save and recover configuration files having the “.qcml”extension (for details refer to para.3–2.3.6 on page 341). Such a file contains (besides other data)the NE network routing data. WARNING: read carefully para.1–2.6.9 below.

Procedure for “.qcml” file back–up:

1 ) launch the TCO Suite Set–Up Tool , as described in para.3–2.3.9 on page 3452 ) in the screen of Fig. 244. on page 346 , click on button Get configuration from NE3 ) the window in Fig. 245. on page 347 will appear. This window is the first step of the Quick

Configuration Procedure (interactive)4 ) clicking repeatedly on Next buttons (without any other actions), reach Step L on page 368 and

click on Save As button: configuration data are saved in a “configuration_name.qcml” file(provide a mnemonic name)

1–2.6.8 NE data save after commissioning completion

For the NE, create a folder containing the following files:– the MIB back–up file [point a ) above]– the “.qcml” configuration file [point b ) above]– the TRS & SAT MSWord file. This can be used, in the future, to compare system performance to that

verified at the commissioning phase.Maintain this folder updated whenever you make changes on the NE.

1–2.6.9 NE data compatibility between SWP 2.1.x versions

[1] MIB back–up fileA MIB back–up file created while system was running with any SWP version < 2.1.1 can be reusedon a system running with the SWP version 2.1.1.A MIB back–up file created while system is running with the SWP version 2.1.1 cannot be reusedon a system running with any SWP version < 2.1.1.

[2] “.qcml” configuration fileA “.qcml” configuration file created while system was running with any SWP version < 2.1.1 can bereused on a system running with the SWP version 2.1.1.A “.qcml” configuration file created while system is running with the SWP version 2.1.1 cannot bereused on a system running with any SWP version < 2.1.1.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

66 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

67 / 5923DB 16142 EAAA Ed.02


1–3 IDU PROVISIONING AND DESCRIPTION

This chapter gives detailed operative information regarding the IDU shelf’s units available with theequipment version this handbook issue is relevant to, for provisioning, installation, commissioning andmaintenance purposes. Information given is relevant to assembly/subassembly and front panel drawings,as well as the usage description of the access points (connectors, visual indicators, buttons). This chapteris organized as follows:

– Provisioning of IDU shelves on page 68

– Labels affixed on the IDU on page 69

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

– Description of IDU Extension unit on page 77• IDU Extension Unit LEDs summary on page 78

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

– Description of Services Protection box on page 84• Alarms Housekeeping (pin–out and description) on page 85• NMS V.11 – Audio 1 (pin–out and description) on page 88• NMS G.703 – Audio 2 (pin–out and description) on page 89• User service channels (pin–out and description) on page 90

– Provisioning and identification of Flash Cards & Software Labels on page 93

– Provisioning and description of equipment accessories on page 96

Note for all provisioning tables:

– the Logistical Item corresponds to the Logistical Item code you can read on the IDU’s label (seeFig. 20. on page 69 )

– please refer to the Installation Handbook for the provisioning of cables and other items that dependon the installation choices.

Cautions to avoid equipment damage

Carefully observe statements specified in para.1–1.6 on page 36

N.B. For detailed operative information regarding the:

– description of equipment interconnections, please refer to para.3–2.2 on page 331

– equipment installation, please refer to the Installation Handbook

– equipment commissioning, please refer to Chapter 3–2 on page 329

– equipment maintenance, please refer to section 4 – MAINTENANCE on page 407.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

68 / 592 3DB 16142 EAAA Ed.02


1–3.1 Provisioning of IDU shelves

Tab. 6. IDU shelf provisioning for “1+0” and “1+1” configurations

CONFIGURATION

Logistical Item &16E1 32E1

Logistical Item &Description

16E116E1 +

AUDIO &USC

16E1 +4 ETH

16E1+4 ETH +AUDIO &

USC

32E132E1 +

AUDIO &USC

ETSI IDU MAIN UNITS(48/60V POWER SUPPLY)For “1+0” and “1+1” configurations

3DB16040ABXX1 0 IDU 16E1 48/60V PSU

X

3DB16058ABXX1 0 IDU 16E1 48/60V PSU AUDIO USC

X

3DB16160AAXX1 0 IDU 16E1 ENH DATA 48/60V PSU

X

3DB16162AAXX1 0 IDU 16E1 ENH DATA 48/60V PSU AUDIOUSC

X

3DB16041ABXX1 0 IDU 32E1 48/60V PSU

X

3DB16059ABXX1 0 IDU 32E1 48/60V PSU AUDIO USC

X

ETSI IDU EXTENSION UNITS(48/60V POWER SUPPLY)Only for “1+1” configurations

3DB16044ABXXEXT IDU 16E1 48/60V PSU

X X X X

3DB16045ABXXEXT IDU 32E1 48/60V PSU

X X

PROTECTION BOXESOnly for “1+1” configurations

3DB16102AAXXE1 Protection (SCSI 68 / D–sub 37)

X X X X X X

3DB16103AAXXServices Protection (D–sub44 / D–sub15)

X X X

Equipment interconnection diagrams(page) ⇒ 332 333 334 335 336 337

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

69 / 5923DB 16142 EAAA Ed.02


1–3.2 Labels affixed on the IDU

This label is affixed on the back side of:

– the IDU MAIN unit [position (C) in Fig. 21. on page 70 ]

– the IDU EXTENSION unit [position (C) in Fig. 23. on page 77 ]

A

B

C

this label is just an example

SYMBOL OR WRITING MEANING

9400AWY Equipment Acronym & Alcatel or Alcatel–Lucent Logo

CE European Community logo

12345 (example) Notified body

! Not harmonized frequency logo

2002/96/EC WEEE (Waste Electrical and ElectronicEquipment) Logo (see para.1–5.10.3 on page 137)

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)SERIAL N CW052402141 (example)

Factory serial number

C Factory serial number bar code 128

24 V ± 20%, 2.2 A max (example) Power Supply Version 24 V

48–60 V ± 20%, 1.1–0.7 A (example) Power Supply Version 48/60 V

24–60 V ± 20%, 2.2–0.7 A (example) Power Supply Version Full Range

Feeding to Continuous Current

Fig. 20. Label affixed on the IDU

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

70 / 592 3DB 16142 EAAA Ed.02


1–3.3 Description of IDU Main unit

1 2 A

9 1110

3 4

12 1413

5 6 7 8

15 16

17 C

18

B

Fig. 21. IDU Main Unit front and rear views

Tab. 7. IDU Main Unit: external interfaces list

Ref.Fig. 21.

Connector or item detail Interface / Explanation Details

Basic Interfaces (without optional plugs–in)

(1) SubD 3 Male Station Battery inputpara.1–3.3.2on page 74

(2)ON/OFF switch: general

power supply switch(IDU Main + its ODU)

I ⇒ ONO ⇒ OFF

(3)RJ45

OS (or ECT) 10/100BaseTpara.1–3.3.4on page 75

(4) Debug RJ45 For

Factory use only

(8) N 50 ohm Female For IDU–ODU cable (N.B.2)

(9)

Acknowledgement: Alarmattending pushbutton; this

pushbutton turns OFF LEDsMAJ/MIN and turns ON

yellow LED ATTD

para.4–5.6.2on page 434

(10)Equipment Controller

Reset pushbutton

possible use insidecorrective

maintenance

(11)Lamp Test pushbutton: it

allows to HW test the LEDsof the unit


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

71 / 5923DB 16142 EAAA Ed.02


Ref.Fig. 21.

DetailsInterface / ExplanationConnector or item detail

(12) SubD 9RS232 connector for NE–CT

serial cablepara.1–3.3.3on page 75

(13) SCSI 68 pin Female 1–16E1 – 64 wires (N.B.1)

(14) SCSI 100 pin Femaleconnector for 100 pin SCSIflat cable (used only in 1+1

configurations)

interconnection withExtension Unit,no pin usage by

Customer

(15) SubD 44 Femaleconnector for Alarms –Housekeeping – NMS

(N.B.1)

(16) – 9 LEDspara.1–3.3.1on page 73

(17) + (18)+ (A)

Flash Cardpara.1–3.7on page 93

(B) label Data Matrix codification for factory use

(C) label unit identificationFig. 20.

on page 69

Optional Interfaces (with optional plugs–in)

Connectors according to the equipped plug–in (if any) (N.B.3) :

(5)

4 x RJ45 Ethernet user data,when

Enhanced Ethernet plug–inis equipped


SCSI 68 pin Female17–32 E1 – 64 wires,

when the 17–32 E1 plug–inis equipped

(N.B.1)

Connectors present only when the Audio + User Service Channel plug–in isequipped (N.B.3) :

(6) + (7)SubD 44 Female

Audio1/2 + G703_V11 UserService Channel

(N.B.1)(6) + (7)

RJ11 Female forEOW telephone

chapter 4–2on page 413

Notes on next page

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

72 / 592 3DB 16142 EAAA Ed.02


Notes to Tab. 7.

(N.B.1) For connector pinout, refer to the Installation Handbook

(N.B.2)

ATTENTION(caution to avoid equipment damage)The N–type connector carries +48 DC voltage for ODU power supply.Do not connect measuring instruments directly.

(N.B.3)

When no plug–in equipped, the slot is closed by a metal plate (inside the panel rearside).

ÁÁÁ ÁÁÁÁMetal plate is mandatory to ensure EMI–EMC performance

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

73 / 5923DB 16142 EAAA Ed.02


1–3.3.1 IDU Main Unit LEDs summary

Nine LEDs are present on the front panel of the IDU Main Unit [position (16) in Fig. 21. on page 70 ]:

GREEN

GREEN YELLOW

RED

RED

RED

RED

YELLOWGREEN

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. 22. LEDs on the IDU Main Unit front panel

[1] ON – This green LED is ON when the Station Battery is connected, the ON/OFF switch is ON, andthe internal DC/DC is working properly.

[2] RDI – The Remote Defect Indication is a local indication of the Remote Equipment Failure alarmsrequiring consequent operator intervention. It is transmitted from the remote station to the local viathe aggregate radio frame. RDI is formed in the remote station by the following roots:

• Main Unit failure (Card Fail)• Extension Unit failure (Card Fail and Card Missing, only in 1+1 configurations)• Data plug–in failure (Card Fail and Card Missing)• 17–32xE1 plug–in failure (Card Fail and Card Missing)• Loss of Signal from Tributaries• Loss of cable from ODU (IDU–ODU cable loss)• ODU transmitted/received power alarm (TX Fail/RX Fail)• ODU incompatible TX power alarm• ODU incompatible TX frequency alarm (only in 1+1 configurations)• ODU incompatible shifter• ODU failure (Card Fail)

[3] MIN – Minor Alarm is the sum of the alarms to which the customer associates, via ECT/NMS, aMINOR severity.

[4] EOW – This LED refers to the use of the EOW. Refer to chapter 4–2 on page 413 for details.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

74 / 592 3DB 16142 EAAA Ed.02


[5] ODUW – The ODUW led ON identifies the TX activity of the ODU connected to the MAIN unit.It is OFF in case of:• IDU–ODU Cable Loss alarm• Mute function activated• ODU switching–off command activated in 1+1 HSB configuration

[6] ATTD – The attended LED is ON when the acknowledgement button [position (9) in Fig. 21. on page70 ] has been pushed

[7] MAJ – Major Alarm is the sum of the alarms to which the customer associates, via ECT/NMS, a highseverity (MAJOR or CRITICAL).

[8] LDI – The Local Defect Indication (LDI) has the purpose to show Local Equipment Failure requiringconsequent actions by operators. The LDI roots are:

• Main Unit failure (Card Fail)• Extension Unit failure (Card Fail and Card Missing, only in 1+1 configurations)• Data plug–in failure (Card Fail and Card Missing)• 17–32xE1 plug–in failure (Card Fail and Card Missing)• Loss of Signal from Tributaries• Loss of cable from ODU (IDU–ODU cable loss)• ODU transmitted/received power alarm (TX Fail/RX Fail)• ODU incompatible TX power alarm• ODU incompatible TX frequency alarm• ODU incompatible shifter• ODU failure (Card Fail)

The lamp test pushbutton [position (11) in Fig. 21. on page 70 ] allows the HW test of all LEDs.

1–3.3.2 Power Supply connector pin–out (MAIN and EXTENSION units)

Tab. 8. Power supply connections

Pin Function

A1 + BATTERY

A2 GROUND

A3 – BATTERY

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

75 / 5923DB 16142 EAAA Ed.02


1–3.3.3 ECT RS232 connector pin–out

Tab. 9. ECT connections

pin 1

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

1–3.3.4 OS (or ECT) 10/100BaseT connector pin–out

Tab. 10. OS (or ECT) connections

N.B. Leds are not operative

RJ45

(IDU MAIN side)Signal Color used

RJ45

(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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

76 / 592 3DB 16142 EAAA Ed.02


1–3.3.5 Ethernet tributaries

Present on the front panel of the IDU Main Unit [position (5) in Fig. 21. on page 70 ] when the EnhancedEthernet plug–in is equipped.

For the Ethernet user data interfaces the following table summarizes the meaning of the LEDs integratedin the RJ45 connectors:

Tab. 11. RJ45 connectors leds for Ethernet user data interfaces

ColorDisplay

FunctionLed–off Led–on Led blinking

LEFT LED GreenLink and

activity statusLink down Link up –

RIGHT LED Yellow activityNo TX/RX

activitydetected

–TX/RX activity

detected

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

77 / 5923DB 16142 EAAA Ed.02


1–3.4 Description of IDU Extension unit

1 2 3 4 5 6 7

89

B C

Fig. 23. IDU Extension Unit front and rear views

Tab. 12. IDU Extension Unit: external interfaces list

Ref.Fig. 23.

Connector or item detail Interface / Explanation Details

Basic Interfaces (without optional plugs–in)

(1) SubD 3 Male Station Battery inputpara.1–3.3.2on page 74

(2)ON/OFF switch: general

power supply switch(IDU Extension + its ODU)

I ⇒ ONO ⇒ OFF

(3)Lamp Test pushbutton: it

allows to HW test the LEDsof the unit


(4) SCSI 68 pin Female 1–16E1 – 64 wires (N.B.1)

(5) SCSI 100 pin Femaleconnector for 100 pin SCSI

flat cable

interconnection withMain Unit,

no pin usage byCustomer

(6) SubD 44 FemaleAudio1/2 + G703_V11 User

Service Channel(N.B.1)

(7) – 3 LEDspara.1–3.4.1on page 78

(8) N 50 ohm Female For IDU–ODU cable (N.B.2)

(B) label Data Matrix codification for factory use

(C) label unit identificationFig. 20.

on page 69

Optional Interfaces (with optional plug–in)

(9)Connector present only when the 17–32 E1 plug–in is equipped (N.B.3) :

(9)SCSI 68 pin Female 17–32 E1 – 64 wires (N.B.1)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

78 / 592 3DB 16142 EAAA Ed.02


Ref.Fig. 23.

DetailsInterface / ExplanationConnector or item detail

Notes

(N.B.1) For connector pinout, refer to the Installation Handbook

(N.B.2)

ATTENTION(caution to avoid equipment damage)The N–type connector carries +48 DC voltage for ODU power supply.Do not connect measuring instruments directly.

(N.B.3)

When no plug–in equipped, the slot is closed by a metal plate (inside the panel rearside).

ÁÁÁ ÁÁÁÁMetal plate is mandatory to ensure EMI–EMC performance

1–3.4.1 IDU Extension Unit LEDs summary

Three LEDs are present on the front panel of the IDU Extension Unit [position (7) in Fig. 23. on page 77 ]:

GREEN GREEN

1) ON = Power ON (green)This green LED is ON when the Station Battery is connected, the ON/OFF switch isON, 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 theEXTENSION unit.It is OFF in case of:– IDU–ODU Cable Loss alarm– Mute function activated– ODU switching–off command activated in 1+1 HSB configuration

3) ANT = Not operative in current SWP version

Fig. 24. LEDs on the IDU Extension Unit front panel

The lamp test pushbutton [position (3) in Fig. 23. on page 77 ] allows the HW test of all LEDs.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

79 / 5923DB 16142 EAAA Ed.02


1–3.5 Description of E1 Protection box

1

2

3

4

5

6

Line Side

7

8

Equipment Side

Fig. 25. E1 Protection box: views of Equipment Side and Line Side connectors

Tab. 13. Equipment Side and Line Side connectors of E1 Protection box

Ref.Fig. 25.

Connector Interface To be connected to

Line side

(1) 1–8 E1

(2)SubD 37 Female

9–16 E1see para.1–3.5.1 on page 80

(3)SubD 37 Female

17–24 E1see para.1–3.5.1 on page 80

(4) 25–32 E1

Equipment side

(5) 1–16 E1same–name connector of IDU Main unit

[ (13) in Fig. 21. on page 70 ]

(6)SCSI 68 pin Female

N.B.

1–16 E1same–name connector of IDU Extension unit

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

(7)

SCSI 68 pin FemaleN.B.

17–32 E1same–name connector of IDU Main unit

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

(8) 17–32 E1same–name connector of IDU Extension unit

[ (9) in Fig. 23. on page 77 ]

N.B. For connector pinout, refer to the Installation Handbook

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

80 / 592 3DB 16142 EAAA Ed.02


1–3.5.1 E1 Protection box: connector pin–out

Notes for all tables:

– for E1 tributaries the same input and output wires are used for 120 ohm (balanced) and 75 ohm(unbalanced); the selection between the two options is possible with CT/OS

– in 75 ohm unbalanced configuration ”Out– Trib.n” is the ground of ”Trib.n”

– pins must be connected to the station DDF, directly or through distribution shelves (see Fig. 3. onpage 40 )

Tab. 14. E1 tributaries (1 to 8) connector pin–out

pin 1

Description Pin # Pin # Description

Not Used 1 20 Not Used

IN+ Trib. 1 2 21 IN– Trib. 1








GND 1029 Not Used

Not Used 1129 Not Used

Out+ Trib. 1 12 30 Out– Trib. 1








All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

81 / 5923DB 16142 EAAA Ed.02



pin 1











GND 1029 Not Used










All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

82 / 592 3DB 16142 EAAA Ed.02



pin 1











GND 1029 Not Used










All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

83 / 5923DB 16142 EAAA Ed.02



pin 1











GND 1029 Not Used










All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

84 / 592 3DB 16142 EAAA Ed.02


1–3.6 Description of Services Protection box

Line Side

Equipment Side

1 2 3 4

5 6 7

Fig. 26. Services Protection box: views of Equipment Side and Line Side connectors

Tab. 18. Equipment Side and Line Side connectors of Services Protection box

Ref.Fig. 25.

Connector Interface To be connected to

Line side

(1)Alarms +

Housekeepingstation DDF for Alarms + Housekeeping;

see para.1–3.6.1 on page 85

(2)

SubD 15 Female

NMS V.11 +Audio 1

station DDF for NMS V.11 + Audio 1;see para.1–3.6.2 on page 88

(3)

SubD 15 FemaleNMS G.703 +

Audio 2station DDF for NMS G.703 + Audio 2;


(3)User Service

Channelsstation DDF for User Service Channels;


Equipment side

(5)Audio1/2 +

G703_V11 UserService Channel

same–name connector of IDU Extension unit[ (6) in Fig. 23. on page 77 ]

(6)SubD 44 Female

N.B.

Audio1/2 +G703_V11 UserService Channel

same–name connector of IDU Main unit[ (6) in Fig. 21. on page 70 ]

(7)Alarms –

Housekeeping –NMS

same–name connector of IDU Main unit[ (15) in Fig. 21. on page 70 ]

N.B. For connector pinout, refer to the Installation Handbook

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

85 / 5923DB 16142 EAAA Ed.02


1–3.6.1 Alarms Housekeeping (pin–out and description)

The “Alarms–Housekeeping” SubD15 connector (pinout in following Tab. 19. ) is divided in:– 3 summarizing discrete alarms – equipment outputs (A_1 to A_3); see point [1] below– 4 housekeeping controls – equipment outputs (HK_O1 to HK_O4); see point [2] on page 86– 6 housekeeping alarms – equipment inputs (HK_I1 to HK_I6; see point [4] on page 87– 1 common wire (COM)– 1 ground (GND).

N.B. the SW User Label depicted in Tab. 19. below represents the name by which each signal isidentified by the External Points Management (see chapter 2–7 on page 247), and QuickConfiguration Procedure External Input and Output Points configuration on page 367.

Tab. 19. Alarms Housekeeping connector pin–out

pin 1

Pin Signal Direction SW User Label

6 HK_I1 INPUT CPI1

13 HK_I2 INPUT CPI2

7 HK_I3 INPUT CPI3

14 HK_I4 INPUT CPI4

8 HK_I5 INPUT CPI5

15 HK_I6 INPUT CPI6

4 HK_O1 OUTPUT CPO1

11 HK_O2 OUTPUT CPO2

5 HK_O3 OUTPUT CPO3

12 HK_O4 OUTPUT CPO4

9 COM

1 A_1 OUTPUT FAIL IDU

2 A_2 OUTPUT FAIL ODU CH#1

3 A_3 OUTPUT FAIL ODU CH#0

10 GND /

[1] SUMMARIZING DISCRETE ALARMS

The 3 summarizing discrete alarms (equipment outputs) are defined as follows:

A_1 IDU HW Failure alarm ( = IDU Main (or Extension unit) Card fail/missing + Loss ofIDU–ODU cable + Loss of Tributaries)

A_2 ODU Main Failure alarm ( = ODU Tx Failure + ODU Rx Failure)

A_3 ODU Spare Failure alarm

For electrical characteristics refer to point [3] on page 86.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

86 / 592 3DB 16142 EAAA Ed.02


[2] HOUSEKEEPING CONTROLS

For the 4 housekeeping controls (equipment outputs), it is possible to choose through CT not onlythe manual setting of each one of them, but also the association to one of the system alarms availablein the CT menu lists (including: Major Alarm, Minor Alarm, Loss of Tributaries, Loss of IDU–ODUcable, 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 ELECTRICALCHARACTERISTICS

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 definesthe 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 largeV2.

IDU

OUT1

OUT2

OUTn

o o oo o o

OUTCommonV1

I1

Fig. 27. Equipment outputs (summarizing and housekeeping)

Note 1: logic can be independently changed for each input and output (the relay is ”closed” whenthe alarm is not present and is ”opened” when the alarm is present) through CT configuration whilefor Summarizing outputs the default configuration is the only possibility.

Note 2: when the power supply is down (and also when the power supply is on, but the SW hasn’tyet initialized the HW), all the relays of the outputs of the alarms/housekeeping are in the ”open” state(HW default condition).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

87 / 5923DB 16142 EAAA Ed.02


[4] EQUIPMENT INPUTS

The IDU is able to detect the status of ”commands” coming from customer’s circuits.A common (in) signal is supplied by the customer’s circuit, and this signal is different from the onedefined 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

o o o

in 1

in n

o o o

common (in)

customerground

V3

I3

customer

V4

out

Fig. 28. Equipment inputs – relay scheme

• alarm present ⇒ the customer relay is ”closed”: –2V ≤ V3 ≤ 0V, |I3| ≤ 10mA This means that the customer’s circuit guarantees that |V3| ≤ 2V and is allowed to drain fromthe IDU a 10mA max current;

• alarm not present ⇒ the customer relay is ”open”: |I3| ≤ 0.2mA. This means that the maximumcurrent drained by the customer’s circuit is 0.2mA.

Case 2 (open collector)

IDU

o o o

in 1

in n

o o o

common (in)

customerground

V3

I3

customer

V4

Fig. 29. Equipment inputs – open collector scheme

The IDU supplies a suitable negative voltage to the customer’s circuit:• alarm present ⇒ the customer transistor conduces (= ”closed”): –2V ≤ V4 ≤ 0V, |I3| ≤ 10mA.• alarm not present ⇒ the customer transistor doesn’t conduce (=”open”): |I3| ≤ 0.2mA.

This limits the max current that the customer’s circuit can drain.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

88 / 592 3DB 16142 EAAA Ed.02


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

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

The NMS_V11 channel is a 64Kb/s; its working mode can be selected between:

– DTE: the data in and data out have to be synchronous, data out being the slave,

– CODIR (asynchronous): TX and RX are totally asynchronous.

Expected/transmitted Clock falling edge is in the middle of the data.

Audio1 outputs can be squelched by CT/OS selection.

Tab. 20. NMS–V.11 + Audio 1 connector pin–out

pin 1


RS422 data in (+) 1 9 RS422 data in (–)

RS422 clock in (+) 2 10 RS422 clock in (–)

RS422 data out (+) 3 11 RS422 data out (–)

RS422 clock out (+) 4 12 RS422 clock out (–)

GND NMS 5 13 Audio1 signal from user (–)

Audio1 signal from user (+) 6 14 Audio1 signal to user (–)

Audio1 signal to user (+) 7 15 Not used

GND Audio 8

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

89 / 5923DB 16142 EAAA Ed.02


1–3.6.3 NMS G.703 – Audio 2 (pin–out and description)

The “(NMS_G703+Audio2)” interface has 5 pins dedicated to NMS and 6 pins dedicated to EOW analogparty line.

The NMS_G703 channel is a 64Kb/s; its working mode can be selected between:

– DTE: G703 data in and G703 data out have to be synchronous, G703 data out being the slave,

– CODIR (asynchronous): G703 data in and G703 data out are totally asynchronous (this modeincludes DCE behavior),

– “In–frame”: this configuration both disables the NMS_G703 interface and enables theinsertion/extraction into/from the first E1 of the 64Kbit/s channel coming–from/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 far–end E1 is enabled and successfully provisioned.

Audio2 outputs can be squelched by CT/OS selection.

Tab. 21. NMS–G.703 + Audio 2 connector pin–out

pin 1


G703 data in (+) 1 9 G703 data in (–)

Not used 2 10 Not used

G703 data out (+) 3 11 G703 data out (–)

Not used 4 12 Not used

GND NMS 5 13 Audio2 signal from user (–)

Audio2 signal from user (+) 6 14 Audio2 signal to user (–)

Audio2 signal to user (+) 7 15 Not used

GND Audio 8

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

90 / 592 3DB 16142 EAAA Ed.02


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

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

– 64Kb/s V11 co–directional – (data+clock);– 64Kb/s co–directional – G.703 asynchronous (i.e. TX and RX data are not necessarily synchronous.

This mode includes DCE behavior);– 64Kb/s V11 contra–directional (data+clock);– 9.6Kb/s asynchronous V24/V28;– 4.8Kb/s asynchronous V24/V28;– 9.6Kb/s V11;– 4.8Kb/s V11.

The pin function is shown in the table below.

Tab. 22. User service channel connector pin–out

pin 1

Pin # Signal Direction

2 COD_RX + INPUT

9 COD_RX – INPUT

3 COD_TX + OUTPUT

10 COD_TX – OUTPUT

4 RX_ASY INPUT

11 TX_ASY OUTPUT

5 CC_RX + INPUT

12 CC_RX – INPUT

6 RX_CK + BID

13 RX_CK – BID

7 CC_TX + OUTPUT

14 CC_TX – OUTPUT

8 CC_TCK + OUTPUT

15 CC_TCK – OUTPUT

1 GND /

N.B. The use of signals is depicted in following figures Fig. 30. to Fig. 33.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

91 / 5923DB 16142 EAAA Ed.02


For V11 co–directional mode, refer to Fig. 30. for the interface description vs pin–out.

IDU AWYUSER EQUIPMENT

CC_RX +CC_RX –

RX_CK +RX_CK –

CC_TX +CC_TX –

CC_TCK +CC_TCK –

DATA

CLOCK

CLOCK

DATA

< USER RADIO >

USER SERVICE CHANNEL V11 CO–DIR

Fig. 30. User service channel: V11 co–directional interface

For V11 contra–directional DCE mode, refer to Fig. 31. for the interface description vs pin–out. Note thatV11 contra–directional DTE mode (as the user–equipment interface) is not supported.

IDU AWY

DCE

USER SUBORDINATEEQUIPMENT (DTE)

DATA

CLOCK

CLOCK

DATA

< USER RADIO >

USER SERVICE CHANNEL V11 CONTRA–DIR – DCE

CC_RX +CC_RX–

RX_CK +RX_CK–

CC_TX +CC_TX–

CC_TCK +CC_TCK–

Fig. 31. User service channel: V11 contra–directional interface

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

92 / 592 3DB 16142 EAAA Ed.02


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


COD_RX+

DATA&CLOCK

< USER RADIO >

USER SERVICE CHANNEL G.703

DATA&CLOCK

COD_RX–

COD_TX+

COD_TX–

Fig. 32. User service channel: G.703 interface

For V24/V28 mode, refer to Fig. 33. for the interface description vs pin–out.


RX_ASY

TX_ASY

DATA&CLOCK

< USER RADIO >

USER SERVICE CHANNEL V28

DATA&CLOCK

Fig. 33. User service channel: V24/V28 interface

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

93 / 5923DB 16142 EAAA Ed.02


1–3.7 Provisioning and identification of Flash Cards & Software Labels

1–3.7.1 Provisioning of Flash Cards & Software Labels

A Software Label (stored on the Flash Card plugged in the IDU Main board) allows flexibility in choosinguser interfaces and modulation as in the following Tab. 23. :

Tab. 23. Flash Cards provisioning and associated & Software Labels

Logistical Item, Description & Software LabelSupported configuration

Logistical Item, Description & Software LabelInt.N# & type Modulation

3DB16079ABXX : 8Mb 4 QAM FLASH CARD 2E1, 4E1 4QAM

Software Label: 8Mb 4 QAM

3DB16080ABXX : 8Mb 4/16 QAM FLASH CARD2E1 4QAM

3DB16080ABXX : 8Mb 4/16 QAM FLASH CARD4E1 4QAM or 16QAM

Software Label: 8Mb 4/16 QAM

3DB16081ABXX : 16Mb 4 QAM FLASH CARD 2E1, 4E1, 8E1 4QAM



3DB16082ABXX : 16Mb 4/16 QAM FLASH CARD4E1, 8E1 4QAM or 16QAM


3DB16083ABXX : 32Mb 4 QAM FLASH CARD2E1, 4E1, 8E1,

16E14QAM



3DB16084ABXX : 32Mb 4/16 QAM FLASH CARD4E1, 8E1, 16E1 4QAM or 16QAM


2E1 4QAM2E1 4QAM

3DB16085ABXX : 64Mb 16 QAM FLASH CARD 4E1, 8E1, 16E1 4QAM or 16QAM

32E1 16QAM


The limitations introduced by the Software Label are related only to frame structure and modulationconfiguration.

There are no limits related to the NE Configuration type (1+0 or 1+1) . Software Label value and NEConfiguration type are independent.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

94 / 592 3DB 16142 EAAA Ed.02


1–3.7.2 Description of Flash Cards & Software Labels

1–3.7.2.1 General

The Flash Card is housed inside the IDU Main Unit shelf [see position (17) in Fig. 21. on page 70 ].

Fig. 34. herebelow shows the FLASH CARD profile and insertion direction

BOTTOM SIDE

CONNECTOR SIDE

INSERTION

Fig. 34. FLASH CARD profile and insertion direction

ATTENTION

(caution to avoid equipment damage)Whenever you have to handle flash card(s), wear always the Antistatic protection device kit (seeFig. 1. on page 36) and connect its termination to a grounded structure, to avoid the possible damageof the flash card contents for electrostatic discharges.

As shown in position (18) in Fig. 21. on page 70, a suitable metal cover, fixed to the IDU Main Unit shelfby three screws, is envisaged to ensure equipment EMI–EMC performance and to avoid item detachment:

1–3.7.2.2 Flash Card identification

The Logistical Items for the possible Flash Card types are specified in Tab. 23. on page 93 , whichindicates, for each P/N, also its Software Label . Flash Card labelling is described in Fig. 35. on page95:

a ) the Flash Card Logistical Item and Software Label are reported on the label affixed on it;

b ) moreover, the Software Label is affixed on the label present on the front panel of the IDU Main Unit(position (A) in Fig. 21. on page 70):

flash card Software Label

For this purpose, the Flash Card plastic bag contains another self–adhesive label, equal to thataffixed on the Flash Card itself, that can be cut as shown below, to obtain the label to be affixed onthe front panel of the IDU Main Unit

flash card Software Label

c ) moreover, the Software Label can be verified by Operator’s Commands: see Fig. 159. on page 256and Fig. 72. on page 166

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

95 / 5923DB 16142 EAAA Ed.02


LABEL AFFIXED ON THE PLASTIC BAGFOR FLASH CARD SHIPMENT

LABEL AFFIXED ONTHE FLASH CARD

AB

CD

A

E

F

G

H

H

C

FIELD WRITING (EXAMPLES) MEANING N.B.

A 3DB16084ABXX Logistical item for Customer n.b.1

B Logistical item for Customer, bar code 39

C BS0731UW055 Factory serial number

D Factory serial number, bar code 39

E 32Mb 4/16 QAM Software Label n.b.1

F 3DB16084ABAA 01 Factory Technical Code + ICS

G V2.1.0/V2.1.1Software versions loaded in the FlashCard banks by Alcatel–Lucent factory

n.b.2

HData matrix (for Alcatel–Lucent internalpurpose)

n.b.1 according to Tab. 23. on page 93

n.b.2 see point [2] on page 56 , and point [2] on page 63

Fig. 35. Flash Card identification labels

1–3.7.2.3 Flash Card upgrade

To replace a Flash Card with a different type, for system upgrade purpose, please refer to para.4–7.3Flash Card upgrade on page 479.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

96 / 592 3DB 16142 EAAA Ed.02


1–3.8 Provisioning and description of equipment accessories

Tab. 24. Equipment accessories

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

Ref. Logistical Item Technical Description N.B.

[1] 3CC07946AAXX Telephone Handset a

[2] 3DB01398AAXX Maintenance Tool Kit

[3] 3DB01397AAXX Installation Kit Tool b[4] 3DB01399AAXX Station Kit Tool

b

a See chapter 4–2 on page 413

b See para.4–3.2.2 on page 416

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

97 / 5923DB 16142 EAAA Ed.02


1–4 ODU PROVISIONING, CHARACTERISTICS AND DESCRIPTION

This chapter describes the ODU configurations, relevant provisioning and operative information forinstallation, commissioning and maintenance purposes:

– ODU general description: refer to point c ) on page 46

– ODU mechanical design and identification on page 98

– Labels affixed on the ODU on page 99

– ODU configurations on page 100

– ODU provisioning and layouts on page 101

– ODU part lists and characteristics on page 104

• Part lists of ODUs with external diplexer on page 105

• Part lists of ODUs with embedded diplexer on page 108

– Antenna configurations on page 113

– ODU operative information on page 119

For the Light service kit cable, please refer to para.3–2.10 on page 405.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

98 / 592 3DB 16142 EAAA Ed.02


1–4.1 ODU mechanical design and identification

The ODU consists of one or two cabinets including the modem + transceiver + branching of a channel.Two mechanical solutions are adopted:

– one with external diplexer, where the branching (diplexer) is internal to the ODU cabinet; each of thistype of ODU is identified by one Logistical Item only

– another with embedded diplexer, where ODU is composed by two independent units: theBRANCHING assembly (containing the diplexer) and the TRANSCEIVER assembly (containing theRF section); each of this type of ODU is identified by two Logistical Items, one for the BRANCHINGassembly and another for the TRANSCEIVER assembly. To read the BRANCHING assemblyidentification label it is necessary to separate the BRANCHING assembly from the TRANSCEIVERassembly.

Tab. 25. ODU dimensions and weights

embedded diplexer external diplexer

Type with .. TRANSCEIVER+ BRANCHING

TRANSCEIVER BRANCHINGTRANSCEIVER+ BRANCHING

Dimensions235 x 235 x 72 mm

(9.25 x 9.25 x 2.8in)248 x 257 x 93 mm

(9.76 x 10.1 x 3.7in)235 x 235 x 73.5 mm (9.25 x 9.25 x 2.9in)

248 x 257 x 156.5 mm (9.76 x 10.1 x 6.6in)

Weight 3.9 kg (8.58 lb) 4.2 kg (9.24 lb) 3.2 kg (7.04 lb) 7.4 kg (16.28 lb)

WITH EMBEDDED DIPLEXER

TRANSCEIVER+

BRANCHING

ODU IDENTIFICATION LABEL(see Fig. 37. on page 99)

TRANSCEIVER

BRANCHING

TRANSCEIVERIDENTIFICATION LABEL(see Fig. 37. on page 99)

BRANCHINGIDENTIFICATION LABEL

(INSIDE)(see Fig. 52. on page 126)

WITH EXTERNAL DIPLEXER

Fig. 36. ODU types, identification, dimensions and weights

The ODUs are delivered with the “nose” adapter in case of configurations with the separated antenna (fordetails, see para.1–4.6.4 on page 117)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

99 / 5923DB 16142 EAAA Ed.02


1–4.2 Labels affixed on the ODU

a ) the following label is affixed externally to all types of ODU and ODU’s TRANSCEIVER boxes (seeFig. 46. on page 120 and Fig. 47. on page 121):

A

B

C

this label is just an example


A9400 Equipment Acronym & Alcatel or Alcatel–Lucent 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 asexamples)

Working frequency range

Shifter MHz (shown numbers as examples) Shifter

TX Sub–band (shown numbers as examples) TX Sub–band

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. 37. Label affixed on the ODU and ODU’s TRANSCEIVER box

b ) only for ODUs with external diplexers, an additional label is placed on the branching assembly (fordetails refer to Fig. 50. and Fig. 52. on pages 124–126).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

100 / 592 3DB 16142 EAAA Ed.02


1–4.3 ODU configurations

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

Tab. 26. ODU configurations

Outdoorconfiguration

ODU ODU coupler ANTENNAAPPLICATIONS AND

ADVANTAGES

1+0 1 x ODU NO 1 x antenna single polar Non–protected

1+1 HSB2 x ODUs atsamefrequency

1/10 dBasymmetric

1 x antenna single polarProtection againstfailures

1+1 HSB SD2 x ODUs atsamefrequency

NO 2 x antennas single polar

Protection againstfailures.

1+1 FD AP2 x ODUs atdifferentfrequencies

NO 1 x antenna double polar

Protection againstfailures.Improvement ofperformancesversus multipath

1+1 FD DA2 x ODUs atdifferentfrequencies

NO2 x antennas single polarin AP configuration (sameor crossed polarization)

versus multipathpropagation

N.B. For explanatory diagrams, refer to para.1–2.3 on page 50 System configurations.

Legend:AP: Alternate PolarDA: Double AntennaFD: Frequency diversityHSB: Hot Stand BySD: Space Diversity

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

101 / 5923DB 16142 EAAA Ed.02


1–4.4 ODU provisioning and layouts

1–4.4.1 Provisioning of ODU (1+0)

a ) ODU transceiver: see para.1–4.5 on page 104

b ) Antenna: see paragraphs:

– 1–4.6.1 on page 114 (1+0 configuration with full integrated antenna)or

– 1–4.6.4 on page 117 (Configuration with separated antenna)

c ) Part list of full integrated antennas, ODU accessories and installation materials: refer toInstallation Handbook

1–4.4.2 Provisioning, layouts and connections of ODU (1+1)

1–4.4.2.1 ODU (1+1) HSB–SD or FD–DA AP with two antennas

Antenna (2)

ODU CH 0

Antenna (1)

ODU CH 1


N.B. Figure shows the solution with full integrated antennas; antennas can be also external (seepoint b ) herebelow)

Fig. 38. Station layout of ODU (1+1) HSB–SD or FD–DA AP with two antennas

– Equipment provisioning:

a ) ODU transceiver (x2): see para.1–4.5 on page 104

b ) Antenna (x2): see paragraphs:

– 1–4.6.1 on page 114 (1+0 configuration with full integrated antenna)or

– 1–4.6.4 on page 117 (Configuration with separated antenna)

c ) Part list of full integrated antennas, ODU accessories and installation materials (x2): refer toInstallation Handbook

– ODU Equipment block diagram: see:

• Fig. 11. on page 52 (1+1 HSB–SD)

• Fig. 13. on page 53 (1+1 FD–DA AP)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

102 / 592 3DB 16142 EAAA Ed.02


1–4.4.2.2 ODU (1+1) HSB or with one antenna

ANTENNA

ODU CH 0

ODU CH 1


COUPLER

N.B. this drawing is an example referred to the coupler used in 13–38 GHz configurations.Couplers used in 7–8 GHz configurations are shown in Fig. 44. on page 117.

Fig. 39. Station layout of ODU (1+1) HSB with one antenna


a ) ODU transceiver (x2): see para.1–4.5.2 on page 108

b ) Antenna and coupler: see paragraphs:

– 1–4.6.2 on page 116[1+1 HSB configuration with coupler and full integrated antenna (13–38 GHz)]

– 1–4.6.3 on page 117[1+1 HSB configuration with coupler and full integrated antenna (7–8 GHz)]

c ) Part list of full integrated antennas, ODU accessories and installation materials: refer toInstallation Handbook

– ODU Equipment block diagram: see:

• Fig. 12. on page 52 (1+1 HSB)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

103 / 5923DB 16142 EAAA Ed.02


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

Double Polar Antenna

ODU CH 0 ODU CH 1


Fig. 40. Station layout of ODU (1+1) FD–AP with one double polar external antenna


a ) ODU transceiver (x2): see para.1–4.5 on page 104

b ) Connection of Double Polar External Antenna: see para.1–4.6.4 on page 117 (Configurationwith separated antenna)

c ) Part list of ODU accessories and installation materials: refer to the Installation Handbook

– ODU Equipment block diagram: see Fig. 14. on page 53

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

104 / 592 3DB 16142 EAAA Ed.02


1–4.5 ODU part lists and characteristics

Notes for all tables:

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

Capacity can be:– 64Mb = 32E1 capacity ODU

Logistical Item Corresponds to the Logistical Item code you can read on the ODU’slabel (see Fig. 37. on page 99 )

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.1–4.5.1 on page 105

– ODUs with embedded diplexer, refer to para.1–4.5.2 on page 108

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

105 / 5923DB 16142 EAAA Ed.02


1–4.5.1 Part lists of ODUs with external diplexer

1–4.5.1.1 General

The diplexer included in the available BRANCHING assemblies refers to ITU–R F.385, 386 and RF specialCUSTOMERS channelling with Tx/Rx separation specified in following Tab. 28. and Tab. 30. Each diplexer is a three port passive device with two band–pass filters as described hereafter (physicalarrangement is shown in Fig. 50. on page 124):

Port A

Port B

Port C

Each BRANCHING assembly has two different variants by duplex spacing, depending on the RF_Txoutput 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:

70 dB

frequencies

attenuation

2.5 dB

fr SHIFTER

f1 f2 f3 f4foL foH

WARNING: f1, f2, f3 and f4 frequencies of the branching filters refer to the extreme channelfrequencies and not to the cut–off frequencies of the filters.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

106 / 592 3DB 16142 EAAA Ed.02


1–4.5.1.2 Part list of 7 GHz ODUs with external diplexer

Tab. 27. 7 GHz Transceiver assemblies

ODU Type Logistical Item Technical Description

ODU 64Mb3DB 06691ABXX ODU 64MB 9470 7.1 – 7.75 GHz LHB

ODU 64Mb3DB 06692ABXX ODU 64MB 9470 7.25 – 7.9 GHz UHB

Tab. 28. Branching assemblies for 7 GHz ODU

N.B. shifter value choice to be done by Craft Terminal

ShifterCentral

Filter 1 MHz(Lower Band)

Filter 2 MHz(Upper Band) BRANCHING ASSEMBLY

ShifterMHz

CentralFreq.MHz

LowLimit

f1

HighLimit

f2

LowLimit

f3

HighLimit

f4Logistical Item

Technical DescriptionBRANCHING 7GHZ ...

154 7212,0 7107,0 7163,0 7261,0 7317,0 3DB 10060 AAXX ... CH1–1P P.SH. 154_C MHz

154 7547,0 7428,0 7512,0 7582,0 7666,0 3DB 06774 AAXX ... CH1–1P P.SH. 154_A MHz

154 7603,0 7484,0 7568,0 7638,0 7722,0 3DB 06774ABXX ... CH2–2P P.SH. 154_A MHz

154 7561,0 7442,0 7526,0 7596,0 7680,03DB 06775 AAXX

... CH1–1P P.SH.154_B MHz

160 7561,0 7442,0 7520,0 7602,0 7680,03DB 06775 AAXX

... CH1–1P P.SH.160 MHz

154 7617,0 7498,0 7582,0 7652,0 7736,03DB 06775ABXX

... CH2–2P P.SH.154_B MHz

160 7617,0 7498,0 7576,0 7658,0 7736,03DB 06775ABXX

... CH2–2P P.SH.160 MHz

161 7240,0 7124,5 7194,5 7285,5 7355,5 3DB 06780 AAXX ... CH1–1P P.SH.161_A MHz

161 7310,0 7194,5 7264,5 7355,5 7425,5 3DB 06780ABXX ... CH2–2P P.SH.161_A MHz

161 7365,0 7249,5 7319,5 7410,5 7480,5 3DB 06781 AAXX ... CH1–1P P.SH.161_B MHz

161 7435,0 7319,5 7389,5 7480,5 7550,5 3DB 06781ABXX ... CH2–2P P.SH.161_B MHz

161 7390,0 7274,5 7344,5 7435,5 7505,5 3DB 06782 AAXX ... CH1–1P P.SH.161_C MHz

161 7460,0 7344,5 7414,5 7505,5 7575,5 3DB 06782ABXX ... CH2–2P P.SH.161_C MHz

161 7540,0 7424,5 7494,5 7585,5 7655,5 3DB 06783 AAXX ... CH1–1P P.SH.161_D MHz

161 7610,0 7494,5 7564,5 7655,5 7725,5 3DB 06783ABXX ... CH2–2P P.SH.161_D MHz

161 7665,0 7549,5 7619,5 7710,5 7780,5 3DB 06784 AAXX ... CH1–1P P.SH.161_E MHz

161 7735,0 7619,5 7689,5 7780,5 7850,5 3DB 06784ABXX ... CH2–2P P.SH.161_E MHz

161 7690,0 7574,5 7644,5 7735,5 7805,5 3DB 06785 AAXX ... CH1–1P P.SH.161_F MHz

161 7760,0 7644,5 7714,5 7805,5 7875,5 3DB 06785ABXX ... CH2–2P P.SH.161_F MHz

168 7299,0 7187,0 7243,0 7355,0 7411,0 3DB 10059 AAXX ... CH1–1P P.SH.168_B MHZ

168 7569,0 7443,0 7527,0 7611,0 7695,0 3DB 06776 AAXX ... CH1–1P P.SH.168 MHZ

168 7625,0 7499,0 7583,0 7667,0 7751,0 3DB 06776ABXX ... CH2–2P P.SH.168 MHZ







All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

107 / 5923DB 16142 EAAA Ed.02


1–4.5.1.3 Part list of 8 GHz ODUs with external diplexer

Tab. 29. 8 GHz Transceiver assemblies

ODU Type Logistical Item Technical Description

ODU 64Mb3DB 06693ABXX ODU 64MB 9470 7.7 – 8.4 GHz LHB

ODU 64Mb3DB 06694ABXX ODU 64MB 9470 8.0 – 8.5 GHz UHB

Tab. 30. Branching assemblies for 8 GHz ODU


ShifterCentral

Filter 1 MHz(Lower Band)

Filter 2 MHz(Upper Band) BRANCHING ASSEMBLY

ShifterMHz

CentralFreq.MHz

LowLimit

f1

HighLimit

f2

LowLimit

f3

HighLimit

f4Logistical Item Technical Description

BRANCHING 8GHZ ...

119 8366.5 8286.0 8328.0 8405.0 8447.03DB 06789 AAXX

... CH1–1P P.SH.119 MHz

126 8366.5 8282.5 8324.5 8408.5 8450.53DB 06789 AAXX

... CH1–1P P.SH.126 MHz

119 8408.5 8328.0 8370.0 8447.0 8489.03DB 06789ABXX

... CH2–2P P.SH.119 MHz

126 8408.5 8324.5 8366.5 8450.5 8492.53DB 06789ABXX

... CH2–2P P.SH.126 MHz

151.610 8315.010 8204.217 8274.189 8355.831 8425.803 3DB 06787 AAXX ... CH1–1P P.SH.151 MHz

151.610 8384.982 8274.189 8344.161 8425.803 8495.775 3DB 06787ABXX ... CH2–2P P.SH.151 MHz

208 8217.0 8064.0 8162.0 8272.0 8370.0 3DB 10073 AAXX ... CH1–1P P.SH.208 MHZ

208 8301.0 8148.0 8246.0 8356.0 8454.0 3DB 10073ABXX ... CH2–2P P.SH.208 MHZ

266 8097.5 7905.0 8024.0 8171.0 8290.0 3DB 06788 AAXX ... CH1–1P P.SH.266 MHZ

266 8209.5 8017.0 8136.0 8283.0 8402.0 3DB 06788ABXX ... CH2–2P P.SH.266 MHZ

294.440 7749.755 8145.915

305.560 7947.835 7738.635 7851.475 8044.195 8157.035 3DB 06786 AAXX... CH1–1P

P.SH.294/305/311 MHZ

311.320 7732.875 8162.795

P.SH.294/305/311 MHZ

311.320 8066.435 7851.475 8162.795 8281.395

... CH2–2P294.440

8063.7407862.965 7970.075

8157.4058264.515 3DB 06786ABXX

... CH2–2PP.SH.294/305/311 MHZ

305.5608063.740

7851.8458157.405

8275.635

P.SH.294/305/311 MHZ

213.5 8147.0 8035.0 8046.0 8248.0 8259.0 3DB 10103 AAXX ... CH1–1P P.SH. 213.5 MHZ

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

108 / 592 3DB 16142 EAAA Ed.02


1–4.5.2 Part lists of ODUs with embedded diplexer

The following tables report the Logistical Items of the available ODUs (with embedded diplexer) with thefollowing information from left to right:

Column 1: Shifter (MHz)Column 1bis : Central Frequency (MHz)Column 2 & 3: Tx and Rx sub–bandsColumn 4 to 7: Tx & Rx frequency ranges at RF interface (MHz)

For some frequency ranges, two types of ODU are envisaged:

– ODU with fixed shifter

– ODU with variable shifter: the shifter value can be set by Craft Terminal

1–4.5.2.1 Part list of 13 GHz ODU with embedded diplexer

Tab. 31. 13 GHz ODU (FIXED–SHIFTER)

RF interface (MHz)

1 1bis 2 3 4 5 6 7Logistical Item

Shifter CF Tx RxRF Txmin

RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

12807.5 1 1p 12750 12865 13016 13131 3CC13688ABXX

26612920.5 2 2p 12861 12980 13127 13246 3CC13689ABXX

26613073.5 1p 1 13016 13131 12750 12865 3CC13690ABXX

13186.5 2p 2 13127 13246 12861 12980 3CC13691ABXX

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

109 / 5923DB 16142 EAAA Ed.02




RF interface (MHz)



RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

14698 1 1p 14630 14766 14945 15081 3CC13692ABXX

31514829,5 2 2p 14760 14899 15075 15214 3CC13693ABXX

31515013 1p 1 14945 15081 14630 14766 3CC13694ABXX

15144,5 2p 2 15075 15214 14760 14899 3CC13695ABXX

14612 1 1p 14500 14724 14920 15144 3CC13696ABXX

42014825,5 2 2p 14710 14941 15130 15361 3CC13697ABXX

42015032 1p 1 14920 15144 14500 14724 3CC13698ABXX

15245,5 2p 2 15130 15361 14710 14941 3CC13699ABXX

14517,5 1 1p 14400 14635 14890 15125 3CC13704ABXX

49014742,5 2 2p 14625 14860 15115 15350 3CC13705ABXX

49015007,5 1p 1 14890 15125 14400 14635 3CC13706ABXX

15232,5 2p 2 15115 15350 14625 14860 3CC13707ABXX

64414600 1 1p 14500 14700 15144 15344 3CC13709ABXX

64415244 1p 1 15144 15344 14500 14700 3CC13711ABXX

72814560 1 1p 14500 14620 15228 15348 3CC13712ABXX

72815288 1p 1 15228 15348 14500 14620 3CC13713ABXX

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

110 / 592 3DB 16142 EAAA Ed.02


1–4.5.2.3 Part lists of 18 GHz ODU with embedded diplexer


RF interface (MHz)



RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

18640,5 1 1p 18581 18700 18921 19040 3CC13714ABXX

34018760,5 2 2p 18701 18820 19041 19160 3CC13715ABXX

34018980 1p 1 18920 19040 18580 18700 3CC13716ABXX

19100 2p 2 19040 19160 18700 18820 3CC13717ABXX

1560 17920 1 1p 17700 18140 19260 19700 3CC12995ABXX1560ETSI 19480 1p 1 19260 19700 17700 18140 3CC12996ABXX

Tab. 34. 18 GHz ODU (VARIABLE–SHIFTER)


RF interface (MHz)



RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

1008 17951,51 1p

17703 18200 18711 192083CC14780ABXX

1010 17950,51 1p

17700 18201 18710 192113CC14780ABXX

1008 18430,52 2p

18182 18679 19190 196873CC14781ABXX

1010 184352 2p

18180 18690 19190 197003CC14781ABXX

1008 18959,51p 1

18711 19208 17703 182003CC14782ABXX

1010 18960,51p 1

18710 19211 17700 182013CC14782ABXX

1008 19438,52p 2

19190 19687 18182 186793CC14783ABXX

1010 194452p 2

19190 19700 18180 186903CC14783ABXX

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

111 / 5923DB 16142 EAAA Ed.02


1–4.5.2.4 Part lists of 23 GHz ODU with embedded diplexer


RF interface (MHz)



RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

22157,5 1 1p 22000 22315 23008 23323 3CC13718ABXX

100822450 2 2p 22300 22600 23308 23608 3CC13719ABXX

100823165,5 1p 1 23008 23323 22000 22315 3CC13720ABXX

23458 2p 2 23308 23608 22300 22600 3CC13721ABXX

Tab. 36. 23 GHz ODU (VARIABLE–SHIFTER)


RF interface (MHz)



RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

1200 21509,51 1p

21200 21819 22400 230193CC14776ABXX

1232 21492,51 1p

21198 21787 22430 230193CC14776ABXX

1050 22306 22252 22360 23302 23410

1200 22090,5 2 2p 21781 22400 22981 23600 3CC14777ABXX

1232 22074,5 21781 22368 23013 23600

1200 22709,51p 1

22400 23019 21200 218193CC14778ABXX

1232 22724,51p 1

22400 23019 21200 218193CC14778ABXX

1050 23356 23302 23410 22252 22360

1200 23290,5 2p 2 22981 23600 21781 22400 3CC14779ABXX

1232 23306,5 23013 23600 21781 22368

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

112 / 592 3DB 16142 EAAA Ed.02




RF interface (MHz)



RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

24768,5 1 1p 24540 24997 25548 26005 3CC13734ABXX

100825221 2 2p 24994 25448 26002 26456 3CC13735ABXX

100825776,5 1p 1 25548 26005 24540 24997 3CC13736ABXX

26229 2p 2 26002 26456 24994 25448 3CC13737ABXX



RF interface (MHz)



RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

27767 1 1p 27540 27994 28548 29002 3CC13738ABXX

100828221 2 2p 27994 28448 29002 29456 3CC13739ABXX

100828775 1p 1 28548 29002 27540 27994 3CC13740ABXX

29229 2p 2 29002 29456 27994 28448 3CC13741ABXX



RF interface (MHz)



RF Txmax

RF Rxmin

RF Rxmax

Logistical Item

37335 1 1p 37050 37620 38310 38880 3CC12987ABXX

126037899,5 2 2p 37619 38180 38879 39440 3CC12988ABXX

126038595 1p 1 38310 38880 37050 37620 3CC12989ABXX

39159,5 2p 2 38879 39440 37619 38180 3CC12990ABXX

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

113 / 5923DB 16142 EAAA Ed.02


1–4.6 Antenna configurations

The ODU can be connected to:

– a full integrated antenna of 30 cm (1FT) or 60 cm (2FT) or 90 cm (3FT) or 120 cm (4FT) or 180 cm(6FT) diameter, in Full Integrated configuration (pole mounting is delivered with the antenna).

N.B. For the list of full integrated antennas (types, P/Ns and related information), please referto the Installation Handbook.

– a separated antenna, if larger diameters are necessary. In this case, the antenna is interconnectedby a flextwist directly to the ODU, or the coupler, depending on the protection used.

For the outdoor section the following 1+1 configuration are presently implemented:

• HSB configuration is available with a 1 dB/10 dB asymmetrical coupler and 1 antenna: thisconfiguration optimizes the infrastructure using only one antenna, a 10 dB coupling has beenchosen to minimize the losses on the normal path (1 dB only).

• without coupler and 2 antennas: this configuration adds a natural Space Diversity and improvesthe link budget avoiding coupler losses on the stand–by path.

• without coupler and 1 dual polarization antenna: this configuration allows a polarizationdiversity, minimizes the antenna and avoids coupler losses on the stand–by path.

The pole mounting versions are given in the following Tab. 40. for each configuration:

Tab. 40. Pole Mounting versions

Version see para

1+0 with full integrated antenna 1–4.6.1 page 114

1+1 HSB configuration with coupler and full integrated antenna (13–38 GHz) 1–4.6.2 page 116

1+1 HSB configuration with coupler and full integrated antenna (7–8 GHz) 1–4.6.3 page 117

Configuration with separated antenna 1–4.6.4 page 117

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

114 / 592 3DB 16142 EAAA Ed.02


1–4.6.1 1+0 configuration with full integrated antenna

The following Fig. 41. and Fig. 42. show the 1+0 configuration with a 30 cm (1FT) antenna in both verticaland horizontal configurations. The modification of the polarization is obtained by rotating the ODU and thenose of the antenna.

antenna

390 mm

“N” connectorfor IDU–ODU cable

antenna

(15.35 in)




360 mm

(14.17 in)

WARNING: in some ODU mechanical arrangements, the “N” connector (for IDU–ODU cable insertion)can be in the opposite position with respect to that depicted in figure above. In any case,this “N” connector is always positioned on the 450 side of ODU assembly.

Fig. 41. View of ODU with full integrated antenna (V polarization)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

115 / 5923DB 16142 EAAA Ed.02


antenna

measures as Fig. 41.

antenna






Fig. 42. View of ODU with full integrated antenna (H polarization)

Please refer to the Installation Handbook, for the P/N of “ full integrated antenna pole mounting“, andfor detailed assembly drawings.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

116 / 592 3DB 16142 EAAA Ed.02


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

– See Fig. 43. below. The 2 ODUs are interconnected through a 1 dB /10 dB coupler. The coupler isfixed on the 1+0 pole mounting with 4 catches. The 2 ODUs are connected to the coupler with theircatches.

– The modification of the polarization is done on the coupler by rotating rings at antenna port and onthe antenna by rotating the nose (the ODUs are always in the same position).

– Different couplers are available, as shown in Tab. 41. herebelow:

Tab. 41. Available couplers (13–38 GHz)

N.B. This list is given for general information purpose.For P/Ns and possible additional and related information, please refer to the InstallationHandbook.

Frequency band Coupler typeWaveguide

(3 ports)Coupling loss

13, 15 GHz 10 dB WR 62 1 dB / 10 dB

18, 23, 25 GHz 10 dB WR 42 1 dB / 10 dB

28, 38 GHz 10 dB WR 28 1 dB / 10 dB

antennaCoupler

535 mm

620 mm

360 mm

COUPLER VIEW

(14.17 in)

(24.41 in)

(21.83 in)

COUPLER WEIGHT = 4.3 Kg about

Fig. 43. Coupler (13–38 GHz)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

117 / 5923DB 16142 EAAA Ed.02


1–4.6.3 1+1 HSB configuration with coupler and full integrated antenna (7–8 GHz)

Tab. 42. Available couplers (7–8 GHz)

N.B. For coupler P/N and assembly drawings of ODUs + coupler, please refer to the InstallationHandbook

Frequency band Coupler type Waveguide (3 ports) Coupling loss

7–8 GHz 10 dB WR 112 1 dB / 10 dB

521

235

max 126

COUPLER WEIGHT = 6 Kg about

Fig. 44. Coupler (7–8 GHz) – example

1–4.6.4 Configuration with separated antenna

The ODU is fixed on a dedicated pole mounting for separated antenna. A nose adapter (different LogisticalItems depending on the waveguide dimension) is used to connect the ODU and the flextwist.

NOSEADAPTER

(under)

NOT INTEGRATEDANTENNA

POLE MOUNTING

WITH EMBEDDED DIPLEXERWITH EXTERNAL DIPLEXER

Fig. 45. Nose adapters for ODU with separated antenna

Please refer to the Installation Handbook, for the P/Ns of “nose adapters” and “not integrated antennapole mounting“, and for detailed assembly drawings.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

118 / 592 3DB 16142 EAAA Ed.02


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

Please note that the use of 600 mm flex twist is not suggested for antennas bigger than 3ft (90 cmdiameter), due to mechanical reasons. The suggested way to make the RF connection is to use theelliptical wave guide fitted with flanged connectors.

Tab. 43. ODU Output flanges with external antenna

N.B. This list is given for general information purpose.For flextwist P/Ns and possible additional and related information, please refer to theInstallation Handbook.

Equipmentand Range

(GHz)

ODU OutputFlange

FLEXTWISTSuggested

AntennaFlange

A C.E.I. E.I.A. B C D

9470 AWYUDR84 R84 WR112 PDR84 UBR84 PBR84

9470 AWY7 – 8

or:7 – 8

UBR84 R84 WR112 PBR84 UBR84 PBR84

9413 AWY12.7 – 13.3


9415 AWY14.2 – 15.4


9418 AWY17.7 – 19.7

9423 AWY21.2 – 23.6


9425 AWY24.5 – 26.5

9428 AWY27.3 – 31.3

UBR320 R320 WR28 PBR320 UBR320 PBR3209438 AWY37.0 – 40.0


L=1000 mm for 7–8 GHzL=600 mm for 13–38 GHz

N.B. If the flex–twist is not provided by Alcatel–Lucent, the user must carefully choose the type ofthe connection guide in order to limit as much as possible galvanic couples betweenantenna/flex–twist and flex–twist/ODU contact surfaces that can induce rust. For this purposeplease note that the surfaces are:– chromium–plated at ODU’s output flange side– tin–plated at flex–twist’s flange side

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

119 / 5923DB 16142 EAAA Ed.02


1–4.7 ODU operative information

This paragraph gives operative information, for installation, commissioning and maintenance purposesregarding:

– ODUs with embedded or external diplexer herebelow

– ODUs with external diplexer (additional information) on page 123

For the Light service kit cable, please refer to para.3–2.10 on page 405.

1–4.7.1 Operative information on ODUs with embedded or external diplexer

1–4.7.1.1 General, views and access points

Fig. 46. (for ODUs with embedded diplexer) and Fig. 47. (for ODUs with external diplexer) on pages120–121 show ODU views and access points.

The external interfaces are listed in Tab. 44. below, with the corresponding connector.

Tab. 44. ODU external interfaces

Ref. inFig. 46.

and Fig. 47. Interface Connector

Furtherinformation

(1) RF interface for connection of antenna or coupler waveguideTab. 45.

herebelow

(2) Connector for IDU/ODU cable male N 50 ohm

(3) Connector for Light service kit cable12–pin LEMO

(Fig. 48. on page 122)

para.3–2.10on page 405

Tab. 45. RF interface

FREQUENCY GHz ⇒ 7–8 13–15 18–25 28–38

Waveguide type ⇒ WR112 WR62 WR42 WR28

N.B. for further information, refer to para.1–4.6 on page 113

N.B. For detailed operative information regarding:

– equipment installation, please refer to the Installation Handbook

– equipment commissioning, please refer to chapter 3–2 on page 329

– equipment maintenance, please refer to section 4 on page 407.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

120 / 592 3DB 16142 EAAA Ed.02


SOLAR SHIELD

TRANSCEIVER+

BRANCHING

(4)

(1)

(3)(2)

(A)

(A)

(A)

(A)

(A) Levers (4) to fix/unfix ODU assembly to antenna or coupler

(1) RF interface for connection of antenna or coupler

(2) Connector for IDU/ODU cable

(3) Connector for Light service kit cable

(4) ODU identification label (see Fig. 37. on page 99)


Fig. 46. Views of ODUs with embedded diplexer

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

121 / 5923DB 16142 EAAA Ed.02


(3) (2)

(1)

(A)

(A)

(A)

(A)

(B)

(B)

(B)

(B)

TRANSCEIVER

BRANCHING

SOLAR SHIELD

(4)

(A) 4 levers to fix/unfix branching assembly (diplexer) to transceiver

(B) 4 levers to fix/unfix branching assembly (diplexer) to antenna or coupler

(1) RF interface for connection of antenna or coupler

(2) Connector for IDU/ODU cable

(3) Connector for Light service kit cable

(4) TRANSCEIVER identification label (see Fig. 37. on page 99)


Fig. 47. Views of ODUs with external diplexer

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

122 / 592 3DB 16142 EAAA Ed.02


7 6

8 12 11 5

1 9 10 4

2 3

KEY

Fig. 48. ODU LEMO connector pinout

1–4.7.2 ODU hardware settings

No hardware settings are envisaged on ODUs with embedded diplexer, while on ODUs with externaldiplexer a setting allows to choose the half–band (LOW or HIGH) for TX (see para.1–4.7.4 on page 123for details).

1–4.7.3 ODU identification

Through the Solar Shield window are visible the ODU or TRANSCEIVER identification label and theVertical or Horizontal polarization mounting. In case of ODUs with external diplexer, the BRANCHINGidentification label (Fig. 52. on page 126) can be viewed only separating the TRANSCEIVER from theBRANCHING.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

123 / 5923DB 16142 EAAA Ed.02


1–4.7.4 Additional operative information on ODUs with external diplexer

1–4.7.4.1 ODU composition

As shown in Fig. 49. below, the 9470AWY ODU assembly is composed, unlike the existing ones in theother frequency bands, by two boxes, one for diplexer system (BRANCHING) and the other for the all otheractive functions (TRANSCEIVER) connected together to form the ODU.

An O–RING present in the TRANSCEIVER box guarantees the ODU assembly pressurization.

N.B. This is a conductive O–RING and must be left dry. Do not wet it with silicon grease (silicongrease must be used only on O–ring between ODU and antenna).

O–RING

TRANSCEIVER

BRANCHING

Fig. 49. Composition of ODUs with external diplexer

The TRANSCEIVER box is very similar to the existing ones 9400AWY ODU used in the other frequencybands, but without the diplexer system.

The BRANCHING box provides the interface between the pole mounting/antenna and theTRANSCEIVER.

The favorite solution foresees the possibility to change in field a spare part TRANSCEIVER withoutdisconnecting the BRANCHING box from the pole mounting/antenna. The TRANSCEIVER andBRANCHING boxes fixing and unfixing are obtained through the four levers (A) shown in Fig. 47. on page121.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

124 / 592 3DB 16142 EAAA Ed.02


1–4.7.4.2 TRANSCEIVER and BRANCHING boxes coupling

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

– (A) BRANCHING box label informative contentdescribed in Fig. 52. on page 126

– (B) (HIGH FREQ) and (C) (LOW FREQ) RF interfaces on BRANCHING box

– (D) (TX) and (E) (RX) RF interfaces on TRANSCEIVER box

The TRANSCEIVER and BRANCHING boxes can be coupled in two alternative ways (1800–rotated withrespect to each other):

– BRANCHING box’s (B) (HIGH FREQ) coupled to TRANSCEIVER box’s (D) (TX)in this case the TX part of the transceiver uses the HIGH frequency range of the Shifter set by CraftTerminal (see field D in Fig. 52. on page 126); obviously the RX part of the transceiver uses thecorresponding LOW frequency range;

– BRANCHING box’s (C) (LOW FREQ) coupled to TRANSCEIVER box’s (D) (TX)in this case the TX part of the transceiver uses the LOW frequency range of the Shifter set by CraftTerminal (see field D in Fig. 52. on page 126); obviously the RX part of the transceiver uses thecorresponding HIGH frequency range.

(A) (B)

(C)

(D)

(E)

TRANSCEIVER BRANCHING

Fig. 50. ODU’s TRANSCEIVER and BRANCHING boxes coupling surfaces

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

125 / 5923DB 16142 EAAA Ed.02


N.B. There is only one possible way to couple the BRANCHING box and the TRANSCEIVER box:there is a mistake–proofing put by the factory on the TRANSCEIVER box, whose positiondepends on the type of transceiver (low or high band, as shown in Fig. 51. below) to ensure thatthe association with the BRANCHING box is always the right one. Notice that this feature wasnot available at the very beginning of the 7/8 GHz introduction.

mistake–proofing

mistake–proofing

Fig. 51. 7–8 GHz ODU’s BRANCHING box mistake–proofing

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

126 / 592 3DB 16142 EAAA Ed.02


1–4.7.4.3 Label affixed inside the ODU BRANCHING box

3DB 06775 AAAA 01

3DB 06775 AAXX

154_B LOW

LOWHIGH

HIGH160

7442 75267596 76807442.5 7512.57602.5 7673.5

A

B

C

D


ALCATELA9400 Equipment Acronym & Alcatel 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

D (shown numbers as examples)

– the field “Shifter MHz” indicates the possiblefrequency bands that can be used with thisbranching assembly.The choice between different shifters is done byCraft Terminal (refer to point [2] on page 237 fordetails).

– for each “Shifter MHz”, the TX “LOW” and“HIGH” rows indicate the frequency rangeassumed by transceiver TX section, according tothe TRANSCEIVER and BRANCHING boxescoupling described in para.1–4.7.4.2 on page124

Fig. 52. Label affixed inside the ODU BRANCHING box

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

127 / 5923DB 16142 EAAA Ed.02


1–5 TECHNICAL SPECIFICATIONS

Data indicated in this manual must be considered as typical valuesThe guaranteed values are only those indicated in the contract.

This chapter describes the technical characteristics of the 9400AWY Rel.2.1 in the following RF bandconfigurations:

Tab. 46. 9400 AWY family

SYSTEM BAND (GHz)

9470AWY 7–8

9413AWY 13

9415AWY 15

9418AWY 18

9423AWY 23

9425AWY 25

9428AWY 28

9438AWY 38

This chapter is organized as follows:

– General Characteristics on page 128, including:• Reference system standards on page 129• RF channeling on page 129• Transmitted Power at antenna port on page 130• 99% power channel bandwidth and Emission Designator on page 131• ETSI System Characteristics on page 132• Switching system on page 134

– Tributary interfaces on page 135

– Modem on page 135

– Maximum capacity and Modulation type on page 135

– IDU–ODU cable on page 135

– Man–machine interface on page 136

– Alarms on page 136

– Power supply on page 136

– Mechanical characteristics on page 136

– Environmental conditions on page 137

– Electro–magnetic compatibility / safety on page 137

– Dismantling & Recycling on page 138

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

128 / 592 3DB 16142 EAAA Ed.02


1–5.1 General Characteristics

Version SPLIT MOUNT (IDU+ODU)

Station type Terminal

Configuration 1+0 / 1+1 HSB / 1+1 FD

Reference standard(system)

Refer to para. 1–5.1.1 page 129

Transmission capacity ETSI: 2xE1, 4xE1, 8xE1, 16xE1, 32xE1

RF channel spacing Refer to para. 1–5.1.2 page 129

Tunability Refer to para. 1–5.1.3 page 130

Transmitted power Refer to para. 1–5.1.3 page 130

99% power channelbandwidth and EmissionDesignator

Refer to para. 1–5.1.4 page 131

ATPC range 20 dB (Pmax / Pmax–20 dB)

RTPC range

ETSI mask compliance till Pmax :• –20dB for 4QAM modulation• –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

Spuriousemissions

Compliant with the relevant ETSI standards

Compliant with ERC Rec. 74–01

BER receiver thresholdRefer to para. 1–5.1.5 page 132 (ETSI)

System gainRefer to para. 1–5.1.5 page 132 (ETSI)

Rx max input level –20 dBm (for a BER of 10–3)

Switching system Refer to para. 1–5.1.6 page 134

User service channels

SC #1 – DATA CHANNEL– 1x64 Kb/s data channel configurable alternatively as one of the

following modes:• G.703 asynchronous co–directional• V11 co–directional• V11 contra–directional• 4.8/9.6 Kbps V11• 4.8/9.6 Kbps V24/V28 asynchronous

– 1x64 Kbps V11 co–directional or G703 (DTE or codirectional)[also embedded in E1 slot for TMN ( first tributary, first slot) ]

SC #2 – EOW

Omnibus voice channel 64 kbit/s DTMF (Q.23) + 4–wire party line (2ways)

NMS channels

– NMS–V.11: 1x64 kbit/s V.11 co–directional for TMN (port 1)– NMS–G.703: 1x64 kbit/s G.703 co–directional for TMN (port 2)– NMS–RF: 1x64 kbit/s radio channel for TMN (internal to the radio

frame)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

129 / 5923DB 16142 EAAA Ed.02


1–5.1.1 Reference system standards

ETSI standard

EquipmentFrequency

band(GHz)

Frequencyrange(GHz)

ChannelingStandard Tx/Rx

separation(MHz)

9470 AWY

7 7.11–7.9

ITU–R F.385

150, 154, 160, 161, 168,182, 196, 245

9470 AWY4&16 QAM

8 7.725–9.5

ITU–R F.385ITU–R F.386

119, 126, 151.614, 208,266, 294.44, 305.56,

311.329413 AWY 4QAM

13 GHz 12.75–13.25 ERC 12–02 2669413 AWY16QAM

13 GHz 12.75–13.25 ERC 12–02ITU–R Rec 497

266

9415 AWY 4QAM15 GHz 14.4–15.35

MEXICOERC 12–07

315728

9415 AWY 16QAM15 GHz 14.4–15.35 ERC 12–07

ITU–R Rec 636728

420, 490, 644

9418 AWY 4QAM18 GHz 17.7–19.7

ERC 12–03ITU–R Rec 595

1008, 1010340, 1560

9418 AWY 16QAM18 GHz 17.7–19.7 ITU–R Rec 595

CHINA340, 1560

1092.5

9423 AWY 4QAM23 GHz 21.2–23.6 ERC 13–02 annex A

1008, 1050,1200,1232

9423 AWY 16QAM23 GHz 21.2–23.6 ERC 13–02 annex A

ITU–R Rec 6371200,1232

12009425 AWY 4QAM

25 GHz 24.5–26.5 ERC 13–02 10089425 AWY 16QAM

25 GHz 24.5–26.5 ERC 13–02ITU–R Rec. 748

1008

9428 AWY 4QAM28 GHz 27.5–29.5

ERC 13–02 10089428 AWY 16QAM

28 GHz 27.5–29.5ERC 13–02

ITU–R Rec. 7481008

9438 AWY 4QAM38 GHz 37–39.5 ERC 12–01 1260

9438 AWY16QAM38 GHz 37–39.5 ERC 12–01

ITU–R Rec 7491260

For all frequency bands, the ETSI reference standard is the harmonized standard EN 302 217. In thisstardard , 4QAM is class 2 and 16QAM is class 4.

1–5.1.2 RF channelling

ETSI RF CHANNELING

Capacity (Mbit/s) 2x2 4x2 8x2 16x2 32x2

RF Channeling with 4 QAM (MHz) 3.5 7 14 28 –

RF Channeling with 16 QAM (MHz) – 3.5 7 14 28

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

130 / 592 3DB 16142 EAAA Ed.02


1–5.1.3 Transmitted power at antenna port

Tolerance:– ± 2.0 dB in temperature range –33°C to +55°C for 0 to –20dB RTPC range

EquipmentOutput power

dBm(Note 1)

Tx/Rx separationMHz

9470 AWY 4QAM 25 – For 7 GHz ODUs, refer to shifters in Tab. 28. onpage 106

9470 AWY 16QAM 21

page 106– For 8 GHz ODUs, refer to shifters in Tab. 30. on

page 107

9413 AWY 4QAM 24Refer to shifters in Tab. 31. on page 108



9415 AWY16QAM 20Refer to shifters in Tab. 32. on page 109

9418 AWY 4QAM 22 Refer to shifters in:– Tab. 33. on page 110 (fixed shifters)

9418 AWY 16 QAM 19– Tab. 33. on page 110 (fixed shifters)– Tab. 34. on page 110 (variable shifters)

9423 AWY 4QAM 19 Refer to shifters in:– Tab. 35. on page 111 (fixed shifters)

9423 AWY 16QAM 16– Tab. 35. on page 111 (fixed shifters)– Tab. 36. on page 111 (variable shifters)







Note 1: Output power at antenna port.

Output power setting (dBm):– ATPC/RTPC range with 1dB step

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

131 / 5923DB 16142 EAAA Ed.02


1–5.1.4 99% power channel bandwidth and Emission Designator

Radio Type99% Power ChannelBandwidth [MHz]

ITU–R/CEPT Rec.Channel Bandwidth

[MHz]

EmissionDesignator

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

132 / 592 3DB 16142 EAAA Ed.02


1–5.1.5 ETSI System Characteristics

Data is split into following Tab. 47. to Tab. 51. according to capacity.Note for all tables: Transmitted PTX tolerance:

±2dB @ ODU Operating temperature range – 33°C ÷ + 55°C

Tab. 47. ETSI System Characteristics 32E1 (typical values)

32E1

Frequency

System Characteristics

⇓QAM

⇓7/8 GHzExternalDiplexer

13 GHz 15 GHz 18 GHz 23 GHz 25 GHz 28 GHz 38 GHz

TX Output Power@ Antenna Port

16 21 20 20 19 16 14 13 13

10–3 BER Threshold@ Antenna Port

16 –81 –79 –79 –78 –78 –77 –76 –74

10–6 BER Threshold@ Antenna Port

16 –80 –78 –78 –77 –77 –76 –75 –73

Net System Gain dB @10–3 BER Threshold

16 102 99 99 97 94 91 89 87

Net System Gain dB @10–6 BER Threshold

16 101 98 98 96 93 90 88 86


16E1

Frequency


⇓QAM



TX Output Power 4 25 24 24 22 19 17 16 16TX Output Power@ Antenna Port 16 21 20 20 19 16 14 13 13

10–3 BER Threshold 4 –88 –86 –86 –85 –85 –84 –83 –8110–3 BER Threshold@ Antenna Port 16 –84 –82 –82 –81 –81 –80 –79 –77


Net System Gain dB @ 4 113 110 110 107 104 101 99 97Net System Gain dB @10–3 BER Thr 16 105 102 102 100 97 94 92 90

Net System Gain dB @10–6 BER Thr

4 112 109 109 106 103 100 98 96Net System Gain dB @10–6 BER Thr 16 104 101 101 99 96 93 91 89

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

133 / 5923DB 16142 EAAA Ed.02



8E1

Frequency


⇓QAM






Net System Gain dB 4 116 113 113 110 107 104 102 100Net System Gain dB@ 10–3 BER Thr 16 108 105 105 103 100 97 95 93

Net System Gain dB@ 10–6 BER Thr

4 115 112 112 109 106 103 101 99Net System Gain dB@ 10–6 BER Thr 16 107 104 104 102 99 96 94 92


4E1

Frequency


⇓QAM






Net System Gain dB 4 119 116 116 113 110 107 105 103Net System Gain dB@ 10–3 BER Thr 16 111 108 108 106 103 100 98 96

Net System Gain dB@ 10–6 BER Thr

4 118 115 115 112 109 106 104 102Net System Gain dB@ 10–6 BER Thr 16 110 107 107 105 102 99 97 95

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

134 / 592 3DB 16142 EAAA Ed.02



2E1

Frequency


⇓QAM



TX Output Power@Antenna Port

4 25 24 24 22 19 17 16 16

10–3 BER Threshold@Antenna Port

4 –97 –95 –95 –94 –94 –93 –92 –90

10–6 BER Threshold@Antenna Port

4 –96 –94 –94 –93 –93 –92 –91 –89

Net System Gain dB@10–3 BER Thr

4 122 119 119 116 113 110 108 106

Net System Gain dB@10–6 BER Thr

4 121 118 118 115 112 109 107 105

1–5.1.6 Protection switching system

[1] EPS (Equipment Protection System)

In 1+1 configurations, the system can support 3 levels of protection against hardware problems.All the switches are independent and have its own switching criteria.

Available switches

Tx EPS Rx EPSODU switch

(HSB)

Select the IDU unit in Tx Select the IDU unit in Rx Select the ODU on line

Not hitless Not hitless Not hitless

Non revertive/Revertive 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

[2] RPS (Radio Protection System)

RPS, hitless–switch type, is equipped to provide protection against radio propagation problems.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

135 / 5923DB 16142 EAAA Ed.02


1–5.2 Tributary interfaces

E1

Input / outputelectrical interface

ITU–T G.703

Code HDB3

Impedance75Ω unbal120Ω bal

Jitter Generation ITU–T G.823

Jitter Tolerance ITU–T G.823

Jitter TransferITU–T G.736ITU–T G.742

1–5.3 Modem

Modulation 4/16 QAM

Demodulation Coherent

Equalizer type 19–tap FSE

Channel coding Reed Solomon (255,239)

Spectrum shaping Raised cosine

1–5.4 Maximum capacity and Modulation type

The employed Software Label (stored in the FLASH CARD plugged into the IDU Main unit) gives themaximum capacity for the tributaries and the Modulation Type.For details please refer to Tab. 23. on page 93.

1–5.5 IDU–ODU cable

Coax. connector N (50 ohm)

Coax. cable type (single)Coaxial single type, 50 W, dielectric foam and braid(n.b.1)

Guaranteed cable maximum length

Depends on:– cable type employed– bit rate ( � 16E1 or > 16E1)(n.b.1)

Signals on the cable DC Voltage/HDB3 Tx/HDB3 Rx (n.b.2)

Gross bit rate on the cable:– ETSI (2 to 16xE1)– ETSI (17 to 32xE1)

39.168 Mbit/s78.336 Mbit/s

n.b.1 for details on cables that can be employed and relevant cable maximum length, refer to theInstallation handbook.

n.b.2 the HDB3 signal contains the main signal, auxiliary signal and IDU–ODU service channel.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

136 / 592 3DB 16142 EAAA Ed.02


1–5.6 Man–machine interface

Visual (LEDs) 9 (on IDU Main unit) +3 (on IDU Extension unit)

Other

– F interface for Personal Computer (WindowsTM) RS232C– TMN interface Ethernet 10/100 Base–T– TMN Data channel 64kbit/s interface RS422/G703– Interface for Telephone Service Channel

1–5.7 Alarms

Equipment alarms 3 outputs (IDU HW Failure alarm, ODU Main Failure alarm, ODU SpareFailure alarm)

Housekeeping alarms 6 inputs / 4 outputs

1–5.8 Power supply

DC nominal voltage (primary) � 48 to � 60 Vdc �20%

Polarity + or – floating (isolated ground)

Max Power Consumption1+0 : � 50W

1+1 : � 100W

1–5.9 Mechanical characteristics

Dimensions (H x W x D) H Weight

1+0 IDU43 x 210 x 443 mm1.7 x 8.3 x 17.4 in

1U< 2.5 kg< 5.5 lb

1+1 IDU86 x 210 x 443 mm

3.4 x 8.3 x 17.4 in2U

< 5 kg< 11 lb

ODU see Tab. 25. on page 98

Antenna

– Integrated with max diameter depending on frequency (refer to theInstallation Handbook for details)

or:– Separated for larger diameters

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

137 / 5923DB 16142 EAAA Ed.02


1–5.10 Environmental conditions

Main environmental aspects of Alcatel–Lucent products are:

– Energy consumption during manufacturing and use– Materials harmfulness and recyclability– Emission to air, water or soil related to the manufacturing and the use of the product– Electromagnetic (EM) emissions– Value recovery at the product end of life

1–5.10.1 Operating environmental conditions

Storage EN 300 019 class 1.3

Transport EN 300 019 class 2.3

Operation

IDUEN 300 019 class 3.2

Temperature range: –5°C to +55°C (23°F to 131°F)Operation

ODUEN 300 019 class 4.1, IP 67

Temperature range: –33°C to +55°C (–27.4°F to 131°F)

1–5.10.2 Electro–magnetic compatibility/safety

EMC EN 300 385 class B grade B/FCC Part 15 subpart B–class A

Safety EN 60 950

Power supply EN 300 132

Electro–Staticdischarge EN 55022 class B

Lightning protection

Symmetric protection implemented in ODU & IDU

� 5kV on cable ground according to IEC 1000–4–5 with 2 wave types:

1.2/50 μs and 10/700 μs

1–5.10.3 Waste from Electrical and Electronic Equipment (WEEE)

This product must be selectively collected and treated. Treatment applied at end of life of the product inthese countries shall comply with the applicable national laws implementing directive 2002/96EC onwaste electrical and electronic equipment (WEEE).

The use of the crossed–out 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 possiblenegative effects on the environment and on human health.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

138 / 592 3DB 16142 EAAA Ed.02


1–5.11 Dismantling & Recycling

Alcatel–Lucent 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 recyclingdetail is the document:

Tab. 52. Reference documentation for dismantling and recycling detail for 9400AWY R.2 equipment

Product CodeDOC.TYPE(N.B.)

Denomination

AWY/S 8BW036840000 EUZZA 9400AWY SCALABLE RADIO SYSTEM ECODECLARATION

N.B. DOC. TYPE for Alcatel–Lucent internal use only

Such a document is available on specific request to your Alcatel–Lucent local dealer.

NOTE FOR Alcatel–Lucent INTERNAL USE

cited document, in Adobe Acrobat pdf format, can be retrieved from PDM archive. Get highestavailable edition.

a ) END OF SECTION

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

139 / 5923DB 16142 EAAA Ed.02

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL

SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL


Chapter 2–1 – SWP 9400AWY R.2.1 V2.1.1 descriptionIt gives general information on the SWP version.

141

Chapter 2–2 – Introduction on TCO Suite and CT views and menusIt describes the functions of the TCO Suite, describes how to start and close theCraft Terminal application, how to login and logout the NE, and sums–up theorganization of the 9400AWY NE Craft Terminal, presented after the NE login.

143

EQUIPMENT CONFIGURATION MANAGEMENT

Chapter 2–3 – ConfigurationIt describes the configuration relevant to the equipment management.

189

Chapter 2–4 – EquipmentIt deals with the presentation of the N.E. and the structure of the hierarchical tree,and the types of subracks and boards, that comprise the Network Element.

219

Chapter 2–5 – Line InterfaceIt describes the operations necessary for the configuration setting and verificationof each tributary.

227

Chapter 2–6 – RadioIt deals with the management of the Radio transmission features.

233

Chapter 2–7 – External input and output pointsIt describes how to display and set the input/output environmental alarms(housekeeping alarms).

247

FUNCTIONS FOR MAINTENANCE

Chapter 2–8 – SupervisionIt describes how to manage the NE access from OS or local ECT and how to restartthe NE.

251

Chapter 2–9 – Protection schemesIt deals with the management of the Radio protections.

257

Chapter 2–10 – LoopbacksIt describes the commands for loopback management, for commissioning ormaintenance purposes.

267

Chapter 2–11 – DiagnosisIt describes how to access the Alarm and Event Log files and explains theSummary Block Diagram View menu.N.B. The chapter does not describe the Log Browser. Reference must be

done to the specific “ELB Operator’s Handbook”.

277

Chapter 2–12 – Performance MonitoringIt deals with the use of the Performance Monitoring functionalities.

289

TABLE CONTINUES

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

140 / 592 3DB 16142 EAAA Ed.02

USER MANUAL9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL


SOFTWARE MANAGEMENT

Chapter 2–13 – Software ManagementIt deals with the management of the functions related to the softwareverification/download.

297

Chapter 2–14 – MIB ManagementIt deals with the management of the functions related to the back–up and restoreof equipment configuration data.

301

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

141 / 5923DB 16142 EAAA Ed.02


2–1 SWP 9400AWY R.2.1 V2.1.1 DESCRIPTION

This chapter gives general information regarding the Software Package this manual refers to.

2–1.1 SWP 9400AWY R.2.1 V2.1.1 general description

2–1.1.1 General

The software products are distributed by Alcatel–Lucent in a CD–ROM.

In this CD–ROM are contained:

• Software packages for NE management by means of the craft terminal

• Software package of the NE, to be installed in the NE or update the NE (by means of downloadfunction)

The software package used for management allows the dialogue between craft terminal and NE, torealize all the functions of the NE and EML–ULS ).

The software package used for updating the NE must be installed on the PC and then downloaded onthe NE, thus following product evolution.

2–1.1.2 Software product list and part numbers

Every Software Product is identified by a Technical Code and a Technical Description and is distributedby a CD–ROM with the same identifiers, listed on the following table:

Tab. 53. Software products part numbers

REF Technical Description Technical Code

[a] SWP 9400AWY R.2.1 V2.1.1 3DB16131ABAA

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

142 / 592 3DB 16142 EAAA Ed.02


2–1.2 SWP 9400AWY R.2.1 V2.1.1 specific information

2–1.2.1 PC characteristics

Refer to para.3–1.1.1 on page 309

2–1.2.2 NE MIB Compatibility

NE MIB structure is automatically converted from previous release 2.1.0, using the procedure describedin Chapter 4–9 on page 495

V2.1.1 NE MIB structure is not backward compatible with those of previous release 2.1.0 (see point[1]–6 )–WARNING on page 495

NE MIB structure is not compatible with any releases 1.0.x and 2.0.x

2–1.2.3 SWP version specific data and Reference Information Models

Make reference to the Product Release Note (see para.5–7.2.2 on page 571 )

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

143 / 5923DB 16142 EAAA Ed.02


2–2 INTRODUCTION ON TCO SUITE AND CT VIEWS AND MENUS

This chapter describes the functions of the TCO Suite, describes how to start and close the Craft Terminalapplication, how to login and logout the NE, and sums–up the organization of the 9400AWY NE CraftTerminal, presented after the NE login.


– Requirements on page 144

– TCO Suite description on page 146

– TCO Suite Alarms & Settings functions on page 156

– PC–NE physical connections on page 170, including:• Physical interfaces for the NE management on page 170• Local connection of the Craft Terminal to the NE on page 171

– Craft Terminal: NE supervision, login, logoff and switch off on page 172

– 9400AWY view organization on page 181

– Introduction to the CT menu options on page 184

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

144 / 592 3DB 16142 EAAA Ed.02


2–2.1 Requirements

a ) PC characteristics

The PC used for TCO Suite application and/or employed as Craft Terminal must meet allspecifications pointed out in para.3–1.1.1 on page 309.

b ) Cables necessary for PC–to–NE local connection

• for the local connection between PC and NE RS232 serial ports, one RS232 cable is necessary(P/N 1AB054120027)N.B. In alternative, for the usage of the NE’s F–interface with any PC having no RS232

serial port (but obviously with USB ports available) it is possible to employ the “USBTO RS232 ADAPTER” , ordering it to Alcatel–Lucent (P/N 1AF11294AA**).

• for the local direct connection between PC and NE Ethernet ports, one cross–connect Ethernetcable is necessary.Otherwise the connection can be done by a normal Ethernet cable through a LAN.For explanatory drawing, see Fig. 59. on page 154.Typical Alcatel–Lucent Ethernet cables are:

Tab. 54. Typical Alcatel–Lucent Ethernet cables

Length Type P/N

6 mnormal 3DB 14050 AA**

6 mcross–connect 3DB 14051 AA**

2 mnormal 3DB 05020 AA**

2 mcross–connect 3DB 05021 AA**

N.B. The TCO Suite applications can use the Ethernet interface only.The Craft Terminal application can use both the Ethernet and the RS232 interfaces.

c ) Craft Terminal

If the Craft Terminal application must be used, the SWP installation must have been already carriedout, as specified in chapter 3–1 on page 309.

d ) NE state

• the SWP (NE–specific components) must be already present in the NE’s flash card and itsactive version (see point [2] on page 63 to do this check) must be equal to that of the:

– SWP CD–ROM this manual refers to (in case of TCO Suite application run directly fromthe CD–ROM itself)

– SWP installed in the Craft Terminal (see point [1] on page 62 to do this check).

Solve different situations, if any, according to instructions given in para.1–2.6.4 on page 64.

• if the NE must be accessed in remote way (by TCO Suite application or by RECT application)it must have already a valid TCP/IP address, and such address must be known by the Operator.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

145 / 5923DB 16142 EAAA Ed.02


e ) Operator profiles and allowed operations

The menu options described in this section are all available logging in the system with theAdministrator profile username and password. Logging the system with other operatorprofiles result in some functionality access limitations. For further information please referto Profiles management , para.2–3.6 on page 214.

f ) Operator skills

• the Operator shall be familiar with the use of personal computers in WINDOWS–NT /WINDOWS–2000 / WINDOWS–XP (professional version only) environment, internally towhich the Network Element’s application software operates.

• the Operator must be familiar with all the functionalities of this equipment.• furthermore, for a number of configuration applications, the operator shall be aware of some

specifications of the International Standard Organization (ISO) and of the standards applied tothe Synchronous Digital Hierarchy (SDH) (CCITT Recommendations).

g ) Documentation

Besides this manual, all the documentation set this manual belongs to must be available to theOperator, to retrieve pieces of information not contained in this manual. The documentation set isdescribed in Appendix G on page 567.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

146 / 592 3DB 16142 EAAA Ed.02


2–2.2 TCO Suite description

This paragraph is organized as follows:

– TCO Suite scopes below

– Summary on page 147

– TCO Suite start–up on page 148

– TCO Suite Main Menu functions on page 149, including:• Pre–Provisioning Tool on page 150• Set–Up Tool on page 150• Alarms & Settings on page 150• Advanced Settings on page 150

– TCO Suite Advanced Settings Page on page 151, including:• Java JRE Package Installation on page 152• Serial –F– Interface Driver Installation on page 153• 1320CT Package Installation on page 153• 1320CT Package De–Installation on page 153• Local Copy of TCO Suite on page 153

– Note: Direct and Remote Connections on page 154

– Warning about interface customization carried out by the Direct Connection on page 155

2–2.2.1 TCO Suite scopes

The TCO Suite is a feature that allows the operator to access and configure the NE from his/her PC withoutthe need for software installation in PC environment (i.e. running the TCO Suite directly from the SWPCD–ROM).

Moreover, after having installed the SWP components and the TCO Suite local copy in the PC environment(as described in chapter 3–1 on page 309), most of TCO Suite functionalities are available also afterhaving removed the SWP CD–ROM from the PC CDROM unit.

TCO Suite works through web pages with simple operations available with a single mouse click.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

147 / 5923DB 16142 EAAA Ed.02


2–2.2.2 Summary

After having started up the TCO Suite (para.2–2.2.3 on page 148), the TCO Suite Main Menu becomesavailable (Fig. 55. on page 149) with the following main tools:

– Pre–Provisioning ToolThis is a full–local application.

– Set–Up Tool and Alarms & SettingsThese applications require the access and the login to a 9400AWY NE from your PC.

To access and login a 9400AWY NE from your PC for these applications:

• the CT–NE connection can be:

– physically and logically local, through a cross–connect Ethernet cable for the local directconnection between PC and NE Ethernet ports

– physically local but logically remote, by a normal Ethernet cable through a LAN for theconnection between PC and NE Ethernet ports

– physically and logically remote, by a connection between PC Ethernet port and the NEthrough the RECT function or the TCP/IP network.

N.B. The Set–Up Tool and Alarms & Settings applications cannot be used through thePC–NE local connection by RS232 serial F interface

• you must have a UserName and password set

• in case of logically remote connection, you must know the NE’s TCP/IP address

– Operational & MaintenanceThis application corresponds to the 1320CT application. Refer to para.172 on page 2–2.5 for details.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

148 / 592 3DB 16142 EAAA Ed.02


2–2.2.3 TCO Suite start–up

Standard behavior

The Suite auto–runs itself (if this feature is enabled on user’s PC) as soon as CD–ROM is read by PC.If auto–run does not start, user must run (double–click with mouse on) the Start.exe file, available onCD–ROM root in order to launch TCO Suite.

Since this TCO Suite works using Java™ software, it is mandatory to have a Java Runtime Environment(JRE) installed on the system. Allowed JREs are Sun only, with version number higher or equal than1.4.2_12. The first operation performed by auto–run procedure is the check for JRE.

All HTML pages used for TCO Suite are XHTML 1.1 and CSS 2.0 standards compliant with respect to W3C(WWW Consortium) specifications.

Minimal screen resolution allowed to use TCO Suite is 1024x768 pixels

If there is no JRE on user’s PC or if there is a JRE installed on user’s PC but its version number if lowerthan 1.4.2_12, user will be asked to install the Sun Java Runtime Environment version 1.4.2_12 availableon TCO Suite CD–ROM (Fig. 53. below).

Fig. 53. Java installation request

In both cases:– if user denies authorization to install the suitable JRE, TCO Suite won’t be executed at all– if user gives authorization to install the suitable JRE, after some minutes the installation message

appears:

Fig. 54. JRE installation completion

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

149 / 5923DB 16142 EAAA Ed.02


After, the default browser (configured as for user preferences) opens the TCO Suite Start.html page(Fig. 55. below).

Special conditions

For any special condition which may occur during the TCO Suite start–up and the countermeasures totake, refer to the Appendix B – TCO suite start–up special conditions on page 511

2–2.2.4 TCO Suite Main Menu functions

Fig. 55. and Fig. 56. on page 149 show the layouts of the “TCO Suite Main Page” as described from theinternal version of AS.html file, respectively for the “CD–ROM version” and the “Local version”.N.B. The TCO Suite Local version must be explicitly created as described in para.2–2.2.5.5 on page

153This page shows the main TCO Suite menu with the following functions:– Pre–Provisioning Tool– Set–Up Tool– Alarms & Settings– Operational & Maintenance– Advanced Settings (N.B.)N.B. The “Advanced Settings” button is not available in the local version of the “TCO Suite Main

Page”.

Fig. 55. TCO Suite Start.html page (CD–ROM version)

Fig. 56. TCO Suite Start.html page (Local version)

Detailed functions and differences between CD–ROM and Local TCO Suites will be described in followingsub–paragraphs.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

150 / 592 3DB 16142 EAAA Ed.02


2–2.2.4.1 Pre–Provisioning Tool

This button is a one–click execution for the Pre–Provisioning Tool.This tool allows the off–line creation and modification of a provisioning file, without accessing any NE.This file will be after used to configure the NE (after having logged it) with a simple load command.

For procedure execution, refer to para.3–2.3.6 point [2] on page 341.

2–2.2.4.2 Set–Up Tool

This button is a one–click execution for the Set–Up Tool.This tool allows to access a NE, recover a configuration file previously created (e.g. through the TCO SuitePre–Provisioning Tool) or get configuration data from the NE, and check/modify/apply such a configurationto the NE.

For procedure execution, refer to para.3–2.3.6 point [3] on page 341.

2–2.2.4.3 Alarms & Settings

The “Alarms & Settings” function allows the user to login a NE through the use of the NE web server viaa generic Internet browser, in order to monitor the status of NE alarms and to get and/or set some NE’sparameters.

For procedure execution, refer to para.2–2.3 on page 156.

2–2.2.4.4 Operational & Maintenance

This function runs the 1320CT software application.

This function has two different behaviors, one for “CD–ROM” TCO Suite and one for “Local” TCO Suite.The main difference is related to 1320CT software installation:– “Local” TCO Suite does not install 1320CT in any case– “CD–ROM” TCO Suite will perform a complete 1320CT installation, if needed (if such software is not

available).

If 1320CT is available on user’s system, the behavior is common between “Local” and “CD–ROM” TCOSuites:

[1] CD–ROM TCO SuiteIn this case, if the 1320CT platform is not installed, the user will be asked to perform the installationand, if the user agrees, the installation will be started.

The 1320CT platform installation is described in para.3–1.5 (Installation of SWP componentsfrom the SWP CD–ROM) from step 5 ) on page 316

[2] Local TCO SuiteIf user’s PC does not have a 1320CT platform installed, no installation is performed and an errormessage is shown to user.

For procedure execution, refer to point e )–1 ) on page 174.

2–2.2.4.5 Advanced Settings

This button will show to user the related HTML page: this function is available through CD–ROM TCO Suiteonly. All functions related to this page are described in following para.2–2.2.5 on page 151.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

151 / 5923DB 16142 EAAA Ed.02


2–2.2.5 TCO Suite Advanced Settings Page

This page is opened clicking the “Advanced Settings” button of the CD–ROM TCO Suite Main Menu(Fig. 55. on page 149). Such page is shown in Fig. 57. below and contains:

– Java JRE Package Installation

– Serial –F– Interface Driver Installation

– 1320CT Package Installation

– 1320CT Package De–Installation

– Local Copy of TCO Suite

– Back : go back to Main Menu of Fig. 55. on page 149

Fig. 57. TCO Suite AS.html page (Advanced Settings)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

152 / 592 3DB 16142 EAAA Ed.02


2–2.2.5.1 Java JRE Package Installation

This button connects to the installation file for the Java Runtime Environment, version 1.4.2_12. Thebehavior of this button depends on browser configuration. The usual behavior is:

– Internet Explorer asks the user to “Open” or “Save” the file (Fig. 58. below):

Fig. 58. Internet Explorer: .exe files management

– Mozilla Firefox automatically saves the file, the first time (or every time, depends on configuration)asking the user where to place it;

– Mozilla browser automatically saves the file, the first time (or every time, depends on configuration)asking the user where to place it;

In any case, for most browsers the default behavior can be changed but this strictly depends on browserconfiguration and user choices.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

153 / 5923DB 16142 EAAA Ed.02


2–2.2.5.2 Serial –F– Interface Driver Installation

This button starts the installation (from the SWP CD–ROM) in PC environment of the LLMAN (AlcatelLower Layer MANager), necessary when communication with NE’s ECT serial port is required.

For procedure execution, refer to para.5–3.2.1 on page 519.

2–2.2.5.3 1320CT Package Installation

This function will automatically perform the complete installation of the existing 1320CT platform withoutinstalling a needed JRE (that is anyway installed if this function can be performed) and without installingthe “Alcatel Lower Layers Manager” software.

For procedure execution, refer to para.3–1.5 on page 314.

2–2.2.5.4 1320CT Package De–Installation

This function is a single–click complete de–installation for the 1320CT package. This function won’tremove neither possible JRE installed nor “Alcatel Lower Layers Manager” software.Sequence of screens shown to user depend on speed and performance of user’s PC since all theprocedure is automatic and all the de–installations needed are performed at the same time without theneed for interaction by the user.

2–2.2.5.5 Local Copy of TCO Suite

This function, written as part of the TCO Suite Java applet, allows the user to create the “Local” TCO Suiteby copying the content of the TcoSuite directory on a location specified by user.

For procedure execution, refer to para.3–1.6.1 on page 318.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

154 / 592 3DB 16142 EAAA Ed.02


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

The difference between “Direct” or “Remote” connection, asked to user as in Fig. 62. on page 156, isdepicted in Fig. 59. below, and reflects the working mode for JUSM application:

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

– in case of “Direct” connection, user’s PC is considered as directly connected to NE via across–connection Ethernet cable so a Ethernet modification is needed on user’s PC since bothfunctions (“Set–Up Tool” and “Alarms & Settings”) have to be sure about PC connection with NE inorder to be performed.

HUB

IP NETWORK

PC Ethernet interface

“Direct”

“Remote”

cross–connect Ethernet cable

Fig. 59. ECT–NE “Direct” and “Remote” connections

For this reason, the TCO Suite will perform a search on user’s computer resources in order to find allnetwork adapters related to active (enabled) network connections. Then, if more than one network adapteris found, the user must select the one to modify in order to connect his/her PC to the NE. This selectionbox is shown in Fig. 60. :

Fig. 60. Network Adapter selection

Such figure is an example created to show the possible layout. Actually, if user’s PC owns one networkadapter only and the “Alcatel Virtual Network Card for Lower Layers”, the selection is automatically donewithout bothering the user, which won’t see the dialog box shown in Fig. 60. above.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

155 / 5923DB 16142 EAAA Ed.02


In order to let the user knows more information about adapters details, by clicking the “Details” togglebutton some supplemental information are shown as in Fig. 61. :

Fig. 61. Network Adapter details

When the user clicks on “Apply” the selected network adapter is modified in order to allow user’s PCconnecting with specified NE.

Network adapters configuration is saved in XML format using the NAML (Network Adapter MarkupLanguage) format in the NAML directory inside user’s personal directory usually located inside“Documents And Settings” directory on system disk.

2–2.2.7 Warning about interface customization carried out by the Direct Connection

When the “Direct” connection (described in previous para.2–2.2.6 on page 154) is set up, the systemcarries out an interface customization that makes any subsequent attempt to start the Craft Terminal usingthe F–interface impossible, even after the logging off from the TCO Suite application and independentlyfrom the settings explained in para.2–2.4.2 on page 171.

These are the simplest alternative ways to solve this situation:

– launch the TCO Suite Alarms & Settings defining the “Remote” connection, then close the TCOSuite application

or:

– perform the PC shut down.

Any of these operations resets the interface customization said above, so that the start of the CraftTerminal using the F–interface becomes again possible.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

156 / 592 3DB 16142 EAAA Ed.02


2–2.3 TCO Suite Alarms & Settings functions


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

2–2.3.1 TCO Suite Alarms & Settings start–up

To launch this application, click on the button Alarms & Settings of the “TCO Suite Main Page” (seeFig. 55. and Fig. 56. on page 149).

Then, User is asked to distinguish between “Direct” or “Remote” connection (Fig. 62. below) and he/shewill be asked to fill the IP address field used to connect to NE.

Fig. 62. Direct or Remote connection by the TCO Suite

The difference between “Direct” or “Remote” connection is described in para.2–2.2.6 on page 154.

WARNING 1: In case you choose the “Direct” connection, read carefully para.2–2.2.7 on page 155(Warning about interface customization carried out by the Direct Connection)

WARNING 2: In case you have in your network some 9400AWY NEs with SWP 2.0.x (N.B.) and otherswith SWP 2.1.x you must be aware that:

• by TCO Suite of SWP 2.0.x you can access only 9400AWY NEs with SWP 2.0.x

• by TCO Suite of SWP 2.1.x you can access only 9400AWY NEs with SWP 2.1.x

The other combinations do not work properly!

N.B. in 9400AWY Rel.2.0, TCO Suite is available starting from SWP–version 2.0.4.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

157 / 5923DB 16142 EAAA Ed.02


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

Fig. 63. NE login by the TCO Suite

As soon as the connection with the NE is established, the Alarms & Settings Main Menu screen appears(Fig. 64. below).

Fig. 64. TCO Suite’s Alarms & Settings Main Menu screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

158 / 592 3DB 16142 EAAA Ed.02


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

Tab. 55. Operations allowed in TCO Suite Alarms & Settings screen according to the Login profile

Login profile

Function Administrator, Craftpersonand Operator

Viewer

Date & Time Setting(para.2–2.3.2 on page 159)

YES read only

Configuration Setting(para.2–2.3.3 on page 160)

YES NO

Configuration Info(para.2–2.3.4 on page 161)

YES YES

Get Configuration File(para.2–2.3.5 on page 164)

YES YES

Active Alarms(para.2–2.3.6 on page 165)

YES YES

Power Measurement(para.2–2.3.7 on page 166)

YES read only

Licence Info(para.2–2.3.8 on page 166)

YES YES

Modem Speed(para.2–2.3.9 on page 167)

YES read only

NAT Option(para.2–2.3.10 on page 168)

YES NO

User can perform desired operations by clicking on proper label in proposed menu. The behavior of theWeb Server for each of menu entry is detailed in the following sub–paragraphs.Logout button gives the user the possibility to clear its authentication parameters and reload the initial page(Fig. 64. on page 157) for starting a new session.

The links between pages are available by following standard procedures and correct “navigation” steps.If the user will follow non–authorized processes or will try to search for other pages, a “404” error will showthe “Page Not Found” result. In this case, the user will be allowed to get back to initial login page and hehas to redo the whole login process.

WARNING: if, during the usage of the TCO Suite Alarms & Settings functions, the connected NEbecomes unavailable (e.g. for network problems, or after having loaded NE data whichmodify the NE IP address), the sand–glass symbol appears and no operations are longerpossible. In this case, close the TCO Suite Alarms & Settings session, then verify the NEreachability (e.g. by PING function).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

159 / 5923DB 16142 EAAA Ed.02


2–2.3.2 Date & Time Setting

For authorized users, this function allows to modify NE internal time so that it can be automatically alignedwith user’s PC internal time or the user can set its preferred time and date on NE. Also, it is possible, forthe user, to verify the status of NTP configuration for automatic synchronization using a couple of NTPserver (main and back–up).

There are two functions available to authorized users:

1. NE Time Setting with OS time;

2. GMT Time Manual Setting.

In the first situation (Fig. 65. below) the user will see his/hers PC internal time and by clicking on apply,NE will receive UTC time based on PC configuration.

For example: if user’s PC is configured as located in central Europe (CET or CEST time zones) and itshows 2006–08–25 11:40:00, by clicking “Apply” button NE web server will receive 2006–08–25 09:40 dueto Daylight Saving (summer) Time one hour difference with respect to normal time and to one hour timedifference between CET time zone and GMT time zone.

Fig. 65. TCO Suite’s Alarms & Settings “Date & Time Configuration” page

The other function allows user to directly send a specific date and time information to NE without botheringon 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 theoperation and current time or selected time.

In case of enabled NTP, this page won’t allow to modify NE time and date

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

160 / 592 3DB 16142 EAAA Ed.02


2–2.3.3 Configuration Setting

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

Fig. 66. TCO Suite’s Alarms & Settings “Configuration Setting” page

To carry out this operation, you must browse from your PC a configuration file “configuration_name.qcml”previously created (e.g. through the TCO Suite Pre–Provisioning Tool, N.B.), and then click on ApplyConfiguration button.

N.B. refer to para.3–2.3.6 on page 341 for details.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

161 / 5923DB 16142 EAAA Ed.02


2–2.3.4 Configuration Info

The Get Configuration Report function allows the user to download the full NE system report. Selecting(by click) this function from main menu will show the user a “Save File” screen (Fig. 67. below) that givesthe user the capability to browse its system in order to select the path where to save the full report file.

N.B. With some browsers (e.g. Mozilla), it is necessary to specify a text–reading application (e.g.WORD PAD) to open and read correctly the file.

Fig. 67. TCO Suite’s Alarms & Settings “Get Report Request”

This screen content, shape, graphics and layout all depend on operating system version and languageand on used browser too. The report file is a text file that describes the configuration of the NE. It containsall the information once added to the quick configuration report or in the current configuration view usedin the former versions. An example of this file content is shown below:

⋅NE CONFIGURATION––––––––––––––––

NE Configuration Type:1+0 16E1/DS1–ETH (PSU4860)

Market: ETSI

Frame Structure: 8E1

Modulation: 16QAM

Impedance: Unbalanced 75 Ohm

TRIBUTARIES CONFIGURATION

–––––––––––––––––––––––––

E1 Tributary 1: Signal Mode: Unframed

E1 Tributary 2: Signal Mode: Disabled



E1 Tributary 5: Signal Mode: Framed



E1 Tributary 8: Signal Mode: Framed

DATA CONFIGURATION

––––––––––––––––––

[Ethernet Port 1]

Status: Disabled

Auto Negotiation: Disabled

Speed Without Autonegotiation: 100 Mbit/s

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

162 / 592 3DB 16142 EAAA Ed.02


Advertised Capability for AutoNegotiation: 10 Mbit/s

[Ethernet Port 2]

Status: Disabled

Auto Negotiation: Disabled

Speed Without Autonegotiation: 100 Mbit/s

Advertised Capability for AutoNegotiation: 10 Mbit/s

RADIO CONFIGURATION

–––––––––––––––––––

[Channel 1]

Tx Frequency: 0 kHz

Tx Range: [5000000 , 40000000] kHz

Rx Frequency: 0 kHz

Rx Range: [5000000 , 40000000] kHz

Current Tx Power: 30 dBm

Atpc Status: Disabled

Shifter Settings: Unconfigured

EXTERNAL POINTS STATUS

––––––––––––––––––––––

[Input Point 1]

User Label:CPI1

Polarity: Active Closed

[Input Point 2]

User Label:CPI2


[Input Point 3]

User Label:CPI3


[Input Point 4]

User Label:CPI4


[Input Point 5]

User Label:CPI5


[Input Point 6]

User Label:CPI6


[Output Point 1]

User Label:CPO1


Switching Criteria: Manual

External State: Off

[Output Point 2]

User Label:CPO2



External State: Off

[Output Point 3]

User Label:CPO3



External State: Off

[Output Point 4]

User Label:CPO4



External State: Off

NETWORK INFORMATION

–––––––––––––––––––

[Ospf Area 1]

IP Address: 0.0.0.0

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

163 / 5923DB 16142 EAAA Ed.02


Stub Flag: FALSE

[Ospf Area 2]

IP Address: 10.0.1.0

Stub Flag: FALSE

Local IP Address: 10.0.1.2

LAN IP Address: 151.98.141.77

Ethernet Status: Enabled

Mask: 192.0.0.0

MAC Address: 00:20:60:00:03:5e

Routing Protocol: None

[Static Route: 1]

IP Address: 151.98.70.0

IP Mask: 255.255.254.0

Point to Point Interface: RF

[Static Route: 2]

IP Address: 151.98.170.0

IP Mask: 255.255.254.0


[Static Route: 3]

IP Address: 172.24.168.0

IP Mask: 255.255.255.0


[TMN–RF]

Status: Disabled


[TMN–V11]

Status: Disabled

Interface Mode: Not Used


[TMN–G703]

Status: Disabled

Interface Mode: Not Used


NTP CONFIGURATION

–––––––––––––––––

Status: Enabled

Main Server IP Address: 100.5.4.75

Spare Server IP Address: 100.5.5.5

INSTALLED SOFTWARE

––––––––––––––––––

[Active SW Package: R94A – V02.01.00]

Status: Committed

Operational State: Enabled

SW Units:

EC – V03.00.03 – Size(Bytes): 1769472

OC_R – V02.01.01 – Size(Bytes): 215469

The content above describe a sample configuration report in text format.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

164 / 592 3DB 16142 EAAA Ed.02


2–2.3.5 Get Configuration File

Just like the Get Configuration Info function, the Get Configuration File allows the user to download thefull NE system report. Instead of being in “human–readable” text format, the configuration file is describedin QCML format and it can be used by Quick Configuration by Text File or by Pre–Provisioning and Set–UpTools. Selecting (by click) this function from main menu will show the user a “Save File” screen(Fig. 68. below) that gives the user the capability to browse its system in order to select the path whereto save the full report file.

N.B. With some browsers (e.g.Mozilla), it is necessary to specify a text–reading application (e.g.WORD PAD) to open and read correctly the file.

Fig. 68. TCO Suite’s Alarms & Settings “Get Configuration” Request

This file is an XML standard–based set of configuration information that Pre–Provisioning and Set–Up Toolcan preview in a human–readable HTML layout and allow the user to modify such configuration using aset of wizard/simplified steps just like the Quick Configuration by Text File do.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

165 / 5923DB 16142 EAAA Ed.02


2–2.3.6 Active Alarms

Alarms monitoring is represented by a simple colored table that will shows an updated list of active alarms.Older alarms, anyway, won’t be removed but in order to be more comprehensible, activated alarms tablewill be updated by recreating the whole table each time, so showing only all active alarms in any moment.

Fig. 69. TCO Suite’s Alarms & Settings “Active Alarms: Static Page”

This table can be presented into two ways: the first one shown when user chooses “Active Alarms” functionis 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 therequest 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 anautomatic refresh process (Fig. 70. below).

Fig. 70. TCO Suite’s Alarms & Settings “Active Alarms: Automatic Page”

This page will do a periodic automatic refresh of its content and anyway allows the user to get back to themanual refresh page.

WARNING: For auto–refreshed pages, a longer timeout is foreseen. This is set to 90 refresh cyclesof 10 seconds each, for a total of 15 minutes. After this timeout, the connection expirationpage is shown.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

166 / 592 3DB 16142 EAAA Ed.02


2–2.3.7 Power Measurement

This page (Fig. 71. below) allows user to read power measurement result.

” Refresh Interval” filed allow the operator to set the time duration of the measurement for automaticrefreshing. The choice is among 5,10,30 sec. Otherwise operator can click “refresh” button directly torefresh the result of power measurement.

Fig. 71. TCO Suite’s Alarms & Settings “Power Measurement”

2–2.3.8 Licence Info

This page allows user to read license so that he can retrieve data needed by Alcatel–Lucent to producea new Software License (Fig. 72. below).

Fig. 72. TCO Suite’s Alarms & Settings “Reading Software License”

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

167 / 5923DB 16142 EAAA Ed.02


2–2.3.9 Modem Speed

This function (Fig. 73. below) allows the authorized user for reading the current F–Interface speed valueand for modifying it through a simple combo box.

Fig. 73. TCO Suite’s Alarms & Settings “Changing F–Interface Speed”

In case of login by viewer profile, the button and combo–box elements are not shown and the page justdisplays the current modem speed.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

168 / 592 3DB 16142 EAAA Ed.02


2–2.3.10 NAT option

Fig. 74. TCO Suite’s Alarms & Settings “NAT option”

[1] NAT router

In the following the scenario, when the NAT router is used in the network, is analyzed, providing alist of warnings and the relevant countermeasures. The scenario is represented by a remotemanager that wants to access the radio network; in between one or more NAT router could bepresent. WTD suggests not using this device because of the consequences that are hereunderdescribed.

[2] What is the NAT router

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

Fig. 75. NAT router

The NAT function cannot by itself support all applications transparently and often must coexist withapplication level gateways (ALGs) for this reason. People looking to deploy NAT based solutionsneed 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 applicationunaware in that the translations are limited to IP/TCP/UDP/ICMP headers and ICMP error messagesonly. NAT devices do not change the payload of the packets, as payloads tend to be applicationspecific. 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

169 / 5923DB 16142 EAAA Ed.02


[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 and3 ) when end–to–end 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 nottranslate IP addresses within SNMP payloads. It is not uncommon for an SNMP specific ALG toreside on a NAT router to perform SNMP MIB translations proprietary to the private network, but forsure it is expensive and NAT device depending.

[4] How the WTD equipments SNMP based are impacted

1 ) About the Manager IP Address Access Control Security

This feature allows the control of the IP manager forbidding the access for any manager thatis not registered. For the 9400AWY family, the “ Start Supervision” operation/sequence iscompleted successful only if IP packets coming from the manager have the same IP sourceaddress than the one contained in the Registration table (retrieved by the SNMP message); thismeans, 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, consideringit as exceptional case.For example for both products can be enabled the “No registration” or “NAT presence” optionthat 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 beupdated to reflect the change in length of FTP control data portion: detailed explanation can befound on the RFC 2663.

Consequently some applications can be impacted as:– Software Download– Backup and Restore

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

170 / 592 3DB 16142 EAAA Ed.02


2–2.4 PC–NE physical connections

2–2.4.1 Physical interfaces for the NE management

See Fig. 76. below:

– the F interface (RS232 serial interface) is used for the connection with the PC configured as CraftTerminal. This connection can be:

• local (ECT function, as explained in para.1–2.4.1 on page 54), through the suitable RS232 cablesupplied with the equipment

• physically remote but logically local (ECT function, as above) through an ECT–equipmentconnection via the public switched telephone network, as explained in Appendix E on page 553

N.B. the F interface usage requires LLMAN installation [see choice b ) on page 311]

– as shown in Fig. 59. on page 154, the Ethernet interface can be used for the:

• local connection, through a cross–connect Ethernet cable, or through a HUB), to the PC:

– configured as Craft Terminal

– or running the TCO Suite directly from the SWP CD–ROM

• connection to the TCP/IP network (provided that the NE has a valid TCP/IP address).Notice that by means of this connection, the NE can be reached by:– the TMN OS (e.g. Alcatel–Lucent 1353NM)– the PC running the TCO Suite directly from the SWP CD–ROM

– by the Radio interface:

– the NE can be reached:

• from remote Craft Terminals (RECT function, explained in para.1–2.4.2 on page 54)

• or from the TMN OS or from the PC running the TCO Suite directly from the SWPCD–ROM, when the NE’s Ethernet interface is not connected (but the NE is definedin the Supervision Network)

– the local Craft Terminal, connected to the F interface or the local Ethernet interface, canreach other NEs by means of the RECT function

Ethernet Interface F Interface Radio Interface

Fig. 76. MAIN Unit front side: interfaces for equipment control

N.B. As delivered from Alcatel–Lucent Factory, the NE’s:– local IP address (associated to the F interface)– and Ethernet TCP/IP address (associated to the Ethernet interface)are both set at default value “10.0.1.2”.Obviously, these values can be maintained only until the NE remains disconnected from theTCP/IP network and from any other NE, and must be changed as soon as possible.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

171 / 5923DB 16142 EAAA Ed.02


2–2.4.2 Local connection of the Craft Terminal to the NE

The CT can be locally connected to the NE through the Serial Port or through the Ethernet Network Port.Only one connection can be active at a time.

Paragraphs 2–2.4.2.1 and 2–2.4.2.2 below describe how to switch from one to the other interface (thissetting is at PC side only).

N.B. This setting is necessary only in case you start the CT by Start ⇒ Alcatel 1320CT [see stepe )–2 ) on page 174].In case you start the CT clicking the button Operational & Maintenance of the TCO Suite MainMenu (see step e )–1 ) on page 174], you do not need to carry out this setting, because propersetting is automatically set–up answering the question of Fig. 77. on page 174.

2–2.4.2.1 Connection through the Serial Port

Remind that, to connect the CT to the NE through the Serial Port, the Alcatel Virtual Network Card forLower Layers Software has to be installed on the PC (refer to para. 5–3.3 on page 522).

N.B. If the IP Address configured for the Alcatel Virtual Card has been changed after the 1320CTPlatform installation, it is necessary to perform a re–customization by entering the followingcommand:

Start → Programs → Alcatel → SNMPCT–K–ADD–ON v3.x.x → SNMP Add–On Customization

N.B. If the connection through Ethernet Network Port has been activated, to activate again theconnection through the Serial Port enter the following command:

Start → Programs → Alcatel→ SNMPCT–K–ADD–ON v3.x.x → NE Connection → Serial Port

2–2.4.2.2 Connection through the Ethernet Network Port

1 ) Configure the Network Card on the CT as explained in the 1320CT Basic Craft TerminalOperator’s Handbook.

2 ) Enter the NE and enable the Ethernet port on the NE (refer to para. 2–3.2.3 on page 195).

3 ) Quit the NE and close the Network Element Synthesis application.

4 ) Activate the CT Connection through the Ethernet Port by the following command:

Start→Programs→Alcatel→SNMPCT–K–ADD–ON v3.x.x→NE Connection→Ethernet Port

N.B. If the IP Address configured on the Ethernet port has been changed, it is necessary to performa re–customization by entering the following commands:

Start → Programs → Alcatel → CT–K– v3.x.x → Customization

Start → Programs → Alcatel → SNMPCT–K–ADD–ON v3.x.x → NE Connection→Ethernet Port

Start → Programs → Alcatel → SNMPCT–K–ADD–ON v3.x.x → SNMP Add–On Customization

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

172 / 592 3DB 16142 EAAA Ed.02


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


– NE management states below– NE Login on page 173– NE Logoff or switch off on page 180– Closing the 1320CT application on page 180

2–2.5.1 NE management states

The elementary building blocks of any telecommunication network are called Network Elements (NEs).

The 9400AWY NE type is ULS.

When operating with the Craft Terminal or the TCO Suite, the NE can present different management statesaccording to the condition of the connection (supervision, local access, connection state, etc.). Alsogeneral Alarm states are presented.

Management states are present at the Network Element Synthesis view level and at the ULS view level.

All information relevant to the management states are described in the 1320CT Basic Craft TerminalOperator’s Handbook (see Tab. 78. on page 571).

The Network Element Synthesis views enable to get access to the views described in this section.

– NE supervision and login

The Network Element Synthesis view enables to work on local or remote NE ULS, selecting themand activating Supervision and Login, as described in para.2–2.5.2 on page 173.

– NE logoff and switch off

In order to logoff the NE, or before disconnecting the F interface cable, or before switching off theNE, close the NE JUSM window and stop the NE supervision as described in para.2–2.5.3 on page180.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

173 / 5923DB 16142 EAAA Ed.02


2–2.5.2 NE supervision and login

a ) Summary

To access and login a 9400AWY NE from you PC for the use of the Craft Terminal functionalities:

• the CT–NE connection can be:– physically and logically local, through the RS232 serial cable for its connection to the

equipment F interface– physically remote but logically local through an ECT–equipment connection via the public

switched telephone network, as explained in Appendix E on page 553– physically and logically local, through a cross–connect Ethernet cable for the local direct

connection between PC and NE Ethernet ports– physically local but logically remote, by a normal Ethernet cable through a LAN for the

connection between PC and NE Ethernet ports– physically and logically remote, by a connection between PC Ethernet port and the NE

through the RECT function or the TCP/IP network.

• you must have a UserName and password set

• in case of logically remote connection, you must know the NE’s TCP/IP address

b ) Cable and network connections (if not yet done)

1 ) Local connection between the PC and the NE

N.B. This operation has to be done whenever you have to access the NE locally; it is highlyrecommended when commissioning and maintenance tasks must be carried out.For other operations, consider that any NE reachable through the TCP/IP network[see point 3 ) below] can be accessed by the PC connected to the TCP/IP network[see point 2 ) below]

Following cautions stated in point e ) on page 36, through the suitable cable connect the ECTto the F interface or to the Ethernet interface of the MAIN unit (refer to Fig. 76. on page 170).

To activate on the CT the connection through the Serial Port or through the Ethernet Port referto para. 2–2.4.2 on page 171.

2 ) Connection of the PC to the TCP/IP network

N.B. Just from NE management point of view, this operation has to be done whenever:

– you have no local access to any NE;

– or, even though you have local access to a NE, other NEs (you want to accessin remote way) are not accessible from the local NE.

3 ) Connection of the NE to the TCP/IP network

N.B. Please take into account that this connection must not be done until the networkrouting data of the NE have been correctly defined. This definition is carried outduring the Configuration Procedure described in chapter 3–2 on page 329.

If, in the following, you want to access the NE through the TCP/IP network (provided that it hasalready inserted correctly inside it from both physical and logical points of view), you must knowthe NE’s TCP/IP address.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

174 / 592 3DB 16142 EAAA Ed.02


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

d ) Only in case of CT–NE connection via public switched telephone network:set up the connection on the public switched telephone network, as described in para.5–5.6 on page560

e ) Craft Terminal start–upThere are two ways to start the CT; they are not equivalent (note):

(note) in case no NE is locally connected to the PC, these modes are equivalent (no CT–NEconnection set–up)

1 ) Preferred mode to start the CT to login a NE: click the button Operational & Maintenanceof the TCO Suite Main Menu (see Fig. 55. and Fig. 56. on page 149). Refer to para.2–2.2.4.4on page 150 for possible additional details.Notice that this choice in independent from the setting (at PC side) of the CT–NE localconnection on the Serial or Ethernet interface (explained in para.2–2.4.2 on page 171). This isthe reason for preferring this simpler modality to start the CT to login a NE.– if LLMAN (Alcatel Lower Layers Manager) is available on user’s system, user is asked to

select between serial or Ethernet port connection by following screen:

Yes

Fig. 77. Choice of Serial or Ethernet interface for PC–NE physical connection

• in case of serial connection (YES answer), no other request is asked to user and1320CT platform is automatically started with the related Serial port connectioncustomization;

• in case of Ethernet connection (NO answer), no other request is asked to user and1320CT platform is automatically started with the related Ethernet port connectioncustomization;

– if LLMAN is not available on user’s system, the 1320CT will be run with the Ethernetconnection customization and the user will be asked the same “Direct”/”Remote” requestshown in Fig. 62. on page 156.

After a while, the “Network Element Synthesis” screen opens [step f ) on page 175].

2 ) Alternative (not preferred) mode: in Windows: Start ⇒ Alcatel 1320CTWith this modality, you must know in advance if the local connection of the Craft Terminal tothe NE is set (at PC side):– on the Serial interface– or on the Ethernet interfaceand consequently switch to one another, according to needs, as explained in para.2–2.4.2 onpage 171.

After a while, the “Network Element Synthesis” screen opens [step f ) on page 175].WARNING: In case you use the Serial interface and the “Network Element Synthesis” does

not open, read carefully para.2–2.2.7 on page 155 (Warning about interfacecustomization carried out by the Direct Connection)

N.B. Only in case of F–interface employment, for a correct operation, and only on some PCswith Windows 2000 or XP, it is necessary to start the Lower Layers Manager (Start →Programs → Alcatel → Lower Layers → Lower Layers Manager) before starting the ECTPlatform (Alcatel 1320CT).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

175 / 5923DB 16142 EAAA Ed.02


f ) Network Element Synthesis screen

There are two cases:

• the PC is locally connected to the NE; screen appears as follows:

Fig. 78. Network Element Synthesis screen (NE locally connected)

– the symbol indicates the NE–CT local connection by serial cable (F–interface). Such

symbol is not present if the connection has been established through the Ethernetinterface.

– the symbol “?” means they NE is not supervised.

Now:– if you have to operate on the NE locally connected, proceed to step h ) on page 177.– if you have to operate on a remote NE, proceed to step g ) on page 176.

• the PC is not locally connected to any NE; the screen (the first time you have launched 1320CTafter its installation) is as follows (empty map):

Fig. 79. Network Element Synthesis screen (empty map)

In this case you must create on this empty map the SNMP NE(s) you want to access, asdescribed in following step g ) .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

176 / 592 3DB 16142 EAAA Ed.02


g ) SNMP NE creation

N.B. This is a simplified description. For complete instructions, please refer to the 1320CTBasic Craft Terminal Operator’s Handbook, section “EML CONSTRUCTION”.

To create a SNMP NE in the Network Element Synthesis map:

• you must know the NE’s TCP/IP addresses. Note: the NE has always two addresses that canbe equal or different:– the “Local Configuration” address, see para.2–3.2.1 on page 192– the “Ethernet Configuration” address, see para.2–3.2.3 on page 195

• and you must be sure that the NE is reachable from your PC. To make this check, open theWindows Command Prompt application and execute the command:

ping <space> –t <space> TCP/IP_addressLeave this command run some minutes, verifying the connection is and remains establishedwithout interruptions, then close the command window.Note: in case the “Local Configuration” and “Ethernet Configuration” addresses are differentfrom each other, perform this check for both.

• then, proceed as shown in Fig. 80. below, inserting in (2) the NE’s own TCP/IP address.Note: in case the “Local Configuration” and “Ethernet Configuration” addresses are differentfrom each other, you must insert the “Local Configuration” address.

N.B. During the creation of the SNMP NE, if not set automatically, insert the number “161”in the TCP/IP Port field.

(1)

(2)

(3)

Fig. 80. SNMP NE creation in the Network Element Synthesis map

After such creation, the empty map of previous Fig. 79. becomes populated as in Fig. 81. below(the symbol “?” means the NE is not supervised).

Fig. 81. Network Element Synthesis screen after SNMP NE creation

• If necessary, create the other SNMP NEs you may need.

• At the end, save the map (Map ⇒ Save). In this way, when you start again 1320CT, you will findthe same NEs you have created in this phase.

• If you need to start supervision and, after, to login any NE present in the map, proceed to nextstep h )

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

177 / 5923DB 16142 EAAA Ed.02


h ) Start supervision on a selected Network Element

From a populated “Network Element Synthesis” map (e.g. Fig. 78. on page 175 and Fig. 81. above):

1 ) select the interested Network Element clicking once left mouse button on it;

2 ) while NE selected, with right mouse button choose Start Supervision and with left mousebutton execute it, clicking once (Fig. 82. below). In alternative, while NE selected, with leftmouse button choose Supervision ⇒ Start

Fig. 82. Start supervision

Wait until the symbol “?” becomes at first (under exploration) and then colored “•” (it

means “NE in supervised state” N.B.), as shown in Fig. 83. on page 177

N.B. In order to know the possible “color” meaning , refer to the:• 1320CT Basic Craft Terminal Rel.3.x Operator’s Handbook:

– chapter “SOFTWARE INSTALLATION”• paragraph “Craft Terminal Configuration”,

• sub–paragraph “Communication with NE”

Fig. 83. NE in supervised state

N.B. If you want to change the User Label of the NE (select it ⇒ Description ), take intoaccount that it must not include the following characters:\ ? : * “ < > | .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

178 / 592 3DB 16142 EAAA Ed.02


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

In this case, operate as follows:

• The JUSM must be closed.In the NE will appear a broken icon and a red bullet.

• Wait for the automatic restarting of the Supervision (at the end of the fading conditions).The icon in NE will become whole and the bullet will take the color relevant to the alarms (if any)active in the NE.

• If the Supervision does not start, close and open again the CT.

• If the Supervision does not start, switch off and switch on the PC.

WARNING: When the supervision of a NE has been started don’t click on the name of the map.This operation causes the lock of the CT and the CT must be closed and opened again.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

179 / 5923DB 16142 EAAA Ed.02


i ) Network Element login

From screen “Network Element Synthesis” with NE in supervised state (e.g. Fig. 83. on page 177):

1 ) select the interested Network Element (NE) clicking once right mouse button on it;

2 ) while NE selected, with right mouse button choose Show Equipment and with left mousebutton execute it, clicking once (Fig. 84. below). In alternative, while NE selected, with leftmouse button choose Supervision ⇒ Show Equipment

Fig. 84. Show Equipment

3 ) after a while, the Login screen appears (Fig. 85. below), that must be filled in with suitablevalues.

Fig. 85. Login screen

At first installation time, one default Administrator user is available only, with (lower case):

• UserName= initial• Password = initialingOtherwise, use the Login information the Administrator has assigned you.

WARNING: The change of the password of this Administrator user is strongly suggested, to be doneat the end of all commissioning phases. Further this initial user, the Administrator isallowed to create/delete users belonging to the predefined profiles.For the Administrator to make such operations, please refer to para. 2–3.6 on page 214.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

180 / 592 3DB 16142 EAAA Ed.02


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

and, after a while, the 9400AWY Main view opens (Fig. 87. on page 181)

After the 9400AWY Main view has opened, all the available menus are introduced in para.2–2.6 onpage 181.

2–2.5.3 NE Logoff or switch off

Before disconnecting the F interface cable or before switching off the NE:

– close the NE JUSM window (Fig. 87. on page 181) clicking

– then, in the Network Element Synthesis Window (Fig. 86. below), stop the NE supervision as follows:

• select NE with mouse left button

• holding it selected, select Stop supervision with mouse right button. In alternative, while NEselected, with left mouse button choose Supervision ⇒ Stop

Fig. 86. NE Stop Supervision

• NE will go to not supervised state.

2–2.5.4 Closing the 1320CT application

– Verify that all NEs in the Network Element Synthesis map are in not supervised state

– Now you can close the Network Element Synthesis Window (Fig. 86. below) clicking

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

181 / 5923DB 16142 EAAA Ed.02


2–2.6 9400AWY view organization

2–2.6.1 Introduction

The 9400AWY view (see Fig. 87. below for the 1+1 configuration) contains the following fields, whichprovide the operator with the information needed to manage the NE:– View title– View area see para.2–2.6.2 on page 182– Main tool bar see para.2–2.6.4 on page 183– Menu bar see para.2–2.7.1 on page 184– Severity alarm synthesis (N.B.)– Domain alarm synthesis (N.B.)– Management state control panel (N.B.)– Message/state area.

N.B. For the meaning of the icons in the Severity alarm synthesis, Domain alarm synthesis and theManagement state control panel refer to Alarm synthesis indication para.4–5.8.2.1 on page437.

The Menu bar , Main Tool bar and the View area contained in the same NE view permit to perform allconfiguration and supervision operations and the display of the specific selected item.The view organization is detailed in the 1320CT Basic Craft Terminal Operator Handbook to which referfor the description.

Domain alarm synthesis

Management state control panel

Viewarea

RESOURCETREE AREA

RESOURCE LIST AREA

RESOURCE DETAIL AREA

Severity alarm synthesis

Menu bar

View titleMain tool bar

Tab panel

Fig. 87. 9400AWY Main view organization

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

182 / 592 3DB 16142 EAAA Ed.02


2–2.6.2 View Area

The View Area manages all domains from which the user can start. It is organized into tabbed panel, e.g.many windows placed one upon another. Each window is selectable (placing it on top of the others) witha 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 tab–panel (e.g. functionalities area) consists of four areas:

– Resource–Tree Area: displays all the available resources of the Radio NE.– Resource–List Area: may be represented by: Tabular View (e.g., Line Interface Domain) or

Graphical View (e.g., Equipment Domain).• Tabular View: displays a tabular representation of the selected resource. As default, no tabular

element is shown.• Graphical View: displays a graphical representation of the selected resource. As default, no

tabular element is shown.– Resource–Detail Area: displays detailed information of a selected item in the Resource List area.

As a default, no entry view is displayed as a consequence of the default behavior of the ResourceList area.

2–2.6.2.1 Resource Tree Area and Selection Criteria

The “Resource Area” displays all the available resources in a tree structure like the protocol stackhierarchy.Each tree node consists of two symbols. The first symbol indicates the state of the structure e.g., if thesymbol is ”+” the tree can be expanded to a lower level. The tree structure can be collapsed if the symbolis “–“. Finally, if there is no symbol, the node represents a leaf. The second symbol is the graphicalrepresentation of the resource.The user must select the resource by clicking with the mouse to carry out an action that depends on thetype of click.Each resource listed above may be selected by using the mouse by a:– Single left click;– Double left click

Single left click:By a single left click the resource is highlighted. This selection causes the activation of theresource list area, e.g., every time the user selects a resource in the resource tree area thecorresponding 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 treestructure and activate the “Resource list area” displaying the same information describedabove. When the tree node is expanded a double click will collapse the tree node showing thesame information in the “Resource list area”.

2–2.6.2.2 Resource Detail Area

This area displays the detailed information of the selected object in the Resource list area. It also providesthe types of operations available

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

183 / 5923DB 16142 EAAA Ed.02


2–2.6.3 Button Policy

The possible buttons for selection are the following:

– Apply this button activates the “modify”, but it does not close the window.

– Cancel this button closes the window without modifying the parameters displayed in the window.

– OK this button activates the modify and closes the window

– Close this button closes the window

– Help this button provides the help management for the functions of the supporting window.

Critical configuration choices generate a warning message for user confirmation before to be activated.

2–2.6.4 Main tool bar

Besides navigation buttons, it contains some shortcut icons for specific tools or views (most of them areaccessible also through the Menu Bar).

previousscreen

not operative

nextscreen

Quick Configuration

Current Configuration view

Summary Block Diagram view

Fig. 88. Main tool bar

N.B. previous screen and next screen buttons are enabled according to the context.

Shortcuts available are:

– Quick Configuration: details in para.3–2.3.7 on page 343

– Summary Block Diagram view: details in para.2–11.5 on page 285

– Current Configuration view: details in para.2–11.6 on page 288

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

184 / 592 3DB 16142 EAAA Ed.02


2–2.7 Introduction to the CT menu options

This paragraph is organized as follows:– Menu organization below– Views menu introduction on page 185– Configuration menu introduction on page 186– Diagnosis menu introduction on page 186– Supervision menu introduction on page 187– SW Download menu introduction on page 187

2–2.7.1 Menu organization

The menu bar allows to perform configuration and supervision functions on the Network Element.

This paragraph lists all menu options and then provides more details on the respective contained entries.

For each of them the relevant operative function are briefly introduced and it is referred the paragraphswhere they are detailed or the introduction to the options of each menu inserted in next paragraphs of thischapter.

From Chapter 2–3 on page 189 details and operating information on all views are given.

In the menu bar, a number of permanent menu items are always displayed. Starting from the left, themenus are:

– Permanent Menus

• Views (first column). See para.2–2.7.2 on page 185

To navigate among the views and to set the TMN parameters.

• Configuration (second column). See para.2–2.7.3 on page 186

To set the general configuration of the NE and to show or modify some parameters(performance monitoring, OverHead parameters).

• Diagnosis (third column). See para.2–2.7.4 on page 186

To get information on the NE (alarms, performance monitoring, remote inventory).

• Supervision (fourth column). See para.2–2.7.5 on page 187

To set the supervision states (i.e. Craft Terminal enabling).

• SW Download (fifth column). See para. 2–2.7.6 on page 187

To manage the NE software (download, MIB management).

• Help (last column).

To activate the help on line.

The menu bar also comprises other menus, presented only when a specific option is selected.

– Other Menus

• Equipment

This menu is present only when the Equipment menu (selected in the View menu or in theEquipment tab panel) is active. It allows to go back to the supporting equipment of the displayedobject.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

185 / 5923DB 16142 EAAA Ed.02


2–2.7.2 Views menu introduction

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

– Previous: Goes back to the previous screen of the application.

– Open Object: Not active.

– Open in New Window: Not active.

– Duplicate View in New Window: Not active.

– Equipment: Opens the Equipment view.Then the “Equipment” menu is available on the menu bar.See Chapter 2–4 on page 219

– External Points: Displays and sets the input/output environmental alarm.See Chapter 2–7 on page 247

– Line Interface: Opens the Line Interface view to configure all the tributary ports.See Chapter 2–5 on page 227

– Performance: Allows to manage the Performance monitoring.See Chapter 2–12 on page 289

– Radio: Allows to manage all the functions relevant to the radio channels.See Chapter 2–6 on page 233

– Protection Scheme: Allows to manage the Protection schemes in 1+1 configuration.See Chapter 2–9 on page 257.

– Loopback: Allows to manage the loopbacks available with the equipment.See Chapter 2–10 on page 267

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

186 / 592 3DB 16142 EAAA Ed.02


2–2.7.3 Configuration menu introduction

This menu allows to set the general configuration of the NE and to show or modify some parameters, bymeans of the following entries:

– NE Time: Displays and set the NE local time.See para. 2–3.1 on page 190

– Network configuration: See para. 2–3.2 on page 191

– Alarm Severities: Manages the Alarm Severity Assignment Profile.See para. 2–3.3 on page 205

– System setting: Allows the system configuration, providing the setting of all the parametersfor the NE setup.See para. 2–3.4 on page 210

– Quick configuration: Allows a full system configuration through a guided procedure.See para. 2–3.5 on page 213

– Profiles management: Allows the CT user profile management.See para. 2–3.6 on page 214

– Log Switch: Inhibits/allows the event and alarm store in the LogSee para. 2–3.7 on page 218

2–2.7.4 Diagnosis menu introduction

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

– Alarms: Displays the equipment alarms.See para. 2–11.1 on page 278

– Log Browsing: Manages the alarms and events stored in the NE.See para. 2–11.2 on page 279

– Remote inventory: Displays the equipment Remote inventory information.See para. 2–11.3 on page 282

– Abnormalcondition list: Displays the manually operations active in the NE.

See para. 2–11.4 on page 284

– 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).See para. 2–11.5 on page 285

– Current configurationView: Displays the current configuration of the NE.

See para. 2–11.6 on page 288

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

187 / 5923DB 16142 EAAA Ed.02


2–2.7.5 Supervision menu introduction

This menu allows to set the supervision states of the NE, by means of the following entries (see chapter2–8 on page 251) :

– Access State: Manages the supervision access to the NE, via CT or OS.See para. 2–8.1 on page 251

– Restart NE: Reset of the NE software.See para. 2–8.2 on page 252

– MIB Management: Allows to perform backup and restore operations of the MIB.See para. 2–8.3 on page 253

– SW key: Displays the type of the key stored in the flash card.See para. 2–8.4 on page 256

2–2.7.6 SW Download menu introduction

This menu allows to manage the NE software, by means of the following entries (see chapter 2–13 on page297) :

– Server Access Configuration: Manages the configuration of the FTP server to be used for the software

download to the NE.See para. 2–13.1 on page 297

– Init SW download: Manages the software download to the NE.See para. 2–13.2 on page 298

– SW status: Shows and manages the status of the software packages installed in the NEmemory banks.See para. 2–13.3 on page 299

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

188 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

189 / 5923DB 16142 EAAA Ed.02


2–3 CONFIGURATION

This chapter describes the following Configuration menus:

– NE Time on page 190

– Network Configuration on page 191

• Local Configuration on page 192• NTP Configuration on page 193• Ethernet Configuration on page 195• IP Configuration on page 196

– IP static routing configuration on page 196– OSPF Area configuration on page 200– IP Address configuration of Point–To–Point Interfaces on page 202

• Routing information on page 204

– Alarm Severities on page 205

– System Settings on page 210

• NE Configuration on page 210• Link Identifier on page 212• Overhead on page 213

– Quick Configuration on page 213

– Profiles management on page 214

• Functional description on page 214• Change Password procedure on page 216• Users Management procedure on page 217

– Log Switch on page 218

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

190 / 592 3DB 16142 EAAA Ed.02


2–3.1 NE Time

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

From the Configuration pull down menu, select the NE Time option.

The following dialogue box opens, from which you can set the local NE time.

Fig. 89. NE Time dialogue box

The NE Time dialogue box displays the current NE time and the current OS time.

To re–align the NE time to the OS time, click on the Set NE Time With OS Time check box and click theApply pushbutton to validate.

The NTP status field is a read–only screen, which shows the configuration regarding the Network TimeProtocol performed in the menu Configuration –> Network Configuration –> NTP Configuration.

The Refresh pushbutton causes the refresh of the screen.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

191 / 5923DB 16142 EAAA Ed.02


2–3.2 Network Configuration

To get access the Network Configuration option select the Configuration pull down menu, as shownin the following figure.

Fig. 90. Network Configuration menu

The Network Configuration allows to perform the following operations:

Local Configuration: defines the local NE addresses

NTP Configuration: allows to enable/disable the Network Time Protocol

Ethernet Configuration: defines the configuration parameters necessary to managethe local NE providing a LAN Ethernet interface

IP Configuration which comprises:

IP static routing configuration: defines the Host/Network destination address for IP staticrouting

OSPF Area configuration: defines the Open Shortest Path First address

IP Address configuration ofPoint–To–Point Interfaces : defines the IP address of the interface which use the PPP

protocol

Routing information shows a summary of the information relevant to the routing which has been configured.

The options are described in next paragraphs.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

192 / 592 3DB 16142 EAAA Ed.02


2–3.2.1 Local Configuration

N.B. This function is equivalent to that of Quick Configuration Procedure’s Step G on page 361

WARNING: read carefully Rules for the definition of the NE’s Local IP and Ethernet IPaddresses on page 361

Select the Configuration pull down menu.

Select the Network Configuration option and then, from the cascading menu, the Local Configurationoption.

The dialogue box opens ( see Fig. 91. on page 192 ) which allows to configure the local IP address of theNE.

This local IP address is the IP address associated to the F interface and to the other interfaces which usethe PPP protocol (the 3 NMS channels).

Apply button is used to perform a configuration change of the data contained in the dialogue box andcloses it; the dialogue is visible until the end of the operations and a wait cursor is displayed.

Close button closes the dialogue.

Help button provides some useful information on the dialogue.

Fig. 91. Local Configuration dialogue box

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

193 / 5923DB 16142 EAAA Ed.02


2–3.2.2 NTP Configuration


By selecting NTP Configuration the dialog–box in Fig. 92. opens, which allows to enable the NetworkTime Protocol.

Fig. 92. NTP Configuration dialogue box

To enable the NTP put a tick in the check box of the Enabling NTP protocol field.

If the NTP has been enabled in the Main Server address field write the IP address of the Server, whichdistributes 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 thesame value of the Main Server.

To configure the setting click on Apply.

The Refresh pushbutton causes the refresh of the screen.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

194 / 592 3DB 16142 EAAA Ed.02


2–3.2.2.1 How to configure the NTP in a network

When the NTP is enabled, one of the NE must be MASTER and all the other NEs must be SLAVEs.An example is shown in Fig. 93.

NE1

NE2

NE3NE4

Fig. 93. Map

As example NE1 must be set as Master:

– disable the NTP protocol.

NE2 is set as Slave:

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





All the other NEs must be set as NE4.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

195 / 5923DB 16142 EAAA Ed.02


2–3.2.3 Ethernet Configuration


WARNING: read carefully Rules for the definition of the NE’s Local IP and Ethernet IPaddresses on page 361

Select the Configuration pull down menu.

Select the Network Configuration option and then, from the cascading menu, the EthernetConfiguration option.

The dialogue box in Fig. 94. on page 195 opens, which allows to define the parameters necessary toconfigure the Ethernet interface.

The following areas are present:

– IP Section which comprises:

• IP Address to be assigned to the N.E.• IP Mask relevant to the IP address• IP Routing Protocol default is “none” state. If “OSPF” choice is selected, the “Associated OSPF

Area “ must be set.WARNING: please do never use the RIP choice present in the IP Routing Protocol field!

• OSPF Area pointer: if in “IP Routing Protocol” the OSPF protocol has been selected, it ispossible to choose OSPF areas.

– Enable which comprises two selections to Enable or Disable the Ethernet interface.

Refresh button refresh the information written in the upper port.Apply button performs a configuration change of the data.Close button closes the dialog without changes of the data.

Fig. 94. Ethernet Configuration dialogue box

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

196 / 592 3DB 16142 EAAA Ed.02


2–3.2.4 IP Configuration

Select the Configuration pull down menu. Select the Network Configuration and then from thecascading menu, the IP Configuration option ( see Fig. 95. on page 196).

Fig. 95. IP configuration screen

2–3.2.4.1 IP static routing configuration

N.B. This function is equivalent to that of Quick Configuration Procedure’s Step I on page 364

The dialog–box opens ( see Fig. 96. on page 197 ) and allows to configure the parameters for IP StaticRouting Configuration.

The following fields and data are present:

[1] IP Address: allows to define the IP address necessary to reach a specific Host

[2] IP Mask: allows to define the IP Mask to reach a network

[3] Default Gateway IP Address: allows to define the address of the next hop gateway

[4] Interface type: allows to use point to point interfaces made available by the NE.

Apply button is used to perform a configuration change of the data contained in the complete table andclose 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

197 / 5923DB 16142 EAAA Ed.02


Fig. 96. IP static routing configuration screen

By pressing Create pushbutton the screen in Fig. 97. on page 198 opens.

In the Host or Network Address Choice field select:

– Host to address to a single IP address;

– Network to address to a range of IP addresses.

In the Default Gateway or Point to Point I/F Choice select:

– Default Gateway IP Address for the Ethernet interface;

– Point to Point Interface Index for the NMS channels (NMS–RF, NMS–V11, NMS–G703)

WARNING: No pending (open) static routes are allowed.The default software uses first the static routes and then the dynamic routes. An openstatic route is always considered as a preferential path.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

198 / 592 3DB 16142 EAAA Ed.02


Fig. 97. Create Static routing

If in the screen of Fig. 97. above the Default Gateway IP Address check box has been selected, writein the Default Gateway IP Address field below the relevant IP address.

If in screen in Fig. 97. above has been selected the Point To Point Interface Index check box, the screenin Fig. 98. on page 199 opens.

N.B. It is also possible to define a Default Gateway Routing (refer to para.2–3.2.4.2 on page 199 fordetails).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

199 / 5923DB 16142 EAAA Ed.02


Fig. 98. Point To Point Interface Choice

In this screen one of the 3 NMS channels (NMS–RF, NMS–V11, NMS–G703) can be selected.

2–3.2.4.2 Default Gateway Routing configuration

It is also possible to define a Default Gateway Routing. To do that, in the screen in Fig. 97. on page 198operate 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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

200 / 592 3DB 16142 EAAA Ed.02


2–3.2.4.3 OSPF Area configuration

N.B. This function is equivalent to that of Quick Configuration Procedure’s Step F on page 360

The dialog–box opens ( see Fig. 99. on page 200 ) and allows to configure the parameters for OSPF(Open Shortest Path First) Area Table Configuration.


– Id– OSPF Area IP Address– OSPF Area Stub

The fields give a synthetical information that includes all the addresses (specific to a NE and to a Network)in an Area.

The ”Id” identifier is used when configuring the PPP interface or the ETH/OS OSPF parameter.

Apply button is used to perform a configuration change of the data contained in the complete RAP tableand close the view; the view is visible until the end of the operations and a wait cursor is displayed.

New button is used to insert a new page.

Delete button is used to delete the selected page.

Close button closes the dialogue without changing of the data.

Fig. 99. OSPF Area configuration screen

WARNING: Area 0 is managed and created by default with Id = 0 and IP address = 0.0.0.0

WARNING: When the area is a Stub area, all interfaces inside the same Stub Area (NMS andEthernet) must be defined “Stub”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

201 / 5923DB 16142 EAAA Ed.02


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

N.B. 3 areas max. can be created.

Fig. 100. Create New OSPF Area

In the screen write the IP address, the IP mask and select the flag (True/False).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

202 / 592 3DB 16142 EAAA Ed.02


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

N.B. This function is equivalent to that of Quick Configuration Procedure’s Step I , point [4] onpage 364

The dialog–box opens ( see Fig. 101. below) and allows to Enable or Disable the three NMS channels,which use the PPP protocol.

Fig. 101. IP Address configuration of Point–To–Point Interfaces screen

If required, enable or disable RF, V11 or G703 NMS access then → Apply. Then, wait for the followingconfirmation window:

→ Click OK to close the window.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

203 / 5923DB 16142 EAAA Ed.02


In alternative to the “G703 NMS”, the “TMN in–frame E1” can be defined.

With this “TMN in–frame” feature, 9400AWY 2.1 equipment is able to introduce in one of the time slots (TS1–31) of the E1#1 tributary, a 64 kb/s signal as network management system (NMS or TMN) to transmitremotely this type of information along the E1#1 route; this selection is alternative to the local availabilityof TMN–G703 (the mutual exclusion is automatic).It is also necessary that the far–end E1#1 tributary is enabled and successfully provisioned.

To activate the “TMN in–frame” feature, in TMN G703 field (see Fig. 102. below) :

– set Mode to In–Frame E1

– define the required E1#1 Timeslot number (default is 1)

Fig. 102. IP Address and Timeslot configuration of Point–To–Point In–Frame E1 TMN

Apply button is used to perform a configuration change of the data contained in the dialog–box and closesit; 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

204 / 592 3DB 16142 EAAA Ed.02


2–3.2.5 Routing information

Select the Configuration pull down menu. Select the Network Configuration and then from thecascading menu, the Routing information option.

The dialog–box in Fig. 103. on page 204 opens.

Fig. 103. Routing information screen

This screen is a read–only screen and displays the routing parameters currently active on the NE.

The pushbutton Refresh allows to refresh the information shown in the screen.

The Close button closes the dialogue without changing of the data.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

205 / 5923DB 16142 EAAA Ed.02


2–3.3 Alarm Severities

By selecting the Alarm Severities option from the Configuration menu the screen in Fig. 104. on page206 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 rulesused to define the alarms severity:

• MAJOR: the alarm affects the service (it is service affecting);

• MINOR or WARNING (according to the impact of the alarm): the alarm doesn’t affects theservice (with the exception of HighBER alarm, which MINOR alarm severity is defined, even ifit is service affecting).

– Profile “No Remote Alarms”. This profile enables the emission of the primary alarms plus EW andLBER 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). Thisprofile 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 sameseverity 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 thehousekeeping alarms. In this case, in order to enhance the flexibility, a different severity isassigned to each alarm profile (WAR, MIN and MAJ).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

206 / 592 3DB 16142 EAAA Ed.02


Fig. 104. Alarm Severities Profile

In the screen of Fig. 104. on page 206 are available 2 buttons:

– Close: to close the screen.– Clone: to create a new Alarm Severity Profile. To create a clone refer to para. 2–3.3.1 on page 207.

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 ServiceAffecting situation and No Service Affecting situation.

Each alarm has its Service Affecting and No Service Affecting attribute, which can differ according to theAlarm 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

207 / 5923DB 16142 EAAA Ed.02


2–3.3.1 How to create a new Alarm Severity Profile

– Select in the screen of Fig. 104. on page 206 the Alarm Profile to be cloned.

– Click the Clone pushbutton.

– The screen of Fig. 105. on page 207 appears.

– Digit the name to be assigned to the new Alarm Profile and click on Apply.

Fig. 105. Name of a cloned alarm profile

– Select again the Alarm Severity option from the Configuration menu.

– Select the just created Alarm Profile (Link 1 in the example of Fig. 106. on page 207).

Fig. 106. Clone of an Alarm Severity Profile

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

208 / 592 3DB 16142 EAAA Ed.02


– 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 andselect a new severity (see Fig. 107. on page 208).

Fig. 107. Selection of a new severity in the Service Affecting field

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

209 / 5923DB 16142 EAAA Ed.02


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

Fig. 108. Selection of a new severity in the No Service Affecting field

– To save the changes in the Alarm Severity Profile click on Apply. (By clicking on Cancel you quit theAlarm Severity Profile screen without any change) (see Fig. 108. on page 209).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

210 / 592 3DB 16142 EAAA Ed.02


2–3.4 System Settings

This menu is used to change the configuration of a system already commissioned.WARNING: this menu must not be used for the first–time NE setup. Setting of all parameters for the

first–time NE setup must be done in the commissioning phase, as explained in Chapter3–2 – Line–Up and Commissioning from page 341

The main window provides tabbed–panels, one for each type of function to be managed:– NE configuration– Link Identifier– Overhead

WARNING: At the first configuration (i.e. with a flash card with an empty MIB) at the end of theconfiguration the “Restart NE” must be performed (refer to para. 2–8.2 on page 252).

WARNING: Should during this procedure to be selected a wrong type (i.e. PSU4860 instead ofPSU2460), to insert the correct type enter the System Settings menu → NE configurationtab panel; select the correct type; click on Apply and then restart the EC by entering menuSupervision and by activating command ”Restart NE”.

2–3.4.1 NE Configuration

The user can view and define the NE configuration by selecting the “NE Parameters” tabbed panel.The window displayed in Fig. 109. below will appear.The fields of this screen are practically equal to those of Quick Configuration Procedure’s Step Ascreen described on page 347. Please refer to it for details not given in this paragraph.

DO NOT USE THIS CHOICE !

Fig. 109. System Settings: NE configuration

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

211 / 5923DB 16142 EAAA Ed.02


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

The “Capacity” can be modified by selecting a different type according to Tab. 64. on page 348 and thenselecting the ”Apply” button to send the new value.

The “Tributary Port Configuration” area is in the lower part of the window. The “Impedance” field allowsthe operator to configure the impedance of the E1 tributary (unbalanced 75 ohm or balanced 120 ohm).The impedance value will be applied by clicking on the related ”Apply” button.

N.B. After a change in the “Type” or “Capacity” or “Modulation” field the explicit confirmation shownin Fig. 110. is requested.

Fig. 110. Confirmation message

N.B. Only one change can be performed in this screen.When the user confirms the change in the “Type” or “Capacity” or “Modulation” field all the otherfields are disabled. To perform another change close the screen and enter again.

N.B. After a change in the “Type” or “Capacity” or “Modulation” field (for the “Modulation” only forthe remote NE configuration) at the completion of the operation the CT forces the JUSM closingwith the following warning message:

Fig. 111. USM closing warning message

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

212 / 592 3DB 16142 EAAA Ed.02


2–3.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. 112. below will appear.The fields of this screen are practically equal to those of Quick Configuration Procedure’s Step Dscreen described on page 358. Please refer to it for details.If changed, the new parameter values will be sent to NE by clicking on the related “Apply” button.

Fig. 112. System Settings: NE configuration

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

213 / 5923DB 16142 EAAA Ed.02


2–3.4.3 Overhead

The ”Overhead” tabbed panel (Fig. 113. below) is present only if the Audio/User Service Channelsplug–in is configured and identifies the parameters for the management of the phone number (EOWfunction) and auxiliary channel interface:

– The fields ”Order Wire Configuration” and ”Type” in the ”Auxiliary Interface Configuration” areaof this screen are practically equal to those of Quick Configuration Procedure’s Step J screendescribed on page 366. Please refer to it for details.If changed, the new parameter values will be sent to NE by clicking on the related “Apply” button.

Fig. 113. Overhead Configuration

– The field Alarm Profile allows to associate to the Overhead alarms a particular Alarm Profile: adefault alarm profile or an Alarm Profile previously created by the Operator (refer to para. 2–3.3.1on page 207). To associate a different Alarm Profile click on the selection button and make theselection among the available Alarm Profiles.

N.B. the default associated Alarm Profile is the Primary Alarm profile.

2–3.5 Quick Configuration

This procedure allows a full system configuration through a guided process, based on a reduced set ofscreens. The related windows will be displayed by a “Wizard Tool” according to a specific order.For the procedure execution, please refer to para.3–2.3.6 on page 341.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

214 / 592 3DB 16142 EAAA Ed.02


2–3.6 Profiles management

2–3.6.1 Functional description

[1] Username and Password

An user is identified by a username and password with the following characteristics:

• Username length: the length must not be more than 20 characters.

• Password length: the length must not be less than six (6) characters under any circumstancesand must not be less than eight (8) characters for administrator user profile. Moreover thepassword length must not be more than 20 characters.

• Password composition: the password must be composed of full ASCII characters set(UPPER/lower case, numeric and special characters).

The CT provides User login procedures (with the Show Equipment action) with the usernamedisplayed on the screen and the clear–text password not displayed on the screen. After 3 numberof consecutive unsuccessful NE login attempts, the CT interface closes the login procedure. Toaccess to the NE, a new Show Equipment action must be performed.

Each user is associated to a predefined profile.

[2] User number

Twenty–five (25) users at most can be created.

[3] User predefined profiles

The list of supported features for each user profile is shown clicking on Appendix Craft TerminalAccess Control in the Users Management help screen of Fig. 117. on page 217.For each functionality on user profile: Full indicates that the related screen is visible both for SETand GET operation; Read Only indicates that the related screen is visible, but only for GEToperations (to see the MIB objects); Not Supported indicates that the related screen is not visible.

The predefined profile are:

• Administrator (both for OS interface and CT/MibBrowser interface)This Operator can do everything on the NE.This Operator can manage security features (to add/remove users or to change own passwordand of all users).

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

215 / 5923DB 16142 EAAA Ed.02


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

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

• viewer (both for OS interface and CT/MibBrowser interface)This Operator can only explore the NE.This Operator cannot add or remove users. This Operator can change own user password

All user predefined profiles can be connected to NE by a F interface (local serial interface) or by aremote interface.

[4] NE scratch behavior

At installation time (NE scratch), a default Administrator user is created with (lower case):• UserName= initial• Password = initialingThe change of the password of this Administrator user is strongly suggested.

Further this initial user, the Administrator is allowed to create/delete users belonging to thepredefined profiles. The manager is prohibited from creating a user with username that alreadyexists.The Administrator is allowed also to change user passwords (own or of all user by administrator).

[5] Reset NE behavior

All the security information sets (username/password/profile for each user) are stored on NEdatabase (MIB data base). After the NE reset, these information sets are not lost and are recreatedas before the NE reset.

Complete on–line information is available in the Users Management help screen of Fig. 117. on page217.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

216 / 592 3DB 16142 EAAA Ed.02


2–3.6.2 Change Password procedure

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

1 ) Configuration ⇒ Profiles Management ⇒ Change Password

Fig. 114. Profile Management options

2 ) Following screen appears; fill it with old and new passwords, taking into account passwordcharacteristics listed in point [1] on page 214. New password will be active at next login (afterhaving logged out).

1

2

3

4

Fig. 115. Changing Password screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

217 / 5923DB 16142 EAAA Ed.02


2–3.6.3 Users Management procedure

This procedure is available to users with the Administrator profile only.

1 ) Configuration ⇒ Profiles Management ⇒ Users Management (see Fig. 114. on page 216)

2 ) Following screen appears. Click on Help

Fig. 116. Users Management screen

3 ) Following screen appears. Click inside to explore matters and carry out the desired action.

Fig. 117. Users Management help screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

218 / 592 3DB 16142 EAAA Ed.02


2–3.7 Log Switch

This screen (Fig. 118. below) of the configuration menu sets the inhibition or allowing of the the event andalarm store in the Event Log and Alarm Log (for their browsing, refer to para.2–11.2 on page 279 ).

The Lock setting corresponds to the store inhibition state.

Fig. 118. Log Switch screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

219 / 5923DB 16142 EAAA Ed.02


2–4 EQUIPMENT

This chapter describes the types of functions offered to the user for Equipment Management.

The equipment domain deals with the management of the NE as a whole and its physical components(subrack, boards,..)

The main screen of the Equipment tab panel differs according to the configuration:

– Fig. 119. on page 220 for 1+0 configuration

– Fig. 120. on page 220 for 1+1 configuration.

In the Resource List Area is shown a graphical representation of the Equipment, which consists of oneIDU 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 Ethernetports, 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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

220 / 592 3DB 16142 EAAA Ed.02


Equipment Status

ODU Status

IDU Status

IDU

ODU

Fig. 119. 1+0 Equipment view

IDU/EXT Ch #1

ODUCh#1

IDU Status

Equipment Status

ODUStatus

IDU/MAIN Ch #0

ODUCh#0

Fig. 120. 1+1 Equipment view

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

221 / 5923DB 16142 EAAA Ed.02


2–4.1 IDU level

To enter the IDU level click on the IDU object in the Resource Tree Area or double click on the IDU imagein the Resource Detail Area.

2–4.1.1 1+0 configuration

The screen in Fig. 121. below will appear.

IDU

MAIN BOARDStatus

IDU Status

Fig. 121. 1+0 IDU view

One IDU is present:

– IDU channel#1: the Main IDU.

The IDU channel#1 includes the IDU/Main Ch#1 object, which includes according to the configuration typethe 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 32xE1configuration

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

222 / 592 3DB 16142 EAAA Ed.02


2–4.1.2 1+1 configuration

The screen in Fig. 122. below will appear for the Ch#1 and the screen in Fig. 123. below will appear forthe Ch#0.

IDU

MAIN BOARDStatus

IDU Status

Fig. 122. 1+1 IDU/MAIN Ch#1 view

IDU

EXTENSION BOARDStatus

IDU Status

Fig. 123. 1+1 IDU Ch#0 view

Two IDUs are present:

– IDU channel#1: the Main IDU– IDU channel#0: the Extension IDU

The IDU channel#1 includes the IDU/Main Ch#1 object which includes according to the configuration typethe following options:

– IDU/MAIN/DATA Ch#1 with the 4 Ethernet ports (this board receives the power supply from the MainIDU only).

– IDU/MAIN/16xE1 Ch#1 with the second group of 16xE1 tributaries to implement the 32xE1configuration

The IDU channel#0 includes the IDU/Ext Ch#0 object which includes according to the configuration typethe following options:

– IDU/EXT/16xE1 Ch#0 with the second group of 16xE1 tributaries to implement the 32xE1configuration

2–4.1.3 Board level

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

223 / 5923DB 16142 EAAA Ed.02


2–4.2 ODU level

To enter the ODU level click on the ODU object in the Resource Tree Area or double click on the ODUimage in the Resource Detail Area. The screen in Fig. 124. below will appear.

Fig. 124. ODU view

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

224 / 592 3DB 16142 EAAA Ed.02


2–4.3 Tab panels in the Resource Detail Area

2–4.3.1 Alarms

The Alarms tab panel provides the fault management, which checks the current state of alarms relatedto the selected object (Fig. 125. below).

Fig. 125. Alarm tab panel for a selected object

The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms arehighlighted. When the alarm disappears it is automatically cleared in the screen.

By putting a tick in the Include alarms from sub–nodes box the alarms currently active in the sub–nodesof 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

225 / 5923DB 16142 EAAA Ed.02


2–4.3.2 Configuration

The “User Label” field (Fig. 126. below) only display the label associated to the selected node in the tree.

The field Alarm Profile allows to associate to the object alarms a particular Alarm Profile: a default alarmprofile or an Alarm Profile previously created by the Operator (refer to para. 2–3.3.1 on page 207). Toassociate a different Alarm Profile click on the selection button and make the selection among the availableAlarm Profiles.


Fig. 126. Configuration tab panel for a selected object

2–4.3.3 Remote Inventory

The information about the unit can be read in the Remote Inventory panel in the Resource Detail Areaas the following window shows (Fig. 127. below):

Fig. 127. Remote Inventory tab panel for a selected object

For detailed information on Remote Inventory, refer to para.2–11.3.1 on page 282

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

226 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

227 / 5923DB 16142 EAAA Ed.02


2–5 LINE INTERFACE

This chapter describes the type of functions available for Line Interface Management.The Line Interface domain deals with the management of the aggregate frame and tributary ports (lineside).The Line Interface menu allows the user to manage the resources of the line interfaces: PDH tributary,NMS channel and Ethernet port, if has been configured.This domain view consists of the following areas (Fig. 128. below):

– Resource Tree Area: displays the tributary ports sorted by the channel number and the NMSinterfaces.

– 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 listarea. This area performs the available functions for involved resource.

Fig. 128. Line Interface View

In the Resource List Area is given the information related to the tributaries:– Interface Type (E1, Ethernet, NMS channels)– Port Number: the port for a given channel and type of port– Channel Number: the number of a channel– Rate/Modulation: the bit rate of the tributary– Signal Mode: the type of frame (Unframed/Framed/Disabled)

To configure a line interface select the interface in the Resource Tree Area and configure the Configurationtab panel in the Resource Detail Area.

N.B. In the Resource Tree Area below the Tributary PDH line are shown all the E1 tributariesaccording to the capacity selected in the System Setting menu (see para.2–3.4.1 on page 210)or in Quick Configuration Procedure’s Step A screen (described on page 347 ).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

228 / 592 3DB 16142 EAAA Ed.02


2–5.1 Tab panels in the Resource Detail Area

2–5.1.1 Alarm

The fault management checks the current state of alarms related to the selected tributary.

It is provided by the alarm panel like the one explained in para. 2–4.3.1 on page 224.

WARNING: The GFP alarm (alarm present in the Ethernet data interface) if active is shown not in thistab panel, but in the Alarm tab panel of the Radio menu.

2–5.1.2 Configuration

There are different tab panels according to the type of interface:

– PDH interface (para. 2–5.1.2.1 on page 228)– NMS interface (para. 2–5.1.2.2 on page 230)– Ethernet interface (para. 2–5.1.2.3 on page 231)

2–5.1.2.1 Tributaries PDH Configuration tab panel

2–5.1.2.1.1 ETSI Market

The window, shown in Fig. 129. below for E1 tributaries, performs all the available functions for a PDHtributary port.

Fig. 129. Line Interface View: E1 Tributary Port

In Fig. 129. above the following fields are read–only fields:

– Interface Type (E1)– Port Number: identifies the ports for a given channel and type of port– Channel Number

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

229 / 5923DB 16142 EAAA Ed.02


The fields, which can be changed, are:

– Signal Mode– Line RAI Insertion– Radio RAI Insertion– Alarm Profile

Signal Mode (for E1 tributary)

[1] Signal Mode

The possible values are:• Framed for the framed received signal• Unframed for the unframed received signal• Disabled

The current state can be modified selecting a different signal mode value and then click on the”Apply” button to send the new value to NE.

WARNING: In case of configuration with two Ethernet ports, some E1 ports must be disabled inorder to allow the transmission of the Ethernet data. Refer to Tab. 65. on page 350 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 defaultalarm profile or an Alarm Profile previously created by the Operator (refer to para. 2–3.3.1 on page207). To associate a different Alarm Profile click on the selection button and make the selectionamong the available Alarm Profile.

N.B. the default associated Alarm Profile is the No Alarm profile.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

230 / 592 3DB 16142 EAAA Ed.02


2–5.1.2.2 NMS interfaces Configuration tab panel

Fig. 130. Line Interface View: NMS interface

For the NMS channels (RF, V11 and G703) only the Alarm Profile can be associated.

The field Alarm Profile allows to associate to the interface alarms a particular Alarm Profile: a defaultalarm profile or an Alarm Profile previously created by the Operator in menu Configuration –> AlarmSeverities. To associate a different Alarm Profile click on the selection button and make the selectionamong the available Alarm Profile.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

231 / 5923DB 16142 EAAA Ed.02


2–5.1.2.3 Data Tributaries Configuration tab panel

N.B. For whole information on Ethernet port characteristics and management, refer to the AppendixD on page 547

The Data Tributaries Configuration tab panels described in following points [1] and [2] are available onlyif the Enhanced Ethernet plug–in is installed and has been defined by choice 16E1–GData in theConfiguration % System Settings screen of Fig. 109. on page 210

[1] Tab panels relevant to all Data Tributaries ports as a whole

QoS (Quality of Service) information and choices in Fig. 131. below is fully equal to that describedin Quick Configuration Procedure’s Step B – point [2] QoS configuration screen described onpage 352 . Please refer to it for details not given here.

Fig. 131. Line Interface View: Data Tributary Port QoS Configuration tab panel

Fig. 132. below shows Performance Monitoring counters of all Data Tributary Ports

Fig. 132. Line Interface View: Data Tributary Port PM counters

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

232 / 592 3DB 16142 EAAA Ed.02


[2] Tab panels relevant to each Data Tributary port

The windows shown in Fig. 133. below and performs all available functions for one of four selectableData tributary port.

Fig. 133. Line Interface View: individual Data Tributary Port Configuration tab panel

a ) Except the field Alarm Profile and the button Restart , information related to a data portConfiguration panel is practically equal to that described in Quick Configuration Procedure’s StepB – point [2] Ethernet GPort configuration screen described on page 351 . Please refer to it fordetails not given here.

b ) The field Alarm Profile allows to associate a particular Alarm Profile to the interface alarms: a defaultalarm profile or an Alarm Profile previously created by the Operator in menu Configuration –> AlarmSeverities. To associate a different Alarm Profile click on the selection button and make the selectionamong the available Alarm Profile.

c ) The Restart button allows forcing auto–negotiation to begin link re–negotiation.

If changed, to confirm the new configuration click on Apply.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

233 / 5923DB 16142 EAAA Ed.02


2–6 RADIO

The Radio domain view allows the user to manage the resources of the radio transmission channel.

A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports, radio portsetc).

This domain view consists of the following areas (Fig. 134. on page 233):

– Resource Tree Area: displays the radio ports sorted by channel number.

– Resource List Area: displays tabular information about the selected resource in tree area.

– Resource Detail Area: displays, through tabbed windows, the object’ s properties selected in thelist area. This area enables to execute the available functions for involved resource.

Fig. 134. Radio Domain View

The following tab panels are present in the Resource Detail Area:

– Alarms: show the active alarms (para. 2–6.1 on page 234 )– Configuration: configures some radio parameters (para. 2–6.2 on page 234 )– Frequency: sets the Radio Frequency (para. 2–6.3 on page 235 )– RTPC & ATPC: sets the manual operation parameters or the automatic operation parameters (para.

2–6.4 on page 238 )– Power Meas: performs the Tx and Rx power measurements (para. 2–6.5 on page 241 )– BER: performs the BER measurement (para. 2–6.6 on page 246 )

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

234 / 592 3DB 16142 EAAA Ed.02


2–6.1 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. 2–4.3.1 on page 224.

2–6.2 Configuration

The window shown in Fig. 135. below controls some functions for a Radio channel.To define the involved port, first select the port/channel in the tabular view: this selection enables the“Resource Detail list” to show the available functions for the single resource.

Fig. 135. Radio–Configuration menu

2–6.2.1 Local or Remote Transmitter Mute

The information related to the transmitter status is shown in the “Tx Mute” field. To change the transmitterstatus choose the desired value (ON for Tx Squelched and OFF for Tx not Squelched) and press therelated “Apply” button.

WARNING: The Tx Remote Mute automatically works (”on” and then “off”) only if performed on thelocal NE (i.e. the NE to which the CT is connected). When a remote Tx mute is executed,the EC changes the channel in mono–directional way, in order to have the possibility tosend the command to remove the mute. If the Network Element has been restarted aftera MUTE, there is no more possibility to set–up the channel, because the remote addressis not known, and, in any case, to set–up the channel a bidirectional communication isneeded. The only way to remove the MUTE command is with local CT or from a remoteCT which can reach the Network Element through another supervisory interface.

2–6.2.2 ODU service kit

This field is a read–only field, which displays the state (connected or not to the ODU) of the light servicekit cable (see para.3–2.10 on page 405 )

2–6.2.3 Alarm Profile

The field Alarm Profile allows to associate a particular Alarm Profile to the object alarms: a default alarmprofile or an Alarm Profile previously created by the Operator (refer to para. 2–3.3.1 on page 207). Toassociate a different Alarm Profile click on the selection button and select among the available AlarmProfile. This panel belongs to “TX Squelch” one.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

235 / 5923DB 16142 EAAA Ed.02


2–6.3 Frequency

The Frequency menu allows to read and, if necessary, to set the frequency parameters.

The system can operate with different types of ODU according to the RF band and to the channelarrangement. There are ODUs which can manage only one shifter (fixed shifter) or several predefinedshifters (flexible shifter). For details, according to ODU type employed, please refer to para.1–4.5 frompage 104 onwards.

Fig. 136. Radio Frequency Functions with Shifter and Rx Freq enabled

Fig. 137. Radio Frequency Functions with Rx Freq disabled

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

236 / 592 3DB 16142 EAAA Ed.02


Fig. 138. Radio Frequency Functions with shifter disabled

WARNING: Since frequency setting could impact on traffic and requires a lot of time, followingmessages are shown in sequence:

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

237 / 5923DB 16142 EAAA Ed.02


[1] ODU with one Shifter only

If the ODU can manage only one shifter the Shifter field in the menu is not available (it is grey).

In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written in theFrequency Range field on the right side) and press push–button Apply (the Rx frequency isautomatically calculated by using the inserted Tx frequency and the shifter).

Note: During the command setting the CT is frozen. Waiting time: max 30’.

[2] ODU with different available Shifters

In the Tx frequency field insert the suitable Tx frequency and press push–button Apply.

In the Shifter field select the suitable shifter and press push–button Apply (the Rx frequency isautomatically calculated by using the inserted Tx frequency and the shifter).

Now the Rx frequency can be changed in order to implement a suitable new shifter. Insert the newvalue in the Rx frequency field and press push–button Apply.

When the Rx frequency is changed a specific warning message about possible impact on the trafficwill 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 beencompleted (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 isdifferent from the shifter value, the background of the Shifter field changes to red color and thespecific warning message shown in figure below is written on the Frequency screen.

Fig. 139. Not standard frequency arrangement

To restore a ”Standard Shifter” configuration, the operator has only to apply again the selected (oranother 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 theShifter field and the specific warning message.

Note: During the command setting the CT is frozen. Waiting time: max 30’.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

238 / 592 3DB 16142 EAAA Ed.02


2–6.4 RTPC & ATPC

This menu (Fig. 140. below) allows to read and, if necessary, to set the Tx power parameters.

The shown information is related to the channel selected in the Resource Tabular View.

Static value of the Tx power

Dynamic value of the Tx power(20 dB range)

ATPC Rx Threshold

Fig. 140. RTPC & ATPC

WARNING: When you change the modulation scheme (from 4 QAM to 16 QAM or vice–versa) the Txpower (in case of operation with RTPC) and the ATPC range (in case of operation withATPC) of the new modulation scheme must be in the correct range. If the value is out ofrange the relevant field in the RTPC & ATPC screen appears empty (automatically isassociated a default value, but this value is not displayed).Fill the field with the suitable value.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

239 / 5923DB 16142 EAAA Ed.02


2–6.4.1 ATPC

The ATPC can be Enabled or Disabled.

The new value will be applied when the ”Apply” button is pressed. If the ATPC has been enabled, theATPC 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 Txside, is the information relevant to the channel (protecting or protected) currently activein the EPS protection scheme. The two transmitters are, therefore, driven by the sameATPC control signal.

[1] ATPC Range

The Min Value and Max Value, for Tx Range in the ATPC management, are shown in the AtpcRange 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 maximumvalue, you must at first change the maximum value, then change the minimum value(obviously setting it smaller than maximum).

When the Apply button is pressed the new values will be applied.

[2] ATPC Rx Threshold

The value of the power low threshold can be changed by writing the new value in the field.When the Apply button is pressed the new values will be applied.

WARNING: During the reconfiguration phase or during the activation of a new software, the alarm“ATPC loop” could be (but not necessarily is) active.

WARNING: It is recommended to use the following Tab. 56. in order to set the ATPC threshold.The ATPC shape is calculated using the max capacity.

Tab. 56. ATPC Range Rx Threshold for ETSI

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

4Min

Value–73 –74 –74 –72 –72 –71 –71 –70

4QAM Max Va-

lue–60 –60 –60 –60 –55 –50 –50 –50

16Min

Value–69 –70 –70 –68 –68 –67 –67 –66

16QAM Max Va-

lue–60 –60 –60 –60 –55 –50 –50 –50

The applied rule is:

Frequency BandATPC Rx threshold setting

Frequency BandMin Value Max Value

7/8, 13, 15 & 18 GHz PRxth + 8 dB –60 dBm

23 GHz PRxth + 8 dB –55 dBm

25 & 38 GHz PRxth + 8 dB –50 dBm

PRxth: Received power level correspondent to BER 10–6 according to modulation scheme,payload and ETSI standard

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

240 / 592 3DB 16142 EAAA Ed.02


2–6.4.2 RTPC

[1] Nominal Power

The Nominal Value field in the “RTPC” area is a read–only field and shows the nominal value of thetransmitted 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), whenthe 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 relatedApply 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 PowerValue label of RTPC area.

If the ATPC is enabled, the Tx power value cannot be modified.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

241 / 5923DB 16142 EAAA Ed.02


2–6.5 Power Measurement

The Power Measurements capability is performed through the “Power Meas” tabbed panel in the resourcedetail view (Fig. 141. below).

BER

Fig. 141. Power Measurements

The Measurement screen allows the operator to set initial parameters for the required measurement.

“Measurement interval” fields allow the operator to set the time–duration of the measurement. Thedefault is Days: 7, Hours: 0, Minutes: 0. A 7–day measurement interval is also the maximum allowedinterval.

“Sample time” field is the period between two consecutive measurement samples. The choice is among6, 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 theoperator. The file is stored in the ALCATEL/CT–Kv3.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 daysfor a 2 s sample time).

By clicking on the ”Start“ button the screen “ Power Measurement Graphic “ appears (see Fig. 141. onpage 241).

The Power Measurement Graphic is available only if the CT is connected to the NE.

The screen in Fig. 142. shows the Tx and Rx measurements related to the local NE.

Through this screen the operator can see, in real time, the power transmitted by the local and remotetransmitter (Tx) and the power received by the local and remote receiver (Rx).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

242 / 592 3DB 16142 EAAA Ed.02


The top graphic screen area shows the TX curves (local and remote), while the bottom area shows theRx curves (local and remote). Note that the colors represent the linked end–point of the two NE; forexample, 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. 142. Power Measurement Graphic

By clicking on “Show details” box, on the left side of the Power Measurement Graphic (see Fig. 142. onpage 242), a new table appears (Fig. 143. on page 243); this table shows the following relevant valuesof 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

243 / 5923DB 16142 EAAA Ed.02


– 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 – 33°C ÷ + 55°C on 0–20dB

RTPC range– PRx = Real Value with 3 dB accuracy from –41 dBm down to –69 dBm included (nominal

received levels)– PRx = Real Value with 4 dB accuracy from –30 dBm down to –40 dBm included and from

–70 dBm down to threshold included

Fig. 143. Power Meas Details

WARNING:– If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB Configuration the

transmitter is in standby).– If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field

the information in dBm is –99, probably the supervision has been lost. The confirmation of the lossof the supervision is given by a broken red icon in Network Element Synthesis screen.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

244 / 592 3DB 16142 EAAA Ed.02


2–6.5.1 How to read a Power Measurement file

Click on Read File field and press on the Select File button. The directory of the CT automatically opensto navigate and get the power measurement file.

N.B. as default, the measurement files are stored in the ALCATEL/CT–Kv3.x.x directory and haveextension .txt.

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

Select the desired file and click the Start button in Fig. 141. on page 241 to open the file.

Fig. 145. Example of “Power Measurement File Reading“

The button in the lower part of the window allow to flow the graph within the measurement interval.

Select the .txt file and click with the mouse right push–button to open .txt file with a text editor (e.g.WordPad) and to see the power information in tabular mode (see Fig. 146. on page 245).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

245 / 5923DB 16142 EAAA Ed.02


Fig. 146. Example of Power Measurement File Reading (with WordPad)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

246 / 592 3DB 16142 EAAA Ed.02


2–6.6 BER measure

This paragraph describes the non–intrusive BER function, by means of which it is possible to start/stopand read the BER measure (Fig. 147. below).

Fig. 147. BER Features

[1] Start and stop BER MeasureThe BER measure function can be started (“Start” button) or stopped (“Stop” button)

[2] Request BER Measure dataThe information of BER Measure is not automatically updated in the Measure part. If the user wantsto 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 calculationThe BER calculation formula is the following:

Pbit_out ≅ α . (CNT_ERR_1SEC/ ΔT)where:• Pbit_out is ’BER measurement’• α assumes the following values:

– α = 4.6E–07 (32E1)– α = 9.2E–07 (16E1)– α = 1.8E–06 (8E1)– α = 3.7E–06 (4E1)– α = 7.4E–06 (2E1)

• CNT_ERR_1SEC (’number of violations’) is the HW counter which accumulates the errors inthe 1 sec. window and after each reading, it resets itself and restarts (the software collects thecounter value each second and to count the ΔT period)

• ΔT (’elapsed time’) is the difference between the start time and the stop time of themeasurement.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

247 / 5923DB 16142 EAAA Ed.02


2–7 EXTERNAL POINTS

This chapter describes the types of functions offered to the user for External Points Management (pleaserefer to para.1–3.6.1 on page 85 for physical implementation).There are two types of external points: input and output external points.

By clicking on the tree root, displayed in Fig. 148. below, the tree will be expanded according to theequipment configuration.A single left click selection of a tree element causes the activation of the corresponding Tabularrepresentation displayed in the ”Resource list area”. A click on a row in the Resource list area opens theConfiguration menu in the Resource Detail Area. An example of this mechanism is displayed in theFig. 148. below.

2–7.1 Input External Points

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

– Id: identification number– UserLabel: associates a user–friendly name to an external point– Polarity: describes the polarity (Active Closed/ Active Opened)– External State: describes the state (on /off)– Alarm Profile: describes the associated Alarm Profile

The lower part provides the possible parameters, which can be modified; after a row selection, the usercan modify the User Label, the Polarity and can associate a different Alarm Profile by clicking on theSelection button.The operator choices will be sent to NE after selecting the “Apply” button.

Fig. 148. Input External Point View

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

248 / 592 3DB 16142 EAAA Ed.02


2–7.2 Output External Points

Seven output external points are available:

The first four external points (CPO#1, 2, 3, 4) (Fig. 149. below) are described by the followingparameters:

– Id: identification number

– UserLabel: a user–friendly name can be associated to an external point

– Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the externalpoint can be changed.

– Criteria: Manual or Automatic. The output can be activated manually by the CT by selecting Manual(Fig. 149. below) or automatically by selecting Automatic (Fig. 150. on page 249). In this case anew field appears (Event) in which it is possible to select the alarm, the generation of which will causethe activation of the external point output.

– External State: describes the state (on /off). In this field the external point can be activated (on) ordeactivated (off).

The operator choices will be sent to NE by clicking on the “Apply” button.

Fig. 149. Output External Points: CP01 ... CP04 (Manual activation)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

249 / 5923DB 16142 EAAA Ed.02


Fig. 150. Output External Points: CP01 ... CP04 (Automatic activation)

The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) (Fig. 151. on page 250)are described by the following parameters:

– Id: identification number

– UserLabel: a user–friendly name can be associated to an external point

– Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the externalpoint can be changed.

N.B. These three output external points are automatically activated when the relevant equipmentsummarizing alarm is active.

The operator choices will be sent to NE by clicking on the “Apply” button.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

250 / 592 3DB 16142 EAAA Ed.02


Fig. 151. Output External Points View: FAIL IDU, FAIL ODU

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

251 / 5923DB 16142 EAAA Ed.02


2–8 SUPERVISION

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

The NE can be managed by the OS or by the Craft Terminal. To control the competition of the OS and theCT, 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 modifythe 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 keysymbol has a rectangular shape.

If the LAC is ”requested”, it means that the CT has requested a permission from the OS and is waiting fora replay.

However, the OS does continue to provide a certain number of services. These services include:– Alarm reception and processing,– Performance processing,– Switching back to the OS access state.

The access state of an NE can be modified from two types of views:– switching from the OS to the Craft Terminal access state– switching from the Craft Terminal access state back to the OS access state

2–8.1.1 Switching from the OS to the Craft Terminal access state

Select the Supervision pull down menu. Then select the Requested option from the Access Statecascading menu as shown in the following figure.

Fig. 152. Configuration of the Craft access state from the Equipment NE view in the OS mode

From the confirmation dialogue box that opens, you can confirm or cancel the ”Craft access” operationusing the Yes or No pushbutton. The request is sent up to the OS which accepts or refuses it.If the OS doesn’t answer in a predefined time, it is assumed that the NE is in the Craft access stateand can be managed by a Craft Terminal.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

252 / 592 3DB 16142 EAAA Ed.02


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

Select the Supervision pull down menu. Then from the Access State cascading menu select the OSoption.From the confirmation dialogue box that opens, you can confirm or cancel the ”OS access” operation.The NE is now managed by the OS.

N.B. The key symbol icon on the management states of the NE view indicates whether the NE ismanaged 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 theNE. When the communication with the NE is lost, the OS automatically recovers thecommunication and forces the state existing before the loss of communication (therefore, CraftTerminal access can be denied or granted).

2–8.2 Restart NE

The RESTART operation is a software reset and can be executed in normal traffic conditions.

From the Supervision cascading menu, select the Restart NE option.

Fig. 153. Restart NE call

The following dialogue box opens.

Fig. 154. Restart NE confirmation

Click the OK button to confirm the restart N.E. operation

Click the Cancel button to abort the restart N.E. operation.

WARNING: After the activation of the Restart NE Command (or after the pressing of the HW resetpush–button) the LLM icon is frozen and the supervision of the local NE and the remoteNE is lost.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

253 / 5923DB 16142 EAAA Ed.02


2–8.3 MIB Management

This menu (Fig. 155. below) refers to the management of the MIB (Management Information Base). TheMIB includes all the system configuration data, except the routing configuration data:

1. Local configuration ⇒ System’s local address

2. NTP server configuration

3. Interface configuration ⇒ NMS configuration⇒ Ethernet configuration

4. IP configuration ⇒ IP Static Routing configuration⇒ OSPF Area configuration⇒ IP Address configuration of point to point configuration

Fig. 155. MIB Management

The routing configuration data are NOT stored into the MIB file, because considered unique to a particularsystem in a network and are NOT meant to be reproduced on other systems in the same network, becausewill cause conflicts in the supervision network centre.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

254 / 592 3DB 16142 EAAA Ed.02


2–8.3.1 Backup

This menu (Fig. 156. below) allows to save on the CT the NE configuration. To backup the configurationwrite the filename in the Backup field (Lower part) and press Confirm Backup.

WARNING: The backup file name must not include the following characters: space, &, /.

Fig. 156. Backup screen

Confirm the backup operation to start the operation.

In the upper part appears the list of the previously created backups.

By pressing Refresh the list is updated with the insertion of the just created backup.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

255 / 5923DB 16142 EAAA Ed.02


2–8.3.2 Restore

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

Fig. 157. Restore screen

Select one of the backups to be downloaded in the upper part and press Confirm Restore.

(By pressing the Reset push–button the previous selection is cancelled and a new selection can be made).

Confirm the restore operation to start the operation.

To activate the new configuration enter command MIB Management ––> Activate.

2–8.3.3 Activate

This command (Fig. 158. below) allows to activate the configuration just downloaded with the restore.

Fig. 158. Activate command

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

256 / 592 3DB 16142 EAAA Ed.02


2–8.3.4 Remove file

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

To remove a backup select the backup file in the upper part and press Confirm Remove.

Confirm the operation to start the operation.

By pressing Refresh the list of backups in the upper part of the screen is updated.

2–8.4 SW key

From the Supervision cascading menu, select the SW key option.

In this screen the type of the key (stored in the flash card installed in the Main IDU unit) is shown.

Fig. 159. SW key screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

257 / 5923DB 16142 EAAA Ed.02


2–9 PROTECTION SCHEMES

This domain is present in 1+1 configuration only.

This domain view consists of the following areas (Fig. 160. below):

– Resource Tree Area: displays the radio ports sorted by channel number.

– Resource List Area: displays tabular information about the selected resource in tree area.

– Resource Detail Area: displays, through tabbed windows, the properties done in list area. This areaenable to perform the available functions for involved resource.

By clicking on the tree root displayed in Fig. 160. below, the tree will be expanded according to protectionschemes supported.

Fig. 160. Protection Schemes

A single left click selection of an element tree causes the activation of the corresponding Graphicalrepresentation displayed in the “Resource list area”. An example of this mechanism is displayed in theFig. 161. on page 258 .

Three 1+1 protection schemes have been implemented:

– Mux/Demux protection: EPS protection in Tx and Rx sides– Radio protection: RPS Hitless Switch in Rx side– HSB protection: Hot Stand–by protection

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

– Mux/Demux Protection corresponds to the Switch Tx and the Rx output switch in Fig. 195. on page287

– the Radio protection corresponds to the Switch RPS HS in Fig. 195. on page 287

– the HSB protection is implemented in the ODU: one Transmitter is connected to the antenna (active),the other transmitter is in stand–by. Refer to Fig. 195. on page 287 . The HSB protection is availableonly if the HSB configuration has been selected.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

258 / 592 3DB 16142 EAAA Ed.02


2–9.1 Equipment Protection Management

The Equipment Protection Management is performed by selecting Mux/Demux Protection tree element.

The following window (Fig. 161. below) allows a complete view of all NE resource involved in the EPSprotection:

– Schema Parameters

– Channels Parameters

To read the correct indication on the switch status press here to refresh the screen

Fig. 161. Mux Protection

2–9.1.1 Schema Parameters

The window “Schema Parameters” displays the parameters that can be modified.

The Schema parameters are:

– Protection Type: this parameter is defined at creation time and it is read only. The supported typeis: 1+1, e.g. a working channel (Main) is protected by a protecting channel (Spare).

– Operation type: it defines if automatic restoration from protecting to protected channel is allowed(revertive mode) or inhibited (not revertive mode).In “Revertive” Operation, after an abnormal condition such fading, hardware problem or maintenanceaction, the relevant protection will automatically switch back to channel #1 as a default state.

The operator choice for “Operation Type” will be applied by clicking on “Apply” button.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

259 / 5923DB 16142 EAAA Ed.02


2–9.1.2 Commands

To enter the Commands menu, click, in the Tree view (Fig. 162. below), on the Spare #0 element or onthe Main #1 element

Fig. 162. Mux Protection Switch (example for Main #1 selected)

The operator can modify the state of the switch through commands Lockout, Forced and Manual.

Tab. 57. Command priority list

Command Priority

Lockout 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 inservice Channel 0, independently of the possible active alarms. This command activates signalingABN.

– Automatic Switch is the normal operation condition: the position of the switch depends on thecommands generated by the logic.

– Manual has the lowest priority: it is performed only if there are no alarms that can activate anautomatic switch. It cannot be performed if Lockout or Forced commands are already activated. Ifthis command is active, it will be removed by an incoming alarm. This command does not activatesignaling ABN.

Note : The “Forced” command for channel 1 is equivalent to the “Lockout “ command for the channel0. 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

260 / 592 3DB 16142 EAAA Ed.02


2–9.2 Radio Protection Management

The Radio Protection Management is performed by selecting the Radio Protection element tree.

The following window (Fig. 163. below) allows a complete view of all NE resource involved in a RPSprotection:– Schema Parameters– Channels Parameters

Protection Command Status NOT Automatically Updated


Fig. 163. Radio Protection View


The window “Schema Parameters” displays the parameters that can be modify.

The Schema Parameters are:

– ”Protection Type” field: defines the protection schema architecture: 1+1 Hitless;

– ”Operation Type” field: the possible values are revertive (automatic restoration allowed) ornotRevertive (automatic restoration Inhibited).In “Revertive” Operation, after an abnormal condition such fading, hardware problem or maintenanceaction, the relevant protection will automatically switch back to channel #1 as a default state.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

261 / 5923DB 16142 EAAA Ed.02


2–9.2.2 Commands


Fig. 164. 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.2–9.1.2 on page 259 ), RPS is switched on CH1,

and these commands are not available (greyed).


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 inservice Channel 0, independently of the possible active alarms. This command activates signalingABN.





All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

262 / 592 3DB 16142 EAAA Ed.02


2–9.3 HSB Transmission Protection Management

The Transmission Protection Management is performed selecting Transmission Protection element tree.

The following windows (Fig. 165. below) allows a complete view of all NE resource involved in a TPSprotection:

– Schema Parameters

– Channels Parameters


Fig. 165. Transmission Protection View


The window “Schema Parameters” displays the parameters that can be modify.

The Schema parameters are:

– Protection Type: this parameter is defined at creation time and it is read only. The supported typeare: 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).In “Revertive” Operation, after an abnormal condition such fading, hardware problem or maintenanceaction, the relevant protection will automatically switch back to channel #1 as a default state.

The operator choice for “Operation Type” will be applied clicking on “Apply” button.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

263 / 5923DB 16142 EAAA Ed.02


2–9.3.2 Commands


Protection Command Status NOT Automatically Updated

Fig. 166. HSB Tx Protection Commands (example for Main #1 selected)

The operator can modify the state of the switch through commands Lockout, Forced and Manual.


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 signalingABN.

– Forced has higher priority than the automatic operation: the activation of this command connectsto the antenna Transmitter 0, independently of the possible active alarms. This command activatessignaling ABN.





All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

264 / 592 3DB 16142 EAAA Ed.02


2–9.4 Rx Static Delay

Fig. 167. Rx Static Delay menu

The Rx Static Delay must be compensated during the commissioning. Two compensating modes arepossible:– Automatic– Manual

These two modes are alternative.

To activate the Automatic mode click on the Align push–button (the compensation procedure isautomatically done).

To activate the Manual mode:

[1] click on the Start push–button;

[2] write the values in the Channel 0/1 fields (N.B.);

[3] click on the Apply push–button to send the value to the NE.

N.B. Write in one field the suitable value (in range 0–31) and in the other field write 0.

At the end of automatic procedure, a warning message will be displayed to explain the result of procedure.For example, if procedure failed the following message is shown:

Fig. 168. Rx Static Delay panel – Warning message for fail

If procedure is correctly ended, a similar warning message will be displayed. When the manual procedureis started, the status of buttons change to allow the available procedure: Stop manual procedure Align ofvalues during manual procedure as shown in Fig. 169. . The automatic procedure is disabled duringmanual operation.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

265 / 5923DB 16142 EAAA Ed.02


Fig. 169. Rx Static Delay in auto mode

When the user stops the manual procedure by clicking on the Stop button, the status of the buttons willturn on the initial one.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

266 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

267 / 5923DB 16142 EAAA Ed.02


2–10 LOOPBACKS

The functions described in this section allow to perform the test operations by loopbacks.

2–10.1 Hardware implementation

The loopbacks can be performed at different levels:

– 2 near end and 1 far end loopbacks are embedded in the IDU

– 2 near end loopbacks are embedded in the ODU

Some loopbacks are declared local only; this means that, when the NE receives a loopback request, theNE executes the request only if it is arriving from the local ECT. This restriction has been introduced toavoid the risk of a permanent disconnection from the NMS of a remote NE.

2–10.1.1 IDU loopbacks

[1] Near end IDU cable loopback – internal – local only

FRAME MODEM IF –RF IF –RF MODEM

Near endODU

Near endIDU

Far endODU

Far endIDU

LIU FRAME LIU

RF

16E1/E3 16E1/E3

Fig. 170. Near end IDU cable loopback

[2] Far end IDU tributary loopback – internal

This loop can be activated separately on each tributary (example: in 16 E1 mode the i–th trib. canbe looped independently from the others).

Assuming that an ECT is connected to the station A, the NE A uses the dedicated link connectionto activate/deactivate this loop on the remote station B. In this way, from station A, it is possible toactivate/deactivate this loop without accessing the NE B through a RECT.

It is not forbidden (even if not considered here) to use a RECT from station B to activate this loop.


Near endODU

Near endIDU

Far endODU

Far endIDU

LIU FRAME LIU

Station A Station B

RF

16E1/E3 16E1/E3

Fig. 171. Far end IDU tributary loopback

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

268 / 592 3DB 16142 EAAA Ed.02


[3] Near end tributary loopback – line

It can be activated separately on each tributary (example: in 16 E1 mode the i–th trib. can be loopedindependently from the others).

It is not forbidden (even if not considered here) to use a RECT from station B to activate this loop.

FRAME MODEM IF–RF IF–RF MODEM

NearendODU

NearendIDU

Far endODU

Far endIDU

LIU FRAME LIU

Station A Station B

RF

16E1/E3 16E1/E3

Fig. 172. Near end tributary loopback

2–10.1.2 ODU loopbacks

[1] Near end ODU cable loopback – internal – local only


Near endODU

Near endIDU

Far endODU

Far endIDU

LIU FRAME LIU

RF

16E1/E3 16E1/E3

Fig. 173. Near end ODU cable loopback

It is executed by the NE only if it sent by the local ECT.

[2] Near end RF loopback – internal – local only (N.B.)

Taking into account the HW implementation of the RF loopback, it is not necessary to switch off theremote transmitter during a local RF loopback.


NearendODU

NearendIDU

Far endODU

Far endIDU

LIU FRAME LIU

RF

16E1/E3 16E1/E3

Fig. 174. Near end RF loopback


The RF loopback is executed by the NE only by the local ECT.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

269 / 5923DB 16142 EAAA Ed.02


2–10.2 Available Loopbacks

N.B. The loopbacks can be activated on the local NE only.

N.B. The DATA block in Fig. 175. is present with the Ethernet port option only.

DATA

TRIB

MUX/DEMUX

IDU

CT

ODU

MODEM RF MODEMRF

ODU

DATA

TRIB

MUX/DEMUX

IDU

1 2 4 5 6 3

Fig. 175. Available loopbacks

Tab. 60. Available loopbacksN.B. Refer to:

– Fig. 176. on page 270 (1+0 configurations)– Fig. 177. on page 271 (1+1 configurations)

No.Loopback

name

CT selection inthe Resource

Tree AreaLocation

Loopbacktype

Note

1E1

Port#xxTributaries Near End External line Input loopback at tributary level.

2E1

Port#xxTributaries Near End Internal

Loopback toward the remotestation at tributary level. Not available.

3E1

Port#xxTributaries Far End Internal

Loopback in the remote station attributary level.

4 IDU cable Channel 1 Near End External lineLoopback at the IDU output ataggregate level.

5ODUcable

Channel 1 Near End External lineLoopback at the ODU input ataggregate level.

6 RF Channel 1 Near End External lineRF local loopback.(N.B.)

WARNING: loopbacks on disabled tributaries are not applied (even if no messages are displayed whenthe command is sent)

N.B.– RF loopback is optional and provided only with specific configurations– Before activating the RF loopback, the Remote Tx must be muted (Menu Radio –>

Configuration)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

270 / 592 3DB 16142 EAAA Ed.02


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

Tributaries(External Line)

ODUCABLE

Radio port(RF loopback)

IDUCABLE

Channel(External Line)

1

2

5 6

4

Fig. 176. 1+0 Loopback types

– An active loopback is indicated by a yellow letter: L

– Switching status are displayed through different dynamic drawings:

If any indication does not correspond to the expected one, press “Refresh” to actualize the view.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

271 / 5923DB 16142 EAAA Ed.02


In Fig. 177. below is given the association of all the possible loopbacks in “1+1” configurations and theirpositions in the block diagram of the equipment provided by the Summary Block Diagram View option,available in the Diagnosis menu.

Tributaries(External Line)

Radio port(RF loopback)

IDUCABLE

Channel(External Line)

ODUCABLE

1

2

5 64

Fig. 177. 1+1 Loopback types




All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

272 / 592 3DB 16142 EAAA Ed.02


2–10.3 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 bynumber.

– Resource List Area: displays tabular information about the loopback supported by the resourceselected in tree area.

– Resource Detail Area: displays, through tabbed windows, the properties done in list area. This areaenables to perform the available functions for involved resource.In this area the following information is given:

Channel: the number of the channel (channel 1 only)

Type Interface: the type of interface in which a loopback can be performed.

Location: the station in which the loopback is performed (Near End/Far End)

Type: the type of the loopback (Internal/Internal IF/External Line)

Modality: the type of the loopback (Loop and Continue only)

Activation: the activation status of a loopback (Active/Not Active)

Clicking on tree root displayed in Fig. 178. below, the tree will be expanded according to NE configuration.

Fig. 178. Loop–back View for PDH Tributaries (1+0)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

273 / 5923DB 16142 EAAA Ed.02


Fig. 179. Loop–back View for PDH Tributaries (1+1)

Fig. 180. Loop–back View for Radio PDH

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

274 / 592 3DB 16142 EAAA Ed.02


Fig. 181. Loop–back CABLE

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

275 / 5923DB 16142 EAAA Ed.02


2–10.4 How to activate a loopback

WARNING: loopbacks on disabled tributaries are not applied (even if no messages are displayed whenthe command is sent)

N.B. For the loopbacks relevant to Ch. 0 and Ch.1 all the switches must be forced/lockout to therelated Channel; for the Tributaries loopbacks must only be forced to the radio switch to Channel0 or lockout to Channel 1.

To activate a loopback:

[1] Select the suitable loopback to be activated by clicking on the relevant object in the Resource TreeArea or by selecting the relevant row in the Resource List Area.

[2] The screen in Fig. 182. below will appear. (In this screen has been selected the loopback on tributaryE1, Near End).

Fig. 182. Loopback activation

[3] Select Active in the Activation field.

[4] Click on Apply.

[5] The Loopback is now ACTIVE (in the row in the Resource List Area the Activation field of the relevantloopback will change from Not Active to Active).

WARNING: when the Loopback commands start, the Craft Terminal is not “frozen”. Before to setanother command, it is recommended to wait 120 to 160 seconds minimum.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

276 / 592 3DB 16142 EAAA Ed.02


2–10.5 How to remove a loopback

To deactivate loopbacks use the following steps:

[1] Select the suitable loopback to be removed by clicking on the relevant object in the Resource TreeArea or by selecting the relevant row in the Resource List Area.

[2] The screen in Fig. 183. below will appear. (In this screen has been selected the loopback on tributaryE1, Near End).

Fig. 183. Loopback removing

[3] Select Not Active in the Activation field.

[4] Click on Apply.

[5] The Loopback is now DEACTIVATED (in the row in the Resource List Area the Activation field of therelevant loopback will change from Active to Not Active).

WARNING: When the Loopback commands start the Craft Terminal is not “frozen”. Before to setanother command is recommended to wait 10 to 25 seconds.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

277 / 5923DB 16142 EAAA Ed.02


2–11 DIAGNOSIS

This chapter describes the Diagnosis menus:

– Alarms on page 278

– Log Browsing on page 279

– Remote Inventory on page 282

– Abnormal Condition List on page 284

– Summary Block Diagram View on page 285

– Current Configuration view on page 288

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

278 / 592 3DB 16142 EAAA Ed.02


2–11.1 Alarms

This item menu allows navigation to the external tool: Alarm Surveillance.The Alarm Surveillance application is dedicated to receive, store, display and manage, in real time, thealarms raised by different sources (current alarms). This facilitates the overall alarm surveillance andimproves the reaction time of the network operators in case of anomalies in the network. It also providesthe possibility to archive and retrieve the alarms (historical alarms), allowing post–analysis of anomaliesin the network.Taking into account the number of alarms that are usually emitted in a network, the Alarm Surveillanceoffers the operator a systematic approach for the alarm visualization.

2–11.1.1 Counter Summary

This is a main window (Fig. 184. below) used to display statistics on alarms. It shows alarm counters,according to severity levels or statuses of the alarms (critical, major, minor, warning, indeterminate,cleared, acknowledged, incoming). In the counter summary, alarms may be grouped according to filteringcriteria in several sub–lists. For each sub–list, each of the counters may be shown or not.

Fig. 184. Alarm Counter Summary Window

2–11.1.2 Alarm Sub–list

The sub–list is a basic working window (Fig. 185. on page 279 ). It regroups alarms according to filteringcriteria defined by the operator, allowing work on a limited subset of alarms. The sub–list can also be sortedaccording to criteria defined by the operator. It makes the management of current alarms easier, andallows information classification before a possible export to a file or a printer.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

279 / 5923DB 16142 EAAA Ed.02


Fig. 185. Alarm Sub–list Window

For additional information, refer to the “AS Operator’s Handbook” (REF.[H] on page 571 of this manual).

N.B. The list of alarms displayed by AS (both current and historical) is not easy to read andunderstand, mainly due to the way in which units and functional entities are indicated in theFriendly Name.

2–11.2 Log Browsing

In the Diagnosis pull–down menu, select the Log Browsing option:

Fig. 186. Log Browsing Sub Menu

The proposed options are:

– select the Alarm Log option to access the Alarm Log file (N.B.)The Alarm Log windows opens, permitting to analyze all the alarms stored in the NE.See para.2–11.2.1 on page 280

– select the Event Log option to access the Event Log file (N.B.)The Event Log windows opens, permitting to analyze all the events stored in the NE.See para.2–11.2.1 on page 280

– select the Software Trace Log option: see para.2–11.2.2 on page 281

N.B. The event and alarm store in the Event Log and Alarm Log can be inhibited or allowed by theLog Switch function (see para.2–3.7 on page 218 )

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

280 / 592 3DB 16142 EAAA Ed.02


2–11.2.1 Alarm and Event Log

By selection of Alarm Log or Event Log item, the specific “Event Log Browsing Application” will bestarted. This application is integrated function of JEMLUSM Core.

This tool collects and shows the alarm log items (Fig. 187. below) and the event log items(Fig. 188. below). Selecting ‘”Set Filter” menu item of main menu bar, it is possible to define a filter thatcan be applied to search of item.

Fig. 187. Alarm Log Display

Fig. 188. Event Log Display

For additional information, refer to the “ELB Operator’s Handbook” (REF.[I] on page 571 of this manual).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

281 / 5923DB 16142 EAAA Ed.02


2–11.2.2 Software Trace Log

N.B. The use of the Software Trace Log option is reserved to the Alcatel–Lucent technicians.

Selecting the “Software Trace Log” custom item of menu displayed in the Fig. 186. on page 279 , theapplication will try to download the trace log file from NE, showing a temporary information box:

Fig. 189. Transfer Information Box

If successfully, the file content will be displayed in a new window (Fig. 190. below), from which it is possibleto save or print the file.

Fig. 190. SW Trace Log

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

282 / 592 3DB 16142 EAAA Ed.02


2–11.3 Remote Inventory

2–11.3.1 General

The Remote Inventory feature allows to store and retrieve the information useful to identify thecomponents of the product. It is also used to identify the actual equipment type and then, eventually, toprovide an equipment mismatch alarm, if the equipment type read from remote inventory data is differentfrom the equipment expected provided by the managers.

The Alcatel–Lucent factory labelling with an electronic inventory data of each replaceable hardware unitis provided according to the Alcatel–Lucent standard format:

Tab. 61. Remote Inventory Alcatel–Lucent standard format

Information field name Location Length (Byte) Encoding

Format identifier 0 2 ASCII ‘22’

Company identifier 1–2 4 ASCII

Mnemonic (see Tab. 62. below) 3–6 8 ASCII

CLEI code 7–11 10 ASCII

Unit Part Number + ICS 12–18 14 ASCII

Software/Firmware PN + ICS 19–25 14 ASCII

Factory identifier 26–27 4 ASCII

Serial Number 28–35 16 ASCII

Date Identifier 36 2 ASCII ‘00’

Date 37–39 6 ASCII

Customer field 40–62 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. 62. Remote Inventory mnemonic field

UNIT TYPE MNEMONIC

IDU Main Unit M4860–32

IDU Extension Unit E4860–32

4xGigabit Ethernet plug–in P4DATASW

PDH Tributary optional plugs–in P16E1DS1

Audio channels, Service Channel plug–in P–AC–SC

ODU unit ODU32–E

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

283 / 5923DB 16142 EAAA Ed.02


2–11.3.2 Remote Inventory display

Selecting the “Remote Inventory” item of Diagnosis menu, a summary screen will be displayed.

This screen is a read–only screen, which shows the remote inventory for all configured equipment.

If it is not possible to read the Remote Inventory information, a “Card Fail” alarm is declared.

Fig. 191. Remote Inventory screen (example)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

284 / 592 3DB 16142 EAAA Ed.02


2–11.4 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. 192. Abnormal Condition List screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

285 / 5923DB 16142 EAAA Ed.02


2–11.5 Summary Block Diagram View

The “Summary Block Diagram View” of the Diagnosis menu displays a global logical view (strictlyrelated to the physical implementation) highlighting a synthesis of all the alarms and statuses present inthe system (ODU+IDU). It can also run by the Summary Block Diagram view shortcut of the Main toolbar (see Fig. 88. on page 183).

This window also shows a logical view of the signal flowing through the functional block and switches.

Line (and arrow) trace changes in compliance with the current switch status. By clicking on the objectsof the drawing shown in the figure the operator can navigate to the specific view to perform maintenanceoperation (for example specific alarm details, equipment details, manual switches, loopback (L),performance monitoring (P).

The Summary Block Diagram View depends on the configuration.

– 1+0 with or without the Ethernet ports

– 1+1 HSB with or without the Ethernet ports

– 1+1 FD with or without the Ethernet ports

Some examples are shown in Fig. 193. to Fig. 196. on pages 286 to 287

In detail, it is possible to:

– navigate from Alarm indicator to related “Alarm Synthesis”;

– navigate from External Point indicator to “External Point” view;

– navigate from Switch indicator to related “Protection Scheme” view;

– navigate from Loopback indicator to specific “Loopback” view; for example, by clicking on (L)indicator of main board (Ch#1) the operator can navigate to loopback view for PDH tributaries;

– navigate from Performance indicator to specific “Performance” view; for example, by clicking on(P) indicator (line side) the operator can navigate to “Current Data” view;

– navigate from ODU box to the ”radio view” with automatic selection of the related channel.

By pressing the Refresh button the refresh of the screen takes place (active loopback and performanceand 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

286 / 592 3DB 16142 EAAA Ed.02


Fig. 193. Summary Block Diagram View example: 1+0 16E1 without Ethernet ports

Fig. 194. Summary Block Diagram View example: 1+1 HSB 16E1 with Ethernet ports

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

287 / 5923DB 16142 EAAA Ed.02


Fig. 195. Summary Block Diagram View example: 1+1 HSB 16E1–ETH with Audio/User ServiceChannel Plug–In (Lockout)

Fig. 196. Summary Block Diagram View example: 1+1 FD 32E1 with Audio/User Service ChannelPlug–In

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

288 / 592 3DB 16142 EAAA Ed.02


2–11.6 Current Configuration view

This screen is a read–only screen, which shows the current configuration of the NE.

Clicking on the Current Configuration view icon of the Main tool bar (see Fig. 88. on page 183) orselecting Current Configuration view from the Diagnosis menu, the following read–only screen isopened:

Fig. 197. Current Configuration view screen

By File ⇒ Save As, screen content can be saved as text file

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

289 / 5923DB 16142 EAAA Ed.02


2–12 PERFORMANCE MONITORING

This chapter describes the functions to provide Performance Monitoring management. It explains theprocedures that the operator must perform in order to activate a PM process.

2–12.1 General information on the performance monitoring process

The performance monitoring (PM) gives indication on the quality of the service.

Quality of service PM is performed in accordance with G.826 and G.784.

It is assumed that the quality of the single tributary (E1, …) can be derived from the quality of the aggregatesignal, 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.

MODEMRF

MODEMRF

FECDECODE

PROPR.FRAMING

PROPR.FRAMING

FECENCODE

Radio Hop (before the switch)

Radio Link (after the switch)

Fig. 198. Radio sections

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

290 / 592 3DB 16142 EAAA Ed.02


2–12.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. 199. below):

– Resource Tree Area: displays the threshold for measurement and the object monitoring sorted bychannel number.

– Resource List Area: displays the PM management for the selected resource in the tree area.

Fig. 199. Performance View

The performance reports can be of 2 different types:

– 15 minutes– 24 hours

N.B. The 15 min Performance Monitoring data are stored in the History Data report only if errorshave been occurred.The 24 h Performance Monitoring data are always stored in the History Data report.

Considering one section (see Fig. 198. on page 289), one current register is for 15 min report and one for24 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 ITU–T G.826 a second is declared Severely Errored Second if it is a second periodwith 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 15min. 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 logcan be seen.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

291 / 5923DB 16142 EAAA Ed.02


With reference to Fig. 200. below, to see (and configure) the current report:

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

[2] click on the desired granularity (15 m or 24 h)

[3] click on CD (Current Data).

With reference to Fig. 200. on page 291 to see an history log:

[1] click on HOP channel (0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or clickon 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 inthe Resource Tree Area in Fig. 200.

Fig. 200. Threshold table association screen

In the Counter Thresholds field select the threshold to be associated and click on Apply.

To associate an Alarm Profile click on the selection box. The Alarm Severity profile screen opens. Selectone of the Profiles available. Click on Apply. Click on Apply on the 15min&24h Tab panel.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

292 / 592 3DB 16142 EAAA Ed.02


2–12.3 CD (Current Data)

The window displayed in Fig. 201. below allows to start and to read the 15min PM report and 24h PMreport.

Fig. 201. Current Data View

2–12.3.1 CD parameters

The fields displayed in the upper part of Fig. 201. on page 292 allow the operator to check and managethe parameter of the current data collection.

– “Suspect interval” shows whether the current data are suspect or not.

– “Elapsed Time” field (read–only) displays the elapsed time in the current interval of monitoring.

– “End Period”: display time of the PM in the graphical description and in the tabular description inthe 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 Historybecause they don’t have errors.

– “Num. Interval supp.”: number of intervals (reports) suppressed in the History because they don’thave errors.

N.B. An interval is defined as “suspect“ if at least one of the following conditions occurs in thecollection 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

293 / 5923DB 16142 EAAA Ed.02


2–12.3.2 CD Counters

The fields and buttons displayed in the lower part of Fig. 201. on page 292 (Counters Area) allow themanagement 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. 201. on page 292, there are button choice to perform action on the current datacollection:

– “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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

294 / 592 3DB 16142 EAAA Ed.02


2–12.4 HD (History Data)

The PM process monitors the parameters during a specified interval (i.e. 15min) and stores their valuesin history data. A History Data collection is created automatically at the end of each time interval of CurrentData and deleted when the relative CD is deleted.

2–12.4.1 HD Parameters

The table displayed on the following window (Fig. 202. below) collects the history data for a related PMreport.

Fig. 202. History Data

The table columns hold the value of following parameters:

– End Period: End period of the relevant report

– Elapsed time: elapsed time in the related interval

– Suspect interval: this field describes whether the History Data is suspect or not.

– Counters: the last columns hold the counters value (BBE, ES, SES, UAS).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

295 / 5923DB 16142 EAAA Ed.02


2–12.5 Threshold tables

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

There are threshold tables for the HOP and for the LINK.

There are two default tables: threshold 1 and 2.

To view the available threshold for PM process, the operator must select the Thresholds Tables nodetree in the Resource Tree Area of the Performance View.

N.B. For the association of the threshold tables to the PM refer to para. 2–12.5.3 “Threshold tableassociation”.

2–12.5.1 How to change a threshold table

Fig. 203. Threshold table

Click on the threshold in the Resource Tree Area in the Resource List Area: the threshold screen willappear.

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, theoperator must edit the new values in the table fields and click on the Apply button.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

296 / 592 3DB 16142 EAAA Ed.02


2–12.5.2 How to create a threshold table

Fig. 204. Thresholds Table creation

Click on Threshold Tables HOP (or LINK) node tree in the Resource Tree Area of the Performance view.The Threshold Data Creation screen will appear.

In the upper part write the name of the new table.

In the lower part write the values for the Low and High thresholds.

To create the new table click on Create.

2–12.5.3 Threshold table association

To each PM can be associated a Threshold Table.

To associate a Threshold Table click on HOP–Channel#0 (or Channel#1) or on LINK in the ResourceTree 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. Selectone of the Profiles available. Click on Apply. Click on Apply on the 15min&24h Tab panel.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

297 / 5923DB 16142 EAAA Ed.02


2–13 SW DOWNLOAD

2–13.1 Server Access Configuration This menu allows to configure the FTP server to be used to download the SWP to the NE.

N.B. The complete procedure to download the SWP to the NE is described in Chapter 4–8 – SWPdownload toward NE on page 485.

Fig. 205. Server access configuration screen

User Id and Password are the login information to access the FTP server.

In the Address field write the IP address of the FTP server.

In the Port field write the port to be used and in the Root Directory field write the directory into which thesoftware has been downloaded.

By clicking on the Use System Default button a screen will appear showing the default configuration.

The CT is the default FTP server with the following parameters:

– User Id: ftp– Password: ftp– Address: IP address of the F interface or IP address of the Ethernet interface, if present.– Port: 15,000

N.B. the System Default can be changed by writing different values in the fields and then by clickingon button OK.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

298 / 592 3DB 16142 EAAA Ed.02


2–13.2 Init SW Download

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

To start download select the desired software version and click on the Init download button.

N.B. This screen displays the software packages previously stored through the menu Supervision–> Files Administration –> Software Administration available in the NES menu.

The Forced check box can be used to force download (i.e. the complete description file is downloadedto the NE).

If the Forced download is not selected, the system shall first proceed to compare the software to bedownloaded with the software present in the NE. Then only the differences are downloaded.

Fig. 206. Init Software Download screen

Recommended operation: Before to start the software download it is recommended to disable theATPC operation (if it has been enabled) and to set in RTPC mode the max. Tx power.

When the SW download starts a screen, showing the in progress operation of the download, appears.Download is aborted when the Abort button is pressed.

WARNING: The download time from the CT to the NE flash is 25–30 min. approx.At 50% of this time starts the download to the first ODU, which lasts 15–20 min. approx.At the end of this time interval starts the download of the second ODU, if present, whichlasts 15–20 min.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

299 / 5923DB 16142 EAAA Ed.02


2–13.3 SW Status

This menu allows to display the information of the software installed in the NE.

The following information is displayed:

– Name: software name

– Version: software version

– Operational state: enabled or disabled

– Current status: committed or standby. The committed status refers to the software currently in use.

By clicking on the Software Units Status button the screen of Fig. 207. below opens, giving additionalinformation on the software package.

Fig. 207. SW Status screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

300 / 592 3DB 16142 EAAA Ed.02


The following information is displayed on the screen:

– EC: software on the Equipment Controller

– OC_R: software on the ODU Controller (Radio) (The total download time of the ODU software is 17to 20 min approx. with some SES after 15 seconds from the activation) (Note 1)

– the other labels give the FPGA firmware version (Note 1)

Note 1: during the download of the ODU and FPGA software arises the alarm “Firmware Download OnGoing”. This alarm disappears when the download is over. The download lasts 2 minutes forevery FPGA starting from the activation of the alarm.

Fig. 208. SW Unit Status screen

The Flash card, which stores the NE software, contains 2 banks.

The 2 banks can store 2 different software versions. One bank will be committed (active) and the otherbank will be standby.

N.B. The second bank will appear when a new software package has been downloaded the first time.

During download, necessary to update the software version, the download file is automatically stored inthe standby bank.

To activate the new version first check the operational status of the standby bank. If the status is enabled(this means that download took place without errors) select Activation or Forced Activation in theSoftware Management Action field and click on the Apply Action button.

By selecting Forced Activation the bank to be activated is forced to restart.

By selecting Activation the bank to be activated restarts only if the content of the two banks differ.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

301 / 5923DB 16142 EAAA Ed.02


2–14 MIB MANAGEMENT


This function allows the backup and/or restore of the MIB and is carried out at two levels:

– the first is available at NE logged–in level, and allows operations depicted in Fig. 209. below:

MIB

NE XXX Flash Card

ECT

NE XXX MIB back–up file

NE AAA MIB back–up file

NE ZZZ MIB back–up file

MIB BackUp

MIB

NE XXX Flash Card

ECT



NE ZZZ MIB back–up file

MIB Restore

MIB delete

Fig. 209. Allowed MIB management tasks at “NE logged–in” level

From operative point of view, this management is described in para.2–8.3 on page 253.

– the second is available at “Network Element Synthesis level” (independently of whether or not theNE is logged in), and allows operations shown in Fig. 210. below (it depicts save/load usingfloppy–disk, but the operation can be done through any available read/write computer resource):

ECT



NE ZZZ MIB back–up fileSave todisk

ECT



NE ZZZ MIB back–up fileLoad from

disk

Fig. 210. Allowed MIB management tasks at “Network Element Synthesis” level

From operative point of view, this management and whole applicative examples are described in thefollowing paragraphs.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

302 / 592 3DB 16142 EAAA Ed.02


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

2–14.2.1 MIB back–up on ECT

This operation, carried out by ECT with the NE logged–in, allows to save the MIB from NE to ECT (seeMIB back–up in 2–8.3.1 on page 254).

2–14.2.2 MIB save to disk

This operation, carried out by ECT through the Network Element Synthesis screen, allows to save MIBfrom ECT to a floppy disk.

N.B. This example depicts the “Save to disk” by using the floppy–disk, but the operation can be donethrough any available read/write computer resource.

1 ) Launch the task as follows:

Fig. 211. Launch of MIB save to disk

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

1

2

Fig. 212. MIB save to disk – phase 1

3 ) The following screen appears:– a table showing the MIBs stored in the PC directory is shown

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

303 / 5923DB 16142 EAAA Ed.02


– select the MIB you want to save (3)– click on OK (4)– the usual window to choose a save target directory appears (5); select it and start the save– at save end, a confirmation message is shown (6) indicating also the name of the saved

folder; see N.B. on next page.

3

4

5

6

Fig. 213. MIB save to disk – phase 2

N.B. The saved MIB folder name acronym does not correspond to the name of the MIB that you haveselected to be saved. In order to know such a correspondence open the saved folder: in the“userlbl.txt” you can find such name.

Fig. 214. Correspondence between MIB saved folder and MIB saved name

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

304 / 592 3DB 16142 EAAA Ed.02


2–14.2.3 MIB load from disk

This operation, carried out by ECT through the Network Element Synthesis screen, allows to load a MIBpreviously saved on a floppy disk into ECT’s MIB area.

N.B. This example depicts the “Load from disk” by using the floppy–disk, but the operation can bedone through any available read/write computer resource.

1 ) Launch the task as follows:

Fig. 215. Launch of MIB load from disk

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

305 / 5923DB 16142 EAAA Ed.02


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

1

2

3

4

5

6

Fig. 216. MIB load from disk – phase 1

3 ) ... procedure continues

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

306 / 592 3DB 16142 EAAA Ed.02


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

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

N.B. the MIB name corresponds to that you had previously saved.

7

8

9

10

Fig. 217. MIB load from disk – phase 2

2–14.2.4 MIB restore from ECT

This operation, carried out by ECT with the NE logged–in, allows to restore the MIB from ECT to NE (seeMIB restore in para. 2–8.3.2 on page 255).

a ) END OF SECTION

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

307 / 5923DB 16142 EAAA Ed.02

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1INSTALLATION AND COMMISSIONING

SECTION 3: INSTALLATION AND COMMISSIONING

This section provides the whole operative instructions for the equipment HW and SW installation andcommissioning.

Please read para.1–2.6.1 on page 59 for an introduction to the procedures ofthis section.


Chapter 3–1 – SWP installation in PC environmentThis chapter details all phases necessary to install for the first time the SWP thismanual refers to, in the PC environment.

309

Chapter 3–2 – Line–Up and CommissioningThis chapter details all phases necessary for the equipment line–up andcommissioning.

329

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

308 / 592 3DB 16142 EAAA Ed.02

USER MANUAL9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1INSTALLATION AND COMMISSIONING

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

309 / 5923DB 16142 EAAA Ed.02


3–1 SWP INSTALLATION IN PC ENVIRONMENT

This chapter details all phases necessary to install for the first time the SWP this manual refers to, in thePC environment.

N.B. Before starting this installation procedure, it is suggested to give a look to para.1–2.6 on page58.

N.B. Procedures described in this chapter are carried out with the PC disconnected from the NE.


3–1.1.1 PC characteristics

For this SWP version, correct ECT installation requires a PC with the requirements hereafterdescribed:

1 ) HW Configuration

– CPU: Pentium III 850 MHz– RAM: 512 Mbytes– Hard Disk space: 4 Gbytes– Display Resolution: 1024x768 pixel– CD–ROM Drive: 24X– Primary Interface: Serial Port RS–232–C 9.6 to 57.6 Kbits/sec.– Communication Interfaces:

• Ethernet Card 10/100 Mbits/sec is mandatory, if local / remote communication withNE’s Ethernet port or TCP/IP network is required (if both connections are requiredcontemporarily, two Ethernet Cards are needed)

• RS232 serial port is mandatory, if local communication with NE’s ECT serial port(F–interface) is required.N.B. In alternative, for the usage of the NE’s F–interface with any PC having no

RS232 serial port (but obviously with USB ports available) it is possible toemploy the “USB TO RS232 ADAPTER” , ordering it to Alcatel–Lucent(P/N 1AF11294AA**).

2 ) Windows Versions

– Windows 2000 till SP4

– Windows XP (Professional Edition only) till SP2: It is mandatory de–activate the Firewallinstalled.

– Windows NT partially supported: CT–K 3.3 and related Q3/SNMP add–on deliveries canbe run on Windows NT but you have to take in account some restrictions in Almap PC 6.5and PC 7.0 components. They must be considered as Craft Terminal platform restrictionsin Windows NT environment.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

310 / 592 3DB 16142 EAAA Ed.02


3 ) Additional SW requirements

– Java Runtime Environment (JRE) version 1.4.2–12 or higher (the necessary version isincluded in the SWP CD–ROM)

– Browser:• System default browser that correctly supports XHTML 1.1 and CSS 2.1 standards:

– Microsoft Internet Explorer 5.5 or higher– Mozilla Firefox 1.5 or higher– Netscape Communicator 6 or higherN.B. Opera browser is not supported in any version.

• It is mandatory to manually disable system and browser proxy configurations priorto use both TCO Suite ”Set–Up Tool” and ”Alarms & Settings” (web server) functions;otherwise, the IP connection from the PC’s web server to the NE cannot take place.

• Used browser window should be at least as larger as 1024x768

– In user’s Windows system desktop folder, files with the following names must not bepresent:• Default_211.qcml• QCML_211.xsd• QCML_211.xsl

– Through system’s Display Properties, ‘Settings’ tab, clicking on ‘Advanced’ button, theDisplay – ‘DPI setting’ should be set to ‘Normal Size (96 DPI)’;

3–1.1.2 Operator skills and privileges

a ) The operator shall be familiar with the use of personal computers in WINDOWS–NT / WINDOWS2000 / WINDOWS XP (Professional Edition only) environment, internally to which the NetworkElement’s application software operates.

b ) Furthermore, for a number of configuration applications, the operator shall be aware of somespecifications of the International Standard Organization (ISO) and of the standards applied to thePlesiochronous Digital Hierarchy (PDH) (ITU–T Recommendations).

c ) For the installation of SW packages, the Operator’s PC privilege and skill must be those of “SystemAdministrator”.

d ) The Operator shall be familiar with the use of Alcatel 1320CT functionalities. If necessary, a goodapproach to the related matters is to read and understand the following sections of the 1320CT BasicCraft Terminal Operator’s Handbook (see Tab. 78. on page 571 ):

• section INTRODUCTION• section GETTING STARTED

3–1.2 Reference Information Model

Make reference to the Product Release Note (see para.5–7.2.2 on page 571 )

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

311 / 5923DB 16142 EAAA Ed.02


3–1.3 Choice of the procedure and summary of SWP installation phases

The procedure and main phases to carry out depend on the ECT environment you want achieve:

a ) Only SNMP management of 9400AWY V2.1.1 through Ethernet interface (by CT and TCO Suite).

In this case you must carry out the following main phases:

1 ) 1320CT Package Installation (installation of SWP components from the SWP CD–ROM):para.3–1.5 on page 314

2 ) Local copy in PC environment of the TCO Suite:para.3–1.6 on page 318

3 ) End of SW installation from SWP CD–ROM:para.3–1.7 on page 320

4 ) NE software downloading preparation:para.3–1.8 on page 321

5 ) CT initial configuration:para.3–1.9 on page 326

6 ) EML construction:para.3–1.10 on page 327

b ) Only SNMP management of 9400AWY V2.1.1 through Ethernet interface (by CT and TCO Suite),as point a ) above, with the additional possibility of management through the NE’s ECT serial port(by CT)

In this case you must carry out the procedure described in Appendix C – Additional SW installationoperations for NE management through the NE’s ECT serial port on page 517

c ) Management of SNMP 9400AWY V2.1.1 [as case a ) or b ) above] and of other SWPs for differentNEs (e.g. Alcatel–Lucent 9600USY, 9600LSY)In this case, before doing anything, read carefully para.3–1.4 on page 312

N.B. Chapter 4–10 on page 497 describes how to to de–install the Software Package from the PC.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

312 / 592 3DB 16142 EAAA Ed.02


3–1.4 Preliminary: installation of different SWPs in the same PC

If you like to install different Alcatel–Lucent SWPs (1320CT–based) in the same PC, you must be awarethat there are some SW components to be installed which are common to such SWPs.

The basic principle is that, due the ascendant compatibility, for such common components you must takeand install, from each SWP, the highest version components, e.g.:– Java Run Time Environment : highest version– Lower Layers Manager : highest version– Craft Terminal Base Platform [Craft Terminal Base Platform Q3 Add–On (EML–IM)] : highest version– Craft Terminal Base Platform SNMP Add–On (EML–IM) : highest version– Craft Terminal Base Platform Help On–Line Add–On : highest version– Craft Terminal NE Type & Release Configuration Add–On: highest version

Just as an example, Fig. 218. on page 313 shows the SW components and points out the common SWcomponents of:– SWP 9600LSY V2.0.4– SWP 9400AWY R.2.1 V2.1.1 (which this handbook refers to)(screens are those appearing after the SWP installation start–up, as in step 5 ) on page 316).

N.B. as far as the SWP 9400AWY R.2.1 V2.1.1 is concerned, JRE and Alcatel Lower LayersManager do not appear in the SWP CD–ROM start–up screen because:– JRE is automatically installed, if necessary, according to rules explained in para.2–2.2.3

on page 148;– Alcatel Lower Layers Manager is installed, if necessary, on Operator explicit request only,

as explained in para.5–3.2 on page 519.

To make the comparison between the versions of the common SW components, please refer to theProduct Release Notes (see para.5–7.2.2 on page 571 ) associated to the SWPs you want to install.In term of method to install:– use CT installation Product Guided and select component depending of the rule before;– install at first the SWP with the common SW components highest versions, and after the other SWPs

leaving unselected the common SW components already installed.Please extend these considerations to the need of installing more than two different SWPs.

Procedure example (referred to the two SWP cited above):

1 ) compare the PC characteristics and verify that your PC meets the highest requirements (as faras the SWP 9400AWY R.2.1 V2.1.1 is concerned, refer to para.3–1.1.1 on pages 309–310

2 ) uninstall all Alcatel–Lucent products (the “clean” situation simplifies the following operations)3 ) carry out the installation of LLMAN from the SWP 9400AWY R.2.1 V2.1.1 CD–ROM as

described in para.5–3.2 on page 519, because its version is higher than that of the SWP9600LSY V2.0.4

4 ) install the SWP 9400AWY R.2.1 V2.1.1 , as described in para.3–1.5 on page 314, selecting allcomponents, because its common SW components have versions higher than those of theSWP 9600LSY V2.0.4

5 ) complete the SWP 9400AWY R.2.1 V2.1.1 installation as described in steps 2 ) to 6 ) of pointa ) on page 311

6 ) using the CT installation Product Guided, start the installation of the SWP 9600LSY V2.0.4,de–selecting (see following Fig. 218. ) the components JRE V1.3 , Alcatel Lower LayersManager V3.4.0 , CT–K v3.2.0 and HOLCT–K–ADD–ON v1.1.0, because already installed(with higher versions) by the SWP 9400AWY R.2.1 V2.1.1 installation

7 ) complete the SWP 9600LSY V2.0.4 installation as described in relevant documentation.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

313 / 5923DB 16142 EAAA Ed.02


commoncomponents

Fig. 218. Common components of different SWPs (example)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

314 / 592 3DB 16142 EAAA Ed.02


3–1.5 1320CT Package Installation (installation of SWP components from theSWP CD–ROM)

N.B. Please read carefully para.3–1.3 on page 311, for the position of this step inside the wholeinstallation procedure.

N.B. Procedures described in the following are carried out with the PC disconnected from the NE.

3–1.5.1 Important warnings

N.B. Windows versions supported are just those listed in point 2 ) on page 309 (e.g. Windows XPHome Edition, Windows 95, 98, ME, etc. are not supported).

N.B. System browser versions supported are just those listed in point 3 ) on page 310 (other versions

are not supported).

N.B. Warning about Windows XP till SP2 – Professional Edition:It is mandatory to de–activate the Firewall installed.

N.B. Windows NT is partially supported: CT–K 3.3 and related Q3/SNMP add–on deliveries can berun on Windows NT with some restrictions.

N.B. These operations must be performed by the Administrator of the PC.

WARNING: During the installation an ALCATEL directory is automatically created, if not alreadypresent.If ALCATEL directory is already present on the PC, for a correct operation of the FTPserver, this directory must have all upper case characters (i.e. “ALCATEL”).

N.B. Note for Users having previously used SWP 9400AWY versions up to V2.0.3:This behavior takes place from V2.0.4: the 1320CT installation of this SWP does not includeanymore the Q3CT–K–Add–On component.In particular, if LLMAN component is not installed because you want to manage AWY NEs onlyby Ethernet interface, also Q3CT–K–Add–On component has not to be installed (or has to beexplicitly de–installed if previously installed) in order to have a correct behavior on 1320CTusage.Obviously, as also applied to previous SW releases, it is mandatory to install LLMAN componentin order to be able to manage AWY NEs by Serial F interface and in this case Q3CT–K–Add–Oncomponent can be installed to enable the possibility to manage also Q3 NEs with the same1320CT installation.

N.B. Notes for Users having previously used any SWP 9400AWY previous versions:When installing this SWP on a PC where are already installed the previous:– SWP 2.0.3, 2.0.4 or 2.1.x versions, it is mandatory select all the components in the

installation procedure– any 1.0.x and 2.0.x versions, it is not necessary to de–install them from PC.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

315 / 5923DB 16142 EAAA Ed.02


3–1.5.2 Operations sequence

Step 1. Initial checks

1 ) Verify that the PC characteristics meet all HW and SW requirements specified in para.3–1.1.1on page 309

2 ) Verify you do have the SWP CD–ROM P/N REF.[a] in Tab. 53. (page 141)

3 ) WARNING : whenever you have already installed a previous–version SWP V2.1.1 including theTCO Suite, delete the existing shortcut to the Start_html icon as well as the TCOSuite folder(see Fig. 227. on page 320). Note: it is not necessary to delete shortcut to the Start_html iconrelevant to previous SWP V2.0.x.

Step 2. Installation start–up

1 ) Insert the SWP CD–ROM in the PC’s CD–ROM unit

2 ) The TCO Suite start–up begins. Please refer to para.2–2.2.3 for the procedure execution andthe management of special conditions that could occur

3 ) At the end of the TCO Suite start–up, the CD–ROM TCO Suite Main Menu screen appears(Fig. 219. below); click on Advanced Settings button

Fig. 219. CD–ROM TCO Suite Main Menu screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

316 / 592 3DB 16142 EAAA Ed.02


4 ) After a while, the CD–ROM TCO Suite Advanced Settings screen appears (Fig. 220. ); click on1320CT Package Installation button

Fig. 220. CD–ROM TCO Suite Advanced Settings screen

5 ) After a while, the SWP component selection screen appears (Fig. 221. ); leave all componentsselected (or click on Select All button), then click on Next button

Fig. 221. SWP component selection screen and installation start

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

317 / 5923DB 16142 EAAA Ed.02


6 ) The installation process begins. After its completion (time depends on PC performance), thefollowing screen appears; clicking on confirmation button (YES / SÌ), the installation report isproduced

Fig. 222. SWP component installation end, and installation report

N.B. At any time, you can also check the components installed (Fig. 223. ) carrying out,in Windows environment:

Start ⇒ Settings ⇒ Control Panel ⇒ Add/Remove Programs

Fig. 223. Check of installed Alcatel SWP components

3–1.5.3 Next step

You have now completed the installation of the SWP components. Leave the:– SWP CD–ROM in the PC’s CD–ROM unit,– and the CD–ROM TCO Suite Advanced Settings screen open,and proceed with the Local copy in PC environment of the TCO Suite, para.3–1.6 on page 318.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

318 / 592 3DB 16142 EAAA Ed.02


3–1.6 Local copy in PC environment of the TCO Suite

N.B. Please read carefully para.3–1.3 on page 311, for the position of this step inside the wholeinstallation procedure.

This step is mandatory to have all TCO Suite functionalities (with exception of those related to the SWPinstallation in PC environment) available from the PC after the extraction of the SWP CD–ROM from thePC’s CD–ROM unit.


1 ) In the CD–ROM TCO Suite Advanced Settings screen (Fig. 220. on page 316) click on LocalCopy of TCO Suite button

2 ) Fig. 224. below: user is asked to choose the location where save must be done; such a locationcould be on the local PC or on a USB “Key”, Flash Memory Card, etc. Confirm or change it, andproceed

N.B. As an example, Fig. 224. below shows the:– TCOSuite.206 folder, that was created installing the SWP 9400AWY R.2.0.4– TCOSuite.217 folder, that was created installing the SWP 9400AWY R.2.1.0It is not necessary to delete them, because the Local Copy of TCO Suite from thisSWP 9400AWY R.2.1 V2.1.1 CD–ROM will create another folder (see Fig. 227. onpage 320).WARNING: If you delete them, you will loose the TCO functionalities associatedrespectively to the SWP 9400AWY R.2.0.4 and SWP 9400AWY R.2.1.0

Fig. 224. Local Copy of TCO Suite location choice

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

319 / 5923DB 16142 EAAA Ed.02


3 ) Where the user selects to put the TCO Suite, will be created a “TCOSuite” directory with thecontent of the same TCO Suite located on CD–ROM. The copy will proceed with a clear showof the progress (Fig. 225. below).

Fig. 225. Local Copy of TCO Suite progress and end

N.B. The user can also cancel the copy operation and all the files copied will be removed(Fig. 226. below).

Fig. 226. Copy cancelled

4 ) Since Java is not system–specific, neither shortcut to local TCO Suite Start.html page, norMicrosoft Windows “Start” menu entry for TCO Suite can be created automatically. User shouldprovide to create them as follows (see following Fig. 227. ): open the TCO Suite folder [from thelocation established in previous step 2 ) ], and create a shortcut to the Start.html icon on the PC’sdesktop.

N.B. Following the example of Fig. 224. on page 318, in order to create the shortcut, payattention to open the new folder that has been created now, and to give it a mnemonicname different from the shortcut associated to the pre–existing SWP.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

320 / 592 3DB 16142 EAAA Ed.02


Pre–existing folders(SWP V2.0.4 & V2.1.0)

New folder(SWP V2.1.1)

OPEN

LINKPC DESKTOP

shortcut toTCO 2.1.1

Fig. 227. Shortcut to the TCO Suite Start icon

3–1.6.2 Next step

You have now completed the Local copy in PC environment of the TCO Suite. Leave the:– SWP CD–ROM in the PC’s CD–ROM unit,– and the CD–ROM TCO Suite Advanced Settings screen open,and proceed to the next installation step (para.3–1.3 on page 311), according to the case a ) or b ) youwant to achieve.

3–1.7 End of SW installation from SWP CD–ROM

Having reached this phase, you have finished the Software transfer from SWP CD–ROM into the PCenvironment. Now, you can extract the SWP CD–ROM from the PC’s CD–ROM unit.

Now proceed with NE software downloading preparation, para.3–1.8 below.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

321 / 5923DB 16142 EAAA Ed.02


3–1.8 NE software downloading preparation

N.B. This description is retrieved from 1320CT Basic Operator’s Handbook and is repeated here forease of operation.

This phase must be manually carried out by the Operator and has the scope of making the new equipmentsoftware package available for its downloading toward the NE’s equipment controller and the peripheralunits (such a downloading is explained in Chapter 4–8 on page 485).This operation is independent from the NE management state and must be executed with the followingprocedure:

1 ) Launch the CT by:– TCO Suite Main Menu ⇒ Operational & Maintenance

or:– Start ⇒ 1320CTFor details, refer to point e ) on page 174

2 ) On NES (Network Element Synthesis) screen that opens, from the Supervision pull downmenu select the File Administration and then the Software Administration option, as shownin Fig. 228. herebelow.

Fig. 228. Selecting SWP Administration

3 ) In the screen that opens (Fig. 229. below) click on Install

Fig. 229. SWP Administrator screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

322 / 592 3DB 16142 EAAA Ed.02


4 ) In the screen that opens (Fig. 230. on page 323 is an example) select the directory where theNE software package is installed:

Alcatel / JUSMw V.x.x.x / ect / swdw / <equipment name> / <version> / <descriptor file> (*)

(*) the 9400AWY equipment name is “R94AWY” ;the version is that you want;the descriptor file has always the extension “.DSC”.

N.B. The NE software package can also be selected from the CD–ROM used for theinstallation of the NE software. In this case, after inserting the CD–ROM in the driver,choose the following:

ect / swdw / <equipment name> / <version> / <descriptor file>

WARNING: in case you have still installed in your PC one or more previous Alcatel–Lucent SWP, instep [2] of Fig. 230. on page 323, you must be sure to open the JUSM folder relevant tothe SWP you have installed now. In such an example:

• JUSMw2.2.16 is associated to SWP 9400AWY 2.0.4

• JUSMw2.3.11 is associated to SWP 9400AWY 2.1.0

• JUSMw2.4.7 is associated to SWP 9400AWY 2.1.1 [you can check the JUSM versioncomparing it with the report produced at installation end (see Fig. 222. on page317 )].

In any case, whenever the version to be selected in step [6] of Fig. 230. on page 323 isnot that you wanted, you can go backward to step [2] to explore the correct JUSM folder.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

323 / 5923DB 16142 EAAA Ed.02


1

2

3

CONTINUES

Fig. 230. Directory selection for the descriptor file “.DSC”

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

324 / 592 3DB 16142 EAAA Ed.02


4

5

6

7

End of Fig. 230. Directory selection for the descriptor file “.DSC”

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

325 / 5923DB 16142 EAAA Ed.02


5 ) On last screen (containing the “.DSC” file), click on Open to activate the installation of theselected“.DSC” file. At the end of the process, a confirmation message is displayed:

6 ) At this point the NE Software Package is installed and available to be downloaded on theNetwork Elements (as described in chapter 4–8 on page 485).Such availability can be verified (as shown in Fig. 231. herebelow) operating in the NetworkElement Synthesis screen (Fig. 228. on page 321), selecting, from the Supervision pull downmenu, the File Administration and then the Software Administration option.

Fig. 231. SWP available for download to NEs

Now proceed with CT initial configuration, para.3–1.9 on page 326.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

326 / 592 3DB 16142 EAAA Ed.02


3–1.9 CT initial configuration

N.B. Procedures described in the following are carried out with the PC disconnected from the NE.

3–1.9.1 Craft Terminal configuration

This procedure is necessary to configure the PC in order to manage the Network Elements and includesthe following types of configuration:

– PC hostname

– CT configuration

– Communication Protocol (TCP/IP):

• TCP/IP without a network card

• TCP/IP with a network card

• Switching between the two configurations

– Serial Communication with the NE

– Screen settings

In order to set–up these configurations, refer to:

1320CT Basic Craft Terminal Operator’s Handbook ,chapter “SOFTWARE INSTALLATION”, paragraph “Craft Terminal Configuration”

3–1.9.2 Craft Terminal local connection to the NE

The CT can be locally connected to the NE preferably through the Ethernet Network Port, or through theSerial Port.

Only one connection can be active at a time.

Please refer to para.2–2.4.2 on page 171 to change from Ethernet Network Port to Serial port or viceversa.N.B. this setting operation is not necessary if you login the local NE through the Operational &

Maintenance button of the TCO Suite Main Menu.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

327 / 5923DB 16142 EAAA Ed.02


3–1.10 EML construction

After having activated the 1320CT application (by TCO Suite Main Menu ⇒ Operational & Maintenanceor Start ⇒ 1320CT) the “Network Element Synthesis screen” appears (example in Fig. 228. on page 321).This NE map specifies the NEs that can be reached by the ECT. This map must be built by the Operator.

N.B. This map is empty in the case of first installation of ECT on a PC.The map content is usually not affected when you install a new SWP or upgrade theSWP–release–”version” (e.g. from V2.1.x to V2.1.y).

The set of procedures necessary to configure the ECT in order to manage the Network Elements (whichinclude the management of Maps, Submaps and Network Elements, like creation, deletion, saving,opening, etc) is named EML construction .

In order to carry out these procedures, refer to the:– 1320CT Basic Craft Terminal Rel.3.x Operator’s Handbook (see Tab. 78. on page 571)

• section “EML CONSTRUCTION”.

An example of NE creation in the map is given in point g ) on page 176.

end of SWP INSTALLATION IN PC ENVIRONMENT procedure

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

328 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

329 / 5923DB 16142 EAAA Ed.02


3–2 LINE–UP AND COMMISSIONING


3–2.1.1 General

This chapter details all phases necessary for the equipment line–up and commissioning, providing theuser with the information needed to connect, power on, and perform a minimum turn–up of an equipmentof the 9400AWY family running with the SWP 9400AWY R.2.1 V2.1.1 .

It is assumed that the mechanical installation of the INDOOR and OUTDOOR units is completed and theantennas are installed and pre–positioned. Moreover, the IF cable has been allocated but not connectedto the IDU. Any information needed to complete the above mentioned operations are out of the scope ofthis chapter. For this purpose refer to the Installation Handbook.

All the cables and measurement kits as described in the following (Tab. 63. on page 330) are supposedto be available.

The Alcatel–Lucent Software package SWP 9400AWY R.2.1 V2.1.1 must have already been installedin the PC used as the Craft Terminal (CT) and the same software already downloaded in the equipment.

3–2.1.2 Conventions

To simplify the description of actions, the following symbols are in use:

Symbol used Meaning

. Manual action

n Check/Verify

CT⇒ On Craft terminal Select

⇒ Select a Menu item

→ Sub Menu item

The commissioning operations described in this document are for a link between a station A and a stationB.If the network includes supervision, station A is the one located between the supervisory station andstation B (see figure below). Installation and commissioning begin at station A.

IDU

ODUODU

IDU

STATION A STATION B

Network(Supervision Side) Network

Fig. 232. Relative positions of stations A and B

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

330 / 592 3DB 16142 EAAA Ed.02


3–2.1.3 Summary of the commissioning phases

Before proceeding with this operation ensure that you have the equipment and accessories required forthat purpose. All these materials should be present in the service bag.

The commissioning procedure is summarized as follows:

– Turn up (phase 1)

• Station A, roughly point the antenna towards station B• Commission station A (phase 1)• Commission station B (phase 1)• Station B, fine align the antenna towards station A• Station A, fine align the antenna towards station B

– Site acceptance tests (phase 2)

• Station A, carry out all the commissioning checks and tests – Report the results in the TRS• Station B, carry out all the commissioning checks and tests – Report the results in the TRS

Tab. 63. Test and commissioning instruments

INSTRUMENT QTY CHARACTERISTICS

Laptop computer running thesupervisory software

1

The PC must have been already configured as CraftTerminal for 9400AWY Rel.2.1.1.If necessary, please refer to the Chapter 3–1 – SWPinstallation in PC environment on page 309 for anyrelated information and installation instructions you mayneed.

PDH Analyzer –Pattern Generator 1 See System configuration

V.11 – G.703 Data Analyzer 1 See System configuration

Ethernet Data Analyzer 1 Optional – See System configuration

Multi–meter 1 Voltmeter AC and DC – Loop tester

Light service kit cable for ODU Rxpower monitoring

1 see para.3–2.10 on page 405

TRS and SAT 1Test Result Sheet and Site Acceptance Test protocol,

available as separate document(REF.[D] on page 570)

3–2.1.4 Safety–EMC–EMF–ESD norms and Cautions to avoid equipment damage

Read carefully Safety–EMC–EMF–ESD norms in Appendix A on page 501, and Cautions to avoidequipment damage in para.1–1.6 on page 36.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

331 / 5923DB 16142 EAAA Ed.02


3–2.2 Description of equipment interconnections

Following sets of drawings show the equipment interconnections at IDU level in the “1+0” (N.B.) and“1+1” configurations, according to the IDU equipment provisioning specified in Tab. 6. on page 68 :

IDU configuration drawings on page

16E1 without plug–ins 332

16E1 + Audio and User Service Channel plug–in 333

16E1 + Enhanced Ethernet plug–in 334

16E1 + Enhanced Ethernet plug–in + Audio and User ServiceChannel plug–in

335

32E1 without plug–ins 336

32E1 + Audio and User Service Channel plug–in 337

N.B. As far as the “1+0” configurations are concerned, two interconnection drawings are depicted:

– one without protection boxes (the standard and cheapest solution)

– the other with the protection box(es), which allows the easy expansion to thecorresponding “1+1” configuration just installing and cabling the IDU Extension unitwithout altering the User line connections already existing on the IDU Main unit.

For the layouts at ODU level, refer to para.1–4.4 on page 101 .

For additional and more detailed information, please refer to the Installation Handbook, in particular for:

– P/Ns of cables to use

– exact shelves layout for cable route optimization

– connector pinout at User line side, in the case the protection boxes are not used. When they are used,you can find the User line side connector pinout in this manual:

• E1 Protection box from page 79

• Services Protection box from page 84

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

332 / 592 3DB 16142 EAAA Ed.02


3–2.2.1 Configurations with 16E1

WARNING: for “1+0” configurations, read carefully N.B. on page 331

E1 line–side user interface cableAlarms & Housekeepings & NMS interface cable

Main ODU CH1

PS

1+0 CONFIGURATION WITHOUT PROTECTION BOXES

E1 line–side user interfaceconnectors

Main ODU CH1

PS

1+0 CONFIGURATION WITH E1 PROTECTION BOX

Alarms & Housekeepings & NMS interface cable


Extension

Main ODU CH1

ODU CH0

PS

PS

1+1 CONFIGURATION


Fig. 233. Equipment interconnections for configurations with 16E1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

333 / 5923DB 16142 EAAA Ed.02


3–2.2.2 Configurations with 16E1 + Audio and User Service Channel plug–in


Main ODU CH1

PS


E1 interface cableAudio & Service channels interface cable



Alarms & Housekeepings & NMS &Audio & Service channels line–side

user interface connectors

Main ODU CH1

PS

1+0 CONFIGURATION WITH PROTECTION BOXES




Extension

Main ODU CH1

ODU CH0

PS

PS

1+1 CONFIGURATION

Fig. 234. Equipment interconnections for configurations with 16E1 + Audio and User Service Channelplug–in

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

334 / 592 3DB 16142 EAAA Ed.02


3–2.2.3 Configurations with 16E1 + Enhanced Ethernet plug–in


Main4 x Ethernet cables ODU CH1

PS


E1 interface cableAlarms & Housekeepings & NMS interface cable


Main

4 x Ethernetcables

ODU CH1

PS


Alarms & Housekeepings& NMS interface cable


Extension

Main ODU CH1

ODU CH0

PS

PS

1+1 CONFIGURATION

4 x Ethernetcables

Alarms & Housekeepings& NMS interface cable

Fig. 235. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plug–in

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

335 / 5923DB 16142 EAAA Ed.02


3–2.2.4 Configurations with 16E1 + Enhanced Ethernet plug–in + Audio and User ServiceChannel plug–in


Main

ODU CH1

PS


4 x Ethernet cablesE1 interface cable Audio & Service channels interface cable





Main

4 x Ethernetcables

ODU CH1

PS





Extension

Main ODU CH1

ODU CH0

PS

PS

1+1 CONFIGURATION

4 x Ethernetcables

Fig. 236. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plug–in +Audio and User Service Channel plug–in

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

336 / 592 3DB 16142 EAAA Ed.02


3–2.2.5 Configurations with 32E1


Main ODU CH1

PS


E1 interface cables Alarms & Housekeepings & NMS interface cable


Main ODU CH1

PS




Extension

Main ODU CH1

ODU CH0

PS

PS

1+1 CONFIGURATION


Fig. 237. Equipment interconnections for configurations with 32E1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

337 / 5923DB 16142 EAAA Ed.02


3–2.2.6 Configurations with 32E1 + Audio and User Service Channel plug–in


Main ODU CH1

PS


E1 interface cables Audio & Service channels interface cable





Main ODU CH1

PS





Extension

Main ODU CH1

ODU CH0

PS

PS

1+1 CONFIGURATION

Fig. 238. Equipment interconnections for configurations with 32E1 + Audio and User Service Channelplug–in

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

338 / 592 3DB 16142 EAAA Ed.02


3–2.3 Commissioning of STATION A – phase 1 (Turn up)

– Where necessary, switch OFF the power supply before disconnecting the earthconnection,

– Do not connect instruments directly to the IDU/ODU cable connector since theconnector carries 48v DC used to supply the ODU.

– Do not connect the IF cable between IDU and ODU while the IDU is powered up.

3–2.3.1 Turn–on preliminary operations

ALL THESE OPERATIONS ARE PERFORMED WITH THE POWER OFF.

n The antenna of station A is pointed towards station B the best as possible (use compass ifnecessary).

n The hardware configuration of the equipment corresponds to the expected one.

n Make visual inspection for units’ installation and cabling:

• The IDU(s) subrack allocation according to the station lay–out

• The IDU(s) subrack and units ground connections

• The power supply voltage is present (48, 60 V DC) with the correct polarity at the IDU powersupply input

• In 1+1 configuration, check the connections between main and extension IDU(s)

• Tributaries and service channel access are cabled on the station DDF

• The IDU–ODU cables ground kit connections

• The ODU(s) ground connections (In the case of a non–integrated antenna, the antenna and the ODU(s) must be ground connected)

• The IDU(s) / ODU(s) cables are connected to IDU(s) and ODU(s)

• The ODU(s) cables connectors waterproofing

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

339 / 5923DB 16142 EAAA Ed.02


3–2.3.2 Powering up the IDU(s) with ODU(s) connected

This operation has the following scopes:

– verify the SWP present both in CT and NE

– make the Central Frequency and Shifter values of ODUs be acquired by IDU (so that they areretained in the NE’s data base).

Proceed as follows:

a ) Switch on IDU (MAIN and, if equipped, EXTENSION)

b ) Start the Craft Terminal and carry out the NE loginProceed as follows (for details refer to para.2–2.5.2 on page 173):

1 ) Connect the cross–connect Ethernet cable between the Ethernet port of the PC and theEthernet interface on the Main IDU (see Fig. 76. on page 170).In alternative connect the RS232 cable between the serial port of the PC and the “F” interface(ECT) on the Main IDU (see Fig. 76. on page 170).

2 ) Power on the PC and wait for its start–up

3 ) Start–up the Craft Terminal and wait for the Network Element Synthesis screen

4 ) Give the NE icon a mnemonic name (e.g. STAZ A as in Fig. 83. on page 177)

5 ) Start supervision on the local Network Element

6 ) Login the local Network Element, using the Administrator UserName & Password

7 ) Wait for the main Equipment view (CT) to appear (for details, refer to para.2–2.6 on page 181)

c ) Check that CT and NE versions are both V2.1.1 (for details, refer to para.1–2.6.3 on page 62).If NOT, proceed as specified in Chapter 4–9 on page 495.

d ) Start the Quick Configuration Procedure clicking on Main Tool Bar’s icon Quick Configuration(see Fig. 88. on page 183), or select Configuration ⇒ Quick Configuration from the Menu bar.The window in Fig. 245. on page 347 will appear. This window is the first step of the InteractiveQuick Configuration Procedure. Clicking repeatedly on Next button (without any other actions),reach Step C on page 353 (Channel configuration) and confirm the Frequency Values fields.Then, clicking repeatedly on Next buttons (without any other actions), reach Step L on page 368 andclick on Finish button. In this way the Frequency Values fields are saved in the NE’s data base, andwill be available even if the ODU(s) is/are disconnected.

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

Proceed as follows:

a ) Close JUSM and stop Supervision on the NE (for details, refer to para.2–2.5.3 on page 180). LeavePC and CT ready for next operations

b ) Switch off IDU (MAIN and, if equipped, EXTENSION)

c ) Disconnect the IDU(s) / ODU(s) cables from IDU(s).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

340 / 592 3DB 16142 EAAA Ed.02


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

N.B. Make sure that IDU–ODU cable is disconnected from the IDU(s) in order to verify via CTthe System PTx Power and Frequency Tx settings as foreseen by Plant documentationbefore powering up the ODU(s).

Since the IDU(s)–ODU(s) connection is not established, when powering up the IDU(s),the ODU(s) will not be operating and then the IDU(s) will display the relative Alarms.

. After switching on the wall circuit breakers, power–on the Main IDU then the Extension IDU if anyvia the front panel power supplies switches.

n The green ”ON” LEDs on both IDUs come on.

On the IDU Main, wait 1 minute for:

n The green “EOW” LED is on.

n The red “LDI” LED is on.

n The red “RDI” LED is on.

Always on the IDU Main, wait another 1 minute for:

n The red “MIN” LED is on

n The red “MAJ” LED is on

WARNING: With a new Flash only LED “ON” is on.

Finally perform a “Lamp Test” by pressing the “LT” pushbutton on IDU(s) in order to verify if the remainingLEDs are operational.

3–2.3.5 NE login

a ) Login again the local Network Element, using the Administrator UserName & Password.

b ) Wait for the main Equipment view (CT) to appear.Note: Since the ODU(s) cables are disconnected, relevant communication alarm is shown.

c ) Proceed as described in para.3–2.3.7 on page 343N.B. This is the Quick Configuration (interactive). If you want to use another modality, please

read para.3–2.3.6 on page 341, and proceed according to the configuration procedure youlike.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

341 / 5923DB 16142 EAAA Ed.02


3–2.3.6 General on Quick Configuration Procedure

This procedure allows a full system configuration through a guided process, based on a reduced set ofscreens. The related windows will be displayed by a “Wizard Tool” according to a specific order.It is possible to create, save and recover configuration files having the “.qcml” extension.To manage configurations (and configuration files) the following options are available:

[1] On–line creation, modification and save of the NE configuration (interactive)This is done by Craft Terminal (e.g. by Quick Configuration shortcut icon), after having loggingin the NE. For the execution of this procedure, refer to para.3–2.3.7 on page 343.

Quick Configuration shortcut icon

[2] TCO Suite Pre–Provisioning Tool: off–line creation, modification and save of aprovisioning file (not interactive)

By this modality, you do not need to login any NE; its main steps are:a ) launch the application,b ) create and check the NE configuration,c ) save the configuration file ( format is “configuration_name.qcml” ).

This file will be after used to configure the NE (after having logged it) with a simple loadcommand.

For the execution of this procedure, refer to para.3–2.3.8 on page 344.

[3] TCO Suite Set–Up Tool: on–line recover, modification and application of a provisioningfile (not interactive)

By this modality, you access one NE, not using the Craft Terminal application, but the TCO Suiteweb server; its main steps are:a ) launch the application and the connection with the target NE,b ) recover a configuration file “configuration_name.qcml” previously created (e.g. through

the TCO Suite Pre–Provisioning Tool), or get configuration data from the NEc ) check/modify the configuration,d ) apply the configuration to the target NE.For the execution of this procedure, refer to para.3–2.3.9 on page 345.WARNING: the execution of the TCO Suite Set–Up Tool is denied to the Viewer operator

profile

N.B. In alternative, through the “TCO Suite’s Alarms & Settings” function (see para.2–2.3 on page156), it is possible:– to send a “configuration_name.qcml” configuration file to a NE (Configuration Setting,

see para.2–2.3.3 on page 160)– to get from a NE its own “configuration_name.qcml” configuration file (Get Configuration

File , see para.2–2.3.5 on page 164)– to get from a NE its own configuration text Report (Configuration Info , see para.2–2.3.4

on page 161).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

342 / 592 3DB 16142 EAAA Ed.02


3–2.3.6.1 Note on the use of the bottom buttons available in the screens

The bottom buttons available in the screens depend on the configuration tool started, and arecontext–specific, e.g.:

– Back: by clicking on this button the procedure goes back to the previous step

– Next: by clicking on this button the procedure goes on the next step

– Finish or Apply to the NE : this button is active only in the last step. By clicking on this button theoperator confirms the configuration and the new parameters are sent to the equipment

– Save As: by clicking on this button, the configuration can be saved as a “configuration_name.qcml”file (provide a mnemonic name)

– Save & Apply: by clicking on this button, two operations are carried out:

• Save: the configuration and the new parameters are temporarily saved on the system disc N.B.

and then:

• Apply: they are sent to the equipment

N.B. the file is saved under the user “home” directory, inside the TCO SUITE’s temporary filefolder. For example, in Windows XP it is:

[system disc]:\Documents and Settings\[username]\temp_tcosuite.2[xx]\[timestamp]\temp.qcml

Example: D:\Documents and Settings\berenice\temp_tcosuite.217\1164279978890\temp.qcml

– Cancel: by clicking on this button, the procedure is cancelled

– Help: by clicking on this button the operator calls the help–on lineWARNING: the Help button is operative in the CT environment only. It is not operative in the TCOSUITE environment.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

343 / 5923DB 16142 EAAA Ed.02


3–2.3.7 On–line creation, modification and save of the NE configuration (interactive)

This job can be done by Craft Terminal, after having logged in the NE.

To start this application, click on Main Tool Bar’s icon Quick Configuration (see Fig. 88. on page 183),or select Configuration ⇒ Quick Configuration from the Menu bar.

The window in Fig. 245. on page 347 will appear. This window is the first step of the procedure. Proceedas specified in para.3–2.3.10 on page 346.

N.B. With the Quick Configuration (interactive), the configurations parameters displayed in thevarious steps are taken from those actually stored in the NE data base. You can check themand modify (if necessary), then go to the following step. The last step is Step L on page 368.In such a step you can:

– click on Save As button: configuration data are saved in a “configuration_name.qcml” file(provide a mnemonic name)

– and / or click on Finish button: configuration data are stored in the NE data base.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

344 / 592 3DB 16142 EAAA Ed.02


3–2.3.8 TCO Suite Pre–Provisioning Tool: off–line creation, modification and save of aprovisioning file (not interactive)

To launch this application, click on the button Pre–Provisioning Tool of the “TCO Suite Main Page” (seeFig. 55. and Fig. 56. on page 149).This button is a one–click execution for the Pre–Provisioning Tool. User could see a so–called “splashscreen” (Fig. 239. below), a temporary message that will disappear after 10 seconds or by clicking on itwith the mouse.

Fig. 239. Pre–Provisioning Tool ”splash screen”

Another screen could be shown, in order to give user some details on current execution.This screen (Fig. 240. below) is a text–based console with detailed information on execution in progress.This window won’t disappear and can’t be closed by clicking on top–right “X” button or Pre–ProvisioningTool will be closed too. The window can be minimized by clicking on top–right “–“ button.

Fig. 240. Pre–Provisioning Tool console

As soon as the Pre–Provisioning Tool is ready, the following screen appears:

Fig. 241. Pre–Provisioning Tool start screen

In this screen you can click on button:– Open configuration : a file selection window opens, requiring a “configuration_name.qcml” file to

be opened. In this case, the configuration process starts from data you have recovered;– or Create configuration : in this case, the configuration process starts from default data.In both cases, the window in Fig. 245. on page 347 will appear. This window is the first step of theprocedure. Proceed as specified in para.3–2.3.10 on page 346, checking and modifying data asnecessary. The last step is Step L on page 368. In such a step you can only click on Save As button:configuration data are saved in a “configuration_name.qcml” file (provide a mnemonic name).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

345 / 5923DB 16142 EAAA Ed.02


3–2.3.9 TCO Suite Set–Up Tool: on–line recover, modification and application of a provisioningfile (not interactive)

To launch this application, click on the button Set–Up Tool of the “TCO Suite Main Page” (see Fig. 55. andFig. 56. on page 149).

User could see a so–called “splash screen” (Fig. 242. below), a temporary message that will disappearafter 10 seconds or by clicking on it with the mouse.

Fig. 242. Set–Up Tool ”splash screen”

Another screen could be shown, in order to give user some details on current execution.This screen (Fig. 243. below) is a text–based console with detailed information on execution in progress.This window won’t disappear and can’t be closed by clicking on top–right “X” button or Pre–ProvisioningTool will be closed too. The window can be minimized by clicking on top–right “–“ button.

Fig. 243. Set–Up Tool console

Then, User is asked to distinguish between “Direct” or “Remote” connection (Fig. 62. on page 156) andhe/she will be asked to fill the IP address field used to connect to NE.The difference between “Direct” or “Remote” connection is described in para.2–2.2.6 on page 154.

Then (Fig. 63. on page 157), User is asked to provide the Username and Password [same rules as in point3 ) on page 179]. In case of remote connection, the NE’s IP address entered in previous screen(Fig. 62. on page 156) is displayed.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

346 / 592 3DB 16142 EAAA Ed.02


As soon as the Set–Up Tool is ready, the following screen appears:

Fig. 244. Set–Up Tool start screen

In this screen you can click on button:

– Get configuration from NE : in this case, the configuration process starts with data taken from theNE; this modality is exactly the same you can do by Craft Terminal through the Quick Configuration(interactive)

– or Open configuration : a file selection window opens, requiring a “configuration_name.qcml” fileto be opened. In this case, the configuration process starts from data you have recovered;

– or Create configuration : in this case, the configuration process starts from default data.

In all cases, the window in Fig. 245. on page 347 will appear. This window is the first step of the procedure.Proceed as specified in para.3–2.3.10 on page 346, checking and modifying data as necessary.

The last step is Step L on page 368. In such a step you can:

– click on Save As button: configuration data are saved in a “configuration_name.qcml” file (providea mnemonic name)

– and / or click on Apply to NE button: configuration data are stored in the NE data base.

3–2.3.10 Quick Configuration Procedure steps

N.B. Following screens do not show the bottom buttons, that depend on the tool by which theconfiguration procedure has been started and by the context. For their use please refer topara.3–2.3.6.1 on page 342.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

347 / 5923DB 16142 EAAA Ed.02


Step A (Main NE parameter configuration)

Fig. 245. below appears as first window of the procedure:

DO NOT USE THIS CHOICE !

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

REMIND:– in interactive modality, this screen is set with values taken from NE’s data base– in not interactive modality, this screen is set with default values

This step provides a screen to configure the following main NE parameters:

Area “Site”:

a ) Site name and location

Area “NE Parameters Configuration”

b ) Protection Type; choose between:• 1+0: unprotected configuration• 1+1 HSB: Hot Standby protected configuration• 1+1 FD: Frequency Diversity protected configuration

c ) Tributary; choose between:• 16E1: max 16xE1 without Ethernet plug–in• 16E1–FData: DO NEVER SELECT THIS CHOICE !• 16E1–GData: max 16xE1 with Enhanced Ethernet plug–in• 32E1: max 32xE1

N.B. the number of actually usable tributaries depends on the employed Software Label(see Tab. 23. on page 93 )

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

348 / 592 3DB 16142 EAAA Ed.02


d ) Power Supply Unit: in this SWP version, only PSU4860 choice is meaningful

N.B. choices PSUVAC and PSU2460 are relevant to hardware items not presently available

e ) if equipped, click on Audio/User Service Channels plug–in

f ) Market : in this SWP version, only ETSI choice is possible

Area “Structure”:

g ) Structure of the Radio Frame configuration : fields (Radio) Capacity and (Radio) Modulation.

The capacity implies the choice of modulation; for example, if the tributary structure is 2E1, only4QAM modulation scheme is supported.

The association between Radio Capacity and Radio Modulation is shown in Tab. 64. below:

Tab. 64. Radio application: Capacity and modulation

Radio Capacity Radio Modulation

2xE1 4QAM

4xE1 4QAM / 16QAM

8xE1 4QAM / 16QAM

16xE1 4QAM / 16QAM

32xE1 16QAM

N.B. the actually usable Radio Capacity and Modulation types depend on the employedSoftware Label (see Tab. 23. on page 93 )

WARNING: When you change the modulation scheme (from 4 QAM to 16 QAM or vice–versa)the Tx power (in case of operation with RTPC) and the ATPC range (in case ofoperation with ATPC) of the new modulation scheme must be in the correct range(refer to para. 2–6.4 on page 238). If the value is out of range the relevant field in theRTPC & ATPC screen appears empty (automatically is associated a default value,but this value is not displayed).Fill the field with the suitable value.

N.B. For the Remote NE, parameters belonging to this step cannot be modified.To modify them, the System Settings menu must be used (refer to para. 2–3.4.1 on page 210).

To go to next step click on button “Next”.

WARNING: At the first configuration (i.e. with a flash card with an empty MIB) at the end of theconfiguration the “Restart NE” must be performed (refer to para. 2–8.2 on page 160).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

349 / 5923DB 16142 EAAA Ed.02


Step B (Tributary configuration)


This Step B has one or two sub–steps:

– one PDH tributary port configuration screen, see point [1] below

– and four Ethernet port configuration screens (only if Enhanced Ethernet plug–in installed andconfigured), see point [2] on page 351

N.B. summary information on Ethernet port characteristics and management is given in AppendixD on page 547

[1] PDH tributary port configuration screenThe screen shown in Fig. 246. below provides the fields to set the signal mode (unframed, framedor disabled) of each E1 port.Moreover, the Impedance for the E1 tributary also must be selected in the Tributary PortConfiguration (unbalanced 75 ohm or balanced 120 ohm).

Fig. 246. Quick Configuration Procedure Step B: PDH Tributary configuration

By clicking on the one facility button (“All Framed”, “All Unframed” and “All Disabled”), the operatorcan configure all the tributaries with the same values; otherwise he can apply all configuration foreach 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 changesin the configuration both in the local and in the remote NE.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

350 / 592 3DB 16142 EAAA Ed.02


HOW TO OPERATE IN CASE OF CONFIGURATION WITH ETHERNET PORTS (I.E. WHENENHANCED ETHERNET PLUG–IN IS EQUIPPED)

In order to allow the actual configuration and transmission of the Ethernet data streams, it ismandatory that, except the case of 32xE1 Radio Capacity:

• at least one (*) PDH tributary port is disabled

• and that the position (according to Fig. 246. on page 349 ) of such disabled PDH tributary portis one of first four.

N.B. If such operation is not done, the following error message is raised by the systemwhen 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 ofFig. 246. on page 349 to disable one PDH tributary port.

(*) the allowed number of tributaries is as follows:

Tab. 65. Allowed number of PDH tributaries with Ethernet port(s) enabled

Radio Capacity(n.b.1)

Number of allowedPDH (E1) Tributaries

Number of allowedEthernet Ports withEnhanced Ethernet

plug–in (n.b.2)

EthernetBandwidth

[N x (E1capacity)]

2xE1 E1 ≤ 1 N ≤ 2

4xE1 E1 ≤ 3GE ≤ 4

N ≤ 4

8xE1 E1 ≤ 7 GE ≤ 4(10/100/1000BT)

N ≤ 8

16xE1 E1 ≤ 15(10/100/1000BT)

N ≤ 16

32xE1 E1 ≤ 16 16 ≤ N ≤ 32

n.b.1 the actually usable Radio Capacity depends on the employed Software Label (seeTab. 23. on page 93 )

n.b.2 in any combination.

In the screen displayed in Fig. 246. on page 349 (and in the following Steps), the “Back” button is enabledalso. It allows the operator to turn back and change the parameters configured in the previous screen.

Now, if in Step A (Fig. 245. on page 347) you have defined 16E1–GData, proceed to next sub–step [2]on page 351

Otherwise:– to go to the next step click on button “Next”.– to go back to the previous step click on button “Back”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

351 / 5923DB 16142 EAAA Ed.02


[2] Ethernet port configuration screen (with Enhanced Ethernet plug–in installed)

Following configuration screens ( Fig. 247. below and Fig. 248. on page 352 ) appear only if inStep A (Fig. 245. on page 347 ) you have defined 16E1–GData.

N.B. For whole information on Ethernet port characteristics and management, refer to theAppendix D on page 547

Fig. 247. Quick Configuration Procedure Step B: Ethernet GPort configuration

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

– Speed with auto–negotiation OFFand

– Capability Advertised

for all Ethernet Ports #33 , #34 , #35 and #36 , even if one or more are disabled (i.e. with PortStatus field not Enabled).If this setting is not done, the following error message is raised by the system when you clickon button “Next” to go to the next step:

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

352 / 592 3DB 16142 EAAA Ed.02


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

For detailed information on QoS configuration, refer to point [8] on page 551

To go to the next step click on button “Next”.To go back to the previous step click on button “Back”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

353 / 5923DB 16142 EAAA Ed.02


Step C (Channel configuration)

REMIND:– in interactive modality, this screen is set with values taken from NE’s data base [if you are executing

this step inside the commissioning procedure, ODU(s) is/are disconnected, but the relevantfrequency values have been acquired by IDU during operations of para.3–2.3.2 on page 339 ]

– in not interactive modality, fields of this screen are all empty

This step allows the operator to define the basic parameters for each configured channel. The relatedscreen (according to the Protection Type set in Step A) is shown in following Fig. 249. :

1+0

1+1 HSB

1+1 FD

Fig. 249. Quick Configuration Procedure: Channels Configuration (Step C)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

354 / 592 3DB 16142 EAAA Ed.02


By this screen, you must set two types of configuration data: frequency data (sub–step [1] on page 354),and ATPC data (sub–step [2] on page 356), taking into account that, in case of:– “1+0” and “1+1 HSB” configurations, you must set data for one frequency only– “1+1 FD” configuration, you must set data for two channels.

[1] Frequency data settingThe system can operate with different types of ODU according to the RF band and to the channelarrangement. There are ODUs which can manage only one shifter (fixed shifter) or severalpredefined shifters (flexible shifter). For details, according to ODU type employed, please refer topara.1–4.5 from page 104 onwards.

1 ) Interactive mode

a ) ODU with one Shifter onlyIf the ODU can manage only one shifter the Shifter field in the menu is not available (it isgrey).In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is writtenin the Frequency Range field on the right side) and press push–button Next (the Rxfrequency is automatically calculated by using the inserted Tx frequency and the shifter).

b ) ODU with different available Shifters1 ) In the Tx frequency field insert the suitable Tx frequency ...2 ) ... then, in the Shifter field select the suitable shifter and press push–button Next (the

Rx frequency is automatically calculated by using the inserted Tx frequency and theshifter).

WARNING: In case of troubles, please refer to point [2] on page 237 for additionalinformation.

N.B. If necessary, you can exploit the “Frequency Data Help”, described below, inInteractive mode too.

Note: During the command setting, the CT is frozen. Waiting time: max 30’.After having set the frequency data, carry out ATPC data setting (next sub–step [2] on page356). (Note: if you have gone to following Step F, go back to this Step C).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

355 / 5923DB 16142 EAAA Ed.02


2 ) Non interactive modeIn the screen of Fig. 249. on page 353, click the “Frequency Data Help” button. The screen offollowing Fig. 250. opens.

Fig. 250. Frequency Data Help: choice of ODU type

According to the ODU system to be configured, click on relevant line. The screen of followingFig. 251. opens.

values used inexample of

Fig. 252. below

Fig. 251. Frequency Data Help: frequency data of chosen ODU type (example)

N.B. The content of these tables is the same of the tables present in:– para.1–4.5.1 from page 105 (Part lists of ODUs with external diplexer)– para.1–4.5.2 from page 108 (Part lists of ODUs with embedded diplexer)

Thus, in non interactive mode, use values retrieved from such help–on–line tables to fill the“Frequency Values” fields of screens of Fig. 249. on page 353.Following Fig. 252. shows an example of Frequency Data manual setting with values takenfrom the table of Fig. 251. above.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

356 / 592 3DB 16142 EAAA Ed.02


Fig. 252. Example of Frequency Data manual setting

[2] ATPC data setting

In the Channel Configuration area of Fig. 249. on page 353, the ATPC can be Disabled orEnabled:• if ATPC is disabled, the power (constantly transmitted) can be selected by writing the suitable

value in the Tx power field in the RTPC area (see following Fig. 253. )• if ATPC is enabled, the RTPC field is greyed (cannot be selected), and the other ATPC

parameters (Max TX Power value, Min TX Power value, and Low Rx Power threshold value)must be configured in the ATPC area fields (see following Fig. 254. ):– strictly following rules stated in para. 2–6.4 on pages 238 to 240– and obviously setting “Max TX Power value” > “Min TX Power value”.WARNING: if you want to set the minimum value of the range greater than the current

maximum value, you must at first change the maximum value, then change theminimum value (obviously setting it smaller than maximum)

Fig. 253. RTPC setting with ATPC disabled

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

357 / 5923DB 16142 EAAA Ed.02


Fig. 254. Setting of enabled ATPC

In case of 1+1 FD, two tabbed panes (as previous Fig. 253. and Fig. 254. ) are proposed for channel0 and for channel 1 with the same choices applied.The ATPC/RTPC parameters condition for a channelimplies the same configuration for the other one.

In case of 1+1 HSB, choices will be applied to both “channels” (Fig. 255. below).

Fig. 255. ATPC and RTPC Configuration for both channels (1+1 HSB)

To go to the next step click on button “Next”.To go back to the previous step click on button “Back”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

358 / 592 3DB 16142 EAAA Ed.02


Step D (Link Identifier configuration)

The amount of microwave links, especially in urban areas, puts the problem of possible interferencesduring installation and turn–on phase.The digital frame incorporates link identity coding capabilities to prevent the capture of an unwanted signal.

Link identifier management can be:

– enabled selecting the choice Mismatch Detection in the screen of Fig. 256. below

– or disabled de–selecting it.

In case of enabled Link identifier management, it is necessary to provide the NEs with the suitable sentand expected link identifiers values. The NE originating the section inserts the sent identifier. The NEterminating the section extracts the received identifier and compares this value to the expected one.

STATION A STATION B

⇐ sent identifier = B⇒ received identifier = A

received identifier = B ⇐sent identifier = A ⇒

When the mismatch detection is enabled and the value of the incoming identifier is different from theexpected 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 identifiercode is used on both the radio channels.

Link identifier functionality is performed by 5 bits link code, then 32 values link code are allowed.

Fig. 256. Quick Configuration Procedure: Link Identifier configuration (Step D)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

359 / 5923DB 16142 EAAA Ed.02


Step E (Automatic restoration criteria configuration)


This step (Fig. 257. below) appears only if any 1+1 configuration has been defined in step A. It allows theoperator to choose the restoration criteria (revertive or not revertive) for the 3 possible protectionsavailable in the 1+1 configuration:

– Radio Protection (Rx RPS–Hitless Switch)

– Mux/Demux Protection (Tx/Rx EPS)

– HSB Tx Protection (RF Hot Stand–by)

Fig. 257. Quick Configuration Procedure: Automatic restoration criteria configuration (Step E)

To go to the next step click on button “Next” .

To go back to the previous step click on button “Back”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

360 / 592 3DB 16142 EAAA Ed.02


Step F (OSPF area configuration)

REMIND:– in interactive modality, this screen is set with values taken from NE’s data base– in not interactive modality, fields of this screen are all empty

WARNING FOR NOT INTERACTIVE MODALITY:if OSPF data are already defined in the NE’s data base, when the file is downloaded to the NE,OSPF data defined in this procedure do not overwrite those present in the NE’s data base. Theonly way to change such data is to use the interactive modality.

This step (Fig. 258. below) allows to configure one or more OSPF Areas (3 areas max.).

Fig. 258. Quick Configuration Procedure: OSPF Area Configuration (Step F)

WARNING: Area 0 is managed and created by default with Id = 0 and IP address = 0.0.0.0

To create a new area write a number in the Area Id field, in the IP address field write the address and clickon 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 andEthernet) 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 Removeor Change button.

To go to the next step click on button “Next”.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

361 / 5923DB 16142 EAAA Ed.02


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


Fig. 259. Quick Configuration Procedure: Local IP address, Ethernet and NTP configuration (Step G)

This step (Fig. 259. above) allows to configure:

– with reference to Fig. 76. on page 170:• the Local IP address associated to the F interface of the NE. This address is that used to identify

the NE as far as the RECT function is concerned.• the Ethernet interface: it can be Enabled or Disabled by ticking the TMN Ethernet field (default

is Enabled). If enabled, enter in the relevant fields the IP address, the IP mask and select theRouting protocol. If the selected routing protocol is OSPF, select also the area number in theassociated OSPF Area field.WARNING: please do never use the RIP choice present in the Routing Protocol field!

Rules for the definition of the NE’s Local IP and Ethernet IP addresses:– as delivered from Alcatel–Lucent Factory, the NE’s Local IP and Ethernet IP addresses

are both set at default value “10.0.1.2” ;– obviously, these values must be changed to have them different from each other and from

those of the other NEs present in the accessible network. In particular such two addressesmust not belong to the same subnetwork (i.e. the third digit must be different. Examples:• wrong definition: Local IP address = 10.0.1.2 and Ethernet IP address = 10.0.1.3• correct definition: Local IP address = 10.0.1.2 and Ethernet IP address = 10.0.2.3

with IP Mask = 255.255.255.0

– the Network Time Protocol (NTP). To enable the NTP put a tick in the check box of the NTP field.If the NTP has been enabled, write in the Main Server field the IP address of the Server, whichdistributes 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 thesame value of the Main Server.

To go to the next step click on button “Next” .To go back to the previous step click on button “Back”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

362 / 592 3DB 16142 EAAA Ed.02


Step H (Configuration of TMN–RF, TMN–V11 and TMN–G703 channels)


Fig. 260. Quick Configuration Procedure: Configuration of TMN–RF, TMN–V11 and TMN–G703channels (Step H)

This step (Fig. 260. above) allows to configure the following TMN channels:

– the “TMN–RF” interface is a communication interface based on the use of an in–frame RF proprietary64 kbit/s channel. Through this interface the NE can exchange management messages with a remoteOS (or Craft Terminal) station.

– through the “TMN–V11” or the “TMN–G703” interface the NE can exchange management messageswith an OS (or Craft Terminal) in the same station.

Each TMN channel can be Enabled or Disabled by selection in its own Enable field.If enabled, in the Remote Address field will appear the IP address of the remote connected NE.In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also theassociated OSPF area.

In the Mode field of the “TMN–V11” and “TMN–G703” interfaces the following selections can be made:– DTE mode:

to interface an SDH service channel, where DCE mode is not available because of the commonsynchronization of the SDH network.

– Co–directional mode:to allow the routing of the LUX40 NMS, avoiding the needed V11/Eth adapter or to link adjacent AWY.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

363 / 5923DB 16142 EAAA Ed.02


In alternative to the “TMN–G703”, the “TMN in–frame” can be defined.

With this “TMN in–frame” feature, 9400AWY 2.1 equipment is able to introduce in one of the time slots (TS1–31) of the E1#1 tributary, a 64 kb/s signal as network management system (NMS or TMN) to transmitremotely this type of information along the E1#1 route; this selection is alternative to the local availabilityof TMN–G703 (the mutual exclusion is automatic).It is also necessary that the far–end E1#1 tributary is enabled and successfully provisioned.

To activate the “TMN in–frame” feature, in TMN G703 field (see Fig. 261. below) :

– set Mode to In–Frame E1

– define the required E1#1 Timeslot number (default is 1)

Fig. 261. Quick Configuration Procedure: Configuration of “TMN in–frame” (Step H)

To go to the next step click on button “Next” .To go back to the previous step click on button “Back”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

364 / 592 3DB 16142 EAAA Ed.02


Step I (IP Static Routes Configuration)

REMIND:– in interactive modality, this screen is set with values taken from NE’s data base– in not interactive modality, fields of this screen are all empty

This step (Fig. 262. below) configures one or more Static Routers.

Fig. 262. Quick Configuration Procedure: IP Static Routes Configuration (Step I)


[1] Host Address: allows to define the IP address necessary to reach a specific Host.

[2] Network Address: it is in alternative to the Host Address; allows to define the IP Mask to reacha 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) availablewith the NE.

WARNING: No pending (open) static routes are allowed.The default software uses first the static routes and then the dynamic routes. An openstatic route is always considered as a preferential path.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

365 / 5923DB 16142 EAAA Ed.02


N.B. Default Gateway Routing configuration

It is also possible to define a Default Gateway Routing. To do that, in the screen in Fig. 262. on page364 select Network Address. The screen changes to following Fig. 263. :

REMIND:• in interactive modality, this screen is set with values taken from NE’s data base• in not interactive modality, fields of this screen are all empty

Fig. 263. Quick Configuration Procedure: Default Gateway Routing configuration (Step I)

In this screen operate as follows:

a ) in IP Address field, write 0.0.0.0

b ) in IP Mask field, write 0.0.0.0

c ) in Default Gateway IP Address field, write the required destination

d ) click Add



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

366 / 592 3DB 16142 EAAA Ed.02


Step J (EOW and Auxiliary Interface Configuration)

REMIND:– in interactive modality, this screen is set with values taken from NE’s data base– in not interactive modality, fields of this screen are with default values

This step (Fig. 264. below) appears only if the Audio/User Service Channels plug–in configuration hasbeen 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 andwrite the station number associated to the Engineering Order Wire to be used in the selective call.Possible values are: 10–99 (see chapter 4–2 on page 413 for details)

N.B. Number 00 is the value associated to the general call.

– the field ”Type” in the ”Auxiliary Interface Configuration” area allows the operator to change theinterface of the auxiliary channels (see para.1–3.6.4 on page 90 for details)

Fig. 264. Quick Configuration Procedure: EOW and Auxiliary Interface configuration (Step J)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

367 / 5923DB 16142 EAAA Ed.02


Step K (External Input and Output Points Configuration)


This step (Fig. 265. below) configures the external points (please refer to para.1–3.6.1 on page 85 forphysical implementation).

Fig. 265. Quick Configuration Procedure: External Input and Output Points configuration (Step K)

For:

– both Inputs and Outputs:• clicking in the Polarity field, Active Closed or Active Opened can be chosen

– Outputs only:• clicking in the Working Mode field, Manual or Automatic can be chosen;

if Manual is chosen, you can select the Associated Event clicking in the relevant field



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

368 / 592 3DB 16142 EAAA Ed.02


Step L (Summary)

This is the last step (Fig. 266. below). The screen shown summarizes all the parameters configured duringthis procedure and some relevant parameters with default values.

Fig. 266. Quick Configuration Procedure: Summary (Step L)

All the parameters can still be changed by clicking on the “Back” button. The operator can navigate backto 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 (providea mnemonic name)

– and/or confirm the selections by pressing the Finish or Apply to NE or Save & Apply button. All theparameters 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 theoperator 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 KOyou must go back to point [1] (Frequency data setting) on page 354 and check andcorrect both values, not only that declared KO.

– or do none of such operations, clicking on Cancel.

If you are inside the commissioning procedure, obviously you must have defined a correct configuration.In this case proceed with next para.3–2.3.11.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

369 / 5923DB 16142 EAAA Ed.02


3–2.3.11 Powering UP the IDU(s) with the ODU(s)

After the completion of the configuration step, switch Off the IDU(s) in order to re–establish theIDU–ODU(s) connections.

Then, switch on the IDU(s), log in the NE and proceed to the following checks:

3–2.3.11.1 Verify ODU(s) alarm status

Purpose: Verify no abnormal communication alarm between IDU(s) and ODU(s)

Required Instruments: PC with Craft Terminal software

Procedure: Connect CT to IDU

. CT ⇒ Views ⇒ Equipment

→ In the left window, select ODU ch#1

n In the lower right window, verify in the alarms list for that there is no internal communication failure

n In the lower right window, verify in the alarms list that there is no TX failure.

z Repeat for Ch#0 if any (1+1)

Fig. 267. ODU(s) alarm status

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

370 / 592 3DB 16142 EAAA Ed.02


3–2.3.11.2 Transmitter power output check

Purpose: Verify via CT the ODU(s) transmitted power output.



. CT ⇒ Views ⇒ Radio

→ From the left window → select Channel #1

→ From the lower right window → select RTPC & ATPC tab panel

n Verify that ATPC is ”Disabled” as already set during the quick step procedure(If required, change the ATPC status to disable in the ATPC field then → Apply)

n Verify that Tx Power value complies with the suitable value already set via the quick step procedure.(If required, change the Tx Power in the RTPC field then → Apply)


Fig. 268. Transmit power check

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

371 / 5923DB 16142 EAAA Ed.02


3–2.3.11.3 Received power measurement

Purpose: Verify via CT the received power to detect any interference





→ From the lower right window → select “Power Meas” tab panel

→ In the Sample time (sec), write the suitable measurement poling time then press → Start

Fig. 269. Received power check

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

372 / 592 3DB 16142 EAAA Ed.02


Pressing “Start” will prompt a graphic monitoring view of the transmitted and received levels:

Ticking the box “show details” in the lower left corner will call a summary view of the TX an Rx levels:

Fig. 270. Received power details

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 thetransmitter 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 fieldthe information in dBm is –99, probably the supervision has been lost. The confirmation of the lossof the supervision is given by a broken red icon in NES screen.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

373 / 5923DB 16142 EAAA Ed.02


3–2.4 Commissioning of STATION B – phase 1 (Turn up)

– To commission station B, perform the same operations carried on at station A–Phase 1 (para.3–2.3on page 338).

– When Station B is fully configured and operational, and assuming that the antenna in station A hasbeen previously correctly pointed, you should receive some field from station A. In this case, proceedto a fine tuning of the antenna to improve as much as possible the received level.

To monitor the received level during alignment, use the Craft Terminal received power measurementfacility described in para.3–2.3.11.3 on page 371, or the Light service kit cable for ODU Rx powermonitoring in addition to a voltmeter (see description in Annex A: antenna alignment on page404).

– For near future tests, establish on the Station DDF hardware loops on every tributary as well as onthe User service channel.

READ THIS GENERAL INFORMATION ABOUT TEST BENCH DRAWINGS

In the test bench drawings depicted in the following, take always account that:

1 ) the standard equipment interfaces for access points are in most cases considered at StationDDF, in turn connected (in “1+1” configurations) to the line–side connectors of the E1Protection box and of the Services Protection box (when the Audio and User ServiceChannel plug–in is equipped). When protection boxes are not employed, Station DDF isconnected directly to the IDU MAIN unit connectors.Station DDF is not detailed in the drawings: refer to your own plant documentation for details.

For detailed information:

– on the description of equipment interconnections (in all “1+0” and “1+1” configurations),please refer to para.3–2.2 on page 331 , making reference to the equipmentinterconnection diagram corresponding to your actual system layout.

– in case of “1+1” configurations, regarding the description of connector pin–out of:• E1 Protection box, please refer to para.1–3.5 on page 79• Services Protection box, please refer to para.1–3.6 on page 84

– regarding the description of IDU MAIN unit connector pin–out, in case of “1+0”configurations, where protection boxes are usually not employed, please refer to theInstallation Handbook

2 ) the Craft Terminal (CT) is always necessary.The connection between CT and NE can be done in two alternative ways (see Fig. 76. on page170):

– trough a cross–connect Ethernet cable between the Ethernet port of the PC and theEthernet interface on the Main IDU

– or trough a RS232 cable between the serial port of the PC and the “F” interface (ECT) onthe Main IDU.

3 ) the additional material for (1+1) configurations is drawn in dotted line.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

374 / 592 3DB 16142 EAAA Ed.02


3–2.5 End of commissioning phase 1 (Turn up) in STATION A

– In Station A, proceed to a final fine alignment of the antenna. To monitor the received level duringalignment, use the Craft Terminal received power measurement facility described in para.3–2.3.11.3on page 371, or the Light service kit cable for ODU Rx power monitoring in addition to a voltmeter(see description in Annex A: antenna alignment on page 404).

Verify in the hop calculation that the calculated received level has been reached.

– Proceed to the remote NE (station B) acquisition in the Craft Terminal map (described in followingpara.3–2.5.1) in order to verify in the both stations:

n Received level complies with hop calculation

n No alarm showing (except unloaded tributaries)

3–2.5.1 Remote NE (station B) acquisition on craft terminal

. Connect the cable between the serial port of the PC and the “F” interface (ECT) on the Main IDU.

. Start the “1320 CT” application.

n Wait until the NES window appears, for the LLMAN to connect and the “Map” indicator to turn grey.

Right click on Station A NE icon and select “Start supervision”, or ⇒ Supervision → Start

n The question mark in the NE icon disappears while the alarm status of the NE appears.

Fig. 271. NES window local NE

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

375 / 5923DB 16142 EAAA Ed.02


z Right click on the first line “Map “sample”” (or click on “Map sample” and select “NE Directory”) andchoose “create SNMP NE”. The following window will prompt

Fig. 272. Create NE in the CT map

→ Write the local IP address of Station B in the TCP/IP Address field and the port number in theTCP/IP Port field (typically: 161), then click OK.The newly created NE will appear in the CT map as shown below.

. Right click on Station B NE icon and select “Start supervision”, or ⇒ Supervision → Start

Fig. 273. NMS Radio side Remote NE acquisition

N.B. The above remote NE acquisition is described assuming that the TMN–RF access have beenenabled in both Stations during Quick Configuration Procedure – step H on page 362. Onthe contrary, the TMN–RF channel can be enabled directly through the CT menu:

. CT ⇒ Configuration ⇒ Network Configuration → IP configuration → IP point to point configuration.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

376 / 592 3DB 16142 EAAA Ed.02


3–2.5.2 Testing configurations for hop quality check

Interfacing with the E1 Protection box, set up the following testing configuration and run on one tributary,a minimum of one hour BER test free of error.

ODU

ODU

ERRORANALYZER

IDU MAIN

E1

IDU MAIN

Remote station

ERRORANALYZER

E1

Fig. 274. Test bench for tributary quality test

Interfacing with the Services Protection box, set up the following testing configuration and run on theUser service channel, through the hardware loopback previously established in station B, a minimum of10 minutes BER test free of error.

ODU

ODU

IDU MAIN

IDU MAIN

“ESC loopback”

Remote station

ESC

DATAANALYZER

G.703 or V11

ESC

Fig. 275. Test bench for User service channel quality test

N.B. In case of V.11 the loopback on the remote station cannot be performed. In this case two dataanalyzer must be used.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

377 / 5923DB 16142 EAAA Ed.02


3–2.6 Commissioning station A – phase 2 (acceptance test)

Commissioning phase 2 is a site acceptance test procedure made up of the required tests to ensure thatthe equipment is fully operational.

This phase describes first of all the way to check and to change (if necessary) via the Craft Terminal menuthe different configuration parameters already set, for most of them, during the Quick ConfigurationProcedure in phase 1, followed by various tests.

Most of the tests and checks results have to be recorded in the TRS (Test Results Sheet ; see Tab. 63. on

page 330). Operator will be invited to do so each time it is required by the following sentence: “Report… into the TRS.”

3–2.6.1 System Installation and cabling visual inspection

3–2.6.1.1 Indoor System installation and cabling inspection

See and fill the indoor inspection check list in the TRS.

3–2.6.1.2 Outdoor System installation and cabling inspection

See and fill the indoor inspection check list in the TRS.

3–2.6.2 Local configuration control

Purpose: Verify via CT the Local Station configuration.



3–2.6.2.1 Check software key (Software Label) code

. CT ⇒ Supervision ⇒ SW key

The screen of Fig. 159. on page 256 opens.

Report the SW Key number and code into the TRS

→ Close.

3–2.6.2.2 Check/set the NE parameters and frame Configuration

. CT ⇒ Configuration ⇒ System Settings

The screen of Fig. 109. on page 210 opens.

If it is necessary to change any parameter, refer to para.2–3.4.1 on page 210

Report the Type, Market, Capacity, Modulation and Impedance into the TRS

→ Close.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

378 / 592 3DB 16142 EAAA Ed.02


3–2.6.2.3 Check/set E1 tributaries configuration

Reference screen: Fig. 129. on page 228 :

. CT ⇒ Views ⇒ Line Interface

In the left window → E1 port# 1

In the lower right window → “Configuration” Tab panel.

Repeat for each E1 port#

If it is necessary to change any parameter, refer to para.2–5.1.2.1.1 on page 228

3–2.6.2.4 Check/set User Enhanced Ethernet interface parameters (Optional)



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

In the lower right window → “Configuration” Tab panel.

If it is necessary to change any parameter, refer to point [2] on page 232

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

379 / 5923DB 16142 EAAA Ed.02


3–2.6.2.5 Check/set the automatic restoration criteria (only 1+1)

3–2.6.2.5.1 Radio Protection


. CT ⇒ Views ⇒ Protection SchemesIn the left window → Radio Protection (RPS)In the lower right window → Schema Parameters Tab panel → Protection Type 1+1

If required, change Operation type (Revertive or Not Revertive) then → Apply

For additional information, refer to para.2–9.2 on page 260

Report the Operation Type into the TRS

3–2.6.2.5.2 Mux/Demux Protection


. CT ⇒ Views ⇒ Protection SchemesIn the left window → Mux/Demux ProtectionIn the lower right window → Schema Parameters Tab panel → Protection Type 1+1




3–2.6.2.5.3 HSB Transmission Protection


. CT ⇒ Views ⇒ Protection SchemesIn the left window → HSB Tx ProtectionIn the lower right window → Schema Parameters Tab panel → Protection Type 1+1




3–2.6.2.6 Check/set the Rx static delay configuration for radio protection (1+1 only)


. CT ⇒ Views ⇒ Protection SchemesIn the left window → Radio ProtectionIn the lower right window → “Rx Static Delay” Tab panel → press Auto (default value)

If required, change to Manual Operation → set suitable values for channel 0 and 1 then → Start


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

380 / 592 3DB 16142 EAAA Ed.02


3–2.6.2.7 Check/set TX and RX frequencies

Reference screen: Fig. 136. to Fig. 138. on pages 235 to 236 :


In the left window → Channel #1

In the lower right window → “Frequency” Tab Panel

Repeat for Channel 0 (only in 1+1)

Report the TX and the RX frequencies into the TRS

If required, change the Tx frequency then → Apply. Rx Freq. will be automatically adjusted

For additional information and warnings, refer to para.2–6.3 on page 235

3–2.6.2.8 Check/set TX power (ATPC Off ) or Tx range and Rx threshold (ATPC On)


ATPC Disabled:

. CT ⇒ Views ⇒ RadioIn the left window → Channel #1In the lower right window → “RTPC&ATPC” Tab Paneln ATPC “Disabled”Repeat for Channel 0 (only in 1+1)Report the ATPC “Disabled” status, Tx nominal Power and Tx Power setting into theTRS

ATPC Enabled:

. CT ⇒ Views ⇒ RadioIn the left window → Channel #1In the lower right window → RTPC&ATPC Tab Paneln ATPC “Enabled”Repeat for Channel 0 (only in 1+1)Report the ATPC “Enabled” status, ATPC Range and ATPC RX Threshold setting intothe TRS

If required, change ATPC Mode or ATPC Range or ATPC Rx Threshold then → Apply

For additional information and warnings, refer to para.2–6.4 on page 238

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

381 / 5923DB 16142 EAAA Ed.02


3–2.6.2.9 Check/set the User data channel type and the station phone number


. CT ⇒ Configuration ⇒ System Setting → “Overhead” Tab Panel

Report the auxiliary interface type and the Phone number into the TRS

→ Close

For additional information and parameter change, refer to para.2–3.4.3 on page 213 , or to QuickConfiguration Procedure’s Step J screen described on page 366

3–2.6.2.10 Check/set the local NE IP address


. CT ⇒ Configuration ⇒ Network Configuration → Local Configuration

Report the local IP Address in the TRS

For additional information and parameter change, refer to para.2–3.2.1 on page 192 , or to QuickConfiguration Procedure’s Step G screen described on page 361

3–2.6.2.11 Check/set OSPF Area Configuration


. CT ⇒ Configuration ⇒ Network Configuration → IP Configuration → OSPF Area Configuration

Report the Id, IP Address, IP Mask and Stub flag into the TRS

For additional information and parameter change, refer to para.2–3.2.4.3 on page 200 , or to QuickConfiguration Procedure’s Step F screen described on page 360

3–2.6.2.12 Check/set the NMS IP point to point interface configuration


. CT ⇒ Configuration ⇒ Network Configuration → IP Configuration → IP Point to PointConfiguration

Report the mode, IP Routing, OSPF Area and Remote Address for Enabled connection intothe TRS

For additional information and parameter change, refer to para.2–3.2.4.4 on page 202 , or to QuickConfiguration Procedure’s Step I , point [4] described on page 364

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

382 / 592 3DB 16142 EAAA Ed.02


3–2.6.2.13 Check/set the Ethernet access (OS) configuration


. CT ⇒ Configuration ⇒ Network Configuration → Ethernet Configuration

Report the IP Address, IP Mask, IP Routing protocol and OSPF Area into the TRS

For additional information and parameter change, refer to para.2–3.2.3 on page 195 , or to QuickConfiguration Procedure’s Step G described on page 361

3–2.6.2.14 Check/set IP static routing configuration


. CT ⇒ Configuration ⇒ Network Configuration → IP Configuration → IP Static RoutingConfiguration

Report the IP Address, IP Mask and Default gateway IP Address or interface type into theTRS

For additional information and parameter change, refer to para.2–3.2.4.1 on page 196 , or to QuickConfiguration Procedure’s Step I described on page 364

3–2.6.3 Channel 1 functionality tests (1+0 and 1+1)

Open the “summary Block diagram view” for all the duration of Channel 1 functionality tests in orderto visualize at any time the Switching and Loopback status of the microwave:

Purpose: Display the summary block diagram



. CT ⇒ Diagnosis ⇒ Summary Block Diagram View

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

383 / 5923DB 16142 EAAA Ed.02


Fig. 276. 1+0 Summary block diagram view

Fig. 277. 1+1 Summary block diagram view




By clicking on a specific object of the drawing, the operator can navigate to the relevant CT menu view.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

384 / 592 3DB 16142 EAAA Ed.02


3–2.6.3.1 Channel protection switching configuration (1+1 only)

Purpose: lockout the channel 0 for all the duration of the channel 1 testing



. CT ⇒ Diagnosis ⇒ Protection Schemes

In the left window → Radio Protection → Spare #0

In the lower right window → Commands scroll list → Lockout → Apply

Repeat for HSB Tx Protection and Mux/Demux Protection

n Check in the summary block diagram that the full channel 1 (TX and RX) path is in service.

Report about the Channel 1 protection switching functionality into the TRS

Fig. 278. Channel 0 lockout mode

For additional information and parameter change, refer to chapter 2–9 on page 257

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

385 / 5923DB 16142 EAAA Ed.02


3–2.6.3.2 Near End Loop back functionality

Purpose: Verify via CT the near end loopback functionality

Required Instruments: PC with Craft Terminal software and E1 Data Analyzer

Procedure: Connect CT to IDUConnect Data analyzer on one Tributary Access (At the Station DDF)

– Four different near end Loopbacks have to be performed one by one. Remove previous loopbackbefore proceeding with the next one. A delay up to 10 seconds may be observed for eachactivation/deactivation.

– Ensure that the local tributary access (used to control via the data analyzer the continuity and thequality of every loopback) is active (framed or unframed) (see para.3–2.6.2.3 on page 378 for moredetails about tributaries configuration)

– Ensure that the local transmitter is not muted. (see para.4–5.9.10 on page 449 for more details aboutTX Mute functionality)

E1

IDU ODU

MUXDEMUXTRIB MODEM RF

1 2 3 4

ANTENNA

(1) Near End Tributary Loopback Point

(2) Near End IDU Cable Loopback Point

(3) Near End ODU Cable Loopback Point

(4) Near End RF Loopback Point (N.B.)


Fig. 279. Near End loopbacks points

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

386 / 592 3DB 16142 EAAA Ed.02


. CT ⇒ Views ⇒ Loopback

In the left window →Tributaries → TX port# NE (select tributary on which the Data Analyzer is connected)

In the lower right window → Activate → Apply

n Data analyzer showing no errors

n Loopback showing in the summary block diagram view

In the lower right window → Deactivate → Apply

Report about the near end Tributary loopback functionality into the TRS

Fig. 280. Loopback control in the CT


In the left window → Channel #1 → IDU Cable





Repeat for Near End IDU Cable and Near End ODU Cable

Report about the near end IDU Cable and ODU Cable loopback functionality into theTRS

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

387 / 5923DB 16142 EAAA Ed.02


3–2.6.3.3 Far End Loop back functionality

Purpose: Verify via CT the Far end loopback functionality



– One Far end loopback has to be performed under the same condition as the near end loopbacks.Moreover, ensure that the remote transmitter like the local transmitter is not muted.

E1

ODU

ANTENNA

ODU

MODEMRF

IDU

MUXDEMUX TRIB

ANTENNA

STATION A STATION B

IDU

1 E1

Fig. 281. Far End loopback point


In the left window → Tributaries → TX port# FE (select the same tributary # that the one which is locallyconnected to the data analyzer)





WARNING: A far end loopback can be removed only from the NE that activated it.

Report about the Far end Tributary loopback functionality into the TRS

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

388 / 592 3DB 16142 EAAA Ed.02


3–2.6.3.4 Tributary functionality test

Purpose: Verify the point to point Tributaries qualityVerify the tributaries alarm status monitoring functionality


Procedure: Connect CT to IDUConnect Data analyzer on Tributary Access (At the Station DDF)

ODU

ODU

ODU

ODU

IDU MAIN

IDU EXTENSION

IDU EXTENSION

IDU MAIN

ERROR ANALYZER

PATTERN GENERATOR

E1

“Tributary loopback”

Remote station

N.B.

N.B.

N.B. the diagram indicates the “loopback” (at remote station) and the connection (at local station)for the first 16 E1 tributaries. To check the other ones, change connections.

Fig. 282. Test bench for tributary functionality check

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

389 / 5923DB 16142 EAAA Ed.02


Assuming that all the tributaries have been enabled (Unframed status) via CT in both stations and thatevery tributary are looped at the DDF in the remote station:

z Perform one minute of BER test on each E1 tributary

n Verify that the analyzer detects no error.

n Verify on CT “Line Interface” view the tributary alarm status:


In the lower right “Alarms list”, verify that while the data analyzer is connected, the “AlarmLossSignal” onthe relevant tributary goes off.

Note: Check also the framed tributaries (if required).

Fig. 283. Tributary alarm status monitoring

Report about the Tributary BER test and alarm CT monitoring into the TRS.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

390 / 592 3DB 16142 EAAA Ed.02


3–2.6.3.5 Service data channel functionality test

Purpose: Verify the point to point Service Data Channel quality

Required Instruments: PC with Craft Terminal software and G703 / V11 64 Kbit/s Data Analyzer

Procedure: Connect CT to IDUConnect Data analyzer on the service channel Access (At the Station DDF)

ODU

ODU

ODU

ODU

IDU MAIN

IDU EXTENSION

IDU EXTENSION

IDU MAIN

Remote station

ESC

DATAANALYZER

64kbit/s (G.703 or V11)

“ESC loopback”

ESC

Fig. 284. Test bench for User Service Channel functionality check

Assuming that the User service Channel is looped at the DDF in the remote station:

z Perform 10 minutes of BER test.

n Verify that the Data analyzer detects no error.

Report about the 64 Kbit/s Data channel BER test into the TRS

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

391 / 5923DB 16142 EAAA Ed.02


3–2.6.3.6 Ethernet Data channel (optional) functionality test

Purpose: Verify the point to point Ethernet Data Channels quality

Required Instruments: PC with Craft Terminal software and 2 Ethernet Data Analyzers

Procedure: Connect CT to IDUConnect Data analyzer on Main IDU Ethernet Access.

Test bench for Enhanced Ethernet plug–in (4xGigabit Ethernet plug–in) equipped: Fig. 285. below

z Perform 10 minutes of BER test on both Optional Ethernet access.

n Verify that the Data analyzer detects no error.

Report about the Ethernet Data Channels BER test into the TRS.

ODU

ODU

ODU

ODU

IDU MAINIDU EXTENSION

IDU EXTENSION

Remote station

ETHERNET DATA

ANALYZER

ETHERNET DATA

ANALYZER

Fig. 285. Test bench for Optional Ethernet Data Channel functionality (with 4xGigabit Ethernet plug–in)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

392 / 592 3DB 16142 EAAA Ed.02


3–2.6.3.7 Ptx and Prx measurement

Purpose: Verify via CT the Transmitted (Ptx) and received (Prx) power




. CT ⇒ Views → Radio


→ From the lower right window → select “Power Meas” tab panel

→ In the Sample time (sec), write the suitable measurement poling time then press → Start

Pressing “Start” will prompt a graphic monitoring view of the transmitted and received levels (see Fig. 142. on page 242 ):

Ticking the box “show details” in the lower left corner will call a summary view of the TX an Rx levels(see Fig. 143. on page 243 )

Report the Current Tx Local End (Ptx) and the current Rx Local End (Prx) into the TRS.

For additional information, PTx and PRx levels software readings tolerance and warnings, refer topara.2–6.5 on page 241

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

393 / 5923DB 16142 EAAA Ed.02


3–2.6.3.8 Inside hop Engineering Order Wire functionality test (optional)

MAIN

ODU

EXTENSION

ODURemote Station

ODU

EXTENSION

ODU

OFF ON

MAIN

EOW

OFF ON

1 2 34 5 67 8 9

#* 0

TPH

Fig. 286. Engineering order wire organization

Make a call from local station:

1. Check that the line is free (green EOW LED is on).

2. Handset OFF/ON switch to ON.

3. On keypad, press # to engage line.

4. Check that yellow EOW LED on MAIN IDU is on (as well as in the remote station)

5. On keypad, dial the two–digit remote station number or 00 for general call.

6. Ring tone is audible in the handset.

In the remote station:

7. Yellow EOW LED is flashing and the IDU is emitting a ring tone.

8. Connect handset to IDU, set ON/OFF switch to ON, press # on keypad. Speak.

Switch off the handsets in both stations to finish the call.

Report about the Order wire functionality into the TRS.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

394 / 592 3DB 16142 EAAA Ed.02


3–2.6.4 Channel 0 functionality tests (1+1 only)

3–2.6.4.1 Channel protection switching configuration

Purpose: Forced the channel 1 for all the duration of the channel 0 testing



. CT ⇒ Diagnosis ⇒ Protection Schemes

In the left window → Radio Protection → Main#1

In the lower right window → Command scroll list → Forced → Apply

n Check in the summary block diagram that the full channel 0 (Tx and Rx) path is in service.

Repeat for:

– the Mux/Demux Protection (see para.2–9.1 on page 258 )

– and, only for HSB systems, the HSB TX Protection (see para.2–9.3 on page 262 )

Report about the Channel 0 protection Switching functionality into the TRS

Fig. 287. Channel 1 forced mode

Note : The “Forced” command for channel 1 is equivalent to the “Lockout “ command for the channel0. In both cases, the result is that the relevant channel protection path is forced to standbystatus.

For additional information and parameter change, refer to chapter 2–9 on page 257

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

395 / 5923DB 16142 EAAA Ed.02


3–2.6.4.2 Near End Loop back functionality

Repeat the same test already performed for channel 1. Report the results into the TRS.

3–2.6.4.3 Far End Loop back functionality


3–2.6.4.4 Tributary functionality test


3–2.6.4.5 Service data channel functionality test


3–2.6.4.6 Ethernet Data channel (optional) functionality test


3–2.6.4.7 Ptx and Prx measurement


3–2.6.4.8 Inside hop Engineering Order Wire functionality test


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

396 / 592 3DB 16142 EAAA Ed.02


3–2.6.5 Hop stability test

Purpose: Verify the Hop stability



– The Hop stability test is performed during two consecutive hours, one time, on one Tributary, in realworking condition whatever the protection configuration (1+ 0 or 1+1).

– The two hours stability test must be free of error in normal propagation conditions (out of fadingperiod)

z Via the CT, let only one active tributary in both station

z In the remote Station, place a hardware loop on the relevant tributary access (at the station DDF).

z In the local station, connect the E1 Data Analyzer on the relevant tributary. Check that the “TributaryAlarm Loss” disappears.

n Verify in both stations that there are no active software loopbacks or switching requests

n Verify in both stations that none alarm is showing.

Report the two hours free of error test result into the TRS.

ODU

ODU

ODU

ODU

IDU MAIN

IDU EXTENSION

IDU EXTENSION

IDU MAIN

ERROR ANALYZER

PATTERN GENERATOR

E1

“Tributary loopback”

Remote station

Fig. 288. Test bench for hop stability test

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

397 / 5923DB 16142 EAAA Ed.02


3–2.6.6 NE integration tests

3–2.6.6.1 NMS Radio side acquisition

Purpose: Verify Via CT the remote NE RF side acquisitionRequired Instruments: PC with Craft Terminal softwareProcedure: Connect CT to IDU

NE Radio side acquisition has been already performed during the Turn Up (commissioning – phase 1).Refer to para.3–2.5.1 on page 374 for more details.

3–2.6.6.2 NMS Line side acquisition (if foreseen in the plant documentation)

Purpose: Verify Via CT the remote NE line side acquisitionRequired Instruments: PC with Craft Terminal softwareProcedure: Connect CT to IDU

Direction 2

V11 G703

Local Station (Station A)

Toward station B

ODU

or

ODU

IDU MAIN – facing station B

IDU MAIN – Direction 2

Fig. 289. Test bench for NMS Line side acquisition

N.B. A transfer cable must be placed between the G703 or V11 connectors of the two ServicesProtection boxes.

On both IDUs, the NMS line side access must be enabled:

. CT ⇒ Configuration ⇒ Network Configuration → IP Configuration → IP Point to Point Configuration

→ Select V11 interface or G703 interface (depending of the transfer cable used) and the required routing.

→ Select enable → Apply

The IP address of the line side remote NE should appear in the remote address field.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

398 / 592 3DB 16142 EAAA Ed.02


z Connect the CT to the IDU facing Station B

. Start the “1320 CT” application.

. Right click on each NE icon and select “Start supervision”, or ⇒ Supervision → Start

Since the NMS RF side NE acquisition has already been performed, both local and remote NE of the hopcurrently under commissioning are visible.

Fig. 290. NES window local NE

z Right click on the first line “Map “sample”” (or click on “Map sample” and select “NE Directory”) andchoose “create SNMP NE”. The following window will prompt

Fig. 291. Create NMS Line side NE in the CT map

→ Write the local IP address of Main IDU direction 2 in the TCP/IP Address field and the port numberin the TCP/IP Port field (typically: 161), then click OK.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

399 / 5923DB 16142 EAAA Ed.02


The newly created NE (direction 2) will appear in the CT map as shown below.

. Right click on “direction 2” NE icon and select “Start supervision”, or ⇒ Supervision → Start

Fig. 292. NMS Line side NE monitoring in the CT map

Check that “Direction 2” NE responds correctly to supervision:

. Right click on the NE icon and select “Show equipment”, or ⇒ Supervision → Show equipment

Report about the NE line side acquisition functionality into the TRS.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

400 / 592 3DB 16142 EAAA Ed.02


3–2.6.6.3 EOW line side call (if foreseen in the plant documentation)

Direction 2

AUDIO 2

Local StationODU

or

ODU


OFF ON

Direction 1

AUDIO 1

OFF ON


Fig. 293. Test bench for EOW line side functionality test

Make a call from IDU direction 1 to IDU direction 2 or any remote station in Direction 2:

A transfer cable must be placed between the Audio 1 or Audio 2 connectors of the two ServicesProtection boxes.

Check that the line is free on both Main IDU(s) (green EOW LED is on).

On IDU direction 1:

1. Check that the line is free (green EOW LED is on).

2. Handset OFF/ON switch to ON.

3. On keypad, press # to engage line.

4. Check that the EOW LEDs turn to yellow (as well as on the IDU direction 2)

5. On keypad, dial the two–digit number of the IDU direction 2 or any remote station in direction 2.

6. Ring tone is audible in the handset.

On IDU direction 2 (or in the remote station in direction 2 which is called):

7. Yellow EOW LED is flashing and the IDU is emitting a ring tone.

8. Connect handset to IDU, set ON/OFF switch to ON, press # on keypad. Speak.

Switch off the handsets to finish the call.

Report about the Order wire Line side functionality into the TRS.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

401 / 5923DB 16142 EAAA Ed.02


3–2.6.6.4 Housekeeping alarms setting and testing (if foreseen in the plant documentation)

N.B. For additional information not given here, refer to chapter 2–7 on page 247

3–2.6.6.4.1 External alarm inputs

Note: These tests should be performed only in specific sites requested by the Customer.

Purpose: Configure and test Via CT the housekeeping external alarm inputsRequired Instruments: PC with Craft Terminal softwareProcedure: Connect CT to IDU

Six alarm inputs are available to monitor either Relay contact or open collector type external alarms.


. CT ⇒ Views ⇒ External Points

In the left window → INPUT → CPI 1 to CPI 6

In the lower right window → User Label → Write the suitable name for the current alarm.→ Polarity → Configure if the alarm must show when closed or opened → Alarm Profile → Primary Alarms (by default)

Testing the external alarms monitoring:

Assuming that CPI 1 is configured in “Active Closed” polarity:

z Place a hardware loop on the station DDF between CPI 1 access point (Sub D – pin 6) and GND point(Sub D – Pin 10). See connection point description in para.1–3.6.1 on page 85.

n Verify in the CT External points view that CPI 1 is showing an alarm.

z Repeat with CPI 2 to 6.

Report about the House keeping input alarms acquisition into the TRS.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

402 / 592 3DB 16142 EAAA Ed.02


3–2.6.6.4.2 Alarms outputs

Purpose: Configure and test the housekeeping equipment alarms outputsRequired Instruments: PC with Craft Terminal software and Multi–meter (loop tester)Procedure: Connect CT to IDU

– Three alarm outputs are dedicated to fixed equipment general alarms: IDU, ODU 1 and SPARE ODU.– Four alarm outputs CPO 1 to 4 can be configured either as equipment alarm or manual remote

control:


. CT ⇒ Views ⇒ External points

In the left window → OUTPUT → CPO 1 to CPI 4

In the lower right window → User Label → Write a name for the current equipment or remote control alarm→ Polarity → Configure if the contact must be closed or

opened when active

To use the relevant Alarm output as a manual remote control:

→ Criteria → Manual → Apply

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 multi–meter (loop tester mode) between CPO 1 access point (Sub D – pin 4) and theCommon wire point (Sub D – pin 9). See connection point description in para.1–3.6.1 on page 85.

. CT ⇒ Views ⇒ External points

In the left window → OUTPUT → CPO 1

In the lower right window → Polarity → Active Closed.

→ Criteria→ Manual → Apply

→ External State → On → Apply

n Loop tester must detect a loop (close circuit).

In the lower right window → External State → Off → Apply

n Loop tester does not detect anymore loop (open circuit).

z Repeat with CPO 2 to 4.

Report about the House keeping Output alarms detection into the TRS.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

403 / 5923DB 16142 EAAA Ed.02


3–2.7 Commissioning station B – Phase 2 (Acceptance Test)

Repeat in Station B all the tests performed in Station A except the Hop Stability Test that has to be run onlyone time for the full hop.

Fill a second Test Result Sheet for Station B

END OF COMMISSIONING ACCEPTANCE TEST

3–2.8 Final operations

As introduced in para.1–2.6.1 on page 59, complete the commissioning of each NE, creating the NEoperator profiles and saving its data.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

404 / 592 3DB 16142 EAAA Ed.02


3–2.9 Annex A: fine antenna alignment

Safety rules for Microwave radiations (EMF norms):read carefully para.5–1.3.8 on pages 507 onwards

Antenna pre–pointing should have been done during equipment hardware installation described in theInstallation Handbook. This annex explains how to carry out the antenna fine alignment.

To do that:

a ) the radio link must be up

b ) in general, fine alignment should be done only on one station of the radio link

c ) connect a voltmeter to the ODU of such a station, through the light service kit cable (seepara.3–2.10 on page 405)

d ) proceed with Vertical alignment, then with Horizontal alignment, as described in the InstallationHandbook (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 polemounting employed. All integrated pole mounting types are described in the InstallationHandbook.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

405 / 5923DB 16142 EAAA Ed.02


3–2.10 Annex B: light service kit cable operative information

Fig. 294. herebelow shows this optional cable (P/N 3CC 13477 AA**):

Red

Black

A B

C

E

D

1

2

3

4

5

6

7

8

9

10

11

12

1

2

3

4

5

6

7

8

9

10

11

12

1

A B

EC D

View following G

1

2 3

4

5

67

8

9 10

1112

View following F

1

23

4

5

6 7

8

910

1211

F G

LEMO wire 6 = ground

Fig. 294. Light service kit cable

Connector usage:

– (A) LEMO connector, to be plugged into LEMO connector on ODU (see Fig. 46. on page 120 andFig. 47. on page 121)

– (B) LEMO connector, for Alcatel–Lucent internal use only.

– banana plugs (C) and (D) : output is a 0 to +3V DC voltage proportional to the radio Rx field. Duringequipment line–up, through a multi–meter it is possible to easily point the antenna until the measuredvoltage is the maximum, corresponding to the maximum radio Rx field. Actual Rx field value can bemeasured by means of the Craft Terminal (see para.2–6.5 on page 241).

– (E) RS232 connector, for Alcatel–Lucent internal use only.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

406 / 592 3DB 16142 EAAA Ed.02


a ) END OF SECTION

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

407 / 5923DB 16142 EAAA Ed.02

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1MAINTENANCE AND UPGRADE

SECTION 4: MAINTENANCE AND UPGRADE

This section contains the whole logical and operative information for the equipment maintenance andsystem SW and HW upgrade.


MAINTENANCE

Chapter 4–1 – Maintenance PolicyIt introduces the basic concepts for the equipment maintenance.

409

Chapter 4–2 – Set and use of EOW functionsIt explains how to configure and use the Engineering Order–Wire functions of theequipment.

413

Chapter 4–3 – Maintenance Tools and Spare PartsIt describes the instruments, accessories and the equipment spare parts that areenvisaged to carry out the routine and corrective maintenance of the equipment.

415

Chapter 4–4 – First Level MaintenanceIt describes the First Level Maintenance (system state display) of the equipment.

421

Chapter 4–5 – Second Level MaintenanceIt describes the preventive and corrective maintenance of the equipment.

429

Chapter 4–6 – Spare Flash Card management and replacement proceduresThis chapter describes how to manage the spare Flash Card and how to replaceit, in case of problems.

465

UPGRADE

Chapter 4–7 – System hardware upgradeThis chapter details all phases necessary to install tributary plug–ins, or to upgrade9400AWY system from (1+0) to (1+1) configuration, or to replace the Flash Cardto improve system capacity.

469

Chapter 4–8 – SWP download toward NEThis chapter details all phases necessary to download inside the NE equipmentenvironment, and then activate, a SWP having a version greater than that presentlyloaded in the NE’s Flash Card.

485

Chapter 4–9 – ECT & NE upgrade from V2.1.0 to V2.1.1This chapter details all phases necessary to install a new SWP ’version’ in the PCenvironment as well as in the equipment environment, in both stations A and B ofthe radio link.

495

Chapter 4–10 – SWP de–installationThis chapter describes how to de–install from the PC the Craft Terminal SoftwarePackage components.

497

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

408 / 592 3DB 16142 EAAA Ed.02

USER MANUAL9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1MAINTENANCE AND UPGRADE

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

409 / 5923DB 16142 EAAA Ed.02


4–1 MAINTENANCE POLICY

This chapter introduces the basic concepts for the equipment maintenance.

4–1.1 Classification of maintenance levels and operators

The maintenance procedures described in the following chapters are based on the followingconsiderations:

– The possibility of carrying out routine and corrective maintenance is based on the availability of:• a suitable set of instruments and accessories• a suitable set of spare parts

These matters are described in chapter 4–3 on page 415.

– Maintenance can be classified as:

• First Level Maintenance:

– ROUTINE (system state check)

• Second Level Maintenance:

– PREVENTIVE (periodic set of measurements and checks)– CORRECTIVE (troubleshooting and repair)

First level maintenance consists of a set of simple operations by means of which a First LevelMaintenance Operator can acknowledge the state of the system and decide whether or not theintervention of a Second Level Maintenance Operator is required in order to bring back the assemblyto optimum operating conditions by troubleshooting and unit replacement, if necessary. In thisphilosophy:

• 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 CraftTerminal, if expressly authorized by the Station Manager.

These actions are described in chapter 4–4 on page 421.

• Second Level Maintenance Operator is authorized to make all actions necessary to repairthe system; moreover he should only be authorized to carry out routine maintenance.

These actions are described in chapter 4–5 on page 429.

With regard to the access to the Craft Terminal functionalities as well as to the TCO SuiteNE–interactive functionalities, notice that it is possible to use the following operator profiles:

• viewer for the First Level Maintenance Operator• craftPerson for the Second Level Maintenance Operator.

– The two–station layout typical of a radio link requires often that different operators can communicatewith each other to solve problems. The EOW functions of this equipment give a simple way for thiscommunication need.

This matter is described in chapter 4–2 on page 413.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

410 / 592 3DB 16142 EAAA Ed.02


4–1.2 First Level Maintenance Personnel skill

First Level Maintenance Personnel must have received:

– an adequate technical background on telecommunications. Experience in first level maintenanceactivities 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 theequipment not in its normal conditions.

4–1.3 Second Level Maintenance Personnel skill

Second Level Maintenance Personnel must have received an adequate technical background ontelecommunications. 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 inpara.5–7.2.1 on page 569 is usually not enough to properly maintain equipment.

4–1.4 Troubleshooting organization

[1] The troubleshooting procedure is carried out with the help of information reported in followingchapters. Anyway this method does not deal with the following issues (which are to be dealt withotherwise):

• faulty electronic alarm indication, processing and detection circuits

• faulty wiring (back–panel, connectors, etc.)

[2] The following interfaces are present on the equipment for troubleshooting purposes:

• Ethernet interface for:– the Telecommunication Management Network ( TMN )– the Craft Terminal (Local or Remote)– the TCO Suite NE–interactive functionalities

• F interface for the Craft Terminal (Local or Remote)

• LEDs located on the NE’s units.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

411 / 5923DB 16142 EAAA Ed.02


[3] Usually, maintenance is firstly done via software (TMN or Local/Remote Craft Terminal or the TCOSuite NE–interactive functionalities) to locate the faulty equipment and the faulty unit or the faultypath 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 eachequipment 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 networkcomposed of max 128 NEs, including itself. This handbook applies to this function.

• on site.The operator is on site in case:

a ) the equipment is not managed by a TMN or by a Remote Craft terminal (RCT).b ) the equipment is not reachable by the remote manager (TMN or RCT) and therefore is

isolated.c ) link problems are present.d ) the trouble has been located and a physical replacement is necessary.

In cases a ) , b ), c ), the alarmed equipment is checked by means of the local Craft Terminal.

[4] The NE is provided with LEDs which indicate Centralized Equipment Alarms.All alarms detected on the units are collected by the IDU MAIN unit, which delivers centralizedindications (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 canbe ”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 MINORalarm 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 frontcoverplate of the IDU MAIN unit.The Craft Terminal applications provide detailed information on the alarm state thus facilitating faultlocation and subsequent removal as indicated in para. 4–5.8 on page 436.

To correctly execute the troubleshooting operations the technician must know theequipment configuration (see Equipment applications on the Craft Terminal).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

412 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

413 / 5923DB 16142 EAAA Ed.02


4–2 USE OF EOW FUNCTIONS

Please refer to chapter 4–1 on page 409 for an introduction to the basic concepts of equipmentmaintenance.This chapter explains how to configure and use the EOW (Engineering Order–Wire) function of theequipment.

4–2.1 Setting information

The EOW functions are possible only in the IDU MAIN unit configurations equipped with the AUDIO +USER SERVICE CHANNEL plug–in.

The telephone handset (P/N REF.[1] in Tab. 24. on page 96) allows to carry out EOW in/out calls at IDUside. It uses DTMF (tone) dialling.

a ) Connection diagram

ODU

Telephone handset

IDU

MAIN UNIT

STATION A

Telephone handsetOFF ON

1 2 34 5 67 8 9

#*

0

ODU

IDU

MAIN UNIT

STATION B

OFF ON

1 234 567 89

#*

0

N.B. each Telephone handset has its own phone number. Phone number can be in the 10 to99 range. Telephone handsets must have different phone numbers.

Physical connection on IDU: connect Telephone handset’s RJ11 plug to TPH connector on the IDUMAIN unit [ (7) in Fig. 21. on page 70 ].

b ) Telephone handset viewCaution: to operate, set the handset switch to “FV”.

RJ 11 connector

Set switch to “FV”

ON/OFF switch

c ) Telephone handset keyboard

KEY MEANING

* Force unlocking of the line

# Engage line

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

414 / 592 3DB 16142 EAAA Ed.02


d ) Telephone handset phone number display/setting

Display/setting is done:• by Quick Configuration Procedure (see Step J on page 366 )• or by Craft Terminal with the following menus (refer to para.2–3.4.3 on page 213 for details):

– display: Configuration ⇒ System Settings ⇒ Overhead ⇒ Phone Parameter– setting: Configuration ⇒ System Settings ⇒ Overhead ⇒ Phone Parameter ⇒ ’phone

number’ ⇒ Apply

e ) Ways of Calling : two different ways of calling are possible:

• 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 callN.B. position of green/yellow LED on IDU MAIN unit:

GREEN RED

YELLOWREDGREEN

RED

EOW

GREEN

YELLOW

RED

4–2.2 Call Set–up/End by Telephone handset connected to the IDU Main unit

a ) To Call from Handset:

1 ) Check that line is free (EOW–free green LED on the MAIN unit is on)2 ) Set Handset ON/OFF switch to “ON”3 ) On keypad, press # to engage line4 ) Check that EOW–busy yellow LED on the MAIN unit is on5 ) On keypad, dial two–digit number of station to be called (or 00 for omnibus call)6 ) Ring tone is audible in the handset, wait for answer

b ) To Answer Call at Handset:

1 ) EOW–busy yellow LED on the MAIN unit flashes and audible tone is present2 ) 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”

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

415 / 5923DB 16142 EAAA Ed.02


4–3 MAINTENANCE TOOLS AND SPARE PARTS


Please refer to chapter 4–1 on page 409 for an introduction to the basic concepts of equipmentmaintenance.

This chapter describes the instruments, accessories and the equipment spare parts that are envisagedto carry out the routine and corrective maintenance of the equipment, and and is organized as follows:

– Instruments and accessories herebelow, including:• Software tools herebelow• Maintenance, Installation and Station Tool Kits on page 416

– Set of spare parts on page 418, including:• Types of Spare Parts on page 418• Number of Spare Parts on page 419• General rules on spare parts management on page 419

4–3.2 Instruments and accessories

4–3.2.1 Software tools

There is a local Craft Terminal (PC) which permits to display all the alarms and which manages theEquipment. Its whole implementation is described in the SECTION 2 (NE MANAGEMENT BY TCO SUITEAND CRAFT TERMINAL) on page 139, while its use for troubleshooting is summed–up in para.4–5.8 onpage 436.

When a TMN is implemented, an Operation System will display alarms and manage all the connectedEquipment of the network. Refer to the relevant handbooks.

Please refer to para.2–2.4.1 on page 170 for an overview on the physical interfaces for the NEmanagement.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

416 / 592 3DB 16142 EAAA Ed.02


4–3.2.2 Maintenance, Installation and Station Tool Kits

For the P/Ns of these Tool Kits, please see REF.[2] , [3] and [4] in Tab. 24. on page 96 .

a ) The Installation Tool Kit includes various types of common usage fixed spanners, standard andcrosshead screwdrivers, polygon spanners, polygon tube spanners, special fixed spanners, a torquewrench, etc.

b ) The Maintenance Tool Kit is practically equal to the Station Tool Kit, with the addition of theAntistatic wrist–band.

c ) The Station Tool Kit is a bag additionally containing various types of cables and cable adapters.

The detailed item list of these Tool Kits is given in Appendix F from page 563 :

• Installation Tool Kit part list, para.5–6.1 on page 563

• MaintenanceTool Kit part list, para.5–6.2 on page 564

• StationTool Kit part list, para.5–6.3 on page 565

N.B. These Tool Kits are standardized kits for the use with all Alcatel–Lucent WTD equipment types:they contain also items that are not used in 9400AWY environment (they are not described inthis manual).

Some special items are listed in Tab. 66. below, which gives also reference to figures where they aredepicted.

Tab. 66. Special items of the Tool Kits

SPECIAL ITEM DESCRIPTION

COMPONENTS OF ANTISTATIC WRIST–BAND

Antistatic wrist–band

Antistatic applications cordFig. 1. on page 36

Plug with crocodile pliersFig. 1. on page 36

Female button termination

SPECIAL EXTRACTORS

Unhook tool for 1.0/2.3 coax Fig. 295. below

SPECIAL TOOLS AND ITEMS FOR ODU

Lever for ODU mounting/dismounting Fig. 296. on page 417

Fig. 295. Special extractor to remove the coaxial cables 1.0/2.3

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

417 / 5923DB 16142 EAAA Ed.02


A

C

B

When, in ODU configurations 1+1 with coupler, you must dismount and then mount one of thetwo ODUs for maintenance purposes, the following operations:

UNBLOCK BEFORE DISMOUNTOne 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 MOUNTBlock the four ODU blocking levers (A)

may produce vibrations that could cause synch loss or other electrical disturbances to the otherODU still working.

Using the special lever:

allows to do the same unblock/block operations without producing vibrations.The following photographs should clarify the correct lever handling and usage.

Fig. 296. Lever for ODU mounting/dismounting

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

418 / 592 3DB 16142 EAAA Ed.02


4–3.3 Set of spare parts

4–3.3.1 Types of Spare Parts

The unit replacement procedures described in paragraph Corrective Maintenance of chapter SecondLevel Maintenance in this section presume that the units present in the spare–part stock correspondexactly to the plug–in replaceable units that are equipped in the system (i.e. with the same Part Number).

4–3.3.2 ODU Spare Parts

The suggested spare parts should be at least those containing electronic parts; in general the spare parttypes are:

– for ODUs with embedded diplexer: the complete ODU.For the P/Ns refer to para. 1–4.5.2 on page 108.

– for ODUs with external diplexer: the TRANSCEIVER assembly. For the P/Ns refer to:• Tab. 27. on page 106 (7 GHz)• Tab. 29. on page 107 (8 GHz)

As a matter of fact, all other ODU–related items listed in Chapter 1–4 on page 97 (but whose P/Ns aregiven in the Installation Handbook) can be considered items to be provisioned as spare parts.

4–3.3.3 IDU Spare Parts

The set of spare parts for the IDU is inclusive of a minimum number of spares for each type of replaceableunits. The suggested spare parts should be at least those containing electronic parts; in general the sparepart types are:

– IDU Main unit, for both (1+0) and (1+1) systems

– IDU Extension unit, for (1+1) systems only

– Flash card, for both (1+0) and (1+1) systems

As a matter of fact, also passive items (whose P/Ns are given in the Installation Handbook) can beconsidered items to be provisioned as spare parts.

a ) Spare parts for IDU Main and Extension units

For P/Ns, refer to para.1–3.1 on page 68.

N.B. In case a terminal has IDU Main and/or Extension units equipped with plug–in(s), and youorder as spare parts such units separately from the plug–in(s), take into account that, whenthe IDU Main or Extension faulty unit must be replaced, the spare part box has first to beopened, then the plug–in must be installed, at last box must be closed.

b ) Spare parts for Flash Card

There are various possible types of Flash Cards. For details refer to para.1–3.7 on page 93 .

For the spare–part–stock, Customer should provision at least one Flash Card for each type (P/N) ofFlash Card equipped in systems in service. For cost saving, as alternative to provision the varioustypes, that with Software Label 64Mb 16 QAM could be provisioned instead.

N.B. Read important information regarding the spare Flash Card management in para.4–6.1on page 465.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

419 / 5923DB 16142 EAAA Ed.02


4–3.3.4 Number of spare parts

The overall number of spares depends on Customer requirements, and should be based on the averageamount of transmission circuits available to be accounted for not only during MTBF (Mean Time BetweenFailures) but also during MTTR (Mean Time To Repair); the latter depending on the amount of spare partsavailable.

4–3.3.5 General rules on spare parts management

Before storing the spare units make sure that they are working by inserting them in an operatingequipment.

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 partsare placed in cabinets to safeguard them from dust and damp.

Moreover, they should also be well grounded to avoid electrostatic discharges.

If the spare parts are stored in another room, or have to be moved from another place, building or site,make sure that the following is observed:

– the spare parts must be wrapped in anti–static and padded envelopes;

– the spare parts must not touch wet surfaces or chemical agents that might damage them (e.g. gas);

– if during transportation the temperature is lower than that of the room where they had been kept,make sure that before using them they pass a certain period in a climatic chamber to prevent thermalshocks and/or the possibility of steaming up.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

420 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

421 / 5923DB 16142 EAAA Ed.02


4–4 FIRST LEVEL MAINTENANCE


Please refer to chapter 4–1 on page 409 for an introduction to the basic concepts of equipmentmaintenance.

This chapter describes the First Level Maintenance of the equipment and is organized as follows:

– System state display by visual indications, below

– TCO Suite and Craft Terminal commonly used functions for system status display andchecks, on page 423

4–4.2 System state display by visual indications

4–4.2.1 LED test

To be sure to have correct indications, carry out the LED test of IDU MAIN unit, pushing pushbutton (9)in Fig. 298. on page 422: while pushed, all leds of the MAIN unit should be turned on.

In 1+1 system, perform the same test also on the IDU Extension Unit, pushing pushbutton (6) inFig. 297. below: while pushed, all leds of EXTENSION unit should be turned on.

4–4.2.2 Alarm LEDs on the IDU MAIN unit

All the alarms detected on the units are collected and processed by the IDU MAIN unit which givescentralized optical indications by means of LEDs on its front coverplate, as shown in Fig. 298. on page422.

4–4.2.3 Alarm LEDs on the Extension unit

(3) LED test

(2) ON/OFF switch

GREEN

LED Normal status

ON (green) ON (if the ON/OFF switch is on)

Fig. 297. LEDs and pushbutton on IDU Extension unit for maintenance purposes

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

422 / 592 3DB 16142 EAAA Ed.02


(10) Reset

(11) LED test(9) Alarm attending

(2) ON/OFF switch

(12) F interface forCraft Terminal

(3) Ethernet (orOS) interfacefor Craft Terminal

GREEN

YELLOW

RED

RED

RED

RED

LED on Meaning Action

Green LED ONIf off (and if the ON/OFF switch is on) there is a problem in the stationbattery or in the MAIN unit

A

Red LED LDI There is a failure in the equipment A

Red LED RDI There is a failure in the remote station A

Red LED MAJDetection of an URGENT alarm: it means that there is at least onealarm (internal and/or external) for which traffic is affected.

A

Red LED MIN

Detection of a NOT URGENT alarm: it means that there is at least onealarm (internal and/or external) for which traffic is not affected (e.g.something is wrong, but the traffic is recovered by an automaticprotection switch).

B

Yellow LED ATTDAlarm condition ATTENDED: it means that an Operator (by pushbutton(8) or by Craft Terminal) has attended the alarm (for details, see para.4–5.6.2 on page 434).

B

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. 298. LEDs and pushbutton on IDU MAIN unit for maintenance purposes

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

423 / 5923DB 16142 EAAA Ed.02


4–4.3 TCO Suite and Craft Terminal commonly used functions for systemstatus display and checks

This paragraph sums up how to use the TCO Suite and Craft Terminal functions for system status displayand checks to be carried out by a First Level Maintenance Operator.

N.B. These operations should be done by the First Level Maintenance Operator only if expresslyauthorized by the Station Manager, who, in his turn, for each 9400AWY NE that should beaccessible by the First Level Maintenance Operator must:– assign him a Username/Password set– in case of remote NE, communicate him the NE’s IP address.

4–4.3.1 Viewing the NE alarms by TCO Suite

Proceed as follows:

1 ) start–up the TCO Suite Alarms & Settings function as explained in para.2–2.3.1 on page 156,using:– the NE’s IP address (if remote NE)– the Username and Passwordcommunicated by the Station Manager

2 ) in the Alarms & Settings Main Menu screen that appears (Fig. 64. on page 157), click on buttonActive Alarms

3 ) refer to para.2–2.3.6 on page 165 for the alarm screen interpretation.

4 ) at the end, close the TCO Suite Alarms & Settings – Active Alarms screen.

4–4.3.2 Viewing the NE status by Craft Terminal

Proceed as follows:

1 ) login the NE as explained in para.2–2.5.2 on page 173, using:– the NE’s IP address (if remote NE)– the Username and Passwordcommunicated by the Station Manager.

2 ) the 9400AWY Main view opens (see Fig. 87. on page 181).From this screen, according to the user profile assigned through the enteredUsername/Password set, you can navigate to make some checks. Suggested checks are:

a ) Summary Block Diagram viewProceed as follows:

• Click on button in the Main tool bar (see Fig. 87. and Fig. 88. on pages181–183)

• for screen interpretation, refer to para.2–11.5 on page 285.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

424 / 592 3DB 16142 EAAA Ed.02


b ) Checks on Radio domainVarious checks are possible selecting the specific matters of the Menu bar, as shown infollowing Fig. 299. to Fig. 304. For screen interpretation, click on their relevant HELP button and/or refer to chapter 2–6on page 233.

3 ) at the end:– first, carry out the NE Logoff as explained in para.2–2.5.3 on page 180– then, close the 1320CT application as explained in para.2–2.5.4 on page 180.

RADIO MENU BAR

Fig. 299. Checks on Radio domain : Alarms

Fig. 300. Checks on Radio domain : Configuration

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

425 / 5923DB 16142 EAAA Ed.02


Fig. 301. Checks on Radio domain : Frequency

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

426 / 592 3DB 16142 EAAA Ed.02


Fig. 302. Checks on Radio domain : RTPC & ATPC

Fig. 303. Checks on Radio domain : non–intrusive BER measurement

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

427 / 5923DB 16142 EAAA Ed.02


Fig. 304. Checks on Radio domain : Power Measurement

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

428 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

429 / 5923DB 16142 EAAA Ed.02


4–5 SECOND LEVEL MAINTENANCE


Please refer to chapter 4–1 on page 409 for an introduction to the basic concepts of equipmentmaintenance.Second level maintenance consists of a set of operations which maintain or bring back the assembly tooptimum operating conditions in a very short time, with the aim of obtaining maximum operationalavailability.Second level maintenance is classified as:– ROUTINE or PREVENTIVE (periodic set of measurements and checks, independently of troubles)– CORRECTIVE (troubleshooting and repair, in case of troubles)

This chapter describes the routine and corrective maintenance operations and is organized as follows:

– Warnings on page 430, including:• EMC norms• Safety rules• Cautions to avoid equipment damage

– Routine (preventive) Maintenance on page 431– Consequences of unit extraction in the IDU on page 432– Corrective Maintenance general flow–chart on page 433– Alarm acknowledgment and attending on page 434– Trouble–Shooting starting with visual indications on page 435– Trouble–Shooting via Craft Terminal on page 436

• Alarm and status synthesis indications on page 437• Details on alarms / statuses on page 439• Description of alarms and of probable causes on page 440

– Hints on the troubleshooting on page 442– IDU Unit replacement on page 451– ODU replacement on page 460– Faulty unit repair and Repair Form on page 463

The handbook parts that should be read (or known) before starting this chapter are:

– chapter 1–2 on page 37 System overview– chapter 1–3 on page 67 IDU provisioning and description– chapter 1–4 on page 97 ODU provisioning, characteristics and description– chapter 4–1 on page 409 Maintenance Policy– chapter 4–3 on page 415 Maintenance Tools and Spare Parts– chapter 4–4 on page 421 First Level Maintenance

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

430 / 592 3DB 16142 EAAA Ed.02


4–5.2 Warnings

4–5.2.1 EMC norms

ATTENTION EMC NORMS

WHEN CARRYING OUT THE GIVEN OPERATIONS OBSERVE THE NORMS STATED IN PARA.5–1.4.3 ON PAGE 509

4–5.2.2 Safety rules

The Safety Rules stated in para.5–1.3 on page 502 describe the operations and/or precautions to observeto safeguard operating personnel during the working phases and to guarantee equipment safety.Please read them carefully before starting each action on the equipment.

SAFETY RULES

General

Carefully observe the front–panel warning labels prior to working on opticalconnections while the equipment is in–service.

Should it be necessary to cut off power during the maintenance phase, proceedto switch off the power supply units as well as cut off power station upstream(rack or station distribution frame)

Electrical safety

DANGER: Possibility of personal injury. Personal injury can be caused by–48 V DC.

DANGER: Possibility of personal injury. Short circuiting, low–voltage,low–impedance, DC circuits can cause severe arcing that can result in burnsand/or eye damage. Remove rings, watches, and other metal jewelry beforeworking with primary circuits. Exercise caution to avoid shorting power inputterminals.

4–5.2.3 Cautions to avoid equipment damage

Read carefully para.1–1.6 on page 36.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

431 / 5923DB 16142 EAAA Ed.02


4–5.3 Routine (preventive) Maintenance

Routine maintenance is a periodic set of measurements and checks. This maintenance discovers thosedevices 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 andobtaining performance data.The Performance Monitoring Application, described in para. 4–5.8.4 on page 441, allows this function.

4–5.3.1 Routine (preventive) Maintenance every year

It is suggested to carry out the following operations yearly:

[1] Mechanical checksCheck that:• the units,• the cables,• the mounting fixturesare inserted and connected correctly.

[2] Grounding checkCheck that the racks, subracks, and modules are grounded (for 9400AWY shelves, see para.5–1.3.6on page 506).

[3] Power cables check

SAFETY RULES

DANGER: Possibility of personal injury. Personal injury can be caused by–48 V DC.

DANGER: Possibility of personal injury. Short circuiting, low–voltage,low–impedance, DC circuits can cause severe arcing that can result in burnsand/or eye damage. Remove rings, watches, and other metal jewelry beforeworking with primary circuits. Exercise caution to avoid shorting power inputterminals.

Make these operations:• Check that the power cable is perfectly safety grounded.• Make sure that the subrack has been tightly fastened to the rack with screws, to guarantee

grounding (the rack is connected to the station ground).

[4] Operative checks

• Visual check:– During the normal operation, check the led normal condition, as specified in para.4–4.2

on page 421.

• Checks by Craft Terminal– some suggested checks are indicated in para.4–4.3 on page 423– the commissioning tests, described in Chapter 3–2 on page 329, can be useful to carry

out equipment functional checks as a whole, in particular as far as checks on radio hopare concerned.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

432 / 592 3DB 16142 EAAA Ed.02


4–5.4 Consequences of unit extraction in the IDU

Generally, a unit can be extracted from the system for the following reasons:

– to replace it with a spare part during corrective maintenance

– to check a spare part taken from the spare part stock

– to restore the suspected faulty unit (after its successful replacement with a spare unit duringcorrective maintenance) to verify that it is really faulty.

The extraction of a unit has always some consequences on system behavior and performance that theMaintenance 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 strictlynecessary 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 theExtension 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 strictlynecessary 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 MAINunit). Otherwise, force with the CT the traffic onto channel 1.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

433 / 5923DB 16142 EAAA Ed.02


4–5.5 Corrective Maintenance general flow–chart

Fault repaired ?Try again withanother unit

If possible, restore replaced unit in the system and performsystem check via Craft Terminal, to verify that is really faulty

Y

N

Possible intermittentfailure

Fixed fault ?N

Send back faulty unit to Repair Centre together withRepair Form compiled (para.4–5.12 on page 463)

START

END

Restore spare part in the system and performsystem check via Craft Terminal

Y

Alarm acknowledgment and attending(para.4–5.6 page 434)

Trouble–Shooting starting with visual indications(para.4–5.7 page 435)

IDU unit replacement (para.4–5.10 page 451)

ODU replacement(para.4–5.11 page 460)

System check via Craft Terminal

Trouble–Shooting starting via Craft Terminal(para.4–5.8 page 436).

Identification of a unit to be replaced.

Fig. 305. Corrective Maintenance general flow–chart

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

434 / 592 3DB 16142 EAAA Ed.02


4–5.6 Alarm acknowledgment and attending

4–5.6.1 Alarm acknowledgment

Refer to Fig. 305. on page 433, for the position of this step inside the corrective maintenance generalflow–chart.

The need for Operator intervention is notified:

– locally (on the front of the equipment or in the station):

• when one of the alarm LEDs MAJ – MIN on the MAIN unit front plate lights up.

– remotely (in a TMN maintenance center) when the OS acknowledges the presence of problems inthe station.

When the local Operator decides to manage the problem, he should carry out the alarm attendingoperation (see para. 4–5.6.2 below). This operation has the scope of notifying locally in the station andremotely to the TMN maintenance center that a local operator is attending the problem.

4–5.6.2 Alarm Attending

See Fig. 298. on page 422:

– the detected alarm condition can be stored through the Alarm attending push–button on the MAINunit.

This operation will turn OFF the LEDs MAJ / MIN and will light up the yellow LED ATTD on the MAINunit (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 turnoff.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

435 / 5923DB 16142 EAAA Ed.02


4–5.7 Troubleshooting starting with visual indications


Some problems may be localized through the LEDs indicated in para. 4–4.2 on page 421.

In any case, the inspection through the Craft Terminal is recommended before any unit replacement.

Flow–chart of Fig. 306. indicates LEDs on the MAIN unit that should be considered first.

Y

MAJOR, MINOR,LDI or RDI LEDon the MAIN unitis “ON”

START

Try login NE by Craft Terminal

Login successful ?N Y

Carry out procedure inpara.4–5.8 page 436

NEND

Carry out procedure inpara.4–5.9.1 page 442

Fig. 306. Troubleshooting starting with visual indications

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

436 / 592 3DB 16142 EAAA Ed.02


4–5.8 Troubleshooting via Craft Terminal


The ECT/RECT application includes several types of functions for system maintenance (used incommissioning operations, too), as depicted in the following table:

FUNCTION FUNCTION DESCRIPTION

Diagnosis para.4–5.8.1 below

Alarm surveillance para.4–5.8.2 on page 437

Loopbacks para. 4–5.8.3 on page 441

Operator’s Controls of the protection switches para. 4–5.8.4 on page 441

Tx mute functions para. 4–5.8.5 on page 441

Performance Monitoring para. 4–5.8.6 on page 441

BER measurement para. 4–5.8.7 on page 441

Commissioning tests para. 4–5.8.8 on page 441

The operating instructions make it possible to identify the faulty unit.Having located the suspected faulty unit, replace it with a spare one (refer to para.4–5.10 on page 451for IDU, or to para.4–5.11 page 460 for ODU).

4–5.8.1 Diagnosis

The options available in the Diagnosis menu are:

– Current Configuration View– Summary Block Diagram View: displays a global logical view (strictly related to the physical

implementation) highlighting a synthesis of all the alarms and statuses present in the system(ODU+IDU).

– Abnormal Condition List– Remote Inventory– Event Log

The generic events occurred and discriminated by the NE are stored in one or more Event Log files.The ELB (Event Log Browsing) application embedded in the 9400AWY SWP allows the Operator toread such log files, in order to have historical data that can be useful to troubleshoot the equipmentor the link or the PDH network, in case of multiple alarm conditions or intermittent alarms.N.B. The event log file examination is quite complex; it is reserved to Alcatel–Lucent

skilled personnel as a debug tool (only using filters on the not meaningful events,it is possible to understand the meaning of the stored data).

For further information and operative procedures, refer to the Chapter 2–11 on page 277.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

437 / 5923DB 16142 EAAA Ed.02


4–5.8.2 Alarm surveillance

The Alarm surveillance available with the CT allow the Operator to examine the alarms currently present inthe equipment or in the link or in the PDH network.

The information on the NE alarm will be mainly obtained by means of the Craft Terminal through the Alarmtab panel data.

The troubleshooting procedure is the following.

a ) Look at the active alarms on the Control Panel always present on the window (which summarizesall the NE alarms). Tab. 67. on page 438 describes the meanings of these alarms/statuses and itsrespective maintenance actions.

b ) In case of alarm, access the Alarm tab panel for troubleshooting.Para 4–5.8.2.2 on page 439 explains how to see the alarms.

MAJOR alarm indicates a severe alarm that could affect the current traffic (interrupt ordegrade). Hence, a prompt intervention is necessary to restore the regular operatingcondition of the equipment.

4–5.8.2.1 Alarm and status synthesis indications

The following Tab. 67. pertains to the alarm and status synthesis given in all the screens, pointed out inthis Fig. 307. :

Fig. 307. Alarm and status synthesis indications

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

438 / 592 3DB 16142 EAAA Ed.02


Tab. 67. Alarm Synthesis indications

Mnemonic Alarm / Status Description Maintenance

CRI Critical alarmSynthesis of alarms that needs immediatetroubleshooting (typical: NE isolation). (N.B.)

MAJ Major (Urgent) alarm Synthesis of alarms that needs immediateMAJ Major (Urgent) alarm Synthesis of alarms that needs immediatetroubleshooting. (N.B.)

MIN Minor (Not urgent) alarmSynthesis of alarms for which a deferred interventioncan be decided. (N.B.)

WNG Warning alarmSynthesis of alarms due to failure of other NE in thenetwork. (N.B.)

IND Indeterminate alarmSynthesis of alarms not associated with the previousseverities. Not operative.

EXTExternal Point(Housekeeping alarm)

Check the relevant station alarm associated with theinput housekeeping indication.

EQP Equipment alarm Synthesis of alarms of the Equipment domain.

TRS Transmission alarm Synthesis of alarms of the Transmission domain.

Local Access state(see para.2–11.2 on page 279)

GREEN LED: Indicates that the Craft Terminal hasthe OS permission to manage the NE (granted).CYAN LED: Indicates that the Craft Terminal has notthe OS permission to manage the NE (denied).

COM NE reachable/unreachable

GREEN LED: Identifies the “ Enable “ operationalstate of the connection between NE and Craft Terminal( SDH service link up ).RED LED: Identified the “ Disable ” operational stateof the connection between NE and Craft Terminal( service link down ).

SUP Supervision stateGREEN LED: NE is under supervision.BROWN LED: NE is not under supervision.Used in the OS.

ALI AlignmentAlignment status of the SH MIB respect to theequipment MIB.

OSOperation System(see para.2–11.2 on page 279)

GREEN LED: Indicates that the N.E. is not managed bythe 1353NM/SH.CYAN LED: Indicates that the N.E. is managed by the1353NM/SH.

NTP Network Time Protocol

GREEN LED: NTP protocol enabled and both NTPservers ( Main and Spare ) are unreachable.BROWN LED: NTP protocol disabled.CYAN LED: NTP protocol enabled and at least one NTPservers ( Main or Spare ) are reachable.

AC Abnormal ConditionGREEN LED: Normal operating condition.CYAN LED: Detection of an ABNORMAL operativecondition. Type: switch forcing.

N.B. The Alarm Profile can modify the assignment of each alarm root to the various synthesis.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

439 / 5923DB 16142 EAAA Ed.02


4–5.8.2.2 Details on alarms / statuses

The troubleshooting proceeds by checking the detailed information on the NE active alarms using the CraftTerminal as in Fig. 308. below.It is also possible to analyze the detailed alarms present on each TP of the Port views of the NE.

[1] Select the Equipment tab panel.

[2] Select one node (or sub–node) in the Resource Tree Area to check if some alarms are active.

[3] Select the Alarm tab panel in the Resource Detail Area.

[4] If the node has sub–nodes put a tick in the Include alarms from sub–nodes field to display thealarms active also in the sub–nodes.

[1]

[2]

[3][4]

Fig. 308. Active alarm screen

Detailed information of some alarms are supplied.The following table summarizes the information obtained in the Alarm view, starting from the left column.

Tab. 68. Alarm information, general description

TITLE DESCRIPTION

Severity severity associated to the alarm and assigned in the Alarm Profile

Event time time of the generation of the alarm

Entity entity involved in the alarm

Probable Cause probable cause of the alarm

Managed Object Class class of the alarm

The information supplied helps the operator during the troubleshooting operations.Tab. 69. on page 440 supplies general information on the alarm meanings and on the respectivemaintenance 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

440 / 592 3DB 16142 EAAA Ed.02


4–5.8.2.3 Description of alarms and of probable causes

The information provided helps the operator during troubleshooting operations.

Tab. 69. General issues of the alarm meanings and their respective maintenance actions

ALARM MEANING MAINTENANCE ACTION

AISAIS detection on the tributary in Txside or Rx side

Check the tributary connectedequipment

ATPC loop problem Problem on the ATPC loop Communication problem

Battery fail Problem on the Station Battery Check the Station Battery

High BER Excessive BERExcessive errors. Check the link(propagation problem)

Dem failDemodulator failure affecting thedemodulated signal

Replace the ODU

Dem LOSLoss of the incoming signal at thedemodulator input

Check the link (propagationproblem)

Cable LOS Problem on the cable or on the ODUReplace the ODU; if the alarm is stillactive replace the cable.

Incompatible FrequencyFrequency setting incompatible withthe ODU P/N

Change the frequency or change theODU

Incompatible PTX Output power out of the limits Replace the ODU

Internal CommunicationProblem

ODU not respondingPress the Reset pushbutton on theMAIN unit. If the alarm is still active,replace the ODU

LAN failure LAN problemCheck the LAN connection orreplace the MAIN unit

Link Identifier Mismatch Mismatch on the link identifier

Check the correct connection of thecable between the IDU and therelevant ODU. If the connection iscorrect, check the link (propagationproblem)

Loss Of Frame

LOF at the Tx tributary input or at Rxtributary output (with framedtributary) or LOF of the Rxaggregate signal

Check the tributary connectedequipment or the line

Loss Of Frame (Aggregatesignal)

LOF of the Rx aggregate signal Check the link (errors)

Loss Of Signal LOS at the Tx tributary input Check the line

Low BER Low BER at the Rx sideCheck the link (propagationproblem)

Mod failInternal modulator failure affectingthe modulated signal

Replace the ODU

Mod LOS No signal at the modulator inputInvestigate by using the loopbackfacilities 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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

441 / 5923DB 16142 EAAA Ed.02


Tab. 69. General issues of the alarm meanings and their respective maintenance actions

ALARM MEANING MAINTENANCE ACTION

Replaceable Unit TypeMismatch

Mismatch between the installed unitand the sw configured unit

Change the unit configuration orchange the unit

Replaceable Unit Type Missing No unit in a configured slot Install the unit

Rx Fail (Radio alarm) No RF received signalCheck the link (propagationproblem)

Threshold CrossPerformance threshold has beencrossed

Errors on the link

Tx Fail (Radio alarm) Transmitter failure Replace the ODU

Unconfigured EquipmentPresent

Unit present in an unconfigured slot Configure the unit

Version MismatchMismatch on the software versionbetween CT software andequipment software

Download the software version

Housekeeping Active input housekeeping Check the housekeeping

4–5.8.3 Loopbacks

The loopbacks (settable by CT) give the possibility to perform some functional tests, thus making the faultlocation and maintenance tests faster and easier. The loopbacks are explained in Chapter 2–10 on page267.

4–5.8.4 Operator’s Controls of the protection switches

In certain troubleshooting conditions, changing the state of the protection switches can be useful to fixproblems.For further information and operative procedures, refer to the Chapter 2–9 on page 257.

4–5.8.5 Tx mute function (local and remote)

This facility allows to switch off the transmitter. This facility can be useful during commissioning to avoidproducing interference if the frequency is not yet properly set.For further information and operative procedures, refer to the Chapter 2–6 on page 233.

4–5.8.6 Performance Monitoring

The Performance Monitoring is responsible for quality events counting and reporting.For further information and operative procedures, please refer to the Chapter 2–12 on page 289.

4–5.8.7 BER measurement

The BER measurement (noon–intrusive) can be carried out as described in para.2–6.6 on page 246

4–5.8.8 Commissioning tests

In some cases, the commissioning tests, described in Chapter 3–2 on page 329, can be useful to carry outequipment functional checks as a whole, in particular as far as checks on radio hop are concerned.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

442 / 592 3DB 16142 EAAA Ed.02


4–5.9 Hints on the troubleshooting

This paragraph gives hints on following matters:– Problems with the Craft Terminal below

• PC restart• Craft Terminal not working on NE’s local Ethernet interface on page 443• Craft Terminal not working on NE’s F–interface on page 444• Craft Terminal blocked on page 445• Checks before MAIN unit or FLASH CARD replacement on page 445

– Analog measurements on page 446– NMS 64 kbit/s V.11 and G.703– Loopbacks– Empty USM icon in NES on page 447– Remote NE unreachable– Configuration change from 4 QAM to 16 QAM– Quick configuration menu correct use on page 447– Abnormal condition list– Tx Mute functionality for interferences investigation on page 449– Tributaries 17 to 32 visible in “16E1+Ethernet” configuration on page 450

4–5.9.1 Problems with the Craft Terminal

With regard to the PC maintenance, refer to the constructor’s documentation.

4–5.9.1.1 PC restart

Should the Craft Terminal Software Product not be working properly or not responding to the operator’scommands, to shutdown and restart the PC , proceed as follows:

– if possible, close the 1320CT application, after having verified that all NEs in the Network ElementSynthesis map are in not supervised state

– in order to shutdown the PC execute the command :

Start > Shutdown

A window (Windows NT Security user dialog) is displayed. It permits to shutdown the computer orrestart it.The same window is displayed pressing the keys <Ctrl> + <Alt> + <Del> simultaneously.

N.B. In the case this procedure is unsuccessful for successive NE login, carry out the checksindicated in following paragraphs 4–5.9.1.2 (Ethernet interface usage) or 4–5.9.1.3 (F interfaceusage), till paragraph 4–5.9.1.5 on page 445.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

443 / 5923DB 16142 EAAA Ed.02


4–5.9.1.2 Craft Terminal not working on NE’s local Ethernet interface

Proceed with the following checks:

– Verify that the CT Ethernet port is effectively that connected by a cross–connect cable to the MAINUNIT Ethernet interface on the left (see Fig. 76. on page 170; that on the right is not for CT interface).

– Restart the Craft Terminal (NE logout, PC switch off/on, NE login).N.B. To carry out NE login, do not use Start ⇒ Alcatel 1320CT, but click the button Operational

& Maintenance of the TCO Suite Main Menu (see Fig. 55. and Fig. 56. on page 149),and answer to question of Fig. 77. on page 174 specifying Ethernet interface usage.

– Disconnect and then reconnect, at PC side, the Ethernet cable; this message should arise atre–connection:

Otherwise:• the cable could not be the required cross–connect type (see Tab. 54. on page 144), or it could

be broken• PC Ethernet port faulty• MAIN unit Ethernet port faulty

If possible, verify the correct working of the Craft Terminal and of the Ethernet cable using them withanother Alcatel–Lucent equipment. If the problem still persists, solve the problem.Otherwise, before replacing the MAIN UNIT or the FLASH CARD, perform steps indicated inpara.4–5.9.1.5 on page 445.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

444 / 592 3DB 16142 EAAA Ed.02


4–5.9.1.3 Craft Terminal not working on NE’s F–interface

Proceed with the following checks:

– Verify that the CT serial port is effectively that connected by cable to equipment’s F interface and thatcable is correctly connected.

– In Windows, verify that the possible selection Start ⇒ Programs ⇒ Alcatel ⇒ Lower Layers doesexist; if not, the installation and configuration of LLMAN and Alcatel Virtual Network Card for LowerLayers (necessary for PC–NE F–interface usage) has not been carried out: refer to Appendix C onpage 517 to know what to do.

– Check for the “Network Connections” order (para.5–3.3.6 on page 546).

– Restart the Craft Terminal (NE logout, PC switch off/on, NE login).N.B. To carry out NE login, do not use Start ⇒ Alcatel 1320CT, but click the button Operational

& Maintenance of the TCO Suite Main Menu (see Fig. 55. and Fig. 56. on page 149),and answer to question of Fig. 77. on page 174 specifying F interface usage.

– Check that speed is the same:• at PC side (see para.5–5.7.3 on page 562)• at NE side through the TCO Suite Alarms & Settings function (see para.2–2.3.1 on page 156,

and para.2–2.3.9 on page 167).

– With the Craft Terminal connected to the equipment F–interface, open the ’Alcatel Lower Layer

Manager’ screen (by clicking with the mouse pointer on the Alcatel symbol in the MS–Windowsmenu bar, or by Start ⇒ Programs ⇒ Alcatel ⇒ Lower Layers ⇒ Lower Layers Manager, andinterpret the various fields of the screen that opens (Fig. 309. below) as described in the 1320CTBasic Craft Terminal Operator’s Handbook (see Tab. 78. on page 571), chapter SoftwareInstallation, paragraph Communication with NE.

Link led

Fig. 309. Lower Layers Manager screen

– If the ’Link led’ is red (i.e. OFF), the problem can be due to:• PC serial physical port faulty• MAIN unit F–interface port faulty• the cable• FLASH CARD missing on MAIN unit (verify) or FLASH CARD/MAIN faulty

If possible, verify the correct working of the Craft Terminal and of the serial cable using them withanother Alcatel–Lucent equipment. If the problem still persists, solve the problem.Otherwise, before replacing the MAIN UNIT or the FLASH CARD, perform steps indicated inpara.4–5.9.1.5 on page 445.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

445 / 5923DB 16142 EAAA Ed.02


4–5.9.1.4 Craft Terminal blocked

In some situations, the CT is blocked (not temporarily) and, even if 1320CT application is closed byTask–Manager and then re–launched again, the following message could arise:

Another instance of the system probably running . Do you really to continue setting?

Answering yes, you enter in Network Element Synthesis, but in this case continuos Autorestart trouble/ Cannot autorestart program are received and the successive start of supervision fails.

If you decide to close again the CT in correct way and re–launch again the 1320CT application, nosignaling of errors are present but the condition does not change (CT is still blocked)

In this situation, there are two solutions:

a ) logging–out and then relogging–in Windows session, thus terminating all active applications

b ) or, if you do not want to close all applications, terminating manually all CT single processes byTask–Manager. The list of processes to be terminated is:• acdbm.exe• FTclient.exe• FTserver.exe• java.exe• LLman.exe• lss.exe• nesim.exe• nspd.exe• secim.exe• admctemlimosi.exe• dxcctemlimosi.exe• tsdsnmpemlim.exeN.B. pay attention not to terminate other processes !

4–5.9.1.5 Checks before MAIN unit or FLASH CARD replacement

If the Craft Terminal application does not respond (login unsuccessful):

1 ) push the RESET button on the MAIN unit and wait 10 minutes;

2 ) if, after 10 minutes, the Craft Terminal application responds, open the ”Alarm status” procedureand proceed investigating the system state;

3 ) if, after 10 minutes, the Craft Terminal application does not respond, replace the MAIN unit, asindicated in para.4–5.10.1 on page 452.

4 ) if the problem still persists after the MAIN unit has been replaced, the failure or contentcorruption of the FLASH CARD must be suspected (a very extraordinary event); proceed withits replacement, as indicated in para.4–6.2 on page 466.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

446 / 592 3DB 16142 EAAA Ed.02


4–5.9.2 Analog measurements

In case of two CT connected to the NE, as shown in the figure below, and at the same time both open onthe menu Radio → Power Meas, the analog measurements relevant to the PTx rem (Tx power of theRemote NE) and the PRx rem (Rx power of the Remote NE) could have some instabilities (i.e. anintermittent +99 dBm is reported for the PTx rem and –99 dBm is reported for the PRx rem).

ODU

Station AIDU

Station BIDU

ODU

4–5.9.3 NMS 64 kbit/s V.11 and G.703

For a correct operation the NMS channel has to be configured in one station as ”DTE” and in the otherstation as ”Codirectional”.

This selection can be done in the Quick Configuration Procedure’s Step H on page 362

4–5.9.4 Loopbacks

For a correct activation of every loopback (Loopback menu):

– the relevant tributary must be enabled (Quick Configuration Procedure’s Step H point [1] on page349 )

– the local transmitter must be not muted (CT Menu Radio → Configuration)

Note 1: The loopback will become active after 6–7 sec. approx. (24 sec. approx. for the RF loopback).

Note 2: The time for a new set is 10 to 25 sec. approx.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

447 / 5923DB 16142 EAAA Ed.02


4–5.9.5 Empty USM icon in NES

Enter Windows Task Manager and stop the process relevant to the empty USM.

4–5.9.6 Remote NE unreachable

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

– The USM must be closed.

In the NES will appear a broken icon and a red bullet:

– Wait for the automatic restarting of the Supervision (at the end of the fading conditions). The icon inNES will become whole and the bullet will take the color relevant to the alarms (if any) active in theNE.

– If the Supervision does not start, close and open again the CT.

– If the Supervision does not start, switch off and switch on the PC.

4–5.9.7 Configuration change from 4 QAM to 16 QAM

With 16 QAM the max. Tx power must be typically 3 dB below the max Tx power of the 4 QAM.

4–5.9.8 Quick configuration menu correct use

The Quick Configuration menu must be used during the first installation to configure completely the NEand also if some multiple configuration changes must be done (i.e. change of all the tributaries from”Framed” to ”Unframed” or vice–versa for the E1 signal both in the Local and Remote NE).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

448 / 592 3DB 16142 EAAA Ed.02


4–5.9.9 Abnormal condition list

The abnormal condition list is a summary of the abnormal conditions currently active in the NE due tomanual operations such channel protection switching commands (Radio, HST Tx or Mux/Demux), Txmuting, or any loopback (tributary, IDU, ODU).

Most of the manual operations listed in the abnormal conditions list may affect the traffic and the normalworking condition of the equipment

By CT ⇒ Diagnosis ⇒ Abnormal condition list

Press “Refresh” to actualize the list each time it is required.

Fig. 310. Abnormal condition list

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

449 / 5923DB 16142 EAAA Ed.02


4–5.9.10 Tx Mute functionality for interferences investigation

The local and the remote transceiver(s) can be muted by the following procedure:

By CT ⇒ Views ⇒ Radio

→ From the left window → select Channel #1 or #0

To mute the local transceivers:

→ From the lower right window → select “on” in the “Tx Local Mute field” → apply

To mute the remote station transceivers:

→ From the lower right window → select “on” in the “Tx Remote Mute” field → apply

N.B. In 1+1 configuration, Tx mute applied either on channel 1 or channel 0 will mute the twochannels transceivers at the same time.

Fig. 311. Tx Mute functionality

WARNING: The Tx Remote Mute automatically works («on» and then «off») only if performed on thelocal 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 sendthe command to remove the mute. If the Network Element has been restarted after aMUTE, there is no more possibility to set–up the channel, because the remote address isnot known, and, any case, to set–up the channel a bidirectional communication is needed.The only way to remove the MUTE command is with local CT or from a remote CT whichcan 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 < –95dBm.

For additional information refer to the handbook Interference investigation procedure, which describesin detail how to test the radio hop in order to find possible interferences.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

450 / 592 3DB 16142 EAAA Ed.02


4–5.9.11 Tributaries 17 to 32 visible in “16E1+Ethernet” configuration

In an “16E1+ Ethernet” type configuration, operator may choose a 32 E1 frame structure capacity. In thiscase, the relevant 17 to 32 tributaries bandwidth will be dedicated to the two User Ethernet ports

Nevertheless, tributaries 17 to 32 might show in the “line interface” CT view as well as in the “Loopbackview”. Since they do not physically exist, operator must ignore the lines dedicated to tributaries 17 to 32,in the “line interface” view as well as in the “loopback view”.

Fig. 312. Tributaries 17 to 32 visible in “16E1+ Ethernet” configuration

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

451 / 5923DB 16142 EAAA Ed.02


4–5.10 IDU unit replacement

In general, an IDU unit can be replaced:

a ) for spare part stock management:

• to check periodically the functionality of spare parts present in the spare part stock

b ) or, during corrective maintenance:

• to replace a faulty (or suspected faulty) unit with the correspondent spare part

• to restore the suspected faulty unit (after its successful replacement with a spare unit duringcorrective maintenance) to verify that it is really faulty.

Please refer to Fig. 305. on page 433 , for the position of this step inside the corrective maintenancegeneral flow–chart.

Tab. 70. herebelow lists the specific procedures, according to the unit type. These procedures areparticularly detailed in order to:– avoid injuries to personnel (electric safety)– avoid damages to the equipment and the spare parts– avoid, as far as possible, traffic interruptions or degrade.

Tab. 70. IDU unit replacement procedures

UNIT PARAGRAPH PAGE

IDU MAIN unit (CH1) 4–5.10.1 452

IDU EXTENSION unit (CH0) 4–5.10.2 456

FLASH CARD (housed on MAIN unit) Chapter 4–6 465

N.B. All these procedures are based, for both “1+0” and “1+1” configurations, on the equipmentinterconnection diagrams depicted in para.3–2.2 on pages 331 to 337 .Please make reference to the equipment interconnection diagram corresponding to yoursystem actual layout.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

452 / 592 3DB 16142 EAAA Ed.02


4–5.10.1 IDU MAIN unit replacement procedure (CH1)

ON/OFF switch

Flash Card label

Equipment ControllerReset pushbutton

Identification labelFlash Card Flash Card cover possible additionalidentification labelof the upgrade kit(see point [14]on page 475)

Fig. 313. Details for IDU MAIN unit or FLASH CARD replacement

General warnings:

Screw fixing

In all described operations, the screw tightening torque must be:


Unit uninstallation and installation

In all described operations, when it is necessary to uninstall or re–install the IDU MAIN unitfrom/in the shelf, wall or desk assembly, please refer to the instructions given in the InstallationHandbook.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

453 / 5923DB 16142 EAAA Ed.02


Procedure:

[1] Preliminary operations for 1+1 configurations:Before removing the defective IDU MAIN unit, carry out following operations (operations by CraftTerminal possible if CT working):

sub–step operation by CTresults on main traffic

and services

[1]–A– enable Force on CH0 Extension’s RPS switch– if set as Revertive, set RPS protection scheme as

No Revertive

[1]–B– enable Force on CH0 Extension’s TPS switch– if set as Revertive, set TPS protection scheme as

No Revertive

in general, noalarms/errors on bothNEs (N.B.)

[1]–C

– enable Force on CH0 Extension’s EPS switch– if set as Revertive, set EPS protection scheme as

No Revertive(N.B.)

NEs (N.B.)

N.B. in case Data plug–in is present, this implies the loss of tributary Ethernet traffic on bothNEs, that cannot be avoided

[2] If the local Craft Terminal is connected, perform the logoff, then switch it off

[3] On the unit identification label present at unit rear side (see Fig. 313. on page 452) read the unitLogistical Item (read also notes in point [14] on page 475, for the possible additional identificationlabel of the upgrade kit)

[4] Get a spare unit with the same Logistical Item (see para.4–3.3.5 on page 419 for general cautions).N.B. If, according to the spare part policy described in para.4–3.3.3 point a ) on page 418 :

• the unit to be replaced is equipped with optional plug–in(s) (17–32xE1 plug–in, orAudio + User Service Channel plug–in, or Data plug–in)

• and the spare unit is not equipped with such plug–in(s), that are instead available asseparate upgrade kits

you must at first install the spare plug–in(s) into the spare IDU Main unit basic, asdescribed in para.4–7.1 on page 469 (obviously the described unit de–installation andre–installation steps do not apply).

[5] Disconnect following cables from the front panel of the IDU MAIN unit to be replaced, in therecommended 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 continueson channel “0” through the IDU EXTENSION unit), with exception of tributary Ethernet traffic,if any

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

454 / 592 3DB 16142 EAAA Ed.02


[6] Turn off the front panel power switch (position “O”, see Fig. 313. on page 452):

• of the IDU MAIN unit to be replaced

• of the IDU MAIN spare unit

[7] if possible, switch off the circuit breaker that gives power supply to the cable connected to the IDUMAIN unit to be replaced.

[8] Disconnect all remaining cables from the front panel of the IDU MAIN unit to be replaced, in therecommended order:• IDU–ODU cable• only in case of 1+1 configurations: SCSI 1+1 interconnection cable between IDU Main and

Extension units• power supply cable• all other remaining cables, if any

Note: before removing cables ensure they are labeled

SAFETY RULESIf operation indicated in previous point [7] has not been carried out, a TNV–2(battery) voltage could be present on Station Battery input (cable side); do nottouch 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 burnsand/or eye damage. Remove rings, watches, and other metal jewelry beforeworking with primary circuits. Exercise caution to avoid shorting power inputterminals.

[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 (seeFig. 1. on page 36).

ATTENTION

(caution to avoid equipment damage)this avoids the possible damage of the electronic devices for electrostatic discharges

[11] Carry out the following operations on the IDU MAIN defective unit (see Fig. 313. on page 452):

• remove the Flash Card cover• extract the Flash Card (it will be mounted in the spare IDU Main unit)• restore the Flash Card cover

[12] Carry out the following operations on the IDU MAIN spare unit (see Fig. 313. on page 452):

• remove the Flash Card cover• insert the Flash Card you have extracted from the IDU MAIN defective unit in previous step [11]• restore the Flash Card cover

[13] Now you can take off the antistatic protection armlet

[14] Install the IDU MAIN spare unit

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

455 / 5923DB 16142 EAAA Ed.02


[15] Reconnect following cables to the front panel of the new IDU MAIN unit, exactly as they wereconnected before the faulty unit was extracted, in the following order:• only in case of 1+1 configurations: SCSI 1+1 interconnection cable between IDU Main and

Extension units• IDU–ODU cable• power supply cable• CT–NE cable

N.B. SAFETY RULES: see previous point [8]

[16] if switched off in step [7] on page 454, switch on the circuit breaker giving power supply to the cableconnected to the new IDU MAIN unit

[17] Turn on power on the new IDU MAIN unit (position “I”, see Fig. 313. on page 452)

[18] Wait for the unit configuration (about 2 minutes)

[19] Switch on CT, start 1320CT, login and enter NE supervision

[20] Additional operation for 1+1 configurations:

operation by CT results on main traffic and services

disable Force on CH0 Extension’s RPS switch no alarms/errors on both NEs

Note: the commands Force on Extension’s TPS and EPS switches [set in previous steps [1]–Band [1]–C on page 453] are lost due to the EC reset for IDU MAIN unit switch off/on

[21] Reconnect tributaries and services cables exactly as they were connected before the faulty unit wasextracted

[22] Check the system status using LED visual inspection and through the Craft Terminal

[23] If necessary, set TPS/RPS/EPS protection scheme as Revertive. Note that TPS and RPS protectionscheme setting to Revertive is not error free.

[24] Flash Card identifier label affixing

Please read para.1–3.7.2.2 on page 94.If the inserted IDU MAIN spare unit has no Flash Card identifier label sticked on it or the label doesnot match the flash card effectively inserted, put a label with the correct information (if not available,create a label writing the information on a self–adhesive sticker).

End of IDU MAIN unit replacement procedure

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

456 / 592 3DB 16142 EAAA Ed.02


4–5.10.2 IDU EXTENSION unit replacement procedure (CH0)

ON/OFF switch

Identification labelpossible additional identification labelof the upgrade kit (see point [14] on page 475)

Fig. 314. 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 re–install the IDU EXTENSIONunit from/in the shelf, wall or desk assembly, please refer to the instructions given in theInstallation Handbook

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

457 / 5923DB 16142 EAAA Ed.02


Procedure:

[1] Preliminary operations:Before removing the IDU EXTENSION defective unit, by Craft Terminal carry out followingoperations:

sub–step operation by CT results on main traffic results on services

[1]–AEnable Lockout on CH1Main’s RPS switch

no alarms/errors on bothNEs


[1]–BEnable Lockout on CH1Main’s TPS switch



[1]–CEnable Lockout on CH1Main’s EPS switch

– no alarms/errors onremote NE

– 1–2 sec alarm/AIS–Sync Loss on localNE


– 1 sec Slip or AIS onlocal NE

[2] On the unit identification label present at unit rear side (see Fig. 314. on page 456) read the unitLogistical Item (read also notes in point [14] on page 475, for the possible additional identificationlabel of the upgrade kit)

[3] Get a spare unit with the same Logistical Item (see para.4–3.3.5 on page 419 for general cautions).N.B. If, according to the spare part policy described in para.4–3.3.3 point a ) on page 418 :

• the unit to be replaced is equipped with the optional 17–32xE1 plug–in• and the spare unit is not equipped with such a plug–in, that is instead available as

separate upgrade kityou must at first install the spare plug–in into the spare IDU Extension unit basic, asdescribed in para.4–7.1 on page 469 (obviously the described unit de–installation andre–installation steps do not apply).

[4] Disconnect following cables from the front panel of the IDU EXTENSION unit to be replaced in therecommended 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 continueson channel “1” through the IDU MAIN unit)

[5] Turn off the front panel power switch (position “O”, see Fig. 314. on page 456):

• of the IDU EXTENSION unit to be replaced

• of the IDU EXTENSION spare unit

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

458 / 592 3DB 16142 EAAA Ed.02


[6] if possible, switch off the circuit breaker that gives power supply to the cable connected to the IDUEXTENSION unit to be replaced.

[7] Disconnect all remaining cables from the front panel of the IDU EXTENSION unit to be replaced, inthe recommended order:• IDU–ODU cable• SCSI 1+1 interconnection cable between IDU Main and Extension units• power supply cable

Note: before removing cables ensure they are labeled

SAFETY RULESIf operation indicated in previous point [6] has not been carried out, a TNV–2(battery) voltage could be present on Station Battery input (cable side); do nottouch 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 burnsand/or eye damage. Remove rings, watches, and other metal jewelry beforeworking with primary circuits. Exercise caution to avoid shorting power inputterminals.

[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 theywere connected before the faulty unit was extracted, in the recommended order:• SCSI 1+1 interconnection cable between IDU Main and Extension units• IDU–ODU cable• power supply cable

N.B. SAFETY RULES: see previous point [7]

[11] if switched off in step [6] on page 458, switch on the circuit breaker giving power supply to the cableconnected to the new IDU EXTENSION unit.

[12] Turn on power on the new IDU EXTENSION unit (position “I”, see Fig. 314. on page 456)

[13] Wait for the unit configuration (about 2 minutes)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

459 / 5923DB 16142 EAAA Ed.02


[14] Carry out following operations:

sub–step operation by CT results on main traffic results on services

[14]–ADisable Lockout on CH1Main’s EPS switch


– 1–2 secalarm/AIS–SyncLoss on local NE


– 1 sec Slip or AIS onlocal NE

[14]–BDisable Lockout on CH1Main’s RPS switch



[14]–CDisable Lockout on CH1Main’s TPS switch



[15] Reconnect tributaries and services cables exactly as they were connected before the faulty unit wasextracted

[16] Check the system status through LED visual inspection and through the Craft Terminal

End of IDU EXTENSION unit replacement procedure

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

460 / 592 3DB 16142 EAAA Ed.02


4–5.11 ODU replacement

In general, an ODU unit can be replaced:

a ) for spare part stock management:to check periodically the functionality of spare parts present in the spare part stock

b ) or, during corrective maintenance:to replace a faulty (or suspected faulty) unit with the correspondent spare partto restore the suspected faulty unit (after its successful replacement with a spare unit duringcorrective maintenance) to verify that it is really faulty.

Please refer to Fig. 305. on page 433 , for the position of this step inside the corrective maintenancegeneral flow–chart.

This procedure is particularly detailed in order to:– avoid injuries to personnel (EMF safety)– avoid damages to the equipment and the spare parts– avoid, as far as possible, traffic interruptions or degrade.

General warnings:

ODU unit uninstallation and installation

In all described operations, when it is necessary to uninstall the faulty ODU and install the spareODU, please refer to possible additional instructions given in the Installation Handbook.

Microwave radiations (EMF norms)

SAFETY RULESWhen operating on the antenna pole, strictly follow cautions stated inpara.5–1.3.8 on page 507 . In particular, if ODU is powered on from IDU, donot stand on the antenna axis and be aware of the complianceboundaries stated in Tab. 73. on page 508

Procedure:

[1] Get a spare ODU unit or, in case of ODU with external diplexer, a spare TRANSCEIVER box:• with the same Frequency Band and the same Frequency Shifter• and with the same or compatible Logistical Itemof 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), carry out steps [1]–A to [1]–C on page 453

• CH0 (ODU connected to IDU EXTENSION unit), carry out steps [1]–A to [1]–C on page 457

[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. 313. on page 452 )

• for channel 0, operate on EXTENSION unit (position “O”, see Fig. 314. on page 456 )

WARNING: this avoids a possible unrecoverable unknown condition of the spare ODU, whenODU will be switched on in next step [9]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

461 / 5923DB 16142 EAAA Ed.02


[4] If present, remove the solar shield (see Fig. 46. on page 120 and Fig. 47. on page 121)

[5] Disconnect the IDU–ODU cable at ODU side

[6] Change the ODU. NOTES:

• in case of ODU configurations 1+1 with coupler, use lever shown in Fig. 296. on page 417;

• in case of 7–8 GHz ODUs:

a ) remove the faulty TRANSCEIVER box in the following way (refer to Fig. 47. on page 121):

1 ) leave the BRANCHING box attached to antenna or coupler, i.e. do not openlevers (B)

2 ) unblock the four levers (A) and separate gently the faulty TRANSCEIVER box fromthe BRANCHING box

3 ) verify the coupling between TRANSCEIVER and BRANCHING boxes (seepara.1–4.7.4.2 on page 124), i.e. if the TRANSCEIVER box’s (D) (TX) is coupled tothe:– BRANCHING box’s (B) (HIGH FREQ)

– or BRANCHING box’s (C) (LOW FREQ)

b ) install the spare TRANSCEIVER box in the following way:

4 ) verify the presence and correct positioning of the O–RING on the spareTRANSCEIVER box (see Fig. 49. on page 123)

5 ) gently couple the spare TRANSCEIVER box on the BRANCHING box in the sameposition you have verified in step 3 ) above

6 ) fix the spare TRANSCEIVER box to the BRANCHING box using the four levers (A)(refer to Fig. 47. on page 121)

[7] Reconnect the IDU–ODU cable at ODU side

[8] If was present, mount the solar shield that was removed in previous step [4]

[9] Switch on the ODU by using the ON/OFF switch (position “I” of the relevant IDU unit (MAIN orEXTENSION unit) that has been switched off in previous step [3] .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

462 / 592 3DB 16142 EAAA Ed.02


[10] Additional operations for (1+1) configurations:by CT, remove forced traffic condition set in previous step [2]To do that, if replaced ODU is that of:

• CH1 (ODU connected to IDU MAIN unit), carry out following operations:

sub–step operation by CTresults on main traffic and

services

[10]–A – disable Force on CH0 Extension’s RPS switch no alarms/errors on both NEs

[10]–B – disable Force on CH0 Extension’s TPS switch no alarms/errors on both NEs

[10]–C – disable Force on CH0 Extension’s EPS switch no alarms/errors on both NEs

• CH0 (ODU connected to IDU EXTENSION unit), carry out steps [14]–A to [14]–C on page459

[11] If necessary, set TPS/RPS/EPS protection scheme as Revertive. Note that TPS and RPS protectionscheme 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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

463 / 5923DB 16142 EAAA Ed.02


4–5.12 Faulty unit repair and Repair Form


4–5.12.1 Faulty unit sending back to repair center

The complete faulty unit (complete ODU assembly, or TRANSCEIVER box in case of 7–8 GHzODU, or IDU Main or Extension Unit including plug–in, if any) must be sent back to theAlcatel–Lucent repair center.

Faulty unit repair must be done by authorized repair centers only.

4–5.12.2 Repair Form filling

To facilitate repair operation, data on the faulty unit must be reported on the form shown inFig. 315. on page 464.The repair form must be filled–in with as much data as possible and returned to Alcatel–Lucenttogether with the faulty unit.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

464 / 592 3DB 16142 EAAA Ed.02


REPAIR FORMFill in this form and affix it to the faulty unit to be returned to Alcatel–Lucent

TO

BE

FIL

LED

IN B

Y T

HE

SE

ND

ER

FAULT PHASE

INSTALLATION /

OPERATION

MAINTENANCE

REASON FOR REPAIR

CLEAR FAULT

INTERMITTENT FAULT

TEMPERATURE FAULT

DROP IN PERFORMANCE

UPGRADE/QUALITY ALERT

PRESUMED CAUSE

INTERNAL

LIGHTNING

AIR COND.

OTHER

EXTERNAL

FAULT STILL PRESENTAFTER REPAIR

COMMENTS

NAME OF SENDER

PROCESSING

NO FAULTS FOUND

STANDARD REPAIRING

QUALITY ALERT

UPGRADE

NOT REPAIRABLE

SUBSTITUTED

(REJECTED)

TURN ONTURN ON

A

B–D

I

I

M

S–X

FAULTS DETECTED

SOLDERING / ADJUSTMENT

CORROSION

C P

V3

COMPONENT

MECHANICAL PRINTED

F–L

V1 V1

DIRT

OTHER

V2

CIRCUIT BOARD

DATE REPAIRING NUMBER REPAIRING CENTRE NAME OF REPAIR OPERATOR

COMMENTS

TO

BE

FIL

LED

IN B

Y T

HE

RE

PA

IR O

PE

RA

TO

R

DATE

CUSTOMER NAME ORDER NUMBER/CONTRACT NUMBER

SITE BRANCH/UNIT/COUNTRY

SYSTEM/EQUIPMENT PRODUCT RELEASE EQUIPMENT SOFTWARE PART NUMBER

SLOTSUBRACKSTATION/RACK

MNEMONIC

SERIAL NUMBER

ALCATEL PART NUMBER

FAULTY UNIT SOFTWARE VERSION

NOTE : LETTERS ARE FOR FACTORY USE

WIRING

Fig. 315. Repair form

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

465 / 5923DB 16142 EAAA Ed.02


4–6 SPARE FLASH CARD MANAGEMENT AND REPLACEMENTPROCEDURES

This chapter, for maintenance purpose, describes how to manage the spare Flash Card and how toreplace it, in case of problems.

N.B. To replace a Flash Card with a different type, for system upgrade purpose, please refer topara.4–7.3 Flash Card upgrade on page 479.

4–6.1 Spare Flash Card management

Please refer to para.1–3.7 on page 93 for detailed information on Flash Card position, types andidentification.

With reference to the Flash Card content description given in para.1–2.5 on page 56 , a spare Flash Card:

a ) usable as “specific” spare part for a certain NE must contain the same SW information stored in theFlash 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 existingin that “specific” NE, provided that no change is made on the NE SW information by Craft Terminal,TCO Suite or by TMN system.

b ) supplied as “generic” spare part, contains default SW information, stored by Alcatel–Lucent factoryfor testing purposes before delivery to Customer. In this case you cannot insert it “as it is” in any NE,without making specific operations by Craft Terminal. The same warning applies also for a Flash Cardsupplied as “specific” spare part for a certain NE [see point a ) above], whenever the NE SWinformation has been changed by Craft Terminal or by TMN system after the system installationphase.

In both cases, it is expected that in the plant, the following back–up information is always available for eachspecific NE:

[1] the MIB back–up fileTo know how to create a MIB back–up file, refer to Chapter 2–14 on page 301.

[2] the “.qcml” configuration fileTo know how to create a “.qcml” configuration back–up file, refer to the Procedure for “.qcml”file back–up on page 65 .

Please, refer to para.1–2.6.7 on page 65 for details.

SUGGESTION

Use one IDU Main unit of the spare–part–stock as an off–line service station (non connected to thenetwork) to manage the content of Flash Cards, before using them as spare parts.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

466 / 592 3DB 16142 EAAA Ed.02


4–6.2 Flash Card replacement procedure


The need for this replacement is for corrective maintenance purposes, whenever the failure or contentcorruption of the Flash Card must be suspected

The Flash Card contains the system software (see para.1–2.5 on page 56). Many types are envisaged: itsidentification is described in para.1–3.7.2.2 on page 94.

ATTENTION

(caution to avoid complete traffic loss)Do not insert in the system a Flash Card the content of which you do not well know!You must be aware that if a Flash Card with SW information different from that running in the systemis inserted “as it is”, the software download will be automatically carried out from the Flash Cardtoward the System’s EC and RCs and Supervisory Units, thus causing a complete system crash.

The steps of the Flash Card replacement procedure to use, detailed in following para.4–6.2.2, depend onthe choice adopted by the Customer with reference to the type of spare flash card stored in thespare–part–stock (refer to the Spare Flash Card management policy described in para.4–6.1 on page465):

a ) “NE–specific” spare part for a certain NE (each NE has its own “specific” spare Flash Card, keptaligned to SW changes made on the NE in service, through an off–line service station).

b ) “generic” spare part that cannot be inserted it “as it is” in any NE.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

467 / 5923DB 16142 EAAA Ed.02


4–6.2.2 Execution of the Flash Card replacement

General warnings:

Screw fixing



Procedure:

[1] Read the Flash Card Software Label on the label affixed on IDU MAIN unit (see Fig. 76. on page170) and according to it, retrieve the Flash Card Logistical Item through Tab. 23. on page 93 .If CT works, you can verify the Flash Card Software Label by Supervision ⇒ SW Key (examplein Fig. 159. on page 256 )

[2] Get the spare Flash Card with the same Logistical Item; leave it in its protective envelope until youhave 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 betogether with it. Proceed to next step [4]

• or “generic”; in this case, before proceeding to next step [4] , isolate the NE from the supervisionnetwork.

N.B. Before to isolate the system from the supervision network, inform the supervisioncenter: if (from the supervision point of view), there are other NEscascade–connected to it (and without supervision ring network) they will be isolated,too.

[4] Wear the antistatic protection armlet [see point b ) on page 36] and connect its termination to agrounded structure

ATTENTION


[5] Remove the Flash Card cover (see Fig. 313. on page 452 ). Store tidily cover and screws for theirsuccessive mount

[6] Extract the faulty Flash Card from the IDU Main Unit, verify again that its type is equal to that of thespare Flash Card and insert the spare Flash Card (refer to Fig. 34. on page 94 for Flash Card profileand insertion direction)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

468 / 592 3DB 16142 EAAA Ed.02


[7] After two minutes, login the NE by CT.Now, if you have inserted:

• a “generic” spare Flash Card, proceed with following step [8]

• a “NE–specific” spare Flash Card, proceed with following step [9]

[8] If you have inserted a “generic” spare Flash Card, carry out following checks and operations by CT:

1 ) verify the SW COMMITTED and STAND–BY versions in the Flash Card, as described in point[2] on page 63 :

– if the SW COMMITTED version is equal to that previously present with the replaced flashcard, proceed with sub–steps 2 ) and 3 ) below

– if the SW COMMITTED version is not equal to that previously present with the replacedflash card, but the STAND–BY version is equal, proceed with the swap between the SWCOMMITTED and STAND–BY versions, as described in para.4–8.5 on page 492 .Then, proceed with sub–steps 2 ) and 3 ) below.

– if neither the SW COMMITTED nor the STAND–BY versions are equal to that previouslypresent with the replaced flash card, proceed with downloading and activation of the targetSWP version, as described in chapter 4–8 on page 485 .Then, proceed with sub–steps 2 ) and 3 ) below.

2 ) launch the TCO Suite Set–Up Tool , as described in para.3–2.3.9 on page 345In the screen of Fig. 244. on page 346 , click on button Open Configuration .When the file selection window opens requiring a “configuration_name.qcml” file to be opened,specify the NE’s specific file [mentioned in point [2] on page 465 ].The window in Fig. 245. on page 347 will appear.Then, clicking repeatedly on Next buttons (without any other actions, or just checkingconfiguration screens, if you like), reach Step L on page 368 and click on Finish button.In this way the “.qcml” configuration data are loaded in the Flash Card data base.

3 ) carry out MIB data restore and activation [using NE’s specific MIB back–up file mentioned inpoint [1] on page 465 ] as shown in MIB Restore in Fig. 209. on page 301 (from operativepoint of view, refer to para.2–8.3.2 and 2–8.3.3 on page 255). In alternative to activation bySW, carry out the Equipment Controller HW Reset, pushing the suitable button on IDU MAINUnit (see Fig. 76. on page 170).

Now, you can reconnect the NE to the supervision network, and proceed with following step [9]

[9] Restore the Flash Card cover removed in previous step [5]


[11] Carry out functional checks by Craft Terminal.

End of procedure

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

469 / 5923DB 16142 EAAA Ed.02


4–7 SYSTEM HARDWARE UPGRADE

This chapter details all phases necessary to carry out the following hardware upgrades:

– Installation of plug–ins, para.4–7.1 below

– upgrade 9400AWY system from 1+0 to 1+1 configuration, para.4–7.2 on page 476

– install a new Flash Card to improve system capacity, para.4–7.3 on page 479

4–7.1 Installation of plug–ins


When Customer orders a 9400AWY equipment, usually , if plug–ins are included in the order, IDU Mainunit and IDU Extension unit are delivered with the required plug–ins already mounted. In such a case, thisprocedure has no use.

This procedure is used whenever, after the installation of a 9400AWY equipment with no plug–in equipped,Customer needs to upgrade it adding plug–ins.

Tab. 71. below lists the plug–ins presently available.

Tab. 71. Available plug–in upgrade kits

Logistical Item Description Notes

3DB16086AAXX 32E1 ON SITE UPGRADE KIT

3DB16130AAXXDATA ENHANCED ON SITE UPGRADE KIT(4 x 10/100/1000 baseT ports)

in alternative

3DB16089AAXX AUDIO + USER SERVICE CHANNEL UPGRADE KIT

Notice that:

– in 1+0 configuration, you can equip any of the plug–in types into the IDU Main unit

– in 1+1 configuration, you can upgrade the system in one of the following ways:

• upgrade from max 16 to max 32 E1 tributaries: you must install the 17–32 E1 PLUG–IN into boththe:– IDU Main unit– IDU Extension unit

• upgrade to Ethernet tributaries: you must install the DATA ENHANCED ON SITE UPGRADEKIT 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

470 / 592 3DB 16142 EAAA Ed.02


4–7.1.2 Procedure

Drawings used to show operations are relevant to the IDU Main unit. Operations to be carriedout for IDU Extension unit are exactly the same.

Screw fixingIn all described operations, the screw tightening torque must be:


Unit uninstallation and re–installationIn all described operations, when it is necessary to uninstall or re–install the IDU unit (MAIN orEXTENSION) from/in the shelf, wall or desk assembly, please refer to the instructions given inthe Installation Handbook

The following operations concern the IDU unit (MAIN or EXTENSION) to be upgraded:

[1] Isolate the power supply, disconnect Craft Terminal [see point f ) on page 36] and disconnect allcables.

[2] Uninstall the unit and place it on a workbench

[3] Fig. 316. :

• if present, dismount both fixing brackets (A and B), there are two screws for each (C)

• undo the side screws D (three on each side) for cover unfix

A

B

C

D

Fig. 316. Dismounting the fixing brackets and cover unfix

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

471 / 5923DB 16142 EAAA Ed.02


[4] Rotating the removed fixing brackets into both the suitable cover’s side holes, slide the box coverout from the box base, as shown in Fig. 317. :

use of fixing bracket to release the cover

sliding out the cover

Fig. 317. Release and sliding out the cover

[5] Wear the antistatic protection armlet and connect its termination to a grounded structure (seeFig. 1. on page 36).

ATTENTION


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

472 / 592 3DB 16142 EAAA Ed.02


[6] Now, you can remove the cover (Fig. 318. ):

Fig. 318. Removing the cover

[7] Fig. 319. : according to the plug–in to be installed, dismount the metal plate (fixed by two screws)which closes the plug–in devoted hole. Take the two removed screws for their fixing.

plate to remove forAUDIO + USER SERVICE

CHANNEL plug–in

plate to remove forTRIBUTARY plug–in

Fig. 319. Dismounting the metal plate

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

473 / 5923DB 16142 EAAA Ed.02


[8] Fig. 320. shows in details the connectors and columns for plug–in fixing by screws

2 columns for plug–infixing by screws

connectorfor plug–in

3 columns for plug–infixing by screws

connectors for plug–in

Fig. 320. Connectors and columns for plug–in fixing by screws

[9] Insert the plug–in in its connector(s) depicted in previous Fig. 320. , and fix it:

• on the PCB using the 2 or 3 screws on the suitable columns depicted in previous Fig. 320.

• to the front panel by the 2 screws or the screw columns

The result must be as shown in following Fig. 321.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

474 / 592 3DB 16142 EAAA Ed.02


Details of 16–32 E1 plug–in installed

Details of Enhanced Ethernet plug–in installed

Details of Audio + User Service Channel plug–in installed

Fig. 321. Plug–in insertion and fix

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

475 / 5923DB 16142 EAAA Ed.02


[10] Reinsert the cover(reverse operation of Fig. 318. on page 472)

[11] Slide in the cover(reverse operation of Fig. 317. on page 471. The fixing brackets use is not necessary)


[13] Fix the cover and, if they were present, mount both fixing brackets(reverse operation of Fig. 316. on page 470)

[14] Upgrade kit identification labelAfter this upgrading, the Unit identification label placed on the box rear side [position (C) in Fig. 21. onpage 70 for the IDU Main Unit, and in Fig. 23. on page 77 for the IDU Extension Unit] is no longerright to correctly identify the assembly as a whole.

This could impact on spare–part–stock management and maintenance.For this reason:• if the upgrade kit is supplied with a suitable self–adhesive label (under study), stick it just on side

of that already existing• otherwise create a label writing the upgrade kit P/N on a self–adhesive sticker, and stick it just

on side of that already existing.

existingidentification labelof the basic unit

additionalidentification labelof the upgrade kit

ÉÉÉÉÉÉÉÉ

[15] Re–install the unit

[16] Complete upgrade operations with:

• system cabling (it is different from that previous to upgrading). Refer to the InstallationHandbook, according to the new hardware configuration

• system data re–definition (it is different from that previous to upgrading), carrying out QuickConfiguration procedure by Craft Terminal (details in para.3–2.3.7 on page 343).

• commissioning procedure, to check the new interface, (details in Chapter 3–2 –Commissioning on page 329).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

476 / 592 3DB 16142 EAAA Ed.02


4–7.2 Upgrade from 1+0 to 1+1 configuration

4–7.2.1 Preface

This upgrade must be done on both stations of the radio link, first on one, then on the other, or at the sametime by two different service teams. A third phase is necessary for the radio link line–up.

a ) First case: “1+0” already equipped with the Protection boxesThis procedure is based on the equipment interconnection diagrams depicted in para.3–2.2 onpages 331 to 337 . In such diagrams you can see:• the “1+0” configuration (”starting configuration”), already equipped with the E1 Protection box

and the Services Protection box . Please make reference to the equipment interconnectiondiagram corresponding to your actual system layout.

• the corresponding “1+1” configuration (”target configuration”)In this case the upgrade to the corresponding “1+1” configuration can be done with a small trafficinterruption time. Nevertheless, the full link unavailability must be planned for the phase [C] .

b ) Second case: “1+0” not equipped with the Protection boxesDue to full hardware changes, station DDF refurbishing, cable extraction/insertion and system switchoff/on need, much more link unavailability time must be foreseen for the upgrade, with respect to casea ) above.In this case, too, you must use one of the “1+1” equipment interconnection diagrams depicted inpara.3–2.2 on pages 331 to 337 as ”target configuration”.

N.B. Operations by Craft Terminal on each station must be done by local ECT through ’F’ or Ethernetinterface only, while the use of RECT is not admitted.

This procedure is particularly detailed in order to:– avoid injuries to personnel (EMF safety)– avoid damages to the equipment– avoid, as far as possible, traffic interruptions or degrade.

General warnings:

Microwave radiations (EMF norms)

SAFETY RULESWhen operating on the antenna pole, strictly follow cautions stated inpara.5–1.3.8 on page 507 . In particular, if ODU is powered on from IDU, donot stand on the antenna axis and be aware of the complianceboundaries stated in Tab. 73. on page 508

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

477 / 5923DB 16142 EAAA Ed.02


4–7.2.2 Procedure

[1] For both stations, ascertain to have all materials necessary for the HW upgrade, at IDU and ODUlevels, as well as necessary installation materials.For materials necessary for hardware upgrade, please refer to the:• para.1–3.1 on page 68 (standard materials for IDU)• Installation Handbook (ODU provisioning and additional installation materials for IDU and

ODU)

PHASE [A] : OPERATIONS ON FIRST STATION

[2] Preliminary operations to be done only in case of “1+0” system not equipped with the Protectionboxes:

a ) switch off the IDU MAIN unit and disconnect all tributary (with the exception of Ethernet, if any)and services cables from its front panel

b ) using the instructions given in the Installation Handbook:– install the E1 Protection box and the Services Protection box– install the IDU EXTENSION unit

N.B. connect its power supply plug to the station battery, but ascertain that itsON/OFF switch is in OFF position and leave it in OFF position till step [9]

– connect the IDU MAIN and EXTENSION units to the E1 Protection box and the ServicesProtection box

– connect the E1 Protection box and the Services Protection box to the station DDF

c ) switch on the IDU MAIN unit, connect the Craft Terminal, switch it on, start 1320CT and loginthe NE (details in para.2–2.5.2 on page 173) and verify the link functionality

[3] If not connected, connect the Craft Terminal, switch it on, start 1320CT and login the NE (details inpara.2–2.5.2 on page 173)

[4] Using the instructions given in the Installation Handbook , install the second ODU; for generalinformation, make reference to Fig. 4. on page 41). Warning: in case of 1+1 ODU configuration:

a ) with two antennas, install the second ODU with its own antenna

b ) with 1+1 coupler:

– if the coupler is already installed, fix the second ODU to the coupler, then go to step [5]

– if the coupler is not installed, carry out following operations (full link unavailability fromsubstep 3 ) till substep 6 ):

1 ) by Craft Terminal, disable ATPC on CH1 (if enabled): see para.2–6.4.1 on page239

2 ) carry out NE logoff (details in para.2–2.5.3 on page 180)

3 ) switch off IDU MAIN unit (CH1)

4 ) disconnect ODU CH1 from antenna, connect the 1+1 coupler to the antenna, andconnect the ODU CH1 to the 1+1 coupler

5 ) switch on IDU MAIN unit (CH1)

6 ) wait until system restart completion, then start 1320CT and login the NE (details inpara.2–2.5.2 on page 173)

7 ) by Craft Terminal, enable ATPC on CH1 (if necessary): see para.2–6.4.1 on page 239

[5] Only in case of “1+0” system already equipped with the Protection boxes: install the CH0 IDUEXTENSION unit and connect it to the E1 Protection box and the Services Protection box, usingthe instructions given in the Installation HandbookN.B. connect its power supply plug to the station battery, but ascertain that its ON/OFF switch

is in OFF position and leave it in OFF position till step [9]

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

478 / 592 3DB 16142 EAAA Ed.02


[6] Connect the 100–pin cable to both IDU MAIN and EXTENSION units, using the instructions givenin the Installation Handbook

[7] Connect the IDU–ODU cable (between the “CH0 Extension IDU” and the second ODU), using theinstructions given in the Installation Handbook

[8] By Craft Terminal carry out the following operations:

1 ) Configuration ⇒ System Setting ⇒ NE Configuration ⇒ 1+1 Configuration: see para.2–3.4.1on page 210

2 ) This configuration change causes the JUSM loss, so that you must login again the NE (detailsin para.2–2.5.2 from page 173)

3 ) Set EPS (Mux/Demux Protection) Lockout: see para.2–9.1 subpara.2–9.1.2 on page 259WARNING: this operation is not error free

4 ) Set CH0 Tx Power as follows: with reference to Fig. 140. on page 238 :select Channel #0 ⇒ click on “RTPC & ATPC” ⇒ insert value in “Tx Power(dBm)” field ⇒ ApplyWARNING: the CH0 Rx remains at 0 till the NE restart carried out in substep [10]–4 ) below

5 ) Note: this step is not necessary in HSB configuration, where frequency is set automatically:Set CH0 Tx Frequency as follows: with reference to Fig. 136. on page 235 :select Channel #0 ⇒ click on “Frequency” ⇒ insert value in “Tx Frequency(kHz)” field ⇒ Apply

[9] Switch on the CH0 Extension IDU by its ON/OFF switch

[10] By Craft Terminal carry out the following operations:

1 ) Set CH0 Frequency Shifter as follows: with reference to Fig. 136. on page 235 :select Channel #0 ⇒ insert value in “Shifter” field ⇒ Apply

2 ) Note: this step is necessary in FD configuration only:Set again CH0 Frequency as follows: with reference to Fig. 136. on page 235 :select Channel #0 ⇒ click on “Frequency” ⇒ insert value in “Tx Frequency(kHz)” field ⇒ ApplyWARNING: the CH0 Rx remains at 0 till the NE restart carried out in substep [10]–4 ) below

3 ) Remove EPS (Mux/Demux Protection) Lockout: see para.2–9.1 subpara.2–9.1.2 on page 259WARNING: this operation is not error free

4 ) Restart NE: see para. 2–8.2 on page 252

PHASE [B] : OPERATIONS ON SECOND STATION

[11] Repeat the previous steps in the other station of the radio link

PHASE [C] : OPERATIONS ON THE LINK

N.B. These operations are meant for the radio link as a whole, and imply full link unavailability.

[12] In case of ODU configuration with two antennas, carry out the alignment of the second ODU antenna(N.B.)

[13] Carry out the CH0 functionality test (N.B.).

N.B. For details on commissioning procedures, please refer to the Chapter 3–2 on page 329.

PHASE [D] : NE DATA SAVE

[14] Save data of both NEs as explained in para.1–2.6.8 on page 65.

End of procedure

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

479 / 5923DB 16142 EAAA Ed.02


4–7.3 Flash Card upgrade


Please refer to para.1–3.7 on page 93 for detailed information on Flash Card position, types andidentification.

N.B. To replace a Flash Card with the same type, for maintenance purpose, please refer topara.4–6.2 – Flash Card replacement procedures on page 466.

In general, the Flash Card upgrade must be done together with HW changes, e.g. changing the systemcapacity from “16xE1” to “32xE1” requires to:

– change:

• the existing Flash Card “32Mb 4/16 QAM FLASH CARD” with the “64Mb 16 QAM FLASHCARD”

corresponding to the change of the:

• Software Label from “32Mb 4/16 QAM” to “64Mb 16 QAM”

This paragraph explains how to do this operation.

– and install (if not yet present) the 17–32xE1 PLUG–IN in the IDU MAIN UNIT, as well in the IDUEXTENSION UNIT in case of 1+1 systems; to carry out this operation, please refer to para.4–7.1 –Installation of plug–ins on page 469.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

480 / 592 3DB 16142 EAAA Ed.02


4–7.3.2 Summary procedure for both stations

This example is for changing the existing Flash Card “16E1/32Mbps DATA 4/16QAM” with the “32E1DS14/16QAM”. Adapt it to the actual change you must do.

Tab. 72. Flash card upgrade carried out by one operator only for both stations

STEP 1 IN STATION BSTEP 2 IN STATION A

(in series to step1)notes

Current configuration Back–up idem

Flash card replacement. This requires, intypical condition (rack installation), toswitch the IDU off and disconnect cables;otherwise, if the installation conditionallows to replace the flash card withoutdisconnecting cables, the NE supports anhot replacement

idem

IDU switch–on (after re–cabling) or NERestart (in case of hot replacement), StartSupervision & Open USM (empty due tothe non–preconfigured flash card)

idem

Check that the SW Key is the new one idem

MIB Restore / Activation, Start Supervision& Open USM

idem

Quick configuration. In this case(=dialogue with ODU already established),the shifter and TX frequency are allowed tobe set also by Quick config. The NE typeis modified to 32E1 and the Tributaryconfig is set again to 16E1 (not to 32E1as desired)

idem

Re–opening USM

Go to STATION A and carry out operationsdetailed in column STEP 2

Open Local and Remote USM

CHANGE REMOTE CONFIG BYSYSTEM SETTING FROM 16E1 TO 32E1CAPACITY the traffic is

impacted forCHANGE LOCAL CONFIG BY SYSTEMSETTING FROM 16E1 TO 32E1CAPACITY

impacted forabout 1 min

Following paragraphs are given just for Operators who need to know what to do in detail for:– Ordering the new Flash Card– Installation of a new Flash Card fully configured in factory– Installation of a new Flash Card not configured in factory

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

481 / 5923DB 16142 EAAA Ed.02


4–7.3.3 Ordering the new Flash Card

Whenever the Base configuration of the 9400AWY NE must be upgraded, Customer must order a newFlash Card:

– of the type consistent with the equipment configuration he wants: see Tab. 23. on page 93 ,

– and preferably, already set by Alcatel–Lucent Factory:

• with the same SWP–version present in the 9400AWY system to be upgraded, already presentin the Flash–Card’s SW committed version bank

• with the same NE network routing data (and other configuration data) of the system to beupgraded (for this purpose, Customer can save the NE’s “.qcml” configuration file onfloppy–disk as explained in the Procedure for “.qcml” file back–up on page 65 , and give it toAlcatel–Lucent Factory). N.B.

• with the same MIB of the system to be upgraded (for this purpose, Customer can save the MIBon floppy–disk as explained in chapter 2–14 on page 301 and give it to Alcatel–Lucent Factory).N.B.

N.B. these options could be subject to possible special contractual terms.

To install a new Flash Card fully configured in factory carry out operations in para.4–7.3.4 on page 482.

To install a new Flash Card not configured in factory carry out operations in para.4–7.3.5 on page 483.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

482 / 592 3DB 16142 EAAA Ed.02


4–7.3.4 Installation of a new Flash Card fully configured in factory

General warnings:



Use of this procedureThis procedure can be carried out only if the new Flash Card is delivered with SW and data asspecified in para.4–7.3.3 on page 481 .

Procedure:

After having got the new Flash Card, the phases for the Flash Card upgrading are:

[1] get the new Flash Card; leave it in its protective envelope until you have worn the antistatic protectionarmlet

[2] wear the antistatic protection armlet [see point b ) on page 36 ] and connect its termination to agrounded structure

ATTENTION


[3] remove the Flash Card cover (see Fig. 313. on page 452 ). Store tidily cover and screws for theirsuccessive mount

[4] extract the old Flash Card from the IDU Main Unit and insert the new one (refer to Fig. 34. on page94 for Flash Card profile and insertion direction)

[5] carry out the Equipment Controller HW Reset, pushing the suitable button on IDU MAIN Unit (seeFig. 313. on page 452 ).About two minutes are necessary for the supervision process to get data from the new flash card.

[6] restore the Flash Card cover removed in step [3] above (screw tightening torque as specified above)

[7] now you can take off the antistatic protection armlet

[8] if not connected, connect the Craft Terminal, switch it on, start 1320CT and login the NE (details inpara.2–2.5.2 on page 173)

[9] carry out the Quick Configuration procedure (interactive) by Craft Terminal [details in para.3–2.3.7on page 343 ], to change the system capacity

[10] carry out functional checks by Craft Terminal

[11] save NE data as explained in para.1–2.6.8 on page 65 ( creation of MIB back–up file and “.qcml”back–up file )

[12] as the new Flash Card is supplied with a self–adhesive label containing the Flash Card SoftwareLabel, get and stick it over the older one [see (A) in Fig. 21. on page 70 ); (N.B. if possible, removethe older self–adhesive label before sticking the newer).

End of procedure

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

483 / 5923DB 16142 EAAA Ed.02


4–7.3.5 Installation of a new Flash Card not configured in factory

General warnings:



Use of this procedureWith this procedure, the system is isolated from the supervision network.In fact, the insertion in a 9400AWY system connected to the network of a Flash Card with:– “default” or “unknown“ NE network routing data– SW Commit Version “unknown“ or lower than that present on the systemmust be absolutely avoided.

Procedure:

After having got the new Flash Card, the phases for the Flash Card upgrading are:

[1] get the new Flash Card; leave it in its protective envelope until you have worn the antistatic protectionarmlet

[2] if not connected, connect the Craft Terminal, switch it on, start 1320CT and login the NE (details inpara.2–2.5.2 on page 173)

[3] by Craft Terminal:

1 ) run the Quick Configuration procedure (interactive) by Craft Terminal [details in para.3–2.3.7on page 343 ]. In the last screen (Step L on page 368) click on Save As button: configurationdata are saved in a “configuration_name.qcml” file

2 ) save the MIB data as shown in MIB BackUp in Fig. 209. on page 301 (from operative point ofview, refer to para.2–8.3.1 on page 254)

[4] carry out NE logoff

[5] isolate the NE from the supervision network

N.B. Before to isolate the system from the supervision network, inform the supervision center:if (from the supervision point of view), there are other NEs cascade–connected to it (andwithout supervision ring network) they will be isolated, too.

[6] wear the antistatic protection armlet [see point b ) on page 36 ] and connect its termination to agrounded structure

ATTENTION


[7] remove the Flash Card cover (see Fig. 313. on page 452 ). Store tidily cover and screws for theirsuccessive mount

[8] extract the old Flash Card from the IDU Main Unit and insert the new one (refer to Fig. 34. on page94 for Flash Card profile and insertion direction)

[9] restore the Flash Card cover removed in step [7] above (screw tightening torque as specified above)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

484 / 592 3DB 16142 EAAA Ed.02


[10] now you can take off the antistatic protection armlet

[11] login the NE and, by Craft Terminal, perform following operations:

1 ) verify the SW COMMITTED version in the Flash Card, as described in point [2] on page 63.If not V2.1.0, proceed with V2.1.0 downloading and activation, as described in chapter 4–8 onpage 485.

2 ) launch the TCO Suite Set–Up Tool , as described in para.3–2.3.9 on page 345.In the screen of Fig. 244. on page 346 , click on button Open Configuration .When the file selection window opens requiring a “configuration_name.qcml” file to be opened,specify the NE’s specific file you have saved in previous step [3]–1 ) on page 483.The window in Fig. 245. on page 347 will appear.Then, clicking repeatedly on Next buttons (without any other actions, or just checkingconfiguration screens, if you like), reach Step L on page 368 and click on Finish button.In this way the “.qcml” configuration data are loaded in the Flash Card data base.

3 ) carry out MIB data restore and activation [using NE’s specific MIB back–up file you have savedin previous step [3]–2 ) on page 483] as shown in MIB Restore in Fig. 209. on page 301 (fromoperative point of view, refer to para.2–8.3.2 and 2–8.3.3 on page 255). In alternative toactivation by SW, carry out the Equipment Controller HW Reset, pushing the suitable buttonon IDU MAIN Unit (see Fig. 76. on page 170).In this way the MIB configuration data are loaded in the Flash Card data base.About two minutes are necessary for the supervision process to get data from the new flashcard.

[12] carry out the Quick Configuration procedure (interactive) by Craft Terminal [details in para.3–2.3.7on page 343 ], to change the system capacity

[13] connect the system to the supervision network

[14] carry out functional checks by Craft Terminal

[15] save NE data as explained in para.1–2.6.8 on page 65.

[16] as the new Flash Card is supplied with a self–adhesive label containing the Flash Card SoftwareLabel, get and stick it over the older one [see (A) in Fig. 21. on page 70 ); (N.B. if possible, removethe older self–adhesive label before sticking the newer).

N.B. In alternative, if an off–line IDU MAIN unit is available at Customer premises, the Flash Cardcan be prepared on it, and then installed on the target system as described in previouspara.4–7.3.4 on page 482.

End of procedure

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

485 / 5923DB 16142 EAAA Ed.02


4–8 SWP DOWNLOAD TOWARD NE

This chapter details all phases necessary to download inside the NE equipment environment, and thenactivate, a SWP having a version greater than that presently loaded in the NE’s Flash Card.

N.B. Before starting this procedure, it is suggested to give a look to para.1–2.6 on page 58.

N.B. Procedures described in this chapter are carried out with the PC connected to the NE.


4–8.1.1 Craft Terminal

The PC, already loaded with the SWP to be downloaded toward the NE (as explained in previous chapter3–1 on page 309) must be available as CT (Craft Terminal).

4–8.1.2 NE state

[1] Equipment state

• equipment must have been previously installed, cabled, powered on and commissioned asdescribed in para.1–2.6.1 on page 59

• the SWP–version present inside the NE’s Flash Card must be lower than that of the ECT (referto para.1–2.6.3 on page 62 to know how to compare them).

[2] Equipment HW constraintsNone

4–8.1.3 Operator skills and profile

a ) In addition to skills stated in para.3–1.1.2 on page 310, the Operator must be familiar with all theequipment functionalities.

b ) The Operator’s profile must be “Administrator” or “craftPerson” (see para.2–3.6 on page 214).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

486 / 592 3DB 16142 EAAA Ed.02


4–8.2 Summary of the SWP download phases

WARNING: this procedure describes the operations to be done on a single NE. You must be awarethat they must be done on both stations A and B of the radio link. For this purpose, makereference to Chapter 4–9 on page 495

The installation phases are:

a ) CT start–up, NE login and initial checks para.4–8.3 herebelow

b ) SW download to the NE, para.4–8.4 on page 487

c ) Activation of the new Software Package on the NE para.4–8.5 on page 492

d ) Additional operations for upgrade from V2.1.0 para.4–8.6 on page 494

e ) MIB save para.4–8.7 on page 494

4–8.3 CT start–up, NE login and initial checks

Step 1. Carry out following operations (for details refer to para.2–2.5.2 on page 173):

a ) Power on the PC and wait for its start–up

b ) Start–up the Craft Terminal and wait for the Network Element Synthesis screen

c ) Carry out Start supervision and Show Equipment on the Network Element that must beaffected by this download operation

d ) Login the Network Element, using the “Administrator” or “craftPerson” UserName &Password

e ) Wait for the main Equipment view (CT) to appear

Step 2. Check SWP versions 2.1.x present in the NE MIB banks, as explained in point [2] on page 63.

You must be aware that the SWP download, carried out in the following, will overwrite the currentStandby 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.4–8.5 onpage 492.

Step 3. Check the SWP version 2.1.y (y > x) availability for download to the NE, as explained in step6 ) on page 325.If not available, carry out completely the procedure described in para.3–1.8 on page 321.

Verify also that the version to be downloaded is greater than those present in both the NE MIBcurrent Standby and Committed banks.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

487 / 5923DB 16142 EAAA Ed.02


4–8.4 SW download to the NE

Step 1. Setup Server Access Configuration

a ) Carry out SW Download ⇒ Server Access Configuration (Fig. 322. below)

Fig. 322. Server Access Configuration start up

b ) The following confirmation box appears. Press OK to close it.

c ) The screen of Fig. 323. on page 488 appears, with empty fields. Click on Use SystemDefault button.

In this way the systems sets automatically the Address and Port fields, that depend onhow the login to the NE has been done:

• by F interface: IP address of the LLMAN to download in interface F mode is set

• by LAN interface: IP address of the PC to download the software in LAN mode is set

N.B. The UserId and Password present in this screen are relevant to the ftp login, areset automatically with the Use System Default button and have no relationshipwith those necessary for the NE login.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

488 / 592 3DB 16142 EAAA Ed.02


Fig. 323. Server Access Configuration set–up screen

d ) Press OK to confirm values and close the window.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

489 / 5923DB 16142 EAAA Ed.02


Step 2. SW Download

a ) Carry out SW Download ⇒ Init SW Download (Fig. 322. below)

Fig. 324. Init SW Download start–up

b ) Wait “List Sw Package” creation ...When action is completed, press “Enter” to close message window.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

490 / 592 3DB 16142 EAAA Ed.02


c ) Now select a specific SWP to download on the NE, and press Init download to start it.

2_1_1

Fig. 325. Init download

d ) Confirm the start of software downloading:

2_1_1

e ) The software downloading in progress is shown by a specific window:

f ) When the download is over the following window is shown:

N.B. The software download lasts about 1/2 hour if performed through the F interface, andfew minutes if the Ethernet interface is used.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

491 / 5923DB 16142 EAAA Ed.02


g ) After the software download completion, by SW Download ⇒ SW Status (seeFig. 326. on page 492), you can verify that the downloaded SW is present as Stand byversion; moreover, clicking on the Software Unit Status button, it is possible to see itscomponents and their version.

V02.01.01

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

492 / 592 3DB 16142 EAAA Ed.02


4–8.5 Activation of the new Software Package on the NE

After the software download (explained in previous para.4–8.4 on page 487), two software packages arepresent in the NE: one “Committed” and the other “Stand by”.

The Activation of the new Software Package on the NE means to make the “Stand by” SWP become the“Committed” one (and viceversa).

Step 1. Stand by SW activation

a ) Carry out SW Download ⇒ SW Status

Fig. 326. SW Status

b ) Fig. 327. below: select the Standby SW (1), set Activation (2) in the “SoftwareManagement Action” field, then Apply Action (3)

(1)

(2)

V02.01.01

(3)

V02.01.01

Fig. 327. Stand by SW activation

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

493 / 5923DB 16142 EAAA Ed.02


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 toclose)

Step 2. Logoff and Re–Login

a ) Logoff the NE

b ) Login the NE and verify, by SW Download ⇒ SW Status (see Fig. 326. on page 492), thatthe SW banks have changed their Current Status.

WARNING: once you have downloaded and made active the new SWP in NE environment, do notmake the mistake of trying to switch the previos version back to COMMITTED status (fordetails, read WARNING on page 495 ).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

494 / 592 3DB 16142 EAAA Ed.02


4–8.6 Additional operations for upgrade from V2.1.0

Proceed as follows:

After having carrying out for the first time:• the V2.1.1 SW download to the NE (para.4–8.4 on page 487)• and the activation of the V2.1.1 on the NE (para.4–8.5 on page 492)carry out for the second time:• the V2.1.1 SW download to the NE (para.4–8.4 on page 487), but, in phase c ) on page 490,

setting Forced before clicking on Init download (Fig. 328. below)

2_1_1

(1)

(2)

Fig. 328. Forced Init download

• and the activation of the Stand by V2.1.1 on the NE (para.4–8.5 on page 492)

N.B. Obviously, at the end of this procedure, you will have both SW banks with V2.1.1 SWP, and theV2.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) inSoftware Package: for this reason, if the active bank is V2.1.0, the download of SWP in the flash cardmust be executed in two steps:• with the first step (normal download procedure) all SW components known by previous SWP

version are downloaded on flash card;• new SWP component is known ONLY by SWP 2.1.1, so after the activation of package SWP

2.1.1, it is necessary to download SWP 2.1.1 again (IN FORCED MODE), to transfer the newSW component image onto flash card.

4–8.7 MIB save

At the end, create a new MIB back–up copy (associated to the new SWP–version), as described in chapter2–14 on page 301.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

495 / 5923DB 16142 EAAA Ed.02


4–9 ECT & NE UPGRADE FROM V2.1.0 TO V2.1.1

This chapter details all phases necessary to install a new SWP ’version’ in the PC environment as wellas in the equipment environment in both stations A and B of the radio link, i.e. in the following case:

– both ECT and equipment (in both stations A and B) are presently running with version V2.1.0– the new SWP V2.1.1 is delivered to Customer by means of the specific SWP CD–ROM.

Procedure:

[1] Preliminary checks and actions on both stations

1 ) if the former version of 2xFast Ethernet plug–in is equipped, it must be removed, and, ifenvisaged, the new version of 4xGbit Ethernet plug–in must be installed; for this purpose, carryout these operations on both stations:

a ) using the instructions given in the 9400AWY V2.1.0 User Manual:

• remove traffic on Fast Ethernet ports

• disable both Fast Ethernet ports

• unconfigure the 2xFast Ethernet plug–in

b ) phisically disinstall the 2xFast Ethernet plug–in

c ) and, if envisaged, install the DATA ENHANCED ON SITE UPGRADE KIT, makingreference to para.4–7.1 on page 469 of this manual

N.B. ignore the “unespected equipment” alarm that arises after the installation of the4xGbit Ethernet plug–in (it is not supported by SWP version V2.1.0)

2 ) check that no hardware or radio transmission problems are present (with exception of the“unespected equipment” alarm stated above). Otherwise, solve them before starting upgrade

3 ) close all Performance Monitoring, analog measurement and BER measurement processes, ifany

4 ) remove all loopbacks as well as all lockout, forced and manual commands on protectionschemes, if any

5 ) do not use functions stated above, or any other action not strictly necessary for the upgrade,until you have completed the SW upgrade of both stations, i.e. not before step [5] on page496 of this procedure.

6 ) WARNING:you must be aware that, once you have downloaded and made active the new SWP V2.1.1 inNE environment (at the end of step [3] for station A , and at the end of step [4] for station B),you cannot switch them back to V2.1.0, because there is no backward compatibility betweenV2.1.1 and V2.1.0 NE data base structures.In case you think you could need to go back to V2.1.0, before next step [2] , i.e. with SWP 2.1.0running both in PC and NE, prepare a spare Flash Card containing:– the SWP 2.1.0 as COMMITTED bank– the associated MIB dataRestoring this Flash Card in the system is the only way to make downgrade.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

496 / 592 3DB 16142 EAAA Ed.02


[2] Operations on local PC (station A)

1 ) Requirements: see para.3–1.1 on page 309 and para.4–8.1 on page 485.

2 ) on local PC, carry out the installation of the new SWP version in the ECT environment and theV2.1.1 NE software downloading preparation, as indicated in Chapter 3–1 from page 309 topage 325

N.B. The Craft Terminal configuration (para.3–1.9.1 on page 326 ) and the EMLconstruction (para.3–1.10 on page 327 ) are not considered necessary becauserelevant data should have already been defined during the CT installation made withSWP 2.1.0.

[3] V2.1.1 software download and activation on station A

3 ) connect the CT to the local NE (station A) by the suitable cross–connct Ethernet cable, launchthe V2.1.1 Craft Terminal and login the local NE (station A) by:

TCO Suite Main Menu ⇒ Operational & Maintenance

4 ) carry out the download (from the CT) and the activation of the new SWP version in the NEenvironment, executing in sequence the operations described in:

– SW download to the NE, para.4–8.4 on page 487

– activation of the new Software Package on the NE, para.4–8.5 on page 492

– additional operations for upgrade from V2.1.0, para.4–8.6 on page 494

[4] V2.1.1 software download and activation on station B

5 ) by RECT functionality, login the remote NE (station B) and carry out same operations madefor station A

[5] Carry out functional checks on radio link

E.g. Performance Monitoring, analog measurement, BER measurement, operations on protectionschemes, loopbacks, etc.

[6] Operations on remote PC (station B)

Do not forget to update also the PC(s) present in station B, as done in step [2]–2 ) above.

End of procedure

497 / 5923DB 16142 EAAA Ed.02


4–10 SWP DE–INSTALLATION

This chapter describes how to de–install from the PC the Craft Terminal Software Package components.This can be useful, for example, when a version of the software package is no more updated.

To de–install the following procedures can be followed:

– automatically, using the CD–ROM containing the installed Software–version product.

– manually, with the Control Panel of WINDOWS NT or WINDOWS 2000/XP when the CD–ROMcontaining the relevant Software product is not available.

Practically, the manual de–installation of the installed SW components must be done in the oppositesequence by which they were installed by the automatic installation process.

Manual procedure

N.B. Before starting this procedure, check that no SW components (or sub–processes) areactive; in case of doubts, restart the PC (switch it off / on).

From Control Panel select Add/Remove Programs and de–install the components in the followingorder:

1 ) CT–NE–ConfUpd (if present)

2 ) ALCATEL JUSM Help On Line (for all versions you like to remove)

3 ) ALCATEL SW Package REG.9400AWY (for all versions you like to remove)

4 ) ALCATEL Radio Common JUSM (for all versions you like to remove)

5 ) ALCATEL Q3CT–K–ADD–ONvX.Y.Z (1320CT)

6 ) ALCATEL SNMPCT–K–ADD–ONvX.Y.Z (1320CT)

7 ) ALCATEL HOLCT–K–ADD–ONvX.Y.Z (1320CT)

8 ) ALCATEL CT–KvX.Y.Z (1320CT)

9 ) Alcatel Lower Layers Manager & Tiny Tools

10 ) Java 2 Runtime Environment. SE vX.Y.Z_KJ

498 / 592 3DB 16142 EAAA Ed.02


a ) END OF SECTION 4

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

499 / 5923DB 16142 EAAA Ed.02

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1APPENDICES

SECTION 5: APPENDICES


Appendix A – Safety–EMC–EMF–ESD norms and equipment labellingIt describes the equipment labelling and the norms mandatory or suggested that mustbe considered to avoid injuries on persons and/or damage to the equipment.Moreover the labels affixed to the IDU and ODU equipment are described.

501

Appendix B – TCO suite start–up special conditionsThis Appendix describes some special conditions that may occur during the TCOSuite start–up and the countermeasures to take.

511

Appendix C – Additional SW installation operations for NE managementthrough the NE’s ECT serial port

This Appendix explains the operations necessary to allow the NE managementthrough the NE’s ECT serial port. Such operations are not necessary if you use TCOSuite and Craft Terminal accessing the NE through its Ethernet interface only.

517

Appendix D – General on Ethernet port characteristics and managementThis Appendix gives summary information that can be useful for the configuration ofEthernet ports.

547

Appendix E – ECT–Equipment connection via public switched telephonenetwork

This Appendix explains the operations necessary to allow the remote connection tothe F–Interface, from a local PC configurated as ECT, through a switched telephoneline of the standard Public Telephone Network.

553

Appendix F – Part lists of tool kits 563

Appendix G – Documentation guideIt contains all information regarding this handbook (purpose, applicability, history) andthe Customer Documentation set it belongs to, in particular the list of the handbooksthe Operators should have in order to carry out the required operations.

567

Appendix H – List of symbols and abbreviations, Glossary of terms 575

Appendix I – Customer documentation feedback 589

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

500 / 592 3DB 16142 EAAA Ed.02

USER MANUAL9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1APPENDICES

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

501 / 5923DB 16142 EAAA Ed.02


5–1 APPENDIX A: SAFETY–EMC–EMF–ESD NORMS ANDEQUIPMENT LABELLING


This appendix describes the equipment labelling and the norms mandatory or suggested (see also pointd ) on page 31) that must be considered to avoid injuries on persons and/or damage to the equipment.The stated norms apply both to the operations described in this manual and to those described in therelated manuals listed in para.5–7.2.1 on page 569.


– Compliance with International Standards herebelow

– Safety Rules on page 502 including:

• General Rules on page 502• Labels Indicating Danger, Forbiddance, Command on page 503• Dangerous Electrical Voltages on page 504• Risks of Explosions on page 505• Moving Mechanical Parts on page 505• Equipment connection to earth on page 506• Heat–radiating Mechanical Parts on page 506• Microwave radiations (EMF norms) on page 507• Specific safety rules in this handbook on page 508

– Electromagnetic Compatibility (EMC norms) on page 509 including:

• EMC General Norms – Installation on page 509• EMC General Norms – Turn–on, Tests & Operation on page 509• EMC General Norms – Maintenance on page 509

– Equipment protection against electrostatic discharges on page 510

– Suggestions, notes and cautions on page 510

– Labels affixed to the 9400AWY equipment on page 510

5–1.2 Compliance with International Standards

Refer to chapter 1–5 on page 127.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

502 / 592 3DB 16142 EAAA Ed.02


5–1.3 Safety Rules

5–1.3.1 General Rules

• Before carrying out any installation, turn–on, tests & operation and maintenance operationscarefully read the related parts of this Manual or other Handbooks, in particular:

– Installation: 9400AWY Installation Handbook

– Commissioning: Chapter 3–2 on page 329

– Maintenance: Section 4: Maintenance and Upgrade on page 407

• Observe safety rules

– When equipment is operating nobody is allowed to have access inside on the equipmentparts 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 operatingthis is allowed exclusively to service personnel, where for Service Personnel or Technicalassistance is meant :

”personnel which has adequate Technical Knowledge and experience necessary to beaware of the danger that he might find in carrying out an operation and of the necessarymeasurements 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 specifiedis not permitted.

The keys and/or the tools used to open doors, hinged covers to remove parts which giveaccess to compartments in which are present high dangerous voltages must belongexclusively to the service personnel.

– For the eventual cleaning of the external parts of the equipment, absolutely do not use anyinflammable 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 observeto 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 stationupstream (rack or station distribution frame).

• The safety rules described in this handbook are distinguished by the following symbol andstatement:

SAFETY RULES

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

503 / 5923DB 16142 EAAA Ed.02


5–1.3.2 Labels Indicating Danger, Forbiddance, Command

It is of utmost importance to follow the instructions printed on the labels affixed to the units and assemblies.

The labels are fully compliant with International Norms ISO 3846–1984. The symbols or statements areenclosed in geometric shapes: ISO 3864–1984.

CONTAINS A SYMBOL STATEMENT

CONTAINS A STATEMENT PROVIDING INFORMATIONOR INSTRUCTION.

CONTAINS A SYMBOLINDICATES WARNING OR DANGER (YELLOWBACKGROUND–BLACK SYMBOL AND RIM)

(YELLOW BACKGROUND–BLACK STATEMENT AND RIM)

INDICATES FORBIDDANCE (WHITE BACKGROUNDWHIT RED RIM–BLACK SYMBOL OR STATEMENT)

IT IS A COMMAND (BLUE BACKGROUND–WHITESYMBOL OR STATEMENT).

The labels have been affixed to indicate a dangerous condition. They may contain any standard–knownsymbol or any statement necessary to safeguard users and service personnel against the most commonones, specifically:

• dangerous electrical voltages

• harmful optical signals

• risk of explosion

• moving mechanical parts

• heat–radiating Mechanical Parts

• microwave radiations

Pay attention to the information stated in the following, and proceed as instructed

The symbols presented in para.5–1.3.3 through 5–1.3.8 are all the possible symbols thatcould be present on Alcatel–Lucent equipment, but are not all necessarily present on theequipment this handbook refers to.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

504 / 592 3DB 16142 EAAA Ed.02


5–1.3.3 Dangerous Electrical Voltages

5–1.3.3.1 Electrical safety: Labelling

The following warning label is affixed next to dangerous voltages (>42.4 Vp; >60 Vdc).

If it is a Class 1 equipment connected to mains, then the label associated to it will state that the equipmentwill have to be grounded before connecting it to the power supply voltage, e.g.:

WARNING !

Ground protect the equipment before connect-ing it to the mains

Make sure that power has been cut off beforedisconnecting ground protection.

5–1.3.3.2 Electrical safety: general rules

DANGER! Possibility of personal injury: carefully observe the specificprocedures for installation / turn–up and commissioning / maintenance of equipment parts where D.C..power is present, described in the relevant installation / turn–up and commissioning / maintenancedocuments and the following general rules:

a ) Personal injury can be caused by –48 V DC. Avoid touching powered terminals with any exposedpart of your body.

b ) Short circuiting, low-voltage, low-impedance, DC circuits can cause severe arcing that can result inburns and/or eye damage. Remove rings, watches, and other metal jewelry before working withprimary circuits. Exercise caution to avoid shorting power input terminals.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

505 / 5923DB 16142 EAAA Ed.02


5–1.3.4 Risks of Explosions

5–1.3.4.1 Labelling and safety instructions

This risk is present when batteries are used, and it is signalled by the following label:

Therefore, slits or apertures are made to let air circulate freely and allow dangerous gasses to down flow(battery–emitted hydrogen). A 417–IEC–5641 Norm. compliant label is affixed next to it indicating that theopenings must not be covered up.

5–1.3.5 Moving Mechanical Parts


The following warning label is affixed next to fans or other moving mechanical parts:

Before carrying out any maintenance operation see that all the moving mechanical parts have beenstopped.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

506 / 592 3DB 16142 EAAA Ed.02


5–1.3.6 Equipment connection to earth

Terminals for equipment connection to earth , to be done according to international safety standards, arepointed out by the suitable symbol:

terminal

symbol

The position of earth connection terminals is specified in the equipment Installation Handbook.

5–1.3.7 Heat–radiating Mechanical Parts


The presence of heat–radiating mechanical parts is indicated by the following warning label in compliancywith IEC 417 Norm, Fig.5041:

DANGER! Possibility of personal injury: carefully observe the specificprocedures for installation / turn–up and commissioning / maintenance of equipment parts whereheat–radiating mechanical parts are present, described in the relevant installation / turn–up andcommissioning / maintenance documents and the following general rule:

a ) Personal injury can be caused by heat. Avoid touching powered terminals with any exposed part ofyour body.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

EMF emissionwarning sign

507 / 5923DB 16142 EAAA Ed.02


5–1.3.8 Microwave radiations (EMF norms)

Equipment emitting RF power (Reminder from site preparation procedure):

– The site must be compliant with ICNIRP guidelines or local regulation if more restrictive.

– The following rules should be strictly applied by Customer:

• Non authorized persons should not enter the compliance boundaries, if any, for the generalpublic.

• Compliance RF boundaries, if any, related to Electro Magnetic Field exposure must be marked.

• Workers should be allowed to switch–off the power if they have to operate inside complianceboundaries.

• Assure good cable connection.

• Install the antenna as high as possible from floor or area with public access ( if possible thecylinder delimitating the compliance boundaries, if any, or the cylinder corresponding to thetransmission area directly in front of antenna with the same diameter as the antenna, more than2 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 trafficshutdown.

Place the relevant stickers:

On the site when applicable (when people can cross the complianceboundaries and/or the transmission area of the antenna, i.e. roof topinstallation)

– 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 ofantenna, visible by someone moving in front of the antenna (roof topinstallation)

On the antenna (rear side)

– EMF emission warning sign, placed on the antenna.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

508 / 592 3DB 16142 EAAA Ed.02


Compliance boundaries:

Tab. 73. Compliance boundaries for 9400AWY transceivers with 1ft (30 cm) antenna:

A

B

System Modulation Worst Configuration A (m) B (m)

9413 AWY Rel 2.0 4 QAM1+0 with integrated antenna

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





Antenna configurations:a ) 1+0 with 1ft. integrated antennab ) 1+1 HSB with coupler and 1ft. integrated antennac ) Configuration with separated 1ft. antenna

5–1.3.9 Specific safety rules in this Manual

Specific safety rules are specified in the following parts:– chapter 3–2 para.3–2.9 on page 404– chapter 4–5 :

• para.4–5.2.2 on page 430• para.4–5.3.1 on page 431• para.4–5.10.1 on page 454• para.4–5.10.2 on page 458• para.4–5.11 on page 460

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

509 / 5923DB 16142 EAAA Ed.02


5–1.4 Electromagnetic Compatibility (EMC norms)

The equipment’s EMC norms depend on the type of installation being carried out (cable termination,grounding etc.,) and on the operating conditions (equipment, setting options of the electrical/electronicunits, presence of dummy covers, etc.).

• Before carrying out any installation, turn–on, tests & operation and maintenance operationscarefully read the related parts of this Manual or other Handbooks, in particular:

– Installation: Installation Handbook– Commissioning: Chapter 3–2 on page 329– Maintenance: Section 4: Maintenance and Upgrade on page 407

• The norms set down to guarantee EMC compatibility, are distinguished inside this handbookby the symbol and term:

ATTENTION EMC NORMS

5–1.4.1 EMC General Norms – Installation

• All connections (towards the external source of the equipment) made with shielded cables useonly cables and connectors suggested in this Manual or in the relevant Plant Documentation,or those specified in the Customer’s”Installation Norms.” (or similar documents)

• Shielded cables must be suitably terminated• Install filters outside the equipment as required• Ground connect the equipment utilizing a conductor with proper dia. and impedance• Mount shields (if utilized), previously positioned during the installation phase, but not before

having cleaned and decrease it.• Before inserting the shielded unit proceed to clean and decrease all peripheral surfaces

(contact springs and connection points, etc.)• Screw fasten the units to the subrack.• To correctly install EMC compatible equipment follow the instructions given.

5–1.4.2 EMC General Norms – Turn–on, Tests & Operation

• Preset the electrical units as required to guarantee EMC compatibility• Check that the equipment is operating with all the shields properly positioned (dummy covers,

ESD connector protections, etc.)• To properly use EMC compatible equipment observe the information given

5–1.4.3 EMC General Norms – Maintenance

• Before inserting the shielded unit, which will replace the faulty or modified unit, proceed to cleanand 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

510 / 592 3DB 16142 EAAA Ed.02


5–1.5 Equipment protection against electrostatic discharges

Before removing the ESD protections from the monitors, connectors etc., observe the precautionarymeasures stated. Make sure that the ESD protections have been replaced and after having terminatedthe maintenance and monitoring operations.

Most electronic devices are sensitive to electrostatic discharges, to this concern the following warninglabels have been affixed:

Observe the precautionary measures stated when having to touch the electronic parts during theinstallation/maintenance phases.

Workers are supplied with antistatic protection devices consisting of (see Fig. 1. on page 36):

• an elasticized band worn around the wrist

• a coiled cord connected to the elasticized band and to the stud on the subrack.

5–1.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....

5–1.7 Labels affixed to the 9400AWY equipment

Following paragraphs indicates the positions and the information contained on the identification labelsaffixed to the equipment, with the exception of those already mentioned in para.5–1.3.2 ( page 503 ) to5–1.5 ( page 510 ):

– Labels affixed on the IDU: para.1–3.2 on page 69

– Flash Card identification labels: Fig. 35. on page 95

– Labels affixed on the ODU: para.1–4.2 on page 99

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

511 / 5923DB 16142 EAAA Ed.02


5–2 APPENDIX B: TCO SUITE START–UP SPECIAL CONDITIONS

This Appendix describes some special conditions that may occur during the TCO Suite start–up(para.2–2.2.3 on page 148 ) and the countermeasures to take.

Depending on selected browser, on browser configuration and preferences and on user’s choices somesecurity questions could be made to the user, like:

Active content may potentially harm your computer or disclose personal information. Are yousure to allow the CD for the execution of active content on the computer?

To proceed, you must answer YES.

In case of specific user’s browser configuration, the browser could ask some questions about “secure” or“blocked” content (Fig. 329. below) and before operating on TCO Suite pages user must click on thisinformation box (usually shown in a pale yellow background on top of the browser HTML page and allowthe browser to manage this information (Fig. 330. on page 512).

click

Fig. 329. Security Questions: Secure Content

As stated before, the layout and graphical representation for this question (if asked) could be different frombrowser to browser and, with respect to the same browser, language and information could vary too.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

512 / 592 3DB 16142 EAAA Ed.02


click

Fig. 330. Secure Questions: Allow Secure Content

Usually, the user has to click with the mouse on such yellow bar and a pop–up menu will appear to askuser if he/she allows running this special content (Fig. 330. above). In some cases another confirmationis requested to the user (Fig. 331. below).

Fig. 331. Execution confirmation (Security Warning)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

513 / 5923DB 16142 EAAA Ed.02


Generally speaking, as soon as the browser is allowed to execute Java applets inside the HTML page,a specific dialog will appear when browser recognizes that Java applets are inside the page.

As usual, both language and graphical layout could vary with respect to browser, operating systemversion, operating system and browser languages and so on. Following Fig. 332. and Fig. 333. show acouple of examples of this warnings: as wrote before, things can differ with respect to language or graphicsand so on.

Fig. 332. Security Warning (English browser on Italian System)

Fig. 333. Security Warning (Italian browser on Italian System)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

514 / 592 3DB 16142 EAAA Ed.02


This request is necessarily shown because TCO Suite applets needs specific parameters and permissionsin order to perform requested operations (reading and writing of files, for example). Applets used areauthenticated and a certificate is used to sign applets in order to tell user (and browser) that someone(Alcatel–Lucent Italia SpA, WTD R&D Software CC, in this case) guarantees about the safety in loadingthose applets inside a browser. Other examples could be more similar to the one shown in Fig. 334. below,usually with JREs with version number 1.4:

Fig. 334. Security Warning (Java 1.4)

Following Fig. 335. shows a wrong security warning with a Java version lower than 1.4. In this case theTCO Suite won’t work:

Fig. 335. Wrong Security Warning (Java 1.3)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

515 / 5923DB 16142 EAAA Ed.02


Another difference that user could perceive is related to a missing JRE but, even in this case, the graphicallayout will differ from system and browser.

If user opens the Start.html page even without a JRE installed shown page would differ from browserand system versions. Following Fig. 336. shows a Mozilla Firefox browser with no JRE installed. On topof browser a yellow alert bar can be seen: in this case the browser detected a special content for whichit has no plug–in so the browser asks the user to automatically install needed plug–in by searching it onthe Internet.

Fig. 336. Firefox browser: no JRE installed

If user allows to search for related plug–in, a specific operation could be started (Fig. 337. below).

Fig. 337. Firefox plug–in search

And if the user agrees, the browser could automatically install the correct plug–in (see following Fig. 338. ).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

516 / 592 3DB 16142 EAAA Ed.02


Since this operations is specifically related to Mozilla Firefox browser, some details could be different withrespect to used version. Anyway, since this operation is automatically managed by the browser no controlcan be made through TCO Suite. Using this procedure will usually install the latest JRE version availableas Mozilla Firefox plugin that is usually newer than the JRE 1.4.2_12 available within the TCO Suite.

Fig. 338. Firefox plug–in installation

As stated before, graphical layout, language, information, alert boxes and everything shown by a browserwould differ from each browser and operating system version or release.

Then, when Java applets and the Start.html page finally goes for a complete execution, the user willsee the content shown in Fig. 55. on page 149.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

517 / 5923DB 16142 EAAA Ed.02


5–3 APPENDIX C: ADDITIONAL SW INSTALLATION OPERATIONS FOR NEMANAGEMENT THROUGH THE NE’S ECT SERIAL PORT

5–3.1 Foreword

This procedure is referenced to by case b ) on page 311 , and is necessary only when you need to usethe NE’s ECT serial port to manage the NE itself by the Craft Terminal functions.

N.B. Carrying out this procedure is not necessary if you want to use TCO Suite and Craft Terminalfunctions, accessing the NE through its Ethernet interface only.

WARNING: the LLMAN installation (step [3] on page 518 ) must always be performed before the1320CT Package Installation (step [4] on page 518 ) . Installing the 1320CT Packagebefore the LLMAN may result in unproper working. If you have installed the 1320CTPackage without having installed before LLMAN, and after you want to install LLMAN, youmust:• un–install the1320CT application (see Chapter 4–10 on page 497 )• install LLMAN and, after, the 1320CT Package, as described in this Appendix.

Procedure:

[1] Installation start–up

1 ) Insert the SWP CD–ROM in the PC’s CD–ROM unit

2 ) The TCO Suite start–up begins. Please refer to para.2–2.2.3 on page 148 for the procedureexecution (in particular for JRE Package automatic installation) and the management of specialconditions that could occur

3 ) At the end of the TCO Suite start–up, the CD–ROM TCO Suite Main Menu screen appears(Fig. 339. below); click on Advanced Settings button

Fig. 339. CD–ROM TCO Suite Main Menu screen

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

518 / 592 3DB 16142 EAAA Ed.02


4 ) After a while, the CD–ROM TCO Suite Advanced Settings screen appears (Fig. 340. below)

Fig. 340. CD–ROM TCO Suite Advanced Settings screen

[2] In the CD–ROM TCO Suite Advanced Settings screen (Fig. 340. on page 518 ) click on button JavaJRE Package Installation . Please refer to para.2–2.2.5.1 on page 152 for details.N.B. as a matter of fact, the JRE Package Installation should have already been done in step

[1] – 2 ) on page 517

[3] Install LLMAN (Alcatel Lower Layers Manager), as described in para.5–3.2 from page 519

[4] Carry out the 1320CT Package Installation (installation in PC of SWP components from the SWPCD–ROM): see para.3–1.5 on page 314 , taking into account that , when you reach para.3–1.5.3on page 317 (Next step) you must come back here to execute steps from [5] below

[5] Install and configure Alcatel Virtual Network Card for Lower Layers, as described in para.5–3.3from page 522 (different sub–procedures, according to the PC Operating System)

[6] Complete the Craft Terminal set–up carrying out the following phases:

1 ) Local copy in PC environment of the TCO Suite:para.3–1.6 on page 318

2 ) End of SW installation from SWP CD–ROM:para.3–1.7 on page 320

3 ) NE software downloading preparation:para.3–1.8 on page 321

4 ) CT initial configuration:para.3–1.9 on page 326

5 ) EML construction:para.3–1.10 on page 327

END OF PROCEDURE

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

519 / 5923DB 16142 EAAA Ed.02


5–3.2 Installation of LLMAN from the SWP CD–ROM


1 ) In the CD–ROM TCO Suite Advanced Settings screen (Fig. 340. on page 518) click on buttonSerial–F–Interface Driver InstallationThis function performs the installation for the “Alcatel Lower Layers Manager” together with thedrivers needed for the “Alcatel Virtual Network Card for Lower Layers”. A splash screen willappear as soon as the button applet is clicked (Fig. 341. below) and the installation begins.

Fig. 341. Alcatel Lower Layers Manager ”splash screen”

2 ) User is asked to select installation and application language (Fig. 342. below).

Fig. 342. Alcatel Lower layers Manager language selection

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

520 / 592 3DB 16142 EAAA Ed.02


3 ) Then the installation is carried out automatically after a simple confirmation by the user(Fig. 343. below).

Fig. 343. Alcatel Lower Layers Manager Installation screens

4 ) Select “Configure Lower Layer” and press “FINISH” button to open next screen (followingFig. 344. )

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

521 / 5923DB 16142 EAAA Ed.02


Fig. 344. Alcatel Lower Layers Manager setting screen

5 ) In screen of Fig. 344. above, complete the configuration and press OK button.

N.B. If a network adapter is not running in the PC, you can set the “System identifier”fieldwith a sequence of 12 “0”. The following window will be displayed.

6 ) Press YES button to confirm.

5–3.2.2 Next step

You have now completed the Installation of LLMAN from the SWP CD–ROM.

Now, you must proceed with step [4] on page 518

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

522 / 592 3DB 16142 EAAA Ed.02


5–3.3 Installation and configuration of Alcatel Virtual Network Card for LowerLayers

At first SWP installation on ECT, after the installation of Alcatel Lower Layer Manager (carried out inprevious para.5–3.2 on page 519), it is necessary, for NE connection using TCP/IP through serial port, toconfigure a Virtual Network Card.

Alcatel Virtual Network Card for Lower Layers is a software component used by Alcatel Lower LayersManager to manage TCP/IP packets through the serial port.

Follow this guide to install and configure Alcatel Virtual Network Card for Lower Layers using theControl Panel.

5–3.3.1 Important warning

Whenever, after the completion of this step, you must install a new network card, always verifythat the Alcatel Virtual Network Card for Lower Layers is always the firstone in the “Network Connections” list. Refer to para.5–3.3.6 on page 546 for details.

5–3.3.2 Choice of the procedure, according to Windows platform

for installation and configuration on refer to paragraph on page

Windows NT 4.0 (partially supported) 5–3.3.3 523

Windows 2000 till SP2 5–3.3.4 529

Windows XP till SP2 (Professional Edition only) 5–3.3.5 537

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

523 / 5923DB 16142 EAAA Ed.02


5–3.3.3 Windows NT 4.0

5–3.3.3.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows NT 4.0)

To install the Alcatel Virtual Network Card for Lower Layers select the Adapters tab in the Network ControlPanel applet.

After installing Alcatel Virtual Network Card for Lower Layers you need to configure it following theinstruction of the Windows NT 4.0: Configuring Alcatel Virtual Network Card for Lower Layers section.

Before installing Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol (pleaserefer to Windows NT Help).– Click the Add... button in the Adapter tab of the Network Control Panel applet.

Fig. 345. Windows NT installation step 1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

524 / 592 3DB 16142 EAAA Ed.02


– In the Insert Disk dialog box, type the source path of the driver files copied during installation phase(e.g. C:\WinNT\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from a Command Promptwindow to discover the right location of the WinNT folder) and click OK.


– If the dialog box in Fig. 347. appears, the driver is already installed.


Alcatel Virtual Network Card for Lower Layers is now installed. You need to configure its TCP/IPparameters before use it in with Alcatel Lower Layers Manager. Proceed with para.5–3.3.3.2 on page525.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

525 / 5923DB 16142 EAAA Ed.02


5–3.3.3.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows NT 4.0)

To configure the Alcatel Virtual Network Card for Lower Layers use both the Bindings and the Protocolstabs in the Network Control Panel applet.

Before configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol(please refer to Windows NT Help).

This operation must be performs at Administrator of the PC, because it subsequently could be toset IP address .

To install the Alcatel Virtual Network Card for Lower Layers run the Network Control Panel applet fromthe Control Panel.

– Select the bindings of Alcatel Virtual Network Card for Lower Layers in the Bindings tab (1), (2) ofthe Network Control Panel applet.

– Disable any unneeded component (3), (4).

– Selecting the Protocols tab (5) of the Network Control Panel applet, the either a message box(Fig. 349. NT configuration step 2) or a dialog box (Fig. 350. NT configuration step 3) may appear.

– Follow the instructions until the dialog box (Fig. 351. NT configuration step 4) will appear.

1

2

3

4

5

Fig. 348. Windows NT configuration step 1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

526 / 592 3DB 16142 EAAA Ed.02


– Click Yes to save changes.


– Select Protocols tab (1), TCP/IP Protocol (2) and click the Properties button (3).

1

2

3


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

527 / 5923DB 16142 EAAA Ed.02


– Configure the IP Address and the Subnet Mask for the Alcatel Virtual Network Card for LowerLayers and push OK.

1

2

3

4

5


*** WARNING ***

If the IP Address of the Virtual Network Card has been changed after a complete SWP installation, it isnecessary, for a correct ECT functionality, to perform an explicit ECT re–customization by executing thefollowing command:

– Start → Programs → Alcatel → SNMPCT–K–ADD–ON v... → SNMP Add–On Customization

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

528 / 592 3DB 16142 EAAA Ed.02


– Click Close in the Protocols tab of the Network Control Panel applet.


– The new configuration of Alcatel Virtual Network Card for Lower Layers will be used at the next restartof the computer.

– If you are configuring or installing the Alcatel Virtual Network Card for Lower Layers you can click Yes.If you are installing some other component you should click No and restart the computer later.


5–3.3.3.3 Next step (Windows NT 4.0)

You have now completed the installation and configuration of the Alcatel Virtual Network Card for LowerLayers in Windows NT 4.0 environment. Now proceed with the Check for the “Network Connections”order, para.5–3.3.6 on page 546.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

529 / 5923DB 16142 EAAA Ed.02


5–3.3.4 Windows 2000

The System Standby function in the Power Option menu of the Control Panel must be alwaysdisabled (select in the Power Schemes tab panel in the Power schemes field “Always On”).

5–3.3.4.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows 2000)

To install the Alcatel Virtual Network Card for Lower Layers run the Add/Remove Hardware Wizard fromthe Control Panel.Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IPprotocol (please refer to Windows 2000 Help).Please make sure of Alcatel Virtual Network Card for Lower Layers is not already installed on your PC:Alcatel Virtual Network Card for Lower Layers has to be installed only once.After installing Alcatel Virtual Network Card for Lower Layers you need to configure it following theinstruction of the Windows 2000: Configuring Alcatel Virtual Network Card for Lower Layers section.

– Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.

Fig. 354. Windows 2000 installation step 1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

530 / 592 3DB 16142 EAAA Ed.02



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

531 / 5923DB 16142 EAAA Ed.02


– Click the Have Disk... button in the Select Network Adapter dialog box.


– In the Install From Disk dialog box, type the source path of the driver files copied during installationphase (e.g. C:\WinNT\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from a CommandPrompt window to discover the right location of the WinNT folder) and click OK.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

532 / 592 3DB 16142 EAAA Ed.02


– Click Next in the Start Hardware Installation dialog box.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

533 / 5923DB 16142 EAAA Ed.02


5–3.3.4.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows 2000)

This operation must be performs at Administrator of the PC, because it subsequently could be toset IP address .

To configure the Alcatel Virtual Network Card for Lower Layers run the Network and Dial–up connectionsapplet from the Control Panel.

Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IPprotocol (please refer to Windows 2000 Help).

To install the Alcatel Virtual Network Card for Lower Layers run the Add/Remove Hardware Wizard fromthe Control Panel.

– Open the network connection using the Alcatel Virtual Network Card for Lower Layers from theNetwork and Dial–up connections applet.

Fig. 359. Windows 2000 configuration step 1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

534 / 592 3DB 16142 EAAA Ed.02


– Uncheck any unneeded component in the Properties dialog box General tab (1). Check and selectthe Internet Protocol (TCP/IP) component (2) and click Properties (3).

1

2

3


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

535 / 5923DB 16142 EAAA Ed.02


– Configure the IP Address (1) and the Subnet Mask (2) and push Advanced (3) to open the relevantAdvanced TC/IP Settings screen

– In the Advanced TC/IP Settings screen’s Interface Metric field, write 50 (4) and push OK (5)

– Having come back to the first screen, push OK (6)

6

1

2

3

4

5


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

536 / 592 3DB 16142 EAAA Ed.02


Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers Managerto use it.

*** WARNING ***



5–3.3.4.3 Next step (Windows 2000)

You have now completed the installation and configuration of the Alcatel Virtual Network Card for LowerLayers in Windows 2000 environment. Now proceed with the Check for the “Network Connections”order, para.5–3.3.6 on page 546.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

537 / 5923DB 16142 EAAA Ed.02


5–3.3.5 Windows XP (Professional Edition only)

The System Standby function in the Power Option menu of the Control Panel must be alwaysdisabled (select in the Power Schemes tab panel in the Power schemes field “Always On”).

5–3.3.5.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows XPProfessional Edition)

To install the Alcatel Virtual Network Card for Lower Layers run the Add Hardware Wizard from the ControlPanel.

After installing Alcatel Virtual Network Card for Lower Layers you need to configure it following theinstruction of the Windows XP: Configuring Alcatel Virtual Network Card for Lower Layers section.

Please make sure of Alcatel Virtual Network Card for Lower Layers is not already installed on your PC:Alcatel Virtual Network Card for Lower Layers has to be installed only once.

– Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

538 / 592 3DB 16142 EAAA Ed.02


Fig. 362. Windows XP installation step 1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

539 / 5923DB 16142 EAAA Ed.02



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

540 / 592 3DB 16142 EAAA Ed.02


– Click the Have Disk... button in the Select Network Adapter dialog box.


– In the Install From Disk dialog box, type the source path of the driver files copied during installationphase (e.g. C:\Windows\System32\Drivers\LLmanNIC; type ”echo %systemroot%” from aCommand Prompt window to discover the right location of the Windows folder) and click OK.

C:\Windows\System32\Drivers\LLmanNIC


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

541 / 5923DB 16142 EAAA Ed.02


– Click Next in the The wizard is ready to install your hardware dialog box.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

542 / 592 3DB 16142 EAAA Ed.02


5–3.3.5.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows XPProfessional Edition)

This operation must be performed by the Administrator of the PC, because it subsequentlycould be to set IP address .

To configure the Alcatel Virtual Network Card for Lower Layers run the Network connections applet fromthe Control Panel.

To install the Alcatel Virtual Network Card for Lower Layers run the Add/Remove Hardware Wizard fromthe Control Panel.

– Open the network connection using the Alcatel Virtual Network Card for Lower Layers from theNetwork and Dial–up connections applet.

Fig. 367. Windows XP configuration step 1

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

543 / 5923DB 16142 EAAA Ed.02


– Uncheck any unneeded component (disable always the QoS Packet Scheduler – 1 –) in theProperties dialog box General tab. Check and select the Internet Protocol (TCP/IP) component (2)and click Properties (3).

12

3


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

544 / 592 3DB 16142 EAAA Ed.02


– Configure the IP Address (1) and the Subnet Mask (2) and Advanced option (3) and then push OK(4).

4

1

2

3


*** WARNING ***



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

545 / 5923DB 16142 EAAA Ed.02


– Configure the Advanced TCP/IP Settings dialog box select the WINS sheet (1), Disable NetBIOSover TCP/IP (2) and then push OK (3).

1

2

3


Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower LayersManager to use it.

5–3.3.5.3 Next step (Windows XP Professional Edition)

You have now completed the installation and configuration of the Alcatel Virtual Network Card for LowerLayers in Windows XP (Professional Edition only) environment. Now proceed with the Check for the“Network Connections” order, para.5–3.3.6 on page 546.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

546 / 592 3DB 16142 EAAA Ed.02


5–3.3.6 Check for the “Network Connections” order

For the SWP to operate correctly, it is necessary that the Alcatel Virtual Network Card for Lower Layersis always the first one in the “Network Connections” list.

To carry out this check, operate as follows:

1 ) Start → Control Panel → Network Connections

2 ) in the field “LAN or High Speed Internet”, select the Device Name “Alcatel Virtual NetworkCard for Lower Layers”

3 ) from “Advanced” menu, select “Advanced Settings”

4 ) in the relevant screen (Fig. 371. below) verify that it is the first in the list. If necessary, move itsposition, using suitable arrows.

Fig. 371. Check for the “Network Connections” order

Whenever, after the installation of this SWP, you must install a new network card, always verifythat the Alcatel Virtual Network Card for Lower Layers is always the first one in the “NetworkConnections” list.

You have now completed the installation, configuration and check of the Alcatel Virtual Network Card forLower Layers. Now proceed with step [6] on page 518

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

547 / 5923DB 16142 EAAA Ed.02


5–4 APPENDIX D: GENERAL ON ETHERNET PORT CHARACTERISTICSAND MANAGEMENT

This Appendix gives summary information that can be useful for the configuration of Ethernet ports.

5–4.1 Ethernet Physical Interface

The Enhanced Ethernet plug–in provides 4 Electrical Gigabit Ethernet ports. Each port performs allphysical 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.

5–4.2 MDI/MDIX crossover

Allows two Ethernet interfaces to be connected directly, without the need to differentiate the cablesas straight or cross–over. This feature allows the use of only one type of ethernet cable in field anddoes not require ECT/NM management.

5–4.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/sand 9728 bytes (jumbo frame) for ports at 1 Gbit/s.FCS field, inside each ethernet frame, is checked; if the check is wrong, the packet is discarded.FCS is always enabled.

5–4.4 Ethernet capacity

With the 100/1000 Base–T Ethernet interfaces, the PDH transport capability is always less than themaximum input bit rate, whereas in case of 10Base–T, the PDH transport capability can be larger orsmaller 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 isdefined by the available frame structure configuration (i.e. 16xE1). Given a gross bit rate, thecombinations of E1 tributaries and data tributaries that can be realized are defined in Tab. 65. onpage 350 .Obviously, the maximum compression of the data signals is reached when the space of only onetributary is reserved, the compression decreases if the space or more tributaries is reserved.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

548 / 592 3DB 16142 EAAA Ed.02


5–4.5 Ethernet flow control

The total radio capacity allocated for global Ethernet traffic is shared between all enabled Ethernetports. The modality of division of the bandwidth among the ports Ethernet enabled is defined fromthe mechanism of QoS configured (see point [8] on page 551 ).When the traffic data bandwidth requested is bigger than available radio capacity two actions arepossible:• 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 bethe 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 whenthe 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 full–duplex.

5–4.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, auto–negotiation is disabled) or automatic mode (auto–negotiation is enabled):these two modalities are valid always for Fast Ethernet signals, only automatic mode for GigabitEthernet signals. In automatic mode a mechanism of auto–sensing (the auto–negotiation) ofthe parameters involved is activated, these parameters are negotiated with the remote Ethernetinterface.Auto–negotiation 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 auto–negotiation restart

During auto–negotiation, each port automatically chooses its mode of operation by advertisingits abilities and comparing them with those received from its link partner.

The parameters that can be advertise during auto–negotiation from each port must be selectedbetween 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 autonegotiationenabled, the link could be established with 10 or 100 Mbit/s speed and half–duplex capability(as defined by the standard 802.3).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

549 / 5923DB 16142 EAAA Ed.02


The following items resume the features supported by ULS in terms of Gigabit EthernetPhysical interface management:– auto–negotiation 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 full–duplex (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, thedirectionality is always full–duplex);

– when the auto–negotiation process fails or when the auto–negotiation parameters arechanged, the auto–negotiation restart command has to be performed in order to have newconfigured parameters effective.

[2] Ethernet Port Layer

The following items resume the features supported by ULS in terms of Gigabit Ethernet Portlayer management:– the Pause function is allowed only when the capability is full–duplex;– 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 caseis 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 queuescauses to discard any further received MAC frames: a correct frame received anddiscarded because of an input queues overflow, is not counted as a received frame;

– total transparency towards the IEEE 802.1Q (VLAN management is presently notsupported);

– Ethernet corrupted frames (Tx and Rx side independently) can be discarded or forwardedto the addressed destination, according to the related SNMP manager request.

5–4.7 Ethernet Switch

The fundamental component of Enhanced data plug–in is the Ethernet switch, which provides theswitching, 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 devicesthat enable multiple physical ethernet LAN segments to be interconnected into a single largernetwork.

The switch supports the following function:

[1] MAC Switching

The switch is capable of evaluate the destination address of each frame received and totransmit the individual frames to the correct egress port in according to information containedin a database “address resolution table” and associated to destination address. If switch doesnot know on which port to forward the frame (destination address is not present in “addressresolution table”), it sends the packet on all ports (flooding). The switch must perform halftransparent bridge functionality that’s 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

550 / 592 3DB 16142 EAAA Ed.02


[2] MAC Learning

The entry in a database, the “address resolution table” is written learned the source addressfrom received unicast packets. The switch supports also static writing of the “address resolutiontable”, 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 anindicative value, the real range is 300 ÷ 600 seconds)

The aging process periodically removes dynamically learned addresses from the “addressresolution table”.The address aging process is used to ensure that if a node is disconnected from the networksegment, or it become inactive, its entry is removed from address database. Aging makes roomfor 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: DWRRalgorithm 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 queueaccording to their priority. Algorithms type Deficit Weighted Round Robin (DWRR) and HighQueue Preempt (HQP) are used to schedule each transmit queue.The ”deficit weighted round–robin” algorithm allows each queue to be serviced in turn, sendinga set amount of packets before moving to the next queue. For every round are sent 8 packetsfrom queue with highest priority and respectively 4, 2, 1 packets from the queues with lowerpriority.

[5] Frame types

The switch is able to treat Ethernet frames of the following types: Ethernet v2, 802.3, 802.1Q.No ECT/NM management is necessary.

[6] IEEE 802.1Q (VLAN management)

In current SWP version, the traffic type IEEE 802.1Q tag is managed in transparent mode (theswitch does not look the tag).

The IEEE 802.1Q tag VLAN feature is enabled including between the other the stripping oradding of the TAG and VLAN lookups in addition to MAC lookups (this feature can be useful tologically break a physical LAN into a few smaller logical LAN and prevent data to flow betweenthe sub–LAN).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

551 / 5923DB 16142 EAAA Ed.02


[7] IEEE 802.3x Flow Control

In case of incoming Ethernet traffic leading to exhaustion of buffers on input queues, PAUSEframes are transmitted in order to slow down remote peer MAC layer.When the flow control is activated any packets shall not be lost.The flow control management is foreseen only for the four user ports and not for the port linkedto the FPGA.

[8] QoS management (IEEE 802.1p, IP–V4 ToS & DiffServ, Port based)

The Ethernet switch provides a Quality of Service mechanism to control all streams. The QoSfeature, referred to the four ports (line side) Gigabit Ethernet, provides up to four internal queuesper port (four user ports and one radio) to support four different traffic priorities. These prioritiescan be programmed in such a way that high–priority traffic in the switch experiences less delaythan lower–priority traffic under congested conditions.For Ethernet flows in the switch, it is possible by CT/NMS (see Fig. 131. on page 231 , andFig. 248. on page 352 ) to choose how assign the priority to each packet according to theinformation in:

a ) IEEE std 802.1p

The packet is examined for the presence of a valid 802.1P userpriority tag. If the tag ispresent the correspondent priority is assigned to the packet.When 802.1p QoS mechanism is adopted the reference is the standard “IEEE802.1D–2004 Annex G User priorities and traffic classes” that defines 7 traffic types andthe corresponding user priority values.Considering that the switch has four egress queues for each port, the mapping 802.1pvalue to queue is the following:

Tab. 74. QoS based on IEEE std. 802.1p

802.1P priority Queue

111,110 Queue 4 (higher priority)

101,100 Queue 3

011,000 Queue 2

010,001 Queue 1 (lower priority)

When an incoming packet is not 802.1p it is assigned to the lowest priority queue.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

552 / 592 3DB 16142 EAAA Ed.02


b ) DiffServ

When DiffServ QoS mechanism is adopted the classification uses the DS field of the IPpacket 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 DSCPvalue (6 bits) to queue is the following:

Tab. 75. QoS based on DiffServ

DiffServ priority Queue

111000, 110000, 101110, 101000 Queue 4 (higher priority)

100110, 100100, 100010, 100000, 011110,011100, 011010, 011000

Queue 3

010110, 010100, 010010, 010000, 001110,001100, 001010, 001000, 000000

Queue 2

all the remaining values Queue 1 (lower priority)

When an incoming packet has not DiffServ valid value, it is assigned to the lowest priorityqueue.

[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 toform a single logical channel. In this way provides a more resilient end to end connection, andenables load balancing.The switch supports:– automatic fail–over: 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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

553 / 5923DB 16142 EAAA Ed.02


5–5 APPENDIX E: ECT–EQUIPMENT CONNECTION VIA PUBLICSWITCHED TELEPHONE NETWORK


This chapter explains the operations necessary to allow the remote connection to the F–Interface, froma local PC (with external or internal modem) configured as ECT, through a switched telephone line of thestandard Public Telephone Network, as shown in Fig. 372. here below.

This kind of remote control is possible for a single equipment as well as for a whole subnetwork.

Telephone net-work

PC/ECT

remote side(equipment side)

RemoteModem

LocalModem

F Interface

Port COM

PC–LAPTOP/ECTwith internal modem

local side(ECT side)

Fig. 372. ECT–Equipment connection via Public Switched Telephone Network

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

554 / 592 3DB 16142 EAAA Ed.02


5–5.2 Certified equipment

The connection has been successfully tested:

a ) with the following types of modems:

1 ) Modem Sportster Flash (US Robotics)

2 ) Modem TD–32 AC (Westermo Teleindustri AB)

3 ) 3Com 56K Faxmodem

b ) with the following types of PC:

1 ) with external modem:characteristics as in para.3–1.1.1 on page 309

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 inpoint b ) 2 ) above

Sportster Flashpoint b ) 2 ) above

3Com 56K Faxmodem

Testing the connection with different types of modems is fully on Customer’s charge.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

555 / 5923DB 16142 EAAA Ed.02


5–5.3 Connection cables

In the following figures, the cables for the connections are described:

PC/ECT (DTE)Cannon 9 pins female

Local Modem (DCE)Cannon 25 pins male

DCD

TD

RD

DTR

DSR

RTS

CTS

GND

DCD

TD

RD

RTS

CTS

DSR

DTR

GND

1

3

4

6

7

8

5

8

5

6

20

7

2 3

4

2

Fig. 373. ECT–Local external Modem cable

Remote Modem (DCE)Cannon 25 pins male

F Interface (DCE)Cannon 9 pins male

TD

RD

RTS

CTS

DSR

CTS

GND

TD

RD

RTS

CTS

DSR

DTR

GND

2 3

4

5

6

20

7

3

2

7

8

6

5

4

Fig. 374. F Interface–Remote Modem cable

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

556 / 592 3DB 16142 EAAA Ed.02


5–5.4 Modem setting

5–5.4.1 Setting of Sportster Flash Modem & 3Com 56K Faxmodem

This modem requires only a SW setting via serial port.

There is a little difference between local and remote modems setting (refer to Fig. 372. on page 553 forthe distinction between “local” and “remote”), relevant to the auto–answer option that must be set in theremote modem and not set in the local modem.

LOCAL MODEM SETTING

To set the local modem, proceed as follows:

1 ) Only for external modem: connect the local modem to the PC/ECT with the cable of Fig. 373. onpage 555.

2 ) Only for external modem: Power and switch on the local modem.

3 ) On the PC, activate program HyperTerminal and configure the PC–Modem serial line with thefollowing parameters:

* Bits per second: 38400* Data Bits: 8* Parity: None* Stop Bit: 1* Flow control: None

4 ) Execute and store the modem set–up, writing the following commands in the HyperTerminalprogram 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, ifnecessary.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

557 / 5923DB 16142 EAAA Ed.02


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:

ATI4U.S. Robotics Sportster Flash 56000 Settings... B0 E1 F1 L2 M1 Q0 V1 X3 Y0BAUD=38400 PARITY=N WORDLEN=8DIAL=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=004S07=060 S08=002 S09=006 S10=014 S11=072 S12=050 S13=000S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019S25=005 S27=001 S28=008 S29=020 S30=000 S31=128 S32=002S33=000 S34=000 S35=000 S36=014 S38=000 S39=012 S40=000S41=004 S42=000 LAST DIALED #:

REMOTE MODEM SETTING

To set the remote modem, proceed as follows:

a ) carry out same steps 1 ) , 2 ) , 3 ) as for local modem setting

b ) execute and store the modem set–up, writing in the HyperTerminal program window the samecommands described in step 4 ) for the local modem setting, and adding the following command:

ATS=1<Return> (Auto–answering setting)

c ) now, setting has been completed. Modem can be switched off and disconnected, if necessary.

N.B. For confirmation, the modem configuration can be checked writing the command“ATI4<Return>” in the HyperTerminal program window.Information displayed should be equal to that displayed for the local modem, with only thedifference for field S00:

S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

558 / 592 3DB 16142 EAAA Ed.02


5–5.4.2 TD–32 AC Modem setting

This modem requires an initial HW set–up via dip–switches and a SW setting via serial port.

To set the modem, both local and remote, proceed as follows:

1 ) The initial HW set–up via dip–switches is indicated in Fig. 375. herebelow:

ON

SW31 2 3 4 5 6 7 8

ON

SW21 2 3 4 5 6 7 8

ON

SW11 2 3 4

ON

SW51 2 3 4 5 6 7 8

ON

SW41 2 3 4 5 6 7 8

Fig. 375. TD–32 AC modem dip–switch setting

2 ) Connect the local modem to the PC/ECT with the cable of Fig. 373. on page 555.

3 ) Power on the local modem (there is no an ON/OFF switch).

4 ) On the PC, activate program HyperTerminal and configure the PC–Modem serial line with thefollowing parameters:


5 ) Execute and store the modem set–up, writing the following commands in the HyperTerminalprogram window:

AT&F1<Return> (Best PC default configuration recall)AT&K0<Return> (DTE/DCE flow control disabling)ATA<Return> (Automatic Answer enabling ––> Only on Remote modem and

wait the message “NO CARRIER”)AT&W0<Return> (Configuration store in NVRAM 0)AT&Y0<Return> (Configuration Set to load at switch–on: NVRAM 0)

6 ) Now, setting has been completed. Modem can be switched off and disconnected, if necessary.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

559 / 5923DB 16142 EAAA Ed.02


N.B. For confirmation, the modem configuration can be checked writing the command“AT\S<Return>” in the HyperTerminal program window.Information displayed should be as follows:

AT\S 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.......043B BELL MODE........OFF &G GUARD TONE......NONE S3 <CR> CHAR........013E CMD ECHO..........ON &K FLOW CONTROL....NONE S4 <LF> CHAR........010F LINE MODE.......AUTO &L NETWORK.........PSTN S5 <BS> CHAR........008L SPKR VOLUME......LOW &Q ASYNC/SYNC.........5 S7 CONNECT TIME.....060M SPKR CONTROL....CALL &R RTS/CTS.........AUTO S8 PAUSE TIME.......002N AUTO MODE.........ON &S DSR OPT............0 S12 ESC GUARD TIME...050Q QUIET............OFF &T ENABLE RDL........NO S30 CONNECT INACT....000V RESULT FORM.....LONG &X SYNC CLOCK.......INT S32 XON CHAR.........017W EC MSG.............0 &Y PROFILE........NVM.0 S33 XOFF CHAR........019X EXT RESULTS........4 \A MAX BLK SIZE.....192 S36 FALLBACK ACTION..007Y 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

5–5.5 PC laptop “Dell Latitude” setting

The following setting must be done:

Control Panel –> Alcatel Lower Layer –> Serial port –> COM3 and Serial port selected

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

560 / 592 3DB 16142 EAAA Ed.02


5–5.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. 372. on page 553 for the distinction between “local” and “remote” modems.

N.B. Leaving the remote modem permanently switched on and permanently connected toF–interface and telephone line, operations set up by steps 1 ) thru 4 ) , it is possible to accessthe equipment in any moment.In order to access the equipment by local ECT, proceed as specified in steps 5 ) thru 14 ) .

1 ) Connect the remote modem to equipment’s F interface with the cable of Fig. 374. on page 555.

2 ) Connect the remote modem to the telephone line (as far as Sportster Flash model is concerned,the connector to be used is the nearest to that used for the connection with equipment’s Finterface and signed with the ’wall’ symbol).

3 ) Power and switch on the remote modem.

4 ) Be sure remote equipment is switched on and correctly working.

5 ) Connect the local modem to the PC/ECT (with the cable of Fig. 373. on page 555.) on the serialport assigned for the connection with F interface (usually COM1).

6 ) Connect the local modem to the telephone line (as far as Sportster Flash model is concerned,the connector to be used is the nearest to that used for the connection with equipment’s Finterface).

7 ) Power and switch on the local modem.

8 ) On the PC, activate program HyperTerminal and configure the PC–Local Modem serial line withthe following parameters:


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 (thiscommand is not stored in the modem NV RAM).

10 ) Execute the telephone call from the PC writing the following command in the HyperTerminalprogram window:

ATDnnn<Return>

where “nnn” is the telephone network number associated to the remote telephone line (thatwhich 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 connectionbetween local and remote modems, switching off the local modem or physically disconnectingthe cable connecting it to the PC.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

561 / 5923DB 16142 EAAA Ed.02


5–5.7 Changing the ECT–equipment connection speed


This feature is meant to use modems with speed different from that documented in previous paragraphs,giving the possibility to configure the ECT connection through modem (speed values: 9600, 19200, 38400,56000) with automatic management of modem set–up and phone call at ECT start–up.

To make change operative, the following operations are necessary:

– at equipment side, the configuration must be set–up as explained in the para.5–5.7.2 below,

– at PC side, the configuration must be set–up as explained in the following para.5–5.7.3 on page 562,

– as far as the modem is concerned, please refer to the constructor documentation.

5–5.7.2 Configuration at NE side

1 ) Login the NE through the TCO Suite Alarms & Settings function (see para.2–2.3.1 on page156) using a login profile allowing the Modem Speed change (see Tab. 55. on page 158),

2 ) enter the Modem Speed screen and set the required speed (see para.2–2.3.9 on page 167).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

562 / 592 3DB 16142 EAAA Ed.02


5–5.7.3 Configuration at PC side

To configure the modem with the relevant speed, enter the menu Settings –> Control Panel of theOperating System and open the Alcatel Lower Layers utility. The menu of Fig. 376. opens.

Fig. 376. Alcatel Lower Layers utility

In the Sub–network Type field select Modem.In the Modem field select the suitable Modem type.In the Modem speed field select the suitable speed (9600, 19200 or 38400) and click on OK.In the Phone Number field enter the phone number, which will be automatically called at the ECT start–up.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

563 / 5923DB 16142 EAAA Ed.02


5–6 APPENDIX F: PART LISTS OF TOOL KITS

This appendix supplies information referenced to by para.4–3.2.2 on page 416

These part lists are given for general information purpose. The parts listed in each tool kit could differ fromthose actually delivered inside the kit (make reference to the part list accompanying the kit).

5–6.1 Installation Tool Kit part list

P/N Description

1AD035000002 HAND TOOL MALE WRENCHE


870952129 CHIAVE FISSA I6XI7


870952417 CHIAVE PIEGATA COMB.ESAG.17

870952706 CHIAVE X ESAG.INCASSATO 6

870959166 CACCIAVITE 5,5X200

879010249 TOOL KEY 5,5 MM

879010250 TOOL KEY 7 MM

8BE815010002 8X10 FIXED SPANNER

8BE815010070 TORQUE WRENCH

8BE815010080 ALLEN WRENCH

8BE815020020 3XIOO SCREWDRIVER

8BE815020021 3.5X100 SCREWDRIVER

8BE815020040 3X60 CROSSHEAD SCREWDRIVER

8BE815020041 4.5X80 CROSSHEAD SCREWDRIVER


8BE815030000 TOOL KIT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

564 / 592 3DB 16142 EAAA Ed.02


5–6.2 Maintenance Tool Kit part list

P/N Description

41172010 INSULATED PLUG WITH PLIERS

41172011 ANTISTATIC WRIST BAND

41911001 CORDONE X APPLICAZIONI A

248501099 FEMALE BUTTON TERMINATION





870959166 CACCIAVITE 5,5X200

879010249 TOOL KEY 5,5 MM

879010250 TOOL KEY 7 MM

1AD024120002 UNHOOK TOOL



3AL79115AAAA EXTRACTOR

3DB00489AAAA COASSIAL CABLE

3DB01229AAAA CABLE

3DB01400AAAA COAXIAL CORD PLUG

3DB02519AAAA CORD

3DB03884AAAA LEVER

3DB05021AAAA CORD

3DB06439AAAA COAXIAL CORD











All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

565 / 5923DB 16142 EAAA Ed.02


5–6.3 Station Tool Kit part list

P/N Description

41172010 INSULATED PLUG WITH PLIERS

41172011 ANTISTATIC WRIST BAND

41911001 CORDONE X APPLICAZIONI A

248501099 FEMALE BUTTON TERMINATION





870959166 CACCIAVITE 5,5X200

879010249 TOOL KEY 5,5 MM

879010250 TOOL KEY 7 MM

1AB026470031 PROTECTION*BIPOLAR

1AB026470031 PROTECTION*BIPOLAR

1AD024120002 UNHOOK TOOL



3AL79115AAAA EXTRACTOR

3DB01229AAAA CABLE

3DB03884AAAA LEVER










All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

566 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

567 / 5923DB 16142 EAAA Ed.02


5–7 APPENDIX G: DOCUMENTATION GUIDE

This appendix contains all information regarding:– this Manual, herebelow– the Customer Documentation set this Manual belongs to, on page 569– general on Alcatel–Lucent Customer Documentation, on page 572

5–7.1 Guide to this Manual

This paragraph contains all information regarding this Manual and is structured as follows:

– Applicability of this Manual herebelow– Purpose of this Manual on page 568

5–7.1.1 Applicability of this Manual

a ) Product–release applicabilityThe current edition of this Manual applies to the 9400AWY Rel.2.1 in the RF band configurationslisted in Tab. 46. on page 127.

b ) NE applicabilityThe current edition of this Manual applies to the following Network Elements (NE): ULS

c ) SWP and Version applicabilityThe current edition of this Manual applies to the set of system’s equipment, configurations andfeatures associated to the following SWP versions:

SWP Technical Description SWP Technical CodeSWP Version

(N.B.)

SWP 9400AWY R.2.1 V2.1.1 REF.[a] in Tab. 53. on page 141 V2.1.1

N.B. For the meaning of SWP Release and Version, please refer to para.5–7.3.2 on page 573.The indication of the Versions in this Manual has the following meaning:this Manual applies starting from the Versions stated in this table, but it could also apply tosubsequent Versions for the following reasons:

a ) this Manual is not modified, unless the new version distributed to the Customerscomprises changes to the man–machine interface, or even in the presence of minorchanges that do not affect negatively the understandability of the procedures describedtherein (e.g. a ”button” moved internally to a screen);

b ) furthermore, if the screens contained in this Manual show the ”version–release” of the”product–release”, then they are not replaced in the subsequent versions of Manual if theircontents remains unchanged.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

568 / 592 3DB 16142 EAAA Ed.02


5–7.1.2 Purpose of this Manual

This Manual belongs to the Customer Documentation set envisaged for the equipment specified inpara.5–7.1.1 on page 567.

Refer to para.5–7.2 on page 569 in order to have the list and description of the Customer Documentationset.

Taking into account that the system consists of an InDoor Unit (IDU), an OutDoor Unit (ODU), and aSoftware Package (SWP), this Manual provides the following information:

– system description at different detail levels, with regard to system, hardware and software

– system technical specifications

– IDU and ODU item Part Numbers and equipping rules (provisioning)

– unit operative hardware description: access point description (usage of LED, pushbuttons, switchesand connectors for Customer use), connection rules, hardware setting options

– operation and maintenance activities the operators can carry out according to the specific softwareapplication(s) referred to in this Manual [see para. 5–7.1.1 point c ) on page 567 ].

– spare parts provisioning

– routine maintenance procedures

– corrective maintenance and unit replacement procedures

– SWP installation

– equipment and radio link commissioning procedure.

Reading the following Manual:

– 1320CT Basic Operator’s Handbook V3.0.1

is not strictly necessary before starting this document, but its knowledge is necessary for operating theprocedures introduced by this document and detailed in the other sections of this Manual.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

569 / 5923DB 16142 EAAA Ed.02


5–7.2 Documentation set description

This paragraph contains all information regarding the 9400AWY Rel.2.1.1 Customer Documentation andis organized as follows:– 9400AWY Rel.2.1.1 Customer Documentation herebelow– Product Release Note on page 571– Additional documentation for 1320CT platform on page 571

WARNING: this Documentation set is relevant to 9400AWY Rel.2.1 final version V2.1.1 only.The Documentation set relevant to 9400AWY Rel.2.1 previous version V2.1.0 andpre–release version V2.1.1* is contained in the CD–ROM P/N 3DB16142ABAA.

5–7.2.1 9400AWY 2.1.1 Customer Documentation

This paragraph lists and briefly describes the documentation set envisaged for 9400AWY Rel.2.1.1.Please refer to following para.5–7.3 on page 572 for a general description of Alcatel–Lucent CustomerDocumentation system.

The list of handbooks given here below is valid as at the issue date of this Handbook andcan be changed without any obligation for Alcatel–Lucent to update it in this Handbook.

The standard Customer Documentation for 9400AWY Rel.2.1.1 is in the English language and isdistributed to Customers only by the following CD–ROM:

Tab. 76. 9400AWY Rel.2.1.1 Documentation CD–ROM

REF Technical Description Technical Code

DCP 9400AWY 2.1 V2.1.1 CD_ROM 3DB 16142 ACAA

[A] This CD–ROM contains, in electronic format (ADOBE ACROBAT pdf files), all handbookslisted in Tab. 77. on page 570

N.B.

a ) Standard supplyOne copy of the 9400AWY Rel.2.1.1 CD–ROM is automatically delivered to Customer together withthe equipment it refers to (one copy for each terminal).As 9400AWY Rel.2.1.1 CD–ROM is a standard commercial item, additional copies can be orderedand delivered as any other Alcatel–Lucent commercial item.Supply to Customers of paper copies of the handbooks is not envisaged.Supply to Customers of Customer Documentation source files is not envisaged.

b ) Product–documentation consistencyEquipment description and lay–out are always general, i.e. they never describe the actualcomposition of the equipment supplied to Customer (this task is entrusted to plant–dependentdocumentation).Detailed hardware documentation concerns actually supplied units and is coherent with theproduction issue of such units.Software–associated handbooks are coherent with the supplied SWP release.Copies of the CD–ROMs regarding a specific product–release previously delivered can be requiredspecifying P/N and edition.

c ) Copyright notificationThe technical information of the handbooks and CD–ROMs supplied to Customers is the propertyof Alcatel–Lucent and must not be copied, reproduced or disclosed to a third party without writtenconsent.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

570 / 592 3DB 16142 EAAA Ed.02


Tab. 77. Handbooks contained in the 9400AWY R.2.1.1 documentation CD–ROM

N.B. The P/Ns of handbooks is just for Alcatel internal management only. As specified in point a )on page 569, they do not represent Commercial item P/Ns.

REF HANDBOOKT NAME HANDBOOK P/N

HANDBOOKS FOR HARDWARE INSTALLATION (n.b.1)

[B]9400AWY Rel.2.1 Installation Handbook 3DB 16142 BAAA

[B]9400AWY Rel.2.1 Installation Guide 3DB 16142 FAAA

USER MANUAL (n.b.2)

[C]9400AWY Rel.2.1 V2.1.1 User Manualthis manual

3DB 16142 EAAA

TRS & SAT DOCUMENT (n.b.3)

[D] 9400AWY Rel.2.1 TRS and SAT 3DB 16142 DAAA

ADDITIONAL DOCUMENTATION

[E]Interference investigation proceduren.b.4

3DB 04165 EAAA

n.b.1 These handbooks provide information regarding equipment hardware installation, accordingto Alcatel–Lucent WTD LAB. rules. Moreover, they give the P/Ns of all installation materialsthat are not given in this User Manual.As shown, two versions are available:

– the Installation Handbook provides detailed descriptions and instructions, and is mainlyaddressed to technicians who have never installed a 9400AWY system before

– the Installation Guide provides same information in a more concise way, and is mainlyaddressed to technicians who have already installed a 9400AWY system

This User Manual makes reference to the Installation Handbook; using it or the InstallationGuide is on Customer choice.

n.b.2 See para.5–7.1.2 on page 568

n.b.3 Contains the Test Report Sheets and the Site Acceptance Test protocol, according toAlcatel–Lucent WTD LAB. rules. The source file of this document (MSWord 2000) is alsodistributed in the Documentation CD–ROM.

n.b.4 Describes the measurement procedure for the interference searching in the various RF bandsused by Alcatel Radio Transmission products. It is common to all Alcatel Radio Transmissionproducts.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

571 / 5923DB 16142 EAAA Ed.02


5–7.2.2 Product Release Note

The Product Release Note contains information not strictly necessary for Customers (like the SW PackageIdentification data, the list of SW Package Components, the list of ECT SW Sub–Components, thedescription of new features and modifications, restrictions and known problems, etc.)

The Product Release Note is neither contained in the Documentation CD–ROM nor automaticallydelivered to Customers.

The Product Release Note is available only on specific request to your Alcatel–Lucent local dealer,specifying the SWP’s Technical Code and ICS (edition) printed on the SWP CD–ROM itself.

5–7.2.3 Additional documentation for 1320CT platform

Tab. 78. Documentation common to Alcatel–Lucent Network Elements using 1320CT platform

REFCT–K

Version(N.B.)

ITEM P/N

[F]� 3.0.1 DCP 1320 CT 3.x CD_ROM EN 3AL 79552 AAAA

[F]Contains, in electronic format, the 1320 CT Operator’s Handbook REF.[G] to [I]

� 3.0.1 1320CT Rel.3.x Basic Operator’s Handbook 3AL 79551 AAAA

[G] Provides general information and operational procedures common to all 1320CT (Craftterminal) of Alcatel–Lucent InfoModel Network Elements.

� 3.0.1 AS Rel.6.5 Operator’s Handbook 3AL 88876 AAAA

[H] Provides detailed information and operational procedures regarding the alarm Surveillancesoftware embedded in the 1320CT software package.

� 3.0.1 ELB Rel.2.x Operator’s Handbook 3AL 88877 AAAA

[I] Provides detailed information and operational procedures regarding the Event Log Browsersoftware embedded in the 1320CT software package.

N.B. The CT Version is displayed when, on the PC, you select the 1320CT application for itslaunch.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

572 / 592 3DB 16142 EAAA Ed.02


5–7.3 General on Alcatel–Lucent Customer Documentation

This paragraph describes in general the Alcatel–Lucent Customer Documentation system, details theassociation between the product levels and the associated documentation, and explains CustomerDocumentation characteristics as well as the policies for its delivery and updating.

This paragraph is fully applicable to the 2nd generation Radio Product families of Alcatel–Lucent WTD(Wireless Transmission Division) only.

5–7.3.1 Customer–Independent Standard Customer Documentation

a ) Definition

Standard Customer Documentation, referred to hereafter, must be always meant asplant–independent and is always independent of any Customization.

Plant–dependent and/or Customized documentation, if envisaged by the contract, is subjected tocommercial criteria as far as contents, formats and supply conditions are concerned

N.B. Plant–dependent and Customized documentation is not described here.

b ) Aims of standard Customer Documentation

Standard system, hardware and software documentation is meant to give the Customer personnelthe possibility and the information necessary for installing, commissioning, operating, andmaintaining the equipment according to Alcatel–Lucent Laboratory design and Installation Dept.choices. In particular:

• the contents of the handbooks associated to the software applications focus on the explanationof the man–machine interface and of the operating procedures allowed by it;

• maintenance is described down to faulty PCB location and replacement.

N.B. No supply to Customers of design documentation (like PCB hardware design andproduction documents and files, software source programs, programming tools, etc.) isenvisaged.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

573 / 5923DB 16142 EAAA Ed.02


5–7.3.2 Product levels and associated Customer Documentation

See Fig. 377. on page 574.

a ) Products

A ”product” is defined by the network hierarchical level where it can be inserted and by the whole ofperformances and services that it is meant for.

E.g. 9400AWY is a product.

b ) Product-releases

A ”product” evolves through successive ”product–releases”, which are the real products marketedfor their delivery at a certain ”product–release” availability date. A certain ”product–release” performsmore functionalities than the previous one.

E.g. Rel.1.0, Rel.2.0 and Rel.2.1 are three successive ”product–releases” of the same ”product”.

A ”product–release” comprehends a set of hardware components and at least one “SoftwarePackage” (SWP); as a whole, they identify the possible network applications and the equipmentperformances that the specific ”product–release” has been designed, engineered, and marketed for.

c ) Configurations and Network Elements

In some cases, a ”product–release” includes different possible “configurations” which aredistinguished from one another by different “Network Element” (NE) types and, from themanagement point of view, by different SWPs.

d ) SWP Releases and Versions

This description is 9400AWY–specific:

• A 9400AWY SWP is identified by its “Denomination”, “Part Number” and “Change Status”, thatare printed on the CD–ROM’s label.

• The SWP Denomination version’s first and second digits (e.g. 2.1) correspond to the “HWproduct–release” number first and second digits; third digit of the SWP version identifies theVersion Level of the SWP.

• A 9400AWY SWP with new “Denomination” and “Part Number” represents a fully new SWPhaving main features in addition to those of the previous SWP.

• A 9400AWY SWP with same “Denomination” and “Part Number” , but with new “ChangeStatus” corresponds to a new version of such SWP, usually developed for bug–fixing purposesand/or minor additional features.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

574 / 592 3DB 16142 EAAA Ed.02


e ) Customer Documentation

A ”product–release–(configuration)” has its own set of standard Customer Documentation, usuallyformed of several handbooks, i.e., in general:• System and Hardware documentation:

– one (or more) Technical Handbook(s)– an Installation Handbook– a Commissioning Handbook or Line–Up Guide

• Software documentation:– a Craft Terminal Operator’s Handbook, associated to the specific SWP–Release– other Operator’s Handbooks (typically those associated to the SW platform embedded

in the SWP)

In other cases (e.g. this Manual), above pieces of information are collected in a single document.

PRODUCT

PRODUCT–RELEASE 1.0 PRODUCT–RELEASE 2.1evolution

CONFIG.A

ALTERNATIVE CONFIGURATIONS

CONFIG.B

SWP REL.1.0 SWP REL.1.1evolution

CONFIG.ASystem & HWDocumentation

SWP REL.1.0SW

Documentation

SWP REL.1.1SW

Documentation

PRODUCTLEVELS

DOCUMENTATION

Fig. 377. Example of Product levels and associated Customer Documentation

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

575 / 5923DB 16142 EAAA Ed.02


5–8 APPENDIX H: LIST OF SYMBOLS AND ABBREVIATIONS,GLOSSARY OF TERMS

5–8.1 List of symbols

Tab. 79. List of symbols

N.B. This table lists some symbols whose interpretation could be doubtful.

SYMBOL MEANING AND COMMENTS

�

In this handbook it is not the division symbol. It means ’from .. to ..’.E.g.:

<value1> � <value2>means:

from <value1> (included) to <value2> (included)

POLARIZATIONSYMBOLS

A polarization symbol like this:

can be assumed as either horizontal H or verticalV

Once you have decided a polarization (e.g. H)

the opposite direction symbol will be opposite polarization (e.g.V

)

5–8.2 List of abbreviations

Tab. 80. List of abbreviationsABBREVIATION MEANING

STARTING WITH NUMBERS

9400AWY Short–haul low/medium capacity digital microwave radio links

9400FSO PDH Low/Medium Capacity Free Space Optic System

9600FSO SDH/SONET High Capacity Free Space Optics System

9600LSY STM 1/0 Long Haul Digital Radio Relay System

9600USY Urban Haul Synchronous split mount Radio System

A

ABIL Enabling

ABN Abnormal

AC Alternate Current

ACD Access Control Domain

ACSE Association Control Service Element

ADC – A/D Analog to Digital Converter

AE Access Enable

AF Atomic Function

ADM Add and Drop Multiplexer

AGC Automatic Gain Control

AIS Alarm indication Signal

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

576 / 592 3DB 16142 EAAA Ed.02



ALR Automatic Laser Restart

ALS Automatic Laser Shutdown

AMI Alternate Mark Inversion

AND Alarm on both station batteries

ANSI American National Standard Institute

AP Alternate Polarization

API Access Point Identifier

APS Automatic Protection Switching

APT Active Problem Table

AS Alarm Surveillance

ASAP Alarm Severity Assignment Profile

ASE Application Service Element

ASIC Application Specific Integrated Circuit

AT Attended Alarm

ATL Far Terminal Alarm

ATM Asynchronous transfer Mode

ATPC Automatic Transmit Power Control

ATTD ATTendeD (alarm storing)

AUX AUXiliary

AVC Attribute Value Change

B

BATT Battery

BB Base Band

BBE Background Block Error

BCA Common Battery Dial Pulsing (Telephone Set)

BER Bit Error Rate

BIP Bit Interleaved Parity

BKPV Back Plane Version

BNC Bayonet Not Coupling

BSC Base Station Controller

BTS Base Transceiver Station

C

CAND All power supply units are faulty

CCDP Co–Channel Dual Polarized (Frequency re–use)

CCITT International Telephone and Telegraph Consultative Committee

CD Current Data

CE European Conformity

CFA Carrier Failure Alarm

C/I Carrier to Interference ratio

CK Clock

CLA Common Loss Alarm

CLEC Competitive Local Exchange Carrier

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

577 / 5923DB 16142 EAAA Ed.02



CMISE Common Management Information Service Element

CMISS Card Missing

CO Central Office

COAX Coaxial

CP Co–polar

CPE Customer premises equipment

CPI Incoming parallel contacts

CPO Outgoing parallel contacts

CPU Central Processor Unit

CRC–n Cyclic Redundancy Check – n

CS (Item) Change Status

CT Craft Terminal

CTP Connection Termination Point

D

DA Distant Alarm

DAV Distinguishing Attribute Value

D/A Digital to Analog (converter/conversion)

DC Direct Current

DCC Data Communication Channel

DCE Data Circuit Terminating Equipment

DCN Data Communication Network

DDF Digital Distribution Frame

DEFEC FEC Decoder

DEM Demodulator

DEMUX Demodulator

DF Dialog Failure

DIV Diversity

DM Degraded Minute

DRRS Digital Radio Relay System

DTE Data Terminal Equipment

DTI Department of Trade and Industry

DTMF Dual Tone Multi Frequency

E

EB Errored Block

EBC Errored Block Count

EBU European Broadcasting Union

EC Equipment Controller

ECC Embedded Communication Channel

ECS External Communication Service

ECT Equipment Craft Terminal

EE Equipment Engineering

EF Equipment Failure

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

578 / 592 3DB 16142 EAAA Ed.02



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

EXC–BER Excessive BER

F

F Interface F (for Craft Terminal) or Fuse

FAD Functional Access Domain

FCC Federal Communications Commission

FCS Frame Check Sequence

FD Frequency Diversity

FE Front End – Fast Ethernet

FEC Forward Error Correction (Code)

FIT Failure Unit

FPGA Field Programmable Gate Array

FR ’Failure Rate’ or ’Frequency Reuse’

FSO Free Space Optics

FTP File Transfer Protocol

G

GA General Alarm or Gate Array

GND Ground

GNE Gateway Network Element

H

H Horizontal (polarization)

HBER High Bit Error Rate

HCS Higher order Connection Supervision

HD History Data

HDBK Handbook

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

579 / 5923DB 16142 EAAA Ed.02



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

I–J

ICS Item Change Status

ID IDentifier

IDU InDoor Unit

IEC International Electro technical Commission

IEEE Institute of Electrical and Electronic Engineering

IF Intermediate Frequency

IM Information Manager – Information Model

IN Input

IND Indicative alarm

INT Internal Local Alarms

I/O Input/Output

IP Internet Protocol

IRC International Radiotechnical Commission

ISO International Standards Organization

ITU–R (*) International Telecommunication Union – Radiocommunication

ITU–T (*) International Telecommunication Union – Telecommunication

JRE Java Run–time Environment

L

LAC Local Access Control

LAN Local Area Network

LAPD Link Access Procedure on D–channel

LBER Low Bit Error Rate

LC Loss of Configuration

LCS Lower Order Connection Supervision

LDI Local Defect Indication

LED Light Emission Diode

LEW Low Early Warning

LIM Link Identifier Mismatch

LLMAN Alcatel Lower Layer MANager

LO Local Oscillator

LOF Loss Of Frame

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

580 / 592 3DB 16142 EAAA Ed.02



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 Near–end Defect Second

NA Not Applicable

NE Network Element

NES Network Element Synthesis

NEBC Near–end Errored Block Count

NF Noise Figure

NFD Net Filter Discrimination

NG Not Urgent

NML Network Management Layer

NMS Network Management System

NRZ Non Return to Zero

NSA Not Service Affecting

NTP Network Time Protocol

NURG Not urgent alarm

O

OBPS On Board Power Supply

OC_R ODU Controller_Radio

OCT Office Craft Terminal

ODF Optical Distribution Frame

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

581 / 5923DB 16142 EAAA Ed.02



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 OR’ing of station power supply alarm

OS Operation System

OSI Open Systems Interconnection

OSPF Open Shortest Path First

OUT Output

OVF Overflow

OW Order Wire

P

PABX Private Automatic Branch Exchange

PBX Private Branch Exchange

PC Personal Computer

PDH Plesiochronous Digital Hierarchy

PFAIL Power supply failure

PI Physical Interface

PLL Phase Locked Loop

PLM PayLoad Mismatch

PM Performance Monitoring

PPI Plesiochronous Physical interface

ppm parts per million

PPP Point to Point Protocol

PRx Received power

PRBS Pseudo Random Binary Signal

P/S Parallel/Serial converter

PS Power Supply

PSA Protection Switch Actual

PSA C Protection Switch Count

PSA D Protection Switch Actual Duration

PSK Portable Service Kit

PSR Protection Switch Request

PSU Power Supply Unit

PTx Transmitted power

Q

QAM Quadrature Amplitude Modulation

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

582 / 592 3DB 16142 EAAA Ed.02



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

RECT Remote Equipment Craft Terminal

REI Remote Error Indication

REF Reference

REL Release

RF Radio Frequency

RFC Remote Frequency Control

RI Remote Inventory

RL Received Level

RLTS Received Level Threshold Second

RMS Root Mean Square

RNURG Not urgent Alarm command. Lights up the relative rack red LED

RPI Radio Physical Interface

RPS Radio Protection Switching

RSOH Regenerator Section OverHead

RSPI Radio Synchronous Physical Interface

RT Transceiver

RTF Remote Terminal Failure

RTPC Remote Transmit Power Control

RURG Urgent Alarm command. Lights up the relative rack red LED

Rx Receiver/Received

S

SA Service Affecting or Service Alarm

SC Service Channel or System Controller

SD Space Diversity

SDH Synchronous Digital Hierarchy

SES Severely Errored Second

SF Signal Fail

SNMP Simple Network Management Protocol

SP Splitter

SQ Squelch

S/P Serial to Parallel

SSF Server Signal Fail

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

583 / 5923DB 16142 EAAA Ed.02



STBY Standby

SU Supervisory Unit

SW ”Switch” or ”Software”

SWP Software Package

T

TA Remote Alarm

TCO Total Cost of Owner

TCP Transmission Control Protocol

TD Layout drawing

TDM Time Division Multiplexer

TEM Transversal Electric Mode

TIM Trace Identifier Mismatch

TL Transmitted Level

TLTS Transmitted Level Threshold Second

TM Transmission and Multiplexing

TMN Telecommunication Management Network

TN Telecommunications Network

TPH Telephone

TP Termination Point

TPS Tx Protection Switching

TR TRansceiver – Technical Report

TRCF Total Received Correct Frames

TRCO Total Received Correct Octets

TRIB Tributary

TRSEF Total Received Service Errored Frames

TS Time Slot

TRU Top Rack Unit

TTF Total Transmitted Frames

TTO Total Transmitted Octets

TTP Trail Termination Point

Tx Transmitter/Transmitted

U

U Unavailability

UAS UnAvailable Second

UAT UnAvailable Time

UDR Unpressurized Rectangular Waveguide Type

UG Urgent Alarm

UMTS Universal Mobile Telecommunications System

URG Urgent

URU Underlying Resource Unavailable

USC User Service Channel

USM User Service Manager

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

584 / 592 3DB 16142 EAAA Ed.02



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 NDCCITT) in 1992 (and in some cases even before then) are classified as ITU–R and ITU–T, respectively.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

585 / 5923DB 16142 EAAA Ed.02


5–8.3 Glossary of terms

Acknowledgment:When an alarm is taken into account by the application, the operator has to acknowledge it to point outthat he has seen it and that he will react in the right way. During alarm configuration it is possible to seta maximum delay for alarm acknowledgement. The operator can decide whether or not the alarm clearhas to be acknowledged.

Administrator:A user who has access rights to all the Management Domains of the Craft Terminal product. He has accessto 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 stateof 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 itsavailable memory space.

Craft Terminal:Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used toconfigure 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 entitiescomposing the network, or on the network itself. The operator specifies the time period for which herequires the report.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

586 / 592 3DB 16142 EAAA Ed.02


International Telegraph and Telephone Consultative Committee:Standard organization for telecommunications. Now called the ITU–T (International TelecommunicationUnion).

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 canundertake signal conversion functions (adapting a signal to two different transmission media) ormultiplexing/demultiplexing functions.

Logs:Logs are files used to store history data concerning the incoming notifications, operator commands andsystem alarms. The size of the log can be configured.

Management Domain:The Craft Terminal product is partitioned into management domains for functional proposes. Eachmanagement 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 usercan manage.

Network Element:Either a telecommunication equipment or groups parts of a Telecommunication Network. Havecharacteristics 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 tothe operator a set of functions necessary to supervise the NEs. The 1353SH is an Operation System.

Operator:The end–user of the Craft Terminal. He supervises a part of the network that is dependant on his user profile.

Physical Interface:Electrical or Electrical/Optical transformers that decouple the line signals and adapt the form of signal forfurther transmission. This functional block also manages clock extraction, signal loss monitoring andloopback functions.

Port:A physical point at which the Network Element can be attached to a transmission medium. A port is eithera termination point or an origination point.

Severity:Linked to alarms, severities indicate the magnitude related to the failure.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

587 / 5923DB 16142 EAAA Ed.02


Telecommunication Management Network:Defines the concept of interoperable management of TNs. They provide an organized network structureto achieve the interconnection of the different components of the TN and the services to process theinformation.

Telecommunication Network:Describes the network to be managed. Provides the transmission, the transport and the switchingsupports 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 predefineduser profiles is determined by a fixed set of FADs. To give user access to Craft Terminal functionality, theadministrator must assign a profile to a UNIX user account by choosing one among the predefined profilesinstalled with Craft Terminal.

User Service Manager:These are presentation processes used by the Craft Terminal to manage the Human Machine Interfaceand facilitate the interaction with the product.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

588 / 592 3DB 16142 EAAA Ed.02


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

589 / 5923DB 16142 EAAA Ed.02


5–9 APPENDIX I: CUSTOMER DOCUMENTATION FEEDBACK

The meaning of this appendix is to collect customer feedback about this handbook.

Scope of this activity is the improvement and innovation of customer documentation through theunderstanding 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 AssistanceCenter. 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 CD–ROM, saving,filling and sending it by e–mail to your Local Alcatel Technical Assistance Center.

• creating a dedicated form on paper or file and sending it to your Local Alcatel TechnicalAssistance Center.

We will take into account of your suggestion.

We reserve to modify consequently the handbook according to the correctness and congruence of thesuggestion and requests.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

590 / 592 3DB 16142 EAAA Ed.02


CUSTOMER DOCUMENTATION FEEDBACK

Handbook data

Product release, version: 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1

Handbook type: USER MANUAL

Handbook part number and edition: 3DB 16142 EAAA Ed.02

General evaluation

SUBJECT 5 (max.) 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 : System description

2 : NE management BY TCO Suite and CT

3 : Installation and commissioning

4 : Maintenance and upgrade

5 : Appendices

Your comments (strictly necessary when value is less than 3)

Suggestion for improvements

Which subject to deepen:

How to deepen:

Subject to eliminate or reduce:

Other comments/suggestions:

Error identified

Reader Info

Name: Date;

Company: Job:

Address:

E–mail:

Phone: Fax:

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not

perm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

–Luc

ent

591 / 5923DB 16142 EAAA Ed.02


All rights reservedPassing on and copying of this document,

use and communication of its contents is not permittedwithout written authorization from Alcatel –Lucent.

www.alcatel–lucent.com

593 / 5923DB 16142 EAAA Ed.02

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1Handbook print & assembly

THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOKQUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO

COD.MANUALE HDBK P/N: 3DB 16142 EAAA Ed.029400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1USER MANUAL

HANDBOOK PRINT AND ASSEMBLY INSTRUCTIONS –ISTRUZIONI DI STAMPA ED ASSIEMAGGIO DEL MANUALE

– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:HANDBOOK COMPOSITION AND ASSEMBLY:

SERVONO 5 SEPARATORI NUMERATI DA 1 A 55 SEPARATORS NUMBERED FROM 1 TO 5 ARE NECESSARY

– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

fasestep

No pagine(facciate)

numeratenumbered

step (facciate)No pages da from a to

1TARGHETTE - LABELSFig. 1. pg. 594

2 PARTE INIZIALE - FRONT MATTER ⇒ 1/592 28/592

3 INSERIRE SEPARATORE ’1’ - INSERT SEPARATOR ’1’

4 SECTION 1: SYSTEM DESCRIPTION ⇒ 29/592 138/592


6SECTION 2: NE MANAGEMENT BY TCO SUITE ANDCRAFT TERMINAL

⇒ 139/592 306/592


8 SECTION 3: INSTALLATION AND COMMISSIONING ⇒ 307/592 406/592


10 SECTION 4: MAINTENANCE AND UPGRADE ⇒ 407/592 498/592


12 SECTION 5: APPENDICES ⇒ 499/592 592/592

594 / 592 3DB 16142 EAAA Ed.02

USER MANUAL9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1Handbook print & assembly

9400AWY Rel.2.17–8–13–15–18–23–25–28–38 GHz

short–haul low/medium capacity digital microwave radio links

SWP 9400AWY R.2.1 V2.1.1

USER MANUAL

3DB 16142 EAAA Ed.02

VOL.1/1

9400AWY Rel.2.17–8–13–15–18–23–25–28–38 GHz


SWP 9400AWY R.2.1 V2.1.1USER MANUAL

3DB 16142 EAAA Ed.02

VOL.1/1

9400AWY Rel.2.17–8–13–15–18–23–25–28–38 GHz short–haul low/medium capacity digital microwave radio links

SWP 9400AWY R.2.1 V2.1.13DB 16142 EAAA Ed.02 USER MANUAL VOL.1/1

9400AWY Rel.2.17–8–13–15–18–23–25–28–38 GHz short–haul low/medium capacity digital microwave radio links

SWP 9400AWY R.2.1 V2.1.13DB 16142 EAAA Ed.02 USER MANUAL VOL.1/1

9400AWY Rel.2.17–8–13–15–18–23–25–28–38 GHz


SWP 9400AWY R.2.1 V2.1.1

3DB 16142 EAAA Ed.02 USER MANUAL VOL.1/1

Fig. 1.

END OF PRINT INSTRUCTIONS – FINE DELLE ISTRUZIONI DI STAMPA

595 / 5923DB 16142 EAAA Ed.02

USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1Handbook editorial information

FOR ALCATEL–LUCENT INTERNAL PURPOSE ONLYTHIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK

QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO

HANDBOOK EDITORIAL INFORMATION(not inserted in the CD–ROM)

PART FOR ALCATEL–LUCENT INTERNAL USE ONLY

Note for Customers: this part contains editorial information for Alcatel–lucent internal use only,and should have not be given to you. Nevertheless, in case you receive it, take into account thatit does not contain information useful for you, so that you can simply ignore it.

COD.MANUALE HDBK P/N: 3DB 16142 EAAA Ed.029400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1USER MANUAL

1 PUBLISHING NOTES FOR THIS MANUAL• Labels on page 594 are done according to A-Italy binder format.• Source files and printable files of this manual are archived in PDM:

– Printable file without revision bars: used for official distribution to Customers (and insertedin CD–ROM without this part)PDF file must be opened with ACROBAT Reader Version 5.0 at least.(N.B. : it has been created with ACROBAT DISTILLER 7.0)

– Source file with revision bars:

SOURCE FORMAT SIZE Mbytes TOTAL N.PAGESPDM ARCHIVE

METHOD

QUICKSILVER 1.5.3 633 600 ⇒ IDU ⇒ WINZIP

WARNING: the source file folder contains also the pdf file with revision bars

Notes on revision bars: revision bars point out changes with respect to the previous editionarchived in PDM

N.B. page numbers specified in table on page 593 are automatic and obtained byautoreference to tags of:– section first page– section last page, marked by the special component ’endofsection’. WARNING:

components ’endofsection’ have white color, to avoid their printing. DO NOTREMOVE THEM, otherwise table on page 593 will have NO TAGs.

– handbook last page, marked by the special component ’efme’.N.B. component ’efme’ correspond to writing “www.alcatel–lucent.com”

on page 592 . DO NOT REMOVE IT, otherwise all pages will haveNO TAGs in footer.

N.B. additional information (source file) in first catalog.

596 / 592 3DB 16142 EAAA Ed.02

USER MANUAL9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1Handbook editorial information



2 HANDBOOK HISTORY

EDDATE

(yymmdd)CHANGE NOTE

(ECO)APPRAISAL AUTHORITY ORIGINATOR

01 070802 B.Gabbrielli, V.Fossati, C.Van Kerrebroeck E.Corradini

02 080125 00000 57267 M.Nosari, C.Van Kerrebroeck E.Corradini

2.1 List of the editions and modified parts

The following Tab. 81. indicates the Manual parts new and modified with respect to the previous edition.

Legend: n = new part m = modified part blank= part unchanged

Tab. 81. History of this ManualMANUAL EDITION ⇒ 01 02 03 04 05

QUICK GUIDE n m

SECTION 1: SYSTEM DESCRIPTION n

1–1 About this manual n m

1–2 System overview n m

1–3 IDU provisioning and description n m

1–4 ODU provisioning, characteristics and description n m

1–5 Technical specifications n m

SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFTTERMINAL

n m

2–1 SWP 9400AWY R.2.1 description n m

2–2 Introduction on TCO Suite and CT views and menus n m

2–3 Configuration n m

2–4 Equipment n m

2–5 Line Interface n m

2–6 Radio n m

2–7 External points n

2–8 Supervision n

2–9 Protection schemes n m

2–10 Loopbacks n m

2–11 Diagnosis n

2–12 Performance Monitoring n

2–13 Software Download n

2–14 MIB Management n

597 / 5923DB 16142 EAAA Ed.02




Tab. 81. History of this ManualMANUAL EDITION ⇒ 01 02 03 04 05

SECTION 3: INSTALLATION AND COMMISSIONING n

3–1 SWP installation in PC environment n m

3–2 Line–Up and Commissioning n m

SECTION 4: MAINTENANCE AND UPGRADE n m

4–1 Maintenance Policy n

4–2 Set and use of EOW functions n

4–3 Maintenance Tools and Spare Parts n m

4–4 First Level Maintenance n

4–5 Second Level Maintenance n

4–6 Spare Flash Card management and replacement procedures n

4–7 System hardware upgrade n m

4–8 SWP download toward NE n m

4–9 ECT & NE upgrade from V2.1.0 to V2.1.1 n m

4–10 SWP de–installation n

SECTION 5: APPENDICES n m

A Safety–EMC–EMF–ESD norms and equipment labelling n m

B TCO suite start–up special conditions n

CAdditional SW installation operations for NE managementthrough the NE’S ECT serial port

n

D General on Ethernet port characteristics and management n m

EECT–Equipment connection via public switched telephonenetwork

n

F Part lists of tool kits ÉÉÉÉÉÉ

n

G Documentation guide n m

H List of symbols and abbreviations, Glossary of terms n

I Customer documentation feedbackÉÉÉÉÉÉ

n

2.2 Notes on ED.01

ED.01 created on August 2nd, 2007 is the first validated and released edition, associated to SWP9400AWY R.2.1 V2.1.1 Version V2.1.1* , corresponding to the pre–release version V2.1.1h.SWP 9400AWY R.2.1 V2.1.1 V2.1.1* is a V2.1.1 not full–features pre–released version distributed toselected Customers only, and is conceived to support just the management of the new Enhanced Dataplug–in (with 4 Gbit Ethernet ports) in addition to the Data plug–in (with 2 Fast Ethernet ports).For additional information, refer to this same part of handbook ED.01 archived in PDM.

598 / 592 3DB 16142 EAAA Ed.02




2.3 Notes on ED.02 draft and released editions

a ) Draft editions neither validated nor officially released issue, for Alcatel–Lucent internal purposes:

1 ) ED.02A–DRAFT created on December 19th, 20072 ) ED.02B–DRAFT created on January 22nd, 2008

First draft edition associated to SWP final version V2.1.1 . It has been created starting from theED.01 archived in PDM, and introducing the following modifications:– changes for V2.1.1 :

• general information in para.1–1.2 on page 32 and chapter 2–1 from page 141• changes for elimination of old–type Data plug–in (2 Fast Ethernet ports):

– System & HW on pages: 38 , 42 , 44 , 45 , 68 , Tab. 7. from page 70 , 76, 282 , 331 (moreover eliminated two pages after page 333 ), 378 , 391 ,469 , 474 , and whole Appendix D from page 547

– SW management on pages: 210 , 231 , 347 , 349 to 351• updating of Enhanced Ethernet port characteristics and management from

pre–release V2.1.1* to final V2.1.1: modified Appendix D point [8] on pages 551and 552

• other changes for GUI modifications from pre–release V2.1.1* to final V2.1.1 onpages: 156 to 158 , 166 , 203 , 231 and 232 , 351 and 352 , 363

– changes for RF Loopback on pages 46 , 268 , 269 , 385 ; 386 (removed test andreport regarding RF loopback, done also in TRS document ED.03)

– changes for RTPC on pages 128 , 238– changes for Transmitted power at antenna port on page 130– changes for Power Measurement on page 243– changes for Flash Cards:

• updated P/Ns, denominations and software labels in Tab. 23. on page 93• inserted new identification labels on pages 94 and 95

– updated description of documentation set on pages 59 , 567 , 569 and 570– corrections and improvements:

• improved description of ECT & NE upgrade from V2.1.0 to V2.1.1 from page 495(and associated WARNINGs on pages 486 and 493 )

• elimination of enclosed documents (same information put in new Appendix F onpage 563 )

• new appendix Customer documentation feedback on page 589• new standardized template look

continues..

599 / 5923DB 16142 EAAA Ed.02




..continues

– corrections submitted for 9400AWY 2.0.6 User Manual ED.01A–DRAFT, consideredapplicable also to this 9400AWY 2.1.1 User Manual:• submitted by P.Garofoli:

– throughout the handbook: “integrated antenna” replaced by “full integratedantenna”

– Fig. 41. , Fig. 42. , Fig. 43. and Fig. 44. on pages 114 to 117• submitted by Y.Y.Lebret: ETSI reference standard in para.1–5.1.1 on page 129• submitted by B.Magnan:

– new para.1–2.6.9 on page 65 ; new N.B. in Tab. 22. on page 90 ;– new WARNING in para.2–3.4 on page 210 ; one line deleted on page 230– “Sample time” on page 241 ; “directory” on pages 241 and 244 ;– EPS Lockout description on page 259 ;– new WARNING in para.2–9.2.2 on page 261– simplified description of Available loopbacks in para.2–10.2 on pages 269 to

271Errors found in previous edition have been corrected.Revision bars point out major (listed above) and minor (not listed above) modifications ofED.02A–DRAFT and ED.02B–DRAFT with respect to ED.01.Revision bars in correspondence of empty lines or empty table rows, point out parts eliminatedor shifted in other places of the handbookTab. 81. from page 596 shows all parts modified (for major and minor changes).N.B. “NO TAG” markers will be replaced by correct values in final edition

600 / 592 3DB 16142 EAAA Ed.02




3 ) Results of peer review held on January 25 , 2008Main additional changes with respect to ED.02B–DRAFT:– corrections submitted by E.Carpine:

• on page 88 : removed “this mode includes DCE behavior” from CODIR description• on page 89 : “In–frame” description corrected. Moreover line “It is also necessary

that the far–end E1#1 tributary is enabled and successfully provisioned” added alsoon pages 203 and 363

– corrections submitted by A.Goncalves:• in Appendix D – General on Ethernet port characteristics and management :

removed all warnings on pages 549 , 550 , 552• eliminated the RF loopback detailed scheme, that was present on page following 268

– corrections submitted by C.Van Kerrebroeck:• throughout the handbook: “SWP 9400AWY IDU32 V2.1.1” replaced by “SWP

9400AWY R.2.1 V2.1.1”• on page 349 : “and two Ethernet port configuration screens” replaced by “and

four Ethernet port configuration screens”• in Tab. 23. on page 93 : eliminated Software Key P/Ns. Moreover, throughout the

handbook: “Software Key” replaced by “Software Label”• in Product Release Note on page 571 : removed “the lists of DDTs”

– additional corrections for harmonization with AWY 2.0.6 User Manual ED.01:• corrected para.1–2.6.9 on page 65• in Tab. 32. on page 109 : “14700” instead of “15988” for 3CC13711ABXX• in para.2–3.2.3 on page 195 :

.. if in “IP Routing Protocol” the OSPF protocol has been selected, it is possible tocreate OSPF areas

replaced by:.. if in “IP Routing Protocol” the OSPF protocol has been selected, it is possible tochoose OSPF areas

• in para.2–3.2.4.3 on page 200 , added “Id” description

b ) Validated and released edition:ED.02 created on January 25th, 2008 is the first validated and released edition associated to SWP9400AWY R.2.1 V2.1.1 final Version V2.1.1 , and fully annuls and replaces previous ED.01 (sameP/N).Errors found in previous edition have been corrected.Revision bars point out all modifications of final ED.02 with respect to ED.01. Revision bars incorrespondence of empty lines or empty table rows, point out parts eliminated or shifted in otherplaces of the handbook. N.B.Tab. 81. from page 596 shows all parts modified (for major and minor changes).

N.B. The handbook officially distributed to Customers (as pdf file inside the specific CustomerDocumentation CD–ROM) contains neither revision bars nor this part (handbook editorialinformation). Source and pdf files of final ED.02 with revision bars are archived in PDM asspecified in chapter 1 on page 595

END OF INTERNAL DOCUMENT – FINE DEL DOCUMENTO INTERNO

9400AWY User Manual Rel2.1.1

Documents

installation handbook

following cdrom

maintenanceread page

commissioningread page

swp version v2

installation guide

file adobe acrobat pdf

acrobat reader help