Alcatel Tco Suite Rel.1.7 For 9400awy r.2.1 v2.1.3 User Manual PDF

AlcatelLucent TCO Suite
SWP TCO SUITE Rel.1.7

for 9400AWY R.2.0 V2.0.6 and 9400AWY R.2.1 V2.1.2 & V2.1.3
User Manual
3DB 75003 BAAA
Ed.01
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
2 / 232
3DB 75003 BAAA Ed.01
USER MANUAL
FRONT MATTER
i Navigation principles
This manual is delivered to Customers in electronic format only (file Adobe Acrobat pdf) inside the specific
SWP TCO SUITE Rel.1.7 CDROM.
This file can be used both in PC and Unix WS environments or any other environment for which a suitable
Acrobat Reader has been envisaged by Adobe.
In particular take into account that, in order to open correctly this pdf file, the use of Acrobat Reader Version
5.0 at least is mandatory. If opened with previous versions of Adobe Acrobat Reader, incomplete
document views will be produced.
For a comfortable navigation, two hyperlink types are present:
those inside the text window, marked by a blue rectangle around any crossreference to a figure,
table, part, section, chapter, paragraph, numbered list, and page: by clicking such a blue rectangle,
you are led to the referenced component
the bookmarks, present on the left side of the text window. They represent the online handbook
table of contents. Bookmarks can be expanded (clicking on [+] ) or reduced (clicking on [] ). By
clicking on one bookmark, you are led to the referenced part.
WARNING: the bookmark window is not visible if you use Acrobat reader in fullscreen modality.
For further information, refer to Acrobat reader help online.
If printed on paper by Users, it is suggested to divide this manual by numbered separators, for an easier
access to the information herein contained:
CONTENTS SEPARATOR
FRONT MATTER
ii Preliminary information
iii Structure of this manual
iv Notes on present edition
V Table of contents
SECTION 1 : TCO SUITE DESCRIPTION AND USAGE 1
SECTION 2 : APPENDICES 2
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
3 / 232 3DB 75003 BAAA Ed.01
USER MANUAL
FRONT MATTER
ii Preliminary information
a ) Warranty
Any warranty must be referred exclusively to the terms of the contract of sale of the equipment to
which this handbook refers to.
AlcatelLucent makes no warranty of any kind with regards to this manual, and specifically disclaims
the implied warranties of merchantability and fitness for a particular purpose. AlcatelLucent will not
be liable for errors contained herein or for damages, whether direct, indirect, consequential,
incidental, or special, in connection with the furnishing, performance, or use of this material.
b ) Information
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of AlcatelLucent.
c ) Copyright Notification
The technical information of this manual is the property of AlcatelLucent and must not be copied,
reproduced or disclosed to a third party without written consent.
d ) Safety recommendations
The safety recommendations here below must be considered to avoid injuries on persons and/or
damage to the equipment:
1 ) Service Personnel
Installation and service must be carried out by authorized persons having appropriate technical
training and experience necessary to be aware of hazardous operations during installation and
service, so as to prevent any personal injury or danger to other persons, as well as prevent
damaging the equipment.
2 ) Access to the Equipment
Access to the Equipment in use must be restricted to Service Personnel only.
3 ) Safety Rules
Recommended safety rules are indicated in the NE User Manual (see Tab. 1. on page 14 )
e ) Cautions to avoid equipment damage
Please refer to the NE User Manual (see Tab. 1. on page 14 )
f ) Service Personnel skill
Service Personnel must have an adequate technical background on telecommunications and in
particular on the AlcatelLucent 9400AWY Network Elements specified in Tab. 1. on page 14
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
4 / 232
USER MANUAL
FRONT MATTER
iii Structure of this manual
Information in this manual is divided into the following parts:
a ) Front matter
This part, with general information, and table of contents.
b ) SECTION 1 : TCO SUITE DESCRIPTION AND USAGE from page 11
This section describes the SWP TCO SUITE Rel.1.7 and its most frequently used functions.
c ) SECTION 2: APPENDICES from page 183
This section describes the less frequently used functions of the SWP TCO SUITE Rel.1.7, and
provides additional information.
d ) Handbook print and assembly instructions
This part (after handbook last page 232 ):
is not present in the handbook paper copy, if supplied by AlcatelLucent factory.
is present in the pdf file. Customer can use it to print and assembly the handbook in the same
way that can be done by AlcatelLucent factory.
iv Notes on present edition
ED.01 is the first validated and released edition associated to SWP TCO SUITE Rel.1.7.
a ) WARNING ABOUT SWP VERSION:
The SWP TCO SUITE version is written on the SWP CDROM you own, and that contain this
manual
The SWP TCO SUITE Rel.1.7 is meant to be used only with the AlcatelLucent 9400AWY
Network Elements specified in the column NE of Tab. 1. on page 14
In whole Manual (and if not differently specified), for SWP TCO SUITE it is always meant SWP
TCO SUITE Rel.1.7
If you have a SWP TCO SUITE version different from 1.7 , do not use this manual, but that
specific for such a version.
This manual is validated in conjunction with SWP TCO SUITE version 1.7 only. Information
relevant to SWP versions different from 1.7 , if any, must be considered preliminary, subject to
change and without any obligation on the part of AlcatelLucent.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
5 / 232 3DB 75003 BAAA Ed.01
USER MANUAL
FRONT MATTER
v Table of contents
i Navigation principles 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii Preliminary information 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iii Structure of this manual 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv Notes on present edition 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 1: TCO SUITE DESCRIPTION AND USAGE 11 . . . . . . . . . . . . . . . . . . . .
11 SWP TCO SUITE SCOPES AND REQUIREMENTS 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 SWP TCO SUITE scopes, usability, features, and distribution to Customers 13 . . . . .
11.2 SWP TCO SUITE User Manual scope, distribution to Customers, and associated
documentation 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 PC requirements to run and install the SWP TCO SUITE 15 . . . . . . . . . . . . . . . . . . . . . . .
11.4 PC Administrator privileges requirements to install and deinstall the SWP TCO
SUITE components 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12 ITEMS FOR SW DISTRIBUTION TO CUSTOMERS 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Items for SW distribution to Customers 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 SWP TCO SUITE CDROM description 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1 SWP TCO SUITE CDROM part number 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2 SWP TCO SUITE CDROM contents 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.3 Additional requirements for the use of the SWP TCO SUITE 21 . . . . . . . . . . . . . . . . . . .
12.3 Notes on SWP CDROM identification, and Product Release Note 22 . . . . . . . . . . . . . .
13 CONNECTIONS BETWEEN THE CRAFT TERMINAL AND THE NE, AND SECURITY
POLICY 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1 Types of physical access from the PC to the NE 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 PCNE network addressing rules 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.1 NEs management interfaces 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.2 NEs local IP address and Ethernet Configuration IP address 28 . . . . . . . . . . . . . . . .
13.2.3 NE reachability from the CT 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.4 Networking scenarios for PC connection to the NEs local IP address 30 . . . . . . . . . . .
13.3 Security 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.1 Summary of security features 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.2 Security by operator profile 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.3 Security by community string 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3.4 Security by access lists 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 GETTING STARTED 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1 Preparation of the Craft Terminal based on SWP TCO SUITE 37 . . . . . . . . . . . . . . . . . . .
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
6 / 232
USER MANUAL
FRONT MATTER
14.2 Equipment SW management by SWP TCO SUITE 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2.1 Flash Card 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2.2 Procedures for the management of the NE software 41 . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3 Startup and functions of the TCO SUITE Main Menu screen 46 . . . . . . . . . . . . . . . . . . .
14.4 Checks the operator must do before accessing a NE 48 . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5 Common behavior of NE login, and application logoff, for the NEinteractive
Provisioning Tool and Alarms & Settings 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5.1 Constraints and preliminary checks 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5.2 NE login procedure 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5.3 Application logoff procedure 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6 Close Current Session 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.7 Operational & Maintenance WebEML 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.8 Operational & Maintenance 1320CT 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15 PROVISIONING TOOL 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16 ALARMS & SETTINGS 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.1 Alarms & Settings overview, startup, and closing 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2 Alarms & Settings functions 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.1 Date & Time Setting 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.2 Configuration Setting 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.3 Configuration Info 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.4 Get Configuration File 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.5 Active Alarms 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.6 Power Measurement 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.7 Modem Speed 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.8 Licence Info 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2.9 NAT Option 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17 ACCEPTANCE TOOL 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1 Acceptance Tool scope 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2 Acceptance Tool start 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3 Acceptance Tool in NEinteractive modality 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3.1 Bench setup and startup of the NEinteractive Acceptance Tool 86 . . . . . . . . . . . . . .
17.3.2 Main functions of the NEinteractive Acceptance Tool 88 . . . . . . . . . . . . . . . . . . . . . . . . .
17.3.3 Create Report 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.4 Acceptance Tool in not NEinteractive modality (offline) 96 . . . . . . . . . . . . . . . . . . . . . . .
18 NETO (NETWORK ELEMENT OVERVIEW) 97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1 General on NEtO 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1.1 NEtO functions 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1.2 NEtO sessions and constraints 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2 NE access constraints 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.3 Summary of actions 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.3.1 Preliminary operations 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
7 / 232 3DB 75003 BAAA Ed.01
USER MANUAL
FRONT MATTER
18.3.2 Operations with NEtO 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4 Details on NEtO screen 105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4.1 Supervision Function 105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4.2 Supervision and Alarm Synthesis roundshaped icons 105 . . . . . . . . . . . . . . . . . . . . . . . .
18.4.3 NEtO screen minimize and restore 106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4.4 NEtO icon in the tray bar 106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4.5 NE Configuration 107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4.6 Command Buttons 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.4.7 How to close the NEtO session 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.5 NE list management 109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19 9400AWY WEBEML 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.1 How to open the 9400AWY NE WebEML main view 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2 9400AWY main view organization 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.3 View Area 115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.3.1 Resource Tree Area and Selection Criteria 116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.3.2 Resource Detail Area 116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4 Main tool bar 117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5 Severity alarm synthesis, and Domain alarm synthesis 118 . . . . . . . . . . . . . . . . . . . . . . . .
19.6 Management state control panel 119 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.7 Access state (allow or inhibit NE Craft Terminal access) 120 . . . . . . . . . . . . . . . . . . . . . . .
19.7.1 Switching from the OS to the Craft Terminal access state 120 . . . . . . . . . . . . . . . . . . . . . .
19.7.2 Switching from the Craft Terminal access state back to the OS access state 120 . . . . .
19.8 Introduction to the WebEML menu commands 121 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.1 Security by operator profile 121 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.2 Menu organization 124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.3 Command button policy 124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.4 Help menu 125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.5 Views menu 126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.6 Configuration menu 130 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.7 Diagnosis menu 131 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.8 Supervision menu 132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.8.9 SW download menu 133 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110 ALARMS MONITOR AND EVENT LOG BROWSER 135 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.1 Log switch 136 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2 Alarms Monitor 136 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.1 Alarms Monitor functions 136 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.2 Alarms Monitor startup for one single NE 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.3 Alarms Monitor Overview 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.4 Multiple NE Alarms Monitor 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.5 Filters menu 142 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.6 File Menu 145 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.7 Printing the alarms and logs 145 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.8 Exporting the alarms and logs 146 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.9 Navigate from AM to USM 147 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.10 Navigate from USM to AM 148 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.2.11 Shortcut icons 149 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
8 / 232
USER MANUAL
FRONT MATTER
110.3 Event Log Browser (ELB) 151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.3.1 ELB scope 151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.3.2 ELB startup 151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110.3.3 Event Log Table screen 152 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
111 MIB MANAGEMENT 155 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
111.1 Default repository folders of MIB backup files 156 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
111.2 Craft Terminal commands for the management of MIB backup files 156 . . . . . . . . . . .
111.3 How to perform the MIB backup 157 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
111.4 How to perform the MIB restore 158 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
111.5 How to remove a MIB backup file from the repository folder 160 . . . . . . . . . . . . . . . . .
112 NE SWP UPGRADE 161 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112.1 Introduction and restrictions 162 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112.2 Case of upgrade to 9400AWY V2.0.6 162 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112.5 Only for upgrade to 9400AWY V2.0.6 or V2.1.2: how to perform, by WebEML,
the SWP download to the NE, and its activation 163 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112.5.1 CT startup, and check for the availability of the SWP to be downloaded 164 . . . . . . .
112.5.2 NE login and initial operations (stations A and B) 164 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112.5.3 SW download to the NE (station A) 165 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112.5.4 Activation of the new Software Package on the NE (station A) 170 . . . . . . . . . . . . . . . .
112.5.5 Additional operation for upgrade from older versions (station A) 172 . . . . . . . . . . . . . . .
112.5.6 Operations on station B 172 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112.5.7 Functional checks on the radio link (stations A and B) 172 . . . . . . . . . . . . . . . . . . . . . . . .
112.5.8 NE data backup (stations A and B) 172 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112.6 Notes about NE SW downgrade 173 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113 MANAGEMENT OF THE SECURITY FEATURES 175 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113.1 Management of security by operator profiles 175 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113.2 Management of security by community string 178 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113.3 Management of security by access lists 180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 2: APPENDICES 183 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21 APPENDIX A: PREPARATION OF THE CRAFT TERMINAL BASED ON SWP TCO SUITE
185 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1 Operations sequence 185 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2 Functions of the other buttons of the Advanced Settings screen 189 . . . . . . . . . . . . . . .
21.3 Note about TCO SUITE previous versions 189 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22 APPENDIX B: JRE INSTALLATION AND SWP TCO SUITE STARTUP 191 . . . . . . . . . . . . . . .
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
9 / 232 3DB 75003 BAAA Ed.01
USER MANUAL
FRONT MATTER
22.1 Need for JRE installation 191 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.2 Standard behavior of SWP TCO SUITE startup 192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.3 Manual installation of Java JRE Package 193 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22.4 Special conditions of SWP TCO SUITE startup 195 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23 APPENDIX C: LLMAN INSTALLATION, CONFIGURATION AND USE 201 . . . . . . . . . . . . . . . . .
23.1 Foreword 201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.2 Important warnings 201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.3 Procedure summary 202 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.4 Installation of LLMAN from the SWP TCO SUITE CDROM 203 . . . . . . . . . . . . . . . . . . . . .
23.4.1 Operations sequence 203 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.4.2 Functions and helps available after the LLMAN installation 206 . . . . . . . . . . . . . . . . . . . . .
23.5 Installation and configuration of a Virtual Network adapter for LLMAN 207 . . . . . . . . . .
23.5.1 Foreword 207 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.5.2 Operations sequence, according to Windows platform 208 . . . . . . . . . . . . . . . . . . . . . . . . .
23.6 Lower Layer settings 210 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.7 Check/set the Network Connections order 212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.8 How to start and use the LLMAN application 213 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.8.1 LLMAN startup with 1320CT 214 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.8.2 LLMAN startup with WebEML 214 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23.8.3 Full information regarding the use of the LLMAN application 216 . . . . . . . . . . . . . . . . . . .
24 APPENDIX D: ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE
NETWORK 217 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.1 Introduction 217 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.2 Certified equipment 218 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.3 Connection cables 219 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.4 Modem setting 220 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.4.1 Setting of Sportster Flash Modem & 3Com 56K Faxmodem 220 . . . . . . . . . . . . . . . . . . . .
24.4.2 TD32 AC Modem setting 222 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.5 PC laptop Dell Latitude setting 223 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.6 Setting up the connection 224 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.7 Changing the ECTequipment connection speed 225 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.7.1 Introduction 225 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.7.2 Configuration at NE side 225 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24.7.3 Configuration at PC side 226 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25 APPENDIX E: SWP TCO SUITE REL.1.7 DEINSTALLATION 227 . . . . . . . . . . . . . . . . . . . . . . . .
26 APPENDIX F: CUSTOMER DOCUMENTATION FEEDBACK 229 . . . . . . . . . . . . . . . . . . . . . . . . .
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
10 / 232
USER MANUAL
FRONT MATTER
a ) END OF SECTION
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
11 / 232 3DB 75003 BAAA Ed.01
USER MANUAL SWP TCO SUITE Rel.1.7
TCO SUITE DESCRIPTION AND USAGE
SECTION 1: TCO SUITE DESCRIPTION AND USAGE
This section describes the SWP TCO SUITE and its most frequently used functions.
The less frequently used functions of the SWP TCO SUITE are described in the SECTION 2 from page
183
SECTION CONTENT PAGE
INTRODUCTIVE DESCRIPTIONS
Chapter 11 SWP TCO SUITE scopes and requirements
It sums up the scopes of the SWP TCO SUITE, and describes the scopes of this
manual, and the system requirements necessary to run the SWP TCO SUITE
13
Chapter 12 Items for SW distribution to Customers
It describes the items foreseen for the system SW (that resident inside the
equipment, and that for the NE management).
17
Chapter 13 Connections between the Craft Terminal and the NE, and
security policy
It describes the types of physical access and the rules to observe (network
addresses and security) , to configure and allow the access from the SWP TCO
SUITEbased Craft Terminal to the NE.
23
OPERATIVE DESCRIPTIONS
Chapter 14 Getting started
It gives the basic information for the use of the SWP TCO SUITE: preparation of
the Craft Terminal, summary of equipment SW management procedures, startup
and functions of the Main Menu screen.
37
Chapter 15 Provisioning tool
It describes in detail the functions of the Main Menus Provisioning Tool.
59
Chapter 16 Alarms & Settings
It describes in detail the Main MenusAlarms & Settings functions.
65
Chapter 17 Acceptance Tool
It describes in detail the functions of the Main Menus Acceptance Tool.
83
Chapter 18 NEtO (Network Element Overview)
It describes in detail the functions of NEtO
97
Chapter 19 9400AWY WebEML
It describes in detail the organization and the functions of the WebEML (Craft
Terminal).
111
OPERATIVE DESCRIPTIONS continues ...
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
12 / 232
... continues OPERATIVE DESCRIPTIONS
Chapter 110 Alarms Monitor and Event Log Browser
It describes in detail the functions of Alarms Monitor and Event Log Browser
embedded in NEtO application
135
Chapter 111 MIB Management
It describes how to perform the NE MIB backup and restore operations
155
Chapter 112 NE SWP upgrade
It describes how to upgrade to a new SWP any 9400AWY Rel.2.x NE, presently
running with a previous SWP.
161
Chapter 113 Management of the security features
It describes how to manage the security features of 9400AWY (by operator profile,
by community string, and by access lists).
175
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
13 / 232 3DB 75003 BAAA Ed.01
11 SWP TCO SUITE SCOPES AND REQUIREMENTS
This chapter sums up the scopes of the SWP TCO SUITE, describes the scopes of this manual, and
describes the PC requirements necessary to run the SWP TCO SUITE
Subject On page
SWP TCO SUITE scopes, usability, features,and distribution to Customers below
SWP TCO SUITE User Manual scope, distribution to Customers, and associated
documentation
14
PC requirements to run and install the SWP TCO SUITE 15
PC Administrator privileges requirements to install and uninstall the SWP TCO
SUITE components
16
11.1 SWP TCO SUITE scopes, usability, features, and distribution to
Customers
[1] SWP scopes
The main objective of the SWP TCO SUITE is to offer, to Customers working with AlcatelLucent
9400AWY Rel.2.0 and Rel.2.1 radio transmission products, new management features, with no need
to update the NEresident software, or to update the existing NEspecific SWP CDROM.
[2] SWP usability
The use of all features of the SWP TCO SUITE is allowed with the AlcatelLucent 9400AWY Network
Elements running with:
SWP 9400AWY R.2.0 V2.0.6
SWP 9400AWY R.2.1 V2.1.2
SWP 9400AWY R.2.1 V2.1.3
[3] SWP features for 9400AWY V2.0.6 and V2.1.2 NE management
With respect to the NE SW management tools:
embedded TCO Suite
1320CTbased Craft Terminal
included in the:
SWP 9400AWY R.2.0 V2.0.6 CDROM
SWP 9400AWY R.2.1 V2.1.2 CDROM
the SWP TCO SUITE provides the following features:
full Microsoft Windows Vistat support
new fullJava NEtO (Network Element Overview), replacing the functions of the NES (Network
Element Synthesis)
new fullJava WebEML (Craft Terminal), replacing the functions of the 1320CT
N.B. to avoid problems to the users of the NE SW management tools included in the
NEspecific SWP CDROM listed above, this new WebEML maintains the same
structure (main view, menu bar, screens organization, parameter name and position,
etc) with a few differences, described in this manual.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
14 / 232
[4] SWP features for 9400AWY V2.1.3 NE management
Differently from 9400AWY NE running with V2.0.6 or V2.1.2, the 9400AWY NE running with V2.1.3
has no 1320CTbased Craft Terminal management tools.
The 9400AWY NE running with V2.1.3 can be managed only by the SWP TCO SUITE.
[5] SWP distribution to Customers
The SWP TCO SUITE is a standalone product delivered on a specific CDROM.
11.2 SWP TCO SUITE User Manual scope, distribution to Customers, and
associated documentation
[1] SWP TCO SUITE User Manual scope
The specific NE User Manual ( Tab. 1. on page 14 ) gives all information regarding:
the NE, from system and hardware points of view
the NE SW management tools included in the specific SWP NE CDROM (only for
V2.0.6 and V2.1.2), supplied with the NE equipment
The scope of this SWP TCO SUITE User Manual is to provide, in a way as concise as possible,
only the description of features of the SWP TCO SUITEs NE SW management tools, that are
different from those of the SWP NE CDROM cited above (with some exceptions).
WARNING: this SWP TCO SUITE User Manual:
does not give detailed information regarding the NE
does not include detailed information that is already present in the specific NE User
Manual, and for which there are no operative differences at NE SW management level.
Therefore, to retrieve NEspecific information, or any other information referenced to in the
following, this SWP TCO SUITE User Manual must be always used together with the specific
NE User Manual having the P/N specified in Tab. 1. on page 14 .
[2] SWP TCO SUITE User Manual distribution to Customers
This manual is delivered to Customers in electronic format only (file Adobe Acrobatt pdf) inside the
specific SWP TCO SUITE CDROM.
[3] Associated documentation
Tab. 1. 9400AWY NEs and associated User Manuals
NE and Manual P/N of the NE User Manual
9400AWY R.2.0 V2.0.6 User Manual 3DB06687LAAA
9400AWY R.2.1 V2.1.2 User Manual 3DB16142GAAA
9400AWY R.2.1 V2.1.3 User Manual 3DB16142JAAA
Notes:
The specific NE User Manual is present in a documentation CDROM automatically delivered
to Customer together with the equipment it refers to (one copy for each terminal).
In some cases, depending on the Edition of the NE User Manual, the cross references to it,
specified in this manual (section_name, chapter_name, paragraph_name), could not
correspond exactly to the referenced part. In this case, you can find the cross referenced
information in another part of the specific NE User Manual.
in the following of this manual, when a generic reference to the NE User Manual is specified,
you must obviously use that corresponding to the specific NE you are working with.
For further information on the 9400AWY documentation set and additional documents (if any), please
refer to the documentation CDROM containing the specific NE User Manual.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
15 / 232 3DB 75003 BAAA Ed.01
11.3 PC requirements to run and install the SWP TCO SUITE
To run and install (if required) all functions of the SWP TCO SUITE, a PC meeting these requirements is
necessary:
1 ) HW Configuration (minimum requirements)
CPU: Pentium III 850 MHz
RAM: 512 Mbytes (1 Gbytes suggested for Windows Vista)
Hard Disk space: 4 Gbytes
Display Resolution: 1024x768 pixel
CDROM Drive: 24X
Communication Interfaces:
Ethernet Card 10/100 Mbits/sec is mandatory, if local / remote communication with
NEs Ethernet port or TCP/IP network is required (if both connections are required
contemporarily, two Ethernet Cards are needed)
RS232C serial port (9.6 to 57.6 Kbits/sec) is suggested, if local communication
with NEs ECT serial port (Finterface) is required.
N.B. In alternative, for the usage of the NEs Finterface with any PC having no
RS232 serial port (but obviously with USB ports available), it is possible
to use an USB to RS232 adapter (see Tab. 2. on page 25 )
Refer to para.13.1 from page 24 , for details on how to connect the PC to the NEs, by local
or remote connection.
2 ) Windows Versions
Windows 2000 SP4
Windows XP till SP2 (Professional Edition only)
Windows Vista
WARNING 1: only one Windows version can be present in the same PC
WARNING 2: for all Windows versions, it is mandatory to deactivate the Firewall installed
WARNING 3: restriction for Windows Vista:
With Windows Vista, the SWP download for NE upgrade cannot use
LLMAN (therefore the NEs F interface must not be used for the SWP
download)
For user convenience, this restriction is repeated on pages 162 and 164
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
16 / 232
3 ) Additional SW requirements
Java Runtime Environment (JRE): JRE 6 update 3
N.B. the necessary version is included in the SWP CDROM
Browser supported:
for Windows 2000 and XP:
Microsoft Internet Explorer 6.0 (6.0.2900.2180 SP1+)
or Microsoft Internet Explorer 7.0 (7.0 .5730.11C0+)
for Windows Vista:
Microsoft Internet Explorer 7.0 (7.0 .5730.11C0+)
for Windows 2000, XP, and Vista:
Mozilla Firefox v2.x starting from v2.0.0.12
N.B. Opera browser is not supported in any version.
WARNING: it is mandatory to manually disable system and browser proxy
configurations prior to use both NEinteractive Provisioning Tool and
Alarms & Settings (web server) functions; otherwise, the IP connection
from the PCs web server to the NE cannot take place.
Used browser window should be at least as larger as 1024x768
4 ) PC settings for its use inside the TCP/IP network
N.B. You have nothing to do, if you are employing a PC already configured for TCP/IP
communication (e.g. already used for any AlcatelLucent 1320CTbased or
NEtObased applications).
These settings include the following types of configuration:
PC hostname
Communication Protocol : TCP/IP (if not automatically configured)
IP address
IP mask
These settings depend on the Windows version employed. Refer to its documentation, to know
how to perform them.
11.4 PC Administrator privileges requirements to install and deinstall the
SWP TCO SUITE components
The PC Administrator privileges are necessary to install:
the Java Runtime Environment (JRE), automatically or manually: see Appendix B on page 191
the AlcatelLucentproprietary LLMAN and related Tiny Tools: see Appendix C on page 201
The PC Administrator privileges are also necessary to deinstall them: see Appendix E on page 227
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
17 / 232 3DB 75003 BAAA Ed.01
12 ITEMS FOR SW DISTRIBUTION TO CUSTOMERS
This chapter describes the items foreseen for the system SW (that resident inside the equipment, and that
for the NE management):
Subject On page
Items for SW distribution to Customers 18
SWP TCO SUITE CDROM description 20
SWP TCO SUITE CDROM part number 20
SWP TCO SUITE contents 20
Additional requirements for the use of the SWP TCO SUITE 21
Notes on SWP CDROM identification, and Product Release Note 22
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
18 / 232
12.1 Items for SW distribution to Customers
The scope of this paragraph is to compare the SW products present in the various CDROMs:
9400AWY R.2.0 V2.0.6 CDROM
9400AWY R.2.1 V2.1.2 CDROM
9400AWY R.2.1 V2.1.3 CDROM
SWP TCO SUITE CDROM
[1] NEspecific equipmentresident software
The software necessary for the system working (equipmentresident software) is present in the
Flash Card delivered with the equipment, and inserted in the IDU MAIN unit.
Refer to para.14.2.1 on page 38 for details.
[2] NEspecific software components for Equipment Controller and Peripheral Units of
9400AWY (IDU and ODU)
These SW components are used whenever you have a:
9400AWY R.2.0 NE running with SWP version < V2.0.6, and you want to upgrade it to SWP
version V2.0.6 , by means of the SW download function
These NEspecific SW components:
are present respectively in the:
9400AWY R.2.0 V2.0.6 CDROM
9400AWY R.2.1 V2.1.2 CDROM
9400AWY R.2.1 V2.1.3 CDROM
are not present in the SWP TCO SUITE CDROM
[3] Additional software products
JRE (Java Runtime Environment), that is present, with the necessary specific version, in the
following CDROMs:
9400AWY R.2.0 V2.0.6 CDROM
9400AWY R.2.1 V2.1.2 CDROM
SWP TCO SUITE CDROM
JRE is automatically installed in the PC at first insertion of the CDROM.
N.B. the JRE version present in the SWP TCO SUITE CDROM is higher than that of JRE
present in the other CDROMs listed above.
N.B. the 9400AWY R.2.1 V2.1.3 CDROM does not contain any JRE component.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
19 / 232 3DB 75003 BAAA Ed.01
LLMAN (Lower Layer MANager), that must be explicitly installed in the PC, whenever the use
of the NEs local F interface (RS232 serial interface) is required. This software product is present
in the following CDROMs:
9400AWY R.2.0 V2.0.6 CDROM
9400AWY R.2.1 V2.1.2 CDROM
SWP TCO SUITE CDROM
N.B. the LLMAN version present in the SWP TCO SUITE CDROM is higher than that of
LLMAN present in the other CDROMs. Moreover, it is also higher than that of
LLMAN present in the SWP TCO SUITE Rel.1.6 CDROM.
[4] NE management SW tools
a ) contained in the SWP TCO SUITE CDROM : refer to para.12.2.2 on page 20
b ) contained in the NEspecific SWP CDROM :
they are the:
embedded TCO Suite
1320CTbased Craft Terminal
present respectively in the:
9400AWY R.2.0 V2.0.6 CDROM
9400AWY R.2.1 V2.1.2 CDROM
The installation and use of these NE management SW tools is explained in the specific NE User
Manual ( Tab. 1. on page 14 )
N.B. the 9400AWY R.2.1 V2.1.3 CDROM does not contain any NE management SW
tool.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
20 / 232
12.2 SWP TCO SUITE CDROM description
12.2.1 SWP TCO SUITE CDROM part number
The P/N of the SWP TCO SUITE CDROM, containing this manual, is written on the CDROM itself you
own.
For SWP CDROM identification, refer to para.12.3 on page 22
12.2.2 SWP TCO SUITE CDROM contents
The following software products are contained in the SWP TCO SUITE CDROM:
[1] Main Menu
The Main Menu is the starting point of this SWP, with the screen depicted in Fig. 10. on page 47.
The functions available are:
Provisioning Tool : it starts a wizard tool, which allows to configure completely and easily one
9400AWY V2.0.6 or V2.1.2 or V2.1.3 NE, in not NEinteractive (offline), or in NEinteractive
(online) modality. This tool allows also to modify a configuration created previously, and to get
the configuration from a running NE.
Alarms & Settings : it starts a NEinteractive function, allowing the user to login a NE through
the use of the NE web server via a generic Internet browser, to monitor the status of NE alarms
and to get and/or set some NEs parameters
Start of one NEtO session : see point [2] below
Start of 1320CT : it is meant for old 9400AWY NEs backward compatibility only
Acceptance Tool : it is meant to be used in the commissioning phase; it replaces the functions
previously covered by the document TRS (Test Report Sheets) available as Pdf, Word or Excel
file; the main advantage is that the Acceptance Tool can take many parameters directly from
the NE
Advanced Settings : functions to install the SWP in PC
[2] NEtO
NEtO (Network Element Overview) is the starting point to make a full supervision and control of the
most recent AlcatelLucent radio transmission 9400AWY NEs: 9400AWY Rel.2.0 from version
V2.0.6, and 9400AWY Rel.2.1 from version V2.1.2.
N.B. NEtO is used also for the AlcatelLucent radio transmission 9500MPR NEs (all versions),
but you must be aware that the SWP TCO SUITE Rel.1.7 does not manage any version
of 9500MPR NEs.
It allows to perform the following operations on one NE:
start its supervision
run the Alarm Monitor function
perform its login, launching the WebEML application specific for the NE type and version ( see
following point [3] )
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
21 / 232 3DB 75003 BAAA Ed.01
[3] WebEML (fullJava Local and Remote Craft Terminal)
The WebEML is used for the complete NE management, allowing the dialogue between the Craft
Terminal and the NE.
Each NE type and version has its own WebEML SW package.
The SWP TCO SUITE contains the WebEML SW packages for:
9400AWY V2.0.6
9400AWY V2.1.2
9400AWY V2.1.3
[4] Additional software products
JRE (Java Runtime Environment), that is automatically installed in the PC at first insertion of
the SWP TCO SUITE CDROM
LLMAN (Lower Layer MANager), that must be explicitly installed in the PC, whenever the use
of the NEs local F interface (RS232 serial interface) is required.
N.B. as specified in point [2] on page 18 , the SWP TCO SUITE CDROM does not contain
the NEspecific software components for NE upgrading. If necessary, they must be
retrieved from the NEspecific SWP CDROM.
12.2.3 Additional requirements for the use of the SWP TCO SUITE
a ) NE software state
the NE type must be ULS, and the SWP active version in the NEs Flash Card must be:
V2.0.6 (if 9400AWY R.2.0)
V2.1.2 or V2.1.3 (if 9400AWY R.2.1)
This check can be done making the NE supervision by NEtO, then reading the NE type (ULS)
and version, as shown in Fig. 46. on page 107
any 9400AWY NE, that must be accessed in local or remote way by the SWP TCO SUITE
applications, must have already a valid local IP address and a valid Ethernet Configuration
IP address [ see para.13.2.2 on page 28 ], and such addresses must be known by the
Operator.
b ) Security
Operations allowed by the SWP TCO SUITEs SW tools are submitted to a security control, described
in para.13.3 on page 33
c ) Operator skills
the Operator shall be familiar with the use of personal computers in WINDOWS environment
[versions specified in point 2 ) on page 15 ], internally to which the Network Elements
application software operates.
the Operator must be familiar with all the functionalities of the 9400AWY R.2.0 and/or
9400AWY R.2.1 equipment.
furthermore, for a number of configuration applications, the operator shall be aware of some
specifications of the International Standard Organization (ISO) and of the standards applied to
the Synchronous Digital Hierarchy (SDH) (CCITT Recommendations).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
22 / 232
12.3 Notes on SWP CDROM identification, and Product Release Note
These notes apply both to the SWP TCO SUITE CDROMs, and to the SWP 9400AWY V2.x.x
CDROMs:
[1] SWP CDROM identification
each SWP is distributed by means of a specific SWP CDROM
a SWP is identified by its Denomination, P/N (Part Number) and CS (Change Status), that
are printed on the CDROMs label
a SWP with new Version Level, providing main features in addition to those of the previous
Version Level SWP, is distributed by means of a SWP CDROM having new Denomination,
new P/N (Part Number), and CS restarting from 01
a SWP patch version, if any, is created to correct SW bugs, and/or to add minor features, and
is distributed by means of a SWP CDROM, that can be identified:
by the same P/N of the former CDROM, but with an incremented CS number (e.g.
CS=02 instead of previous CS=01)
or by a new P/N, and CS restarting from 01
[2] Product Release Note
the Product Release Note contains information not strictly necessary for Customers (like the
SW Package Identification data, the list of SW Package Components, the list of ECT SW
SubComponents, the description of new features and modifications, restrictions and known
problems, etc.)
the Product Release Note is neither contained in the SWP CDROM nor automatically
delivered to Customers
the Product Release Note is available only on specific request to your AlcatelLucent local
dealer, specifying the SWP TCO SUITE CDROM P/N and ICS (edition) printed on the SWP
CDROM itself (see point [1] above).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
23 / 232 3DB 75003 BAAA Ed.01
13 CONNECTIONS BETWEEN THE CRAFT TERMINAL AND THE NE,
AND SECURITY POLICY
This chapter describes the types of physical access and the rules to observe (network addresses and
security) , to configure and allow the access from the SWP TCO SUITEbased Craft Terminal to the NE.
Subject On page
Types of physical access from the PC to the NE 24
NEs F interface (RS232 serial interface) on IDU MAIN unit 25
NEs Ethernet interface on IDU MAIN unit 26
NEs pointtopoint radio interface and NMS (TMN connections) rings and
chains
27
PCNE network addressing rules 28
NEs management interfaces 28
NEs local IP address and Ethernet Configuration IP address 28
NE reachability from the CT 29
Networking scenarios for PC connection to the NEs local IP address 30
Security 33
Summary of security features 33
Security by operator profile 34
Security by community string 35
Security by access lists 36
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
24 / 232
13.1 Types of physical access from the PC to the NE
The physical access to a 9400AWY NE, for its management by the PC running the SWP TCO SUITE
software , can be on the following interfaces of the 9400AWY NE:
F interface (RS232 serial interface), see point [1] on page 25
Ethernet management interface, see point [2] on page 26
Pointtopoint radio interface and NMS (TMN connections) rings and chains, see point [3] on page
27
Notes for all types of access:
a ) Depending on physical interface, the use of some SW management tools has some restrictions.
b ) LCT and RCT
The specification of LCT (Local Craft Terminal) and RCT (Remote Craft Terminal), in following tables
Tab. 3. to Tab. 6. , is relevant to the CT characterization for the supervised NE.
This implies different command feasibility behaviors, as described in para.19.8.1 from page 121
(some commands cannot be executed by RCT).
c ) Max number of contemporary accesses to the same NE
For the NE access by:
Main Menu NEinteractive functions (online Provisioning Tool and Alarms & Settings), up
to five Ethernet user connections are supported at the same time on a single NE
WebEML (through NEtO) and OS, refer to para.18.2 on page 98
9400AWY R.2.1 IDU MAIN unit
F Interface
Management
Ethernet Interface
9400AWY R.2.0 IDU MAIN unit
NMS Interface
(G703 + V11)
Radio Interface
(IDUODU cable)
Radio Interface
(IDUODU cable)
NMS Interface
(V11)
NMS Interface
(G703)
F Interface
Management
Ethernet Interface
Fig. 1. Physical interfaces for the 9400AWY NE management
Comparison with the NE management software tools of the:
9400AWY R.2.0 V2.0.6 CDROM,
and of the 9400AWY R.2.1 V2.1.2 CDROM
with the SWP TCO SUITE, there is no need of manual interface customization for alternative use of
Finterface or Ethernetinterface
with the SWP TCO SUITE, the access to the NE requires always the NE address specification, even
in case of PCNE interconnection by Finterface
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
25 / 232 3DB 75003 BAAA Ed.01
[1] NEs F interface (RS232 serial interface) on IDU MAIN unit
WARNING 1: for the use of the F interface, the LLMAN installation and configuration must be
performed, as described in the Appendix C on page 201
PUBLIC SWITCHED
TELEPHONE NETWORK
PCs RS232 interface
RS232 cable
PCs modem
F
NE supervised through F interface
Modem
Refer to the Appendix D on page 217 , to know how to implement the connection via the public switched
telephone network.
Tab. 2. Typical AlcatelLucent RS232 cable and adapter
Cable / Adapter P/N Notes
RS232 cable 1AB054120027 Standard RS232 cable
USB to RS232 adapter 1AF11294AA**
In addition to the standard RS232 cable, for the
usage of the NEs Finterface with any PC having
no RS232 serial port (but obviously with USB
ports available)
Tab. 3. Allowed NE management SW tools on NEs F interface
SW management tool
Allowed on
Finterface
NEs TCP/IP address
required for NE access
LCT /
RCT
SWP TCO SUITE Main Menu
NEinteractive functions:
Provisioning Tool
Alarms & Settings
Acceptance Tool
NO
SWP TCO SUITE WebEML YES NO LCT
Fig. 2. Connections between PC and NE through NEs F Interface
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
26 / 232
[2] NEs Ethernet interface on IDU MAIN unit
ETH
SWITCH
IP NETWORK
PC Ethernet interface
crossconnect Ethernet cable
Eth
NE supervised through Ethernet interface
normal (direct) Ethernet cable
Tab. 4. Typical AlcatelLucent Ethernet cables
The suggested AlcatelLucent Ethernet cables are:
type length (m) P/N
1 3CC52141AAAA
normal (direct) cable 5 3CC52141ABAA
15 3CC52141ACAA
crossconnect cable
1 3CC52142AAAA
crossconnect cable
5 3CC52142ABAA
Tab. 5. Allowed NE management SW tools on NEs Ethernet interface
SW management tool
Allowed on
Eth.interface
NEs TCP/IP address
required for NE access
LCT /
RCT
Provisioning Tool
Alarms & Settings
Acceptance Tool (N.B.)
YES YES
SWP TCO SUITE WebEML YES YES RCT
N.B. for details on NE access in case of Acceptance Tool use, refer to chapter 17 from page
83
Fig. 3. Ethernet connections between PC and NE
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
27 / 232 3DB 75003 BAAA Ed.01
[3] NEs pointtopoint radio interface and NMS (TMN connections) rings and chains
ODU
ODU
STATION A
STATION B
9400AWY RADIO LINK
Access to Station B from PC
connected locally to Station A
NE supervised through Radio interface
Local PC
IP NETWORK Remote PC
PUBLIC
SWITCHED
TELEPHONE
NETWORK
PC connected
locally to Ethernet
or F interface of
STATION A
PC connected remotely to Ethernet or F
interface of STATION A
Access to Station B from PC
connected remotely to Station A
F
Eth
NMS Eth
NMS
NE supervised through NMS
(G703V11)
NMS
Eth
Eth
NMS
NMS
Eth
NE supervised through Ethernet
interface
NE supervised through NMS
(G703V11)
Other NE
Other NE
Other NE
TMN system
Refer to the specific NE User Manual ( Tab. 1. on page 14 ) for details on the NMS connections.
Tab. 6. Allowed NE management SW tools on NEs Radio interface and NMS rings and chains
SW management tool
Allowed on
interface of
STATION A
NEs TCP/IP
address required
for NE access
LCT /
RCT
Provisioning Tool
F NO
Provisioning Tool
Alarms & Settings
Acceptance Tool (N.B.)
Ethernet YES YES
SWP TCO SUITE WebEML
F
YES YES RCT SWP TCO SUITE WebEML
Ethernet
YES YES RCT
N.B. for details on NE access in case of Acceptance Tool use, refer to chapter 17 from page
83
Fig. 4. Access to NE through NEs radio Interface and NMS rings and chains
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
28 / 232
13.2 PCNE network addressing rules
This paragraph describes the network address rules that must be observed to allow a PC (running the
SWP TCO SUITE) the access to one or more 9400AWY NEs.
13.2.1 NEs management interfaces
For its management by SWP TCO SUITE tools, the 9400AWY NE has:
one Ethernet management interface, which is used to access the NE, and that is identified by its local
IP address and Ethernet Configuration IP address, defined in para.13.2.2 below
one pointtopoint TMNRF interface toward the other NE of the radio link
and one selectable pointtopoint TMNV11 or TMNG703 interface toward another colocated NE
all pointtopoint interfaces (TMNRF, and TMNV11 or TMNG703) are unnumbered and borrow
the IP address from the local IP address
13.2.2 NEs local IP address and Ethernet Configuration IP address
As delivered from AlcatelLucent Factory, the NEs addresses:
local IP address, used to identify uniquely the NE inside the Transmission Management Network
(TMN)
and the Ethernet Configuration IP address, used to identify uniquely the NEs Ethernet
management interface inside the TCP/IP network
are both set at default value 10.0.1.2, as shown in screen below (one of the steps of the Full
Configuration Procedure described in chapter 15 from page 59 )
These values can be maintained only until the NE remains disconnected from the TCP/IP network and
from the TMN, and must be changed to have them different from those of the other NEs present in the
accessible network. Their setting is foreseen in the commissioning phase; for details, refer to the specific
NE User Manual ( Tab. 1. on page 14 )
In the commissioning phase, you can define the local IP address and Ethernet Configuration IP
address:
with the same value (suggested solution)
or with different values
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
29 / 232 3DB 75003 BAAA Ed.01
WARNING: if such NE addresses are different, they must not belong to the same subnetwork, as in
following correct example:
local IP address = 151.98.96.221
and Ethernet Configuration IP address = 151.98.97.232
with IP Mask = 255.255.255.0
N.B. in the case these NE addresses are different:
the local IP address is that to be always used to access the NE by NEtO application
the Ethernet Configuration IP address is that to be always used to access the NE
by the NEinteractive Provisioning Tool and Alarms & Settings (web server)
functions.
13.2.3 NE reachability from the CT
[1] Foreword
The CT must be able to reach the NE, through one of the local or remote connections described on
previous pages 25 to 27
The access rules are different according to the type of application used; if you access a NE from your
PC:
1 ) through the Finterface, and by the NEtO application, the NEs local IP address must be
always used, and there are no network constraints
2 ) through the Ethernet interface, and by the NEtO application, for which the NEs local IP
address must be always used, it is necessary to build a networking relationship, according to
the PCNE connection scenario, between:
the IP address of the PC
the local IP address of the NE
the Ethernet Configuration IP address of the NE
as described in para.13.2.4 from page 30
3 ) through the Ethernet interface, and by the NEinteractive Provisioning Tool and Alarms &
Settings applications (web server operations), any problems between the IP addresses of the
PC and the NE are solved automatically, choosing Local or Remote in the application start
screen, as described in para.14.5 from page 49
[2] How to check the NE reachability from the CT
N.B. Usually, these operations have to be performed once only (i.e., whenever you have not
done them previously for the specific NE). This check is not necessary in case of PCNE
connection through the Finterface.
To make this check, open the Windows Command Prompt application and execute the command:
ping <space> NE_address
Verify the connection, then close the command window.
Note: in case the local IP address and Ethernet Configuration IP address are different from each
other, perform this check for both.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
30 / 232
13.2.4 Networking scenarios for PC connection to the NEs local IP address
These scenarios describe the networking address configurations necessary to allow a PC (running the
SWP TCO SUITE) to access a 9400AWY NE through its local IP address.
N.B. Address values are given as examples. Moreover:
address_value/24 means with IP mask = 255.255.255.0
In this case, if the address_value is that of the subnet 192.168.1.0, all addresses 192.168.1.0
to 192.168.1.255 are stated as belonging to the subnet
address_value/32 means with IP mask = 255.255.255.255
In this case, if the address_value is that of the subnet 192.168.1.0, only the address
192.168.1.0 is stated as belonging to the subnet
[1] NE local access by one PC
the CT accesses the NE using the local IP address; the SNMP traps are sent by NE using the
local IP address as source IP address
it is possible to configure the Ethernet Configuration IP address with the same value used for
local IP address
the subnet must be defined both on the PC and the NE
Eth
9400AWY NE
subnet = 10.0.1.0/24
.2
.1
10.0.1.1
[2] NE local and remote access by one PC, with Default Gateway or Static Route, or OSPF
in this scenario, to reach the local and remote NEs by their own local IP address, the PC must
be configured with a Default Gateway or Static Route having as gateway the Ethernet
Configuration IP address of the local NE (192.168.1.1 in the following examples)
at the same time the CT must be reachable by the remote NE using a Static Route on the remote
NE, or enabling OSPF on both local and remote NEs
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
31 / 232 3DB 75003 BAAA Ed.01
First example
Eth
9400AWY NE
subnet = 192.168.1.0/24
.2
.1
Set:
Default Gateway = 192.168.1.1
or:
Static Route 10.0.1.0/24 Gateway 192.168.1.1
10.0.1.1
10.0.1.2
9400AWY NE
LOCAL NE REMOTE NE
Second example
Eth
9400AWY NE
subnet = 192.168.1.0/24
.2
.1
Set:
or:
Static Route 176.16.1.0 /24 Gateway 192.168.1.1
and:
Static Route 10.0.1.0/24 Gateway 192.168.1.1
10.0.1.1
172.16.1.1
9400AWY NE
LOCAL NE REMOTE NE
WARNING: if both the local IP address and the Ethernet Configuration IP address of the local
NE belong to the same subnetwork, the local IP address of the local and remote
NEs must never belong to the same subnetwork. E.g. the following scenario does not
work:
Eth
9400AWY NE
.2
.1
10.0.1.1 reachable
10.0.1.2 unreachable
9400AWY NE
LOCAL NE REMOTE NE
subnet = 10.0.1.0/24
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
32 / 232
[3] NE access by more than one PC
to allow more than one PC to access the NEs in the network, theirlocal IP address, and the
IP addresses of the PCs, must belong to different subnets
Eth
9400AWY NE
subnet = 192.168.1.0/24
.2
.1
Set:
or:
Static Route 10.0.1.0/24
Gateway 192.168.1.1
10.0.1.1
10.0.1.2
Eth
9400AWY NE
10.0.1.1
10.0.1.2
.1
.2
subnet = 192.168.2.0/24
Set:
or:
Static Route 10.0.1.0/24
Gateway 192.168.2.1
[4] Notes on OSPF routing
the OSPF routing protocol can be activated on each pointtopoint interface (TMNRF,
TMNV11, and TMNG703) and on the Ethernet Configuration IP address interface
the 9400AWY NE can act as ABR (Area Border Router) managing a maximum of 4 areas
(Backbone + 3 areas). It is possible to assign different OSPF areas to each pointtopoint
interface, and to the Ethernet Configuration IP address interface
an OSPF area can be configured as Stub Area. Configuring a Stub Area reduces the topological
database size and reduces the memory requirements for NE inside that area for NEs that are
not ABR
the OSPF Area Identifier can take a form similar to an IP address A.B.C.D
the Area 0 or Backbone has Area ID 0.0.0.0
the Area ID has not any correlation with the IP address of the interface that belongs to that area
enabling OSPF, static routing information configured on one NE are automatically redistributed
as OSPF external routes inside the OSPF areas active on this NE
static routings are not redistributed inside the OSPF areas configured as Stub Area
if OSPF is enabled on NEs, static routes, if needed, have to be added only on the NE reached
by Ethernet (called Gateway NE)
in case of CT not directly connected to the Gateway NE, the Ethernet interface of this NE must
be reachable in order to make the software download working
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
33 / 232 3DB 75003 BAAA Ed.01
an example of OSPF Area configuration is shown in following figure:
9400AWY NE
local IP address
10.0.1.3
10.0.1.1
10.0.1.2
10.0.1.3
Eth
9400AWY NE
TMN
G703
or
V11
TMN
RF
local IP address
10.0.1.1
local IP address
10.0.1.2
9400AWY NE
OSPF Area 1 OSPF Area 2
.2
.1
subnet = 192.168.1.0/24
OSPF Area 0
13.3 Security
13.3.1 Summary of security features
The aim of the security features of 9400AWY system is to protect the NE from all undesired accesses.
The following security features are available:
usable on AWY 2.0.6, 2.1.2, and 2.1.3:
Security by operator profile, described in detail in para.13.3.2 on page 34
This is a standard feature, allowing the NE access only through a UserName and Password set,
valid for the specific NE.
As delivered from AlcatelLucent factory, the Flash Card contains only one default
Administrator UserName and Password set.
usable on AWY 2.1.3 only:
Security by community string, described in detail in para.13.3.3 on page 35
This feature is associated to the NEtO applications, and allows to assign to the NE a community
string. An user who wants to access such a NE, must provide this community string before
before to supervise and login the NE.
Security by access lists, described in detail in para.13.3.4 on page 36
The NE management operations that can be done by means of the SWP TCO SUITE are
grouped in different services: snmp, http, ftp and telnet.
The feature Security by access lists allows to write an access list table, for each one of the
services stated above, containing the IP addresses allowed to perform that specific service.
Both these security features are optional.
For both these security features, the Flash Card (as delivered from AlcatelLucent factory) contains
default parameters, corresponding to security feature not active.
N.B. The management of the security features is described in chapter 113 on page 175
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
34 / 232
13.3.2 Security by operator profile
[1] UserName and Password
To login a NE, whichever the physical access method, you must have a UserName and Password
set, valid for the specific NE.
UserName and Password are requested by a prompt screen like this:
At first installation time, one default Administrator user is available only, with (lower case):
UserName= initial
Password = initialing
Otherwise, use the Login information the Administrator has assigned you.
In the login procedure, the username is displayed on the screen, while the cleartext password is
not displayed on the screen. After 3 times of consecutive unsuccessful NE login attempts, the CTNE
logical interface closes the login procedure. To access the NE, a new login action must be performed.
WARNING: The change of the password of this Administrator user is strongly suggested, to be
done at the end of all commissioning phases. Further this initial user, the
Administrator is allowed to create/delete users belonging to the predefined profiles.
[2] Login profiles
Each user (identified by a UserName and a Password) is associated to one of the predefined profiles.
The predefined profiles are the following:
Administrator (both for OS interface and CT/MibBrowser interface)
The Administrator can do everything on the NE.
In particular, only the Administrator can manage the security features summed up in
para.13.3.1 on page 33 :
add/remove users, besides changing own password and those of all users
set/change/remove the community string
set/change/remove the access lists
export the access lists from a NE, and import them in another NE.
Constructor (only for OS interface)
This Operator can do everything on the NE also to access to the Manager List bypassing the
RM checks, but for this Operator some administration functions are disabled: for example the
Constructor cannot add or remove operators, and cannot do backup and restore.
This user profile is related only to OS system and so not stored on MIB NE.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
35 / 232 3DB 75003 BAAA Ed.01
Operator (both for OS interface and CT/MibBrowser interface)
This Operator has in charge the operation at network level, not at radio site.
This Operator can change her/his own user password.
This Operator cannot manage network configuration, only for NTP Configuration, due to
dangerous isolation of NE.
This Operator cannot either do quick configuration, or backup/restore, or restart NE. Also the
provisioning of equipment is not supported, as well the operations requiring the operator
presence on the radio site.
CraftPerson (only for CT/MibBrowser interface)
This Operator has in charge the installation and the maintenance at radio site.
This Operator can do everything on NE system, but cannot manage the security features, but
can change her/his own user password.
viewer (both for OS interface and CT/MibBrowser interface)
This Operator can only explore the NE.
This Operator can change her/his own user password.
[3] Operations allowed to Login profiles, according to functions, access, and local access status
NEinteractive Provisioning Tool (described in point [2] from page 61 )
allowed to the Administrator, CraftPerson and Operator
denied to the Viewer
Alarms & Settings (described in chapter 16 from page 65 )
according to Tab. 7. on page 67
NEinteractive Acceptance Tool (described in chapter 16 from page 65 )
allowed to the Administrator and CraftPerson
denied to the Operator and Viewer
WebEML (described in chapter 19 from page 111 )
refer to para.19.8.1 on page 121
13.3.3 Security by community string
N.B. available on AWY 2.1.3 NEs only
This feature is associated to the NEtO applications only.
As delivered from AlcatelLucent factory, the Flash Card contains the community string = private as
default value. When NEtO is opened, it contains always community string = private as default value.
This condition corresponds to security by community string not active.
The NE Administrator, if modifies the NEs own community string (as described in para.113.2 on page
178 ), must communicate this string to the users who should be authorized to supervise and login the NE.
Any of these users, to be authorized to access such a NE, must provide this community string before
to supervise and login the NE, as described on page 101
For the system behaviors when the community string of a NE is modified, while an user has a NEtO
session opened on the same NE (supervision, WebEML, and Alarms Monitoring), refer to points 2 ) and
3 ) on page 179
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
36 / 232
13.3.4 Security by access lists
N.B. available on AWY 2.1.3 NEs only
This feature is associated to all SWP TCO SUITE applications.
The NE management operations that can be done by means of the SWP TCO SUITE are performed using
the following different services:
snmp: all NEinteractive operations performed accessing the NE by NEtO ( chapter 18 on
page 97 )
http : all NEinteractive operations performed accessing the NE starting from the Main Menu
screen ( Fig. 10. on page 47 ):
NEinteractive Provisioning Tool ( point [2] on page 61 )
Alarms & Settings ( chapter 16 on page 65 )
ftp : all NEinteractive operations corresponding to:
downloading a file from the NE (e.g. the Get Configuration File described in
para.16.2.4 on page 75 )
uploading a file to the NE (e.g. the Configuration Setting described in para.16.2.2
on page 69 )
telnet telnet is the protocol used when the access to the NE is performed by NEtO from a Remote
Craft Terminal [ point b ) on page 24 ]
Note that, to perform some operations, more than one of the stated services are used. For example:
both snmp and telnet are used to login a NE by NEtO from a Remote Craft Terminal
both http and ftp are used to download a file from a NE using the Alarms & Settings functions.
In the Flash Card, for each one of the stated services, there is an Access List table, as shown in
Fig. 74. on page 180
In the Flash Card, as delivered from AlcatelLucent factory, all these four Access List tables contain
0.0.0.0 as default value in the IP Address and in the IP Mask fields.
This condition corresponds to security by access lists not active.
The NE Administrator, if wants to limit the use of one of the stated services to a specific list of managers,
must insert and enable their IP Address and their IP Mask into the corresponding Access List table,
as described in para.113.3 on page 180
After this setting, any user, whose PCs IP Address is not listed in an Access List table, will not be
authenticated for the use of the corresponding service (for the specific NE).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
37 / 232 3DB 75003 BAAA Ed.01
14 GETTING STARTED
This chapter gives the basic information for the use of the SWP TCO SUITE.
Subject On page
Preparation of the Craft Terminal based on SWP TCO SUITE below
Equipment SW management by SWP TCO SUITE 38
Flash Card 38
Procedures for the management of the NE software 41
Startup and functions of the SWP TCO SUITE Main Menu screen 46
Checks the operator must do before accessing a NE 48
Common behavior of NE login, and application logoff, for the
NEinteractive Provisioning Tool and Alarms & Settings
49
Constraints and preliminary checks 49
NE login procedure 50
Application logoff procedure 54
Close Current Session 55
Operational & Maintenance WebEML 56
Operational & Maintenance 1320CT 58
14.1 Preparation of the Craft Terminal based on SWP TCO SUITE
If not yet done, the first thing you must do is to copy the TCO SUITE software from the CDROM to your
PC , as described in the Appendix A on page 185 , even if some functions can be run directly from the
CDROM.
N.B. The functions that can be run directly from the TCO SUITE CDROM, without performing the
copy procedures of the Appendix A , are:
Provisioning Tool, see Chapter 15 on page 59
Alarms & Settings, see Chapter 16 on page 65
Acceptance Tool, see Chapter 17 on page 83
Operational & Maintenance 1320CT, see para.14.8 on page 58
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
38 / 232
14.2 Equipment SW management by SWP TCO SUITE
This paragraph introduces the information regarding the equipment software management.
14.2.1 Flash Card
A Flash Card is always plugged into the IDU Main board; it contains the whole Equipment programs and
configuration data.
14.2.1.1 Flash Card types
Various types of Flash Cards are available; each of them allows a fixed max system throughput [i.e. the
max number of user interfaces, in terms of equivalent Mb/s traffic, and the supported modulation (4QAM
and/or 16QAM) ].
Each type of Flash Card is identified by a Logistical Item P/N and by a licence information.
Please refer to the specific NE User Manual ( Tab. 1. on page 14 ) for details on the available types of
Flash Card and their identification.
WARNING: the Flash Cards of 9400AWY R.2.0 and of 9400AWY R.2.1 are not interchangeable.
14.2.1.2 Flash Card content
The Flash Card contains the whole Equipment programs and configuration data, as shown in
Fig. 5. below:
a ) Case of AWY 2.0.6 and 2.1.2
SW
COMMIT
VERSION
(ACTIVE)
SW
STANDBY
VERSION
(not active)
MIB
SW instances
NE Data
SOFTWARE KEY
Fixed Data
(Licence info)
b ) Case of AWY 2.1.3
SW
COMMIT
VERSION
(ACTIVE)
SW
STANDBY
VERSION
(not active)
MIB
SW instances
NE Data
SERIAL NUMBER
Fixed Data
LICENCE STRING & LICENCE KEY
Licence Data
Licence info
Fig. 5. Flash Card content
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
39 / 232 3DB 75003 BAAA Ed.01
[1] Licence information
1 ) Case of AWY 2.0.6 and 2.1.2: fixed licence information
The licence information can be read by the CT command Supervision % SW Key (see
para.19.8.8 on page 132 ), which opens the screen of Fig. 6. below, or by the Licence Info
screen of the Alarms & Settings function (see para.16.2.8 on page 78 ):
the SW Key number indicates the licence information.
the SW Key code indicates the fixed max system throughput.
In this case, you can change the max system throughput only replacing physically the Flash
Card with another type (another P/N, allowing the desired system throughput).
Fig. 6. Flash Card licence information (case of AWY 2.0.6 and 2.1.2)
2 ) Case of AWY 2.1.3: dynamically changeable licence information
The licence information can be read by the CT command Supervision % SW Key (see
para.19.8.8 on page 132 ), which opens the screen of Fig. 7. below, or by the Licence Info
screen of the Alarms & Settings function (see para.16.2.8 on page 78 ):
the Serial Number is that physically associated to the Flash Card
the Licence String indicates the fixed max system throughput
the Set Licence Key field indicates the licence, associated to the Flash Cards Serial
Number, and implicitly defines its current Licence String.
In this case you can change the max system throughput in two ways:
replacing physically the Flash Card with another type (another P/N, allowing the desired
system throughput), as in the case 1 ) above
or asking AlcatelLucent a new Licence Key pattern, associated to the Flash Cards
Serial Number, then introducing it (by copy and paste) in the Set Licence Key field, at
last clicking the button Apply.
Fig. 7. Flash Card licence information (case of AWY 2.1.3)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
40 / 232
[2] SW instances
The SW COMMIT VERSION is that used by the system.
The SW STANDBY VERSION instance is created the first time a SW download from CT to the NE
is performed.
As supplied by AlcatelLucent factory, the SWPversion downloaded in Factory is the most recently
released at the date of Flash Card delivery to the Customer, so that the SW instances present in the
flash card are:
the SW COMMIT VERSION
and the SW STANDBY, loaded with the SW version immediately previous (maintenance
release) with respect to the COMMIT one.
[3] NE data
N.B. as shown in Fig. 5. on page 38 , differently from SW instances, NE data are present as
a single instance in the Flash Card.
a ) Base configuration
It is defined by the Flash Cards licence information. It means that you can change the system
configuration data only within its throughput limits.
The licence information can be modified as described in previous point [1] on page 39
b ) MIB
The MIB (Management Information Base) contains all NE configuration data.
As supplied by AlcatelLucent factory, the NE configuration data are set to default values.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
41 / 232 3DB 75003 BAAA Ed.01
14.2.2 Procedures for the management of the NE software
SWP TCO SUITE CDROM
It contains the SW tools for the NE
management
NE SWP downloading
from PC to Flash Card

