1353nm70 Oh Eng Ed03

3AL 89061 AAAA Ed.
03
Operators Handbook
Alcatel 1350
Management Suite
1353NM Rel.7.0
Element Management application for Alcatel Optical and
Radio transport networks
Version 7.0
VOLUME 1/1:
Map management and network
administration utilities
3AL 89061 AAAA Ed.03
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
1
03

SC.1: HANDBOOK GUIDE

/ 3AL 89061 AA AA

12
12

1353NM REL.7.0 OPERATORS HANDBOOK

TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 HANDBOOK STRUCTURE 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 General information 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 History 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Notes on Ed.01a 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2 Notes on Ed.01 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3 Notes on Ed.02 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 PRODUCT-RELEASE HANDBOOKS 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Handbooks related to the products software 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Handbooks related to the products hardware 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 List of NEs supported by 1353NM 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 1353NM REL.7.0 OPERATORS HANDBOOK DESCRIPTION 8 . . . . . . . . . . . . . . . . . . . . . . .
3 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Products, product-releases, versions and Customer Documentation 9 . . . . . . . . . . . . . .
3.2 Handbook supply to Customers 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Aims of standard Customer Documentation 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Handbook Updating 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Changes introduced in the same product-release (same handbook P/N) 10 . . . . . . . . . . . .
3.4.2 Supplying updated handbooks to Customers 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Changes due to a new product-release 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Customer documentation supply on CDROM 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1 Contents, creation and production of a CDROM 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2 Use of the CDROM 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3 CDROM identification 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.4 CDROM updating 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01A 040123
V.SCORTECCI ITAVE V.PORRO ITAVE
02 040728 SC04091002
050623 03 SC04091002
V.BALCONI ITAVE M.ARMANINI ITAVE
1353NM REL.7.0
VERSION 7.0
OPERATORS HANDBOOK
L.FORESTA
L.FORESTA
A.CORTESE L.FORESTA

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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
2
03


/ 3AL 89061 AA AA

12
12
LIST OF FIGURES AND TABLES
TABLES
Table 1. Handbooks related to the specific software application 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. Related Handbooks 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. Documentation on CDROM 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
3
03


/ 3AL 89061 AA AA

12
12
1 HANDBOOK STRUCTURE
1.1 General information
WARNING
ALCATEL 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. ALCATEL 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.
NOTICE
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 ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied,
reproduced or disclosed to a third party without written consent.
1.2 Handbook applicability
This handbook applies to the following product-releases:
PRODUCT ANV P/N
1353NM 3AL 89052 AAAA
PRODUCT RELEASE VERSION (N.B.) ANV P/N
1353NM 7.0 7.0 3AL 89053 AAAA
N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operators Handbooks) are not
modified unless the new software version distributed to Customers implies manmachine
interface changes or in case of slight modifications not affecting the understanding of the
explained procedures.
Moreover, should the screen prints included in the handbook contain the productreleases
version marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
4
03


/ 3AL 89061 AA AA

12
12
1.3 History
VERSIONS AS INTERNAL DOCUMENTS
Specified at the beginning of each section.
RELEASED VERSIONS (as 3AL 89061 AAAA handbook)
ED Creation Scope Archived
01A January 2004 Creation NO
01 April 2004 Creation YES
02 July 2004 Creation YES
1.3.1 Notes on Ed.01a
This handbook issue is relevant to 1353NM Rel.7.0 Version 7.0. validated software, which is conceived
for the management of Q3, SNMP, Q2 and QB3* Alcatel Network Elements supported by 1353NM.
This edition is not archived.
1.3.2 Notes on Ed.01
This handbook issue is relevant to 1353NM Rel.7.0 Version 7.0. validated software, which is conceived
for the management of Q3, SNMP, Q2 and QB3* Alcatel Network Elements supported by 1353NM.
This edition is officially archived.
1.3.3 Notes on Ed.02
It is the second officially released issue of the handbook. It includes:
Modification of FTS procedures;
Adding of new function: Ping NE from PNM application;
Adding of new external equipment management: OA512 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
5
03


/ 3AL 89061 AA AA

12
12
2 PRODUCT-RELEASE HANDBOOKS
The list of handbooks given here below is valid on the issue date of this Handbook and
can be changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available on the issue date of this
Handbook.
The standard Customer Documentation in the English language for the equipment whose
product-release-version is stated in para.1.2 on page 3 consists of the following handbooks:
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
6
03


/ 3AL 89061 AA AA

12
12
2.1 Handbooks related to the products software
Table 1. Handbooks related to the specific software application
REF HANDBOOK ANV Part No.
THIS
HANDBOOK
[1]
1353NM Rel.7.0
Operators Handbook
3AL 89061 AAAA
[2]
1353NM Rel.7.0
Administration Guide
3AL 89061 BAAA

Table 2. Related Handbooks
REF HANDBOOK ANV Part No.
THIS
HANDBOOK
[3]
1350 Rel.7.0
Installation Guide
3AL 88888 AAAA
[4]
1350 7.0 System Management
Operators Handbook
3AL 88874 AAAA
[5] PMDS 1.1 Users Guide 3AL 88875 AAAA
[6]
1330AS 6.5
Operators Handbook
3AL 88876 AAAA
[7]
ELB 2.X
Operators Handbook
3AL 88877 AAAA
[8] 1353NM NE LIST Handbook 3AL 89063 AAAA
[9]
1353NM NR5 Equipment Specific
Operators Handbook
3AL 89062 AAAA

Table 3. Documentation on CDROM
See para.3.5 on page 11
REF CDROM TITLE ANV Part No.
1353NM Rel.7.0 CDROMDOC EN 3AL 89059 AAAA
[10]
Contains, in electronic format, the following handbooks: REF.[1], REF.[2] and REF.[4] to [9].
Envisaged after the release of the handbooks.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
7
03


/ 3AL 89061 AA AA

12
12
2.2 Handbooks related to the products hardware
Refer to WS supplier handbooks.
In particular refer to such handbooks to obtain the following information (where applicable):
COMPLIANCE WITH EUROPEAN NORMS
SAFETY RULES
General rules
Harmful optical signals
Risk of explosion
Moving mechanical parts
Heatradiating Mechanical Parts
ELECTROMAGNETIC COMPATIBILITY
ELECTROSTATIC DISCHARGERS (ESD)
EQUIPMENT LABELS
2.3 List of NEs supported by 1353NM
The NE list has been moved in the NE LIST Handbook [8]. The NE LIST Handbook contains the different
NE lists of the SH Release and Software Version starting from Release 7.0.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
8
03


/ 3AL 89061 AA AA

12
12
2.4 1353NM REL.7.0 OPERATORS HANDBOOK DESCRIPTION
This handbook composed of one volume, is subdivided in the following sections:
SECTION 1: HANDBOOK GUIDE (this document)
The Handbook Guide gives general information on the application and use of the Handbook.
The Introduction Manual describes the main features of the graphical interface and provides a general
overview of the system architecture, the managed equipments and the different functionalities provided
by the 1353NM.
SECTION 2: GETTING STARTED
This document aims at introducing the 1353NM working environment, to the users of the system, in terms
of getting access to the system, the environment utilities, the existing 1353SH functionalities and
navigation through the system.
SECTION 3: TVA
The Topology Viewer Application (TVA) provides the user with: coherent views of a telecommunication
network in an intuitive graphical format, the integration of different network management applications in
a unique interface which uses an only one look and feel. The Telecommunication Network managed by
client applications is represented by TVA as a set of TVA objects as follows: topology objects like views,
equipment objects associated to Managed Elements (ME) like NEs (switches, adddrop multiplexers,
routers) and (topology and logical) links between NEs.
SECTION 4: PNM
PNM is devoted to the integration of EML (Element Management Layer) subsystems. That is, PNM
achieves the integrated management of various kinds of network elements (NEs) which are already
individually managed by their own EML subsystem.
SECTION 5: EML CONSTRUCTION
The aim of this document is to describe the operations related to the management of Maps, Submaps and
symbols within the 1353NM. The actions leading to the creation, edition, deletion, storage and listing of
Maps shall be indicated and the navigation through the necessary sequences of the Maps needed to
create the TN will be described.
Sufficient details on the addition, the removal and the selection of Network Element symbols are given to
enable an easy characterization of the network.
SECTION 6: PROCEDURES Manual
The aim of this document is to describe some procedures clarifying all the necessary items to achieve
specific functionalities and configuration. For the correct understanding of this Procedures Manual all the
commands described in the NM Operators Handbook have to be considered Known.
SECTION 7: OA512 management
The aim of this document is to describe the management of Omni Access 512 integrated in 1353NM
Subsystem.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
9
03


/ 3AL 89061 AA AA

12
12
3 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION
3.1 Products, product-releases, versions and Customer Documentation
A product is defined by the network hierarchical level where it can be inserted and by the whole of
performance and services for which it is meant.
A product evolves through successive product-releases which are the real products marketed for
their delivery at a certain product-release availability date.
So, a productrelease defines a set of hardware components and a software package which, as a whole,
identify the possible network applications and the equipment performance which the specific
product-release has been designed, engineered and marketed for.
In some cases a product-release has further development steps, named versions, that are born to
improve or add some performance (mainly software) with respect to the previous version, or for bug fixing
purposes.
A product-release has its own standard Customer Documentation, composed by one or more
handbooks.
A new version of a product-release may or may not produce a change in the status of the Customer
Documentation set, as described in para.3.4 on page 10.
3.2 Handbook supply to Customers
Handbooks are not automatically delivered together with the equipment they refer to.
The number of handbooks per type to be supplied must be decided at contract level.
3.3 Aims of standard Customer Documentation
Standard Customer Documentation, referred to hereafter, must be always meant as plant-independent.
Plant-dependent documentation, if envisaged by the contract, is subjected to commercial criteria as far
as contents, formats and supply conditions are concerned (plant-dependent documentation is not
described here).
Standard hardware and software documentation is meant to give the Customer personnel the possibility
and the information necessary for installing, commissioning, operating and maintaining the equipment
according to AlcatelTelecom Laboratory design choices.
In particular the contents of the handbooks associated to the software applications focus on the
explanation of the man-machine interface and of the operating procedures allowed by it.
Consequently, no supply to the Customers of design documentation (like software source programs,
programming tools, etc.) is envisaged.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
10
03


/ 3AL 89061 AA AA

12
12
3.4 Handbook Updating
The handbooks associated to the productrelease are listed in para.2 on page 5.
Each handbook is identified by:
the name of the product-release (and version when the handbook is applicable to the versions
starting from it, but not to the previous ones),
the handbook name,
the handbook P/N,
the handbook edition (usually first edition=01),
the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
3.4.1 Changes introduced in the same product-release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
only the date changes (pointed out in the Table of Contents) when modifications are made to the
editorial system not changing the technical contents of the handbook.
the edition, hence the date, is changed because modifications made concern technical contents. In
this case:
in each section, the main changes with respect to the previous edition are listed;
in affected chapters of each section, revision bars on the left of the page indicate modifications
in text and drawings (this is done after the first officially released and validated version).
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) or draft edition maintain the same edition but with
the addition of a version character (e.g. from Ed.02 to Ed.02A).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operators Handbooks) are not
modified unless the new software version distributed to Customers implies manmachine
interface changes or in case of slight modifications not affecting the understanding of the
explained procedures.
Moreover, should the screen prints included in the handbook contain the product-releases
version marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
3.4.2 Supplying updated handbooks to Customers
Supplying updated handbooks to Customers who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue
(supplying erratacorrige sheets is not envisaged).
3.4.3 Changes due to a new product-release
A new product-release changes the handbook P/N and the edition starts from 01. In this case the modified
parts of the handbook are not listed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
11
03


/ 3AL 89061 AA AA

12
12
3.5 Customer documentation supply on CDROM
In the following CDROM means Customer Documentation on CDROM
3.5.1 Contents, creation and production of a CDROM
In most cases, a CDROM contains the documentation of one productrelease(version) and for a certain
language.
In some other cases, the same CDROM can contain the documentation of different productrelease
(version)s for a certain language.
As a general rule:
CDROMs for Network Management products do not contain:
the Installation Guides
the documentation of system optional features that Customers could not buy from Alcatel
together with the main applicative SW.
CDROMs for Network Elements products do not contain:
the documentation of system optional features (e.g. System Installation Handbooks related to
racks that Customers could not buy from Alcatel together with the main equipment).
A CDROM is obtained collecting various handbooks and documents in .pdf format. Bookmarks and
hyperlinks make the navigation easier. No additional information is added to each handbook, so that the
documentation present in the CDROMs is exactly the same the Customer would receive on paper.
The files processed in this way are added to files/images for managing purpose and a master CDROM
is recorded.
Suitable checks are made in order to have a virusfree product.
After a complete functional check, the CDROM image is electronically transferred to the archive of the
Production Department, so that the CDROM can be produced and delivered to Customers.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
12
03


/ 3AL 89061 AA AA

12
12
3.5.2 Use of the CDROM
The CDROM can be used both in PC and Unix WS environments.
The CDROM starts automatically with autorun and hyperlinks from the opened Index document permit
to visualize the .pdf handbooks.
Other hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting documents.
In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must have been
installed on the platform.
The CDROM doesnt contain the Adobe Acrobat Reader program. The Customer is in charge of getting
and installing it.
ReadMe info is present on the CDROM to this purpose.
Then the Customer is allowed to read the handbooks on the PC/WS screen, using the navigation and
zooming tools included in the tool, and to print selected parts of the documentation through a local printer.
3.5.3 CDROM identification
Each CDROM is identified:
1 ) by the following external identifiers, that are printed both on the booklet and the CDROM upper
surface:
the name of the productrelease(s) (and version when the CDROM is applicable to
the versions starting from it, but not to the previous ones),
a writing indicating the language(s),
the CDROM P/N (ANV P/N),
the CDROM edition (usually first edition=01)
2 ) and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose
collection and processing the CDROM itself has been created.
3.5.4 CDROM updating
The list of source handbook/document P/Nseditions indicated in previous para. 3.5.3 point 2 ) , in
association with the CDROM own P/Nedition, is also loaded in the AlcatelInformationSystem as a
structured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system,
a check in the AlcatelInformationSystem is made to identify the list of CDROMs that must be updated
to include the new editions of these handbooks/documents.
This causes the planning and creation of a new edition of the CDROM.
Updating of CDROMs always follows, with a certain delay, the updating of the single handbooks
composing the collection.
END OF DOCUMENT
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
1
02

SC.2: GETTING STARTED

/ 3AL 89061 AA AA

64
64


TABLE OF CONTENTS
1 INTRODUCTION 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Document structure 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 SYSTEM ACCESS 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Logging in to the system 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Password expiration 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Workspace description 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Locking the screen 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Manual Lock 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Inactivity Timeout 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Logging out 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 THE MAIN FUNCTIONALITIES 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Access 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 The TMNOS 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 1353NM System Management 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 Alarm management 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 NE Construction Management 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 PMDS management functionality 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Quitting the 1353NM applications 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 System stop 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 VIEWS DESCRIPTION 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Equipment views description 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 NE (Network Element) view 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Board view 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 Port view 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 MAP NAVIGATION 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Root map navigation 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Hierarchical tree map navigation 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
01A 040123
02 040728 SC04091002
050623 03 SC04091002
V.BALCONI ITAVE V.PORRO ITAVE
1353NM REL.7.0
VERSION 7.0
OPERATORS HANDBOOK
L.FORESTA
L.FORESTA
A.CORTESE L.FORESTA

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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
2
02


/ 3AL 89061 AA AA

64
64
6 EQUIPMENT VIEW 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Open in Window command 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 NE Equipment views 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 Navigating to the Board View 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2 Navigating to the Port View 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3 Navigating to Management menu commands 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 NE ALARMS AND NE STATUS 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 NE Alarm. 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.1 Description 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.2 Propagation. 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 NE Status 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 Description 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 ONLINE DOCUMENTATION 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 Overview 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Help on help 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 Help on context 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 Glossary 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5 About the help version 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6 Tutorial 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 Navigation Bar 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
3
02


/ 3AL 89061 AA AA

64
64
FIGURES
Figure 1. Login panel view. 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. First time Password expiration 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Password expiration after a fixed interval time 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Password expiration when a presentation is not reachable 8 . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. The 1353NM workspace Front Panel. 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Locking the screen using a manual lock. 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Screen lock Password: entry box. 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Logging out using the front panel. 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. HPCDE Panel 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. TMNOS manager 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Accessing the 1353NM functionalities. 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Alarm Management view. 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. 1353NM map. 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. QB3* NE view. 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Q3 NE view example. 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Control panel alarm icon shapes. 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Per domain icon alarms 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Example of the contents of the message area of a QB3* NE view. 26 . . . . . . . . . . . . . . . . . .
Figure 19. Example of a QB3* NE Board view. 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Example of a Q3 NE Board view. 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Example of a detailed port view for QB3* NE. 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Example of a detailed port view for Q3 NE. 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. File: Local Pesistency: Restore map 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Question box 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Local Restore map selection box 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. 1353NM Map 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. NE popup menu. 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. NE Supervision popup menu 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Opening a view in a window 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Examples of Views menu 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Example of a Board view for a QB3* NE. 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Example of a Board view for a Q3 NE. 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Selecting a specific port view of a QB3* NE Board View. 43 . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Example of a QB3* NE Port View. 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Selecting a specific port view of a Q3 NE Board View. 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Example of a Q3 NE Port View. 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Alarm representation in the Equipment views. 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Obtaining help on help. 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Netscape Help Window 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Obtaining context sensitive help. 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Obtaining the glossary. 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Glossary help window 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Obtaining info about the help version. 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. About the help on version window 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Obtaining help home page 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Tutorial help window 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
4
02


/ 3AL 89061 AA AA

64
64
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
5
02


/ 3AL 89061 AA AA

64
64
1 INTRODUCTION
1.1 Scope
1.1.1 Document scope
The aim of this document is to introduce the 1353NM working environment. The access to the system,
the environment utilities and navigation ways through the system are descibed in detail. More detailed
information on PNM environment are given in the EML Construction manual.
1.2 Document structure
This document is composed of the following chapters:
Chapter 2: System Access. Introduces the first steps undertaken to access your working
environment
Chapter 3: Access to the main functionalities. Describes the workspace and the different subsystems
that can be accessed to.
Chapter 4: Views description. Gives a description of the Network topology and the Network
Equipment views.
Chapter 5: Navigation. Gives information about how to navigate among the different sub systems.
Chapter 6: Equipment View. Gives information about the Q3 and QB3* equipment window
reprentations.
Chapter 7: NE alarms and NE status. Gives information about the alarms and their propagation.
Chapter 8: On-line documentation. Explains the functioning of the online documentation you may
use in the SDH Manager system.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
6
02


/ 3AL 89061 AA AA

64
64
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
7
02


/ 3AL 89061 AA AA

64
64
2 SYSTEM ACCESS
2.1 Logging in to the system
This is the first operation you will have to undertake to access the system. The view that will greet you,
called the Login panel is presented below.
Login name
Entry box
Password
Entry box
Push buttons
Workstation
name
Figure 1. Login panel view.
To correctly access the 1353NM:
Enter your login name.
N.B. Your login name is assigned to you by the 1353NM administrator.
Enter your password.
After a correct login, the login view is replaced by a transition view giving certain software copyright
indications. This view is automatically replaced by the normal workspace view containing the Front Panel
from which you will be able to access the 1353NM functionalities.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
8
02


/ 3AL 89061 AA AA

64
64
2.2 Password expiration
This new login management, applied to the current SH network release, forces a new user, who is trying
at first time to login to the 1353NM system, to change the password (see Figure 2. ). The previous pass-
word is no more valid then clicking on Dismiss button the Change Password window opens and the
new password can be applied.
Figure 2. First time Password expiration
After a fixed interval time (expressed in days), depending on the operator profile, the operator password
expires and a new one is required. Thus during a new login session after entering user and password a
new password is required (see Figure 3.
Figure 3. Password expiration after a fixed interval time
Clicking on Dismiss button, the Change Password window opens and the new password can be ap-
plied.
If during the password expiration the masterpresentation connection is not alive, the new password is
not required. In this case, instead of Figure 3. , Figure 4. is shown and clicking on Dismiss button, the
login will be accepted. The password modification procedure requirement will be postponed to a next login,
until all workstation are alive.
Figure 4. Password expiration when a presentation is not reachable
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
9
02


/ 3AL 89061 AA AA

64
64
2.3 Workspace description
Your workspace is described as the functionalities that appear on your workstation screen after login.
The workspace Front Panel is described below.
Clock
Date
WS
activity
Terminal Letter
Padlock
Workspaces
Exit
File
Manager
Manager
Printer
Text
Editor
TMNOS
Figure 5. The 1353NM workspace Front Panel.
The components of this front panel are distributed across two rows.
Top row of the Front Panel (from left to right)
The Clock icon displays the current time on your workstation.
The Date display indicates the day and the date and enables you to access a calender.
The WS activity icon indicates the internal activity of the workstation.
The Help icon enables you to launch the help application.
The Padlock icon enables you to lock your workstation screen.
The Workspaces icons enable you to access different workspaces. There are only two available
workspaces (workspaces One and Two) used in the 1353NM product.
The Printer icon enables you to access the printing facilities. You can drag a file to the printer
icon to print it or simply access printer information.
The Letter icon gives access to the electronic mail service.
The File Manager icon gives you access to the files in your home directory.
The Terminal icon launches a hpterm command shell on your workspace.
The TMNOS System icon gives you access to the functionalities offered by the 1353NM
product for the management of the network.
Bottom row of the Front Panel (from left to right)
The ALCATEL logo icon gives access to information about the 1353NM product.
The Workspace naming icon enables you to rename your workspaces.
The Key icon launches the password modification application on your workspace enabling you
to change your password.
The EXIT icon launches the logout procedure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
10
02


/ 3AL 89061 AA AA

64
64
2.4 Locking the screen
This utility enables you to lock the screen to prevent other users from using your working environment.
Two ways of doing this are described below.
2.4.1 Manual Lock
lock
Figure 6. Locking the screen using a manual lock.
To lock the screen simply click on the small Padlock icon situated on the Front Panel described above.
The screen will lock immediately. The following figure will appear on the screen.
Username
Password Entry box
Figure 7. Screen lock Password: entry box.
To resume work type in your password in the Password: entry box.
2.4.2 Inactivity Timeout
During a work session, the screen will be automatically locked by the system, if you have not undertaken
any operations on it since a certain time. The parameters of the screen lock can not be configured (e.g.
the timeout period before the screen locks).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
11
02


/ 3AL 89061 AA AA

64
64
2.5 Logging out
Logging out from the workstation will automatically quit all graphical applications that you opened and give
place to the Login panel.
Use the Front Panel.
Click on the EXIT icon on the front panel, using the Select mouse button, as shown in the figure
below.
EXIT icon
Figure 8. Logging out using the front panel.
A dialogue box opens from which you can confirm or cancel the Logout operation.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
12
02


/ 3AL 89061 AA AA

64
64
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
13
02


/ 3AL 89061 AA AA

64
64
3 THE MAIN FUNCTIONALITIES
The access to 1353NM functionalities is described in the following paragraph.
3.1 Access
The graphical interface is based on:
HP Common Desktop Environment (HP-CDE)
OSF Motif applications
The HP_CDE Tool panel ( See Figure 9. ) has been customized to contain the TMNOS Manager
(righthand side).
Clock
Date
WS
activity
Terminal Letter
Padlock Workspaces
Exit
File
Manager
Manager
Printer
Text
Editor
TMNOS
Figure 9. HPCDE Panel
Clicking on the Manager icon you can open the TMNOS Management. ( See Figure 10. )
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
14
02


/ 3AL 89061 AA AA

64
64
3.2 The TMNOS
Figure 10. TMNOS manager
By clicking on the TMNOSs icon opens a window containing all the OSs icons, i.e. all the systems resident
on the server/ws. The colour of each icon depends on the OS process state:
green all the processes are running
red at least one process is not running
blue all the processes are stopped
yellow the process state is unknown. It may be due to a isolation condition.
The window contains a pulldown menu bar comprising the following menus:
File containing the only option Close to close the window
Edit containing the only option Clear Message area
View It allows to show/hide OS area orMessage area
OS
Start System. This submenu is present both for RM and NM. The Start option is available
if the selected OS is in the Stop state.
Stop System. This submenu is present both for RM and NM. The Stop option is available
if the selected OS is in the running state.
Both options are provided if the selected OS is in the Wrong state (partially stopped).
System Config. This submenu is available both for RM and NM. It allows to configure the
system in terms of processes
Process Monitoring. This submenu is available both for RM and NM. It opens the
Process Monitor window.
System Information. It gives information on the product actually installed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
15
02


/ 3AL 89061 AA AA

64
64
Actions (active only for resident Manager) containing a list of menus that vary
depending on the OS type (RM or NM) and on its actual status. The relevant OS icon must be
selected. The available submenus are:
1353NMAdmin. This submenu permits to launch the System Management applications:
Sec Administration; Ne Administration and Data Management.
Alarms. This submenu is only available for NM. It permits to launch the AS application.
SMF. It contains the following options:
Operator
Log
Trace
Failure
Scheduler
Backup
Restore
Cleanup
Topology Manager. It permits to launch the map application.
Command Log Viewer. It permits to launch the netscape to display logs.
Performance Monitoring. It permits to launch the Performance Monitoring display
window.
Global Actions (active only for resident Manager) It permits to launch the entire
system actions. It contains the following submenus:
Operator. It contains the following options:
Global Operators Administration
Change Password
Session management
Max Operator Logged Administration
Set Personal Printer
Synchronize Systems
Alarm Federations
The window contains a tool bar (active only for resident Manager) which allows to launch the most
frequently used applications. They are:
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
16
02


/ 3AL 89061 AA AA

64
64
EXIT
PERFORMANCE
MONITORING
ALARM
SURVEILLANCE
SYSTEM
CONFIG
PROCESS
MONITORING
SYSTEM
VERSION
1353NM
ADMIN
TOPOLOGY
MANAGER
Figure 11. Accessing the 1353NM functionalities.
Exit
System Config
Process Monitoring
System Configuration
1353NM Admin
Alarm Surveillance
Topology Manager
Performance Monitoring
N.B. Depending on your access rights, you may or may not have access to some of the management
functions described below. The management functions that you cannot access are represented
as greyed icons or greyed menu options.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
17
02


/ 3AL 89061 AA AA

64
64
3.2.1 1353NM System Management
N.B. This management function is reserved to the 1353NM System Administrator.
This submenu permits to launch the System Management applications: Sec Administration; Ne
Administration and Data Management.
3.2.2 Alarm management
This management functionality covers provision of information concerning alarm surveillance, and alarm
management such as displaying alarm lists and acknowledging alarms. The functionality is provided by
the Alarm Surveillance (AS) application.
To access this management functionality, click on the Alarm icon in the scrolling subpanel of Figure 11.
The main view of the alarm manager opens.
An example of the view that opens is shown below.
Figure 12. Alarm Management view.
For details on this management function refer to the Operation Manual Alarm Manager AS.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
18
02


/ 3AL 89061 AA AA

64
64
3.2.3 NE Construction Management
Topology Management
This management functionality is accessed from the TMNOS selecting the function Topology
Management.
NE Equipment Management
This management functionality covers configuration and manipulation of the NE using the Operating
System. The functionality is provided by the Element Management Layer User Service Manager
(EMLUSM) application.
To access this management functionality, select the NE in the Network Topology view by clicking on it with
the Select mouse button. The NE is highlighted. Open the Show Equipment option from the popup
menu.
3.2.4 PMDS management functionality
The operator can open the PMDS (Performance Monitoring Display) clicking on Performance icon. The
purpose of the PMV application is to present the performance data monitored on the TPs (termination
Points). The error counters data collection can be represented with textul reports and graphical 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
19
02


/ 3AL 89061 AA AA

64
64
3.3 Quitting the 1353NM applications
During normal operations, to quit the 1353NM applications you simply have to logout from your workspace
(see para. Logging out).
If you do not want to log out but simply close the applications, select the File: Exit option from the Network
Topology view.
A confirmation dialogue box opens from which you can confirm or cancel the Exit operation using the
Yes or No push buttons.
To only quit an equipment view, select the Close option from the Views pull down menu.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
20
02


/ 3AL 89061 AA AA

64
64
3.4 System stop
This section deals with what occurs when the 1353NM is stopped on your workstation (WS). The stopping
of the 1353NM applications on your workstations may be decided by the System Administrator following
a system crash.
Before stopping the 1353NM, you will be informed by the 1353NM system Administrator that there is an
ongoing 1353NM shutdown. You will no longer be able to launch operations on the 1353NM but you will
be given the opportunity to cleanly exit all the 1353NM applications before the 1353NM system shuts
down.
When the 1353NM is shutdown you are not logged out. The logout procedure is described in para. Logging
out.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
21
02


/ 3AL 89061 AA AA

64
64
4 VIEWS DESCRIPTION
Figure which follows shows an example of 1353NM map.
A detailed description can be found in Section TVA ( Topology Viewer Application ) and in Section PNM
( Physical Network Management )
TITLE
MAP TREE
GLOBAL AREA
ZOOMED AREA
PULLDOWN MENU
TOOL BAR
Figure 13. 1353NM map.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
22
02


/ 3AL 89061 AA AA

64
64
4.1 Equipment views description
There are three types of equipment views. The NE views, the board views and the port views.
4.1.1 NE (Network Element) view
The front side of an NE may be composed of several racks, with several subracks in each of them. Each
subrack is composed of several slots in which are inserted boards.
The number of views related to an equipment depends on the NE type. e.g. because several types of
equipment are made only of one subrack, the rack view is not available when this equipment is displayed.
Two examples of NE view are given in the following figures. The first one for a QB3* NE, the other one
for a Q3 NE.

Message area
Management
states control panel Icon representing the global
board alarm severity
ADM_001: 1641sm 2.7
Severity alarm panel
Figure 14. QB3* NE view.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
23
02


/ 3AL 89061 AA AA

64
64

Message area
Management
states control panel
Icon representing the global
board alarm severity
Severity alarm panel
Domain alarm panel
Figure 15. Q3 NE view example.
This views show an NE subrack, in which the different boards are represented. Icons in the top left hand corner
give information on the number and the severity of the current alarms. Icons representing the management
states are defined in the right side (for QB3* NE) or in the top right corner (for Q3 NE) of this view.
Boards may be duplicated in an NE for equipment protection reasons, to avoid loss of communications
in case of equipment failure.
Some boards contain several ports used for transmission purposes and interconnections between the
different boards.
The lock representation which appears over some boards (with the Put in service command for Q3 NE),
indicates that these boards cannot be removed because they are involved in one of the following
processes:
cross connection,
equipment protection,
multiplex section protection,
synchronization,
(port) NML assigned.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
24
02


/ 3AL 89061 AA AA

64
64
To be able to remove one of this board (the lock, with the Put out of service command for Q3 NE), you
must first stop the running process in which it is involved. (Only the unlocked boards can be removed with
the Remove command for Q3 NE).
The NE view (see Figure 14. ) contains an alarm panel, a management states control panel and a
message area. They provide you with information needed to manage the network.
a ) The Severity Alarm Panel
The 1353NM provides an alarm functionality that informs the operator on the severity of the different
alarms in the NE as well as on the number of current alarms. There are five different alarm severity
levels. In the 1353NM these different levels are associated with colours.
Red: Critical alarm (CRI).
Orange: Major alarm (MAJ).
Yellow: Minor alarm (MIN).
Cyan: Warning alarm (WNG).
Blue: Indeterminate (IND).
Each alarm severity is represented by an alarm icon situated in the top left hand corner of the view.
These alarm icons are constantly represented on the different Equipment views (NE view, Board view
or Port view) so that the operator is always aware of the alarms occurring in the system.
Furthermore the shape of the alarm icons in the alarm panel gives an indication of the occurrence
of alarms. The figures below describe the different examples.
An alarm icon with a circle inside it (and a number at the bottom of the icon) indicates that alarms
of the number and the type defined by the icon are occurring.
An alarm icon with a rectangle inside it indicates that no alarms of the type defined by the icon are
occurring.
An alarm icon greyed out indicates that spontaneous incoming alarm notification have been inhibited.

Circular shaped alarm icon
indicating alarm occurrence.
Rectangular shaped icon in-
dicating a stable state.
Greyed icon indicating alarm
notification inhibition.
Figure 16. Control panel alarm icon shapes.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
25
02


/ 3AL 89061 AA AA

64
64
The Q3 NE view presents three or four other icons in the top right of the window. These icons
summarize the alarms per domain: Synchronization (SYNC), External Point (EXTP for ADM only),
Equipment (EQP) and Transmission (TRNS).
Figure 17. Per domain icon alarms
N.B. Since some synchronization alarms are counted as a communication alarm on a
synchronization object, it is counted one time in transmission alarm and one time in
synchronization alarm. The result is that the sum of the numbers in the domain icons can
not correspond to the sum of the numbers displayed in the severity icons : the severity
alarm total number is always <= to the domain alarm total number.
b ) The Management States Control Panel
The different management states concerning the NE (see QB3* and Q3 Generic Ne Management
manuals) are also represented via icons located in the right side (for QB3* NE) or in the top right
corner (for Q3 NE) of the equipment views. These icons are:
The SUP icon: The Supervision state. Indicates whether or not the NE is under OS supervision.
The ALI icon: The Alignment state. Indicates whether or not the NE and OS MIBs are aligned.
The icon with a key symbol: The Local Access state. Indicates whether the NE is managed by
a craft terminal or by the OS
The Q3 / COM icon: The Operational state. Indicates whether or not the communication with
the OS is established.
The CTC icon: The Connected state. Indicates whether the NE is connected to local Craft
terminal.
The NML / MGR icon: The Assignment state. Indicates whether the NE is assigned to Network
Management tasks.
The NTP icon: The Network Time Protocol indicates whether the NTP communication protocol
is Enable (green frame) or Disable ( brown frame).
The SIM icon: The Simulator state. Indicates whether the Simulator is disable (green) or enable
(blue)
The AC icon: The abnormal condition state indicates whether some abnormal conditions have
been recognized. The user can visualize them with the Diagnosis> Abnormal condition list
command.
N.B. Position the cursor over one of the states icons, to display in the message area (see
Figure 18. ) the management state corresponding to the color displayed by this icon.
A color is applied to each management states icons. They give an indication of the status of the NE.
These colours may be configured
N.B. As for the alarm icons, a rectangular management state icon represents the stable state
while a circular icon shape represents an unstable management state.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
26
02


/ 3AL 89061 AA AA

64
64
c ) The Message area
The information displayed in the message area depends on the mouse cursor location within the
view. It can give two main types of information:
Information on the contents of the view, i.e. board name, port name etc... This information
depends on the type of view (NE view, Board view or Port view).
Information on the control panel. Displays the visual information provided by the icons in a
written form.
In the following figure the mouse cursor is situated on the slot 6. The message area therefore
indicates which board is present in slot 6.

Message area
sr1 / STM1_EL_Aggr#6
ADM_001: 1641sm 2.7
Figure 18. Example of the contents of the message area of a QB3* NE view.
N.B. Details on NE states and alarm are given in the QB3*and Q3 Ne Management manuals of this
SH Operators Handbook.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
27
02


/ 3AL 89061 AA AA

64
64
4.1.2 Board view
Each board that appears in the NE view has a particular detailed view concerning it. To avoid representing
all the views, only the general layout is described in this section, using an STM1 aggregate board view
for a QB3* NE, and a 2Mbit tributary board view for a Q3 NE.
The following figures represent these board views.
N.B. The control panel and the message area are identical to those in the NE view and are not
described again in this section.
Port
icons
Indications on the probable causes of the
alarms occurring in the board.
Board
Administrative State
ADM_001: 1641sm 2.7
Figure 19. Example of a QB3* NE Board view.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
28
02


/ 3AL 89061 AA AA

64
64

Port
icons
Board
Figure 20. Example of a Q3 NE Board view.
The board views show:
The icon representations of the ports it is composed of. There are as many icons as there are
different ports. In the above figure one type of ports is represented: an optical SDH port for the QB3*
NE board view and a PDH port view for the Q3 NE board view.
An Alarm probable causes information area which enable you to determine the probable cause of
the alarms occurring in the board.
This alarm probable causes information area uses the alarm severity colour definition described
previously to indicate the severity of the alarms occurring.
Small alarm icons on a corner of the port icons that indicate the most critical alarm occurring in the
port. To get details on the alarms occurring in the ports, navigate to the port view.
N.B. Some Q3NE transmission alarms detected in the port view are not propagated to the board
view. See the Procedures manual (Section 1.5) , Chapter 4 Procedures To Handle
Transmission Alarms in the scope of SH.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
29
02


/ 3AL 89061 AA AA

64
64
4.1.3 Port view
Navigation to the port views is explained in the Navigation Chapter.
The port view is the final view of the NE and shows in the most detail the composition of the ports, in terms
of the TPs that compose them.
To avoid representing all the different port views an STM1 aggregate optical port view (for QB3* NE) and
a STM1 optical port view (for Q3 NE) are used to underline the descriptions given hereafter.
The port views are represented in the following figures.
Functional blocks of the board
concerning this particular port
Port functional state
information message area
Port and board
identification
Specific TPs that
make up the port view
ADM_001: 1641sm 2.7
Figure 21. Example of a detailed port view for QB3* 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
30
02


/ 3AL 89061 AA AA

64
64

Functional blocks of the board
concerning this particular port
Port and board
identification
Figure 22. Example of a detailed port view for Q3 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
31
02


/ 3AL 89061 AA AA

64
64
The port views show:
The signal processing functional blocks concerning the port.
These functional blocks are placed in the top part of the view. The acronyms situated on each
functional block identifies the specific operations undertaken by the functional block.
The Termination Points (TPs) associated with each type of port .
The TPs are placed under the functional blocks. The acronyms of the TPs identify the type of TP. This
helps to identify the type of signal that transits by the port.
A port functional state information message area.
This message area gives information on the Administrative state, the Protection state, the Laser
shutdown state and the Operational state of the port.
The information in the functional state message area may change from port to port. For example,
electrical ports do not have the Laser shutdown information and PDH ports only have the NML
assignment information.
Small alarm icons placed next to the TP representations, and in the functional blocks, indicate alarm
occurrence. These alarm icons are identified by acronyms indicating the probable cause of the alarm
occurring.
These alarm icons use the alarm severity colour feature to indicate the severity of the alarm. The
operator can therefore determine the type and severity of the alarm occurring in a specific part of the
port.
N.B. The control panel and the message area are identical to those in the NE view and are not
described again in this 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
32
02


/ 3AL 89061 AA AA

64
64
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
33
02


/ 3AL 89061 AA AA

64
64
5 MAP NAVIGATION
5.1 Root map navigation
In order to navigate through the different views the following steps are to be followed.
a ) From the previously opened map view select pulldown menu item File: Local Pesistency: Restore
map
Figure 23. File: Local Pesistency: Restore map
b ) A question box asks for saving modification done on the actually opened map.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
34
02


/ 3AL 89061 AA AA

64
64
Figure 24. Question box
c ) If you click on Yes button, your changes will be saved. Subsequently the Local Restore map selection
box opens.
Figure 25. Local Restore map selection box
d ) Select the desired map and click on Restore button. Finally the map opens. See following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
35
02


/ 3AL 89061 AA AA

64
64
Figure 26. 1353NM Map
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
36
02


/ 3AL 89061 AA AA

64
64
Figure 27. NE popup menu.
e ) Pointing to a NE, you can open the popup menu. In particular it is possible to open the NE view via
the Show Equipment menu.
In addition you may make use of the Supervision menu to control main NM to NE 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
37
02


/ 3AL 89061 AA AA

64
64
Figure 28. NE Supervision popup menu
5.1.1 Hierarchical tree map navigation
Refer to Section TVA.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
38
02


/ 3AL 89061 AA AA

64
64
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
39
02


/ 3AL 89061 AA AA

64
64
6 EQUIPMENT VIEW
6.1 Open in Window command
Navigating amongst different views may be performed either inside the same window, or opening a new
window. This is useful if you want to navigate to another view without clearing the current view.
This operation can be carried out from Equipment views.
After selecting the desired element (board, port) from the current equipment view, select the Open In
Window option from the Views pull down menu as shown in the following figure.
Previous Esc
Equipment
External Points
Synchronization
Open object Alt+O
Open In Window Alt+W
Close Alt+Q
Views
Figure 29. Opening a view in a window
The selected view is then displayed in a new window.
N.B. Only three windows can be opened simultaneously. This option is not available in the Port view.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
40
02


/ 3AL 89061 AA AA

64
64
6.2 NE Equipment views
The NE symbols in the Network Topology views allow the user to open a detailed NE view. It is then
possible to navigate amongst the different NE Equipment views and to access other management
domains.
There are two types of NE Equipment views:
the views that reflect the equipment structure on different levels namely Room view, Equipment view
with rack and subrack level, Board view and Port view. These views follow an hierarchical order.
From the access point Room view, the user has to navigate through the various levels down to the
destination view. On the other hand it is possible to directly access the various levels via Equipment
Overview. For W/OMSN and WDM equipments the USM representation starts from the Equipment
View at rack level.
the views providing specific information according to management domains i.e. : Equipment
Overview, Synchronization view and Transmission view. These views are described in the Q3
NE Management section for Q3 NE equipments and QB3* NE Management section for QB3* NE
equipments. They can be directly accessed via Views menu.
Previous
Equipment
External Points
LO transmission
HO transmission
Synchronization
Open Object
Open in Window
Close
Views
Previous
Room
Equipment Overview
Transmission
Synchronization
Open Object
Open in Window
Close
Views
Example of aView menu for a QB3* NE Example of aView menu for a Q3 NE
Figure 30. Examples of Views menu
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
41
02


/ 3AL 89061 AA AA

64
64
6.2.1 Navigating to the Board View
The Board view can be opened from the subrack level of the Equipment view. To get there, access the
Room view via Views menu and then navigate through rack level of the Equipment view by double-clicking
on the relevant rack and subrack. Or select the relevant board in the Equipment Overview (for OMSG
only) and directly navigate to the Board view.
There are two ways of opening a Board view from the subrack level of the Equipment view:
via Views pull down menu
by double-clicking on the desired board
If you use the menu option, click on the board you want to visualize. The contour is highlighted in the view
showing that the board is selected. Select the Open Object or Open In Window option of the Views pull
down menu.
The Board view is then opened
Port icons
Board
Figure 31. Example of a Board view for a QB3* 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
42
02


/ 3AL 89061 AA AA

64
64
Port
icons
Board
Figure 32. Example of a Board view for a Q3 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
43
02


/ 3AL 89061 AA AA

64
64
6.2.2 Navigating to the Port View
The Port view can be opened from the Board view. To get there, access the Room view via Views menu
and then navigate through rack level and subrack level of the Equipment view by double-clicking on the
relevant rack, subrack and board. Or select the relevant port in the Equipment Overview and directly
navigate to the Port view. For W/OMSN and WDM equipments the USM representation starts from the
Equipment View at rack level and the board view is opened through the previous to the Board view
navigation.
From the Board view you can access a specific Port view
via Views pull down menu (only for QB3* NE equipments)
by double-clicking on the desired board
If you use the menu option, click on the port representation icon and select the Open Object or Open In
Window option of the Views pull down menu.

Selected port
Figure 33. Selecting a specific port view of a QB3* NE Board View.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
44
02


/ 3AL 89061 AA AA

64
64
The port view is then opened.

Aggregate board
functional blocks
Terminal Point (TP)
associated with the
specified port.
Identification of the port
and board types
Figure 34. Example of a QB3* NE Port View.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
45
02


/ 3AL 89061 AA AA

64
64
Selected port
Board functional state
Figure 35. Selecting a specific port view of a Q3 NE Board View.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
46
02


/ 3AL 89061 AA AA

64
64
Identification of the port
and board types
Functional blocks
of the board concerning
this particular port
Figure 36. Example of a Q3 NE Port View.
6.2.3 Navigating to Management menu commands
These views are described in the Q3 NE Management section for Q3 NE equipments and in the QB3*
NE Management section for QB3* NE equipments .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
47
02


/ 3AL 89061 AA AA

64
64
7 NE ALARMS AND NE STATUS
This section describes the types of alarms that are defined for the 1353SH, in terms of severity levels, and
the way they are propagated through the different Equipment views (NE, Board or Port views).
7.1 NE Alarm.
7.1.1 Description
Five different alarm severity levels are provided by the 1353SH.
Critical (CRI).
Major (MAJ).
Minor (MIN).
Warning (WNG).
Indeterminate (IND).
These levels are associated with different colours. They enable you to know the severity of the current
alarms occurring in the Equipment.
7.1.2 Propagation.
In all the equipment views, small icons synthetically summarizing the alarms occurring in these different
entities, are represented next to the Board or Port entities themselves. The Transmission alarms, related
to the received information stream, are recognize on the TP points of the boards but are not signalled on
the synthesis small icon alarm of the Q3NEs board. To find out the board with the occurred transmission
alarm the user can open the applicative AS selecting Diagnosis>Alarms>Transmission Alarms menu
option in the USM menu commands. Then, after reading the listed physical board indications, come back
to the USM, select the board and open the Port view to check the previous transmission alarms.
These icons have the following characteristics:
Colour: enables you to determine the severity of the alarm occurring (critical, major,...) in the board
or port. This functionality enables a rapid diagnosis and navigation to the views where the source of
the problem lies.
Aspect: inside the icon either a is drawn, in which case no alarm is occurring in the entity, or a
x sign is drawn, in which case alarms are occurring in the entity.
Using these two characteristics that are depicted in Figure 37. , you can determine the existence of alarms
in the entities you manage.
The figure below shows:
A section of a NE view with some boards defined and the alarm icon below the board representations,
A section of a Board view with a port defined and the alarm icon next to the port representation,
A section of a Port view with the alarm icons drawn next to the subunits composing the port.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
48
02


/ 3AL 89061 AA AA

64
64

Icon summarizing the
alarms occurring in the
board. The colour of the
icon indicates the sever-
ity of the most critical
alarm occurring in the
board.
port. The colour of the
icon indicates the sever-
ity of the most critical
alarm occurring in the
port.
board element named
MST.
The colour of the icon in-
dicates the severity of
the alarm.
The name of the icon
identifies the alarm.
Figure 37. Alarm representation in the Equipment views.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
49
02


/ 3AL 89061 AA AA

64
64
7.2 NE Status
7.2.1 Description
In the Network topology views, each NE composing the TN is associated with a status that is related to
its functional state. This section describes the relationship between the different NE statuses, the NE
management states and the alarm severities. Furthermore, the propagation of the statuses through the
hierarchy of views is described.
The status of the NE is displayed on the Network Topology views graphical interface using colours. The colour
of an NE indicates its status. The different NE statuses are:
Critical
Major
Minor
Warning
Restricted
Disabled
Unknown
Normal
The NE status is a function of its alarm severity (listed in paragraph Alarms / NE Alarms and NE Status
/ NE Alarm / Description), its alignment state, its operational state and its supervision state. Details on NE
states are given in the QB3*and Q3 Ne Management manuals of this SH Operators Handbook.
The relationships between the NE statuses and these different states are represented in the tables that
follow.
a ) Critical NE status.
A NE status is critical if the NE operational state is disabled, or, if it presents a critical alarm status
and no other dysfunctions.
NE
Status
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
state
Disabled Supervised
CRITICAL
Critical In configuration Enabled Supervised
Critical Aligned Enabled Supervised
N.B. The sign signifies that the value of this state doesnt impact on the final NE status.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
50
02


/ 3AL 89061 AA AA

64
64
b ) Major NE status.
A NE status is major if the OS and NE MIBs are misaligned, or, if the NE presents major alarms and
no other dysfunctions.
NE
Status
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
state
Misaligned Enabled Supervised
MAJOR
Major In configuration Enabled Supervised
Major Aligned Enabled Supervised
c ) Minor NE status.
A NE status is minor if the NE presents minor alarms and no other dysfunctions.
NE
Status
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
state
MINOR
Minor In configuration Enabled Supervised
MINOR
Minor Aligned Enabled Supervised
d ) Warning NE status.
A NE status is warning if alarms are either warning, indeterminate or cleared and the alignment state
in configuration, or, if the alarms are warning and no other dysfunctions present.
NE
Status
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
state
WARNING
Warning,
Indeterminate,
Cleared
In configuration Enabled Supervised
Warning Aligned Enabled Supervised
e ) Restricted NE status.
A NE status is restricted when it is currently undergoing operations (aligning MIB or
activating/deactivating Supervision). This means that no other operations can be carried out on the
NEs until the operations are completed.
NE
Status
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
state
RESTRICTED
Activating/
Deactivating
RESTRICTED
Aligning Enabled 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
51
02


/ 3AL 89061 AA AA

64
64
f ) Disabled NE status.
A NE status is disabled when the NE is just declared.
NE
Status
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
state
DISABLED Declared
g ) Unknown NE status.
A NE status is unknown if the alarms are indeterminate (meaning that the OS has not received an
update of the current alarms occurring) and no other dysfunctions are present in the NE.
NE
Status
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
state
UNKNOWN Indeterminate Aligned Enabled Supervised
h ) Normal NE status.
This occurs when all the alarms are cleared and the NE is functioning correctly.
NE
Status
Alarm
Status
NE Alignment
state
NE Operational
state
NE Supervision
state
NORMAL Cleared Aligned Enabled Supervised
To each of these NE statuses a colour is associated. The default colours set are listed below:
Critical: Red
Major: Orange
Minor: Yellow
Warning: Cyan
Restricted: Tan
Disabled: Dark brown
Unknown: Blue
Normal: Green
The alarm status propagation and the modification of the default colours are described in the EML
Construction of SH Operators Handbook: the first one in Constructing the Geographical Entities
chapter, the second one in NE Customizations chapter.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
52
02


/ 3AL 89061 AA AA

64
64
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
53
02


/ 3AL 89061 AA AA

64
64
8 ONLINE DOCUMENTATION
8.1 Overview
The Help is an important aspect of the 1353SH product. Using this functionality you can get information
on actions you are carrying out or on any particular topic linked to the 1353SH.
The help is based on world wide web technologies. The topics are written in html. Netscape Gold is the
browser used to navigate through the html pages and it is also used to edit the user personal pages.
Navigation through the help is also possible using a customized navigation bar permanently displayed in
the left of the help screen (see paragraph Navigation principles).
To know how to use Netscape, access the Netscape online help on the web, by typing the following URL
(Uniform Resource Locator) directly into the location Netsite: text field of Netscape (or using the URL
dialog box produced by the File|Open Location menu item):
http://home.netscape.com/eng/mozilla/3.0/handbook/index.html
Access to 1353SH help is possible in two different ways: Permanent access and access when using the
1353SH.
Help permanent access:
Any time you need information, you can start Netscape and access the 1353SH help by typing the
correct URL directly into the location Netsite: text field. It is not necessary to have an 1353SH product
running, you just need Netscape and the help location URL.
N.B. To have the correct URL, ask your system administrator.
Help access when using the 1353SH:
The 1353SH enables to access the help from the help menu, using the help push buttons of the dialog
boxes or by pressing the F1 key of the keyboard. This two last options gives you access to contextual
help. The help menu gives access to the following parts of the help:
help on help,
help on context,
glossary,
about (on version),
tutorial.
The menu options detailed in the following chapters are in fact entry points to the main help system. Once
you have entered the help system, via one of these menu options, hyperlinks enable you to navigate to
other parts of the help system and to view other help topics.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
54
02


/ 3AL 89061 AA AA

64
64
8.2 Help on help
Help on help opens the Netscape help system. It helps understand the basics of navigation and also
presents facilities that will enable you to quickly find the information you need. Using this option opens the
current online documentation chapter. This help is available from any Help pull down menu option.
To access help on help, select the On Help... option from the Help pull down menu.
Figure 38. Obtaining help on help.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
55
02


/ 3AL 89061 AA AA

64
64
The Netscape help window opens:
Figure 39. Netscape Help Window
Select the desired menu item.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
56
02


/ 3AL 89061 AA AA

64
64
8.3 Help on context
To access the on line context sensitive help you can either:
Press on the F1 key placed on top of the keyboard to get help on the active window.
Select the On Context option from the Help pull down menu to get help on the relevant application
window.
Click on the Help push button from any window.
The advantage of the help on context using push buttons is that it directly brings up the help that applies
to the actual context you are in. For example, in a dialogue box concerning the creation of a network
element symbol, clicking on the Help push button will open a help window giving information on this action.
Figure 40. Obtaining context sensitive help.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
57
02


/ 3AL 89061 AA AA

64
64
8.4 Glossary
This help option enables you to display the 1353SH online glossary.
To access the 1353SH Glossary, select the Glossary option from the Help pull down menu.
Figure 41. Obtaining the glossary.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
58
02


/ 3AL 89061 AA AA

64
64
A window like the following example is opened.

Figure 42. Glossary help 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
59
02


/ 3AL 89061 AA AA

64
64
8.5 About the help version
About the help version displays the version and copyright for the 1353SH Product.
To access the Help on Version, select the About... option from the Help pull down menu.
Figure 43. Obtaining info about the help 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
60
02


/ 3AL 89061 AA AA

64
64

Figure 44. About the help on version 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
61
02


/ 3AL 89061 AA AA

64
64
8.6 Tutorial
Tutorial displays the 1353SH help home page.
To access the handbooks contents and structure, select the Tutorial option from the Help pull down
menu.
Figure 45. Obtaining help home page
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
62
02


/ 3AL 89061 AA AA

64
64

Figure 46. Tutorial help 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
63
02


/ 3AL 89061 AA AA

64
64
8.7 Navigation Bar
The navigation bar which is displayed on the left side of the screen allows quick access to the following
help pages:
Home
The home page offers links to other documentation that is part of the Operation Manual SH Software.
Contents
The contents of the currently consulted manual are displayed.
Previous and Next
Those buttons can be used to navigate within a document.
Glossary
The glossary pages are displayed.
Help
This description of the navigation bar is displayed.
Whats New
A versions history list is displayed.
User Pages
The user pages offer the opportunity to take notes or make commentaries. These user pages are
created automatically during the user account creation and can only be accessed from this user.
Search
If available, the search function performs a string search within all online-help files supporting the
search function. The output is a list of files containing the search 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
64
02


/ 3AL 89061 AA AA

64
64
END OF DOCUMENT
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
1
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66


TABLE OF CONTENTS
1 GENERALITIES 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 What is TVA? 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Key Concepts 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Views and Maps 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 TVA Objects, Child Views and Symbols 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 TVA Functionalities 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 USER INTERFACE OVERVIEW 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Main Window 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 TVA Main Window 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Menu Bar 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 Tool Bar 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4 Tree Area 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5 Overview Area 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.6 View Area 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.7 Message Area 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.8 Console Button 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Secondary Windows and Dialog Boxes 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Secondary Windows 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Dialog Boxes 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 File Chooser Dialog Box 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Network Representation 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 View Symbol 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 NE Symbol 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3 Link Symbol 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.4 Offpage Connector 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.5 State Icons 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.6 Information Box 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.7 Selected Symbols 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.8 Current View 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Selection Rules 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Using the Mouse 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Using the Keyboard 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
01A 040123
V.SCORTECCI V.PORRO
02 040728 SC04091002
V.SCORTECCI V.PORRO
050623 03 SC04091002
V.BALCONI V.PORRO
1353NM REL.7.0
VERSION 7.0
OPERATORS HANDBOOK
L.MERLI
L.MERLI
A.CORTESE L.FORESTA

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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
2
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.4.3 NE and Symbols 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.4 Interaction between the Tree Area and the View Area 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Getting Help 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 WINDOW MANAGEMENT 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Creating a New Map 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Setting the Map Parameters 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Using the Local Persistency 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 Saving a Map as Local Map 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 Saving a Local Map 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.3 Restoring a Local Map 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.4 Deleting a Map File 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Opening a TVA Object 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Opening a TVA Object in the Current Main Window 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Opening a TVA Object in Another Main Window 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Opening a Grouped Link 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4 Opening an Offpage Connector 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Duplicating the Main Window 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Closing the Current Window 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 Opening the Console Window 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.1 Using a Shortcut Button to open the Console Window 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8 Quitting TVA 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 VIEW MANAGEMENT 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Using the View Menu 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Configuring a Display Filter 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Activating/Deactivating a Display Filter 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 Configuring a Command Filter 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.4 Activating/Deactivating a Command Filter 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.5 Zooming in/out a View 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.6 Managing the Related Views 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.7 Setting the General Parameters of a View 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.8 Setting the Display Parameters of a View 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Managing the View Filters 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Filter Editor Window 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 Managing Filters 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Modifying the Current Filter 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 SYMBOL MANAGEMENT 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Creating a Child View 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Adding a Graphic Symbol 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Adding a Graphic Link 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Improving the Layout Display 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Activating/Deactivating the Frozen Mode 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 Selecting All the Symbols 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Cutting a Symbol 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8 Copying a Symbol 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9 Pasting a Symbol 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.10 Deleting a Symbol 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.11 Deleting All the Symbols from All the Views 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 NAVIGATION 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Navigating by Using the Go Menu 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 ABBREVIATIONS 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
3
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
FIGURES
Figure 1. Main Window 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Menu Bar 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Example of a Pulleddown Menu 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Tool Bar 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Example of a File Chooser Dialog Box 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. View Symbol Used in the View and Overview Areas 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. View Symbol Used in the Tree Area 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Basic NE Symbol 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. NE Symbol 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Blue Broken Icon Showing an NE Communication State at Disabled 19 . . . . . . . . . . . . . . . .
Figure 11. Composite NE Symbol 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Basic Simple Link Symbol 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Basic Grouped Link Symbol 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Simple Link Symbol 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Offpage Connector Symbol 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Example of an OffPage Connector 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Administrative State Icons 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Usage State Icons 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Availability Status Icons 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Local Access State Icons 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Communication State Icon 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. MIB Alignment State Icons 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Example of an Information Box 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Example of a Selected Symbol 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Example of a Symbol in the Tree Area for a View Containing Selected Symbols 25 . . . . . .
Figure 26. Example of a Symbol in the Tree Area for the Currently Displayed View 25 . . . . . . . . . . . .
Figure 27. Help Menu 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. File Menu 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. TVA Confirmation Dialog Box for Creating a New Map 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. TVA Confirmation Dialog Box for Saving the Current Map 30 . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Map Parameters Dialog Box 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Example of a View Showing the Contents of a Grouped Link 36 . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Console Window 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Screen Button Indicating a New Error 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Confirmation Dialog Box for Quitting TVA 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. View Menu 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Related Views Dialog Box 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Example of a RowColumn Layout 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Example of a Cartesian Layout 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. View Parameters Dialog Box 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Options Window 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Filter Editor Window 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. File Menu of the Filter Editor Window 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Working Area of the Filter Editor Window 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Edit Menu 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. Child View Creation Dialog Box 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Graphic Symbol Creation Dialog Box 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. Graphic Connection Creation Dialog Box 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 51. Go Menu 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
4
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
5
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
1 GENERALITIES
This chapter:
introduces TVA (see section 1.1)
gives TVA key concepts (see section 1.2)
presents the TVA functionalities (see section 1.3)
1.1 What is TVA?
The Topology Viewer Application (TVA) provides the user with:
coherent views of a telecommunication network in an intuitive graphical format
the integration of different network management applications in a unique interface which uses an only
one look and feel
The Telecommunication Network managed by client applications is represented by TVA as a set of TVA
objects as follows:
topology objects like views
equipment objects associated to Managed Elements (ME) like NEs (switches, adddrop multiplexers,
routers) and (topology and logical) links between NEs
TVA allows client applications to plug in their own commands by adding via configuration the correspond-
ing menus and/or icons in the TVA menus and/or toolbar.
1.2 Key Concepts
1.2.1 Views and Maps
View
A view is a way for assembling and displaying, by means of graphical symbols, a set of objects sharing
common characteristics that may be for example:
geographical (state, region, site, town, ...)
functional (switching, transmission, access, ...)
logical (clientoperator, ...)
The division of the network according to one of the previous characteristics is under the responsibility of
the user or the client applications.
Map
A map is an organized set of views, a hierarchical structure with a root view at the top. In the map structure,
each view (except the root view) is a part of another view (or more). A view contained in another one is
called child view. The view which contains it is called parent view.
NOTE: A view cannot contain itself; this would generate a Circular Reference error.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
6
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
TVA does not create the original views and maps, but receives them from the client applications at startup.
The user can create some child views (refer to section 5.1). All the views contained in a view must belong
to the same map.
1.2.2 TVA Objects, Child Views and Symbols
TVA objects exist independently of any view. They are not contained in any view. They are represented
in the views by means of symbols.
Symbols contain only graphical information (position in the view, label, ...).
Several symbols corresponding to the same ME may exist in the same view and/or in different views of
the map.
Symbols may also represent child views contained in the current view.
According to the type of symbol, the user may perform different actions:
if the symbol represents an ME, the user can execute an application command from it
if the symbol represents a child view, the user can visualize its contents
1.3 TVA Functionalities
TVA provides the user with functionalities as follows:
Maps and views
choice of the map parameters
local persistency
choice of the view parameters
creation of a child view from the current view
definition of related views (to associate a view to the current one)
Symbols
selection and moving of symbols
classical editing commands (cut/copy/paste) on the symbols
display filtering (to display only symbols that match characteristics defined by the user)
command filtering (to perform commands only on the symbols that match characteristics defined by the
user)
Navigation
within the views
from a current view to a related view
Help on line
general help
contextual help, depending on the current 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
7
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2 USER INTERFACE OVERVIEW
This chapter describes:
the main window of TVA (see section 2.1)
the secondary windows used in TVA (see section 2.2)
the symbols used to represent the network (see section 2.3)
the selection rules (see section 2.4)
how to get help (see section 2.5)
2.1 Main Window
This section presents the TVA main window (see paragraph 2.1.1) then details all the parts that compose
it (see paragraphs 2.1.2 to 2.1.8).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
8
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.1.1 TVA Main Window
The TVA main window is the entry point of the user interface. It is displayed at the application startup and
contains all the commands you need to use TVA.
Figure 1. Main Window
The main window is composed of four areas (from top to bottom):
a menu bar (see paragraph 2.1.2)
a tool bar (see paragraph 2.1.3)
a working area divided into three other areas:
at the top left: the tree area (see paragraph 2.1.4)
at the bottom left: the overview area (see paragraph 2.1.5)
on the right: the view area (see paragraph 2.1.6)
an information area divided into two other areas:
on the left: the message area (see paragraph 2.1.7)
on the right (just before the Alcatel logo): the console button (see paragraph 2.1.8)
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
9
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
The three parts of the working area can be resized and hidden by using the separation bars.
Resizing a part of the working area
To horizontally resize a part of the working area, drag and drop the small rectangle located on the vertical
separation bar.
To vertically resize the tree or overview area, drag and drop the small rectangle located on the horizontal
separation bar.
Note: The separation bars cannot pass the minimum size of the tree area.
Hiding a part of the working area
To hide the overview area for example, click on the down arrow located on the horizontal separation bar.
To return to the previous size of the overview area, click on the up arrow also located on the horizontal
separation bar.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
10
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.1.2 Menu Bar
Figure 2. Menu Bar
The menu bar contains pulldown menus that allows you to access most of TVA functionalities.
The gap between the Go and Help menus is to be used by the client application to insert its own menus.
In the example of figure 2, four specific menus have been inserted by the client application.
To use a pulldown menu, click on it. The available items appears in form of a list. Select an item by clicking
on it.
Section 7.1 recapitulates the functionalities offered by each pulldown menu.
Figure 3. Example of a Pulleddown Menu
Some item names are immediately followed by suspension points that mean a dialog box will open. When
there is not any suspension points, the action is immediately performed.
Submenu
A right arrow on the right of a menu item means a submenu exists from this item.
Mnemonic
Each menu and item name includes an underlined character called mnemonic. You can more quickly ac-
cess a menu or a menu item by typing <Alt> then its mnemonic.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
11
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
Shortcut Key
A shortcut key is a sequence of keys located in the right of some menu item. You can also type this shortcut
key to more quickly access a menu item.
Tick Box
Some menu item are preceded by a small square you can tick (or untick) in order to activate (or deactivate)
a command.
Greyed Menu
A greyed menu or menu item means it is not available for the elements currently selected in the view area.
The reason may be:
the number of selected elements is too small or too great
no element is selected
the selected element(s) do(es) not support(s) the wished action
Contextual Menu
TVA also provides a contextual menu whose items depend on the area pointed by the mouse.
Access the contextual menu by clicking with the right mouse button.
Section 7.2 recapitulates the functionalities offered by the contextual menu according to the location it is
called from.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
12
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.1.3 Tool Bar
Figure 4. Tool Bar
The tool bar contains icons that allows you to quickly access the often used TVA functionalities.
To use the tool bar, click on the desired icon.
Section 7.3 recapitulates the shortcuts offered by the icons.
2.1.4 Tree Area
The tree area displays in a hierarchical way the list of the views contained in a map.
At the beginning, the tree area is empty. It is filled when you populate the map and updated at each creation
or deletion of views.
Each node of the tree represents a view whose symbol is described in paragraph 2.3.1.
The root node on the top is given the map name.
When you doubleclick on a node, the content of the corresponding view is displayed in the view area.
Thus the tree area can be used to switch from a view to another one.
Expanding/Shrinking a Branch
If a node represents a parent view (i.e. containing child views), it is preceded by a + or button.
click on the + button to make visible the child views contained in a parent view
click on the button to make them invisible
2.1.5 Overview Area
The overview area displays all of the current view. It is not scrollable.
A mobile frame represents the part of the overview that is displayed in the view area.
By moving and/or resizing this frame, you can modify the contents of the view area.
Clicking once on a corner of the frame then expanding (or shrinking) it has a shrinking (respectively ex-
panding) zoom effect on the view 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
13
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.1.6 View Area
The view area displays the current view that shows child views, MEs and links in form of symbols. These
symbols are dynamically updated (shape, color, flashing) and can be selected, edited and removed.
Section 2.3 gives more details about the use of symbols in the network representation.
A background graphic can be associated to each view. It is a image file in GIF or JPEG format. It can be
zoomed at the same time as the symbols of the view.
Paragraph 4.1.7 explains how to associate a background graphic to a view.
This view area can be scrolled horizontally and vertically to have a visibility of all the objects and symbols.
The scrolling can be made by using the horizontal and vertical scrollbars, or the arrow keys.
The view area can also be zoomed and the scrollbars adapted to the view contents and the zooming factor.
Refer to paragraph 4.1.5 for more details
2.1.7 Message Area
The message area displays help on commands, and error or information messages.
2.1.8 Console Button
When clicking on the console button, you can open the Console window that displays error and information
messages.
Refer to section 3.7 for more details.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
14
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.2 Secondary Windows and Dialog Boxes
In addition to the main window, you can access other windows by using the menu bar and the tool bar.
These windows are called:
secondary windows if they include a menu bar (see paragraph 2.2.1)
dialog boxes if not (see paragraph 2.2.2)
Specific dialog boxes called file chooser dialog boxes are described in paragraph 2.2.3.
2.2.1 Secondary Windows
The only secondary window is the Filter Editor window (refer to section 4.3).
2.2.2 Dialog Boxes
Dialog boxes allow you to display and/or set parameter values. You must give required information before
going on.
The dialog boxes are composed of two main areas:
a working area, used to display information or set parameter values
a button area including one or more of the following push buttons:
Apply: to apply the modifications
Close: to close the dialog box after applying the modifications
OK: to confirm the modifications and close the dialog box
Cancel: to close the dialog box without taking any modification into account
Help: to access the contextual help on line (see paragraph 2.5)
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
15
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.2.3 File Chooser Dialog Box
The file chooser dialog box allows you to manage files.
Figure 5. Example of a File Chooser Dialog Box
The structure of this dialog box is always the same whatever the way of calling it. Only its title and the first
button at the bottom change.
To choose a file:
Select a directory either by doubleclicking on it in the Folder list or by directly keyboarding its path in
the Enter path or folder name field.
The files contained in the selected directory appears in the Files list.
Select a file either by clicking on it in the Files list or by directly keyboarding it in the Enter file name field.
As soon as the file is chosen, click on the Open (or Save or Delete) push button to perform the wished
operation.
When you delete a file, the file chooser dialog box reopens. To close the dialog box, click on the Cancel
push button.
Clicking on the Update push button refreshes the contents of the selected directory in the Folder and Files
lists.
Clicking on the Cancel push button closes the dialog box without choosing any file.
Clicking on the Help push button opens the contextual help on line (see paragraph 2.5).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
16
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.3 Network Representation
In the main window, TVA use symbols to represent:
views (see paragraph 2.3.1)
Network Elements (NE) (see paragraph 2.3.2)
links (see paragraph 2.3.3)
offpage connectors (see paragraph 2.3.4)
states (see paragraph 2.3.5)
information (see paragraph 2.3.6)
selected symbols (see paragraph 2.3.7)
current views (see paragraph 2.3.8)
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
17
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.3.1 View Symbol
A view is represented by two symbols:
one in the overview and view areas
another one in the tree area
In the Overview and View Areas
Figure 6. View Symbol Used in the View and Overview Areas
This view symbol is composed of:
a rectangle, in which a bitmap indicates the type of view (state, region, city, site, room, building, subnet-
work, logical) under the rectangle:
a user label that has been defined either at the creation time (see section 5.1) in case of a child view,
or in the client application over the rectangle:
a small state icon indicating (when it is present) a disabled communication state on at least one ME con-
tained in the view.
The color of the symbol indicates the alarm status synthesis of the view. It corresponds to the most severe
alarm status of the MEs contained in the view.
A cross on the view symbol indicates that the operational state of at least one ME contained in the view
is disabled.
In the Tree Area
Figure 7. View Symbol Used in the Tree Area
This view symbol is composed of:
a bitmap on the left of the bitmap: a dot whose color indicates the alarm status synthesis of the view (same
color as for the view symbol in the view and overview areas) according to the synthesis type and mode
chosen in the Map
Parameters dialog box (see section 3.2)
on the right of the bitmap: a user label that has been defined either at the creation time (see section 5.1)
in case of a child view, or in the client 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
18
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.3.2 NE Symbol
Figure 8. Basic NE Symbol
The NE symbol is always composed of a rectangle containing:
a bitmap that corresponds to the type of the NE (switch, adddrop multiplexers, routers, ...)
under the bitmap: a text field indicating the type of the NE
Figure 9. NE Symbol
As shown in figure 9, other elements may also appear according to the NE states and/or from information
coming from the client application:
on the right of the bitmap: two sets of characters formatted as follows:
nnnS+
mmmS+
where:
nnn is the number of alarms
mmm is the number of active (non acknowledged) alarms
S is the highest severity
+ (optional) means there are other severities less than S
under the rectangle: a user label that has been defined in the client 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
19
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
in the middle of the rectangle: one or two lines of text annotation filled in by the client application
over the rectangle: small state icons used to draw the users attention to changes of the NE states (refer
to paragraph 2.3.5)
The color of the symbol indicates the alarm status of the NE. It corresponds to the most severe alarm
emitted by the NE.
Communication State at Disabled
When the NE communication state is disabled, the NE symbol appears as a blue broken icon (see figure
10).
Figure 10. Blue Broken Icon Showing an NE Communication State at Disabled
Composite NE
Figure 11 below shows the symbol used in the tree area to represent a composite NE.
Figure 11. Composite NE Symbol
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
20
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.3.3 Link Symbol
The links can be simple (see figure 12) or grouped (see figure 13).
Figure 12. Basic Simple Link Symbol
Figure 13. Basic Grouped Link Symbol
A grouped link includes several simple links that exist between the same NEs.
The link symbol is always composed of a rectangle in the middle of a black line. This rectangle contains
a bitmap corresponding to the type of link (fiber, electric, bundle, radio, logical, grouped, ...).
Figure 14. Simple Link Symbol
As shown in figure 14, other elements may also appear according to the link states and/or from information
coming from the client application:
under the rectangle: a user label that has been defined by the client application
in the middle of the rectangle: one or two lines of text annotation filled in by the client application
The color of the symbol indicates the alarm status of the link:
for a simple link, it corresponds to the most severe alarm status of the linked NEs
for a grouped link, it corresponds to the most severe alarm status of the simple links contained in the
grouped link
A cross on the symbol indicates the operational state of the link:
for a simple link, the cross means the operational state of at least one of the linked NEs is disabled
for a grouped link, the cross means the operational state of at least one simple link contained in the
grouped link is disabled
Communication State at Disabled
When the link communication state is disabled, the link symbol appears in blue color.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
21
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.3.4 Offpage Connector
The offpage connector is a navigation symbol assuring the continuity of a link between two symbols that
are located on two distinct views.
Figure 15. Offpage Connector Symbol
The offpage connector symbol is represented by a diamond. Its user label gives the name of the object
it replaces.
The figure below shows an example of an offpage connector.
Figure 16. Example of an OffPage Connector
You can navigate towards the view containing the missing symbol by doubleclicking on the offpage con-
nector symbol.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
22
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.3.5 State Icons
The state icons provide you with information concerning the following NE states:
administrative state
NO ICON unlocked (default value)
Figure 17. Administrative State Icons
usage state
Figure 18. Usage State Icons
availability status
NOT AVAILABLE
Figure 19. Availability Status Icons
local access state
Figure 20. Local Access State Icons
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
23
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
communication state
Figure 21. Communication State Icon
MIB alignment state
Figure 22. MIB Alignment State Icons
Other states may be added by the client application and represented by TVA.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
24
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.3.6 Information Box
The information box (also called balloon) contains all the information related to a symbol. It is another
way of visualizing the states of an NE.
It can be accessed by selecting a symbol, then pressing the bar space or clicking with the middle mouse
button.
The figure below shows an example of an information box.
Figure 23. Example of an Information Box
The information that have not been defined appear in italic non bold characters.
The distribution of the information between the state icons and the information box can be customized at
user level (refer to paragraph 4.1.8).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
25
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.3.7 Selected Symbols
When a symbol is selected in the view area, it appears as follows:
Figure 24. Example of a Selected Symbol
When at least a symbol is selected in the current view of the view area, the corresponding symbol of the
view in the tree area appears as follows (black indicator around the dot).
Figure 25. Example of a Symbol in the Tree Area for a View Containing Selected Symbols
NOTE: This black indicator is propagated recursively to the parent view(s) of the view containing the se-
lected symbol(s).
2.3.8 Current View
The symbol of the view currently displayed in the view area appears as follows (black rectangle) in the tree
area.
Figure 26. Example of a Symbol in the Tree Area for the Currently Displayed View
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
26
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.4 Selection Rules
This section explains:
the selection by using the mouse (see paragraph 2.4.1)
the selection by using the keyboard (see paragraph 2.4.2)
the differences of selection between the NEs and symbols (see paragraph 2.4.3)
the interaction between the tree area and the view area (see paragraph 2.4.4)
2.4.1 Using the Mouse
Most of selection are performed by means of the mouse buttons.
There are three mouse buttons:
the left button allows you to select anything
the middle button is used only for opening the information box (see paragraph 2.3.6)
the right button allows you to perform operations on symbols
In a left handed mouse configuration, the functionalities provided by the left and right buttons are
reversed.
The middle and right buttons are used only in the view area of the main window.
In the whole document, click means click by using the left mouse button. The uses of the other mouse
buttons are clearly indicated.
In the view area, you can also:
select several symbols by drawing a selection rectangle around them
cancel the current selection by clicking anywhere on the background image
You can also doubleclick on a view symbol to open it.
2.4.2 Using the Keyboard
The <Shift> key can be used as follows, in case of a multiselection:
to extend the current selection, press the <Shift> key while clicking on the new object to be added to the
selection
to add or remove an object to/from a multiple selection, press the <Shift > key while clicking on this object
The selection extension by means of the <Shift> key may apply to symbols that belong to different views
displayed in several main windows.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
27
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.4.3 NE and Symbols
As several symbols located in distinct views can represent the same NE, selecting the symbol of an NE
in a view amounts to selecting all the symbols related to this NE in all the views.
The indicator symbolism described in paragraph 2.3.7 allows you to know where all the symbols related
to the selected NE(s) are located.
However the meaning of the selection depends on the action to be performed.
The Cut/Copy/Paste/Delete actions (available in the Edit menu) apply only to the symbols selected in the
current view.
All the other actions apply on the NE whose symbol is selected in the current view.
2.4.4 Interaction between the Tree Area and the View Area
The selection in the tree area is independent of the selection in the view area. Selecting a symbol in the
tree area does not change the selection in the view area, and vice versa.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
28
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
2.5 Getting Help
TVA provides you with an HTML (Hyper Text Markup Language) help on line that can be accessed at any
time by using the Help menu.
Figure 27. Help Menu
The items of the Help menu are as follows:
On Version: to display information related to the current TVA release
On TVA: to access the home page of the help on line
On Window: to access the help on line at the page that describes the main window
In the three cases, the help is displayed by means of an HTML browser like for example Netscape.
Contextual help on line
TVA also provides you with a contextual access to the help on line. Indeed the secondary windows and
dialog boxes include an Help push button that allows you to directly access the help on line at the page
that describes this current window or dialog box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
29
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3 WINDOW MANAGEMENT
This chapter describes the functions offered by the File menu.
Figure 28. File Menu
This menu allows you to:
create a new map (see section 3.1)
set the map parameters (see section 3.2)
use the local persistency (see section 3.3)
open a TVA object (see section 3.4)
duplicate the main window (see section 3.5)
close the current window (see section 3.6)
open the Console window (see section 3.7)
quit TVA (see section 3.8)
3.1 Creating a New Map
This function consists in opening a new map that replaces the currently displayed one.
To create a new map, use the menu path:
File > New Map
Two cases may occur:
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
30
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
If you had not modified the currently displayed map, the following confirmation dialog box opens:
Figure 29. TVA Confirmation Dialog Box for Creating a New Map
Click on the OK push button. A new empty map opens with default parameters. To change them, see sec-
tion 3.2.
If you had modified the currently displayed map, the following confirmation dialog box opens:
Figure 30. TVA Confirmation Dialog Box for Saving the Current Map
When you click on the Yes push button, a file chooser dialog box opens (see paragraph 2.2.3) allowing
you to give a name to the map to be saved.
As soon as the current map is saved, a new empty map opens with default parameters. To change them,
see section 3.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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
31
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.2 Setting the Map Parameters
This function consists in setting synthesis engine parameters that will be used in the whole map (i.e. in
all the views belonging to the map).
A synthesis engine propagates abnormal operation data through the views of a map. For instance the
alarm status of an NE in the lowest level view of a map can be made visible at the highest level view of
the same map.
To set the map parameters, use the menu path:
File > Map Parameters
The following dialog box opens:
Figure 31. Map Parameters Dialog Box
This dialog box allows you to make active or not the following types of synthesis engines:
Operational State Propagates the disabled operational state.
Alarm Status Propagates any alarm status
Communication State Propagates the disabled communication state.
Then for each enabled synthesis engine type, you can choose a synthesis mode.
For the first three synthesis types, there is only a Default mode provided by TVA, but the client application
that uses TVA may add other synthesis modes.
The Default mode propagates the flashing symbol state, the disabled communication state and/or the dis-
abled operational state at the view level as soon as at least one of the symbol contained in the view is in
this state.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
32
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
For the Alarm Status synthesis engine, three modes are provided by TVA:
Default
The table below gives the way the alarm status is propagated through the views (a symbol is normal when
its alarm status is clear)
States of the Symbols in the View Alarm Status of the View
Symbols are neither normal nor abnormal Indeterminate
All the symbols are normal Cleared
One symbol is abnormal and all other ones are nor-
mal
Warning
More than one symbol is abnormal and more than
one other symbol is normal
Minor
One symbol is normal and all other ones are abnor-
mal
Major
All the symbols are abnormal Critical
Table 1: Alarm Status Propagation by Default
Threshold value
The synthesis engine propagates the alarm status according to the percentages given below:
active pending: 70%
indeterminate: 50%
warning: 30%
minor: 20%
major: 10%
critical: 5%
Most critical
The synthesis engine propagates the most critical alarm status of the symbol belonging to the view.
Adding a Comment
You can add a comment in the Map Comment field.
Enabling/Disabling a Synthesis Type
To enable/disable a synthesis engine type, click on the corresponding tick box. A tick means the synthesis
engine is enabled.
Choosing a Synthesis Mode
To choose the synthesis mode of a previously enabled synthesis type, click on the down arrow of the corre-
sponding option button, then select the mode in the list which appears.
Concerning the use of the OK, Cancel and Help push button, refer to paragraph 2.2.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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
33
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.3 Using the Local Persistency
The local persistency allows you to store and retrieve complete maps (and the submaps, objects and sym-
bols they contain) in map files. Thanks to the local persistency, you can:
save a map as a local map (see paragraph 3.3.1)
save a local map (see paragraph 3.3.2)
restore a local map (see paragraph 3.3.3)
delete a map file (see paragraph 3.3.4)
reset the local database (see paragraph 3.3.5)
3.3.1 Saving a Map as Local Map
To save for the first time the current map in a map file, use the menu path:
File > Local Persistency > Save Map As
A file chooser dialog box opens (see paragraph 2.2.3) allowing you to give a name to the map to be saved.
3.3.2 Saving a Local Map
To save a map already declared in a map file, use the menu path:
File > Local Persistency > Save Map
A file chooser dialog box opens (see paragraph 2.2.3) allowing you to end the saving.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
34
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.3.3 Restoring a Local Map
To restore a map from a map file, use the menu path:
File > Local Persistency > Restore Map
If you had not modified the currently displayed map, a file chooser dialog box opens (see paragraph 2.2.3)
allowing you to select the map to be retrieved. If you had modified the currently displayed map, the follow-
ing confirmation dialog box opens:
As soon as the current map is saved, another file chooser dialog box opens (see paragraph 2.2.3) allowing
you to select the map to be retrieved.
3.3.4 Deleting a Map File
To delete a map file, use the menu path:
File > Local Persistency > Delete Map File
A file chooser dialog box opens (see paragraph 2.2.3) allowing you to select the map file to be 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
35
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.4 Opening a TVA Object
This function consists in visualizing the content of a TVA object (view, grouped link or offpage connector).
either in the current main window (see paragraph 3.4.1)
or in another main window (see paragraph 3.4.2)
You can use this function to navigate within the views of a map.
For more details about the opening of:
a grouped link, refer to paragraph 3.4.3
an offpage connector, refer to paragraph 3.4.4
3.4.1 Opening a TVA Object in the Current Main Window
To open a TVA object in the current main window:
Click on the TVA object symbol in the view area or in the tree area. Use the menu path:
File > Open View
The content of the selected TVA object replaces the current view in the view area.
Another way of opening a TVA object is to doubleclick on its symbol.
3.4.2 Opening a TVA Object in Another Main Window
To open a TVA object in another main window:
Click on the TVA object symbol in the view area.
Use the menu path:
File > Open View in new Window
A new main window opens. Its view area displays the contents of the selected TVA object.
This function is not available from the tree 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
36
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.4.3 Opening a Grouped Link
When you opens a grouped link, the following specific view appears.
Figure 33. Example of a View Showing the Contents of a Grouped Link
3.4.4 Opening an Offpage Connector
Opening an offpage connector has the same effect as navigating towards the view that contains the other
extremity of the offconnector (see paragraph 2.3.4)
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
37
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.5 Duplicating the Main Window
This function allows you to display several main windows in the same time. That can be useful for visualiz-
ing two different views of the map in the same time.
To duplicate the main window, use the menu path
File > Duplicate Window
A new main window opens. Its contents is exactly the same as the other main window.
3.6 Closing the Current Window
This function allows you to close the current main window. It is available only when several main windows
are open.
To close the current main window, use the menu path
File > Close
The current main window closes.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
38
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.7 Opening the Console Window
The Console window provides you with information about errors related to TVA.
To open the Console window, use the menu path:
File > Show Console
Another way of opening the Console window is to use the shortcut button (see paragraph 3.7.1).
The following window opens:
Figure 34. Console Window
This window is read only. At any time, you can:
remove its contents by clicking on the Clear push button
close it by clicking on the Close push button
The error messages can also be displayed on the message area at the bottom of the main 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
39
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.7.1 Using a Shortcut Button to open the Console Window
At the bottom of the TVA main window, on the left of the Alcatel logo, a button in form of screen represents
the Console window. When an error occurs, a red ! sign appears in the screen (see figure below).
Figure 35. Screen Button Indicating a New Error
By clicking on this button, you can quickly open the Console 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
40
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
3.8 Quitting TVA
To quit TVA, use the menu path:
File > Exit
If you had not modified the currently displayed map, the following confirmation dialog box opens:
Figure 36. Confirmation Dialog Box for Quitting TVA
Click on the OK push button to confirm. All the TVA windows will be closed.
Clicking on the Cancel push button allows the user to return to the main window.
If you had modified the currently displayed map, the following confirmation dialog box opens:
As soon as the current map is saved, all the TVA windows close.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
41
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4 VIEW MANAGEMENT
This chapter describes:
the functions offered by the View menu (see section 4.1)
the management of the view filters (see section 4.2)
the use of the Filter Editor window (see section 4.3)
4.1 Using the View Menu
Figure 38. View Menu
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
42
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
configure a display filter (see paragraph 4.1.1)
activate/deactivate a display filter (see paragraph 4.1.2)
configure a command filter (see paragraph 4.1.3)
activate/deactivate a command filter (see paragraph 4.1.4)
zoom in/out a view (see paragraph 4.1.5)
manage the related views (see paragraph 4.1.6)
set the general parameters of a view (see paragraph 4.1.7)
set the display parameters of a view (see paragraph 4.1.8)
4.1.1 Configuring a Display Filter
This function consists in choosing the criteria of a display filter.
A display filter can be used to hide or display symbols in all the views of the current map, according to their
properties.
The configuration and management of the display filters is performed through the Filter Editor window.
To configure a display filter, use the menu path:
View > Edit Filter
The Filter Editor window opens (refer to section 4.3).
The first time...
When no filter exists, you can access the Filter Editor window for the display filter by clicking on the corre-
sponding icon in the tool bar (refer to section 7.3).
4.1.2 Activating/Deactivating a Display Filter
This function consists in applying or removing the current display filter to all the views of the current map.
To activate/deactivate a display filter, use the menu path:
View > Activate Filter
When the display filter is activated:
a tick appears in the small square located just before the menu item
the current view in the view area of the main window displays only the symbols whose properties match
this filter
the icon corresponding to the display filter in the tool bar is no longer crossed out (refer to section 7.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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
43
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4.1.3 Configuring a Command Filter
This function consists in choosing the criteria of a command filter.
A command filter can be used to apply command only on symbols whose properties match the item defined
in the filter.
The configuration and management of the command filters is performed through the Filter Editor window.
To configure a command filter, use the menu path:
View > Edit Command Filter
The Filter Editor window opens (refer to section 4.3).
The first time...
When no filter exists, you can access the Filter Editor window for the command filter by clicking on the
corresponding icon in the tool bar (refer to section 7.3).
4.1.4 Activating/Deactivating a Command Filter
This function consists in applying or removing the current command filter to all the views of the current map.
To activate/deactivate a command filter, use the menu path:
View > Activate Command Filter
When the command filter is activated:
a tick appears in the small square located just before the menu item
the action requested by the client application will concern only the symbols whose properties match this
filter
the icon corresponding to the command filter in the tool bar is no longer crossed out (refer to section 7.3)
The display filter and the command filter are independent. When a display filter is applied, some symbols
may be hidden, but the command filter may involve them even so.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
44
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4.1.5 Zooming in/out a View
This function allows you to zoom in/out the current view in the view area.
There are three main zoom functions:
enlargement of a zone of the view
application of an enlargement/reduction percentage
adaptation to the size of the view area
Zone
To define the view zone to be enlarged:
Use the menu path:
View > Zoom > Box
The cursor becomes a cross which allows you to select a zone that will be enlarged.
Percentage
To apply an enlargement/reduction percentage on all the view displayed in the view area:
Use the menu path:
View > Zoom
Select a percentage in the submenu that appears.
100% corresponds to the display by default.
Adaptation
To adapt the size of the current view to the size of the view area:
Use the menu path:
View > Zoom > Fit
Shortcuts
TVA offers shortcuts for performing more quickly the zoom functions:
type <I> to apply the zoom value by default (100%)
type <Ctrl>+ U to zoom in
type <Ctrl>+ Z to zoom out
type <F> to adapt the view to the size of the view 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
45
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4.1.6 Managing the Related Views
This function consists in associating a view (called related view) to the current one. You can then navigate
at any time from the current view towards the related view.
To manage the related views of the current one, use the menu path:
View > Related Views
The following dialog box opens.
Figure 39. Related Views Dialog Box
This dialog box displays the name of the current view.
The Related Views list presents all the related views that have been associated to the current one.
The Available Views area presents in the form of a tree all the views that can be set as related.
To set a view as related of the current one:
select it in the Available Views area
click on the Add push button
To remove a related view:
select it in the Related Views list
click on the Remove push 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
46
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
To remove all the related view from the Related Views list, click on the Clear push button.
To access a related view from the current one, refer to section 6.1.
4.1.7 Setting the General Parameters of a View
The general parameters of a view are defined as follows:
view name
image used as background
layout
TVA offers two ways of laying out the symbols in a view:
RowColumn layout (by default)
Figure 40. Example of a RowColumn Layout
Each symbol is centered in a cell whose size is based on the largest and highest symbol size in the view.
All the cells are arranged in rows and columns.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
47
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
This layout is independent of possible links between symbols.
You can move a symbol by dragging it on an other symbol in the view. This permutes both symbols.
Cartesian layout
Figure 41. Example of a Cartesian Layout
Each symbol is positioned on the view according to its (x,y) coordinates.
You can move a symbol anywhere in the view. To set the general parameters of a view:
Use the menu path:
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
48
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
View > View Parameters
Figure 42. View Parameters Dialog Box
In the Name field, enter the view name.
Click on the Background option button, then select a image file in the list that appears. Select None to have
no background.
Click on the Layout option button, then select the desired arrangement for the symbols in the view.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
49
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4.1.8 Setting the Display Parameters of a View
This function allows you to choose the way of displaying the symbol properties.
In fact the symbol properties (symbol name, symbol type, different states, ...) can be displayed in the sym-
bol itself and/or by means of an information box (also called balloon).
For more detailed information about the symbols and the information box, refer to section 2.3.
To set the display parameters of a view:
Use the menu path:
View > Display Options
Figure 43. Options Window
In the Property Display Customization table, for each line, select the way of displaying the corresponding
property, by ticking:
the In Renderer column so that the property appears in the symbol itself
the In Balloon column so that the property appears in the information box.
Use the vertical scrollbar to reach the invisible lines.
The display parameters apply to all the views of the current map.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
50
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4.2 Managing the View Filters
A filter is a logical AND expression of elementary items. Each item is a comparison of a property having
one or several values (like the alarm status property for instance).
TVA offers two kinds of filters:
the display filter
the command filter
Display Filter
The display filter is used to hide or display symbols in the current view, according to their properties. For
instance you may want to display in a view only NEs whose alarm status is Critical.
Command Filter
The command filter is used to apply command only on symbols whose properties match the item defined
in the filter.
This kind of filter can be used for applying commands of the client applications. The standard TVA com-
mands (Cut, Copy, Paste, ...) are not concerned.
Filter Editor Window
The Filter Editor window allows you to manage and edit the display and command filters.
For more detailed information, refer to section 4.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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
51
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4.3 Filter Editor Window
The Filter Editor window allows you to:
manage the display and command filters
modify the current display or command filter
To open the Filter Editor window, use the menu path:
View > Edit Filter or Edit Command Filter
or click on the corresponding icon in the tool bar (only when no filter exists).
Figure 44. Filter Editor Window
This window is composed of three areas (from top to bottom):
a menu bar including:
the File menu that allows the filter management (see paragraph 4.3.1)
the Help menu whose About Filter Editor item accesses the contextual help on line (see paragraph 2.5)
a table showing the items of the current filter
a working area containing different fields and buttons and allowing you to modify the current filter (see
paragraph 4.3.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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
52
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4.3.1 Managing Filters
The filter management is performed by using the File menu of the Filter Editor window.
Figure 45. File Menu of the Filter Editor Window
Apply the filter to all the views of the current map.
The icon corresponding to the filter in the tool bar is no longer crossed out (refer to section 7.3).
Close the Filter Editor window
NOTE: If the filter currently displayed in the window has not been applied, a confirmation dialog box opens.
Revert to the currently applied filter
create a New filter
NOTE: This action empties the working area of the Filter Editor window.
Open a new filter, by means of a file chooser dialog box (see paragraph 2.2.3)
Save the current filter
Save the current filter As another name, by means of a file chooser dialog box (see paragraph 2.2.3)
Delete a filter, by means of a file chooser dialog box (see paragraph 2.2.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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
53
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
4.3.2 Modifying the Current Filter
To modify the current filter, use the working area of the Filter Editor window (see figure 45).
Figure 46. Working Area of the Filter Editor Window
The first line is a copy of the column headers of the item table.
The second one is used to add or modify an item.
Adding an Item
To add an item:
Click on the option button located below Property, then select a symbol property.
Click on the option button located below Operator, then select the operator to be applied between the
property and an available value.
According to the property and operator previously chosen, the area located below Value may become a
scrollable list, an option button or a text entry field.
Choose or enter a value.
Click on the Add push button.
The item is added at the end of the table.
Modifying an Item
To modify an item:
Select an item in the table.
The selected item appears in the working area.
Modify one or several elements of this item.
Click on the Modify push button.
The modified item replaces the former one in the table.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
54
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
Removing an Item
To remove an item:
Select an item in the table.
Click on the Remove push button.
The removed item disappears from the table.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
55
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
5 SYMBOL MANAGEMENT
Figure 47. Edit Menu
create a child view (see section 5.1)
add a graphic symbol (see section 5.2)
add a graphic link (see section 5.3)
improve the layout display (see section 5.4)
activate/deactivate the frozen mode (see section 5.5)
select all the symbol of a view (see section 5.6)
cut a symbol (see section 5.7)
copy a symbol (see section 5.8)
paste a symbol (see section 5.9)
delete a symbol from a view (see section 5.10)
delete all the symbols from all the views (see section 5.11)
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
56
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
5.1 Creating a Child View
This function consists in creating an empty child view in the current view.
To create a child view:
Use the menu path:
Edit > Create Child View
Figure 48. Child View Creation Dialog Box
In the Name field, enter the child view name.
Choose a symbol by clicking on it.
Click on the Apply push button.
NOTE: Several child views may be created in the same parent view.
As soon as the last child view is created, click on the Close push button to close the dialog box.
Concerning the use of the Help push button, refer to paragraph 2.2.2.
The position of the child view symbol newly created depends on the layout mode (see paragraph 4.1.7)
of the parent view:
in RowColumn layout mode, the new symbol is positioned at the last row and column of the view area
in Cartesian mode, the symbol is positioned in the center of the view area. If the creation has been re-
quested from the contextual menu, the symbol is positioned at the location of the cursor.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
57
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
5.2 Adding a Graphic Symbol
This function consists in adding a graphic symbol in the current view.
A graphic symbol is a TVA object that is not managed by the client application. It is the reason why it cannot
represent an NE and cannot be supervised
To create a graphic symbol:
Use the menu path:
Edit > Add Symbol
Figure 49. Graphic Symbol Creation Dialog Box
Click on the Type option button, then select a graphic symbol type.
In the User Label field, enter the graphic symbol name.
NOTE: Several graphic symbols may be created by using the same dialog box.
As soon as the last graphic symbol is created, click on the Close push button to close the dialog box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
58
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
5.3 Adding a Graphic Link
This function consists in adding a graphic link in the current view.
A graphic link is a TVA object that is not managed by the client application. It is the reason why it cannot
be supervised.
To create a graphic link:
Select both extremities of the link.
Use the menu path:
Edit > Add Connection
Figure 50. Graphic Connection Creation Dialog Box
The dialog box indicates the user labels of both connection extremities.
Click on the Type option button, then select a graphic link type.
In the User Label field, enter the graphic link name.
Click on the Close push button to close the dialog box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
59
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
5.4 Improving the Layout Display
This function is useful to make the display of the network symbols more understandable (when for example
the links are tangled).
To improve the layout display, use the menu path:
Edit > Layout > Network
When this function is used, the layout is forced to the cartesian mode (refer to paragraph 4.1.7).
5.5 Activating/Deactivating the Frozen Mode
The frozen mode prevents you to move the symbols in a view whose layout is in Cartesian mode.
To activate (or deactivate) the frozen mode, use the menu path:
Edit > Frozen Mode
When the frozen mode is activated, a tick appears in the small square located just before the menu item.
5.6 Selecting All the Symbols
This function allows you to select in an only time all the symbols of the current view.
This selects in fact the objects represented by the symbols. All the symbols representing those objects
are selected in all the views where they appear.
To select all the symbols, use the menu path:
Edit > Select All
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
60
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
5.7 Cutting a Symbol
This function consists in moving the selected symbol in the clipboard so that it can be pasted elsewhere.
NOTE: This does not concern the object represented by the symbol. The selected symbol is re-
moved only from the current view.
Only symbols that represent MEs and child views can be cut.
When an extremity of a link is removed, the link itself disappears.
To cut a symbol:
Select it.
Use the menu path:
Edit > Cut
The selected symbol disappears from the current view, but it remain available to be pasted in another view.
Several symbols can be selected to be cut at the same time.
5.8 Copying a Symbol
This function consists in duplicating the selected symbol in the clipboard so that it can be pasted in the
same view or elsewhere.
This does not concern the TVA object represented by the symbol. Only the symbol selected in the current
view is duplicated.
Only symbols that represent MEs and child views can be copied.
To copy a symbol:
Select it.
Use the menu path:
Edit > Copy
The selected symbol is duplicated in the clipboard.
Several symbols can be selected to be copied at the same time.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
61
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
5.9 Pasting a Symbol
This function consists in pasting in the current view one or more symbols that have been previously put
in the clipboard at the time of a cut or copy operation.
To paste the contents of the clipboard, use the menu path:
Edit > Paste
The contents of the clipboard is moved to the current view.
When pasting a symbol that was a link extremity in a view that contains the other link extremity, the link
is restored, but for a graphic link.
5.10 Deleting a Symbol
This function consists in definitely removing a symbol from the current view.
This does not concern the TVA object represented by the symbol. Only the symbol selected in the current
view is removed, except the offpage connector that is removed in both views where it appears.
Any symbol can be deleted.
To delete a symbol:
Select it. Use the menu path:
Edit > Delete
A confirmation dialog box opens. Several symbols can be selected to be deleted at the same time.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
62
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
5.11 Deleting All the Symbols from All the Views
This function consists in definitely removing all the symbols of a TVA object from all the views.
The disappearance of all the symbols of a TVA object leads to the disappearance of the TVA object itself.
Any symbol can be deleted.
To remove a symbol from all the views, use the menu path:
Edit > Delete from all views
A confirmation dialog box opens.
Several symbols can be selected to be deleted at the same time.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
63
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
6 NAVIGATION
This chapter describes the functions offered by the Go menu that is a way of navigating within the views
of a map (see section 6.1).
You can also navigate:
by means of the tree area (refer to paragraph 2.1.4)
by opening an object (refer to section 3.4)
6.1 Navigating by Using the Go Menu
Figure 51. Go Menu
The items of the Go menu are as follows:
Root: to reach the root view.
Backward: to go back to the view that had been displayed before the current one.
Forward: to go back to the view that had been displayed after the current one.
Related Views: to reach one of the related views of the current one (refer to paragraph 4.1.6).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
64
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
65
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
7 ABBREVIATIONS
ALMAP
ALcatel MAnagement Platform
GIF
Graphics Interchange Format
HTML
Hyper Text Markup Language
JPEG
Joint Photographic Experts Group
ME
Managed Element
MIB
Managed Information Base
NE
Network Element
TVA
Topology Viewer 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
66
02

SC.3: TVA

/ 3AL 89061 AA AA

66
66
END OF DOCUMENT
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
1
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126


TABLE OF CONTENTS
1 GENERALITIES 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 What is PNM? 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 NEs and Links 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Remote NE and Remote Unit 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Static Link 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Management States 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Using PNM in Viewer Mode 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 Views, Maps and Submaps 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2 Objects and Symbols 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Using PNM in Secured Mode 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 USER INTERFACE OVERVIEW 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 PNM Main Window 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Menu Bar 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Tree Area 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 Table Area 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4 Interaction between the Tree Area and the Table Area 22 . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5 PNM Main Window in Viewer Mode 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 PNM Command Dialog Box 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Accessing a PNM Command Dialog Box 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Description 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 Sorting the Elements in the List Box 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4 Modifying the Display of the Elements 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Message Dialog Boxes 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Help On Line 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Using the Help Menu 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Using the Help Push Buttons 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 INVENTORY MANAGEMENT 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Definition of Contents Filter 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Defining an NE Contents Filter 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Changing the Layout of the Tree Area 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Displaying Syntheses in the Tree Area 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
01A 040130
V.SCORTECCI V.PORRO
02 040728 SC04091002
V.SCORTECCI M.ARMANINI
050623 03 SC04091002
V.BALCONI M.ARMANINI
1353NM REL.7.0
VERSION 7.0
OPERATORS HANDBOOK
L.MERLI
L.MERLI
A.CORTESE L.FORESTA

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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
2
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3.4 Selecting/Deselecting All the NEs or Links 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Printing the Content of the Table Area 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Exiting PNM 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 Populating the Map 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8 Selecting NEs or Links on/from the Map 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 OPERATIONS ON NES 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Information about an NE 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Getting Information about an NE 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Modifying the Access State of an NE 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Switching the NE Access State from OS to Local 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Switching the NE Access State from Local to OS 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Requesting a Local Access from a Craft Terminal 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 Granting the Local Access for All NEs in Requested Access State 58 . . . . . . . . . . . . . . . . .
4.2.5 Denying the local access for All NEs in Requested Access State 58 . . . . . . . . . . . . . . . . . .
4.3 Management State Consultation 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 Consulting the NE Management States 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Consulting the Link Management States 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Managing the NE MIB 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 Uploading the NE MIB into the OS 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2 Downloading Information from the OS into the NE MIB 64 . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3 Compare the NE MIB and Its Image in the OS 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4 Dumping the NE MIB into a File 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 Managing the NE Time 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1 Getting the Time of an NE 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2 Synchronizing the NE Time with the OS Time 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 Managing the Administrative State of an NE 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 Managing the Supervision of an NE 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.1 Starting the NE Supervision 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.2 Stopping the NE Supervision 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.8 Resynchronizing PNM 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9 Uploading the Remote Inventory 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.10 Ping NE 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 INVENTORIES AND NAVIGATION 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Accessing the Global NE Inventory 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Definition of an Inventory Selection Filter 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1 Defining an NE Inventory Selection Filter 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Navigation towards Other Applications 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 Alarm Management 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2 Accessing the Alarm Management 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.3 Visualizing Alarm Information 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.4 Navigating towards an Equipment View 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Creation/Deletion Monitoring 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Monitoring the Creation/Deletion in Viewer Mode 92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 Accessing the Map NE Inventory 95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Accessing the Map Complement NE Inventory 97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8 Definition of a Selection Filter from the Viewer Window 98 . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8.1 Defining an NE Selection Filter on the Current Map 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 CREATION/DELETION OF NES OR LINKS 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Creation of NEs or Links 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Creating an NE 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2 Creating a Remote NE 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
3
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.1.3 Creating a Static Link 106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Deletion of NEs and Links 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 Deleting an NE 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2 Deleting a Static Link 109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Modification of NE or Link Characteristics 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Modifying the NE Characteristics 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Cloning an NE 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Declaration of the NE and OS Addresses 115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.1 Setting an NE Address 115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5.2 Changing an OS Address 119 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 EXTERNAL TEXT 121 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 TERMINOLOGY 123 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 Abbreviations 123 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Glossary 125 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
4
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
FIGURES
Figure 1. NE: Global Inventory window 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. NE menu bar: Global Inventory window 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Example of pulldown menus 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Tree area 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Popup menu of the Tree Area 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Table Area 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. PNM Main Window (ALMAP TVA Viewer Mode) 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Example of PNM command dialog box 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Example of an Error Message Dialog Box 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Help Menu 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Inventory Menu 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Inventory menu in viewer mode 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Example of an NE Inventory Filter Dialog Box (Static Attributes Panel) 33 . . . . . . . . . . . . . .
Figure 14. Example of an NE Inventory Filter Dialog Box ( Dynamic Attributes Panel) 34 . . . . . . . . . .
Figure 15. Flat Layout 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Hierarchical Layout 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. OS Topology Layout 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. OS Topology Hierarchical Layout 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Network Topology Layout 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Network Topology Hierarchical Layout 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Global Inventory dialog box 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Operations menu. 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Information dialog box for an NE 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Information dialog box for a Link 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Local AccessSwitch to Local Dialog Box 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Local AccessSwitch to OS Dialog Box 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. Local AccessSwitch to Requested Dialog Box. 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Requested Monitoring Dialog Box 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Local AccessRequested to Local Dialog Box 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Local AccessRequested to OS dialog box 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Current Status Dialog Box for an NE 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Current Status Dialog Box for a Link 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. MIB AlignmentAlign MIB Up Dialog Box 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. MIB AlignmentAlign MIB Down (Manual) Dialog Box 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. MIB AlignmentAlign MIB Down (Global) Dialog Box 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. MIB AlignmentCompare MIBs Dialog Box 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. MIB AlignmentDump MIB Dialog Box 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Time ManagementGet Time Dialog Box before the Execution of the Command 68 . . . . .
Figure 39. Time ManagementGet Time Dialog Box after the Execution of the Command 69 . . . . . . .
Figure 40. Time ManagementSet Time Dialog Box before the Execution of the Command 70 . . . . .
Figure 41. Time ManagementSet Time Dialog Box after the Execution of the Command 71 . . . . . . .
Figure 42. AdministrationLock Dialog Box 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Administration. Unlock Dialog box 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Example of a Supervision Dialog box 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. SupervisionStop Dialog Box 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Message dialog Box for the Resynchronization of PNM 78 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Upload Remote Inventory Dialog Box 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. Menu Operations : Ping NE 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Ping NE function window 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. Select NEs on a map 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
5
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 51. Ping result for selected NEs 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 52. Tools Menu 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 53. Tools Menu in Viewer Mode (from an Inventory Window) 86 . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. Tools Menu in Viewer Mode (from the Viewer Window) 87 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. Monitor dialog box (Creation Monitoring Panel) 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. Monitor Dialog Box (Creation Monitoring Panel) in Viewer Mode 92 . . . . . . . . . . . . . . . . . . .
Figure 57. Monitor Dialog Box (Deletion Monitoring Panel) in Viewer Mode 93 . . . . . . . . . . . . . . . . . . .
Figure 58. NE: Map Inventory Window 95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. NE: Complement Inventory Window 97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. Declarations Menu 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. NE Creation Dialog Box 101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. NE Creation Dialog Box in Viewer Mode 103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. Remote NE Creation Dialog Box 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. Deletion Dialog Box 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. Modification Dialog Box for a basic NE 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. Modification Dialog Box for a Dynamic Link 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. Example of a Clone Dialog Box 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. Address Dialog Box for a Q2 Address 115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. Address Dialog Box for a QB3* Address 116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. Address Dialog Box for a Q3 Address 117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. Example of an Address Dialog Box for an IP Address 117 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. OS Address Dialog Box 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 73. Current Status Dialog Box for an NE when PNM is External Text Enabled 121 . . . . . . . . . . .
Figure 74. Example of a Filter Dialog Box (Static Attributes Panel) when PNM is External Text
Enabled 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
6
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
7
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
1 GENERALITIES
1.1 What is PNM?
In order to improve Alcatel TMN subsytems management, Alcatel Telecom has launched an internal initia-
tive which aims to provide Alcatel development centers with generic components to be reused in their own
network management products.
PNM (Physical Network Manager) is such a generic component being developed within the ALMAP pro-
gram.
PNM is devoted to the integration of EML (Element Management Layer) subsystems. That is, PNM
achieves the integrated management of various kinds of network elements (NEs) which are already indi-
vidually managed by their own EML subsystem.
PNM offers two main functions:
NE Directory: PNM maintains and presents, via the graphical user interface, common information about
the NEs managed in aTMN environment.
Integrated NE Management: PNM allows an operator to perform generic and specific management op-
erations on one or several NEs by coordinating the activity of various element managers (i.e. EML subsys-
tems). Generic operation activation and followup are integrated in PNM while specific operations are del-
egated to the appropriate EML subsystem.
PNM is intended to be integrated into a TMN environment consisting of wide range EML components, each
of them managing NEs of specific types and releases.
The PNM graphical user interface presents the organization of NEs in a suitable format (e.g. geographical
or topological) for the operator, by means of:
an inventory including a tree and a table
a hierarchy of interactive windows called submaps or views (only when PNM is integrated with viewer
and map management applications like ALMAP TVA, HP OVw)
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
8
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
1.2 NEs and Links
This paragraph covers the following topics:
Remote NE and Remote Unit
Composite NE and SubNE
Static Link
Dynamic Link
The elementary building blocks of any telecommunication network are the Network Elements (NEs). The
connection between two NEs is called a link.
PNM can manage:
several types of NEs:
basic NEs (that are not remote NEs)
remote NEs and remote units
static links
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
9
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
1.2.1 Remote NE and Remote Unit
A remote NE is distinguished by its need to be managed by the OS through another NE called master NE.
The remote NE is physically connected to its master NE, which is responsible for the exchange of manage-
ment information between the OS and the remote NE.
A remote unit is an NE component (a board for example) that is connected to a master NE.
1.2.2 Static Link
A static link is used to draw a graphical link only between related NEs. It based on NE attributes which are
not animated. It does not appear in the link inventory.
PNM can manage two types of static links:
hierarchical static links that represent a hierarchical relationship between NEs like for example:
the link between a Q2 NE and its mediation device
the link between a master NE and a remote NE
the link between a master NE and a remote unit
The hierarchical static link management is optional.
generic static links that represent a simple relationship between NEs whatever their type PNM does
not make any control on static links with respect to the topology of the 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
10
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
1.3 Management States
This section presents the different management states of NEs and dynamic links from the OS point of view.
Management states are available for any manageable entity, including remote NEs and remote units. In
this section, NE stands for any manageable entity.
The NE and dynamic link management states are as follows:
NE management states: Supervision, Alignment, Communication, Administrative, Usage, Operational,
Local Access, and a single Alarm status. Dynamic link management states: Supervision, Alignment, Ad-
ministrative,Operational, and a single Alarm status.
Actions undertaken from PNM can have an influence only on the NE management states, not on the link
management states.
The management states are described below. The meanings presented hereafter come from ALMAP.
They could be slightly different:
Supervision state: gives information relative to the supervision state of the NE or the dynamic link. There
are four possible values. The operational state and the access state can then be fixed.
Declared: the NE or the dynamic link is just declared to the OS.
Supervised: the NE or the dynamic link is under supervision.
Activating: the NE or the dynamic link is being brought under supervision and no management tasks
can be performed on it.
Deactivating: the supervision process on the NE or the dynamic link is being stopped and no man-
agement tasks can be performed on it.
Communication state: reflects the capability of the NE to communicate with the EML. This management
state does not concern dynamic links. Possible values are:
Disabled: the communication between the EML and the NE is interrupted.
Enabled: the EML can communicate with the NE.
Administrative state: reflects the administration of a resource. Possible values are:
Locked: the resource is administratively prohibited from performing services for its users.
Unlocked: the resource is administratively permitted to perform services for its users. this is indepen-
dent of its inherent operability.
Usage state: reflects the usage of the NE. This management state does not concern dynamic links. Pos-
sible values are:
Idle: the resource is not currently in use.
Busy: the resource is in use and it has no spare operating capacity to provide for additional users
simultaneouly.
Active: the resource is in use and it has sufficient spare operating capacity to provide for additional
users simultaneouly.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
11
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Alignment state: indicates whether the NE MIB and its image in the OS are aligned or not. There are five
possible values.
Aligning Up: the system is performing a MIB Align Upwards operation. No operation can be done
on the NE or the dynamic links.
Aligning Down: the system is performing a MIB Align Downwards operation. No operation can be
done on the NE or the dynamic links.
Aligned: the NE MIB and its image in the OS are identical. In Config: the NE or the dynamic link is
being configured and no alignment has been undertaken yet.
Misaligned: the NE MIB and its image in the OS are not identical and eventually, the NE or the dy-
namic link has to be reconfigured.
Auditing: the NE or the dynamic link is under OS supervision and the system is comparing the NE
MIB with its image in the OS.
Local access state: denotes the granting or denial of access for management operations on the NE via
the craft terminal. This management state does not concern dynamic links. There are three possible val-
ues.
Granted: the NE can be managed by the local craft terminal.
Requested: the local manager has requested update permission from the remote manager and is
waiting for a reply.
Denied: the NE cannot be managed by the local craft terminal.
Operational state: reflects the capability for the NE or the dynamic link to accept the EML supervision.
There are two possible values.
Disabled: the NE or the dynamic link cannot be supervised. This means the resource is internally
facing a major failure.
Enabled: the NE or the dynamic link can be supervised.
Alarm status: indicates the highest severity alarm currently present on the NE or the dynamic link. There
are six possible values.
Critical: the NE or the dynamic link operational state is disabled, or the NE or the dynamic link pres-
ents malfunctions. An immediate corrective operation is required.
Major: the OS and NE or dynamic link MIBs are misaligned, or the NE or the dynamic link presents
dysfunctions. Urgent corrective operation is required.
Minor: the NE or the dynamic link presents dysfunctions. A corrective operation should be taken in
order to prevent more serious fault (for example service affecting).
Warning: it indicates the detection of a potential or impending service affecting fault before any signif-
icant effects have been felt. Operation should be taken to further diagnose (if necessary) and correct
the problem in order to prevent it from becoming a more serious fault.
Active Pending: the NE or the dynamic link is in a pending state.
Cleared: there is no outstanding alarm within the NE or the dynamic link.
Indeterminate: the OS has not received an update of the current alarms occurring.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
12
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
A mechanism enables the OS to determine whether it manages the supervised NEs or the supervised dy-
namic link. This mechanism enables the OS to detect changes in the NE or in the dynamic link configura-
tion or in the operational state of the NE or the dynamic link. This mechanism is launched automatically
after the NE, or the dynamic link, is brought under supervision by the OS. It is stopped if the OS is shut
down or if the NE or the dynamic link is no longer under supervision.
Any disruption in the communication link between the OS and the NE or the dynamic link results in an up-
date of the management states once the OS has detected the communication failure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
13
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
1.4 Using PNM in Viewer Mode
When PNM is used with a wiever like ALMAP TVA or HP OVw, you can see and manage the NEs in maps
and submaps representing the network topology.
1.4.1 Views, Maps and Submaps
A submap (also called view in TVA) is used to assemble and to display by means of graphical symbols
a set of objects sharing common characteristics (geographical, topological, etc...).
In the map structure, each submap, except the root submap, is part of another submap.
A map (also called main view in TVA) is an organized set of submaps, a hiearchical structure with a start-
ing root at the top.
NOTE: A submap cannot contain itself.
All the submaps contained in a submap must belong to the same map.
A submap containing another submap(s) is called parent submap. A submap contained in a parent sub-
map is called child submap.
CAUTION: CNEs are represented by submaps that must contain only sub NEs. Do not populate these
specific submaps with other NEs than sub NEs.
1.4.2 Objects and Symbols
In the network topology views that are dealt with in this manual, objects are NEs, sites and links (or connec-
tions) between them (see figures 7 and 8).
A symbol on a submap is the representation of an object. Two types of symbols can be distinguished:
Managed symbols: represent supervised entities managed in the OS. They generally represent NEs or
dynamic links. In the NE case, the network characteristics of the symbols (name, network address...) are
defined in the OS.
Graphical symbols: these symbols are not managed by the system but are simply a graphical represen-
tation of an object. They generally represent geographical entities such as sites, static links or connec-
tions.
NOTE:There may be multiple representations (symbols) of the same object in a map. However this object
is defined only once in the OS.
Symbols in a submap can either be explodable or executable ones.
Explodable symbols: they are parent symbols. When you double click on them, they open child submaps
containing other symbols (of managed or graphical type).
Executable symbols: they are associated to the operations detailed below which can be performed on
the managed objects these symbols represent. Launch these operations by double clicking on the consid-
ered symbols.
Different operations (start supervision, stop supervision, ...) may be performed on managed objects.
However, any NE does not necessarily support any operation (depending on the NE type and release, or
depending on the management features available in the OS).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
14
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Moreover, the symbol color of an NE depends on the communication state, supervision state, operational
state and alarm status of this NE and a text annotation is displayed on the symbol to provide more informa-
tion.
1.5 Using PNM in Secured Mode
According to your delivery, PNM is configured to run with or without the security ALMAP SEC generic com-
ponent.
It is out of the scope of this document to detail the access control mechanisms. Let us consider here that
SEC allows the definition of operators access rights by means of operator profiles.
An operator profile defines:
the authorized functions by means of FADs (Functional Access Domains)
the authorized objects by means of OADs (Object Access Domains)
the authorized combinations between these FADs and OADs
A user can perform an action on an object only if the corresponding function, the object and the function/ob-
ject combination are in his/her operator profile.
In the PNM context, access rights consist, from the operators point of view, in the access to a restricted
(or not) number of functions of PNM (this means the possibility to use them) and in the possibility to man-
age NEs/links belonging to predefined Access Control Domains (ACD).
As an operator and in case your PNM application is provided with the access control features, your access
rights will be defined by the current available menu items and domains (containing NEs/links).
The Access Control Domains that are available to you are listed in the Access Control Domains popup
list of all the NEs/links management dialog boxes.
In case PNM is supposed to run in nonsecured mode, the ACD concept appears nowhere.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
15
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2 USER INTERFACE OVERVIEW
This chapter deals with:
the PNM main window
the PNM command dialog box
the message dialog boxes
the help on line
NOTE: All what concerns the use of PNM in viewer mode is described in specific sections or indicated in
the margin by PNM in Viewer Mode.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
16
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.1 PNM Main Window
The PNM main window is the first window that opens at PNM launching, i.e. with PNM in Viewer Mode
the Topology manager window is presented. From this window, you can access all the functions offered
by PNM.
PNM in Viewer Mode
In viewer mode, see paragraph 2.1.5.
NE: Global Inventory window
The NE: Global Inventory window is composed of two areas (from top to bottom):
Figure 1. NE: Global Inventory window
a menu bar (see paragraph 2.1.1)
a working area divided into two other areas:
on the left: the tree area (see paragraph 2.1.2)
on the right: the table area (see paragraph 2.1.3)
Resizing the Tree and Table Areas
To horizontally resize the two parts of the working area, drag and drop the vertical separation bar.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
17
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.1.1 Menu Bar
Figure 2. NE menu bar: Global Inventory window
The menu bar contains pulldown menus that allows you to access most of PNM functionalities.
To use a pulldown menu, click on it. The available items appears in form of a list. Select an item by clicking
on it.
Conventions
Figure 3. below shows the conventions used within the pulldown menus.
Figure 3. Example of pulldown menus
The conventions used in the pulldown menus are as follows:
...: Some item names are immediately followed by suspension points that mean a dialog box will open.
When there is not any suspension points, the action is immediately performed.
Submenu: A right arrow on the right of a menu item means a submenu exists from this item.
Mnemonic: Each menu and item name includes an underlined character called mnemonic. You can more
quickly access a menu or a menu item by typing <Alt> then its mnemonic.
Shortcut Key: A shortcut key is a sequence of keys located in the right of some menu items. You can also
type this shortcut key to more quickly access a menu item.
Tick Box: Some menu item are preceded by a small square you can tick (or untick) in order to activate
(or deactivate) an option.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
18
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
PNM Menu Entities
The PNM menu entities are as follows:
Inventory pulldown menu: see chapter 3
Operations pulldown menu: see chapter 4
Tools pull downmenu: see chapter 5
Declarations pulldown menu: see chapter 6
Help menu items: see paragraph 2.4.1
PNM in Viewer Mode. In viewer mode, the PNM menu entities are also inserted in the menu bar of the
viewer window, except the Inventory pulldown menu that is specific to the Inventory window.
2.1.2 Tree Area
Figure 4. Tree area
The tree area displays the NEs according to a layout you can choose (see section 3.2). The layout by de-
fault is the layout presented in the Popup Menu paragraph below.
At the bottom of the tree area, the Total Count field indicates the total number of NEs visible in the inventory.
If PNM is in nonsecured mode and if no contents filter is applied, this is the total number of NEs managed
by PNM.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
19
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Expandable Node
A [+] (or []) symbol preceding a node means this one contains a branch that can be expanded (or respec-
tively shrinked). There are two ways of expanding/shrinking a node: you can either click on the [+] or []
symbol or doubleclick on the node label (for example Africa in the previous figure).
Popup Menu
A right click on the [+] or [] symbol of a node opens a popup menu (see Figure 5. ).
Figure 5. Popup menu of the Tree Area
This popup menu allows you to:
expand, shrink or select the NEs of:
the whole subtree: all what is under the current node
the first level: all what is from the first level under the current node
the current node
display the tree completely expanded except the last level (Pretty Layout option available only for the root
node)
Popup Property Panel
A right click anywhere in the tree (except on a [+] or [] symbol) opens a popup panel. This panel displays
the properties of the NE located just over an horizontal line that appears in the same time as the popup
panel.
When you move the mouse while holding down the right button, the property panel displays in real time
the information corresponding to the NE under which the horizontal line is positioned.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
20
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Selection Mechanisms
To select an NE in the tree area, click simply on it.
To perform a multiselection, you can:
press the <Ctrl> key while clicking on an NE to add (or remove) this one to (from) the selection
press the <Shift> key while clicking on an NE to add all the NEs located between this one and the last se-
lected NE
use the popup menu (see above)
Selected NEs appears in reverse video.
Displaying the Next or Previous Selected NE
When several NEs are selected in the tree area, you can go from the one to the next (previous) one by
right clicking on the bottom (top) triangle of the scroll bar. The table part is updated accordingly.
Interaction with the Table Area
The selection and the display in the tree area interact with those ones of the table 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
21
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.1.3 Table Area
Figure 6. Table Area
The table area displays the characteristics (columns) of the NEs managed by PNM (rows). The number
and order of the columns is completely configurable.
Resizing Columns
To resize a column, move the cursor to the right vertical line of its header. When the cursor becomes an
horizontal double arrow, you can click then move right or left the mouse to enlarge or reduce the column
width.
Moving Columns
To move a column, right click on its header then drag and drop it.
Sort
By default, the data displayed in the table are sorted according to the layout of the tree area. You can sort
them in another way by means of the column headers.
For example if you want to sort the data by names, click on the header of the Name column. The small
square located just over the vertical scroll bar becomes a downarrow indicating the data are now sorted
by increasing order on the name. If you want to sort them by decreasing order, click on this downarrow
that becomes at this time an uparrow.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
22
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Filter
At the bottom left of the table area, the Contents Filter Active check box allows you to apply a filter to the
NEs list displayed in the table.
When you open the NE: Global Inventory window for the fist time, there is no contents filter and the check
box is grey. If you click on it, the NE Global Inventory Filter dialog box appears allowing you to set the con-
tents filter criteria .
When you click on the check box after having defined a contents filter, the check box becomes green and
the contents filter that you have been defining is applied to the NE list.
Afterwards, this check box operates like a toggle to apply or not the contents filter. To open again the NE
Global Inventory Filter dialog box, you must use the menu bar.
The total number of NEs matching the contents filter is displayed in the Total Count field .
Popup Property Panel
Like in the tree area , a right click anywhere in the table (except in the column headers) opens a popup
panel. This panel displays in a vertical form all the characteristics of the NE located just over an horizontal
line that appears in the same time as the popup panel.
When you move the mouse while holding down the right button, the property panel displays in real time
the information corresponding to the NE under which the horizontal line is positioned.
Selection Mechanisms
The selection mechanisms in the table area are the same as in the tree area (see section 2.1.2), but you
can also select or unselect all the NEs in the list by clicking on the losange located at the right bottom of
the table. When at least one NE is selected, the losange is red.
Displaying the Next or Previous Selected NE
As in the tree area, when several NEs are selected in the table area, you can go from the one to the next
(previous) one by right clicking on the bottom (top) triangle of the scroll bar.
Counting of the Selected NEs
At the bottom right of the table area, the Selected Count field indicates the number of NEs currently se-
lected in the table. On the right of this field, a toggle allows you:
to be aware when at least one NE is selected (activated red toggle) or to select all the NEs to deselect
all of them (unactivated toggle)
interaction with the Tree Area
The selection and the display in the table area interact with those ones of the tree area.
2.1.4 Interaction between the Tree Area and the Table Area
Interaction between the Tree Area and the Table Area. Any NE selected in one of the area is also selected
in the other area.
Searching for a Selected NE
When you select for example an NE in the tree area, maybe it is not visible in the table area. To make it
visible, doubleclick on it in the tree area and then it appears in the first line of the table. This process also
operates from the table area towards the tree 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
23
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.1.5 PNM Main Window in Viewer Mode
In viewer mode, the first window that appears at PNM launching provides you with the display of symbols
representing maps, submaps (or views) and links between these symbols.
Figure 7. PNM Main Window (ALMAP TVA Viewer Mode)
PNM Menus
When integrated with a viewer, PNM inserts its own menu entities ( Operations, Tools, Declarations pull
down menus and specific items in the Help pulldown menu) in the viewer menu bar.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
24
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.2 PNM Command Dialog Box
PNM provides a generic dialog box which allows you to perform commands on elements such as NEs or
dynamic links.
2.2.1 Accessing a PNM Command Dialog Box
To access a PNM command dialog box, you have first to select elements either manually (see the Selection
Mechanisms paragraphs in sections 2.1.2 and 2.1.3) or by using a selection filter (see section 5.3), then
select an action to be performed on those elements by means of the menu bar.
PNM in Viewer Mode
In viewer mode, you can also use the selection filter from the viewer 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
25
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.2.2 Description
Figure 8. shows an example of a PNM command dialog box.
Figure 8. Example of PNM command dialog box
A PNM command dialog box includes:
a title bar indicating the main function of the dialog box (Supervision in the example)
a top zone containing the command label (Stop in the example) and a list box with three columns:
?: this column contains toggles whose aspect indicates the states of the selected elements:
Unactivated (Pending): the element is waiting for triggering
Activated blue (Not Applicable): the element does not support the command: for example if you want
to perform a start supervision on an already supervised NE
Activated black (User Canceled): you have decided to cancel the command for this particular element
Activated green (Success): the operation performed on the element has succeeded
Activated yellow (Security Refused): the operator access rights do not allow to perform the command
on this element.
Activated red (Error): the operation performed on the element has failed
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
26
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
If there is no toggle on a line, this means it has been hidden. In fact, you have the possibility to hyde a toggle
in order to make easier your reading of the list box.
NOTE: When PNM runs in nonsecured mode, the activated yellow toggle does not exist.
NOTE: When PNM has been configured to run without precondition, the activated blue toggle does not
appear.
Name: this column displays the user labels of the selected elements.
Command Status: this column displays extra information related to the command. It is correlated with the
? column:
before performing operation: this column displays the command status related to the operation to be
performed, for example Waiting for triggering or Wrong supervision state.
during and after the operation: this column displays the result information related to the performed
operation, for example Success, Error or a customized error message.
An horizontal progress bar showing the work in progress. During this phase, the Close push button is de-
activated (greyed).
A field area displaying information about elements present in the list box. This area can contains up to six
fields:
Pending: this field gives the number of elements in the Pending state displayed in the list box
Not Applicable: this field gives the number of elements in the Not Applicable state displayed in the
list box
User Canceled: this field gives the number of elements in the User Canceled state displayed in the
list box
Security Refused: this field gives the number of elements in the Security Refused state displayed
in the list box
Success: this field gives the number of element in the Success state displayed in the list box. It is
filled up during the operation process
Error: this field gives the number of elements in the Error state displayed in the list box. It is filled up
during the operation process.
N.B. When PNM runs in nonsecured mode, the Security Refused field does not exist.
N.B. When PNM has been configured to run without precondition, the Not Applicable field does not
appear.
A disc symbol is displayed on the left of each field (except for Pending). The disc is empty or full if the corre-
sponding toggles are respectively all hidden or all displayed in the list box.The disc is half full if at least
one of the corresponding toggles is hidden in the list box.
A bottom area containing three push buttons:
Apply: to perform the operation
Close: to close the dialog box
Help: to access the help on line related to this dialog box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
27
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Dynamical Updating
The PNM command box is dynamically updated. For example a lot of commands need the NE to be Super-
vised. If you select a Declared NE and open the PNM command window, the line corresponding to this
NE is tagged Not Applicable (activated blue toggle) and the Command Status column indicates Wrong
supervision state.
You can then open a second PNM command window to start the NE. Once the NE is Supervised, the first
PNM command window is updated: the line corresponding to the NE is tagged Pending (unactivated
toggle) and the Command Status column indicates Waiting for triggering.
2.2.3 Sorting the Elements in the List Box
At any time, you can sort the elements in the list box by clicking on the column headers that operates like
toggle buttons:
activated: sort on the status in the following order: Error, Success, Pending, Security Refused, Not
Applicable, User Canceled then hidden toggles
Name activated: sort in alphabetical order on the element name
Command Status activated: sort in alphabetical order on the command status
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
28
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.2.4 Modifying the Display of the Elements
You can modify the display of the elements before, during and after the command execution.
Before the Command Execution
You have different ways of modifying the display of the elements in the list box:
by clicking on the toggles of the ? column:
Unactivated: the toggle becomes activated black, that corresponds to the User Canceled state
Activated black: the toggle comes back unactivated, that corresponds to the Pending state
Activated blue: the toggle disapears from the list box and cannot be displayed again, except by click-
ing on the corresponding toggle of the field area
by clicking on the blue or black toggles of the field area in order to display or hide all the related toggles
present in the list box
The disc located on the left of the Not Applicable or User Canceled field is empty or full if the corresponding
toggles are respectively all hidden or all displayed in the list box. It is half full if at least one of the corre-
sponding toggles is hidden in the list box.
N.B. Before executing the command, the Success and Error fields are empty and the corresponding
toggles not active
During or after the Command Execution
As previously, you have two ways of modifying the display of the elements in the list box:
by clicking on the toggles of the ? column. These toggles disappear from the list box and cannot be
displayed again, except by clicking on the corresponding toggles of the field area
by clicking on the blue, black, green, red or yellow toggles of the field area in order to display or hide
all the related toggles present in the list box:
The disc located on the left of the Not Applicable, User Canceled, Success, Error or Security Refused field
is empty or full if the corresponding toggles are respectively all hidden or all displayed in the list box. It is
half full if at least one of the corresponding toggles is hidden in the list box.
N.B. When PNM runs in nonsecured mode, the Security Refused field and the corresponding disc
and yellow toggle do not exist.
N.B. When PNM has been configured to run without precondition, the Not Applicable field does not
appear
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
29
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.3 Message Dialog Boxes
PNM uses small dialog boxes like in figure below to display information or error messages.
There are two kinds of error error message dialog boxes:
when the error occurs at the triggering of the command, the error message dialog box that opens disap-
pears one minute later
when the error occurs during the execution of the command, the error message that opens is modal, i.e.
it must be closed before any other operation in the window or dialog box from which the failed command
was launched
NOTE: The error message dialog boxes are modal, that means you must take the error message into ac-
count then close the dialog box before any other operation on the application.
Figure 9. Example of an Error Message Dialog Box
Click on the Close push button to close the dialog box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
30
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
2.4 Help On Line
PNM provides an help on line you can access by using:
the Help menu
the Help push buttons
In both cases the help on line is displayed by means of an HTML browser like Netscape for example.
2.4.1 Using the Help Menu
The Help menu (see below figure) is available in the menu bar of the Inventory windows.
Figure 10. Help Menu
This items of the Help menu are as follows:
On Inventory: to access the help on line at the page that describes the current Inventory window
On PNM: to access the home page of the PNM help on line
PNM in Viewer Mode
In viewer mode, the On PNM item is moved in the Help menu of the viewer.
2.4.2 Using the Help Push Buttons
An Help push button is available in most of the dialog boxes. In that case, the help on line opens at the
page which describes the current dialog box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
31
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3 INVENTORY MANAGEMENT
This chapter describes the functions offered by the Inventory menu
Figure 11. Inventory Menu
set the contents filter
change the layout of the tree area
display syntheses in the tree area
select / deselect all the NEs or links
print the contents of the table area
exit PNM
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
32
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
PNM in Viewer Mode
In viewer mode, the Inventory menu is slightly different.
Figure 12. Inventory menu in viewer mode
The changes are as follows:
the Population item allows you to populate the map. It is greyed if the current map is readonly.
the Select On Map and Select From Map items allow you to find in the viewer window the NEs or links
selected in an Inventory window, and respectively to find in an Inventory window the NEs or links selected
in the viewer window.
the Close item replaces Exit. It allows you to close the current Inventory window and return to the viewer
window.
Those new items manage the relationships with the viewer.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
33
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3.1 Definition of Contents Filter
This function consists in defining the display filter criteria for:
the NEs of an NE Inventory window
3.1.1 Defining an NE Contents Filter
To define the display filter criteria for the NEs of an NE Inventory window, use the menu path:
Inventory > Contents Filter
A dialog box like in figure below opens.
Figure 13. Example of an NE Inventory Filter Dialog Box (Static Attributes 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
34
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 14. Example of an NE Inventory Filter Dialog Box ( Dynamic Attributes Panel)
This dialog box contains two panels in which you recognize all the NE attributes present in the table area
of the NE Inventory 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
35
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Configuring the Filter
In the Static Attributes panel, use the option buttons to filter the NEs according to their Type and Release,
Supervision Area, EML Domain and/or ACD.
NOTE: When PNM runs in nonsecured mode, the ACD option button does not exist.
Enter text to filter the NEs according to their User Label and/or Location Name. You can use the following
special characters (wildcards):
*: represents any sequence of characters
?: represents any single character
[xyz]: represents x or y or z character
[xz]: represents x to z characters in the ASCII order
To filter the NEs according to their creation date, activate the Creation From and/or Creation To toggle and
modify the different parts of the date by clicking on them then using the up/down arrows.
In the Dynamic Attributes panel, activate the toggles (that become green) to filter the NEs according to
their management states.
Resetting the Filter
In the Static Attributes panel, clicking on the Reset push button amounts not to filter. In that case, all the
NEs are displayed.
In the Dynamic Attributes panel, the Reset push button operates like a global toggle to activate or deacti-
vate all the other ones. In both cases, all the NEs will appear in the table area of the NE Inventory window.
This just allows you to more quickly eliminate (or keep) some attributes rather than keep (or respectively
eliminate one by one all the other ones.
Applying the Filter
To make the filter active, click on the Apply push button.
In the NE Inventory window, the Contents Filter Active check box becomes green.
Closing the Dialog Box
To close the dialog box, click on the Close push button.
This action does not deactivate the filter
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
36
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3.2 Changing the Layout of the Tree Area
You can change the layout used in the tree area to display the NEs or links.
To access this function, use the menu path:
Inventory > Layout
A submenu opens in which you can select:
Flat: to display the NEs or links on a single level
Hierarchical: like previously but with the hierarchy of the remote NEs, remote units and subNEs
OS Topology: to display the distribution of the NEs according to the supervision area and the EML domain
they belong to
OS Topology Hierarchical: like previously but with the hierarchy of the remote NEs, remote units and sub
NEs
Network Topology: to display the distribution of the NEs according to their location name
Network Topology Hierarchical: like previously but with the hierarchy of the remote NEs, remote units and
subNEs
Hierarchical Layout
In a hierarchical layout, remote NEs and remote units appear as children of master NEs. In the same way,
subNEs are represented as children of composite NEs.
NOTE: The figure below show an example for the tree area of an NE Inventory window. The same subme-
nu also applies to the tree area of the Link Inventory windows, except the Hierarchical items that have
sense only for remote NEs, remote units and subNEs.
A checked box in the submenu indicates the chosen layout.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
37
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 15. Flat Layout
Figure 16. Hierarchical Layout
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
38
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 17. OS Topology Layout
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
39
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 18. OS Topology Hierarchical Layout
Figure 19. Network Topology Layout
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
40
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 20. Network Topology Hierarchical Layout
Customized Topology
In case of customized topologies defined during its integration, PNM provides you with the access to the-
corresponding layout thanks to the bottom part of the Layout submenu.
Contents Filter and Hierarchical Layout
In case of contents filtering on remote NEs, remote units and/or subNEs, the master NEs and CNEs-
should not appear in the tree. But in case of hierarchical layout, they are displayed even so, preceded by
a red point.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
41
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3.3 Displaying Syntheses in the Tree Area
PNM can display different syntheses (for example alarm status, supervision state, communication state
or any other) in the tree area. This depends on the way PNM has been customized during its integration.
To access this function, use the menu path:
Inventory > Synthesis
A submenu opens in which you can activate (checked box) one or several syntheses. Checked boxes indi-
cates active syntheses.
You can see in Figure 4. an example of a synthesis on the NE alarm status by means of icons in form of
small colored baloons. Note that any other icon may be used by PNM customization.
Note also that in the cases of alignment state, alarm status and external text, of the synthesis is transmitted
from the NEs towards the root of the tree. This is especially useful when you see for example a critical alarm
status at the root level and you want to know what NE is at the origin of the critical alarm.
On the other hand, the master NEs and CNEs have their own states that do not reflect the ones of the
remote NEs, remote units and subNEs.
Showing / Hiding All the Syntheses
To show (or hide) all the syntheses, use the menu path:
Inventory > Synthesis > Show All (or Hide All)
Exclusive Mode
When activated (checked box), the exclusive mode allows you to activate the syntheses one by one.
When the exclusive mode is deactivated, you can activate several syntheses at the same time.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
42
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3.4 Selecting/Deselecting All the NEs or Links
This function allows you to select or deselect all the NEs or links displayed in an Inventory window
Selecting All
To select all the NEs or links, use the menu path:
Inventory > Select All
Another way of selecting all the NEs or links is to click on the toggle located at the bottom right of the table
area.
Deselecting All
To deselect all the NEs or links, use the menu path:
Inventory > Deselect All
Another way of deselecting all the NEs or links is also to click on the red toggle located at the bottom right
of the table 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
43
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3.5 Printing the Content of the Table Area
This function allows you to print all the NEs (or links) displayed in the table area or only the selected ones.
Printing the Selected NEs
To print the selected NEs or links, use the menu path:
Inventory > Print Selected
Printing All the NEs
To print all the NEs or links, use the menu path:
Inventory > Print All
3.6 Exiting PNM
To exit PNM, use the menu path:
Inventory > Exit
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
44
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3.7 Populating the Map
This function allows you to select the policy of creation of the NE symbols. It is available only when PNM
is integrated with a viewer. Proceed as follows:
Use the menu path:
Inventory > Population
Figure 21. Global Inventory dialog box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
45
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
In the Population Input area, decide if the population concerns only the NEs currently selected in the NE:
Global Inventory dialog box (Selected NEs toggle activated by default) or all the NE (click on the All NEs
toggle).
NOTE: After a population operation, the Selected NEs toogle always comes back to the activated position.
In the Population Mode area, choose the way of populating the map by activating one of the following
toggles:
OS Topology: PNM uses the supervision area and the EML domain to create (or to choose if italready
exists) the necessary submaps.
For example, if the supervision area is Area1 and the EML domain value is 100, PNM creates a first sub-
map named Area1 in the root submap, theml_domain_100 into the Area1 submap, then put the NE
symbol into the eml_domain_100 submap.
Network Topology: PNM uses the location name to create (or to choose if it already exists) the necessary
submaps.
For example, if the location name is submap1/submap2, PNM creates a first submap named submap1,
then a second submap named submap2 into the submap1 submap, then put the NE symbol into the
submap2 submap.
If the location name has not been defined at the NE creation, the NE symbol will be created into the root
submap.
Submap Topology: in case of customized topologies defined during its integration, PNM allows you to
select one of them by means of an option button.
Submap Topology: PNM creates the NE symbol in an existing submap you can choose by using the option
button.
In the Population Options area, you may activate two options:
No duplication: when activated, this option prevents the NE symbols from being duplicated in the same
submap during population operations.
Hierarchical: when this option is activated, the remotes NEs, remote units and subNEs are managed
with the following rule: the remote NEs are located on the same submap as their master NE, the remote
units are located in a submap associated to their master NE and the subNEs are located in a submap
associated to their composite NE.
If this option is not activated, all the NEs are treated on the basis defined in the Population Mode area.
Launching the Population
To start the population, click on the Apply push button.
The NE symbols corresponding to the NEs selected in the NE: Global Inventory window appears in the
PNM main window, into the suitable submaps.
If an error is detected, the symbols are created in a particular submap named Map_population_Error.
This submap is attached to the root submap.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
46
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
3.8 Selecting NEs or Links on/from the Map
Selecting NEs or Links on/from the Map
Those functions allows you to visualize in an Inventory window the NEs or links selected in the map and
vice versa.
Selecting NEs or Links on the Map
To locate in the map the NEs or links selected in an Inventory window, use the menu path:
Inventory > Select On Map
The NEs or links selected in an Inventory window are highlighted in the map.
Selecting NEs or Links from the Map
To display in an Inventory window the NEs or links selected in the map, use the menu pathInventory >
Select From Map. The NEs or links selected in the map appear in reverse video in the Inventory 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
47
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4 OPERATIONS ON NES
This chapter describes the functions offered by the Operations menu.
Figure 22. Operations menu.
get information about an NE or a link
modify the access state of an NE
consult the management states of an NE or a link
manage the NE MIB
manage the NE time
manage the administrative state of an 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
48
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
manage the supervision of an NE
resynchronize PNM with the EMLs
upload the remote inventory
ping one or more NEs
The Operations menu is configurable.
PNM in Viewer Mode
By default the Operations menu is identical to the one of the viewer window.
4.1 Information about an NE
This section explains how to display the characteristics of:
an NE
4.1.1 Getting Information about an NE
To get information about an NE, proceed as follows:
Select an NE in the NE: Global Inventory window.
Use the menu path:
Operations > Information
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
49
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 23. Information dialog box for an NE
This dialog box is readonly.
PNM in Viewer Mode
Like the NE Creation dialog box, the Information dialog box in viewer mode contains an additional field
named Comments.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
50
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 24. Information dialog box for a Link
4.2 Modifying the Access State of an NE
The NE access state indicates if the NE is managed by the OS or from a craft terminal. This section covers:
switch the NE access state from OS to local
switch the NE access state from local to OS
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
51
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
request a local access from a craft terminal
grant the local access for all NEs in requested access state
deny the local access for all NEs in requested access state
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
52
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.2.1 Switching the NE Access State from OS to Local
This function allows a craft terminal located next to the NE to manage it instead of the OS. This function
is available only from PNM installed in the supervision room. To switch the NE access state from OS to
local, proceed as follows:
In the NE: Global Inventory window, select an NE whose local access state is Denied.
Use the menu path:
Operations > Access State > Local
Figure 25. Local AccessSwitch to Local Dialog Box
In the Local Access column of the NE: Global Inventory window, the NE local access state changes to-
Granted
Once the NE is in local access state, the OS cannot manage it anymore. However it continue to provide
some services like:
the reception and processing of alarms
the switching back to the OS access state
The access state of a remote NE or a remote unit cannot be modified as it keeps aligned on the access
state of its master 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
53
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.2.2 Switching the NE Access State from Local to OS
This function allows the OS to manage afresh an NE that was under control of a craft terminal.
To switch the NE access state from local to OS, proceed as follows:
In the NE: Global Inventory window, select an NE whose local access state is Granted. Use the menu
path:
Operations > Access State > OS
Figure 26. Local AccessSwitch to OS Dialog Box
In the Local Access column of the NE: Global Inventory window, the NE local access state changes to De-
nied.
The access state of a remote NE or a remote unit cannot be modified as it keeps aligned on the access
state of its master 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
54
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.2.3 Requesting a Local Access from a Craft Terminal
This function allows a craft terminal to request a local access to the NE it wants to control.
This function is available only from PNM installed in a craft terminal.
To request a local access, proceed as follows:
In the NE: Global Inventory window, select an NE you want to manage by means of the craft terminal.
Its local access state must be Denied.
Use the menu path:
Operations > Access State > Requested
Figure 27. Local AccessSwitch to Requested Dialog Box.
In the Local Access column of the NE: Global Inventory window, the NE local access state changes to Re-
quested.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
55
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
The following dialog box appears on PNM installed in the supervision room.
Figure 28. Requested Monitoring Dialog Box
This dialog box warns you (if you are an operator in the supervision room) that the local access state of
an NE is Requested.
As long as you do not answer this request, the New Requested NEs toggle remains red and you cannot-
close the dialog box.
So you must grant or deny the local access request by clicking on the Requested to Granted or Requested-
to Denied push button.
As soon as you click on one of the two push buttons, the New Requested NEs toggle becomes inactive
and the No New Requested NEs toggle becomes green.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
56
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Request Granted
If you want to grant the request, the following dialog box opens.
Figure 29. Local AccessRequested to Local Dialog Box
In the Local Access column of the NE: Global Inventory window, the NE local access state changes to-
Granted.
Now you can close the Requested Monitoring dialog box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
57
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Request Denied
If you want to deny the request, the following dialog box opens.
Figure 30. Local AccessRequested to OS dialog box
In the Local Access column of the NE: Global Inventory window, the NE local access state changes to De-
nied.
Now you can close the Requested Monitoring dialog box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
58
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.2.4 Granting the Local Access for All NEs in Requested Access State
PNM allows you in a simple way to grant the local access for all the NEs whose access state is currently
Requested.
NOTE: This function is available only from PNM installed in the supervision room.
To perform this function, use the menu path:
Operations > Access State > Requested to Local
The Local Access Requested to Local dialog box presented in Figure 29. opens.
For using this PNM command dialog box, refer to section 2.2.
In the NE: Global Inventory window, the Local Access of the concerned NEs changes to Granted.
4.2.5 Denying the local access for All NEs in Requested Access State
PNM allows you in a simple way to deny the local access for all the NEs whose access state is currently
Requested.
To perform this function, use the menu path:
Operations > Access State > Requested to OS
The Local Access Requested to OS dialog box presented in Figure 30. opens.
In the NE: Global Inventory window, the Local Access of the concerned NEs changes to Denied.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
59
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.3 Management State Consultation
This section explains how to consult the management states of:
an NE
a link
4.3.1 Consulting the NE Management States
To consult the management states of an NE, proceed as follows:
Use the menu path:
Operations > Show Statuses
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
60
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 31. Current Status Dialog Box for an NE
The NE user label appears in the title of the dialog box.
Unused attributes are greyed.
To close the dialog box, click on Close push 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
61
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.3.2 Consulting the Link Management States
To consult the management states of a link, proceed as follows:
Select a link in the Link: Global Inventory window.
Use the menu path:
Operations > Show Statuses
Figure 32. Current Status Dialog Box for a Link
The link user label appears in the title of the dialog box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
62
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.4 Managing the NE MIB
During the construction of the network topology the creation of a new NE in the network is associated with
the description of its configuration in the OS. This NE configuration may be different from the actual physi-
cal configuration of the NE, described in the NE MIB (Management Information Base), and an alignment
operation may be necessary to adjust the NE MIB and the OS.
Moreover, during the normal functioning of the network it may be necessary to modify the NE configuration,
physically or by using the graphical interface, after what an alignment operation between the NE MIB and
its image in the OS appears to be necessary.
This section explains how to:
upload the NE MIB into the OS
download MIB information from the OS into the NE MIB
compare the NE MIB with its image in the OS
dump the NE MIB into a file
The alignment state of dynamic links is not managed from PNM 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
63
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.4.1 Uploading the NE MIB into the OS
This function consists in aligning the OS with the NE MIB.
This operation may be necessary if:
a communication failure between the OS and the NE has occured
the NE configuration has been changed during a local management by a craft terminal and the NE MIB
differs from its image in the OS
To upload the NE MIB into the OS, proceed as follows:
Use the menu path:
Operations > MIB > Align Upwards
Figure 33. MIB AlignmentAlign MIB Up Dialog Box
The NE configuration contained in the NE MIB is uploaded into the OS. The NE MIB and its image in the
OS are now aligned.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
64
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.4.2 Downloading Information from the OS into the NE MIB
This function consists in aligning the NE MIB with the NE configuration coming from the OS.
This operation may be necessary when the OS is launched or if a new configuration is needed for a NE.
There are two available variations for such an operation:
in a manual alignment, the NE configuration present in the OS is as much as necessary downloaded into
the NE MIB, according to the EML agent decision.
in a global alignment, the NE configuration is unconditionally downloaded.
In the first case, the entire NE configuration could be downloaded as well if needed.
To download the NE configuration from the OS into the NE MIB, proceed as follows:
Use the menu path:
Operations > MIB > Manual Align Downwards
or
Operations > MIB > Global Align Downwards
One of the two following dialog boxes opens.
Figure 34. MIB AlignmentAlign MIB Down (Manual) Dialog Box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
65
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 35. MIB AlignmentAlign MIB Down (Global) Dialog Box
The NE configuration contained in the OS is downloaded into the NE MIB. The NE MIB and its image in
the OS are now aligned.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
66
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.4.3 Compare the NE MIB and Its Image in the OS
This function consists in determining any difference between the NE MIB and its image in the OS.
To compare the NE MIB with its image in the OS, proceed as follows:
In the NE: Global Inventory window, select an NE whose supervision state is Supervised and commu-
nication state is enabled.
Use the menu path:
Operations > MIB > Compare
Figure 36. MIB AlignmentCompare MIBs Dialog Box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
67
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.4.4 Dumping the NE MIB into a File
This function just consists in launching a request (dump the NE MIB into a file) that is processed by the
EML. No result is provided by PNM.
The process is carried out even if the NE is not supervised (its supervision state is declared).
This manual operation is intended to give humanreadable information regarding the NE configuration in
the OS.
To dump the NE MIB into a file, proceed as follows:
Use the menu path:
Operations > MIB > Dump MIB
Figure 37. MIB AlignmentDump MIB Dialog Box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
68
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.5 Managing the NE Time
get the time of an NE
synchronize the NE time with the OS time
4.5.1 Getting the Time of an NE
To get the time of an NE, proceed as follows:
Use the menu path:
Operations > Time > Get
Figure 38. Time ManagementGet Time Dialog Box before the Execution of the Command
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
69
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
The NE time appears in the Command Status, as shown in figure below.
Figure 39. Time ManagementGet Time Dialog Box after the Execution of the Command
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
70
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.5.2 Synchronizing the NE Time with the OS Time
To synchronize the NE time with the OS time, proceed as follows:
Use the menu path:
Operations > Time > Set
Figure 40. Time ManagementSet Time Dialog Box before the Execution of the Command
The NE time apprears in the Command Status, as shown in figure below. It has changed. It is now the same
as the OS time.
NOTE: If the NE is associated with an NTP server (see paragraph ), you cannot synchronize its time with
the OS time.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
71
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 41. Time ManagementSet Time Dialog Box after the Execution of the Command
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
72
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.6 Managing the Administrative State of an NE
To change the administrative state of an NE, proceed as follows:
In the NE: Global Inventory window, select an NE whose supervision state is Supervised, communication
state is enabled and administrative state is unlocked (or locked)
Use the menu path:
Operations > Administration > Lock (or respectively Unlock)
One of the two following dialog boxes opens.
Figure 42. AdministrationLock Dialog Box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
73
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 43. Administration. Unlock Dialog box
For using those PNM command dialog boxes, refer to section 2.2.
In the Administrative column of the NE: Global Inventory window, the NE administrative state changes to
Locked (respectively Unlocked).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
74
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.7 Managing the Supervision of an NE
Supervising NEs is an essential aspect of the network management. It enables the gathering of informa-
tion concerning the behavior of the NE with respect to its functional state.
The supervision of an NE consists in establishing a communication that allows the user to perform EML
operations such as configuration and alarm management.
The NE address must have been declared prior to starting the supervision of this NE. Otherwise error mes-
sages will be displayed.
The dynamic link supervised state is not managed from PNM application.
start the NE supervision
stop the NE 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
75
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.7.1 Starting the NE Supervision
You can perform a start supervision by using one of the six following options:
Default
Align up
Align down
Enhanced align down
Audit
No alignment
NOTE: Since remote NEs or remote units are automatically brought under supervision when the supervi-
sion of the corresponding master NE is started, the start supervision operation is not available for such
remote elements.
Default
To perform a start supervision (align up, align down, enhanced align down, audit or no alignment) defined
in the Type/Release configuration file, use the menu path:
Operations > Supervision > Default
Align Up
To align the OS local configuration with the NEs at the end of the start supervision, use the menu path:
Operations > Supervision > Align Up
Align Down
To align the NE configurations with the OS at the end of the start supervision, use the menu path:
Operations > Supervision > Align Down
Enhanced Align Down
To align the NE configurations with the last OS at the end of the start supervision, use the menu path:
Operations > Supervision > Enhanced Align Down
Audit
To compare the NE MIB with its image in the OS during the start supervision, use the menu path:
Operations > Supervision > Audit
No Alignment
To perform a start supervision without any alignment, use the menu path:
Operations > Supervision > No Alignment
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
76
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
PNM Command Dialog Box
Whatever the start supervision option you have chosen, a PNM command dialog box like in figure below
opens.
Figure 44. Example of a Supervision Dialog box
In the Supervision column of the NE: Global Inventory window, the NE supervision state changes to Super-
vised.
Once the NE is supervised, an association between the NE and the OS is created. Thus PNM will be able
to animate the NE symbol color according to the changes of the NE states.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
77
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.7.2 Stopping the NE Supervision
The supervision of remote NEs or remote units cannot be stopped individually. Rather, it is automatically
stopped when the supervision of the corresponding master NE is stopped.
To stop the supervision of an NE, select it then use the menu path:
Operations > Supervision > Stop
Figure 45. SupervisionStop Dialog Box
In the Supervision column of the NE: Global Inventory window, the NE supervision state changes to De-
clared.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
78
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.8 Resynchronizing PNM
To make sure that the NE and dynamic link states displayed by PNM are really up to date, you can perform
a manual resynchronization by proceeding as follows:
Select the NE or dynamic links to be resynchronized.
Use the menu path:
Operations > Resynchronize
You can also resynchronize completely PNM, but in that case, you must know that this can take a long
time according to the number of NEs and links to be resynchronized.
At the end of the resynchronization, the following message dialog box appears.
Figure 46. Message dialog Box for the Resynchronization of PNM
NOTE: If the resynchronization operation fails, an error message is displayed
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
79
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
4.9 Uploading the Remote Inventory
This function consists in launching the EML process that inventories the components of an NE. No re-
sponse is provided by PNM.
To perform this operation, proceed as follows:
Use the menu path:
Operations > Upload Remote Inventory
Figure 47. Upload Remote Inventory Dialog Box
NOTE: The uploaded Remote Inventory file can be found under the directory
/usr/Systems/1353NM/data/ri
4.10 Ping NE
This function allows to ping one or several NEs to see if they are reachable. The function is activated from
menu Operations. There are two different possibilities to use Ping NE.
a ) No NEs selected on the map
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
80
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Select from menu operations function Ping NE as shown in following figure
Figure 48. Menu Operations : Ping NE
Selecting PIing NE the function window will be displayed, one or more NEs can be selected to perform
the ping function to test the NE reachability.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
81
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 49. Ping NE function window
Select the NEs from the list clicking on the arrow on the left, then click on the Ping Selected button to
execute the ping. A window with the ping result for the selected NEs will be displayed.
b ) One or more NEs seleceted on the map
Select one or more NEs on the map as shown in following figure
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
82
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 50. Select NEs on a map
Select from Operations menu the function Ping NE. For each selected NE a dialog box is displayed with
the ping operation result as shown in following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
83
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 51. Ping result for selected 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
84
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
85
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
5 INVENTORIES AND NAVIGATION
This chapter describes the functions offered by the Tools menu (see below figure)
Figure 52. Tools Menu
access the global NE inventory
set an inventory selection filter
navigate towards other applications
monitor the creation/deletion of an NE or a link
associate an NE to an NTP server
NOTE: The Show Alarms and Show Equipment items are examples of one and a same generic command.
There could be other similar items using this generic command or nothing.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
86
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
PNM in Viewer Mode
In viewer mode, the Tools menu is slightly different and depends on the window from which it is pulled
down:
from an Inventory window
from the viewer window
Figure 53. Tools Menu in Viewer Mode (from an Inventory 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
87
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 54. Tools Menu in Viewer Mode (from the Viewer Window)
The changes are as follows:
two additional items in the NE Inventory submenu:
the Map item allows you to inventory the NEs that appear on the map
the Map Complement items allow you to inventory the NEs that do not appear on the map
two additional items in the Link Inventory submenu:
the Map items allows you to inventory the links that appear on the map
the Map Complement items allows you to inventory the links that do not appear on the map
from the viewer window, the Selection Filter item is replaced by the Map Filter submenu allowing you
to set a selection filter on the map
NOTE: By default the Tools menu is identical to the one of the viewer 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
88
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
5.1 Accessing the Global NE Inventory
The global NE inventory lists all the NEs managed by PNM, including master NEs and remote NEs. To
access the global NE inventory, use the menu path:
Tools > NE Inventory > Global
The NE: Global Inventory window that opens is fully described in section 2.1.
5.2 Definition of an Inventory Selection Filter
This function consists in defining the selection filter criteria for:
the NEs of an NE Inventory window
PNM in Viewer Mode
When PNM is in viewer mode, you can define an additional selection filter (map filter) from the viewer win-
dow.
5.2.1 Defining an NE Inventory Selection Filter
To define the selection filter criteria for the NEs of an NE Inventory window, use the menu path:
Tools > Selection Filter
The NE Inventory Selection Filter dialog box that opens is similar to the one presented in Figure 13. and
Figure 14.
Configuring the Filter
Refer to the corresponding item in paragraph 3.1.1.
Resetting the Filter
In the Static Attributes panel, clicking on the Reset push button amounts not to filter. In that case, all the
NEs are selected.
In the Dynamic Attributes panel, the Reset push button operates like a global toggle to activate or deacti-
vate all the other ones. In both cases, all the NEs will be selected in the table area of the NE Inventory
window. This just allows you to more quickly eliminate (or keep) some attributes rather than keep (or re-
spectively eliminate one by one all the other ones.
Applying the Filter
To make the filter active, click on the Apply push button. In the NE Inventory window, the NEs matching
the selection filter criteria are selected.
This action does not deactivate the filter.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
89
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
5.3 Navigation towards Other Applications
PNM application can be integrated with other applications which allows you for example to:
manage alarms
visualize and configure the NE equipment
Composite NE
In case of composite NE (CNE), you also can navigate towards either the composite NE view or the host
NE view.
5.3.1 Alarm Management
In PNM context, if the ALMAP AS (Alarm Surveillance) application is installed on your worstation, you can
perform alarm management
PNM in Viewer Mode
In viewer mode, you can in addition visualize the alarm information
5.3.2 Accessing the Alarm Management
Thanks to AS, you can perform operations on the alarms occuring on an NE. To access AS, proceed as
follows:
Select an NE.
Use the menu path:
Tools > Show Alarms
The AS Alarm Sublist window related to the selected NE opens.
This is an example of integration of PNM with AS. We may also decide at the integration time that there
will be only one Alarm Sublist window for all the currently selected NEs.
Refer to the ALMAP AS Users Guide for more information about the alarm management.
5.3.3 Visualizing Alarm Information
For each NE symbol present within a submap, the AS application allows the display of the corresponding
alarm synthesis information:
a flashing symbol when the NE is impacted by incoming alarms
the total and acknowledged active alarm numbers
the most severe alarms
Refer to the ALMAP AS Users Guide for more information about the NE symbol management by AS
5.3.4 Navigating towards an Equipment View
To navigate towards an equipment (or a CNE) view, proceed as follows:
Select an NE
Use the menu path:
Tools > Show Equipment
The equipment view related to the selected NE opens.
Refer to the external application documentation for more information.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
90
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
5.4 Creation/Deletion Monitoring
This fonction consists in informing you when an element (NE or link) has been created in or removed from
the network since either the beginning of the PNM session or the last purge.
PNM in Viewer Mode
According to the PNM configuration, the creation/deletion monitoring function can be activated either auto-
matically at PNM startup or by using the following menu path:
Tools > Show Monitor
Figure 55. Monitor dialog box (Creation Monitoring 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
91
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
This dialog box includes two similar panels: one for the created elements, the other one for the removed
elements.For each panel:
the Name list is ordered as follows: the first line is the last created/removed element
the field located below the list gives the number of concerned elements
the Purge push button allows you to reset the content of the list
the Quiet and Popup toggle buttons allow you to choose the way to be informed:
Quiet: the Monitor dialog box is updated on creation/deletion event and you can consult when you want
Popup: the Monitor dialog box is also updated but is automatically raised on create/deletion event
Starting the Monitoring
To start the monitoring, click on the Start push button.
The Start push button becomes a Stop push button.
Stopping the Monitoring
To stop the monitoring, click on the Stop push button.
This action does not stop nor purge the monitor.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
92
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
5.5 Monitoring the Creation/Deletion in Viewer Mode
Monitoring the CreaIn viewer mode, this function mainly allows you to see NEs that are not yet on the map.
According to the PNM configuration, the creation/deletion monitoring function can be activated either auto-
matically at PNM startup or by using the following menu path:
Tools > Show Monitor
Figure 56. Monitor Dialog Box (Creation Monitoring Panel) in Viewer Mode
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
93
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 57. Monitor Dialog Box (Deletion Monitoring Panel) in Viewer Mode
This dialog box includes two panels: one for the created elements, the other one for the removed elements.
The two panels are similar to the ones of the standalone mode, except the Creation Monitoring panel that
allows you in addition to populate the map with the NEs newly created.
Starting the Monitoring
To start the monitoring, click on the Start push button.
The Start push button becomes a Stop push 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
94
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Stopping the Monitoring
To stop the monitoring, click on the Stop push button.
Populating the Map
Once NEs and/or links appear in the Name list after being created or deleted, you can select them to popu-
late the map.
In the Creation Monitoring panel, the Add Selection to Map, Add All to Map push buttons and those ones
of the Population Options area may be used like the equivalent buttons of the Global Inventory Population
dialog box.
This action does not stop nor purge the monitor.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
95
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
5.6 Accessing the Map NE Inventory
The map NE inventory is used only when PNM runs in viewer mode. It lists all the NEs (including master
NEs and remote NEs) managed by PNM and present in the current map.
To access the map NE inventory, use the menu path:
Tools > NE Inventory > Map
The following window opens.
Figure 58. NE: Map Inventory Window
The properties of this window are the same as those ones of the NE: Global Inventory 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
96
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Remote NEs and SubNEs
In case of a remote NE or subNE, we have to distinguish two cases:
if the master NE or CNE is located into the current map, it is displayed in the NE: Map Inventory window
and may be selected like a simple NE.
If the master NE or CNE is located out of the current map, it is displayed in the NE: Map Inventory window
but cannot be selected. Its name is then preceded in the tree area by a red dot). The choice between these
two representations depends on the configuration. The presence of such a master NE or CNE is necessary
to keep a coherent hierarchy in the tree area.
Menu Bar
The menu bar contains the following pulldown menus:
Inventory: see chapter 3
Operations: see chapter 4
Tools: see this chapter
Declarations: see chapter 6
Help: see paragraph 2.4.1
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
97
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
5.7 Accessing the Map Complement NE Inventory
The map complement NE inventory is used only when PNM runs in viewer mode. It lists all the NEs (includ-
ing master NEs and remote NEs) managed by PNM but that are not present in the current map.
To access the map complement NE inventory, use the menu path:
Tools > NE Inventory > Map Complement
The following window opens.
Figure 59. NE: Complement Inventory 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
98
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
5.8 Definition of a Selection Filter from the Viewer Window
Defining an NE Selection Filter on the Current Map
Defining a Link Selection Filter on the Current Map
This function consists in defining the selection filter criteria from the viewer window for:
the NEs of the current map
the links of the current map
5.8.1 Defining an NE Selection Filter on the Current Map
Defining an NE Selection Filter on the Current Map
To define the selection filter criteria for the NEs of the current map, use the menu path:
Tools > Map Filter > NE
The NE Map Filter dialog box that opens is similar to the one presented in Figure 13. and Figure 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
99
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6 CREATION/DELETION OF NES OR LINKS
This chapter describes the functions offered by the Declarations menu
Figure 60. Declarations Menu
create an NE or a link
delete an NE or a link
modify the characteristics of an NE or a link
clone an NE
migrate an NE to a host NE
migrate NEs to sub NEs
migrate NEs to a new type and release
set the NE addresses
The Declarations menu is configurable.
PNM in Viewer Mode
By default the Declarations menu is identical to the one of the viewer 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
100
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.1 Creation of NEs or Links
6.1.1 Creating an NE
There are two methods for creating a NE:
either by providing all the necessary NE characteristics (type and release, user label and other optional
parameters) or by copying from the OS the configuration of an existing NE then providing only another
user label
The second method is called NE cloning
Remote NE
As the remote NEs are not selfsufficient, they require a particular creation procedure.
After the NE Creation
Except for remote NEs, the creation procedure does not imply specifying all the information needed to start
the NE supervision. The NE address is always specified some time after the NE creation and before start-
ing the NE supervision.
The EML agent supplies the default OS addresses for the NE during the synchronization phase of the cre-
ation process. These values can be overridden later.
Mediation Devices
Certain types of NEs (Q2 NEs) cannot exchange their management information directly with the OS, there-
fore they need sending their information via a mediation device. The mediation device need not being spe-
cified at creation time, but rather once the network address has been set
Creating an NE
To create an NE, proceed as follows:
Use the menu path:
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
101
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Declarations > Create > NE
Figure 61. NE Creation Dialog Box
Select a Family, a Type and a Release for the NE to be created by using the corresponding option buttons.
NOTE: The NE types you can choose depend on the NE family you just have been selecting. In the same
way, the choice of NE releases depends on the NE type previously selected.
In the User Label field, enter the user friendly name of the NE.
In the Location Name field, enter the location where the NE will be created. This field may be optional,
according to the PNM configuration.
Possibly use the Supervision Area option button to force the allocation of the NE to an EML domain be-
longing to this supervision area. PNM will assign the NE creation to the EML agent having the biggest ca-
pacity in terms of NEs among those supporting the required NE type and release in the supervision 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
102
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Possibly use the EML Domain option button to force the assignment of the NE to that EML domain, pro-
vided that it supports the required NE type and release. The list of running EMLs depends on the previously
chosen supervision area.
NOTE: A Q2 NE must be allocated to the same EML domain as the NE providing its mediation function.
This should be done manually.
NOTE: If none of the two previous attributes (supervision area and EML domain) are provided, the NE will
be allocated to the least loaded EML domain among all of those supporting the required NE type and re-
lease.
NOTE: Both attributes are compatible. In case of conflict (no EML domain in the specified supervision
area), an error message is displayed.
Use the ACD option button to select the access control domain of the NE.
NOTE: When PNM runs in nonsecured mode, the ACD option button does not exist.
Launching the Creation
To trigger the creation, click on the Apply push button.
The new NE appears in the NE: Global Inventory window. Its supervision state is Declared and its charac-
teristics (except the NE address) are defined in the OS.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
103
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
PNM in Viewer Mode
When PNM runs in viewer mode, you can create an NE from the current submap in the viewer window.
The NE Creation dialog box that opens in viewer mode (see figure below) owns an additional field named
Comments where you can enter any text.
Figure 62. NE Creation Dialog Box in Viewer Mode
Once you click on the Apply push button, the NE symbol appears in the current submap.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
104
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.1.2 Creating a Remote NE
To create a remote NE, proceed as follows:
In the NE: Global Inventory window, select the master NE to which you want to attach the remote NE.
Use the menu path:
Declarations > Create > Remote NE
Figure 63. Remote NE Creation Dialog Box
In this dialog box, you cannot modify the Master NE, Supervision Area and EML Domain fields. In fact
they contain the values corresponding to the selected master 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
105
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Fill in the rest of the dialog box as you would do for a basic NE. The available types and releases are only
the ones allowed for this kind of master NE.
As the master NE may support several remote NEs connected to it, it is necessary to identify the slot of
the master NE in which the remote NE should be plugged. Enter the remote NE index number in the RNE
Index field. The index value must range from the values given in the PNM resource file.
Launching the Creation
To trigger the creation, click on the Apply push button.
The new remote NE appears in the NE: Global Inventory window.
PNM in Viewer Mode
When PNM runs in viewer mode, you can create a remote NE from the current submap in the viewer win-
dow.
The Remote NE Creation dialog box in viewer mode contains an additional field named Comments.
The remote NE symbol is created in the same submap as the master NE and a static link is automatically
added between 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
106
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.1.3 Creating a Static Link
To create a static link, proceed as follows:
In the NE: Global Inventory window, select the NEs between which you want to create the static link.
Use the menu path:
Declarations > Create > Static Link
The static link symbol is created between the two NEs but does not appear in the Link: Global Inventory
window.
PNM in Viewer Mode
The display of the static links in the viewer window depends on the type of static link.
Hierarchical Static Links
Mediation Device Q2 NE Link
In order to represent the relationship between a Q2 NE and its mediation device, a link is automatically
created between the corresponding symbols. This link is a static and hierarchical link based on the FDN
of the mediation device. The Q2 NE and its mediation device symbols must be located in the same sub-
map. If the Q2 NE is removed, the corresponding link is also deleted.
The link state between a Q2 NE and its mediation device is not managed, therefore the link symbol is not
animated.
Master NE Remote NE (or Remote Unit) Link
In order to represent the relationship of a remote NE (or remote unit) and its master NE, a link is automati-
cally created by PNM when the remote NE symbol is created. That is a static and hierarchical link. Master
NE and remote NE (or remote unit) symbols must be located in the same submap. These links are created
during the PNM/Agent synchronization time, from the Inventory views and during the remote NE (or re-
mote unit) creation time.
If the master NE or the remote NE (or remote unit) is removed, the corresponding link is also deleted. The
link state between a remote NE (or remote unit) and its master NE (or submaster NE) is not managed,
therefore the link symbol is not animated.
The hierarchical static links are not secured by the ALMAP SEC component. A link symbol is displayed
if and only if both linked NE symbols are displayed in the same submap.
The hierarchical links may be not displayed if required by configuration.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
107
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Generic Static Links
This kind of link is a graphical representation, used to express a particular relationship between two NEs.
Any kinds of link may be represented:
NENE link
NERNE link
RNERNE link
NERU link
RURU link
OSNE link
...
This link is automatically displayed by PNM when the NE symbols are created. The NE symbols must be
located in the same submap.
These links are created during the PNM/Agent synchronization time or from the Inventory views.
The link symbol attributes are managed by the EML in charge of the NEs.
If one of the linked NEs is removed, the corresponding link is also deleted. The state of a relational link
is not managed, therefore the link symbol is not animated.
The generic static links are not secured by the ALMAP SEC component. A link symbol is displayed if and
only if both linked NE symbols are displayed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
108
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.2 Deletion of NEs and Links
delete an NE
delete a static link
6.2.1 Deleting an NE
Deleting an NE consists in removing its characteristics from the OS. This function is not available on re-
mote units.
To remove an NE, proceed as follows:
In the NE: Global Inventory window, select an NE
Use the menu path:
Declarations > Delete > Generic
Figure 64. Deletion Dialog Box
The NE disappears from the NE: Global Inventory 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
109
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Deleting a Mediation Devices
Before deleting a mediation device, you must first delete the Q2 NEs that depend on it or allocate them
to another mediation device.
PNM in Viewer Mode
WARNING. When you use the viewer mode, do not confuse this function which will cause the removal of
all the NE symbols from all the submaps, with the deletion function of the viewer (not in the Declaration
menu of PNM) that consists to remove only one (or several) NE symbol from the current submap or all
of the submaps.
6.2.2 Deleting a Static Link
To delete a static link, proceed as follows:
In the NE: Global Inventory window, select the NEs between which you want to delete the static link.
Use the menu path:
Declarations > Delete > Static Link
The static link between the two NEs is removed.
PNM in Viewer Mode
When PNM runs in viewer mode, you can delete a static link from the current submap in the viewer window.
You have just to select two NE symbols then use the menu path given at the beginning of this paragraph.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
110
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.3 Modification of NE or Link Characteristics
modify the NE characteristics
modify the remote NE characteristics
modify the dynamic link characteristics
This section does not deal with the address change.
6.3.1 Modifying the NE Characteristics
To modify the characteristics of an NE, proceed as follows:
Use the menu path:
Declarations > Modify
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
111
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 65. Modification Dialog Box for a basic NE
The title of the dialog box recalls the user label of the NE to be modified.
You can modify only the User Label and Location Name fields and choose another ACD.
Applying the Modifications
To validate the modifications, click on the Apply push button.
The NE characteristics are updated in all open windows.
PNM in Viewer Mode
Like the NE Creation dialog box, the Modification dialog box in viewer mode contains an additional field
named Comments. You can modify it too.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
112
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 66. Modification Dialog Box for a Dynamic Link
The title of the dialog box recalls the user label of the link to be modified.
You can modify only the User Label and Location Name fields and choose another ACD.
Applying the Modifications
To validate the modifications, click on the Apply push button.
The dynamic link characteristics are modified in all open windows.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
113
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.4 Cloning an NE
This function allows you to duplicate an NE with its configuration. This may be useful to create an NE
whose characteristics are very similar to another one.
The cloning operation is not allowed on the composite NEs.
To clone an NE, proceed as follows:
Use the menu path:
Declarations > Clone
A dialog box like in figure below opens.
Figure 67. Example of a Clone Dialog Box
The title of the dialog box recalls the user label of the NE to be cloned.
You can modify only the same fields as in a Modification dialog box , but you must enter a new User Label.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
114
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Launching the Cloning
To trigger the cloning, click on the Apply push button.
The cloned NE appears in the NE: Global Inventory window.
Since neither the supervision area nor the EML domain can be changed, the new NE is always allocated
to the EML agent managing the cloned NE.
PNM in Viewer Mode
When PNM runs in viewer mode, you can clone an NE from the current submap in the viewer window. The
new NE will be placed on the same submap as the cloned NE.
In the first area, use the option buttons to select the family, type and release of the CNE that is to be created
and will contain the currently selected NE. Only CNEs supporting the type of the currently selected NE are
proposed by the option buttons.
Launching the Migration
To trigger the migration, click on the Apply push button.
In the NE: Global Inventory window, the migrated NE disappears as basic NE and a new CNE appears.
The creation of the composite NE brings about the creation of a list of subNEs by default.
The list of the subNEs is available in a hierarchical way in the NE Global Inventory dialog box.
PNM in Viewer Mode
When PNM runs in viewer mode, you can migrate an NE to a host NE by selecting them from the current
submap in the viewer window.
During the migration, the symbol of the currently selected NE is transfered to the newly created CNE sub-
map. All the occurences of this NE that could exist in other submaps are removed.
Like the NE Creation dialog box presented at the end of paragraph 6.1.1, the Migrate to Host NE CNE
Creation dialog box in viewer mode contains an additional field named Comments.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
115
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.5 Declaration of the NE and OS Addresses
set an NE address
change an OS address
6.5.1 Setting an NE Address
Once the NE has been created in PNM, you have to provide the OS with the address of the real NE that
is in the network.
PNM can manage different types of NE addresses: Q2, QB3*, Q3 or free addresses such as TCPIP.. It
is the reason why the address declaration is separated from the NE creation and address input forms de-
pend on the type of NE.
This feature can also be used to change the NE address later on.
Moreover some NE types, such as remote NEs, do not embed their own address, as they exchange their
management information with the OS through other NEs. Therefore no address capture is expected for
such NEs.
To set an NE address, proceed as follows:
Use the menu path:
Declarations > Set Addresses > NE Address
The dialog box that opens may be like one of the examples shown in figures below.
Figure 68. Address Dialog Box for a Q2 Address
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
116
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 69. Address Dialog Box for a QB3* Address
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
117
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 70. Address Dialog Box for a Q3 Address
Figure 71. Example of an Address Dialog Box for an IP Address
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
118
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
The title of the dialog box recalls the user label of the NE whose network address is to be set. The first
time such an NE Address dialog box opens (that is before any address has been supplied for this NE),
the various fields are empty.
Q2 NE
For a Q2 NE, you must fill in supply the Mediation Name field with the user label of the QB3* NE providing
the mediation function.
QB3* NE
For a QB3* NE, you must fill in the NSAP presentation address in accordance with the ISO definition (AFI,
IDI, Organization Id., Area, System Id. and Sel. fields).
Q3 NE
For a Q3 NE, you must fill in the Presentation, Session, Transport fields corresponding to the OSI selec-
tors, and the NSAP presentation address in accordance with the ISO definition (AFI, IDI, Organization Id.,
Area, System Id. and Sel. fields).
Logical Number
For QB3* or Q2 NE types, you must enter a Logical Number used in either QB3* or Q2 subaddressing.
Validating the NE Address
To validate the modifications in the dialog box, click on the Apply push 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
119
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
6.5.2 Changing an OS Address
NEs exchanging their management information directly with the OS need addressing information in order
to be able to communicate with the OS across the network. Such an OS address is conveyed to the NE
by the EML agent during the creation process.
Actually certain types of NEs have two OS addresses at their disposal: the main OS address and a spare
OS address, enabling them to switch from one OS to another. This is intended to support, for instance,
OS resilience or OS migration.
At the beginning, both addresses conveyed to the NE are identical, and they are known by the EML agent
by configuration. The given address relates to the workstation which hosts the EML agent.
Once the NE is created, each OS address may be individually changed (for NEs which support it).
To change an OS address, proceed as follows:
In the NE: Global Inventory window, select an NE whose supervision state is 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
120
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Use the menu path:
Declarations > Set Addresses > OS Address
Figure 72. OS Address Dialog Box
The title of the dialog box recalls the user label of the NE whose OS addresses are to be changed.
The first time an OS Address dialog box opens, the OS Main Address and OS Spare Address (known by
configuration) are displayed in the corresponding fields.
You can change the main OS presentation (PSAP) address in accordance with the ISO definition (AFI,
IDI, Organization Id., Area, System Id. and Sel. fields).
You can also change the optional spare OS PSAP address by using the same format.
NOTE: The OS main address can only be changed if the NE is supervised (i.e. its supervision state is Su-
pervised). However the OS Address dialog box can always be displayed whatever the supervision state
is and you can change the OS spare address in all cases.
Validating the OS Addresses
To validate the modifications in the dialog box, click on the Apply push 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
121
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
7 EXTERNAL TEXT
The external text is a piece of information provided by the EML agent.
When PNM is configured to display external texts, this attribute appears in the following dialog boxes:
Current Status for an NE
NE Inventory Filter (Static Attributes panel)
NE Inventory Selection Filter (Static Attributes panel)
Current Status Dialog Box
Next figure shows how the external text attribute appears in a Current Status dialog box for an NE.
Figure 73. Current Status Dialog Box for an NE when PNM is External Text Enabled
Filter Dialog Box
The figure below shows how the external text attribute appears in a filter dialog box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
122
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Figure 74. Example of a Filter Dialog Box (Static Attributes Panel) when PNM is External Text Enabled
PNM in Viewer Mode
When PNM runs in viewer mode, the external text attribute also appears in the following dialog boxes:
NE Map Inventory Filter (Static Attributes panel)
NE Map Inventory Selection Filter (Static Attributes panel)
NE Map Complement Inventory Filter (Static Attributes panel)
NE Map Complement Inventory Selection Filter (Static Attributes panel)
NE Map Filter (Static Attributes panel)
The External Text field appears in those dialog boxes like in the example 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
123
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
8 TERMINOLOGY
8.1 Abbreviations
ACD
Access Control Domain
ALMAP
ALcatel MAnagement Platform
AS
Alarm Surveillance
CNE
Composite NE
DNM
Distributed Network Manager
EML
Element Management Layer
FAD
Functional Access Domain
HP
Hewlett Packard
HTML
Hyper Text Markup Language
IM
Information Manager
MIB
Managed Information Base
NE
Network Element
NSAP
Network Service Access Point
NTP
Network Time Protocol
OAD
Object Access Domain
OS
Operation System
OVw
OpenView window
PNM
Physical Network Manager
PSAP
Presentation Service Access Point
RNE
Remote NE
RU
Remote Unit
SEC
SECurity
SSAP
Session Service Access Point
TMN
Telecommunication Management 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
124
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
TN
Telecommunication Network
TSAP
Transport Service Access Point
TVA
Topology Viewer Application
USM
User Service Manager
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
125
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
8.2 Glossary
Administrator
A user who has access rights to all the management domains of the product. He has access to
the whole network and to all the management functionality.
Alarm
A warning of a system malfunction which may have an immediate or potentially negative
impact on the operation of equipment or the OS.
Alarm Status
Identifies the type and severity of an alarm.
Craft Terminal (CT)
Workstation or Personal computer (PC) from which the local access to an NE is possible. It
can be used to configure or perform monitoring tasks on the NE.
EML Application
This application is responsible for the configuration and management of NEs.
Information Manager (IM)
A software unit representing the functional core of an application (or a part of it), handling
the application data processing and its persistency. An IM opposes itself and provides
services to an USM (User Service Manager) in charge of the dialog with the operator.
Management Information Base (MIB)
Describes all the managed objects controlled by the system. The OS MIB and the NE MIB
are typical exmaples in this system.
Network Element (NE)
Either a single telecommunications equipment or part of a Telecommunications Network.
Has characteristics compliant with CCITT recommendations.
Network Services Access Point (NSAP)
This refers to the access point in layer 3 (network layer) of the OSI stack which provides
services to the transport layer (layer 4). This access point is identified by a unique NSAP
address which is constructed according to international standards. On PNM an NSAP
address must be provided to uniquely identify the NE to be supervised.
Notification
Spontaneous data received by the system concerning an 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
126
02

SC.4: PNM

/ 3AL 89061 AA AA

126
126
Operation System (OS)
A system dedicated to the supervision of NEs in a standard way, using protocols and
interfaces. It offers to the operator a set of functions necessary to supervise the NEs.
Operator
The enduser of the product. He supervises a part of the network that is dependant on his
user profile.
Severity
Linked to the alarms, the severity indicate the magnitude of a failure.
Telecommunication Management Network (TMN)
Defines the concept of interoperable management of TNs. They provide an organized
network structure to achieve the interconnection of the different components of the TN and
the services to process the information.
Telecommunication Network (TN)
Describes the network to be managed. Provides the transmission, the transport and the
switching support for the interconnected network elements.
User Service Manager (USM)
These are presentation processes used by PNM to manage the user interface and facilitate
the interaction with the product.
END OF DOCUMENT
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
1
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116


TABLE OF CONTENTS
1 MAP 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Create the map 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Map Background and Layout 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Creating a child submap 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 CONSTRUCTING THE MANAGEABLE ENTITIES 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Adding NEs to the Topological representation 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Creating NEs 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Create a remote NE 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 Adding a NE symbol 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Poulation from Inventory 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 CLONING NE 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Modifying NEs from Network Topology views 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 NE ADDRESS 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 SUPERVISION 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 NE management states 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Introduction 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 Consulting the different management states 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.3 Resynchronize NE States in the Network Topology view 39 . . . . . . . . . . . . . . . . . . . . . . . . . .
6 SUPERVISING NES 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Starting supervision of NEs 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Stopping NE supervision 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 Different NE subversion of the same NE type (only applicable to W/OMSN) 44 . . . . . . .
6.3 Abort Supervision 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Black icon with question point 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 OS ADDRESS FOR AN EQUIPMENT 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 OS Address 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 ADD CONNECTION 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
01A 040127
V.SCORTECCI V.PORRO
02 040728 SC04091002
V.SCORTECCI V.PORRO
050623 03 SC04091002
1353NM REL.7.0
VERSION 7.0
OPERATORS HANDBOOK
L.MERLI
L.MERLI
A.CORTESE L.FORESTA

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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
2
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
9 DIAGNOSE 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 Remote Inventory on PNM 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Remote Inventory Visualization 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Remote Inventory Wizard 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 Remote Inventory Search 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Abnormal Condition ( AC ) Viewer 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Maintenance Memory 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 Create ISA board 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 MAPS MANAGEMENT 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 Introduction 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Submaps and local maps 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1 Opening a map 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2 Modifying map characteristics 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.3 Modifying submap characteristics 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.4 Deleting a map 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.5 Deleting a Submap 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 DNM Management 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 VIEW: DISPLAY OPTIONS 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 NE Time Management 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1 Get NE Time Action 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.2 Set NE Time Action 84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12 FILE TRANSFER SCHEDULER 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Software Status 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 FT Scheduler Job 95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1 Job editing facilities 106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2 View Report 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3 FT Scheduler Editor 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.1 Save and Open menu options 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.2 Window Management 115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
3
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
FIGURES
Figure 1. File: New Map 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Question: Save current map 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. View: View Parameters pulldown menu 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. View popup menu 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Background selection 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Layout selection 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Root map display with background 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Edit: Create Child View 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Child View icon selection 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Child View icon selection box: Close button 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Declarations: Create: NE 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. NE Creation 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Tools: NE Inventory: Global 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Inventory: Population 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Submap topology selection 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Global Inventory population dialog box 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Root map and submap 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Submap view 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Declarations: Set Addresses: NE Address 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Q3 NE ADDRESS dialogue box. 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. QB3* NE ADDRESS dialog box 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Q2 NE ADDRESS dialogue box. 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Example of IP address for 1690WM equipment 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. An example of the evolution of the NE management states. 37 . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Operations: Show Statuses 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Current status dialog box 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. NE: Operations: Supervision: Align Up 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Align Up Supervision 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Align Up end Supervision 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Black icon with question point 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Displaying and changing the OS address for an NE. 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. OS Address dialog box 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Operations: Add Connection 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Add Connection dialog box 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Icon selection 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Add Connection creation: Apply button 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. The connection is drawn in the map 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Diagnose menu options 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Upload Remote Inventory option 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Remote Inventory uploading example 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Show Remote Inventory menu 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Show Remote Inventory window example 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Wizard dialog box 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Remote Inventory Search dialog box 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. AC (Abnormal Condition) Viewer menu 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. AC Viewer window 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Manual Refresh command 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. AC View icons 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Navigation from AC Viewer (PNM) to NE USM 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. Refresh time configuration option 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
4
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 51. Set refresh time and confirmation windows 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 52. Set default time and confirmation windows 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 53. Uploading the maintenance memory 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. Create ISA board option 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. File options. 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. File: Save Map As 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. Save Map As dialog box 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. DNM Message 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. File: Map management 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. DNM Map Management dialog box 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. SECUSM browser: DNMAccessControlDomain 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. dnmusm admin added to profile Administrator 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. New DNM Map Management dialog box 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. GET NE TIME 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. Example of GET NE TIME/ 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. FT Scheduler option 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. SW Status menu All NEs option and its tooltip 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. NEs SWDL Status 87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. Export command 87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. File export characteristic 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. SW Status selected by name with a NE list menu 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. SW Status selected by name with Select one from list indication 88 . . . . . . . . . . . . . . . . .
Figure 73. NE by name selection 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 74. NE software status detail 89 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 75. Q3NE Software unit detail example 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 76. QB3*NE Software Package Descriptor view example 91 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 77. Software management action example 92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 78. Confirmation box window 92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 79. SW Status Selected by NE Type with a NE list menu 93 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 80. SW Status Selected by NE Type with Select one from list indication 93 . . . . . . . . . . . . . .
Figure 81. NE by type selection 94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 82. NE by type SW status 94 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 83. Selecting the New option from the Job menu 95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 84. New Job creation 96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 85. Job type selection 96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 86. SWDL job: Adding a new Session example 97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 87. SWDL job: Adding NE equipment 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 88. SWDL package assignment example 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 89. Backup job window example 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 90. Backup job assignment example 101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 91. Closing the job scheduler 102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 92. Job running indication window 102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 93. Example of job Status 103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 94. Example of backup job status 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 95. Job status and View Report command 105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 96. Select extension with Shift key 106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 97. Select extension with Ctrl key 107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 98. Cutting a branch 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 99. Pasting a branch 109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 100. Backup report window example 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 101. SWDL report window example 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 102. Entering the file name to save 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 103. FT Scheduler Editor menu 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 104. Opening an existing job 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
5
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 105. Opening a selected job 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 106. List of the job opened 115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 107. View of multiple job windows 116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
6
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
7
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
1 MAP
INTRODUCTION
A map is an abstract entity, that represents a collection of symbols interconnected to represent a network. A
map contains a set of created objects. Some of these objects correspond to supervisable entities (network ele-
ments) and others are only graphical and are not supervised (network nodes, Local Area Networks (LANs) sites,
regions, connections between the graphical symbols). Maps are built by authorized operators during the
construction phase. A given operator works from a subset of maps, according to his access rights.
In order to allow authorized operators to make changes to the supervised network in a flexible and reversible
manner, maps can be created, edited, saved, opened and deleted without modifying the current map of other
operators. Once a construction map is an accurate image of the supervised network, authorized operators can
distribute it to operators in relation with access rights. It is up to the client operator to decide to use the new map.
Two types of maps are available:
A distributed map is the original map created by the administrator or constructor from which a local
map is generated for the user which has the proper access rights to use it. The administrator and
constructor always acts on the original map, each deletion or modification are irreparable.
A local map is an operator own version of the distributed map. An operator always acts on its local
map and modifies it as necessary without affecting the original one.
The building blocks of Maps are called submaps.
A submap is a collection of related symbols displayed in a single graphical window. Submaps are orga-
nized in a hierarchical way. Each submap may contain symbols that represent other submaps. Navigation
through the different submaps that make up the Map is done by doubleclicking on symbols. This opens
the associated submap in a window on the terminal.
Symbols that generate other submaps are called Parent symbols and the submaps they create are called
Child submaps. The first submap created is called the Root submap. It contains the parent symbols from
which the submap hierarchy will be established.
When a submap is opened, the name of the Root submap is written in the bottom left corner of the submap.
The name of the submap is given in the bottom right corner of the submap. In Figure 1. the submap is the
Root submap.
Depending on the access rights, management operations on submaps may or may not be undertaken.
An Object is a particular entity or resource in a networked systems environment. In the Network Topology
views that are dealt with in this manual, objects are either Sites, NEs or Connections between these differ-
ent entities.
A symbol on a submap is the representation of an Object described in the OS MIB.
Two types of symbols can be distinguished:
Managed symbols: represent a supervised entity managed by the system.
They generally represent NEs. In this case the network characteristics (name, network address...)
are defined in the OS MIB,
Graphical symbols: not managed by the system but are simply a graphical representation of an ob-
ject. They generally represent geographical entities such as connections or sites.
N.B. There may be multiple representations (symbols) in a map of a given managed object. However the
object is uniquely defined in the OS MIB. This means that no matter how many representations (sym-
bols) of an entity appear in a map, there is only one description of the object in the OS MIB.
1.1 Create the map
SCOPE
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
8
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
The aim of this chapter is to introduce the steps necessary to define the network topology. This is done
step by step, so that the most detailed and correct description of the network is given.
As defined in the previous chapter, geographical entities represent sites or connections and are not man-
aged by the system. Therefore, this chapter describes the creation of the site and the connection symbols.
It may be necessary to create a new Map in order to create a new network or to represent differently an
existing network without modifying the original network layout.
SEQUENCE
a ) To create a new Map select the pulldown menu File: New Map.
Figure 1. File: New Map
b ) To create a new Map select the pulldown menu File: New Map. A question box asks if you want
to save the current map before opening the new on.
Figure 2. Question: Save current map
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
9
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
1.2 Map Background and Layout
Figure 3. View: View Parameters pulldown menu
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
10
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 4. View popup menu
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
11
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 5. Background selection
Figure 6. Layout selection
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
12
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 7. Root map display with background
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
13
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
1.3 Creating a child submap
SCOPE
The scope of this procedure is to create a Child view
SEQUENCE
a ) From the Root map select Edit: Create Child View.
Figure 8. Edit: Create Child View
b ) From the Child View icon selection dialog box (see below figure) select the icon and click on Apply
button.
Figure 9. Child View icon selection
c ) The icon of the child view is displayed on the map. Click on Close button of the icon selection box
to close the box. See below figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
14
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 10. Child View icon selection box: Close 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
15
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
2 CONSTRUCTING THE MANAGEABLE ENTITIES
The previous chapter dealt with general Map and Submap construction concerning the geographical enti-
ties (sites and connections) and the navigation through the different submaps.
This chapter describes the steps involved in the addition of manageable entities to submaps.
The operations that can be undertaken are:
creating a NE,
MIB cloning,
adding or removing a NE symbol,
Declaring or changing the NE address.
NOTE: The NE to create has been correctly installed with the right software version
NOTE: The emlim which will manage the NE to create has been correctly installed in 1353NM
2.1 Adding NEs to the Topological representation
There are two methods for creating a NE on a submap:
either by providing all the necessary characteristics of the NE to be created (Type and release,
unique user friendly name and other optional parameters),
or by copying the OS MIB configuration from an existing NE, providing only (at least) the user
friendly name (user label) of the new NE, for the NEs which support this operation.
The second method is called MIB cloning.
Moreover, certain types of NE requires a particular creation procedure, as they have not their selfsuffi-
ciency (not standalone). They are called 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
16
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
2.1.1 Creating NEs
The creation of a NE enables you to create a graphical NE symbol on a submap and at the same time create
its corresponding configuration in the OS MIB. To create a NE of a specified type and release, the following
information is required :
a unique user friendly name (User Label).
Other information (such as EML domain, supervision area) may be provided, but is not mandatory.
N.B. Certain types of NEs (Q2 NEs) cannot exchange their management information directly with the
OS, therefore they need to send their information via a mediation device. The mediation device
has not to be specified at creation time, but rather when the network address is set
SEQUENCE
a ) To create a NE, place yourself on the submap on which the NE must be created.
Select the Declarations: Create: NE pull down menu as shown in the figure below.
Figure 11. Declarations: Create: NE
The following dialogue box opens allowing you to enter the NEs characteristics.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
17
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 12. NE Creation
b ) In the above dialogue box, the Family criterion provides a way to filter the NE types by categories.
Select a family of NE types from the list. The selected family of NEs is highlighted and the NE Type list
is updated to show all supported NEs in that family.
c ) Select a NE type from the list. The NE type is highlighted to show it has been selected. At the same
time the available releases concerning the selected NE type are listed in the top right hand corner
of the dialogue box.
Select the required NE Release.
Enter the NE user label (friendly name) and the location name in their respectively entry boxes. In the NM
system the maximum character number for the location name has been fixed to 32. This maximum lenght
has been provided for both Q3 and QB3* NEs. The existing NEs with longer location name will be taken
over and accepted by the system but if the user will try to modify it the new one will be accepted if shorter
than 32.
The User Label and Location Name are mandatory. The maximum character numbers for the User Label
is 32.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
18
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
The maximum character numbers, for User Label of 1540PO, when the PO is connected to a
network terminal (NT), is max. 7 where the default max. installation value is 32
The Location Name field allows to specify the location of the NE being created.
The remaining fields Supervision Area, EML Domain and Comments) are not mandatory but a wrong
Supervision Area assignment can create a not reachable NE:
The Supervision Area is associated to different management interface (OSI protocol stack) provided by
the NM. Specifying the Supervision Area label forces the NE to be allocated to an EML domain belonging
to this supervision area. Then the Supervision Area marks the lan type connected to the NE.
Specifying the EML Domain forces the assignment of the NE to that EML domain, provided that it supports
the required NE type and release.
N.B. A Q2 NE must be allocated to the same EML domain as the QB3* NE providing its
mediation function. This should be done manually. An error message will be dis-
played if it is not the case.
If none of these two attributes are provided, the NE will be allocated to the least loaded EML domain
among all of those supporting the required NE type and release.
If both attributes are provided, they must be compatible. In case of conflict (EML domain not in speci-
fied supervision area), an error message will be displayed.
Specifying the Access Control Domain forces the assignment of the NE to that control domain. The
possible control domains are defined in the user profile. If this security is not defined in the user pro-
file, the Security field will be Disabled and the Unknown is specified in the Access Control Domain
list.
N.B. The Access Control Domain feature is used to limit the number of possible opera-
tions on a specific NE. But it can also limit the operations allowed to an operator. For
example, the NE creation can be forbidden to a specific user.
The Comments field allows the operator to enter some comments about the NE being created.
Confirm or cancel the creation operation using the OK or Close push buttons at the bottom of the dialogue
box.
The processing of the request is indicated by the cursor changing to a busy (clock) cursor and no further
operation can be performed on the NE until the operation is completed.
The Close push button enables to close the dialogue box.
If you close the dialogue box during the creation process, the NE graphical representation on the submap will
be removed but the creation process will not be cancelled. However, the operator will have to perform a Global
NE Inventory) to see the NE graphical representation on the submap.
d ) Following this Create NE operation, the NE graphical representation appears on the submap and
the NE characteristics (except for the NE address) are defined in the OS MIB. A NE object is thus
created in the OS MIB.
After the creation operation the NE supervision state passes to the Declared state.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
19
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
e ) To access the Equipment view, select the NE by clicking on it with the Select mouse button. Open
the Supervision pull down menu and choose the Show Equipment option from this menu, as ex-
plained in the Getting Started manual. Note that a declared NE Equipment View, managed by Q3,
can be opened but nothing will be visualized.
In this view, the SUP icon, representing the supervision state of the NE is in the Declared colour.
N.B. If the name given to the NE during this Create NE operation is the name of an existing NE then
the system will alert you of this fact by opening a dialogue box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
20
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
2.1.2 Create a remote NE
tbd
Remove NG (new generation) remote NE
tbd
2.1.3 Adding a NE symbol
Refer to Sections TVA and PNM
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
21
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
2.2 Poulation from Inventory
SEQUENCE
a ) From the PNM window select Tools: NE Inventory: Global
Figure 13. Tools: NE Inventory: Global
b ) From the NE Inventory window select the NE to create and issue the pulldown menu Populate
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
22
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 14. Inventory: Population
c ) A dialog box is presented, allowing the user to choose the population options:
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
23
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 15. Submap topology selection
Population Input. Contains the options:
Selected NEs. Only the selected NEs will be placed in the maps
All NEs. All NEs present in the Inventory list will be placed in the maps
Population Mode
OS Topology. The system creates a different submap per each installed EMLIM and places
each NE into its own submap
Network Topology. The system creates a different submap per each site and places each NE
into its own submap
Submap Topology. The user selects on the popup subwindow ( see above figure ) the subnet-
work where the NE(s) will be placed
Population Options
If this option is not activated, all the NEs are treated on the basis defined in the Population Mode 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
24
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
No duplication. when activated, this option prevents the NE symbols from being duplicated in
the same submap during population operations.
Hierarchical. when this option is activated, the remotes NEs, remote units and subNEs are
managed with the following rule: the remote NEs are located on the same submap as their mas-
ter NE, the remote units are located in a submap associated to their master NE and the sub
NEs are located in a submap associated to their composite NE.
Figure 16. Global Inventory population dialog box
For more detailed information refer to Section PNM.
An example of root map with one submap is displayed in the figure which follows.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
25
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 17. Root map and submap
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
26
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 18. Submap view
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
27
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
3 CLONING NE
Refer to Section PNM
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
28
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
3.1 Modifying NEs from Network Topology views
This paragraph deals with the characteristics of a NE (excluding the NE addresses).
Refer to Section PNM. See in particular Declarations: Modify
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
29
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
4 NE ADDRESS
SCOPE
In order to communicate with a NE, PNM requires the network address of the NE to be configured in the
OS MIB.
Since various addressing mechanisms should be supported, the address declaration is separated from
the NE creation, and address input forms depend on the type of NE.
The NE address management could be handled out of the system in particular cases (for instance, the
EML agent may take care of it).
N.B. The currently supported NE address formats are IP addressing, Q3 addressing, QB3* address-
ing and Q2 addressing.
This operation is only allowed if the NE supervision state is Declared.
CONDITIONS
The local NE address on the equipment must be previously set up via the Craft Terminal
SEQUENCE
a ) To supply the NE address of an equipment, place yourself on the submap on which the NE is located.
Select the NE for which you want to declare the address.
Select the NE Address... option from the Declarations: Set Addresses pull down menu as shown in the
Figure 19. below.
Figure 19. Declarations: Set Addresses: NE Address
According to the NE type, one of the following dialogue boxes (Figure 20. Figure 21. & Figure 22. ) opens
allowing you to enter some addressing information.
The title of the dialogue box indicates the name of the NE for which the network address is to be changed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
30
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
The first time such a NE address input dialogue box is open (that is before any address has been supplied
for this NE), the various entry boxes are empty ).
Figure 20. Q3 NE ADDRESS dialogue box.
b ) For a Q3 NE you must fill in the OSI Address (Presentation Selector, Session Selector and Trans-
port Selector) and the NSAP presentation address (see Figure 20. ) (PresentationAFI, System
ID and Sel entry boxes), in accordance with the OSI definition.
The following values are provided :
OMSG : Presentation = 31; Session =31; Transport = 31; AFI = 39 or 47 or 49; Sel = 01
System ID = any value: it is recommended to fill in the NE MAC address.
W/OMSN (1664SM, 1666 SM) : Presentation = 0002; Session = 00; Transport = 00; Sel = 1d or 1D
AFI = 39 or 47 or 49
W/OMSN (new gen.) : Presentation, Session and Transport any values admitted : the same values set
by the craft terminal have to be provided by the NM;
AFI = 39 or 47 or 49
The other fields IDI, Organization ID, Area, are optional
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
31
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 21. QB3* NE ADDRESS dialog box
For a QB3* NE you must fill in the NSAP presentation address (see Figure 21. ), in accordance with
the OSI definition (AFI, System ID, Sel and Logical Number entry boxes).
AFI = 39 or 47 or 49
Sel = 1d or 1D
Logical Number >= 5
The other fields IDI, Organization ID, Area, are optional
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
32
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 22. Q2 NE ADDRESS dialogue box.
For a Q2 NE you must supply the user friendly name (Mediation Name entry box) of the QB3* NE
providing the mediation function to the Q2 NE and the Logical Number.
Logical Number = 1 B 254
Confirm or cancel the NE address declaration using the OK or Close push buttons at the bottom of the dia-
logue box.
N.B. The same NE address declaration feature can also be used to change the NE address later on.
However the NE address can only be changed if the NE is not supervised (declared state). In
spite of this it can always be displayed whatever the supervision state is.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
33
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
IP addressing
Two Q3NEs can utilize the IP address: the 1690 WM (american equipment) and the 1641/1664SX equip-
ments. To set the 1690 WM address select the Free Form NE Address (see Figure 23. ) and set the
TCP/IP address. The number format is four group of 3 digits each separated by a point : e.g.
151.43.71.121. The EMLLIM will convert the TCP/IP number into the Q3 format address.
Figure 23. Example of IP address for 1690WM equipment
RCF 1006 protocol is applied to 1641/1664 SX ( OMSG family).
For RCF protocol the following values are provided :
Presentation = 31; Session =31; Transport = 74703031; AFI = 39 or 47 or 49; Sel = 01
System ID = convert the IPAddress to hexsadecimal, with 4 leading zeros:
e.g. 149.204.78.1 >000095cc4e01
ID (4digits), Organisation Id (16 digits) and Area (4 digits) are optional fields
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
34
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
35
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
5 SUPERVISION
5.1 NE management states
5.1.1 Introduction
The elementary building blocks of any telecommunication network are the Network Elements (NEs). This
section presents the different management states of an NE from the OS point of view. There are 5 manage-
ment states and one Alarm status:
Supervision state:
gives information relative to the supervision state of the NE. There are 4 states.
Declared: the NE is not being supervised (e.g. it has just been declared to the OS).
Supervised: the NE is under supervision.
Activating: the NE is being brought under supervision and no management tasks can be per-
formed on it.
Deactivating: the supervision process on the NE is being stopped and no management tasks
can be performed on it.
Only an NE in Supervised state can be fully managed by the USM application. Please note the
software downloading operations can be also applied to a Declared NE.
MIB Alignment state:
occurs during the NE Supervision state. There are 2 states.
Misaligned: this is a transitory state before being able to visualize the NE configuration.
Aligned: the system becomes aligned when all the operations for synchronizing the NM with
the NE are fully completed. For the Q3 / SNMP NEs the synchronization procedure involves the
alarms, the PM and the NE configuration while for the QB3* NEs the synchronization is relative
to alarms and PM only.
N.B. The alignment state goes automatically to misaligned state when the operational state
goes to disabled.
Local access state:
relates to the ability for the NE to be managed from the local craft terminal CT. There are 3 states.
Granted: the NE may be managed by the local craft terminal. In this case, the icon is displayed
green on the CT and blue on the OS.
Denied: the NE can not be managed by the local craft terminal. In this case, the icon is dis-
played blue on the CT and green on the OS.
Requested: the local manager (CT) has requested update permission from the OS and is wait-
ing for a reply (granted or denied) from the remote manager.
This parameter is set from the OS to Granted or Denied. The CT can only request local access or
return access to the OS.
When no OS is logged in, a CT gets a requested local access after a while. When an OS is logged
in, a CT does not get local access. In this case, it is necessary to call the OS operator to set the local
access state to 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
36
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
If the Local access state is Granted, some USM operations can be disabled (greyed).
As long as local access is granted for CT, the access for NM is denied.
Craft Terminal Connected state:
The Craft Terminal Connected state on the NM-DXC shows if a CT is logged in on the NE. This
means, a Craft Terminal has started supervision on the selected NE in the PNM view.
CT not connected (green): no CT supervises the NE
CT connected (blue): CT supervises the NE.
Operational state:
relates to the ability for the NE and the OS to communicate together. There are 2 states.
Disabled: the communication link between the OS and the NE is interrupted.
Enabled: the NE is either in the activating, deactivating or supervised supervision state and
communication between the NE and OS is possible.
NML Assignment state:
indicates whether an NE is used for Network Management purposes. There are 3 states:
Free: the NE is not assigned to Network management tasks. Element manager level ( 1353 NM
can be selected in the manager list)
Observed: Network management tasks may be applied to the NE.
Assigned: the NE is assigned to Network management tasks (superior network manager se-
lected in the manager list, e.g. 1354 RM). This causes a reduced access on the 1353 NM.
The NML assignment state can be displayed with the Set Manager List dialog.
To supervise the NE, the NMOS establishes a permanent association with the NE.
Any disruption in the communication link between the OS and the NE results in an update of the manage-
ment states when the OS has detected the communication failure. More details are given on Q3 / QB3
NE Management relevant sections.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
37
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
5.1.2 Consulting the different management states
To understand the way in which the different management states are interrelated, the following representa-
tion may be helpful. The NE states are as follows:
NE_STATE [Operational state, Access state, Supervision state, Alignment state, Nml Assignment state]
In the following diagram, depending on the operations undertaken, the management states change. If a
particular management state can take any value, it is represented by the sign in the state representa-
tion. For example, at the launching of the 1353NM, the representation is NE_STATE [, , , , ].
Figure 24. is an example of how the management states can evolve following different operations.

NE_STATE[disabled, granted, declared, , ]
Decl are NE
NE_STATE[, , activating, , ]
Start Supervi si on
Supervi si on
fai l
NE_STATE[enabled, denied, supervised, aligned, ]
Supervi si on
successful
Stop Supervi si on
NE_STATE[, , deactivating, , free/ observed]
Stop Supervi si on
successful
Al l ow
Local _access
NE_STATE[enabled, Granted, supervised, aligned, ]
Compare
MI Bs.
NE_STATE[enabled, denied, supervised, misaligned, free/ observed ]
NE_STATE[enabled, denied, supervised, aligned, ]
Downl oad
Stop Supervi si on
Figure 24. An example of the evolution of the NE management states.
The Network Topology views enable you to get access to the current NE status in which the different NE
management states are described.
The Network Topology views enable you to get the status information on:
A Site: in this case all the NE statuses are shown,
One or more NEs: in which case only that (or those) particular NEs management states are shown.
One or more Sites and one or more NEs: this is the most general case.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
38
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
The above cases are identical in the operations that are undertaken but differ only in the number and type
of the symbols selected. In this section only the most general case is treated.
In a Network Topology view, select the sites and the NEs of which you require the NE management states.
Select the Show Statuses... option from the Operations pull down menu as shown in the following figure.
Figure 25. Operations: Show Statuses
The NE Status dialogue boxes of all the NEs concerned by the operation are opened. An example of this
dialogue box is shown in the following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
39
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 26. Current status dialog box
The title of the dialogue box indicates the NE that is concerned.
N.B. The relationships between the NE statuses and the severity alarm are described in the NE
Alarms and NE status chapter of the Getting Started section (Vol.1/4 of the NM Operations
Handbook manual) .
5.1.3 Resynchronize NE States in the Network Topology view
An automatic refresh of the Network Topology view is performed regularly. However, to make sure that the NE
states displayed by the Network Topology view are really up to date, it is possible to perform a manual refresh.
From the Network Topology view, select the Resynchronize option from the Operations pull down menu.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
40
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
41
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
6 SUPERVISING NES
Supervising NEs is an essential aspect of network management! It enables the gathering of information
concerning the behaviour of the NE with respect to its functional state.
The creation of an NE symbol and the declaration of its characteristics in the OS MIB put the supervision
state of the NE in the Declared state.
You can start the supervision of:
A Site: in this case, the operation is performed on all NEs in the site.
One or more NEs: in this case, only a set of NEs is concerned by the operation.
One or more sites and NEs: this is the most general case.
N.B. The NE addresses must have been declared before starting supervision of those NEs. Other-
wise error messages will be displayed.
6.1 Starting supervision of NEs
SEQUENCE
a ) Select the sites and the NEs to supervise in the Network Topology views. They are highlighted.
b ) Select the Operations: Supervision pull down menu. The operator can then select supervision
either of the options (Align Up..., Align down... or Audit...) for starting the NE Supervision.
Figure 27. NE: Operations: Supervision: Align Up
N.B. Enhanced Align down is applicable only for QB3* equipments. It corresponds to a MIb global
align down
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
42
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 28. Align Up Supervision
The following dialogue box opens from which the operator confirms or cancels the Start Supervision op-
eration using the Ok or Close push buttons.
In this dialogue box, the list of NEs that will undergo the Start Supervision operation is given.
To launch the Start Supervision operation, use the Apply push button.
Messages concerning the supervision operation appear next to the list of NEs.
N.B. Selecting the Close push button will exit the dialogue box without launching the supervision op-
eration.
An Information dialogue box opens indicating that the Start Supervision operation is terminated. Click
on the Ok push button of the Information dialogue box to continue.
When the Start Supervision operation is over, click on the Close push button in to close the dialogue box.
Once the Supervised state is established, an association between the NEs and the OS is created.
This association called implies that the OS constantly supervises the NE. This association is released,
by the OS, only when the supervision is stopped. NE or OS failure automatically cancels the association
which is automatically reestablished by the OS once the NE becomes contactable once again (in the
event of NE failure or network failure) or when the OS is restarted (in the event of OS failure).
On a NE which has been created, the first time the command Align up is required. Figure which follows
shows an example of Align Up end 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
43
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 29. Align Up end Supervision
6.2 Stopping NE supervision
As for the Start Supervision operation, the Stop Supervision operation can be done from the Network
Topology views:
They allow you to stop the supervision of:
A Site: in this case, the operation is performed on all NEs in the site.
One or more NEs: in this case, only a set of NEs is concerned by the operation.
One or more sites and NEs: this is the most general case.
As for the Start Supervision operation, the most general case is explained in this section.
From the Network Topology view, select the NEs of which you require to stop the supervision. Select the
Stop option from the Operations: Supervision pull down menu.
The dialogue box that opens is similar to the one displayed for the start supervision operation. This dia-
logue box gives the list of NEs that will be involved in the Stop Supervision operation.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
44
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Selecting the Apply push button launches the Stop Supervision operation. Messages appear in the dia-
logue box next to the list of NEs indicating the progress of the Stop Supervision operation.
N.B. Pay attention that the Stop Supervision will be suspended during the data PM collection. It may
be necessary to complete the PM collection the following waiting time:
10 minutes for OMSN and 5 minutes for OMSG, during the even day hours
40 minutes for OMSN and 120 minutes for OMSG at the midnight.
6.2.1 Different NE subversion of the same NE type (only applicable to W/OMSN)
Since a NE MIB might be not compatible with next version of the same NE Type & Release, subversion
indication (a letter A,B and so on) has been introduced to automatically distinguish the version. The
reason of different subversions is due to features enhancement or bug fixing. Then the solution is an addi-
tional package for sdhNE object that contains the value of the NE subversion.
In order to manage this subversion of the same NE Type & Release, we have to read this new package
at startup time. USM will subscribe for AVC (Attribute Value Change) of the package of NE subversion.
In this way it is possible to know when the subversion of NE changes.
The following situations can be met:
NE declared and supervisioned:
When the operator starts the USM, it will retrieve the package from emllim which knows the correct sub
version, and then uses it. In additional the USM will subscribe for AVC on NE subversion.
NE declared and not supervisioned:
In this case the subversion is unknown, so the emlim sends back to the USM, the value undefined for
the package subversion and for the version the latest acquired. .
USM already opened:
If a start supervision occurred after USM started and the version of NE is different from previous one,
then the AVC of the new version will be notified to the USM. In this case the USM will show the operator
a message box indicating the equipment change and the USM will be closed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
45
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
6.3 Abort Supervision
In addition to the usual Stop Supervision operation the user can select the Abort Supervision com-
mand.. The Stop Supervision operation allows the operator to perform a smooth closing of the manage-
ment session with the relevant NE. Therefore, before closing the management session, the NM retrieves
the collected PM data that have not been jet retrieved. If the request for Stop Supervision is issued in
some critical periods, immediately after every hours (e.g. at 8, 10, 12, etc.) or immediately after midnight,
then the NM waits for the collection of the last period, which can last a while.
The Abort Supervision operation allows the operator to immediately close the management session with-
out performing the collection of latest historical PM data. Therefore, this operation is normally faster, and
in some cases much faster, than the normal Stop supervision operation.
A warning message is displayed and a confirmation is required before the abort supervision command is
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
46
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
6.4 Black icon with question point
Figure 30. Black icon with question point
PROBLEM
A new 1353NM sw package has been installed which does not manage the versions actually resident on
the NE.
CORRECTIVE ACTION
Execute an NE sw upgrade via SW download commands.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
47
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
7 OS ADDRESS FOR AN EQUIPMENT
NEs exchanging their management information directly with the OS need addressing information in order
to be able to communicate with the OS across the network.
Actually certain types of NEs have two OS addresses at their disposal: the main OS address and a spare
OS address, thus enabling them to switch from one OS to another. This is intended to support, for instance,
OS resilience or OS migration.
At the beginning, both addresses conveyed to the NE are identical, and they are known by the EML agent
by configuration. The given address relates on the workstation which hosts the EML agent.
Only the spare OS address may be individually changed (for NEs which support it).
N.B. The OS address of an equipment can only be changed if the NE is supervised. Nevertheless
it can always be displayed.
To change the NE address for an equipment, place yourself on the submap on which the NE is located.
Select the NE for which you want to change the address. It is then highlighted.
7.1 OS Address
SEQUENCE
a ) Select Declarations: Set Addresses: OS Address
Figure 31. Displaying and changing the OS address for an NE.
b ) The OS Address dialog box is displayed.
The title of the dialogue box displays the name of the NE for which the OS addresses are to be changed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
48
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 32. OS Address dialog box
The first time the OS input address dialogue box is opened, the default main and spare OS addresses
(known by configuration) are displayed in the corresponding entry boxes.
c ) You can change the main OS NSAP presentation address, in accordance with the ISO definition (AFI,
ADI, Organization ID, Area, System ID and Sel entry boxes)
You can also change the optional spare OS NSAP presentation address, using the same format.
The SEL field shall always be put to 1d
d ) Confirm or cancel the changes to the OS addresses using the OK or Close push buttons at the bottom
of the dialogue box.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
49
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
8 ADD CONNECTION
The following figures show an example of creation of connection in the NM map.
Notice that connections are only graphical objects, created only to render easier the users tasks.
A detailed description of the Connection management commands can be found in Section TVA
Figure 33. Operations: Add Connection
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
50
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 34. Add Connection dialog box
Figure 35. Icon selection
Figure 36. Add Connection creation: Apply 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
51
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 37. The connection is drawn in the map
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
52
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
53
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
9 DIAGNOSE
All the options reported on Figure 38. are described in the QB3* or Q3 NE MANAGEMENT manuals.
Figure 38. Diagnose menu options
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
54
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
9.1 Remote Inventory on PNM
9.1.1 Remote Inventory Visualization
The remote inventory are factory information identifying the boards, the final test and eventually other data.
The data are written inside each boards and the operator can only collect the data and read them.
Select a NE in the map and then the Remote Inventory Display option to display the RI data. if the NE is
in supervision state the user with the Upload Remote Inventory option can update the RI data loading the
last available one.
Select a NE and then Operations: Upload Remote Inventory option as in the example of Figure 39.
Figure 39. Upload Remote Inventory option
After the OK confirmation, wait the Success indication as shown in the example of Figure 40.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
55
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 40. Remote Inventory uploading example
Now the Remote Inventory data, for the selected NE, can be shown with the Display Remote Inventory
command.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
56
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 41. Show Remote Inventory menu
Select Operations: Display Remote Inventory to open Figure 42.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
57
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 42. Show Remote Inventory window example
The Remote Inventory window starts with the beginning data and time of the RI and the NE name indica-
tion. Then the following info are listed:
USER LABEL
Gives the information related to the NE type and the rack, subrack and slot board indications.
The list is ordered starting from the first rack on the left, the first subrack on the top and the
first board on the left.
LOCATION NAME (if available)
Specifies only the slot where the board is plugged in. The rack and subrack indications could
be fixed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
58
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
ELEMENT IDENTIFICATION
ALCATEL Company
It indicates the Companys (Alcatels branch) which designs the unit.
Refer to Alcatel for the abbreviation meaning (four characters).
Unit Type
Specifies type of board, e.g. EmptySlot, AGG16... .
Unit Part Number
It indicates Alcatel or Factory product Part No.. The number indicated is that printed on the la-
bels or on the units front plates.
Software Part Number
It indicates the id. of the unit resident software
CLEI Code
It indicates the CLEI code according to Bellcore specs. TRISD325
MANUFACTORING INFORMATION
Manufactoring plant
It indicates the Companys manufacturing plant id. within the company, producing the unit.
Refer to Alcatel for the abbreviations meaning.
Serial Number
It indicates the product serial number as specified by the NR 130 Norm.
Date identifier and Date
It indicates the meaning of the date that follows.
It is a twodigit code supplying the following information:
00 date of construction at the time of final testing
01 production order data
02 construction date of the unit lot
03 date product has been forwarded to customer
04 customer order date
Date (YYMMDD)
The identification of the date depends on the indications stated in the previous field. When only
the year is displayed, the format must be YY
OPERATOR INVENTORY DATA (if available)
Operator Data
It indicates customers data ( name, site...)
Free For System Use
This is reserved for the registration of modifications at the site. Each modification is identified
by a number. Two numbers can be displayed at a time. After more than two modifications, the
oldest entry is deleted.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
59
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
9.1.2 Remote Inventory Wizard
The RI wizard allows to execute a RI uploading operation on multiple selected NEs, to show the RI log and
to display all the RI windows of the chosen NEs.
The RI wizard is an application program designed for QB3* and Q3 NE protocol interfaces. To open the
RI wizard, in the PNM management window, select Operations > Remote Inventory Wizard option
The SEL and un SEL buttons, on the left side , display the selected NE list and not selected NE
list on the right side of the wizard window. The user can visualize all the available (selected and not se-
lected NEs) NEs enabling the SEL and un SEL buttons as shown in Figure 43. In the right side field
there is the SEL column with a button which allows to select or not select any NEs. Clicking on it, its
color change from green to red or vice versa. The highlighted NEs with the green color are the Selected
ones while those with the red color are the Not Selected ones. Clicking on the scrolling arrows / bar
the user can pass trough all the selected / not selected NEs and modifies their (selected / not selected)
status. When the selected / not selected NE list has been completed, the user can activate the required
operation on the Selected NE list:
Show Log and Display RI = both disabled
The RI uploading, of any NE belonging to the Selected NE list, is performed but there is no indication
about the RI uploading: which are the NEs successfully uploaded and which are not.
Show Log= enabled and Display RI = disabled
The RI uploading, of any NE belonging to the Selected NE list, is performed. At the end a file log will
be generated which informs the operator about the RI uploading situation.
Show Log= disabled and Display RI = enabled
The RI uploading, of any NE belonging to the Selected NE list, is performed. At the end the RI win-
dows of the successful uploading operation will be opened.
Show Log and Display RI = both enabled
The RI uploading, of any NE belonging to the Selected NE list, is performed. At the end a file log will
be generated which informs the operator about the RI uploading situation and the RI windows of all
the successful uploading operations will be opened.
In any case, when the Display RI option is disabled, to open the RI windows, in PNM windows, select
the NE and click on Show Remote Inventory option (see Figure 41. ).
The selected / not selected NE list can be filtered through the NE Family , the NE Type and the User
Label entries.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
60
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 43. Wizard dialog box
Depending on the configured NEs in the NMOS system, clicking on the NE family button, one of the
present family can be selected:
all, adm, snmp, wdm,...
If the selected NE Type does not belong to the NE Family the NE type indication is modified to all. If
for the same NE type there are many NEs the user can edit the User Label to drop the required NEs.
The filtering is applied clicking on the filter button.
Different operations can be performed clicking on the four buttons in the right bottom field.
:push on this button to start the Wizard command on the selected / not selected NE list. The wizard
log window and / or the RI windows ( as in Figure 42. ) will be opened depending on the status previously
selected ( Show Log / Display RI ) .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
61
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
: push on this button to save the selected / not selected NE list
: push on this button to come back to the last old saved selected / not selected NE list
: push on this button to save the selected / not selected NE list and to exit from the RI wizard applica-
tion
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
62
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
9.1.3 Remote Inventory Search
With the remote inventory search the operator can search a text, in the remote inventory files, and then
visualize the remote inventory of the wished NE through the NE USM navigation. Click on the Search
button of the Wizard dialog box to open Figure 44.
Figure 44. Remote Inventory Search dialog box
Two different text search can be performed:
editing the text in the Text Search entry box
selecting the Family Type check button, the red bar to open the pull down menu and the family
type component to enter in the text search. (as shown in Figure 44. ).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
63
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
The reset button can be used to cancel the entry text. The search operation starts clicking on the Search
button
The Search Result is listed, after a waiting time, at the bottom field. This field is divided into three parts:
Network Element Name = NE name where the text has been found
Number= number of times for which the test has been found
Search= processed text
The last row at the bottom field contains the Total Number = all times summary.
Pointing the mouse on a command, a tooltip, showing the command meaning, is displayed.
With a double click, on the Network Element Name of the search result, the user can navigate on the
NE USM. With the NE USM remote inventory commands any remote inventory board details can be easily
visualized.
Click on X button to exit and leave the application or on help button to access to help on line facility.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
64
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
9.2 Abnormal Condition ( AC ) Viewer
The Abnormal Condition (AC) is the status of the NE that informs about the presence of special conditions,
forced by the operator via management commands, which prevent the NE from behaving normally accord-
ing to its default configuration. The AC condition status in Q3, SNMP and QB3* supervised NEs is dis-
played on both the GUI (USM) of the NE itself and on the PNM application as shown in Figure 45. , but
the operator commands generating the AC status are located on the USM only.
N.B. It has to be noted that the submap whith an NE in AC status does not display at its turn the
AC status, that is the AC status , as all other statuses, are not inherited by the submap including
the relevant NE.
Figure 45. AC (Abnormal Condition) Viewer menu
General AC for W/OMSN or specific Q3 NE AC conditions (i.e. AC Radio condition on LHR) are described
in the proper NECT Operators Handbook. The QB3* NE AC conditions are logged as NE events into
the NM in an Event Log file. The SNMP NE AC events are described in its own Operators Manuals. Each
operator acting on the NM system can open his own instance of AC Viewer application.
SEQUENCE
a ) Deselect, on PNM map, all NEs to enable the AC Viewer application and then click on Tools: Diag-
nose: AC Viewer to open Figure 46. The AC Viewer window lists all the Q3, (SNMF if any), and QB3*
NEs characterized by the AC status. The NE list is automatically updated on configured interval
time. The chosen refresh time is shown at the bottom of the AC Viewer window.
b ) The operator can force manually the updating of NE list, without having to wait for the period of time,
clicking on the Refresh button as shown in Figure 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
65
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 46. AC Viewer 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
66
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 47. Manual Refresh command
If the AC Viewer has been iconized and the AC NE list, at the refresh time, has been modified, the AC
Viewer icon color changes from blue to red to highlighted that the previous AC NE list has been updated:
if the user opens and iconizes again the AC Viewer, the icon will be displayed again in blue color.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
67
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 48. AC View icons
The AC Viewer is a centralized point for detection of abnormal condition statuses on all supervised NEs.
Then by looking at this AC Viewer application, the operator can inmediately detect which nodes are char-
acterized by any forcing condition that is causing the AC status. Selecting the NE name from AC NE list,
the user, clicking on the Show Equipment button, navigates directly to the related USM NE and can open,
with the USM commands ( Diagnosis > Abnormal Condition List, as shown in Figure 49. ), the USM Ab-
normal Condition List window. For Q3 NE Abnormal Condition details refer to NR5 Equipment Specific
Handbook.
Figure 49. Navigation from AC Viewer (PNM) to NE USM
To configure the automatic refresh time interval, select from the Option menu the set Automatic Refresh
as shown in Figure 50.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
68
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 50. Refresh time configuration option
The set refresh window opens . Two different options can be chosen: setting a new time value and default
time value. Select the new time check button at the top of set refresh window (see Figure 51. ) and move
the Hour / Minute / Seconds scroll bars to set the new time value (1Min.<accepted value <24Hours ).
The Clear button sets the new time to 1Min. , but leaves the dialog box open, the Cancel button dis-
cards the new entries and closes the dialog box, the as Default button opens the confirmation window
of Figure 51.
On the Confirmation window the OK button inserts the accepted value, displaying the corresponding
seconds between brackets, at the bottom of Figure 50. and closes all dialog boxes, the Cancel button
closes the confirmation box dialog and comes back to the set Refresh 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
69
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 51. Set refresh time and confirmation windows
Select the default time check button at the bottom of set refresh window (see Figure 52. ) The default
time value is fixed to 15Min. and can not be modified. TheCancel button closes the dialog box, the as
Default button opens the confirmation window of Figure 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
70
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 52. Set default time and confirmation windows
On the Confirmation window the OK button inserts the 15Min. (900 sec.) value displaying it between
brackets at the bottom of Figure 50. and closes all dialog boxes, the Cancel button closes the confirma-
tion box dialog and comes back to the set Refresh 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
71
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
9.3 Maintenance Memory
The Maintenance Memory (MM) is a local repository stored in any Q3/QB3* NE containing the list of events
which characterized the NE during the last time period. It enables the operator to rapidly discover the
sequence of actions, of user commands, of software failures.... .
This option can be opened from PNM management: select Operations: Upload Maintenance Memory
(Figure 53. ). This feature is also described in the QB3*NE MANAGEMENT manual, Maintenance
Memory chapter.
Figure 53. Uploading the maintenance memory
This option is only used to upload the NE maintenance memory into the NM station getting the last
sequence events stored into the 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
72
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
9.4 Create ISA board
The ISA board management for OMSN has been described in Section Procedures, para 1.5, OMSN
and ATM board management ... chapter 3 . The ISA board management involves both PNM USM / EML
USM commands then this procedure description helps the operator to understand easily all the required
operations.
Figure 54. Create ISA board option
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
73
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
10 MAPS MANAGEMENT
10.1 Introduction
Two types of maps are available: the local map and the distributed map. A distributed map is the original
map created by a privileged user from which a local map may be generated by operators having the
appropriate access permissions. An operator always works on his own local map and modifies it as
necessary without affecting the original. Only privileged users are allowed to affect the distributed map,
each deletion or modification being irreparable.
A detailed description of the local map management is given at Section TVA. See chapter 3.
The access to these operations is given by the File pull down menu:
Figure 55. File options.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
74
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
10.2 Submaps and local maps
This chapter describes the general operations that the operator may achieve on submaps and local maps.
10.2.1 Opening a map
See section TVA. In particular see paragraph Restoring a Local map
10.2.2 Modifying map characteristics
See section TVA. In particular see paragraph Setting the Map parameters and View: View Parameters
10.2.3 Modifying submap characteristics
See section TVA. In particular see paragraph View: View Parameters
a ) Modifying the submaps name.
b ) Modifying the background graphics of the submap.
c ) Modifying the submap layout.
10.2.4 Deleting a map
See section TVA. In particular see paragraph File: Local Persistency: Delete Map File
10.2.5 Deleting a Submap
Delete Child View.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
75
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
10.3 DNM Management
CONDITIONS
The operator axadmin is actually logged.
SEQUENCE
a ) Save the actual map marzia by selecting File: Save Map As...
tks
Figure 56. File: Save Map As
b ) In the Save Map As dialog box enter the map name and click on OK 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
76
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 57. Save Map As dialog box
A DNM Message alerts that the Security profile has been changed.
Figure 58. DNM Message
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
77
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
c ) To verify that the map has been saved you may issue File: Map management.
Figure 59. File: Map management
The map which hs been just saved is present in the map tree. See following figure.
Figure 60. DNM Map Management dialog box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
78
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
d ) To verify on SECUSM browser, notice that the object DnmACD named pippo is now present. See
following figure.
Figure 61. SECUSM browser: DNMAccessControlDomain
And the association dnmusmadmin has been added to profile Administrator
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
79
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 62. dnmusm admin added to profile Administrator
e ) Exit from USM and reenter with an other user with profile Administrator. The new saved map is visible.
See following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
80
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 63. New DNM Map Management dialog box
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
81
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
11 VIEW: DISPLAY OPTIONS
This feature is intended to enable the operator to customize the displaying of management states within
his submaps, in term of color attributes.
The description of this feature is given in Section TVA, para Setting the Display Parameters od a View.
The involved command is View: Display Options
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
82
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
11.1 NE Time Management
This management allows the operator to get or to set NE(s) time at the Network Topology view level.
It is implemented at PNM level in the Supervision pull down menu.
However, an operator may have access rights to get the NE time but no access rights to set the NE time.
The operators profile defines the access rights for the operations.
If the operator does not have the access rights, the corresponding menu is greyed.
Even if the operator has access rights for the two operations, only NEs belonging to the operator access
domain list will be displayed and processed.
11.1.1 Get NE Time Action
To get NE(s) time, a GET request is sent to each selected NEs.
Select the NE and issue Operations: Time: Get
When the user clicks on this option, a window is displayed with all the NEs name related to the selec-
tion (site or NE(s)) as shown in Figure 64. :
Figure 64. GET NE TIME
When the operator clicks on the Apply button, a GET request is sent to all the listed NEs. For each
NE, a message is displayed (see Figure 65. ):
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
83
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
NE Date and Time: as soon as the NE answer has been received and is correct.
Figure 65. Example of GET NE TIME/
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
84
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
11.1.2 Set NE Time Action
To set NE time, the OS time is recovered and sent to the NEs by a SET request.
Select the NE and issue Operations: Time: Set
Click on Apply. The Command status sting contains dat/time sent by EML to NE.
The operator cannot set the NE Time when the NE supports the NTP Protocol or when the NE is managed
by the Craft Terminal (directly connected to the 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
85
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
12 FILE TRANSFER SCHEDULER
The FT Scheduler allows to execute a software downloading operation on multiple NEs, the defining se-
quence to follow and the activation time as SWDL ( Software Downloading Scheduler). Besides allows
to execute the SNMP MIB back up and the Q3 MIB align up.
Thus the FT scheduler is an application designed for QB3* , SNMP and Q3 NE protocol interfaces. To
open the FT Scheduler, in the PNM management window , select Supervision > FT Scheduler option
(as shown in Figure 66. ) . The application automatically excludes those NEs that do not support SWDL
protocol or MIB Backup / Align Up.
Figure 66. FT Scheduler option
The usm process can be installed on any OS types (Master or Presentation). Only one FT Scheduler USM
can run at the same time on the same OS workstation: if the user tries to open a new FT Scheduler USM,
a warning box will advice that the application is already running.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
86
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
12.1 Software Status
The Software Status menu allows visualizing the NE software status on different modalities: for all NEs,
for NE name and for NE type. The info is retrieved from NEs themselves.
To get the SW Status of all NEs, select the SW Status menu and then All NEs option.
Note that pointing on every single item of the FT Scheduler menu, a tooltip showing the command meaning
is displayed as shown in the example of Figure 67.
Figure 67. SW Status menu All NEs option and its tooltip
The All NEs option lists the SW Status of all the reachable NEs created on the NM system, independently
of the NE Supervision state, excluding the NEs not managed by the tool as mentioned in the previously
paragraph (see Figure 68. ).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
87
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 68. NEs SWDL Status
The NE software package banks are distinguished by the different color: the first bank is green, the second
one is yellow. The selected row becomes light blue.
Clicking on the column names ( grey ) it is possible to sort rows. The up/down arrow visualizes the increas-
ing/decreasing sorting chosen ( by name, by version,...). The Exportcommand creates a file in CSV
(Comma Separated Value) format with assigned name and path. This type of export file is utilizable by
other applications. Clicking on the Export button Figure 69. opens.
Figure 69. Export command
Clicking on OK the file name and path are visualized as shown on Figure 70.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
88
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 70. File export characteristic
A similar SW status window can be opened selecting the NE by Type. Depending on the NE number, de-
fined on the NM system, it is possible to have two different Select By Name menus. The first one, shown
in Figure 71. , represents a menu with a NE list while the second one, shown in Figure 72. , a menu with
the Select one from list indication, used to help selection on large number of NEs.
Figure 71. SW Status selected by name with a NE list menu
Figure 72. SW Status selected by name with Select one from list indication
Selecting, for example in Figure 71. the 1650SMC21, Figure 74. 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
89
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Clicking on the Select one from list in Figure 72. a secondary window with a filter area is visualized
(Figure 73. ): the filters can be applied On the NE Type and On the Supervision Area. The NE Type
selects one NE, while the Supervision Area one ethernet board. Supervision Area defines the set of
NEs supervised via a given LAN network interface. The supervision area field gives the name list of the
ethernet board itself. Selecting the filters, the result will be listed in the Select NE field.
Figure 73. NE by name selection
Select the NE name and click on OK button to open Figure 74. The same Figure 74. can be opened
with a double click on the selected row of NE Software Status Table ( Figure 68. ).
The Software Status Details are represented on a double panel. The number with grey background repre-
sents the visualized panel while the one, with dark grey background, indicates the hidden panel. Click on
the dark grey background panel to pass from a panel to the other. (Figure 74. shows panel number 1)
Figure 74. NE software status detail
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
90
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Selecting a Q3NE element the Software Unit Status button will be enabled while the View Descriptor
File button will be disable (greyed). Clicking on the Software Unit Status button Figure 75. opens.
Figure 75. Q3NE Software unit detail example
N.B. It should be noted that in the Software Unit detail window the ATM SW package types can be
visualized, as shown in the example of Figure 75. .
Clicking on the View Descriptor File button Figure 76. opens, only for QB3* 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
91
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 76. QB3*NE Software Package Descriptor view example
Some Software Management Action can be accessed via the NE Software Status Detail Dialog box.
The available actions depend on the NE type and loaded SW Package status. A pull up menu shows the
available actions (see Figure 77. ). The possible actions are:
None : no action.
Activate: serves to activate the selected software package.
Force: force reactivating of active SW package.
Commit : the selected SW package (the active one) will be activated at NE restart.
Delete : the selected package will be deleted on the NE.
Duplicate: the selected package will be duplicated on the 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
92
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 77. Software management action example
When the required action has been selected , click on the Apply Action button: a confirmation dialog box
is shown before starting the action (see Figure 78. )
Figure 78. Confirmation box window
For theSelected By NE Type option it is possible to have two similar different menus depending on the
number of NE types. The first one represents a menu with a NE list, the second one with the Select one
from list indication. Selecting, for example in Figure 79. the 1664 SM, Figure 82. 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
93
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 79. SW Status Selected by NE Type with a NE list menu
Figure 80. SW Status Selected by NE Type with Select one from list indication
Clicking on the Select one from list indication of Figure 80. , the secondary window of Figure 81. is
opened.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
94
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 81. NE by type selection
Clicking on the selected NE type, Figure 82. opens. From NE Software Status table it is always possible,
selecting a row, NE software package, to open the NE software status detail of Figure 77.
Figure 82. NE by type SW status
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
95
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
12.2 FT Scheduler Job
The FT scheduling function is based on the information contained into the Job descriptor file.
The Job menu allows to create job descriptor files, to open the existing descriptor files, to show the run-
ning job status and the job report.
Figure 83. Selecting the New option from the Job menu
The job editor allows to generate a Job containing a sequence of Sessions each one composed of a
set of NEs. The policy of providing different sessions within the same job allows having a two levels ap-
proach in the FT operation. All the NEs belonging to a session are Downloaded / Backedup before
the NEs of the next session: the job will start from the first NE of the first session and will go on, respecting
the order of sessions and in each session the order of NEs. This permits to control the DCN traffic in the
network, then the global FT phase can be organized in order to not overload some specific GNEs or inter-
connecting DCN links. The maximum NE number for any session is 90 but there is no limit regarding the
maximum session number in a job.
Select the New job to open Figure 84. and then click on the start button
to choose (see Figure 85. ) the new Backup or Download job.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
96
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 84. New Job creation
Figure 85. Job type selection
Click on Yes or on No to start editing/building the Backup or the SWDL ( Software Download ) job.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
97
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
The editor job window (see Figure 84. ) is composed by two parts: left and right sides. The left side is simi-
lar to a tree directory. Here the user creates the job tree selecting, with the mouse button or with the arrow
buttons, the different tree branches . To navigate up/down, to add or delete sessions or NEs click, with
the right mouse button, on the branch and select the menu option (see Figure 86. ). The right side window
represents the configuration side to fill in with the required indication.
On the right side enter the mandatory job Name and the optional Info. Select then Now or At Time.
Choosing At Time, click on the editing boxes and typing the requested values to introduce Data and Time
of the job activation . A red check sign on the left window will point out a correctly configured branch. Then
the user can go on selecting, with the right mouse button, the new entry data.
Figure 86. SWDL job: Adding a new Session example
Select the Add Session to add a new session item. Then click again, with the right mouse button, to open
the Add NE menu as shown in Figure 87.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
98
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 87. SWDL job: Adding NE equipment
Click again on the new created tree branch ( similar to a subdirectory indication ), to open the configuration
window shown on Figure 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
99
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 88. SWDL package assignment example
In the SWDL window, the NE Label can be filtered choosing the Supervision area and the NE Type.
If many NEs are managed the filters visualize a restricted NE set in the NE Label field making easier the
required selection.
The selected NE label will be also shown at the left window side as name of the tree branch: the NE detail
will be reported in the related NE detail field accordingly. Depending on the selected server and on the NE
type, the list of available software package will be shown. Then select the package version in the list to
complete the NE SWDL package configuration. If the operator wants to select a SWDL package belonging
to another NE Type, he can enter the NE type into the Package Filter and then, clicking on the Apply
Package Filter button, choose the NE package. The Apply Package Filter command can be also used
to perform two other operations:
If a ISA board is equipped into a OMSN, the OMSN software package can be selected by Apply
Package Filter option to show an enhanced OMSN software package: for example to change the
Software package 650SMC with the 650SMCE enter it in the Package Filter and click on the Ap-
ply Package Filter button.
The same Apply Package Filter option associated to the CTRL button can be used to force the
software package list updating in the FT Scheduler editor after a new software package installation.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
100
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Repeat the same Add NE or Add Session items to complete the job procedure. At the end the user can
select Submit to start the SWDL job, Save to save the job into a file name or close, selecting the Exit
option to close Job Scheduler Editor menu (see Figure 91. ). Note that before submitting a job, all
branches have to be correctly updated, the red check sign indication will appear on every completed item.
The same concepts can be applied to a Backup job but the backup job window is slightly different to the
SWDL one. In Figure 89. is shown a Backup window example. The main differences are the periodic job
and the misalignment flag options.
Figure 89. Backup job window example
A periodic backup job is automatically rescheduled every 24 hours selecting At Time and the Periodic
Job options. A Backup job assignment example is represented in Figure 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
101
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 90. Backup job assignment example
If the Misalignment Flag is selected the Backup operation on the target NE will be executed only if the
MIB NENM misalignment is detected. This option is available only for those NEs supporting it.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
102
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 91. Closing the job scheduler
If the SWDL / Backup Scheduler has been opened and a Job is running, a warning message is displayed
on the screen as shown in Figure 92. The user can check the job current status clicking on the Yes button
of the job running indication window. The same Show SWDL / Backup running job commands are also
available on the Job menu option ( see Figure 83. ).
Figure 92. Job running indication window
The job status gives all the session statuses and single NE procedure values for backup and SWDL (see
Figure 93. ):
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
103
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
green color indicates that the swdl procedure has been successfully executed,
red color indicates a failed procedure,
grey color indicates that the procedure has not been started,
orange color indicates the procedure is still running.
On the right window side are reported the selected NE SWDL / Backup details.
Figure 93. Example of job Status
Select the Abort button to interrupt the SWDL in progress job or the Close button to close the monitor-
ing window. From the SWDL / Backup monitoring window the user can open the View Report window
(see Figure 101. ) selecting from the Job menu, the relative command (see Figure 95. )
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
104
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 94. Example of backup job status
Note that in Backup job window the Abort button is not active selecting the single NE branches.
In the status of job / session / SWDLNE or BackupNE, the following colored icons can be found:
grey: Waiting start
orange: Activated
green: finished operation with No Error
red: finished operation with Errors
red with a crossed sign: Aborted operation
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
105
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 95. Job status and View Report command
N.B. The View report is described in para. 12.2.2 (on page 110).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
106
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
12.2.1 Job editing facilities
Shift and Ctrl keys
The scheduler editor allows selecting several NEs at the same time. The required condition is that all the
NEs to be included belong to the same family.
To define the set of NEs belonging to the same family select, in the left job window, the first NE belonging
to the chosen family and then, pushing on the Shift key, the last one. All the NEs between the ones chosen
will be simultaneously selected, excluding other NE types. In the example of Figure 96. the 1664sm31
NE has been selected identifying the NE family, then the 1641sm28 NE (last available NE) has been se-
lected, but only the first three NEs, of the same type, have been included in the set.
Figure 96. Select extension with Shift key
It is also possible to select different NEs, belonging to the same family, through the Ctrl key. Choose the
first NE type identifying the NE family, and pushing on the Ctrl key, select all the other NEs. In the example
of Figure 97. the operator has selected the 1664sm31 NE and then, pushing on the Ctrl key, the
1664smR3.2B, 1650 smc1.1ve and 1641sm28 but only the first two NEs have been chosen.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
107
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 97. Select extension with Ctrl key
On the right side of the job window the user has to choose the common NE software package available
among the software package list. (see Figure 96. and Figure 97. ).
Cut & Paste Editing
To cut one or more job tree branches, select tree branch to cut and click on the Cut option from the Edit
menu as shown in Figure 98. Apply the Paste command following the same procedure. In the examples
of Figure 98. and Figure 99. the branch of 1641sm2.7 has been cut from the Pluto job and has been
pasted on another job descriptor.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
108
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 98. Cutting a branch
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
109
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 99. Pasting a branch
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
110
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
12.2.2 View Report
Two View Report options are available: the View SWDL Report and the View Backup Report. These
view report files can be opened with the relevant options from the job menu ( see Figure 83. ) or with
the View Report commands from the SWDL / Backup job menu ( see Figure 95. )
The View report starts with the beginning data and time of the FT Scheduler Job and the Job name
indication.
Then, for each NE lists, the beginning data and time of the SW Download / Backup, NE name, software
name, software version, software type, Server address ( alias named EML Area Domain) and the forced/
not forced SWDL type attribute. It follows, for each NE, the end data and time of the SW Download /
Backup , NE name, SWDL / Backup result and, eventually, the Error indication.
The report terminates with the end data and time of the SW Download / Backup Scheduler Job and
the summary indication of the SWDL successfully executed and the SWDL failed.
The Backup view report example is shown in Figure 100. while the SWDL report is shown in Figure 101.
Figure 100. Backup report window 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
111
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 101. SWDL report window example
The SWDL / Backup View report can be configured in two different ways:
adding info in the report file at each job start time : all the SWDL / Backup info will be stored in the
report file appending them to the existing;
writing a new report file at each job start time : the report file is created new and only the last SWDL
/ Backup info will be stored.
To configure the SWDL / Backup View report, access to the directory :
/alcatel/Kernel/SystemInstances/1353NM_<Inst_number>/swdl/swdlsched/conf,
select the file: param.cfg and modify the BCKP_LOG_FILE_REWRITE and/or SWDS_LOG_FILE_RE-
WRITE values in following way :
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
112
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
False = if the job report file must be created new only if it doesnt exist, at job start time, otherwise it will
be appended
True = if the job report file must be created new at each job start time, it will be rewritten each time that
a job starts.
The default values are: SWDS_LOG_FILE_REWRITE= True; BCKP_LOG_FILE_REWRITE=
False.
12.3 FT Scheduler Editor
12.3.1 Save and Open menu options
Before closing a job window the user can save the created file clicking on the Save option job window
(see Figure 105. ). The first time the Save As window will be opened and the file name has to be typed
into the bottom editing field ( see Figure 102. ). Following times the file will be saved without displaying
the Save As window. The same Save and Save As options can be selected from the SWDL Scheduler
Job pull down menu (see Figure 103. ).
Figure 102. Entering the file name to save
To access the available job list , click on the Open option of the FT Scheduler editor menu. The same
option can be selected from the FT Scheduler Job menu (see Figure 83. )
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
113
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 103. FT Scheduler Editor menu
Figure 104. Opening an existing job
Choose the job name from the list as shown in Figure 104. and click on OK to open Figure 105.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
114
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 105. Opening a selected job
The Delete file command of Figure 103. deletes the selected job clicking on the OK 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
115
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
12.3.2 Window Management
Window
All the opened jobs, listed in the Window menu, can be visualized, one by one, on the SWDL Scheduled
Editor window. Choose the job name and click on it to open the relative window.
Figure 106. List of the job opened
Arrange Window
To see more jobs simultaneously on the scheduler editor, select the Multiple Document View option
of the Arrange Window menu as shown in Figure 107. To reduce or enlarge the job window use the two
little boxes with the up and down arrows in the title bar; to close the window use the box with the cross
in it.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
116
02

SC.5: EML CONSTR.

/ 3AL 89061 AA AA

116
116
Figure 107. View of multiple job windows
END OF DOCUMENT
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
1
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72


TABLE OF CONTENTS
1 INTRODUCTION 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Edition scope 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.3 Target audience 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Document Organization 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Q3 BASED NE MANAGEMENT 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Data storage and recovery procedures 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 The MIBless architecture of 1353NM 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 The backup of Q3 NE into 1353NM 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 The onboard simulator of Q3 NE into 1353NM 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 Equipment boards replacement procedures without affecting the service 19 . . . . . . . . . . .
2.3.2 Procedure to perform an offline configuration 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 RM behavior with respect to the MIBless architecture 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 OMSN AND ATM BOARD MANAGEMENT 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Introduction 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 OMSNs and ISA board: PNM customization 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Create ISA board 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 ISA Address 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 OMSN + ISA: Supervision 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Rename ISA board 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 Error Recovery: commands for NM administrators 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 PROCEDURES TO HANDLE TRANSMISSION ALARMS 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Introduction 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Why Transmission alarms are not shown at subrack view? 33 . . . . . . . . . . . . . . . . . . . . . . .
4.3 How to identify transmission alarms starting from NE subrack view 34 . . . . . . . . . . . . . . .
4.4 Transmission alarms sublist in AS component. 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 ALARM SEVERITY ASSIGNMENT PROFILE CUSTOMIZATION FOR OMSN 39 . . . . . . . . . . . . . .
5.1 Introduction 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Scope 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
01A 040127
02 040728 SC04091002
V.SCORTECCI ITAVE M.ARMANINI ITAVE
050623 03 SC04091002
V.BALCONI ITAVE M.ARMANINI ITAVE
1353NM REL.7.0
VERSION 7.0
OPERATORS HANDBOOK
L.MERLI
L.MERLI
A.CORTESE L.FORESTA

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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
2
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
5.1.2 Description and Warnings 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.3 Description of the procedure 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Customizing a new ASAP on NMOS 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1 Introduction 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2 ASAP creation Procedure on NM 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Customizing a new ASAP on RMOS for PDH ports 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 Customize the new ASAP 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2 Error analysis 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 FILE TRANSFER SCHEDULER 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Introduction 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 FTS Application 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Functionality 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Operational scenario 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Job Planning 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6 Job Editor 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7 Job Scheduling 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.8 Job Monitoring 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.9 Job Report 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10 NE SW Status Visualization 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.11 NE SW Management 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.12 Appendix A 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 OBJECT ASSIGNMENT DOMAIN 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
3
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
FIGURES
Figure 1. QB3* NE and Q3 NE NM connection types 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Misalignement (warning alarm) between NE NM MIB and NE configuration 11 . . . . . . . . . .
Figure 3. NE Statuses shown window 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Simulator menu Align Up option 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Information window during a MIB Align Up procedure 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. NE NM MIB representation 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. RM connected to NE simulator 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Onboard Simulator monitoring 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Operations: Create ISA 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Create ISA dialog box 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Possible ISA boards 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. ISA: Set Address: NE Address 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Set Addresses: IP Address 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Start Supervision on OMSN. 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Operations: Rename ISA 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Alarm indication syntheses 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Alarm Menu 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Alarm surveillance window 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. AS navigation back to NE EML USM 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Relationship between AS and Port View of NE EML USM 36 . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Show Equipment pop up menu 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Configuring Alarm Severity Assignment Profile. 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. ASAPs Management dialogue box. 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. ASAP Edition dialogue box example. 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Example of Management dialogue box with two customized ASAPs 45 . . . . . . . . . . . . . . . .
Figure 26. ASAP Identifier on ASAP Edition dialogue box 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. ASAP list 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. DCN network example 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Balancing the DCN traffic load 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Optimizing the load traffic for session 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Job editor example 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. MIB backup job example 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Misalignment Flag in the backup job 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Job in progress status example 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. SWDL job report example 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. NEs software status table example 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Action on NE software package memory banks 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Example of DCN traffic increasing the LAN load 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. OAD: Object: Create 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. new OAD object 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Elementary OAD: Create 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Edit Operator profile 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Elementary OAD and ACD of the Viewer Profile 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Create NE 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLES
Table 1. Default Assignment of Service Dependency and Severity on OMSN 44 . . . . . . . . . . . . . . . . .
Table 2. Possible customization Assignment of Service Dependency and Severity on OMSN 44 . . .
Table 3. Link load of level 1 ( example of Figure 30. ) 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Link load of level 2 ( example of Figure 30. ) 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
4
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Table 5. Link load of level 3 (example of Figure 30. ) 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 10. Link load of level 4 (example of Figure 38. ) 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
5
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
1 INTRODUCTION
1.1 Scope
1.1.1 Document scope
The aim of this document is to describe some procedures, concerning the NM configuration, in which can
be involved the PNM / USM commands. Then in our intentions this document could clarify, through step
by step items, how to perform some of the SH functionalities. Any different chapter is related to a different
procedure and the title of any chapter is self explaining of the described procedure. The detail commands
can be found in the other sections of this same Operators Manual. The procedures are only concerning
the actions to be performed to achieve the final results. During the documentation phase other procedures
could be added according to the different network release commands and fuctionalities.
1.1.2 Edition scope
None.
1.1.3 Target audience
This document is intended for people who are in charge the DCN network and NEs management using
the NMOS system.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
6
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
1.2 Document Organization
This document consists of the following chapters:
Introduction this chapter
Q3 Based NE Management explains concepts related to the new Q3 MIB management
OMSN and ATM Board Management for NM Operator explains how to configure and managed the
ATM ISA board.
Procedures to Handle Transmission Alarms explains how to consider the transmission alarm in NM
system.
Alarm Severity Assignment Profile (ASAP) Customization for OMSN explain how to assign a custo-
mization ASAP to a PDH path. The procedure must be executed on 1353NM and on 1354RM.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
7
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
2 Q3 BASED NE MANAGEMENT
2.1 Data storage and recovery procedures
In NR5, the MIBless architecture has been adopted in NM concerning the management of Q3 NEs. This
implies that 1353NM system does not mirror the NE configuration, and directly uses the NE itself as a refer-
ence configuration base.
This has a bunch of consequences in the procedures to be used by the Network Operators in managing
the Network, e.g. backup/restore and configuration alignment procedures.
Moreover, a new entity appears in the scope of the management of Q3 Network Elements, the NE on
board simulator on 1353NM management platform.
This technical description aims at describing the new management architecture, why and how the NE on
board simulator shall be used when managing a Telecommunication Network, and how the management
procedures are impacted from Operator viewpoint.
2.1.1 The MIBless architecture of 1353NM
Starting from1353NM 5.x (hereafter simply referred to as NM) is the Element Management platform that
provides the Network operator with the capabilities to configure and monitor the supported Network Ele-
ments (NEs). The 1353NM product allows managing NEs different both in transmission technology (SDH,
WDM, Radio, ATM, IP) and in management interface they provide towards the management system (Q3,
QB3*, SNMP). In this paper, we will focus on Q3 technology, and its main differences with respect to QB3*
technology.
With respect to NR3 management structure, 1353NM implements an important architecture change in the
management of Q3 NEs, the socalled MIBless architecture.
As far as Q3 NEs are concerned, no replication of NE configuration data is kept within NM and the NM
relies on the database stored within the Q3 NEs themselves. This is due to the capability of NM5 to manage
very big NEs (i.e. DXCs) so that it is not reasonable to duplicate the NE configuration inside NM and to
perform configuration synchronization.
On the other hand, in the scope of the management of QB3* NEs, a complete copy of the configuration
of each NE is stored within the 1353NM platform (the socalled NECTAS tables). When reading or modify-
ing the configuration of a QB3* NE, the 1353NM Operator actually works on the local mirrored configura-
tion data. If he/she wants the configuration changes to be applied in the Network Element (NE), the Opera-
tor shall ask for the download of the new configuration data onto the actual NE.
In this architecture, MIB upload, download and audit capabilities are provided to the Operator to maintain
synchronized the copy of the NE configuration stored in the NM against the actual NE configuration. It is
worth noting that the copy of NE configuration present inside NM does not include the identification of acti-
vated Performance Monitoring points of measure.
This MIBless architectural choice has some consequences on the Network Management in general, on
management procedures and on Operator perspective. It is worth reminding once more that this new con-
cept applies to the management of Q3 NEs only, and the architecture for the management of QB3* NEs
is completely unchanged, and the related operator procedures as well.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
8
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
The following list includes the main concepts associated to this new architecture:
1 ) The reference database for NM is the NE database itself. The NM operator actually works on
the NE database, and not anymore on a local copy of the NE configuration. Only some adminis-
trative NE configuration data are stored within the NM (typically NE name, location, address,
and some other few information). This choice avoids any possible problem of desynchroniza-
tion of data between EML and NE.
2 ) The data communication network (DCN) connecting the NM to the NE assumes a bigger rele-
vance both in terms of reliability and rate. In fact, the faster the network, the faster the response
time of the system in displaying NE configuration data (normal USM views). Moreover, if the NE
is isolated, the operator has no possibility (in principle, see later chapter on simulator) to see
its actual configuration.
3 ) The MIBless architecture implies that there is no need at (re) connection time for the NM to
perform a complete database resynchronization against the actual NE configuration. Only
alarms, the identification of monitored Termination Points and some few other configuration
data have to be synchronized at connection time.
SENIM
OPTICS IM
QB3* EML IM
Nectas tables
OPTICS IM QB3*
USM
USM
RM
RM DB
RM DB
1
1
1
2
2
2
4 3
1
2
Q3 NE
Q3 NE
QB3* NE
QB3* NE
DB
DB
DB
DB
MIB
Q3 EML IM
NM
USM
USM
Figure 1. QB3* NE and Q3 NE NM connection types
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
9
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Despite the fact that NM is not any more the repository of the NE configuration for Q3 NEs, NM product
maintains a central role in the management of the network and in recovery procedures. The following list
includes the main functions (visible or not to the operator) that can be performed only from NM:
1 ) The NM is still the unique management system directly connected to the NEs (with the only ex-
ception of 1664SX which can be directly managed by 1354NP for restoration purposes). Any
other management system (RM, SY, BM) which needs to act on the NE has to pass through
the NM.
2 ) The NM product is responsible for establishing and maintaining the OSI association with the
managed NEs. It is up to the NM to retry to establish the OSI association after any disconnection
of the management link.
3 ) The NM is responsible for the handling of alarms generated by the NE, also with respect to upper
managers so acting as a sort of mediation device.
4 ) The NM is responsible for the collection of PM historical data from the NE, independently of the
Manager who started them.
5 ) The NM is responsible for the recovery actions to be taken in case of major NE problem (NE
substitution, NE loss of configuration memory).
6 ) The NM is responsible for the NEs SW download and NEs MIB backup.
7 ) Finally, the NM is responsible for equipment provisioning, synchronization configuration, exter-
nal point configuration, and for all the functionalities which are not available at NML level.
In few words, the NM is the management platform devoted to all the maintenance activities of the transmis-
sion network, and it acts as a central agent between all the network management systems and the NEs.
Nevertheless, it maintains all the capabilities to completely configure and manage the NEs in all their man-
agement domains.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
10
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
2.2 The backup of Q3 NE into 1353NM
The 1353NM product does not maintain any updated copy of the NE configuration. The NM directly works
on the NE MIB to read and change the current NE configuration.
Nevertheless, in the scope of providing recovery procedures, the NM provides facilities to backup and re-
store the database (MIB) of each Q3 NE. The MIB alignup/aligndown procedures are all based on the
same protocol (ISO 802.1e on top of CLNP) used for the SW download.
The MIB file copied into NM is used only as a backup copy of the actual NE configuration, and it is not,
in any case, used during normal network management activities. Therefore, the NE MIB image is not up-
dated online when the actual NE is being configured (independently on the originator of the configuration
changes, either NM operator, or RM / SY systems).
The MIB backup includes all the NE information (i.e. NSAP address, Ethernet, LAPD, ) excepts the
payload structure, crossconnection and PM data.
The MIB backup file size depends on the NEtype. Examples of file sizes are:
1640FOX around 140KB
1650SMC around 170KB
1660SM around 630KB
1664SM around 90KB
1666SR around 30KB
1641SX around 40MB (for a big DXC configuration)
and the time required for backup is in the order of few minutes (5 to 10 for DXC).
It is likely worth noting that the backup of DXC is performed via SMF.
N.B. Note that backup files for new equipments are compressed, then requiring less memory space
and less transmission time.
Now, the MIB of the NE backed up into NM is actually the exact copy of the memory inside the NE. This
copy is strictly dependent on NE type and release, and its basically readable by the NE only.
Since RM contains in its internal database all the configuration of the NE as far as the transmission frag-
ments are concerned, it is mandatory for the MIB backedup into the NM to be always synchronized with
the latest changes in the Equipment and Synchronization configuration information.
In other words, the NM operator shall perform an upload of the NE MIB every time either CT or NM
operators performed any change in the Equipment (board provisioning) or Synchronization con-
figuration. In this way, NM and RM systems together contain a global and consistent information of the
actual NE configuration.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
11
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
In order to trigger the Operator for such upload, an alarm is generated by the system every time there is
even the doubt that the Synchronization or Equipment configuration changed with respect to the copy
present in the NM system. The alarm (with MIB backup misaligned probable cause and warning severity
see Figure 2. ) will be cleared by the system as soon as the MIB upload operation has been successfully
performed on the relevant NE using the Supervision Align Up option.
Figure 2. Misalignement (warning alarm) between NE NM MIB and NE configuration
The MIB upload operation is manual, and not automatic, since the system cannot automatically know
when the sequence of configuration operations done by NM Operator is finished, or if the configuration
operation done by CT Operator is really to be adopted by the centralized management platforms.
The utility of the backup copy is basically associated to the possibility to restore the previous configuration
data into a NE that failed. In this scope, it is mandatory for the management systems to be able to recreate
the latest configuration of the NE in order to download it.
The backup and restore of the MIB database can be performed by CT as well, so that the NE MIB will be
transferred onto CT platform.
The MIB operation is completely decoupled from the existence and usage of NE onboard simulator in
NM. In fact, for example, DXC and WDM NEs do not support the simulator on NM, while they do support
the possibility to backup and restore their MIB.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
12
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
The (NE) simulator, named also onboard simulator, utilizes the same NM NE MIB ( NE MIB copy in
the SH system ) and the different expression is often used to distinguish the enviroment of NM NE MIB
activation. So the onboard simulator is activated in read/write configuration when the NE Supervision
has been stopped: the Supervision State is Declared (see Figure 3. ).
Figure 3. NE Statuses shown 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
13
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
The MIB alignup. ( see Figure 4. )
The alignup option allows the operator to upload the copy of the MIB image from the NE into the area
of the NM simulator. The simulator will use this copy, which is supposed to be the last updated one of the
NE database. When the database is being aligndown, this MIB image will be downloaded into the NE.
The last NE MIB image alignup always overwrites the previously one, even if its contents have been
changed using the NE simulator.
Figure 4. Simulator menu Align Up option
With the NE Supervision State Supervision, open NE USM application and select the Align Up option,
confirm the align up and wait the end of the operation (see Figure 5. ).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
14
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 5. Information window during a MIB Align Up procedure
N.B. The Activate option shall performed after an Align Down to NE command to activate the
NM NE MIB copy into the NE equipment
After pushing the Activate button the related NE shall restart itself therefore the NM operator
has to wait a few minutes until the NE will became aligned with the new MIB previously down-
loaded . During this transitory period no actions on the NE are possible because the NE is in Q3
isolation.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
15
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
The following picture depicts the NM MIB depository.
Q3 NE
Q3 NE
QB3* NE
QB3* NE
OPTICS IM
NECTAS tables
DB
DB
QB3* USM
QB3* USM Q3 USM
Q3 USM
NM
Q3 OBS
Q3 OBS
ISO 802.1e
QB3*
DB
DB
SH NE MIB
Figure 6. NE NM MIB representation
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
16
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
2.3 The onboard simulator of Q3 NE into 1353NM
An important change in NR5 is related to the introduction within the NM of NE onboard simulators (OBS).
The onboard simulator is used to simulate the presence of the actual NE on the NM in order to read (and
write) the MIB copy resident on the NM. The onboard simulator is actually the same SW of the NE, just
ported onto NM platform.
The onboard simulator is a tool that shall be used in the scope of precise procedures, hereafter listed,
and normally it is always switched off. The OBS is not provided for testing or debugging purposes, but it
is an integral part of NM product.
The reasons why the OBS is required on NM are the following:
1 ) In case of a DCN failure between the NM and the GNE, the NM operator has lost access to the
NEMIB. He is not anymore able to know the the NE configuration. Normally there is no strong
reason why the NM operator should be interested in knowing the last known NE configuration,
but if he/she does want to navigate through the NE configuration, he/she can start up the simula-
tor and read the backup copy of that NE.
2 ) When an offline configuration operation is performed. The offline configuration procedure is the
possibility for RM operator to act on the configuration of one Q3 NE even if it is not yet currently
reachable (because not yet installed). This feature can offer to the Network Administrator the
possibility to preconfigure the network, starting creating the network topology and even trans-
mission configuration before the network actually exists.Hence this feature applies only once
in the network lifetime.All the NEs pertaining to the network shall be declared and provisioned,
even if not yet installed in field. In this scope, the NM Operator can use the onboard simulator
to provision each new NE, one at a time. Through this simulator, the 1354RM system can get
aware of ports existing in each NE, so that RM can populate its internal database. From this
moment on, the onboard simulator shall be switched off and RM will work on its own database.
3 ) The replacement of an Equipment Controller (EC) is in fact the main reason for the develop-
ment of the OBS The replacement requires a procedure which synchronises onsite activities
on the management system to avoid traffic perturbation. The procedure is based on a resyn-
chronization between the data stored into 1354RM system and the NE MIB backup. In this
scope, the simulator is mandatory to allow RM to write onto NE MIB backup in order to realize
the realignment. The procedure is slightly different with respect to the QB3* environment, but
the results of both procedures are the same.
Therefore this is an emergency procedure applied when a NE is unreachable or to replace the EC, per
default, only one OBS can be opened at a time.
Hence, it is clear that the simulator shall be used only in very special and delicate network phases, and
that its usage shall be controlled by expert network operators.
The OBS is manageable by NM not by Craft Terminal
A more detailed description of the above procedures are provided in para.2.3.1 and 2.3.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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
17
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
NE
simulator
NE
simulator
OPTICS IM
DB
DB
USM
OPTICS IM
Q3 EML IM
NEs IDs
NM
Q3 NE
Q3 NE
DB
DB
DB
DB
RM
OPTICSIM
OPTICSIM
STARTED
USM
Figure 7. RM connected to NE simulator
Once understood why and when the NE OBS shall be used, it is clear why the operator can only start the
NE simulator manually. No automatic mechanism to startup the simulator exists in NM. Moreover, the
NE simulator can be started only if the associated NE is not currently read (condition of Q3 isolation).
The NM operator shall startup only one simulator at a time.
As it is manually started, the NE simulator shall be manually stopped. If the simulator of a given NE is
started, and maybe the NE becomes reachable again, the operator keeps on working on the NE simulator
until he manually stops it.
Once started, the NM operator is aware of the fact that he/she is currently working on the simulator, and
not on the actual NE, by the relevant state on the right side of the USM. Moreover an OBS monitoring pro-
cess is available to detect globally which simulator is active, if any (see Figure 8. ).
The onboard simulator can be opened from TMNOS view. On Board Simulator Monitoring. Clicking on
the monitor picture, the box window shows the NE equipment name where the OBS is running. Note that
this window is not automatically updated: push the Refresh button to know the current onboard simula-
tor status.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
18
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 8. Onboard Simulator monitoring
Assuming that the supervision of that NE was not previously stopped on a given NE, if this latter rebe-
comes reachable while the NM Operator is working on the simulator, and hence on the local MIB, the oper-
ator is aware of this by the clearing of the Q3 isolation alarm, which is visible on both AS and USM. If,
on the other hand, the supervision was previously stopped for that NE, the operator can check about the
reachability of the NE by the OSI ping functionality.
Select the Administration icon >System Management features >Local Data Management >Ping NE
to open the communication test tool window.
The OBS feature is not available at all for DXCs, because the DXC is already redundant with two AUs.
Moreover, OBS is not available for WDM, since not yet managed at NML level.
Finally, it is worth adding a note on the releases of simulators and associated NEs. It could occur that the
release of a given NE simulator is different (lower) than the release of the actual NE. This is possible, and
due to the fact that the NE simulator needs to be aligned with the actual NE as far as the configuration of
the NE is concerned. All the dynamic NE behaviors (e.g. event or alarm reporting, PM collection) are not
relevant for the NE OBS. Therefore, it can happen that during the testing phase, some NE behaviors re-
lated to the dynamic mechanisms of the NE have been corrected, but they did not require a new NE simula-
tor 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
19
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
2.3.1 Equipment boards replacement procedures without affecting the service
The Equipment boards replacement have to be performed following specific procedures written taking
in account the NR and the board type. The operator can refer to the network integration of existing docu-
ments.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
20
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
2.3.2 Procedure to perform an offline configuration
The offline configuration procedure applies to RM and NM operators to act on the configuration of one
Q3 NE even if the latter not yet currently reachable (because not yet installed). This feature offers to the
network administrator the possibility to preconfigure the network, starting creating the network topology
and even transmission configuration even before the network actually exists (predeployment phase).
Hence this feature applies only once in the network lifetime.
In order to start the offline configuration, the NM operator shall startup the onboard simulator as soon
as RM has to retrieve ports from that NE. NM operator shall configure the NE in terms of equipment config-
uration (boards, etc.). Then the RM can upload the ports from the simulator according to the configuration
entered by NM operator. Once aware of the NE equipment configuration, RM works locally configuring the
NEs RM MIB in download disable mode. During the network configuration done by RM, the simulators on
NM shall remain stopped. The network population offline procedure is:
1 ) Open the NM PNM window and create the NEs on the Map View in the Declared Supervision
State
2 ) Select, on NM PNM, the NE and open the USM. Select the Start Simulator option from the
Supervision menu.
3 ) Configure the NE equipment and the NE synchronization sources
4 ) On 1354RM, enable the NE NM MIB uploading to upload the NE Simulator ports
5 ) On 1354RM, disable the NE NM MIB uploading. The 1354RM will work with its internal NEs RM
MIB
6 ) Stop the NM onboard simulator and restart from step 2 ) up to consider all the NEs involved
in the network configuration
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
21
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
As soon as the actual NE will become reachable, two possible policies are implemented:
a ) The NM operator shall download the NE NM MIB onto the actual NE, in order to instruct it about equip-
ment configuration, and then the consistency download from RM will be performed directly with the
NE in order to download the RM related configuration information. Once downloaded the image
stored in NM, the configuration can be activated in the NE even if not complete (it does not include
the configuration performed by RM). This operation affects traffic, if the network already carries traf-
fic. Normally it is not a problem since the NE is new and it does not carry any traffic. The procedure
is:
1 ) On NM, open the PNM window and change the NE Supervision State in Supervision for all
the reachable NEs.
2 ) Open the USM window and select the Align down option from the Supervision menu. Repeat
the operation for all the NEs involved in the network configuration.
3 ) On 1354RM enable the NEs RM MIB downloading mode to manage the NEs transmission net-
work.
b ) The simulator is activated on NM. RM performs a consistency download, actually working on the on
board simulator, and hence on the NE NM MIB. The NE NM MIB is Aligned down onto the real NE,
which will be then automatically aligned with both NM and RM. The RM is working in disable down-
loading mode and the NM simulator has been stopped. The following procedure has to be applied
to any NE taken over by NMRM management system.
1 ) On NM open the PNM window and change the NE Supervision state in Supervision
2 ) Open the NE USM window and select the Align Up option from the Supervision>Simulator
menu
3 ) On NM open the PNM window and change the NE Supervision state in Declared
4 ) Open the NE USM window and select the Start option from the Supervision>Simulator menu
to start up the onboard simulator
5 ) On RM enable the NE NM MIB uploading to upload the SDH and PDH ports.
6 ) On RM in disable downloading mode, execute a mark audit and verify that the list of misaligned
objects does not concern the equipment and synchronization configuration.
7 ) On NM open the PNM window and change the NE Supervision State in Supervision to manage
the NE configuration.
8 ) On RM enable the NE downloading to manage the NE paths.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
22
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
2.4 RM behavior with respect to the MIBless architecture
1354RM product reflects in its internal behavior the new NR5 MIBless architecture of NM management
platform. Actually, this is rather an internal issue and does not impact the procedures for managing the
network at Network Management Level.
The MIBless architecture of NM does not have any impact on the type and amount of data managed by
RM. RM is the manager of the transmission network, and contains in its internal database all the informa-
tion related to the transmission network only. RM is not aware of the Equipment configuration of a NE, and
not even of the synchronization or networking configuration of a given NE.
On the other hand, the passthrough role of NM implies that RM system sends commands directly to NEs,
and their actual reachability becomes an important parameter for RM. In case of command to be sent to
an unreachable NE, the RM stores the relevant commands internally, and automatically resends them
as soon as the NE rebecomes reachable. But this has no impact on the operators view of the manage-
ment. If the NE is not currently reachable, the path cannot be implemented anyway. The difference is
based on internal mechanisms: for QB3* NEs, the NM will send the command for the path implementation
to the newly reachable NE, while for Q3 NEs, the RM does.
Since RM keeps on having its internal database mirroring the Network configuration, there is the need to
maintain the RM database synchronized with the actual Network Element MIB.
RM is now responsible for guaranteeing that there is no misalignment about configuration information. An
efficient mechanism has been setup in order to allow RM to immediately identify whether there could be
misalignment with a given NE. In such a case, the RM operator is informed, and he/she can react by audit-
ing the misalignment and eventually forcing the RM configuration information into the NE.
As for NR3, the RM operator is able to specify whether he wants to really act on the network element config-
uration (download enabled mode) or just work on the RM database (download disabled mode). If the
download disable mode is entered by RM operator, the RM operator can still work configuring its network,
but configuration commands are not sent to NEs for modification change, but just stored internally for later
appliance or for crosscheck with actual NE configuration.
The RM system enters the downloaddisabled mode status as soon as either of the following events oc-
curs:
A given NE is not reachable by RM for any reason (DCN failure, NE failure, NM restart, etc).
Once the NE is reachable again, the RM automatically downloads towards it the locally stored
configuration changes.
The NM operator has granted the access to the CT operator into a given NE. Once the NE is
reachable again, the RM system informs the operator about possible inconsistencies, but no
automatic download is performed towards the involved NE. It is up to the operator to act and
decide whether to perform an audit or just to force the realignment (download from RM).
The RM operator has asked for download disable to a given NE. Once the operator exits the
download disable status, the RM performs an automatic download towards the 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
23
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
3 OMSN AND ATM BOARD MANAGEMENT
3.1 Introduction
This document describes the procedures associated to the management of the ISA board into OMSN NEs,
in particular focusing at board creation and supervision operations performed through EMLUSM and PNM
applications. This is a guideline document oriented to NM Operators involved in management of ATM
boards, starting from release 5.x, the first one offering the management of ISA boards inside OMSNs.
Basic EML operations, like Create/Remove NE and Start/Stop Supervision, are assumed to be known,
as well as NEspecific operations to be done with the EMLUSM, like Set/Remove Board and IP address
configuration.
Since OMSNs are actually multiservice nodes and the provisioning of different communication services
is achieved via different management entities, from now on the term entities will refer to both the OMSN
NEs and the ATM boards.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
24
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
3.2 OMSNs and ISA board: PNM customization
ISA boards cannot be considered as all the other PDH/SDH boards normally equipped into the NEs, since
they run a SNMP agent interworking with the SNMP EMLIM at NM level, that is supporting parallel man-
agement sessions with respect to Q3 connections established between the Q3 EMLIM and the OMSN
ECs.
Q3
EMLIM
1353NM
ISA
SNMP
EMLIM
OMSN
Equipment
Controller
The peculiar nature of ISA boards and the generic requirement on PNM to support both SDH and ATM
alarm synthesis in the OMSN icon, has lead the design of a PNM customization where all the managed
ISA boards are represented by dedicated icons (in the same way standard NEs are)
In the following, a procedure is described for the configuration of PNM enabling proper ISA management
inside network maps/submaps.
ISA management in PNM needs basically two preliminary operations, to be carried out just once, before
the first ISA board is to be equipped into a given OMSN described into a given Map.
the SDH equipment (one element)
the ATM boards (n elements, as many as the ISA equipped)
As usual, the Operator shall select the NE of interest from the PNM Global Inventory (in this context the
ISA boards are listed into the Global Inventory as standard NEs). The insertion of the SDH OMSN into the
OMSN submap itself is mandatory, otherwise the PNM will not perform a correct behaviour.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
25
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
3.3 Create ISA board
SEQUENCE
a ) Select the NE which houses the ISA board and issue Operations: Create ISA. See following figure.
Figure 9. Operations: Create ISA
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
26
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
b ) The Create ISA dialog box is presented as per Figure 10. You can select the board type (see possible
options on Figure 11. )
Figure 10. Create ISA dialog box
Figure 11. Possible ISA boards
c ) Enter the suitable selections and click on Apply button to confirm. The ISA board is diplayed with an
icon similar to NE icon. The userlabel contains the name of the parent NE and the ISA slot position.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
27
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
3.4 ISA Address
SEQUENCE
Figure 12. ISA: Set Address: NE Address
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
28
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
a ) Assuming that the IPoverOSI tunneling is already correctly configured in the OMSN (it is out of
scope of this procedure description), the Operator can set the IP Address of the ISA boards by select-
ing the menu: Set Addresses: IP Address
Figure 13. Set Addresses: IP Address
When a new board has to be provisioned into the OMSN, the first step is always settinginservice the
board itself via the EMLUSM. The same applies to ISA boards.
The Operator starts the OMSN EMLUSM, selects the slot of interest and, from the Equipment > Set menu
chooses the ATM board type: ATM4x4 in case of a 4x4 ATM matrix, ATM8x8 in case of a 8x8 ATM ma-
trix.
In the reference case an ATM4x4 is provisioned.
Now the Operator shall perform a parallel description of the ISA as NE contained within the OMSN domain
(submap) into the PNM, as it is for all the managed NEs at EML level.
Reminding that Titti submap could in general contain the OMSN itself plus a number of alreadydescribed
ISA boards, the Operator can create the new ISA instance into the PNM by selecting the OMSN icon and
choosing the menu option NE Directory > Create ISA Board, thus opening a new window (see fig.8) into
the PNM.
The User Label of the ISA board is automatically generated as derived from the OMSN User Label, once
Rack/Subrack/Slot coordinates of ISA iteself are inserted by the Operator. Also ISA IP address shall be
inserted (dotted format). No complete Friendly names shall be chosen by the Operator, as per all other
NEs. If no OMSN (namely 1640FOX, 1650SMC or 1660SM) is selected the menu is greyed out.
It is worth noting that the NM Operator shall insert consistent information about ISA coordinates and IP
address between OMSN EMLUSM and PNM, otherwise the NM will not be able to start the supervision
on ISA and manage the ATM services.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
29
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
3.5 OMSN + ISA: Supervision
SEQUENCE
a ) Select the ISA board icon from the map and issue Supervision: No Alignment
Figure 14. Start Supervision on OMSN.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
30
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
3.6 Rename ISA board
As already highlighted, the ISA User Labels must be aligned to the parent OMSN User Label. As a conse-
quence, each time the OMSN friendly name changes, the user labels of slave ISA Boards shall be modified
accordingly.
The supervision shall be stopped on all the NE provided services (Q3 OMSN + all ISAs).
OMSN friendly name is changed according to the normal procedure. Then the Operator shall launch a
new, dedicated tool for ISA label modification, from the menu Operations: Rename ISA.
The Rename ISA Board tool addresses just the OMSNlabel change only, not the change of ISAphysical
coordinates (e.g. slot change into the subrack). If an ISA has to be moved from Slot X to Slot Y, the only
available procedure is first removing the ISA and then recreating it as it is a new board to be setup.
The Operator has the responsibility to update the OMSN label according to what already defined when
performed the Change Q3 Ne name procedure, since no doublechecks are implemented to detect opera-
tors errors.
It is worth noting that the new OMSN name shall be inserted just once, and the tool will automatically up-
grade the labels of all the equipped ISA inside the OMSN.
When the tool starts, the list of all managed Metro OMSNs Friendly Names is shown. Each time a item
in the list is selected, the contained ISA boards are shown in the lower side of the window .
In order to change one of the current OMSN User Labels displayed on the left side of the list, the Operator
shall insert the new user label in the right column (the one displayed in red). Then he can commit the modifi-
cations by clicking on the Apply button
The user may change the name of the ISA board via the menu Operations: Rename ISA
Figure 15. Operations: Rename ISA
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
31
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
3.7 Error Recovery: commands for NM administrators
In case an NM Operator made an error during the ISA Board creation phase (wrong rack e/o subrack e/o
slot position), the NM administrators (axadmin profile) with granted access to the Command Line will be
able to perform a manual renaming of the user label associated to the ISA board.
The command syntax will be provided in the 1353NM Administration Guide.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
32
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
33
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
4 PROCEDURES TO HANDLE TRANSMISSION ALARMS
4.1 Introduction
This technical description provides a highlevel description for procedures to be followed by Operators
to deal with Transmission Alarms with 1353NM product, starting from release 5.x, when supervising Q3
CMISEbased NEs.
The basic reason for these guidelines is that, for CMISE based NEs, transmission alarms do not contribute
to the alarm synthesis shown in the subrack view of the Network Element. Therefore, starting from the
subrack view of a given NE, a new procedure is required to identify immediately where transmission
alarms are.
4.2 Why Transmission alarms are not shown at subrack view?
This section aims at explaining the rationale behind the choice of preventing transmission alarms to be
part of Alarm Synthesis in the NE subrack view.
The new behavior, applying to 2nd generation NEs, based on CMISE management interface, has been
designed according to the principle that the 1353NM, as a product devoted to the maintenance of the
equipment in the network, is not basically involved in the management of the Transmission services pro-
vided by the network, which is a core task of other Network Management Platforms.
Therefore, the 1353NM product shall be designed and optimized in order to help the Operators to identify
immediately the roots of equipment alarms. This will improve the network maintenance process by reduc-
ing reaction times, without being flooded by alarms referred to the Transmission Services, which are the
responsibility of other personnel in the Customers organization.
The subrack view of 2nd generation NEs provides a perboard Alarm Synthesis related to equipment
alarms only. Hence, the Operator can immediately identify which boards currently have some mainte-
nancerelevant alarms.
Nevertheless, the counters on the topleft part of the NE GUI, indicating the total number of active alarms
on the NE, do include the Transmission alarms, in order to provide a global view of the NE alarm status.
Moreover, the new splitting of alarms in alarm domains and associated counters, on the topright part of
the GUI, allows the Operator identifying specifically the number of transmission alarms currently active
on the NE (see Figure 16. ).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
34
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 16. Alarm indication syntheses
4.3 How to identify transmission alarms starting from NE subrack view
As stated, the transmission alarms do not contribute to the alarm synthesis associated to each board of
the NE subrack view. Therefore, a procedure has been setup to allow the Operator to identify where Trans-
mission alarms are, with no need of an unfocused, timeconsuming navigation activity through all the
Views of the GUI before detecting which transmission object has been affected.
The new procedure is actually much more efficient and effective than the previous one, used with QB3*
technology NEs.
A new set of options is present in Figure 17. , under Diagnosis/Alarms menu item .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
35
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 17. Alarm Menu
The Transmission Alarms item allows the operator to open the Alarm Surveillance application (AS), focus-
ing only on the current transmission alarms of that NE, as shown in Figure 18. .
Figure 18. Alarm surveillance window
The Operator can now select the current alarm of interest and, exploiting the ASEMLUSM navigation
capability, moving back to the NE EMLUSM application, now addressing the proper View with respect to
the affected resource.
The AS menu of Figure 19. allows performing the required navigation:
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
36
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 19. AS navigation back to NE EML USM
In this scope, the Operator does not have to navigate throughout the NE configuration, starting from the
subrack view, in order to identify the Transmission alarm: the right view displaying the resource actually
affected by the alarm of interest is immediately available, so that remote diagnostic tasks from the NOC
could be started with no delays. You can look at the following figure and see that the Operator has selected
a LossOfSignal item in the AS and the navigation back to the EMLUSM has automatically poppedup
the Port View associated to the SPI experiencing the LOS.
The procedure to locate Transmission alarms seems strongly improved with respect to previous NM re-
leases and QB3* technology, keeping in the meanwhile the target of a user interface optimized for equip-
ment maintenance activities.
Figure 20. Relationship between AS and Port View of NE EML 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
37
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
4.4 Transmission alarms sublist in AS component.
In case the Operator wishes to pay even more attention to Transmission alarms, thus orienting the
1353NM to be a management system pushed beyond the pure equipment maintenance scope, it is pos-
sible to customize the system by creating an alarm view devoted to transmission alarms only.
Starting from such view, the Operator can again select an alarm, and navigate onto the GUI associated
to that alarm, and again the GUI will be opened on the View where the alarmed resource 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
38
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
39
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
5 ALARM SEVERITY ASSIGNMENT PROFILE CUSTOMIZATION FOR OMSN
5.1 Introduction
The procedure described in this document is a shortterm solution is only available from FIX12 of NR5.0C
PL2.
The operator has to follow the procedure having care in avoiding any human error.
The ASAP (alarm severity assignment profile) is a descriptor which associates the proper severity to the
probable cause of each alarm.
This profile is then associated to the relevant resource.
For more detailed explanation please refer to 1354RM Operators Handbook, Section Maintenance.
5.1.1 Scope
The scope of this procedure is to change the severity of some alarms. In particular, PDH functional blocks
concerned are:
PPI, E* ( E1 or E3 ), P* ( P12 or P3 )
while SDH functional blocks V * ( V12 or V3 ) are not concerned:
In the previous system version releases, 1354RM was associating the standard All Alarms ASAP to the
PDH functional blocks of the SDH paths, while the SDH functional blocks (e.g. VC12) were associated
by 1354RM to the default No Remote Alarms ASAP.
5.1.2 Description and Warnings
The procedure must be executed first on 1354NM, then on 1354RM.
It is mandatory to assign the same ASAP identifiers to the whole network, i.e. to each NE, to
each NM, to each RM of the network.
Since the ASAP identifiers are automatically assigned by 1353NM, it is important to execute the
same identical ASAP creation procedure per each 1353NM
5.1.3 Description of the procedure
The procedure is constituted by the following main steps:
a ) The 1353NM operator, per each NE, creates the new customized ASAP, associating the severity to
the Probable Cause for the involved alarm.
b ) The 1354RM operator associates to each type of PDH port involved, the ASAP identifier previously
created by the NM operator.
The detailed procedures are described in the paragraphs which follow.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
40
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
5.2 Customizing a new ASAP on NMOS
5.2.1 Introduction
This section describes the procedures on NM to provide the ASAP customization required from RM.
The freeuse ASAPs are always created cloning an already existing ASAP: hence, also in freeuse
ASAPs all foreseen (for a certain NE) probableCauses will be always present. Removing or adding proba-
bleCauses is not allowed.
The maximum number of freeuse ASAPs supported in NMOS is product dependent: the free use
ASAPs are 2 for OMSN.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
41
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
5.2.2 ASAP creation Procedure on NM
Select the supervised OMSN NE in the map window view and with Show Equipment command open the
NE EML USM window. Then click on Configuration >Alarms Severities as shown in Figure 22.
Figure 21. Show Equipment pop up menu
Figure 22. Configuring Alarm Severity Assignment Profile.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
42
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 23. opens.
Figure 23. ASAPs Management dialogue box.
Select an ASAP in the List of ASAP field to enable the Clone button. Obviously the operator should
select the ASAP which most matches the required customization, since the customization procedure is
manual in this NM release. click on the Clone button to create the new freeuse ASAPs identifier with the
default number#10001 ( as shown in Figure 24. ). It is important not to change the ASAP Id since the
same shall be used on RM and therefore it is guarantee of coherence among the network.
The user can mark the new ASAP, adding a character string after the identifier (#10001, #10002) as shown
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
43
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 24. ASAP Edition dialogue box example.
The operator can modify the severity associated with each probable cause. Hence, select the Probable
Cause Families: Communication, Equipment, ... whose severity level you want to modify. Then select the
Probable Causes Name and click on the option button: Service Affecting (SA), and then Non Service
Affecting (NSA) and then Service Independent (SI). For each one you can choose the severity value
among Critical, Major, Minor, Warning or Nonalarm. A Nonalarm probable cause corresponds
to no alarm emitted for this probable cause.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
44
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
OMSN do not support the SI severity but the SI severity can be provided selecting, in SA and NSA fields,
the same severity value as indicated in Table 1. and Table 2. case 2 (SI). Usually the NSA default se-
verity is lower than the SA severity ( see Table 1. ) but in general any possible severity customization
assignment can be chosen ( see Table 2. ).
Table 1. Default Assignment of Service Dependency and Severity on OMSN
Case Service Affecting (SA) Non Service Affecting (NSA) Service Independent (SI)
1 major
minor or warning or non-
alarmed
not used
2 ( SI ) major, minor, warning major, minor, warning not used
Table 2. Possible customization Assignment of Service Dependency and Severity on OMSN
Case Service Affecting (SA) Non Service Affecting (NSA) Service Independent (SI)
1
critical or major or minor
or warning or non-alarmed
critical or major or minor
or warning or non-alarmed
not used
2 ( SI )
critical, major, minor,
warning
critical, major, minor,
warning
not used
When you have configured the ASAP, press the OK button to confirm the settings and close the dialogue
box or the Cancel push button to cancel the new settings and close the dialog box. If necessary, repeat
the previous ASAP creation starting from the ASAP clone of Figure 23. The second new ASAP identifier
will begin with #10002 ... as shown in Figure 25.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
45
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 25. Example of Management dialogue box with two customized ASAPs
When the procedure has been completed close the selected NE EML USM and start again from the begin-
ning selecting a new NE from the map view window. Therefore to assign to PDH ports of RMOS the cus-
tomized ASAPs the above same procedure has to be applied to any NE involved in the path communica-
tion circuit.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
46
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
5.3 Customizing a new ASAP on RMOS for PDH ports
5.3.1 Customize the new ASAP
In order to associate a new alarm profile, previously created via NM on all PDH ports of all NEs composing
the whole network, the RM operator has to execute the following procedure:
a ) Shutdown the 1354RM system. From 1354RM Process Monitor window select Actions: Shutdown:
System. Wait...
b ) Exit from CDE session.
c ) Execute login as root user
d ) Edit the following startup script:
/usr/snml/nxnlenv_make
Within this file it is possible to change the ASAP identifier for PDH Ports.
The relevant variables are:
NL_PdhPort_2Mb_ASAP for 2 MB Ports
The commands to be entered are respectively:
export NL_PdhPort_2Mb_ASAP=<ASAP identifier numeric field for 2Mb ports>
where <ASAP identifier numeric field forxxMb ports> is the value previously defined by the NM operator.
The same ASAP id can be associated to several PDH port types.
N.B. The syntax is case sensitive ( Uppercase/Lowercase )
See following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
47
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
ASAP IDENTIFIER 5digit numeric field
Figure 26. ASAP Identifier on ASAP Edition dialogue box
e ) Execute the script customize_patch:
/usr/snml/etc/customize_patch
Exit from CDE session.
f ) Login as snml user
g ) From the Process Monitor window execute Actions: Startup: System. The system starts using the
new environment variables previously defined in file
/usr/snml/nxnlenv_make
N.B. Notice that after each patch installation, it is mandatory to reenter the customize commands
above mentioned on page 46.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
48
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
5.3.2 Error analysis
Once the RM operator implements a PDH circuit, he has to specify whether he wants to enable PDH
alarms. In case he does want, the specified ASAP profile will be used.
If the ASAP required for the PDH circuit has not been preconfigured into the terminating NE, then RM
will display a generic error message, indicating that something went wrong in the implementation of the
circuit.
In this case, the Operator has to check the reason of the failure:
1 ) To verify on NM if the required cloned ASAP is present on path terminating NEs.
2 ) To check on RM using the routing display for the actual implementation of the path (if the error
occurs during the implementation or commissioning of the path)
3 ) To check on RM using the NAP view (if the message error appears upon a request for ASAP
change done during circuit lifetime)
EXAMPLE
a ) The routing display of the path shows that the path implementation state is failed to implement and
that NAP consistency state is failed to align. See following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
49
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
b ) In case the reason for path implementation state= failed to implement is missing ASAP on terminat-
ing NE, the NAP alarm detail will show PDH disabled alarms as cause of misalignment. See figure
which follows.
.
.
PDH Disabled Alarms
4 ) The misalignment is due to the fact that:
a ) at RM level in the /usr/snml/nxnlenv_make file ( see below figure) the ASAP identifier
for 2Mb ports is equal to 7
while
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
50
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
b ) at NM level this ASAP identifier is not existent in the NE for that port. See following figure
Figure 27. ASAP list
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
51
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6 FILE TRANSFER SCHEDULER
6.1 Introduction
The FT Scheduler is an application useful to launch multiple file transfer (SW Download, MIB backup)
between the OS and the NEs providing scheduling & periodic services. In addition, to avoid critical network
load, the FTS allows to plan the DCN loading during the file transfer. Figure 28. shows a DCN network
example.
LAN
Router Router
1 3 2 4
1 2
1353NM
NE 1
5
NE 2 NE 3
6
NE 4
NE 5
NE 6 NE 7
LAN nodes LAN node
Figure 28. DCN network 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
52
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.2 FTS Application
The FTS application can be applied to all NEs supporting File Transfer (SWDL, MIB backup) independent-
ly from the technologies and/or the protocol type. The application masks operational differences so the
operation and result are uniformed for different NE protocol type: QB3*, Q3 and SNMP.
Then the same FTS windows and procedures will be applicable for different NE types.
6.3 Functionality
The main features offered by the FT Scheduler are:
scheduling of SWDL jobs;
scheduling of MIB backup jobs;
periodic scheduling of MIB backup Jobs;
Job (SWDL or MIB backup) progress monitoring;
NE SW status retrieving in single or multiple form;
NE SW management;
NE SW status data export;
operation and result logging.
SWDL and MIB backup functionality are offered working simultaneously on a set of NEs.
6.4 Operational scenario
The managed file transfers are:
SW Download (scheduling services);
MIB backup ( scheduling and periodic services)
File Transfer operations are based on the application task named Job. A Job is defined by a Descriptor
File, that contains the list of the target NEs and all the parameters related to the action to be scheduled
(SWDL or MIB Backup).
The Job activation time may be immediate or programmed. In addition, MIB Backup Jobs may be periodi-
cally reactivated every 24 hours.
The SW management function allows managing SW versions loaded on the NE. The allowed SW Manage-
ment commands set depends from the NE SW status and from the functionality supported by the target
NE. SW management is allowed on a single NE at a time and its not scheduled, i.e. commands are imme-
diately sent to the target NE.
The FTS application allows to retrieve the list of the SW version loaded on all the NEs, with the associated
status. The NEs SW version may be retrieved on single NE or on a set of NEs. Some filters are available
to select subset of NEs. When the SW status is retrieved on a set of NEs is possible to save the result in
an exportable file (ASCII format), useful for external analysis.
N.B. MIB backup operation may be implemented differently for different NE types: may be MIB align
up or MIB backup. This document and the FTS, use the operation name MIB backup.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
53
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.5 Job Planning
The FTS Scheduling function is based on the information contained into the Job descriptor file. The Job
is composed by different sessions, each of one containing a set of NEs ( see the File Transfer Scheduler
chapter of the1353NM Operators Handbook) .
The same job allows having a priority levels approach in the FTS operation. All the NEs pertaining to a
session are Downloaded / Backedup before the NEs of the next session: the job will start from the
first NE of the first session and will go on, respecting the order of sessions and in each session the order
of NEs. This permits to control the DCN traffic in the network, then the global FT phase can be organized
in order to avoid overloading some specific GNEs or DCN links.
Taking in account the network shown in Figure 28. : for having a good balanced DCN traffic load each LAN
node divides the network into two links, each of one will support, in both sides, quite the same NE number.
The FTS application emphasizes the possibility to maintain a reduced DCN load dividing the file transfer
load time by sessions.
The application launches, for each session, the maximum number of simultaneous file transfer allowed
(<=10 for each involved NM LAN: then the maximum simultaneous file transfer, inside a session, is 10
multiply by the number of involved LAN ). When one session terminates, the application launches the next
defined session.
The maximum NE number for any session is 90 but there is no limit regarding the maximum session num-
ber in a job.
The DCN traffic load affects the NEs and the network branches involved in the OSNE communication
Considering any NE load equivalent to 1 , charging any DCN branch with a balanced load, it can be
suggested the following job planning rule:
Distribute the DCN traffic dividing the global traffic load of each branch through different
sessions trying to reduce the session numbers : in each session the same network branch will
be passed through by the traffic the minimum number of times.
In a real DCN network, each session will contain NEs belonging to different LANs and the optimum traffic
load for branches will take in account the network communication capacity and the file transfer traffic be-
tween NM and tens / hundred of NEs.
The DCN examples, here reported, concern elementary networks with a single LAN and a few NEs. The
procedures show how to divide the total DCN traffic without exceeding the suggested optimum traffic load
for branches.
Let us assume, in the examples that follow, the optimum DCN traffic load for branch <=1.
Higher is the LAN load, lower will be the session numbers.
We can reduce the session numbers increasing the LAN load value but the traffic load for branches will
be increased too (see para. 6.12 ).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
54
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Level 1=3
Level 2=2
Level 3=1
1353NM
Figure 29. Balancing the DCN traffic load
In the example of Figure 29. have been represented the link connection between NM and each NE types:
the traffic in the branch NM NE1 has been balanced with the traffic in the branch NM NE4 but these
branches, in each session, are passed through by the traffic two times and the suggested planning rule
has been disappointed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
55
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
LAN
Router Router
1 3 2 4
1 2
1353NM
NE 1
5
NE 2 NE 3
6
NE 4
NE 5
NE 6 NE 7
Level 1 =4
Level 2
Level 3
Level 4
1 1 1
1
1
1 1
1
1
1
1
1
Level 3
1
Figure 30. Optimizing the load traffic for session
In the example of Figure 30. ,following the suggested planning rule, has been considered a LAN load <=4
and the job has been divided in the following sessions:
First session: GNE1, GNE2, GNE3 and GNE4
Second session: NE1, NE2, NE4 and NE6
Third session: GNE5, NE3, NE5 and NE7
Fourth session: GNE6
The link load will be:
Table 3. Link load of level 1 ( example of Figure 30. )
Branch Session 1
link load
Session 2
link load
Session 3
link load
Session 4
link load
Lan load = 4 4 4 1
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
56
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Table 4. Link load of level 2 ( example of Figure 30. )
Branch Session 1
link load
Session 2
link load
Session 3
link load
Session 4
link load
Router 1GNE1= 1 1 1 1
Router 1GNE2=
1 1 1 0
Router 2GNE3=
1 1 1 0
Router 2GNE4=
1 1 1 0
The traffic load, in any branch of each session, is <=1 ( Table 4. ) as suggested in the planning rule.
Table 5. Link load of level 3 (example of Figure 30. )
Branch Session 1
link load
Session 2
link load
Session 3
link load
Session 4
link load
GNE1NE1 = 0 1 0 0
GNE2NE2 = 0 1 0 0
GNE3NE4= 0 1 0 0
GNE4NE6= 0 1 0 0
GNE1GNE5= 0 0 1 1
GNE2NE3= 0 0 1 0
GNE3NE5= 0 0 1 0
GNE4NE7= 0 0 1 0
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
57
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Branch Session 1
link load
Session 2
link load
Session 3
link load
Session 4
link load
GNE5GNE6 = 0 0 0 1
As before the traffic load, reported on Table 5. and Table 6. , in any branch of each session, is <=1
The traffic load has been represented dividing the DCN network with different network levels. In
Figure 30. the DCN has been divided into 4 levels and the load, in any branch of each session, is minimum
( <=1). With a higher LAN load it is possible to reduce the session numbers but we can not minimize the
traffic load in any branch of each session (see appendix A).
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
58
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.6 Job Editor
The job planning of Figure 30. is built through the job editor of Figure 31. : the generic NEs have been
substituted by the real ones.
Figure 31. Job editor 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
59
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.7 Job Scheduling
A defined job may be executed at the submitted time (option Now) or at programmed time (option At
Time), in addition, only for MIB backup, can be also chosen At Time with a Periodic Job parameter
that allows an automatic MIB backup job activation every 24 hours (see Figure 32. ).
Figure 32. MIB backup job 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
60
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 33. Misalignment Flag in the backup job
Moreover in the MIB backup Scheduler editor, the user can select, for each NE, the Misalignment flag
(see Figure 33. ). This flag allows to load (or reload) the MIB backup file only when the MIB misalignment
alarm has been recognized, avoiding unnecessary MIB backup operation.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
61
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.8 Job Monitoring
During the job running the job status can be checked by the job in progress window (see Figure 34. ).
Figure 34. Job in progress status example
The colors icons identify the job status:
grey: Waiting start
orange: Activated
green: Finished operation with Success
red: Finished operation with Errors
red with a crossed sign: Aborted operation
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
62
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.9 Job Report
Moreover the FTS application allows programming a SWDL / Backup job not obliging the NM operator
to be present (and awake) during the operation (overnight). A log report is provided to verify how the job
operation worked out (see Figure 35. ).
Figure 35. SWDL job report 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
63
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.10 NE SW Status Visualization
The FTS allows checking the SW releases currently loaded on the NEs, the running one (active) and the
ones stored in the spare bank of the memory. This operation is possible on a single NE ( menu option:
Selected by name ), or on a predefined set of NEs of a given type ( menu option: Select by NE Type ),
or globally on all the managed NEs ( menu option: All NEs ).
Figure 36. NEs software status table example
The information is retrieved directly from the NEs so that it reflects the current status of the network. The
NE SW Status table, used to show SW Status for a set of NEs, allows to export values in a file for the exter-
nal analysis.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
64
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.11 NE SW Management
A new software package downloaded is stored in the NE standby bank: the activation can be performed
in a second time. The same Figure 37. can be opened with a double click on the selected NE of the soft-
ware status list or selecting the Select By Name option from SW Status pull down menu.
Figure 37. Action on NE software package memory banks
NE SW Detail window shows the status of the data loaded in each memory bank of the NE and the allowed
SW Management operation (actions).
The SW Management actions that can be performed on the NE are:
None: no action,
Activate: to activate the selected software package on the NE,
Force: to force the selected software package activation on the NE,
Commit: to commit the software package activated on the NE
Delete: to delete the selected software package on the NE
Duplicate: to duplicate the selected software package on the NE
The SW Management Action list shows the allowed operation depending from the NE SW Status.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
65
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
6.12 Appendix A
Consider the same DCN network of Figure 30. but with a LAN load <=7 : the job could be divided in the
following sessions:
First session: GNE1, GNE2, GNE3, GNE4, GNE5 and GNE6
Second session: NE1, NE2, NE3, NE4, NE5, NE6 and NE7
Branch Session 1 Session 2
Lan load 6 7
Router 1GNE1= 3 1
Router 1GNE2= 1 2
Router 2GNE3=
1 2
Router 2GNE4=
1 2
The traffic load, in many branches is >1 (Router1GNE1 of Session1 is =3). That could cause an over-
loading of the DCN traffic.
GNE1NE1= 0 1
GNE2NE2= 0 1
GNE3NE4= 0 1
GNE4NE6= 0 1
GNE1GNE5= 2 0
GNE2NE3= 0 1
GNE3NE5= 0 1
GNE4NE7 0 1
As before the traffic load, reported on Table 9. in branch GNE1GNE5 of Session1 , is >1.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
66
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
GNE5GNE6 1 0
Therefore this second job planning does not optimize the network traffic load.
The distribution traffic load, at different network levels, has been visualized in Figure 38.
LAN
Router Router
1 3 2 4
1 2
1353NM
NE 1
5
NE 2 NE 3
6
NE 4
NE 5
NE 6 NE 7
Level 1 =7
Level 2
Level 3
Level 4
3 2 2
2
1
2 1
1
1
1
1
1
Level 3
1
Figure 38. Example of DCN traffic increasing the LAN load
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
67
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
7 OBJECT ASSIGNMENT DOMAIN
SEQUENCE
a ) Click on icon 1353NM Admin. The System Management Tools box is displayed.
b ) From the System Management Tools box select SEC Administration.
c ) Select SEC USM Browser
d ) Select OAD: Object and click on Create Object button. see below figure.
e ) Enter name (e.g. ROSSO), family (e.g. Access control Domain), System Id ( string or FDN ) and click
on Apply button. The new OAD is now present. See Figure 40.
OAD
Object
Create
name
ACD
Figure 39. OAD: Object: Create
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
68
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
NEW OAD
Figure 40. new OAD object
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
69
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
f ) Point with the mouse to Elementary OAD and issue the popup menu Create new Elementary OAD.
The same menu option is present in the popup menu of an existing Elementary OAD
Figure 41. Elementary OAD: Create
g ) Enter the Elementary OAD name and move to the right subbox the objects to assign. Click on Apply
button to confirm.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
70
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
h ) Select the Operator profile to which you want to assign the Elementary OAD and click on Edit Opera-
tor profile. See following figure.
OPTION BUTTONS
LEFT BOX RIGHT BOX
Figure 42. Edit Operator profile
In the Edit dialog box select option button Elementary OAD ( deselecting the other buttons ) and from the
left selection box select the Elementary OAD to add and include it ( e.g. rossino) by pressing the right
arrow. Click on Apply to confirm.
Now all operators with profile=Viewer contain the Elementary OAD rossino
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
71
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
Figure 43. Elementary OAD and ACD of the Viewer Profile
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
72
02

SC.6: PROCEDURES

/ 3AL 89061 AA AA

72
72
i ) Restart LSS process to render effective the change
EXAMPLE
An operator with profile=admin and Elementary OAD=rossino and ACD=ROSSO, when creating a new
NE will be able to select ACD=ROSSO to include or not the management of the new NE. See following
figure.
Figure 44. Create NE
END OF DOCUMENT
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
1
02

SC.7:OA512 MANAGEMENT

/ 3AL 89061 AA AA

28
28


TABLE OF CONTENTS
1 GENERALITIES 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 OmniAccess 512 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 References 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 OA512 Integration in 1353NM 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Preconditions for the Integration of OA512 in 1353NM 3 . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 1353NM activation 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 OA512 INTEGRATION 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 OA512 EmlDomain 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 1353NM registration on OA512 System 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Configuring trap management 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 OA512 MANAGEMENT 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 OA152 Network Element Creation 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Security 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 OA512 Network Element Supervision 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Navigation from 1353NM Topology Management to OA512 USM 18 . . . . . . . . . . . . . . . . . .
3.5 Ping NE 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 ALARM MANAGEMENT 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Navigation from AS to OA512 USM 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Navigation from Topology Management to AS USM 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
01A 040720

02 040728 SC04091002
M.BERTONI M.ARMANINI
050623 03 SC04091002
1353NM REL.7.0 OA512

USER GUIDE

A.CORTESE L.FORESTA

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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
2
02


/ 3AL 89061 AA AA

28
28
FIGURES
Figure 1. Alcatel CDE Front Panel 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. TMN OS application 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. System Configuration window 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. EMLIMSGM Configuration 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. OA512 Coonfiguration 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Topology Manager 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. 1353NM Create Network Element 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. OA152 NE Creation 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. NE Set Address 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. OA512 Set Address 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. NE Supervision 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Start Supervision 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. NE Show Equipment 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. OA512 User Interface 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Ping NE result 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Main Alarm List 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. AS Administration Selection 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Probable Cause List Selection 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. AS Administration 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Navigation to OA512 USM 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. OA512 USM 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Navigation to AS USM 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. OA512 Alarms Sublist 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLES
Table 1. Handbooks related to Omni Access 512 management 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. OA512 Traps management 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. Trap Mask Calculation 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
3
02


/ 3AL 89061 AA AA

28
28
1 GENERALITIES
1.1 OmniAccess 512
The OmniAccess 512 (OA512) family is a group of stackable switches that offers multiservice access to
an enterprise (WAN) backbone. Designed to connect branch offices to the main office Frame Relay net-
work, this switch combines LAN switching, WAN routing and Service Level MAnagement in a single plat-
form.
The OA512 supports up to two widearea uplinks. Userinstallabel USP, T1/E1 and ISDN submodules
provide flexibility. Support of frame relay, leased lines and ISDN offers a broad range of solutions for con-
necting an enterprise branch office.
1.2 References
Table 1. Handbooks related to Omni Access 512 management
REF HANDBOOK Part No.
[1]
OMNI ACCESS 512
User Manual Release 4.3
03070210 Rev.B
1.3 OA512 Integration in 1353NM
1353NM integrates OA512, it is managed as a Network Element.
Operations carried out by 1353NM on OA512 are :
Create OA512 NE starting from PNM;
Start/Stop Supervision of OA512;
Show Equipment;
Alarm management.
1.4 Preconditions for the Integration of OA512 in 1353NM
This paragraph lists some conditions to allow the integration of OA512 in 1353NM Subsystem.
If a global installation is performed, OA512 application is automatically installed, but with partial sys-
tem installation a selection should be done to install OA512 application.
1353NM Subsystem must be registered on OA512 equipment in order to enable proper operations.
The relevant procedure is explained in a dedicated paragraph.
Alarm/Trap management:configuration description of the managed traps and the operations to en-
able the management on 1353NM is explained in a dedicated paragraph.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
4
02


/ 3AL 89061 AA AA

28
28
1.5 1353NM activation
TMN OS is the graphical interface of OSKernel application dedicated to manage the different Subsystem
Instances built on the same hardware machine.
TMN OS application is the box containing and managing all the NM Subsystems customized on a single
physical machine.
TMN OS Icon
Figure 1. Alcatel CDE Front Panel
Select TMN OS icon as shown in the previous figure to start TMN OS application. The TMNOS Manage-
ment Window will be shown in a few seconds, you have to select the 1353NM instance you want to man-
age.
Figure 2. TMN OS 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
5
02


/ 3AL 89061 AA AA

28
28
2 OA512 INTEGRATION
This chapter explains the integration steps to be done in order to manage OA512 starting from 1353NM.
These operations should be done before activating any 1353NM function towards OA512.
2.1 OA512 EmlDomain
OA512 are supervised by 1353NM Subsystem through SGM (Snmp Generic Mapper) component. This
application allows to manage System using SNMP protocol in a generic way. During System Configuration
phase, this application gets an identification number (emilm id). To get this information which is useful for
some operations explained in following paragraphs, select from TMNOS menu OS > SystemConfig,
following window will be displayed
EMLIMSGM ID
Figure 3. System Configuration window
During System Configuration the UDP port number is assigned to EMLIMSGM. This port number should
be greater than 1024 and the operator should take care to assign different port number for different config-
ured emlims. Selecting on the right side of the SystemConfig window EMLIMSGM_xxx, the following win-
dow will be displayed
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
6
02


/ 3AL 89061 AA AA

28
28
Figure 4. EMLIMSGM Configuration
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
7
02


/ 3AL 89061 AA AA

28
28
2.2 1353NM registration on OA512 System
OA512 should know 1353NM Subsystem in order to be managed by it, the identification of NM on
OA512 System is achieved by the IP address. To define the 1353NM IP address on OA512 follow these
steps (only for Administrators profile):
open an UX terminal on 1353NM Workstation;
execute the command : telnet <OA512 IP address>;
insert OA512 administrator login and password to be logged into the device;
type the command snmpc, the configuration will be displayed as shown in following figure;
Figure 5. OA512 Coonfiguration
in order to set 1353NM IP address, insert a line n=xxx.yyy.zzz.aaa where n is the number follwing
the last of the list, xxx.yyy.zzz.aaa is 1353NM IP address; for IP addresses the numbers go from 7
to 16.
the next two prompts ask to insert word 0:1 and word 2:3 for trap configuring, the value to insert are
explained in following paragraph;
the last prompt asks for UDP port number, the UDP port configured for receiving trap; this value is
the value assigned during system configuration procedure and should be read from the window
shown in Figure 4. . This information is reachable starting from SystemConfig 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
8
02


/ 3AL 89061 AA AA

28
28
2.3 Configuring trap management
As explained in previous paragraph, trap management can be configured to receive only a subset of the
possible traps. The subset manged by 1353NM is shown in the folowing table.
Trap Object ID Description Bit
Position
Hex Value
coldStart 1.3.6.1.2.1.11.0 The sending protocol entity is re
initializing itself such that the
agents configuration or the proto-
col entity implementation may be
altered
(word 0) 0 (word 0) 1
warmStart 1.3.6.1.2.1.11.1 The sending protocol entity is re
initializing itself such that neithr the
agents configuration nor the proto-
col entity implementation may be
altered
(word 0) 1 (word 0) 2
tempAlarm 1.3.6.1.4.1.800.
3.1.1.4.0.1
The temperature sensor have de-
tected a temperature in the chassis
that exceeds the threshold. These
sensors are physically located on
the MPM module, but can detect
temperature changes throughout
the chassis.
(word 1) 0 (word 1) 1
portLinkUpEvent 1.3.6.1.4.1.800.
3.1.1.4.0.8
A physical, logical, or virtual port
was enabled. These ports may be
enabled through the UI or Switch
Manager. Note that if you enable a
physical port, any associated log-
ical and virtual ports will also be en-
abled. And if you enable a logical
port, such as a WAN service, asso-
ciated virtual ports will be enabled.
(word 1) 7 (word 1) 80
portLinkDownEvent 1.3.6.1.4.1.800.
3.1.1.4.0.9
A physical, logical, or virtual port
was disabled. These ports may be
disabled through the UI or Switch
Manager. Note that if you disable a
physical port, any associated log-
ical and virtual ports will also be
disabled. And if you disable a log-
ical port, such as a WAN service,
associated virtual ports will be dis-
abled.
(word 1) 8 (word 1) 100
portPartitioned 1.3.6.1.4.1.800.
3.1.1.4.0.10
The physical port detected jabber.
Jabber may be produced by a bad
port connection, such as a faulty
cable.
(word 1) 9 (word 1) 200
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
9
02


/ 3AL 89061 AA AA

28
28
Table 2. OA512 Traps management
The trap are configured in four words (128 bits). The first word (Word 0) contains only standard traps as
they are defined within RFC (MIB) documents. Words 1,2 and 3 contain Alcatelspecific traps. To set these
traps a sum should be made of the values corresponding to the selected traps.
The trap mask to enter during the configuration on OA512 is to calculate as follows :
The mask value ffffffff:ffffffff indicates that all traps are enabled for words 0 and 1. Pressing <enter> this
value is accepted, you have instead to enter follwing value :
Trap Type Bit Settings
Word 0 Word 1
coldStart 00 00 00 01 : 00 00 00 00
warmStart 00 00 00 02 : 00 00 00 00
tempAlarm 00 00 00 00 : 00 00 00 01
portLinkUpEvent 00 00 00 00 : 00 00 00 80
portLinkDownEvent 00 00 00 00 : 00 00 01 00
portParitioned 00 00 00 00 : 00 00 02 00
Total = 00 00 00 03 : 00 00 03 81
Table 3. Trap Mask Calculation
The value calculated is the value to insert for the trap mask in the configuration explained in previous para-
graph.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
10
02


/ 3AL 89061 AA AA

28
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
11
02


/ 3AL 89061 AA AA

28
28
3 OA512 MANAGEMENT
3.1 OA152 Network Element Creation
In order to manage OA512 System from 1353NM a new Network Element should be created. The cre-
ation of the new Network Element starts from Topology Managent (PNM) application, to open the applica-
tion select from TMNOS menu Actions | > Topology Manager or pressing the icon
Figure 6. Topology Manager
The map management window will be displayed with the last saved map. OA512 can be created in a new
map or in an alredy existent map. To create the Network Element select from the menu Declaration >
Create > NE ... as shown in following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
12
02


/ 3AL 89061 AA AA

28
28
Figure 7. 1353NM Create Network Element
The above selection will display the NE Creation window where the new Network Element data should be
inserted.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
13
02


/ 3AL 89061 AA AA

28
28
Figure 8. OA152 NE Creation
Network Element data to insert for the OA512 NE creation are :
Family : NE family OmniAccess
Type : NE type OA512
Release : NE release 1.0
User Label : User Label for the Network Element
Location Name : where the NE is positioned
Supervision Area : select the lan where the NE is connected
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
14
02


/ 3AL 89061 AA AA

28
28
EML domain : select from the list the domain corresponding to the emlim managing OA512. The
emlim managing OA512 is EMLIMSGM. The information about the domain can be found in the Sys-
tem Configuration window.
Click on the Apply button to confirm the Network Element creation, the click on the Close button to close
this window.
After the NE creation, the OA512 IP address should be assigned to the new Network Element. To set the
NE address select Declarations > Set Addresses > NE Address... from the Topology Management
menu as shown in following figure.
Figure 9. NE Set Address
After the selection a dialog box to insert the IP address is displayed, as shown hereafter
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
15
02


/ 3AL 89061 AA AA

28
28
Figure 10. OA512 Set Address
After this operation, the Network Element creation is completed.
3.2 Security
Security is not managed by 1353NM for OA512. This means basically that users of any profile are enabled
to open the OA512 specific application and perform all available operations on the switch.
3.3 OA512 Network Element Supervision
After the creation, a Network Element should be supervised by 1353NM Subsystem in order to be man-
aged by the Network Management system. Select from menu Operations > Supervision > No Align-
ment.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
16
02


/ 3AL 89061 AA AA

28
28
Figure 11. NE Supervision
To start the supervision click on the button Apply and wait for the operation to finish, then click on the button
Close to exit.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
17
02


/ 3AL 89061 AA AA

28
28
Figure 12. Start 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
18
02


/ 3AL 89061 AA AA

28
28
3.4 Navigation from 1353NM Topology Management to OA512 USM
Once OA512 is supervised, navigation to the native OA512 management application (XVision) is allowed
selecting from the popup menu the Show Equipment option.
Figure 13. NE Show Equipment
This operation opens OA512 user interface as shown in following figure.
Figure 14. OA512 User 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
19
02


/ 3AL 89061 AA AA

28
28
For details on OA512 see OmniAccess 512 User Manual.
The contents and set of operations available with XVision are not part of the present manual. Please refer
to [2] for a detailed description of the application.
3.5 Ping NE
A useful function to test the OA512 NE reachability from 1353NM is the Ping NE function. Select the
OA512 NE on the map, select from the menu Operations > Ping NE. The operations result will be dis-
played after a few seconds as shown in following figure.
Figure 15. Ping NE result
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
20
02


/ 3AL 89061 AA AA

28
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
21
02


/ 3AL 89061 AA AA

28
28
4 ALARM MANAGEMENT
Alarms are managed by a generic component called AS (Alarm Surveillance) integrated in the common
platform OSKernel and can be activated from TMNOS menu. For OA512 a subsystem of traps is man-
aged and can be see using AS USM. Starting from TMNOS menu the main AS USM window is displayed
as shown in following figure. This list contains all the alarms received.
Figure 16. Main Alarm List
OA512 managed alarms are shown by AS in realtime. To allow realtime management a particular
alarm OA512 New Event is used which is suggested to be configured for autopurging from AS adminis-
tration facilities. The autopurge action is associated to the OA512 New Event Probable Cause. The alarm
is not registarted in the Current Alarm List, but in the Historical Alarm List.
The autopurge action is configurable with AS component. Selecting from the summary alarm window Op-
tions > Administration > 1353NM_<Inst_numb> as shown in following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
22
02


/ 3AL 89061 AA AA

28
28
Figure 17. AS Administration Selection
The administration window is displayed. To activate the autopurge action on the Probable Cause OA512
New Event, select the button near Probable Cause and select the string from the displayed list, as shown
in following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
23
02


/ 3AL 89061 AA AA

28
28
Figure 18. Probable Cause List Selection
Select the Probable Cause on the left list and then press the arrow button to take it on the Selected Prob-
able Causes list. Use the OK button to confirm the selection.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
24
02


/ 3AL 89061 AA AA

28
28
Figure 19. AS Administration
The selection is stored in the main administration window, to confirm the option press the Apply 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
25
02


/ 3AL 89061 AA AA

28
28
4.1 Navigation from AS to OA512 USM
Starting from the main alarm list window it is possible to navigate to OA512 USM selecting Navigation >
External Appliaction > Related EmlUsm. Each time a navigation is selected a new OA512 USM window
will be opened.
Figure 20. Navigation to OA512 USM
Selecting the above navigation the OA512 USM is displayed.
Figure 21. OA512 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
26
02


/ 3AL 89061 AA AA

28
28
4.2 Navigation from Topology Management to AS USM
On the other side its possible to navigate from Topology Management, selecting OA512 Network Element,
to AS USM displaying the alarms sublist concerning OA512 alarms.
Figure 22. Navigation to AS USM
Selecting the option Show alarms the list of OA512 alarms will be displayed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
27
02


/ 3AL 89061 AA AA

28
28
Figure 23. OA512 Alarms Sublist
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
28
02


/ 3AL 89061 AA AA

28
28
END OF DOCUMENT
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
1
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37


TABLE OF CONTENTS
1 PRODUCT OVERVIEW 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 SAN Extender 169xSE 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 References 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 SAN Extender 169xSE Integration in 1353NM 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Preconditions for the Integration of 169xSE in 1353NM 5 . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Installation of 169xSE Client Application 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.1 Installation Requirements 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2 Installing the Server 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.3 Installing the Client. 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Customizing the NMSE Server 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1 Registering NMSE in the NM Framework 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2 Defining Users 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.3 Registering Network Elements in the NM Framework 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.4 Registering Network Elements in NMSE 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.5 Adding Switches to the Servers List 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 Managing the Database 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8 1353NM activation 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 169XSE INTEGRATION 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Steps sequence to manage 169xSE NEs 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 169xSE EmlDomain Configuration 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 169XSE SAN EXTENDER MANAGEMENT 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 169xSE Network Element Creation 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Security 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 169xSE Network Element Supervision 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Navigation from 1353NM Topology Management to USM 25 . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Navigation to SANman application 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Ping NE 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 ALARM MANAGEMENT 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Navigation from AS to 169xSE USM 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Navigation from Topology Management to AS USM 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
01A 040720

02 040728 SC04091002
050510 03 SC04091002
1353NM REL.7.0 1353NMSE

USER GUIDE

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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
2
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 1. NMSE in TMN Architecture 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Remote SAN interconnection 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 1. Handbooks related to 169xSE management 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. Suggested configuration for the Client PC 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Install Wizard Mode Selection Screen 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Server Main Window 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. The Add Switch Window 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Advanced Options for Adding Switches 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Options Window, Statistic Tab 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Alcatel CDE Front Panel 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. TMN OS application 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. System Configuration window 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. EMLIMSGM Configuration 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Configuration data confirmation 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Topology Manager 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. 1353NM Create Network Element 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. 169xSE NE Creation 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. NE Set Address 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. 169xSE Set Address 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. NE Supervision 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Start Supervision 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. NE Show Equipment 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. 169xSE USM 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Open SANman application from TMNOS selecting icon 27 . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Open SANman application from TMNOS selecting menu Actions 27 . . . . . . . . . . . . . . . . .
Figure 24. User Interface 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Ping NE result 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Main Alarm List 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. AS Administration Selection 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. AS Administration Window 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Navigation to SANman application 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. 1353NMSE Alarms List 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Navigation to AS USM 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. 169xSE Alarms Sublist 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
3
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
1 PRODUCT OVERVIEW
1.1 SAN Extender 169xSE
1693SE and 1696SE are high performance gateway that interconnects SAN islands using readily avail-
able fiber optic infrastructure such as SONET, DWDM or dedicated fiber.
169xSE refers to two different products in Alcatel catalogue:
1693SE
1696SE
1693 SAN Extender is a switching gateway providing seamless bidirectional integration of Fibre Channel
(FC) and Gigabit Ethernet (GbE) networks over long distances without disruption or technology changes.
1696 SAN Extender enables the extension of Storage Area Networking over distances of up thousands
of kilometers. It is specifically designed for applications that are critically dependent on dedicated and high-
ly reliable long distnace connectivity, such as disaster recovery, remote site backup, and datacenter to
datacenter sharing.
Figure 1. NMSE in TMN Architecture
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
4
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
With the ever increasing volumes of storage, todays enterprise is rapidly adopting the Storage Area Net-
work (SAN) as the fundation for a scalable, high performance storage system. SANs are tipically built on
Fibre Channel (FC) which provides a high bandwith, low latency fabric for interconnecting servers and
storage devices. Storage System Integrators have to come to rely on this high level of performance within
the Data Center. The challenge is to interconnect multiple Data Centers without sacrificing performance.
Figure 2. Remote SAN interconnection
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
5
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
1.2 References
Table 1. Handbooks related to 169xSE management
REF HANDBOOK Part No.
[1] 1353NMSE Network Manager for SAN Extender
1.3 SAN Extender 169xSE Integration in 1353NM
1353NM integrates 169xSE, it is managed as a Network Element.
Operations carried out by 1353NM on 169xSE are :
Create 169xSE NE starting from the Topology Viewer;
Start/Stop Supervision of 169xSE NE;
Show Equipment;
Alarm management.
1.4 Preconditions for the Integration of 169xSE in 1353NM
This paragraph lists some conditions to allow the integration of 169xSE in 1353NM Subsystem.
If a global installation is performed, 1353NMSE application is installed on 1353NM, but with partial
system installation a selection should be done to install 1353NMSE application.
1353NM Subsystem must be activated by GoGlobal application from a PC where 1353NMSE cli-
ent application is installed. If this condition isnt verified the Show Equipment command doesnt open
the NE USM.
To achieve a correct installation and integration of 169xSE follow the procedure described in para-
graph 1.5 for the Client installation, the Customization of the NMSE Server and setting the parame-
ters for the registration of the traps on 1353NM Subsystem.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
6
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
1.5 Installation of 169xSE Client Application
1.5.1 Installation Requirements
The NMSE software has two separate applications: Server and Client. The Server should be installed on
a dedicated Windowscompatible PC. It is recommended to have at least 3 Gigabytes of free disk space
on the Server PC for collecting monitoring data from all switches managed by NMSE.
The NMSE Client application should be installed on a user PC which will also have Alcatels Go Global
remote terminal application installed. The NMSE Client works in conjunction with Go Global to provide
management and monitoring capabilities for SAN Extender switches. The suggested configuration for the
Client PC is as follows:
Component Minimum Requirement
Processor Pentium III, 850 MHz CPU
RAM 256 MB
Hard Drive 10 Gb
CDROM Drive 24x
Operating System Windows XP Professional
Monitor 1024 / 768 256 colors, small fonts
Table 2. Suggested configuration for the Client PC
Multiple instances of the Client application can be installed in the management network, communicating
with the same NMSE Server application.
Installation of more than one NMSE Server on the same management subnet is not recom-
mended. Multiple servers may cause difficulties in logging, performance monitoring and time
synchronization.
To install the NMSE Server or Client, use the CD supplied with the SAN Extender (1693SE or 1696SE)
or the selfextractable file downloaded from Alcatels software support directory. Run the setup applica-
tion, which has several screens. When the Mode Selection screen appears (Figure 3. ), choose Client or
Server to be installed, then click Next.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
7
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 3. Install Wizard Mode Selection Screen
1.5.2 Installing the Server
On the NMSE Server station, also called the Master Platform, start the setup application as described
above. In the Install Wizard screen, choose the Server application, then click Next.
No further inputs are required. Once the installation process has completed, the NMSE Server application
can be activated in the following ways:
In the final screen of the installation process, check Yes, Launch the program file, then click Finish.
Or
Launch the application as a standard Windows program, from the Start Programs 1353SE menu.
After installation, the Server will need to be customized in order to register it within the Network Manager
framework, restrict access, define network elements, configure encryption, and manage the database.
The customization procedure is described in paragraph 1.6: Customizing the NMSE Server on page 8
.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
8
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
1.5.3 Installing the Client.
On the client PC, which has already had Go Global installed, start the setup application as described
above. In the Install Wizard screen, choose the Client application, then click Next.
No further inputs are required. Once the installation process has completed, the NMSE Client application
can be activated in the following ways:
In the final screen of the installation process, check Yes, Launch the program file, then click Finish.
Or
Launch the application as a standard Windows program, from the Start Programs 1353SE menu.
After rebooting the system, the NMSE Client will start automatically.
When the Client application starts up, it activates the SUS (Startup Service). The SUS icon will be placed
into the system tray. The management and monitoring windows of the NMSE Client will be activated later
by actions in the Go Global application.
Detailed operating instructions for the NMSE Client are given in document [1].
1.6 Customizing the NMSE Server
After installation, the NMSE Server must be customized in order to register it within the Network Manager
framework, restrict access, register network elements, configure encryption and manage the database.
1.6.1 Registering NMSE in the NM Framework
The NMSE Server is registered in the NM framework by a root user. The user must edit the NM Servers
/etc/hosts file to add a line of the following format:
<NMSE IP address> <NMSE server name> # SanServer
For example:
151.98.28.33 PCSan # SanServer
Note that # SanServer is a required string, not a parameter.
After this addition is made, the NMSE Server station can be recognized and contacted by the NM system.
1.6.2 Defining Users
In order to limit application access to authorized users, the NMSE operator defines a list of users and their
access privilege levels in the users.ini file located in the root directory of the 1353NMSE application. This
list works as an additional security level to the regular SNMP community definitions. The access list must
conform to the main 1353NM Server authentication policy.
The two access privilege levels are Read/Write (RW) and Read Only (RO). RW allows full administrator
level access to the managed switches. A user with RW access can configure, upgrade and monitor
switches. RO privilege allows only monitoring of the managed switches.
To add, delete or change users, the operator manually edits the users.ini file. The default user is alcatel
(casesensitive) with access level set to RW. (This default user is predefined and is not included in the
users.ini 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
9
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Example: The contents of the users.ini file after installation shows one user (SuperUser) defined with privi-
lege level of RW. Lines beginning with ; are comments only, showing possible users and privilege levels
that can be defined.
;[ALL]
;Acc=RO
[SuperUser]
Acc=RW
;[User]
;Acc=RO
Example: Two new users are added to the file: Tornado with RW access, and Storm with RO access
[Tornado]
Acc=RW
[Storm]
Acc=RO
1.6.3 Registering Network Elements in the NM Framework
A network element (NE) is a switch in the network being managed by the 1353NM Framework. SAN Ex-
tenders of the 1693SE and 1696SE families can be created as managed NEs in the 1353NM list so that
they will be considered nodes in the SAN. In the Topology Viewer Application (TVA) window, open the Dec-
larations menu, then select Create NE. Please refer to paragraph 3.1 in this chapter for more information.
1.6.4 Registering Network Elements in NMSE
Switches supported by NMSE include all models of the Alcatel 1693SE and 1696SE families of SAN Ex-
tenders. In addition, some models from other vendors can be partially supported, depending on the SNMP
MIBs they have implemented. For example, Brocades (or OEM Brocades) Fibre Channel switches are
supported and can be managed using most common commands from the NMSE Client.
Each supported NE (switch) must have at least one management interface configured.Parameters include
IP address, network mask, default gateway IP address, SNMP community, permitted users and their pro-
files.
A switch must be registered in the NMSE Servers list of network elements before it can be managed by
the NMSE application. It is recommend that all switches managed by the 1353NM Server also be regis-
tered in the NMSE Servers list. Use the NMSE Server Main Window (Figure 4. ) to add, change or delete
switches.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
10
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 4. Server Main Window
Colorcoded switch icons: the Tree View shows a list of switches in the SAN, with status indicated
by the following icon colors:
Red: switch has been defined in the SAN but is not physically connected.
Green: switch is defined in the SAN, there is a good connection, and the switch is fully under
SNMP control.
Blue: switch has unknown communication status.
Yellow: switch can be seen in the SAN but there is no direct communication (no ping). There
is FC inband communication.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
11
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
1.6.5 Adding Switches to the Servers List
A switch can be added to the Servers list even if it is not yet physically connected to the network, or if its
status prevents it from communicating.
1 ) Right click the SAN (globe) icon in the Workspace Tree. A popup menu appears.
2 ) Select Add Switch. The Add Switch window appears (Figure 5. ).
Figure 5. The Add Switch Window
3 ) Enter the IP Address.
4 ) The Switch Name parameter is optional and has the following limitations:
No spaces
Maximum 31 characters
First character must be alphabetic
5 ) Set the SNMP Community to the value that has been set for the network elements SNMP agent
community. The SNMP community and users.ini file together define the users and privileges
for the particular NE.
6 ) Click OK.
7 ) Click Advanced in the Add Switch window. The window is displayed
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
12
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 6. Advanced Options for Adding Switches
NOTE: It is recommended not to enter the switch name, in order to avoid switch name conflicts. If the switch
is connected to the network, the NMSE Server will autodetect the switch name and display it after the
other data has been entered.
8 ) Enable (check) or disable (uncheck) Polling. If enabled, Polling interval specifies how frequently
(in seconds) statistics and status data are collected from the switch. Statistics storage rate spec-
ifies (in minutes) the resolution of data that will be stored in the database.
9 ) Enter the Switch Parameters: WWN, Number of ports and Domain ID. These parameters can-
not be determined automatically if the switch is not yet physically connected or cannot commu-
nicate. (Where zoning is supported, a predefined switch can be used in zoning strategy once
these parameters have been defined.)
To delete a switch:
Rightclick on the switch, and select Delete from the popup menu.
To modify the properties of an existing switch:
Rightclick on the switch, and select Properties from the popup menu.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
13
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
1.7 Managing the Database
The NMSE Server application collects data from all managed network elements and automatically saves
the data to multiple databases located on the NMSE Server PC.
There are three types of databases:
Statistics Database: keeps full statistical information for all managed network elements, in-
cluding number of transmitted and received frames and bytes for the whole switch and for each
port; error counters; and other statistics.
Traps Database: keeps history of all alerts generated by all managed network elements.
Logs Database: accumulates operation logs for managed network elements.
To specify the size and location of these databases:
1 ) In the NMSE Server Main Window, open the Options menu and select Options. The Options
window appears. Select the Statistic tab (Figure 7. ).
Figure 7. Options Window, Statistic Tab
2 ) Specify the Size of the database file (in Megabytes). The default is 50. Once a file reaches this
size it will be archived on the local hard drive and a new file will be opened.
3 ) Specify the Number of database files. This is the maximum number of files that will be created
for each type of database. The default is 10.
4 ) Click OK.
5 ) Select the Folders tab. Set the file path for the location of database files on the local hard drive.
6 ) Click 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
14
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
1.8 1353NM activation
TMN OS is the graphical interface of OSKernel application dedicated to manage the different Subsystem
Instances built on the same hardware machine.
TMN OS application is the box containing and managing all the NM Subsystems customized on a single
physical machine.
TMN OS Icon
Figure 8. Alcatel CDE Front Panel
Select TMN OS icon as shown in the previous figure to start TMN OS application. The TMNOS Manage-
ment Window will be shown in a few seconds, you have to select the 1353NM instance you want to man-
age.
Figure 9. TMN OS 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
15
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
2 169XSE INTEGRATION
This chapter explains the integration steps to be done in order to manage 169xSE starting from 1353NM.
These operations should be done before activating any 1353NM function towards 169xSE.
2.1 Steps sequence to manage 169xSE NEs
Installation of 1353NMSE Client application on the Personal Computer from which the opera-
tor performs the remote connection to 1353NM platforms via GOGlobal.
1353NMSE Server station shall be known to 1353NM Master platform and reachable via IP
networking. The simplest way to achieve IP connectivity is declaring 1353NMSE Server into
/etc/hosts file. Root user can edit the file and add following line :
<SANman IP address> <SANman server name> #SanServer
N.B. The comment # SanServer is not an optional but a mandatory string> It cannot be
omitted. E.g. 151.98.28.33 PCScan #SanServer
2.2 169xSE EmlDomain Configuration
Once the installation steps are completed, System Configuration phase should be started to configure em-
lim to manage 169xSE NEs.
169xSE are supervised by 1353NM through SGM (Snmp Generic Mapper) component. During System
Configuration phase, this application gets an identification number (emilm id). To configure the application
select from TMNOS menu OS > SystemConfig, following window will be displayed
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
16
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
EMLIMSGM ID
Figure 10. System Configuration window
During System Configuration the UDP port number is assigned to EMLIMSGM. This port number should
be greater than 1024 and the operator should take care to assign different port number for different config-
ured emlims. Selecting on the right side of the SystemConfig window EMLIMSGM_xxx, the following win-
dow will be displayed
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
17
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 11. EMLIMSGM Configuration
Insert a port number greater than 1024 and select Actions > Apply&Exit as shown in following figure.
Figure 12. Configuration data confirmation
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
18
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
3 169XSE SAN EXTENDER MANAGEMENT
3.1 169xSE Network Element Creation
In order to manage 169xSE from 1353NM a new Network Element should be created. The creation of the
new Network Element starts from Topology Managent application, to open the application select from
TMNOS menu Actions | > Topology Manager or pressing the icon
Figure 13. Topology Manager
The map management window will be displayed with the last saved map. 169xSE can be created in a new
map or in an already existent map. To create the Network Element select from the menu Declaration >
Create > NE ... as shown in following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
19
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 14. 1353NM Create Network Element
The above selection will display the NE Creation window where the new Network Element data should be
inserted.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
20
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 15. 169xSE NE Creation
Network Element data to insert for the NE creation are :
Family : NE family SAN family
Type : NE type 169xSE
Release : NE release 1.0
User Label : User Label for the Network Element. The first symbol of the name must be letter. The
current implementation of SANman does not allow to include the following characters into NE name
: ~ ! @ # $ % ^ & * ( ) _ + = < > ? / , ; \ : \\ [ ] { } and space.
Location Name : where the equipment is installed
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
21
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Supervision Area : identifies the LAN card of the 1353NM Master platform (HP server) through which
the management traffic to/from 169xSE shall go through, according to the DCN design. In case
1353NM Master is equipped with one LAN Card for NE management channels, no selection re-
quested to endusers.
EML domain : it identifies the Manager process instance in charge of direct interworking with the NE
SNMP agent; no user selection let 1353NM automatically choose the proper SNMP Manager
instance according to load balancing criteria. Select from the list the domain corresponding to the
emlim managing 169xSE. The emlim managing 169xSE is EMLIMSGM. The information about the
domain can be found in the System Configuration window.
ACD : it identifies a given network domani, applicable just in case the global network under 1353NM
supervision is securely partitioned to split the management responsibilies to different users.
Click on the Apply button to confirm the Network Element creation, the click on the Close button to close
this window.
Once the 169xSE equipment is created into the 1353NM Global Inventory and is available to be inserted
into the Network Maps.
After the NE creation, the 169xSE IP address should be assigned to the new Network Element. To set the
NE address select Declarations > Set Addresses > NE Address... from the Topology Management
menu as shown in following figure.
Figure 16. NE Set Address
After the selection a dialog box to insert the IP address is displayed, as shown hereafter
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
22
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 17. 169xSE Set Address
After this operation, the Network Element creation is completed.
3.2 Security
Security is not managed by 1353NM for 169xSE NE. This means basically that users of any profile are
enabled to open the specific application and perform all available operations on the switch.
3.3 169xSE Network Element Supervision
After the creation, a Network Element should be supervised by 1353NM Subsystem in order to be man-
aged by the Network Management system. Select from menu Operations > Supervision > No Align-
ment.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
23
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 18. NE Supervision
To start the supervision click on the button Apply and wait for the operation to finish, then click on the button
Close to exit.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
24
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 19. Start 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
25
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
3.4 Navigation from 1353NM Topology Management to USM
Once 169xSE is supervised, navigation to the SANman management application is allowed selecting from
the popup menu the Show Equipment option.
Figure 20. NE Show Equipment
This operation opens the user interface as shown in following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
26
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 21. 169xSE 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
27
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
3.5 Navigation to SANman application
From TMNOS it is possible to activate SANman application selecting the dedicated icon as shown in fol-
lowing figure
Figure 22. Open SANman application from TMNOS selecting icon
Figure 23. Open SANman application from TMNOS selecting menu Actions
Selecting the highlighted icon in the figure or TMNOS menu Actions > Open 1353NMSE Map, the
application main window is displayed where all the managed SAN equipment are displayed in the resource
tree.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
28
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 24. User Interface
The contents and set of operations available with application are not part of the present manual. Please
refer to [1] for a detailed description of the application.
3.6 Ping NE
A useful function to test the 169xSE NE reachability from 1353NM is the Ping NE function. Select the
169xSE NE on the map, select from the menu Operations > Ping NE. The operations result will be dis-
played after a few seconds as shown in following figure.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
29
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 25. Ping NE result
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
30
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
4 ALARM MANAGEMENT
Alarms are managed by a generic component called AS (Alarm Surveillance) integrated in the common
platform OSKernel and can be activated from TMNOS menu. For 169xSE a subsystem of alarms is
managed and can be seen using AS USM. Starting from TMNOS menu the main AS USM window is dis-
played as shown in following figure. This list contains all the alarms received.
Figure 26. Main Alarm List
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
31
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 27. AS Administration Selection
The administration window is displayed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
32
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 28. AS Administration 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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
33
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
4.1 Navigation from AS to 169xSE USM
Starting from the main alarm list window it is possible to navigate to SANman USM selecting Navigation
> External Appliaction > Related EmlUsm. Each time a navigation is selected a new SANman USM
window will be opened.
Figure 29. Navigation to SANman application
Selecting the above navigation the 169xSE USM is displayed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
34
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 30. 1353NMSE Alarms List
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
35
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
4.2 Navigation from Topology Management to AS USM
On the other side its possible to navigate from Topology Management, selecting OA512 Network Element,
to AS USM displaying the alarms sublist concerning OA512 alarms.
Figure 31. Navigation to AS USM
Selecting the option Show alarms the list of 169xSE alarms will be displayed.
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
36
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
Figure 32. 169xSE Alarms Sublist
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
.
ED
1
A
A

0
0
0
1
4

0
0
0
4

(
9
0
0
7
)

A
4

A
L
I
C
E

0
4
.
1
0
37
03

SC.8:1353NMSE

/ 3AL 89061 AA AA

37
37
END OF DOCUMENT

1353nm70 Oh Eng Ed03

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1353nm70 Oh Eng Ed03

Uploaded by

Copyright:

Available Formats

3AL 89061 AAAA Ed.

You might also like