alcatel 9400awy 9400fso - nokia
TRANSCRIPT
3DB 05653 CAAA Ed.02
Craft Terminal Operator’s Handbook
Alcatel 9400AWY & 9400FSO
9400AWY Rel.1.011–13–15–18–23–25–28–32–38 GHz
Short–haul low/medium capacity digital microwave radio links
9400FSO Rel.1.0PDH Low/Medium Capacity Free Space Optic System
SWP 9400AWY R.1.0(from version V1.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
1
02
/3DB 05653 CA AA
258
258
SWP 9400AWY R1.0 C.T. OPER.HDBK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRELIMINARY INFORMATION 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HANDBOOK APPLICABILITY, PURPOSE AND HISTORY 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HANDBOOK STRUCTURE 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAFETY–EMC–ESD NORMS AND EQUIPMENT LABELLING 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CAUTIONS TO AVOID EQUIPMENT DAMAGE 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QUICK GUIDE 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 1: INSTALLATION 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–1 SWP INSTALLATION IN PC ENVIRONMENT 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.1 Requirements 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–1.1.1 PC characteristics 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.1.2 Operator skills 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–1.2 Summary of SW installation phases 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.3 SWP loading in PC WINDOWS–NT/XP/2000 environment 22. . . . . . . . . . . . . . . . . . . . . . .
1–1.3.1 Installation of 1320CT + NE software from SWP CD–ROM 22. . . . . . . . . . . . . . . . . . . . . 1–1.3.2 Installation of SIBDL program from SWP CD–ROM 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.3.3 End of SW installation from SWP CD–ROM 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–1.4 CT initial configuration 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.4.1 NE Login 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.4.2 Craft Terminal configuration 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1.4.3 NE software downloading preparation 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–2 SWP DOWNLOAD TOWARD NE 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.1 Requirements 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–2.1.1 NE hardware 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.1.2 Craft Terminal 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.1.3 Operator skills and profile 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–2.2 Summary of the SWP installation phases 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.3 SW download to the NE 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01 040519 A.FUMAGALLI ITAVE G.ZILIANI RTT
02 040723 S404070501 A.FUMAGALLI ITAVE G.ZILIANI RTT
9400AWY–FSO REL.1.0SWP VERSION UP TO V1.0.1OPERATOR’S HANDBOOK
G.CONSONNI E.CORRADINI – ITAVE
V.RODELLA E.CORRADINI – ITAVE
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
1–2.4 Commissioning 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2.5 Configuration data definition 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1–3 NE UPGRADE TO A NEWER SWP ’VERSION’ (SAME SWP ’RELEASE’) 47. . . . . . . . . . . . . .
SECTION 2: AWY/FSO NE MANAGEMENT 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–1 GENERAL INTRODUCTION ON VIEWS AND MENUS 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.1 9400 AWY/FSO view organization 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–1.1.1 View Area 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.1.2 Resource Tree Area 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.1.3 Resource Detail Area 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.1.4 Button Policy 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–1.2 Introduction to the menu options 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2.1 Views menu introduction 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2.2 Configuration menu introduction 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2.3 Diagnosis menu introduction 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2.4 Supervision menu introduction 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1.2.5 Download menu introduction 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–2 CONFIGURATION 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.1 NE Time 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2 Network Configuration 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–2.2.1 Local Configuration 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.2 Ethernet Configuration 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.3 IP Configuration 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.2.4 Routing information 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–2.3 Alarm Severities 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.3.1 How to create a new Alarm Severity Profile 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–2.4 System Settings 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.4.1 NE Configuration 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.4.2 Link Indentifier 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2.4.3 Overhead 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–2.5 Quick Configuration Procedure 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–3 EQUIPMENT 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.1 IDU level 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–3.1.1 1+0 configuration 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.1.2 “1+0 extendable” and “1+1” configuration 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.1.3 Procedure for configuration change from “1+0 extendable” to “1+1” 100. . . . . . . . . . . . . . 2–3.1.4 Board level 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–3.2 ODU level 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.3 Tab panels in the Resource Detail Aarea 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–3.3.1 Alarms 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.3.2 Configuration 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3.3.3 Remote Inventory 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–4 LINE INTERFACE 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.1 Tab panels in the Resource Detail Area 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–4.1.1 Alarm 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4.1.2 Configuration 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–5 RADIO 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.1 Alarm 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.2 Configuration 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–5.2.1 Local or Remote Transmitter Mute 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.2.2 ODU service kit 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.2.3 Alarm Profile 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–5.3 Frequency 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.3.1 Tx Radio Frequency 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.3.2 Rx Radio Frequency 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–5.4 RTPC & ATPC 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.4.1 ATPC 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.4.2 Tx Nominal Power 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.4.3 Tx Current Power 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.4.4 Manual Operation on Tx Power 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.4.5 ATPC Range 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.4.6 ATPC Rx Threshold 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–5.5 Power Measurement 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5.5.1 How to read a Power Measurement file 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–6 FSO 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.1 Channel#1 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.2 FSO Port#1 – Ch#1 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–6.2.1 Alarm 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.2.2 Configuration 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6.2.3 Measurements 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–6.3 Laser#1 or Laser#2 127. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–7 EXTERNAL POINTS 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.1 Input External Points 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.2 Output External Points (in V.1.0.0) 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7.3 Output External Points (in V.1.0.1) 131. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–8 SUPERVISION 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.1 Access state (allow or inhibit NE Craft access) 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–8.1.1 Switching from the OS to the Craft Terminal access state 133. . . . . . . . . . . . . . . . . . . . . . 2–8.1.2 Switching from the Craft Terminal access state back to the OS access state 134. . . . . .
2–8.2 Restart NE 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8.3 SW key 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–9 PROTECTION SCHEMES 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.1 Mux Protection Management 138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–9.1.1 Schema Parameters 139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.1.2 Commands 139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–9.2 Radio Protection Management 141. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.2.1 Schema Parameter 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.2.2 Commands 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–9.3 HST Transmission Protection Management 144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.3.1 Schema Parameters 144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9.3.2 Commands 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–10 LOOPBACKS 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.1 Available Loopbacks 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–10.1.1 1+0 FSO Loopbacks 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.1.2 1+0 Radio Loopbacks 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.1.3 1+1 Radio Loopbacks 154. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–10.2 How to activate a loopback 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10.3 How to remove a loopback 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–11 DIAGNOSIS 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.1 Log Browsing 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.2 Remote Inventory 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.3 Abnormal Condition List 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.4 Summary Block Diagram View 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11.5 Current Configuration View 164. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–12 PERFORMANCE MONITORING 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.1 General information on the performance monitoring process 165. . . . . . . . . . . . . . . . . . 2–12.2 Performance menu 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.3 CD (Current Data) 169. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–12.3.1 CD parameters 170. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.3.2 CD Counters 170. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–12.4 HD (History Data) 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12.4.1 HD Parameters 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–12.5 Threshold Data 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–13 SW DOWNLOAD 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.1 Server Access Configuration 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.2 Init SW Download 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13.3 SW Status 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 3: AWY/FSO MAINTENANCE 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–1 MAINTENANCE INTRODUCTION 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.1 Maintenance of the PC 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1.2 Problems with THE Craft Terminal 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–2 TROUBLESHOOTING 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.1 Purpose of this procedure 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.2 Corrective Maintenance general flow–chart 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.3 Troubleshooting organization 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.4 Troubleshooting by means of the Craft Terminal 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–2.4.1 Alarm synthesis indication 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2.4.2 Details on alarms / statuses 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–2.5 Description of alarms and of probable causes 188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 4: SWP DESCRIPTION AND VERSIONS 191. . . . . . . . . . . . . . . . . . . . . . . .
4–1 SWP 9400AWY R.1.0 DESCRIPTION 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.1 General 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.2 Software product list and part numbers 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1.3 Software licence list and part numbers 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–2 SWP REG.9400AWY R.1.0 V1.0.0 SPECIFIC INFORMATION 195. . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.1 ECT requirements 195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.2 SWP version specific data 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–2.2.1 SW Package Identification 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.2.2 SW Package Components 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.2.3 ECT SW Sub–Components 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.2.4 NE MIB Compatibility 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–2.3 New features and modifications 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.4 Restrictions and known problems 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2.5 New features and modifications of SWP versions higher than V.1.0.0 197. . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
4–3 SWP REG.9400AWY R.1.0 V1.0.1 SPECIFIC INFORMATION 199. . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.1 ECT requirements 199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.2 SWP version specific data 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–3.2.1 SW Package Identification 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.2.2 SW Package Components 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.2.3 ECT SW Sub–Components 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.2.4 NE MIB Compatibility 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4–3.3 New features and modifications 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.4 Restrictions and known problems 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3.5 Operative hints 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 5: APPENDICES 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX A : EQUIPMENT DESCRIPTION AND COMPONENTS 205. . . . . . . . . . . . . . . . . . . . . . . . . A.1 : Functions and configurations 206. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2 : IDU and ODU Components 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.1 : IDU 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.2 : ODU 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.3 : Allowed Equipment Types 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.4 : Remote Inventory Management 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX B : SW ALLOCATION, FLASH CARD AND EQUIPMENT CONTROL 213. . . . . . . . . . . . B.1 : Allocation of equipment and craft terminal software 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2 : Flash Card 216. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2.1 : Flash Card types 216. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.2 : Flash Card identification 216. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.3 : Flash Card contents 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.4 : Flash Card upgrade (for 9400AWY only) 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3 : Equipment control 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3.1 : Interfaces (see Fig. 143. on page 205): 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3.2 : Operator–Equipment Interaction 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3.3 : ECT 219. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3.4 : RECT 219. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX C : GENERAL ON SWP INSTALLATION 221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.1 : Troubleshooting situations 222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.2 : Common situations 223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX D : ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE NET-WORK 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1 : Introduction 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2 : Certified equipment 226. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3 : Connection cables 227. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.4 : Modem setting 228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.4.1 : Setting of Sportster Flash Modem & 3Com 56K Faxmodem 228. . . . . . . . . . . . . . . . . . . . . . D.4.2 : TD–32 AC Modem setting 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.5 : PC laptop “Dell Latitude” setting 231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.6 : Setting up the connection 232. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.7 : Changing the ECT–equipment connection speed 233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.7.1 : Introduction 233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.7.2 : Configuration at PC side 234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX E : DOCUMENTATION GUIDE 235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E.1 : Handbook guide 235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.1.1 : Handbook applicability 236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
E.1.2 : Purpose of the handbook 237. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E.1.3 : Handbook history 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E.2 : Documentation set description 240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E.2.1 : 9400AWY Rel.1.0 product–release–version handbooks 241. . . . . . . . . . . . . . . . . . . . . . . . . E.2.2 : 9400FSO Rel.1.0 product–release–version handbooks 243. . . . . . . . . . . . . . . . . . . . . . . . . . E.2.3 : Handbooks common to 9400AWY Rel.1.0 and 9400FSO Rel.1.0 245. . . . . . . . . . . . . . . . . E.2.4 : Specific documentation for SNMP 246. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E.2.5 : General on Alcatel Customer Documentation 246. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX F : ACRONYMS AND ABBREVIATIONS 251. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX G : GLOSSARY OF TERMS 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
LIST OF FIGURES AND TABLES
FIGURESFig. 1. NT installation step 1 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 2. NT installation step 2 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 3. NT installation step 3 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 4. NT configuration step 1 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 5. NT configuration step 2 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 6. NT configuration step 3 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 7. NT configuration step 4 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 8. NT configuration step 5 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 9. NT configuration step 6 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 10. 2000/XP installation step 1 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 11. 2000/XP installation step 2 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 12. 2000/XP installation step 3 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 13. 2000/XP installation step 4 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 14. 2000/XP installation step 5 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 15. 2000/XP configuration step 1 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 16. 2000/XP configuration step 2 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 17. 2000/XP configuration step 3 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 18. Selecting Software Administration 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 19. Directory selection 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 20. 9400 AWY Main view organization 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 21. View Areas 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 22. Resource tree area 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 23. Tab panels 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 24. NE Time dialogue box 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 25. Network Configuration menu 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 26. Local Configuration dialogue box 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 27. Ethernet Configuration dialogue box 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 28. IP configuration screen 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 29. IP static routing configuration screen 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 30. Create Static routing 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 31. Point To Point Interface Choice 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 32. OSPF Area configuration screen 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 33. Create New OSPF Area 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 34. IP Address configuration of Point–To–Point Interfaces screen 71. . . . . . . . . . . . . . . . . . . . . . . . Fig. 35. Routing information screen 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 36. Alarm Severities Profile 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 37. Name of a cloned alarm profile 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 38. Clone of an Alarm Severity Profile 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 39. Selection of a new severity in the Service Affecting field 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 40. Selection of a new severity in the No Service Affecting field 77. . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 41. System Settings: NE configuration 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 42. System Settings: Link Identifier 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 43. Overhead Configuration 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 44. Quick Installation Procedure: NE Configuration (Step 1) 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 45. Quick Installation Procedure: Frame Configuration (Step 2) 84. . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 46. Quick Installation Procedure: Tributaries Configuration (Step 3) 85. . . . . . . . . . . . . . . . . . . . . . Fig. 47. Quick Installation Procedure: Tributaries Configuration (Step 4) 86. . . . . . . . . . . . . . . . . . . . . . Fig. 48. Quick Configuration Procedure: Channels Configuration (Step 5) 87. . . . . . . . . . . . . . . . . . . . . Fig. 49. Quick Configuration Procedure: Local IP Address (Step 6) 88. . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 50. Quich Installation Procedure: OSPF Area Configuration (Step 7) 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
8
02
/3DB 05653 CA AA
258
258
Fig. 51. Quick Installation Procedure: IP Static Router Configuration (Step 8) 90. . . . . . . . . . . . . . . . . Fig. 52. Quick Configuration Procedure: NMS–RF Interface Configuration (Step 9) 91. . . . . . . . . . . . . Fig. 53. Quick Configuration Procedure: NMS–V11 Interface Configuration (Step 10) 92. . . . . . . . . . . Fig. 54. Quick Configuration Procedure: NMS–G703 Interface Configuration (Step 11) 93. . . . . . . . . Fig. 55. Quick Installation Procedure: Ethernet Configuration (Step 12) 94. . . . . . . . . . . . . . . . . . . . . . . Fig. 56. Quick Configuration Procedure: Summary (Step 13) 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 57. 1+0 FSO Equipment view 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 58. 1+0 Radio Equipment view 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 59. 1+1 Radio Equipment view 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 60. 1+0 IDU view 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 61. 1+1 IDU view 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 62. Main board view 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 63. FSO ODU view 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 64. Radio ODU view 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 65. Alarm tab panel for a selected object 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 66. Configuration tab panel for a selected object 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 67. Remote Inventory tab panel for a selected object 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 68. Line Interface View 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 69. Line Interface View: Tributary Ports 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 70. Radio Domain View 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 71. Radio Frequency menu 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 72. Rtpc & Atpc 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 73. Manual Operatin on Tx Power 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 74. Power Measurements 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 75. Power Measurement Graphic 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 76. Power Meas Details 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 77. Name of File ( Log File ) selected screen 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 78. Example of “Power Measurement File Reading“ 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 79. Example of Power Measurement File Reading (with WordPad) 118. . . . . . . . . . . . . . . . . . . . . . . Fig. 80. FSO Domain View 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 81. FSO port configuration 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 82. Measurements screen 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 83. Power Measurement Graphic Screen 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 84. Details Dialog screen 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 85. Name of File ( Log File ) selected screen 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 86. Example of “Power Measurement File Reading“ 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 87. Example of Power Measurement File Reading (with WordPad) 126. . . . . . . . . . . . . . . . . . . . . . . Fig. 88. FSO laser configuration 127. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 89. Input External Point View 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 90. Output External Points View 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 91. Output External Points View 131. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 92. Configuration of the Craft access state from the Equipment NE view in the OS mode 133. . . Fig. 93. Restart NE call 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 94. Restart NE confirmation 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 95. SW key screen 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 96. Protection Schemes 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 97. Mux Protection 138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 98. Mux Protection Switch (Spare #0) 139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 99. Mux Protection Switch (Main #1) 140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 100. Radio Protection View 141. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 101. Radio Protection Switch (Spare #0) 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 102. Radio Protection Switch (Main #1) 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 103. Transmission Protection View 144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 104. Tx Protection Commands (Spare #0) 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 105. Tx Protection Commands (Main #1) 146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 106. 1+0 FSO available loopbacks 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 107. Channel 1 Loopback View 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 108. Tributaries Loopback View 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 109. 1+0 FSO Loopback types 150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 110. 1+0 Radio available loopbacks 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 111. Channel 1 Loopback View 152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 112. Tributaries Loopback View 152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 113. 1+0 Radio Loopback types 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 114. 1+1 Radio available loopbacks 154. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 115. Channel 1 Loopback View 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 116. Tributaries Loopback View 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 117. 1+1 Radio Loopback types 156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 118. Loopback activation 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 119. Loopback removing 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 120. Diagnosis menu 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 121. Summary Block Diagram View: 1+0 FSO 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 122. Summary Block Diagram View: 1+0 Radio 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 123. Summary Block Diagram View: 1+1 HST Radio 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 124. Summary Block Diagram View: 1+1 FD Radio 164. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 125. Radio section 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 126. Anomalies, defects, errored blocks, ES and SES according to ITU–T G.826 166. . . . . . . . . . Fig. 127. Performance View 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 128. Threshold table association screen 168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 129. Current Data View 169. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 130. History Data 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 131. Thresholds Tables 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 132. Threshold table configuration 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 133. Server access configuration screen 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 134. Init Software Download screen 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 135. SW Status screen 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 136. SW Unit Status screen 178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 137. Corrective Maintenance general flow–chart 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 138. Active alarm screem 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 139. (1+0) IDU 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 140. (1+1) IDU 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 141. (1+0) ODU (electrical or optical) 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 142. (1+1) ODU (only electrical) 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 143. Interfaces for equipment control and Flash card label on MAIN Unit 213. . . . . . . . . . . . . . . . . Fig. 144. MAIN unit + FLASH CARD 213. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 145. FLASH CARD profile and insertion direction 213. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 146. Equipment main parts containing local SW 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 147. Software management main phases 221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 148. ECT–Equipment connection via Public Switched Telephone Network 225. . . . . . . . . . . . . . . . Fig. 149. ECT–Local external Modem cable 227. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 150. F Interface–Remote Modem cable 227. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 151. TD–32 AC modem dip–switch setting 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 152. Alcatel Lower Layers utility 234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 153. Example of SWP Release and Version numbering 247. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 154. Example of Product levels and associated Customer Documentation 248. . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
TABLESTab. 1. Radio application: Market, capacity and modulation 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 2. FSO application: Market, capacity and modulation 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 3. Command priority list 140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 4. Command priority list 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 5. Command priority list 146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 6. 1+0 FSO loopbacks 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 7. 1+0 Radio loopbacks 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 8. 1+1 Radio loopbacks 154. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 9. SES Thresholds 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 10. Alarm Synthesis indication 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 11. Alarm information, general description 187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 12. General issues of the alarm meanings and their respective maintenance actions 189. . . . . . . Tab. 13. Software products part numbers 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 14. Software licence part numbers 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 15. Markets, product type, tributaries and modulations forecasted 206. . . . . . . . . . . . . . . . . . . . . . . Tab. 16. Shelves Equipment Types 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 17. IDU allowed board/plug–in types in (1+0) configurations 210. . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 18. IDU allowed board/plug–in types in (1+1) configurations 210. . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 19. Allowed board types in optical ODU ETSI 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 20. Available Flash cards 216. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 21. Handbook history 238. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 22. 9400AWY Rel.1.0 product release handbooks 241. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 23. 9400AWY Rel.1.0 Technical Handbook 242. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 24. 9400AWY Rel.1.0 Installation and Line–Up Handbooks 242. . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 25. 9400AWY Rel.1.0 Documentation on CD–ROM 242. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 26. 9400FSO Rel.1.0 product release handbooks 243. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 27. 9400FSO Rel.1.0 Technical Handbook 244. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 28. 9400FSO Rel.1.0 Installation and Line–Up Handbooks 244. . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 29. 9400AWY Rel.1.0 Documentation on CD–ROM 244. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 30. Operator’s Handbooks related to the specific Software Package SWP 245. . . . . . . . . . . . . . . . Tab. 31. Documentation common to Alcatel Network Elements using 1320CT platform 245. . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
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 Handbooks REF. [A] onpage 242 and [E] on page 244. The warning labels that can be found on the equipment partsare indicated on page 13.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.E.2 on page 240 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
12
02
/3DB 05653 CA AA
258
258
HANDBOOK APPLICABILITY, PURPOSE AND HISTORY
Please refer to para.E.1 on page 235.
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–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 19This part describes in detail the operations necessary for the SWP installation and upgrading (ECTparts and equipment parts).
c ) SECTION 2: AWY/FSO NE MANAGEMENT on page 49In this section, the description of the menu structure and of all the AWY and FSO NE functionalitiesavailable in the Craft Terminal is given.
d ) SECTION 3: AWY/FSO NE MAINTENANCE on page 179In this section the description of the AWY and FSO NE troubleshooting based on the use of the CraftTerminal is given.
e ) SECTION 4: SWP DESCRIPTION AND VERSIONS on page 191This 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 203In this section some additional information and instructions are given:• Equipment description and components• SW allocation, Flash Card and equipment control• General on SWP installation• 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
13
02
/3DB 05653 CA AA
258
258
SAFETY–EMC–ESD NORMS AND EQUIPMENT LABELLING
a ) Please refer to Technical Handbook to obtain details regarding following information:
• Compliance with European norms
• Safety rules:
TOPIC WARNING LABEL ON EQUIPMENT
General rules
Dangerous Electrical Voltages
Harmful optical signals
For 9400FSO read carefully next page
Risk of explosion
Moving mechanical parts
Heat–radiating mechanical parts
Equipment emitting RF power
• Equipment protection against electrostatic discharges:
TOPIC WARNING LABEL ON EQUIPMENT
Device sensitive to electrostatic discharges
• 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
14
02
/3DB 05653 CA AA
258
258
WARNING FOR 9400FSO ODU EQUIPMENT!
CAUTION: USE OF CONTROL OR ADJUSTMENTS OR PERFORMANCE OF PROCEDURES OTHERTHAN THOSE SPECIFIED HEREIN MAY RESULT IN HAZARDOUS LASER RADIATION EXPOSURE!
Product Laser SafetyThe following special notes provide the laser safety specifications for the 9400FSO Terminal:
INFORMATION ALERT!
LASER DEVICES PRESENT WITHIN THIS EQUIPMENT ARE HAZARDOUS WHEN VIEWED WITHOPTICAL INSTRUMENTS.LASER HAS THE FOLLOWING OUTPUT CHARACTERISTICS UNDER MAXIMUM CONDITIONS:
Laser Type Wavelength (nm) Output Power (mW)–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––VCSEL 835 – 865 16–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
EN –CLASS 1M laser products According to EN 60825–1 ; EN 60825–2
INVISIBLE LASER RADIATION
DO NOT VIEW DIRECTLY WITH OPTICAL INSTRUMENTS (BINOCULARS OR TELESCOPES)
CLASS 1M LASER 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
15
02
/3DB 05653 CA AA
258
258
CAUTIONS TO AVOID EQUIPMENT DAMAGE
a ) 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
b ) Board’s extraction/insertion levers on ACCESS, MAIN IDU and EXTENSION IDU units
These units are provided with levers to facilitate their extraction and insertion from/into the shelf. Inturn, such levers are provided with screws that:• must be loosened, before operating on levers for the unit extraction from the shelf; this avoids
the breakage of levers• must be tightened, after the unit insertion in the shelf; this ensures the equipment EMI–EMC
performance.
c ) Unit assemblies
Each of the ACCESS, MAIN IDU, EXTENSION IDU and FANS unit assembly (“main board” + “babyboard(s)” + “front plate”) must be considered an unique item from the service and maintenance pointsof view. Such an assembly is supplied by Alcatel “as it is” and must never be disassembled.
d ) Screw fixing
All boards and dummy plates are provided with screws that, in normal operation conditions, must bealways tightened onto the shelf to avoid their detachment and to ensure the equipment EMI–EMCperformance and correct ventilation.The screw tightening torque for fixing the units to the subrack 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
QUICK GUIDEC.T. OPERATOR’S HANDBOOK SWP 9400AWY R.1.0
N.B. In the documentation on CD–ROM, this table represent hyperlinks to the referenced parts.
If you need immediate operative information on how to:
GENERAL TOPICS FOR 9400AWY AND 9400FSO
get information on systemdocumentation
read Appendix E on page 235
get information on safety, EMC,ESD norms and equipment labelling
read page 13
have the description of the systemfrom the software point of view
read:
Chapter 4–1 on page 193
Appendix A on page 205
Appendix B on page 213
logically configure a station (orchange its configuration) andlogically set–up connections
get:
9400AWY T h i l H db k (R f [A] 242)logically provision equipment boards
9400AWY Technical Handbook (Ref. [A] on page 242)
get item P/Nsor
SO fget operative information regardingthe units in IDU shelf and ODU(connectors, leds, buttons)
9400FSO Technical Handbook (Ref. [E] on page 244)
and read its QUICK GUIDE (same topics)
HW INSTALLATION
physically install and cable theequipment hardware
For:
– 9400AWY, get 9400AWY Rel.1.0 Installation Handbook(Ref.[B] on page 242) and proceed as specified by it
– 9400FSO, get 9400FSO Rel.1.0 Installation Handbook(Ref.[F] on page 244) and proceed as specified by it
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
17
02
/3DB 05653 CA AA
258
258
.. continuesIf you need immediate operative information on how to:
SWP INSTALLATION AND COMMISSIONING
install SWP (first time) on ECT proceed as specified in chapter 1–1 on page 21
download SWP (first time) into theequipment
proceed as specified in chapter 1–2 on page 45
commission equipment
For:
– 9400AWY, get 9400AWY Rel.1.0 Line–up Guide(Ref.[C] on page 242) and proceed as specified by it
– 9400FSO, get 9400FSO Rel.1.0 Line–up Guide(REF.[G] on page 244) and proceed as specified by it
update ECT and equipment with anewer SWP version (same SWPrelease)
proceed as specified in chapter 1–3 on page 47
ECT SOFTWARE USAGE FOR EQUIPMENT SW MANAGEMENT
have an overview on menu treestructure
manage equipment configuration
set–up parameters for maintenance(configure housekeeping alarms;configure the Alarms Management,access the Alarm Surveillance andshow the alarm condition).
open SECTION 2 – AWY/FSO NE MANAGEMENT on page49 of this handbook and then search the informationaccording to the listed topics
access the Events Log file
use of the Performance Monitoringfunctionalities
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
18
02
/3DB 05653 CA AA
258
258
.. continuesIf you need immediate operative information on how to:
9400AWY MAINTENANCE
provision and manage spare partsget 9400AWY Technical Handbook (Ref. [A] on page 242)
carry out preventive maintenance
get 9400AWY Technical Handbook (Ref. [A] on page 242)and read its QUICK GUIDE (same topic)
carry out corrective maintenance
get 9400AWY Technical Handbook (Ref. [A] on page 242),and go to its section MAINTENANCE, chapter Second LevelMaintenance paragraph Corrective Maintenance andproceed as specified; in any case, such section will usuallylead to the SECTION 3 – AWY/FSO NE MAINTENANCE onpage 179 of this handbook.
Alternatively, access directly SECTION 3 – AWY/FSO NEMAINTENANCE on page 179 of this handbook and proceedas specified; if a board must be replaced, you will be led to theuse of paragraph Unit Replacement Procedures of the9400AWY Technical Handbook for the correct replacingprocedures.
9400FSO MAINTENANCE
provision and manage spare partsget 9400FSO Technical Handbook (Ref.[E] on page 244)
carry out preventive maintenance
get 9400FSO Technical Handbook (Ref.[E] on page 244)and read its QUICK GUIDE (same topic)
carry out corrective maintenance
get 9400FSO Technical Handbook (Ref.[E] on page 244),and go to its section MAINTENANCE, chapter Second LevelMaintenance paragraph Corrective Maintenance andproceed as specified; in any case, such section will usuallylead to the SECTION 3 – AWY/FSO NE MAINTENANCE onpage 179 of this handbook.
Alternatively, access directly SECTION 3 – AWY/FSO NEMAINTENANCE on page 179 of this handbook and proceedas specified; if a board must be replaced, you will be led to theuse of paragraph Unit Replacement Procedures of the9400FSO Technical Handbook for the correct replacingprocedures.
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
19
02
/3DB 05653 CA AA
258
258
SECTION 1: INSTALLATION
SECTION CONTENT PAGE
Chapter 1–1 – 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.
21
Chapter 1–2 – SWP download toward NEThis chapter details all phases necessary to install for the first time a SWP in theequipment environment.
45
Chapter 1–3 – NE Upgrade to a newer 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.
47
The symbol points out references to Other Handbooks.
Referenced handbook P/Ns are given in para.E.2 on page 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
20
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
1–1 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.
Before starting the installation procedures, it is suggested to give a look to para.B.1 on page 214and Appendix C on page 221.
Procedures described in this chapter are carried out with the PC disconnected from the NE.
This is a general procedure, valid for all NE types. The official SWP installation procedure is thatincluded in the:
9400AWY Line Up Guideor
9400FSO Line Up Guide
1–1.1 Requirements
1–1.1.1 PC characteristics
For version refer to paragraph on page
V.1.0.0 & V.1.0.1 4–2.1 195
1–1.1.2 Operator skills
The operator shall be familiar with the use of personal computers in WINDOWS–NT / WINDOWS 2000 / WINDOWS XP environment, internally to which the Network Element’s application software operates.
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 Recommandations).
1–1.2 Summary of SW installation phases
The sequence of installation phases for the SWP loading in PC WINDOWS–NT/XP/2000 environment (PCis disconnected from Equipment Controller) are as follows:
a ) Installation from SWP CD–ROM
1 ) installation of 1320CT + NE software from SWP CD–ROM2 ) installation of SIBDL program from SWP CD–ROM3 ) end of SW installation from SWP CD–ROM
b ) CT initial configuration
4 ) NE login5 ) Craft Terminal configuration6 ) NE software downloading preparation
that are described in detail in following 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
22
02
/3DB 05653 CA AA
258
258
1–1.3 SWP loading in PC WINDOWS–NT/XP/2000 environment
Procedures described in the following are carried out with the PC disconnected from the NE.
1–1.3.1 Installation of 1320CT + NE software from SWP CD–ROM
1–1.3.1.1 SWP standard installation
The SWP installation can be performed by two different procedures:
1 ) CT Products automatic installation
2 ) CT Products installation guided
The first procedure is used to “upgrade” the new SWP in the system, the second one has to be used toperform the first installation of SWP and to “upgrade” two specific components: Java and LLMan.
The standard installation sequence uses the “guided” procedure to install the first two components (Javaand LLMan), and then the “automatic” one to install the other components.
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
23
02
/3DB 05653 CA AA
258
258
Step 2. Select “JRE” and “Alcatel Lower Layer Manager” components.
Step 3. Press “NEXT” button to execute the installation of the previously selected components.
Step 4. Execute Java installation answering to questions.
Step 5. If a computer restart is requested, select NO restart to continue the installation.
N.B. The computer restart must be performed at the end of the installation 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
24
02
/3DB 05653 CA AA
258
258
Step 6. Press “NEXT” button to start the installation of the Lower Layers Manager.
Step 7. Select “Configure Lower Layer” and press “FINISH” button to complete the operation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Step 8. Complete the configuration and press OK button. N.B.: If a network adapter is notrunning in yourPC, you can set the “System identifier”field with a sequence of 12“0”. The following window will bedisplayed.
Step 9. 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
26
02
/3DB 05653 CA AA
258
258
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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
1–1.3.1.2 Alcatel Virtual Network Card for Lower Layers
After the SWP installation on ECT it is necessary, for NE connection using TCP/IP through serial port, toconfigure a virtual network interface.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.
1–1.3.1.2.1 Windows NT 4.0
1–1.3.1.2.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.Before installing Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol (pleaserefer to Windows NT Help).To configure the Alcatel Virtual Network Card for Lower Layers run the Network Control Panel applet fromthe Control Panel.
– Click the Add... button in the Adapter tab of the Network Control Panel applet.
Fig. 1. 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
28
02
/3DB 05653 CA AA
258
258
– 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.
Fig. 2. NT installation step 2
– If the dialog box in Fig. 3. appears, the driver is already installed.
Fig. 3. NT installation step 3
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
29
02
/3DB 05653 CA AA
258
258
1–1.3.1.2.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).
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. 5. NT configuration step 2) or a dialog box (Fig. 6. NT configuration step 3) may appear.
– Follow the instrucions until the dialog box (Fig. 7. NT configuration step 4) will appear.
1
2
3
4
5
Fig. 4. 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
30
02
/3DB 05653 CA AA
258
258
– Click Yes to save changes.
Fig. 5. NT configuration step 2
– Select Protocols tab (1), TCP/IP Protocol (2) and click the Properties button (3).
1
2
3
Fig. 6. NT configuration step 3
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
– Configure the IP Address and the Subnet Mask for the Alcatel Virtual Network Card for LowerLayers and push OK.
1
2
3
4
5
Fig. 7. NT configuration step 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
32
02
/3DB 05653 CA AA
258
258
– Click Close in the Protocols tab of the Network Control Panel applet.
Fig. 8. NT configuration step 5
– 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.
Fig. 9. NT configuration step 6
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
1–1.3.1.2.2 Windows 2000/XP
1–1.3.1.2.2.1 Installing the Alcatel Virtual Network Card for Lower Layers
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).
To configure the Alcatel Virtual Network Card for Lower Layers run the Network and Dial–up connectionsapplet from the Control Panel.
– • Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.
Fig. 10. 2000/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
34
02
/3DB 05653 CA AA
258
258
Fig. 11. 2000/XP installation step 2
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
– Click the Have Disk... button in the Select Network Adapter dialog box.
Fig. 12. 2000/XP installation step 3
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
– 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 CommandPropt window to discover the right location of the WinNT folder) and click OK.
Fig. 13. 2000/XP installation step 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
37
02
/3DB 05653 CA AA
258
258
– Click Next in the Start Hardware Installation dialog box.
Fig. 14. 2000/XP installation step 5
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
38
02
/3DB 05653 CA AA
258
258
1–1.3.1.2.2.2 Configuring the Alcatel Virtual Network Card for Lower Layers
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. 15. 2000/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
39
02
/3DB 05653 CA AA
258
258
– 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
Fig. 16. 2000/XP configuration step 2
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
– Configure the IP Address (1) and the Subnet Mask (2) and push OK (3).
3
1
2
Fig. 17. 2000/XP configuration step 3
Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers Managerto use 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
41
02
/3DB 05653 CA AA
258
258
1–1.3.2 Installation of SIBDL program from SWP CD–ROM
Refer to chapter B.1 for general information on SIBDL program (in particular point 2 ) in para.B.3.2 onpage 219 and point 2 ) in para.C.1 on page 222).
The SIBDL program is not automatically installed by the auto–installation process.
The installation of SIBDL is detailed in the dedicated Section of the:
9400AWY Line Up Guide
or
9400FSO Line Up Guide
N.B. It is not mandatory to install SIBDL in this phase. You can postpone it when necessary (take intoaccount that you will need the SWP CD–ROM).
1–1.3.3 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
42
02
/3DB 05653 CA AA
258
258
1–1.4 CT initial configuration
Procedures described in the following are carried out with the PC disconnected from the NE.
1–1.4.1 NE Login
In order to carry out procedures described in following paragraphs Craft Terminal configuration, NEProfile management and NE software downloading preparation , the NE must be logged–in, asdescribed herebelow:
a ) Craft Terminal (CT) start–up
1 ) CT start :
– power on CT and wait for PC start–up
– Start ⇒ 1320CT–P v.x.x.x ; notes:
• if choice 1320CT–P v.x.x.x is not available, PC is not configured as Craft Terminal:Software Package loading is necessary
• x.x.x depends on Software Package loaded
after a while, the “Network Element Synthesis” screen will appear, showing all NetworkElements that can be selected. After this Start operation, all NEs appear with symbol “?”(it means they are not supervised)
b ) Start supervision on a selected Network Element (NE)
From screen “Network Element Synthesis” ( see point a ) – 1 ) ) :
1 ) select the interested Network Element (NE) clicking once left mouse button on it;
2 ) while NE selected, with right mouse button choose Start Supervision and with left mousebutton execute it (click once).
Wait until the symbol “?” becomes colored “•” (it means “NE in supervised state”)
c ) Network Element login
From screen “Network Element Synthesis” with NE in supervised state ( see point b ) – 2 ) ):
1 ) select the interested Network Element (NE) clicking once right mouse button on it;
2 ) select Show 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
43
02
/3DB 05653 CA AA
258
258
1–1.4.2 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”
1–1.4.3 NE software downloading preparation
N.B. This description is retrieved from 1320CT Basic Operator’s Handbook, section “EMLconstruction”, chapter “Administrating files”, paragraph “Software Administration” and isrepeated here for ease of operation.
This phase must be manually carried out by the Operator and has the scope of making the new equipmentsoftware package available for its downloading toward the equipment controller and the peripheral units.
This operation is independent from the NE management state and must be executed with the followingprocedure:
1 ) From the Supervision pull down menu select the File Administration and then the SoftwareAdministration option, as shown in Fig. 18. on page 43.
Fig. 18. Selecting Software Administration
2 ) In the figure that opens (see next as an example) select the directory where the NE softwarepackage is installed: Alcatel / JUSMxxx / ect / swdw / <equipment name> / <version> /<descriptor file>.The NE software package can also be selected from the CD–ROM used for the installation ofthe NE software. In this case, after inserting the CD–ROM in the driver, choose the following:ect / swdw / <equipment name> / <version> / <descriptor file>.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 19. Directory selection
3 ) Click on Open to activate the installation file selected. At the end of the process, a confirmationmessage is displayed.
4 ) At this point the NE Software Package is installed in another directory and available to bedownloaded on the Network Element.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
1–2 SWP DOWNLOAD TOWARD NE
This chapter details all phases necessary to install for the first time a SWP in the equipment environment.
Before starting the installation procedures, it is suggested to give a look to para.B.1 on page 214and Appendix C on page 221.
Procedures described in this chapter are carried out with the PC connected to the NE.
This is a general procedure, valid for all NE types. The official SWP installation procedure is thatincluded in the:
9400AWY Line Up Guideor
9400FSO Line Up Guide
1–2.1 Requirements
1–2.1.1 NE hardware
The equipment must have been already physically installed, cabled and powered on, according to theinstructions given in the:
9400AWY Installation Handbookor
9400FSO Installation Handbook
1–2.1.2 Craft Terminal
The Craft Terminal, already loaded with the SWP to be downloaded toward the NE (N.B.), must beavailable together with the cable for its connection to the equipment F interface.
N.B. as explained in previous chapter 1–1 on page 21.
1–2.1.3 Operator skills and profile
In addition to skills stated in para.1–1.1.2 on page 21, the Operator must be familiar with all the equipmentfunctionalities.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
1–2.2 Summary of the SWP installation phases
The installation phases are:
a ) SW download to the NE (PC is connected to Equipment Controller), para.1–2.3 herebelowb ) Commissioning, para.1–2.4 herebelowc ) Configuration data definition, para.1–2.5 herebelow
1–2.3 SW download to the NE
1 ) Through the suitable cable, connect the PC to F interface of the MAIN unit (see Fig. 143. onpage 213)
2 ) Activate ECT (1320CT x.x.x) and execute the Login to the NE (see para.1–1.4.1 on page 42).
3 ) Perform the SW download with the following Craft Terminal commands (refer to para.2–13.2on page 176 for detailed description):
a ) SW Download ⇒ Init SW download
b ) the screen of Fig. 134. on page 176 opens
c ) select the NE–version to be downloaded
d ) with SWP Version 1.0.1 is necessary to select “Forced” option on CT screen for SWDownload activation request
e ) click on “Init download” button
f ) then, after about 1/2 hour, ⇒ SW Download ⇒ SW status ⇒ Apply Action to activate thesoftware.
N.B. The software download can be performed also by using the Ethernet interface of the PC. In thiscase the download lasts only few minutes.
1–2.4 Commissioning
The commissioning instructions are given in:
9400AWY Line Up Guide
or
9400FSO Line Up Guide
1–2.5 Configuration data definition
The instructions given in the handbook cited in para. 1–2.4 above may not include the definition of all theEquipment configuration data that could be necessary.
In order to manage this data, refer to the Section 2 AWY/FSO NE MANAGEMENT on page 49.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
1–3 NE UPGRADE TO A NEWER 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 223, i.e.:
– ECT and equipment are running with one of the Software Packages with P/N indicated in Tab. 13. onpage 193 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–1.1 on page 21 and para.1–2.1 on page 45.
2 ) Carry out the installation of the new SWP version in the ECT environment, as indicated inchapter 1–1 on page 21.
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 191. In case you receive a version higher thanthe highest listed on page 191, 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–13.2 on page 176 for detailed description):
• SW Download ⇒ Init SW download
• the screen of Fig. 134. on page 176 opens
• select the new NE–version to be downloaded
• with SWP Version 1.0.1 is necessary to select “Forced” option on CT screen for SWDownload 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 ) erform NE logoff followed by NE login.
The result is to have the Equipment working with the new SWP version neverthelessmaintaining the old 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
48
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
SECTION 2: AWY/FSO NE MANAGEMENT
SECTION CONTENT PAGE
Chapter 2–1 – General introduction on views and menusThis chapter describes the organization of the 9400AWY/FSO ULS N.E.,presented after the NE login.
51
EQUIPMENT CONFIGURATION MANAGEMENT
Chapter 2–2 – ConfigurationThis chapter describes the configuration relevant to the equipment management.
61
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.
97
Chapter 2–4 – Line InterfaceThis chapter describes the operations necessary for the configuration setting andverification of each tributary.
105
Chapter 2–5 – RadioThis chapter deals with the management of the Radio transmission features.
109
Chapter 2–6 – FSOThis chapter deals with the management of the FSO transmission features.
119
Chapter 2–7 – External input and output pointsThis chapter describes how to display and set the input/output environmentalalarms (housekeeping alarms).
129
FUNCTIONS FOR MAINTENANCE
Chapter 2–8 – SupervisionThis chapter describes how to manage the NE access from OS or local ECT andhow to restart the NE.
133
Chapter 2–9 – Protection schemesThis chapter deals with the management of the Radio protections.
137
Chapter 2–10 – LoopbacksThis chapter describes the commands for loopback management, forcommissioning or maintenane purposes.
147
Chapter 2–11 – 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”.
159
Chapter 2–12 – Performance MonitoringThis chapter deals with the use of the Performance Monitoring functionalities.
165
SOFTWARE MANAGEMENT
Chapter 2–13 – Software ManagementThis chapter deals with the management of the functions related to the softwareverification/download and to the back–up and restore of equipment configurationdata.
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
50
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–1 GENERAL INTRODUCTION ON VIEWS AND MENUS
This chapter describes the organization of the 9400 AWY/FSO 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.
N.B. This operator handbook explains the menus for Rel.1.0.0 and Rel.1.0.1.Version 1.0.0 manages the Radio application only (1+0 configuration).Version 1.0.1 manages the Radio application (1+0 and 1+1 configurations) and the FSOapplication.
2–1.1 9400 AWY/FSO view organization
The 9400 AWY/FSO view ( see Fig. 20. on page 52 ) contains the following fields, which provide theoperator with the information needed to manage the NE:
• Severity alarm synthesis,• Domain alarm synthesis,• Management status control panel,• View title,• View area,• Message/state area.
The Menu bar 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. 20. on page 52 shows the 9400 AWY 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
52
02
/3DB 05653 CA AA
258
258
Menu bar
Viewarea
Severity alarmsynthesis
Domain alarm synthesis
Main toolbar
Management state control panel
Fig. 20. 9400 AWY 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 Section 3 paragraph Alarm synthesis indication inthis 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
53
02
/3DB 05653 CA AA
258
258
2–1.1.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 (or FSO in V.1.0.1)
– Protection Schemes (for Radio application only in V.1.0.1)
– 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. 21. 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
54
02
/3DB 05653 CA AA
258
258
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.1.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. 22. Resource tree area
2–1.1.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
55
02
/3DB 05653 CA AA
258
258
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 collapsethe tree node showing thesame information in the “Resource list area”.
2–1.1.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.1.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 should require a warning message for user confirmation before to beactivated.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–1.2 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 61 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.2.1 on page 57.
To navigate among the views and to set the TMN parameters.
• Configuration (second column). See para.2–1.2.2 on page 59.
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.2.3 on page 59.
To get information on the NE (alarms, performance monitoring, remote inventory).
• Supervision (fourth column). See para.2–1.2.4 on page 60.
To set the supervision states (i.e. Craft Terminal enabling).
• SW Download (fifth column). See para. 2–1.2.5 on page 60.
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
57
02
/3DB 05653 CA AA
258
258
2–1.2.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 97.
– External Points: Displays and sets the input/output environmental alarm.See Chapter 2–7 on page 129.
– Line Interface: Opens the Line Interface view to configure all the tributary ports.See Chapter 2–4 on page 105.
– Performance: Allows to manage the Performance monitoring.See Chapter 2–12 on page 165.
– Radio: Allows to manage all the functions relevant to the radio channels.See Chapter 2–5 on page 109.
– FSO: Allows to manage all the functions relevant to the FSO channel.See Chapter 2–6 on page 119.This menu is available in V.1.0.1 only.
– Protection Scheme: Allows to manage the Protection schemes in 1+1 configuration.See Chapter 2–9 on page 137.This menu is available in V.1.0.1 only for the Radio application.
– Loopback: Allows to manage the loopbacks available with the equipment.See Chapter 2–10 on page 147.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
N.B. It is possible to enter directly menus Equipment, External Points, Line Interface, Performance,Radio ( or FSO ), Protection Scheme, Loopback by clicking on the relevant tab panel above theview area. Refer to Fig. 23. on page 58.
Tab panel
Fig. 23. 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
59
02
/3DB 05653 CA AA
258
258
2–1.2.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 61.
– Network configuration: See para. 2–2.2 on page 62.
– Alarm Severities: Manages the Alarm Severity Assignment Profile.See para. 2–2.3 on page 73.
– System setting: Allows the system configuration, providing the setting of all the parametersfor the NE setup. See para. 2–2.4 on page 78.
– Quick configuration: Allows a full system configuration through a guided procedure.See para. 2–2.5 on page 82.
2–1.2.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–11.1 on page 159.
– Current configurationView: Displays the current configuration of the NE.
See para. 2–11.2 on page 159.
– Summary Block Diagram View: Displays a global logical view (strictly related to the physical implementation)
highlighting a synthesis of all the alarms and statuses present in the system(ODU+IDU).See para. 2–11.4 on page 160.
– 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
60
02
/3DB 05653 CA AA
258
258
2–1.2.4 Supervision menu introduction
This menu allows to set the supervision states of the NE, by means of the following entries (see chapter2–8 on page 133) :
– Access State: Manages the supervision access to the NE, via CT or OS.Opens the following menu options:• OS• RequestedSee para. 2–8.1 on page 133.
– Restart NE: Reset of the NE software.See para. 2–8.2 on page 134.
– SW key: Displays the type of the key stored in the flash card.See para. 2–8.3 on page 135.
2–1.2.5 Download menu introduction
This menu allows to manage the NE software, by means of the following entries (see chapter 2–13 on page175) :
– Server Access Configuration: Manages the configuration of the FTP server to be used for the software
download to the NE.See para. 2–13.1 on page 175.
– Initi SW download: Manages the software download to the NE.See para. 2–13.2 on page 176.
– SW status: Shows and manages the status of the software packages installed in the NEmemory banks.See para. 2–13.3 on page 177.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–2 CONFIGURATION
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. 24. 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.
With a click on the Daylight Saving Time (DST) check box the manual management of the summer timetakes place.
The Refresh pushbutton allows to read the time actually present 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
62
02
/3DB 05653 CA AA
258
258
2–2.2 Network Configuration
To get access the Network Configuration option select the Configuration pull down menu, as shownin the following figure.
Fig. 25. Network Configuration menu
The Network Configuration allows to perform the following operations:
Local Configuration: defines the local NE addresses
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
63
02
/3DB 05653 CA AA
258
258
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. 26. on page 63 ) 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. 26. 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
64
02
/3DB 05653 CA AA
258
258
2–2.2.2 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. 27. on page 64 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 poiner: 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. 27. 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
65
02
/3DB 05653 CA AA
258
258
2–2.2.3 IP Configuration
Select the Configuration pull down menu. Select the Network Configuration and then from thecascading menu, the IP Configuration option ( see Fig. 28. on page 65).
Fig. 28. IP configuration screen
2–2.2.3.1 IP static routing configuration
The dialog–box opens ( see Fig. 29. on page 66 ) 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
66
02
/3DB 05653 CA AA
258
258
Fig. 29. IP static routing configuration screen
By pressing Create pushbutton the screen in Fig. 30. on page 67 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)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 30. Create Static routing
If in the screen of Fig. 30. on page 67 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. 30. on page 67 has been selected the Point To Point Interface Index check box, thescreen in Fig. 31. on page 68 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
68
02
/3DB 05653 CA AA
258
258
Fig. 31. 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
69
02
/3DB 05653 CA AA
258
258
2–2.2.3.2 OSPF Area configuration
The dialog–box opens ( see Fig. 32. on page 69 ) and allows to configure the parameters for OSPF (OpenShortest Path First) Area Table Configuration.
The following fields and data are present:
– OSPF Area IP Address– OSPF Area Range Mask– 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. 32. OSPF Area configuration screen
By pressing Create pushbutton the screen in Fig. 33. on page 70 opens.
N.B. 3 areas max. can be created.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 33. 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
71
02
/3DB 05653 CA AA
258
258
2–2.2.3.3 IP Address configuration of Point–To–Point Interfaces
The dialog–box opens ( see Fig. 34. on page 71 ) 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. 34. 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
72
02
/3DB 05653 CA AA
258
258
2–2.2.4 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. 35. on page 72 opens.
Fig. 35. 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
73
02
/3DB 05653 CA AA
258
258
2–2.3 Alarm Severities
By selecting the Alarm Severities option from the Configuration menu the screen in Fig. 36. on page74 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
74
02
/3DB 05653 CA AA
258
258
Fig. 36. Alarm Severities Profile
In the screen of Fig. 36. on page 74 are available 2 buttons:
– Close: to close the screen.– Clone: to create a new Alarm Sevetiry Profile. To create a clone refer to para. 2–2.3.1 on page 75.
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
75
02
/3DB 05653 CA AA
258
258
2–2.3.1 How to create a new Alarm Severity Profile
– Select in the screen of Fig. 36. on page 74 the Alarm Profile to be cloned.
– Click the Clone pushbutton.
– The screen of Fig. 37. on page 75 appears.
– Digit the name to be assigned to the new Alarm Profile and click on Apply.
Fig. 37. 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. 38. on page 75).
Fig. 38. 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
76
02
/3DB 05653 CA AA
258
258
– 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. 39. on page 76).
Fig. 39. 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
77
02
/3DB 05653 CA AA
258
258
– 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. 40. on page 77).
Fig. 40. 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. 40. on page 77).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
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– Link Identifier– Overhead
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. 41. on page 78 will appear.
The field “Type” contains all the allowed configurations supported for the NE (radio and FSO). Theoperator choice will be applied by selecting the related “Apply” button.
The “Structure” area displays the market, capacity and modulation and, if needed, the ability to changeit, according to NE market configured in the previous screen.
The field ”Market” contains two market types: ETSI or ANSI (refer to Tab. 1. and Tab. 2. ). The operatorchoice will be applied by selecting the related “Apply” button.
Fig. 41. 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
79
02
/3DB 05653 CA AA
258
258
The information related to the modulation type is shown in the “Modulation” field. The possible values are”4QAM” or ”4QAM” and ”16QAM”. The capacity and the Modulation can be modified by selecting a differenttype according to Tab. 1. for the Radio application and Tab. 2. for the FSO application and then selectingthe ”Apply” button to send the new value.
The “Tributary Port Configuration” area is in the lower part of the window. The “Impedance” field allowsthe operator to configure the impedance of the E1/DS1 tributary (unbalance 75 ohm or balance 120 ohm).
The impedance value will be applied by clicking on the related ”Apply” button.
Tab. 1. Radio application: Market, capacity and modulation
Market Capacity Modulation
ETSI 2xE1 4QAM
4xE1 4QAM / 16QAM
8xE1 4QAM / 16QAM
16xE1 4QAM / 16QAM
1xE3 4QAM / 16QAM
ANSI 4xDS1 4QAM
8xDS1 4QAM / 16QAM
16xDS1 4QAM / 16QAM
1xDS3 4QAM / 16QAM
Tab. 2. FSO application: Market, capacity and modulation
Market Capacity Modulation
ETSI 16xE1 4QAM
1xE3 4QAM
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–2.4.2 Link Indentifier
The ”Link Identifier” area, shown in Fig. 42. on page 80, displays the current values of parameters relatedto link management and, if necessary, modifies them.
The operator choices will be sent to NE by clicking on the related “Apply” button. The parameters involvedare:
– Mismatch detection: this field disables or enables the link identifier mismatch detection.
– Expected Value: this field is the link identifier value expected by the NE (allowed values: 1 to 16).
– Sent Value: this field is the link identifier value transmitted by the NE (allowed values: 1 to 16).
Fig. 42. System Settings: Link Identifier
The operator choice will be applied by selecting 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
81
02
/3DB 05653 CA AA
258
258
2–2.4.3 Overhead
The ”Overhead” tabbed panel identifies the parameters for the management of the phone number andauxiliary interface (Fig. 43. on page 81).
Fig. 43. 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 75).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
82
02
/3DB 05653 CA AA
258
258
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. 44. on page 83 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Step 1
Fig. 44. Quick Installation Procedure: NE Configuration (Step 1)
The first step provides a screen to configure two NE parameters:
– Market (ETSI or ANSI); for FSO application the market is ETSI only;– Type configuration.
The possible selections for the Type field are:
– Radio application:• 1+0 (PSU4860): unprotected configuration• 1+0 EXT HST (PSU4860): Hot Standby extendable configuration• 1+0 EXT FD (PSU4860): Frequency Diversity extendable configuration• 1+1 HST (PSU4860): Hot Standby protected configuration• 1+1 FD (PSU4860): Frequency Diversity protected configuration
– FSO application:• 1+0 FSO (PSUM4860H): unprotected configuration
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.
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
84
02
/3DB 05653 CA AA
258
258
Step 2
The screen shown in Fig. 45. on page 84 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 79.
Moreover, if the tributary selected is E1 the Impedance also must be selected in the Tributary PortConfiguration (unbalance 75 ohm or balance 120 ohm).
Fig. 45. Quick Installation Procedure: Frame Configuration (Step 2)
In the screen displayed in Fig. 45. on page 84 (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. in FSO application the applicable capacity is 16E1 or E3 only and modulation is 4 QAM only.
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
85
02
/3DB 05653 CA AA
258
258
Step 3
Step 3 allows the operator to choose, for each tributary configured, the signal mode or disable it(Fig. 46. on page 85).
Fig. 46. Quick Installation 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.
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
86
02
/3DB 05653 CA AA
258
258
Step 4
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. 47. on page 86):
– Radio protection (Rx EPS)
– Mux protection (Tx EPS)
– HST Tx protection (RF Hot Stand–by)
Fig. 47. Quick Installation Procedure: Tributaries Configuration (Step 4)
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
87
02
/3DB 05653 CA AA
258
258
Step 5
Step 5 allows the operator to define the basic paramters for each configured channel. The related screenis shown in the Fig. 48. on page 87:
Fig. 48. Quick Configuration Procedure: Channels Configuration (Step 5)
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 112).
If ATPC is disabled in the RTPC area the power (costantly 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.
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+1HST the choices will be applied to both “channels”. In case of 1+1FD, the samescreen will be reproposed 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 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
88
02
/3DB 05653 CA AA
258
258
Step 6
Step 6 performs the network configuration (Fig. 49. on page 88). This window allows to enter to IP addressassociated to the F interface of the NE.
Fig. 49. 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.
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
89
02
/3DB 05653 CA AA
258
258
Step 7
Step 7 allows to configure one or more OSPF Areas (3 areas max.) (Fig. 50. on page 89).
Fig. 50. Quich Installation Procedure: OSPF Area Configuration (Step 7)
To create a new area write a number in the Area Id field, in the IP address field write the address and inthe Range Mask field enter the range associated to the OSPF area and click on 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.
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
90
02
/3DB 05653 CA AA
258
258
Step 8
The following windows for Network Configuration allow the complete IP configuration.
Step 8 configures one or more Static Routers (Fig. 51. on page 90).
Fig. 51. Quick Installation Procedure: IP Static Router Configuration (Step 8)
The following fields and data are present:
[1] Host Address: allows to define the IP address necessary to reach a specific Host.
[2] Network Address: it is in alternative to the Host Address; allows to define the IP Mask to 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.
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
91
02
/3DB 05653 CA AA
258
258
Step 9
Step 9 allows the configuration of the NMS–RF channel (Fig. 52. on page 91):
Fig. 52. Quick Configuration Procedure: NMS–RF Interface Configuration (Step 9)
The “NMS–RF” interface is a communication interface based on the use of an inframe RF proprietary 64kbit/s channel. Through the “NMS–RF” interface the NE can exchange management messages with aremote 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.
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
92
02
/3DB 05653 CA AA
258
258
Step 10
Step 10 allows the configuration of the NMS–V11 interface (Fig. 53. on page 92):
Fig. 53. 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.
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 protocl and in case of OSPF protocol select also theassociated OSPF area.
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 commonsynchronisation 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.
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
93
02
/3DB 05653 CA AA
258
258
Step 11
Step 11 allows the configuration of the NMS–G703 interface (Fig. 54. on page 93):
Fig. 54. 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.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 protocl and in case of OSPF protocol select also theassociated OSPF area.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 commonsynchronisation 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.
– In frame E1–DS1 mode:as alternative mode is possible to drop in the G703 64 kbit/s in Tributary 1, Time Slot 1 allowing thetransport of supervision messages along the traffic path.
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
94
02
/3DB 05653 CA AA
258
258
Step 12
Step 12 (Fig. 55. on page 94) allows to configure the Ethernet Interface.
Fig. 55. Quick Installation 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.
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
95
02
/3DB 05653 CA AA
258
258
Step 13
Step 13 is the last step. The screen shown summarizes all the parameters configured during thisprocedure and some relevant parameters with default values (Fig. 56. on page 95).
Fig. 56. 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
96
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
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 205 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 is shown in Fig. 57. on page 97 for 1+0 FSO configuration.
The main screen of the Equipment tab panel is shown in Fig. 58. on page 98 for 1+0 Radio configuration.
The main screen of the Equipment tab panel is shown in Fig. 59. on page 98 for 1+1 Radio configuration.
In the Resource List Area is shown a graphical representation of the Equipment, which consists of an IDUand an ODU.
A coloured ball gives information on the status of the associated object. The colour differs according tothe severity of the alarms:
– Green: no alarm– White: indetermination alarm active (not operative)– Cyanic: warning alarm active– Yellow: minor alarm active– Brown: major alarm active– Red: critical alarm active
IDU
FSO ODU
IDU Status
ODU Status
Equipment Status
Fig. 57. 1+0 FSO 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
98
02
/3DB 05653 CA AA
258
258
IDU
ODU
IDU Status
ODU Status
Equipment Status
Fig. 58. 1+0 Radio Equipment view
IDU
ODU
IDU Status
Equipment Status
ODU Status
Fig. 59. 1+1 Radio 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
99
02
/3DB 05653 CA AA
258
258
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
Configuration available both with 9400AWY and 9400FSO.
The screen in Fig. 60. on page 99 will appear.
IDU
MAIN BOARDStatus
ACCESS BOARD StatusIDU Status
ACCESS BOARDMAIN BOARD
Fig. 60. 1+0 IDU view
The IDU consists of 2 boards:
– Access board
– Main board
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–3.1.2 “1+0 extendable” and “1+1” configuration
Configurations available with 9400AWY only.
The screen in Fig. 61. on page 100 will appear.
IDU
MAIN BOARDStatus
IDU Status
ACCESS BOARDMAIN BOARD
EXTENSIONBOARDStatus
EXTENSION BOARD
ACCESS BOARD Status
FANSBOARDStatus
FANS BOARD
Fig. 61. 1+1 IDU view
The IDU consists of 4 boards:– Access board– Main board– Extension board (not present in “1+0 extendable” configuration)– Fans board
2–3.1.3 Procedure for configuration change from “1+0 extendable” to “1+1”
There are many ways to proceed for this configuration change, but some of them give no good results.Thus, follow this procedure to obtain a correct result, without traffic impacts:
1 ) Install the second ODU unit and the relevant IDU–ODU cable (refer to 9400AWY InstallationHandbook)
2 ) On IDU, extract the dummy plate closing the Extension board slot3 ) Get the Extension board, switch off it, insert it in the shelf and connect the IDU–ODU cable4 ) Set, by Local ECT, 1+1 configuration using System Setting function5 ) Restart the NE6 ) Switch on the Extension board7 ) Proceed as specified in the 9400AWY Installation Handbook and Line–Up Guide for the
operations regarding the second ODU installed. In particular, set, by Local CT, Tx Power andTx Frequency values related to second 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
101
02
/3DB 05653 CA AA
258
258
2–3.1.4 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. 62. on page 101 is shown the screen of the MAIN IDU board.
BOARD Status
Fig. 62. 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
102
02
/3DB 05653 CA AA
258
258
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. 63. on page 102 will appear in case of FSO configuration.The screen in Fig. 64. on page 102 will appear in case of Radio configuration.
Fig. 63. FSO ODU view
Fig. 64. Radio 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
103
02
/3DB 05653 CA AA
258
258
2–3.3 Tab panels in the Resource Detail Aarea
2–3.3.1 Alarms
The Alarms tab panel provides the fault mangement, which checks the current state of alarms related tothe selected object (Fig. 65. on page 103).
Fig. 65. 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
104
02
/3DB 05653 CA AA
258
258
2–3.3.2 Configuration
The “User Label”’ field (Fig. 66. ) 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 75). 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 Primary Alarm profile.
Fig. 66. 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 following window shows (Fig. 67. on page 104):
Fig. 67. 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
105
02
/3DB 05653 CA AA
258
258
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 view allows the user to manage the resources of a PDH signal, i.e. frames, tributaryports (line), etc.This domain view consists of the following areas (Fig. 68. on page 105):
– Resource Tree Area: displays the frames and tributary ports sorted by the channel number.– Resource List Area: displays tabular information about the selected resource in the tree area.– Resource Detail Area: displays, through tabbed windows, the selected object’ s properties in list
area. This area performs the available functions for involved resource.
Fig. 68. Line Interface View
In the Resource List Area is given the information related to the tributaries:
– Type Interface (E1/E3 etc..)– 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/Framed IsdnPra/Disabled)
To change the Signal Mode select the tributary and change the Signal Mode field in the Resource DetailArea.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–4.1 Tab panels in the Resource Detail Area
2–4.1.1 Alarm
The fault mangement 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 103.
2–4.1.2 Configuration
The window, shown in Fig. 69. on page 106, performs all available functions for a tributary port.
The managed tributary types are: E1, E3.
To define the involved ports, the channel selection in the tree view is first required; therefore the selectionof the desired tributary port in the tabular view enables the “Resource Detail list” to show the availablefunctions for the single one resource.
Fig. 69. Line Interface View: Tributary Ports
The information related to a PDH frame is shown in Fig. 69. on page 106, where the following fields areonly read fields:
– Interface Type (E1/E3 etc..)
– Port Number: indentifies the ports for a given channel and type of port
– Channel Number
The fields, which can be changed are:
– Signal Mode
– Tx RAI Insertion
– Rx RAI Insertion
– 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
107
02
/3DB 05653 CA AA
258
258
Signal Mode
The possible values are:
– Framed for the framed received signal
– FramedIsdnPra for an ISDN PRA 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.
Tx RAI Insertion
This field refers to the insertion of the RAI signal in Tx side. The possible values are:
– Inibited: it is not possible to force the RAI insertion
– Forced: the RAI insertion is performed
– Enabled: the RAI insertion is possible.
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.
Rx RAI Insertion
This field refers to the insertion of the RAI signal in Rx side. The possible values are:
– Inibited: it is not possible to force the RAI insertion
– Forced: the RAI insertion is performed
– Enabled: the RAI insertion is possible.
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.
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 75). 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
108
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
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. 70. on page 109):
– 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. 70. Radio Domain View
Five tab panels are present in the Resourse Detail Area:
– Alarms: shows the active alarms (refer to para. 2–5.1 on page 110)– Configuration: configures some radio parameters (refer to para. 2–5.2 on page 110)– Frequency: sets the Tx RF frequency (refer to para. 2–5.3 on page 111)– RTPC & ATPC: sets the manual operation parameters or the automatic operation parameters (refer
to para. 2–5.4 on page 112)– Power Meas: performs the Tx and Rx power measurements (refer to para. 2–5.5 on page 114).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–5.1 Alarm
The fault mangement 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 103.
2–5.2 Configuration
The window shown in Fig. 80. on page 120 performs all the available functions for a Radio PDH port.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.
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.
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 75). Toassociate a different Alarm Profile click on the selection button and select among the available AlarmProfile.
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
111
02
/3DB 05653 CA AA
258
258
2–5.3 Frequency
This menu (Fig. 71. on page 111) 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. 71. Radio Frequency menu
2–5.3.1 Tx Radio Frequency
The ”Tx Freq” field in the “Frequency Value” area of tabbed window (Fig. 71. on page 111) 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.
2–5.3.2 Rx Radio Frequency
The ”Rx Freq” field in the “Frequency Value” area of the tabbed window (Fig. 71. on page 111) shows thecurrent 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
112
02
/3DB 05653 CA AA
258
258
2–5.4 RTPC & ATPC
This menu (Fig. 72. on page 112) 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.
Fig. 72. Rtpc & Atpc
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.
2–5.4.2 Tx Nominal Power
The “Nominal Value” field in the “RTPC” area (Fig. 72. on page 112) is a read–only field and shows thenominal value of the transmitted power (expressed in dBm).
2–5.4.3 Tx Current Power
The “Tx Power” field in the “RTPC” area (Fig. 72. on page 112) shows the current value of Tx power(expressed in dBm), when the ATPC is disabled and no manual operation on the transmitted power isactive. In this case, it is possible to modify this value by writing the new value and by pressing the related“Apply” button.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
113
02
/3DB 05653 CA AA
258
258
2–5.4.4 Manual Operation on Tx Power
To start a Manual Operation click on the Selection button in the Manual Operation field in Fig. 72. on page112. The screen in Fig. 73. on page 113 opens.
Fig. 73. Manual Operatin on Tx Power
Initially the ”Power Value” field shows the current Tx power. By pressing button “Start Manual”, the powerlevel can be modified with the up–arrow and down–arrows (in steps of 0.1 dBm) or by clicking on theAutomatic Apply buttons to change the power by +0.1 dBm or +1 dBm or –0.1 dBm or –1 dBm. The”Apply” button is also enabled.
The new value must be within the allowed range shown in ”Power Range” area of Fig. 72. on page 112;it is applied when the Apply button is pressed.
The “Stop Manual” button stops the manual operation.
2–5.4.5 ATPC Range
The Min Value and Max Value, for Tx Range in the Atpc management, are shown in the ”Atpc Range”area. The min and max level can be changed by writing the new value in the field.
When the ”Apply” button is pressed the new values will be applied.
2–5.4.6 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–5.5 Power Measurement
The Power Measurements capability is performed through the “Power Meas” tabbed panel in the resourcedetail view (Fig. 74. on page 114).
Fig. 74. 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.
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. 83. onpage 123).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
The Power Measurement Graphic is available only if the CT is connected to the NE.
The screen in Fig. 75. 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 analized;
– 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. 75. Power Measurement Graphic
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
By clicking on “Show details” box, on the left side of the Power Measurement Graphic (see Fig. 75. onpage 115), a new table appears (Fig. 76. on page 116); this table shows the following relevant values ofthe 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.
– 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. 76. Power Meas 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
117
02
/3DB 05653 CA AA
258
258
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. 77. Name of File ( Log File ) selected screen
Select the desired file and click the Start button in Fig. 74. on page 114 to open the file.
Fig. 78. 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
118
02
/3DB 05653 CA AA
258
258
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. 79. on page 118).
Fig. 79. 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
119
02
/3DB 05653 CA AA
258
258
2–6 FSO
N.B. This menu is available in V.1.0.1 only.
The FSO domain view allows the user to manage the resources of the FSO transmission channel.
This domain view consists of the following areas:
– Resource Tree Area: displays the FSO port.
– Resource List Area: displays tabular information about the selected resource in tree area.
– Resource Detail Area: dislpays, through tabbed windows, the object’ s properties selected in thelist area. This area enables to execute the available functions for involved resource.
In the Resource Tree Area the following objects can be selected:
– Channel#1 refer to para. 2–6.1 on page 120
– FSO Port#1 – Ch#1 refer to para. 2–6.2 on page 121
– Laser#1 or Laser#2 refer to para. 2–6.3 on page 127
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–6.1 Channel#1
By selecting the Channel 1 object in the Resource Tree Area the screen in Fig. 80. on page 120 appears:
Fig. 80. FSO Domain View
In the Resource List Area is shown the following information:
– Type Interface: the type of the interface (FSO Port only)
– Port number: the number of the port (port 1 only)
– Channel number: the number of the channel (channel 1 only)
– Heater status: the status of the heater installed inside the FSO ODU (Off/On). To activate the Heaterselect FSO Port#1 – Ch#1 in the Resource Tree Area and select Configuration in the ResourceDetail Area.
– Rx Power: the power of the received signal in dBm
– Temperature: the internal temperature inside the FSO ODU measured by an internal temperaturesensor.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–6.2 FSO Port#1 – Ch#1
By selecting the FSO Port#1 – Ch#1 object in the Resource Tree Area the screen in Fig. 81. on page 121appears.
Fig. 81. FSO port configuration
In the Resource List Area is shown the following information:
– Type Interface: the type of the interface (FSO Port only)
– Port number: the number of the port (port 1 only)
– Channel number: the number of the channel (channel 1 only)
– Laser Index: the identification number of the 2 Lasers installed in the FSO ODU.
– Laser Status: the status of the Laser (On/Off). To switch on or off a Laser select the Laser object inthe Resource Tree Area and select Configuration in the relevant Resource Detail Area.
Three tab panels are present in the Resourse Detail Area:
– Alarms: shows the active alarms (refer to para. 2–6.2.1 on page 122)
– Configuration: configures some FSO parameters (refer to para. 2–6.2.2 on page 122)
– Power Meas: performs the Tx and Rx power measurements (refer to para. 2–6.2.3 on page 122).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–6.2.1 Alarm
The fault mangement 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 103.
2–6.2.2 Configuration
The window shown in Fig. 81. on page 121 performs all the available functions for the FSO port.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 resource.
2–6.2.3 Measurements
The Measurement screen (see Fig. 82. on page 122) allows the operator to set initial parameters for therequired 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.
The log file contains the sample value and records the measurement up to a maximum dimension ( 7 daysfor a 2 s sample time).
Fig. 82. Measurements screen
By clicking on the ”Start“ button the screen “Power Measurement Graphic“ appears (see Fig. 83. onpage 123).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 83. Power Measurement Graphic Screen
The Power Measurement Graphic is available only if the CT is connected to NE.
The screen in Fig. 83. on page 123 shows the current Rx measurement and the ODU alarms related tothe local NE.
The top graphic screen area shows the Rx curve, while the bottom area shows the alarms active in theODU. The alarms have different colors according to their severity.
The top of the screen offers all the characteristics present in the current measurement:
– FSO port: gives the symbolic name associated to the channel that you are analyzing
– 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
By clicking on “Show details” box, on the left side of the Power Measurement Graphic (see Fig. 83. onpage 123), a new table appears (Fig. 84. on page 124); this table shows the following relevant values ofthe received and transmitted power:
– 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.
Fig. 84. Details Dialog 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
125
02
/3DB 05653 CA AA
258
258
2–6.2.3.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. 85. Name of File ( Log File ) selected screen
Select the desired file and click the Start button in Fig. 82. on page 122 to open the file.
Fig. 86. 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
126
02
/3DB 05653 CA AA
258
258
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. 87. on page 126).
Fig. 87. 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
127
02
/3DB 05653 CA AA
258
258
2–6.3 Laser#1 or Laser#2
By selecting the Laser object in the Resource Tree Area the screen in Fig. 88. on page 127 appears.
Fig. 88. FSO laser configuration
In the Resource List Area is shown the following information:
– Type Interface: the type of the interface (FSO Port only)
– Port number: the number of the port (port 1 only)
– Channel number: the number of the channel (channel 1 only)
– Laser Index: the identification number of the 2 Lasers installed in the FSO ODU.
– Laser Status: the status of the Laser (On/Off). To switch on or off a Laser select Configuration inthe relevant Resource Detail Area.In the Laser status field 4 options are available:
• On: the selected Laser is switched ON• Off: the selected Laser is switched OFF• On All: both Lasers (1 and 2) are switched ON• Off All: both Lasers (1 and 2) are switched 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
128
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–7 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. 89. on page 129, 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 Resourse list area opens theConfiguration menu in the Resourse Detail Area. An example of this mechanism is diplayed in theFig. 89. on page 129.
2–7.1 Input External Points
An input external point is described by the following parameters (Fig. 89. on page 129):
– 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. 89. 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
130
02
/3DB 05653 CA AA
258
258
2–7.2 Output External Points (in V.1.0.0)
An output external point is described by the following parameters (Fig. 90. on page 130):
– Id: identification number
– UserLabel: associate a user–friendly name to an external point
– Polarity: describes the polarity (Active Closed/ Active Opened)
– External State: describes the state (on /off)
The lower part provides the possible parameters which can be modified; after a row selection, the usercan modify the User Label, Polarity and External State of the external point selected (On=active; Off=notactive).
The operator choices will be sent to NE by clicking on the “Apply” button.
Fig. 90. Output External Points 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
131
02
/3DB 05653 CA AA
258
258
2–7.3 Output External Points (in V.1.0.1)
Seven output external points are available (Fig. 91. on page 131):
The first four external points (CPO#1, 2, 3, 4) 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 external
point can be changed.– External State: describes the state (on /off). In this field the external point can be activated (on) or
deactivated (off).
The operator choices will be sent to NE by clicking on the “Apply” button.
The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) are described by thefollowing 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 external
point 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.
Fig. 91. Output External Points 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
132
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–8 SUPERVISION
2–8.1 Access state (allow or inhibit NE Craft access)
The NE can be managed by the OS or by the Craft Terminal. To control the competition of the OS and theCT, a Local Access Control (LAC) is available.
If the LAC is ”access denied”, it means that the OS manages the NE and the CT is not allowed to modifythe NE configuration (it can only “read”). In the view, the icon with a key symbol has a circular shape.
If the LAC is “granted”, it means that the CT is allowed to manage the NE. In the view, the icon with a keysymbol has a rectangular shape.
If the LAC is ”requested”, it means that the CT has requested a permission from the OS and is waiting fora replay.
However, the OS does continue to provide a certain number of services. These services include:
– Alarm reception and processing,
– Performance processing,
– Switching back to the OS access state.
The access state of an NE can be modified from two types of views:
2–8.1.1 Switching from the OS to the Craft Terminal access state
Select the Supervision pull down menu. Then select the Requested option from the Access Statecascading menu as shown in the following figure.
Fig. 92. 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
134
02
/3DB 05653 CA AA
258
258
2–8.1.2 Switching from the Craft Terminal access state back to the OS access state
Select the Supervision pull down menu. Then from the Access State cascading menu in Fig. 121. onpage 161, select the OS option.From the confirmation dialogue box that opens, you can confirm or cancel the ”OS access” operation.The NE is now managed by the OS.
N.B. The key symbol icon on the management states of the NE view indicates whether the NE ismanaged by a craft terminal or by the OS.
N.B. Local Craft Terminal access is denied on recovery phase after a loss of communication of theNE. When the communication with the NE is lost, the OS automatically recovers thecommunication and forces the state existing before the loss of communication (therefore, CraftTerminal access can be denied or granted).
2–8.2 Restart NE
The RESTART operation is a software reset and can be executed in normal traffic conditions.
From the Supervision cascading menu, select the Restart NE option.
Fig. 93. Restart NE call
The following dialogue box opens.
Fig. 94. 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–8.3 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. 95. 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
136
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–9 PROTECTION SCHEMES
N.B. This menu is available in V.1.0.1 only for the Radio application.
This domain is present in 1+1 configuration.
This domain view consists of the following areas (Fig. 96. on page 137):
– Resource Tree Area: displays the radio ports sorted by channel number.
– Resource List Area: displays tabular informations 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. 96. on page 137, the tree will be expanded according toprotection schemes supported.
Fig. 96. 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 exemple of this mechanism is displayed in thefollowing figure (Fig. 97. on page 138).
Three 1+1 protection schemes have been implemented:
– Mux protection: EPS protection in Tx side– Radio protection: EPS protection 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
138
02
/3DB 05653 CA AA
258
258
To see the current position of the switches enter the menu Diagnosis –> Summary Block Diagram View(refer to para. 2–11.4 on page 160).
– The Mux protection corresponds to the Switch Tx in Fig. 123. on page 163 or Fig. 124. on page 164
– The Radio protection corresponds to the Switch Rx in Fig. 123. on page 163 or Fig. 124. on page164
– 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. 123. on page 163.
2–9.1 Mux Protection Management
The Equipment Protection Management is performed by selecting Mux Protection tree element.
The following windows (Fig. 97. on page 138) allows a complete view of all Ne resource involved in theEPS protection:
– Schema Parameters
– Channels Parameters
Fig. 97. 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
139
02
/3DB 05653 CA AA
258
258
2–9.1.1 Schema Parameters
The window “Schema Parameters” displays the parameters that can be modify.
The Schema parameters are:
– Protection Type: this parameter is defined at creation time and it is read only. The supported 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–9.1.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 98. on page 139) oron the Main #1 element (Fig. 99. on page 140).
Fig. 98. 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
140
02
/3DB 05653 CA AA
258
258
Fig. 99. 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. 3. 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
141
02
/3DB 05653 CA AA
258
258
2–9.2 Radio Protection Management
The Radio Protection Management is performed selecting Radio Protection element tree.
The following windows (Fig. 100. on page 141) allows a complete view of all Ne resource involved in aRPS protection:
– Schema Parameters
– Channels Parameters
Fig. 100. 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
142
02
/3DB 05653 CA AA
258
258
2–9.2.1 Schema Parameter
The window “Schema Parameters” displays the parameters that can be modify.
The Schema Parameters are:
– ”Protection Type” field: defines the protection schema architecture: 1+1;
– ”Operation Type” field: the possible values are revertive (automatic restoration allowed) ornotRevertive (automatic restoration Inhibited).
2–9.2.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view (Fig. 101. on page 142)or on the Main #1 element (Fig. 102. on page 143).
Fig. 101. 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
143
02
/3DB 05653 CA AA
258
258
Fig. 102. Radio 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. 4. 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
144
02
/3DB 05653 CA AA
258
258
2–9.3 HST Transmission Protection Management
The Transmission Protection Management is performed selecting Transmission Protection element tree.
The following windows (Fig. 103. on page 144) allows a complete view of all Ne resource involved in aTPS protection:
– Schema Parameters
– Channels Parameters
Fig. 103. Transmission Protection View
2–9.3.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 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
145
02
/3DB 05653 CA AA
258
258
2–9.3.2 Commands
To enter the Commands menu click on the Spare #0 element (Fig. 104. on page 145) or on the Main #1element (Fig. 105. on page 146) in the Tree view.
Fig. 104. 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
146
02
/3DB 05653 CA AA
258
258
Fig. 105. Tx Protection Commands (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 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.
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. 5. 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
147
02
/3DB 05653 CA AA
258
258
2–10 LOOPBACKS
The functions described in this section allow to perform the test operations.
This domain view consists of the following areas:
– Resource Tree Area: displays the object on which the loopbacks can be performed, sorted bynumber.
– Resource Filter Area: display the possible filters to apply to loopback search.
– 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
148
02
/3DB 05653 CA AA
258
258
2–10.1 Available Loopbacks
N.B. The loopbacks can be activated on the local NE only.
2–10.1.1 1+0 FSO Loopbacks
TRIB MODEMMUX/DEMUX
OPT.TxRx
21 4 5 7
MODEM TRIB
3
IDU FSO ODU FSO ODU IDU
CT
MUX/DEMUX
6
OPT.TxRx
Fig. 106. 1+0 FSO available loopbacks
Tab. 6. 1+0 FSO loopbacks
No.Loopback
name
CT selection inthe Resourse
Tree Area
Ref. toFig.
LocationLoopback
typeNote
1E1/DS1Port#xx
TributariesFig. 108. Fig. 109.
Near End External lineInput loopback attributary level
2E1/DS1Port#xx
Channel 1Fig. 107. Fig. 109.
Near End External line
Loopback toward theremote station attributary level. Thisloopback can beactivated in theremote station only.
3E1/DS1Port#xx
Channel 1 Fig. 107. Far End InternalLoopback in theremote station attributary level
4 IDU cable Channel 1Fig. 107. Fig. 109.
Near End InternalLoopback at the IDUoutput at aggregatelevel
5ODU FSO
cableChannel 1
Fig. 107. Fig. 109.
Near End InternalLoopback at the ODUinput at aggregatelevel
6ODU FSO
IF #1Channel 1
Fig. 107. Fig. 109.
Near End Internal IF
Loopback betweenthe Modulator outputand Demodulatorinput
7ODU FSO
opticalChannel 1
Fig. 107. Fig. 109.
Near End InternalOptical loopback atthe ODU level
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 107. Channel 1 Loopback View
Fig. 108. 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
150
02
/3DB 05653 CA AA
258
258
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. 109. on page 150 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)
ODU FSOCABLE
ODU FSOOptical
ODU FSOIF#1
IDUCABLE
Channel(External Line)
1
2
5 7
64
Fig. 109. 1+0 FSO 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
151
02
/3DB 05653 CA AA
258
258
2–10.1.2 1+0 Radio Loopbacks
TRIB MODEMMUX/DEMUX
RF
21 4 5 6
MODEMRF TRIB
3
IDU ODU ODU IDU
CT
MUX/DEMUX
Fig. 110. 1+0 Radio available loopbacks
Tab. 7. 1+0 Radio loopbacks
No.Loopback
name
CT selection inthe Resourse
Tree Area
Ref. toFig.
LocationLoopback
typeNote
1E1/DS1Port#xx
TributariesFig. 112. Fig. 113.
Near End External lineInput loopback attributary level
2E1/DS1Port#xx
Channel 1Fig. 111. Fig. 113.
Near End External line
Loopback toward theremote station attributary level. Thisloopback can beactivated in theremote station only.
3E1/DS1Port#xx
Channel 1 Fig. 111. Far End InternalLoopback in theremote station attributary level
4 IDU cable Channel 1Fig. 111. Fig. 113.
Near End InternalLoopback at the IDUoutput at aggregatelevel
5 ODU cable Channel 1Fig. 111. Fig. 113.
Near End InternalLoopback at the ODUinput at aggregatelevel
6 Radio port Channel 1Fig. 111. Fig. 113.
Near End Internal RF local loopback
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 111. Channel 1 Loopback View
Fig. 112. 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
153
02
/3DB 05653 CA AA
258
258
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. 113. on page 153 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. 113. 1+0 Radio 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
154
02
/3DB 05653 CA AA
258
258
2–10.1.3 1+1 Radio Loopbacks
TRIB MODEMMUX/DEMUX
RF
21 4 5 6
MODEMRF TRIB
3
IDU ODU ODU IDU
CT
MUX/DEMUX
Fig. 114. 1+1 Radio available loopbacks
Tab. 8. 1+1 Radio loopbacks
No.Loopback
name
CT selection inthe Resourse
Tree Area
Ref. toFig.
LocationLoopback
typeNote
1E1/DS1Port#xx
TributariesFig. 116. Fig. 117.
Near End External lineInput loopback attributary level
2E1/DS1Port#xx
Channel 0 or 1Fig. 115. Fig. 117.
Near End External line
Loopback toward theremote station attributary level. Thisloopback can beactivated in theremote station only.
3E1/DS1Port#xx
Channel 0 or1Fig. 115. Fig. 117.
Far End InternalLoopback in theremote station attributary level
4 IDU cable Channel 0 or 1Fig. 115. Fig. 117.
Near End InternalLoopback at the IDUoutput at aggregatelevel
5 ODU cable Channel 0 or 1Fig. 115. Fig. 117.
Near End InternalLoopback at the ODUinput at aggregatelevel
6 Radio port Channel 0 or 1Fig. 115. Fig. 117.
Near End Internal RF local loopback
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 115. Channel 1 Loopback View
Fig. 116. 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
156
02
/3DB 05653 CA AA
258
258
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. 117. on page 156 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. 117. 1+1 Radio 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
157
02
/3DB 05653 CA AA
258
258
2–10.2 How to activate a loopback
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. 118. on page 157 will appear.(In this screen has been selected the loopback on tributary E1, Near End Type).
Fig. 118. Loopback activation
[3] Select Active in the Activation field.
[4] Click on Apply.
[5] In the row in the Resource List Area the Activation field of the relevant loopback changes from NotActive to 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
158
02
/3DB 05653 CA AA
258
258
2–10.3 How to remove a loopback
To remove a loopback:
[1] Select the suitable loopback to remove by clicking on the relevant object in the Resource Tree Areaor by selecting the relevant row in the Resource List Area.
[2] The screen in Fig. 119. on page 158 will appear.(In this screen has been selected the loopback on tributary E1, Near End Type).
Fig. 119. Loopback removing
[3] Select Not Active in the Activation field.
[4] Click on Apply.
[5] In the row in the Resource List Area the Activation field of the relevant loopback changes from Activeto Not 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
159
02
/3DB 05653 CA AA
258
258
2–11 DIAGNOSIS
In the Diagnosis menu four options are available as shown in Fig. 120.
Fig. 120. Diagnosis menu
2–11.1 Log Browsing
In the Diagnosis pull–down menu, select the Log Browsing option.
The proposed options:
– Select the Alarm Log option to access the Alarm Log file.
The Alarm Log windows opens, permitting to analyze all the alarms stored in the NE.Refer to the “ELB Operator’s Handbook”.
– Select the Event Log option to access the Event Log file.
The Event Log windows opens, permitting to analyze all the events stored in the NE.Refer to the “ELB Operator’s Handbook”.
– Software Trace Log option is reserved to the Alcatel technicians.
2–11.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
160
02
/3DB 05653 CA AA
258
258
2–11.3 Abnormal Condition List
The Abnormal Condition List option in the Diagnosis menu displays all the abnormal conditions (i.e.the manual operations) currently active in the NE.
The abnormal conditions can be:
– Switch commands Forced or Lockout– Loopback– Tx power manual operation– Tx muting (manual or automatic)– ODU service kit connected– FSO laser muting
2–11.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 FSO (see Fig. 121. on page 161)– 1+0 Radio (see Fig. 122. on page 162)– 1+1 HST Radio (see Fig. 123. on page 163)– 1+1 FD Radio (see Fig. 124. on page 164)
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
161
02
/3DB 05653 CA AA
258
258
Fig. 121. Summary Block Diagram View: 1+0 FSO
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 122. Summary Block Diagram View: 1+0 Radio
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 123. Summary Block Diagram View: 1+1 HST Radio
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Fig. 124. Summary Block Diagram View: 1+1 FD Radio
By pressing the Refresh button the refresh of the screen takes place (active loopback and performanceand position of the switch).
2–11.5 Current Configuration View
This screen is a read–only screen, which shows the current configuration of the NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–12 PERFORMANCE MONITORING
This chapter describes the functions to provide Performance Monitoring management. It explains theprocedures that the operator must perform in order to activate a PM process.
2–12.1 General information on the performance monitoring process
The performance monitoring (PM) gives indication on the quality of the service.
Quality of service PM is performed in accordance with G.826 and G.784.
It is assumed that the quality of the single tributary (E1, T1, …) 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 and one for 24 h; 16 recent registersare available for 15 min and one for 24 h.
The radio section monitored is:
– Radio Hop Section: the section between two radio stations inside the protection section;
MODEMRF
MODEMRF
FECDECODE
PROPR.FRAMING
PROPR.FRAMING
FECENCODE
Radio Hop (before the switch)
Fig. 125. Radio section
The counters supported are the following:
– Errored Seconds– Severly 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. 9. 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 Blocksnumber/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
166
02
/3DB 05653 CA AA
258
258
The flow chart shown below illusrtates 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. 126. 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
167
02
/3DB 05653 CA AA
258
258
2–12.2 Performance menu
The performance view allows the user to activate and monitor the PM process on the selected object.
This domain view consists of the following areas (Fig. 127. on page 167):
– 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. 127. 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 only of HOP 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
168
02
/3DB 05653 CA AA
258
258
With reference to Fig. 127. on page 167 to see (and configure) the current report:
[1] click on the channel (0 or 1) (in 1+0 configuration channel 1 only)
[2] click on HOP
[3] click on the desired granularity (15 m or 24 h)
[4] click on CD (Current Data).
With reference to Fig. 127. on page 167 to see an history log:
[1] click on the channel (0 or 1) (in 1+0 configuration channel 1 only)
[2] click on HOP
[3] click on the desired granularity (15 m or 24 h)
[4] click on the desired HD (History Data).
To each PM can be associated a threshold table. To associate a threshold table click on HOP in theResourse Tree Area. The screen in Fig. 128. will appear.
Fig. 128. Threshold table association screen
In this screen the threshold (1 or 2) and an Alarm Profile can be associated to the report.
To associate an Alarm Profile click on the selection box and selet one of the Alarm Profiles available.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–12.3 CD (Current Data)
The window displayed in Fig. 129. on page 169 allows to start and to read the 15min PM report and 24hPM report.
Fig. 129. 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
170
02
/3DB 05653 CA AA
258
258
2–12.3.1 CD parameters
The fields displayed in the upper part of Fig. 129. on page 169 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.
2–12.3.2 CD Counters
The fields and buttons displayed in the lower part of Fig. 129. on page 169 (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 (Erroredblock), 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. 129. on page 169, 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
171
02
/3DB 05653 CA AA
258
258
2–12.4 HD (History Data)
The PM process monitors the parameters during a specified interval (i.e. 15min) and stores their valuesin history data. A History Data collection is created automatically at the end of each time interval of CurrentData and deleted when the relative CD is deleted.
2–12.4.1 HD Parameters
The table displayed on the following window (Fig. 130. on page 171) collects the history data for a relatedPM report.
Fig. 130. 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
172
02
/3DB 05653 CA AA
258
258
2–12.5 Threshold Data
This section describes how to see or change the threshold tables assigned to PM counters.
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.
By clicking on the threshold table on the view area the parameters of the 2 tables will appears (Fig. 131. onpage 172).
Fig. 131. Thresholds Tables
By clicking on threshold 1 or 2 in the Resourse List Area the screen in Fig. 132. on page 173 will appear.
In the upper part of Fig. 132. on page 173, the “Name” field displays the name assigned to the thresholdtable.
In the lower part of Fig. 132. on page 173, low and high threshold for each counter is shown. To changethem, the operator 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
173
02
/3DB 05653 CA AA
258
258
Fig. 132. Threshold table 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
174
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–13 SW DOWNLOAD
2–13.1 Server Access Configuration
An FTP server can be used to speed up the software download to the NE .
This menu allows to configure an FTP server on which the previously loaded SWP will be downloaded.
N.B. Copy the ECT directory present in the SWP CD on the FTP server.
Fig. 133. Server access configuration screen
User Id and Password are the login information to access the FTP server.
In the Address field write the address of the FTP server. If in this field the address of the CT is written,downloading takes place through the Ethernet interface (and not the F interface).
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
176
02
/3DB 05653 CA AA
258
258
2–13.2 Init SW Download
Through this menu software is downloaded to the NE in order to upgrade the NE software version.
To start download select the desired software version and click on the Init download button.
N.B. This screen displays the software packages previously stored through the menu Supervision–> Files Administration –> Software Administration available in the NES menu.
The Forced check box can be used to force download (i.e. the complete description file is downloadedto the NE).
If the Forced download is not selected, the system shall first proceed to compare the software to bedownloaded with the software present in the NE. Then only the differences are downloaded.
Fig. 134. Init Software Download screen
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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
2–13.3 SW Status
This menu allows to display the information of the software installed in the NE.
The following information is displayed:
– Name: software name
– Version: software version
– Operational state: enabled or disabled
– Current status: committed or standby
By clicking on the Software Units Status button the screen of Fig. 135. on page 177 opens, givingadditional information on the software package.
Fig. 135. 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
178
02
/3DB 05653 CA AA
258
258
The following information is displayed on the screen:
– EC: software on the Equipment Controller
– OC_R: software on the ODU Controller (Radio)
– OC_F: software on the ODU Controller (FSO)
Fig. 136. 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
179
02
/3DB 05653 CA AA
258
258
SECTION 3: AWY/FSO MAINTENANCE
SECTION CONTENT PAGE
Chapter 3–1 – Maintenance introduction 180
Chapter 3–2 – Troubleshooting 181
The symbol points out references to Other Handbooks.
Referenced handbook P/Ns are given in para.E.2 on page 240 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
180
02
/3DB 05653 CA AA
258
258
3–1 MAINTENANCE INTRODUCTION
This section is the 9400AWY/FSO Maintenance Manual; it describes mainly the NE troubleshooting basedon the use of the Craft Terminal.
It applies to 9400AWY SWP Rel.1.0.
The document that should be read before starting this document is:
9400AWY Technical Handbooks, section MAINTENANCEor:
9400FSO Technical Handbooks, section MAINTENANCE
– 9400AWY Rel.1.0 Technical Handbook and 9400FSO R.1.0 Technical Handbook R.1.0.
N.B. In particular, knowing the contents of section “MAINTENANCE” of Technical Handbook isa must.
– 1320CT Basic Operator’s Handbook V.3.0.1
The maintenance procedures consist of the following steps:
– PC Maintenance. See para.3–1.1 herebelow.
– Problems with the Craft Terminal PC (shut–down and restart ). See para.3–1.2 herebelow.
– Corrective Maintenance (Troubleshooting). See Chapter 3–2 on page 181.
3–1.1 Maintenance of the PC
With regard to the PC maintenance, refer to the constructor’s documentation.
3–1.2 Problems with THE Craft Terminal
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 unsuccesful, carry out the checks indicated in:
9400AWY or 9400FSO Technical Handbookssection MAINTENANCE,
chapter SECOND LEVEL MAINTENANCEparagraph TROUBLESHOOTING–PROBLEMS WITH THE CRAFT TERMINAL
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
3–2 TROUBLESHOOTING
3–2.1 Purpose of this procedureTroubleshooting involves detection, location and correction of the failures occurred in the equipment andreplacement of the defective parts.
3–2.2 Corrective Maintenance general flow–chartAs depicted in Fig. 137. herebelow, troubleshooting via Craft Terminal is just a step inside the CorrectiveMaintenance process.
Alarm acknowledgment and attending (para...)
Trouble–Shooting starting with visual indications (para......)
Trouble–Shooting via Craft Terminal.Identification of a unit to be replaced.
Other measures
Unit replacement in the IDU (para...). ODU replacement (para...)
System check via Craft Terminal
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 and performsystem check via Craft Terminal
Y
Fig. 137. Corrective Maintenance general flow–chart
For detailed information regarding the whole Corrective Maintenance procedure, please refer to:
9400AWY or 9400FSO 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
182
02
/3DB 05653 CA AA
258
258
3–2.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
183
02
/3DB 05653 CA AA
258
258
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–2.4 on page 184.
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
184
02
/3DB 05653 CA AA
258
258
3–2.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. 10. on page 185 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–2.4.2 on page 186 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
185
02
/3DB 05653 CA AA
258
258
3–2.4.1 Alarm synthesis indication
The following troubleshooting table pertains to the alarm and status synthesis given in all the screens.
Tab. 10. 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 immediatetroublshooting. NB1.
MIN Minor (Not urgent) alarmSynthesis of alarms for which a deferred interventcan 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
186
02
/3DB 05653 CA AA
258
258
3–2.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. 138. on page 186):
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 Resourse Tree Area to check if some alarms are active.
[3] Select the Alarm tab panel in the Resourse 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. 138. Active alarm screem
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
187
02
/3DB 05653 CA AA
258
258
The following table summarizes the information obtained in the Alarm view, starting from the left column.
Tab. 11. 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. 12. on page 189 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
188
02
/3DB 05653 CA AA
258
258
3–2.5 Description of alarms and of probable causes
The information provided helps the operator during troubleshooting operations.
N.B. UNIT REPLACEMENT
After having identified a unit to be replaced, in order to carry out the replacement correctly,please refer to:
9400AWY or 9400FSO Technical Handbooks,section MAINTENANCE
chapter SECOND LEVEL MAINTENANCE,paragraph UNIT REPLACEMENT PROCEDURES
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
189
02
/3DB 05653 CA AA
258
258
Tab. 12. 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 2 Mbit 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 (E1/DS1)
LOF at the Tx tributary input or at Rxtributary output (with framedtributary) or LOF of the Rxaggregate signal
Check the E1/DS1 connectedequipment or the line
Loss Of Frame (Aggregatesignal)
LOF of the Rx aggregate signal Check the link (errors)
Loss Of Signal LOS at the Tx tributary input Check the line
Low BER Low BER at the Rx sideCheck the link (propagationproblem)
Mod failInternal modulator failure affectingthe modulated signal
Replace the ODU
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Tab. 12. General issues of the alarm meanings and their respective maintenance actions
ALARM MEANING MAINTENANCE ACTION
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)
Rx LOS (FSO alarm) No Optical received signalCheck the link (propagationproblem)
Threshold CrossPerformance threshold has beencrossed
Errors on the link
Transmitter degraded (FSOalarm)
Laser degraded (output power 3 dBbelow the nominal power)
Minor alarm
Transmitter Failure (FSOalarm)
Transmitter failureReplace the ODU if the alarm ispresent at the same time on LASER1 and LASER
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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
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.
SECTION CONTENT PAGE
INFORMATION INDEPENDENT ON THE SPECIFIC SWP VERSIONS
Chapter 4–1 – SWP REG.9400AWY R.1.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).
193
INFORMATION ON THE SPECIFIC SWP VERSIONSThese chapters give operative information regarding the Software Package Version1.0.x, starting from version V1.0.0: requirements (PC and equipment Firmware), SWPackage Identification, SW Package Components, ECT SW Sub–Component, NEMIB Compatibility, new features, restrictions and known problems.
Chapter 4–2 – SWP REG.9400AWY R.1.0 V.1.0.0 specific informationN.B. Version 1.0.0 manages the Radio application only (1+0 configuration).
195
Chapter 4–3 – SWP REG.9400AWY R.1.0 V.1.0.1 specific informationN.B. Version 1.0.1 manages the Radio application (1+0 and 1+1
configurations) and the FSO application.199
The symbol points out references to other handbooks.
Referenced handbook P/Ns are given in Appendix E 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
192
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
4–1 SWP 9400AWY R.1.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.
4–1.2 Software product list and part numbers
Every Software Product is identified by a denomination and a part number and is distributed by a CD–ROMwith the same identifiers, listed on the following table:
Tab. 13. Software products part numbers
Name ANV Part NumberFactory
Part NumberN.B.
SWP 9400 AWY R.1.0 CD–ROM 3DB 04798 AAAA 415.201.017 Y 1
N.B. 1 Software Package associated to LCT or RCT SW Licence ( For AWY/FSO ULS NEs).See para.4–1.3 on page 194 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
194
02
/3DB 05653 CA AA
258
258
4–1.3 Software licence list and part numbers
Every Software licence is identified by a denomination and a part number, listed on the following table.
Tab. 14. Software licence part numbers
Name ANV Part NumberFactory
Part NumberN.B.
SWL–ULS R1.0 FEE 3DB 05638 AAAA 700.500.050 P 1, 3
SWL–LCT 9400 AWY R1.0 FEE 3DB 04811 AAAA 700.500.028 D2 3
SWL–RCT 9400 AWY R1.0 FEE 3DB 04812 AAAA 700.500.029 E2, 3
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.
3 Software licence valid for AWY and FSO application.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
4–2 SWP REG.9400AWY R.1.0 V1.0.0 SPECIFIC INFORMATION
This chapter gives operative information regarding the Software Package Version 1.0.0: requirements (PCand equipment Firmware), SW Package Identification, SW Package Components, ECT SWSub–Component, NE MIB Compatibility, new features, restrictions and known problems.
For versions higher than V1.0.0 please refer to next chapters of this section.
Please refer to para.E.2.5.2 on page 247 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 236.
4–2.1 ECT requirements
For ECT installation it is necessary a PC with the requirements hereafter described:
1 ) HW Configuration
– CPU: Pentium III 850 MHz– RAM: 256 Mbytes (512 Mbytes suggested for Windows XP)– Hard Disk space: 4 Gbytes– Display Resolution: 1024x768 pixel– CD–ROM Drive: 24X– Primary Interface: Serial Port RS–232–C 9.6 to 57.6 Kbits/sec.– Optional Interface: Ethernet Card 10/100 Mbits/sec.
2 ) Windows Versions
– Windows NT 4.0 SP3 till SP6– Windows 2000 till SP4– Windows XP till SP1
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.
4 ) Additional information
– On IDU PQ/ECRC controller it is requested a Raw Loader version V8.1.0 of May 22nd,2003 or higher.
– Reference SNMP–IM version: 2.14 (SGPA 3.2.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
196
02
/3DB 05653 CA AA
258
258
4–2.2 SWP version specific data
N.B. With reference to the Versions stated on this page, please read carefully theN.B. on page 236.
4–2.2.1 SW Package Identification
Identification Version Date
SWP REG. 9400AWY R1.0 V1.0.0 April 19th, 2004
4–2.2.2 SW Package Components
Name Description Version
SWP REG. 9400AWY R1.0SW Package for 2G Radio Regenerator LowCapacity PDH Equipments
V1.0.0
SWC–ECT9400AWY_V10 Equipment Craft Terminal SW Component V1.0.0
SWC–EC9400AWY_V10 Equipment Controller SW Component V1.0.0
SWC–OCR9400AWY_V10 ODU Radio Controller SW Component V1.4.4
SWC–OCF9400AWY_V10 ODU FSO Controller SW Component V1.0.19
SWC–FD9400AWY_V10 File Descriptor for SW Download Component V1.0.0
4–2.2.3 ECT SW Sub–Components
Name Version Description
JRE V1.4.1–04 Java 2 Run Time Environment
LLMAN V3.3.2 Lower Layers Manager
CT–K V3.0.2 P5 Craft Terminal Base Platform
CT–K SNMP Add–On V3.0.3 P2 Craft Terminal Base Platform SNMP Add–On (EML–IM)
CT–K HOL Add–On V1.0.0 P2 Craft Terminal Base Platform Help On–Line Add–On
JUSM–SNMP–COMMON V1.0.0 User Service Manager for SNMP MW NEs
JUSM–SNMP–HELP V0.1.0 Help On–Line for SNMP MW NEs
CT–K Q3 Add–On V3.0.3 P2 Craft Terminal Base Platform Q3 Add–On (EML–IM)
4–2.2.4 NE MIB Compatibility
NE MIB it is not compatible with previous versions (this is the first version) and has to be manuallyconfigured.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
4–2.3 New features and modifications
Not Applicable for first release.
N.B. Version 1.0.0 manages the Radio application only (1+0 configuration).
4–2.4 Restrictions and known problems
– For a corrected operation, only on some PC with Windows 2000 or XP using serial connection, dueto an unidentified problem to be solved by ECT Platform, it is necessary to start Low Layers Managerbefore to start ECT Platform (Alcatel 1320CT).
– Alarm Surveillance: the application closure is followed by a message error (with Windows NT only).No impact in the functionality.
– At first activation sometimes, after NES opening, the message “ANTP: Unrecoverable error” appearsalso with ANTP deactivasted (with Windows NT only).No impact in the functionality.
– SNMP Agent it is not able to correctly manage event reporting when IP addresses are different onNMS ports and Ethernet port.
4–2.5 New features and modifications of SWP versions higher than V.1.0.0
Please refer to next chapters of this section.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
4–3 SWP REG.9400AWY R.1.0 V1.0.1 SPECIFIC INFORMATION
This chapter gives operative information regarding the Software Package Version 1.0.1: requirements (PCand equipment Firmware), SW Package Identification, SW Package Components, ECT SWSub–Component, NE MIB Compatibility, new features, restrictions and known problems.
Please refer to para.E.2.5.2 on page 247 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 236.In case you receive a SWP with version higher than that stated, please refer tothe documentation accompanying the SWP delivery to get this information.
4–3.1 ECT requirements
As for V.1.0.0 (see para.4–2.1 on page 195).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
4–3.2 SWP version specific data
N.B. With reference to the Versions stated on this page, please read carefully theN.B. on page 236.
4–3.2.1 SW Package Identification
Identification Version Date
SWP REG. 9400AWY R1.0 V1.0.1 July 8th, 2004
4–3.2.2 SW Package Components
Name Description Version
SWP REG. 9400AWY R1.0SW Package for 2G Radio Regenerator Low CapacityPDH Equipments
V1.0.1
SWC–ECT9400AWY_V10 Equipment Craft Terminal SW Component V1.0.1
SWC–EC9400AWY_V10 Equipment Controller SW Component V1.0.4
SWC–OCR9400AWY_V10 ODU Radio Controller SW Component V1.4.12
SWC–OCF9400AWY_V10 ODU FSO Controller SW Component V1.1.0
SWC–FD9400AWY_V10 File Descriptor for SW Download Component V1.0.1
4–3.2.3 ECT SW Sub–Components
Name Version Description
JRE V1.4.1–04 Java 2 Run Time Environment
LLMAN V3.3.2 Lower Layers Manager
CT–K V3.0.3 P4a Craft Terminal Base Platform
CT–K SNMP Add–On V3.1.0 P1b Craft Terminal Base Platform SNMP Add–On (EML–IM)
CT–K HOL Add–On V1.0.0 P2 Craft Terminal Base Platform Help On–Line Add–On
JUSM–SNMP–COMMON V1.0.2 User Service Manager for SNMP MW NEs
JUSM–SNMP–HELP V0.1.1 Help On–Line for SNMP MW NEs
CT–K Q3 Add–On V3.0.3 P2 Craft Terminal Base Platform Q3 Add–On (EML–IM)
4–3.2.4 NE MIB Compatibility
NE MIB it is automatically converted from previous released versions 1.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
201
02
/3DB 05653 CA AA
258
258
4–3.3 New features and modifications
With respect to the previous SWP REG.9400AWY R.1.0 V1.0.0, the SWP REG.9400AWY R.1.0 V1.0.1introduces the following features and modifications:
a ) Version 1.0.1 manages the Radio application (1+0 and 1+1 configurations) and the FSO application.
b ) Inserted new management for polarity configuration by CT on Summarizing alarms.
c ) It has been modified to “onlyLocal” the tipology of Near–End Tributary E3/DS3 loopback.
d ) It has been extended the management of “Service Kit Connected” alarm for Pegaso ASIC alignment(1 bit of 1 register).
e ) Improved management of Soft–Reset associated to new version of Traminer CPLD.
f ) Improved management of “Lac State” in caso of NMS system already connected.
g ) It has been extended the loopback management to enable the functionality also to NMS system.
h ) Improved management of “CardFail” alarm to speed–up HST switching.
i ) It has been extended the management of “LossOfSignal” alarm also in case of Auxiliary Interfaceconfigured as V11 Codirectional.
j ) Improved management of maintenance operations control.
k ) Improved management of alarms related to EPS TX switch position.
l ) Improved management of 1+1 configurations for both ETSI and FCC systems.
m ) Improved management of IDU–ODU connection in case of on–line modification of system capacityand/or modulation.
n ) Improved management of Protections control features.
o ) Improved management of Performance Monitoring features.
p ) Improved management of TMN–RF pointToPoint in case of on–line modification of system capacity.
q ) It has been completed the correct management of HST switch in case of contemporary presence ofthe alarms (TX Fail and RUP).
r ) It has been resolved the problem on incorrect reporting of MAC Address value associated to LANinterface.
s ) It has been inserted a new version of OC Radio SW, aligned to the same version used on UXFLAT1+0 configuration, with the following modifications:• Tx Power filtered on Tx Power configuration changement• Frequency plan V06 modified on local loop for the RX base band LO Frequency• IDU detection at ODU startup improvement• Inhibition of the reading ODU remote received power level interruption, for ATPC• Correction of a bug in the temperature regulation for the overload attenuator• Modification of DCA thresholds, for UxFlat• Configuration saving on data changed only, for UxFlat• New Perseo parameters to improve 16QAM/8E1, for UxFlat• Use of MVT detection for all the rates in 4QAM, for UxFlat• New Perseo parameters to improve 4QAM/8E1, for UxFlat
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
4–3.4 Restrictions and known problems
– For a corrected operation, only on some PC with Windows 2000 or XP using serial connection, dueto an unidentified problem to be solved by ECT Platform, it is necessary to start Low Layers Managerbefore to start ECT Platform (Alcatel 1320CT).
– Alarm Surveillance: the application closure is followed by a message error (with Windows NT only).No impact in the functionality.
– At first activation sometimes, after NES opening, the message “ANTP: Unrecoverable error” appearsalso with ANTP deactivasted (with Windows NT only).No impact in the functionality.
4–3.5 Operative hints
a ) Installation procedure
It is the same of previous version 1.0.0 but it is necessary to select “Forced” option on CT screen forSW Download activation request. This warning has been introduced in relevant procedures:
• para.1–2.3 on page 46
• chapter 1–3 on page 47
b ) Configuration change from “1+0 extendable” to “1+1” (9400AWY only)
Some ways to proceed for this configuration change do not give good results. The suggestedprocedure has been introduced in para.2–3.1.3 on page 100.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
SECTION 5: APPENDICES
SECTION CONTENT PAGE
Appendix A – Equipment description and componentsThis Appendix sums–up the equipment functions and defines its components fromthe SW point of view.
205
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.
213
Appendix C – General on SWP installationThis Appendix introduces the basic information regarding the software installation.
221
Appendix D – 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.
225
Appendix E – 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.
235
Appendix F – Acronyms and abbreviations 251
Appendix G – Glossary of terms 255
The symbol points out references to Other Handbooks.
Referenced handbook P/Ns are given in para.E.2 on page 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
204
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
APPENDIX A : EQUIPMENT DESCRIPTION AND COMPONENTS
This appendix sums–up the equipment functions and defines its components from the SW point of view:
– Functions and configurations on page 206
– IDU and ODU Components on page 207:
• IDU on page 207
• ODU on page 208
• Allowed Equipment Types on page 209
• Remote Inventory Management on page 211
For more detailed in formation from the hardware point of view, please refer to:
9400 AWY Technical Handbook
or:
9400 FSO Technical Handbook
From the software point of view, the equipment management is carried out as explained in Section 2AWY/FSO NE MANAGEMENT on page 49, in chapters relevant to the EQUIPMENT CONFIGURATIONMANAGEMENT .
The equipment type HSW indicated in Tab. 18. on page 210 is managed from SWP Version1.0.1 (it is not managed by SWP Version 1.0.0).
The equipment type M2460 indicated in Tab. 17. Tab. 18. on page 210 is managed but is notphysically available.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
A.1 : Functions and configurations
ULS NE (9400AWY and 9400FSO) has the aim to multiplexer/demultiplexer the main tributaries (up to 16E1/16 DS1 or 1 E3/1 DS3) with different modulation formats.The following Tab. 15. summarizes the relation among market, product type tributaries and modulation.
Tab. 15. Markets, product type, tributaries and modulations forecasted
Market Product Type Tributary Modulation
2xE1 4QAM
4xE1 4QAM / 16QAM
AWY 8xE1 4QAM /16QAM
ETSI 16xE1 4QAM / 16QAM
1xE3 4QAM / 16QAM
FSO16xE1 4PSK
FSO1xE3 4PSK
4xDS1 4QAM
ANSI AWY8xDS1 4QAM / 16QAM
ANSI AWY16xDS1 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. 15. ) and generates a PDH frame.The demultiplexer function receives a PDH frame and generates main tributaries.
– Signal Protection switch (if any)The function provides one protection channel for the main signal against channel–associated failuresfor both hardware failures and temporary signals degradation or losses due to propagation effects(e.g. rain) according to equipment configuration.
– Radio Physical Interface (AWY)The function converts a radio frequency signal into an internal logic level signal, and vice versa(RPPI). Specifically, the following functions are performed:• Modulation and Tx functions in the transmit side• Demodulation and Rx functions in the receive side
– Free Space Optics (FSO)The function converts an optical signal into an internal logic level signal, and vice versa. 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 channel (1+0 configurations and 1+0 extendible configurations);– two channels (1+1 configurations).
The FSO is supported only in 1+0 configuration. The 2+0 and N+1 configurations are 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
207
02
/3DB 05653 CA AA
258
258
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.
A.2.1 : IDU
The indoor part is composed by one shelf (see Fig. 139. and Fig. 140. ). It contains the following units:
– (1+0) IDU• slot 1: ACCESS Unit• slot 2: Main Unit
slot 1: ACCESS Unit
slot 2: MAIN Unit
Fig. 139. (1+0) IDU
– (1+1) IDU• slot 1: ACCESS Unit• slot 2: Extension Unit• slot 3: Main Unit• slot 4: FAN unit
slot 1: ACCESS Unit
slot 2: EXTENSION Unit (N.B.)
slot 3: MAIN Unit
slot 4:FANUnit
(N.B.)
Fig. 140. (1+1) IDU
N.B. In the 1+1 sub–equipped configurations (1+0 EXPANDABLE), slots 2 and 4 are not used.
The ACCESS unit accommodates the connectors referred to E1/E3/DS1/DS3 tributaries, user servicechannel, housekeeping and summarizing, NMS V11 and G703 interfaces, and a telephone jack.
The Main Unit contains the MULDEM, the PQECRC and the Power Supply units. The MULDEM unitmanages the ETSI 1xE3/16xE1 and ANSI 1xDS3/16xDS1 tributaries, the Mux/Demux and the cableinterface functions. The PQECRC unit implements the Equipment and IDU Controller functions. The Dataunit implementing Ethernet functions can be plugged onto the Main unit. It is not supported in the currentrelease. The Main unit is used both in 1+0 and 1+1 configurations.
The Extension Unit contains the MULDEM and the Power Supply units. The Hitless unit and the Data unitimplementing Ethernet functions can be plugged onto the Extension unit. Data unit is not supported in thecurrent release. The Extension unit is used only in 1+1 configurations.
The FAN unit contains fans in order to provide the necessary ventilation to the IDU shelf (t is supportedonly in 1+1 configurations). Only the FAN unit is shown at SNMP interface, independently from the numberof fans composing 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
208
02
/3DB 05653 CA AA
258
258
A.2.2 : ODU
According to the configuration type, two ODU types are managed in the Outdoor part. They can be:– ODU (electrical ODU)– ODUFSO (optical ODU)
The ODU type is implicitly defined by the NE configuration. Each ODU contains a PQECRC unit whichimplements the ODU Controller functions.
ODU / ODUFSO
Fig. 141. (1+0) ODU (electrical or optical)
ODU Ch#1 ODU Ch#2
Fig. 142. (1+1) ODU (only electrical)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
A.2.3 : Allowed Equipment Types
This paragraph provides information on the allowed equipment types for all the configurations supportedby ULS NE.
[1] Shelves Equipment Types
The following Tab. 16. provides the shelves equipment types allowed for each supported NEconfiguration and market type:
Tab. 16. Shelves Equipment Types
NEConfiguration
MarketType
Shelfposition
Allowed Equipment TypeDescription
AllowedEquipment
Type
EquipmentLabel
(note 1) 1 IDU 1+0 Shelf IDU10 IDU
1+0 ETSI2
ODU 1+0 4/16 QAM ETSI ODU–EODU Ch#1
ANSI2
ODU 1+0 4/16 QAM ANSI ODU–AODU Ch#1
1+0 FSO(note 1) 1 IDU 1+0 Shelf IDU10 IDU
1+0 FSOETSI 2 ODU 1+0 FSO ETSI ODUFSO–E ODUFSO
(note 1) 1 IDU 1+1 Shelf IDU11 IDU
1 1ETSI
2ODU 1+0 4/16 QAM ETSI ODU–E
ODU Ch#11+1(note 2)
ANSI2
ODU 1+0 4/16 QAM ANSI ODU–AODU Ch#1
(note 2)ETSI
3ODU 1+0 4/16 QAM ETSI ODU–E
ODU Ch#0ANSI
3ODU 1+0 4/16 QAM ANSI ODU–A
ODU Ch#0
(note 1) The equipment types allowed for IDU shelf are market type independent.
(note 2) All the 1+1 configurations. In case of 1+0 extendible configurations shelf position 3 is notsupported.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
[2] : Slots and Sub–slots Equipment Types
The following tables indicate the allowed equipment types for each slot inside each shelf type andif the equipment expected value is settable by the operator.
• IDU
Tab. 17. IDU allowed board/plug–in types in (1+0) configurations
IDU10
Position Allowed Equipment Type DescriptionAllowed
EquipmentType
EquipmentLabel
1.1 Access Unit ACCESS IDU/ACCESS
1.2Main Unit Full Range Supply (±24/±60 V)
Main Unit ±48/±60 V Range SupplyMain Unit ±48/±60 V Range High Power Supply (N.B.)
M2460M4860
M4860H
IDU/MAINCh#1
N.B. This power supply (“high power” version) is allowed only in case of 1+0 FSO configuration.
Tab. 18. IDU allowed board/plug–in types in (1+1) configurations
IDU11
Position Allowed Equipment Type DescriptionAllowed
EquipmentType
EquipmentLabel
1.1 Access Unit ACCESS IDU/ACCESS
1.2(note 1)
Not provisionedExtension Unit Full Range Supply (±24/±60 V)
Extension Unit ±48/±60 V Range Supply
EMPTYE2460E4860
IDU/EXT Ch#0
1.2.1(note 2)
Hitless Switch unit (not implemented) HSWIDU/EXT/HSW
Ch#0
1.3Main Unit Full Range Supply (±24/±60 V)
Main Unit ±48/±60 V Range SupplyM2460M4860
IDU/MAIN Ch#1
1.4 FAN unit FAN IDU/FAN
(note 1) In the 1+1 sub–equipped configurations this slot is empty.
(note 2) Position 1.2.1 is created only in the 1+1 Hitless configurations (HST and FD).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
• Electrical ODUNo slot can be defined inside the Electrical ODU.
• Optical ODU
Tab. 19. Allowed board types in optical ODU ETSI
ODUFSO–E
Position Allowed Equipment Type DescriptionAllowed
EquipmentType
EquipmentLabel
2.1 Optical Interface ETSI board OPINT–E ODUFSO/OPINT
2.2 Optical Transceiver board OPTR ODUFSO/OPTR
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 will be provided by the following equipmenttypes:– Main Unit (M2460, M4860, M4860H)– Extension Unit (E2460, E4860)– Hitless Switch Unit (HSW) (not implemented)– Access Unit (ACCESS)– FAN unit (FAN)– ODU unit (ODU–E, ODU–A )– ODU FSO unit (ODUFSO–E)
For all the other equipment types the remoteInventoryStatus columnar object assumes the value“unavailable”.The RI data of each sub–components unit (i.e. MULDEM in the IDU, MILOU in the ODU, OPTR in theODUFSO) won’t be seen at 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 are provided in its own remote inventory data this type of information. It isused to identify the actual equipment type and then, eventually, to provide an equipment mismatch alarm,if the equipment type read from remote inventory data is different from the equipment expected providedby the managers.If it isn’t possible to read the Remote Inventory information, a “Card Fail” alarm is declared.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
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 216– the general characteristics of the ECT and RECT, on page 218.
Fig. 143. herebelow shows the Interfaces for equipment control
Fig. 144. herebelow shows the MAIN UNIT + FLASH CARD unit assembly view
Fig. 145. herebelow shows the FLASH CARD profile and insertion direction
Ethernet Interfacefor OS connection
F Interfacefor ECT connection
Flash cardlabel
Fig. 143. Interfaces for equipment control and Flash card label on MAIN Unit
FLASH CARD
EQUIPMENT CONTROLLER BABY BOARD (PQ/ECRC)
MAIN BOARD
FRONT PLATE
Fig. 144. MAIN unit + FLASH CARD
TOP SIDE
INSERTION
Fig. 145. 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
214
02
/3DB 05653 CA AA
258
258
B.1 : Allocation of equipment and craft terminal software
Fig. 146. 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+0compact/expandable configurations).
FLASHCARD
EQUIPMENTCONTROLLER
RAM
MULDEMSUBUNIT
PQ/ECRC SUBUNIT
F
Ethernet
MAIN UNIT
EXTENSION UNIT
RT–0
ODUCONTROLLER
MULDEMSUBUNIT
FLASHEPROM
RAM
RT–1
ODUCONTROLLER
FLASHEPROM
RAM
Fig. 146. 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
215
02
/3DB 05653 CA AA
258
258
c ) Local software allocation
Once the system has been configured and activated (as explained in Section 1 Installation),Equipment and Craft Terminal must not necessarily be left connected, because equipment containsall the software necessary for its working.
This equipment local software comprises programs and configuration data. Programs and data aremanaged differently from each other:
1 ) Equipment ControllerWhole Equipment SW (programs and configuration data) is contained in the Flash Card housedin MAIN 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. 144. andFig. 145. on page 213.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, the Flash Card contains two independent instances of the Equipment SWprograms (one active, the other stand–by), so that the above cited SW download is actuallydone toward the stand–by instance, while equipment goes on working with the SW programsof the active instance. Swapping between the two instances is done only under Operator’srequest.
2 ) Peripheral UnitsThe Peripheral units (RTs) contain their own local SW (programs and configuration data),housed in a local Flash Eprom (physically not removable). The programs in this local FlashEprom can be overwritten by means of a SW download from the Equipment Controller with thesame active–standby duplication described before for the Equipment Controller.
3 ) Equipment Configuration Data (MIB)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 217 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
216
02
/3DB 05653 CA AA
258
258
B.2 : Flash Card
B.2.1 : Flash Card types
A FLASH CARD is plugged into the Main board (see Fig. 144. on page 213) giving the maximum capacityfor the tributaries and the modulation type as reported in the following Tab. 20. (5 possible types of Flashcard).
Tab. 20. Available Flash cards
Flash Card Name Capacity Modulation
Full Flexible Flash Card Full flexible Full flexible
16xE1/DS1 16 QAM Flash Card Full flexible 16 QAM
4xE1/DS1 16 QAM Flash Card Up to 4xE1/DS1 16 QAM
16xE1/DS1 4 QAM Flash Card Full flexible 4 QAM
4xE1/DS1 4 QAM Flash Card Up to 4xE1/DS1 4 QAM
Notes:
1 ) A 16 QAM Flash card does not allow the transmission of a 4 QAM signal.
2 ) A 4xE1/DS1 Flash Card does not allow the transmission of a capacity greater than 4xE1/DS1.
3 ) As far as E3/DS3 tributary rate is concerned, only the Full Flexible Flash card can be selected.
4 ) The Full Flexible Flash Card allows the transmission of whatever capacity and modulation.
5 ) In 9400FSO equipment, only the Full Flexible Flash Card can be used.
6 ) For the P/Ns of the Flash Card types please refer to the:
9400 AWY/FSO Technical Handbook,section “System composition and configurations”
chapter “IDU part list“
B.2.2 : Flash Card identification
a ) the Flash Card P/N 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. 143. on page 213).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
B.2.3 : Flash Card contentsThe following table indicates the FLASH CARD contents in the various phases of SW management:
NE DATA
PHASEBASE
CONFIGURATIONSW PROGRAMS ROUTING
CONFIGURATIONn.b.2
MIBn.b.1
1 ) As suppliedby Factory Defined by Flash
Not present Not present Not present
2 ) After SWPdownload
yCard P/N.Not changeable,but with Flash Present
To be defined byC.T.
To be defined byC.T.
3 ) After NE datadefinition
but with FlashCard upgrade(see para B.2.4
Present
Present Present
MODIFICABILITY⇒
(see para B.2.4herebelow) By a new SWP
download n.b.4Yes, by C.T. Yes, by C.T.
SAVE/RESTORE⇒ NO Unmeaningful NO NO n.b.3
NE= Network Element C.T. = Craft Terminal SWP= Software Package
n.b.1 MIBThe system configuration data set is named MIB. Such data are defined by Craft Terminal afterthe SWP download. They can be changed only within the limits implicitly defined by theemployed Flash Card type. For its save/restore refer to n.b.3 herebelow.
n.b.2 ROUTING CONFIGURATION DATAThey are:
1. Local configuration ⇒ System’s local address2. NTP server configuration3. Interface configuration ⇒ NMS configuration
⇒ Ethernet configuration4. IP configuration ⇒ IP Static Routing configuration
⇒ OSPF AREA configuration
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.
n.b.3 The MIB file save/restore to/from a file in the Craft Terminal (or OS) environment is not possiblein SWP first version(s). It should be possible in future versions(s).
n.b.4 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.E.2.5.2 on page 247.
B.2.4 : Flash Card upgrade (for 9400AWY only)Refer to the instructions given in the:
9400AWY Technical Handbook, section “System composition and configurations”chapter “IDU operative information“, para.”Flash Card”
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
B.3 : Equipment control
B.3.1 : Interfaces (see Fig. 143. on page 213):
• 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 para.B.3 on page 218
– remote through a ECT–equipment connection via public switched telephone network, asexplained in Appendix D on page 225.
B.3.2 : Operator–Equipment Interaction
1 ) The Local Operator can manage the Equipment software programs and most configuration datathrough the Equipment Craft Terminal 1320CT connected to the F interface (see Fig. 146. onpage 214 and Fig. 143. on page 213).The Craft Terminal characteristics (computer configuration) are listed in chapter 4–2 on page195.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 CraftTerminal application.
The general information on the Craft Terminal is presented in the:
1320CT Basic Craft Terminal Operator’s Handbook
that the operator has to read before this Handbook.In this Handbook is given the general description regarding use, navigation, rules, etc., commonto all the NE using the same Craft Terminal.Furthermore, the same handbook contains the detailed description of common operations as“Installation” and common screens as “Network Element Synthesis view”.The Network Element Synthesis view is the first view presented to the operator entering 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 directlyallows to manage the Network Element.
A detailed description of the AWY/FSO’s EML–ULS screens is given in the dedicated Sections
2–AWY/FSO NE MANAGEMENT and 3–AWY/FSO MAINTENANCE 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
219
02
/3DB 05653 CA AA
258
258
2 ) A further SW application, also available in the PC and OS environment and named SIBDL(Standard Image Binary Download), deals with the SW download in special cases, which aredetailed in the following. The physical interface for running this application from Craft Terminalis ’F’ interface.The installation and use of SIBDL is detailed in the dedicated Section of the:
9400AWY Line Up Guide
or
9400FSO Line Up Guide
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 9600USY&MDR9000s station an ALCATEL proprietary SWP (SoftWare Package) isemployed, which depends on the product–release and the NE (Network Element) associated to thespecific configuration.
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
220
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
APPENDIX C : GENERAL ON SWP INSTALLATION
This Appendix introduces the basic information regarding the software installation.
N.B. Before reading this paragraph, it is suggested to read (if not yet done) previous para.B.1 onpage 214.
Fig. 147. depicts the main phases for SW management.
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
Fig. 147. 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
222
02
/3DB 05653 CA AA
258
258
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
• (3) NE SWP downloading from ECT toward the Network–Element’s Equipment Controller (EC)
• (4) SW downloading from EC toward the Peripheral Units.
– NE configuration data management:
• (5) NE configuration data definition.
The 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–1 on page 21
– SWP download toward NEthat includes tasks (3) to (5) mentioned above.The relevant operating instructions are given in chapter 1–2 on page 45
These main procedures are usually carried out sequentially; some different situations are described inpara.C.2 on page 223.
Furthermore, additional procedures are envisaged to be used in special situations, as described inpara.C.1 herebelow.
C.1 : Troubleshooting situations
In the following situations:
1 ) Flash Card to be replaced
or:
2 ) NE not in–factory configured
use the SW download through SIBDL program; refer to the dedicated section of the:
9400AWY Line Up Guide
or
9400FSO Line Up Guide
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
C.2 : Common situations
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 preliminary actions.
2 ) Network Element already configured with the more recent SWP version, but the CraftTerminal is not available or has a version older with respect to that of the NetworkElement(s).
A.B.c
ECT
A.B.d
NE
ECT release = NE release
ECT version < NE version
In this case, carry out SWP installation in Craft Terminal environment as explained in Chapter1–1 on page 21. After that, the situation is equal to that of point 1 ) above.
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.1.0.0), in the case a newer version of the same A.B SWP package has to be installed(e.g.1.0.1).
Refer to Chapter 1–3 on page 47.After that, the situation is equal to that of point 1 ) above.
N.B. Please refer to para.E.2.5.2 on page 247 for the meaning of SWP Release, Version and PatchLevel.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
APPENDIX D : ECT–EQUIPMENT CONNECTION VIA PUBLIC SWITCHEDTELEPHONE NETWORK
D.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. 148. 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. 148. 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
226
02
/3DB 05653 CA AA
258
258
D.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 195
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
227
02
/3DB 05653 CA AA
258
258
D.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. 149. 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. 150. 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
228
02
/3DB 05653 CA AA
258
258
D.4 : Modem setting
D.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. 148. on page 225 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. 149. onpage 227.
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
229
02
/3DB 05653 CA AA
258
258
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
230
02
/3DB 05653 CA AA
258
258
D.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. 151. 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. 151. TD–32 AC modem dip–switch setting
2 ) Connect the local modem to the PC/ECT with the cable of Fig. 149. on page 227.
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:
* Bits per second: 38400* Data Bits: 8* Parity: None* Stop Bit: 1* Flow control: None
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
231
02
/3DB 05653 CA AA
258
258
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
D.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
232
02
/3DB 05653 CA AA
258
258
D.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. 148. on page 225 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. 150. on page 227.
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. 149. on page 227.) 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:
* Bits per second: 38400* Data Bits: 8* Parity: None* Stop Bit: 1* Flow control: None
9 ) For PC laptop Dell Latitude only, type the following command inside HyperTerminal program:’AT&C0&D0&R1’
N.B. this command must be typed every time the Hyper terminal session is opened (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
233
02
/3DB 05653 CA AA
258
258
D.7 : Changing the ECT–equipment connection speed
D.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.D.7.2 on page 234.
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 UNACCESSIBILITY.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
D.7.2 : Configuration at PC side
N.B. Please read carefully paragraph Introduction on page 233.
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. 152. opens.
Fig. 152. 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
235
02
/3DB 05653 CA AA
258
258
APPENDIX E : DOCUMENTATION GUIDE
This appendix contains all information regarding:
– this handbook, herebelow
– the Customer Documentation set this handbook belongs to, on page 240
E.1 : Handbook guide
This paragraph contains all information regarding this handbook:
– Handbook applicability on page 236
– Purpose of the handbook on page 237
– Handbook history on page 238
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
E.1.1 : Handbook applicability
a ) Product-release applicabilityThis handbook applies to the following product-releases:
• 1+0 or 1+1 for Radio application 9400AWY
PRODUCT RELEASE ANV P/N FACTORY P/N
9411AWY 1.00.00 3DB 05476 AAAA 522.174.410
9413AWY 1.00.00 3DB 05478 AAAA 522.174.500
9415AWY 1.00.00 3DB 05481 AAAA 522.174.600
9418AWY 1.00.00 3DB 04729 AAAA 522.174.000
9423AWY 1.00.00 3DB 05484 AAAA 522.174.700
9425AWY 1.00.00 3DB 05490 AAAA 522.174.900
9428AWY 1.00.00 3DB 05493 AAAA 522.175.000
9432AWY 1.00.00 3DB 05496 AAAA 522.175.100
9438AWY 1.00.00 3DB 04732 AAAA 522.144.100
• 1+0 for Free Space Optics application 9400FSO
PRODUCT RELEASE ANV P/N FACTORY P/N
9400FSO 1.00.00 3DB 04263 AAAA 522.173.500
b ) NE applicabilityThis handbook applies to the following Network Elements (NE): ULS
c ) SWP Version applicabilityThis handbook applies to the following Software Package Releases (SWP) and SWP versions:
SWP ReleaseSWP ANV &
FACTORY P/NSWP Version
(N.B.1)
SWP 9400AWY R 1 0 CD–ROM ref Tab 13 on page 193V.1.0.0 (N.B.2)
SWP 9400AWY R.1.0 CD–ROM ref.Tab. 13. on page 193V.1.0.1 (N.B.3)
N.B.1 For the meaning of SWP Release and Version, please refer to para.E.2.5.2 on page 247.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.
N.B.2: Version 1.0.0 manages the Radio application only (1+0 configuration).N.B.3: Version 1.0.1 manages the Radio application (1+0 and 1+1 configurations) and the FSO
application.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
E.1.2 : Purpose of the handbook
This handbook belongs to the Customer Documentation set envisaged for the equipment specified in para.E.1.1 on page 236.Please refer to para.E.2 on page 240 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. E.1.1 on page 236).
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:
– 9400 AWY Technical Handbook Ed.01 for the Radio application.
– 9400 FSO Technical Handbook Ed.01 for the FSO application.
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 (N.B.), 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
238
02
/3DB 05653 CA AA
258
258
E.1.3 : Handbook history
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. 21. indicates the handbook parts new and modified with respect to the previous edition.
Legendn = new part m = modified part blank= part unchanged
Tab. 21. Handbook historyHANDBOOK EDITION ⇒ 01 02 03 04 05
FRONT MATTER n
Preliminary information n
Handbook applicability, purpose and history n
Handbook structure n
Safety–EMC–ESD norms and equipment labelling n
Quick guide n m
SECTION 1: INSTALLATION n m
1–1 SWP installation in PC environment n m
1–2 SWP download toward NE n m
1–3 NE Upgrade to a newer SWP ’version’ (same SWP ’release’)ÉÉÉÉÉÉ
n
SECTION 2: AWY/FSO NE MANAGEMENT n
2–1 General introduction on views and menus n m
2–2 Configuration n
2–3 Equipment n m
2–4 Line Interface n
2–5 Radio n
2–6 FSO n m
2–7 External input and output points n m
2–8 Supervision n
2–9 Protection schemes n m
2–10 Loopbacks n
2–11 Diagnosis n
2–12 Performance Monitoring n
2–13 Software Management n
SECTION 3: AWY/FSO NE MAINTENANCE n
3–1 Maintenance introduction n
3–2 Troubleshooting n
table continues
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Tab. 21. Handbook historyHANDBOOK EDITION ⇒ 0504030201
SECTION 4: SWP DESCRIPTION AND VERSIONS n m
4–1 SWP REG.9400AWY R.1.0 description n
4–2 SWP REG.9400AWY R.1.0 V.1.0.0 specific information n m
4–3 SWP REG.9400AWY R.1.0 V.1.0.1 specific informationÉÉÉÉÉÉ n
SECTION 5: APPENDICES n
A Equipment description and components n
B SW allocation, Flash Card and equipment control n m
C General on SWP installation n m
DECT–Equipment connection via public switched telephonenetwork
n
E Documentation Guide n m
F Acronyms and abbreviations n
G Glossary of terms n
E.1.3.1: Notes on draft editions
Draft editions neither validated nor officially released issue, for internal validation purposes:
– Ed.01A–DRAFT created on December 12th, 2003– Ed.01B–DRAFT created on January 26th, 2004– Ed.01C–DRAFT created on March 9th, 2004
E.1.3.2: Notes on Ed.01
Ed.01 created on May 19th, 2004 is the first released and validated version of the handbook.
E.1.3.3: Notes on Ed.02
Ed.02 created on July 23rd, 2004 is the second released and validated version of the handbook.This issue has been done to align the handbook to the new features of SWP version V.1.0.1; for a summary,see new Chapter 4–3 SWP R.1.0 V.1.0.1 specific information in section SWP DESCRIPTION ANDVERSIONS.Changes related to this new versions have been introduced throughout the handbook, where necessary.This edition can be used also with previous version V1.0.0.Errors found in previous edition have been corrected.Revision bars point out major (listed above) and minor (not listed above) modifications with respect toprevious edition.Revision bars in correspondence of empty lines or empty table rows, point out parts eliminated or shiftedin other places of the 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
240
02
/3DB 05653 CA AA
258
258
E.2 : Documentation set description
This paragraph contains all information regarding the Customer Documentation set this handbookbelongs to:
– 9400AWY Rel.1.0 product–release–version handbooks on page 241
– 9400FSO Rel.1.0 product–release–version handbooks on page 243
– Handbooks common to 9400AWY Rel.1.0 and 9400FSO Rel.1.0 on page 245
– Specific documentation for SNMP on page 246
– General on Alcatel Customer Documentation on page 246 including:
• Customer–Independent Standard Customer Documentation on page 246
• Product levels and associated Customer Documentation on page 247
• Handbook and CD–ROM supply to Customers on page 249
The list of handbooks given in the following is valid as at the issue date ofthis Handbook and can be changed without any obligation for ALCATELto update it in this Handbook.
Some of the handbooks listed in the following may not be available as atthe issue date 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
241
02
/3DB 05653 CA AA
258
258
E.2.1 : 9400AWY Rel.1.0 product–release–version handbooks
This paragraph lists and briefly describes the handbooks making up the documentation set envisaged for9400AWY Rel.1.0 product release.
Please refer to following para.E.2.5 on page 246 for a general description of Alcatel CustomerDocumentation system.
The standard Customer Documentation in the English language for the 9400AWY Rel.1.0 system ismodularly composed by different handbooks.
Tab. 22. herebelow lists the handbooks.
The [REF] indication in Tab. 22. is relevant to the handbook brief description given in tables Tab. 23. thru’Tab. 25. and Tab. 30. thru’ Tab. 31. in the following.
Tab. 22. 9400AWY Rel.1.0 product release handbooks
TECHNICAL HANDBOOK REF
9400AWY Technical Handbook [A]
INSTALLATION AND LINE–UP HANDBOOKS
9400AWY Installation Handbook [B]
9400AWY Line–up Guide [C]
OPERATOR’S HANDBOOKS (in alternative, according to SWP used)
9400AWY/FSO CT Operator’s Handbook SWP 1.0 [I]
9400AWY/FSO CT Operator’s Handbook SWP 1.1 [J]
DOCUMENTATION CD–ROM
DCP 9400AWY R.1.0 CD_ROM [D]
1320 CT OPERATOR’S HANDBOOKS
– 1320CT Basic Operator’s Handbook– AS Operator’s Handbook– ELB Operator’s Handbooksee Tab. 31. on page 245
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Tab. 23. 9400AWY Rel.1.0 Technical Handbook
REF HANDBOOKANV P/N
Factory P/NNOTES
[A]
9400 AWY Rel. 1.0 Technical Handbook3DB 05653 BAAA
without Factory P/N[A]
It provides information regarding AWY equipment description and composition, stationlayouts, hardware setting documentation and maintenance.
Tab. 24. 9400AWY Rel.1.0 Installation and Line–Up Handbooks
• The Installation Handbook provides information regarding Equipment installation, accordingto Alcatel Installation Engineering Dept. rules.
• The Line–up Guide provides information regarding equipment line up and commissioning,according to Alcatel Installation Engineering Dept. rules.
REF HANDBOOKANV P/N
Factory P/NNOTES
[B] 9400 AWY Rel.1.0 Installation Handbook3DB 05653 DAAA
without Factory P/N
[C] 9400 AWY Rel.1.0 Line–up Guide3DB 05653 EAAA
without Factory P/N
Tab. 25. 9400AWY Rel.1.0 Documentation on CD–ROM
REF CD–ROM TITLEANV P/N
Factory P/NNOTES
DCP 9400AWY 1.0 CD_ROM3DB 05653 AAAA
417.200.029
[D] Contains, in electronic format (ACROBAT pdf files), all handbooks listed in Tab. 22. onpage 241 (when all envisaged handbooks are released), with exception of 1320 CTOperator’s Handbooks
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
E.2.2 : 9400FSO Rel.1.0 product–release–version handbooks
This paragraph lists and briefly describes the handbooks making up the documentation set envisaged for9400FSO Rel.1.0 product release.
Please refer to following para.E.2.5 on page 246 for a general description of Alcatel CustomerDocumentation system.
The standard Customer Documentation in the English language for the 9400FSO Rel.1.0 system ismodularly composed by different handbooks.
Tab. 26. herebelow lists the handbooks.
The [REF] indication in Tab. 26. is relevant to the handbook brief description given in tables Tab. 27. thru’Tab. 31. in the following.
Tab. 26. 9400FSO Rel.1.0 product release handbooks
TECHNICAL HANDBOOK REF
9400FSO Technical Handbook [E]
INSTALLATION AND LINE–UP HANDBOOKS
9400FSO Installation Handbook [F]
9400FSO Line–up Guide [G]
OPERATOR’S HANDBOOKS (in alternative, according to SWP used)
9400AWY/FSO CT Operator’s Handbook SWP 1.0 [I]
9400AWY/FSO CT Operator’s Handbook SWP 1.1 [J]
DOCUMENTATION CD–ROM
DCP 9400FSO R.1.0 CD_ROM [H]
1320 CT OPERATOR’S HANDBOOKS
– 1320CT Basic Operator’s Handbook– AS Operator’s Handbook– ELB Operator’s Handbooksee Tab. 31. on page 245
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
Tab. 27. 9400FSO Rel.1.0 Technical Handbook
REF HANDBOOKANV P/N
Factory P/NNOTES
[E]
9400FSO Rel.1.0 Technical Handbook3DB 05654 BAAA
without Factory P/N[E]
It provides information regarding FSO equipment description and composition, stationlayouts, hardware setting documentation and maintenance.
Tab. 28. 9400FSO Rel.1.0 Installation and Line–Up Handbooks
• The Installation Handbook provides information regarding Equipment installation, accordingto Alcatel Installation Engineering Dept. rules.
• The Line–up Guide provides information regarding equipment line up and commissioning,according to Alcatel Installation Engineering Dept. rules.
REF HANDBOOKANV P/N
Factory P/NNOTES
[F] 9400FSO Rel.1.0 Installation Handbook3DB 05654 CAAA
without Factory P/N
[G] 9400FSO Rel.1.0 Line–up Guide3DB 05654 DAAA
without Factory P/N
Tab. 29. 9400AWY Rel.1.0 Documentation on CD–ROM
REF CD–ROM TITLEANV P/N
Factory P/NNOTES
DCP 9400FSO 1.0 CD_ROM3DB 05654 AAAA
417.200.030
[H] Contains, in electronic format (ACROBAT pdf files), all handbooks listed in Tab. 26. onpage 243 (when all envisaged handbooks are released), with exception of 1320 CTOperator’s Handbooks
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
E.2.3 : Handbooks common to 9400AWY Rel.1.0 and 9400FSO Rel.1.0
Tab. 30. Operator’s Handbooks related to the specific Software Package SWP
REF HANDBOOKANV P/N
Factory P/NNOTES
[I]9400 AWY/FSO Rel.1.0CT Operator’s Handbook SWP 1.0
3DB 05653 CAAAwithout Factory P/N
nb1this handbook
[J]9400 AWY/FSO Rel.1.0CT Operator’s Handbook SWP 1.1
3DB 05653 FAAAwithout Factory P/N
nb2
Provides AWY/FSO SWP screens and operational procedures for Equipment SW management andmaintenance.
nb1 SWP identification: ref.Tab. 13. on page 193
nb2 SWP identification: t.b.d.
Tab. 31. Documentation common to Alcatel Network Elements using 1320CT platform
REFQ3CT–PVersion(N.B.)
HANDBOOKANV P/N
Factory P/NNOTES
[K]
� 3.0.11320CT Rel.3.xBasic Operator’s Handbook
3AL 79551 AAAA
957.140.042 N[K]
Provides general information and operational procedures common to all 1320CT (Craftterminal) of Alcatel InfoModel Network Elements.
[L]
� 3.0.1AS Rel.6.5Operator’s Handbook
3AL 88876 AAAAwithout Factory P/N
[L]Provides detailed information and operational procedures regarding the alarm Surveillancesoftware embedded in the 1320CT software package.
[M]
� 3.0.1ELB Rel.2.xOperator’s Handbook
3AL 88877 AAAAwithout Factory P/N
[M]Provides detailed information and operational procedures regarding the Event Log Browsersoftware embedded in the 1320CT software package.
[N]� 3.0.1
DCP 1320 CT 3.x CD_ROM EN
3AL 79552 AAAA417.100.032
[N]
Contains, in electronic format, the 1320 CT Operator’s Handbook REF.[K] to [N]
N.B. The CT Version is displayed when, on the PC, you select the 1320CT application for itslaunch. The Q3CT–P/K Version embedded in the SWP this handbook refers to, is specifiedin the paragraph ECT SW Sub–Components of chapter (in Section 4 – SWPDESCRIPTION AND VERSIONS) related to the SWP version you use.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
E.2.4 : Specific documentation for SNMP
The documents relevant to SNMP are not available as individual items, but are directly included in theSNMP SWP CD–ROMs themselves.
E.2.5 : 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.
E.2.5.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
247
02
/3DB 05653 CA AA
258
258
E.2.5.2: Product levels and associated Customer Documentation
See Fig. 154. on page 248.
a ) ProductsA ”product” is defined by the network hierarchical level where it can be inserted and by the wholeof performances and services that it is meant for.E.g. 9400AWY is a product.
b ) Product-releasesA ”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 ElementsIn 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. 153. 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 purposesor minor additional features
1. 0. 7or minor additional features(same SWP Release within sameProduct–Release)
1. 0. 9
SWP evolution for 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. 153. 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
248
02
/3DB 05653 CA AA
258
258
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. 154. 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
249
02
/3DB 05653 CA AA
258
258
E.2.5.3: Handbook and CD–ROM supply to Customers
a ) Standard supply
Handbooks and CD–ROMs are standard commercial items and are ordered and delivered as anyother Alcatel commercial item.Handbooks and CD–ROMs are not automatically delivered together with the equipment they referto.The number of handbooks or CD–ROMs per type to be supplied must be decided at contract level.
b ) Product–documentation consistency
Equipment 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 handbooks regarding a specific product–release previously delivered can be requiredspecifying P/N and edition.
c ) In–advance supply
Whenever handbooks or CD–ROMs are delivered before the relevant equipment delivery, there isthe risk that their contents might not agree with the characteristics of the equipment which will bedelivered: the more they are in advance the less are they likely to agree.
d ) Supplying updated handbooks and CD–ROMs to Customers
Supplying updated handbooks or CD–ROMs to Customers who have already received previousissues is subject to commercial criteria.By updated handbook delivery, we mean the supply of a complete copy of a new issue of thehandbook (supplying errata–corrige sheets is not envisaged).
e ) Copyright notification
The 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.
f ) Supply to Customers of Customer Documentation source files
Presently not envisaged.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out 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
02
/3DB 05653 CA AA
258
258
APPENDIX F : ACRONYMS AND ABBREVIATIONS
N.B. For the explanation of the acronyms of the alarms refer to Section MAINTENANCEpara.3–2.4.1 Alarm synthesis indication on page 185.
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
252
02
/3DB 05653 CA AA
258
258
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
253
02
/3DB 05653 CA AA
258
258
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
254
02
/3DB 05653 CA AA
258
258
PM: Performance Monitoring
PPP:Point to Point Protocol
PSU: Power Supply Unit
QAM: Quadrature Amplitude Modulation
QOS: Quality Of Service
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
255
02
/3DB 05653 CA AA
258
258
APPENDIX G : 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
256
02
/3DB 05653 CA AA
258
258
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
257
02
/3DB 05653 CA AA
258
258
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
258
02
/3DB 05653 CA AA
258
258
END OF DOCUMENT