DURATION (about):
30 minutes with
F interface
15 minutes with
Ethernet interface
NE DATA
CHANGE
(see point [2] on page 42 )
SWP load from Flash Card
to Equipment Controller
and peripheral units
(IDU & ODU)
DURATION:
some minutes
NE DATA
BACKUP
NE DATA
RESTORE
PREPARATION OF
CRAFT TERMINAL BASED
ON SWP TCO SUITE
(see Appendix A
from page 185 )
NE SW download & activation
(if necessary) N.B.
NE data management
1 NE SW download
2 NE SW activation
SWP NE Rel.X.Y.Z CDROM
It contains the SW components to be
downloaded to any NE Rel.X.Y presently
running with a SW version < X.Y.Z
N.B. the NE SW download & activation is necessary only in case of upgrading of the NE SWP (see
point [7] on page 45 ).
Fig. 8. Main phases of the equipment SW management
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
42 / 232
The procedures for the management of the NE software, described in the following, are related to the
contents of the Flash Card, described in previous para.14.2.1 on page 38 :
Firsttime equipment startup and commissioning
Changing NE data
NE data backup
NE data restore
Flash Card licence management
Flash Card replacement
Upgrading of the NE SWP
System restart
[1] Firsttime equipment startup and commissioning
It must be done according to the instructions given in the specific NE User Manual ( Tab. 1. on page
14 ) , more precisely:
section SW INSTALLATION AND COMMISSIONING
chapter LineUp and Commissioning
After the commissioning completion, create a folder, specific for the NE, containing the following files:
the MIB backup .bar file , and the NE configuration backup .qcml file (see point [3] on
page 43 )
the TRS (Test Result Sheet & Site Acceptance Test Protocol) report by means of the
Acceptance Tool of the TCO SUITEs Main Menu (see Chapter 17 on page 83 ). This can
be used, in the future, to compare the system performance to that verified at the commissioning
phase time.
and maintain this folder updated whenever you make changes on the NE data.
[2] Changing NE data
NE data, contained in the MIB, can be changed (within the limits defined by the Flash Cards licence
information), by the suitable commands of:
the Craft Terminal
the NEinteractive Provisioning Tool
the Alarms & Settings functions
Changes of the NE data are submitted to the security policy described in para.13.3 from page 33
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
43 / 232 3DB 75003 BAAA Ed.01
[3] NE data backup
The NE data backup must be always performed:
at the end of the commissioning (see point [1] on page 42 )
every time you change any NE data (see point [2] on page 42 )
every time you upgrade the NE SWP (see point [7] on page 45 )
WARNING: If you change the NE data without performing the backup operations here
described, in case of troubles you will have to create again the NE configuration data
from the beginning, wasting time and with high probability of errors.
Every time you change any NE data, you must always save them by both the following two
procedures (they are both necessary, because some data are present only in one of the two backup
files):
a ) MIB back up (.bar file)
Refer to chapter 111 on page 155 (Supervision % MIB Management % Backup)
b ) NE configuration backup (.qcml file)
There are two alternative, but equivalent, ways:
using the function Get Configuration File of the Alarms & Settings tool (see
para.16.2.4 on page 75 ). In this case the save screen appears:
or clicking the button Get Configuration from NE in the Start wizard screen of the
NEinteractive Provisioning Tool (see Fig. 20. on page 61 ). In this case the following
screen appears ( Fig. 9. ), where you must click the Save as ... button:
Fig. 9. Last wizard screen of the NEinteractive Provisioning Tool
In both cases, save the file, giving it a mnemonic name and choosing the directory for save.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
44 / 232
[4] NE data restore
Whenever you must restore in the NE the data you have previously saved by the procedures of
previous point [3] , perform the data restore operations in the following order:
a ) at first, perform the NE configuration restore (.qcml file)
There are two alternative, but equivalent, ways:
using the function Configuration Setting of the Alarms & Settings tool (see
para.16.2.2 on page 69 ), at first browsing the backup file, then clicking on the button
Apply Configuration
or clicking the button Open Configuration in the Start wizard screen of the
NEinteractive Provisioning Tool (see Fig. 20. on page 61 ). In this case, the following
file selection screen opens, where you must browse the backup file, and then click on
the button Open:
Then, the screen of Fig. 9. on page 43 opens, but with the button Apply enabled: click
on it to send the configuration file to the NE. In alternative, click on Modify parameters,
to check the configuration before sending it to the NE.
WARNING: In some cases (depending on the data that have been changed), an automatic
system restart is executed (see point [8] on page 46 ), and the CTNE
communication is lost. Therefore, wait the time necessary for the restart
completion, after which you can perform again the NE login.
b ) then, perform the MIB restore (.bar file)
Refer to chapter 111 on page 155 (Supervision % MIB Management % Restore)
[5] Flash Card licence management
The Flash Card licence management allows to improve the max system throughput. It can be done:
for AWY 2.0.6 and 2.1.2, physically replacing the Flash Card with another type, as described
in following point [6] a )
or, only for AWY 2.1.3, as described in point 2 ) on page 39
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
45 / 232 3DB 75003 BAAA Ed.01
[6] Flash Card replacement
The Flash Card replacement implies always the NE data backup (before the replacement) and
restore operations (after the replacement), described in previous points [3] and [4]
The Flash Card replacement may be required for two reasons:
a ) Flash Card replacement with another type (i.e. another licence information), to improve the
max system throughput.
This type of replacement must be done according to the instructions given in the specific NE
User Manual ( Tab. 1. on page 14 ) , more precisely:
section MAINTENANCE AND UPGRADE
chapter System hardware upgrade
paragraph Installation of a new Flash Card to improve system capacity
N.B. The physical replacement of the Flash Card is necessary only for AWY 2.0.6 and
2.1.2; in the case of AWY 2.1.3 the licence information is managed without the
physical replacement of the Flash Card, as described in point 2 ) on page 39
b ) Flash Card replacement with the same type (i.e. the same licence information), for corrective
maintenance (i.e. when the Flash Card is suspected faulty).
This type of replacement must be done according to the instructions given in the specific NE
User Manual ( Tab. 1. on page 14 ) , more precisely:
chapter Spare Flash Card management and replacement procedures
paragraph Flash Card replacement procedure
[7] Upgrading of the NE SWP
This procedure is envisaged whenever a new NE SWP release (new with respect to that presently
loaded in the system) is supplied to Customer by the relevant NE SWP CDROM.
E.g. the SWP 9400AWY V2.1.2 CDROM is supplied to a Customer owing a 9400AWY R.2.1 NE
running with a SW version < V2.1.2 (V2.1.1, for example).
It means that the SW COMMIT VERSION bank in the Flash Card contains the SW components of
the version V2.1.1 (see point [2] on page 40 ) and must be replaced by those of the version V2.1.2.
With reference to such an example, the SWP upgrading corresponds to make the following
operations:
at first, the loading of the new V2.1.2 SW components (previously copied in the PC environment
from the SWP 9400AWY V2.1.2 CDROM) in the Flash Cards SW STANDBY VERSION bank
secondly, the swap of the SW COMMIT VERSION and SW STANDBY VERSION banks,
automatically followed by a system restart, which loads the new SW components in all
peripherals.
The NE SW upgrading must be done according to the instructions given in chapter 112 from page
175
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
46 / 232
[8] System restart
The system restart (reloading of all RAMs present in the system with information stored in the Flash
Card and reset of all peripherals):
is performed automatically in one of the following conditions:
after the activation of a new SWP
after a MIB restore and activation
only in some cases, depending on affected data, after the download of a configuration
.qcml file
after system power off / on
can be performed manually by the operator in one of the following ways:
pushing the reset button on the IDU Main Unit
with the NE logged in by WebEML, by the command Supervision Restart NE ( see
para.19.8.8 on page 132 ); clicking OK on the confirmation box (Do you really want to
restart this NE?), the system restart begins.
About 2 to 5 minutes are necessary for system restart.
WARNING: at the system restart beginning, the CTNE communication, if open, is lost.
Therefore, if necessary, you must perform again the NEinteractive application,
waiting the time necessary for the restart completion.
14.3 Startup and functions of the TCO SUITE Main Menu screen
There are two ways to launch the SWP TCO SUITE Main Menu screen:
a ) directly from the SWP TCO SUITE CDROM:
1 ) Verify that your PC meets the requirements described in para.11.3 on page 15
2 ) Insert the SWP TCO SUITE CDROM in your PC
3 ) If never done previously, the startup of the SWP TCO SUITE is performed automatically (it
installs, if necessary, the JRE required version), and the Main Menu screen opens ( Fig. 10.
below)
N.B. in case of problems, or for startup details, refer to Appendix B on page 191 (in
particular, take into account that the installation of the JRE requires the PC
Administrator privileges)
b ) clicking the shortcut to the Local Copy of the TCO Suite
N.B. To use this modality, the SWP TCO SUITE Local version, and the relevant shortcut, must
have been created previously, as described in step 7 ) on page 187
in both cases, the Main Menu screen of following Fig. 10. opens:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
47 / 232 3DB 75003 BAAA Ed.01
A
B
C
D
E
F
G
Fig. 10. Main Menu screen
The functions of the various buttons is summarized below.
N.B. before clicking any button, please read the instructions given in the relevant chapter or
paragraph.
A Provisioning Tool: see chapter 15 on page 59
9400AWY R.2.0 V2.0.6 CDROM,
With the SWP TCO SUITE, the button Provisioning Tool combines the functions of the
PreProvisioning Tool and SetUp Tool.
B Alarms & Settings: see chapter 16 on page 65
C Close Current Session: see para.14.6 on page 55
D Operational & Maintenance WebEML: see para.14.7 on page 56
E Operational & Maintenance 1320CT: see para.14.8 on page 58
F Acceptance Tool: see chapter 17 on page 83
G Advanced Settings: button present only in CDROM version. See Appendix A on page 185
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
48 / 232
14.4 Checks the operator must do before accessing a NE
The SWP TCO SUITE includes not NEinteractive applications, and NEinteractive applications.
For all NEinteractive applications, the checks that any operator must perform before attempting the
access from her/his PC (running the SWP TCO SUITE) to a 9400AWY NE, are summed up below:
N.B. Usually, these checks have to be performed once only (i.e., whenever you have not done them
previously for the specific NE).
a ) the operator must know the NEs local IP address and/or the Ethernet Configuration IP address,
that must have already been defined correctly inside the network from both physical and logical
points of view. Note:
the local IP address is that to be always used to access the NE by NEtO application
the Ethernet Configuration IP address is that to be always used to access the NE by the
NEinteractive Provisioning Tool and Alarms & Settings (web server) functions.
For details, refer to para.13.2.2 on page 28 , and to para.13.2.4 on page 30
b ) the PC must be able to reach the NE. To make this check, if necessary, refer to point [2] on page
29
c ) if more than one network adapter is present in the PC, you must know which is that used for the
PCNE connection (its identity could be required in the login procedure).
d ) if not yet done, it is mandatory to manually disable system and browser proxy configurations prior
to use the web server operations; otherwise, the IP connection from the PCs web server to the NE
cannot take place.
e ) the operator must have an UserName and Password set, valid for the NE that must be loggedin.
This information must be provided by the NE Administrator to the user.
Note: the operations allowed, after the successful login, depend on the NE login profile.
For details, refer to para.13.3.2 on page 34
f ) only for AWY 2.1.3 NE, and only for access by NEtO: if the NE Administrator has defined a
community string (different from the default value) for the specific NE, the operator must know it.
g ) only for AWY 2.1.3 NE: if the NE Administrator has defined the security by access lists for the
specific NE, the operator must know whether or not the IP address of her/his PC is enabled to the
specific services she/he wants to perform.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
49 / 232 3DB 75003 BAAA Ed.01
14.5 Common behavior of NE login, and application logoff, for the
NEinteractive Provisioning Tool and Alarms & Settings
The NEinteractive Provisioning Tool functions are described in point [2] from page 61
The Alarms & Settings functions are described in chapter 16 from page 65
This paragraph is referenced to by them, for executing the NE login, and the application logoff.
14.5.1 Constraints and preliminary checks
WARNING: as specified in Tab. 3. on page 25 and Tab. 6. on page 27, these functions must not
be launched if the PCNE connection is done through the F interface, whichever the
addressed NE is (local or remote)
Before to run one of these functions (clicking the suitable button of the Main Menu) you must make the
following checks:
a ) perform the checks listed in para.14.4 on page 48
b ) in addition, if the PCNE connection is physically local (i.e. through the direct connection by a
crossconnect Ethernet cable between the PC and NE Ethernet ports, or by an Ethernet switch), you
must know if:
the IP address of the PC
and the Ethernet Configuration IP address of the NE (see para.13.2.2 on page 28)
belong, or not, to the same subnetwork This implies a different choice between Local or Remote
in the application start screen [ step 4 ) on page 52 ]
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
50 / 232
14.5.2 NE login procedure
1 ) If necessary, perform Close Current Session, clicking the Main Menu relevant button
N.B. The first time you use the NEinteractive Provisioning Tool or the Alarms & Settings
function, you should not need to perform the Close Current Session. Refer to the step
2 ) on page 54 , to understand this need at a second time. Anyway, if you like to know
the current situation, click this button: the Network settings OK ( Fig. 16. on page 55 )
certifies that you start from a clear condition.
2 ) Launch the application you want (NEinteractive Provisioning Tool below, or Alarms & Settings
on page 51 ) from the Main Menu screen ( Fig. 10. on page 47 ), and enter the connection
parameters:
a ) to run the NEinteractive Provisioning Tool, click the specific button:
The screen of Fig. 11. below opens, where you have to specify Connect to NE (1) , then enter
the NE IP address (2) as detailed in step 3 ) on page 51 , then specify Local or Remote (3)
as detailed in step 4 ) on page 52 , and, at last, clicking OK button (4).
If more than one network adapter is found in the PC, the choice of which to use is forwarded
to the user [next step 5 ) on page 52 ]
Otherwise (only one network adapter is found in the PC), if the PCNE connection is correctly
established, the NE login screen appears [next step 6 ) on page 53 ]
(1)
(2)
(3) specify Local or Remote (4)
Fig. 11. Connection parameter screen for the NEinteractive Provisioning Tool
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
51 / 232 3DB 75003 BAAA Ed.01
b ) to run theAlarms & Settings function, click the specific button:
The screen of Fig. 12. below opens, where you have to enter the NE IP address (1) as detailed
in step 3 ) below, then specify Local or Remote (2) as detailed in step 4 ) on page 52, and,
at last, clicking OK button (3).
If more than one network adapter is found in the PC, the choice of which to use is forwarded
to the user [next step 5 ) on page 52 ]
Otherwise (only one network adapter is found in the PC), if the PCNE connection is correctly
established, the NE login screen appears [next step 6 ) on page 53 ]
(1)
(2) specify Local or Remote
(3)
Fig. 12. Connection parameter screen for the Alarms & Settings function
3 ) Specification of NE IP address in Fig. 11. or Fig. 12.
WARNING: if the local IP address and Ethernet Configuration IP address are different, you
must specify the Ethernet Configuration IP address : for details, refer to to
para.13.2.2 on page 28
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
52 / 232
4 ) Specification of Local or Remote in Fig. 11. or Fig. 12.
According to the checks you should have done in para.14.5.1 on page 49 :
a ) if the PCNE connection is physically remote (i.e. through IP network, or through Radio
interface, or through NMS rings and chains), specify Remote
b ) if the PCNE connection is physically local (i.e. through the direct connection by a
crossconnect Ethernet cable between the PC and NE Ethernet ports, or by an Ethernet
switch), and the IP address of the PC and the Ethernet Configuration IP address of the NE:
belong to the same subnetwork, specify Remote
do not belong to the same subnetwork, specify Local
As a consequence of the Local specification, the application adds semipermanently an
IP address to your PC, to allow it to reach the NE.
This semipermanently added IP address is cleared performing the Close Current
Session [see step 2 ) on page 54 ], or restarting the PC.
5 ) Choice of the network adapter, if required
The application performs a search on users computer resources in order to find all network adapters
related to active (enabled) network connections [see point c ) on page 48 ]. Then, if more than one
network adapter is found, the user must select the one to use. An example of selection box is shown
in Fig. 13. below:
Fig. 13. Network Adapter selection
Such figure is an example created to show the possible layout. Actually, if users PC owns one
network adapter only and the Alcatel Virtual Network Card for Lower Layers, the selection is
automatically done without bothering the user, which will not see the dialog box shown in Fig. 13.
above.
WARNING: the virtual network card you may have created for the LLMAN (by the procedures
described in Appendix C from page 201 ) must never be selected to connect the
PC to the NE, for running the NEinteractive Provisioning Tool and the Alarms &
Settings functions.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
53 / 232 3DB 75003 BAAA Ed.01
To know more information about adapters details, by clicking the Details toggle button some
supplemental information are shown as in Fig. 14. :
Fig. 14. Network Adapter details
Network adapters configuration is saved in XML format using the NAML (Network Adapter Markup
Language) format in the NAML directory inside users personal directory usually located inside
Documents And Settings directory on system disk.
When the user clicks Apply in screen of Fig. 13. or Fig. 14. , and if, in step 4 ) on page 52 :
Remote has been specified, the PCNE connection is setup using the selected network
adapter (without performing any adaptation)
Local has been specified, a new address is added to the network adapter, to allow the PC
connection with specified NE, and the PCNE connection is setup
At last, if the PCNE connection is correctly established, the NE login screen appears [step 6 )
below]
6 ) NE login and application opening
If the PCNE connection is correctly established, the NE login screen opens, where user is asked
to provide his/her UserName and Password (for details, see point [1] on page 34 ):
After having filled the fields UserName and Password, followed by the Apply button clicking, if
login successful:
in case of NEinteractive Provisioning Tool, the screen of Fig. 20. on page 61 opens
in case of Alarms & Settings, the screen of Fig. 21. on page 66 opens
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
54 / 232
14.5.3 Application logoff procedure
1 ) Exit from the application NEinteractive Provisioning Tool or the Alarms & Settings, clicking
of the relevant screen
2 ) If necessary, perform Close Current Session, clicking the Main Menu relevant button.
Explanation:
After having exiting the application for a certain NE ....
... and if, in step 4 ) on page 52 you have specified:
Remote, you have nothing to do to launch one of the applications NEinteractive
Provisioning Tool or the Alarms & Settings for the same or another NE
Local, you have to decide if the semipermanent change on the used network adapter must:
remain. In this case, if you run again the NEinteractive Provisioning Tool or the Alarms
& Settings, no question is raised, and the connection to the NE previously connected is
established again;
be removed. In this case, click the Close Current Session button and the network settings
restoration message ( Fig. 15. on page 55 ) will appear, certifying that the network
adapter restoration has been done, and that you can now launch one of the applications
NEinteractive Provisioning Tool or the Alarms & Settings for another NE.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
55 / 232 3DB 75003 BAAA Ed.01
14.6 Close Current Session
This function is run clicking the following button of Main Menu screen ( Fig. 10. on page 47 ):
This function allows to close current session restoring the network settings modified by a previous run of
the NEinteractive Provisioning Tool or Alarms & Settings in Local mode [as described in step 4 )
on page 52 ].
It means that, if you have previously used one of such functions, and you want to use the same function
with another NE, before clicking the relevant buttons, you must at first click on the button Close Current
Session.
Fig. 15. (example) shows the message certifying the network adapter restoration:
Fig. 15. Close Current Session: network settings restoration message
Fig. 16. shows that you can run the NEinteractive Provisioning Tool or Alarms & Settings starting from
a cleared condition.
Fig. 16. Close Current Session: Network settings OK
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
56 / 232
14.7 Operational & Maintenance WebEML
This button launches the NEtO application. Before to click it, read carefully the following warnings:
WARNING 1: for the use of this function, the Local copy of WebEML (Jusm/CT) must have already
been performed, as described in point 8 ) on page 188
WARNING 2: in case of CTNE connection through the F interface ( see Fig. 2. on page 25 ), before
to click the button Operational & Maintenance WebEML, you must perform all operations
described in point c ) on page 99 , i.e.:
check of LLMAN (Lower Layer MANager) installation and configuration
PC desktop Properties System standby and System hibernates both set to Never
manual start of LLMAN
Standard behavior:
If the Local copy of WebEML (Jusm/CT) has been performed, this function runs the NEtO software
application, opening its first screen:
For NEtO usage, refer to the Chapter 18 on page 97
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
57 / 232 3DB 75003 BAAA Ed.01
Special conditions:
If the Local copy of WebEML (Jusm/CT) is not found in the default local place, this function asks
the user if there is a previously performed local copy:
Selecting:
Yes, specify the folder where the WebEML is. then function will run NEtO in the specified folder.
No, this function asks if user wants to perform WebEML Local Copy:
If choice No, this function exits. If choice Yes, WebEML in the CDROM is copied from the
CDROM to a specified folder [as described in point 8 ) on page 188 ], then NEtO is started.
WARNING: the Local copy of WebEML (Jusm/CT) can be done only from the CDROM.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
58 / 232
14.8 Operational & Maintenance 1320CT
This function runs the 1320CT software application previously installed on users PC, and is meant for old
9400AWY NEs backward compatibility. Before to click it, read carefully the following warnings:
WARNING 1: if users PC does not have a 1320CT platform installed, an error message is shown to user
(besides, take into account that no 1320CT installation can be performed by the SWP TCO
SUITE CDROM, because it does not contain the relevant SW components).
WARNING 2: the 1320CT application must not be used with 9400AWY NEs running with V2.1.3.
WARNING 3: in case of CTNE connection through the F interface ( see Fig. 2. on page 25 ), before
to click the button Operational & Maintenance1320CT, you must perform the same
operations envisaged for NEtO launch, described in point c ) on page 99 , i.e.:
check of LLMAN (Lower Layer MANager) installation and configuration
PC desktop Properties System standby and System hibernates both set to Never
manual start of LLMAN
If the 1320CT software application is present on users PC, the Network Element Synthesis (NES) screen
opens:
For NES usage, refer to the specific NE User Manual ( Tab. 1. on page 14 ).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
59 / 232 3DB 75003 BAAA Ed.01
15 PROVISIONING TOOL
This chapter describes in detail the functions of the Main Menus Provisioning Tool.
N.B. Besides from the Local Copy of the TCO Suite, the Provisioning Tool can be run also directly
from the TCO SUITE CDROM, without performing the copy procedures of the Appendix A
This function allows to create, modify and/or apply provisioning files in two ways:
not NEinteractive (offline), point [1] below
or NEinteractive, point [2] on page 61
[1] Not NEinteractive modality (offline)
This modality allows the offline creation and modification of a .qcml configuration provisioning file,
without accessing any NE.
This .qcml file will be after used to configure the NE (after having logged it) with a simple load
command.
The screen of Fig. 17. below opens, where you have to specify Do not connect to NE (offline), and
then click OK
(1)
(2)
Fig. 17. Start of the Not NEinteractive Provisioning Tool
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
60 / 232
After clicking the OK button, the following prompt screen appears, where you must choose the
9400AWY system type, and then click OK:
Fig. 18. Not NEinteractive Provisioning Tool: choice of NE version
After clicking OK, the following screen appears:
Fig. 19. Start wizard screen of the Not NEinteractive Provisioning Tool
This is the first screen of the Full Configuration Procedure, described in point [3] on page 62
See also the Configuration file conversion feature, described in point [4] on page 63
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
61 / 232 3DB 75003 BAAA Ed.01
[2] NEinteractive modality
By this modality, you access one NE, not using the Craft Terminal application, but the NE web server;
its main steps are:
launch the application and the connection with the target NE,
recover a configuration file configuration_name.qcml previously created (e.g. through the Not
NEinteractive Provisioning Tool described in previous point [1] on page 59 ), or get
configuration data from the NE
check/modify the configuration,
apply the configuration to the target NE.
WARNING: when the traffic is running, the use of the Provisioning Tool in NEinteractive modality,
may cause E1 and/or Ethernet traffic interruption.
Procedure
a ) Start of the application
To start this application, and login the NE, strictly follow instructions given in para.14.5 on
pages 49 to 53
b ) Use of the application
After having successfully connected to the NE and loggedin it, the following screen appears:
Fig. 20. Start wizard screen of the NEinteractive Provisioning Tool
This is the first screen of the Full Configuration Procedure, described in point [3] on page
62
See also the Configuration file conversion feature, described in point [4] on page 63
c ) Exiting from the application
Strictly follow instructions given in para.14.5.3 on page 54
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
62 / 232
[3] Full Configuration Procedure
This procedure allows a full system configuration through a guided process, based on a reduced set
of screens (steps). The related windows are displayed by a Wizard Tool according to a specific step
sequence.
Clicking the Help button in the Start wizard screen:
of the Not NEinteractive Provisioning Tool ( Fig. 19. on page 60 )
or of the NEinteractive Provisioning Tool ( Fig. 20. on page 61 )
the following help screen opens (example for 9400AWY R.2.1 V2.1.3):
Please, follow this guide, to have all information necessary for choosing and filling the various fields
of each step, to go forward and backward within the procedure steps, and to save or get the .qcml
configuration file, or apply the configuration to the NE.
In addition, to get system hardwarerelated information you may not find in the help online, refer to
the specific NE User Manual ( Tab. 1. on page 14 ), more precisely:
section NE MANAGEMENT BY SOFTWARE APPLICATIONS
chapter Provisioning
or, for some older User Manuals:
section INSTALLATION AND COMMISSIONING
chapter Lineup and commissioning
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
63 / 232 3DB 75003 BAAA Ed.01
[4] Configuration file conversion feature
After having clicked the button Open Configuration in
Fig. 19. on page 60 (not NEinteractive modality)
or in Fig. 20. on page 61 (NEinteractive modality)
you can also specify a .qcml configuration file that was created on a 9400AWY system running with
a SWP version < V2.0.6 or < V2.1.2 or < V.2.1.3
In this case, the Configuration file conversion feature converts the source file (or tries to do it) to
the target format, according to the following rules:
a ) in not NEinteractive modality, if in the NE version choice screen ( Fig. 18. on page 60 ) you
have selected:
1 ) Version V2.0.6,
you can select a .qcml configuration file that was created on a 9400AWY system running
with one of following versions of 9400AWY R.2.0:
V2.0.4 (only if configured for ETSI market) and V2.0.5
The result. if successful, will be the file conversion to the target format V2.0.6
2 ) Version V2.1.2,
with one of following versions of:
9400AWY R.2.0:
V2.0.4 (only if configured for ETSI market), V2.0.5, and V2.0.6
9400AWY R.2.1:
V2.1.0 and V2.1.1
3 ) Version V2.1.3,
with one of following versions of:
9400AWY R.2.0:
V2.0.4 (only if configured for ETSI market), V2.0.5, and V2.0.6
9400AWY R.2.1:
V2.1.0 and V2.1.1 and V2.1.2
b ) in NEinteractive modality, if you have logged in a 9400AWY with:
Version V2.0.6, the format conversion feature is as in point 1 ) above
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
64 / 232
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
65 / 232 3DB 75003 BAAA Ed.01
16 ALARMS & SETTINGS
This chapter describes in detail the Main MenusAlarms & Settings functions.
Subject On page
Alarms & Settings overview, startup, and closing below
Alarms & Settings functions 66
Date & Time Setting 68
Configuration Setting 69
Configuration Info 70
Get Configuration File 75
Active Alarms 76
Power Measurement 77
Modem Speed 77
Licence Info 78
NAT option 79
16.1 Alarms & Settings overview, startup, and closing
The Alarms & Settings function is a NEinteractive function, allowing the user to login a NE through the
use of the NE web server via a generic Internet browser, in order to monitor the status of NE alarms and
to get and/or set some NEs parameters.
N.B. Besides from the Local Copy of the TCO Suite, it can be run also directly from the TCO SUITE
CDROM, without performing the copy procedures of the Appendix A
Procedure
a ) Start of the application
To start this application, and login the NE, strictly follow instructions given in para.14.5 on pages
49 to 53
b ) Use of the application
After having successfully connected to the NE and loggedin it, the screen of Fig. 21. on page 66
appears.
c ) Exiting from the application
Strictly follow instructions given in para.14.5.3 on page 54
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
66 / 232
16.2 Alarms & Settings functions
AWY 2.0.6 & 2.1.2
AWY 2.1.3
Fig. 21. Alarms & Settings Main Menu screen
WARNING 1: when PC to NE connection is established, a timeout for an automatic logout is set, so
that after 5 minutes of connection without user operations, the application logouts
automatically (for security purposes), and user is obliged to repeat again login.
WARNING 2: if, during the usage of the Alarms & Settings functions, the connected NE becomes
unavailable (e.g. for network problems, or after having loaded NE data which modify the
NE IP address), the sandglass symbol appears and no operations are longer possible.
In this case, close the Alarms & Settings session, then verify the NE reachability (e.g. by
ping function), and login it again.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
67 / 232 3DB 75003 BAAA Ed.01
Operations allowed according to AWY type and the Login profile (refer to point [2] on page 34 for details)
are:
Tab. 7. Operations allowed in the Alarms & Settings screen according to the AWY type and Login
profile
Function
Operation allowed according to
Function type
Available for
AWY type
Operation allowed according to
Login profile
Function type
and where described
2.0.6 &
2.1.2
2.1.3 Administrator CraftPerson Operator Viewer
Date & Time Setting
YES YES set & read read only read only read only
Configuration Setting
YES YES YES YES NO NO
Configuration Info
YES YES YES YES YES YES
Get Configuration File
Active Alarms
Power Measurement
YES YES set & read set & read read only read only
Licence Info
YES YES
YES
(with 2.1.3
licence
management)
read only read only read only
Community String
para.113.2 on page 178
NO YES YES NO NO NO
Access List Restore
point [6] on page 182
NO YES YES NO NO NO
Access List Backup
point [5] on page 182
NO YES YES NO NO NO
Modem Speed
YES YES set & read set & read set & read read only
NAT Option
YES YES set & read set & read NO NO
User can perform desired operations by clicking on proper label in proposed menu. The behavior of the
Web Server for each of menu entry is detailed in the following subparagraphs.
Logout button gives the user the possibility to clear its authentication parameters and reload the initial page
(Fig. 21. on page 66) for starting a new session.
The links between pages are available by following standard procedures and correct navigation steps.
If the user will follow nonauthorized processes or will try to search for other pages, a 404 error will show
the Page Not Found result. In this case, the user will be allowed to get back to initial login page and he
has to redo the whole login process.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
68 / 232
16.2.1 Date & Time Setting
For set & read authorized users ( see Tab. 7. on page 67 ), this function allows to modify NE internal
time so that it can be automatically aligned with users PC internal time or the user can set its preferred
time and date on NE. Also, it is possible, for the user, to verify the status of NTP configuration for automatic
synchronization using a couple of NTP server (main and backup).
The read only authorized users ( see Tab. 7. on page 67 ) cannot make any setting operation.
There are two functions available to authorized users:
1. NE Time Setting with OS time;
2. GMT Time Manual Setting.
In the first situation (Fig. 22. below) the user will see his/hers PC internal time and by clicking on apply,
NE will receive UTC time based on PC configuration.
For example: if users PC is configured as located in central Europe (CET or CEST time zones) and it
shows 20060825 11:40:00, by clicking Apply button NE web server will receive 20060825 09:40 due
to Daylight Saving (summer) Time one hour difference with respect to normal time and to one hour time
difference between CET time zone and GMT time zone.
Fig. 22. Alarms & Settings Date & Time Setting request
The other function allows user to directly send a specific date and time information to NE without bothering
on time zones but simply specifying all the information needed.
In both cases there could be some short delays (few seconds) between applied time shown after the
operation and current time or selected time.
In case of enabled NTP, this page wont allow to modify NE time and date
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
69 / 232 3DB 75003 BAAA Ed.01
16.2.2 Configuration Setting
For authorized users ( see Tab. 7. on page 67 ), the Configuration Setting process allows the operator
for sending to NE the operators desired configuration.
The unauthorized users ( see Tab. 7. on page 67 ) cannot see this screen.
Fig. 23. Alarms & Settings Configuration Setting page
To carry out this operation, you must browse from your PC a configuration file configuration_name.qcml
previously created (e.g. through the Provisioning Tool), and then click on Apply Configuration button.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
70 / 232
16.2.3 Configuration Info
The Configuration Info function allows the user to download the full NE system report. Selecting (by click)
this function from main menu will show the user a Save File screen ( Fig. 24. below ) that gives the user
the capability to browse its system in order to select the path where to save the full report file.
N.B. With some browsers (e.g. Mozilla), it is necessary to specify a textreading application (e.g.
WORD PAD) to open and read correctly the file.
Fig. 24. Alarms & Settings Configuration Info request
This screen content, shape, graphics and layout all depend on operating system version and language
and on used browser too. The report file is a text file that describes the configuration of the NE. It contains
all the information once added to the quick configuration report or in the current configuration view used
in the former versions. An example of this file content is shown below:
CONFIGURATION INFO
==================
Site Name: uls213_107
Site Location: tp

