Awy Operator Swp20 Ed03

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

1

03

/3DB 06687 CA AA

340

340

SWP 9400AWY R2.0 C.T. OPERATOR’S HDBK

TABLE OF CONTENTS

LIST OF FIGURES AND TABLES 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PRELIMINARY INFORMATION 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HANDBOOK APPLICABILITY, PURPOSE AND HISTORY 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HANDBOOK STRUCTURE 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING 16. . . . . . . . . . . . . . . . . . . . . . . .

CAUTIONS TO AVOID EQUIPMENT DAMAGE 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

QUICK GUIDE 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 1: INSTALLATION 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–1 : GENERAL ON EQUIPMENT INSTALLATION AND SWP INSTALLATION AND MANAGEMENT 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–1.1 Main phases for 9400AWY HW and SW installation 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.2 First SWP installation in PC and NE environments 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.3 How to check ECT and NE versions 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.4 Common situations requiring ECT and/or NE upgrade 29. . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.5 Flash Card related special procedures 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.6 NE configuration data change and save 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.7 Craft Terminal related special procedures 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2 SWP INSTALLATION IN PC ENVIRONMENT 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.1 Requirements 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.1.1 PC characteristics 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.1.2 Operator skills and privileges 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.2 Reference Information Model 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.3 Summary of SW installation / de–installation phases 32. . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.4 SWP loading in PC WINDOWS–NT / 2000 / XP (Professional Edition only) environment 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.4.1 Important warnings 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.4.2 Summary of installation of 1320CT + NE software from SWP CD–ROM 33. . . . . . . . . . 1–2.4.3 CT Products installation guided 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

01 050510 A.BESTETTI ITAVE E.CORRADINI ITAVE

02 051109 0000023753 A.BESTETTI ITAVE E.CORRADINI ITAVE

06020603 0000029168 V.FOSSATI ITAVE E.CORRADINI ITAVE

9400AWY REL.2.0 OPERATOR’S HANDBOOK

V.FOSSATI G.ZILIANI – RTT

V.FOSSATI G.ZILIANI – RTT

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

2

03

/3DB 06687 CA AA

340

340

1–2.4.4 Alcatel Virtual Network Card for Lower Layers 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.4.5 CT Products automatic installation 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.4.6 End of SW installation from SWP CD–ROM 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.5 CT initial configuration 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.5.1 Craft Terminal configuration 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.5.2 Craft Terminal connection to the NE 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–2.6 De–installation phases 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3 SWP DOWNLOAD TOWARD NE 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.1 Requirements 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3.1.1 Craft Terminal 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.1.2 NE state 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.1.3 Operator skills and profile 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–3.2 Summary of the SWP installation phases 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.3 SW download to the NE 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.4 Activation of the new Software Package on the NE 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3.5 MIB save 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–4 ECT & NE UPGRADE TO A NEW SWP ’VERSION’ (SAME SWP ’RELEASE’) 79. . . . . . . . . .

1–5 SYSTEM HARDWARE UPGRADE 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.1 Upgrade from 1+0 to 1+1 configuration 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.2 Flash Card upgrade 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–5.2.1 Introduction 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.2.2 Summary procedure for both stations 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.2.3 Ordering the new Flash Card 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5.2.4 Installation of a new Flash Card fully configured in factory 85. . . . . . . . . . . . . . . . . . . . . . 1–5.2.5 Installation of a new Flash Card not configured in factory 86. . . . . . . . . . . . . . . . . . . . . . .

SECTION 2: NE MANAGEMENT 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1 GENERAL INTRODUCTION ON VIEWS AND MENUS 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.1 Requirements 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2 NE management states 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.3 NE supervision, login, logoff and switch off 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1.3.1 NE Login 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.3.2 NE Logoff or switch off 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1.4 9400AWY view organization 96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.4.1 View Area 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.4.2 Resource Tree Area 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.4.3 Resource Detail Area 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.4.4 Button Policy 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1.5 Introduction to the menu options 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.5.1 Views menu introduction 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.5.2 Configuration menu introduction 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.5.3 Diagnosis menu introduction 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.5.4 Supervision menu introduction 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.5.5 Download menu introduction 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2 CONFIGURATION 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.1 NE Time 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2 Network Configuration 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.2.1 Local Configuration 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.2 NTP Configuration 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.3 Ethernet Configuration 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

3

03

/3DB 06687 CA AA

340

340

2–2.2.4 IP Configuration 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.5 Routing information 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.3 Alarm Severities 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.1 How to create a new Alarm Severity Profile 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.4 System Settings 127. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.4.1 NE Configuration 127. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.4.2 Overhead 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.5 Quick Configuration Procedure 131. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.6 Profiles management 146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–2.6.1 Functional description 146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.6.2 Change Password procedure 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.6.3 Users Management procedure 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3 EQUIPMENT 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.1 IDU level 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.1.1 1+0 configuration 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.1.2 1+1 configuration 154. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.1.3 Board level 156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.2 ODU level 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.3 Tab panels in the Resource Detail Area 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–3.3.1 Alarms 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.3.2 Configuration 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.3.3 Remote Inventory 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–4 LINE INTERFACE 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.1 Tab panels in the Resource Detail Area 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–4.1.1 Alarm 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.1.2 Configuration 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–5 RADIO 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.1 Alarm 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.2 Configuration 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–5.2.1 Local or Remote Transmitter Mute 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.2.2 ODU service kit 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.2.3 Alarm Profile 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–5.3 Frequency 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.3.1 Frequency menu in Rel. 2.0.0 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.3.2 Frequency menu from Rel. 2.0.1 174. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–5.4 RTPC & ATPC 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.4.1 ATPC 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.4.2 RTPC 178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–5.5 Power Measurement 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.5.1 How to read a Power Measurement file 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–6 EXTERNAL POINTS 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.1 Input External Points 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.2 Output External Points 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–7 SUPERVISION 189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.1 Access state (allow or inhibit NE Craft access) 189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–7.1.1 Switching from the OS to the Craft Terminal access state 189. . . . . . . . . . . . . . . . . . . . . . 2–7.1.2 Switching from the Craft Terminal access state back to the OS access state 190. . . . . .

2–7.2 Restart NE 190. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.3 MIB Management 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–7.3.1 Backup 192. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

4

03

/3DB 06687 CA AA

340

340

2–7.3.2 Restore 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.3.3 Activate 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.3.4 Remove file 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–7.4 SW key 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–8 PROTECTION SCHEMES 195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.1 Mux/Demux Protection Management 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–8.1.1 Schema Parameters 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.1.2 Commands 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–8.2 Radio Protection Management 199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.2.1 Rx Static Delay 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.2.2 Schema Parameters 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.2.3 Commands 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–8.3 HST Transmission Protection Management 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.3.1 Schema Parameters 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.3.2 Commands 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–9 LOOPBACKS 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.1 Available Loopbacks 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–9.1.1 1+0 Loopbacks 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.1.2 1+1 Loopbacks 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–9.2 How to activate a loopback 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.3 How to remove a loopback 215. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–10 DIAGNOSIS 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.1 Log Browsing 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.2 Remote Inventory 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.3 Abnormal Condition List 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.4 Summary Block Diagram View 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.5 Current Configuration View 222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11 PERFORMANCE MONITORING 223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.1 General information on the performance monitoring process 223. . . . . . . . . . . . . . . . . . 2–11.2 Performance menu 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.3 CD (Current Data) 227. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11.3.1 CD parameters 228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.3.2 CD Counters 228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11.4 HD (History Data) 229. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.4.1 HD Parameters 229. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–11.5 Threshold tables 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.5.1 How to change a threshold table 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.5.2 How to create a threshold table 231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.5.3 Threshold table association 231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–12 SW DOWNLOAD 233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.1 Server Access Configuration 233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.2 Init SW Download 234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.3 SW Status 235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–13 MIB MANAGEMENT 237. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.1 Introduction 237. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.2 MIB management at Network Element Synthesis level and examples 238. . . . . . . . . . .

2–13.2.1 MIB back–up on ECT 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.2.2 MIB save to disk 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.2.3 MIB load from disk 240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

5

03

/3DB 06687 CA AA

340

340

2–13.2.4 MIB restore from ECT 242. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 3: NE MAINTENANCE 243. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1 TROUBLESHOOTING 245. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.1 Purpose of this procedure 245. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.2 Corrective Maintenance general flow–chart 246. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.3 Troubleshooting organization 247. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.4 Troubleshooting by means of the Craft Terminal 249. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.4.1 Alarm synthesis indication 250. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.4.2 Details on alarms / statuses 251. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–1.5 Warnings on the troubleshooting 253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.1 Problems with the Craft Terminal 253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.2 Analog measurements 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.3 NMS 64 kbit/s V.11 and G.703 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.4 Loopbacks 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.5 Empty USM icon in NES 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.6 NE unreachable 256. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.7 Configuration change from 4 QAM to 16 QAM 256. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.8 Quick configuration menu correct use 256. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.9 Abnormal condition list 257. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.10 Tx Mute functionality for interferences investigation 258. . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.5.11 Tributaries 9 to 16 visible in “8E1/DS1_Ethernet” configuration 259. . . . . . . . . . . . . . . . .

3–1.6 Description of alarms and of probable causes 260. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.7 Unit replacement 261. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–2 SPARE FLASH CARD MANAGEMENT AND REPLACEMENT PROCEDURES 263. . . . . . . . . . 3–2.1 Spare Flash Card management 263. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.2 Flash Card replacement procedures 264. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3–2.2.1 Flash Card replacement with a spare flash card “specific” for the NE 265. . . . . . . . . . . . . 3–2.2.2 Flash Card replacement with a “generic” spare flash card 266. . . . . . . . . . . . . . . . . . . . . .

SECTION 4: SWP DESCRIPTION AND VERSIONS 267. . . . . . . . . . . . . . . . . . . . . . . .

4–1 SWP 9400AWY R.2.0 DESCRIPTION 269. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.1 General 269. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.2 Software product list and part numbers 270. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.3 OEM Software licence list and part numbers 270. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–2 SWP REG.9400AWY R.2.0 V2.0.0 SPECIFIC INFORMATION 271. . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.1 ECT requirements 271. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.2 Reference Information Model 271. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.3 SWP version specific data 272. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–2.3.1 SW Package Identification 272. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.3.2 SW Package Components 272. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.3.3 ECT SW Sub–Components 272. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.3.4 NE MIB Compatibility 272. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–2.4 New features and modifications 273. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.5 Restrictions and known problems 273. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4–3 SWP REG.9400AWY R.2.0 V2.0.1 SPECIFIC INFORMATION 275. . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.1 ECT requirements 275. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.2 Reference Information Model 275. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.3 Equipment hardware requirements 275. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.4 SWP version specific data 276. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

6

03

/3DB 06687 CA AA

340

340



4–4 SWP REG.9400AWY R.2.0 V2.0.2 SPECIFIC INFORMATION 283. . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.1 ECT requirements 283. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.2 Reference Information Model 283. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.3 Equipment hardware requirements 283. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4.4 SWP version specific data 284. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



SECTION 5: APPENDICES 287. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX A : EQUIPMENT DESCRIPTION AND COMPONENTS 289. . . . . . . . . . . . . . . . . . . . . . . . . A.1 : Functions and configurations 290. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2 : IDU and ODU Components 291. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.2.1 : IDU 293. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.2 : ODU 294. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.3 : Allowed Equipment Types 294. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.4 : Remote Inventory Management 296. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.3 : Equipment Protection Switching Management 296. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4 : External Points Management 297. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX B : SW ALLOCATION, FLASH CARD AND EQUIPMENT CONTROL 299. . . . . . . . . . . . B.1 : Allocation of equipment and craft terminal software 300. . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2 : Flash Card 302. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.2.1 : Flash Card types 302. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.2 : Flash Card identification 302. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.3 : Flash Card content 307. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.3 : Equipment control 309. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3.1 : Interfaces (see Fig. 180. on page 289): 309. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3.2 : Operator–Equipment Interaction 309. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3.3 : ECT 310. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3.4 : RECT 310. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX C : ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE NETWORK 311. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.1 : Introduction 311. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.2 : Certified equipment 312. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.3 : Connection cables 313. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.4 : Modem setting 314. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.4.1 : Setting of Sportster Flash Modem & 3Com 56K Faxmodem 314. . . . . . . . . . . . . . . . . . . . . . C.4.2 : TD–32 AC Modem setting 316. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.5 : PC laptop “Dell Latitude” setting 317. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.6 : Setting up the connection 318. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.7 : Changing the ECT–equipment connection speed 319. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.7.1 : Introduction 319. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

7

03

/3DB 06687 CA AA

340

340

C.7.2 : Configuration at PC side 320. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX D : DOCUMENTATION GUIDE 321. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1 : Handbook guide 321. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.1.1 : Handbook applicability 322. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.2 : Purpose of the handbook 323. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.3 : Handbook history 324. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.2 : Documentation set description 327. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2.1 : 9400AWY Rel.2.0 Customer Documentation 327. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2.2 : Additional documentation for 1320CT platform 329. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.3 : General on Alcatel Customer Documentation 330. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.1 : Customer–Independent Standard Customer Documentation 330. . . . . . . . . . . . . . . . . . . . . D.3.2 : Product levels and associated Customer Documentation 331. . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX E : ACRONYMS AND ABBREVIATIONS 333. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX F : GLOSSARY OF TERMS 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

8

03

/3DB 06687 CA AA

340

340

LIST OF FIGURES AND TABLES

FIGURESFig. 1. Main phases for 9400AWY HW and SW installation 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 2. Software management main phases 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 3. How to check ECT version 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 4. How to check NE SW version 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 5. Windows NT installation step 1 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 6. Windows NT installation step 2 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 7. Windows NT installation step 3 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 8. Windows NT configuration step 1 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 9. Windows NT configuration step 2 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 10. Windows NT configuration step 3 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 11. Windows NT configuration step 4 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 12. Windows NT configuration step 5 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 13. Windows NT configuration step 6 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 14. Windows 2000 installation step 1 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 15. Windows 2000 installation step 2 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 16. Windows 2000 installation step 3 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 17. Windows 2000 installation step 4 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 18. Windows 2000 installation step 5 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 19. Windows 2000 configuration step 1 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 20. Windows 2000 configuration step 2 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 21. Windows 2000 configuration step 3 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 22. Windows XP installation step 1 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 23. Windows XP installation step 2 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 24. Windows XP installation step 3 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 25. Windows XP installation step 4 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 26. Windows XP installation step 5 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 27. Windows XP configuration step 1 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 28. Windows XP configuration step 2 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 29. Windows XP configuration step 3 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 30. Windows XP configuration step 4 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 31. De–installation 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 32. IDU expansion from (1+0) to (1+1) 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 33. Network Element Synthesis Window 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 34. NE in supervised state 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 35. Login screen 94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 36. NE Stop Supervision 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 37. 9400AWY Main view organization 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 38. View Areas 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 39. Resource tree area 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 40. Tab panels 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 41. NE Time dialogue box 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 42. Network Configuration menu 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 43. Local Configuration dialogue box 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 44. NTP Configuration dialogue box 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 45. Map 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 46. Ethernet Configuration dialogue box 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 47. IP configuration screen 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 48. IP static routing configuration screen 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 49. Create Static routing 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 50. Point To Point Interface Choice 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

9

03

/3DB 06687 CA AA

340

340

Fig. 51. OSPF Area configuration screen 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 52. Create New OSPF Area 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 53. IP Address configuration of Point–To–Point Interfaces screen 120. . . . . . . . . . . . . . . . . . . . . . . . Fig. 54. Routing information screen 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 55. Alarm Severities Profile 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 56. Name of a cloned alarm profile 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 57. Clone of an Alarm Severity Profile 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 58. Selection of a new severity in the Service Affecting field 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 59. Selection of a new severity in the No Service Affecting field 126. . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 60. System Settings: NE configuration 127. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 61. Confirmation message 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 62. USM closing warning message 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 63. Overhead Configuration 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 64. Quick Configuration Procedure: NE Configuration (Step 1) 132. . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 65. Quick Configuration Procedure: Frame Configuration (Step 2) 133. . . . . . . . . . . . . . . . . . . . . . . Fig. 66. Quick Configuration Procedure: Tributaries Configuration (Step 3) 134. . . . . . . . . . . . . . . . . . . . Fig. 67. Quick Configuration Procedure: Tributaries Configuration (Step 4) 135. . . . . . . . . . . . . . . . . . . . Fig. 68. Quick Configuration Procedure: Channels Configuration (Step 5 in Rel. 2.0.0) 136. . . . . . . . . Fig. 69. Quick Configuration Procedure: Channels Configuration (Step 5 from Rel. 2.0.1) 137. . . . . . . Fig. 70. Quick Configuration Procedure: Local IP Address (Step 6) 138. . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 71. Quick Configuration Procedure: OSPF Area Configuration (Step 7) 139. . . . . . . . . . . . . . . . . . . Fig. 72. Quick Configuration Procedure: IP Static Router Configuration (Step 8) 140. . . . . . . . . . . . . . . Fig. 73. Quick Configuration Procedure: NMS–RF Interface Configuration (Step 9) 141. . . . . . . . . . . . . Fig. 74. Quick Configuration Procedure: NMS–V11 Interface Configuration (Step 10) 142. . . . . . . . . . . Fig. 75. Quick Configuration Procedure: NMS–G703 Interface Configuration (Step 11) 143. . . . . . . . . Fig. 76. Quick Configuration Procedure: Ethernet Configuration (Step 12) 144. . . . . . . . . . . . . . . . . . . . Fig. 77. Quick Configuration Procedure: Summary (Step 13) 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 78. Profile Management options 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 79. Changing Password screen 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 80. Users Management screen 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 81. Users Management help screen 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 82. 1+0 Equipment view 152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 83. 1+1 Equipment view 152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 84. 1+0 IDU view 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 85. 1+1 IDU/MAIN Ch#1 view 154. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 86. 1+1 IDU Ch#0 view 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 87. Main board view 156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 88. ODU view 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 89. Alarm tab panel for a selected object 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 90. Configuration tab panel for a selected object 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 91. Remote Inventory tab panel for a selected object 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 92. Line Interface View 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 93. Line Interface View: E1 Tributary Port 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 94. Line Interface View: E3 Tributary Port 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 95. Line Interface View: DS1 Tributary Port 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 96. Line Interface View: DS3 Tributary Port 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 97. Line Interface View: NMS interface 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 98. Line Interface View: Ethernet Port 168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 99. Line Interface View: Ethernet Port auto–negotiation 169. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 100. Radio Domain View 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 101. Radio Configuration menu 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 102. Radio Frequency menu in Rel. 2.0.0 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 103. Radio Frequency menu from Rel. 2.0.1 174. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 104. Not standard frequency arrangement 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

10

03

/3DB 06687 CA AA

340

340

Fig. 105. Rtpc & Atpc 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 106. Power Measurements 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 107. Power Measurement Graphic 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 108. Power Meas Details 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 109. Name of File ( Log File ) selected screen 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 110. Example of “Power Measurement File Reading“ 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 111. Example of Power Measurement File Reading (with WordPad) 183. . . . . . . . . . . . . . . . . . . . . . Fig. 112. Input External Point View 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 113. Output External Points: CP01 ... CP04 (Manual activation) 186. . . . . . . . . . . . . . . . . . . . . . . . . Fig. 114. Output External Points: CP01 ... CP04 (Automatic activation) 187. . . . . . . . . . . . . . . . . . . . . . . Fig. 115. Output External Points View: FAIL IDU, FAIL ODU 188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 116. Configuration of the Craft access state from the Equipment NE view in the OS mode 189. . Fig. 117. Restart NE call 190. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 118. Restart NE confirmation 190. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 119. MIB Management 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 120. Backup screen 192. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 121. Restore screen 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 122. Activate command 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 123. SW key screen 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 124. Protection Schemes 195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 125. Mux Protection 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 126. Mux Protection Switch (Spare #0) 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 127. Mux Protection Switch (Main #1) 198. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 128. Radio Protection View 199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 129. Rx Static Delay menu 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 130. Radio Protection Switch (Spare #0) 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 131. Radio Protection Switch (Main #1) 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 132. Transmission Protection View 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 133. Tx Protection Commands (Spare #0) 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 134. Tx Protection Commands (Main #1) 205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 135. 1+0 available loopbacks 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 136. Channel 1 Loopback View 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 137. Tributaries Loopback View 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 138. 1+0 Loopback types 210. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 139. 1+1 available loopbacks 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 140. Channel 1 Loopback View 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 141. Tributaries Loopback View 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 142. 1+1 Loopback types 213. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 143. Loopback activation 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 144. Loopback removing 215. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 145. Diagnosis menu 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 146. Summary Block Diagram View: 1+0 without Ethernet ports 219. . . . . . . . . . . . . . . . . . . . . . . . . Fig. 147. Summary Block Diagram View: 1+0 with Ethernet ports 219. . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 148. Summary Block Diagram View: 1+1 HST without Ethernet ports 220. . . . . . . . . . . . . . . . . . . . . Fig. 149. Summary Block Diagram View: 1+1 HST with Ethernet ports 220. . . . . . . . . . . . . . . . . . . . . . . Fig. 150. Summary Block Diagram View: 1+1 FD without Ethernet ports 221. . . . . . . . . . . . . . . . . . . . . . Fig. 151. Summary Block Diagram View: 1+1 FD with Ethernet ports 221. . . . . . . . . . . . . . . . . . . . . . . . . Fig. 152. Radio sections 223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 153. Anomalies, defects, errored blocks, ES and SES according to ITU–T G.826 224. . . . . . . . . . Fig. 154. Performance View 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 155. Threshold table association screen 226. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 156. Current Data View 227. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 157. History Data 229. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 158. Threshold table 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

11

03

/3DB 06687 CA AA

340

340

Fig. 159. Thresholds Table creation 231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 160. Server access configuration screen 233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 161. Init Software Download screen 234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 162. SW Status screen 235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 163. SW Unit Status screen 236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 164. Allowed MIB management tasks at “NE logged–in” level 237. . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 165. Allowed MIB management tasks at “Network Element Synthesis” level 237. . . . . . . . . . . . . . . Fig. 166. Launch of MIB save to disk 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 167. MIB save to disk – phase 1 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 168. MIB save to disk – phase 2 239. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 169. Correspondence between MIB saved folder and MIB saved name 239. . . . . . . . . . . . . . . . . . . Fig. 170. Launch of MIB load from disk 240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 171. MIB load from disk – phase 1 241. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 172. MIB load from disk – phase 2 242. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 173. Corrective Maintenance general flow–chart 246. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 174. Active alarm screen 251. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 175. Abnormal condition list 257. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 176. Tx Mute functionality 258. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 177. Tributaries 9 to 16 visible in “8E1/DS1_Ethernet” configuration 259. . . . . . . . . . . . . . . . . . . . . . Fig. 178. 9400AWY R.2.0 split–mount system 291. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 179. Possible configurations of ODU (1+1) 292. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 180. MAIN Unit front side: interfaces for equipment control and Flash–Card–label position 299. . Fig. 181. MAIN Unit back side: Flash Card position 299. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 182. Flash Card profile and insertion direction 299. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 183. Equipment main parts containing local SW 300. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 184. Flash Card content 307. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 185. ECT–Equipment connection via Public Switched Telephone Network 311. . . . . . . . . . . . . . . . Fig. 186. ECT–Local external Modem cable 313. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 187. F Interface–Remote Modem cable 313. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 188. TD–32 AC modem dip–switch setting 316. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 189. Alcatel Lower Layers utility 320. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 190. Example of SWP Release and Version numbering 331. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 191. Example of Product levels and associated Customer Documentation 332. . . . . . . . . . . . . . . .

TABLESTab. 1. Additional feature and SWP–version relationship 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 2. Flash card upgrade carried out by one operator only for both stations 83. . . . . . . . . . . . . . . . . Tab. 3. Radio application: Market, capacity and modulation 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 4. ATPC Range Rx Threshold for ETSI 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 5. ATPC Range Rx Threshold for ANSI 178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 6. Command priority list 198. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 7. Command priority list 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 8. Command priority list 205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 9. 1+0 loopbacks 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 10. 1+1 loopbacks 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 11. SES Thresholds 223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 12. Alarm Synthesis indication 250. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 13. Alarm information, general description 252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 14. General issues of the alarm meanings and their respective maintenance actions 260. . . . . . . Tab. 15. Software products part numbers 270. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 16. Software licence part numbers 270. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 17. Markets, tributaries and modulations forecasted 290. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 18. Shelves Equipment Types 294. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 19. Allowed board/plug–in types in IDU Main shelf 295. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

12

03

/3DB 06687 CA AA

340

340

Tab. 20. Allowed board/plug–in types in IDU Extension shelf 295. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 21. Characteristics of the protection scheme 296. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 22. Available Flash cards for 9400AWY Rel.2 302. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 23. Capacity and modulation for 9400AWY R.2.0 flash cards (IDU basic) 303. . . . . . . . . . . . . . . . . Tab. 24. Capacity and modulation for 9400AWY R.2.0 flash cards (with 9–16 E1/DS1 plug–in) 304. . Tab. 25. Capacity and modulation for 9400AWY R.2.0 flash cards (with E3/DS3 plug–in) 305. . . . . . . Tab. 26. Capacity and modulation for 9400AWY R.2.0 flash cards (with Ethernet plug–in) 306. . . . . . . Tab. 27. 9400 AWY family 322. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 28. Handbook history 324. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 29. 9400AWY Rel.2.0 Documentation CD–ROM 327. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 30. Handbooks contained in the 9400AWY Rel.2.0 Documentation CD–ROM 328. . . . . . . . . . . . . Tab. 31. Documentation common to Alcatel Network Elements using 1320CT platform 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

13

03

/3DB 06687 CA AA

340

340

PRELIMINARY INFORMATION

a ) Warranty

Any warranty must be referred exclusively to the terms of the contact of sale of the equipment thishandbook refers to.ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims theimplied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liablefor errors contained herein or for damages, whether direct, indirect, consequential, incidental, orspecial, 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.

c ) Copyright Notification

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

d ) Safety recommendations

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

1 ) Service PersonnelInstallation and service must be carried out by authorized people having appropriate technicaltraining and experience necessary to be aware of hazardous operations during installation andservice and of measures to avoid any danger to them, to any other people and to the equipment.

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

3 ) Safety normsRecommended safety norms are not indicated in this manual, but in the Technical Handbook(see Tab. 30. on page 328). The warning labels that can be found on the equipment parts areindicated on page 16.Local safety regulations must be used if mandatory. Safety instructions in such handbookshould be used in addition to the local safety regulations. In the case of conflict between safetyinstructions stated in such manual and those indicated in local regulations, mandatory localnorms will prevail. Should not local regulations be mandatory, then safety norms in the abovecited manual will prevail.

e ) Service Personnel skillService Personnel must have been an adequate technical training on telecommunications and inparticular on the equipment this handbook refers to.Reading this handbook and the associated handbooks indicated in para.D.2 on page 327 is usuallynot enough to properly install, operate and maintain equipment.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

14

03

/3DB 06687 CA AA

340

340

HANDBOOK APPLICABILITY, PURPOSE AND HISTORY

Tab. 1. Additional feature and SWP–version relationship

This handbook describes SWP 9400AWY Rel.2.0, taking into account all system features that are madeavailable by first SWP version V2.0.0, as well as by successive SWP releases–versions. This tablesums–up the major additional features (mainly related to new HW items and relevant performance) thatare available starting from a certain SWP–version successive to first SWP version V2.0.0.

Additional featureAvailable fromSWP–version

New 48/60V and 24V PSU ETSI IDU Main and Extension units, with different’3DB xxxxx AB––’ P/N(refer to para.1–3.1.2 point [2] on page 67)

mandatory fromV2.0.1

7–8 GHz ODUs (new 9470AWY product) N.B.

Frequency shifter management (refer to para.2–5.3.2.2 on page 175)V2.0.2

Profiles management (refer to para.2–2.6 on page 146V2.0.2

New full–range (24–60V) IDU Main and Extension units N.B.

ANSI version (DS1/DS3) interfaces and relevant ANSI IDU Main and Extensionunits and Plug–Ins N.B. V2.0.3

to be confirmedANSI version ODUs N.B.

to be confirmed

N.B. the claimed item management must be meant from SWP–version point of view, independentlyfrom actual availability of related HW items.In particular, take into account that, on issue date of this handbook, IDU MAIN andEXTENSION units for 24–60V power supply are not available.

Ed.03 of this handbook is validated in conjunction with SWP versions V2.0.0 to V2.0.2only. Information relevant to SWP versions > V2.0.2 , if any, must be consideredpreliminary, subject to change and without any obligation on the part of ALCATEL.

For detailed information regarding handbook applicability, purpose and history, please refer to para.D.1on page 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

15

03

/3DB 06687 CA AA

340

340

HANDBOOK STRUCTURE

Information in this handbook is divided into the following parts:

a ) FRONT MATTER• TABLE OF CONTENTS• LIST OF FIGURES AND TABLES• PRELIMINARY INFORMATION• HANDBOOK STRUCTURE• SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING• CAUTIONS TO AVOID EQUIPMENT DAMAGE• QUICK GUIDE

It allows to access immediately the most frequently needed operative pieces of informationcontained in this handbook and in other related handbooks.

b ) SECTION 1: INSTALLATION on page 21This part describes in detail the operations necessary for the SWP installation and upgrading (ECTparts and equipment parts) and those to upgrade the 9400AWY system from (1+0) to (1+1)configuration or replace the Flash Card to improve system capacity.

c ) SECTION 2: NE MANAGEMENT on page 89In this section, the description of the menu structure and of all the NE functionalities available in theCraft Terminal is given.

d ) SECTION 3: NE MAINTENANCE on page 243In this section the description of the NE troubleshooting based on the use of the Craft Terminal isgiven.

e ) SECTION 4: SWP DESCRIPTION AND VERSIONS on page 267This section gives information on the Software Packages this handbook refers to, and that are bothindependent and independent on the specific SWP Version: commercial information (SWP andSoftware Licences P/Ns), PC requirements, SW Package Identification, SW Package Components,ECT SW Sub–Component, NE MIB Compatibility and additional features of new SWP versions.

f ) SECTION 5: APPENDICES on page 287In this section some additional information and instructions are given:• Equipment description and components• SW allocation, Flash Card and equipment control

• ECT–Equipment connection via public switched telephone network• Documentation Guide• Acronyms and abbreviations• Glossary of terms

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

16

03

/3DB 06687 CA AA

340

340

SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING

a ) Please refer to Technical Handbook (from ED.03) to obtain details regarding following information:

• Compliance with European norms

• 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 than ALCATEL’s,loaded with software applications described in this Handbook, is supplied in the Constructor’stechnical 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

17

03

/3DB 06687 CA AA

340

340

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 “as it is” and must never be disassembled .

b ) Antistatic protection device kit

When operating on boards out of the equipment shelf, this kit (see figure below) must be always warnand its termination must be connected to a grounded structure, to avoids the possible damage of theelectronic devices for electrostatic discharges.

ELASTICIZED BAND

COILED CORD

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 MAIN IDU UNIT or EXTENSION IDU UNIT.

e ) Craft Terminal connection