INSTALLED SOFTWARE:
[Active SW Package: R94A V02.01.03]

Status: Committed
Operational State: Enabled
SW Units:
OC_R V03.00.01 Size(Bytes): 1334619
EC V03.03.17 Size(Bytes): 2787100

NETWORK EQUIPMENT CONFIGURATION:
NE Configuration Type:1+1 HSB 16E1 GETH (PSU4860) EPS

Market: ETSI
Capacity: 32E1
Modulation: 16QAM

TRIBUTARY CONFIGURATION:
Impedance: Balanced 120 Ohm

E1 Port #1: Signal Mode: Unframed
E1 Port #2: Signal Mode: Unframed
E1 Port #3: Signal Mode: Disabled
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
71 / 232 3DB 75003 BAAA Ed.01

DATA CONFIGURATION:
[Ethernet Port 33]

Status: Disabled
Auto Negotiation: Enabled
Speed without AutoNegotiation: 100 Mbit/s
Flow Control Status (tx): Asymmetric
AutoNegAdvertise rate ability:
10base Half Enable
10base Full Enable
100base Half Enable
100base Full Enable
1000base Full Enable
Qos Classification Mode:
802.1p
Vlan Accept Frame Type:
all
Vlan Pvid:
1
Vlan Priority:
0
Autolink Shutdown Status:
Disabled
Rate control value:
0
[Ethernet Port 34]
Status: Disabled
10base Half Enable
10base Full Enable
100base Half Enable
100base Full Enable
802.1p
all
Vlan Pvid:
1
Vlan Priority:
0
Disabled
Rate control value:
0
[Ethernet Port 35]
Status: Disabled
10base Half Enable
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
72 / 232
10base Full Enable
100base Half Enable
100base Full Enable
802.1p
all
Vlan Pvid:
1
Vlan Priority:
0
Disabled
Rate control value:
0
[Ethernet Port 36]
Status: Disabled
10base Half Enable
10base Full Enable
100base Half Enable
100base Full Enable
802.1p
all
Vlan Pvid:
1
Vlan Priority:
0
Disabled
Rate control value:
0
Eth Vlan Bridge Type:
802.1Q