To connect the CT cable (at IDU’s F 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’s F interface and PC side• now the PC can be safely switched on.

f ) Craft Terminal disconnection

To disconnect the CT cable (at IDU’s F interface and/or PC side):• perform the logoff, exiting from the CT applications• 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

18

03

/3DB 06687 CA AA

340

340

QUICK GUIDEC.T. OPERATOR’S HANDBOOK SWP 9400AWY R.2.0

If you need immediate operative information on how to:

GENERAL TOPICS

get information on systemdocumentation

read Appendix D on page 321

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

read page 16

acknowledge cautions to avoidequipment damage

read page 17

have the description of the systemfrom the software point of view

read:

Chapter 4–1 on page 269

Appendix A on page 289

Appendix B on page 299

logically configure a station (orchange its configuration) andlogically set–up connections

logically provision equipment boards

get item P/Ns

get operative information regardingthe units in IDU shelf and ODU(connectors, leds, buttons)

get 9400AWY Rel.2.0 Technical Handbook and read itsQUICK GUIDE (same topics)

set and use the EOW functions ofthe equipment

know the consequences of unitextraction in IDU shelf

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

19

03

/3DB 06687 CA AA

340

340

.. continuesIf you need immediate operative information on how to:

EQUIPMENT INSTALLATION AND COMMISSIONING

install and commission equipmenthardware and software, as deliveredfrom Alcatel factory

read para.1–1.1 on page 24

LOGIN & LOGOFF (AFTER INSTALLATION AND COMMISSIONING)

login proceed as specified in para.2–1.3.1 on page 92

logoff proceed as specified in para.2–1.3.2 on page 95

change own password (for all users,from SWP version 2.0.2)

proceed as specified in para.2–2.6.2 on page 148

manage usernames and passwordsof all users (for administrator only,from SWP version 2.0.2)

proceed as specified in para.2–2.6.3 on page 149

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

proceed as specified in Appendix C on page 311

ECT SOFTWARE USAGE FOR EQUIPMENT SW MANAGEMENT(AFTER INSTALLATION AND COMMISSIONING)

have an overview on menu treestructure

open SECTION 2 – NE MANAGEMENT on page 89 of thismanage equipment configuration

open SECTION 2 – NE MANAGEMENT on page 89 of thishandbook and then search the information according to the

set–up parameters for maintenance

handbook and then search the information according to thelisted topics

use functions for SW management

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

20

03

/3DB 06687 CA AA

340

340

.. continuesIf you need immediate operative information on how to:

SYSTEM UPGRADE

upgrade ECT and equipment with anewer SWP version(same SWP release)

proceed as specified in chapter 1–4 on page 79

install a tributary plug–in on IDUMain and/or Extension unit

get 9400AWY Rel.2.0 Technical Handbook and read itsQUICK GUIDE (same topic)

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

proceed as specified in para.1–5.1 on page 81

replace Flash Card to improvesystem capacity

proceed as specified in para.1–5.2 on page 82

MAINTENANCE

provision and manage spare partsget 9400AWY Rel.2.0 Technical Handbook and read its

carry out preventive maintenance

get 9400AWY Rel.2.0 Technical Handbook and read itsQUICK GUIDE (same topic)

carry out corrective maintenance

get 9400AWY Rel.2.0 Technical Handbook, and go to itssection MAINTENANCE chapter Second LevelMaintenance paragraph Corrective Maintenance andproceed as specified; in any case, such section will usuallylead to the SECTION 3 – NE MAINTENANCE on page 243of this handbook to carry out troubleshooting via CraftTerminal.

Alternatively, access directly SECTION 3 – NEMAINTENANCE on page 243 of this handbook and proceedas specified.

To find any other kind of information not listed in the above table, please refer to the TABLE OFCONTENTS of this 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

21

03

/3DB 06687 CA AA

340

340

SECTION 1: INSTALLATION

SECTION CONTENT PAGE

Chapter 1–1 – General on equipment installation and SWP installation andmanagement

This chapter introduces the basic information regarding the main phases for9400AWY HW and SW installation, and those regarding the software management,with particular emphasis on SWP release and versions upgrading situations.

23

Chapter 1–2 – SWP installation in PC environmentThis chapter details all phases necessary to install for the first time a SWP in the PCenvironment, or to upgrade it with a new version of the same SWP, or to de–install theSWP components from the PC.

31

Chapter 1–3 – 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.

67

Chapter 1–4 – CT & NE Upgrade to a new SWP “version” (same SWP “release”)This chapter details all phases necessary to install a new SWP ’version’ in the PCenvironment as well as in the equipment environment.N.B. Procedure not meaningful for first version (V2.0.0) of the SWP.

79

Chapter 1–5 – System hardware upgradeThis chapter details all phases necessary to upgrade 9400AWY system from (1+0)to (1+1) configuration or replace the Flash Card to improve system capacity.

81

The symbol points out references to the other Handbooks.

Referenced handbook P/Ns are given in para.D.2 on page 327.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

22

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

23

03

/3DB 06687 CA AA

340

340

1–1 : GENERAL ON EQUIPMENT INSTALLATION AND SWP INSTALLATIONAND MANAGEMENT

This chapter 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 chapter, it is suggested to read Appendix B on page 299.

N.B. Please refer to para.D.3.2 on page 331 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 24

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

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

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

– Flash Card related special procedures on page 29

– NE configuration data change and save on page 30

– Craft Terminal related special procedures on page 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

24

03

/3DB 06687 CA AA

340

340

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

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

HW INSTALLATIONdescribed in:

ECT INSTALLATIONdescribed in:

9400AWYInstallation Handbook

Chapter 1–2 – SWP installation in PCenvironment on page 31 of this handbook

EQUIPMENT POWER–ON AND COMMISSIONINGdescribed in:

9400AWYLine–Up Guide

NE CONFIGURATION DATA SAVEdescribed in para.1–1.6 on page 30

of this chapter

Fig. 1. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

25

03

/3DB 06687 CA AA

340

340

1–1.2 First SWP installation in PC and NE environments

Fig. 2. 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 PCMS–NT ENVIRONMENT

2) NEW SWPINSTALLATION

3) NE SWP LOADINGINTO EQUIPMENTCONTROLLER(if necessary)

DURATION: – 1/2 hour with interface F– some 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. 2. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

26

03

/3DB 06687 CA AA

340

340

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 necessaryN.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.

• (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 1–2 on page 31

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

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

27

03

/3DB 06687 CA AA

340

340

1–1.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. 3. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

28

03

/3DB 06687 CA AA

340

340

[2] How to check NE versionProceed as follows:

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

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

version committed(active)

version stand–by(not active)

N.B. Usually, when the equipment is shipped from factory, only one SW version (committed) ispresent in the flash card.

Fig. 4. How to check NE SW 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

29

03

/3DB 06687 CA AA

340

340

1–1.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 26:

3 ) 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.0.0), in the case a newer version of the same A.B SWP package has to be installed(e.g.2.0.1).

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

4 ) 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 Chapter1–2 on page 31. After that, the situation is equal to that of point 1 ) on page 26.

1–1.5 Flash Card related special procedures

Taking into account the information contained in the Flash Card (see para.B.2 on page 302 forexplanations, if necessary), you could need to:

5 ) for system upgrade purposes, replace the flash card currently in use with a different typeFlash Card (see para.B.2.1 on page 302)In this case, please refer to Chapter 1–5.2 on page 82.

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

30

03

/3DB 06687 CA AA

340

340

1–1.6 NE configuration data change and save

It must be emphasized that , every time you change the equipment configuration data (see para.B.2.3 onpage 307), you must always save the relevant data:

a ) data present in Flash Card’s MIB bank [see point b ) on page 308]data present in Flash Card’s MIB bank can be saved in a MIB back–up file as described in Chapter2–13 on page 237.The same paragraph explains how to recover MIB data from the MIB back–up file.

The procedures in this handbook make often reference to the MIB data restore from the MIB back–upfile.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 cannot be saved in the MIB back–up file [see point c ) on page 308]NE network routing data can be easily saved as print–screens in a MS–Word file as follows:

1 ) open a new MS–Word document

2 ) open the screen containing the values of one of the NE network routing data you want to save

3 ) on the PC keyboard keep key “Alt” pushed and contemporarily push key “Print”, then releaseboth keys.With this operation the active screen image is copied to the PC clipboard

4 ) click in the opened MS–Word document and perform the “paste“With this operation the screen image is saved from the PC clipboard to the MS–Word document

5 ) click in the opened MS–Word document, under the image that has been saved, and push key“return”. You are ready to save another screen image.Save the MS–Word document, without closing it.

6 ) repeat steps 2 ) to 5 ) , until you have copied all screens

7 ) Print the MS–Word document, close and save it where you like.

1–1.7 Craft Terminal related special procedures

If you need to:

8 ) de–install Alcatel SW from the PC used as Craft terminal, refer to para.1–2.6 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

31

03

/3DB 06687 CA AA

340

340

1–2 SWP INSTALLATION IN PC ENVIRONMENT

This chapter details all phases necessary to install for the first time a SWP in the PC environment, or toupgrade it with a new version of the same SWP, or to de–install the SWP components from the PC.

Before starting the installation procedures, it is suggested to give a look to para.B.1 on page 300and Chapter 1–1 on page 23.

Procedures described in this chapter are carried out with the PC disconnected from the NE.

1–2.1 Requirements

1–2.1.1 PC characteristics

For all SWP versions, correct ECT installation requires a PC with the requirements hereafterdescribed:

1 ) HW Configuration

– CPU: Pentium III 850 MHz– RAM: 256 Mbytes (512 Mbytes suggested for Windows XP)– Hard Disk space: 4 Gbytes– Display Resolution: 1024x768 pixel– CD–ROM Drive: 24X– Primary Interface: Serial Port RS–232–C 9.6 to 57.6 Kbits/sec.– Optional Interface: Ethernet Card 10/100 Mbits/sec.

2 ) Windows Versions

– Windows 2000 till SP4– Windows XP (Professional Edition only) till SP2: It is mandatory de–activate the Firewall

installed.– Windows NT partially supported: CT–K 3.2 and related Q3/SNMP add–on deliveries can

be run on Windows NT but you have to take in account some restrictions in Almap PC 6.5and PC 7.0 components. They must be considered as Craft Terminal platform restrictionsin Windows NT environment.

3 ) Additional requirements

– Netscape Communicator or MS Internet Explorer 4.x or higher.– Java 2 Run Time Environment versions from 1.3.1–06 to 1.4.1–04

N.B. Each specific Java version could require minimal Windows SP 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

32

03

/3DB 06687 CA AA

340

340

1–2.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 Rel.3.x Operator’s Handbook (see Tab. 31. on page 329):

• section INTRODUCTION

• section GETTING STARTED

1–2.2 Reference Information Model

For version refer to paragraph on page

V 2.0.0 4–2.2 271

V 2.0.1 4–3.2 275

V 2.0.2 4–4.2 283

1–2.3 Summary of SW installation / de–installation phases

The sequence of installation phases for the SWP loading in PC WINDOWS–NT / XP (Professional Editiononly)/ 2000 environment (PC is disconnected from Equipment Controller) are as follows:

a ) Installation from SWP CD–ROM, para.1–2.4 on page 33

1 ) summary of installation of 1320CT + NE software from SWP CD–ROM, para.1–2.4.2 on page33

2 ) end of SW installation from SWP CD–ROM, para.1–2.4.6 on page 62

b ) CT initial configuration, para.1–2.5 on page 63.

Para.1–2.6 on page 65 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

33

03

/3DB 06687 CA AA

340

340

1–2.4 SWP loading in PC WINDOWS–NT / 2000 / XP (Professional Edition only)environment

Procedures described in the following are carried out with the PC disconnected from the NE.

1–2.4.1 Important warnings

Windows versions supported are just those listed in point 2 ) on page 31 (e.g. Windows XP

Home Edition, Windows 95, 98, ME, etc. are not supported).

Warning about Windows XP till SP2 – Professional Edition:

It is mandatory to de–activate the Firewall installed.

Windows NT is partially supported: CT–K 3.2 and related Q3/SNMP add–on deliveries can berun on Windows NT with some restrictions.

When installing this SWP on a PC where the same CT–K version was installed from a CD–ROM

related to Q3 NE, then it is mandatory to install the CT–K component from thisSWP. To do that you must carry out the CT Products automatic installation described inpara.1–2.4.5 on page 62.

1–2.4.2 Summary of installation of 1320CT + NE software from SWP CD–ROM

This operation must be performed by the Administrator of the PC, because he could set its IPaddress.

Hereafter are described the SWP installation procedures to be used for:

– First installation

The first time this SWP is installed on the PC, follow this procedure:

1 ) First, install the Java and LLMan components by using the guided installation mode, describedin the para. 1–2.4.3 – CT Products installation guided, on page 34.

2 ) Second, configure the Alcatel Virtual Network Card by using the procedure described in thepara.1–2.4.4 – Alcatel Virtual Network Card configuration, on page 37.

3 ) At the end, install the other components, by using the automatic installation mode, describedin the para.1–2.4.5 – CT Products automatic installation, on page 62.

– Complete updating

To update one or more components on the PC, follow this procedure:

1 ) To update the Java and LLMan components use the guided installation mode, described in thepara.1–2.4.3 – CT Products installation guided, on page 34.

2 ) To update the other components use the automatic installation mode, described in thepara.1–2.4.5 – CT Products automatic installation, on page 62.

– Partial automatic updating

To update one or more components, excluded Java and LLMan, use only the automatic installationmode, described in the para.1–2.4.5 – CT Products automatic installation, on page 62.

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”).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

34

03

/3DB 06687 CA AA

340

340

1–2.4.3 CT Products installation guided

In the following is described (step by step) the procedure to install “JRE” and “Alcatel Lower LayerManager” with the “CT Products installation guided”.

Operations sequence:

Step 1. Select the “CT Products installation guided” and press “NEXT” 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

35

03

/3DB 06687 CA AA

340

340

Step 2. Select “JRE” (ONLY if you have an OLDER version) and “Alcatel Lower Layer Manager”components.

WARNING: if try to update JRE and JRE V 1.4.1 is already installed, the procedure automaticallyde–install, it WITHOUT making the new installation. Keep attention in this case to the“Question Window” that appears, which ask you to proceed to the de–installation.

Step 3. Press “NEXT” button to execute the installation of the previously selected components.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

36

03

/3DB 06687 CA AA

340

340

Step 4. Press “NEXT” button to start the installation of the Lower Layers Manager.

Step 5. Select “Configure Lower Layer” and press “FINISH” button to complete the operation.

Step 6. 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”field with

a sequence of 12 “0”. The following window will be displayed.

Step 7. Press YES button to confirm.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

37

03

/3DB 06687 CA AA

340

340

1–2.4.4 Alcatel Virtual Network Card for Lower Layers

At first SWP installation on ECT, after installation of Alcatel Lower Layer Manager and before theinstallation of other ECT SW components, it is necessary, for NE connection using TCP/IP through serialport, to configure 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.

for installation on refer to paragraph on page

Windows NT 4.0 (partially supported) 1–2.4.4.1 38

Windows 2000 till SP2 1–2.4.4.2 44

Windows XP till SP2 (Professional Edition only) 1–2.4.4.3 52

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

38

03

/3DB 06687 CA AA

340

340

1–2.4.4.1 Windows NT 4.0

1–2.4.4.1.1 Installing the Alcatel Virtual Network Card for Lower Layers

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. 5. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

39

03

/3DB 06687 CA AA

340

340

– 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. 7. 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

40

03

/3DB 06687 CA AA

340

340

1–2.4.4.1.2 Configuring the Alcatel Virtual Network Card for Lower Layers

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. 9. NT configuration step 2) or a dialog box (Fig. 10. NT configuration step 3) may appear.

– Follow the instructions until the dialog box (Fig. 11. NT configuration step 4) will appear.

1

2

3

4

5

Fig. 8. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

41

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

42

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

43

03

/3DB 06687 CA AA

340

340

– 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.


1–2.4.4.1.3 Next step

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 CT Products automatic installation,para.1–2.4.5 on page 62.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

44

03

/3DB 06687 CA AA

340

340

1–2.4.4.2 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”).


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. 14. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

45

03

/3DB 06687 CA AA

340

340


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

46

03

/3DB 06687 CA AA

340

340

– Click the Have Disk... button in the Select Network Adapter 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

47

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

48

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

49

03

/3DB 06687 CA AA

340

340


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. 19. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

50

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

51

03

/3DB 06687 CA AA

340

340

– Configure the IP Address (1) and the Subnet Mask (2) and push OK (3).

3

1

2


Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers Managerto use it.

*** WARNING ***



1–2.4.4.2.3 Next step

You have now completed the installation and configuration of the Alcatel Virtual Network Card for LowerLayers in Windows 2000 environment. Now proceed with the CT Products automatic installation,para.1–2.4.5 on page 62.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

52

03

/3DB 06687 CA AA

340

340

1–2.4.4.3 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”).


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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

53

03

/3DB 06687 CA AA

340

340

Fig. 22. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

54

03

/3DB 06687 CA AA

340

340


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

55

03

/3DB 06687 CA AA

340

340

– Click the Have Disk... button in the Select Network Adapter 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

56

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

57

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

58

03

/3DB 06687 CA AA

340

340


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. 27. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

59

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

60

03

/3DB 06687 CA AA

340

340

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

61

03

/3DB 06687 CA AA

340

340

– 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.

1–2.4.4.3.3 Next step

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 CT Productsautomatic installation, para.1–2.4.5 on page 62.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

62

03

/3DB 06687 CA AA

340

340

1–2.4.5 CT Products automatic installation

Hereafter is described the procedure to install all the components except “JRE” and “Alcatel Lower LayerManager” with the “CT Products automatic installation”

Operations sequence:

Step 1. Select the “CT Products automatic installation ” and press “NEXT” button.

Step 2. Select all components except “JRE” and “Alcatel Lower Layer Manager”.

Step 3. Press “NEXT” button to execute the installation of the previously selected components.

1–2.4.6 End of SW installation from SWP CD–ROM

Having reached this phase, you have finished the Software transfer from SWP CD–ROM to the PCenvironment. Now, you can extract the SWP CD–ROM from the PC’s CD–ROM 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

63

03

/3DB 06687 CA AA

340

340

1–2.5 CT initial configuration

Procedures described in the following are carried out with the PC disconnected from the NE.

1–2.5.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 ,section “INSTALLATION”, chapter “Craft Terminal 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

64

03

/3DB 06687 CA AA

340

340

1–2.5.2 Craft Terminal connection to the NE

The CT can be connected to the NE through the Serial Port or through the Ethernet Network Port.

Only one connection can be active. The default connection is the Serial port.

1–2.5.2.1 Connection through the Serial Port

This connection is the default connection.

To connect the CT to the NE through the Serial Port:

1 ) The Alcatel Virtual Network Card for Lower Layers Software has to be installed on the PC (referto para. 1–2.4.4 on page 37).

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 v.3.1.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 v.3.1.x → NE Connection → Serial Port

1–2.5.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–2.2.3 on page 113).

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 v.3.1.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– v.3.1.x → Customization

Start → Programs → Alcatel → SNMPCT–K–ADD–ON v.3.1.x → NE Connection→Ethernet Port

Start → Programs → Alcatel → SNMPCT–K–ADD–ON v.3.1.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

65

03

/3DB 06687 CA AA

340

340

1–2.6 De–installation phases

This paragraph describes how to de–install from the PC the Software Package required by the CraftTerminal to manage the relevant Network Element.This can be useful, for example, when a version of the software package is no more updated.To de–install the following procedure can be followed:– with the CD–ROM containing the relevant Software product.– with the Control Panel of WINDOWS NT or WINDOWS 2000/XP when the CD–ROM containing the

relevant Software product is not present.From Control Panel select Add/Remove Programmes and de–install the components shown in thefollowing figure.

Fig. 31. De–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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

66

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

67

03

/3DB 06687 CA AA

340

340

1–3 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.

Before starting the installation procedures, it is suggested to give a look to para.B.1 on page 300and Chapter 1–1 on page 23.

Procedures described in this chapter are carried out with the PC connected to the NE.


1–3.1.1 Craft Terminal

The Craft Terminal, already loaded with the SWP to be downloaded toward the NE (as explained inprevious chapter 1–2 on page 31), must be available together with the cable for its connection to theequipment F interface.

1–3.1.2 NE state

[1] Equipment state

• equipment must have been previously installed, cabled, powered on and commissioned asdescribed in para.1–1.1 on page 24

• the SWP–version present inside the NE’s Flash Card must be lower than that of the ECT (referto para.1–1.3 on page 27 to know how to compare them).

[2] Equipment HW constraints from V2.0.1As far as the ETSI IDU MAIN AND EXTENSION UNITS (48/60V and 24V power supply) areconcerned:

• the use of the units with the new P/N (3DB xxxxx AB––) is mandatory when the used SWPversion is � 2.0.1

• the use of the units with the old P/N (3DB xxxxx AA––) is possible only when the used SWPversion is = 2.0.0

For details, please refer to Chapter IDU PART LIST in Technical Handbook (from Ed.02)

1–3.1.3 Operator skills and profile

a ) In addition to skills stated in para.1–2.1.2 on page 32, the Operator must be familiar with all theequipment functionalities.

b ) For SWP version V2.0.2 or later, the Operator’s profile must be “Administrator” or “craftPerson” (seepara.2–2.6 on page 146). Please refer to N.B. on page 70 for additional information.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

68

03

/3DB 06687 CA AA

340

340

1–3.2 Summary of the SWP installation phases

The installation phases are:

a ) SW download to the NE, para.1–3.3 herebelow

b ) Activation of the new Software Package on the NE para.1–3.4 on page 76

c ) MIB save para.1–3.5 on page 78

1–3.3 SW download to the NE

Following cautions stated in point e ) on page 17, through the suitable cable, connect the ECT to the Finterface of the MAIN unit (see Fig. 180. on page 299).

N.B. The software download can be performed also by using the OS Ethernet interface of the PC.To activate the Ethernet connection refer to para. 1–2.5.2.2 on page 64. In this case thedownload will last only few minutes.

Step 1. Start the ECT

• Start → Alcatel 1320CT

Step 2. Install the current SWP on the platform environment

• On NES (Network Element Synthesis) start “SWP Administrator”: Supervision → FilesAdministration (SWP Administrator)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

69

03

/3DB 06687 CA AA

340

340

• On SWP Administrator windows press install bottom

• Browse the SWP file descriptor “R94a.dsc” from the disk(C:\ALCATEL\JUSMw0.1.5\ect\swdw\R94AWY\2.0.x) N.B.

N.B. select the version 2.0.x that must be downloaded

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

70

03

/3DB 06687 CA AA

340

340

Step 3. Start Supervision

• On NES (Network Element Synthesis) start “Supervision”: Supervision → Start

Step 4. Show Equipment

• On NES (Network Element Synthesis) start “Show Equipment”: Supervision → ShowEquipment

N.B. There are two cases:

a ) the SWP version present on CT is V2.0.0 or V2.0.1 or V2.0.2 and the SWP version presenton NE is < 2.0.2In this case the NE is logged in immediately, and the 9400AWY Main view opens (proceedwith next step 5)

b ) the SWP version present on CT is � V2.0.3 and the SWP version present on NE is � 2.0.2In this case the Login screen appears (Fig. 35. on page 94), that must be filled in withsuitable values; if they are correct, NE is logged in, and the 9400AWY Main view opens(proceed with next step 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

71

03

/3DB 06687 CA AA

340

340

Step 5. Setup Server Access Configuration

• On JUSM start “Server Access Configuration”: SW Download → Server Access 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

72

03

/3DB 06687 CA AA

340

340

• In the “FTP Login” window the field “Address” must be set with the same address written in“Alcatel Lower Layer Manager – IP Network – Local address”. Press “OK” to confirm.

1

2

3

N.B. The UserId and Password present in this screen are relevant to the ftp login, are setautomatically with the Use System Default button and have no relationship with thosenecessary for the NE login.

Use System Default button

When the operator click the Use System Default button the field ADDRESS can be set in two differentmodes:1) by F interface: set IP address of the LLMAN to download in interface F mode2) by LAN interface: set IP address of the PC to download the software in LAN mode

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

73

03

/3DB 06687 CA AA

340

340

Step 6. Init SW Download

• On JUSM start “Init SW Download”: SW Download → Init SW Download

• Wait “List Sw Package” creation ...

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

74

03

/3DB 06687 CA AA

340

340

• When action is completed, press “Enter” to close message window.

• Now select a specific SWP to download on the NE, and press “Init download” to start it.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

75

03

/3DB 06687 CA AA

340

340

• Confirm the start of software downloading:

• The software downloading in progress is shown by a specific window:

• When the download is over the following window 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

76

03

/3DB 06687 CA AA

340

340

1–3.4 Activation of the new Software Package on the NE

• On JUSM start “SW Download”: SW Download → SW Download.

• After the software download, two software packages are present in the NE: one “Committed”and the other “Stand by”. The “NE Software Status Detail” window shows the information.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

77

03

/3DB 06687 CA AA

340

340

• To activate the new software package select the software package in “Stand by Status”.

• Now select on “Software Management Action” field “Activation”.

• Press “Apply Action”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

78

03

/3DB 06687 CA AA

340

340

• Confirm the selected action.

• After this window the NE restarts with the new software package.

1–3.5 MIB save

At the end, create a new MIB back–up copy (associated to the new SWP–version), as described in chapter2–13 on page 237.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

79

03

/3DB 06687 CA AA

340

340

1–4 ECT & NE UPGRADE TO A NEW SWP ’VERSION’ (SAME SWP ’RELEASE’)

This chapter details all phases necessary to install a new SWP ’version’ in the PC environment as wellas in the equipment environment.This procedure can be used only in the case depicted in point 3 ) on page 29, i.e.:

– ECT and equipment are running with one of the Software Packages with P/N indicated in Tab. 15. onpage 270 and with generic version ’A.B.c’ (’A.B’ is the SW release, ’c’ is the patch level)

– a new version of SWP ’A.B.d’ (d > c), having the same P/N, is delivered to Customer.

Procedure:

1 ) Requirements: see para.1–2.1 on page 31 and para.1–3.1 on page 67.

2 ) Carry out the installation of the new SWP version in the ECT environment, as indicated inchapter 1–2 on page 31.

3 ) The subsequent phases depend on the compatibility of MIB structure between previous andnew SWP versions. This MIB compatibility is indicated in the suitable chapter–paragraph(according to SWP Version) in Section 4 on page 267. In case you receive a version higher thanthe highest listed on page 267, please refer to the documentation accompanying the SWPdelivery to get this information.

N.B. Usually the MIB structure is fully compatible inside a SWP Release, so that thefollowing step 4 ) must be taken into consideration.

4 ) new MIB structure compatible with old MIB structure:

a ) perform the SW download with the following Craft Terminal commands (refer topara.2–12.2 on page 234 for detailed description):

• perform step 1 to 5 in para. 1–3.3 on page 68

• SW Download ⇒ Init SW download

• the screen of Fig. 161. on page 234 opens

• select the new NE–version to be downloaded

• with SWP Versions � 2.0.1 is necessary to select “Forced” option on CTscreen for SW Download activation request

• click on “Init download” button

• then, after about 1/2 hour, ⇒ SW Download ⇒ SW status ⇒ Apply Action to activatethe software.

N.B. The software download can be performed also by using the Ethernet interfaceof the PC. In this case the download lasts only few minutes.

b ) perform NE logoff followed by NE login.

The result is the Equipment working with the new SWP version nevertheless maintaining theold configuration data.

5 ) new MIB structure not compatible with old MIB structure

Procedure presently not 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

80

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

81

03

/3DB 06687 CA AA

340

340

1–5 SYSTEM HARDWARE UPGRADE

This chapter details all phases necessary to upgrade 9400AWY system from 1+0 to 1+1 configuration orinstall a new Flash Card to improve system capacity.

1–5.1 Upgrade from 1+0 to 1+1 configuration

N.B. This is a summary description. For detailed operative information, please refer to the 9400AWYRel.2.0 Installation Handbook and to the 9400AWY Rel.2.0 Line–Up Guide.

[1] Ascertain to have all materials necessary for the HW upgrade, at IDU and ODU levels as well asinstallation materials are concerned

[2] Install the second ODU (for general information, make reference to Fig. 179. on page 292)

[3] Install the CH0 Extension IDU ( b in Fig. 32. below )

[4] Connect the 100–pin cable ( c in Fig. 32. below )

[5] Connect the service cable ( d in Fig. 32. below )

[6] Connect the IDU–ODU cable

[7] Switch on the CH0 Extension IDU

[8] Connect the tributary connection ( e in Fig. 32. below )

[9] Repeat the previous steps in the other station of the link (to reduce the impact on traffic the HWimplementation must be done on the two terminal sides of the link)

[10] When the HW installation is completed and the link is managed by the CT: on the remote link sidein SYSTEM SETTING change the configuration, then repeat the setting in local side.

ËËËËËËËËËËËË a

b

c e d

a

from (1+0 & 8 E1/DS1)to (1+1 & 8 E1/DS1)

a

ËËËËËËËËËËËË a

b

c de

from (1+0 & 16E1/DS1)to (1+1 & 16 E1/DS1)

a

a

b

c e dËËËËËËËËË

from (1+0 & E3/DS3)to (1+1 & E3/DS3)

a

ËËËËËËËËË a

b

c e d

from (1+0 & Ethernet + 8 E1/DS1)to (1+1 & Ethernet + 8 E1/DS1)

Fig. 32. IDU expansion from (1+0) to (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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

82

03

/3DB 06687 CA AA

340

340

1–5.2 Flash Card upgrade

1–5.2.1 Introduction

Please refer to para.B.2 on page 302 for detailed information on Flash Card position, types, identificationand content.

N.B. To replace a Flash Card with the same type, for maintenance purpose, please refer topara.3–2.2 – Flash Card replacement procedures on page 264.

In general, the Flash Card upgrade must be done together with HW changes, e.g. changing thesystem capacity from “8E1/DS1” to “16E1/DS1” requires to:

– change the existing SW Key “8E1/DS1” to “16E1/DS1”; this chapter explains how to dothis operation

– and install (if not yet present) the 9–16 E1/DS1 PLUG–IN in the IDU MAIN UNIT, as wellin the IDU EXTENSION UNIT in case of 1+1 systems; to carry out this operation, pleaserefer to the TECHNICAL HANDBOOK, chapter IDU OPERATIVE INFORMATION,paragraph Installation of tributary plug–ins.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

83

03

/3DB 06687 CA AA

340

340

1–5.2.2 Summary procedure for both stations

This example is for changing existing SW Key “8E1/DS1” to “16E1/DS1”. Adapt it to the actual change youmust do.

Tab. 2. 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 (from SW Key“8E1/DS1” to “16E1/DS1”). This requires,in typical 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 16E1 and the Tributaryconfig is set again to 8E1 (not to 16E1as 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 8E1 TO 16E1CAPACITY the traffic is

impacted forCHANGE LOCAL CONFIG BY SYSTEMSETTING FROM 8E1 TO 16E1CAPACITY

impacted forabout 1 min

Following paragraphs are given just for Operators who need to know what to do in detail:– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

84

03

/3DB 06687 CA AA

340

340

1–5.2.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. 22. on page 302),

– and, already set by Alcatel Factory:

• with the same SWP–version (or higher) present in the 9400AWY system to be upgraded,already present in the Flash–Card’s SW COMMIT VERSION bank

• with the same NE network routing data of the system to be upgraded [such data could beprovided as specified in point b ) on page 30]