Static Vlan Xconn:
[Vlan Xconn: 1]
vlan name: Default VLAN_1, VID:1, untagPort:15, egressPort:31

RESTORATION CRITERIA:
Radio Protection: Revertive

Mux/DeMux Protection: Revertive
HSBTx Protection: Revertive

RADIO CONFIGURATION:
[Channel 1]
ATPC Status: Disabled
RTPC Tx Power: 10.0 dBm
Tx Frequency: 14500000 kHz
Tx Range: [14500000; 14724000] kHz
Rx Frequency: 14920000 kHz
Rx Range: [14920000; 14920000] kHz
Shifter Central Frequency: 14612000 kHz
Shifter Amplitude: 420000 kHz

[Channel 0]
ATPC Status: Disabled
RTPC Tx Power: 17.0 dBm
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
73 / 232 3DB 75003 BAAA Ed.01
Tx Frequency: 14500000 kHz
Tx Range: [14500000; 14724000] kHz
Rx Frequency: 14920000 kHz
Rx Range: [14920000; 14920000] kHz
Shifter Central Frequency: 14612000 kHz
Shifter Amplitude: 420000 kHz

LINK IDENTIFIER:
Expected Mode: Disabled

Expected Value: 0
Sent Value: 0

ETHERNET CONFIGURATION:
Local IP Address:
130.1.1.107

Status: Enabled
IP Address:
172.25.20.107
IP Mask:
255.255.255.0
MAC Address:
00:11:3f:c0:ee:66

Routing Protocol: OSPF
OSPF Area:0

[Network Time Protocol]:
Status: Enabled
Main Server: 151.98.99.242
Spare Server: 151.98.99.244

OSPF AREAS:
[Ospf Area 0]
IP Address: 0.0.0.0
Stub Area: OFF
[Ospf Area 1]
IP Address: 130.0.0.0
Stub Area: OFF
[Ospf Area 2]
IP Address: 0.0.0.2
Stub Area: OFF

TMN INTERFACES:
[TMNRF]
Status: Enabled
RF Remote Address: 130.1.1.108
Routing IP Protocol: OSPF
OSPF Area:2
[TMNV11]
Status: Enabled
Remote Address: 130.1.1.108
Mode: Codirectional
OSPF Area:2
[TMNG703]
Status: Enabled
Remote Address: 130.1.1.101
Mode: Codirectional
OSPF Area:0

STATIC ROUTES:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
74 / 232

EXTERNAL POINTS STATUS:
[Input Point 1]
User Label:CPI#1a
Polarity: Active Closed
[Input Point 2]
User Label:CPI#2a
Polarity: Active Open
[Input Point 3]
User Label:CPI#3a
[Input Point 4]
User Label:CPI#4a
[Input Point 5]
User Label:CPI#5a
[Input Point 6]
User Label:CPI_6_prova