– and preferably, already set by Alcatel Factory:

• 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–13 on page 237 and give it to Alcatel 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

85

03

/3DB 06687 CA AA

340

340

1–5.2.4 Installation of a new Flash Card fully configured in factory

General warnings:

Screw fixingIn all described operations, the screw tightening torque must be:


This procedure can be carried out only if the new Flash Card is delivered with SW and data asspecified in para.1–5.2.3 on page 84.

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–1.3.1 on page 92)

[3] by Craft Terminal, save the MIB data [as shown in MIB BackUp in Fig. 164. on page 237 (fromoperative point of view, refer to para.2–7.3.1 on page 192)]

[4] wear the antistatic protection armlet (see point b ) on page 17) and connect its termination to agrounded structure

ATTENTION

(caution to avoid equipment damage)this avoids the possible damage of the electronic devices for electrostatic discharges

[5] remove the Flash Card cover (see Fig. 181. on page 299). Store tidily cover and screws for theirsuccessive mount

[6] extract the old Flash Card from the IDU Main Unit and insert the new one (refer to Fig. 182. on page299 for Flash Card profile and insertion direction)

[7] carry out MIB data restore and SW activation [(using MIB saved in step [3] above) as shown in MIBRestore in Fig. 164. on page 237 (from operative point of view, refer to para.2–7.3.2 and 2–7.3.3on page 193)]. In alternative to activation by SW, carry out the Equipment Controller HW Reset,pushing the suitable button on IDU MAIN Unit (see Fig. 180. on page 299). About two minutes are necessary for the supervision process to get data from the new flash card.

[8] restore the Flash Card cover removed in step [5] above (screw tightening torque as in point c ) onpage 17)

[9] now you can take off the antistatic protection armlet

[10] carry out Quick Configuration procedure by Craft Terminal (details in para.2–2.5 on page 131), tochange the system capacity

[11] carry out functional checks on the radio link by Craft Terminal

[12] as the new Flash Card is supplied with a self–adhesive label containing the Flash Card Name, getand stick it over the older one (see Fig. 180. on page 299); (N.B. if possible, remove the olderself–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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

86

03

/3DB 06687 CA AA

340

340

1–5.2.5 Installation of a new Flash Card not configured in factory

General warnings:

Screw fixing

In all described operations, the screw tightening torque must be:


With this procedure, the system is isolated from the supervision network.In fact, the insertion in a 9400AWY system connected to the network of a Flash Card with:– “default” or “unknown“ NE network routing data– SW Commit Version “unknown“ or lower than that present on the 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–1.3.1 on page 92)

[3] by Craft Terminal, take notice of the NE network routing data currently set [suggested procedurespecified in point b ) on page 30]

[4] by Craft Terminal, save the MIB data as shown in MIB BackUp in Fig. 164. on page 237 (fromoperative point of view, refer to para.2–7.3.1 on page 192)

[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 17) and connect its termination to agrounded structure

ATTENTION



[8] extract the old Flash Card from the IDU Main Unit and insert the new one. Refer to Fig. 182. on page299 for Flash Card profile and insertion direction

[9] restore the Flash Card cover removed in step [7] above (screw tightening torque as in point c ) onpage 17)


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

87

03

/3DB 06687 CA AA

340

340

[11] now you must perform all operations regarding the NE SW download and data definition, as it is wasdone at the equipment SW first time installation:

• SWP download from C.T. to NE, using the same SWP–version• NE network routing data definition (using data annotated in step [3] above)• MIB data restore and activation (using MIB saved in step [4] above) as shown in MIB Restore

in Fig. 164. on page 237 (from operative point of view, refer to para.2–7.3.2 and 2–7.3.3 onpage 193). In alternative to activation by SW, carry out the Equipment Controller HW Reset,pushing the suitable button on IDU MAIN Unit (see Fig. 180. on page 299).About two minutes are necessary for the supervision process to get data from the new flashcard.

[12] carry out Quick Configuration procedure by Craft Terminal (details in para.2–2.5 on page 131), tochange the system capacity

[13] connect the system to the supervision network

[14] carry out functional checks on the radio link by Craft Terminal

[15] as the new Flash Card is supplied with a self–adhesive label containing the Flash Card Name, getand stick it over the older one (see Fig. 180. on page 299); (N.B. if possible, remove the olderself–adhesive label before sticking the newer).

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.1–5.2.4 on page 85.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

88

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

89

03

/3DB 06687 CA AA

340

340

SECTION 2: NE MANAGEMENT


Chapter 2–1 – General introduction on views and menusThis chapter describes the organization of the 9400AWY ULS N.E., presented afterthe NE login.

91

EQUIPMENT CONFIGURATION MANAGEMENT

Chapter 2–2 – ConfigurationThis chapter describes the configuration relevant to the equipment management.

107

Chapter 2–3 – EquipmentThis chapter deals with the presentation of the N.E. and the structure of thehierarchical tree, and the types of subracks and boards, that comprise the NetworkElement.

151

Chapter 2–4 – Line InterfaceThis chapter describes the operations necessary for the configuration setting andverification of each tributary.

161

Chapter 2–5 – RadioThis chapter deals with the management of the Radio transmission features.

171

Chapter 2–6 – External input and output pointsThis chapter describes how to display and set the input/output environmentalalarms (housekeeping alarms).

185

FUNCTIONS FOR MAINTENANCE

Chapter 2–7 – SupervisionThis chapter describes how to manage the NE access from OS or local ECT andhow to restart the NE.

189

Chapter 2–8 – Protection schemesThis chapter deals with the management of the Radio protections.

195

Chapter 2–9 – LoopbacksThis chapter describes the commands for loopback management, forcommissioning or maintenance purposes.

207

Chapter 2–10 – DiagnosisThis chapter describes how to access the Alarm and Event Log files and explainsthe Summary 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”.

217

Chapter 2–11 – Performance MonitoringThis chapter deals with the use of the Performance Monitoring functionalities.

223

SOFTWARE MANAGEMENT

Chapter 2–12 – Software ManagementThis chapter deals with the management of the functions related to the softwareverification/download.

233

Chapter 2–13 – MIB ManagementThis chapter deals with the management of the functions related to the back–upand restore of equipment configuration data.

237

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

90

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

91

03

/3DB 06687 CA AA

340

340

2–1 GENERAL INTRODUCTION ON VIEWS AND MENUS

This chapter describes the organization of the 9400AWY N.E., presented after the NE login.First the view organization is introduced, then the accessible menu options are listed.Some further advices are given for Navigation principles.


a ) Craft Terminal

• the Craft Terminal, loaded with the SWP relevant to this NE, must be available together with thecable for its connection to the equipment F interface.

• the Craft Terminal SWP–version must match that loaded in this NE. Solve different situations,if any, according to instructions given in para.1–1.4 on page 29.

• this NE must have been already configured in the used Craft Terminal.

b ) Operator profiles and allowed operations

Starting with SWP–version V2.0.2, the menu options described in this section are allavailable logging in the system with the Administrator profile username and password.Logging the system with other operator profiles result in some functionality accesslimitations. For further information please refer to Profiles management , para.2–2.6 onpage 146.

c ) 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 somespecifications of the International Standard Organization (ISO) and of the standards applied tothe Synchronous Digital Hierarchy (SDH) (CCITT Recommendations).

d ) Documentation

Besides this handbook, all the documentation set this manual belongs to must be available to theOperator, to retrieve pieces of information not contained in this handbook. The documentation setis described in Appendix D on page 321.

2–1.2 NE management states

The elementary building blocks of any telecommunication network are called Network Elements (NEs).When operating with a Craft Terminal, the NE can present different management states according to thecondition of the connection (supervision, local access, connection state, etc.). Also general Alarm statesare 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 included in the Basic Craft Terminal Operator’sHandbook.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

92

03

/3DB 06687 CA AA

340

340

2–1.3 NE supervision, login, logoff and switch off

The Network Element Synthesis views enable to get access to the views described in this handbook.

– NE supervision and loginThe Network Element Synthesis view enables to work on local or remote NE ULS, selecting themand activating Supervision and Login, as described in para.2–1.3.1 below.

– NE logoff and switch offIn 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–1.3.2 on page95.

2–1.3.1 NE Login

a ) Cable connection (if not yet done)

Following cautions stated in point e ) on page 17, through the suitable cable connect the ECT to theF interface or to the OS Ethernet interface of the MAIN unit (refer to Fig. 180. on page 299).

To activate on the CT the connection through the Serial Port or through the Ethernet Port refer topara. 1–2.5.2 on page 64.

b ) Craft Terminal (CT) start–up

1 ) CT start :

– power on the CT and wait for PC start–up

– Start ⇒ Alcatel 1320CT:

• if choice Alcatel 1320CT is not available, PC is not configured as Craft Terminal:Software Package loading is necessary

after a while, the “Network Element Synthesis” screen will appear (Fig. 33. below),showing all Network Elements that can be selected. After this Start operation, all NEsappear with symbol “?” (it means they are not supervised)

Note: the symbol indicates the NE to which CT is locally connected by cable

Fig. 33. Network Element Synthesis Window

N.B. For a corrected operation, only on some PC with Windows 2000 or XP by using theserial connection, it is necessary to start the Lower Layers Manager (Start →Programs → Alcatel → Lower Layers → Lower Layers Manager) before starting theECT Platform (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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

93

03

/3DB 06687 CA AA

340

340

c ) Start supervision on a selected Network Element (NE)

From screen “Network Element Synthesis” (Fig. 33. above) :

1 ) select the interested Network Element (NE) clicking once left mouse button on it;

N.B. During the creation of the SNMP NE (refer to the 1320CT Basic Craft TerminalOperator’s Handbook, section 5 “EML CONSTRUCTION”), in the TCP/IP Port fieldnumber “161” must be inserted.

2 ) while NE selected, with right mouse button choose Start Supervision and with left mousebutton execute it (click once). In alternative, while NE selected, with left mouse button chooseSupervision ⇒ Start

Wait until the symbol “?” becomes at first (under exploration) and then colored “•” (it

means “NE in supervised state”), as shown in Fig. 34. below

N.B. In order to know the possible “color” meaning , refer to the:• 1320CT Basic Craft Terminal Rel.3.x Operator’s Handbook (see Tab. 31. on page

329)– chapter “SOFTWARE INSTALLATION”

• paragraph “Craft Terminal Configuration”,• sub–paragraph “Communication with NE”

Fig. 34. NE in supervised state

N.B. The User Label of the NE must not include the following characters:\ ? : * “ < > | .

WARNING: Due to a deep fading, the radio remote NE can be unreachable. In this condition in theUSM will appear the following 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

94

03

/3DB 06687 CA AA

340

340

In this case, operate as follows:

• The JUSM must be closed.In the NES will appear a broken icon and a red bullet.

• Wait for the automatic restarting of the Supervision (at the end of the fading conditions).The icon in NES will become whole and the bullet will take the color relevant to the alarms (ifany) 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.

d ) Network Element login

From screen “Network Element Synthesis” with NE in supervised state (Fig. 34. on page 93):

1 ) select the interested Network Element (NE) clicking once right mouse button on it;

2 ) select Show Equipment. There are two cases:

a ) the SWP version (present both on CT and NE) is V2.0.0 or V2.0.1In this case the NE is logged in, and the 9400AWY Main view opens (Fig. 37. on page 97)

b ) the SWP version (present both on CT and NE) is � V2.0.2In this case the Login screen appears (Fig. 35. below), that must be filled in with suitablevalues.

Fig. 35. 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.

If the Login values are correct, the 9400AWY Main view opens (Fig. 37. on page 97)

After the 9400AWY Main view has opened, all the available menus are explained in Section 2 NEMANAGEMENT on page 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

95

03

/3DB 06687 CA AA

340

340

2–1.3.2 NE Logoff or switch off

Before disconnecting the F interface cable or before switching off the NE:

– close the NE JUSM window clicking

– then, in the Network Element Synthesis Window (Fig. 36. below), stop the NE supervisionas follows:• select NE with mouse left button• holding it selected, select Stop supervision with mouse right button. In alternative,

while NE selected, with left mouse button choose Supervision ⇒ Stop

Fig. 36. NE Stop Supervision

• NE will go to not supervised state, with symbol “?” as shown in Fig. 33. on page 92.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

96

03

/3DB 06687 CA AA

340

340

2–1.4 9400AWY view organization

The 9400AWY view ( see Fig. 37. on page 97 ) contains the following fields, which provide the operatorwith the information needed to manage the NE:

• Severity alarm synthesis,

• Domain alarm synthesis,

• Management status control panel,

• View title,

• View area,

• Message/state area.

The Menu bar and the View area contained in the same NE view permit to perform all configuration andsupervision operations and the display the specific selected item.

The view organization is detailed in the Basic Craft Terminal Operator Handbook to which refer for thedescription.

N.B. Fig. 37. on page 97 shows the 9400AWY in 1+1 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

97

03

/3DB 06687 CA AA

340

340

Menu bar

Viewarea

Severity alarmsynthesis

Domain alarm synthesis

Main toolbar

Management state control panel

Fig. 37. 9400AWY Main view organization

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.3–1.4.1 on page250.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

98

03

/3DB 06687 CA AA

340

340

2–1.4.1 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

– Sw Download

The following figure shows the tabbed panel organization.

Each tab panel is labeled with the set name ( e.g. Equipment, Line Interface, etc ).

RESOURCETREE AREA

RESOURCE DETAIL AREA

RESOURCE LIST AREA

Fig. 38. View Areas

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

99

03

/3DB 06687 CA AA

340

340

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) orGraphical View (e.g., Equipment Domain).

• Tabular View: displays a tabular representation of the selected resource. As default, no tabularelement is shown.

• Graphical View: displays a graphical representation of the selected resource. As default, notabular 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–1.4.2 Resource Tree Area

The “Resource Area” displays all the available resources in a tree structure like the protocol stackhierarchy. The below figure shows an example of the resource tree instance (for the Line Interfacefunctions):

Fig. 39. Resource tree area

2–1.4.2.1 Selection Criteria

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

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

100

03

/3DB 06687 CA AA

340

340

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–1.4.3 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

2–1.4.4 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

101

03

/3DB 06687 CA AA

340

340

2–1.5 Introduction to the menu options

The menu bar allows to perform configuration and supervision functions on the Network Element.

This paragraph lists all menu options and then provides more details on the respective contained entries.

For each of them the relevant operative function are briefly introduced and it is referred the paragraphswhere they are detailed or the introduction to the options of each menu inserted in next paragraphs of thischapter.

From Chapter 2–2 on page 107 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–1.5.1 on page 102.

To navigate among the views and to set the TMN parameters.

• Configuration (second column). See para.2–1.5.2 on page 104.

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–1.5.3 on page 104.

To get information on the NE (alarms, performance monitoring, remote inventory).

• Supervision (fourth column). See para.2–1.5.4 on page 105.

To set the supervision states (i.e. Craft Terminal enabling).

• SW Download (fifth column). See para. 2–1.5.5 on page 105.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

102

03

/3DB 06687 CA AA

340

340

2–1.5.1 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–3 on page 151.

– External Points: Displays and sets the input/output environmental alarm.See Chapter 2–6 on page 185.

– Line Interface: Opens the Line Interface view to configure all the tributary ports.See Chapter 2–4 on page 161.

– Performance: Allows to manage the Performance monitoring.See Chapter 2–11 on page 223.

– Radio: Allows to manage all the functions relevant to the radio channels.See Chapter 2–5 on page 171.

– Protection Scheme: Allows to manage the Protection schemes in 1+1 configuration.See Chapter 2–8 on page 195.

– Loopback: Allows to manage the loopbacks available with the equipment.See Chapter 2–9 on page 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

103

03

/3DB 06687 CA AA

340

340

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

Tab panel

Fig. 40. Tab panels

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

104

03

/3DB 06687 CA AA

340

340

2–1.5.2 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–2.1 on page 108.

– Network configuration: See para. 2–2.2 on page 109.

– Alarm Severities: Manages the Alarm Severity Assignment Profile.See para. 2–2.3 on page 122.

– System setting: Allows the system configuration, providing the setting of all the parametersfor the NE setup. See para. 2–2.4 on page 127.

– Quick configuration: Allows a full system configuration through a guided procedure.See para. 2–2.5 on page 131.

– Profiles management: Allows the CT user profile management.N.B. this feature is available starting with SWP version V2.0.2.See para. 2–2.6 on page 146.

2–1.5.3 Diagnosis menu introduction

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

– Log Browsing: Manages the events stored in the NE.Opens the following menu options:• Alarm log• Event log• Software Trace logSee para. 2–10.1 on page 217.

– Current configurationView: Displays the current configuration of the NE.

See para. 2–10.2 on page 217.

– 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–10.4 on page 218.

– Abnormalcondition list: Displays the manually operations active in the 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

105

03

/3DB 06687 CA AA

340

340

2–1.5.4 Supervision menu introduction

This menu allows to set the supervision states of the NE, by means of the following entries (see chapter2–7 on page 189) :

– Access State: Manages the supervision access to the NE, via CT or OS.Opens the following menu options:• OS• RequestedSee para. 2–7.1 on page 189.

– Restart NE: Reset of the NE software.See para. 2–7.2 on page 190.

– MIB Management: Allows to perform backup and restore operations of the MIB.See para. 2–7.3 on page 191.

– SW key: Displays the type of the key stored in the flash card.See para. 2–7.4 on page 194.

2–1.5.5 Download menu introduction

This menu allows to manage the NE software, by means of the following entries (see chapter 2–12 on page233) :

– Server Access Configuration: Manages the configuration of the FTP server to be used for the software

download to the NE.See para. 2–12.1 on page 233.

– Init SW download: Manages the software download to the NE.See para. 2–12.2 on page 234.

– SW status: Shows and manages the status of the software packages installed in the NEmemory banks.See para. 2–12.3 on page 235.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

106

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

107

03

/3DB 06687 CA AA

340

340

2–2 CONFIGURATION

This chapter describes the following Configuration menus:

– NE Time on page 108

– Network Configuration on page 109

• Local Configuration on page 110

• NTP Configuration on page 111

• Ethernet Configuration on page 113

• IP Configuration on page 114

– IP static routing configuration on page 114

– OSPF Area configuration on page 118

– IP Address configuration of Point–To–Point Interfaces on page 120

• Routing information on page 121

– Alarm Severities on page 122

– System Settings on page 127

• NE Configuration on page 127

• Overhead on page 130

– Quick Configuration Procedure on page 131

– Profiles management on page 146

• Functional description on page 146

• Change Password procedure on page 148

• Users Management procedure 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

108

03

/3DB 06687 CA AA

340

340

2–2.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. 41. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

109

03

/3DB 06687 CA AA

340

340

2–2.2 Network Configuration

To get access the Network Configuration option select the Configuration pull down menu, as shownin the following figure.

Fig. 42. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

110

03

/3DB 06687 CA AA

340

340

2–2.2.1 Local Configuration

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. 43. on page 110 ) 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. 43. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

111

03

/3DB 06687 CA AA

340

340

2–2.2.2 NTP Configuration

By selecting NTP Configuration the dialog–box in Fig. 44. opens, which allows to enable the NetworkTime Protocol.

Fig. 44. 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.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

112

03

/3DB 06687 CA AA

340

340

2–2.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. 45.

NE1

NE2

NE3NE4

Fig. 45. Map

As example NE1 must be set as Master:

– enable the NTP protocol;– in the Main Server address field and in the Spare Server address field write nothing (in this way

the NE is defined as Master).

NE2 is set as Slave:

– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

113

03

/3DB 06687 CA AA

340

340

2–2.2.3 Ethernet Configuration

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. 46. on page 113 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 can be only in “ None” state. If “OSPF” or “ Both“ options of Routing IP

Protocol field are selected, also the “ Associated OSPF Area “ must be set.• OSPF Area pointer: if as IP Routing Protocol the OSPF protocol has been selected it is possible

to create OSPF areas.

– Enable which comprises two selections to Enable or Disable the Ethernet interface.

Refresh button refresh the information written in the upper port.Apply button performs a configuration change of the data.Close button closes the dialog without changes of the data.

Fig. 46. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

114

03

/3DB 06687 CA AA

340

340

2–2.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. 47. on page 114).

Fig. 47. IP configuration screen

2–2.2.4.1 IP static routing configuration

The dialog–box opens ( see Fig. 48. on page 115 ) 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 aspecific 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 availableby 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

115

03

/3DB 06687 CA AA

340

340

Fig. 48. IP static routing configuration screen

By pressing Create pushbutton the screen in Fig. 49. on page 116 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

116

03

/3DB 06687 CA AA

340

340

Fig. 49. Create Static routing

If in the screen of Fig. 49. on page 116 the Default Gateway IP Address check box has been selected,write in the Default Gateway IP Address field below the relevant IP address.

If in screen in Fig. 49. on page 116 has been selected the Point To Point Interface Index check box,the screen in Fig. 50. on page 117 opens.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

117

03

/3DB 06687 CA AA

340

340

Fig. 50. Point To Point Interface Choice

In this screen one of the 3 NMS channels (NMS–RF, NMS–V11, NMS–G703) can be 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

118

03

/3DB 06687 CA AA

340

340

2–2.2.4.2 OSPF Area configuration

The dialog–box opens ( see Fig. 51. on page 118 ) and allows to configure the parameters for OSPF(Open Shortest Path First) Area Table Configuration.


– OSPF Area IP Address

– OSPF Area Stub

The fields give a synthetical information that includes all the addresses (specific to a NE and to a Network)in an Area.

Apply button is used to perform a configuration change of the data contained in the complete RAP 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. 51. OSPF Area configuration screen

WARNING: Area 0 is managed and created by default with Id = 0 and IP address = 0.0.0.0

WARNING: If the area is a Stub area the functionalities of the Remote Craft Terminal are not fullyguaranteed.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

119

03

/3DB 06687 CA AA

340

340

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

N.B. 3 areas max. can be created.

Fig. 52. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

120

03

/3DB 06687 CA AA

340

340

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

The dialog–box opens ( see Fig. 53. on page 120 ) and allows to Enable or Disable the three NMSchannels, which use the PPP protocol.

OK 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.

Fig. 53. IP Address configuration of Point–To–Point Interfaces 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

121

03

/3DB 06687 CA AA

340

340

2–2.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. 54. on page 121 opens.

Fig. 54. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

122

03

/3DB 06687 CA AA

340

340

2–2.3 Alarm Severities

By selecting the Alarm Severities option from the Configuration menu the screen in Fig. 55. on page123 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

123

03

/3DB 06687 CA AA

340

340

Fig. 55. Alarm Severities Profile

In the screen of Fig. 55. on page 123 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–2.3.1 on page 124.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

124

03

/3DB 06687 CA AA

340

340

2–2.3.1 How to create a new Alarm Severity Profile

– Select in the screen of Fig. 55. on page 123 the Alarm Profile to be cloned.

– Click the Clone pushbutton.

– The screen of Fig. 56. on page 124 appears.

– Digit the name to be assigned to the new Alarm Profile and click on Apply.

Fig. 56. 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. 57. on page 124).

Fig. 57. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

125

03

/3DB 06687 CA AA

340

340

– 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. 58. on page 125).

Fig. 58. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

126

03

/3DB 06687 CA AA

340

340

– 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. 59. on page 126).

Fig. 59. 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. 59. on page 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

127

03

/3DB 06687 CA AA

340

340

2–2.4 System Settings

This menu allows the system configuration, providing the setting of all the parameters for the NE setup.

The main window provides 3 tabbed–panels, one for each type of function to be managed:

– NE configuration– Overhead

WARNING: At the first configuration (i.e. with a flash card with an empty MIB) at the end of theconfiguration the “Restart NE” must be performed (refer to para. 2–7.2 on page 190).

WARNING: Should during this procedure to be selected a wrong type (i.e. PSU4860 instead of PSU24), to insert the correct type enter the System Settings menu → NE configuration tab panel; select the correct type; click on Apply and then restart the EC by entering menu Supervision and by activating command ”Restart NE”.

2–2.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. 60. on page 127 will appear.The field “Type” contains all the allowed configurations supported for the NE. The operator choice will beapplied by selecting the related “Apply” button.The “Structure” area displays the market, capacity and modulation and, if needed, the ability to changeit, according to NE market configured in the previous screen.The field ”Market” contains the market type: ETSI or ANSI (refer to Tab. 3. on page 128). The operatorchoice will be applied by clicking the related “Apply” button.

Fig. 60. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

128

03

/3DB 06687 CA AA

340

340

Tab. 3. Radio application: Market, capacity and modulation

Market Capacity Modulation

2xE1 4QAM

4xE1 4QAM / 16QAM

ETSI 8xE1 4QAM / 16QAM

16xE1 4QAM / 16QAM

1xE3 4QAM / 16QAM

4xDS1 4QAM

ANSI 8xDS1 4QAM / 16QAMANSI(see Tab. 1. on page 14) 16xDS1 4QAM / 16QAM

1xDS3 4QAM / 16QAM

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

WARNING: When you change the modulation scheme (from 4 QAM to 16 QAM or vice–versa) the 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 (refer to para. 2–5.4on page 176). If the value is out of range the relevant field in the RTPC & ATPC screenappears empty (automatically is associated a default value, but this value is not displayed).Fill the field with the suitable value.

The Capacity can be modified by selecting a different type according to Tab. 3. and then selecting the”Apply” button to send the new value.

N.B. After a change in the “Type” or “Market” or “Capacity” or “Modulation” field the explicitconfirmation shown in Fig. 61. is requested.

Fig. 61. Confirmation message

N.B. Only one change can be performed in this screen. When the user confirms the change in the “Type” or “Market” or “Capacity” or “Modulation” fieldall the other fields are disabled. To perform another change close the screen and enter 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

129

03

/3DB 06687 CA AA

340

340

N.B. After a change in the “Type” or “Market” or “Capacity” or “Modulation” field (for the “Modulation”only for the remote NE configuration) at the completion of the operation the CT forces the JUSMclosing with the following warning message (see Fig. 62. ).

Fig. 62. USM closing warning message

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/DS1 tributary (unbalanced 75 ohm or balanced 120ohmfor E1 tributary; balanced 100 ohm for DS1 tributary).

The impedance value will be applied by clicking on the related ”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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

130

03

/3DB 06687 CA AA

340

340

2–2.4.2 Overhead

The ”Overhead” tabbed panel identifies the parameters for the management of the phone number andauxiliary interface (Fig. 63. on page 130).

Fig. 63. Overhead Configuration

The field ”Phone Number” in the ”Order Wire Configuration” area allows the operator to read and writethe station number associated to the Engineering Order Wire to be used in the selective call. Possiblevalues are: 10–99.

N.B. Number 00 is the value associated to the general call.

The parameter will be sent to NE by clicking on the related “Apply” button.

The field ”Type” in the ”Auxiliary Interface Configuration” area allows the operator to change theinterface of the auxiliary channels.The parameter will be sent to NE by clicking on the related “Apply” button.

The field Alarm Profile allows to associate to the Overhead alarms a particular Alarm Profile: a defaultalarm profile or an Alarm Profile previously created by the Operator (refer to para. 2–2.3.1 on page 124).To associate a different Alarm Profile click on the selection button and make the selection among theavailable Alarm Profiles.

N.B. the default associated Alarm Profile is the Primary 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

131

03

/3DB 06687 CA AA

340

340

2–2.5 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.

To start this application, select the “Quick Configuration” option from the “Configuration” menu. Thewindow in Fig. 64. on page 132 will appear. This window is the first step of the procedure.

The procedure consists of different steps according to the configuration:

– 1+0 configuration:

• 6 steps for the simplified configuration

• 12 steps for the advanced configuration (the advanced configuration can be activated in step5)

– 1+1 configuration:

• 7 steps for the simplified configuration

• 13 steps for the advanced configuration (the advanced configuration can activated in step 6)

Note on the use of the buttons available in the screens:

– 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: this button is active only in the last step. By clicking on this button the operator confirms theconfiguration and the new parameters are sent to the equipment.

– Cancel: by clicking on this button the operator quits the procedure without any change in theconfiguration.

– Help: by clicking on this button the operator calls the help–on line.

In the following is explained step by step the most complete procedure for 1+1 configuration.

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).

WARNING: Should during this procedure to be selected a wrong type (i.e. PSU4860 instead of PSU24), to insert the correct type enter the System Settings menu → NE configuration tab panel; select the correct type; click on Apply and then restart the EC by entering menu Supervision and by activating command ”Restart NE”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

132

03

/3DB 06687 CA AA

340

340

For all steps of this procedure, with reference to items to be configured, pleaserefer to Tab. 1. on page 14 for system features and SWP–versionrelationship

Step 1 (NE Parameter configuration)

Fig. 64. Quick Configuration Procedure: NE Configuration (Step 1)

Step 1 provides a screen to configure two NE parameters:– Market– Type configuration.

The possible selections for the Type field are:– 1+0 unprotected configuration– 1+1 HSB: Hot Standby protected configuration– 1+1 FD: Frequency Diversity protected configuration

N.B. Every type is available with the following tributaries:– 8xE1/8xDS1– 16xE1/16xDS1– 1xE3/1xDS3– 8xE1/8xDS1 + 2 Ethernet ports

and with the following Power Supply Units:– ±24 V Power Supply– ±48/±60 V Power Supply– ±24/±60 V Power Supply (Full Range)

The market choice implies a first selection of possible frame structure. The type definition implies theequipment configuration and other related functions: for example, the protection schemes supported.

N.B. For the Remote NE in this step the Type and the Market cannot be modified. To modify them the System Settings menu must be used (refer to para. 2–2.4.1 on page 127).

To go to step 2 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

133

03

/3DB 06687 CA AA

340

340

Step 2 (Frame structure and modulation format)

The screen shown in Fig. 65. on page 133 provides the fields to set the Structure of the Frameconfiguration (Capacity and Modulation).

The capacity implies the choice of modulation; for example, if the tributary structure is 2E1 (for ETSImarket) only 4QAM modulation scheme is supported.

N.B. The association between Capacity and Modulation is shown in Tab. 3. on page 128.

Moreover, the Impedance for the E1 tributary also must be selected in the Tributary Port Configuration(unbalanced 75 ohm or balanced 120 ohm).

Fig. 65. Quick Configuration Procedure: Frame Configuration (Step 2)

In the screen displayed in Fig. 65. on page 133 (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.

N.B. For the Remote NE in this step the Capacity and the Modulation cannot be modified. To modifythem the System Settings menu must be used (refer to para. 2–2.4.1 on page 127).

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

134

03

/3DB 06687 CA AA

340

340

Step 3 (Tributary configuration)

Step 3 allows the operator to choose, for each tributary configured, the signal mode or disable it(Fig. 66. on page 134).

Fig. 66. Quick Configuration Procedure: Tributaries Configuration (Step 3)

By clicking on the one facility button (“All Framed”, “All Unframed” and “All Disabled”), the operator canconfigure all the tributaries with the same values; otherwise he can apply all configuration for each tributaryby selecting the related value from the relevant scroll list.

N.B. This procedure can be used also after the first configuration to perform multiple changes in theconfiguration both in the local and in the remote NE.

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

Market Capacity Number of disabled tributaries

2xE1 � 1

ETSI4xE1 � 1

ETSI8xE1 � 1

16xE1 � 8

ANSI4xDS1 � 1

ANSI(see Tab. 1. on page 14)

8xDS1 � 1(see Tab. 1. on page 14)

16xDS1 � 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

135

03

/3DB 06687 CA AA

340

340

Step 4 (Automatic restoration criteria configuration)

Step 4 allows the operator to choose the restoration criteria (revertive or not revertive for the 3 possibleprotections available in the 1+1 configuration (Fig. 67. on page 135):

– Radio Protection (Rx RPS–Hitless Switch)

– Mux/Demux Protection (Tx/Rx EPS)

– HSB Tx Protection (RF Hot Stand–by)

Fig. 67. Quick Configuration Procedure: Tributaries Configuration (Step 4)

To go to the next step click on button “Next” . For:

– SWP version = 2.0.0, proceed to Step 5 on page 136

– SWP version > 2.0.0, proceed to Step 5 on page 137


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

136

03

/3DB 06687 CA AA

340

340

Step 5 (Channel configuration) in Rel. 2.0.0

Step 5 allows the operator to define the basic parameters for each configured channel. The related screenis shown in the Fig. 68. on page 136:

Fig. 68. Quick Configuration Procedure: Channels Configuration (Step 5 in Rel. 2.0.0)

In the Channel Configuration area the ATPC can be Enabled or Disabled. If enabled, the other ATPCparameters (min. value, max. value and Rx threshold) must be configured in RTPC & ATPC menu in theRadio domain (refer to para. 2–5.4 on page 176).

If ATPC is disabled in the RTPC area the power (constantly transmitted) can be selected by writing thesuitable value in the Tx power field.

In the Frequency Value area the Tx operating frequency must be written in the Tx Freq field.

N.B. The Tx Frequency value can be changed only on the Local NE (To change the Tx frequencyfor the Remote NE use the Radio menu – refer to para. 2–5.3 on page 173).

The Rx Frequency is automatically changed according to the frequency shifter available with the ODU.

All the values must be selected according to the relevant allowed ranges (shown between brackets).

N.B. In case of 1+1 HSB the choices will be applied to both “channels”. In case of 1+1FD, the samescreen will be re–proposed for channel 0 with the same choices applied for channel 1, with thepossibility to change the frequency, but without any possibility to change ATPC/RTPC selection.

To go to the next step 6 on page 138 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

137

03

/3DB 06687 CA AA

340

340

Step 5 (Channel configuration) from Rel. 2.0.1

Step 5 allows the operator to define the basic parameters for each configured channel. The related screenis shown in the Fig. 69. on page 137:

Fig. 69. Quick Configuration Procedure: Channels Configuration (Step 5 from Rel. 2.0.1)

In the Channel Configuration area the ATPC can be Enabled or Disabled. If enabled, the other ATPCparameters (min. value, max. value and Rx threshold) must be configured in RTPC & ATPC menu in theRadio domain (refer to para. 2–5.4 on page 176).

If ATPC is disabled in the RTPC area the power (constantly transmitted) can be selected by writing thesuitable value in the Tx power field.

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).

ODU with one Shifter onlyIf 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 Next (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’.

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 the shifter).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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

138

03

/3DB 06687 CA AA

340

340

Step 6 (Local configuration)

Step 6 performs the network configuration (Fig. 70. on page 138). This window allows to enter to IPaddress associated to the F interface of the NE.

N.B. The IP Address can be changed only on the Local NE (To change the IP Address for theRemote NE use the menu Configuration → Network Configuration → Local Configuration– refer to para. 2–2.2.1 on page 110).

Fig. 70. Quick Configuration Procedure: Local IP Address (Step 6)

For an advanced network configuration the operator must select the “Advanced Configuration” flag.

If the flag has been selected, the screens in the next steps allow the operator to perform a completeconfiguration of all the Network parameters.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

139

03

/3DB 06687 CA AA

340

340

Step 7 (OSPF area configuration)

Step 7 allows to configure one or more OSPF Areas (3 areas max.) (Fig. 71. below).

Fig. 71. Quick Configuration Procedure: OSPF Area Configuration (Step 7)

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.

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.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

140

03

/3DB 06687 CA AA

340

340

Step 8 (IP static route configuration)

The following windows for Network Configuration allow the complete IP configuration.

Step 8 configures one or more Static Routers (Fig. 72. on page 140).

Fig. 72. Quick Configuration Procedure: IP Static Router Configuration (Step 8)


[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 open static 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

141

03

/3DB 06687 CA AA

340

340

Step 9 (NMS RF channel configuration)

Step 9 allows the configuration of the NMS–RF channel (Fig. 73. on page 141):

Fig. 73. Quick Configuration Procedure: NMS–RF Interface Configuration (Step 9)

The “NMS–RF” interface is a communication interface based on the use of an in–frame RF proprietary64 kbit/s channel. Through the “NMS–RF” interface the NE can exchange management messages witha remote OS (or Craft Terminal) station.

The NMS–RF channel can be Enabled or Disabled by selection in the NMS RF 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.



All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

142

03

/3DB 06687 CA AA

340

340

Step 10 (NMS V11 channel configuration)

Step 10 allows the configuration of the NMS–V11 interface (Fig. 74. on page 142):

Fig. 74. Quick Configuration Procedure: NMS–V11 Interface Configuration (Step 10)

Through the “NMS–V11” interface the NE can exchange management messages with an OS (or CraftTerminal) in the same station.

The NMS–V11 channel can be Enabled or Disabled by selection in the NMS V11 field.



In the PPP_MODE field 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

143

03

/3DB 06687 CA AA

340

340

Step 11 (NMS G703 channel configuration)

Step 11 allows the configuration of the NMS–G703 interface (Fig. 75. on page 143):

Fig. 75. Quick Configuration Procedure: NMS–G703 Interface Configuration (Step 11)

Through the “NMS–G703” interface the NE can exchange management messages with an OS (or CraftTerminal) in the same station.

The NMS–G703 channel can be Enabled or Disabled by selection in the NMS G703 field.



In the MODE field 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 link adjacent AWY or to interface MUX based on 64 kbit/s, avoiding any V.11/G.703 adapter.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

144

03

/3DB 06687 CA AA

340

340

Step 12 (Ethernet configuration)

Step 12 (Fig. 76. on page 144) allows to configure the Ethernet Interface.

Fig. 76. Quick Configuration Procedure: Ethernet Configuration (Step 12)

The Ethernet interface can be Enabled or Disabled by selection in the Ethernet configuration field.

If enabled, in the relevant fields below enter the IP address, the IP mask and select the Routing IPprotocol. If the selected routing protocol has been OSPF, select also the area number in the AssociatedOSPF Area 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

145

03

/3DB 06687 CA AA

340

340

Step 13 (Summary)

Step 13 is the last step. The screen shown summarizes all the parameters configured during thisprocedure and some relevant parameters with default values (Fig. 77. on page 145).

Fig. 77. Quick Configuration Procedure: Summary (Step 13)

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.

At the end the operator can confirm the selections by pressing the “Finish” button. All the parameters willbe stored and sent to the 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

146

03

/3DB 06687 CA AA

340

340

2–2.6 Profiles management

N.B. this feature is available starting with SWP version V2.0.2.

2–2.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. 81. on page 149.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. 81. on page 149.

• 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

147

03

/3DB 06687 CA AA

340

340

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. 81. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

148

03

/3DB 06687 CA AA

340

340

2–2.6.2 Change Password procedure

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

1 ) Configuration ⇒ Profiles Management ⇒ Change Password

Fig. 78. Profile Management options

2 ) Following screen appears; fill it with old and new passwords, taking into account passwordcharacteristics listed in point [1] on page 146. New password will be active at next login (afterhaving logged out).

1

2

3

4

Fig. 79. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

149

03

/3DB 06687 CA AA

340

340

2–2.6.3 Users Management procedure

This procedure is available to users with the Administrator profile only.

1 ) Configuration ⇒ Profiles Management ⇒ Users Management (see Fig. 78. on page 148)

2 ) Following screen appears. Click on Help

Fig. 80. Users Management screen

3 ) Following screen appears. Click inside to explore matters and carry out the desired action.

Fig. 81. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

150

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

151

03

/3DB 06687 CA AA

340

340

2–3 EQUIPMENT

This chapter describes the types of functions offered to the user for Equipment Management.

N.B. Please refer to Appendix A on page 289 for the detailed description of equipment functions andcomponents.

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. 82. on page 152 for 1+0 configuration

– Fig. 83. on page 152 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: 8xE1/DS1, 16xE1/DS1, E3/DS3 withor without the Ethernet ports.

A colored ball gives information on the status of the associated object (Equipment, ODU, IDU, IDU board).The colour 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

152

03

/3DB 06687 CA AA

340

340

IDU

ODU

Equipment Status

ODU Status

IDU Status

Fig. 82. 1+0 Equipment view

IDU/MAIN Ch #1

ODU

Ch#1

IDU Status

Equipment Status

ODUStatus

IDU Ch #0

ODU

Ch#0

Fig. 83. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

153

03

/3DB 06687 CA AA

340

340

2–3.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–3.1.1 1+0 configuration

The screen in Fig. 84. on page 153 will appear.

IDU

MAIN BOARDStatus

IDU Status

Fig. 84. 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 2 Ethernet ports

– IDU/MAIN/8xE1/DS1 Ch#1 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1configuration

– IDU/MAIN/1xE3/DS3 Ch#1 with the E3/DS3 tributaries 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

154

03

/3DB 06687 CA AA

340

340

2–3.1.2 1+1 configuration

The screen in Fig. 85. on page 154 will appear for the Ch#1 and the screen in Fig. 86. on page 155 willappear for the Ch#0.

IDU

MAIN BOARDStatus

IDU Status

Fig. 85. 1+1 IDU/MAIN Ch#1 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

155

03

/3DB 06687 CA AA

340

340

IDU

IDU Status

Fig. 86. 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 2 Ethernet ports (this board receives the power supply from the MainIDU only).

– IDU/MAIN/8xE1/DS1 Ch#1 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1configuration

– IDU/MAIN/1xE3/DS3 Ch#1 with the E3/DS3 tributaries interface.

The IDU channel#0 includes the IDU/Ext Ch#0 object which includes according to the configuration typethe following options:

– IDU/EXT/8xE1/DS1 Ch#0 with the second group of 8xE1/DS1 trib. to implement the 16xE1/DS1configuration

– IDU/EXT/1xE3/DS3 Ch#0 with the E3/DS3 tributaries 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

156

03

/3DB 06687 CA AA

340

340

2–3.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.

As example in Fig. 87. on page 156 is shown the screen of the MAIN IDU board.

BOARD Status

Fig. 87. Main board 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

157

03

/3DB 06687 CA AA

340

340

2–3.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. 88. on page 157 will appear.

Fig. 88. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

158

03

/3DB 06687 CA AA

340

340

2–3.3 Tab panels in the Resource Detail Area

2–3.3.1 Alarms

The Alarms tab panel provides the fault management, which checks the current state of alarms relatedto the selected object (Fig. 89. on page 158).

Fig. 89. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

159

03

/3DB 06687 CA AA

340

340

2–3.3.2 Configuration

The “User Label” field (Fig. 90. ) 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–2.3.1 on page 124). Toassociate a different Alarm Profile click on the selection button and make the selection among the availableAlarm Profiles.


Fig. 90. Configuration tab panel for a selected object

2–3.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. 91. on page 159):

Fig. 91. Remote Inventory tab panel for a selected object

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

160

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

161

03

/3DB 06687 CA AA

340

340

2–4 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. 92. on page 161):

– 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. 92. Line Interface View

In the Resource List Area is given the information related to the tributaries or to the NMS channels:– Type Interface (E1/DS1 or E3/DS3, Ethernet, NMS 64 kbit/s channel)– Port Number: the port for a given channel and type of port– Channel Number: the number of a channel– Rate/Modulation: the bit rate of the tributary– Signal Mode: the type of frame (Unframed/Framed/Disabled)

To configure a line interface select the interface in the Resource Tree Area and configure the Configurationtab panel in the Resource Detail Area.

N.B. In the Resource Tree Area below the Tributary PDH line are shown all the E1/DS1 tributariesaccording to the capacity selected in the System Setting menu or in Quick Configuration 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

162

03

/3DB 06687 CA AA

340

340

2–4.1 Tab panels in the Resource Detail Area

2–4.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–3.3.1 on page 158.

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–4.1.2 Configuration

There are different tab panels according to the type of interface:

– PDH interface (para. 2–4.1.2.1 on page 162)– NMS interface (para. 2–4.1.2.2 on page 167)– Ethernet interface (para. 2–4.1.2.3 on page 167)

2–4.1.2.1 Tributaries PDH Configuration tab panel

2–4.1.2.1.1 ETSI Market

The window, shown in Fig. 93. on page 162 for E1 tributary and Fig. 94. on page 162 for E3 tributary,performs all the available functions for a PDH tributary port.

Fig. 93. Line Interface View: E1 Tributary Port

Fig. 94. Line Interface View: E3 Tributary Port

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

163

03

/3DB 06687 CA AA

340

340

In Fig. 93. on page 162 and Fig. 94. on page 162 the following fields are read–only fields:

– Interface Type (E1, E3)– Port Number: identifies the ports for a given channel and type of port– Channel Number

The fields, which can be changed, are:

– Signal Mode– Line RAI Insertion– Radio RAI Insertion– Alarm Profile

Signal Mode (for E1 tributary)

The possible values are:

– Framed for the framed received signal– Unframed for the unframed received signal– Disabled

The current state can be modified selecting a different signal mode value and then click on the ”Apply”button to send the new value to NE.

WARNING: In case of the configuration with the two Ethernet ports some E1 ports must be at leastdisabled in order to allow the transmission of the Ethernet data. Refer to the following Table.

Capacity Number of disabled E1 tributaries

2xE1 � 1

4xE1 � 1

8xE1 � 1

16xE1 � 8

Signal Mode (for E3 tributary)


– Framed G.751 for the framed received signal– Framed G.753 for the framed received signal (not applicable)– Unframed for the unframed received signal– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

164

03

/3DB 06687 CA AA

340

340

Line RAI Insertion (for E1 tributary only)

This feature is available for framed signals only.

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

– Forced: the RAI insertion is performed– Enabled: the RAI insertion is possible.


Radio RAI Insertion (for E1 tributary only)

This feature is available for framed signals only.

This field refers to the insertion of the RAI signal in Rx side. The possible alternative values are:

– Forced: the RAI insertion is performed– Enabled: the RAI insertion is possible.


Alarm Profile

The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default alarmprofile or an Alarm Profile previously created by the Operator (refer to para. 2–2.3.1 on page 124). Toassociate a different Alarm Profile click on the selection button and make the selection among the availableAlarm 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

165

03

/3DB 06687 CA AA

340

340

2–4.1.2.1.2 ANSI Market

Note: refer to Tab. 1. on page 14.

The window, shown in Fig. 95. on page 165 for DS1 tributary and Fig. 96. on page 165 for DS3 tributary,performs all the available functions for a tributary port.

Fig. 95. Line Interface View: DS1 Tributary Port

Fig. 96. Line Interface View: DS3 Tributary Port

In Fig. 95. on page 165 and Fig. 96. on page 165 the following fields are read–only fields:

– Interface Type (DS1, DS3)– Port Number: identifies the ports for a given channel and type of port– Channel Number

The fields, which can be changed, are:

– Signal Mode– Line Coding (AMI/B8ZS : for DS1 tributary only)– Line length (0–133, 133–266, 266–399, 399–533, 533–655 : for DS1 tributary only)– Alarm Profile

Signal Mode (for DS1 tributary)


– Framed SF for the Super Framed received signal– Framed ESF for the Extended Super Framed received signal– Unframed for the unframed received signal– 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

166

03

/3DB 06687 CA AA

340

340

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

Capacity Number of disabled DS1 tributaries

4xDS1 � 1

8xDS1 � 1

16xDS1 � 8

Signal Mode (for DS3 tributary)


– Framed for the framed received signal– Unframed for the unframed received signal– Disabled


Line Coding (for DS1 tributary only)

This field refers to the coding relevant to the tributary signal. The possible values are:

– B8ZS– AMI


Line Length (for DS1 tributary only)

This field refers to the length of the connected line. The possible values are:

– 0–133– 133–266– 266–399– 399–533– 533–655


Alarm Profile

The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default alarmprofile or an Alarm Profile previously created by the Operator (refer to para. 2–2.3.1 on page 124). Toassociate a different Alarm Profile click on the selection button and make the selection among the availableAlarm 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

167

03

/3DB 06687 CA AA

340

340

2–4.1.2.2 NMS interfaces Configuration tab panel

Fig. 97. Line Interface View: NMS interface

For the NMS 64 kbit/s channels only the Alarm Profile can be associated.

The field Alarm Profile allows to associate to the interface alarms a particular Alarm Profile: a 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.

N.B. The default associated Alarm Profile is the No Alarm profile.

2–4.1.2.3 Tributaries Data Configuration tab panel

The Ethernet interfaces can be configured according to two different modalities: manual (or default type)mode (auto–negotiation is disabled) or automatic mode (auto–negotiation is enabled). In automatic modea mechanism of auto–sensing (the auto–negotiation) of the parameters involved is activated. Theseparameters are negotiated with the remote Ethernet interface.

The following items resume the features supported:

– the rate (10 or 100 Mb/s) is always configurable independently of the modality (manual or automatic);

– the directionality is always full–duplex (no carrier control mechanism is implemented to usethe half–duplex mode);

– when the auto–negotiation process fails or when the auto–negotiation parameters are changed, theauto–negotiation restart command has to be performed in order to have new configured parameterseffective.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

168

03

/3DB 06687 CA AA

340

340

1 – Configuration menu

Fig. 98. Line Interface View: Ethernet Port

In this menu the Ethernet port can be Enabled or Disabled and the Errored Frames can be discarded inTx side and in Rx side. To each Ethernet port can also be associated an Alarm Profile.

The field Alarm Profile allows to associate to the interface alarms a particular Alarm Profile: a 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.

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

Refer to the following Table.

Market Capacity Number of disabled tributaries

2xE1 � 1

ETSI4xE1 � 1

ETSI8xE1 � 1

16xE1 � 8

ANSI

4xDS1 � 1

ANSI(see Tab. 1. on page 14.)

8xDS1 � 1(see Tab. 1. on page 14.)

16xDS1 � 8

N.B. The default associated Alarm Profile is the No Alarm profile.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

169

03

/3DB 06687 CA AA

340

340

2 – Auto–negotiation

Fig. 99. Line Interface View: Ethernet Port auto–negotiation

In this menu the Auto–negotiation protocol regarding the Ethernet port can be Enabled or Disabled.

To confirm the new configuration click on Apply.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

170

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

171

03

/3DB 06687 CA AA

340

340

2–5 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. 100. on page 171):

– 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. 100. Radio Domain View

Five tab panels are present in the Resource Detail Area:

– Alarms: shows the active alarms (refer to para. 2–5.1 on page 172)– Configuration: configures some radio parameters (refer to para. 2–5.2 on page 172)– Frequency: sets the Tx RF frequency (refer to para. 2–5.3 on page 173)– RTPC & ATPC: sets the manual operation parameters or the automatic operation parameters (refer

to para. 2–5.4 on page 176)– Power Meas: performs the Tx and Rx power measurements (refer to para. 2–5.5 on page 179).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

172

03

/3DB 06687 CA AA

340

340

2–5.1 Alarm

The fault management allows to check the current state of alarms related to the selected object.It is provided by the alarm panel like that shown in para. 2–3.3.1 on page 158.

2–5.2 Configuration

The window shown in Fig. 101. on page 172 performs all the available functions for a Radio channel.To define the involved port, first select the port/channel in the tabular view: this selection enables the“Resource Detail list” to show the available functions for the single resource.

Fig. 101. Radio Configuration menu

2–5.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–5.2.2 ODU service kit

This field is a read–only field, which displays the state of the Portable Service Kit (connected or not to theODU).

2–5.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–2.3.1 on page 124). Toassociate a different Alarm Profile click on the selection button and select among the available AlarmProfile.


All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

173

03

/3DB 06687 CA AA

340

340

2–5.3 Frequency

– For SWP version = 2.0.0, refer to para.2–5.3.1 below– For SWP version > 2.0.0, refer to para.2–5.3.2 on page 174

2–5.3.1 Frequency menu in Rel. 2.0.0

This menu (Fig. 102. on page 173) allows to read and, if necessary, to set the frequency parameters.The information shown concerns the port/channel selected in the Resource Tabular View.

Fig. 102. Radio Frequency menu in Rel. 2.0.0

2–5.3.1.1 Tx Radio Frequency

The ”Tx Freq” field in the “Frequency Value” area of tabbed window (Fig. 102. on page 173) shows thecurrent value of the transmission radio frequency (expressed in kHz). To change this parameter write thenew value in the field and press the ”Apply” button.The new value must be within the allowed radio frequency range. The allowed range is shown in “Min/MaxValue” fields.

N.B. During the command setting the CT is frozen. Waiting time: max. 30’.

2–5.3.1.2 Rx Radio Frequency

The ”Rx Freq” field in the “Frequency Value” area of the tabbed window (Fig. 102. on page 173) showsthe current value of the receive radio frequency (expressed in kHz).It is automatically changed as a consequence of the definition of the Tx frequency according to theFrequency Shifter.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

174

03

/3DB 06687 CA AA

340

340

2–5.3.2 Frequency menu from Rel. 2.0.1

This menu (Fig. 103. on page 174) allows to read and, if necessary, to set the frequency parameters.

Fig. 103. Radio Frequency menu from Rel. 2.0.1

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).

2–5.3.2.1 ODU with one Shifter only

If the ODU can manage only one shifter the Shifter field in the menu is not available (it is grey).

In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written in the FrequencyRange field on the right side) and press push–button Apply (the Rx frequency is automatically calculatedby using the inserted Tx frequency and the shifter).

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

175

03

/3DB 06687 CA AA

340

340

2–5.3.2.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 new value(± 5 MHz respect to the value previously automatically calculated) in the Rx frequency field and presspush–button Apply.

WARNING: The Rx frequency must be ± 5 MHz respect to the value automatically calculated accordingto the Tx frequency and to the shifter.

When the Rx frequency is changed a specific warning message about possible impact on the traffic willappear. This message requires an explicit confirmation to proceed.

At the end a specific result message appears to inform the operator that the operation has been completed(or failed in case of failure).

At this point other operations can be normally requested by the operator.

WARNING: Whenever the difference (as absolute value) between Rx and Tx frequencies is differentfrom the shifter value, the background of the Shifter field changes to red color and aspecific warning message is written on the Frequency screen as shown in Fig. 104. :“WARNING: Frequency parameters are not aligned to standard configurationassociated to the selected Shifter.For more information, refer to technical handbook” (N.B.)N.B. Information present from Ed.02 of Technical Handbook.

Fig. 104. Not standard frequency arrangement

To restore a “Standard Shifter” configuration, the operator has only to apply again the selected (or anotherone) Shifter value or to apply again the Tx frequency.

As result, the normal Frequency screen is restored removing both red color as background of the Shifterfield 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

176

03

/3DB 06687 CA AA

340

340

2–5.4 RTPC & ATPC

This menu (Fig. 105. on page 176) allows to read and, if necessary, to set the Tx power parameters.

The shown information is related to the channel selected in the Resource Tabular View.

Static value of the Tx power(30 dB range)

Dynamic value of the Tx power(20 dB range)

ATPC Rx Threshold

Fig. 105. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

177

03

/3DB 06687 CA AA

340

340

2–5.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 (HST 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 level can be changed by writing the new value in the field.

When the Apply button is pressed the new values will be applied.

[2] ATPC Rx Threshold

The value of the power low threshold can be changed by writing the new value in the field.When the Apply button is pressed the new values will be applied.

WARNING: During the reconfiguration phase or during the activation of a new software the alarm“ATPC loop” is active.

It is recommended to use the following Tab. 4. (for ETSI) and Tab. 5. (for ANSI) in order toset the ATPC threshold. The ATPC shape is calculated using the following max capacity:• E3 for ETSI• DS3 for ANSI

Tab. 4. ATPC Range Rx Threshold for ETSI

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

4

MinValue

–73 –74 –74 –72 –72 –71 –71 –704

QAM MaxValue

–60 –60 –60 –60 –55 –50 –50 –50

16

MinValue

–69 –70 –70 –68 –68 –67 –67 –6616

QAM MaxValue

–60 –60 –60 –60 –55 –50 –50 –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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

178

03

/3DB 06687 CA AA

340

340

Tab. 5. ATPC Range Rx Threshold for ANSI

TH15

GHz18

GHz23

GHz38

GHz

4

MinValue

–72 –70 –70 –664

QAM MaxValue

–60 –60 –55 –50

16

MinValue

–68 –66 –66 –6216

QAM MaxValue

–60 –59 –55 –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/FCC standard

2–5.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

179

03

/3DB 06687 CA AA

340

340

2–5.5 Power Measurement

The Power Measurements capability is performed through the “Power Meas” tabbed panel in the resourcedetail view (Fig. 106. on page 179).

Fig. 106. 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 among2, 6, 30, 60 sec.

The last section of the dialog is referred to an optional Log file.

By selecting Create File the log file is created and a default path and name for this file is displayed to theoperator. The file is stored in the ALCATEL/CT–Kv3.0.1 directory.

N.B. The file name must not include the following characters: \ ? : * “ < > |.

The log file contains the sample value and records the measurement up to a maximum dimension ( 7 daysfor a 2 s sample time).

By clicking on the ”Start“ button the screen “ Power Measurement Graphic “ appears (see Fig. 106. onpage 179).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

180

03

/3DB 06687 CA AA

340

340

The Power Measurement Graphic is available only if the CT is connected to the NE.

The screen in Fig. 107. 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).

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. 107. Power Measurement Graphic

By clicking on “Show details” box, on the left side of the Power Measurement Graphic (see Fig. 107. onpage 180), a new table appears (Fig. 108. on page 181); 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

181

03

/3DB 06687 CA AA

340

340

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

– Rx Local End• max Rx local value and date when this value was received for the first time.• min. Rx local value and its current date when this value was received for the first time.• current Rx local value and its current date.

– Rx Far End• max Rx remote value and date when this value was received for the first time.• min. Rx remote value and its current date when this value was received for the first time.• current Rx remote value and its current date.

N.B. PTx and PRx levels software readings tolerance is:– PTx = Real Value ± 3dB– PRx = Real Value ± 5dB

Fig. 108. Power Meas Details

WARNING:– If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HST Configuration the

transmitter is in standby).– If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field

the information in dBm is –99, probably the supervision has been lost. The confirmation of the 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

182

03

/3DB 06687 CA AA

340

340

2–5.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.0.1 directory and haveextension .txt.

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

Select the desired file and click the Start button in Fig. 106. on page 179 to open the file.

Fig. 110. Example of “Power Measurement File Reading“

The button in the lower part of the window allow to flow the graph within the measurement 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

183

03

/3DB 06687 CA AA

340

340

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. 111. on page 183).

Fig. 111. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

184

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

185

03

/3DB 06687 CA AA

340

340

2–6 EXTERNAL POINTS

This chapter describes the types of functions offered to the user for External Points Management.There are two types of external points: input and output external points.

By clicking on the tree root, displayed in Fig. 112. on page 185, 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. 112. on page 185.

2–6.1 Input External Points

An input external point is described by the following parameters (Fig. 112. on page 185):

– 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. 112. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

186

03

/3DB 06687 CA AA

340

340

2–6.2 Output External Points

Seven output external points are available:

The first four external points (CPO#1, 2, 3, 4) (Fig. 113. on page 186) 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. 113. on page 186) or automatically by selecting Automatic (Fig. 114. on page 187). In this casea new field appears (Event) in which it is possible to select the alarm, the generation of which willcause the 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. 113. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

187

03

/3DB 06687 CA AA

340

340

Fig. 114. Output External Points: CP01 ... CP04 (Automatic activation)

The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) (Fig. 115. on page 188)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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

188

03

/3DB 06687 CA AA

340

340

Fig. 115. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

189

03

/3DB 06687 CA AA

340

340

2–7 SUPERVISION

2–7.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:

2–7.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. 116. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

190

03

/3DB 06687 CA AA

340

340

2–7.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–7.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. 117. Restart NE call

The following dialogue box opens.

Fig. 118. 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 remoteNEs 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

191

03

/3DB 06687 CA AA

340

340

2–7.3 MIB Management

This menu (Fig. 119. on page 191) refers to the management of the MIB (Management Information Base).The MIB includes all the system configuration data, except the routing configuration data:

1. Local configuration ⇒ System’s local address

2. NTP server configuration

3. Interface configuration ⇒ NMS configuration⇒ Ethernet configuration

4. IP configuration ⇒ IP Static Routing configuration⇒ OSPF Area configuration⇒ IP Address configuration of point to point configuration

Fig. 119. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

192

03

/3DB 06687 CA AA

340

340

2–7.3.1 Backup

This menu (Fig. 120. on page 192) allows to save on the CT the NE configuration. To backup theconfiguration write the filename in the Backup field (Lower part) and press Confirm Backup.

WARNING: The backup file name must not include the following characters: space, &, /.

Fig. 120. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

193

03

/3DB 06687 CA AA

340

340

2–7.3.2 Restore

This menu (Fig. 121. on page 193) allows to download to the NE a previously created backup.

Fig. 121. 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–7.3.3 Activate

This command (Fig. 122. on page 193) allows to activate the configuration just downloaded with therestore.

Fig. 122. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

194

03

/3DB 06687 CA AA

340

340

2–7.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–7.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. 123. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

195

03

/3DB 06687 CA AA

340

340

2–8 PROTECTION SCHEMES

This domain is present in 1+1 configuration only.


– Resource Tree Area: displays the radio ports sorted by channel number.

– Resource List Area: displays tabular information about the selected resource in tree area.

– Resource Detail Area: displays, through tabbed windows, the properties done in list area. This areaenable to perform the available functions for involved resource.

By clicking on the tree root displayed in Fig. 124. on page 195, the tree will be expanded according toprotection schemes supported.

Fig. 124. 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 thefollowing figure (Fig. 125. on page 196).

Three 1+1 protection schemes have been implemented:

– Mux/Demux protection: EPS protection in Tx and Rx sides– Radio protection: RPS Hitless Switch in Rx side– HST protection: Hot Stand–by protection

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

196

03

/3DB 06687 CA AA

340

340

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

– Mux/Demux protection corresponds to the Switch Tx and the Rx output switch in Fig. 149. on page220 or Fig. 151. on page 221

– The Radio protection corresponds to the Switch RPS HS in Fig. 149. on page 220 or Fig. 151. onpage 221