[Output Point 1]
User Label:fuori1
Working Mode: Manual
External State: Off
[Output Point 2]
User Label:CPO#2222
External State: Off
[Output Point 3]
User Label:CPOtre
Working Mode: Automatic
Associated Event: Line side LOS Alarm
[Output Point 4]
User Label:CPO#4444
External State: Off
[Output Point 5]
User Label:FAIL IDU
[Output Point 6]
User Label:FAIL ODU CH#1
[Output Point 7]
User Label:FAIL ODU CH#0
The content above describe a sample configuration report in text format.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
75 / 232 3DB 75003 BAAA Ed.01
16.2.4 Get Configuration File
Just like the Configuration Info function function, the Get Configuration File function allows the user to
download the full NE system report. Instead of being in humanreadable text format, the configuration
file is described in QCML format and it can be used by the Provisioning Tool. Selecting (by click) this
function from main menu will show the user a Save File screen (Fig. 25. below) that gives the user the
capability to browse its system in order to select the path where to save the full report file.
N.B. With some browsers (e.g.Mozilla), it is necessary to specify a textreading application (e.g.
WORD PAD) to open and read correctly the file.
Fig. 25. Alarms & Settings Get Configuration File request
This file is an XML standardbased set of configuration information that the Provisioning Tool can preview
in a humanreadable HTML layout and allow the user to modify such configuration using a set of
wizard/simplified steps.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
76 / 232
16.2.5 Active Alarms
Alarms monitoring is represented by a simple colored table that will shows an updated list of active alarms.
Older alarms, anyway, wont be removed but in order to be more comprehensible, activated alarms table
will be updated by recreating the whole table each time, so showing only all active alarms in any moment.
Fig. 26. Alarms & Settings Active Alarms: Static Page
This table can be presented into two ways: the first one shown when user chooses Active Alarms function
is a simple page that will show to user alarms active at the moment of its selection.
To give user a better control on this status table, a Refresh button is provided. This button will redo the
request to NE and updates shown HTML page anytime is pressed.
The Enable Automatic Refresh button allows the user to forget about doing a refresh by providing an
automatic refresh process (Fig. 27. below).
Fig. 27. Alarms & Settings Active Alarms: Automatic Page
This page will do a periodic automatic refresh of its content and anyway allows the user to get back to the
manual refresh page.
WARNING: For autorefreshed pages, a longer timeout is foreseen. This is set to 90 refresh cycles
of 10 seconds each, for a total of 15 minutes. After this timeout, the connection expiration
page is shown.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
77 / 232 3DB 75003 BAAA Ed.01
16.2.6 Power Measurement
According to Tab. 7. on page 67 , this page ( Fig. 28. below ) allows:
authorized set & read users, to set the power measurement
all users, to read the power measurement result.
Refresh Interval filed allows the operator to set the time duration of the measurement for automatic
refreshing. The choice is among 5,10,30 sec. Otherwise operator can click refresh button directly to
refresh the result of power measurement.
Fig. 28. Alarms & Settings Power Measurement request
16.2.7 Modem Speed
According to Tab. 7. on page 67 , this page ( Fig. 29. below ) allows:
all users, to read the current FInterface speed value
authorized set & read users, to modify it, through a simple combo box.
N.B. see also para.24.7 on page 225
Fig. 29. Alarms & Settings Modem Speed request
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
78 / 232
16.2.8 Licence Info
a ) Case of AWY 2.1.3
This screen allows an operator logginin the NE with the Administrator profile, to read and manage
dinamically the license information, as described in point [1] 2 ) on page 39
N.B. in case of login profile different from Administrator, the Set Licence key field and Apply
button are not available, so that only the read operation is possible.
b ) Case of AWY 2.0.6 and 2.1.2
This page allows the user just to read the license information.
Fig. 30. Alarms & Settings Licence Info request
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
79 / 232 3DB 75003 BAAA Ed.01
16.2.9 NAT Option
According to Tab. 7. on page 67 , this page ( Fig. 31. below ) allows authorized set & read users, to
set the NAT Option, described in the following.
The unauthorized users (see Tab. 7. on page 67 ) cannot see this screen.
Fig. 31. Alarms & Settings NAT option request
N.B. This setting is independent from that of the Provisioning tool:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
80 / 232
[1] NAT router
In the following the scenario, when the NAT router is used in the network, is analyzed, providing a
list of warnings and the relevant countermeasures. The scenario is represented by a remote
manager that wants to access the radio network; in between one or more NAT router could be
present. WTD suggests not using this device because of the consequences that are hereunder
described.
[2] What is the NAT router
The Network Address Translation allows a single device, such as a router, to act as agent between
the Internet (or public network) and a local (or private) network. This means that only a single
unique IP address is required to represent an entire group of computers to anything outside their
network. The shortage of IP addresses is the main reason to use NAT.
Fig. 32. NAT router
The NAT function cannot by itself support all applications transparently and often must coexist with
application level gateways (ALGs) for this reason. People looking to deploy NAT based solutions
need to determine their application requirements first and assess the NAT extensions (i.e., ALGs)
necessary to provide application transparency for their environment. NAT devices are application
unaware in that the translations are limited to IP/TCP/UDP/ICMP headers and ICMP error messages
only. NAT devices do not change the payload of the packets, as payloads tend to be application
specific. NAT devices (without the inclusion of ALGs) do not examine or modify transport payload.
For this reason, NAT devices are transparent to applications in many cases.
[3] What are the NAT router limitations
As stated on the RFC 2663
IP Network Address Translator (NAT) Terminology and Considerations
there are three main areas where NAT devices often cause difficulties:
1 ) when an application payload includes an IP address,
2 ) the FTP application unless to operate dedicated setting and
3 ) when endtoend security is needed (ex. IPSec transport mode or the TCP MD5 Signature
Option)
About 1 ) , SNMP is one such application with address content in payload. NAT routers would not
translate IP addresses within SNMP payloads. It is not uncommon for an SNMP specific ALG to
reside on a NAT router to perform SNMP MIB translations proprietary to the private network, but for
sure it is expensive and NAT device depending.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
81 / 232 3DB 75003 BAAA Ed.01
[4] How the WTD equipments SNMP based are impacted
1 ) About the Manager IP Address Access Control Security
This feature allows the control of the IP manager forbidding the access for any manager that
is not registered. For the 9400AWY family, the Start Supervision operation/sequence is
completed successful only if IP packets coming from the manager have the same IP source
address than the one contained in the Registration table (retrieved by the SNMP message); this
means, in case of NAT usage, no way to access the equipment.
2 ) Disabling the Manager IP Access Control
Obviously the case of NAT presence has been overcame with some modification, considering
it as exceptional case.
For example for both products can be enabled the No registration or NAT presence option
that skips the previous check.
In this case some drawbacks can be observed, compared to the standard behavior.
9400AWY case
No registration Standard Access Control
NE Reset NOK OK
Loopback commands NOK OK
Shifter management NOK OK
3 ) About the FTP application
One of the most popular internet applications FTP could not work in presence of the NAT,
unless specific implementations are provided.
Generally the TCP checksum and the TCP sequence and acknowledge numbers must be
updated to reflect the change in length of FTP control data portion: detailed explanation can be
found on the RFC 2663.
Consequently some applications can be impacted as:
Software Download
Backup and Restore
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
82 / 232
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
83 / 232 3DB 75003 BAAA Ed.01
17 ACCEPTANCE TOOL
This chapter describes in detail the functions of the Main Menus Acceptance Tool:
Subject On page
Acceptance Tool scope 84
Acceptance Tool start 85
Acceptance Tool in NEinteractive modality 86
Bench setup and startup of the NEinteractive Acceptance Tool 86
Main functions of the NEinteractive Acceptance Tool 88
Create Report 90
Acceptance Tool in not NEinteractive modality (offline) 96
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
84 / 232
17.1 Acceptance Tool scope
The radio link lineup, commissioning, and acceptance phases are summarized as follows:
[1] Turn up (phase 1)
1 ) These phases are performed with IDUODU cable(s) disconnected from IDU:
a ) Station A, roughly point the antenna towards station B (if not done in the Hardware
Installation procedure)
b ) Commission station A (phase 1)
c ) Commission station B (phase 1)
ODU ODU
STATION A STATION B
IDU IDU
CT
CT
2 ) Powering up the IDU(s) with the ODU(s), fine antenna alignment, and preliminary checks
Stations A & B
d ) Station B, fine align the antenna towards station A, and preliminary checks
e ) Station A, fine align the antenna towards station B, and preliminary checks
ODU ODU
STATION A STATION B
IDU IDU
CT
CT
[2] Site acceptance tests (phase 2)
3 ) Station A, perform all the commissioning checks and tests Report the results in the TRS
ODU ODU
STATION A STATION B
IDU IDU
CT
DDF
test loops
4 ) Station B, perform all the commissioning checks and tests Report the results in the TRS
ODU ODU
STATION A STATION B
IDU IDU
CT
DDF
test loops
DDF
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
85 / 232 3DB 75003 BAAA Ed.01
N.B. the radio link lineup, commissioning, and acceptance phases are described in detail in the
specific NE User Manual ( Tab. 1. on page 14), more precisely:
section SW INSTALLATION AND COMMISSIONING
chapter LineUp and Commissioning
The Acceptance Tool is used in the phase 2 (Site acceptance tests) to create the TRS document (Test
Report Sheets & Site Acceptance report), and allows to:
retrieve automatically most of the system information from the equipment (local and remote stations),
introduce manually the remaining system information (not retrieved automatically), test results and
comments through dedicated screens on the PC,
create a file containing all data (extension .atml), that can be open at a second time and modified
as needed,
generate a final TRS document in Adobe Acrobatt .pdf format, following predefined output
templates.
17.2 Acceptance Tool start
N.B. Besides from the Local Copy of the TCO Suite, the Acceptance Tool can be run also directly
from the TCO SUITE CDROM, without performing the copy procedures of the Appendix A
This function can be run in two ways:
NEinteractive, para.17.3 on page 86
or not NEinteractive (offline), para.17.4 on page 96
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
86 / 232
17.3 Acceptance Tool in NEinteractive modality
17.3.1 Bench setup and startup of the NEinteractive Acceptance Tool
With reference to Fig. 33. below, to use this function:
you must know the Ethernet Configuration IP address of the Local station, and the Local IP
address of the Remote station. Refer to para.13.2.2 on page 28 for details.
for each of the two NEs that must be loggedin, you must have an UserName and Password set. The
allowed Login profile can be only Administrator or CraftPerson. Refer to point [1] on page 34
for details.
WARNING: this function must not be launched if the PCNE connection is done through the F
interface, and must not be launched if the PCNE connection is trough the IP network.
As shown in Fig. 33. below:
setup the bench,
through the ping function, check that both NEs are reachable by the PC (using the addresses stated
above),
start the Acceptance Tool from the Main Menu screen (see para.17.2 on page 85 ),
fill the Local and Remote fields, then click OK.
ODU
ODU
LOCAL STATION
9400AWY RADIO LINK
Eth
CT
REMOTE STATION
IDU IDU
Local = Ethernet Configuration IP address Remote = Local IP address
crossconnect
Ethernet cable
Fig. 33. Bench setup and startup of NEinteractive Acceptance Tool
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
87 / 232 3DB 75003 BAAA Ed.01
If both NEs are reachable by the PC, the NE login screen opens, where user is asked to provide his/her
UserName and Password (for details, see point [1] on page 34 ):
Fig. 34. Authentication request for NE login
N.B. two NE login screens must be filled, one for each of the two NEs.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
88 / 232
17.3.2 Main functions of the NEinteractive Acceptance Tool
If the double NE login of Fig. 34. on page 87 is successful, the following screen opens:
Fig. 35. Main functions of the NEinteractive Acceptance Tool
The following functions are available:
a ) Modify Report allows to open an .atml file saved previously [see point c ) on page 91 ]. If you
click this button, a suitable screen will ask you to browse and open the file. After having opened the
file the following screen opens:
Clicking the button Next> in this screen, the first step of the Acceptance Tools Create Report
function opens (see Fig. 37. on page 91 ). Now, you can navigate the report steps to introduce
the changes you like.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
89 / 232 3DB 75003 BAAA Ed.01
b ) Create Blank Report allows to create a blank .pdf file.
A blank report can be useful for Customers who prefer to fill the information on the printed papers
by hand.
If you click this button:
at first, you are asked to choose a template:
Fig. 36. Choose report template
then, a suitable screen will ask you to give a name to the file, and to specify where to save it.
c ) Create Report allows to create the real NEinteractive report, as detailed in para.17.3.3 on page
90
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
90 / 232
17.3.3 Create Report
Clicking Create Report in the screen of Fig. 35. on page 88 , causes the following operations:
At the end, clicking Next starts the creation of the report.
The report structure is intuitive for the Operators performing the commissioning phase according to the
chapter LineUp and Commissioning of the specific NE User Manual ( Tab. 1. on page 14 ). Some
usage notes are added:
a ) the report is organized in steps. You can move forward and backward in such steps, by means of the
<Prev and Next> buttons:
b ) each step has two tabbed panels, one for the Local station, the other for the Remote one:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
91 / 232 3DB 75003 BAAA Ed.01
c ) in the last step:
you can click:
Save , to save the report in an .atml file. If you click this button, a suitable screen will ask you
to give a name to the file, and to specify where to save it.
N.B. this Save execution is always strongly suggested.
Generate Report , to save the report in a .pdf file. If you click this button:
at first, you are asked to choose a template (see Fig. 36. on page 89 )
then, a suitable screen will ask you to give a name to the file, and to specify where to save
it.
An example of the steps of this procedure is given in the following (example referred to AWY 2.1.3):
Fig. 37. First step of the Acceptance Tools Create Report function
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
92 / 232
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
93 / 232 3DB 75003 BAAA Ed.01
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
94 / 232
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
95 / 232 3DB 75003 BAAA Ed.01
Fig. 38. Last step of the Acceptance Tools Create Report function
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
96 / 232
17.4 Acceptance Tool in not NEinteractive modality (offline)
Start the Acceptance Tool from the Main Menu screen (see para.17.2 on page 85 ),
select Do not connect to NE (offline), then click OK
after clicking the OK button, the following prompt screen appears, where you must choose the
9400AWY system type, and then click OK:
after choice and OK, the following screen opens:
The following functions are available:
Modify Report operates as described in point a ) on page 88
Create Blank Report operates as described in point b ) on page 89
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
97 / 232 3DB 75003 BAAA Ed.01
18 NETO (NETWORK ELEMENT OVERVIEW)
This chapter describes in detail the functions of NEtO.
Subject On page
General on NEtO 98
NEtO functions 98
NEtO sessions and constraints 98
NE access constraints 98
Summary of actions 99
Preliminary operations 99
Operations with NEtO 100
Details on NEtO screen 105
Supervision Function 105
Supervision and Alarm Synthesis roundshaped icons 105
NEtO screen minimize and restore 106
NEtO icon in the tray bar 106
NE Configuration 107
Command Buttons 108
How to close the NEtO session 108
NEs List Management 109
Main actions with NEtO On pages
perform the preliminary operations before to startup one NEtO session 99
startup one NEtO session 100
start the supervision of one NE, and choose (if necessary) the PCNE
connection (F or Ethernet or NMS connection)
102 to 104
start the WebEML application on the supervised NE
start the Alarm Monitor application on the supervised NE
close the NEtO session
108
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
98 / 232
18.1 General on NEtO
18.1.1 NEtO functions
NEtO (Network Element Overview) is the starting point for 9400AWY V2.0.6, V2.1.2 and V2.1.3 WebEML
application.
Following functions are allowed:
Starting of Supervision of a 9400AWY NE (status and alarms summary)
Starting of WebEML on a supervised 9400AWY NE
Starting of AM (Alarm Monitoring) on a supervised 9400AWY NE
Creation/Save/Retrieve/Modify of one (or more) list of favorite NEs
that are described in detail in the following.
NEtO application allows user to execute its functions through mnemonics keyboard shortcuts, as
described in detail in the following.
18.1.2 NEtO sessions and constraints
[1] NEtO session
NEtO works as a singlesession instance dedicated to one NE only.
It means that if you have one NEtO instance open for one NE (and you want to leave it open), you
must launch another NEtO instance to access another NE.
WARNING: Even if allowed by SW, opening more than one NEtO session (from the same PC)
on the same NE is a forbidden operation, and must be absolutely
avoided.
[2] Max number of contemporaneous NEtO sessions
The number of NEtO sessions, that can be run at the same time (from the same PC), depends on
the PC performance (processor type, RAM size, operating system type, etc.) and the possible
contemporaneous run of RAMeating and processorstressing programs).
As a general rule, the following figures can be considered reasonable:
max 5 NEtO sessions used for NE supervision only (i.e. without logging in the NE for the
WebEML and AM functions)
or max 2 NEtO sessions used for NE management by WebEML and AM
At any rate, the attempt to launch one more NEtO session, in addition to those already running, which
would override the available computer resources, is solved automatically simply ignoring it, without
any error message. Then, you must at first close one of the running NEtO sessions, to open another
one.
18.2 NE access constraints
The following limitations (relevant to the NE access, not to the NEtO session) must be taken into account:
a ) the contemporaneous presence on one NE of various managers (LCT, RCT and an OS) is possible,
from different Craft Terminals (WebEML, or 1320CT) or OS. The access disable flag avoids access
conflict between the OS and both RCT and LCT on some operations, like configuration modification
and remote control with access filtering.
b ) at most ten OS/LCT/RCT access instances can be active at a time over one NE :
one local LCT access instance only (on NEs Finterface)
plus nine remote RCT/OS instances at most (on NEs Management Ethernet interface, and on
Radio interface and NMS interface
The coexistence of OS, LCT and RCT access instances in the whole network is guaranteed, since
the conflict in accessing the NE is solved locally by the NE itself.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
99 / 232 3DB 75003 BAAA Ed.01
18.3 Summary of actions
18.3.1 Preliminary operations
a ) Make cable and network connections (if not yet done)
According to the chosen CTNE access type, make, or verify, the relevant physical connection (local
or remote) between the CT and the NE, as depicted in:
Fig. 1. on page 24 (physical interfaces for the 9400AWY NE management)
Fig. 2. on page 25 (access through NEs F Interface)
Fig. 3. on page 26 (access through NEs Ethernet Interface)
Fig. 4. on page 27 (access through NEs radio Interface and NMS rings and chains)
Warning about the NE connection to the TCP/IP network and to the NMS network
These connections must not be done until the network routing data of the NE have been
correctly defined. This definition is performed during the firsttime equipment startup and
commissioning (see point [1] on page 42 )
b ) Power on the PC and wait for its startup (if not yet done)
c ) Only in case of CTNE connection through the F interface
WARNING 1: for the use of the F interface, the LLMAN (Lower Layer MANager) installation and
configuration must have already be performed, as described in the Appendix C on
page 201
WARNING 2: to use the LLMAN, check/set the suitable PC desktop Properties System standby
and System hibernates, that must be both set to Never, as shown in Fig. 96. on
page 213
WARNING 3: to use the F interface, you must at first start manually the LLMAN. To do that, perform
operations described in para.23.8.2 from page 214
d ) Only in case of CTNE connection via public switched telephone network (through the F interface):
After having performed operations of previous step c ) , set up the connection on the public switched
telephone network, as described in para.24.6 on page 224
e ) Perform the checks listed in para.14.4 on page 48
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
100 / 232
18.3.2 Operations with NEtO
a ) Startup one NEtO session
WARNING 1: NEtO can be run only if the Local copy of WebEML (Jusm/CT) has already been
performed, as described in point 8 ) on page 188
WARNING 2: if not yet done, read carefully para.18.1.2 on page 98
WARNING 3: if the PCNE physical connection is made on the serial interface, be sure to have
started LLMAN [see point c ) on page 99 ]
The startup of one NEtO session can be done:
clicking the Shortcut to the Local copy of WebEML (see Fig. 80. on page 188 )
AWY_CT_V01_07
or clicking the button Operational & Maintenance WebEML of the Main Menu screen (see
Fig. 10. on page 47 )
The NEtO initial screen opens, allowing operations depicted in Fig. 39. :
start the supervision of one NE
[step c ) on page 102 ]
icons for NE list management (see para.18.5 on page 109 )
shrink glass (see para.18.4.3 on page 106 )
para.18.4.6
on page 108
if present,
ignore this field
insert the NE read
write Community
String of one
NE (if necessary)
[step b )
on page 101 ]
Fig. 39. NEtO initial screen
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
101 / 232 3DB 75003 BAAA Ed.01
b ) Insert the NE readwrite Community String (if necessary)
N.B. this operation is meaningful only:
for AWY 2.1.3 NEs
and only if the NE Administrator has defined a community string (different from the
default value) for the specific NE you want to login (details in para.13.3.3 on page
35 ). To proceed, you must know this string, and you must write it before to start the
Supervision of such NE.
To make this operation, click the button CS (Community String) on the open NEtO initial screen
(Fig. 39. on page 100 ). The following screen opens:
Insert the Community String, then click OK
(1)
(2)
N.B. the button Use Default resets the community string at the default value, at NEtO side
only.
Now, you can start the Supervision of such NE [ step c ) on page 102 ]
WARNING: in the case you want, in the following, access another NE in the same NEtO session,
you must be aware that this community string setting remains active at NEtO side
until you reset it by the button Use Default, or change it clicking again on button CS,
or when you close the NEtO session.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
102 / 232
c ) Start the Supervision of one NE
WARNING: in case of AWY 2.1.3 NE, for which the NE Administrator has defined a community
string (different from the default value) for the specific NE on which you want to start
the supervision, be sure to have performed the operation described in step b ) on
page 101
From the open NEtO initial screen ( Fig. 39. on page 100 ), to start the Supervision of one NE,
operate as depicted in Fig. 40. below (for details refer to para.18.4.1 on page 105 ).
(2) click
(1) insert the
NE address
(read WARNING below)
(3) step d ) on page 103 ,
or step e ) on page 104 ,
or error message,
depending on NE reachability
para.18.4.6
on page 108
WARNING: if the local IP address and Ethernet Configuration IP address are different, you
must specify the local IP address : for details, refer to to para.13.2.2 on page 28
Fig. 40. Start Supervision for one NE in NEtO initial screen
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
103 / 232 3DB 75003 BAAA Ed.01
d ) Choice (if necessary) of the network adapter for PCNE connection
If more than one network adapter is found in the PC, the following screen appears (an example),
where user must select the one to use and then click OK.
In the case of PCNE connection by F interface, and provided that LLMAN has been manually
started [see point c ) on page 99 ], you must select the Virtual Network Card that has been
associated to the PC serial interface
N.B. You can know this association by means of the Lower Layers Settings screen (see
para.23.6 on page 210 )
If the connection is correctly established, the NEtO screen changes as in Fig. 41. (NE
supervised).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
104 / 232
e ) Operations possible for a supervised NE
For a supervised NE, operations depicted in Fig. 41. are possible:
[A] [B]
[C]
[A] get information regarding the NE Supervision and Alarm Synthesis states
Details in para.18.4.2 on page 105
[B] get/change data regarding the NE Information and/or the NE Description; or move to the
supervision of another NE (closing the current NE supervision)
[C] start WebEML and/or Alarm Monitor, or exit from NEtO
Fig. 41. Operations possible for a supervised NE
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
105 / 232 3DB 75003 BAAA Ed.01
18.4 Details on NEtO screen
18.4.1 Supervision Function
The supervision function allows operator registering himself/herself as a new manager inside NE MIB and
performing cyclic (periodic) monitoring on connection. To start supervision, operator must specify NE IP
address in the IP Address field, and then simply press OK button (see Fig. 40. on page 102 ).
If supervision succeeds, screen is updated with information retrieved from NE and supervision icon
changes its color from gray to green, stating NE is correctly supervised, as described in para.18.4.2
below.
When a supervision error, a link down or other problems arise during supervision, icon will become red.
Alarm Synthesis area will be updated as well.
To end an ongoing supervision, simply click on Exit button (this will also close NEtO) or change NE IP
address and click OK button to start supervision procedure on a different NE (this will stop previous
supervision).
18.4.2 Supervision and Alarm Synthesis roundshaped icons
Information on supervision status and active alarms are shown in this area ( Fig. 42. ).
Fig. 42. Supervision and Alarm Synthesis roundshaped icons
Roundshaped icons change their colors according to current NEtO functions and situation:
as far as the Supervision icon is concerned:
gray color means that supervision is not active (to be started)
green color means that supervision function is ongoing
red color means that NE link does not work
the Alarm Synthesis area is enabled only if the supervision is active (Supervision icon green).
It contains the possible alarm severities, accompanied by the number of alarms affecting the specific
type. Alarms and supervision state colors for icons are the same and default for all AlcatelLucent
devices):
green color means that no alarms are present
red color is always assigned to the icon of Critical alarms (if any)
orange color is always assigned to the icon of Major alarms (if any)
yellow color is always assigned to the icon of Minor alarms (if any)
cyan color is always assigned to the icon of Warning alarms (if any)
white color is always assigned to the icon of Indeterminate alarms (if any)
More details on the active alarms can be obtained in the Alarm Monitoring screen, that can be opened
by the suitable command button (see para.18.4.6 on page 108 ).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
106 / 232
18.4.3 NEtO screen minimize and restore
NEtO screen can be minimized using the shrink glass button in the Menu Bar.
Fig. 43. shows the reduced NEtO view, allowing the user to save screen space while continuously
checking supervision and alarms status.
The magnifying glass button allows showing normal NEtO screen.
magnifying glass
Fig. 43. NEtO screen: reduced screen
18.4.4 NEtO icon in the tray bar
Alarm severity icon shown in Fig. 43. will appear in operating system tray bar (see Fig. 44. ), close to
system clock and other system software icons.
Fig. 44. Alarm severity icon in system traybar
This icon will also have a specific tooltip, visible when mouse cursor is moved over it, that will show: name
of application, NE IP address, and highest severity alarms number.
Traybar icon is not interactive and does not present any menu or executable command if clicked either
with left or right mouse button.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
107 / 232 3DB 75003 BAAA Ed.01
18.4.5 NE Configuration
The panel is made by these areas:
NE Info section, containing information related to NE addressing;
NE Description section, with information about NE characteristics;
[1] Network Element Information
This area is related to wanted NE identification ( Fig. 45. ).
Fig. 45. NEtO NE Configuration View: NE Information
IP Address parameter displays the actual NE IP address used by NEtO functions. SNMP port is the
default standard number 161, so not shown.
This box shows only IP address information, while status information is provided by the second area
of NEtO window. OK button will start supervision on specified NE, if reachable.
Keyboard shortcut Alt + o behaves as clicking on OK button with mouse.
Whenever a stop supervision is needed, user can both click on Exit button (see Fig. 47. ), so
stopping supervision and closing NEtO, or by simply changing NE IP Address, writing a new one,
and then clicking on OK. This step will stop existing supervision starting supervision on the newly
specified NE.
WARNING: whenever you have written, in step b ) on page 101 , a community string, you must
be aware that this setting remains active at NEtO side until you reset it by the button
Use Default, or change it clicking again on button CS, or when you close the NEtO
session.
Whether IP address is correctly written, other than clicking on OK button, supervision process will
start on specified NE by pressing enter (carriage return) key on keyboard.
[2] Network Element Description
This area contains some parameters displaying general information about supervised NE ( Fig. 46. ).
Fig. 46. NEtO NE Configuration View: NE Description
a ) The readonly field Type ULS means always 9400AWY NE. The readonly field Version
shows the Flash Cards SW COMMIT VERSION presently running on the NE: see point [2]
on page 40
b ) The parameters Site Name and Site Location can be read and modified (and applied to NE
using the Apply button). Please note that changing these labels values will also automatically
update NEtO window title content: window title will always contain Site Name of supervised
NE.
WARNING: Site Name and Site Location name cannot contain special characters, such
as <, >, &, and
Keyboard shortcut Alt + a behaves the same as clicking on Apply button with mouse.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
108 / 232
18.4.6 Command Buttons
Fig. 47. shows the command buttons available on NEtO screen:
Fig. 47. NEtO NE Configuration View: Command Buttons
Show and Alarm Monitor buttons are enabled only when a NE is supervised:
the Show button starts the WebEML application on the supervised NE.
WARNING: the Show button is greyed (i.e. not selectable) in the case the WebEML
application has already been started.
Notice that, besides from this NEtO screen, the WebEML application can be
launched also through the Navigate from AM to USM function (see
para.110.2.9 on page 147 )
Keyboard shortcut Alt + S behaves as clicking on Show button with mouse.
For details on WebEML, refer to Chapter 19 on page 111
the Alarm Monitor button starts AM application on the supervised NE.
WARNING: the Alarm Monitor button is greyed (i.e. not selectable) in the case the AM
application has already been started on the specific NE.
Notice that, besides from this NEtO screen, the AM application can be launched
also by the WebEML application:
through the command Diagnosis % Alarms % NE Alarms
or through the Navigate from USM to AM function (see para.110.2.10
on page 148 )
Keyboard shortcut Alt + m behaves as clicking on Alarm Monitor button with mouse.
For details on AM, refer to Chapter 110 on page 135
Exit button is always enabled.
The Exit button only ends the NE supervision (if active), and closes the NEtO application.
WARNING: the Exit button does not close other related applications. Therefore, to close one
NEtO session, operate as described in para.18.4.7 below
Keyboard shortcut Alt + E behaves as clicking on Exit button with mouse.
18.4.7 How to close the NEtO session
a ) If open, close the NE JUSM window ( Fig. 49. on page 114 ) clicking
b ) if open, close the Alarms Monitor window ( Fig. 52. on page 138 ) clicking
c ) only when both buttons Show and Alarm Monitor have become black (i.e. selectable), you can
click on Exit button. This ends the NE supervision (if active), and closes the NEtO windows and
application.
N.B. if you try to Exit the NEtO application while the NE JUSM window and/or the Alarms Monitor
window is/are still open, the NEtO screen goes to a permanent hung state, even if, after, you
will close them (in this case, you must close NEtO by Task Manager, or restarting the PC).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
109 / 232 3DB 75003 BAAA Ed.01
18.5 NE list management
NEW (creates a new
list of favorite NEs)
OPEN (loads a file containing
a list of favorite NEs)
OPEN (opens the current
list of favorite NEs)
NEtO can manage and organize one (or more) list(s) of available NEs by showing user a table containing
such data. Using both (New) and (Open) icons, user will be able to open NEs table modal window
(see Fig. 48. ).
Fig. 48. NEtO List Management
While Open icon allows opening a previously saved file containing a list of NEs, New icon allows
creating a new list, specifying file name containing its data only when those data will be saved. Window
allows user managing its NEs data by:
Get Current button is used to read information from main NEtO view. This operation always adds
a new line in NE list table with all information related to currently supervised NE. This happens even
though a NE with corresponding IP address is still present in the list;
New button, adding a new NE from scratch. This allows user to fill the IP Address field only with
its needed NE.
Remove button, removing a selected NE;
Set Current button, filling main NEtO view IP address with datum from selected NE. User must
previously select a valid line in NEs table and then click on Set Current button so filling NEtO main
window data. This operation will automatically close the NE list window but does not start supervision
on set NE;
Save button, saving table list in a specified file.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
110 / 232
All data are saved in a custom XML format called NEtO and this structured file will contain all data shown
in Fig. 48. related to all NEs added to the list. This XMLbased file is further customized so helping user
easily identifying this kind of files within a huge set of files: instead of using the common .xml file
extension, a specific .NEtO file extension is used, both in file names and in filtering files while
opening/saving.
User can have its own NEs lists repository, containing all .NEtO files that it produced with NEs information
inside. Closing this window is as simple as clicking on Close button. User can see data related to NEs
as shown in Fig. 48.
As for NEtO main window, even NE list window allows using keyboard and hotkeys to perform operations.
Through:
Keyboard shortcut Alt + g behaves as clicking on Get Current button with mouse;
Keyboard shortcut Alt + s behaves as clicking on Set Current button with mouse;
Keyboard shortcut Alt + n behaves as clicking on New button with mouse;
Keyboard shortcut Alt + r behaves as clicking on Remove button with mouse;
Keyboard shortcut Alt + v behaves as clicking on Save button with mouse;
Keyboard shortcut Alt + c behaves as clicking on Close button with mouse.
N.B. Since NEtO list files are XMLbased, they contain simple text characters with specific tags to
identify information. This allows user/operator to possibly modify files by itself, whenever
needed. Anyway, list files not strictly fulfilling XML NEtO grammars and structure cannot be
considered correct and used by NEtO list management. Such manual modification is strongly
discouraged.
Suggested usage sequence for NEtO interface and NE list is:
1 ) Fill NEtO main view IP Address field with NE IP address;
2 ) Start supervision by clicking Ok button;
3 ) Open the NEs table (any method, through New or Open button);
4 ) Click on Get Current;
5 ) Save the list and close the list window.
This will produce a clean and uptodate NEs table list. NE table lists wont never be updated if user will
modify, say, NE site name, site location or even IP address. Such data are used for references purposes
but user must take care to keep them updated.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
111 / 232 3DB 75003 BAAA Ed.01
19 9400AWY WEBEML
This chapter describes in detail the organization and the functions of the WebEML (Craft Terminal):
Subject On page
How to open the 9400AWY NE WebEML main view 113
9400AWY view organization 114
View Area 115
Resource Tree Area and Selection Criteria 116
Resource Detail Area 116
Main tool bar 117
Severity alarm synthesis, and Domain alarm synthesis 118
Management state control panel 119
Access state (allow or inhibit NE Craft Terminal access) 120
Switching from the OS to the Craft Terminal access state 120
Switching from the Craft Terminal access state back to the OS access state 120
Introduction to the WebEML menu commands 121
Security by operator profile 121
Menu organization 124
Command button policy 124
Help menu 125
Views menu 126
Configuration menu 130
Diagnosis menu 131
Supervision menu 132
SW download menu 133
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
112 / 232
Comparison with the 1320CT of the:
9400AWY R.2.0 V2.0.6 CDROM,
The WebEML functions are embedded in NEtO, and replace the equivalent functionalities embedded
in 1320CT.
The Quick Configuration icon is no longer present in the Main tool bar
The Quick Configuration command is no longer present in the Configuration menu.
Therefore, the Quick Configuration procedure must be launched by the Provisioning tool , described
in chapter 15 on page 59
The Alignment icon is no longer present in the Management state control panel
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
113 / 232 3DB 75003 BAAA Ed.01
19.1 How to open the 9400AWY NE WebEML main view
The 9400AWY main view screen (example in Fig. 49. on page 114 ) can be opened for a NE supervised
by NEtO in one of the following ways:
clicking the Show button in its NEtO screen (see para.18.4.6 on page 108 )
or, with its AM (Alarm Monitor) screen already open, through the Navigate from AM to USM function
(see para.110.2.9 on page 147 ).
The login screen opens, where user is asked to provide his/her UserName and Password (for details, see
point [1] on page 34 ):
After having filled the fields UserName and Password, followed by the Apply button clicking, if login
successful:
loading of JUSM is performed, with all data regarding the NE configuration and those related to the
security customization described in para.13.3 on page 33 :
and the 9400AWY main view screen appears (example in Fig. 49. on page 114 ).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
114 / 232
19.2 9400AWY main view organization
The 9400AWY main view (Fig. 49. below is an example for 9400AWY R.2.1 in 1+1 configuration) is
opened as described in previous para.19.1 on page 113 , and contains the following fields, which provide
the operator with the information needed to manage the NE:
Area Meaning
View title according to screen
View area see para.19.3 on page 115
Main tool bar see para.19.4 on page 117
Severity alarm synthesis, and Domain alarm synthesis see para.19.5 on page 118
Management state control panel see para.19.6 on page 119
Menu bar see para.19.8 on page 121
The Menu bar , Main Tool bar and the View area contained in the same NE view permit to perform all
configuration and supervision operations and the display of the specific selected item.
Domain alarm synthesis
Management state control panel
View
area
RESOURCE
TREE AREA
RESOURCE LIST AREA
RESOURCE DETAIL AREA
Severity alarm synthesis
Menu bar
View title
Main tool bar
Tab panel
Fig. 49. 9400AWY Main view organization (example)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
115 / 232 3DB 75003 BAAA Ed.01
19.3 View Area
RESOURCE
TREE AREA
RESOURCE LIST AREA
RESOURCE DETAIL AREA
The View Area manages all domains from which the user can start. It is organized into tabbed panel, e.g.
many windows placed one upon another. Each window is selectable (placing it on top of the others) with
a tab shown on the top.
Each panel represents a set of functions. The area consist of the following sets:
Equipment
External Points
Line Interface
Performance
Radio
Protection Schemes (in 1+1 configuration only)
Loopback
Each tab panel is labeled with the set name ( e.g. Equipment, Line Interface, etc ).
Each tabpanel (e.g. functionalities area) consists of four areas:
ResourceTree Area: displays all the available resources of the Radio NE.
ResourceList Area: may be represented by: Tabular View (e.g., Line Interface Domain) or
Graphical View (e.g., Equipment Domain).
Tabular View: displays a tabular representation of the selected resource. As default, no tabular
element is shown.
Graphical View: displays a graphical representation of the selected resource. As default, no
tabular element is shown.
ResourceDetail Area: displays detailed information of a selected item in the Resource List area.
As a default, no entry view is displayed as a consequence of the default behavior of the Resource
List area.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
116 / 232
19.3.1 Resource Tree Area and Selection Criteria
The Resource Area displays all the available resources in a tree structure like the protocol stack
hierarchy.
Each tree node consists of two symbols. The first symbol indicates the state of the structure e.g., if the
symbol is + the tree can be expanded to a lower level. The tree structure can be collapsed if the symbol
is . Finally, if there is no symbol, the node represents a leaf. The second symbol is the graphical
representation of the resource.
The user must select the resource by clicking with the mouse to carry out an action that depends on the
type of click.
Each resource listed above may be selected by using the mouse by a single or double left click:
Single left click:
By a single left click the resource is highlighted. This selection causes the activation of the
resource list area, e.g., every time the user selects a resource in the resource tree area the
corresponding Tabular or Graphical representation is displayed in the Resource list area .
Double left click:
Using this type of selection on the items of the resource tree, the user can expand the tree
structure and activate the Resource list area displaying the same information described
above. When the tree node is expanded a double click will collapse the tree node showing the
same information in the Resource list area.
19.3.2 Resource Detail Area
This area displays the detailed information of the selected object in the Resource list area. It also provides
the types of operations available
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
117 / 232 3DB 75003 BAAA Ed.01
19.4 Main tool bar
Besides navigation buttons, it contains some shortcut icons for specific views (they are accessible also
through the Menu Bar).
previous
screen
not
operative
next
screen
Current Configuration view
Summary Block Diagram view
navigation buttons
VLAN configuration
Ethernet Port PM configuration
Fig. 50. Main tool bar
N.B. previous screen and next screen buttons are enabled according to the context.
Shortcuts available are:
for AWY 2.0.6, 2.1.2 and 2.1.3:
Summary Block Diagram view: shortcut to menu command:
Diagnosis % Summary Block Diagram View
Current Configuration view: shortcut to menu command:
Diagnosis % Current Configuration view
for AWY 2.1.3 only, and only with Enhanced Data plugin configured:
VLAN configuration: shortcut to menu command:
Configuration % Network configuration % VLAN configuration
Ethernet Port PM configuration: shortcut to menu command:
Diagnosis % Ethernet Port Counters Monitoring
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
118 / 232
19.5 Severity alarm synthesis, and Domain alarm synthesis
These areas contain the list of alarms listed by severity, and accompanied by the number of alarms
affecting the specific type:
CRI Critical alarm
Synthesis of alarms that needs immediate
troubleshooting (typical: NE isolation)
MAJ Major (Urgent) alarm
MAJ Major (Urgent) alarm
troubleshooting
MIN Minor (Not urgent) alarm
Synthesis of alarms for which a deferred intervention
can be decided
WNG Warning alarm
Synthesis of alarms due to failure of other NE in the
network
IND Indeterminate alarm
Synthesis of alarms not associated with the previous
severities. Not operative.
EXT
External Point
(Housekeeping alarm)
Synthesis of the relevant station alarm incoming as
input housekeeping signals
EQP Equipment alarm Synthesis of alarms of the Equipment domain
TRS Transmission alarm Synthesis of alarms of the Transmission domain
For detailed information and related maintenance procedures, refer to the specific NE User Manual
(Tab. 1. on page 14 ), more precisely:
chapter Second Level Maintenance
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
119 / 232 3DB 75003 BAAA Ed.01
19.6 Management state control panel
LAC (Local Access Control)
(N.B.)
GREEN LED: Indicates that the Craft Terminal
has the OS permission to manage the NE
(granted).
CYAN LED: Indicates that the Craft Terminal has
not the OS permission to manage the NE (denied).
NE reachable / unreachable
GREEN LED: Identifies the Enable operational
state of the connection between NE and Craft
Terminal ( SDH service link up ).
RED LED: Identified the Disable operational
state of the connection between NE and Craft
Terminal ( service link down ).
Supervision state
GREEN LED: NE is under supervision.
BROWN LED: NE is not under supervision. Used
in the OS.
Operation System
(N.B.)
GREEN LED: Indicates that the NE is not
managed by the 1353NM/SH.
RED LED: Indicates that the NE is managed by the
1353NM/SH.
Network Time Protocol
GREEN LED: NTP protocol enabled and both NTP
servers ( Main and Spare ) are unreachable.
BROWN LED: NTP protocol disabled.
CYAN LED: NTP protocol enabled and at least one
NTP servers ( Main or Spare ) are reachable.
Abnormal Condition
GREEN LED: Normal operating condition.
CYAN LED: Detection of an ABNORMAL
operative condition. E.g. protection switch forcing.
N.B. The NE can be managed by the OS or by the Craft Terminal.
To control the competition of the OS and the CT, a Local Access Control (LAC) is available, as
described in following para.19.7
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
120 / 232
19.7 Access state (allow or inhibit NE Craft Terminal access)
The NE can be managed by the OS or by the Craft Terminal. To control the competition of the OS and the
CT, a Local Access Control (LAC) is available:
if the LAC is access denied, it means that the OS manages the NE, and the CT is not allowed to
modify the NE configuration (it can only read). In the view, the icon with a key symbol has a circular
shape.
if the LAC is granted, it means that the CT is allowed to manage the NE. In the view, the icon with
a key symbol has a rectangular shape.
if the LAC is requested, it means that the CT has requested a permission from the OS and is waiting
for a reply.
However, the OS does continue to provide a certain number of services. These services include:
Alarm reception and processing,
Performance processing,
Switching back to the OS access state.
The access state of an NE can be modified in two ways:
switching from the OS to the Craft Terminal access state
switching from the Craft Terminal access state back to the OS access state
19.7.1 Switching from the OS to the Craft Terminal access state
By WebEML, perform Supervision Access State Requested ( see para. 19.8.8 on page 132 ).
From the confirmation dialogue box that opens, you can confirm or cancel the Craft access operation using
the Yes or No pushbutton. The request is sent up to the OS which accepts or refuses it.
If the OS doesnt answer in a predefined time, it is assumed that the NE is in the Craft access state and
can be managed by a Craft Terminal.
19.7.2 Switching from the Craft Terminal access state back to the OS access state
By WebEML, perform Supervision Access State OS ( see para. 19.8.8 on page 132 ).
From the confirmation dialogue box that opens, you can confirm or cancel the OS access operation.
The NE is now managed by the OS.
N.B. The key symbol icon on the management states of the NE view ( para.19.6 on page 119 )
indicates whether the NE is managed by a craft terminal or by the OS.
N.B. Local Craft Terminal access is denied on recovery phase after a loss of communication of the
NE. When the communication with the NE is lost, the OS automatically recovers the
communication and forces the state existing before the loss of communication (therefore, Craft
Terminal access can be denied or granted).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
121 / 232 3DB 75003 BAAA Ed.01
19.8 Introduction to the WebEML menu commands
N.B. The conversion of the WebEML menus, which are natively in English, in other languages is
possible, on contact basis (this process is called localization). The following languages are
supported: Spanish, Italian, German, French. Localization is not done in the standard CT
product, but is in charge of AlcatelLucent local units. Please refer to them for additional
information.
19.8.1 Security by operator profile
The security by operator profile has been introduced in para.13.3.2 on page 34
The commands present in the menu bar can be enabled (with black text) or disabled (with greyed text),
as depicted in following example:
commands disabled (greyed text)
command enabled (black text)
all commands enabled (black text)
In fact, the operations allowed by the WebEML depend on the combination of the following security
parameters:
the type of command to be forwarded
the login profile associated to the UserName and Password employed: Administrator, or Constructor,
or Operator, or CraftPerson, or Viewer, described in point [2] on page 34
the CT physical access characterization: LCT (Local Craft Terminal) or RCT (Remote Craft Terminal).
The LCT or RCT characterization for the WebEML is depicted in tables on pages 25 to 27
In few words: only the CT connected to NEs Finterface has the functionalities of LCT, for that NE
only, but not for other NEs that can be reached through it
and the current LAC status, granted or denied: see para.19.6 on page 119
N.B. In few words, all commands are enabled only when:
the physical access is by LCT,
the login profile associated to the used UserName and Password is Administrator,
the current LAC status is granted
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
122 / 232
To know the security parameters defined above, perform following operations:
1 ) In the menu bar, perform Help % Tutorial (see para.19.8.4 on page 125 )
In the help screen that opens, click NE Management , then scroll the help page until you find MENU
CONFIGURATION, then click on Profile Management:
2 ) then, click on Appendix: Craft Terminal Access Control :
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
123 / 232 3DB 75003 BAAA Ed.01
3 ) the relevant description screen opens as in example below, where the security parameters are
described by 5 tables, one for each of the login profiles (Administrator, Constructor, Operator,
CraftPerson, and Viewer):
4 ) The profile management is performed through the CT commands Supervision % Profiles
management (see para.19.8.8 on page 132 )
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
124 / 232
19.8.2 Menu organization
The menu bar allows to perform configuration and supervision functions on the Network Element.
This paragraph lists all menu options and then provides more details on the respective contained entries.
For each of them the relevant operative function are briefly introduced and it is referred the paragraphs
where they are detailed or the introduction to the options of each menu inserted in next paragraphs of this
chapter.
In the menu bar, a number of permanent menu items are always displayed. Starting from the left, the
menus are:
Permanent Menus
Views (first column). See para.19.8.5 on page 126
To navigate among the views and to set the TMN parameters.
Configuration (second column). See para.19.8.6 on page 130
To set the general configuration of the NE and to show or modify some parameters
(performance monitoring, OverHead parameters).
Diagnosis (third column). See para.19.8.7 on page 131
To get information on the NE (alarms, performance monitoring, remote inventory).
Supervision (fourth column). See para.19.8.8 on page 132
To set the supervision states of the NE, to restart the NE, to manage its MIB, and to show
information regarding the equipped Flash Card.
SW Download (fifth column). See para. 19.8.9 on page 133
To manage the NE software (download, MIB management).
Help (last column). See para. 19.8.4 on page 125
To activate the help on line.
The menu bar also comprises other menus, presented only when a specific option is selected.
Other Menus
Equipment
This menu is present only when the Equipment menu (selected in the View menu or in the
Equipment tab panel) is active. It allows to go back to the supporting equipment of the displayed
object.
19.8.3 Command button policy
In all command windows, the possible buttons for commands are the following:
Apply this button activates the modify, but it does not close the window.
Cancel this button closes the window without modifying the parameters displayed in the window.
OK this button activates the modify and closes the window
Close this button closes the window
Help this button provides the help management for the functions of the supporting window.
Critical configuration choices generate a warning message for user confirmation before to be activated.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
125 / 232 3DB 75003 BAAA Ed.01
19.8.4 Help menu
This menu presents the following entries:
On Help: this menu entry will show the complete online help available
On Context: selecting this entry will present a context help with respect to selected window area
Glossary: this command will show a list of acronyms and abbreviations that can be useful to explain
used terms
Tutorial: the Tutorial menu entry shows a user guide for the JUSM application. This one, and all
the entries above, is shown ad HTML pages in the default Internet browser.
About: selecting About item, a window will be displayed with the release information of JUSM
application and its components, as in following example:
An example showing the use of the Tutorial menu is given on pages 122 to 123
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
126 / 232
19.8.5 Views menu
The menu on the left side of the screen, allows to navigate among the views, to set some parameters, and
to perform tests, 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.
See point [1] on page 127
External Points: Displays and sets the input/output environmental alarm.
Line Interface: Opens the Line Interface view to configure all the tributary ports.
Performance: Allows to manage the Performance monitoring.
Radio: Allows to manage all the functions relevant to the radio channels.
Protection Schemes: Allows to manage the Protection schemes in 1+1 configuration.
Loopback: Allows to manage the loopbacks available with the equipment.
N.B. It is possible to enter directly any menu Equipment, External Points, Line Interface,
Performance, Radio, Protection Schemes, or Loopback, clicking the view area on the relevant
tab panel.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
127 / 232 3DB 75003 BAAA Ed.01
[1] Equipment view
The Equipment view deals with the management of the NE as a whole, as well as for its physical
components (subrack, boards,..). Its first screen (example) is as in Fig. 49. on page 114
For usage description, please refer to the Help online (see para.19.8.4 on page 125 )
To get SWPspecific hardware or software related information you may not find in the help online,
you can make also reference to the specific NE User Manual (Tab. 1. on page 14 ), more precisely:
chapter Equipment
Note for AWY 2.0.6 and 2.1.2: the navigation in this view is exactly as that present in the 1320CT,
described in the relevant NE User Manual
[2] External Point
The External Point view (an example shown below) allows to manage the input and output external
points (housekeeping).
chapter External Points
[3] Line Interface
The Line Interface view (an example shown below) deals with the management of the aggregate
frame and tributary ports (line side).
The Line Interface menu allows the user to manage the resources of the line interfaces: PDH
tributary, NMS channel and Ethernet port, if has been configured.
chapter Line Interface
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
128 / 232
[4] Performance
The Performance view (an example shown below) allows to manage the functions to provide
Performance Monitoring functions.
chapter Performance Monitoring
[5] Radio
The Radio domain view (an example shown below) allows the user to manage the resources of the
radio transmission channel(s).
chapter Radio
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
129 / 232 3DB 75003 BAAA Ed.01
[6] Protection Schemes
The Protection Schemes view (an example shown below) is present in 1+1 configurations only, and
allows user to operate on switches and parameters associated to the protection schemes employed
in the system.
chapter Protection Schemes
[7] Loopback
The Loopback view (an example shown below) allows user to to perform the test operations by
loopbacks.
chapter Loopbacks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
130 / 232
19.8.6 Configuration menu
This menu allows to set the general configuration of the NE and to show or modify some parameters, by
means of the following entries and subentries:
NE Time: Displays and sets the NE local time (*)
Network configuration: Allows to manage the NE network configuration (*)
N.B. the submenu Vlan Configuration is available only in the following conditions:
AWY 2.1.3 only
with Enhanced Data plugin configured
Alarm Severities: Manages the Alarm Severity Assignment Profile (*)
System setting: Allows the system configuration, providing the setting of all the parameters
for the NE setup (*)
Profiles management: Allows the CT user profile management
See para.113.1 on page 175
Log Switch: Inhibits/allows the event and alarm store in the Log
See para.110.1 on page 136
(*) For usage description, please refer to the Help online (see para.19.8.4 on page 125 )
chapter Configuration
Note for AWY 2.0.6 and 2.1.2: the behavior of these functions is exactly as that present in the 1320CT,
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
131 / 232 3DB 75003 BAAA Ed.01
19.8.7 Diagnosis menu
This menu allows to get diagnostic information regarding the NE, by means of the following entries and
subentries:
Alarms % NE Alarms: Starts the Alarm Monitor (AM) application
See para. 110.2 from page 136
Log Browsing % Event Log: Manages the events stored in the NE
See para. 110.3 from page 151
Log Browsing % Software Trace Log
N.B. The use of the Software Trace Log option is reserved to the
AlcatelLucent technicians for SW debugging purposes (*)
Remote inventory: Displays the equipment Remote inventory information (*)
Abnormal condition list: Displays the manual operations active in the NE (*)
Summary Block Diagram View:
Displays a global logical view (strictly related to the physical
implementation) highlighting a synthesis of all the alarms and
statuses present in the system (ODU+IDU) (*)
Current configuration View: Displays the current configuration of the NE (*)
Ethernet Port Counters Monitoring:
Sets and reads the Performance Monitoring on Ethernet Ports (*)
N.B. the menu Ethernet Port Counters Monitoring is available only in the following
conditions:
AWY 2.1.3 only
with Enhanced Data plugin configured
chapter Diagnosis
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
132 / 232
19.8.8 Supervision menu
This menu allows to set the supervision states of the NE, to restart the NE, to manage its MIB, and to show
information regarding the equipped Flash Card, by means of the following entries and subentries:
Access State: Manages the supervision access to the NE, via CT or OS
See para. 19.7 on page 120
Restart NE: See point [8] on page 46
MIB Management: Allows to perform backup and restore operations of the NEs MIB.
See chapter 111 on page 155
SW key: Displays the type of Flash Card equipped in the system and the licence
information (see point [1] on page 39 )
chapter Supervision
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
133 / 232 3DB 75003 BAAA Ed.01
19.8.9 SW download menu
This menu allows to manage the NE software instances (committed and standby) present in the NEs
Flash Card memory banks, by means of the following entries:
Server Access Configuration: Manages the configuration of the FTP server to be used for the
software download to the NEs Flash Card (*)
Init SW download: Manages the software download to the NEs Flash Card (*)
SW status: Shows and manages the status of the software packages installed
in the NEs Flash Card (*)
(*) For usage description, please refer:
to the Help online (see para.19.8.4 on page 125 )
and/or to chapter 112 from page 161
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
134 / 232
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
135 / 232 3DB 75003 BAAA Ed.01
110 ALARMS MONITOR AND EVENT LOG BROWSER
This chapter describes in detail the functions of Alarms Monitor and Event Log Browser embedded in NEtO
application.
9400AWY R.2.0 V2.0.6 CDROM,
The Alarms Monitor (AM) and Event Log Browser (ELB) functions are embedded in NEtO, and
replaces the functionalities of both the AM and ELB applications embedded in 1320CT.
Subject On page
Log switch 136
Alarms Monitor 136
Alarms Monitor functions 136
Alarms Monitor startup for one single NE 137
Alarms Monitor Overview 137
Multiple NE Alarms Monitor 141
Filters menu 142
File menu 145
Printing the alarms and logs 145
Exporting the alarms and logs 146
Navigate from AM to USM 147
Navigate from USM to AM 148
Shortcut icons 149
Event Log Browser (ELB) 151
ELB scope 151
ELB startup 151
Event Log Table screen 152
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
136 / 232
110.1 Log switch
By default, the recording of:
events in the Event Log is enabled; their browsing is obtained by the ELB application, described
in para.110.3 from page 151
the alarm events in the Alarm Log of AM is enabled; their browsing is obtained by the AM
application, described in para.110.2 from page 136
The Log Switch screen (Fig. 51. below) can be opened in the NE WebEML application, through the
command Configuration % Log Switch.
By this screen, it is possible to verify, and inhibit (Lock) or allow (Unlock), the store of the events and
alarms respectively in the Event Log and Alarm Log (for the specific NE).
Fig. 51. Log Switch screen
110.2 Alarms Monitor
110.2.1 Alarms Monitor functions
Alarms Monitor (AM) is the application from which the operator can have a global view of the current alarm
and also the alarm log for one or more 9400AWY NEs, within the limits (i.e. the max number of NEtO
instances) specified in point [2] on page 98
AM application requires a supervision manager (NEtO instance) opened for each Network Element
monitored.
The user can:
view the alarms currently present on one or more Network Element(s) in real time
view the historical alarms data (raise/clear log)
view the alarms (both current and historical) filtered by one or more properties.
navigate from an alarm in AM to the specific interface in JUSM, and viceversa from an alarm
selected in JUSM to the specific row in AM, to facilitate troubleshooting
print and export data to external file.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
137 / 232 3DB 75003 BAAA Ed.01
110.2.2 Alarms Monitor startup for one single NE
The AM application can be launched for a supervised 9400AWY NE in the following ways:
clicking the Alarms Monitor button in its NEtO screen (see para.18.4.6 on page 108 )
or by its WebEML application:
through the command: Diagnosis % Alarms % NE Alarms
or through the Navigate from USM to AM function (see para.110.2.10 on page 148 )
These ways are mutually exclusive (one AM instance only can be active at a time over one NE for one
PC).
The AM screen opens (see Fig. 52. on page 138 ).
110.2.3 Alarms Monitor Overview
After its launch, the AM screen opens: see Fig. 52. on page 138 , and also the Shortcut icons in
para.110.2.11 on page 149 , that, for simplicity, are not shown in following figures).
a ) At the top right, the field Synthesis shows the number of active alarms for any severity, with the same
meaning of Fig. 42. on page 105
b ) On the left side of the application, below each NE, two global lists of alarms are displayed:
CURRENT_ALARM shows all the equipment alarms currently present,
ALARM_LOG shows all the equipment alarms currently present and the history of the alarms
(i.e. cleared alarms).
N.B. when an alarm is no longer active, it disappears from the CURRENT_ALARM list, and is
displayed in the ALARM_LOG list as a cleared alarm.
Each global list has some default filters (some filters for the CURRENT_ALARM list, and other filters
for the ALARM_LOG list), as follows:
CRI contains all the alarms having a CRITICAL severity
MAJ contains all the alarms having a MAJOR severity
MIN contains all the alarms having a MINOR severity
WRG contains all the alarms having a WARNING severity
IND contains all the alarms having an INDETERMINATE severity
CLR contains all the alarms which are in the CLEARED state, that is, which are no longer active
(this filter is available within the list ALARM_LOG only).
For each list and for each filter, the number of active alarms is shown inside brackets.
These two lists can be filtered using customized filters provided by means of the menu Filters %
Add a Filter .. (see para.110.2.5 from page 142 ).
Single clicking on a filter or on a global list on the left part of the screen shows up on the right side
the relevant tab panel with all the alarms [see point c ) below]
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
138 / 232
c ) On the right, the view of the alarms is displayed:
a Tab in the internal window for each filter that the user want to see. By default Current alarms
and Alarm Log tabs are always visible
for each view, the alarms are shown in a Table.
N.B. when the application is opened for the first time, only two tabbed panes are displayed;
demonstrate respectively the global active alarms (see Fig. 52. ) and the alarm log (see
Fig. 53. ).
Severity alarm synthesis, as in Fig. 42. on page 105
Fig. 52. Alarms Monitor Severity alarm synthesis and Current Alarms
Fig. 53. Alarms Monitor Alarm Log
WARNING:
The Alarm Log Table is updated only if the corresponding Log Switch is unlocked (see
The Alarm Log Table:
on the NE MIB, has a limited size (about 700 rows, depending on the space available in
the Flash Card). When the maximum size is reached, the first element is cleared and the
new one is overwritten on it;
on the AM application, can display a number of rows much higher (anyway limited to max
5000, to avoid system overload), because they are stored in the PC environment.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
139 / 232 3DB 75003 BAAA Ed.01
From the category tree in the left, the operator can also view the alarms or logs with specific severity. E.g.
Fig. 54. shows only the major alarms.
Fig. 54. Alarms Monitor Shows only the major alarms
For each alarm row, these fields are shown:
Time & Date: date and time of the alarm raise or clear.
The format of date and time is yyyy/mm/dd hh:mm:ss
Probable cause: name of the probable cause of the alarm
Alarm Type: alarm class:
TRS = Transmission Alarm alarm not created inside the equipment, but generated by a
connected equipment or due to transmission/propagation problems
EQUIPMENT = alarm inside the equipment
Friendly Name: object of the equipment where the alarm occurred.
Severity: alarm severity:
Critical: RED
Mayor: ORANGE
Minor: YELLOW
Warning: CYAN
Indeterminate: GREY
Cleared: GREEN
Additional Text (if any)
Specific problem: for some alarms, additional information is provided about the involved resource
(for instance, when a threshold alarm is raised, it states the specific threshold exceeded).
Clicking into the column header, it is possible to sort the data by the values of the column itself.
Selection of one or more row of a table is allowed.
Rightclicking on an alarm row opens the menu shown below. The various options are described in the
following.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
140 / 232
The figure below shows an example where many tables are opened at the same time.
To make one table be displayed, click its header. It goes in the front, and becomes the active table.
To close one table, click the cross symbol of its header. To open it again, click it in the category tree on
the left.
close
put in front
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
141 / 232 3DB 75003 BAAA Ed.01
110.2.4 Multiple NE Alarms Monitor
While AM is active for a NE, to start AM contemporaneously on another NE, open another NEtO instance
for it, and perform the same operation described in para.110.2.2 on page 137
Take into account that only one AM instance can be running, whichever the number of NEs monitored.
When AM is active for more than one NE, the AM screen shows all the monitored NEs, as depicted in
following Fig. 55. :
on the left, a tree with the list of NE and subtree with the filters active for each NE is displayed.
on the right, the view of the alarms is displayed:
an internal window for each NE that the user can see
a Tab in the internal window for each filter that the user want to see. By default Current alarms
and Alarm Log tabs are always visible
for each view, the alarms are shown in a Table.
Refer to descriptions on previous pages 137 to 148 , for detailed information regarding the monitoring
of one NE.
N.B. See also Shortcut icons in para.110.2.11 on page 149
first NE
Severity alarm synthesis of first NE
tab panels of first NE
second NE Severity alarm synthesis of second NE
tab panels of second NE
Fig. 55. Example of multiple NE Alarms Monitor (2 NEs)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
142 / 232
110.2.5 Filters menu
The Menu Filters provides the following menus, described in the following:
[1] Add a Filter
This menu allows to create customized logs adding some new specific filters. The windows which
opens is shown in Fig. 56. below:
Fig. 56. Alarms Monitor Add a filter
A filter can be created selecting one of the following fields (or more). To save the created filter click
on the Done pushbutton. (Clicking on the Cancel pushbutton clears the filter configuration). The
created filter appears on the left side of the application.
Filter Name field
Enter the filter name in the Filter Name field.
Scope field
Select CURRENT to create a filter showing the current alarms only, or select LOG to create
a filter for current and cleared alarms.
The filter can be applied to all the NEs by selecting All or it can be applied to one or more NEs
by selecting one or more NEs using the mouse.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
143 / 232 3DB 75003 BAAA Ed.01
Alarm Type field
Select Alarm Type to create a filter for the selected type of alarm:
TRS = Transmission Alarm
EQUIPMENT = Equipment alarm
Perceived severity field
Select Perceived severity and then one or more severity levels and/or Cleared state to filter the
alarm having the selected severity levels.
Event Time field
Select Event Time and then enter the starting date (From) and the ending date (To) to filter the
alarms created during that specific time frame only.
Probable Cause field
Select Probable Cause and then choose a specific alarm (one or more) to filter these particular
alarms only.
[2] Delete Filters ...
When this menu is selected, the window shown below opens (example):
Fig. 57. Alarms Monitor Delete Filters ...
By means of this menu the filters previously created can be canceled. Default filters cannot be
canceled.
Select one specific NE (or more NEs) in the Scope column, select a specific filter (or more filters)
in the Filters column and then click on the Done Pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.
[3] Delete Selected Filter
Default filters cannot be deleted. Selecting a customized filter and selecting Filters % Delete
Selected Filter, the filter is deleted, after having confirmed the following question:
[4] Edit Selected Filter
Default filters cannot be edited. Selecting a customized filter and selecting Filters % Edit Selected
Filter, the same screen of Fig. 56. on page 142 opens, where you can make your changes, then
click Done pushbutton to confirm them.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
144 / 232
[5] Save Filters As ...
Fig. 58. Alarms Monitor Save Filters As ...
A default filter, or a filter previously created by means of the Add a filter menu, can be saved to be
used for some other Craft Terminals.
Select in the Scope and Filters columns a specific filter to be saved, enter the filter name in the Name
field, select the Folder where to save the file relevant to filter and then click on the Done Pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.
[6] Load Filters From ...
Fig. 59. Alarms Monitor Load Filters From ...
A filter previously saved on another Craft Terminal can be loaded on your Craft Terminal by this menu.
Click on Browse to navigate and then choose the filter file to be loaded. The Scope and the Loaded
Filters columns will show respectively the NE list and the filters list made available by the selected
file.
Entering some characters in the Filters Prefix field and then clicking on the Done pushbutton, the
inserted characters are attached before the names of the Loaded Filters. For instance entering
<Vim>, the names of the filters change from APT to VimAPT.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
145 / 232 3DB 75003 BAAA Ed.01
110.2.6 File Menu
The File menu allows to Save or Load the AM History:
[1] Save History for selected NE
This menu allows to save a file with one of the two global lists of each NE. Select the global list of
a specific NE, open the Save History menu for the selected NE, and enter filename and relevant
directory in the opening window.
[2] Load History for selected NE
By means of this menu it is possible to display the global list of a certain NE previously saved.
110.2.7 Printing the alarms and logs
As shown below, in AM screen (with mouses right button), select Print current view to launch the print,
then specify the printer.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
146 / 232
110.2.8 Exporting the alarms and logs
As shown in Fig. 60. , in AM screen (with mouses right button), at first Select All to select all shown
alarms, then Export Alarms (in CSV, HTML, XML, or PDF format), and specify where to save the file;
at last Select None to deselect all alarms previously selected.
N.B. The CSV method defines a model to memorize the data of a table using comma character. The
fields of a single row are separated by one symbol , and the rows of a table are separated by
the NEWLINE character.
Fig. 60. Exporting the alarms and logs
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
147 / 232 3DB 75003 BAAA Ed.01
110.2.9 Navigate from AM to USM
The AM program gives to the user the possibility to navigate from AM to JUSM (and viceversa).
When a user selects an alarm in AM screen, he/she can request to show the object, on which the alarm
was raised, in JUSM, as in example of Fig. 61.
N.B. If not active, JUSM is automatically started (the login prompt is displayed, with UserName and
Password to be entered).
(1) With mouses left button, select one alarm
(2) On selected alarm, with mouses right
button, select Navigate to USM
(3) JUSM shows the object,
on which the alarm was raised
Fig. 61. Navigate from AM to USM
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
148 / 232
110.2.10 Navigate from USM to AM
This operation is complementary to the Navigate from AM to USM described before.
When a user selects an alarm in JUSM screen, he/she can request to show the same alarm in the AM
screen, as in example of Fig. 62.
N.B. If not active, AM is automatically started.
(1) With mouses left button,
select one alarm
(2) With mouses right button,
select Navigate to AM
(3) AM screen opens
with the same alarm selected
Fig. 62. Navigate from USM to AM
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
149 / 232 3DB 75003 BAAA Ed.01
110.2.11 Shortcut icons
The following shortcut icons, for simplicity not shown in previous figures, are available:
A B C D
R
E F G H I
L M
J
K P Q N O
A and B: these functions are particularly useful during the Multiple NE Alarms Monitor
(para.110.2.4 on page 141 ); A arranges windows vertically, while B arranges windows boxed, as
in following examples:
VERTICAL ARRANGEMENT BOXED ARRANGEMENT
C maximizes Windows
D exits from the AM application
E expands all tree nodes
F collapses all tree nodes
G removes the selected NE from the AM application
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
150 / 232
H, I, and J are related to the filter management ( para.110.2.5 on page 142 ); H adds a new filter,
I deletes the selected filter, and J edits the selected filter.
K and L are related to the management of the rows in the active table; K selects all rows, while J
deselects all rows.
M performs the Navigation to USM ( para.110.2.9 on page 147 ).
N, O, P and Q are related to the Export of the alarms and logs ( para.110.2.8 on page 146 );
their export format is clearly shown by the icon.
R acts as the Print Current View available on all screens.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
151 / 232 3DB 75003 BAAA Ed.01
110.3 Event Log Browser (ELB)
110.3.1 ELB scope
An event is meant to be:
a configuration change
a change of the value of an attribute
an automatic switchover
a manual operation carried out by the operator.
ELB is a tool that shows the list of events generated on NE at a specific moment. The main functionalities
offered are:
list of events and main information (time, type, etc.)
print them
export a summary view of events lists to an HTML file, or to a CSV (Comma Separated View) file.
110.3.2 ELB startup
The ELB application can be launched on a loggedin 9400AWY NE through the WebEML command:
Diagnosis % Log Browsing % Event Log
If the NE does not respond at the get request or responds with an ACCESS DENIED message, the
application communicates the problem to the user and does not refresh the tables containing alarms and
event. A special indicator shows to the user that the application is offline until a new user request for
tables refresh succeeds.
After refresh completion, the Event Log Table screen opens.
WARNING: The Event Log Table is updated only if the corresponding Log Switch is unlocked (see
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
152 / 232
110.3.3 Event Log Table screen
At first command execution, or by the user command Refresh, the application retrieves the data about the
events presents on NE in that moment.
[1] Row contents
The events are shown as rows in a table. For each event, the following field are shown:
Time: date and time of occurrence of the event. The format is week day/month/day hh:mm:ss.
Reference Time (CEST) year.
Notification ID: a unique identifier for the event.
Explanation: a statement built with the event log data to explain what the event represents.
Refresh the
Events
table to current
values
Print the Events
Export the Events data to an external file
Fig. 63. Event Log Table screen
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
153 / 232 3DB 75003 BAAA Ed.01
[2] Sorting rows
Clicking on columns headers, events can be ordered by the fields values.
[3] Selecting rows
Clicking on rows, the events (one ore more) can be selected. This selection can be used in the screen
of Fig. 64. below.
Clicking the Clear Selection pushbutton in the screen of Fig. 63. on page 152 , all rows are
deselected.
[4] Printing events
Clicking the Printer symbol in the screen of Fig. 63. on page 152 , all events are printed,
independently from the selection you may have done (point [3] above).
[5] Export events to an external file
The application allows to export the content of the events table in the following ways:
in an HTML table
in CSV formatted text
The CSV method defines a model to memorize the data of a table using comma character. The
fields of a single row are separated by one symbol , and the rows of a table are separated by
the NEWLINE character.
as PDF document
in XML format
In both cases, you can choose to export All entries or the Selection you may have done (point
[3] above).
Fig. 64. Export events screen
After having made the selection, and clicked OK pushbutton, a save screen is opened, asking where
save must be done.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
154 / 232
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
155 / 232 3DB 75003 BAAA Ed.01
111 MIB MANAGEMENT
This chapter describes how to perform the NE MIB backup and restore operations, introduced in
para.14.2.2 from page 41
Subject On page
Default repository folders of MIB backup files 156
Craft Terminal commands for the management of MIB backup files 156
How to perform the MIB backup 157
How to perform the MIB restore 158
How to remove a MIB backup file from the repository folder 160
9400AWY R.2.0 V2.0.6 CDROM,
with the SWP TCO SUITE Rel.1.7, the NE MIB backup and restore operations (functions of NEtO)
are much simpler
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
156 / 232
111.1 Default repository folders of MIB backup files
There is one default repository folder of MIB backup files for all NEs having the same SWPrelease.
The folder name is backup, and is under the path where you have performed the Local copy of WebEML
(Jusm/CT): see point 2 ) on page 185 , and point 8 ) on page 188 .
This folder is automatically selected when you perform any of the commands listed in following
para.111.2
The example below shows two MIB backup files present in the backup folder for 9400AWY V2.1.2.
C:\TCO_SUITE_17\AWY_CT_V01.07.xx\AWY_CT_V02.01.02\backup
C:\TCO_SUITE_17\AWY_CT_V01.07.xx\AWY_CT_V02.01.02\backup
WARNING: the file name contains always the version as prefix (V020102_ in the example above,
corresponding to version V2.1.2).
This prefix is inserted automatically by the SW, when the MIB backup file is created ( see
following para.111.3 ), and is used automatically by the SW, when the MIB restore must
be performed ( see following para.111.4 )
Therefore, this prefix must never be changed.
111.2 Craft Terminal commands for the management of MIB backup files
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
157 / 232 3DB 75003 BAAA Ed.01
111.3 How to perform the MIB backup
Perform the command Supervision % MIB Management % Backup
The Backup screen opens. Proceed as in following example:
file already existing (example)
(1) name the new file to create (example)
(2) click Save
(3) click Yes
new file added !
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
158 / 232
111.4 How to perform the MIB restore
Perform the command Supervision % MIB Management % Restore
The Restore screen opens. Proceed as in following example:
(1) select the file to restore (example)
(2) click Open
(3) click Yes
(4) continues ..
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
159 / 232 3DB 75003 BAAA Ed.01
(4) .. continues
At this point, the restored file is present in a Flash Cards temporary area, but has not been activated in
the actual MIB memory. The following question raises:
At this question, if you answer:
Yes, the activation of the restored MIB is started.
This implies an automatic system restart (see point [8] on page 46 ), and the CTNE communication
is lost.
Therefore, wait the time necessary for the restart completion, after which you can perform again the
NEtO startup and the NE login.
No, no action is made, but the restored file is still present in a Flash Cards temporary area.
When you decide to activate it, perform the command:
Supervision % MIB Management % Activate
which operates as answering Yes in the question screen above
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
160 / 232
111.5 How to remove a MIB backup file from the repository folder
Perform the command Supervision % MIB Management % Remove file
The Remove file screen opens. Proceed as in following example:
(1) select the file to remove (example)
(2) click Remove file
(3) click Yes
Result: file has been removed:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
161 / 232 3DB 75003 BAAA Ed.01
112 NE SWP UPGRADE
This chapter describes how to upgrade to a new SWP any 9400AWY Rel.2.x NE, presently running with
a previous SWP.
The procedures in this chapter apply:
only for the upgrade to 9400AWY versions V2.0.6, or V2.1.2, or V2.1.3.
and in both these cases (for explanations, if necessary, refer to para.12.3 on page 22 ):
upgrade to a SWP with new Version Level (with respect to that presently running, e.g. from
9400AWY SWP V2.1.2 to 9400AWY SWP V2.1.3)
upgrade to a new SWP patch version (with respect to that presently running, e.g. from
9400AWY SWP V2.1.2 to 9400AWY SWP V2.1.2 patch version).
Subject On page
Introduction and restrictions 162
Case of upgrade to 9400AWY V2.0.6 162
Only for upgrade to 9400AWY V2.0.6 or V2.1.2: how to perform, by
WebEML, the SWP download to the NE, and its activation
163
CT startup, and check for the availability of the SWP to be downloaded 164
NE login and initial operations (stations A and B) 164
SW download to the NE (station A) 165
Activation of the new Software Package on the NE (station A) 170
Additional operation for upgrade from older versions (station A) 172
Operations on station B 172
Functional checks on the radio link (stations A and B) 172
NE data backup (stations A and B) 172
Notes about NE SW downgrade 173
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
162 / 232
112.1 Introduction and restrictions
As a preface to this chapter, if necessary, refer to para.14.2 from page 38 , and in particular to point
[7] on page 45
RESTRICTION FOR WINDOWS VISTA
With Windows Vista, the SWP download for NE upgrade cannot use LLMAN (therefore the NEs F
interface must not be used for the SWP download).
112.2 Case of upgrade to 9400AWY V2.0.6
The upgrade of any 9400AWY Rel.2.0:
presently running with a SWP version < 2.0.6
to the SWP version 2.0.6
can be done in two ways:
using the 1320CTbased Craft Terminal; in this case, make fully reference to the instructions given
in the specific 9400AWY R.2.0 V2.0.6 User Manual ( Tab. 1. on page 14 ) , more precisely:
chapter SWP download toward NE
or, using the TCO SUITEbased Craft Terminal; in this case, use the instructions given in para.112.5
from page 163
The upgrade of any 9400AWY Rel.2.1:
can be done in two ways:
using the 1320CTbased Craft Terminal; in this case, make fully reference to the instructions given
in the specific 9400AWY R.2.1 V2.1.2 User Manual ( Tab. 1. on page 14 ) , more precisely:
chapter CT & NE upgrade to V2.1.2 from previous version V2.1.x
or, using the TCO SUITEbased Craft Terminal; in this case, use the instructions given in para.112.5
from page 163
To upgrade any 9400AWY Rel.2.1:
please make fully reference to the instructions given in the specific 9400AWY R.2.1 V2.1.3 User Manual
( Tab. 1. on page 14 ) , more precisely:
chapter NE upgrade to V2.1.3 from previous version V2.1.x
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
163 / 232 3DB 75003 BAAA Ed.01
112.5 Only for upgrade to 9400AWY V2.0.6 or V2.1.2: how to perform, by
WebEML, the SWP download to the NE, and its activation
N.B. the instructions for the use of the SW Download menu with 9400AWY V2.1.3 are given in the
User Manual cited in para.112.4 on page 162
9400AWY R.2.0 V2.0.6 CDROM,
With the SWP TCO SUITE, the preparation of the SWP to be downloaded to the NE is performed by
the command SW Download Init SW Download (with the 1320CTbased Craft Terminal, it is
performed by the Network Element Synthesis screen)
WARNING:
You must be aware that these operations must be done on both stations A and B of the radio link.
The suggested sequence of phases is:
Phase Operation
Station
Described in para. Phase Operation
A B
Described in para.
1
CT startup, and check for the availability of
the SWP to be downloaded
112.5.1 on page 164
2
NE login and initial operations (stations A and
B)
x x 112.5.2 from page 164
3 SW download to the NE (station A) x 112.5.3 from page 165
4
Activation of the new Software Package on
the NE (station A)
x 112.5.4 from page 170
5
Additional operation for upgrade from older
versions (station A)
x 112.5.5 on page 172
6 Operations on station B x 112.5.6 on page 172
7
Functional checks on the radio link (stations
A and B)
x x 112.5.7 on page 172
8 NE data backup (stations A and B) x x 112.5.8 on page 172
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
164 / 232
112.5.1 CT startup, and check for the availability of the SWP to be downloaded
a ) Power on the PC and wait for its startup
b ) Verify that the SWP to be downloaded is available in the PC
The NEspecific SW components to be downloaded are not present in the SWP TCO SUITE
CDROM. Such components should have been copied in the PC during the 1320CT installation
(refer to the User Manuals cited in para.112.3 and 112.2 on page 162 for details).
The directory where the NE software package is installed is:
Alcatel / JUSMw V.x.x.x / ect / swdw / <equipment name> / <version> / <descriptor file> (*)
(*) the 9400AWY equipment name is R94AWY
JUSMw V.x.x.x depends on the 9400AWY CDROM
the version is 2.0.6 or 2.1.2, according to what you have to do
the descriptor file name for 9400AWY is always R94A.DSC
N.B. This descriptor file R94A.DSC is that you must select in step c ) on page 166
N.B. The descriptor file R94A.DSC can also be selected directly from the:
9400AWY R.2.0 V2.0.6 CDROM
or:
9400AWY R.2.1 V2.1.2 CDROM
In this case, after inserting the CDROM in the PC, in step c ) on page 166 , choose the
following path from the CDROM root:
ect / swdw / <equipment name> / <version> / <descriptor file>
112.5.2 NE login and initial operations (stations A and B)
Perform following operations by WebEML (for details refer to chapter 19 from page 111 ):
a ) Login the 9400AWY station A NE, using the Administrator or CraftPerson UserName & Password
WARNING: as specified in para.112.1 on page 162 , with Windows Vista, the SWP download
for NE upgrade cannot use LLMAN (therefore the NEs F interface must not be used
for the SWP download)
b ) Wait for the main Equipment view to appear
c ) Verify that the version to be downloaded is greater (or equal, only in case a new SWP patch version)
than those present in both the NE MIB current Standby and Committed banks (check by SW
Download SW Status, and verify both banks)
WARNING: you must be aware that the SWP download, performed in the following, will overwrite
the current Standby version. In the case you want to maintain such a version, and
overwriting the other (i.e. that presently Committed), activate the current Standby
version as described in para.112.5.4 on page 170
d ) Perform the NE data backup, as described in point [3] on page 43
e ) Check that no hardware or radio transmission problems are present. Otherwise, solve them before
starting upgrade
f ) Close all Performance Monitoring, analog measurement and BER measurement processes, if any
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
165 / 232 3DB 75003 BAAA Ed.01
g ) Do not use functions stated above, or any other action not strictly necessary for the upgrade, until
you have completed the SW upgrade of both stations, i.e. not before the operations described in
para.112.5.6 on page 172 of this procedure
h ) Before to start the software download, it is recommended to disable the ATPC operation (if it has been
enabled) and to set in RTPC mode the max. Tx power
i ) By another NEtO session, perform on the 9400AWY station B NE the same operations done for
station A
112.5.3 SW download to the NE (station A)
Step 1. Server Access Configuration Setup
a ) By WebEML, perform SW Download Server Access Configuration
b ) The following screen opens:
c ) Click the button Use System Default
In this way the systems sets automatically the various fields, that depend on how the login to
the NE has been done:
by Ethernet interface: IP address of the PC to download the software in LAN mode is set
by F interface: IP address of the LLMAN to download in interface F mode is set (remind:
never with Windows Vista)
N.B. The UserId and Password present in this screen are relevant to the ftp login, are set
automatically with the Use System Default button and have no relationship with
those necessary for the NE login.
d ) Press OK to confirm values and close the window.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
166 / 232
Step 2. SW Download
a ) By WebEML, perform SW Download Init SW Download
b ) The following screen opens (example where no Software Packages are available):
Fig. 65. Empty Init SW download screen
c ) Click the button Add
The following screen opens. With reference to point b ) on page 164 , explore the path where
the descriptor file R94A.DSC (associated to the version to be downloaded) is present, then click
button Open
2_1_2
Fig. 66. Selection of the descriptor file R94A.DSC (example for V2.1.2 download)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
167 / 232 3DB 75003 BAAA Ed.01
d ) Now ( Fig. 67. below) select (1) a specific SWP to download on the NE, then (2) press Init
download to start it.
(1) select
N.B.
(2)
2_1_2
Fig. 67. Init SW download (example for V2.1.2 download)
N.B. normally, the Forced check box must not be used.
You must tick it only in the case you want to download a certain version to a NE whose
flash card is already loaded with the same version (i.e. for corrective maintenance
purposes)
e ) Confirm the start of software downloading (example for V2.1.2 download):
Yes
2_1_2
f ) The software downloading in progress is shown by a specific window:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
168 / 232
Description of the software downloading process:
if, in the Init SW download screen ( Fig. 67. on page 167 ) you have:
unselected the Forced check box (default choice):
at first, the download process compares the versions of the SW components to
be downloaded with those of the corresponding SW components present in the
NEs flash card Standby bank,
then, only the SW components (if any) whose version is higher than that of the
corresponding SW components in the Standby bank are downloaded to it.
selected the Forced check box, all SW components are downloaded to the Standby
bank in any case, also overwriting those whose versions are equal.
The software download from the Craft Terminal to the NEs flash card is performed without
traffic interruption on the user ports, and lasts:
some tens of seconds, if no download is executed (this time is anyway necessary for
the comparison phase, to decide which SW components must be downloaded)
about 30 minutes, if performed locally through the F interface
about 15 minutes, if the local Ethernet interface is used
about 1.5 hour, if the download is performed toward a remote NE, through the NMS
network or the radio interface
WARNING: in this last case (download toward a remote NE), verify that the
download bar does move, even slowly. If it does not move, it means
that the download does not work properly (there are no messages to
the operator). In this case, abort the software download window by
the suitable Abort button, and begin again the software download
procedure.
g ) When the download is over, the following window is shown; click OK to close it.
N.B. this message appears even if no download is actually executed.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
169 / 232 3DB 75003 BAAA Ed.01
h ) After the software download completion, by WebEML perform SW Download SW Status,
select the Standby bank, and verify (see example figure for V2.1.2 below):
that the downloaded SW is present as Stand by version, and that is the version you
wanted
and that its Operational Status is Enabled (this means that the download took place
without errors)
WARNING: if the Operational Status is Disabled, repeat the download
N.B. clicking on the Software Unit Status button, it is possible to see its components and
their version
V02.01.02
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
170 / 232
112.5.4 Activation of the new Software Package on the NE (station A)
After the software download (explained in previous para.112.5.3 from page 165 ), two software
packages are present in the NE: one Committed and the other Stand by.
The Activation of the new Software Package on the NE means to make the Stand by SWP become the
Committed one (and viceversa).
Step 1. Activation of the Standby SW bank
a ) By WebEML, perform SW Download SW Status
b ) Fig. 68. below (example for V2.1.2 activation): select the Standby SW bank (1), set Activation
or Forced Activation (2) in the Software Management Action field, then click Apply Action
(3)
N.B. difference between Activation and Forced Activation:
selecting Activation, the system performs an automatic restart, after the swap,
only if the contents of the Committed and the Stand by banks are different
selecting Forced Activation, the system performs anyway an automatic
restart, after the swap.
(1)
(2)
V02.01.02
(3)
V02.01.02
Fig. 68. Activation of the Standby SW bank
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
171 / 232 3DB 75003 BAAA Ed.01
c ) Confirm the selected action:
d ) This message appears (click OK to close) ...
e ) ... and the NE restarts with the new software package.
N.B. The JUSM becomes unavailable (the following message appears (click OK to
close)
Effects of the Activation of the Standby SW bank process:
the previous Stand by bank becomes the Committed one, and viceversa
the SW components of the new Committed bank (after the swap) are loaded in the Equipment
Controller and in all peripherals (IDU and ODU)
the equipment data base structure is converted to the structure of the new SWP (only for
upgrade; for downgrade, refer to para.112.6 on page 173 )
Step 2. Logoff and ReLogin
a ) Logoff the NE
b ) Login the NE and verify, by SW Download SW Status, that the SW banks have changed
their Current Status.
WARNING: once you have downloaded and made active the new SWP in NE environment, do not
make the mistake of trying to switch the previous version back to COMMITTED status,
unless you explicitly want to perform the NE SW downgrade, described in para.112.6
on page 173
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
172 / 232
112.5.5 Additional operation for upgrade from older versions (station A)
This additional operation is mandatory in the following cases:
upgrade to the SWP version 2.1.2, of any 9400AWY Rel.2.1 previously running with version 2.1.0
upgrade to the SWP version 2.0.6, of any 9400AWY Rel.2.0 previously running with any version
V2.0.0, or V2.0.1, or V2.0.2, or V2.0.3, or V2.0.4
Proceed as follows:
After having performed for the first time:
the SW download to the NE (para.112.5.3 from page 165 )
and its activation on the NE (para.112.5.4 from page 170 )
perform for the second time:
the SW download to the NE (para.112.5.3 on page 165 ), but, in phase d ) on page 167 ,
setting Forced before clicking on Init download
and the activation of the Stand by on the NE (para.112.5.4 from page 170 )
N.B. Obviously, at the end of this procedure, you will have both SW banks with the same SWP, and
the previous SWP has been lost.
Why is this operation required?
Starting from AWY V2.0.5, and AWY V2.1.1, some new SW components have been added (with
respect to V2.0.5 and V2.1.0) in the SWP: for this reason, if the active bank is respectively < V2.0.5,
or < V2.1.1, the download of SWP in the flash card must be executed in two steps:
with the first step (normal download procedure) only the new version of the SW components
known by previous SWP version are downloaded on flash card
the new SW components are known ONLY by SWP > V2.0.4, or SWP > V2.1.0, so after the
activation of the SWP V2.0.6, or V2.1.2, it is necessary to download it again (IN FORCED
MODE), to transfer the new SW component image onto flash card.
112.5.6 Operations on station B
Perform on station B all operations you have performed on station A (described from para.112.5.3 on
page 165 , to para.112.5.5 above.
112.5.7 Functional checks on the radio link (stations A and B)
Perform functional checks on the radio link (e.g. Alarm Monitor, Performance Monitoring, analog
measurement, BER measurement, operations on protection schemes, loopbacks, etc.)
112.5.8 NE data backup (stations A and B)
Perform the NE data backup for both stations, as described in point [3] on page 43
N.B. These backup files are consistent with the data base structure of the new Committed SW bank,
while those created in step d ) on page 164 were consistent with the data base structure of
the old Committed SW bank (that has now become the Stand By bank).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
173 / 232 3DB 75003 BAAA Ed.01
112.6 Notes about NE SW downgrade
If, in the Flash Card, the version of the SWP in the Stand by bank (e.g. V2.1.1) is lower than that present
in the Committed bank (e.g. V2.1.2), the activation of the Stand by bank corresponds to the NE SW
downgrade (i.e., following the example above, from V2.1.2 to V2.1.1).
This operation is greatly discouraged for backward data base structure incompatibility.
In fact, when the lower version SWP is activated, the data base is scratched, and you must redefine all
NE data from the beginning.
Additional notes:
the downgraded NE must be managed by the proper SW management tool (e.g. to manage a
9400AWY V2.1.1, you must use the 1320CTbased Craft Terminal installed from the SWP 9400AWY
V2.1.1 CDROM)
the data base, scratched by the downgrade operation (e.g. from V2.1.2 to V2.1.1), remains scratched
even if you perform the upgrade (e.g. from V2.1.1 to V2.1.2); therefore, also in this case, you must
redefine all NE data from the beginning.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
174 / 232
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
175 / 232 3DB 75003 BAAA Ed.01
113 MANAGEMENT OF THE SECURITY FEATURES
This chapter describes how to manage the security features of 9400AWY (by operator profile, by
community string, and by access lists).
Subject On page
Management of security by operator profiles below
Management of security by community string 178
Management of security by access lists 180
113.1 Management of security by operator profiles
[1] Description of the security by operator profile feature
Refer to para.13.3.2 on page 34
[2] Username and Password format
An user is identified by a username and password with the following characteristics:
Username length: the length must not be more than 20 characters.
Password length: the length must not be less than six (6) characters under any circumstances
and must not be less than eight (8) characters for administrator user profile. Moreover the
password length must not be more than 20 characters.
Password composition: the password must be composed of full ASCII characters set
(UPPER/lower case, numeric and special characters).
Each user is associated to a predefined profile.
[3] User number
Twentyfive (25) users at most can be created.
[4] User predefined profiles
The predefined profiles are described in point [2] on page 34
The list of supported features for each user profile is shown by the suitable tables available in the
help online [see point 3 ) on page 123 ].
[5] NE scratch behavior
At installation time (NE scratch), a default Administrator user is defined: see point [1] on page 34
[6] Restart NE behavior
All the security information sets (username/password/profile for each user) are stored permanently
in the NE database (MIB data base). After the NE reset, these information sets are not lost and are
recreated as before the NE reset.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
176 / 232
[7] Change Password procedure
With this procedure, available for all Operator Profiles, any user, after the successful login by
WebEML (Craft Terminal), can change his/her password:
1 ) Configuration Profiles Management Change Password
Fig. 69. Profile Management options
2 ) Following screen appears; fill it with old and new passwords, taking into account password
characteristics listed in point [2] on page 175 . The new password will be active at next login
(after having logged out).
1
2
3
4
Fig. 70. Changing Password screen
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
177 / 232 3DB 75003 BAAA Ed.01
[8] Users Management procedure
This procedure is available to users with the Administrator profile only, by WebEML (Craft Terminal):
1 ) Configuration Profiles Management Users Management (see Fig. 69. on page 176)
2 ) Following screen appears. Click on Help
Fig. 71. Users Management screen
3 ) Following screen appears. Click inside to explore matters and carry out the desired action.
Fig. 72. Users Management help screen
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
178 / 232
113.2 Management of security by community string
N.B. this feature is not manageable on AWY 2.0.6 and 2.1.2 NEs
[1] Description of the security by community string feature
[2] Management of the security by community string
This kind of management is available:
only to users with the Administrator profile,
and only after having logged in successfully the NE by the Main Menus Alarms & Settings
function.
Procedures
1 ) on the Main Menus Alarms & Settings screen ( Fig. 21. on page 66 ), click Community
String. The following screen opens:
Fig. 73. Alarms & Settings Community String request
The values displayed in Fig. 73. are the defaults (present in the Flash Card as delivered from
AlcatelLucent factory):
the Read Community string (default = public ) must not be changed
the Write Community string ( default = private ) can be changed to activate the security
by community string
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
179 / 232 3DB 75003 BAAA Ed.01
2 ) How to change the Write Community string
To change the Write Community string:
enter the new string in the field taking into account the following format:
number of characters: 6 at minimum, 10 at maximum
admitted characters are only:
letters a to z, A to Z
digits 0 to 9
then, click Apply
After the successful Write Community string change, the consequences are the following:
at NE side, the change takes effect at once (no NE restart is performed)
at user side, any NEtO session opened on the NE (supervision, WebEML, and Alarms
Monitoring) is lost.
The operator, independently of her/his profile, to supervision again the NE:
first at all, has to close the NEtO window (by Exit button)
then, she/he starts again the NEtO session [ step a ) on page 100 ]
then, she/he inserts the new Community String (that the NE Administrator must
have communicated to the users) as specified in step b ) on page 101
then, she/he proceeds from step c ) on page 102
3 ) How to reset the Read Community and Write Community strings
To reset the Read Community and Write Community strings at their default values:
in the screen of Fig. 73. on page 178 , click Default
then, click Apply
The consequences of this operation are as in point 2 ) above.
But, in this case, the operator who has lost the CTNE communication, to supervision again the
NE, must not perform the step b ) on page 101 (i.e. must not insert any Community String).
Both the Read Community and Write Community strings are stored permanently in the NE
database (MIB data base), and they are kept at NE restart.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
180 / 232
113.3 Management of security by access lists
N.B. this feature is not manageable on AWY 2.0.6 and 2.1.2 NEs
[1] Description of the security by access lists feature
[2] Management of the Access List tables
The Access List tables have the default status shown in Fig. 74. below, which is one of the steps
of the Full Configuration Procedure of the Provisioning Tool, described in chapter 15 on page
59 . In case the Provisioning Tool is run:
in not NEinteractive mode (offline), all operators can obviously write the tables
in NEinteractive mode (online), only a user with the Administrator profile can write the tables,
and, at the end of the configuration, can apply it to the NE.
To avoid conflicts, only one Administrator at a time (the first who logs in the NE by the online
Provisioning Tool) can fill the Access List tables; the others are excluded till the completion of
the job.
Fig. 74. Access list configuration default screen
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
181 / 232 3DB 75003 BAAA Ed.01
To insert and remove the IP Addresses and IP Masks of the enabled Managers PCs in each
Access List table, refer to the online help, clicking the relevant button.
Additional information:
Each row of each Access List table enables one or more Managers, i.e., if the first row is
the following:
IP: 151.99.98.1 Mask: 255.255.255.255
it means that only one Manager is defined.
Otherwise, if it is:
IP: 151.99.98.1 Mask: 255.255.255.0
then 256 Managers are enabled.
That is, the number of rows does not necessarily indicate the number of Managers,
because, for each row, many Managers can be defined.
When an Access List table is modified (with respect to the default status):
the IP address of the Administrators PC (from which the Access List table has been
modified) is automatically inserted in the table with IP Mask 255.255.255.255;
the default row with both IP Address and IP Mask = 0.0.0.0 is automatically removed.
When all IP Addresses and IP Masks of the previously enabled Managers PCs are
removed from an Access List table, this is automatically reset at the default condition (only
one row, with both IP Address and IP Mask = 0.0.0.0)
N.B. the content of the Access List tables is not shown to operators logging in the NE with a
profile different from Administrator.
[3] Activation of the changes made on the Access List tables
In the case of changes regarding:
theSNMP and http Access List tables, no NE restart is required: changes apply at once, as
soon as, at the end of the configuration procedure by the online Provisioning Tool, the new
configuration file is applied to the NE;
theftp and telnet Access List tables, it is necessary:
at first, to confirm the changes applying the new configuration file to the NE;
then, performing the NE restart.
The Access List tables are stored permanently in the NE database, and they are kept at NE
restart.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
182 / 232
[5] Access List Backup from a NE
Once the Access List tables have been defined in a NE (if at least one of them has a content different
from the default), it is possible, only for an user with the Administrator profile, exporting them all on
a suitable backup file, clicking the button Access List Backup on the Main Menus Alarms &
Settings screen ( Fig. 21. on page 66 ), which opens the following screen:
Fig. 75. Alarms & Settings Access List Backup request
[6] Access List Restore to a NE
A backup file obtained as described in point [5] above, can be restored (only by an user with the
Administrator profile) in the same NE, or another AWY 2.1.3 NE, clicking the button Access List
Restore on the Main Menus Alarms & Settings screen ( Fig. 21. on page 66 ), which opens the
following screen:
Fig. 76. Alarms & Settings Access List Restore request
After the successful restore operation, perform the NE restart.
a ) END OF SECTION
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
183 / 232 3DB 75003 BAAA Ed.01
APPENDICES
SECTION 2: APPENDICES
This section describes the less frequently used functions of the SWP TCO SUITE, and provides additional
information.
Appendix A Preparation of the Craft Terminal based on the SWP TCO SUITE
This Appendix describes the Advanced Settings screen, and details all phases
necessary to copy and/or install the SWP components from the SWP TCO SUITE
CDROM, in the PC environment.
185
Appendix B JRE installation and SWP TCO SUITE startup
This Appendix describes how to install the required version of JRE, the standard
behaviour of the SWP TCO SUITE startup, as well as some special conditions that
may occur during it, and the countermeasures to take.
191
Appendix C LLMAN installation, configuration and use
This Appendix explains the operations to be done on the PC to allow the NE
management through the NEs F serial port.
201
Appendix D ECTEquipment connection via public switched telephone
network
This Appendix explains the operations necessary to allow the remote connection to
the FInterface, from a local PC configurated as ECT, through a switched telephone
line of the standard Public Telephone Network.
217
Appendix E SWP TCO SUITE Rel.1.7 deinstallation
This Appendix describes how to deinstall from the PC the SWP TCO SUITE
components.
227
Appendix F Customer documentation feedback 229
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
184 / 232
APPENDICES
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
185 / 232 3DB 75003 BAAA Ed.01
APPENDICES
21 APPENDIX A: PREPARATION OF THE CRAFT TERMINAL BASED
ON SWP TCO SUITE
This Appendix describes the Advanced Settings screen, and details all phases necessary to copy and/or
install the SWP components from the SWP TCO SUITE Rel.1.7 CDROM, in the PC environment.
Subject On page
Operations sequence below
Functions of the other buttons of the Advanced Settings screen 189
Note about TCO SUITE previous versions 189
21.1 Operations sequence
2 ) In your system disk, create a folder where to put all files (e.g. TCO_SUITE_17 in Fig. 77.
below).
WARNING: the name of this folder must contain neither blank spaces, nor characters which
may confuse the filing system, like:
\ ? : * < > | .
WARNING: the absolute path where the folder is put, must not contain blank spaces (e.g.
you cannot put it in the My Documents folder, which has a blank space).
TCO_SUITE_17
Fig. 77. Creation of folder for repository of SWP TCO SUITE Rel.1.7 files
3 ) insert the SWP TCO SUITE Rel.1.7 CDROM in your PC
4 ) if never done previously, the startup of the SWP TCO SUITE Rel.1.7 is performed
automatically (it installs, if necessary, the JRE required version), and the Main Menu screen
opens ( Fig. 10. on page 47 )
N.B. in case of problems, or for details, refer to Appendix B on page 191 (in particular,
take into account that the installation of the JRE requires the PC Administrator
privileges)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
186 / 232
APPENDICES
5 ) click on Advanced Settings button
6 ) the Advanced Settings screen opens ( Fig. 78. below )
Fig. 78. SWP TCO SUITE Rel.1.7 Advanced Settings screen (AS.html page of CDROM version)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
187 / 232 3DB 75003 BAAA Ed.01
APPENDICES
7 ) starting from the Advanced Settings screen, perform the Local copy of TCO Suite:
N.B. this operation does not require the PC Administrator privileges
(1)
(2) Choose the folder created in step 2 ) on page 185
(3)
(4)
(5)
(6) (7)
(8)
(9) shortcut created
on the desktop
WARNING
TcoSuite.17
TCO_SUITE_17
C:/TCO_SUITE_17
E:\TcoSuite.17x has been successfully copied
WARNING: in case the automatic creation of the shortcut fails (it could happen with PC set
to some languages), you can create it manually [Start.exe file in TcoSuite.xx
folder, under the root created in step 2 ) on page 185 ]
Fig. 79. Local copy of TCO Suite
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
188 / 232
APPENDICES
8 ) starting from the Advanced Settings screen, perform the Local copy of WebEML (Jusm/CT):
(1)
(2) Choose the folder created in step 2 ) on page 185
(3)
(4)
(5)
(6) (7)
(8)
(9) shortcut created
on the desktop
WARNING
AWY_CT_V01_07
N.B. this folder has been created
in step 7 ) on page 187
C:/TCO_SUITE_17
E:\AWY_CT_V01.07.xx has been successfully copied
TcoSuite.17x
WARNING: in case the automatic creation of the shortcut fails (it could happen with PC set
to some languages), you can create it manually [NEtO.exe file in NEtO folder,
under the root created in step 2 ) on page 185 ]
Fig. 80. Local copy of WebEML (Jusm/CT)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
189 / 232 3DB 75003 BAAA Ed.01
APPENDICES
9 ) starting from the Advanced Settings screen, perform (if necessary) the LLMAN installation
and configuration
This operation is necessary if you want to access any 9400AWY through its serialFinterface
(see Fig. 2. on page 25 ).
For the execution of the procedure, refer to the Appendix C on page 201
N.B. this operation requires the PC Administrator privileges
WARNING: the version of LLMAN contained in the SWP TCO SUITE Rel.1.7 CDROM is
higher than that of LLMAN contained in the:
9400AWY R.2.0 V2.0.6 CDROM
9400AWY R.2.1 V2.1.2 CDROM
SWP TCO SUITE Rel.1.6 CDROM
Therefore, if, in the past, you have used any of such CDROMs to install LLMAN
during the:
1320CTbased Craft Terminal preparation,
or SWP TCO SUITE Rel.1.6based Craft Terminal,
you must install this new version of LLMAN.
N.B. the new version of LLMAN is fully compatible with all 1320CTbased
applications.
10 ) at this point, if you have not performed the LLMAN installation and configuration, the
Preparation of the Craft Terminal based on SWP TCO SUITE Rel.1.7 is completed.
You do no longer need to use the SWP TCO SUITE Rel.1.7 CDROM, that can be extracted
from the PC.
21.2 Functions of the other buttons of the Advanced Settings screen
starts the manual installation of Java JRE
Package; see para.22.3 on page 193
go back to Main Menu of Fig. 10. on page 47
21.3 Note about TCO SUITE previous versions
In case you had installed in the past a previous version of the TCO SUITE for 9400AWY (i.e. version <
SWP TCO SUITE Rel.1.7), take into account that different TCO SUITE versions are independent from
each other. Nevertheless, because the new version does not exclude any feature of the old ones, and to
avoid possible confusion on your PC desktop, we suggest to deinstall the old versions.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
190 / 232
APPENDICES
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
191 / 232 3DB 75003 BAAA Ed.01
APPENDICES
22 APPENDIX B: JRE INSTALLATION AND SWP TCO SUITE STARTUP
This Appendix describes how to install the required version of JRE, the standard behaviour of the SWP
TCO SUITE startup, as well as some special conditions that may occur during it, and the
countermeasures to take.
Subject On page
Need for JRE installation below
Standard behavior of SWP TCO SUITE startup 192
Manual installation of Java JRE Package 193
Special conditions of SWP TCO SUITE startup 195
22.1 Need for JRE installation
Since the SWP TCO SUITE works using Java software, it is mandatory to have a Java Runtime
Environment (JRE) installed on the system.
Allowed JREs are Sun only, with version number higher or equal than that necessary for SWP TCO SUITE
(the necessary version is included in the SWP TCO SUITE CDROM).
The check of the JRE availability in the system, and of its version, is performed any time the SWP TCO
SUITE CDROM is inserted in the PC.
JRE can be installed:
automatically, at first insertion in the PC of the SWP TCO SUITE CDROM , as described in
or manually, as described in para.22.3 on page 193
WARNING: in both cases (automatic or manual installation) the PC Administrator privileges are
necessary.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
192 / 232
APPENDICES
22.2 Standard behavior of SWP TCO SUITE startup
The Suite autoruns itself (if this feature is enabled on users PC) as soon as the SWP TCO SUITE
CDROM is read by PC.
If autorun does not start, to launch the Suite, user must run (doubleclick with mouse) the Start.exe
file, available on SWP TCO SUITE CDROM root.
The first operation performed by autorun procedure is the check for JRE.
The policy adopted with the application running inside the browser, where normally the customer runs also
other applications that could require different JREs, is as follows:
if the JRE plugged into the browser is newer than or equal to the required version, the tool startup
will continue, and the screen of Fig. 10. on page 47 opens;
if the JRE plugged into the browser is older than the required version, user is asked to install it
(automatically from the SWP TCO SUITE CDROM) as shown in Fig. 81. below. The user can
accept and the tool startup will continue, otherwise the installation exits and the tool startup is
aborted.
Fig. 81. Java installation request
WARNING: the PC Administrator privileges are necessary to install JRE.
If user gives authorization to install JRE from CDROM, the installation message appears:
Fig. 82. JRE installation in progress
After, the default browser (configured as for user preferences) opens the SWP TCO SUITE Start.html page
( Fig. 10. on page 47 )
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
193 / 232 3DB 75003 BAAA Ed.01
APPENDICES
22.3 Manual installation of Java JRE Package
The Manual installation of Java JRE Package is done clicking the relevant button of the Advanced Settings
screen (see Fig. 78. on page 186 ):
WARNING: the PC Administrator privileges are necessary to install JRE.
This button connects to the installation file for the Java Runtime Environment contained in the SWP TCO
SUITE CDROM. The behavior of this button depends on browser and Windows version. Examples:
Mozilla Firefox on Windows XP asks the user where to place the .exe file; after saving, you must
execute it, to install the application.
Internet Explorer on Windows XP asks the user to Run or Save the .exe file:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
194 / 232
APPENDICES
If user chooses:
Run, the following Security Warning appears, where you should click Run.
Consequently, JRE installation from the CDROM starts with the message of Fig. 82. on page
192 , and ends with a suitable confirmation message.
Save, user is asked where to place the .exe file; after saving, you must execute it, to install the
application.
In any case, for most browsers the default behavior can be changed but this strictly depends on browser
configuration and user choices.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
195 / 232 3DB 75003 BAAA Ed.01
APPENDICES
22.4 Special conditions of SWP TCO SUITE startup
Depending on selected browser, on browser configuration and preferences and on users choices some
security questions could be made to the user, like:
To proceed, you must answer YES.
In case of specific users browser configuration, the browser could ask some questions about secure or
blocked content (Fig. 83. below) and before operating on TCO Suite pages user must click on this
information box (usually shown in a pale yellow background on top of the browser HTML page and allow
the browser to manage this information (Fig. 84. on page 196).
As stated before, the layout and graphical representation for this question (if asked) could be different from
browser to browser and, with respect to the same browser, language and information could vary too.
click
Fig. 83. Security Questions: Secure Content
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
196 / 232
APPENDICES
click
Fig. 84. Secure Questions: Allow Secure Content
Usually, the user has to click with the mouse on such yellow bar and a popup menu will appear to ask
user if he/she allows running this special content (Fig. 84. above). In some cases another confirmation
is requested to the user (Fig. 85. below).
Fig. 85. Execution confirmation (Security Warning)
Generally speaking, as soon as the browser is allowed to execute Java applets inside the HTML page,
a specific dialog will appear when browser recognizes that Java applets are inside the page.
As usual, both language and graphical layout could vary with respect to browser, operating system
version, operating system and browser languages and so on. Following Fig. 86. shows an example of this
warnings: as wrote before, things can differ with respect to language or graphics and so on.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
197 / 232 3DB 75003 BAAA Ed.01
APPENDICES
Fig. 86. Security Warning (English browser on Italian System)
This request is necessarily shown because TCO Suite applets needs specific parameters and permissions
in order to perform requested operations (reading and writing of files, for example). Applets used are
authenticated and a certificate is used to sign applets in order to tell user (and browser) that someone
(AlcatelLucent Italia SpA, WTD R&D Software CC, in this case) guarantees about the safety in loading
those applets inside a browser.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
198 / 232
APPENDICES
Another difference that user could perceive is related to a missing JRE but, even in this case, the graphical
layout will differ from system and browser.
If user opens the Start.html page even without a JRE installed shown page would differ from browser
and system versions. Following Fig. 87. shows Internet Explorer browser with no JRE installed. On top
of browser a yellow alert bar can be seen: in this case the browser detected a special content for which
it has no plugin so the browser asks the user to automatically install needed plugin by searching it on
the Internet.
Fig. 87. Internet Explorer browser: no JRE installed
If user allows to search for related plugin, a specific operation could be started (following Fig. 88. ).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
199 / 232 3DB 75003 BAAA Ed.01
APPENDICES
Fig. 88. Firefox plugin search
And if the user agrees, the browser could automatically install the correct plugin (see following Fig. 89. ).
Since this operations is specifically related to Mozilla Firefox browser, some details could be different with
respect to used version. Anyway, since this operation is automatically managed by the browser no control
can be made through TCO Suite. Using this procedure will usually install the latest JRE version available
as Mozilla Firefox plugin that is usually newer than the JRE version available within the TCO Suite.
Fig. 89. Firefox plugin installation
As stated before, graphical layout, language, information, alert boxes and everything shown by a browser
would differ from each browser and operating system version or release.
Then, when Java applets and the Start.html page finally goes for a complete execution, the user will
see the content shown in Fig. 10. on page 47
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
200 / 232
APPENDICES
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
201 / 232 3DB 75003 BAAA Ed.01
APPENDICES
23 APPENDIX C: LLMAN INSTALLATION, CONFIGURATION AND USE
This Appendix explains the operations to be done on the PC to allow the NE management through the NEs
F serial port.
Subject On page
Foreword below
Important warnings below
Procedure summary 202
Installation of LLMAN from the SWP TCO SUITE CDROM 203
Operations sequence 203
Functions and helps available after the LLMAN installation 206
Installation and configuration of a Virtual Network adapter for LLMAN 207
Foreword 207
Operations sequence, according to Windows platform 208
Lower Layer settings 210
Check/set the Network Connections order 212
How to start and use the LLMAN application 213
LLMAN startup with 1320CT 214
LLMAN startup with WebEML 214
Full information regarding the use of the LLMAN application 216
23.1 Foreword
This procedure is necessary only when you need to use the NEs F serial port to manage the NE itself or
any other NE accessible from it, by the WebEML functions.
N.B. Performing this procedure is not necessary if you want to use the WebEML functions, accessing
the local NE through its Ethernet interface only.
N.B. These installation operations require the PC Administrator privileges
23.2 Important warnings
Warning for Windows Vista, on page 206
Warning about the Network Connections order, on page 212
Warning about the PC settings, on page 213
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
202 / 232
APPENDICES
23.3 Procedure summary
N.B. if you are performing this procedure following step 9 ) on page 189 , you have still the
Advanced Settings screen open ( Fig. 78. on page 186 ); in this case continue from step 6 )
below.
Otherwise, begin from step 1 ) below.
2 ) insert the SWP TCO SUITE CDROM in your PC
3 ) if never done previously, the startup of the SWP TCO SUITE is performed automatically (it installs,
if necessary, the JRE required version), and the Main Menu screen opens ( Fig. 10. on page 47
):
N.B. in case of problems, or for details, refer to Appendix B on page 191 (in particular, take
into account that the installation of the JRE requires the PC Administrator privileges)
4 ) click on Advanced Settings button
5 ) the Advanced Settings screen opens ( Fig. 78. on page 186 )
6 ) install LLMAN (AlcatelLucent Lower Layers Manager), as described in para.23.4 from page 203
7 ) Install and configure a Virtual Network Card for LLMAN, as described in para.23.5 from page
207
8 ) perform the settings for the Lower Layer, as described in para.23.6 from page 210
9 ) check/set the Network Connections order, as described in para.23.7 from page 212
Only after having executed all operations stated above, you can use the LLMAN application, as described
in para.23.8 from page 213
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
203 / 232 3DB 75003 BAAA Ed.01
APPENDICES
23.4 Installation of LLMAN from the SWP TCO SUITE CDROM
N.B. these installation operations require the PC Administrator privileges.
23.4.1 Operations sequence
1 ) In the SWP TCO SUITE CDROM Advanced Settings screen ( Fig. 78. on page 186 ), click on
button SerialFInterface Driver Installation
This function performs the installation for the Alcatel Lower Layers Manager together with the
drivers needed for the Alcatel Virtual Network Card for Lower Layers and the help documentation
(a splash screen will appear as soon as the button applet is clicked and the installation begins).
2 ) User is asked to select installation and application language:
3 ) In subsequent screen, click on Next button
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
204 / 232
APPENDICES
4 ) If a previous version of LLMAN is not found, the installation of LLMAN is performed: see next step
5 )
If a previous version of LLMAN is found, the following screen appears:
Leave the choice upgrade selected, then click on Next button.
This causes:
at first, the uninstallation of the previous version:
and, secondly, after having clicked OK button, the installation of the new version of LLMAN:
see next step 5 )
N.B. the new version of LLMAN is fully compatible with all 1320CTbased applications.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
205 / 232 3DB 75003 BAAA Ed.01
APPENDICES
5 ) After the installation completion, the screen below appears.
In this screen deselect the choice Configure Lower Layer (this operation can be done only after the
installation and configuration of the Virtual Network Card, as described in para.23.6 on page 210),
then click on Finish button.
N.B. if you leave selected the choice Display the network component setup help, the screen
of Fig. 91. on page 208 opens.
Please note that, for the correct configuration process, you are strongly
suggested to open this help, and to perform all operations in the stated
sequence.
You have now completed the Installation of LLMAN from the TCO SUITE CDROM.
You do no longer need to use the TCO SUITE CDROM, that can be extracted from the PC.
Now, please read information in next para.23.4.2 on page 206
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
206 / 232
APPENDICES
23.4.2 Functions and helps available after the LLMAN installation
Fig. 90. below (Windows XP example) shows the LLMAN functions available after the installation of
LLMAN, performed in previous para.23.4.1 on page 203
The Help files contain all necessary information to install and configure a Virtual Network Card, so that,
in the following, only reference to them is given, without repeating their contents.
A
B
C
Functions and helps usage sequence:
A: see para.23.5 from page 207
B: see para.23.6 from page 210
C: see para.23.8 from page 213
Fig. 90. Available LLMAN functions and helps
IMPORTANT WARNING FOR WINDOWS VISTA
The help files listed above have the .hlp extension
In native mode, Windows Vista does no longer support such files.
To view .hlp files on Windows Vista, you need to install the application WinHlp32.exe
To download it, connect to www.microsoft.com/downloads , and look for it.
Now, you must proceed with para.23.5 on page 207
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
207 / 232 3DB 75003 BAAA Ed.01
APPENDICES
23.5 Installation and configuration of a Virtual Network adapter for LLMAN
N.B. these installation and configuration operations require the PC Administrator privileges.
23.5.1 Foreword
After the installation of LLMAN (performed in previous para.23.4 on page 203 ), it is necessary to install
and configure a Virtual Network Card.
In fact, AlcatelLucent Lower Layers Manager, in order to manage IP packets over its point to point links
(either Serial port or Modem), uses a virtual (i.e. software) network adapter.
This virtual network adapter, depending on the operating system as described in next para.23.5.2 on
page 208 , can be:
the Microsoft Loopback adapter; in this case, also the Logical Link Control Protocol for
AlcatelLucent Lower Layers must be installed
or the AlcatelLucent Virtual Network Card for Lower Layers.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
208 / 232
APPENDICES
23.5.2 Operations sequence, according to Windows platform
1 ) Do Start % Programs % AlcatelLucent % Lower Layers % Lower Layers IP Manager Setup
Help ( Fig. 90. on page 206 ), and then display the first document: screen of Fig. 91. below opens.
Fig. 91. Start page of Lower Layers IP Manager Setup Help
According to the Windows platform of your PC, choose the proper help, and strictly follow it, to install
and configure the Virtual Network Card.
If you have installed and configured:
the Microsoft Loopback adapter, you must proceed with next step 2 ) on page 209
the AlcatelLucent Virtual Network Card for Lower Layers, you must proceed with
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
209 / 232 3DB 75003 BAAA Ed.01
APPENDICES
2 ) If, in previous step 1 ) on page 208 , you have installed and configured the Microsoft Loopback
adapter, now you must install and configure the Logical Link Control Protocol for AlcatelLucent
Lower Layers.
To do that, perform Start % Programs % AlcatelLucent % Lower Layers % Lower Layers LLC
Protocol Setup Help ( Fig. 90. on page 206 ), and then display the first document: screen of
Fig. 92. below opens.
Fig. 92. Start page of Lower Layers LLC Protocol Setup Help
According to the Windows platform of your PC, choose the proper help, and strictly follow it, to install
and configure the Lower Layers LLC Protocol.
Then you must proceed with para.23.6 on page 210
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
210 / 232
APPENDICES
23.6 Lower Layer settings
N.B. the setting operation requires the PC Administrator privileges. Just reading information, does
not require them.
Having followed the instructions given in the previous paragraphs of this Appendix, you have installed and
configured the virtual network adapter proper for the Windows platform of your PC.
Now you must associate such a virtual network adapter to the PCs RS232 serial port (COMx) that will be
used for the PCNE physical connection.
To do that, perform Start % Programs % AlcatelLucent % Lower Layers % Lower Layers Settings
( Fig. 90. on page 206 ): screen of Fig. 93. below opens.
Fig. 93. Lower Layers Settings screen
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
211 / 232 3DB 75003 BAAA Ed.01
APPENDICES
To fill properly the fields of the Lower Layers Settings screen, click its Help button, which opens the
associated help ( Fig. 94. below), and proceed as specified:
Fig. 94. Start page of Lower Layers Settings Help
N.B. This help can be also obtained performing Start % Programs % AlcatelLucent % Lower
Layers % Lower Layers Settings Help ( Fig. 90. on page 206 )
Now, you must proceed with para.23.7 on page 212
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
212 / 232
APPENDICES
23.7 Check/set the Network Connections order
For the SWP to operate correctly, it is necessary that the Virtual Network Card (that you have associated
to the PCs RS232 serial port in previous para.23.6 on page 210 ) is always the first one in the Network
Connections list.
To perform this check, operate as follows (example for Windows XP):
1 ) Start Control Panel Network Connections
2 ) in the field LAN or High Speed Internet, select the Device Name that has been assigned in
the Lower Layers Settings screen ( Fig. 93. on page 210 ) , e.g. Alcatel Virtual Network Card
for Lower Layers
3 ) from Advanced menu, select Advanced Settings
4 ) in the relevant screen (Fig. 95. below) verify that it is the first in the list. If necessary, move its
position, using suitable arrows.
Fig. 95. Check for the Network Connections order
WARNING: Whenever, after the completion of this installation and configuration procedure, you must
install a new network card, always verify that this Virtual Network Card is always the first
one in the Network Connections list.
End of procedure: you have completed the installation, configuration and check of the Virtual Network
Card for Lower Layers.
The LLMAN application is now available. To use it, refer to next para.23.8 on page 213
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
213 / 232 3DB 75003 BAAA Ed.01
APPENDICES
23.8 How to start and use the LLMAN application
LLMAN can be started only if you have successfully executed all operations described in previous
paragraphs of this Appendix.
LLMAN must be started before the start of the WebEML (which, in turn, opens the NEtO screen), or before
the start of the 1320CT (which, in turn, opens the NES screen).
WARNING: After the LLMAN startup, during system hibernate or standby, the LLMAN could not
working correctly after reentering the system.
So, when using LLMAN, it is mandatory that the PC desktop Properties System standby
and System hibernates are both set to Never, as shown in Fig. 96. below:
(1)
(2)
(3)
Fig. 96. PC desktop Properties settings for LLMAN
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
214 / 232
APPENDICES
23.8.1 LLMAN startup with 1320CT
In this case, if necessary, LLMAN is started automatically. It can also be started manually, as described
in para.23.8.2 below.
23.8.2 LLMAN startup with WebEML
In this case LLMAN must be started manually. To do that, perform following operations:
1 ) From WINDOWS screen, start LLMAN performing Start % Programs % AlcatelLucent % Lower
Layers % Lower Layers Manager ( Fig. 90. on page 206 )
2 ) LLMAN starts, and its animated symbol appears in operating system tray bar.
This animated icon indicates the communication status:
if the physical link between the computer and the equipment is missing, the red icon
appears;
during the attempts to establish the communication between the computer and the connected
equipment, the yellow icon appears;
while the communication between the computer and the connected equipment is established,
the AlcatelLucent icon appears.
In this case, doubleclick on the icon, to open the LLMAN screen: see next step 3 )
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
215 / 232 3DB 75003 BAAA Ed.01
APPENDICES
3 ) Main fields and command buttons of the LLMAN screen
Green link led means
connection
established on the
serial link
Local IP address of NE
connected to the PC
serial port (or
USB/RS232 adapter)
Closes the screen (but not
the LLMAN program)
Closes the
LLMAN program
Fig. 97. LLMAN screen
4 ) Click on Close button to close the screen, leaving the LLMAN program running.
Now you can start NEtO (or 1320CT) using the NEs F interface.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
216 / 232
APPENDICES
23.8.3 Full information regarding the use of the LLMAN application
Clicking on the Help button of LLMAN screen ( Fig. 97. above), the relevant full help is opened; explore
it to find information not given in this Appendix.
N.B. This help can be also obtained performing Start % Programs % AlcatelLucent % Lower
Layers % Lower Layers Manager Help ( Fig. 90. on page 206 )
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
217 / 232 3DB 75003 BAAA Ed.01
APPENDICES
24 APPENDIX D: ECTEQUIPMENT CONNECTION VIA PUBLIC
SWITCHED TELEPHONE NETWORK
Subject On page
Introduction below
Certified equipment 218
Connection cables 219
Modem setting 220
Setting of Sportster Flash Modem & 3Com 56K Faxmodem 220
TD32 AC Modem setting 222
PC laptop Dell Latitude setting 223
Setting up the connection 224
Changing the ECTequipment connection speed 225
Introduction 225
Configuration at NE side 225
Configuration at PC side 226
24.1 Introduction
This chapter explains the operations necessary to allow the remote connection to the FInterface, from
a local PC (with external or internal modem) configured as ECT, through a switched telephone line of the
standard Public Telephone Network, as shown in Fig. 98. here below.
This kind of remote control is possible for a single equipment as well as for a whole subnetwork.
Telephone net-
work
PC/ECT
remote side
(equipment side)
Remote
Modem
Local
Modem
F Interface
Port COM
PCLAPTOP/ECT
with internal modem
local side
(ECT side)
Fig. 98. ECTEquipment connection via Public Switched Telephone Network
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
218 / 232
APPENDICES
24.2 Certified equipment
The connection has been successfully tested:
a ) with the following types of modems:
1 ) Modem Sportster Flash (US Robotics)
2 ) Modem TD32 AC (Westermo Teleindustri AB)
3 ) 3Com 56K Faxmodem
b ) with the following types of PC:
1 ) with external modem:
characteristics as in para.11.3 on page 15
2 ) with internal modem:
PC laptop Dell Latitude:
Processor equipped: PENTIUM III
Operating system: Microsoft Windows 2000 v. 5.00.2195 service pack 2
RAM equipped: 128 Mbytes
Hard disk equipped: 10 Gbytes
Internal Modem: 3COM 56K v.90 Mini PCI MODEM
c ) and with the following local/remote combinations:
Local Modem Remote Modem
Sportster Flash
Sportster Flash TD 32 AC
3Com 56K Faxmodem
TD 32 AC
TD 32 AC Sportster Flash
3Com 56K Faxmodem
TD 32 AC
PC laptop Dell Latitude as in
point b ) 2 ) above
Sportster Flash
point b ) 2 ) above
3Com 56K Faxmodem
Testing the connection with different types of modems is fully on Customers charge.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
219 / 232 3DB 75003 BAAA Ed.01
APPENDICES
24.3 Connection cables
In the following figures, the cables for the connections are described:
PC/ECT (DTE)
Cannon 9 pins female
Local Modem (DCE)
Cannon 25 pins male
DCD
TD
RD
DTR
DSR
RTS
CTS
GND
DCD
TD
RD
RTS
CTS
DSR
DTR
GND
1
3
4
6
7
8
5
8
5
6
20
7
2
3
4
2
Fig. 99. ECTLocal external Modem cable