– The HST protection is implemented in the ODU: one Transmitter is connected to the antenna(active), the other transmitter is in stand–by. Refer to Fig. 149. on page 220. The HST protectionis available only if the HST configuration has been selected.

2–8.1 Mux/Demux Protection Management

The Equipment Protection Management is performed by selecting Mux/Demux Protection tree element.

The following window (Fig. 125. on page 196) allows a complete view of all Ne resource involved in theEPS protection:

– Schema Parameters

– Channels Parameters

To read the correct indication on the switch status press here to refreshthe screen

Fig. 125. Mux Protection

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

197

03

/3DB 06687 CA AA

340

340

2–8.1.1 Schema Parameters

The window “Schema Parameters” displays the parameters that can be modify.

The Schema parameters are:

– Protection Type: this parameter is defined at creation time and it is read only. The supported 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).

The operator choice for “Operation Type” will be applied by clicking on “Apply” button.

2–8.1.2 Commands

To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 126. on page 197)or on the Main #1 element (Fig. 127. on page 198).

Fig. 126. Mux Protection Switch (Spare #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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

198

03

/3DB 06687 CA AA

340

340

Fig. 127. Mux Protection Switch (Main #1)

The operator by the Craft Terminal can modify the state of the switch through commands Lockout, Forcedand Manual.

Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel),independently of the possible active alarms. This command activates signaling ABN.

Forced has higher priority than the automatic operation: the activation of this command forces in serviceChannel 0, independently of the possible active alarms. This command activates signaling ABN.

Automatic Switch is the normal operation condition: the position of the switch depends on the commandsgenerated by the logic.

Manual has the lowest priority: it is performed only if there are no alarms that can activate an automaticswitch. It cannot be performed if Lockout or Forced commands are already activated. If this command isactive, it will be removed by an incoming alarm. This command does not activate signaling ABN.

Tab. 6. Command priority list

Command Priority

Lockout 1

Forced 2

Automatic switch 3

Manual 4

N.B. to release a previously activated command select None and click on Apply.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

199

03

/3DB 06687 CA AA

340

340

2–8.2 Radio Protection Management

The Radio Protection Management is performed by selecting the Radio Protection element tree.

The following window (Fig. 128. on page 199) allows a complete view of all Ne resource involved in a RPSprotection:

– Rx Static Delay




Fig. 128. Radio Protection 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

200

03

/3DB 06687 CA AA

340

340

2–8.2.1 Rx Static Delay

Fig. 129. Rx Static Delay menu

The Rx Static Delay must be compensated during the installation.

Two compensating modes are possible:

– Automatic

– Manual

The two modes are alternative.

To activate the Automatic mode click on the Align push–button (the compensation procedure 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.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

201

03

/3DB 06687 CA AA

340

340



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).

2–8.2.3 Commands

To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 130. on page 201)or on the Main #1 element (Fig. 131. on page 202).

Fig. 130. Radio Protection Switch (Spare #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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

202

03

/3DB 06687 CA AA

340

340

Fig. 131. Radio Protection Switch (Main #1)


Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel),independently of the possible active alarms. This command activates signaling ABN.

Forced has higher priority than the automatic operation: the activation of this command forces in serviceChannel 0, independently of the possible active alarms. This command activates signaling ABN.




Command Priority

Lockout 1

Forced 2

Automatic switch 3

Manual 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

203

03

/3DB 06687 CA AA

340

340

2–8.3 HST Transmission Protection Management

The Transmission Protection Management is performed selecting Transmission Protection element tree.

The following windows (Fig. 132. on page 203) allows a complete view of all Ne resource involved in aTPS protection:




Fig. 132. Transmission Protection View



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).

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

204

03

/3DB 06687 CA AA

340

340

2–8.3.2 Commands

To enter the Commands menu click on the Spare #0 element (Fig. 133. on page 204) or on the Main #1element (Fig. 134. on page 205) in the Tree view.

Fig. 133. Tx Protection Commands (Spare #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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

205

03

/3DB 06687 CA AA

340

340

Fig. 134. Tx Protection Commands (Main #1)


Lockout has higher priority than Forced: the activation connects to the antenna Transmitter 1 (defaulttransmitter), independently of the possible active alarms. This command activates signaling ABN.

Forced has higher priority than the automatic operation: the activation of this command connects to theantenna Transmitter 0, independently of the possible active alarms. This command activates signalingABN.




Command Priority

Lockout 1

Forced 2

Automatic switch 3

Manual 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

206

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

207

03

/3DB 06687 CA AA

340

340

2–9 LOOPBACKS

The functions described in this section allow to perform the test operations.

This domain view consists of the following areas:

– Resource Tree Area: displays the object on which the loopbacks can be performed, sorted 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 areaenable to perform the available functions for involved resource.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

208

03

/3DB 06687 CA AA

340

340

2–9.1 Available Loopbacks

2–9.1.1 1+0 Loopbacks

N.B. The loopbacks can be activated on the local NE only.

N.B. The DATA block in Fig. 135. 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. 135. 1+0 available loopbacks

Tab. 9. 1+0 loopbacks

No.Loopback name

CT selection inthe Resource

Tree Area

Ref. toFig.

LocationLoopback

typeNote

1E1/DS1

Port#xx orE3/DS3

Tributaries Fig. 138. Near End External line Input loopback at tributary level.

2E1/DS1

Port#xx orE3/DS3

Tributaries Fig. 138. Near End InternalLoopback toward the remotestation at tributary level. Not available.

3E1/DS1

Port#xx orE3/DS3

Tributaries Fig. 138. Far End InternalLoopback in the remote stationat tributary level.

4 IDU cable Channel 1 Fig. 138. Near End External lineLoopback at the IDU output ataggregate level.

5ODUcable

Channel 1 Fig. 138. Near End External lineLoopback at the ODU input ataggregate level.

6 RF Channel 1 Fig. 138. Near End External lineRF local loopback.(Note 1)

Note 1: Before activating this loopback the Remote Tx must be muted (Menu Radio –> Configuration)

Note 2: For the DS1/DS3 tributaries refer to Tab. 1. on page 14.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

209

03

/3DB 06687 CA AA

340

340

Fig. 136. Channel 1 Loopback View

Fig. 137. Tributaries Loopback 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

210

03

/3DB 06687 CA AA

340

340

In the Resource List Area are listed all the loopbacks which can be performed.

In this area the following information is given:

– Channel: the number of the channel (channel 1 only)

– Type Interface: the type of interface in which a loopback can be performed.

– Location: the station in which the loopback is performed (Near End/Far End)

– Type: the type of the loopback (Internal/Internal IF/External Line)

– Modality: the type of the loopback (Loop and Continue only)

– Activation: the activation status of a loopback (Active/Not Active)

In Fig. 138. on page 210 is given the association of all the possible loopbacks and their positions in theblock diagram of the equipment provided by the Summary Block Diagram View option, available in theDiagnosis menu.

Tributaries(External Line)

ODUCABLE

Radioport

(RF loop)

IDUCABLE

Channel(External Line)

1

2

5 6

4

Fig. 138. 1+0 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

211

03

/3DB 06687 CA AA

340

340

2–9.1.2 1+1 Loopbacks

N.B. The loopbacks can be activated on the local NE only.

N.B. The DATA block in Fig. 139. 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. 139. 1+1 available loopbacks

Tab. 10. 1+1 loopbacks

No.Loopback name

CT selection inthe Resource

Tree Area

Ref. toFig.

LocationLoopback

typeNote

1E1/DS1

Port#xx orE3/DS3

Tributaries Fig. 142. Near End External line Input loopback at tributary level.

2E1/DS1

Port#xx orE3/DS3

Tributaries Fig. 142. Near End InternalLoopback toward the remotestation at tributary level. Not available.

3E1/DS1

Port#xx orE3/DS3

Tributaries Fig. 142. Far End InternalLoopback in the remote stationat tributary level.

4 IDU cable Channel 0 or 1 Fig. 142. Near End External lineLoopback at the IDU output ataggregate level.

5ODUcable

Channel 0 or 1 Fig. 142. Near End External lineLoopback at the ODU input ataggregate level.

6 RF Channel 0 or 1 Fig. 142. Near End External lineRF local loopback.(Note 1)

Note 1: Before activating this loopback the Remote Tx must be muted (Menu Radio –> Configuration).

Note 2: For the DS1/DS3 tributaries refer to Tab. 1. on page 14.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

212

03

/3DB 06687 CA AA

340

340

Fig. 140. Channel 1 Loopback View

Fig. 141. Tributaries Loopback 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

213

03

/3DB 06687 CA AA

340

340

In the Resource List Area are listed all the loopbacks which can be performed.

In this area the following information is given:

– Channel: the number of the channel (channel 1 only)

– Type Interface: the type of interface in which a loopback can be performed.

– Location: the station in which the loopback is performed (Near End/Far End)

– Type: the type of the loopback (Internal/Internal IF/External Line)

– Modality: the type of the loopback (Loop and Continue only)

– Activation: the activation status of a loopback (Active/Not Active)

In Fig. 142. on page 213 is given the association of all the possible loopbacks and their positions in theblock diagram of the equipment provided by the Summary Block Diagram View option, available in theDiagnosis menu.

Tributaries(External Line)

Radio port(RF loop)

IDUCABLE

Channel(External Line)

ODUCABLE

1

2

5 64

Fig. 142. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

214

03

/3DB 06687 CA AA

340

340

2–9.2 How to activate a loopback

N.B. For the loopbacks relevant to Ch. 0 and Ch.1 all the switches must be forced/lockout to 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. 143. on page 214 will appear. (In this screen has been selected the loopback ontributary E1, Near End).

Fig. 143. 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 set another commandis 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

215

03

/3DB 06687 CA AA

340

340

2–9.3 How to remove a loopback

To deactivate loopbacks use the following steps:

[1] Select the suitable loopback to be removed by clicking on the relevant object in the Resource TreeArea or by selecting the relevant row in the Resource List Area.

[2] The screen in Fig. 144. on page 215 will appear. (In this screen has been selected the loopback ontributary E1, Near End).

Fig. 144. 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 set another commandis 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

216

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

217

03

/3DB 06687 CA AA

340

340

2–10 DIAGNOSIS

In the Diagnosis menu four options are available as shown in Fig. 145.

Fig. 145. Diagnosis menu

2–10.1 Log Browsing

In the Diagnosis pull–down menu, select the Log Browsing option.

The proposed options:

– Select the Alarm Log option to access the Alarm Log file.

The Alarm Log windows opens, permitting to analyze all the alarms stored in the NE.Refer to the “ELB Operator’s Handbook”.

– Select the Event Log option to access the Event Log file.

The Event Log windows opens, permitting to analyze all the events stored in the NE.Refer to the “ELB Operator’s Handbook”.

– Software Trace Log option is reserved to the Alcatel technicians.

2–10.2 Remote Inventory

This screen is a read–only screen, which shows all the information on the equipment.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

218

03

/3DB 06687 CA AA

340

340

2–10.3 Abnormal Condition List

The Abnormal Condition List option in the Diagnosis menu displays all the abnormal conditions (i.e.the manual operations) currently active in the NE.

The abnormal conditions can be:

– Switch commands Forced or Lockout– Loopback– Tx power manual operation– Tx muting (manual or automatic)– ODU service kit connected

2–10.4 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).

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 (see Fig. 146. on page 219, Fig. 147. on page 219)– 1+1 HST with or without the Ethernet ports (see Fig. 148. on page 220, Fig. 149. on page 220)– 1+1 FD with or without the Ethernet ports (see Fig. 150. on page 221, Fig. 151. on page 221)

In detail, it is possible to:

– navigate from Alarm indicator to related “Alarm Synthesis”;– navigate from External Point indicator to “External Point” view;– navigate from Switch indicator to related “Protection Scheme” view;– navigate from Loopback indicator to specific “Loopback” view; for example, by clicking on (L)

indicator of main board (Ch#1) the operator can navigate to loopback view for PDH tributaries;– navigate from Performance indicator to specific “Performance” view; for example, by clicking on

(P) indicator (line side) the operator can navigate to “Current Data” view;– navigate from ODU box to the ”radio view” with automatic selection of the related channel.

To refresh the screen press the Refresh button.

N.B.• Loopback indicator: yellow letter L means active loop.• Performance indicator: yellow letter P means active performance.

N.B. In the 1+1 configuration the current position of the switches is also shown.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

219

03

/3DB 06687 CA AA

340

340

Fig. 146. Summary Block Diagram View: 1+0 without Ethernet ports

Fig. 147. Summary Block Diagram View: 1+0 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

220

03

/3DB 06687 CA AA

340

340

Fig. 148. Summary Block Diagram View: 1+1 HST without Ethernet ports

Fig. 149. Summary Block Diagram View: 1+1 HST 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

221

03

/3DB 06687 CA AA

340

340

Fig. 150. Summary Block Diagram View: 1+1 FD without Ethernet ports

Fig. 151. Summary Block Diagram View: 1+1 FD 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

222

03

/3DB 06687 CA AA

340

340

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

2–10.5 Current Configuration View

This screen is a read–only screen, which shows the current configuration of the 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

223

03

/3DB 06687 CA AA

340

340

2–11 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–11.1 General information on the performance monitoring process

The performance monitoring (PM) gives indication on the quality of the service.Quality of service PM is performed in accordance with G.826 and G.784.It is assumed that the quality of the single tributary (E1, DS1, …) can be derived from the quality of theaggregate signal, therefore no dedicated quality of service PM is foreseen on the single tributaries.Considering one section (see below), one current register is for 15 min report and one for 24 h report; 96history data can be stored for 15 min report and 8 history data for 24 h report.

N.B. The 15 min Performance Monitoring data are stored in the History Data report only if errorshave been occurred.The 24 h Performance Monitoring data are always stored in the History Data report.

The radio section monitored is:

– Radio Hop Section: the section between two radio stations inside the protection section– Radio Link Section: the section identifying the protected section.

MODEMRF

MODEMRF

FECDECODE

PROPR.FRAMING

PROPR.FRAMING

FECENCODE

Radio Hop (before the switch)

Radio Link (after the switch)

Fig. 152. Radio sections

The counters supported are the following:

– Errored Seconds– Severely Errored Seconds– Background Block Error– Unavailable Seconds

The primitives used for the hop section quality monitoring is the Reed–Solomon (RS) decoder (block size:2040 bits). The following table provides, for each frame structure, the main features useful to define a SES.

Tab. 11. SES Thresholds

E3 16E1 8E1 4E1 2E1 DS3 16DS1 8DS1 4DS1

Gross bit rate [MHz] 39,168 39,168 19,584 9,792 4,896 57,120 28,560 14,280 7,140

RS Blocks number/sec. 19200 19200 9600 4800 2400 28000 14000 7000 3500

SES Threshold (Note 1) 5760 5760 2880 1440 720 8400 4200 2100 1050

(Note 1) Note that according to ITU–T G.826 a second is declared Severely Errored Second if it is asecond period with more than 30 % of errored blocks or at least one defect.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

224

03

/3DB 06687 CA AA

340

340

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

T1313790–98

Monitoredsecond

YesDefects?

No

Anomalies?

N

%EB≥ 30?

ES(but not a SES)

Path inavailable

State?

cES = cES + 1

Path inavailable

State?

cBBE = cBBE + EB(s) cSES = cSES + 1

End

cES = cES + 1

SES(and therefore an ES)

No

Yes

Yes

No

No

Yes Yes

Fig. 153. Anomalies, defects, errored blocks, ES and SES according to ITU–T G.826

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

225

03

/3DB 06687 CA AA

340

340

2–11.2 Performance menu

The performance view allows the user to activate and monitor the PM process on the selected object.


– Resource Tree Area: displays the threshold for measurement and the object monitoring sorted bychannel number.

– Resource List Area: displays the PM management for the selected resource in the tree area.

Fig. 154. Performance View

The performance reports can be of 2 different types:

– 15 minutes

– 24 hours

The following description explains the functions to provide the PM process with a granularity period of 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

226

03

/3DB 06687 CA AA

340

340

With reference to Fig. 155. on page 226 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. 155. on page 226 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. 155.

Fig. 155. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

227

03

/3DB 06687 CA AA

340

340

2–11.3 CD (Current Data)

The window displayed in Fig. 156. on page 227 allows to start and to read the 15min PM report and 24hPM report.

Fig. 156. Current Data 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

228

03

/3DB 06687 CA AA

340

340

2–11.3.1 CD parameters

The fields displayed in the upper part of Fig. 156. on page 227 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.

2–11.3.2 CD Counters

The fields and buttons displayed in the lower part of Fig. 156. on page 227 (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. 156. on page 227, 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

229

03

/3DB 06687 CA AA

340

340

2–11.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–11.4.1 HD Parameters

The table displayed on the following window (Fig. 157. on page 229) collects the history data for a relatedPM report.

Fig. 157. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

230

03

/3DB 06687 CA AA

340

340

2–11.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–11.5.3 “Threshold tableassociation”.

2–11.5.1 How to change a threshold table

Fig. 158. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

231

03

/3DB 06687 CA AA

340

340

2–11.5.2 How to create a threshold table

Fig. 159. 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–11.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

232

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

233

03

/3DB 06687 CA AA

340

340

2–12 SW DOWNLOAD

2–12.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 shown in para. 1–3.3 on page 68.

Fig. 160. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

234

03

/3DB 06687 CA AA

340

340

2–12.2 Init SW Download

N.B. The first part of the procedure to download the SW to the NE is shown in para. 1–3.3 on page68.

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. 161. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

235

03

/3DB 06687 CA AA

340

340

2–12.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. 162. on page 235 opens, givingadditional information on the software package.

Fig. 162. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

236

03

/3DB 06687 CA AA

340

340

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)

– FFENI, FGAIA, FGAEX, FMEDU, FPONT: FPGA firmware version (Note 1)

Note 1: during the download of the ODU and FPGA software arises the alarm “Firmware Download OnGoing”. This alarm disappears when the download is over. The download lasts 2 minutes forevery FPGA starting from the activation of the alarm.

Fig. 163. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

237

03

/3DB 06687 CA AA

340

340

2–13 MIB MANAGEMENT

2–13.1 Introduction

This function allows the backup and/or restore of the MIB and is carried out at two levels:

– the first is available at NE logged–in level, and allows operations depicted in Fig. 164. 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. 164. Allowed MIB management tasks at “NE logged–in” level

From operative point of view, this management is described in para.2–7.3 on page 191.

– the second is available at “Network Element Synthesis level” (independently of whether or not theNE is logged in), and allows operations shown in Fig. 165. 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. 165. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

238

03

/3DB 06687 CA AA

340

340

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

2–13.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–7.3.1 on page 192).

2–13.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. 166. 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. 167. MIB save to disk – phase 1

3 ) The following screen appears:

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

239

03

/3DB 06687 CA AA

340

340

– a table showing the MIBs stored in the PC directory is shown– 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. 168. 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. 169. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

240

03

/3DB 06687 CA AA

340

340

2–13.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. 170. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

241

03

/3DB 06687 CA AA

340

340

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. 171. MIB load from disk – phase 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

242

03

/3DB 06687 CA AA

340

340

3 ) ... procedure continues– 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. 172. MIB load from disk – phase 2

2–13.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–7.3.2 on page 193).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

243

03

/3DB 06687 CA AA

340

340

SECTION 3: NE MAINTENANCE


Chapter 3–1 – Troubleshooting 245

Chapter 3–2 – Spare Flash Card management and replacement proceduresThis chapter describes how to manage the spare Flash Card and how to replace it,in case of problems.

263

The symbol points out references to the other Handbooks.

Referenced handbook P/Ns are given in para.D.2 on page 327 of this 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

244

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

245

03

/3DB 06687 CA AA

340

340

3–1 TROUBLESHOOTING

3–1.1 Purpose of this procedure

This section is the 9400AWY Maintenance Manual; it describes mainly the NE troubleshooting based onthe use of the Craft Terminal.

It applies to 9400AWY SWP Rel.2.0.

The document that should be read before starting this document is:

– 9400AWY Rel.2.0 Technical Handbook

N.B. In particular, knowing the contents of section “MAINTENANCE” of Technical Handbook isa must.

– 1320CT Basic Operator’s Handbook V.3.x (see Tab. 31. on page 329)

Troubleshooting involves detection, location and correction of the failures occurred in the equipment andreplacement of the defective parts.

This chapter is organized as follows:

– Corrective Maintenance general flow–chart on page 246

– Troubleshooting organization on page 247

– Troubleshooting by means of the Craft Terminal on page 249• Alarm synthesis indication on page 250• Details on alarms / statuses on page 251

– Warnings on the troubleshooting on page 253• Problems with the Craft Terminal on page 253

– PC restart– Craft Terminal not working– Craft Terminal blocked

• Analog measurements on page 255• NMS 64 kbit/s V.11 and G.703• Loopbacks• Empty USM icon in NES• NE unreachable on page 256• Configuration change from 4 QAM to 16 QAM• Quick configuration menu correct use• Abnormal condition list on page 257• Tx Mute functionality for interferences investigation on page 258• Tributaries 9 to 16 visible in “8E1/DS1_Ethernet” configuration on page 259

– Description of alarms and of probable causes on page 260

– Unit replacement on page 261

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

246

03

/3DB 06687 CA AA

340

340

3–1.2 Corrective Maintenance general flow–chartAs depicted in Fig. 173. herebelow, troubleshooting via Craft Terminal is just a step inside the CorrectiveMaintenance process.

Trouble–Shooting via Craft Terminal.Identification of a unit to be replaced.

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 togetherwith Repair Form compiled (para......)

START

END

Restore spare part in the system andperform system check via Craft Terminal

Y

Unit replacement (para 3–1.7 on page 261)

System check via Craft Terminal

Alarm acknowledgment and attending (para...)

Trouble–Shooting starting with visual indications (para......)

Fig. 173. Corrective Maintenance general flow–chart

For detailed information regarding the whole Corrective Maintenance procedure, please refer to:

9400AWY Technical Handbooks, section MAINTENANCEchapter SECOND LEVEL MAINTENANCE, paragraph CORRECTIVE 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

247

03

/3DB 06687 CA AA

340

340

3–1.3 Troubleshooting organization

The troubleshooting procedure is carried out with the help of some tables, reported hereinafter. Anywaythis method does not deal with the following issues (which are to be dealt with otherwise):

– faulty electronic alarm indication, processing and detection circuits

– faulty wiring (back–panel, connectors, etc.)

The following interfaces are present on the equipment for troubleshooting purposes:

• Ethernet interface for the Telecommunication Management Network ( TMN )

• F interface for the Craft Terminal (Local or Remote)

• LEDs located on the NE’s units.

Usually, maintenance is firstly done via software (TMN or Remote Craft Terminal) to locate the faultyequipment and the faulty unit or the faulty path and then on site to physically correct the trouble.

Maintenance can be done:

• from a TMN network management center

• from a Remote Craft Terminal (RCT) management center

• on site.

TMN network management center: by means of the TMN, the maintenance technician can see thealarms generated by each equipment of the managed network (see the relevant TMN handbooks).

Remote craft terminal: the operator, connected to a local NE, can remotely manage and troubleshoota network composed of max 128 NEs, including itself. This handbook applies.

On site : the operator is on site in case :

1 ) the equipment is not managed by a TMN or by a Remote Craft terminal (RCT).

2 ) the equipment is not reachable by the remote manager (TMN or RCT) and therefore is isolated.

3 ) link problems are present.

4 ) the trouble has been located and a physical replacement is necessary.

In cases 1 ) , 2 ), 3 ), the alarmed equipment is checked by means of the local Craft Terminal.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

248

03

/3DB 06687 CA AA

340

340

The NE is provided with LEDs which indicate:

Centralized Equipment Alarms:

All alarms detected on the units are collected by the MAIN unit, which delivers centralized indications (bymeans of LEDs on the front coverplate). Specifically:

• Red LED: detection of a MAJOR (URGENT) alarm.

• Red LED: detection of a MINOR (NOT URGENT) alarm.

• Yellow LED: alarm condition ATTENDED.

• Red LED: detection of a LDI (problem in the local equipment).

• Red LED: detection of an RDI (problem in the remote equipment).

In the case of a MAJOR or MINOR alarm, after locating the alarmed unit, the alarm condition can be”attended” by pressing the alarm storing push button on the front panel of the 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.

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 on the front coverplate (F interface) of the MAINunit.

The Craft Terminal applications provide detailed information on the alarm state thus facilitating faultlocation and subsequent removal as indicated in para. 3–1.4 on page 249.

To correctly execute the troubleshooting operations the technician must know the equipmentconfiguration (see Equipment applications on the Craft Terminal).

The following tables should be also consulted when the unit LEDs flash; as a matter of fact, the flashingcondition might be due to external alarm causes usually, related to line 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

249

03

/3DB 06687 CA AA

340

340

3–1.4 Troubleshooting by means of the Craft Terminal

Troubleshooting proceeds by checking the detailed information on the NE alarm by using the CraftTerminal.

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. 12. on page 250 describes the meanings of these alarms/statuses and itsrespective maintenance actions.

b ) In case of alarm, access the Alarm tab panel for troubleshooting.Para 3–1.4.2 on page 251 explains how to see the alarms.

MAJOR alarm indicates a severe alarm that could affect the current traffic (interrupt or degrade). Hence, a prompt intervention is necessary to restore the regular operating condition of the equipment.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

250

03

/3DB 06687 CA AA

340

340

3–1.4.1 Alarm synthesis indication

The following troubleshooting table pertains to the alarm and status synthesis given in all the screens.

Tab. 12. Alarm Synthesis indication

Mnemonic Alarm / Status Description Maintenance

CRI Critical alarmSynthesis of alarms that needs immediatetroubleshooting (typical: NE isolation). NB1.

MAJ Major (Urgent) alarmSynthesis of alarms that needs immediate

MAJ Major (Urgent) alarmSynthesis of alarms that needs immediatetroubleshooting. NB1.

MIN Minor (Not urgent) alarmSynthesis of alarms for which a deferred interventioncan be decided. NB1.

WNG Warning alarmSynthesis of alarms due to failure of other NE in thenetwork. NB1.

IND Indeterminate alarmSynthesis of alarms not associated with the previousseverities. Not operative.

EXTPExternal Point(Housekeeping alarm)

Check the relevant station alarm associated with theinput housekeeping indication.

EQP Equipment alarm Synthesis of alarms of the Equipment domain.

TRNS Transmission alarm Synthesis of alarms of the Transmission domain.

SUP Supervision stateGREEN LED: NE is under supervision.BROWN LED: NE is not under supervision.Used in the OS.

Local Access state

GREEN LED: Indicates that the Craft Terminal 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 ).

AC Abnormal ConditionGREEN LED: Normal operating condition.CYAN LED: Detection of an ABNORMAL operativecondition. Type: switch forcing.

ALI AlignmentAlignment status of the SH MIB respect to theequipment MIB.

NB1: 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

251

03

/3DB 06687 CA AA

340

340

3–1.4.2 Details on alarms / statuses

The troubleshooting proceed by checking the detailed information on the NE alarm by using the CraftTerminal.

To display the active alarms (refer to Fig. 174. on page 251):

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. 174. Active alarm screen

Detailed information of some alarm are supplied.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

252

03

/3DB 06687 CA AA

340

340

The following table summarizes the information obtained in the Alarm view, starting from the left column.

Tab. 13. 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. 14. on page 260 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

253

03

/3DB 06687 CA AA

340

340

3–1.5 Warnings on the troubleshooting

3–1.5.1 Problems with the Craft Terminal

With regard to the PC maintenance, refer to the constructor’s documentation.

3–1.5.1.1 PC restart

This procedure describes how to shutdown and restart the PC should the Craft Terminal SoftWare Productnot be working properly or not responding to the operator’s commands.

In order to shutdown the PC execute the command :

Start > Shutdown

A window (Windows NT Security user dialog) is displayed. It permits to shutdown the computer or restartit.

The same window is displayed pressing he keys <Ctrl> + <Alt> + <Del> simultaneously.

N.B. In the case this procedure is unsuccessful, carry out the checks indicated in followingparagraphs 3–1.5.1.2 and/or 3–1.5.1.3.

3–1.5.1.2 Craft Terminal not working

Whenever the login with the Craft Terminal does not work, proceed with the following checks:

– Restart the Craft Terminal (logout and switch off/on).

– 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). The fields to be verified in this screen are:

COM1

Port

ON

Physical

ON

OSI orLogical

– Verify that the CT port is effectively that connected by cable to equipment’s F interface

– If ’Physical’ is OFF, the problem can be due to:• CT physical port faulty• MAIN unit F–interface port faulty• the cable

If possible, verify the correct working of the Craft Terminal and of the CT–F interface cable using themwith another Alcatel equipment. If the problem still persists, solve the problem.Otherwise, proceed with the MAIN unit replacement, or perform steps indicated in para.3–1.5.1.4 onpage 254.

– If ’OSI/Logical’ is OFF, the problem can be due to:• FLASH CARD missing on MAIN unit (verify) or FLASH CARD/MAIN faultyProceed with the MAIN unit replacement, or perform steps indicated in para.3–1.5.1.4 on page 254.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

254

03

/3DB 06687 CA AA

340

340

3–1.5.1.3 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 !

3–1.5.1.4 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, asdescribed in:

9400AWY Technical Handbooks,section MAINTENANCE

chapter SECOND LEVEL MAINTENANCE,paragraph UNIT REPLACEMENT PROCEDURES

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.3–2.2 on page 264.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

255

03

/3DB 06687 CA AA

340

340

3–1.5.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

3–1.5.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 in Step 10 (for NMS V.11 channel) andin Step 11 (for NMS G.703 channel) or in the Menu Configuration → Network Configuration → IPConfiguration → IP Point to Point Configuration.

3–1.5.4 Loopbacks

For a correct activation of every loopback (Loopback menu):

– the relevant tributary must be enabled (Quick Configuration Procedure → Step 3)

– the local transmitter must be not muted (Menu Radio → Configuration)

Note 1: The loopback will become active after 6–7 sec. approx. (24 sec. approx. for the RF loopback).

Note 2: The time for a new set is 10 to 25 sec. approx.

3–1.5.5 Empty USM icon in NES

Enter Windows Task Manager and stop the process relevant to the empty USM.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

256

03

/3DB 06687 CA AA

340

340

3–1.5.6 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.

3–1.5.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.

3–1.5.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 or from ”Unframed” to ”Framed SF” or ”FramedESF” or vice–versa for the DS1 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

257

03

/3DB 06687 CA AA

340

340

3–1.5.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. 175. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

258

03

/3DB 06687 CA AA

340

340

3–1.5.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. 176. 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, anycase, 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 < –95 dbm.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

259

03

/3DB 06687 CA AA

340

340

3–1.5.11 Tributaries 9 to 16 visible in “8E1/DS1_Ethernet” configuration

In an “8E1/DS1_Ethernet” type configuration, operator may choose a 16 EI (or DS1) frame structurecapacity. In this case, the relevant 9 to 16 tributaries bandwidth will be dedicated to the two User Ethernetports

Nevertheless, tributaries 9 to 16 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 9 to 16,in the “line interface” view as well as in the “loopback view”.

Fig. 177. Tributaries 9 to 16 visible in “8E1/DS1_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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

260

03