Remote Modem (DCE)
Cannon 25 pins male
F Interface (DCE)
Cannon 9 pins male
TD
RD
RTS
CTS
DSR
CTS
GND
TD
RD
RTS
CTS
DSR
DTR
GND
2

3
4
5
6
20
7
3
2
7
8
6
5
4
Fig. 100. F InterfaceRemote Modem cable
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
220 / 232
APPENDICES
24.4 Modem setting
24.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. 98. on page 217 for the
distinction between local and remote), relevant to the autoanswer option that must be set in the remote
modem and not set in the local modem.
LOCAL MODEM SETTING
To set the local modem, proceed as follows:
1 ) Only for external modem: connect the local modem to the PC/ECT with the cable of Fig. 99. on
page 219.
2 ) Only for external modem: Power and switch on the local modem.
3 ) On the PC, activate program HyperTerminal and configure the PCModem serial line with the
following parameters:
* Bits per second: 38400
* Data Bits: 8
* Parity: None
* Stop Bit: 1
* Flow control: None
4 ) Execute and store the modem setup, writing the following commands in the HyperTerminal
program window:
AT&F1<Return> (Best PC default configuration recall)
ATT<Return> (Tone Dialling instead than Pulse Dialling)
ATX3<Return> (Second Signal disabling, avoids problems with PABX)
AT&W0<Return> (Configuration store in NVRAM 0)
5 ) Now, setting has been completed. External Modem can be switched off and disconnected, if
necessary.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
221 / 232 3DB 75003 BAAA Ed.01
APPENDICES
N.B. For confirmation, the modem configuration can be checked writing the command
ATI4<Return> in the HyperTerminal program window.
Information displayed should be as follows:
ATI4
U.S. Robotics Sportster Flash 56000 Settings...

B0 E1 F1 L2 M1 Q0 V1 X3 Y0
BAUD=38400 PARITY=N WORDLEN=8
DIAL=TONE OFF LINE CID=0

&A3 &B1 &C1 &D2 &H1 &I0 &K1
&M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1

S00=000 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004
S07=060 S08=002 S09=006 S10=014 S11=072 S12=050 S13=000
S15=000 S16=000 S18=000 S19=000 S21=010 S22=017 S23=019
S25=005 S27=001 S28=008 S29=020 S30=000 S31=128 S32=002
S33=000 S34=000 S35=000 S36=014 S38=000 S39=012 S40=000
S41=004 S42=000

LAST DIALED #:
REMOTE MODEM SETTING
To set the remote modem, proceed as follows:
a ) carry out same steps 1 ) , 2 ) , 3 ) as for local modem setting
b ) execute and store the modem setup, writing in the HyperTerminal program window the same
commands described in step 4 ) for the local modem setting, and adding the following command:
ATS=1<Return> (Autoanswering setting)
c ) now, setting has been completed. Modem can be switched off and disconnected, if necessary.
ATI4<Return> in the HyperTerminal program window.
Information displayed should be equal to that displayed for the local modem, with only the
difference for field S00:
S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
222 / 232
APPENDICES
24.4.2 TD32 AC Modem setting
This modem requires an initial HW setup via dipswitches and a SW setting via serial port.
To set the modem, both local and remote, proceed as follows:
1 ) The initial HW setup via dipswitches is indicated in Fig. 101. herebelow:
ON
SW3
1 2 3 4 5 6 7 8
ON
SW2
1 2 3 4 5 6 7 8
ON
SW1
1 2 3 4
ON
SW5
1 2 3 4 5 6 7 8
ON
SW4
1 2 3 4 5 6 7 8
Fig. 101. TD32 AC modem dipswitch setting
2 ) Connect the local modem to the PC/ECT with the cable of Fig. 99. on page 219.
3 ) Power on the local modem (there is no an ON/OFF switch).
4 ) On the PC, activate program HyperTerminal and configure the PCModem serial line with the
following parameters:
* Data Bits: 8
* Parity: None
* Stop Bit: 1
5 ) Execute and store the modem setup, writing the following commands in the HyperTerminal
program window:
AT&F1<Return> (Best PC default configuration recall)
AT&K0<Return> (DTE/DCE flow control disabling)
ATA<Return> (Automatic Answer enabling > Only on Remote modem and
wait the message NO CARRIER)
AT&W0<Return> (Configuration store in NVRAM 0)
AT&Y0<Return> (Configuration Set to load at switchon: NVRAM 0)
6 ) Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
223 / 232 3DB 75003 BAAA Ed.01
APPENDICES
AT\S<Return> in the HyperTerminal program window.
Information displayed should be as follows:
AT\S