/3DB 06687 CA AA

340

340

3–1.6 Description of alarms and of probable causes

The information provided helps the operator during troubleshooting operations.

Tab. 14. 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)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

261

03

/3DB 06687 CA AA

340

340

Tab. 14. General issues of the alarm meanings and their respective maintenance actions

ALARM MEANING MAINTENANCE ACTION

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

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

3–1.7 Unit replacement

After having identified a unit to be replaced, in order to carry out the replacement correctly, please refer:

– as far as IDU MAIN UNIT, IDU EXTENSION UNIT and ODU are concerned, to:

9400AWY Technical Handbooks, section MAINTENANCEchapter SECOND LEVEL MAINTENANCE,

paragraph UNIT REPLACEMENT PROCEDURES

– as far as FLASH CARD is concerned, to chapter 3–2 Spare Flash Card management andreplacement procedures on page 263

WARNING:

Before to disconnect the cable IDU–ODU of N.E., the corresponding IDU unit must be alwaysturn–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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

262

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

263

03

/3DB 06687 CA AA

340

340

3–2 SPARE FLASH CARD MANAGEMENT AND REPLACEMENT PROCEDURES

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.1–5.2 Flash Card upgrade on page 82.

3–2.1 Spare Flash Card management

Please refer to para.B.2 on page 302 for detailed information on Flash Card position, types, identificationand content.

With reference to the Flash Card content description given in para.B.2.3 on page 307, a spare Flash Card:

a ) supplied as “specific” spare part for a certain NE should contain the same SW information (SWCOMMIT VERSION, MIB and NE network routing data) stored in the Flash Card present in the NEdelivered to Customer from Alcatel factory. In this case, such a “specific” spare Flash Card can beused at any time only to replace that existing in that “specific” NE, provided that no change is madeon the NE SW information by Craft Terminal or by TMN system.

b ) supplied as “generic” spare part, contains default SW information, stored by Alcatel factory for testingpurposes before delivery to Customer. In this case you cannot insert it “as it is” in any NE, withoutmaking 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] MIB back–up file

[2] NE network routing data

Please, refer to para.1–1.6 on page 30 for details.

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 PQ/ECRC and Supervisory Units, thus causing a complete system crash.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

264

03

/3DB 06687 CA AA

340

340

3–2.2 Flash Card replacement procedures

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.B.2.3 on page 307). Many types are envisaged: itsidentification is described in para.B.2.2 on page 302.

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 PQ/ECRC and Supervisory Units, thus causing a complete system crash.

The Flash Card replacement procedure to use depends on the choice adopted by the Customer withreference to the type of spare flash card stored in the spare–part–stock (refer to the Spare Flash Cardmanagement policy described in para.3–2.1 on page 263):

a ) “specific” spare part for a certain NE (each NE has its own “specific” spare Flash Card, kept alignedto SW changes made on the NE in service, through an off–line service station).In this case proceed as specified in para.3–2.2.1 on page 265.

b ) “generic” spare part that cannot be inserted it “as it is” in any NE.In this case proceed as specified in para.3–2.2.2 on page 266.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

265

03

/3DB 06687 CA AA

340

340

3–2.2.1 Flash Card replacement with a spare flash card “specific” for the NE

General warnings:

Screw fixing

In all described operations, the screw tightening torque must be:


Procedure to be used only in the case specified in point a ) on page 264

Procedure:

[1] read the Flash Card Name on the label affixed on IDU MAIN unit (see Fig. 180. on page 299) andaccording to it, retrieve the Flash Card Technical Code through Tab. 22. on page 302. If CT works,you can verify the Flash Card type by Supervision ⇒ SW Key (example in Fig. 123. on page 194)

[2] get the spare Flash Card with the same Technical Code; leave it in its protective envelope until youhave worn the antistatic protection armlet;

N.B. verify that is really “specific” for the NE where it must be inserted, by suitabledocumentation that should be together with it

[3] wear the antistatic protection armlet [see point b ) on page 17] and connect its termination to agrounded structure

ATTENTION



[5] 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. 182. on page 299 for Flash Cardprofile and insertion direction)

[6] if you are not sure of the spare Flash Card’s MIB content, carry out MIB data restore and activation(using NE’s specific MIB back–up file) as shown in MIB Restore in Fig. 164. on page 237 (fromoperative point of view, refer to para.2–7.3.2 and 2–7.3.3 on page 193). In alternative to activationby SW, carry out the Equipment Controller HW Reset, pushing the suitable button on IDU MAIN Unit(see Fig. 180. on page 299).About two minutes are necessary for the supervision process to get data from the new flash card.

[7] restore the Flash Card cover removed in step [4] above


[9] 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

266

03

/3DB 06687 CA AA

340

340

3–2.2.2 Flash Card replacement with a “generic” spare flash card

Procedure to be used only in the case specified in point b ) on page 264.

In practice , you have to rebuild all SW information on the Flash Card.

You can do that using the procedure Installation of a new Flash Card not configured in factorydescribed in para.1–5.2.5 on page 86).

Such a procedure requires the NE to be isolated from the supervision network.

N.B. Before to isolate the system from the supervision network, inform the supervision center: if (fromthe supervision point of view), there are other NEs cascade–connected to it (and withoutsupervision ring network) they will be isolated, too.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

267

03

/3DB 06687 CA AA

340

340

SECTION 4: SWP DESCRIPTION AND VERSIONS

This section gives information on the Software Packages this handbook refers to, and that are bothindependent and independent on the specific SWP Versions.


INFORMATION INDEPENDENT ON THE SPECIFIC SWP VERSIONS

Chapter 4–1 – SWP REG.9400AWY R.2.0 descriptionThis chapter gives information on the Software Packages this handbook refers to,and that are independent on the specific SWP Version: commercial information(SWP and Software Licences P/Ns).

269

INFORMATION ON THE SPECIFIC SWP VERSIONSThese chapters give operative information regarding the Software Package Version2.0.x, starting from version V2.0.0: requirements (PC and equipment Firmware),Reference Information Model, SW Package Identification, SW PackageComponents, ECT SW Sub–Component, NE MIB Compatibility, new features,restrictions and known problems.

Chapter 4–2 – SWP REG.9400AWY R.2.0 V.2.0.0 specific information 271



The symbol points out references to the other handbooks.

Referenced handbook P/Ns are given in Appendix D on page 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

268

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

269

03

/3DB 06687 CA AA

340

340

4–1 SWP 9400AWY R.2.0 DESCRIPTION

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

4–1.1 General

The software products are distributed by Alcatel 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.

Alcatel typically offers several software licences on the software product.

They are referred both to the Network Element software features and to the Craft Terminal softwarefeatures.

Note for all tables:

Technical Code Technical part number of the item

N.B.:– The correspondance between Commercial Codes and associated

Technical Codes, if any, is given in chapter Commercial Codes ofthe 9400AWY Rel.2.0 Technical Handbook (from Ed.03), whichdescribes also the usage of Technical Codes and correspondentCommercial Codes.

– The last two Technical Code letters stand for a ”feasible alternative”,they might differentiate two items even though still functionallycompatible. For this reason the indicated Technical Code does notinclude the last two letters (replaced by **).

Technical Description Technical Description of the item.The correspondance between Commercial Descriptions andassociated Technical Descriptions, if any, is given in chapter Commercial Codes of the 9400AWY Rel.2.0 Technical Handbook (fromEd.03).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

270

03

/3DB 06687 CA AA

340

340

4–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. 15. Software products part numbers

REF Technical Description Technical Code Notes

(a) SWP 9400AWY R.2.0 CD–ROM 3DB 06690 AA**For versions 2.0.0 & 2.0.1N.B.

(b) SWP 9400AWY R.2.0.2 CD–ROM 3DB 06690 AB**For versions � 2.0.2N.B.

(c) SWP OPTICS–IM WTD SNMP V218 CD–ROM 3DB 04799 AC** For version 2.0.0

(d) SWP OPTICS–IM WTD SNMP V220 CD–ROM 3DB 04799 AE** For version 2.0.1

(e) SWP OPTICS–IM WTD SNMP V221 CD–ROM 3DB 04799 AF** For versions � 2.0.2

N.B. Software Package associated to LCT or RCT SW Licence.

4–1.3 OEM Software licence list and part numbers

Every Software licence is identified by a denomination and a part number, listed on the following table.

Tab. 16. Software licence part numbers

Technical Description Technical Code N.B.

SWL–ULS R2.0 FEE 3DB 06819 AA** 1

SWL–LCT 9400 AWY R2.0 FEE 3DB 06820 AA**2

SWL–RCT 9400 AWY R2.0 FEE 3DB 06821 AA**2

N.B. 1 Licence for Network Element software features (one per Transceiver):

2 Licence alternative for Craft Terminal software features:• SWL–LCT: local Craft Terminal functionality• SWL–RCT: remote Craft Terminal functionality.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

271

03

/3DB 06687 CA AA

340

340

4–2 SWP REG.9400AWY R.2.0 V2.0.0 SPECIFIC INFORMATION

This chapter gives operative information regarding the Software Package Version 2.0.0: requirements (PCand equipment Firmware), Reference Information Model, SW Package Identification, SW PackageComponents, ECT SW Sub–Component, NE MIB Compatibility, new features, restrictions and knownproblems.

Please refer to para.D.3.2 on page 331 for the meaning of SWP Release, Version and Patch Level.

N.B. With reference to the Versions stated in this chapter, please read carefully theN.B. on page 322.

4–2.1 ECT requirements

Refer to para.1–2.1.1 on page 31


Reference SNMP–IM version: 2.18 (SGPA 3.4.1).Related SWP: REF.(c) in Tab. 15. on page 270.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

272

03

/3DB 06687 CA AA

340

340

4–2.3 SWP version specific data

N.B. With reference to the Versions stated on this page, please read carefully theN.B. on page 322.

4–2.3.1 SW Package Identification

Identification Version Date

SWP REG. 9400AWY R2.0 V2.0.0 April 16th, 2005

4–2.3.2 SW Package Components

Name Description Version

SWP REG. 9400AWY R2.0SW Package for Radio Regenerator Low Capacity PDHEquipments AWY Scalable

V2.0.0

SWC–ECT9400AWY_V20 Equipment Craft Terminal SW Component V2.0.8

SWC–EC9400AWY_V20 Equipment Controller SW Component V2.0.10

SWC–OCR9400AWY_V20 ODU Radio Controller SW Component V1.7.7

SWC–FFENI9400AWY_V20 Fenice FPGA JBC Image File Component V1.0.13

SWC–FGAIA9400AWY_V20 Gaia FPGA JBC Image File Component V1.0.0

SWC–FGAEX9400AWY_V20 Gaia–Ext FPGA JBC Image File Component V1.0.2

SWC–FMEDU9400AWY_V20 Medusa FPGA JBC Image File Component V1.0.1

SWC–FPONT9400AWY_V20 Ponto FPGA JBC Image File Component V1.0.1

SWC–FD9400AWY_V20 File Descriptor for SW Download Component V2.0.0

4–2.3.3 ECT SW Sub–Components

Name Version Description

JRE V1.4.1–04 Java 2 Run Time Environment

LLMAN V3.4.0 Lower Layers Manager

CT–K V3.2.0 P6 Craft Terminal Base Platform

CT–K SNMP Add–On V3.1.2 P4 Craft Terminal Base Platform SNMP Add–On (EML–IM)

CT–K HOL Add–On V1.1.0 P0 Craft Terminal Base Platform Help On–Line Add–On

CT–K NE–CONF Add–On V1.25 Craft Terminal NE Type&Release Configuration Add–On

JUSM–SNMP–COMMON V2.0.8 User Service Manager for SNMP MW NEs

JUSM–SNMP–HELP V2.0.3 Help On–Line for SNMP MW NEs

CT–K Q3 Add–On V3.1.1 P2 Craft Terminal Base Platform Q3 Add–On (EML–IM)

4–2.3.4 NE MIB Compatibility

Due to different IDU scalable HW platform (9400AWY Rel.2.0), ULS V2.0.0 MIB is not compatible with ULSV1.0.x MIB (9400AWY Rel.1.0 and 9400FSO Rel.1.0). The NE data must be manually configured.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

273

03

/3DB 06687 CA AA

340

340

4–2.4 New features and modifications

– Complete management of 9400AWY Rel.2.0 IDU HW platform for ETSI market– Complete management of 8E1, E3 and Data plug–ins

N.B. The IDU hardware of 9400AWY Rel.1.0 and the 9400FSO Rel.1.0 hardware are not supportedby SWP REG. 9400AWY R2.0.

4–2.5 Restrictions and known problems

This for EC:

a ) It has been temporary inhibited the management of Attended button.An investigation has to be done in order to verify the state of associated pin.

b ) Restrictions related to configuration with data plug–in and frame structure 16E1:

• Before changing the configuration FROM 1+0 or 1+1 with 8E1 plug–in TO 1+0 or 1+1 with Dataplug–in (frameStructure=16E1), it is necessary to disable tributary from 9 to 16 and removeloopback from trib.9 to trib.16

• The inhibition of loopback activation on tributary from 9 to 16 with Data plug–in is notimplemented yet.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

274

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

275

03

/3DB 06687 CA AA

340

340





NOTE FOR ALCATEL INTERNAL USE: information in this chapter is retrieved from document:

– 8BW03051 0033 FMZZA ED.03 25/10/2005 (Release Note SWP REG.9400AWY R.2.0)


Refer to para.1–2.1.1 on page 31 (they are the same as for V2.0.0)


Reference SNMP–IM version: 2.20 (SGPA 3.4.2).Related SWP: REF.(d) in Tab. 15. on page 270.

4–3.3 Equipment hardware requirements

Please refer to para.1–3.1.2 point [2] on page 67.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

276

03

/3DB 06687 CA AA

340

340


N.B. With reference to the Versions stated in this paragraph, please read carefullythe N.B. on page 322.



SWP REG. 9400AWY R2.0 V2.0.1 Oct 11th, 2005




V2.0.1









SWC–FGAAE9400AWY_V20 Gaia AE FPGA JBC Image File Component V2.0.1

SWC–FGAAX9400AWY_V20 Gaia–Ext AE FPGA JBC Image File Component V2.0.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

277

03

/3DB 06687 CA AA

340

340



ISI–PSOS–PPC V2.5.0F P135 PSOSsystem Library for PQUICC processors

TLX–SLX–DDPPC V8.1.0.P128 Platform tools and script file for SUN Solaris

KS–PQ1–GECRC V8.1.0 P136 Kernel Subsystem Generic Part for PQUICC

KS–PQ1–SECRC V8.1.0 P135 Kernel Subsystem EC Specific Part for PQUICC

RWL–PQ1–SECRC V8.1.0 Raw Loader EC Specific for PQUICC

CS–PQ1–GEN–QB3 V7.3.3 Q3 Interface Management Generic Part for PQUICC

CS–PQ1–GEN–8021E V8.1.0.P10 Client Download Module Library for PQUICC

MGT–PQX–GEN V9.0.0.P20 IP Management

CS–PQX–GEN–RTG V9.0.0.P11 OSPF & RIP Routing Protocols Management

CS–PQ1–GEN–SNMPV91 V7.3.2 SNMP Protocol Management

KS–PQ1–GEN–IPNTP V7.2.1 NTP Management

VFS–PQ1–GEN V8.1.0 File System for PQUICC

DM–MA–GEN V7.1.1 DM and MA Generic Part for PQUICC

GRF–PRECOMP–SLX V1.0.0 GRF Pre–Compiler Product for SUN Solaris

GRF–RUNTIME–PQ1 V1.0.0 GRF Run–Time Library for PQUICC

INT–EC–OC V1.1.20 EC–OC IDU/ODU Interface

SVI–INTERFACE V10.2.0 SNMP Virtual Interface

SGPA V3.4.1 SNMP Generic Program Agent for 2G Radio Equipments

VHM V2.1.8 Virtual Hardware Module


NE MIB is compatible with previous release 2.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

278

03

/3DB 06687 CA AA

340

340


With respect to previous SWP V2.0.0, new features and modifications are:

[1] This for ECT:

1 ) Warning message on Set Frequency Parameters

2 ) Warning message on TX Mute function

3 ) USM instability: alarm surveillance improvement.

4 ) Quick Configuration improvement: shifter management

5 ) Quick Configuration improvement: pause after change of NE type from 1+0 to 1+1 andviceversa

6 ) Summary Block: block of NMS alarm has been added

7 ) OSPF area management: mask information has been removed

8 ) MIB management menu: Restore and Activation improvement

9 ) Alarm ”Loss of GFP on Ethernet Port egressing (Rx Side)” is reported at CT

10 ) Link Identifier has been removed from System Settings parameters

11 ) Added management of allowedDS1LineLenght table

12 ) Improvement management of Frequency Shifter

13 ) Improvement management of Static Delay

14 ) Removed inhibition in 8E1/DS1 –ETH configuration to allow DS3 frame structure

15 ) Solved problems on Rx NEAR–END loopback for FCC configuration

16 ) NEType allowed list improvement

17 ) QC: added shifter management

18 ) GFPCon alarm improvement

19 ) Power Meas graph improvement

20 ) Configuration View: data parameters

21 ) New Frequency Shifter management

22 ) PMDS improvement (SH 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

279

03

/3DB 06687 CA AA

340

340

[2] This for EC:

1 ) The functionality of automatic EPLD download (GAIA and GAIA_AE) has been removed,because it has been verified that, for GAIA components, the reading of EPLD version (madeby IDU–SW during restarts and after board power–on) creates impacts on traffic.

2 ) To avoid strictly dependencies to HW codes, it has been changed the algorithm used toenable/disable the automatic FPGA/EPLD download and to enable/disable ATTENDED button(based on remote inventory contents): for this reason, to avoid unexpected behavior, beforeactivate new SW package 2.0.1h it has to be kept attention on remote inventory of the boards.

The automatic FPGA/EPLD download and the attended button are DISABLED ONLY on boardsED.2 and on boards ED.3, and, as consequence, they are ENABLED in ALL OTHER CASES.These editions are recognized by means of UNIT PART NUMBER (stored in remote Inventory);the automatic FPGA/EPLD download it is DISABLED ONLY when the contents of UNIT PARTNUMBER is one of the following:– MULDEM MAIN: 3DB06395AAAA– MULDEM EXTENSION : 3DB06404AAAA

The download can be anyway disabled putting the file NOAUTOSWDW under/home/adm–lc–ng/debug folder, but the management of the attended button CANNOT bedisabled and using boards without the right management of this button there could bemisalignment on alarm management (both on NMS and on leds).

It has been also changed the algorithm used to recognize different GAIA components(GAIA/GAIA_AE): it is retrieved idCode directly from GAIA and this information is used to selectthe right file image to download.

3 ) Inserted filter of EarlyWarning alarm in case of near–end E3/DS3 loopback presence

4 ) Updated HBER threshold values (FENICE) in ANSI configurations (4/8/16DS1 and DS3) withthe same values used for ETSI market.

5 ) It has been inserted a check on backup contents (during restore operation) to verify if theconfiguration saved is compatible with SW key: for this reason it has been changed thedatabase and backup made with previous pre–release are no more compatible if it is used aSW KEY different from FULL–FLEXIBLE.

6 ) 6) Inserted new management in case of change of ETH rate 10/100 or 100/10This behavior can be disabled putting the file noMedusaSpeed in /home/adm–lcng/ debugfolder (the file is read ONLY during EC startup)

7 ) Inserted filter of EarlyWarning alarm in case of IDU cable loopback presence

8 ) Inserted modifications on versions check for FPGA/EPLD automatic download

9 ) A modification in EC database has been made; for this reason in case of downgrade to previousEC version there could be some problems related to NOT ENABLED pointToPoint interfaces:after downgrade all pointToPoint are enabled (they can be deactivated by CT/NMS).

10 ) The automatic FPGA/EPLD download HAS BEEN ENABLED ONLY ON BOARD ED.4The edition is recognized by means of UNIT PART NUMBER (stored in remote Inventory):– MULDEM MAIN : 3DB 06395 AAAB and 3DB 06395 ABAA– MULDEM EXTENSION : 3DB 06404 AAAB and 3DB 06404 ABAAThe download can be disabled putting the file NOAUTOSWDW under /home/adm–lcng/ debugfolder.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

280

03

/3DB 06687 CA AA

340

340

11 ) Inserted management of Transparent Ethernet (1530 bytes) (modified Medusa defaultconfiguration)

12 ) Inserted management of EXAR Low Cost (modified EXAR default configuration).

13 ) Inserted management of ODU–SMT (it is managed as standard ODU).

14 ) Inserted management to mask IDU–ODU driver read (B_FULL inhibition) when IDU cableloopback is executed.

15 ) Inserted inhibition of LinkIdentifier enable and updating.

16 ) Reported all modifications and improvements inserted in new SWP AWY 1.0.2 (Telus version):– Inserted retry (5) on Pegaso (SPI) read in case of fail, before declare card fail alarm

The successfully retries are traced on SW–Trace log file in the following way “Recoverederror in reading Pegaso reg#x ch#y after n retry.

– In case of Loss of Signal on tributary #1 and #9 a check on exar register #0 contents isdone: in case the content is not the expected the register is re–configured and a specifictrace is inserted on SW–Trace log file.

– After a card fail (both HW or SW) the board is completely re–configured .– Inserted traces in SW–Trace log file to trace all card fail detection.

17 ) Resolved problem in management of CONF_SW_RPS_KO pin on Gutturnio after EXTENSIONswitch–off/disconnection and connection with EXTENSION powered off.

18 ) Resolved problem related to usage of addresses 0.0.0.x in OSPF .

19 ) Alignment to Ominx Scalable 1+0 and 1+1 ANSI files Ed.2

20 ) The automatic FPGA/EPLD download HAS BEEN ENABLED ONLY ON BOARD ED.4The edition is recognized by means of UNIT PART NUMBER (stored in remote Inventory):– MULDEM MAIN : 3DB06395AAAB– MULDEM EXTENSION : 3DB06404AAABThe download can be disabled putting the file NOAUTOSWDW under /home/adm–lcng/ debugfolder.

21 ) Added management of new GAIA/GAIA_EXT image files (for new Altera components): newcomponents are mounted ONLY on boards ED.4 and are recognized by means of ICS (storedin remote inventory):– ICS � 2 identify new GAIA/GAIA_EXT components

22 ) Added alarm notification during FPGA/EPD download

23 ) Enabled ATTENDED button management only on boards ED.4This remove the restriction present in previous pre–releases and in release 2.0 (“It has beentemporary inhibited the management of Attended button”)

24 ) Added management of “Clock 39Mhz” alarm as CARD FAIL root

25 ) Updated management of CONF_SW_RPS_KO pin: EXT card missing alarm and fail onCYPRESS–HITLESS configuration are taken into account.

26 ) Inserted management of specific forcing commands for EPS and HST protection: thesecommands are used during maintenance operation on MAIN MULDEM board (pin MAIN3 andMAIN4).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

281

03

/3DB 06687 CA AA

340

340

27 ) Inserted management for specific maintenance operation on MAIN board: to avoid earlierswitch of RPS protection on main board (in case ODU is not yet configured), the switch ispermitted ONLY at the end of ODU configuration. This mechanism has been implemented usingFAIL_ODU_MAIN pin on Gutturnio: this pin is put in FAIL state when ODU ch#1 is disconnectedor when CARD FAIL is detected on MAIN MULDEM board. The pin is put in ACTIVE state whenthe alarm is switched off and ODU is configured.

28 ) Updated HW configuration for SERVICE CHANNELS

29 ) Added management of allowedDS1LineLenght table

30 ) Added management of flexible delay during ODU–SW download: different delay time is usedaccording to ODU–SW running .

31 ) Improvement management of allowedFrequencyShifter table update

32 ) Improvement management on FrequencyShifter update in 1+1HST

33 ) Improvement management on LABEL associated to PdhFrameHOPThresholdData andPdhFrameLinkThresholdData

34 ) Improvement management on Market change: the frameStructure is automatically updated(the little frame allowed by SW–KEY is chosen)This remove the restriction present in previous pre–release (“The market change has to beexecuted with Quick Configuration and not with System Setting menu”)

35 ) Solved problems on DATA plug–in (Medusa registers corruption)

36 ) Solved problems on FAR–END loopback

37 ) Solved problem to permit many restore operations before the backup activation (MIBmanagement)

38 ) Added management of 1+1 FCC configuration (Ominx Scalable 1+1 ANSI files Ed.1)For information related to supported HW configuration refer to release note inserted in OmnixScalable 1+1 ANSI files– Management of all equipment configurations (DS1/DS3/DATA)– Tributary management and specific DS1 parameters: LineCode and LineLenght– Loopback management– Performance Monitoring management

39 ) Added management of IF–Table

40 ) Added management of ODU–SW not compatible with new shifter messages: in this case newmessages are not sent. This behavior is active during SW–MISMATCH

41 ) Added management of MIB upgrading changing FROM 1+0 or 1+1 with 8E1 plug–in TO 1+0or 1+1 with DATA plug–in (frameStructure=16E1):– Tributary from 9 to 16 are automatically disabled– Loopback active on tributary from 9 to 16 are automatically removed

42 ) Added management of 1+0 FCC configuration (Ominx Scalable 1+0 ANSI files Ed.1):– Management of all equipment configurations– Tributary management and specific DS1 parameters: LineCode and LineLenght– Loopback management– Performance Monitoring management

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

282

03

/3DB 06687 CA AA

340

340

43 ) Solved problem related to maintenance action on MAIN board: during EC restart the KTPScommand is checked and maintained.

44 ) Improvement management of Filter History Data retrieval (this function can be enabled onlyfrom NMS manager)

45 ) Improvement management on radio measurement function

46 ) Improvement on ODU–SW download: reduced pause time between each block to speed–upthe transfer.

[3] This for ODU:

1 ) Upgrade of MRU boards part number

2 ) ODU 7–8 Implementation of exception cases for shifter management

3 ) SWPN 3CC14614AAAA

4 ) ODU 7–8 new parameter to calculate Prx

5 ) ”Exotix” shifters case for 8 GHz (precision 10khz instead of 1Mhz)

6 ) EEPROM address on MRU board same as TIFU board

7 ) No alarm after shifter update

8 ) Add new boards’ remote inventories

9 ) Tx Power shutdown on IDU/ODU com failure

10 ) Data clock inversion only on CR boards (Perseo parameter)

11 ) Add new boards’ remote inventories

12 ) Data clock inversion only on CR boards (Perseo parameter)


This for ECT:

a ) For Windows 2000 and Windows XP it is mandatory set ”Power schemes” equal to ”AlwaysOn” into ”Power Options Properties”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

283

03

/3DB 06687 CA AA

340

340





NOTE FOR ALCATEL INTERNAL USE: information in this chapter is retrieved from document:

– 8BW03051 0033 FMZZA ED.04 23/12/2005 (Release Note SWP REG.9400AWY R.2.0)


Refer to para.1–2.1.1 on page 31 (they are the same as for V2.0.0 and V2.0.1)


Reference SNMP–IM version: 2.21 (SGPA 3.4.4).Related SWP: REF.(e) in Tab. 15. on page 270.

4–4.3 Equipment hardware requirements

Please refer to para.1–3.1.2 point [2] on page 67.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

284

03

/3DB 06687 CA AA

340

340


N.B. With reference to the Versions stated in this paragraph, please read carefullythe N.B. on page 322.



SWP REG. 9400AWY R2.0 V2.0.2 Dec 15th, 2005




V2.0.2









SWC–FGAAE9400AWY_V20 Gaia AE FPGA JBC Image File Component V2.0.1

SWC–FGAAX9400AWY_V20 Gaia–Ext AE FPGA JBC Image File Component V2.0.1




JRE V1.4.1–04 Java 2 Run Time Environment

LLMAN V3.4.0 Lower Layers Manager

CT–K V3.2.0 P6 Craft Terminal Base Platform

CT–K SNMP Add–On V3.1.2 P4 Craft Terminal Base Platform SNMP Add–On (EML–IM)

CT–K HOL Add–On V1.1.0 P0 Craft Terminal Base Platform Help On–Line Add–On

CT–K NE–CONF Add–On V1.26 Craft Terminal NE Type&Release Configuration Add–On

JUSM–SNMP–COMMON V2.2.4 User Service Manager for SNMP MW NEs

JUSM–SNMP–HELP V2.2.2 Help On–Line for SNMP MW NEs

CT–K Q3 Add–On V3.1.1 P2 Craft Terminal Base Platform Q3 Add–On (EML–IM)


NE MIB is compatible with previous releases 2.0.0 and 2.0.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

285

03

/3DB 06687 CA AA

340

340


With respect to previous SWP V2.0.1, new features and modifications are:

[1] This for ECT:

1 ) This JUSM version supports ULS 2.0.(1) and 2.0.(2)

2 ) SECURITY and PROFILES MANAGEMENT on SNMPv2

3 ) A warning message has been added in the Frequency panel when the frequency parameters(with shifter configuration) are not consistent.

4 ) Specific changes has been added into LAC properties file

[2] This for EC:

1 ) Inserted management of SNMP v2 Security features:– User creation and deletion– User password change– Password verification– Username list

2 ) Inserted management of new PSU +24/+60 and new allowed NE configuration types

3 ) nserted new SNMP–AGENT to manage in a right way the “addressing”: theSNMP–RESPONSE are sent inserting in SNMP message the address used in the requestmessage, while the SNMP–TRAP are sent using always the LOCAL IP ADDRESS of theNetwork Element. It is possible, only for particular situation, to use the “old” addressingmanagement putting the file OLDADDRESS under /home/adm–lc–ng/debug folder.

4 ) Changed maximum number of allowed shifter from 25 to 50.This modification has impacts on SNMP–AGENT (increased number of entries inopticsIMAllowedShifter table) and in EC–OC interface protocol (in the same way has beenincreased the maximum number of shifter returned by ODU).

5 ) Inserted management of “User channel G.703 patch for ANSI mode” as described in specificnote distributed by M.Brioschi. The patch is executed only in ANSI mode (the check on marketis executed verifying what has been configured by operator); FENICE version is taken intoaccount: if FPGA version is minor or equal to v1.0.16 the patch isn’t executed. No check isexecuted on PONTO version.

6 ) Inserted modifications in shifter management; it has been added a check between shifter valueconfigured and list of allowed shifters returned by ODU: if the configured shifter is not in the list,it is “invalidated” (set to UNDEFINED) and an update of SNMP–MIB is executed.This can happen in case of ODU substitution, if new ODU has a different frequency range.

7 ) Inserted the management of alarm severity probable cause (string) also in case of creation ofnew alarm profile (CLONE). The modification can be tested only with MibBroswer, because thisinformation is not displayed on CT.

8 ) Inserted checks in SNMP–AGENT: the SNMP–MIB cannot be viewed or modified (read/write)by NOT REGISTERED manager. This modification is relevant when Mib–Broswer orproprietary Manager is used (because Alcatel manager makes the registration before any otherMIB access)

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

286

03

/3DB 06687 CA AA

340

340

9 ) Inserted a modification in the management of allowedShifter list: it has been added a check onODU status, to inhibits the consistency checks between the allowedList and the value storedin database in case of empty list from ODU or ODU missing (if ICP alarms is active or if ODUdoesn’t answer)

10 ) Inserted patch to solve problems related V11 contro–directional (re–routing of V11 contro–dir)The patch is implemented only in FCC market (both for PONTO and for FENICE) and is appliedonly if FENICE version is greater than 1.0.18.

11 ) Inserted a modification to avoid checks on Manager registration: this is not a official way tooperate, it can be used as backup solution with OMNIX–SNMP tool (avoiding registrationphase).The registration check is not executed if the file NOREGISTRATION is put under/home/adm–lc–ng/debug folder: it is necessary reset EC because the file presence it is verifiedonly at start–up.

12 ) Modified the parameters used to check the availability of PPP connection on TMN channels(keep–alive management).In particular, it have been changed retries number from 2 to 6 and timer period from 2 to 5seconds.This modification has been inserted in order to solve problems evidenced during tests(perturbation events) in network with more than 20 NEs.The side effect of the modification of these parameters is the change of the detection time ofa PPP Failure alarm that results increased from 4 to 30 seconds.

[3] This for OC:

1 ) Increase of shifter numbers in Idu/Odu communication

2 ) ATPC using FPGA instead of PERSEO

3 ) Addition of manual Idu selection before Automatic detection, with a timeout of 10second, usedfor production.


This for ECT:

a ) For Windows 2000 and Windows XP it is mandatory set ”Power schemes” equal to ”AlwaysOn” into ”Power Options Properties”.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

287

03

/3DB 06687 CA AA

340

340

SECTION 5: APPENDICES


Appendix A – Equipment description and componentsThis Appendix sums–up the equipment functions and defines its components fromthe SW point of view.

289

Appendix B – SW allocation, Flash Card and equipment controlThis Appendix presents the software allocation in the various parts of the equipment,the types of Flash Card and its contents, and the general characteristics of the ECTand RECT.

299

Appendix C – 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.

311

Appendix D – Documentation GuideThis Appendix contains all information regarding this handbook (purpose,applicability, history) and the Customer Documentation set it belongs to, in particularthe list of the handbooks the Operators should have in order to carry out the requiredoperations.

321

Appendix E – Acronyms and abbreviations 333

Appendix F – Glossary of terms 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

288

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

289

03

/3DB 06687 CA AA

340

340

APPENDIX A : EQUIPMENT DESCRIPTION AND COMPONENTS

Please refer to Tab. 1. on page 14 for system features and SWP–version relationship

This appendix sums–up the equipment functions and defines its components from the SW point of view:

– Functions and configurations on page 290

– IDU and ODU Components on page 291:

• IDU on page 293

• ODU on page 294

• Allowed Equipment Types on page 294

• Remote Inventory Management on page 296

– Equipment Protection Switching Management on page 296

– External Points Management on page 297

For more detailed in formation from the hardware point of view, please refer to:

– 9400AWY Rel.2.0 Technical Handbook from ED.02

From the software point of view, the equipment management is carried out as explained in Section 2 –NE MANAGEMENT on page 89, in chapters relevant to the EQUIPMENT CONFIGURATIONMANAGEMENT .

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

290

03

/3DB 06687 CA AA

340

340

A.1 : Functions and configurations

ULS NE has the aim to multiplexer/demultiplexer the main tributaries (up to 16xE1 / 16xDS1 or 1xE3 /1xDS3) with different modulation formats.

The following Tab. 17. resumes the relation among market, tributaries and modulation.

Tab. 17. Markets, tributaries and modulations forecasted

Market Tributary Modulation

2xE1 4QAM

4xE1 4QAM / 16QAM

ETSI 8xE1 4QAM /16QAM

16xE1 4QAM / 16QAM

1xE3 4QAM / 16QAM

4xDS1 4QAM

ANSI8xDS1 4QAM /16QAM

ANSI16xDS1 4QAM / 16QAM

1xDS3 4QAM / 16QAM

The main functions performed by IDU and ODU of ULS equipment are the following:

– Multiplexer/DemultiplexerThe multiplexer function receives main tributaries (see Tab. 17. above) 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 InterfaceThe 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

291

03

/3DB 06687 CA AA

340

340

A.2 : IDU and ODU Components

The ULS NE is composed by two different parts: the indoor and the outdoor part. In the following they aredescribed from physical and management point of view.

Antenna

IDU

IDU–ODU cable

ODU

NEULS

MAIN SHELFIDU Ch#1

ODU Ch#1

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

IDU

ODU

NEULS

IDU–ODU cables

EXTENSION SHELFIDU Ch#0

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

MAIN SHELFIDU Ch#1

for possible ODU (1+1)configurations

see Fig. 179. on page 292

Fig. 178. 9400AWY R.2.0 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

292

03

/3DB 06687 CA AA

340

340

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 CH 0

ODU CH 1

to IDU MAIN UNIT

to IDU EXTENSION UNIT

ANTENNA

COUPLER

ODU (1+1) HSB with one antenna(13–38 GHz)

ODU (1+1) HSB with notintegrated antenna (7–8 GHz)

Double Polar Antenna

ODU CH 0 ODU CH 1


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

Fig. 179. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

293

03

/3DB 06687 CA AA

340

340

A.2.1 : IDU

The indoor part is composed by one or two units/shelves (see Fig. 178. on page 291):– IDU Main Unit Ch#1– IDU Extension Unit Ch#0

[1] IDU Main UnitThe IDU Main unit is used both in 1+0 and 1+1 configurations.Six different types of IDU Main Unit are envisaged (with different P/Ns):• IDU Main Unit for ETSI market, for ±24 V Power Supply• IDU Main Unit for ETSI market, for ±48/±60 V Power Supply• IDU Main Unit for ETSI market, for ±24/±60 V Power Supply (Full Range)• IDU Main Unit for ANSI market, for ±24 V Power Supply• IDU Main Unit for ANSI market, for ±48/±60 V Power Supply• IDU Main Unit for ANSI market, for ±24/±60 V Power Supply (Full Range)

The IDU Main Unit provides the external interfaces for the 8xE1 (ETSI version) or 8xDS1 (ANSIversion) tributaries, user service channel, housekeeping and summarizing alarms, NMS V11 andG703 interfaces and a telephone jack. It contains the MONOM, the PQECRC and the Power Supplyunits. The MONOM unit manages 8E1/DS1 tributaries, the Mux/Demux and the cable interfacefunctions. The PQECRC unit implements the Equipment and IDU Controller functions.

a ) Software Key on IDU Main unitA Software Key (Flash Card) is always plugged onto the Main board allowing flexibility inchoosing user interfaces. Refer to para.B.2 on page 302 for details.

b ) Optional plug–in unit for IDU Main unitAn optional plug–in unit (alternative between them, with different P/Ns) for:– additional 8xE1 plug–in or 8xDS1 plug–in– or 1xE3 plug–in or 1xDS3 plug–in– or Data plug–in implementing Ethernet interfacescan be plugged onto the IDU Main unit.

[2] IDU Extension UnitThe IDU Extension Unit is used only in 1+1 configurations.Six different types of IDU Extension Unit are envisaged (with different P/Ns):• IDU Extension Unit for ETSI market, for ±24 V Power Supply• IDU Extension Unit for ETSI market, for ±48/±60 V Power Supply• IDU Extension Unit for ETSI market, for ±24/±60 V Power Supply (Full Range)• IDU Extension Unit for ANSI market, for ±24 V Power Supply• IDU Extension Unit for ANSI market, for ±48/±60 V Power Supply• IDU Extension Unit for ANSI market, for ±24/±60 V Power Supply (Full Range)

The IDU Extension Unit contains the MONOE, the Power Supply and the Hitless Switch units.

c ) Optional plug–in unit for IDU Extension unitAn optional plug–in unit (alternative between them, with the same P/Ns of those envisaged forthe IDU Main Unit) for:– additional 8xE1 plug–in or 8xDS1 plug–in– or 1xE3 plug–in or 1xDS3 plug–inmust be plugged onto the IDU Extension unit, when the same type of plug–in unit is equippedon the IDU Main unit .Note: even if equipped on the IDU Main unit, Data plug–in is not envisaged on IDU Extensionunit.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

294

03

/3DB 06687 CA AA

340

340

A.2.2 : ODU

According to the configuration type, one or two electrical ODU are managed in the Outdoor part. Each ODUcontains a PQECRC unit. It implements the ODU controller functions.

A.2.3 : Allowed Equipment Types

This paragraph provides information on the allowed equipment types for all the configurations supportedby ULS NE.In the following tables, the list of allowed equipment types for each physical position, includes the wholeset of possible types, but, according to the NE configuration defined by the managers, only one value willbe present for each physical position.

N.B. Both IDU and ODU shelves are numbered inside a virtual rack (equipmentPosition = 1). All theIDUs, ODUs and contained positions will be numbered accordingly.

[1] Shelves Equipment Types

The following Tab. 18. provides the shelves equipment types allowed for each supported NEconfiguration (see support domain section for the list of supported configurations).The shelves are numbered according to the following sequence rule:• IDU Ch#1• ODU Ch#1• IDU Ch#0• ODU Ch#0

Tab. 18. Shelves Equipment Types

NEConfiguration

MarketType

PositionAllowed Equipment Type

Description

AllowedEquipment

Type

EquipmentLabel

1+0(note 1) 1.1.0.0 IDU Main Shelf IDU–M IDU Ch#1

1+01+0 ETH(note 2)

ETSI1.2.0.0

ODU 1+0 4/16 QAM ETSI ODU–E ODU Ch#1(note 2)

ANSI1.2.0.0

ODU 1+0 4/16 QAM ANSI ODU–A

(note 1) 1.1.0.0 IDU Main Shelf IDU–M IDU Ch#1

ETSI1.2.0.0

ODU 1+0 4/16 QAM ETSI ODU–E ODU Ch#1

1+1 ANSI1.2.0.0

ODU 1+0 4/16 QAM ANSI ODU–A1+1(note 3) (note 1) 1.3.0.0 IDU Extension Shelf IDU–E IDU Ch#0

ETSI1.4.0.0

ODU 1+0 4/16 QAM ETSI ODU–E ODU Ch#0

ANSI1.4.0.0

ODU 1+0 4/16 QAM ANSI ODU–A

(note 1) The equipment types allowed for IDU shelf are market type independent.

(note 2) All the 1+0 configurations.

(note 3) All the 1+1 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

295

03

/3DB 06687 CA AA

340

340

[2] Slots and Sub–slots Equipment Types

The following tables indicate the allowed equipment types for each slot inside each shelf type.

1 ) IDU

IDU–M

Tab. 19. Allowed board/plug–in types in IDU Main shelf

Position Allowed Equipment Type DescriptionAllowed

EquipmentType

Equipment Label

Main Unit ±24 V Supply M24S

1.1.1.0 Main Unit ±48/±60 V Range Supply M4860S IDU/MAIN Ch#11.1.1.0

Main Unit ±24/±60 V Range Supply M2460S

IDU/MAIN Ch#1

8xE1/DS1 plug–in unit P8E1DS1

1.1.1.1 1xE3/DS3 plug–in unit P1E3DS3 IDU/MAIN/<note 1> Ch#11.1.1.1

2xEthernet plug–in unit P2DATAS

IDU/MAIN/<note 1> Ch#1

(note 1) The label is one of the following:– E1, when the 8xE1/DS1 plug–in is provisioned and it configured to work in E1 mode– DS1, when the 8xE1/DS1 plug–in is provisioned and it configured to work in DS1 mode.– E3, when the 1xE3/DS3 plug–in is provisioned and it configured to work in E3 mode– DS3, when the 1xE3/DS3 plug–in is provisioned and it configured to work in DS3 mode.– DATA, when the 2xDATA plug–in is provisioned.

IDU–E

Tab. 20. Allowed board/plug–in types in IDU Extension shelf

Position Allowed Equipment Type DescriptionAllowed

EquipmentType

Equipment Label

Ext. Unit ±24 Supply E24S

1.3.1.0 Ext. Unit ±48/±60 V Range Supply E4860S IDU/EXT Ch#01.3.1.0

Ext. Unit ±24/±60 V Range Supply E2460S

IDU/EXT Ch#0

1.3.1.18xE1/DS1 plug–in unit P8E1DS1

IDU/EXT/<note 1> Ch#01.3.1.11xE3/DS3 plug–in unit P1E3DS3

IDU/EXT/<note 1> Ch#0

(note 1) The label is one of the following:– E1, when the 8xE1/DS1 plug–in is provisioned and it configured to work in E1 mode– DS1, when the 8xE1/DS1 plug–in is provisioned and it configured to work in DS1 mode.– E3, when the 1xE3/DS3 plug–in is provisioned and it configured to work in E3 mode– DS3, when the 1xE3/DS3 plug–in is provisioned and it configured to work in DS3 mode.

2 ) ODU

No slot can be defined inside the Electrical 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

296

03

/3DB 06687 CA AA

340

340

A.2.4 : Remote Inventory Management

The Remote Inventory feature allows to store the information useful to identify the components of theproduct.From management point of view the Remote Inventory data are provided by the following equipmenttypes:– Main Unit (M24S, M4860S, M2460S)– Extension Unit (E24S, E4860S, E2460S)– Ethernet plug–in (P2DATAS)– PDH Tributary optional plugs–in (P8E1DS1, P1E3DS3)– ODU unit (ODU–E, ODU–A)

For all the other equipment types the remoteInventoryStatus columnar object assumes the value“unavailable”.The RI data of each sub–components unit (i.e. MONOM in the IDU, MILOU in the ODU) cannot be seenat SNMP management interface but only by means of factory tools.Also the information about the equipment type can be read from the remote inventory data (‘Unitmnemonic’ field). All the units must be provided in its own remote inventory data this type of information.It is used to identify the actual equipment type and then, eventually, to provide an equipment mismatchalarm, if the equipment type read from remote inventory data is different from the equipment expectedprovided by the managers.If it is not possible to read the Remote Inventory information, a “Card Fail” alarm is declared.

A.3 : Equipment Protection Switching Management

Just one EPS protection scheme is supported. It provides protection both of the PDH multiplexer and ofthe demultiplexer functional blocks.The following Tab. 21. defines the characteristics of this protection scheme.

Tab. 21. Characteristics of the protection scheme

Parameter Type Value

Protection group type 1+1

Switching type Single ended

Restoration criteria Revertive/Non Revertive

Switching condition Equipment failures

Operator commandsLockout spare Forced switch from main to spare Manualswitch from main to spare and vice–versa

The configuration of this protection scheme is performed by the NE in conjunction with the equipmentprovisioning process (declaration of boards).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

297

03

/3DB 06687 CA AA

340

340

A.4 : External Points Management

ULS NE has the capability to monitor 6 input contacts (housekeeping alarms) and 4 output contacts(housekeeping controls).The polarity of each external point can be configured through the SNMP management interface.External output points can be automatically controlled by the agent or manually used by the operator. Inthe first case the event that controls the output state is assigned by the operator. The allowed events aredefined in the following table:

AllowedEvent Id

Allowed Event Allowed Event description

1 Major Alarm OR of critical and mayor alarms

2 Minor Alarm OR of minor and warning alarms

3 Service Affecting Alarm OR of service affecting alarms

4 Line side LOS Alarm OR of PDH tributaries and Ethernet interfaces LOS alarms

5 Cable Loss IDU Alarm OR of cable loss IDU alarms

6 Radio Signal Fail Alarm OR of radio signal fail and HBER alarms

7 Local Defect Indication see Technical Handbook for the primitives

8 Remote NE Failure Indication see Technical Handbook for the primitives

Also the summarizing alarms are managed via SNMP interface. They are managed according to the rulesdescribed in the following table:

IndexConfiguration

UserLabelExternal

StatePolarity Criteria

AutomaticEvent

AutomaticEvent IdIndex

ValueConfiguration

Read–write Read–onlyRead–write

Read–only

Read–only Read–only

5All the 1+0

Fail IDU

6

All the 1+0All the 1+1

on/ offactiveLow/activeHigh

automaticFail ODU

Ch#1 –1

7 All the 1+1

activeHighFail ODU

Ch#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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

298

03

/3DB 06687 CA AA

340

340

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

299

03

/3DB 06687 CA AA

340

340

APPENDIX B : SW ALLOCATION, FLASH CARD AND EQUIPMENT CONTROL

This Appendix presents:– the software allocation in the various parts of the equipment, herebelow– the types of Flash Card and its contents, on page 302– the general characteristics of the ECT and RECT, on page 309.

Fig. 180. herebelow shows the Interfaces for equipment control

Fig. 181. herebelow shows the FLASH CARD position on back side of MAIN unit

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

Ethernet Interfacefor ECT or OS connection

F Interfacefor ECT connection

Flash cardlabel

Equipment ControllerReset pushbutton

Fig. 180. MAIN Unit front side: interfaces for equipment control and Flash–Card–label position

Flash card

Flash card cover

Fig. 181. MAIN Unit back side: Flash Card position

TOP SIDE

CONNECTORSIDE

INSERTION

Fig. 182. Flash Card profile and 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

300

03

/3DB 06687 CA AA

340

340

B.1 : Allocation of equipment and craft terminal software

Fig. 183. herebelow roughly depicts the NE main parts containing the local SW and the interfaces with theOperator (Extension Unit and RT–0 are present in 1+1 configuration and are not equipped in 1+0configuration).

FLASHCARD

EQUIPMENTCONTROLLER

RAM

MONOMSUBUNIT

PQ/ECRC SUBUNIT

F

Ethernet

MAIN UNIT

EXTENSION UNIT

RT–0

ODUCONTROLLER

MONOESUBUNIT

FLASHEPROM

RAM

RT–1

ODUCONTROLLER

FLASHEPROM

RAM

Fig. 183. Equipment main parts containing local SW

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

301

03

/3DB 06687 CA AA

340

340

Once the system has been configured and activated (as explained in Section 1 Installation on page 21),Equipment and Craft Terminal must not necessarily be left connected, because equipment contains all thesoftware necessary for its working.

This equipment local software comprises programs and configuration data. Programs and data aremanaged differently from each other:

a ) SW resident in Equipment Controller and Flash Card

Whole Equipment SW (programs and configuration data) is contained in the Flash Card housed inMAIN unit’s PQ/ECRC sub–unit (the Flash Card contains also the software (programs andconfiguration data) relevant to the peripheral units, i.e., in the figure RTs). See Fig. 181. andFig. 182. on page 299.

This flash card is removable (i.e. replaceable), and the programs can be overwritten by a SWdownload from CT (through F interface) or Network Management Operation System (throughEthernet interface) to the MAIN unit.

More precisely, as shown in Fig. 184. on page 307, the Flash Card contains two independentinstances of the Equipment SW programs (one active, the other stand–by), so that the above citedSW download is actually done toward the stand–by instance, while equipment goes on working withthe SW programs of the active instance. Swapping between the two instances is done only underOperator’s request.

b ) SW resident in Peripheral Units

The Peripheral units (RTs) contain their own local SW (programs and configuration data), housed ina local Flash Eprom (physically not removable). The programs in this local Flash Eprom can beoverwritten by means of a SW download from the Equipment Controller with the sameactive–standby duplication described before for the Equipment Controller.

c ) Equipment Configuration Data

The whole equipment configuration data (together with programs) are stored in the MAIN unitPQ/ECRC sub–unit Flash Card. Refer to point B.2.3 on page 307 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

302

03

/3DB 06687 CA AA

340

340

B.2 : Flash Card


B.2.1 : Flash Card types

A FLASH CARD is plugged into the Main board (see Fig. 181. on page 299) allowing flexibility in choosinguser interfaces as in the following Tab. 22. (6 possible types of Flash card):

Tab. 22. Available Flash cards for 9400AWY Rel.2

Technical Description Technical Code

4E1DS1 4 QAM FLASH CARD 3DB 06571 AA––

4E1DS1 4/16 QAM FLASH CARD 3DB 06572 AA––

8E1/DS1 4 QAM FLASH CARD 3DB 06606 AA––

8E1/DS1 4/16 QAM FLASH CARD 3DB 06607 AA––

4 QAM FLASH CARD 3DB 06573 AA––

16E1/DS1 E3/DS3 4/16QAM FLASH CARD 3DB 06574 AA––

The following tables show the possible combinations of interface types and numbers that can be supportedby each of the six types of flash cards defined in Tab. 22. above:

• Tab. 23. on page 303, to be used when no tributary plug–in is equipped

• Tab. 24. on page 304, to be used when tributary 9–16 E1/DS1 plug–in is equipped

• Tab. 25. on page 305, to be used when tributary E3/DS3 plug–in is equipped

• Tab. 26. on page 306, to be used when Ethernet plug–in is equipped

B.2.2 : Flash Card identification

a ) the Flash Card Technical Code is reported on the label affixed on it;

b ) moreover, the Flash Card Name is affixed on the label present on the front panel of the MainUnit (see Fig. 180. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

303

03

/3DB 06687 CA AA

340

340

Tab. 23. Capacity and modulation for 9400AWY R.2.0 flash cards (IDU basic)

Flash Card NameInt.N# without plug–in (IDU basic)

Flash Card NameInt.N#& type Supported configuration Supported modulation

2E1 1E1…2E1 4 QAM

4E1DS1 4QAM 4E1 1E1…4E1 4 QAM4E1DS1 4QAM

4DS1 1DS1…4DS1 4 QAM

2E1 1E1…2E1 4 QAM

4E1DS1 4/16QAM 4E1 1E1…4E1 4 and 16 QAM4E1DS1 4/16QAM


2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 QAM




2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 and 16 QAM



8DS1 1DS1…8DS1 4 and 16 QAM

2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 QAM

8E1 1E1…8E1 4 QAM


4QAM 8DS1 1DS1…8DS1 4 QAM4QAM ÉÉÉÉÉÉÉÉÉÉÉÉ

16E1ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

naÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

na

ÉÉÉÉÉÉÉÉ

16DS1 ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

na ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

na

ÉÉÉÉÉÉÉÉ

E3 ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ


na

ÉÉÉÉÉÉÉÉ

DS3 ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ


na

2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 and 16 QAM

8E1 1E1…8E1 4 and 16 QAM

16E1/DS1 E3/DS34DS1 1DS1…4DS1 4 QAM

16E1/DS1 E3/DS34/16QAM

8DS1 1DS1…8DS1 4 and 16 QAM4/16QAM

ÉÉÉÉÉÉÉÉ

16E1 ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ


na

ÉÉÉÉÉÉÉÉ



na

ÉÉÉÉÉÉÉÉ



naÉÉÉÉÉÉÉÉ



na

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

304

03

/3DB 06687 CA AA

340

340

Tab. 24. Capacity and modulation for 9400AWY R.2.0 flash cards (with 9–16 E1/DS1 plug–in)

Flash Card NameInt.N#& type

with 9–16 E1/DS1 plug–inFlash Card Name

Int.N#& type Supported configuration Supported Modulation

2E1 1E1…2E1 4 QAM



2E1 1E1…2E1 4 QAM



2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 QAM




2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 and 16 QAM




2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 QAM

8E1 1E1…8E1 4 QAM


4QAM 8DS1 1DS1…8DS1 4 QAM4QAM

16E1 1E1…16E1 4 QAM


ÉÉÉÉÉÉÉÉ



na

ÉÉÉÉÉÉÉÉ



na

2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 and 16 QAM

8E1 1E1…8E1 4 and 16 QAM



8DS1 1DS1…8DS1 4 and 16 QAM4/16QAM

16E1 1E1…16E1 4 and 16 QAM

16DS1 1DS1…16DS1 4 and 16 QAMÉÉÉÉÉÉÉÉ



naÉÉÉÉÉÉÉÉ



na

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

305

03

/3DB 06687 CA AA

340

340

Tab. 25. Capacity and modulation for 9400AWY R.2.0 flash cards (with E3/DS3 plug–in)

Flash Card NameInt.N#& type

with E3/DS3 plug–inFlash Card Name

Int.N#& type Supported configuration Supported Modulation

2E1 1E1…2E1 4 QAM



2E1 1E1…2E1 4 QAM



2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 QAM




2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 and 16 QAM




2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 QAM

8E1 1E1…8E1 4 QAM


4QAM 8DS1 1DS1…8DS1 4 QAM4QAM ÉÉÉÉÉÉÉÉ16E1

ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉna

ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉnaÉÉÉÉ

ÉÉÉÉÉÉÉÉ

16DS1ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

naÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

na

E3 E3 4 QAM

DS3 DS3 4 QAM

2E1 1E1…2E1 4 QAM

4E1 1E1…4E1 4 and 16 QAM

8E1 1E1…8E1 4 and 16 QAM



8DS1 1DS1…8DS1 4 and 16 QAM4/16QAM ÉÉÉÉ

ÉÉÉÉ16E1 ÉÉÉÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉÉÉÉna ÉÉÉÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉÉÉÉna

ÉÉÉÉÉÉÉÉ



na

E3 E3 4 and 16 QAM

DS3 DS3 4 and 16 QAM

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

306

03

/3DB 06687 CA AA

340

340

Tab. 26. Capacity and modulation for 9400AWY R.2.0 flash cards (with Ethernet plug–in)

Int.N#with Ethernet plug–in

Flash Card Name Int.N#& type TDM BW (a)

ETHERNETBW (b)

(a)+ (b)SupportedModulation

2E1 0E1…2E1 2E1…0E1 � 2E1 4 QAM

4E1DS1 4QAM 4E1 0E1…4E1 4E1…0E1 � 4E1 4 QAM4E1DS1 4QAM

4DS1 0DS1…4DS1 4DS1…0DS1 � 4DS1 4 QAM

2E1 0E1…2E1 2E1…0E1 � 2E1 4 QAM

4E1DS1 4/16QAM 4E1 0E1…4E1 4E1…0E1 � 4E1 4 and 16 QAM4E1DS1 4/16QAM


2E1 0E1…2E1 2E1…0E1 � 2E1 4 QAM

4E1 0E1…4E1 4E1…0E1 � 4E1 4 QAM

8E1DS1 4QAM 8E1 0E1…8E1 8E1…0E1 � 8E1 4 QAM8E1DS1 4QAM



2E1 0E1…2E1 2E1…0E1 � 2E1 4 QAM

4E1 0E1…4E1 4E1…0E1 � 4E1 4 and 16 QAM

8E1DS1 4/16QAM 8E1 0E1…8E1 8E1…0E1 � 8E1 4 and 16 QAM8E1DS1 4/16QAM


8DS1 0DS1…8DS1 8DS1…0DS1 � 8DS1 4 and 16 QAM

2E1 0E1…2E1 2E1…0E1 � 2E1 4 QAM

4E1 0E1…4E1 4E1…0E1 � 4E1 4 QAM

8E1 0E1…8E1 8E1…0E1 � 8E1 4 QAM


4QAM 8DS1 0DS1…8DS1 8DS1…0DS1 � 8DS1 4 QAM4QAM

16E1 0E1…8E1 16E1…0E1 � 16E1 4 QAM


E3 ÉÉÉÉÉÉÉÉÉÉÉÉ

na ÉÉÉÉÉÉÉÉÉÉÉÉ

na ÉÉÉÉÉÉÉÉÉÉ

na 4 QAM

DS3ÉÉÉÉÉÉÉÉÉÉÉÉ

na 51,184Mbps 51,184Mbps 4 QAM

2E1 0E1…2E1 2E1…0E1 � 2E1 4 QAM

4E1 0E1…4E1 4E1…0E1 � 4E1 4 and 16 QAM

8E1 0E1…8E1 8E1…0E1 � 8E1 4 and 16 QAM

16E1/DS1 E3/DS34DS1 0DS1…4DS1 4DS1…0DS1 � 4DS1 4 QAM


8DS1 0DS1…8DS1 8DS1…0DS1 � 8DS1 4 and 16 QAM4/16QAM

16E1 0E1…8E1 16E1…0E1 � 16E1 4 and 16 QAM

16DS1 0DS1…8DS1 16DS1…0DS1 � 16DS1 4 and 16 QAM

E3 ÉÉÉÉÉÉÉÉÉÉÉÉ

na ÉÉÉÉÉÉÉÉÉÉÉÉ

na ÉÉÉÉÉÉÉÉÉÉ

na 4 and 16 QAM

DS3 ÉÉÉÉÉÉÉÉÉÉÉÉ

na 51,184Mbps 51,184Mbps 4 and 16 QAM

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

307

03

/3DB 06687 CA AA

340

340

B.2.3 : Flash Card content

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

SWCOMMITVERSION(ACTIVE)

SWSTAND–BYVERSION(not active)

MIB

NE networkrouting data

Baseconfiguration

SW instances

NE Data

Fig. 184. Flash Card content

[1] 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.D.3.2 on page 331.

As supplied by Alcatel factory:

• usually only the SW COMMIT VERSION is present

• unless differently required by Customer, the SWP–version downloaded in Factory is the mostrecently released at the date of Flash Card delivery to the Customer.

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

[2] NE data

N.B. as shown in Fig. 184. above, differently from SW instances, NE data are present as singleinstances in the Flash Card.

a ) Base configuration

It is defined by Flash Card Technical Code.

It is not changeable, but with Flash Card upgrade (see para.1–5.2 on page 82).

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

308

03

/3DB 06687 CA AA

340

340

b ) MIB

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

As supplied by Alcatel factory:– if the Flash card is supplied together with 9400AWY equipment, NE configuration data are

consistent with the actual HW configuration– if the Flash card is supplied alone, usually and unless differently required by Customer,

NE configuration data are set to default values

MIB can be saved as a file in the Craft Terminal environment, as well can be restored in the FlashCard retrieving this file from the Craft Terminal, as described in detail in Chapter 2–13 – MIBManagement on page 237.

c ) NE network routing data

Defined by Craft Terminal, they are:1. Local configuration ⇒ System’s local address2. NTP server configuration

3. Interface configuration ⇒ NMS configuration ⇒ Ethernet configuration

4. IP configuration ⇒ IP Static Routing configuration ⇒ OSPF AREA configuration

All those listed parameter are NOT stored into the MIB file because considered unique to aparticular system in a network and are NOT meant to be reproduced on other systems in thesame network because will cause conflicts in the supervision network centre.

As supplied by Alcatel factory:– if, before delivery, Customer communicates the NE network routing data values, they are

stored in the supplied Flash card by Factory– otherwise, the NE network routing data are set to default values.

[3] System restart

The system restart (reloading of all RAMs present in the system with information stored in the FlashCard) is without traffic interruption and is carried out:• after the activation of a new SWP• after power off/on• after EC/OC reset (manual of after new SWP activation)• after plug–in insertion

[4] FPGA download

As a whole, the correct performance of a certain SWP is granted if the system software workstogether with the FPGAs’ SW versions specifically required by the SWP itself. When a new SWP isloaded into the NE, the SW versions present in the equipped FPGA may not be consistent with thoseexpected, so FPGA upgrade could be necessary.When a new SWP is loaded from ECT into the ULS NE, also the SW images of FPGAs are loadedinto the PQ/ECRC. Each of these SW images is downloaded automatically toward the relevant FPGAonly in case the FPGA version currently running is lower than that made available by the new SWP.The FPGA version comparison and the possible FPGA download are without traffic interruption andare launched every time a system restart is carried out.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

309

03

/3DB 06687 CA AA

340

340

B.3 : Equipment control