CMD DESCRIPTION / OPTION CMD DESCRIPTION / OPTION CMD DESCRIPTION / OPTION

COUNTRY...........IT &A CHR ABORT OPT.....NO *H NEG. SPEED......HIGH
DTE BPS........38400 &B DTR DIAL OPTION...NO S0 RINGS TO ANS.....002
DTE PARITY.....8NONE &C DCD OPTION........ON S1 RING COUNT.......000
LINE SPEED......NONE &D DTR OPTION.........0 S2 <ESC> CHAR.......043
B BELL MODE........OFF &G GUARD TONE......NONE S3 <CR> CHAR........013
E CMD ECHO..........ON &K FLOW CONTROL....NONE S4 <LF> CHAR........010
F LINE MODE.......AUTO &L NETWORK.........PSTN S5 <BS> CHAR........008
L SPKR VOLUME......LOW &Q ASYNC/SYNC.........5 S7 CONNECT TIME.....060
M SPKR CONTROL....CALL &R RTS/CTS.........AUTO S8 PAUSE TIME.......002
N AUTO MODE.........ON &S DSR OPT............0 S12 ESC GUARD TIME...050
Q QUIET............OFF &T ENABLE RDL........NO S30 CONNECT INACT....000
V RESULT FORM.....LONG &X SYNC CLOCK.......INT S32 XON CHAR.........017
W EC MSG.............0 &Y PROFILE........NVM.0 S33 XOFF CHAR........019
X EXT RESULTS........4 \A MAX BLK SIZE.....192 S36 FALLBACK ACTION..007
Y LONG SPACE DISC...NO \G REMOTE FLOW......OFF S37 MODE SELECT......000
%C COMPRESSION.....BOTH \K BRK OPT............5 S48 V42 NEG CTRL.....007
K EXT. SERVICES......0 \N ECL MODE........AUTO S95 RES. CODE........000
24.5 PC laptop Dell Latitude setting
The following setting must be done:
Control Panel > Alcatel Lower Layer > Serial port > COM3 and Serial port selected
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
224 / 232
APPENDICES
24.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. 98. on page 217 for the distinction between local and remote modems.
N.B. Leaving the remote modem permanently switched on and permanently connected to
Finterface and telephone line, operations set up by steps from 1 ) to 4 ) , it is possible to
access the equipment in any moment.
In order to access the equipment by local ECT, proceed as specified in steps 5 ) thru 14 ) .
1 ) Connect the remote modem to equipments F interface with the cable of Fig. 100. on page 219.
2 ) Connect the remote modem to the telephone line (as far as Sportster Flash model is concerned,
the connector to be used is the nearest to that used for the connection with equipments F
interface and signed with the wall symbol).
3 ) Power and switch on the remote modem.
4 ) Be sure remote equipment is switched on and correctly working.
5 ) Connect the local modem to the PC/ECT (with the cable of Fig. 99. on page 219.) on the serial
port assigned for the connection with F interface (usually COM1).
6 ) Connect the local modem to the telephone line (as far as Sportster Flash model is concerned,
the connector to be used is the nearest to that used for the connection with equipments F
interface).
7 ) Power and switch on the local modem.
8 ) On the PC, activate program HyperTerminal and configure the PCLocal Modem serial line with
the following parameters:
* Data Bits: 8
* Parity: None
* Stop Bit: 1
9 ) For PC laptop Dell Latitude only, type the following command inside HyperTerminal program:
AT&C0&D0&R1
N.B. this command must be typed every time the Hyper terminal session is opened (this
command is not stored in the modem NV RAM).
10 ) Execute the telephone call from the PC writing the following command in the HyperTerminal
program window:
ATDnnn<Return>
where nnn is the telephone network number associated to the remote telephone line (that
which the remote modem is connected to).
11 ) Wait the message indicating the successful connection between local and remote modems.
N.B. The message text depends on the modem type, as follows:
CONNECT 14400/ARQ/V32/LAPM/V42BIS (Sportster Flash)
CONNECT 38400 (TD 32 AC)
12 ) Close HyperTerminal program.
13 ) Activate the ECT applicative SW as usual.
14 ) At the end of the job, after having logged out from the ECT applicative SW, close the connection
between local and remote modems, switching off the local modem or physically disconnecting
the cable connecting it to the PC.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
225 / 232 3DB 75003 BAAA Ed.01
APPENDICES
24.7 Changing the ECTequipment connection speed
24.7.1 Introduction
This feature is meant to use modems with speed different from that documented in previous paragraphs,
giving the possibility to configure the ECT connection through modem (speed values: 9600, 19200, 38400,
56000) with automatic management of modem setup and phone call at ECT startup.
To make change operative, the following operations are necessary:
at equipment side, the configuration must be setup as explained in the para.24.7.2 below,
at PC side, the configuration must be setup as explained in the following para.24.7.3 on page 226,
as far as the modem is concerned, please refer to the constructor documentation.
24.7.2 Configuration at NE side
1 ) Login the NE through the Alarms & Settings function (see chapter 16 from page 65 ) using
a login profile allowing the Modem Speed change (see Tab. 7. on page 67 ),
2 ) enter the Modem Speed screen and set the required speed (see para.16.2.7 on page 77).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
226 / 232
APPENDICES
24.7.3 Configuration at PC side
To configure the modem with the relevant speed, enter the menu Settings > Control Panel of the
Operating System and open the Alcatel Lower Layers utility. The menu of Fig. 102. opens.
Fig. 102. Alcatel Lower Layers utility
In the Subnetwork Type field select Modem.
In the Modem field select the suitable Modem type.
In the Modem speed field select the suitable speed (9600, 19200 or 38400) and click on OK.
In the Phone Number field enter the phone number, which will be automatically called at the ECT startup.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
227 / 232 3DB 75003 BAAA Ed.01
APPENDICES
25 APPENDIX E: SWP TCO SUITE Rel.1.7 DEINSTALLATION
This Appendix describes how to deinstall from the PC the SWP TCO SUITE components.
a ) Deinstallation of Local copy of TCO Suite and of Local copy of WebEML
1 ) Delete from the desktop the shortcuts created in steps 7 ) and 8 ) on pages 187 and 188
2 ) Restart the PC
3 ) Delete the folder created in step 2 ) on page 185
b ) Deinstallation of Alcatel Lower Layers Manager & Tiny Tools
These components have been installed as described in Appendix C on page 201
Before deinstalling them, be sure that they are not used by other still existing applications (e.g. other
AlcatelLucent 1320CTbased or NEtObased applications).
From Control Panel select Add/Remove Programs and deinstall the related components.
c ) Deinstallation of JRE
The JRE (version required for SWP TCO SUITE Rel.1.7) has been installed as described in Appendix
B on page 191
Before deinstalling it, be sure that it is not used by other still existing applications.
From Control Panel select Add/Remove Programs and deinstall the related component.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
228 / 232
APPENDICES
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
229 / 232 3DB 75003 BAAA Ed.01
APPENDICES
26 APPENDIX F: CUSTOMER DOCUMENTATION FEEDBACK
The meaning of this appendix is to collect customer feedback about this handbook.
Scope of this activity is the improvement and innovation of customer documentation through the
understanding of customer needs.
Your comments are welcome.
Please send your comment also if you appreciate the handbook.
You can send them to your Local Alcatel Technical Assistance Center.
They will be addressed to the team in charge of the relevant manual.
The following form supplies an example only of useful info, as a guide of the type of expected feedback.
It is possible fill part of the form, add other data and so on.
How to send feedback:
copying the example form, filling it and sending it to your Local Alcatel Technical Assistance
Center. In this case handbook data are already available at the page bottom.
using the same form (if available) as a file in the relevant documentation CDROM, saving,
filling and sending it by email to your Local Alcatel Technical Assistance Center.
creating a dedicated form on paper or file and sending it to your Local Alcatel Technical
Assistance Center.
We will take into account of your suggestion.
We reserve to modify consequently the handbook according to the correctness and congruence of the
suggestion and requests.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
230 / 232
APPENDICES
CUSTOMER DOCUMENTATION FEEDBACK
Handbook data
Product release, version: SWP TCO SUITE Rel.1.7
Handbook type: USER MANUAL
Handbook part number and edition: 3DB 75003 BAAA Ed.01
General evaluation
SUBJECT 5 (max.) 4 3 2 1 (min.)
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Section evaluation
SECTION 5 (max.) 4 3 2 1 (min.)
Front matter
1 : TCO SUITE DESCRIPTION AND USAGE
2 : APPENDICES
Your comments (strictly necessary when value is less than 3)
Suggestion for improvements
Which subject to deepen:
How to deepen:
Subject to eliminate or reduce:
Other comments/suggestions:
Error identified
Reader Info
Name: Date;
Company: Job:
Address:
Email:
Phone: Fax:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s
d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t
p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
L
u
c
e
n
t
231 / 232 3DB 75003 BAAA Ed.01
APPENDICES
INFORMATION FOR ALCATELLUCENT INTERNAL USE ONLY
ED
DATE
(yymmdd)
CHANGE NOTE
(ECO)
APPRAISAL AUTHORITY ORIGINATOR
01 090312 C.Wenyu, T.Pinaud E.Corradini
Editorial information: refer to the last section of the *REVBAR.pdf file present in the zipped source file
folder archived in PDM.
All rights reserved
Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel Lucent.
www.alcatellucent.com
233 / 232 3DB 75003 BAAA Ed.01
Handbook print & assembly
THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK
QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
COD.MANUALE HDBK P/N: 3DB 75003 BAAA Ed.01
for 9400AWY R.2.0 V2.0.6 and 9400AWY R.2.1 V2.1.2
USER MANUAL
HANDBOOK PRINT AND ASSEMBLY INSTRUCTIONS
ISTRUZIONI DI STAMPA ED ASSIEMAGGIO DEL MANUALE
COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:
HANDBOOK COMPOSITION AND ASSEMBLY:
SERVONO 2 SEPARATORI NUMERATI DA 1 A 2
2 SEPARATORS NUMBERED FROM 1 TO 2 ARE NECESSARY
STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
fase
step
No pagine
(facciate)
numerate
numbered
step
(facciate)
No pages
da from a to
1
TARGHETTE - LABELS
Fig. 1. pg. 234
2 PARTE INIZIALE - FRONT MATTER 1/232 10/232
3 INSERIRE SEPARATORE 1 - INSERT SEPARATOR 1
4 SECTION 1 : TCO SUITE DESCRIPTION AND USAGE 11/232 182/232
5 INSERIRE SEPARATORE 2 - INSERT SEPARATOR 2
6 SECTION 2: APPENDICES 183/232 232/232
fine istruzioni assemblaggio end of assembly instructions
234 / 232
Handbook print & assembly
TCO SUITE Rel.1.7
USER MANUAL
VOL.1/1
TCO SUITE Rel.1.7
USER MANUAL
VOL.1/1
TCO SUITE Rel.1.7
3DB 75003 BAAA Ed.01 USER MANUAL VOL.1/1
TCO SUITE Rel.1.7
3DB 75003 BAAA Ed.01 USER MANUAL VOL.1/1
TCO SUITE Rel.1.7
USER MANUAL
VOL.1/1
Fig. 1.
END OF PRINT INSTRUCTIONS FINE DELLE ISTRUZIONI DI STAMPA

Alcatel Tco Suite Rel.1.7 For 9400awy r.2.1 v2.1.3 User Manual PDF

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Alcatel Tco Suite Rel.1.7 For 9400awy r.2.1 v2.1.3 User Manual PDF

Caricato da

Copyright:

Formati disponibili

AlcatelLucent TCO Suite

SWP TCO SUITE Rel.1.7

[Active SW Package: R94A V02.01.03]

NE Configuration Type:1+1 HSB 16E1 GETH (PSU4860) EPS

Impedance: Balanced 120 Ohm

[Ethernet Port 33]

Radio Protection: Revertive

Expected Mode: Disabled

Potrebbero piacerti anche