B.3.1 : Interfaces (see Fig. 180. on page 299):

• The NE can be controlled by the OS (e.g. Alcatel 1353SH) through the Ethernet interface.

• ECT (Equipment Craft Terminal, briefly Craft Terminal) can be connected to the MAIN unitthrough a RS232 interface (F interface). This connection can be:

– local (ECT) through a suitable cable supplied with the equipment, or remote (RECT) asexplained in following para.B.3.3 and B.3.4 on page 309

– remote through a ECT–equipment connection via public switched telephone network, asexplained in Appendix C on page 311.

B.3.2 : Operator–Equipment Interaction

The Local Operator can manage the Equipment software programs and most configuration datathrough the Equipment Craft Terminal 1320CT connected to the F or Ethernet OS interface (seeFig. 183. on page 300 and Fig. 180. on page 299).The Craft Terminal characteristics (computer configuration) are listed in chapter 4–2 on page 271.The Craft Terminal is a project in charge of the local management of single network elements,providing ITU– compliant Information Model Interface to the Network Element.Multiple NE management up to 128 Network elements is possible obtaining a remote Craft Terminalapplication.

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

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

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.This Operator’s Handbook deals with the EML–ULS views of the Craft Terminal, which directly allowsto 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 on page 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

310

03

/3DB 06687 CA AA

340

340

B.3.3 : ECT

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

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

B.3.4 : RECT

The Remote Equipment Craft Terminal is a feature only present in the Single NE Link architecturewhich allows the local operator, using an ECT connected to the F 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 NEpertaining to different areas (assuming that the DCN network has been correctly designed and henceinter–area communication 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 (128).

The RECT features and limitations are briefly the following:

1 ) The RECT function provides a remote login facility similar to those offered by an OS to manageseveral configured NEs, included the local one.

2 ) The contemporaneous presence of the RECT function and an OS is possible. The accessdisable flag avoids access conflict between the OS and both RECT and ECT on someoperations as configuration modification and remote control with access filtering.

3 ) The NE which may be remotely controlled by a RECT must be configured and must be loadedwith the same SW version supporting the RECT function. A NE not supporting RECT functionshall refuse the incoming association issued by a RECT and the ECT displays only localinformation.

4 ) Only three RECTs shall be active at a time over one NE. The coexistence of ECTs and RECTsin the whole network is guaranteed since the conflict in configuring the NEs is solved locally bythe NE itself.

5 ) The operator, through the RECT function, is able to see the alarm synthesis of the wholenetwork .

6 ) In a network the maximum number of NEs equipped with the RECT function are 128. This valueidentifies what it is understood as ”small network” for which the RECT function may replace theElement 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

311

03

/3DB 06687 CA AA

340

340

APPENDIX C : ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHEDTELEPHONE NETWORK

C.1 : Introduction

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. 185. here below.

This kind of remote control is possible for a single equipment as well as for a whole subnetwork.

��

��

��

��

��

��

��

F Interface

Port COM

��

��

Fig. 185. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

312

03

/3DB 06687 CA AA

340

340

C.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.4–2.1 on page 271

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

313

03

/3DB 06687 CA AA

340

340

C.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

TDRD

DTRDSRRTSCTSGND

DCDTD

RDRTSCTSDSRDTRGND

1

346785

8

56207

2 3

4

2

Fig. 186. ECT–Local external Modem cable

Remote Modem (DCE)Cannon 25 pins male

F Interface (DCE)Cannon 9 pins male

TDRD

RTSCTSDSRCTSGND

TDRDRTSCTSDSRDTRGND

2 3456

207

32786

54

Fig. 187. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

314

03

/3DB 06687 CA AA

340

340

C.4 : Modem setting

C.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. 185. on page 311 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. 186. onpage 313.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

315

03

/3DB 06687 CA AA

340

340

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

316

03

/3DB 06687 CA AA

340

340

C.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. 188. 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. 188. TD–32 AC modem dip–switch setting

2 ) Connect the local modem to the PC/ECT with the cable of Fig. 186. on page 313.

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

317

03

/3DB 06687 CA AA

340

340

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

C.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

318

03

/3DB 06687 CA AA

340

340

C.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. 185. on page 311 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. 187. on page 313.

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. 186. on page 313.) 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

319

03

/3DB 06687 CA AA

340

340

C.7 : Changing the ECT–equipment connection speed

C.7.1 : Introduction

This feature is meant to use modems with speed different from that documented in previous paragraphs,giving the possibility to configure the ECT connection through modem (speed values: 9600, 19200, 38400,56000) with automatic management of modem set–up and phone call at ECT start–up.

As a matter of fact, this feature is not enough to set up the desired configuration.

To make change operative, the following operations should be necessary:

– at equipment side, special pshell text commands must be forwarded through a special cable to beplugged inside the equipment

– at PC side, the configuration must be set–up as explained in the following para.C.7.2 on page 320.

The default speed is 38400 and must not be changed by Customer !

Customers who need the change of modem speed must require theoperation to be performed by the Technical Assistance Center (TAC) ofrelevant Alcatel Selling or Supporting Unit.

DO NOT ATTEMPT TO USE THIS FEATUREWITHOUT TAC ASSISTANCE.

YOU COULD CAUSEUNRECOVERABLE ECT INACCESSIBILITY.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

320

03

/3DB 06687 CA AA

340

340

C.7.2 : Configuration at PC side

N.B. Please read carefully paragraph Introduction on page 319.

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. 189. opens.

Fig. 189. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

321

03

/3DB 06687 CA AA

340

340

APPENDIX D : DOCUMENTATION GUIDE

This appendix contains all information regarding:

– this handbook, herebelow

– the Customer Documentation set this handbook belongs to, on page 327

– general on Alcatel Customer Documentation, on page 330

D.1 : Handbook guide

This paragraph contains all information regarding this handbook:

– Handbook applicability on page 322

– Purpose of the handbook on page 323

– Handbook history on page 324

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

322

03

/3DB 06687 CA AA

340

340

D.1.1 : Handbook applicability

a ) Product-release applicabilityThe current edition of this handbook applies to the 9400AWY Rel.2 in the following RF bandconfigurations:

Tab. 27. 9400 AWY family

PRODUCT BAND (GHz)

9470AWY 7–8

9413AWY 13

9415AWY 15

9418AWY 18

9423AWY 23

9425AWY 25

9428AWY 28

9438AWY 38

b ) NE applicabilityThe current edition of this handbook applies to the following Network Elements (NE): ULS

c ) SWP Version applicabilityThe current edition of this handbook applies to the following Software Package Releases (SWP) andSWP versions:

SWP ReleaseSWP P/N

REF.(x) in Tab. 15. on page 270SWP Version

(N.B.)

SWP 9400AWY R.2.0 CD–ROM REF.(a) V2.0.0 & V2.0.1

SWP 9400AWY R.2.0.2 CD–ROM REF.(b) V2.0.2

N.B. For the meaning of SWP Release and Version, please refer to para.D.3.2 on page 331.The indication of the Versions in this handbook has the following meaning:this handbook applies starting from the Versions stated in this table, but it could also apply tosubsequent Versions for the following reasons:

a ) the Operator Handbook is not modified, unless the new version distributed to theCustomers comprises changes to the man–machine interface, or even in the presence ofminor changes that do not affect negatively the understandability of the proceduresdescribed therein (e.g. a ”button” moved internally to a screen);

b ) furthermore, if the screens contained in the handbook show the ”version–release” of the”product–release”, then they are not replaced in the subsequent versions of handbook iftheir contents 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

323

03

/3DB 06687 CA AA

340

340

D.1.2 : Purpose of the handbook

This handbook belongs to the Customer Documentation set envisaged for the equipment specified in para.D.1.1 on page 322.Please refer to para.D.2 on page 327 to have the list and description of such Customer Documentationset.

This handbook describes the operation and maintenance activities the operators can carry out accordingthe specific software application(s) referred to in this handbook (see para. D.1.1 on page 322).

This handbook must be used together with the associated Technical Handbook and, with someexceptions, does not replicate information contained into it.

In particular, all cautions relevant to safety on rules for EMC and ESD, as well as warnings regardingoperations that may cause damages to the equipment, are not duplicated here, but must be retrieved fromthe Technical Handbook.

When using this handbook, it is assumed that the Operators know:

• the structure (hardware composition) and all the possible operating modes of the equipment(product-release) that this handbook refers to.

• how to use a PC and the Windows environment applications.

Before accessing other sections of this handbook, read completely this section in order to have informationon:

– SWP P/Ns and composition

– how to access the other sections of this handbook according to the SWP type (if more than oneenvisaged)

– how to manage Craft Terminal SW and Equipment SW for new installations or for upgrading previousinstallation to the new SW version.

– how to make ECT–equipment remote connection on Public Switched Telephone Network.

The document that should be read before starting this document is:

– 9400AWY Rel.2.0 Technical Handbook

N.B. In any case, the Technical Handbook must be always available to the Operator in chargeof the equipment software management, as it contains information and documents that areused in the procedures described in this manual (e.g. the hardware setting documents, theunit replacement procedures, etc.).

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 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

324

03

/3DB 06687 CA AA

340

340

D.1.3 : Handbook history

D.1.3.1: List of the editions and modified parts

The first and the two most recent editions of the document are indicated in the table of contents. Changeswith respect to the previous edition are pointed out by revision bars.The following Tab. 28. indicates the handbook parts new and modified with respect to the previousedition.Legend

n = new part m = modified part blank= part unchanged

Tab. 28. Handbook historyHANDBOOK EDITION ⇒ 01 02 03 04 05

FRONT MATTER n

Preliminary information n m

Handbook applicability, purpose and history n m

Handbook structure n m m

Safety, EMC, EMF, ESD norms and equipment labelling n m m

Cautions to avoid equipment damage n

Quick guide n m m

SECTION 1: INSTALLATION n m m

1–1General on equipment installation and SWP installation andmanagement

n m m

1–2 SWP installation in PC environment n m m

1–3 SWP download toward NE n m m

1–4CT & NE Upgrade to a newer SWP ’version’ (same SWP’release’)

n m

1–5 System hardware upgrade n m

SECTION 2: NE MANAGEMENT n

2–1 General introduction on views and menus n m m

2–2 Configuration n m m

2–3 Equipment n m

2–4 Line Interface n m m

2–5 Radio n m m

2–6 External points n

2–7 Supervision n m

2–8 Protection schemes n m

2–9 Loopbacks n m

2–10 Diagnosis n m

2–11 Performance Monitoring n m

2–12 Software Download n m

2–13 MIB Management n

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

325

03

/3DB 06687 CA AA

340

340

Tab. 28. Handbook historyHANDBOOK EDITION ⇒ 0504030201

SECTION 3: NE MAINTENANCE n m

3–1 Troubleshooting n m m

3–2 Spare Flash Card management and replacement proceduresÇÇÇÇÇÇ

ÇÇÇÇÇÇ

n

table continues

SECTION 4: SWP DESCRIPTION AND VERSIONS n m m

4–1 SWP REG.9400AWY R.2.0 description n m m

4–2 SWP REG.9400AWY R.2.0 V.2.0.0 specific information n m m

4–3 SWP REG.9400AWY R.2.0 V.2.0.1 specific information ÇÇÇÇÇÇ

n m

4–4 SWP REG.9400AWY R.2.0 V.2.0.2 specific information ÇÇÇÇÇÇ

ÇÇÇÇÇÇ

n

SECTION 5: APPENDICES n m

A Equipment description and components n m m

B SW allocation, Flash Card and equipment control n m m

CECT–Equipment connection via public switched telephonenetwork

n

D Documentation Guide n m m

E Acronyms and abbreviations n

F Glossary of terms n

D.1.3.2: Notes on Ed.01

– Draft editions neither validated nor officially released issue, for internal validation purposes:• Ed.01A–DRAFT created on April 5th, 2005.

– Ed.01 created on May 10th, 2005 is the first released and validated version of the handbook,associated to SWP version V2.0.0.


– Draft editions neither validated nor officially released issue, for internal validation purposes:• Ed.02A–DRAFT created on September 26th , 2005.

– Ed.02 created on November 9th, 2005 is the second released and validated version of the handbook,and has been done to align the handbook to the new features of SWP version V2.0.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

326

03

/3DB 06687 CA AA

340

340


– Draft editions neither validated nor officially released issue, for internal validation purposes:• Ed.03A–DRAFT created on December 12th, 2005• Ed.03B–DRAFT created on December 22nd, 2005• Ed.03C–DRAFT created on January 16th, 2006

– Ed.03 created on February 6th, 2006 is the third released and validated version of the handbook, andhas been done for the following major changes:• This issue has been done to align the handbook to the new features of SWP version V2.0.2

(N.B.).Nevertheless, handbook can be used also in association with SWP former versions V2.0.0 toV2.0.1.Changes related to this new version have been introduced throughout the handbook, wherenecessary.

• Besides those strictly associated to new SWP version V2.0.2, following additional majorchanges have been introduced:– throughout the handbook:

• the documentation distribution policy has been modified (see appendixDocumentation Guide)

• ’FULL FLEXIBLE’ flash card name changed to ’16E1/DS1 E3/DS3 4/16QAM’• all references to 9411AWY (11 GHz) and 9432AWY (32 GHz) products have been

removed (development frozen or delayed)• all references to SIBDL application (unused in 9400AWY environment) have been

cancelled• some operative instructions have been improved, according to suggestions and

requests from field operation teams– in section INSTALLATION:

• Chapters 1–1 – General on equipment installation and SWP installation andmanagement (shifted from section APPENICES), 1–2 – SWP installation in PCenvironment and 1–3 – SWP download toward NE improved and corrected

• redefined Chapter 1–5 – System hardware upgrade containing:– new procedure for Upgrade from 1+0 to 1+1 configuration– procedure for Flash Card upgrade, fully revised

– in section NE MANAGEMENT:• description of OSPF Area configuration (para.2–2.2.4.2 on page 118, and on page

139 of Quick Configuration Procedure) corrected• in chapter 2–5 – Radio, the tables for ATPC Rx Threshold setting have been

updated– section NE MAINTENANCE improved, in particular:

• paragraph Warnings on the troubleshooting improved• new chapter 3–2 Spare Flash Card management and replacement procedures

Errors found in previous edition have been corrected.Revision bars point out major (listed above) and minor (not listed above) modifications of Ed.03 withrespect to ED.02.Revision bars in correspondence of empty lines or empty table rows, point out parts eliminated orshifted in other places of the handbook.

N.B. This edition is validated in conjunction with SWP versions V2.0.0 to V2.0.2 only.For additional feature and SWP–version relationship, please refer to Tab. 1. on page14.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

327

03

/3DB 06687 CA AA

340

340

D.2 : Documentation set description

This paragraph contains all information regarding the 9400AWY Rel.2.0 Customer Documentation andis organized as follows:

– 9400AWY Rel.2.0 Customer Documentation herebelow– Additional documentation for 1320CT platform on page 329

D.2.1 : 9400AWY Rel.2.0 Customer Documentation

This paragraph lists and briefly describes the documentation set envisaged for 9400AWY Rel.2.0.

Please refer to following para.D.3 on page 330 for a general description of Alcatel CustomerDocumentation system.

The list of handbooks given here below is valid at the issue date of this Handbook andcan be changed without any obligation for ALCATEL to update it in this Handbook.

The standard Customer Documentation for 9400AWY Rel.2.0 is in the English language and is distributedto Customers only by the following CD–ROM:

Tab. 29. 9400AWY Rel.2.0 Documentation CD–ROM

REF Technical Description Technical Code NOTES

DCP 9400AWY 2.0 CD_ROM 3DB 06687 AA**

[A] Contains, in electronic format (ADOBE ACROBAT pdf files), all handbooks listed inTab. 30. on page 328.

N.B.

a ) Standard supplyOne copy of the 9400AWY Rel.2.0 CD–ROM is automatically delivered to Customer together withthe equipment it refers to (one copy for each terminal).As 9400AWY Rel.2.0 CD–ROM is a standard commercial item, additional copies can be ordered anddelivered as any other Alcatel 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 and must not be copied, reproduced or disclosed to a third party without written consent.

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

328

03

/3DB 06687 CA AA

340

340

Tab. 30. Handbooks contained in the 9400AWY Rel.2.0 Documentation CD–ROM

N.B. The P/Ns of handbooks is just for Alcatel internal management only. As specified in point a )on page 327, they do not represent Commercial item P/Ns.

REF HANDBOOK DOCUMENT P/N NOTES

9400 AWY Rel. 2.0 Technical Handbook 3DB 06687 BAAA

[B] Provides information regarding AWY equipment description and composition, stationlayouts, hardware setting documentation and maintenance.

[C]

9400 AWY Rel.2.0CT Operator’s Handbook SWP 2.0

3DB 06687 CAAA this handbook

[C]Provides AWY SWP screens and operational procedures for Equipment SW management andmaintenance.

[D]9400 AWY Rel.2.0 Installation Handbook 3DB 06687 DAAA

[D]Provides information regarding Equipment installation, according to Alcatel WTD LAB. rules.

9400 AWY Rel.2.0 Line–up Guide 3DB 06687 EAAA

[E] Provides information regarding equipment line up and commissioning, according to AlcatelWTD LAB. rules.

Interference investigation procedure 3DB 04165 EAAA

[F] 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

329

03

/3DB 06687 CA AA

340

340

D.2.2 : Additional documentation for 1320CT platform

Tab. 31. Documentation common to Alcatel Network Elements using 1320CT platform

REFCT–K

Version(N.B.)

ITEM P/N NOTES

[G]� 3.0.1

DCP 1320 CT 3.x CD_ROM EN

3AL 79552 AAAA[G]

Contains, in electronic format, the 1320 CT Operator’s Handbook REF.[H] to [J]

[H]

� 3.0.11320CT Rel.3.xBasic Operator’s Handbook

3AL 79551 AAAA

[H]Provides general information and operational procedures common to all 1320CT (Craftterminal) of Alcatel InfoModel Network Elements.

[I]

� 3.0.1AS Rel.6.5Operator’s Handbook

3AL 88876 AAAA

[I]Provides detailed information and operational procedures regarding the alarm Surveillancesoftware embedded in the 1320CT software package.

[J]

� 3.0.1ELB Rel.2.xOperator’s Handbook

3AL 88877 AAAA

[J]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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

330

03

/3DB 06687 CA AA

340

340

D.3 : General on Alcatel Customer Documentation

This paragraph describes in general the Alcatel Customer Documentation system, details the associationbetween the product levels and the associated documentation, and explains Customer Documentationcharacteristics as well as the policies for its delivery and updating.

This paragraph is fully applicable to the 2nd generation Radio Product families of Alcatel WTD (WirelessTransmission Division) only.

D.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 Laboratory design and Installation Dept. choices. Inparticular:

• 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

331

03

/3DB 06687 CA AA

340

340

D.3.2 : Product levels and associated Customer Documentation

See Fig. 191. on page 332.

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. 9400 AWY 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 and Rel.2.0 are two 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

See Fig. 190. herebelow.

A SWP is identified by the “configuration” name and by the “version” number (tree digits).

The version’s first digit corresponds to the “product–release” number first digit; the second digitidentifies, together with the first, the SWP “release”.

The third digit of the SWP version identifies the Patch Level of the SWP Release.

SWP version

SWP Release

ProductRelease’sfirst digit

Patch Level

SWP evolution for bug fixing purposesand/or minor additional features

1. 0. 7and/or minor additional features(same SWP Release within same Product–Release) 1. 0. 9

SWP evolution for main additional features(new SWP Release within same Product–Release)

1. 0. 7(new SWP Release within same Product–Release)(N.B. see next page) 1. 1. 2

SWP evolution for additional features1. 0. 7

SWP evolution for additional features(new SWP Release of a new Product–Release) 2. 0. 2

Fig. 190. Example of SWP Release and Version numbering

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

332

03

/3DB 06687 CA AA

340

340

N.B. Sometimes, different SWP Releases (within the same Product–Release) are commerciallydistinguished by different names, e.g. :

SWP version SWP–Release commercial name

1.0.x 1.0

1.1.x 1.0B

1.2.x 1.0C

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)

PRODUCT

PRODUCT–RELEASE 1.0 PRODUCT–RELEASE 2.0evolution

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. 191. 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

333

03

/3DB 06687 CA AA

340

340

APPENDIX E : ACRONYMS AND ABBREVIATIONS

N.B. For the explanation of the acronyms of the alarms refer to Section MAINTENANCEpara.3–1.4.1 Alarm synthesis indication on page 250.

ACD: Access Control Domain

ADM: Add/Drop Multiplexer

AIS: Alarm Indication Signal

ALR: Automatic Laser Restart

ALS: Automatic Laser Shutdown

ANSI: American National Standard Institute

APS: Automatic Protection Switching

AS: Alarm Surveillance

ASAP: Alarm Severity Assignment Profile

ATM: Asynchronous Transfer Mode

ATPC: Automatic Transmit Power Control

AVC: Attribute Value Change

BBE: Background Block Error

BER: Bit Error Rate

BIP: Bit Interleaved Parity

BKPV: Back Plane Version

CPI: Control Point Input

CPO: Control Point Output

CRC: Cyclic Redundancy Check

CSES: Consecutive Severely Errored Second

CD: Current Data

CD–ROM: Compact Disc Read Only Memory

CCITT: Telegraph and Telephone International Consultative Committee

CPU: Central Processor Unit

CT: Craft Terminal

DEM: DEModulator

DTE: Data Terminal Equipment

DTMF: Dual Tone Multi Frequency

EB: Errored Block

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

334

03

/3DB 06687 CA AA

340

340

EC: Equipment Controller

ECC: Embedded Communication Channels

ECT: Equipment Craft Terminal

EFD: Event Forwarding Discriminator

ELB: Event Log Browsing

EML: Element Management Layer

EOW: Engineering Order Wire

EPS: Equipment Protection Switch

ES: Errored Second

ETSI: European Telecommunication Standard Institute

EW: Early Warning

FAD: Functional Access Domain

FD: Frequency Diversity

FEC: Forward Error Corrector

FSO: Free Space Optics

FTP: File Transfer Protocol

GA: General Alarm

GNE: Gateway Network Element

HCS: Higher order Connection Supervision

HBER: High Bit Error Rate

HD: History Data

HET: HETerofrequency

HMI: Human Machine Interface

HS: High Speed

HST: Hot STandby

ID: Identifier

IDU: InDoor Unit

ISO: International Standards Organization

IEEE: Institute of Electrical and Electronics Engineers

IM: Information Manager

IP: Input Port or Internet Protocol

ISO: International Standards Organization

Kbit/s: Kilobits per second

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

335

03

/3DB 06687 CA AA

340

340

LAC: Local Access Control

LAN: Local Area Network

LBER: Low Bit Error Rate

LCS: Lower Order Connection Supervision

LO: Local Oscillator

LOF: Loss Of Frame

LOS: Loss Of Signal

LS: Low Speed

MAC: Media Access Control

Mbit/s: Megabits per seconds

MIB: Management Information Base

MLR: Manual Laser Restart

MOC: Managed Object Class

MOD: Modulator

MSp: Manual Switch to protecting channel

MSw: Manual Switch to working channel

NE: Network Element

NML: Network Management Layer

NMS: Network Management System

NSA: Non Service Affecting

NTP: Network Time Protocol

OBPS: On Board Power Supply

OC_F: ODU Controller_FSO

OC_R: ODU Controller_Radio

ODU: OutDoor Unit

OH: OverHead

OP: Output Port

OS: Operation System

OSI: Open Systems Interconnection

OSPF: Open Shortest Path First

PDH: Plesiochronous Digital Hierarchy

PI: Physical Interface

PLL: Phase Locked Loop

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

336

03

/3DB 06687 CA AA

340

340

PM: Performance Monitoring

PPP:Point to Point Protocol

PSU: Power Supply Unit

QAM: Quadrature Amplitude Modulation

QOS: Quality Of Service

RAI: Remote Alarm Insertion

RAM: Random Access Memory

RC: Radio Controller

RDI: Remote Defect Indication

RECT: Remote Equipment Craft Terminal

REI: Remote Error Indication

RF: Radio Frequency

RPS: Radio Protection Switching

RS: Reed Solomon

RT: Transceiver

SA: Service Affecting

SC: Service Channel or System Controller

SD: Signal Degrade

SDH: Synchronous Digital Hierarchy

SES: Severly Errored Second

SF: Signal Fail

SSF: Server Signal Fail

SWP: SoftWare Package

TCP: Transmission Control Protocol

TDM: Time Division Multiplexer

TMN: Telecommunications Management Network

TN: Telecommunications Network

TP: Termination Point

UAS: UnAvailable Second

UAT: UnAvailable Time

URU: Underlying Resource UnAvailable

USM: User Service Manager

WST: Way Side Traffic

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

337

03

/3DB 06687 CA AA

340

340

APPENDIX F : 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

338

03

/3DB 06687 CA AA

340

340

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

339

03

/3DB 06687 CA AA

340

340

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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

340

03

/3DB 06687 CA AA

340

340

END OF DOCUMENT

3DB 06687 CAAA Ed.03

Craft Terminal Operator’s Handbook

Alcatel 9400AWYRel.2.0

7–8–13–15–18–23–25–28–38 GHzshort–haul low/medium capacity digital microwave radio links

SWP 9400AWY R.2.0SWP 9400AWY R.2.0.2


Documentation set for 9400AWY Rel.2.0

The standard Customer Documentation for 9400AWY Rel.2.0 is in the English language and is distributedto Customers only by the following CD–ROM:

CD–ROM TITLE Technical Code Commercial Code

DCP 9400AWY 2.0 CD_ROM 3DB 06687 AA** 3EJ 14535 AAAA

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

Document TitleDocument

Technical CodeNotes

9400AWY Rel.2.0 Technical Handbook 3DB 06687 BAAA

9400AWY CT Operator’s Handbook SWP 2.0 3DB 06687 CAAA this handbook

9400AWY Rel.2.0 Installation Handbook 3DB 06687 DAAA

9400AWY Rel.2.0 Line–up Guide 3DB 06687 EAAA

Interference investigation procedure 3DB 04165 EAAA

For further information, please refer to Appendix Documentation guide in section APPENDICES

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

CONTENTS SEPARATOR

FRONT MATTER:– TABLE OF CONTENTS– LIST OF FIGURES AND TABLES– PRELIMINARY INFORMATION– SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING– CAUTIONS TO AVOID EQUIPMENT DAMAGE– QUICK GUIDE

SECTION 1: INSTALLATION 1

SECTION 2: NE MANAGEMENT 2

SECTION 3: NE MAINTENANCE 3

SECTION 4: SWP DESCRIPTION AND VERSIONS 4

SECTION 5: APPENDICES 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

Y 1

03

RELEASED

/3DB 06687 CAAA TQZZA

4

4

QUESTA PAGINA NON VA INSERITA NEL MANUALETHIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

COD.MANUALE HDBK P/N: 3DB 06687 CAAA Ed.039400AWY Rel.2.0SWP 9400AWY R.2.0 & R.2.0.2C.T. OPERATOR’S HANDBOOK

ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (source & pdf)

– No PAGINE TOTALI PER ARCHIVIAZIONE: 342+4 = 346– DIMENSIONE BINDER SORGENTE (du –ks): 450.697 Mbyte

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING– 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

fasestep

No pagine(facciate)

numeratenumbered

step (facciate)No pages da from a to

1 TARGHETTE - LABELS

2 FRONTESPIZIO - FRONT 2

3 PARTE INIZIALE – FRONT MATTER ⇒ 1/340 20/340

4 INSERIRE SEPARATORE ’1’ - INSERT SEPARATOR ’1’

5 SECTION 1: INSTALLATION ⇒ 21/340 88/340


7 SECTION 2: NE MANAGEMENT ⇒ 89/340 242/340


9 SECTION 3: MAINTENANCE ⇒ 243/340 266/340


11 SECTION 4: SWP DESCRIPTION AND VERSIONS ⇒ 267/340 286/340


13 SECTION 5: APPENDICES ⇒ 287/340 340/340

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 342

TOTALE FOGLI A4 TOTAL A4 SHEETS: 171

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

docu

men

t, us

e an

d co

mm

unic

atio

n of

its

cont

ents

not p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

Y 2

03

RELEASED


4

4

QUESTA PAGINA NON VA INSERITA NEL MANUALETHIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

WTDSite

Originators

VIMERCATE

:

Domain

9400AWY REL.2.0

Division

SWP 9400AWY R.2.0&2.0.2

Rubric

TypeDistribution Codes Internal External

::::

9400AWY REL.2.0SWP 9400AWY R.2.0 & 2.0.2 SWP 9400AWY R.2.0 C.T. OPER.HANDBOOK

:

E.CORRADINI

Approvals

NameApp.

App.Name

V.FOSSATI

P.CREMONESI R.PELLIZZONI

PUBLISHING NOTES

• Labels are done according to A-Italy binder format.• Source files and printable files of this handbook are archived in PDM:

– Source files: ALICE 6.10 ARCHIVED BY GAPI 4.1.3– Printable file: PDF file must be opened with ACROBAT Reader Version 5.0 at least.

(N.B. : it has been created with ACROBAT DISTILLER 7.0)

3DB 06687 CAAAEd.039400AWY Rel.2.0

SWP 9400AWY R.2.0 & R.2.0.2

7–8–13–15–18–23–25–28–38 GHzshort–haul low/medium capacity digital microwave radio linksC.T. OPERATOR’S 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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

Y 3

03

RELEASED


4

4

9400AWY Rel.2.07–8–13–15–18–23–25–28–38 GHz

short–haul low/medium capacity digital microwave radio links

SWP 9400AWY R.2.0 & R.2.0.2

C.T. OPERATOR’S HANDBOOK


VOL.1/1

9400AWY Rel.2.07–8–13–15–18–23–25–28–38 GHz


SWP 9400AWY R.2.0 & R.2.0.2

C.T. OPERATOR’S HANDBOOK


VOL.1/1

9400AWY Rel.2.07–8–13–15–18–23–25–28–38 GHz

short–haul low/medium capacity digital microwave radio linksSWP 9400AWY R.2.0 & R.2.0.2

3DB 06687 CAAA Ed.03 C.T. OPERATOR’S HANDBOOK VOL.1/1

9400AWY Rel.2.07–8–13–15–18–23–25–28–38 GHz short–haul low/medium capacity digital microwave radio links

SWP 9400AWY R.2.0 & R.2.0.2 3DB 06687 CAAA Ed.03 C.T. OPERATOR’S HANDBOOK VOL.1/1

9400AWY Rel.2.07–8–13–15–18–23–25–28–38 GHz


SWP 9400AWY R.2.0 & R.2.0.2

3DB 06687 CAAA Ed.03 C.T. OPERATOR’S HANDBOOK VOL.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 p

erm

itted

with

out w

ritte

n au

thor

izat

ion

from

Alc

atel

.

ED

1AA

000

14 0

004

(900

7) A

4 –

ALI

CE

04.

10

Y 4

03

RELEASED


4

4

FINE DEL DOCUMENTO INTERNO – END OF INTERNAL DOCUMENT

Awy Operator Swp20 Ed03

Documents

Transcript of Awy Operator Swp20 Ed03