1354 RM

QUESTA PAGINA NON VA INSERITA NEL MANUALE
All rights reserved. Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization from Alcatel.
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

COD.MANUALE HDBK P/N: 957.130.882
U Ed.03 3AL 61260 AAAA Ed.03
1300NM
1354RM Rel.5.2B
ADMINISTRATION GUIDE
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
No PAGINE TOTALI PER ARCHIVIAZIONE: 204

DIMENSIONE BINDER SORGENTE (du ks): 4.949 kBytes
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS
STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
No pagine
(facciate)
No pages
numerate
numbered
da from
a to
1/198
198/198
TARGHETTE - LABELS
957.130.882 U Ed.03
3AL 61260 AAAA Ed.03
frontespizio
front
manuale
manual
198
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:
200
TOTALE FOGLI A4 TOTAL A4 SHEETS:
100
WARNING FOR A-UNITS OTHER THAN A-ITALY
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Labels are done according to A-Italy binder format.

Source file ALICE 6.10
03
RELEASED
957.130.882 TQZZA
3AL 61260 AAAA TQZZA

4
1/ 4
Site
VIMERCATE
Originators
M.VARISCO

ALCATEL OPTICS GROUP
1354RM REL.5.2B
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
TND
1354RM REL.5.2B ADMINISTRATION GUIDE

Internal :
External
:
Approvals
Name
App.
M.RAGNI
Name
App.
INFORMAZIONI EDITORIALI
ORIGINALE SU FILE: ALICE 6.10
sistemazione figlist
957.130.882 U
3AL 61260 AAAA
Ed.03
1300NM
1354RM Rel.5.2B
1AA 00014 0004 (9007) A4 ALICE 04.10
Regional Network Manager for SDH and Optical Networks

ED
03
RELEASED
957.130.882 TQZZA

4
2/ 4

1300NM
1354RM Rel.5.2B
957.130.882 U Ed.03
VOL.1/1
1300NM
1354RM Rel.5.2B
957.130.882 U Ed.03
VOL.1/1
1300NM
1354RM Rel.5.2B
957.130.882 U Ed.03
VOL.1/1
1300NM 1354RM Rel.5.2B

957.130.882 U Ed.03 3AL 61260 AAAA Ed.03
VOL.1/1
1300NM
1354RM Rel.5.2B
1AA 00014 0004 (9007) A4 ALICE 04.10
957.130.882 U Ed.03
ED
03
VOL.1/1
RELEASED
957.130.882 TQZZA

4
3/ 4
1AA 00014 0004 (9007) A4 ALICE 04.10
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT
ED
03
RELEASED
957.130.882 TQZZA
4/ 4
Administration Guide
Alcatel 1300NM
Network Management
1354RM Rel.5.2B
957.130.882 U Ed.03
957.130.882 U Ed.03
1AA 00014 0004 (9007) A4 ALICE 04.10

1354RM REL.5.2B ADMINISTRATION GUIDE
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REFERENCED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Product-release handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Handbooks related to the specific software application . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2 Handbooks related to the products hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Purpose of the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Required skill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
10
10
11
11
11
11
12
2 HARDWARE AND SOFTWARE REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 IM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 US configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 IM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 US configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
14
14
15
16
16
18
3 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Installation and Customization of Complete delivery Packages . . . . . . . . . . . . . . . . . . . .
3.1.1 SMF installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 Reconfigure SMF installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 1354RM Installation Environment Variable Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Installation of Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 RM DB resizing after installation patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 MultiIM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
20
21
21
22
25
25
26
4 HPOV DM CUSTOMIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 PMD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
27
03
001206
SC00120501
M. Ragni ITAVE
M. Varisco ITAVE
02
000721
SC00072405
M. Ragni ITAVE
M. Varisco ITAVE
01
000414
M. Ragni ITAVE
M. Varisco ITAVE
ED
DATE
APPRAISAL AUTHORITY
ORIGINATOR
CHANGE NOTE
1354RM R5.2.x
System Administrator
Reference Guide
ED
03
957.130.882 U

198
1 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
28
28
28
5 IPC RESOURCES CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
6 USERS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 1354RM Operators Managing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 HPOVw Users Profile for NetView application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2 CDE Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3 Unix Shell Profile (.profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Network Access Domain Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Adding an RM Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2 Defining a new RM Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.3 Access Rules description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.4 Delivered set of Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.5 Default mapping between User Profiles and Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
32
32
33
33
34
35
36
37
48
48
7 PROCESS MONITOR & CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 Maintenance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Integration of IM Agent in 1354RM PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
49
50
8 DATABASE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1 Database Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Database disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 Database extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5 DB realignment via redo log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6 Identifier Defragmentation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.1 Procedure steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.2 idDefrag procedure structure of log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 DB configuration for huge networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8 Managing indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
53
54
60
61
63
64
64
65
66
66
9 SYSTEM MANAGEMENT FEATURES (SMF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1 EMLs Data Definition for SMFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Description of smf_conf file parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Networks configuration file generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 1354RM Scheduled Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 MultiScreen Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
67
68
69
70
70
10 1354RM BEHAVIOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 EMLs management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.1 Procedures to define EMLs managing Q3 NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.2 Procedures to create EMLs managing QB3* NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.3 Procedures to delete EMLs managing QB3* NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Path / HOTrail allocation algorithm failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Distributed Network Maps (DNM) application customization . . . . . . . . . . . . . . . . . . . . .
10.3.1 Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.2 Registration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.3 Resources Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 Trace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4.1 User Interface applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4.2 Information Manager Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
71
71
71
71
72
74
74
74
74
75
75
75
ED
03
957.130.882 U

198
2 / 198

4.2 Installation on Distributed Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 Remote Event Sieve configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Object Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

10.5 Consistency Download problem with transmux ports . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.5.1 RM with 2Mb ports and WX with a single port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.2 RM with a single port and WX with 2Mb ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
76
77
78
11 1354RM CUSTOMIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 Environment variables changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Users Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.1 Counters refresh rate on agent response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.2 Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 EMLNML Alignment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Inventory Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 Map Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 Path/HOTrail Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6.1 Path/Trail allocation algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6.2 Reuse already allocated resources in Broadcast paths. . . . . . . . . . . . . . . . . . . . . . . . . .
11.6.3 Using Virtual Nodes during Path Allocation Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6.4 Configurable switch in Drop&Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6.5 Changing timeout for Cross Connection management actions . . . . . . . . . . . . . . . . . . . .
11.6.6 Configuring consistency flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.1 Flooding protection mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.2 Alarm clearing hysteresis period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.8 Nap uploading timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.9 SNCP switch timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10 Printer Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.11 Unused Virtual PDH ports garbage collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.12 Setting Linked Get Replies Maximum Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.13 NetView Symbols Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14 Performance Monitoring Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14.1 PM Data Collection Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14.2 PM Data Archive Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14.3 PM Scheduled Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14.4 PM Automatic Start/Stop Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15 How to change the default ASAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.16 Procedure to set Swedish language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
79
80
80
80
80
81
81
82
82
82
83
83
83
84
84
84
84
85
85
85
86
86
87
88
88
90
91
91
92
92
12 QNN INTERFACE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.1 Enabling / Disabling Qnn Agent Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 RM user definition for Qnn ZoomIn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1 RM users definition script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3 RM ZoomIn from NN using RM USM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4 Limitation of Network Construction lead by Qnn Agent . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5 Limitation of Qnn path provisioning lead by RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6 Assigning Network Resources to 1354NN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
93
93
93
94
95
96
96
13 EML SIMULATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1 Simulated EML data generation and EML registration . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1.1 Available Simulated data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1.2 Simulated data file syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 Real Network Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
97
97
98
99
100
14 HOW TO CHANGE THE USERLABEL OF NES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.1 NEs with SENIM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 NEs with TSDIM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3 Aligning the userLabel of PMNEs and PMTPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
101
101
101
102
ED
03
957.130.882 U

198
3 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
102
15 MIGRATION PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1 1354RM R2.4 (NR3.1) to 1354RM R5.2.x Migration Procedure . . . . . . . . . . . . . . . . . . . . .
15.2 Virtual EML registration on Communication Infrastructure (CI) . . . . . . . . . . . . . . . . . . .
15.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2.2 Procedure steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3 Migration Procedure of NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3.1 NE migration between QB3* and QB3 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3.2 neGroup modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.4 OVW Map Conversion from 1354RM R2.4 to 1354RM R5.2.x . . . . . . . . . . . . . . . . . . . . . .
15.4.1 Recover Maps after migration when changing ntwDomld . . . . . . . . . . . . . . . . . . . . . . . .
15.5 Virtual EML registration on Communication Infrastructure (CI) . . . . . . . . . . . . . . . . . . .
15.5.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.5.2 Procedure steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
103
104
108
108
108
109
110
115
117
117
118
118
118
16 UPDATE OF MSSPRING INFOS (MSSPRING TAKEOVER) . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2 Procedure steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.3 Format of nodedata file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.4 Loading of a prebuilt nodedata file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
119
120
121
121
APPENDIX A INTEGRATION OF 1354RM WITH A1330AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.1 Installing A1330 AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2 Deinstalling A1330 AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3 A1330 AS customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3.1 Swedish language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
123
123
123
124
124
APPENDIX B INTEGRATION OF 1354RM WITH GENERIC OSOS INTERFACE . . . . . . . . . . . .

B.1 Generic OSOS Interface Subsysystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2 Generic OSOS Interface Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3 Generic OSOS Interface deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125
125
125
126
APPENDIX C INTEGRATION OF 1354RM WITH SEC SECURIYT SUBSYSTEM . . . . . . . . . . . . .

C.1 SEC Architecture on 1354RM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.2 Installing SEC Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.3 Deinstalling SEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.4 SEC Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.5 Alarm Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
127
127
128
129
130
131
APPENDIX D COMMAND FILE SPECIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.1 Command Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.1 Syntax Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.2 Setting time reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.3 Setting network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.4 Path commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.5 Trail commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.6 Port User Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.7 CHOWN commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.8 PM commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.9 aSAP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.10 restRule commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.11 Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.12 Sleep command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.13 Setting timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
135
136
137
138
138
139
145
149
149
150
155
156
158
158
158
ED
03
957.130.882 U

198
4 / 198

14.4 Moving ET from Generic to Meshed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

D.1.14 Exit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D.1.15 Connection command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.16 Topology Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.17 Upload and Remove NAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.18 Configure et, physical connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.2 tool description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.2.1 Handling errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.1 Example on paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.2 Example on paths protected with Drop & Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.3 Example on broadcast path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.4 Example on broadcast paths (2nd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.5 Example on trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.6 Example of path that uses HO trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.7 Example on measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.8 Example on aSAProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.9 Example on restoration rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.10 Example on implement, deimplement connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.11 Example on create, remove, implement and deimplement topology. . . . . . . . . . . . . . . .
D.3.12 Example on upload and remove nap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3.13 Example configure physical connection and et. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
158
159
161
165
165
166
166
167
168
170
173
175
182
186
188
190
191
192
193
197
198
03
957.130.882 U

198
5 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
FIGURES
Figure 1. Example of directories allocation with at least two physical disks . . . . . . . . . . . . . . . . . . . .
Figure 2. Distribution of files in two application disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Supported topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Not supported topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Reference Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
61
95
95
167
TABLES
Table 1. Handbooks related to the specific software application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. NR 5.0B Related Handbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. Documentation on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Access Rules Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5. NAD / FAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
10
10
40
45
ED
03
957.130.882 U

198
6 / 198

LIST OF FIGURES AND TABLES
HISTORY

As internal document 3AL 61217 ACAA TCZZA

01 on March 1st, 2000 Ed.1
Creation 1354RM R5.2.0 First delivery
02 on April 27th, 2000 Ed.2
1354RM R5.2.0 Integration with SEC, migration ET from generic to meshed, new user qnnpmop for
QNN and installation kit and patch procedures modified.
03 on June 1st, 2000 Ed.3
1354RM R5.2.1 EML simulation, enable of SEC with AS, Map Management features and migration
procedure.
04 on August 24th, 2000 Ed.4
1354RM R5.2.1 Set of Swedish language and new batch commands.
05 on September 19th, 2000 Ed.5
1354RM R5.2.1 Limitation of Qnn path provisioning and new codes of error in path allocation.
ED
DATE
CORRESPONDING TO 3AL 61217 ACAA TCZZA ED.
01
000414
01
02
000721
03
03
001206
05
REFERENCED DOCUMENTS
1AA 00014 0004 (9007) A4 ALICE 04.10
(For Alcatel internal use only)

[1]
HP OpenView Distributed Management Agent Platform Administrators Reference

HP Part No. J106490016
[2]
O. Frelot ALMAP Reference Platforms

Ed. 8; August 31st, 1999; 3BP 21610 0002 DTZZA
[3]
G. Chaminade ALMAP Reference Platforms Consistency Control

Ed.3 April 30th, 1998 ; NMU/C/97/0037
[4]
A. Borsotti A1300 NM3.1 Equipping Option List

Ed.1It.1 July 20th, 1998 ; 3AL 71002 ABAA BHZZA
ED
03
957.130.882 U

198
7 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.882 U
198
8 / 198

1 INTRODUCTION
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:
1AA 00014 0004 (9007) A4 ALICE 04.10
ANV P/N
Factory P/N
1354RM
3AL 61101 AAAA
521.200.800
PRODUCT
RELEASE
VERSION (*)
ANV P/N
Factory P/N
1354RM
5.2B
3AL 61169 ADAA
521.560.420
N.B.
ED
PRODUCT
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.
03
957.130.882 U

198
9 / 198
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 9 consists of the following handbooks:
1.3.1 Handbooks related to the specific software application
Table 1. Handbooks related to the specific software application
REF
HANDBOOK
ANV Part No.
FACTORY
Part No.
[1]
1354RM Rel.5.2B
Installation Guide
3AL 61261 AAAA
957.130.892 W
[2]
1354RM Rel.5.2B
Operators Handbook
3AL 61259 AAAA
957.130.872 H
[3]
1354RM Rel.5.2B
Administration Guide
3AL 61260 AAAA
957.130.882 U
ANV Part No.
FACTORY
Part No.
3AL 71109 AAAA
957.130.722 A
THIS
HANDBOOK
Table 2. NR 5.0B Related Handbooks
REF
HANDBOOK
1330AS Rel.5.1
Operators Handbook
[4]
THIS
HANDBOOK
or note
Table 3. Documentation on CDROM

REF
ANV Part No.
FACTORY Part No.
3AL 61262 AAAA
417.100.028
[5]
NOTE
Envisaged after the release of all
Handbooks
1AA 00014 0004 (9007) A4 ALICE 04.10
Contains, in electronic format, the following handbooks: REF.[2] to [4]
ED
03
957.130.882 U

198
10 / 198

1.3 Product-release handbooks
1.3.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
1.4 Purpose of the Document

Purpose of this document is to provide a simple guideline for:
hardware and software requirements,

installation and customization,
activation,
system administrator guide.
of Alcatel Telecom TND 1354RM R5.2.x product.

Refer to:
1353SH R5.2
1353WX R1.7.1
1330AS R5.0.0 & R5.1.0

Installation Guide for additional information related to the interworking and installation on HP workstation.
1.5 Intended audience

This document is intended to be used by the 1354RM System Administrator in order to install and configure
the product.
1.6 Required skill
1AA 00014 0004 (9007) A4 ALICE 04.10
A good knowledge of HPUX 10.20, Oracle 7.x Database Management System and HPOV DM platform
is considered a mandatory prerequisite.
ED
03
957.130.882 U

198
11 / 198
In this document the installation procedure and maintenance operations are described with all the shell
commands needed by this procedure. Either Korn Shell (ksh) or Bourne Shell (sh) are supposed to be
used by the operator.
N.B.
Normally are described commands that can be used with a Korn Shell. If you are using a Bourne
Shell you have to pay attention to the symbol definition command. In Korn Shell you can define
a symbol in the following way:
export symbol_name=<symbol_value>
on the contrary, if you use Bourne shell, you have to split the command in the followings:
symbol_name=<symbol_value>
export symbol_name
The shell commands to be used are described using the following conventions:
Bold means that the string must be typed as it is described in the manual;
<Angle bracket> represent command parameter that must be specified by the operator;
shell commands needed to be executed as root user are prompted with #;

all the other commands are prompted with $, these commands can be performed by the snml user
or other administrator user (the only that have Unix access).
N.B.
To execute command as root user, it is recommended to change the username using the
command:
su root
1AA 00014 0004 (9007) A4 ALICE 04.10
instead of su root, because with the recommended command all the RM environment
variables are kept.
ED
03
957.130.882 U

198
12 / 198

1.7 Conventions
1AA 00014 0004 (9007) A4 ALICE 04.10

2 HARDWARE AND SOFTWARE REQUIREMENTS

1354RM product supports distributed configuration. It is possible to install Information Manager (IM)
configuration and User Service (US) configuration on different physical hosts. IM configuration is a
complete one and supports DB, agents and user interface; US configuration supports only user interface
providing network access to IM hosts via CMISE and SQLNet interface.
ED
03
957.130.882 U

198
13 / 198
2.1.1 IM configuration
For hosts to be adopted please refer to Equipping Option list [4].
At least 128 Mb RAM size are required; 256 Mb RAM are recommended.
At least two physical disks are required in order to provide good backup and restore facilities :
1)
the first disk contains the directories used to save backup, reference base, redo log and
mirrored database information.
the second disk contains the 1354RM product,
2)
N.B.
the bdf HPUX command, specifying the directory as a parameter, can be used to
verify in which filesystem a directory is stored.
Required disk space is the following :
Data Disk. 1354RM installation tree size depends on number of NEs and paths that must be
managed:
small: ~ 1 Gb
medium: ~ 1.5 Gb
large: ~ 1.9 Gb
If the RM help is installed the previous Disk size shall be increased of 200 Mb.
Backup and Mirror Disk. Backup and Mirror data size depends on number of NEs and paths that
must be managed by 1354RM. The following sizes are referred to snapshot backup area,
reference base for incremental backup and archive area for Oracle redo log files (in this sorting
criteria):
small:
50 Mb + 300 Mb + 300 Mb = 650 Mb
medium: 50 Mb + 500 Mb + 300 Mb = 850 Mb
large:
50 Mb + 1100 Mb + 300 Mb = 1450 Mb
Please note that the previously specified snapshot backup area size do not take into account
the disk space required by SH backup and it depends on the number of SH managed by the
1354RM.
N.B.
In order to guarantee Oracle data consistency, Data Disk (1354RM installation) must be
local to the workstation on which 1354RM system will run, and can not be stored in a
filesystem reached via NFS.
The following data have to be also taken into account to evaluate a correct 1354RM disk occupation
:
Installation kit gzipped tar file (if no mass storage device is used): ~ 200 Mb
Swap File on Disk: ~ 512 Mb
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The previous disk occupation data do not take into account the table space created in the
1354RM Oracle DB by other subsystems (e.g. 1330 AS Alarm Surveillance).
03
957.130.882 U

198
14 / 198

2.1 Hardware Requirements
1AA 00014 0004 (9007) A4 ALICE 04.10

2.1.2 US configuration
For hosts to be adopted please refer to Equipping Option list [4].
At least 128 Mb RAM size are required; 256 Mb RAM are recommended.
Required Disk size:

1354RM installation subtree size is ~ 450 Mb.
The following data have to be also taken into account to evaluate a correct 1354RM disk occupation:
ED
Installation kit gzipped tar file (if no mass storage device is used): ~ 200 Mb
Swap File on Disk: ~ 512 Mb
03
957.130.882 U

198
15 / 198
2.2.1 IM configuration
1354RM IM have to be installed on Almap HP4 platform updated with the HP4.2 patch level plus the
PHSS_15076 HP patch (for further details, please, refers to Almap Reference Platforms document [2]).
Anyway, at least, the following configuration should be used (note that the OSFMotif 1.2 must be installed
within HPUX 10.20 ):
1AA 00014 0004 (9007) A4 ALICE 04.10
Bundle(s):
B3560CBEng
B3691AA_APZ
B3782EA
DMPlatDKHP10man
DMPlatDKHPUX10x
DMPlatEngHP10man
DMPlatEngHPUX10x
HPUXEngCR700
J2160A_APZ
J2655AA_APZ
OVLicenseSvrHP10
SoftBenchRef
XSW700CR1020
XSW700GR1020
C.05.25
B.10.20.89
B.10.20
B.05.01
B.05.01
B.05.01
B.05.01
B.10.20
C.07.00
B.10.20.02
B.05.01.00
C.05.25
B.10.20.36
B.10.20.36
English C SoftBench S700 10.x

HP GlancePlus/UX for s700 10.20
HPUX Media Kit (Reference Only. See Description)
DM TMN Manager Developers Kit man pages
DM TMN Manager Developers Kit
DM TMN Manager Platform Man Pages
DM TMN Manager Platform
English HPUX CDE Runtime Environment
OSI Trnspt and Srvcs for 9000/700
100VGAnyLAN/9000 EISA
OpenView License Server for HPUX10.x
SoftBench 5.0 (Reference Only. See Description)
Extension Software Patch Bundle
Product(s) not contained in a Bundle:

OTSLITE9000
C.07.00
OSI Trnspt and Svcs 9000
PHCO_13661
B.10.00.00.AA POSIX shell cumulative patch
PHCO_13698
B.10.00.00.AA ksh(1) cumulative patch
PHNE_10077
B.10.00.00.AA patch for EISA 100VGAnyLAN product
PHNE_8830
B.10.00.00.AA OTS C.07.00 cumulative mega patch
PHSS_15076
B.10.00.00.AA OV NNM5.0x Consolidated Patch 61698
Oracle 7. The following modules are used:
ORACLE7 Server (RDBMS)

7.2.3.0.0
SQL*Plus
3.2.3.0.0
SQL*Net V2
2.2.3.0.0
TCP/IP Protocol Adapter V2

2.2.3.0.0
PL/SQL V2
2.2.3.0.0
ED
03
957.130.882 U

198
16 / 198

2.2 Software Requirements

The following system kernel parameters have to be set, at least, with these values:
maxusers = 64
maxuprc = 200
ncallout = 548
nproc = 532
shmmni = 200
shmseg = 120
msgmap = 258
msgseg = 7168
msgtql = 256
shmmax = 512 * 1024 * 1024

semmni = 50
semume = 25
semmns = 200
semmnu = 200
In order to improve performances, it is suggested to remove the following HPOV DM processes

(using the following commands):
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
(these values are recommended by ORACLE installation)
$OV_BIN/ovdelobj
$OV_BIN/ovdelobj
$OV_BIN/ovdelobj
$OV_BIN/ovdelobj
$OV_BIN/ovdelobj
$OV_LRF/netmon.lrf
$OV_LRF/ovtopmd.lrf
$OV_LRF/ovtrapd.lrf
$OV_LRF/ovactiond.lrf
$OV_LRF/snmpCollect.lrf
03
957.130.882 U

198
17 / 198
1354RM US have to be installed on Almap HP4 platform updated with the HP4.2 patch level plus the
PHSS_15076 HP patch (for further details, please, refers to Almap Reference Platforms document [2]).
Anyway, at least, the following configuration should be used (note that the OSFMotif 1.2 must be installed
within HPUX 10.20 ):
Bundle(s):
B3560CBEng
B3691AA_APZ
B3782EA
DMPlatDKHP10man
DMPlatDKHPUX10x
DMPlatEngHP10man
DMPlatEngHPUX10x
HPUXEngCR700
J2160A_APZ
J2655AA_APZ
OVLicenseSvrHP10
SoftBenchRef
XSW700CR1020
XSW700GR1020
English C SoftBench S700 10.x

HP GlancePlus/UX for s700 10.20
HPUX Media Kit (Reference Only. See Description)
DM TMN Manager Developers Kit man pages
DM TMN Manager Developers Kit
DM TMN Manager Platform Man Pages
DM TMN Manager Platform
English HPUX CDE Runtime Environment
OSI Trnspt and Srvcs for 9000/700
100VGAnyLAN/9000 EISA
OpenView License Server for HPUX10.x
SoftBench 5.0 (Reference Only. See Description)
Product(s) not contained in a Bundle:

OTSLITE9000
C.07.00
OSI Trnspt and Svcs 9000
PHCO_13661
B.10.00.00.AA POSIX shell cumulative patch
PHCO_13698
B.10.00.00.AA ksh(1) cumulative patch
PHNE_10077
B.10.00.00.AA patch for EISA 100VGAnyLAN product
PHNE_8830
B.10.00.00.AA OTS C.07.00 cumulative mega patch
PHSS_15076
B.10.00.00.AA OV NNM5.0x Consolidated Patch 61698
The following system kernel parameters have to be set, at least, with these values:
maxusers = 64
maxuprc = 200
shmmni = 200
shmseg = 120
msgmap = 258
msgseg = 7168
msgtql = 256
In order to improve performances, it is suggested to remove the following HPOV DM processes

(using the following commands):
1AA 00014 0004 (9007) A4 ALICE 04.10
C.05.25
B.10.20.89
B.10.20
B.05.01
B.05.01
B.05.01
B.05.01
B.10.20
C.07.00
B.10.20.02
B.05.01.00
C.05.25
B.10.20.36
B.10.20.36
ED
$OV_BIN/ovdelobj
$OV_BIN/ovdelobj
$OV_BIN/ovdelobj
$OV_BIN/ovdelobj
$OV_BIN/ovdelobj
$OV_LRF/netmon.lrf
$OV_LRF/ovtopmd.lrf
$OV_LRF/ovtrapd.lrf
$OV_LRF/ovactiond.lrf
$OV_LRF/snmpCollect.lrf
03
957.130.882 U

198
18 / 198

2.2.2 US configuration
3 INSTALLATION
1AA 00014 0004 (9007) A4 ALICE 04.10

WARNING
The following is the Installation procedure that have to be used only internally
by Alcatel Units during Integration phase. Customers and Alcatel Installation
post DR4 must follow the Installation Procedure described in document NR3
Installation Guide.
In the following paragraph, the shell commands needed to perform installation, customization and
activation of 1354RM are given.
ED
03
957.130.882 U

198
19 / 198
3.1 Installation and Customization of Complete delivery Packages
a)
If there is an old version installed, shutdown the 1354RM system, the 1354RM Oracle instance and
all user service manager instances (ovw, browser and mngAgent).
Since the 1354RM installation performs a reset of OVwDB (even if the Old Mib option is
chosen) no maps will be present at the end of installation. Its mandatory to save the maps to be
kept using DNM application.
b)
Exit from normal user CDE space and login again as root user in CDE login form.
c)
The user snml with the default shell equal to /bin/ksh is created automatically; snml user must be
part of dba group; dba is the same group of the user oracle. This snml user will be the 1354RM
system administrator.
# sam ....
N.B.
d)
Please, do not use as snml user home directory the same directory that will be used as
installation directory of 1354RM product (see d ))
Create (if it does not exist) an empty directory for 1354RM installation tree root :
# mkdir <yoursnmlinstroot>
e)
Change current directory to the SNML installation root and extract restore_gz file from 1354RM
installation tar kit (1354RM installation tar kit is relative to the current directory).
N.B.
Please, do not use the command cd /usr/snml since it will generate some
inconsistencies during the etc/restore_gz procedure.
# cd <yoursnmlinstroot>
# gunzip d c <1354RM...yourmediadevice or tar file> | tar xvf ./etc/restore
N.B.
f)
Please, note that 1354RM... is the standard prefix of each RM complete delivery or
patches.
Execute restore_gz script running the following command:

# etc/restore <1354RM...yourmediadevice or tar file>
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
g)
ED
The installation procedure creates a link /usr/snml that is linked to 1354RM installation
root directory.
A graphical window with all the needed environment variables (etc/env_snml file) is presented to the
user. The variables, if possible, are initialized with the values assigned to them by the operator in
previous release. The user can change, if needed, their values and save them in the new
etc/env_snml file clicking on Apply button (please refer to 3.1.3 for variables description).
03
957.130.882 U

198
20 / 198

In the following you can find the procedure to install a complete 1354RM delivery.

h)
Execute customize script pressing the Customize button, a window will be opened containing the
traces of the Customize execution. If some errors occur during customize execution, it signals to
the operator the log file where he can find information on the occurred error. The customize procedure
will produce a trace file called etc/customize.trc containing all the messages printed out by the
customize script.
i)
At the end of the previous step, it is necessary to verify the contents of the im_host_conf file, since
it is is generated by the customize procedure (please refers to the paragraph 4.2.1)
j)
If the network to be managed is very big and managed using many EMLs, some system and DB
parameters should be changed, as suggested in the procedure described in the paragraph 8.7.
k)
To activate all the CDE configuration changes it is recommended to exit from the current CDE session
and log in again to use 1354RM product.

3.1.1 SMF installation
Login as root user and launch the swinstall procedure:
$ swinstall s <package full path name> SMF
3.1.2 Reconfigure SMF installation
After a 1354RM new installation the SMF icon is no longer present on the vertical palette of the desktop.
1AA 00014 0004 (9007) A4 ALICE 04.10
Execute the following command:

$ swconfig x reconfigure=true SMF
ED
03
957.130.882 U

198
21 / 198
In the following you can find an explanation of the meaning of variables contained in the file
${SNML_HOME}/etc/env_snml, that have to be initialized for a correct 1354RM installation.
N.B.
In order to verify in which filesystem a directory is stored the bdf <dir_name> HPUX command
can be used.
3.1.3.1 Application Variables

SNML_HOME
Root directory of 1354RM product installation tree. The directory must exist
before installation.
The directory must have snml as owner and dba as group and its group write
access enabled (i.e. rwxrwxrx)
HOST_TYPE
It specifies if the host is an Information Manager (IM), with a complete 1354RM

installation, or an User Service (US), where the User Interface Application only
is installed. In the former installation type the database is created and agents
can be started, in the second type can be started User Interface Application
only, that are connected with a remote database.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
In a multiworkstation installation only one can be defined as

Information Manager. In the following chapter this workstation will be
referred as the IM host.
MIB
Meaningful for IM configuration only.

This variable specifies if the old 1354RM database must be saved or not. Its
values can be NEW (create new DB), OLD (save the current DB or recover
it from an old installation directory) or REC (recover DB from backup).
NEW :
using this option the customize procedure will create
a new empty DB.
OLD :
using this option the customize will copy the old DB
in the new directory (if the new installation is
performed on a new installation tree) or keep the old
DB (if the installation is performed on the old
installation tree).
REC :
this option should be used after a disk failure that
causes the reinstallation of 1354RM application.
The customize procedure will not create a new DB in
order to save the mirrored DB information to permit
the recover of DB from an incremental backup.
SNML_MIRROR

This variable specifies the directory that contains the database mirrored data
and Oracle Archive Log data.
ED
N.B.
It is mandatory that $SNML_MIRROR and /backup/snml

directories are completely disjointed. It is important that the
mirror directory is placed in an independent tree regards the
/backup/snml directory, otherwise some operations will fail (e.g.
during restore the redolog file will be overwritten).
N.B.
In order to support properly 1354RM backup and restore features,

this mirror directory and the /backup/snml directory must be created
on a different physical disk than the one where 1354RM product
has to be installed.
03
957.130.882 U

198
22 / 198

3.1.3 1354RM Installation Environment Variable Definition

DIRECTORIES ALLOCATION
Configuration with two disks
SNML_HOME
SNML_MIRROR
/backup/snml
Figure 1. Example of directories allocation with at least two physical disks

NTWDOMAIN

This variable specifies the identifier of the network domain handled by the
1354RM (by default the variable value is 1).
IM_SERVER
Meaningful for US configuration only.

This variable specifies the hostname of the IM workstation.
REMOTE_SERVER

This variable has to be set to allow the transfer of all 1354RM backup to a remote
server. This server must be a 1354RMIM workstation. These two 1354RM
system must to have identical value of the variables that specifies the Oracle
root directory (ORACLE_HOME) and the RMDB Mirror directory
(SNMLMIRROR); moreover the directory /tmp must to have enough space to
take up the gzipped backup transfer.
AC_INFO_FLAG

This variable specifies if the old AC_INFO directory must be saved or not. Its
value can be YES (recover the old directory) or NO (create new directory).
CNM_FLAG
If this variable is set to YES two CNM (Customer Network Management)

operators will be defined [see paragraph 6.3.3.4] in the system.
3.1.3.2 Oracle DB Variables
1AA 00014 0004 (9007) A4 ALICE 04.10
In the following the environment variables that have to be defined to allows the installation procedure to
configure in the proper way the Oracle database are listed.
ORACLE_HOME
This variable specifies the Oracle root directory.
DB_SIZE

It indicates the 1354RM Oracle database size. Possible values are small,
medium (default) and large.
ED
03
957.130.882 U

198
23 / 198
The following environment variables are used to configure properly HPOV during the 1354RM installation
procedure.
AGENT_REGISTRATION
It specifies if the agent LRF file static registration must be performed during the
1354RM installation phase. Its values can be yes (perform the static
registration default) or no (do not perform the static registration).
3.1.3.4 Operating System Variables
PRINTER
This variable specifies the default system printer.
To enable the printer functionality in the RM help the Iview*printerConfig resource must be defined in
$XAPPLRESDIR/$LANG/Iview file. This resources is a semicolon separated list of comma separated
tuples giving printer network names.
a)
b)
c)
d)
Login as snml user and execute:

$ vi $XAPPLRESDIR/$LANG/Iview and press [Enter]
type /printerConfig: press [Enter]
insert a line (not commented) related to your printer (for example):
Iview*printerConfig: hplj75, LaserJet75;
to configure more than one printer, divided the description lines with |;
save and quit the file pressing [Esc] and typing :x! and [Enter].
TAPE_SERVER

This variable specifies the host to which the tape is connected. Its default value
is none and it means no tape driver is installed and, when the backup is
performed, data are saved on disk only.
If the tape server is local to the IM workstation, the host name of IM workstation
has to be indicated.
If the tape server host is different from the IM one, on the tape server host the
snml user must be defined and in its home directory a .rhosts file has to exist
with an entry composed as the following:
<IM host name>
1AA 00014 0004 (9007) A4 ALICE 04.10
X_CONSOLE
ED
snml

This variable specifies the name of the workstation that will be used as console
in a plant where a server has been adopted.
03
957.130.882 U

198
24 / 198

3.1.3.3 HPOV Variables

3.2 Installation of Patches

In the following you can find the procedure to install a 1354RM patch. A patch can be installed only if the
related delivery has been already installed.
a)
Shutdown the 1354RM system all user service manager instances (ovw, browser and mngAgent).
Since the 1354RM patch installation performs a reset of OVwDB, no maps will be present at
the end of installation. Its mandatory to save the maps to be kept using DNM application.
b)
Exit from normal user CDE space and login again as root user in CDE login form.
c)
Change current directory to the SNML installation root and extract install_patch file from 1354RM
patch package.
# cd <yoursnmlinstroot>
# gunzip d c <1354RM...your tar file gzipped> | tar xf ./etc/install_patch
d)
Execute the install patch script running the following commands:

# ./etc/install_patch <1354RM...full path name tar file gzipped>
N.B.
In case of more patches you must execute the install_patch script one time only at the end
(after the gunzip of all patches).
The procedure stops the control/system/database (IM only) and starts the install_patch on an
independent window, during this operation the files that have been corrected and that have been
included in the patch package will overwrite the old bugged ones.
e)
To activate all the CDE configuration changes it is recommended to exit from the current CDE session
and log in again to use 1354RM product.

3.2.1 RM DB resizing after installation patch
If you want to change the storage parameters of the Oracle database after the installation of a patch,
please execute the following steps:
a)
b)
c)
execute a backup of the RM database and the AS database (only if you want to save the AS data)
execute the step of the chapter [8.1]
execute the following command
1AA 00014 0004 (9007) A4 ALICE 04.10
# mv /backup/snml/Ntwk/tablespaces.dat /tmp/tablespaces.dat
d)
ED
execute the restore.
03
957.130.882 U

198
25 / 198
At the end of 1354RM installation in the file /usr/snml/conf/<hostname>/ntwDomains is described the

default Network Domain (with the Identifier specified in env_snml file) that will be used by RM user
interface. The information will have the following format:
loc <n>
on RMIM workstation
far <n> <hostname>
on RMUS workstation
where <n> is the Network Domain Identifier and <hostname> is the name of the host where the
relevant RMIM is running.
N.B.
In a ntwDomains file a loc line can only exist.
In order to enable the RM User Interface to connect to different Network Domain the user shall insert
manually in the ntwDomains file a file with the far format and execute the following commands:
# /usr/snml/etc/install_patch
and if AS is installed:
# /usr/snml/etc/us_config_A1330
The /etc/hosts file must contain the new added RMIM workstation address and the
AGENT_REGISTRATION environment variable, in /usr/snml/etc/env_snml file, must be set to yes.
When the MultiIM configuration is enabled, opening an empty map in NetView will present a dialog box
to the user in order to associate a Network Domain to the map (info taken into account when normal
operation are executed), on the other side opening the Browser application a MultiRM icon is presented
as root object and, with the Main related item operation, the user can view all the defined Network
Domains.
To have got access to the whole network domain, in a multimaster network configuration (i.e. 3 IM WSs
and 1 USM WS), it is necessary to do the following steps:
1AA 00014 0004 (9007) A4 ALICE 04.10
1)
2)
3)
ED
Add user1 on USM and IM_1 (assuming you are working on USM ws);
Add the USM ws console on all IM WSs by Add console function (working on each IM);
Add the user1 on IM_2 and IM_3 by Add Operator function (working on each IM).
03
957.130.882 U

198
26 / 198

3.3 MultiIM Configuration

4 HPOV DM CUSTOMIZATION
4.1 PMD Configuration
The adopted stack for the communication between RMUS and RMIM processes (RM F interface) is the
RFC 1006 (OTS light). With RM delivery is distributed a file pmd.lrf (in the directory /usr/snml/lrf/OV)
where HPOV CI configuration parameters are set by 1354RM. These parameters specify the size of
stacks or the timeout in seconds to wait for response to confirmed operations. This file is automatically
registered in place of the default pmd.lrf file by the customize and customize_patch procedures. If the
system administrator wants to change these values, he has to execute the following procedure with root
user privileges:
stop the 1354RM system.

deregister old pmd registration file
# $OV_BIN/ovdelobj /usr/snml/lrf/OV/pmd.lrf
change values in /usr/snml/lrf/OV/pmd.lrf
register new pmd registration file
# $OV_BIN/ovaddobj /usr/snml/lrf/OV/pmd.lrf
stop and restart HPOV to make actual the new PMD configuration values
# $OV_BIN/ovstop
# $OV_BIN/ovstart
Values specified in pmd.lrf files are:
SACSE;O1200, SCMIP;O1200;I5000;Q5000, SXMPV7;O1200;I5000;Q5000
1AA 00014 0004 (9007) A4 ALICE 04.10
The previous options change for CMIP and XMPV7 stack:

O : the timeout value (in seconds) for confirmed requests;
Q : the unsent operations queue size;
I : the active confirmed operations queue size.
ED
03
957.130.882 U

198
27 / 198
4.2.1 Remote Event Sieve configuration

This configuration is based on a configuration file (/usr/snml/conf/im_host_conf), where host names of
workstation are described giving also their product supported (EML, AS or RM). This file is automatically
used by applications to create Remote Event Sieve in order to enable sending events only on workstations
really involved in the event handling.
The file is update in automatic way by the RM and AS installation procedures. When a new EMLs
workstation is installed the following procedure has to be executed to update the configuration file:
$ /usr/snml/etc/update_nml_sieve
N.B.
WX host name must be removed manually from im_host_conf file, since no Event Forwarding
Discriminator shall be created on WX.
N.B.
In order to allow the interworking between HPUX 10.10 / HPOV 4.2 workstations and
HPUX 9.5 / HPOV 4.01 ones, the user have to modify manually the im_host_conf file
adding after the name of HPUX 9.5 workstations the tag DM40 (please, note that as
separator between hostnames and tag must be used one or more spaces, the <TAB>
character is not managed).
Please note that each time the user executes a customize, customize_patch, install_A1330 and
deinstall_A1330 procedures the im_host_conf file is automatically rebuilt, so the DM40 tags
are lost.
4.3 Object Registration

In the directory $NXNL_PRD/lrf are present the local registration files, used by the installation procedure
to register the objects managed by agent process. A lrf file exists for each agent and has the same agent
name with the .lrf tag.
1AA 00014 0004 (9007) A4 ALICE 04.10
In directory /usr/snml/etc are present two procedures: addobj and delobj. These procedures have to be
executed with root user privileges and register (addobj) and deregister (delobj) all the 1354RM local
registration files.
ED
03
957.130.882 U

198
28 / 198

4.2 Installation on Distributed Platform
5 IPC RESOURCES CONFIGURATION
1AA 00014 0004 (9007) A4 ALICE 04.10


Agent processes of 1354RM product use some IPC resources that are specified by the following symbols
defined in $NXNL_PRD/.nxnlenv (in brackets default values are specified):
ED
1)
Queues : Five queues are used and their identification numbers are specified by
TOPMNGQUE (62), TRSMNGQUE (63), ALRMGRQUE (64), PMCONSISTQUE (65) and
QNNERQUE (90) symbols.
2)
Semaphores : A semaphore is used and its identification number is specified by ALRMGRSEM

(64) symbol.
03
957.130.882 U

198
29 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.882 U
198
30 / 198

6 USERS MANAGEMENT
6.1 1354RM Operators Managing
In the 1354RM customized CDE environment, a 1354RM subpanel is defined in the CDE panel from which
is possible to start 1354RM application (see 6.2.2).
To handle 1354RM operators data on US or IM node the system administrator must:
a)
b)
select in 1354RM subpanel the SMF Button,

select the Operator Admin application, by means of this functionality the System Administrator can:
1)
2)
3)
4)
5)
6)
7)
8)
Add a new operator;

Remove an operator;
Change an operator password;
NAD Management;
List all the defined operator;
List successful login;
List unsuccessful login;
List the currently logged in operator.
1AA 00014 0004 (9007) A4 ALICE 04.10
This procedure handle the users on all the workstation belonging to the 1354RM distributed architecture.
ED
03
957.130.882 U

198
31 / 198
Five user profiles are defined: OS Administrator, Administrator, Constructor, Path Builder & Look Only
Users. This profiles specify the operations that an operator can execute. In order to define the correct FADs
five environments have been defined specifying five versions for:
HPOVw Registration files.

CDE initialization files.
X Application Resources directory.
Browser Toolbar configuration files.
Unix user profile file (.profile).
6.2.1 HPOVw Users Profile for NetView application

In the SNML delivery five HPOVw user profiles are defined to support the NetView application.
These profiles are defined by a set of registration files that are stored in the following directories:
/usr/snml/conf/users/OSadmin/OVwRegDir
for OS administrator user
/usr/snml/conf/users/admin/OVwRegDir
for Administrator user
/usr/snml/conf/users/Constructor/OVwRegDir
for Constructor user
/usr/snml/conf/users/PathBuilder/OVwRegDir
for Path Builder user
/usr/snml/conf/users/LookOnly/OVwRegDir
for Look Only user
The registration files for OS administrator, administrator and constructor enable the user to perform all
NetView operations (Network Construction, Save Map in DNM database, Create Virtual Entity, etc.).
The registration files for Path Builder enable the user to perform a limited subset of the NetView operations,
that is to synchronize map with existing data, to get distributed map from DNM database, starting event
logger or browser application.
The Look Only user registration files enable the user to perform get operations only.
In order to support NAD functionality in NetView application some constraints to its synchronization
process should be defined. The constraints are specified by means of a synchronization level that is given
as an input parameter to the NetView application. It is specified in the file nxnlOus of the relevant user in
the command line (by default all the profiles have no constraints defined):
Command Initial Restart Shared $NXNL_PRD/bin/nxnlOus syncroLevel 0
1AA 00014 0004 (9007) A4 ALICE 04.10
The system administrator can specify, if it is necessary, the synchronization level for a whole users profile
modifying the syncroLevel option value in the command line.
The synchronization levels that can be specified are:
0 : no restrictions applied;
1 : constraints applied to network level;

(not meaningful for the current delivery)
2 : constraints applied to subnetwork level;
3 : constraints applied to elementary topology level only;

(nodes inside sbn are showed)
4 : constraints applied to node level;

(nodes contained in ET and sbn)
The NetView synchronization process will align the characteristics of all the object already present in the
map and it will add in the map new discovered topological object contained in the constraints level
previously specified.
ED
03
957.130.882 U

198
32 / 198

6.2 User Profiles
6.2.2 CDE Customization

Five CDE customization files are defined:

/usr/snml/conf/users/OSadmin/dt/C/dtwmrc
for OS administrator user
/usr/snml/conf/users/admin/dt/C/dtwmrc
for administrator user
/usr/snml/conf/users/Constructor/dt/C/dtwmrc
/usr/snml/conf/users/PathBuilder/dt/C/dtwmrc
/usr/snml/conf/users/LookOnly/dt/C/dtwmrc
for Look Only user
From the vertical subpanel these users can start the TMNOSs, System Management Features, Alarm
List, Browser and NetView (ovw) applications. It is also available a customized popup menu (associated
to the right mouse button) that contains functions to start the same applications.
From the horizontal panel the OS administrator & administrator can get the UNIX access, open a File
Manager, start the Mailer and functions to print terminal hardcopy.
From the horizontal panel the Constructor & Look Only users can start the Mailer and functions to print
terminal hardcopy.
From the horizontal panel the Path Builder user can open a File Manager, start the Mailer and functions
to print terminal hardcopy.
The print terminal hardcopy functions use the standard PRINTER variable (that can be defined for all users
in .nxnlenv file) to determine the printer device to use, that must be able to print ASCII text and Hardcopy
postscript.
6.2.3 Unix Shell Profile (.profile)
Meaningful for IM configuration only
1AA 00014 0004 (9007) A4 ALICE 04.10
Five .profile template files are defined in the 1354RM installation that are used by the OperatorAdmin
procedure to customize the .profile for 1354RM users. These files are:
ED
/usr/snml/conf/users/OSadmin/profile
for OS administrators user
/usr/snml/conf/users/admin/profile
for Administrators user
/usr/snml/conf/users/Constructor/profile
/usr/snml/conf/users/PathBuilder/profile
/usr/snml/conf/users/LookOnly/profile
for Look Only user
03
957.130.882 U

198
33 / 198
The combination between a UNIX user and the workstation on which he is loggedin is identified in RM
by the initiators concept (see also X.741).
RM allows to define and modify the rights of each initiator to execute the functionality foreseen by his User
Profile (see 6.2) on group of network objects like group of paths, NAPs etc.
This definition implies that a UNIX operator can have different rights depending on the
workstation used.
A command allowed by the User Profile can be denied by the Access Rules either completely or
only on specific objects. The Users FAD is identified by the combination of the Users Profile
(see 6.2) and the access rule associated to his initiator (see 6.3.3.1).
The Access Rules are taken into account only by the Network Managemnent functions. SMFs
depends only by Users Profile.
UNIX USER
List of WS
RM INITIATOR
The Access Rules used to check the rigth of a given Initiator on Network Resources (e.g. paths, NAPs,
topologies...) are based on an attribute related to each single resource.
This attribute is called NAD. NAD may assume only single values (not set of values !).
1AA 00014 0004 (9007) A4 ALICE 04.10
The currently defined Access Rules allow to define initiators beloging to the following categories :
ED
administrators able to work on all the resources independently from their NAD
03
957.130.882 U

198
34 / 198

6.3 Network Access Domain Management

non VPN initiators able to see all the resources and to operate only on resources not related
to VPN operators. In this category is possible to define Network Constructor and / or Path
Builder Initiators.
VPN initiators able to operate on and to visualize only assigned resources (with possible
exceptions on free resources see 6.3.3.1). These initiators can normaly perform only path
configuration operations.
Look only initiators able only to see Network Resources and not to operate on them
6.3.1 Adding an RM Operator

A new operator can be added using SMF applications. The following functions of the Operator
Administration facility shall be used: <Add Operator> & <Network Access Domain>.
Using the Add Operator function it is possible to define a new UNIX user on a specific workstation. In the
Add operator function is mandatory to select the User Profile (i.e. the set of Menus displayed for that user
on the User Interface) and the related Initiator (see 6.3.5).
For example a Unix user related to the Path Builder user profile can be mapped with the default Non VPN
Initiator.
If two UNIX users are mapped to the same Initiator they will share the same Network
Resources and capabilities.
If the created user shall be related to a not existing Initiator, it is mandatory to edit, manually a file (see
6.3.2).
Once the initiator is created (if necessary), it has to be mapped to the user by means of the Network
Access Domain SMF function. The list of users is presented with their currently defined Initiators.
Selecting the user it is possible to change its initiator using the popup menu. In the popup menu
all the defined initators are listed.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Access Rules are described in paragraph 6.3.3.1 & 6.3.3.2.
ED
03
957.130.882 U

198
35 / 198
The initiator information are defined in the file:

/usr/snml/ac_info/initiators.ac.<n>
where <n> is the network domain of the current RM.
Each Initiator is identified by a line in the initiator file.

An Initiator is specified by :
an integer identifier (it must be unique in the file);

The Initiator Identifier must be given according to the following rules:
Non VPN Initiators must have Identifier less than 300
VPN Initiators must have Identifier greater than 300
The identifier 0 (zero) is reserved (it is used to identify free resources).
The Identifier 301 is reserved for 1354NN (when present)
a Name (it must be unique in the file);

The Initiator Name is added to the possible values of the NAD attribute. The NAD attribute
is used to mark Network Resources (using the change NAD command) and to evaluate
Access Rules.
a comma separated list of access rules. These rules can be:
embedded rules;
customer rules (they are a redefinition of the embedded rules in terms of scheduling).
An example of the file follows:

#RM initiator : InitiatorName
50
: Path Administrator
55
: PathWatcher
: Rules
: AC_R_PADMIN
: AC_R_PATHRO
In the example, the Initiator 50 is called Path Administrator and is mapped to the rule AC_R_PADMIN.
This access rule allows all the operations on paths (see 6.3.3.1).
In the Rules field more than one rule can be specified.
1AA 00014 0004 (9007) A4 ALICE 04.10
The rules are evaluated sequentially and in case of duplication or inconsistency only the first is
taken into account.
ED
03
957.130.882 U

198
36 / 198

6.3.2 Defining a new RM Initiator

6.3.3 Access Rules description
RM INITIATOR
Id
Name
Customer Rules
List of Rules
Embedded Rules
6.3.3.1 Embedded Access Rules

The rules define the access of an initiator to the network resources.
The possible Access Rules belong to a predefined set. The mapping of Initiator and rules is not completely
free but some logical limitations exist.
The available rules are (more datails are present in 6.3.3.3) :
AC_R_SNML: RM Administrator.
Its able to perform all the operations without any limit.
It must be assigned very carefully because an Initiator with this capability can modify
operations performed by 1354NN.
It is not usefull to compose this rule with any other one.
N.B.
This rule is mapped by default on the RM Administrator snml. It is

mandatory do not change the snml initiator.
AC_R_PADMIN: Path Administrator.

It can manage paths and releated resources (NAPs and LCs) not explicitely assigned to
VPN domains.
This rule can be composed with AC_R_TOPMAN and/or AC_R_PAYMAN in order to
achieve the needed level of functionality.
1AA 00014 0004 (9007) A4 ALICE 04.10
the AC_R_PADMIN rule cannot be used for VPN Initiator.
ED
03
957.130.882 U

198
37 / 198
AC_R_PATHALL: Path Allocator.

It can allocate/deallocate paths and manage the resources (NAPs and LCs) not explicitely
assigned to VPN domains.
This rule can be composed with AC_R_TOPMAN and/or AC_R_PAYMAN in order to
the AC_R_PATHALL rule cannot be used for VPN Initiator.
AC_R_PATHRO: Path Watcher.

It can only get paths and NAPs.
the AC_R_PATHRO rule cannot be used for VPN Initiator.
AC_R_TOPMAN: Topology Manager.

It can operate on topologies in order to modify the network.
This rule can be composed with AC_R_PADMIN and/or AC_R_PAYMAN in order to
the AC_R_TOPMAN rule cannot be used for VPN Initiator.
AC_R_PAYMAN: Payload Manager.

It can operate on payload configuration.
This rule can be composed with AC_R_PADMIN and/or AC_R_TOPMAN in order to
the AC_R_PAYMAN rule cannot be used for VPN Initiator.
RVPN: Restricted Virtual Private Network Operator.

Its able to create, view, modify paths only using resources (NAPs & LCs) assigned to his
NAD.
It can be assigned only to VPN Initiator.
VPN: Virtual Private Network Operator.

As RVPN except that the routing can be done also on free LCs (Security Label=0).
This Rule is used also for 1354NN activities.
It can be used only for VPN Initiators
EVPN: Enhanced Virtual Private Network Operator.

As VPN except that also free NAPs can be used for path setup.
It can be used only for VPN Initiators
1AA 00014 0004 (9007) A4 ALICE 04.10
No check is performed to avoid the assignment of a VPN rule to non VPN Initiators and
viceversa.
AC_R_NN: NN Operator.
As VPN except that you can assign free objects too (path,trail,lc and NAP).
ED
03
957.130.882 U

198
38 / 198


6.3.3.2 Customer Access Rules

A customer Rule is a redefinition of an embedded access rule only in terms of Daily and Weekly
Scheduling.
The customized rules must be defined editing the /usr/snml/ac_info/scheduling.ac.<n> file (where <n>
is the Network Domain Id of the current RM): for each new rule a new line shall be added that contains
the corrispondent embedded rule and the time scheduling.
The information included in the file is :
Name of the Customer Rule
Daily Scheduling: its the validity start & end time of the Rule. Starting and Ending Time has the
format hh.mmhh.mm (hh = hour, mm = minute) and shall be expressed in UTC (Greenwich Time).
An empty value enables the rule in the whole day.
Weekly Scheduling: it contains the days of the week for which the daily scheduling applies. Possible
values are in the range from 0 (Sunday) to 6 (Saturday). An empty value enables the rule in all the
days.
Embedded Rule: it is the name of the embedded rule referred in term of functionalities
An example of the file follows:

#Customer Rule : Daily Scheduling : Weekly Scheduling
AC_R_NEWPADMIN : 08.0019.00
: 1 , 2 , 3, 4 , 5
: Embedded Rule
: AC_R_PADMIN
Customer rules can be inserted in the Initiator definition file (see 6.3.2).
6.3.3.3 Default mapping between Access Rules and Object Class
1AA 00014 0004 (9007) A4 ALICE 04.10
Legend for ownership :
O:
Owned objects (Security label equal Initiator Id)
OF :
Owned or free objects (Security Label equal Initiator Id or 0 )
N:
Not VPN objects (Security label <=300)
A:
All objects
Gray :
Disabled by default rules
ED
03
957.130.882 U

198
39 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
Table 4. Access Rules Description

Operation
P
A
T
H
allocate, deallocate,
ED
Notes
RULE
R
V
P
N
V
P
N
E
V
P
N
P
T
H
A
D
M
P
T
H
A
L
L
implement, deimple- O
ment, commission,
decommission, add/
remove protection.....
get
S
N
M
L
N
N
O
P
Add / remove leg
For the add leg, the check

is performed also on the
NAP (see Use in Path)
Create
The initiator ID is taken as

NAD of the created object.
In the redolog, the path
creation is followed by a
change of NAD in order to
be able to replicate the final result in term of NAD.
The check to allow or not a
path creation is made on
the path and on the specified NAPs; the path is
created if the NAPs can be
related to the path (see
NAP class)
Change Owner
O
F
It is the action to change

the NAD. The operation is
registered in the redolog
Delete
The check is done on the

path and NOT on the used
NAPs (unset of the pathPtr
attribute)
P
T
H
R
/
O
T
O
P
P
A
Y
L
O
A
D

C
L
A
S
S
03
957.130.882 U

198
40 / 198


N
A
P
L
C
remove nap
O
F
get
O
F
change owner
O
F
The operation is register
Use in path (create a O

path or add leg)
O
F
The command is not present at the user interface

but is embedded in create
path and add leg. It is defined as set on pathPtr attribute
Change owner
O
F
The command is registered in the redolog.

As a consequence of this
operation the LC is also
moved from the original
Routing Link bundle to the
appropriate one. A new
routing links is created if
needed.
Use in path
O
F
O
F
O
F

but is embedded in path or
trail allocation. It is defined
as set on the belongTrailId
attribute.
The allocation algorithm

during the search only
uses the Routing Links
matching the condition for
LCs
Delete
get
1AA 00014 0004 (9007) A4 ALICE 04.10
Configure Payload
ED

but is embedded in the
payload configuration of
physical connections and
HOTrails.
A
Only for HOTrails
03
957.130.882 U

198
41 / 198
T
R
A
I
L
Change owner
The command is registered in the redolog
Configure Payload
Create
It is the creation of the HO

Trail
Remove
It is the action to remove

the HOTrail; as a consequence a payload deconfig. is started.
T
R
A
I
L
Set Qnn Info
T
O
P
O
L.
/
P
H
C
O
N
N
Create
It is the operation to activate topologies, Nodes,

physical Connection (action)
Implement
It includes the configuration at HO
Deimplement
Remove
Start Network Activ.
Get
Upload NAPs
Configure Payload
Get
M
S
S
P
R
I
N
G
1AA 00014 0004 (9007) A4 ALICE 04.10
O
F
ED
Operate on protection
blocks
Get
A
Operation are : modify the
WTR,
force,
manual,...synchronize
03
957.130.882 U

198
42 / 198



C
T
P
/
T
T
P
Change defaults for

UPA propagation
P
D
H
P
O
R
T
Configurate PDH port
It is the action to modify the

configuration of a transmux board
It is the action to loopback

a PDH port for testing. The
action can also be started
on a NAP but only as an
extension at US level.
Configuration Download
It is the action to enable /

disable the configuation
download from RM to NEs.
The check is performed
also for operation started
on single NEs
Start Audit
It is the action to start Auditing differences between

NE and EML view. The
check is performed also on
operations started on
single NEs.
Get
O
T
H
E
R
S
1AA 00014 0004 (9007) A4 ALICE 04.10
Get
Get
Operations
R
V
P
N
ED
Loop Back
Get
E
M
L
V
P
N
E
V
P
N
P
T
H
A
D
M
P
T
H
A
L
L
P
T
H
R
/
O
T
O
P
P
A
Y
L
O
A
D
S
N
M
L
Eventually restricted by
FAD at the user Interface
Restricted by FAD implemented at the user interface
N
N
O
P
03
957.130.882 U

198
43 / 198
New rules have been added to manage Performance Monitoring activities. They are described in the
following paragraphs.
AC_R_PMSNML: Performance Monitoring SNML
PMSNML is the rule allowing full capability of managing PM domain objects. This rule allows to operate
on all the PM Domain data regardless from the ownership (NAD) of PM data, paths and trails
AC_R_PMVPN: Performance Monitoring Virtual Private Operator
PMVPN is, in the PM domain, the equivalent of the VPN rule in the path management domain. This rule
allows to operate / visualize PM data, put under monitoring path or trail only related to a given NAD.
N.B.
If an operator is the owner of a measure then he is the owner of the pmTp and the pmTransport
of the measure.
AC_R_PMADMIN: Performance Monitoring Administrator
PMADMIN is, in the PM domain, the equivalent of the PADMIN rule in the path domain. This rule allows
to fully operate on PM domain related to non VPN measures, PM transport etc. and visualize all
the PM data even if belonging to VPN domains.
Non VPN domain is the set of all RM objects with nad<300.
AC_R_PMRO: Performance Monitoring Read Only
PMREAD is the read only rule on PM domain. This rule allows to visualize all the PM related
information regardless to the ownership.
AC_R_PMVPNRO: Performance Monitoring Read Only VPN
PMREAD is the read only rule on a given NAD. This rule allows to visualize the PM related information
related to a given NAD.
6.3.3.5 Default mapping between Access Rules for PM and Object Class
1AA 00014 0004 (9007) A4 ALICE 04.10
Legend for ownership :
: Owned objects (Security label equal Initiator Id)
OF : Owned or free objects (Security Label equal Initiator Id or 0 )
: Not VPN objects (Security label <=300)
: All objects
Gray
ED
03
:Disabled by default rules
957.130.882 U

198
44 / 198

6.3.3.4 Embedded Rules for PM
1AA 00014 0004 (9007) A4 ALICE 04.10

Table 5. NAD / FAD

C
L
A
S
S
Operation
M
E
A
S
U
R
E
Notes
RULE
P
M
V
P
N
P
M
A
D
M
I
N
Create
Delete
Set
Activate, Stop and Consistency
Correlate Transport to Measure
This action correlates a Measure to

a Path or Trail.
The check is performed on the
Path/Trail too.
Correlate Tp to Measure
The check is performed on the Tp

(nap, cap, ctp) too.
Correlate Report to Measure
The check is performed on the report (Counter Report or TCR) too.
C
O
U
N
T
E
R
Create
Delete
Set
R
E
P
O
R
T
Get
ED
P
M
V
P
N
R
O
Get
P
M
R
O
P
M
S
N
M
L
This is the first step to start a measure session.
See the note about this action in the

Measure class context.
03
957.130.882 U

198
45 / 198
T
C
A
Create
Delete
P
r
o
f
i
l
e
Set
Correlate pmTp To TCA
T
C
R
Create
Delete
Set

Measure class context.
Create
This command is not present at the

user interface. It is a consequence
of the Correlation of a Path/Trail to
a Measure.
Delete
Create
Delete
Correlate pmTp To TCA
P
A
T
H
N
A
P
Get
Get
P
M
T
R
A
N
S
P
M
T
P
Get
1AA 00014 0004 (9007) A4 ALICE 04.10
Get
ED
A
The check is performed on the
pmTp too.
A
This command is not present at the
user interface. It is a consequence
of the Correlation of a Tp to a Measure
A
TCA class context.
03
957.130.882 U

198
46 / 198

Table 5. NAD / FAD
1AA 00014 0004 (9007) A4 ALICE 04.10

Table 5. NAD / FAD
T
R
A
I
L
O
N
A
C
T
P
/
T
T
P
OF
N
A
ED
03
957.130.882 U
198
47 / 198
A set of Initiators is provided with 1354RM delivery. They represent the most typical operator profiles for
the network management.
Initiator Name
Rules
Description
Free Pool
No Rules
Used to define composite rules.

Not mapped to any user.
RM Administrator
SNML
All operations allowed.
Advanced Operator
PAYLOAD
PTHADM
Network Constructor
TOP
PTHADM
PAYLOAD
Path Watcher
PTHR/O
User profile for readonly operations on path trail.
Path Administrator
PTHADM
Operator for working on path.
Path Allocator
PTHALL
Path create and allocate/deallocate allowed.
1354 NN
VPN
Qnn Agent.
RVPN Operator
RVPN
It is the restricted Virtual Private

Operator.
VPN Operator
VPN
It is the Virtual Private Operator.
EVPN Operators
EVPN
It is the enhanced Virtual Private Operator.
Payload Manager
PAYLOAD
cnm_pathbuilder
VPN
PMVPN
cnm_lookonly
PMVPNR/O
6.3.5 Default mapping between User Profiles and Initiators

User Profile related to an operator has impacts on User Interface by hiding or showing some action menus
(see 6.2).
1AA 00014 0004 (9007) A4 ALICE 04.10
The correspondence between User Profiles and Default Initiators is described in the following table.
User Interface Profile
Default Initiators
OS Administrator
RM Administrator
Administrator
Network Constructor + System Features
Constructor
Network Constructor
Path builder
Path Administrator or EVPN or VPN or RVPN
Path allocator
Path Allocator
Look Only
Path watcher on whole RM
cnm_pb
cnm_pathbuilder
cnm_lo
cnm_lookonly
ED
03
957.130.882 U

198
48 / 198

6.3.4 Delivered set of Initiators

7 PROCESS MONITOR & CONTROL

7.1 Maintenance Commands
1354RM Agents and Oracle database can be handled using mngAgent utility. It can be used in a graphic
or not graphic mode. Not graphic mode is useful if you want to use it in a shell command (e.g. system
startup file).
Graphic Mode: Run by snml user the following commands:
$ DISPLAY=<your_node_name>:0.0
$ export DISPLAY
$ mngAgent
Start Oracle database before starting 1354RM system.
Not Graphic Mode: Run by snml user the following commands:
a)
Start or stop database instance:

$ mngAgent [ startup | shutdown ] database
The 1354RM system must be stopped in order to shutdown database instance.
b)
Start or stop 1354RM system:

$ mngAgent [ startup | shutdown ] system
The 1354RM system can be started only if database instance is already active.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
The startup operation starts only the agents belonging to the currently set run level.
c)
Start or stop any 1354RM agent:

$ mngAgent [ startup | shutdown ] <agent_name>
Agents can be started only if database instance is already active and if the agent itself belong to the
current runlevel.
d)
Enable or disable 1354RM control function:

$ mngAgent [ startup | shutdown ] control
e)
Check 1354RM system status:

$ mngAgent check
The command set the Unix system variable ? with the status code of 1354RM system (0 = Run,
1 = Wrong, 2 = Off)
f)
Set the current run level:

$ mngAgent set_run_lev <run_level_number>
The command change the current run level to the one specified, stopping running processes not
belonging to the selected run level and starting stopped processes belonging to the selected run
level.
g)
Get the current run level:

$ mngAgent get_run_lev
The command set the Unix system variable ? with the currently set run level.
ED
03
957.130.882 U

198
49 / 198
7.2 Integration of IM Agent in 1354RM PMC
Other Alcatel network applications can enable 1354RM PMC to start and to control their own Agents. To
do this a file named mng_agent_conf must be placed on the installation home directories of the involved
applications in which they have to specify the characteristics of their agents. In particular in this file must
be specified the agent parameters, if the process has child processes (and if it has, their names), where
is placed the Agent trace file, etc..
When a mng_agent_conf is modified or a new one is delivered, in order to notify to PMC the modifications
the script procedure:
# /usr/snml/etc/update_network
have to be executed (as root user) to regenerate the PMC configuration file (see also 9.1).
For each process the following parameters have to be defined:
agent_name : name of controlled agent

agent_type : it specifies the agent handling type. It can be set either as general (for process
managed as normal Unix processes ) or hpov (for process managed by means of ovstart and
ovstop HPOV function).
agent_image : (this entry is meaningful only for agent with agent_type = general)
absolute path name of the executable agent image. It is also possible to indicate script file that
starts executable image inside if it uses exec Unix command.
agent_params : (this entry is meaningful only for agent with agent_type = general)
agent parameters used by executable image, or script, in the startup phase. In the parameters
description spaces are replaced by commas.
agent_child (n lines) : child processes name, number of its instances that are controlled by PMC
and max memory size for each instance (this has the same meaning of the agent_max_size)
parameter. A new line exists for each agent child processes.
agent_start_wait : (this entry is meaningful only for agent with agent_type = general)
timeout (number of seconds) to wait before PMC can check the correct agent initialization after
its startup.
agent_shut_wait : (this entry is meaningful only for agent with agent_type = general)
timeout (number of seconds) to wait before PMC can check the correct agent termination after
its shutdown.
agent_mon_interval : number of seconds between two consecutive polling operation on the
agent.
agent_max_size : maximum memory size (in Kb) that can be reached by the agent. If this value
is reached and the monitor function is enabled an automatic agent shutdown and restart is
executed, if it is reached but the monitor function is disabled, the agent is displayed with the
WRONG status.
agent_trace_location : directory or file containing the trace information associated to the
process.
agent_trace_default : it specifies the default trace file to be visualized, between the ones
displayed to the operator. Typically this multiple trace files selection is between agent trace file
and its child processes trace files.
agent_run_level : it specifies all run levels to which controlled agent belongs to.
agent_ps_info : name of controlled agent to use searching it into a ps ef list. This option has
to be specified only if this name is different from the one indicated
agent_actions_name : Ordering number and actions name for controlled Agent.
agent_actions_command : Ordering number and command for controlled Agent. In the
command description spaces must be replaced by commas.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.882 U

198
50 / 198

The relation between Action and command to be executed is done by means of the ordering
number.
Inside Action command scripts the following environment variables can be used:
$AGENT_PID
to indicate the actual agent process PID;
$AGENT_NAME
to specify the agent name.
$AGENT_CHILD_PIDS to specify the complete PID list of the agent children.
1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.
ED
03
957.130.882 U

198
51 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.882 U
198
52 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10

8 DATABASE MANAGEMENT
8.1 Database Creation
In order to create a new database the following procedure shall be executed:
$ $DB_ROOT/etc/create_db
After the database recreation you can perform a restore of network configuration, alarms and PM data
from a backup (if any).
ED
03
957.130.882 U

198
53 / 198
8.2 Database disk usage
The script must be run as snml administrator by running from a shell the command:
$ db_report
The script sends a mail containing the report to the snml administrator. The same report is also saved in
file /tmp/mailfile.out. Here follows an excerpt of such a report:
From snml Wed Apr
1 10:23:41 MET 1998
To: snml
FILESYSTEM PARTITIONING on tlvhfs
==============================================
Filesystem
kbytes
used
/dev/dsk/c0t6d0
1851289
935444
730716
avail %used Mounted on

56% /
/dev/dsk/c0t5d0
2049173 1451593
392662
79% /tmp_mnt/dktmn_21
MEMORY STATUS OF ORACLE INSTANCE dbsnml started from tlvhfs

==============================================
FREE EXTENTS IN ALL TABLESPACES

LEGENDA
bytes:
size of the file in bytes
used:
size of the allocated extents in bytes
free:
size of the free extents in bytes
file_name
tablespace_name
bytes
used
free
%free

data01.dbf
DATA
73400320
49414144
23986176 32.6785714
index01.dbf
INDEX_T
41943040
5183488
36759552 87.6416016
index02.dbf
INDEX_T
41943040
1114112
40828928
rbs01.dbf
RBS
8388608
7948288
system01.dbf
SYSTEM
15728640
8220672
temp01.dbf
TEMP
10485760
2048
97.34375
440320 5.24902344
7507968
47.734375
10483712 99.9804688
STORAGE ALLOCATED FOR ALL TABLE SEGMENTS

LEGENDA
size:
allocated extents in bytes
owner
table_segment
size
extents

SNML
AG
532480
SNML
CAP
266240
1054720
...
1AA 00014 0004 (9007) A4 ALICE 04.10
SNML
ED
TRANS
03
957.130.882 U

198
54 / 198

It is advisable to run periodically the script db_report, to check the use of disk space made by Oracle.
ALLOCATED EXTENTS TO ALL TABLES

tables_tot_size (bytes)
27447296
STORAGE ALLOCATED FOR INDEX SEGMENTS STORED WITH DATA
LEGENDA
size:
owner
index_segment
size
extents

SNML
COUNT_INDEX
15308800
SNML
PMLDST_INDEX
266240
UNIQUE_TRAIL_USERLABEL
266240
...
SNML
ALLOCATED EXTENTS TO INDEXES STORED WITH DATA

indexes_total_1 (bytes)
21964800
STORAGE ALLOCATED FOR INDEX SEGMENTS STORED SEPARATELY
LEGENDA
size:
owner
index_segment
size
extents

SNML
CAP_IDX1_INDEX
1054720
SNML
CTP_IDX2_INDEX
1054720
51200
...
SNML
PK_TRANPK_TRANCONNID
ALLOCATED EXTENTS TO INDEXES STORED SEPARATELY

indexes_total_2 (bytes)
6293504
STATISTICS FOR SCHEMA OBJECTS/1
LEGENDA
num_rows:
number of rows in the table
avg_row_len:
average length of a row in bytes
blocks:
blocks with data allocated to the table
empty_blocks: blocks allocated that contain no data

avg_space:
average free space (bytes) in an allocated block
(block size = 2048K)
1AA 00014 0004 (9007) A4 ALICE 04.10
table
num_rows avg_row_len
blocks empty_blocks
avg_space

AG
CAP
259
52
56
127
442
843
14
10
504
632
...
TRANS
ED
03
957.130.882 U

198
55 / 198
STATISTICS FOR SCHEMA OBJECTS/2

index:
name of the index
values:
number of leaf rows (possibly not distinct)
size:
sum of the lengths of the all leaf rows (bytes)
values: number of deleted leaf rows

size:
sum of the lenghts of deleted leaf rows (bytes)
blocks:
number of allocated blocks
(block size = 2048K)

index
values
size
values
size
blocks

CAP_IDX1_INDEX
COUNT_INDEX
52
1271
515
366968
7115386
7475
205
5571
...
UNIQUE_TRAIL_USERLABEL
130
It is also advisable to run periodically the script db_memory, to check the use of RAM memory made by
Oracle.
The script must be run as snml administrator by running from a shell the command:
$ db_memory
The script sends a mail containing the report to the snml administrator. The same report is also saved in
file /tmp/db_memory.out. Here follows an excerpt of such a report:
From snmlr50 Fri Nov
6 14:50:40 MET 1998
To: snml
Analysis of database memory bound to Oracle instance dbhhk started from tlvhhk
1 SYSTEM GLOBAL AREA
Total System Global Area
12785888 bytes
Fixed Size
47936 bytes
Variable Size
10157472 bytes
Database Buffers
2252800 bytes
Redo Buffers
327680 bytes
1.1 SHARED POOL AREA
1.1.1 LIBRARY CACHE (SHARED SQL + PL/SQL AREAS)

LEGENDA
Shared SQL area: shared pool memory in use by SQL statements
Executions: number of SQL statements accessed for execution
Cache misses: library cache misses while executing
%Reparses: percent of statement reparses over executions
Note: %Reparses should be less than 1% for optimum performance
1960385 Shared SQL area (bytes)
Executions Cache misses
%Reparses
1AA 00014 0004 (9007) A4 ALICE 04.10
698191
ED
7678 1.09968648
03
957.130.882 U

198
56 / 198

LEGENDA
1.1.2 DICTIONARY CACHE ACTIVITY

LEGENDA

dictionary cache: size in bytes of the dictionary cache

Dictionary Gets: number of requests for information
Dictionary Get Misses: requests resulting in cache misses
%Get misses: percent of misses over requests
Note: %Get misses should be less than 1015% for optimum performance
dictionary cache
352576 bytes
Dictionary Gets Dictionary Get Misses %Get misses

3099531
51926
1.67527004
1.2 BUFFER CACHE AREA

LEGENDA
db block gets + consistent gets: total number of requests for data
physical reads: requests of data resulting in access to data files on disk
Hit ratio: percent of data found in buffer over data requests
Note: Hit ratio should be greater than 6070% for optimum performance
db block gets
consistent gets
physical reads
273088
3116137
227425
93.28% Hit ratio

1.3 REDO LOG AREA
LEGENDA
Latch: token a user process must obtain to allocate data into a redo log buffer
WTW Gets: willingtowait requests successful the first time
WTW Misses: willingtowait requests unsuccessful the first time
IMM Gets: successful immediate requests for a latch
IMM Misses: unsuccessful immediate requests for a latch
Note: the ratios Misses/Gets (WTW or IMM) should not exceed 1%
Latch
WTW Gets WTW Misses
IMM Gets IMM Misses

redo allocation
redo copy
535426
11
0% WTW ratio for redo allocation latch

0% WTW ratio for redo copy latch
0% IMM ratio for redo allocation latch
1AA 00014 0004 (9007) A4 ALICE 04.10
0% IMM ratio for redo copy latch
ED
03
957.130.882 U

198
57 / 198
2 USER AND SYSTEM SESSIONS

SESSIONS CURRENTLY OPEN
schema
osuser
PID
machine
program

user

SYS
oracle72 9418
tlvhhk
oracle@tlvhhk (PMON)
SYS
oracle72 9419
tlvhhk
oracle@tlvhhk (DBWR)
SYS
oracle72 9420
tlvhhk
oracle@tlvhhk (LGWR)
SYS
oracle72 9421
tlvhhk
oracle@tlvhhk (SMON)
oracle@tlvhhk (RECO)
SYS
oracle72 9422
tlvhhk
SNML5
SNML5
snmlr50
6292
tlvhhk
@tlvhhk (TNS interface)
SNML5
SNML5
snmlr50
6974
tlvhhk
SNML5
SNML5
snmlr50
7201
tlvhiu
@tlvhiu (TNS interface)
SNML5
SNML5
snmlr50
6440
tlvhhk
SYSTEM
SYSTEM
snmlr50
7526
tlvhhk
SNML5
SNML5
snmlr50
6928
tlvhhk
SNML5
SNML5
snmlr50
6449
tlvhhk
SNML5
SNML5
snmlr50
6282
tlvhhk
SNML5
SNML5
snmlr50
6443
tlvhhk
SNML5
SNML5
snmlr50
6446
tlvhhk
SNML5
SNML5
snmlr50
6397
tlvhhk
SNML5
SNML5
snmlr50
6439
tlvhhk
SNML5
SNML5
snmlr50
6441
tlvhhk
SNML5
SNML5
snmlr50
6243
tlvhhk
SNML5
SNML5
snmlr50
6605
tlvhhk
SNML5
SNML5
snmlr50
6613
tlvhhk
sqlplus@tlvhhk (TNS interface)
sqlplus@tlvhhk (TNS interface)
2.1 PROGRAM GLOBAL AREA

(stacks for servers and background processes)
Tot stacks for all sessions
2589040 bytes
Max stacks for all sessions
2589040 bytes
2.2 USER SESSIONS AREA INTO SGA
LEGENDA
Total user memory: memory currently allocated to all user sessions
Max user mem: max memory allocated (not at the same time!) to all sessions
Total user memory
351284 bytes
Max user memory
1AA 00014 0004 (9007) A4 ALICE 04.10
696004 bytes
ED
03
957.130.882 U

198
58 / 198
3 CONTENTION FOR RESOURCES

ROLLBACK SEGMENTS
1AA 00014 0004 (9007) A4 ALICE 04.10

Note: hits should be more than 95%

NAME
GETS
WAITS
hits

SYSTEM
4101
LARGE_RBS
7832
100
100
R01
7824
100
R02
7932
100
R03
7794
100
R04
7780
100
The administrator must check that for each tablespace there is at least a data file with over than 30% free
space. If not so, the administrator must consider for that tablespace the database extension procedure
described in the next paraghraph.
The administrator must also check that for each table or index segment, the associated number of extents
doesnt exceed 10 otherwise he must consider the full backup and restore procedure described in
paragraph [8.4].
ED
03
957.130.882 U

198
59 / 198
Oracle uses preallocated and not extendible tablespaces, so it could happen some RM functions fails
and in trace files could be found messages as the following:
Message: ORA01653: unable to extend table SNML. TP by 512 in tablespace DATA
N.B.
TP is the name of table where the error arises, messages with different table name
can be found.
To solve this problem the tablespace must be extended using the following procedure (its no necessary
to shutdown RM system and databases):
$ export ORACLE_SID=dbsnml
$ $ORACLE_HOME/bin/sqlplus system/manager
SQL> select * from dba_data_files;
FILE_NAME
FILE_ID TABLESPACE_NAME
BYTES
BLOCKS STATUS

/usr/snml/databases/dbsnml/data/system01.dbf
1 SYSTEM
15728640
7680 AVAILABLE
/usr/snml/databases/dbsnml/data/rbs01.dbf
2 RBS
15728640
7680 AVAILABLE
/usr/snml/databases/dbsnml/data/temp01.dbf
3 TEMP
10485760
5120 AVAILABLE
FILE_NAME
FILE_ID TABLESPACE_NAME
BYTES
BLOCKS STATUS

/usr/snml/databases/dbsnml/data/data01.dbf
4 DATA
31457280
15360 AVAILABLE
/usr/snml/databases/dbsnml/data/index01.dbf
5 INDEX_T
10485760
5120 AVAILABLE
SQL> alter tablespace data add datafile /usr/snml/databases/dbsnml/data/data02.dbf size

30 M;
SQL> quit;
Finally it is necessary to enable the write right for the group of the new file (the command shall be execute
as root Unix user):
# chmod g+w /usr/snml/databases/dbsnml/data/data02.dbf
N.B.
In the previous sqlplus session a new datafile for the tablespace data is created
(/usr/snml/databases/dbsnml/data/data02.dbf). It is recommended to create new datafile
with the same size of the previous ones.
1AA 00014 0004 (9007) A4 ALICE 04.10
It is strongly reccomended to execute a backup and a restore on the RM database.
ED
03
957.130.882 U

198
60 / 198

8.3 Database extension
8.4 Backup and Restore

The backup/restore functions permit to save/restore the following data types:
Network configuration data (and HPOV maps saved into DNM repository);
Alarm data;
PM data;
OS data: Operating System configuration data (i.e. /etc/hosts) Third party software (HPOV ORS
DB) Application configuration data (i.e. us_nodes, im_host_conf);
Operator data.
N.B.
The previous data types could be saved all together or in separate way selecting the relevant
data on user interface.
The first three subsystems backup/restore procedure are based on the Oracle import/export features, so
only table data are saved and not the table structure. This imply to recreate the Oracle DB (see 8.1) before
restoring them.
The Figure 2. illustrates the information distributed in the two disks.
EXTERNAL DISK
APPLICATION / OP. SYS.
INTERNAL DISK
BACKUP / MIRROR
Operating System
/backup
Base Software
archives files
( /mirror/arch )
Application SW ( RM )
Oracle DB
redologs & control
reference base
( /mirror/db_ref_base )
redologs & control
( /mirror/mirror )
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 2. Distribution of files in two application disks
ED
03
957.130.882 U

198
61 / 198
a)
For each installed EML the relevant NR3 directory should be created:
$ mkdir p /backup/1353<sys>_<nn>
where <sys> is SH or WX according to the managed EML and <nn> is the logical
number of the EML (EML Domain Id). The EML name (1353<sys>_<nn>) could
be found in the file /usr/snml/conf/conf_network.
b)
Create the link to the NR2 directories structure:

$ ln s /backup/<sys> /backup/1353<sys>_<nn>/Ntwk
c)
Run Restore Procedure and ignore the warning message.
During the backup the RM system is switched in read only run level, so its guaranteed the saved data
integrity.
The network backup function is available both as a periodical action and on user request via user interface.
The files originated by a backup are stored onto a disk (other than the one in which resides the Oracle
database) and optionally on a tape (see Figure 2. ).
Different backups are stored on an unique tape.
1AA 00014 0004 (9007) A4 ALICE 04.10
The suggested frequency is once per day.
ED
03
957.130.882 U

198
62 / 198

Prior to execute the backup / restore feature for NR2 EMLs (SH and WX) it is necessary to
execute the following manual workaround procedure:

8.5 DB realignment via redo log

After a RM network data restore, the DB can be realigned up to the failure using the RM redo log file.
In this file all the configuration operations (but network topology modification) are traced.
a)
b)
c)
d)
To realign the DB, copy the redo log file in the users home directory (i.e. /users/snml) creating a new
file with .rmCmd extension and empty the current redo log file, using the following commands :
$ cp $NLredolog <user_home_dir>/<filename>.rmCmd
$ >$NLredolog
Perform the Upload NAPs operation. The uploaded NAP are not traced in the redo log file, but path
operations executed by the rmBatchUtil procedure refer them by means of their userlabel. This is the
reason why the Upload NAPs can be executed manually after the restore.
Set to False the global configuration of the ETs involved in payload configuration operations.
Payload configuration is rebuilt by creating and configuring / reconfiguring HOtrails. HOTrails
in a ring can only be created if the global configuration is set to False.
Start the batch procedure opening the CDE file manager from the CDE panel and selecting from
popup menu of the saved file the Executebatch command. Please note that the output of the
batch procedure will be redirected to a file (which name is <filename>.rmCmd.log) in order to be able
to analyze the results at the end of the execution.
During the execution, the performed operations print on the terminal their results. The results of
the batch execution may depend from external conditions (timeouts, concurrences...) so, may
happen that a small number of operations in a large batch file can fail when repeated. This can
be recovered taking into account that the output file of rmBatchUtil reports either the commands
and the results. Failed commands may be saved in an other file and executed later. Pay
attention in case of failure on allocation, add protection or remove protection, that also previous
constraints definition must be rerun together with the failed commands.
e)
Set to True the global configuration of the ETs at point c ). The correct values for the configuration
of the ET will be automatically recalculated.
1AA 00014 0004 (9007) A4 ALICE 04.10
Please note that the previous procedure should be used in case of global Network data restore
(RM plus all the EMLs). In case of partial RM restore the results of the execution of redo log file,
could be unpredictable.
ED
03
957.130.882 U

198
63 / 198
In the following its described the procedure needed to defrag the primary keys identifiers of RM database
tables.
After the procedure execution, the primary key column value of every table will be in the range 1..n, where
n equals the number of rows of the table. All foreign keys will be updated accordingly.
Note: only sensitive tables (TP and TRANPK among the others) will be updated.
8.6.1 Procedure steps
f)
Perform a system full backup.
g)
Stop 1354RM system if necessary (but not the database, which has to be on) using Process Control
facility.
h)
login as snml user.
i)
Change your current directory to the conversion directory:

cd $DB_ROOT/admin/conv
j)
Add a new datafile to the tablespace INDEX_T.

This is necessary since a large index (named NEWOLD_TEMP_INDEX) will be created on a
temporary table (named NEWOLD_TEMP) to boost performance.
The size of this datafile has to be proportional to RM database dimension. A size of 10MB is normally
enough; increase this size if you find any error regarding NEWOLD_TEMP_INDEX.
Please refer to par. 8.3 to see how to add a new datafile; of course, exchange tablespace index_t
for tablespace data, use index<nn>.dbf (<nn> = a number of your choice, which makes the file
name distinct from existing files) instead of data02.dbf, and specify an appropiate size.
k)
Create the rollback segment large_rbs.

This is necessary since the operations on database take a lot of rollback segment space,
far more than normal database operation.
To create large_rbs, perform:
$ORACLE_HOME/bin/sqlplus system/manager @create_large_rbs.sql
l)
Perform the ids defragmentation procedure:

./idDefrag
First of all, the procedure displays some warnings and informations.
Check all, expecially this one:
the database to be managed (environment variable $NXNL_DATABASE)
1AA 00014 0004 (9007) A4 ALICE 04.10
Then, the procedure asks the operator for confirmation (message Do you want to continue ?).
If the variable $NXNL_DATABASE is correctly set, the operator must enter y, otherwise the operator
can enter n (feel free to press <CtrlC> if you like) , (re)set the uncorrect environment variable, and
restarts ./idDefrag. No operation on database is performed until you enter y.
If any errors occur the procedure stops.
Check the logfile idDefrag.log (which is created in the current directory) to diagnose the error.
ED
03
957.130.882 U

198
64 / 198

8.6 Identifier Defragmentation Procedure

N.B.
If any error occurs during execution of ./idDefrag (after your y confirmation) the
database is left in an unconsistent state.
After fixing the problem, you have to perform a RM database full restore and then
repeat this whole sequence of operations (i.e. starting from point b)).
*** Its not enough to restart the shell script ./idDefrag ***.
The same situation arises if ./idDefrag is interrupted (after your y confirmation),
whatever the reason (included user <ctrlc> request).
Every time the procedure is executed, the previous log file is automatically saved as idDefrag.log.old.
m ) Drop large_rbs rollback segment.
To drop, perform:
$ORACLE_HOME/sqlplus system/manager @drop_large_rbs.sql
n)
Remove the datafile previously added to INDEX_T tablespace.

This operation is normally not necessary since the dimension of the datafile is always only a fraction
of the database itself. In addition, you are incouraged not to perform it since it needs some critical
database operations. Only if you are an Oracle expert, check Oracle Server: Administrators Guide,
chapter 7, Managing the Size and Files of the Database.
o)
Perform a Network Discovery operation on NN system, for the Network(s) managed by the RM
whose database you have modified.
This is necessary to align NN database with the modified RM one.
Alternatively, you may shut down and restart the whole NN system, since NN system automatically
realign itself with RM at restart.
8.6.2 idDefrag procedure structure of log file
1AA 00014 0004 (9007) A4 ALICE 04.10
(Check file idDefrag.log.example if available in $DB_ROOT/admin/conv)

Since the procedure is written in PL/SQL, the log file is mainly the copy of sqlplus display output.
The main steps are:
a)
disabling of all FOREIGN KEY constraints.
b)
For every primary key of every table (e.g. tpId of TP table):

creation of newold id mapping table (NEWOLD_TEMP). This mapping is printed on log.
transformation (update) of primary key and of all referencing foreign keys.
dropping of NEWOLD_TEMP.
c)
enabling of all FOREIGN KEY constraints.
d)
resetting of all SEQUENCEs to the 1 + max value of primary key column.

E.g., if the column tpId has max (tpid) = 200, TP_SEQUENCE will be set to 201.
N.B. Only a subset of all primary keys (that is, the ones which may overflow above 2,000,000,000) are
defragmented by this procedure. Currently (19 December 1997) they are:
TP.tpId
TRANPK.tranconnId
PMTROP.pmTranOpId
PMREOP.pmReportOpid
Other primary keys will be added if necessary.
ED
03
957.130.882 U

198
65 / 198
8.7 DB configuration for huge networks
The Oracle startup parameter shared_pool_size must be set to 64 M. The procedure is as follows:
a)
b)
c)
d)
e)
f)
shutdown the system and the database;

cd $DB_ROOT/admin/pfile
su oracle
vi init1.ora
change the value of shared_pool_size to 64000000 (64 Mb).
restart the database and the system.
Every time that the customize procedure has been done this procedure must be reexecuted.
8.8 Managing indexes

Some problems of performances can arise when a lot of network objects are updated and/or a lot of alarms
are received and cleared. In fact, in this case the structures of indexes inside the RM database are broken
into fragments; unfortunately ORACLE is not able to manage this situation automatically.
1AA 00014 0004 (9007) A4 ALICE 04.10
As workaround, indexes have to be dropped and created again. The SQL script
/usr/snml/databases/utility/manageIndexes.sql
is done to do that. It is possible to run it by executing the following command (by snml):
$manageIndexes
It is suggested to execute this script periodically after the backup.
ED
03
957.130.882 U

198
66 / 198

The Configurable Parameter shmmax must be set to 100000000 (100 Mb).
1AA 00014 0004 (9007) A4 ALICE 04.10

9 SYSTEM MANAGEMENT FEATURES (SMF)

9.1 EMLs Data Definition for SMFs
In order to handle management features commands a file named smf_conf must be placed on the
installation home directory of 1354RM and 1353SH both on RM and SH workstations. In smf_conf file
each product must specify its own characteristics and features procedures.
Each specified procedure should respect the following requirements:
a)
b)
c)
d)
e)
f)
g)
h)
ED
it should be an absolute path name of a file executable and readable by each user;
if not differently specified (see paragraph 9.1.1), the procedure returns:
a code = 0 in case of success;
a code 0 0 in all other cases;

it should provide, on standard error, information describing the occurred errors;
commands and parameters (if any) should be separated by coma character (,) instead of blank;
not supported commands have to be inserted giving as parameter the string none;
labels which require necessarily a command expression, are marked by the word mandatory;
it should be able to trap the SIGTERM signal for aborting request;
it should be able to log the executed operation.
03
957.130.882 U

198
67 / 198
9.1.1 Description of smf_conf file parameters
SYSTEM parameters
sys_name : <name>
mandatory.
it is the product system name that is used by the system features; ex. 1354NN, 1354RM,
1353SH1, ..., 1353SHn. It must be unique among systems which are part of the same TMN
network.
sys_check_comm : <checkprocname> mandatory.

this is the procedure that determines the system state, used to visualize the right icon inside the
OSs _network window of the VUE ToolBox. Procedure return code value identifies:
0: system running (all agents are running);
1: system not running and not stopped;
2: system stopped (all agents are stopped);
otherwise: system state is undefined.
sys_start_comm : <startprocname> mandatory.

this is the procedure that starts the system.
sys_stop_comm : <stopprocname>
mandatory.
this is the procedure that stops the system.
sys_log_comm : <logprocname> mandatory.

this is the procedure that starts on current display graphic (TCL/TK) log view utility.
sys_check_control : <checkprocessesautostartprocname>
mandatory.
this procedure allows to check the processes autostart status: the procedure returns 0
(autostart ON), or 1 (autostart OFF).
sys_start_control : <putONautostartprocname> mandatory.

this procedure puts ON the processes autostart status.
sys_stop_control : <putOFFautostartprocname> mandatory.

this procedure puts OFF the processes autostart status.
sys_print_control : <printprocname>.
this is a customized procedure to execute print actions requested by an operator using SMF
application functions. If the command is given, it is the same for all the functions which provide
the possibility to print.
1AA 00014 0004 (9007) A4 ALICE 04.10
SUBSYSTEM parameters
subsys_name : <name>
mandatory.
It is the subsystem name (e.g. 1354RM, 1354NN, node name of 1353SH workstation ...). It must
be unique among subsystems which are part of the same TMN network.
subsys_check_comm : <checkprocname> mandatory.

this is the procedure that determines the subsystem state, used to visualize the right icon inside
the OSs_network > WS windows of the VUE ToolBox. Procedure return code value identifies:
0: subsystem running (all agents are running)
1: subsystem not running and not stopped
2: subsystem stopped (all agents are stopped)
otherwise: system statue is undefined.
subsys_start_comm : <startprocname>
mandatory.
this is the procedure that starts the subsystem.
subsys_stop_comm : <stopprocname>
mandatory.
this is the procedure that stops the subsystem.
ED
03
957.130.882 U

198
68 / 198

In the following the needed smf_conf labels and related commands are described:

SUBSYSTEM backup/restore
Five different backup/restore data types are supported:
network configuration data (identified by Ntwk acronym)
performance monitoring data (identified by PM acronym)
operator data (identified by Op acronym)
alarm data (identified by Al acronym)
TMN OS configuration data (identified by OS acronym)
For each data type subsystem backup, rollback and restore procedure are identified according to the
following:
subsys_bck_<data type> : <backupprocname>

it is the procedure that executes backup saving data in a predefined directory
/backup/<subsystem name>/<data type> on workstation from which the procedure is started.
subsys_tbck_<data type> : <time>
estimated time, in seconds, to complete this backup .
subsys_rbck_<data type> : <rollbackprocname>
it is the procedure that executes rollback of backup actions; it is automatically executed in case
of failure of one subsystem backup command.
subsys_res_<data type> : <restoreprocname>
it is the procedure that executes restore from data stored in the directory /backup/<subsystem
name>/<data type> on workstation from which the procedure is started.
subsys_tres_<data type> : <time>
estimated time, in seconds, to complete this restore.
For the 1353SH, subsys_tbck_<data type> and subsys_tres_<data type> times will be initialized
after the initial backup at the end of the first installation. The backup time measurement will be used
to have a restore time estimation.
end_subsys
9.1.2 Networks configuration file generation

Once a new installation of managed subsystem (EML or A1330) has been completed (and due to this a
new smf_conf file is available), the users has to execute the following command (as root user):
# /usr/snml/etc/update_network
1AA 00014 0004 (9007) A4 ALICE 04.10
to generate new system management features configuration according to the smf_conf file description.
The same script must be used even to generate new configuration file for PMC application (see also 7.2).
The update_network procedure must be executed both from IM and US hosts in the given order.
ED
03
957.130.882 U

198
69 / 198
Using the Periodic Action function defined inside the SMF application in 1354RM subpanel, is possible
to book specific action to be executed periodically.
1)
2)
select in 1354RM subpanel the SMF Button,

select the Periodic Action application.
The scheduling operation are:

1)
Network Backup: it allows to start periodically the backup function in order to save the network
configuration data.
Save and Clean Log&Trace files: it enables a periodical cleaning of the agents trace files to
avoid that they can grow until they fill the file system. The current trace file is saved into a backup
(.bak) copy and than it is emptied. It is recommended to enable this periodic function.
In the file $NXNL_PRD/conf/traceFileSize.par must be specified the maximum size (disk blocks
number) that the trace file can reach (default MAXTRACESIZE=1000 disk blocks).
Clean DB archives: it enables a periodical cleaning of the oracle archived redo log files. It would
be mandatory to enable this function if the Incremental DB archive backup is not used.
Incremental DB Archive Backup: it allows to specify the execution frequency of the incremental
backup.
Save and Clean Events Log: it enables a periodical archive of the Events Log.
Archive System Messages: it defines the frequency of the check on the size of the Archive
System Message files. If the current size is greater than 3000 lines the current files is saved in
a backup copy and a new empty one is created. The function mantains a pool of the last 10
archived files.
2)
3)
4)
5)
6)
N.B.
During the installation phase the Save and Clean Log&Trace files and the Clean DB
archives (this one only when the installation is done with the parameter MIB different
by REC) functions are enabled with a frequency of 15 minutes.
For all these functionalities the following operations are available:

1)
Show scheduled time : it displays, if it is defined, the current booking time of the related
operation.
Set scheduled time : it allows to the administrator to insert, or to change, the scheduling time
of the related operation.
Cancel scheduled time : it removes the previous inserted booking time for the related operation.
2)
3)
9.3 MultiScreen Installation

In order to permit to System Management Features to work properly in 1354RM with distributed
architecture (IMUS workstations or Xterminals) a tools is available to declare all nodes. The tool is
contained in the SMF application in 1354RM subpanel and it is named Console Administration. This utility
can be used to add, remove, lock or unlock a specific node and list all the 1354RM nodes. It can be used
from any node of 1354RM distributed architecture.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
No automatic discovery of existing workstations or Xterminal is performed, but the application

will display only data inserted manually buy 1354RM administrators.
03
957.130.882 U

198
70 / 198

9.2 1354RM Scheduled Operations

10 1354RM BEHAVIOR
10.1 EMLs management
10.1.1 Procedures to define EMLs managing Q3 NEs
EMLs that are managed by 1354RM can be created/deleted online in RM database using the following
commands:
# /usr/snml/bin/AddEML <EML_id>
# /usr/snml/bin/RemEML <EML_id>
These procedures register/deregister the EMLs into HP/OV and add/remove the management records to
the PMC.
10.1.2 Procedures to create EMLs managing QB3* NEs
EMLs that are managed by 1354RM can be created in RM database using the following command:
N.B.
$ usr/snml/bin/nlCreateInDb eml [ id <EML_id> ] f
Identifier parameter will be requested explicitly by the procedure if it is not indicated. The EML
identifier must not be reserved by 1354RM (see next paragraph). The creation of a virtual EML
doesnt require the f option.
EMLs are created with dummy userlabel with the format EML_<id>, that will be replaced by the real
EMLs userlabel during the EMLNML alignment process (see 11.3).
Using the h option, as indicated below, the command prints on the screen its syntax:
N.B.
$ nlCreateInDb h
The emlDomain 0 is reserved by RM, that use it as a virtual EML.
10.1.3 Procedures to delete EMLs managing QB3* NEs

EMLs which have been accidently created in the RM database and are not needed can be removed with
the following command:
$ usr/snml/bin/nlCreateInDb del fdn ntwDomId=1/emlDomId=13 f
1AA 00014 0004 (9007) A4 ALICE 04.10
You can find the fdn for the eml you want to delete by going into the network view, upload available EMLs
and select the EML which should be deleted. After that execute View>Object Attributes>Long Report.
For the selection Name attribute you find the string you have to give as fdn parameter.
ED
03
957.130.882 U

198
71 / 198
When a path allocation is asked from the User Interface, a first consistency analysis is performed and the
result is reported to the user. If the allocation activity does not succeed, the path working state attribute
is set to Failed to Allocate and using the event logger (from the event log file) the error code (and the
related message) can be retrieved.
The possible error codes are :
a)
Not enough resources in the network; this covers many cases:

1)
2)
3)
4)
there are no more free link connections in a physical connection;

a physical connection has been configured with different payload;
a connection inside an NE is not possible due to an NE constraint;
a connection inside an NE is not possible due to an NE limitation (e.g. HO dropinsert or bridge
& switch connections in 1661SMC):
a physical connection has been impacted by an alarm and the path has been defined with
notAlarmedResourcesOnly attribute;
5)
Suggestion for analyzing the problem:
if the allocation of unprotected path/trail fails, check if one or more of the previously described
cases occur;
if nothing is discovered after this check, put constraints on the path/trail, in order to force the
desired route;
b)
Not found east and west CTPs with same payload position in protected connections (NE
constraint);
In a protected path/trail, the routing algorithm has found both main and spare routes, but there are
no main and spare idle CTPs in a protected connections with the same payload position and this is
not compliant with some NEs (all ADMs);
unprotect the path/trail and allocate in order to have more information on the main route, then
put constraints on the path/trail, in order to force a route different from the minimum cost one;
c)
Unable to manage overlap between main and spare (NE constraint);

In a protected path/trail, the routing algorithm has found both main and spare routes, with at least
1 common routing link, but after has discovered that it is not possible neither to use 2 different link
connections in the common routing links, nor to create 2 protected connections at the boundary of
these common routing links;
put constraints on the path/trail, in order to force another route
d)
The spare route completely overlaps the main route (only path/trail allocation);
1AA 00014 0004 (9007) A4 ALICE 04.10
The routing algorithm has found only 1 possible route (main) between origin and destination; the
reasons why the spare route has not been found can be that one or more of conditions described
in a ) occur;
check if one or more of conditions described in a ) occur;
ED
03
957.130.882 U

198
72 / 198

10.2 Path / HOTrail allocation algorithm failures

e)
Protecting this route wouldnt improve the protection level (only path/trail add protection);
The routing algorithm has not found the spare route between origin and destination; the reasons can
be that one or more of conditions described in a ) occur;
f)
Not enough resources in the network only a subset of sink NAPs is reachable;
In a broadcast path, the routing algorithm has found the route for some legs but not for all; the reasons
why the routes for the other legs have not been found can be one or more of conditions described
in a ) occur;
g)
A link connection specified in path constraint is not acceptable;

A constraint on the path/trail has been inserted, specifying to use a link connection that is already
used in another path/trail or configured or in a wrong state;
remove or change the constraint, or check the state of the link connection;
h)
Incompatible constraints;
More constraints on the path/trail have been inserted, but some of them are incompatible.
check the constraint and remove the incompatibility;
i)
Incompatible CTPs;
It happens during an HO trail allocation defined starting from two CTPs if the user adds a constraint
on a link connection not compatible with one of two CTPs.
check and remove the constraint;
j)
Specific RM error. Possible values are:
Error connecting to data base;
Error reading data from data base;
Not enough space in RAM;
....
1AA 00014 0004 (9007) A4 ALICE 04.10
restart the trsMngAgent using process control.
ED
03
957.130.882 U

198
73 / 198
10.3.1 Environment Variables

The following three environment variables are defined to identify the directory where the DNM Manager
save or get the map image:
NXNL_MAPDBHOST :
NXNL_MAPDBUSER :
NXNL_MAPDBAREA :
it specifies the host where the MAP DB area is placed.

it specifies the owner username of the MAP DB area.
it specifies the path name of the MAP DB area.
This environment variables are initialized in the /usr/snml/.nxnlenv file.

10.3.2 Registration Files
In the registration file mngmapOus (see 6.2.1) are defined the text strings used to build the DNM pulldown
menu. The Administrator can modify them in order to obtain a more friendly menu.
10.3.3 Resources Files
In the 1354RM delivery the resource files directory is named /usr/snml/xapplresdir that contains
languagedependant directories (default language is C). In this directory is present the DNM resource
file that is called mngmap, in which three variables are defined to permit to the Administrator to customize
the Mail Message sent when a map image is saved to users that can use it.
mailMsg :
mailCommand :
mailAllUser :
it contains the mail text that is sent to enabled users

it specifies the Unix Mail command used to send the mail message. The
variable that follow the s option is the Subject of the message.
it is initialized with the default username list that represents all the system
users. It is used to send a mail message when an operation is performed
on a map image visible by all users.
To improve the customization flexibility of the mail message text, can be used four environment variables
that are initialized with the proper values each time :
1AA 00014 0004 (9007) A4 ALICE 04.10
map_action :
map_name :
map_comment :
map_subject :
ED
it is initialized with the action performed on the map image.

it is initialized with the name of the map image involved in the operation.
it is initialized with the memo text related to the involved map image.
it is initialized with a string indicating the mail subject consistent with the
performed operation.
03
957.130.882 U

198
74 / 198

10.3 Distributed Network Maps (DNM) application customization
10.4 Trace management

This feature is not supported to the customer: it has been introduced for debug purpose only.
The trace levels and trace group numbers that must be indicated to analyze SNML applications are listed
in the README.trace file, presents in the $NXNL_PRD/bin directory.
10.4.1 User Interface applications
To enable the trace utility for User Interface applications, the user has to define two environment variables
in a normal Unix window, and then start manually the User Interface application. The two environment
variables are :
NXNL_XON_G = Number of Trace Group

NXNL_XON = Trace Level
10.4.2 Information Manager Applications

The trace utility can be enabled for Information Manager Agent Processes at run time, performing the
following steps:
1)
Insertion of trace level and, eventually, trace group in the file:

$NXNL_PRD/trcLevel/<agent_name>.trc
In this file the involved trace levels must be inserted in the first row, in the second (optional) the
trace group number.
2)
Signal to the process to get the new trace level using:

kill 17 <process_PID>
or using the appropriate pulldown menu action of PMC.
3)
The trace outputs are on a file named <agent_name>.trc placed in the directory
$NXNL_PRD/trace/<agent_name>.trcDir/
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Trace for children agents (i.e. pathImp) are placed in the directory of the parent
process (in this case trsMngAgent).
03
957.130.882 U

198
75 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
Hereafter are listed two alignment procedure between 1354RM and 1353WX to recover from transmux
ports configuration misalignment that can be produced after either a 1353WX or 1354RM restore (e.g.
restoring on WX a backup where a port is configured at 64 x 2Mb, but on RM it is configured as a single
140Mb port).
ED
03
957.130.882 U

198
76 / 198

10.5 Consistency Download problem with transmux ports

10.5.1 RM with 2Mb ports and WX with a single port

In the following procedure is listed the workaround in the case that RM has 64 (16) x 2Mb ports and the
WX has a single 140Mb (34Mb) port:
1)
perform a restore of the network (if WX MIB is corrupted, delete the WX persistency, if not and
it seems that RM and WX have the same content, keep the WX persistency);
2)
perform the synchronization of the WX EML domain (synchronize the physical ports);
3)
check the synchronization of the EML:

a)
b)
if the synchronization result of the EML is misaligned means that WX and RM have
different physical ports configuration, so it is necessary to check if in WX MIB the
misaligned ports have some connections (this case cannot be handeled by RM):
1)
start the Consistency Procedure (either global or on connections only). At the end
RM should have deleted all not foreseen connections (also the ones supported by
140Mb or 34 Mb not aligned ports);
2)
start (again) the Consistency Procedure (either global or on ports only). At the end
RM should have deassigned all the not aligned ports. It is so possible to jump to next
point without deleting the WX persistency;
3)
then the synchronisation of the EML will be misaligned (and the operator can be sure
that WX has no connection on that unkown port from RM);
4)
find the just created 140Mb port (it should be in the observed Assignment State);
5)
perform the Configure PDH port action on such 140Mb port, so on WX side:
the 64 * 2Mb ports are created (NMLobserved, with same FDNs as RM ones);
the 140Mb port is deleted;
if the synchronization of the EML is aligned (WX and RM has any different physical ports),
the normal Consistency Procedure can be performed by the operator (see next bullet 4);
4)
set Configure Disable on the WX node;
5)
switch to the Consistency run level using PMC;
6)
perform a global Consistency Download (all should be successful);
7)
switch to the Full functionality run level using PMC;
8)
make on the WX node a Configure StartAudit (it checks that WX content and 1641SX content
are aligned);
9)
check of the StartAudit value:

if the StartAudit becomes aligned (green), set Configure Enable on the WX node;
if the StartAudit becomes misaligned (yellow), check each configure mismatch alarm and
decide if you can interrupt traffic or not. If you may not interrupt traffic, modify the RM till
all connections are aligned.
1AA 00014 0004 (9007) A4 ALICE 04.10
After this set Configure Enable on the WX node.
ED
03
957.130.882 U

198
77 / 198
This is a special case, because RM has the 140Mb (34Mb) port which is assigned and the WX not. The
1641SX has a structured 140Mb (34Mb) port and it could have also connections on it. The RM cannot
remove the NAP related to this 140Mb (34Mb) port because WX has not this NAP and RM cannot manage
a crossconnection on a TTP which is only seen by the WX. To align this situation it shoul be made
manually by RM:
1)
perform a restore of the network;
2)
perform the synchronization of the EML domain (synchronize the physical ports);
3)
if the synchronization result of the EML is misaligned, recognize which 140Mb (34Mb) ports
are misaligned. It means that WX and RM have different physical ports configuration, so it is
necessary to check if in WX MIB the misaligned ports have some connections (this case cannot
be handeled by RM). In this case delete WX persistency, start WX again (on AU) and perform
a synchronisation of the EML;
4)
then the synchronisation of the EML will be aligned;
5)
set Configure Disable on the WX node;
6)
switch to the Consistency run level using PMC;
7)
perform a Consistency Download global (all should be successful);
8)
switch to the Full functionality run level using PMC;
9)
make on the WX node a Configure StartAudit (it checks that WX content and 1641SX content
are aligned);
10 ) check of the StartAudit value:

if the StartAudit becomes aligned (green), set Configure Enable on the WX node;
if the StartAudit becomes misaligned (yellow), check each configure mismatch alarm and
decide if you can interrupt traffic or not. If you may not interrupt traffic, modify the RM till
all connections are aligned (this means in this case structure the transmux port and
implement the lost path).
1AA 00014 0004 (9007) A4 ALICE 04.10
After this set Configure Enable on the WX node.
ED
03
957.130.882 U

198
78 / 198

10.5.2 RM with a single port and WX with 2Mb ports
1AA 00014 0004 (9007) A4 ALICE 04.10

11 1354RM CUSTOMIZATION
11.1 Environment variables changes
In the following paragraphs are described some customizations possible in RM. Hereafter is described
the standard way to change and to take effect them, and it should be applied if some variables are
changed. For nonstandard variables the change procedure is described directly in the relevant
paragraph.
In the following paragraphs for the standard managed variables the following data are listed:
Relevant Process
(Father Process, if necessary)
Variable Name (with default value)
The relevant process is the one to be restarted to activate the variable value. If it is followed by another
name in brackets, it means that it is a child process and its father shall be restarted to activate the variable
value.
Standard way of changing variables is:
a)
Edit the file /usr/snml/.nxnlenv; all the variables are described as :

<Variable_Name> = <Variable_Value>
b)
Change the variable value and save the files;
c)
After this you need to shutdown and startup the Relevant Agent (or its father).
ED
03
957.130.882 U

198
79 / 198
11.2.1 Counters refresh rate on agent response

Relevant Process:
Variable Name:
browser
NXNL_COUNTERTIME (unset)
This variable defines the rate on which the browser has to refresh its item counters when the operator has
performed a get or an inventory and the agents are sending the related replies. The possible values are:
unset : the refresh is done every response;

0 : the refresh is done at the end only;
n : the refresh is done every n replies.
11.2.2 Browser
Relevant Process:
Variable Name:
browser
NXNL_MAX_NUM_ITEMS (unset)
NXNL_MAX_NUM_ITEMS_INWIN (unset)
NXNL_MAX_WINS (unset)
These three variables are related to the maximum number of objects displayable in the browser
(NXNL_MAX_NUM_ITEMS), the maximum number of objects displayable into a single window of browser
(NXNL_MAX_NUM_ITEMS_INWIN) and the maximum number of windows opened at the same time
(NXNL_MAX_WINS). When these thresholds are exceeded a warning box is displayed.
N.B.
If the environment variables are not set (or set with value 0) no checks are done about number
of objects displayed in the browser.
11.3 EMLNML Alignment Process

Relevant Process:
Variable Name:
emlObjAgent
NLhbp (180)
This variable enables the polling mechanism toward EMLs. Its value indicates the timeout (in seconds
between two different polling activity.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
If the environment variable is not set (or set with value 0) the EML data alignment polling activity
is disabled.
03
957.130.882 U

198
80 / 198

11.2 Users Services
11.4 Inventory Processes

Relevant Process:
Variable Name:
topBrwAgent
NXNL_INVPROCESS (1,2,100,2)
This variable configures the number of processes dedicated to inventory actions (e.g. path list, physical
connection structure, ...) and must be set in nxnlenv_make file before to start the customize_patch
procedure.
By default the heavy inventory starts on instance NXNL_NTWBRRDA=1 or 2 (in random way) and the
light inventory starts on instance NXNL_NTWBRRDA=100 or 101 (in random way) and there are two
processes dedicated to heavy inventory and two processes dedicated to light one.
E.g. NXNL_INVPROCESS=1,4,100,4 means that the heavy inventory can start on object instance
$NXNL_NTWBRRDA=1 or 2 or 3 or 4 (random) and the light inventory can start on
$NXNL_NTWBRRDA=100 or 101 or 102 or 103.,
Its clear that by default four lrf files are created in lrf directory; in the example eight lrf files are created in
lrf directory.
11.5 Map Management
Variable Name:
NXNL_MAPNAMERULE (unset)
The users having the Look Only ot he Path Builder profiles have now the capability to perform the highlight
of a path on the Map. This is possible also if they do not have the right to write on a map, because a
temporary map is atomatically created (and deleted) by the system.
1AA 00014 0004 (9007) A4 ALICE 04.10
To enable this feature you must set the variable, before executing the customize_patch procedure,
specifying the naming rule (if exist, otherwise this feature can not work) used to identify the default map,
e.g. NXNL_MAPNAMERULE = *_PTTNAME then execute the customize_patch and the command by
snml user: echo enable > /usr/snml/conf/CopyMap.
ED
03
957.130.882 U

198
81 / 198
11.6.1 Path/Trail allocation algorithm

Relevant Process:
Variable Name:
N.B.
pathAll (trsMngAgent)
K2 (2)
K34 (1)
K140 (1)
K2, K34 & K140 variables can assume integer values only.
During the allocation phase, the cost of a given routing link is dynamically evaluated with the following
formula :
Cost = C ( 1 + K / F )
Where :
C:
F:
K:
cost of the routing link without taking into account any usage factor
number of free linkconnections in the routing link
Parameter allowing the tuning of the sensibility of the cost to the loading of the
routing link
The three variables are taken into account by the allocation of different path types: K2 (2Mbits paths), K34
(34Mbits & 45Mbits paths), K140 (140Mbits paths).
11.6.2 Reuse already allocated resources in Broadcast paths.
Relevant Process:
Variable Name:
SAME_RES_TYPE (20)
DIFF_RES_TYPE (40)
1AA 00014 0004 (9007) A4 ALICE 04.10
By means of these variables is reduced the cost of routing link already allocated by the relevant broadcast
path, in order to force the allocation algorithm to reuse as much as possible the resources. The cost
calculated in the previous paragraph is multiplied by SAME_RES_TYPE/100 (default 20%) if the path
already use the routing link in the same route type as the allocating one (both main or both spare),
otherwise it is multiplied by DIFF_RES_TYPE/100 (default 40%).
ED
03
957.130.882 U

198
82 / 198

11.6 Path/HOTrail Management
11.6.3 Using Virtual Nodes during Path Allocation Phase

Relevant Process:
Variable Name:
DISABLEVIRTUALCTPTOCTP (not defined by default)
By means of this variable it is possible to enable or disable the crossing of Virtual Nodes during the Path
Allocation phase. If the environment variable DISABLEVIRTUALCTPTOCTP is defined and has a value
different by 0 the Virtual Nodes are taken into account during the Implementation phase only if the path
terminates on them (no passtrough can be defined on virtual nodes). If the variable is not defined or
defined with value equal to 0 all virtual nodes are taken into account as normal nodes during the allocation
phase.
N.B.
When there is interworking RMNN it is necessary setting (see 12.4 paragraph):

export DISABLEVIRTUALCTPTOCTP=1
11.6.4 Configurable switch in Drop&Continue

Relevant Process:
Variable Name:
DROPCONTSWITCHCONF (0)
By means of this variable it is possible to set the nominal position of the switches in Drop&Continue
connections in a spare route of the path or trail.
If the variable is set to 0 (or not defined) the main side of the switches is turned to the main route of the
path, if it is set to 1 the main side of the switches is turned to the spare route of the path.
11.6.5 Changing timeout for Cross Connection management actions
Relevant Process:
Variable Name:
pathImp (trsMngAgent)
NLtimeoutBase (300)
NLtimeoutReq (30)
By means of this variable it is possible to change the timeout for cross connection management actions
(create, delete, update squelching and so on), with the exception of HO CTPHO CAP creation/deletion
which are handled differently and by a different process.
The timeout for every request is set via this formula:
timeout = NLtimeoutBase + n * NLtimeoutReq
where n is the number of requests sent to NEs but not answered yet.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Normally NLtimeoutReq is zero so the timeout is fixed and equal to NLtimeoutBase.
03
957.130.882 U

198
83 / 198
11.6.6 Configuring consistency flow control
Relevant Process:
Variable Name:
consChkAge
IMP_FLOWCONTROL_MAX_OUTSTANDING (15)
By means of this variable you can set the maximum number of create/delete/update_squelching
messages concurrently sent to NEs during consistency download. If the number of sent messages equals
the threshold specified by this variable, the consistency process will wait until a message is answered
before sending another one.
N.B.
This simple mechanism of flow control overcomes internal message queues overflow in OSes
(like WX) which dont use HO OpenView CI builtin flow control feature.
11.7 Alarm management

11.7.1 Flooding protection mechanism
Relevant Process:
Variable Name:
emlAlrMng
HP_TOthreshold (60)
HP_almthreshold (150)
LP_TOthreshold (60)
LP_almthreshold (100)
These variables are related to high priority (HP_TOthreshold, HP_almthreshold) and low priority
(LP_TOthreshold, LP_almthreshold) alarms, they are used to implement a flooding protection
mechanism.
When RM receives more than HP_almthreshold high priority alarms in HP_TOthreshold time (sec) it stops
to analyze them (no propagation is done) and emits a High Priority Alarm Flooding alarm for the relevant
EML. It doesnt analyze alarms until a HP_TOthreshold period terminates with an alarm rate lower than
HP_almthreshold. The same mechanism is implemented for low priority alarms with the Low Priority
Alarm Flooding issuing.
The alarm synchronization isnt automatically performed but its up to the operator to require it.
11.7.2 Alarm clearing hysteresis period
Relevant Process:
Variable Name:
pathAlrMng (emlAlrMng)
NLdeltatime (5)
1AA 00014 0004 (9007) A4 ALICE 04.10
This variable set a hysteresis period on clearemission time of an alarm. It means that when an alarm is
cleared the RM process wait NLdeltatime seconds before starting the propagation phase, if the same
alarm raise up again (same object with same probable cause) in this period the RM doesnt propagate
neither the clear nor the new raise of the alarm, leaving the previous alarms as they are.
ED
03
957.130.882 U

198
84 / 198

11.8 Nap uploading timer

Relevant Process:
Variable Name:
objImpCnf
(topMngAgent_csa)
NLnaptim (1200)
This variable defines the default timeout value (in seconds) for the NAP upload of a single node. If a node
contains a large number of PDH ports (e.g. more than 300) it is suggested to set a bigger timeout value.
11.9 SNCP switch timer

Relevant Process:
Variable Name:
pathImp
(trsMngAgent)
tsdFepCfg
NL_TIMER_WATCHSW (600)
NL_TIMER_MNGSW (60)
The NL_TIMER_WATCHSW variable defines the watching period lenght (in seconds) of switch state, the
watching period begin from synchronize switch command. During this period all switch events are
managed.
The NL_TIMER_MNGSW variable defines the timeout value (in seconds) for the execution of a manage
SNCP command. The value of this variable has to be minor than the NL_TIMER_WATCHSW.
11.10 Printer Commands
Variable Name:
NXNL_PRINT (/usr/snml/bin/tops L | lp)
The RM printer functions (started from report windows or by CDE desktop popup menu) use the
environment variables NXNL_PRINT to execute the printing command.
If the variable is set to null the printer functions use the lp Unix command, otherwise they execute the
command described in the variable.
Using the default command the printouts have landscape orientation and each row contains up to 180
characters.
When this variable is changed, to take it effective it is required to exit from CDE workspace and then login
again.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
This commands is used only for ASCII printout, not for Hardcopy popup menu commands.
03
957.130.882 U

198
85 / 198
11.11 Unused Virtual PDH ports garbage collection
Relevant Process:
Variable Name:
trsMngAgent
NLCheckVirtual (not defined by default)
PDH ports and related NAPs, defined in a virtual NE, and not involved in any path, can be removed at the
trsMngAgent startup. This feature can be enabled or disabled by means of this environment variable. If
the variable is defined the check is performed, if it is not defined the check is skipped.
11.12 Setting Linked Get Replies Maximum Number

Relevant Process:
topMngAgent_g
(nlMon_g)
In the 1354RM product, it does not exist the possibility to stop a get operation that produces a big amount
of linked replies (e.g. not filtered full scope get operation). In any case is provided the possibility to define
a maximum number of linked get reply that can be produced by a single operation.
The maximum number must be defined as a parameter to the topMngAgent_g process specifying it in
the configuration file $NXNL_PRD/conf/conf_nlMon_g.
The syntax is:
/usr/snml/bin/topMngAgent_g, suffix, <xxx>, answer, <n_ans>
The parameter <n_ans> indicates the maximum number of linked replies allowed (default 1000). If it is
indicated the number 0 no limit is set. If during a get operation the reply limit is reached a warning message
is displayed to the operator.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
The string described in this paragraph as <xxx> is the suffix of the agents instances and must
not be changed.
03
957.130.882 U

198
86 / 198

11.13 NetView Symbols Labels

The fonts used in the Netview applications are specified in the file:
/usr/snml/conf/users/admin/xapplresdir/C/OVw
and they are defined by means of the symbols :

*size30Font:
*size20Font:
*size10Font:
*smallFont:
They are automatically referenced by HPOVw depending on the number of symbols to be displayed in
a submap.
If the symbol labels are too small the System Administrator could change the size of this fonts (i.e. the small
font could be changed from *helveticamediumr*80* into *helveticamediumr*120*
and then restart NetView application (close all the HPOVw windows and start again the application).
In the following an alternative font set with respect to the delivered one is listed:
*size30Font:
*size20Font:
*size10Font:
*smallFont:
1AA 00014 0004 (9007) A4 ALICE 04.10
*helveticamediumr*140*
ED
03
957.130.882 U

198
87 / 198
11.14.1 PM Data Collection Customization

11.14.1.1 EMLs configuration file
Relevant Process:
pmCollMng
(pmMng)
It is on User responsibility to specify in a configuration file eml_PM_nodes the host machines where the
EMLIM applications communicating to RM the PM Data are.
The file eml_PM_nodes is present in the /usr/snml/conf directory and must be manually filled by the
operator.
In the file a row has to be specified for each managed EML. Each row has the following syntax:
<EML_ID> <host1> <host2> <remote_user> <home dir remote user> <dir 15M> <dir 24H>
where:
<EML_ID>:
<host1>:
<host2>:
it is the EML identifier .

it is the logical host name where EMLIM application runs .
for WX, it is the second logical host name where the files could be present.
For SH it must be set to none.
<remote_user>:
it is the remote user used by RM during the remote connection to get files.
<home dir remote user>: it is the home directory of the remote user
<dir 15M>:
it is the name of the subdirectory where EML provides files for 15 minutes
granularity.
<dir 24H>:
it is the name of the subdirectory where EML provides files for 24 hours
granularity.
Example for SH:
200 dogbert none rmpm /usr/1335sh/rmplug/data/pm pm15Dir pm24Dir
11.14.1.2 SENIM data file collection timeout
Relevant Process:
pmCollMng
(pmMng)
1AA 00014 0004 (9007) A4 ALICE 04.10
To customize the timeout between two different file collection operations the following options can be
inserted in the process starting command in the file /usr/snml/bin/pmCollMng :
timeout15m <n>: it allows to customize the timeout value representing the collection frequency of
the 15 minutes transfer files from the EMLs to RM. The value <n> must be expressed in minutes and
it must be included between 15 (i.e. a quarter) and 225 (i.e. 3 hours and 45 minutes). If the option
is not specified the default value is 15 minutes;
timeoutday <n>: it allows to customize the timeout value representing the collection frequency of
the 24 hours transfer files from the EMLs to RM. The collection activity has anyway a builtin timeout
of 4 hours after midnight to collect data file relevant for the last elapsed day. The value <n> must be
expressed in minutes and it must be included between 1440 (i.e. one day) and 8640 (i.e. six days).
If the option is not specified the default value is 1440 (i.e. one day);
ED
03
957.130.882 U

198
88 / 198

11.14 Performance Monitoring Customization
11.14.1.3 TSD data file collection timeout

Relevant Process:
tsdFepColl.exe
TFEP/COLL acts on a periodic basis: the collection frequency could be provisioned from a user by means
of a configuration file COLL_CFG . In COLL_CFG file the user can specify:
the granularity (e.g. G
24, 24 hours granularity)
a granularity list indicating the day partition and the collection frequency (e.g. 12 60, a copy from
EML is done every 60 minutes for the period starting from the previous period end till 12 A.M)
The configuration file COLL_CFG should be present in the directory specified by the enviornment
variable PM_DATA_WORK; at the moment a COLL_CFG.make file is present as templete. Its in charge
of the user to provide the COLL_CFG file.
When the file COLL_CFG is not present a default value is adopted from the tsdFepColl agent:
24: freqency one hour
15: frequency 15 minutes
11.14.1.4 SENIM Maximum number of data collection processes

Relevant Process:
lpmCollMng
To define the maximum number of parallel collection activity that can be executed the following option can
be inserted in the process starting command in the file /usr/snml/bin/pmCollMng
maxscript <n>: the value <n> represents the maximum number of scripts that can be execute in
parallel to collect the PM transfer files from the EMLs. If it is not specified the default value is 3.
11.14.1.5 TSD Maximum number of data collection processes

Relevant Process:
tsdFepColl.exe
1AA 00014 0004 (9007) A4 ALICE 04.10
To define the maximum number of parallel collection activity that can be executed the following variable
could be used NLcollMaxScript. If it is not specified the default value is 3
ED
03
957.130.882 U

198
89 / 198
11.14.2 PM Data Archive Customization
To allow the PM data archive function a new ORACLE user environment is required. The following
procedure shall be executed after the RM installation:
a)
Create the ORACLE user (rmpmarch/rmpmarch) and relevant tablespace:

$ /usr/snml/bin/pmInitRMPArchive.com
b)
Create required tables and views (dropping the old ones if any):
$ /usr/snml/bin/pmCreateRMPArchive.com
c)
Initialize the PM Book Period table in RM User DB (snml/snml) in order to customize the starting
& ending time of Archive activity that will be taken into account by the next user archive request (it
must not be executed in case of DB import):
$ /usr/snml/bin/pmInitRMP.com
N.B.
The starting date is by default the beginning of the current month and the ending date is
calculated using the variables described in 11.14.2.2 paragraph.
11.14.2.2 PM Data Archive Period Granularity

Variable Name:
DETAILEDARCHIVEPERIODDURATION (7)
NORMALARCHIVEPERIODDURATION (1)
These variables are related to the archive activity of PM data of 15 min

(DETAILEDARCHIVEPERIODDURATION) and 24h (NORMALARCHIVEPERIODDURATION). The first
one indicates the number of days (by default a week) that has to be elapsed before enable the archive
activity on 15 min. The latter variable indicates the number of months (by default a month) that has to be
elapsed before enable the archive activity on 24 min.
After that this period is elapsed the archive activity is enabled to archive data relevant to the elapsed
period. Once the archive activity is executed a new period shall be elapsed to enable again the archive
activity.
N.B.
When the archive request is issued by the operator, if more than one archive periods are
elapsed (difference between current time and end archive period is bigger that the duration
indicated by these variables), all data relevant for these elapsed archive periods will be archived
in one shot.
1AA 00014 0004 (9007) A4 ALICE 04.10
When these variables are changed, to take them effective, it is required to exit from CDE workspace and
then login again.
ED
03
957.130.882 U

198
90 / 198

11.14.2.1 Create ORACLE User for Archive purpose
11.14.2.3 Delete prevention of Archived PM Data in the RM DB

Variable Name:
DETAILEDARCHIVEPERIODOVERLAP (7)
NORMALARCHIVEPERIODOVERLAP (1)
These variables are related to the prevention of archive purging of PM data of 15 min
(DETAILEDARCHIVEPERIODOVERLAP) and 24h (NORMALARCHIVEPERIODOVERLAP). The first
one indicates the number of days (by default a week) in which is granted that archived data relevant for
15 min will not be removed from RM DB. The latter variable indicates the number of months (by default
a month) in which is granted that archived data relevant for 24h will not be removed from RM DB.
When these variables are changed, to take them effective, it is required to exit from CDE workspace and
then login again.
11.14.3 PM Scheduled Report
Relevant Process:
Variable Name:
pmMng
PM_DELAY_MIN (135) value in minutes
PM_DELAY_DAY (8)
value in hours
PM_DELAY_MIN (relevant for 15 min data) / PM_DELAY_DAY (relevant for 24h data) an useful value
used in order to grant that when a report has to be generated, the meaningful counters have been already
collected and analyzed (i.e. stored in the DB). They allow to synchronize the collect & analysis and the
report generation activities.
e.g. PM_DELAY_MIN= 30 the fifteen minutes report of the period 25/08/200023.00 to 23.15 will be
generated at 23.45 of 25/08/2000.
e.g. PM_DELAY_DAY= 8 the daily report of 25/08/2000 will be generated at 8.00 AM of 26/08/2000.
11.14.4 PM Automatic Start/Stop Measures
Relevant Process:
Variable Name:
pmMng
NLschedule15 (600)
NLschedule24 (600)
1AA 00014 0004 (9007) A4 ALICE 04.10
These variables allow to set the timeout value for the automatic Start and Stop of 15 min / 24h Measures.
Their value has to be expressed in seconds (e.g. NLschedule15=60 means that the timeout for 15 min
measures elapses each minute).
ED
03
957.130.882 U

198
91 / 198
In 1354RM a default ASAP for paths,trails and physical connections is created at the installation time and
it is identified by the value default ASAP as userLabel (its asapId is always equal to 0).
An offline procedure permits to substitute the default ASAP with an ASAP previously defined by the user.
The steps to execute this procedure are:
a)
Stop the system;
b)
execute a full backup (this procedure modifies the RMDB);
c)
execute the procedure (by snml).

$ /usr/snml/bin/changeDefaultAsap
This procedure asks the userLabel of the new default ASAP to the operator.
The procedure checks if the ASAP specified by the operator is already defined. If it is not defined, the error
message
Asap <userLabel specified by the operator> not Found
will appear.
11.16 Procedure to set Swedish language

In order to enable the swedish chars on the keyboard you have to execute the following operations as nnml
user:
1AA 00014 0004 (9007) A4 ALICE 04.10
$ cd XAPPLRESDIR/C/include
$ cp NLguiCommon NLguiCommon_english
$ cp NLguiCommon_latin1 NLguiCommon
$ cp NLfont NLfont_english
$ cp NLfont_latin1 NLfont
$ cp NLmatrix NLmatrix_english
$ cp NLmatrix_latin1 NLmatrix
ED
03
957.130.882 U

198
92 / 198

11.15 How to change the default ASAP

12 QNN INTERFACE MANAGEMENT

12.1 Enabling / Disabling Qnn Agent Management
In order to enable or disable the management of Qnn Agent by the 1354RM PMC the following command
has to be executed (using the root Unix username) :
# /usr/snml/etc/QnnAgentMng [ add | rem ]
The command will change the configuration file of the PMC application, but in order to make effective the
new configuration it is necessary to exit from PMC and than restart it again.
N.B.
Exiting and restarting the PMC does not have any impact on the RM system status.
Before to remove the Qnn Agent by the PMC handling the user has to shutdown it.
After a patch installation the operator should perform the enabling of the QnnAgent
Management.
12.2 RM user definition for Qnn ZoomIn

The zoomin operation from 1354NN to RM can be performed with three different profiles according to
the definitions given in the Qnn interface. The defined profiles are:
a)
b)
c)
NN administrator;
NN user;
NN viewer.
The first profile is mapped on the RM user qnnmng, the second one is mapped on the RM user qnnagent
and the latter one with the RM user qnnview.
If the following users are not defined, the zoomin from NN cannot work and it is not
displayed any additional message.
12.2.1 RM users definition script

After plugin installation, in order to create the four gateway users (qnnmng, qnnagent, qnnview and
qnnpmop) to zoomin from NN the following command has to be executed (using the root Unix
username) on all the RM workstations:
# cd /usr/snml/etc
# ./AddQnnUser
1AA 00014 0004 (9007) A4 ALICE 04.10
The command will define the users with the following characteristics:
RM user
qnnmng
qnnagent
qnnviewer
qnnpmop
ED
: Profile
: OSadmin
: PathBuilder
: LookOnly
: PathBuilder
: NAD
: 1
: 301
: 40
: 301
(to permit ftp operation from NN)
03
957.130.882 U

198
93 / 198
The 1354RM zoomin execute from 1354NN is usually performed running the required application on
1354RM Master system. If there are many 1354NN operators, this activity can overload the 1354RM
Master system.
In order to reduce the amount of activities on RM Master it is possible to specify which 1354RM USM of
the same 1354RM cluster have to execute the zoomin application instead of the 1354RM Master.
The /usr/snml/conf/qnnDispMapping file contains the relationship between the 1354NN X Display
require the zoomin and the 1354RM USM that have to execute the application. To request this feature
add one line for each display that have to be served by 1354RM USM in the qnnDispMapping with the
following syntax:.
<nn display> <RM USM hostnamer> where nn display is the 1354NN display identifier, using
the X11 standard notation (eg.NNDISPLAY:0.0) and RM USM hostname is the hostname of the
RM USM of the same 1354RM cluster of the 1354RM Master.
N.B.
In case of 1354RM USM failure, the 1354RM zoomin will fail also.
N.B.
If the 1354RM USM is removed from the network also the related line(s) have to be
removed from /usr/snml/conf/qnnDispMapping.
1AA 00014 0004 (9007) A4 ALICE 04.10
Example of /usr/snml/conf/qnnDispMapping:
nnmst1:0.0
rmusm1
nnxt01:0.0
rmusm2
nnmst1:1.0
rmusm3
ED
03
957.130.882 U

198
94 / 198

12.3 RM ZoomIn from NN using RM USM

12.4 Limitation of Network Construction lead by Qnn Agent

The Qnn Agent is not able to manage a path that crosses connections between two Virtual NEs
representing other RM domains. It means that it doesnt manage properly topologies with direct
connections between two Virtual NEs (RM domains).
1354RM
Network Domain n
CTPA
CTPB
CTPA
CTPB
Physical Connection
Subnetwork Connection
Virtual NE
Figure 3. Supported topology
1354RM
Network Domain n
CTPA
CTPB
CTPA
CTPB
Physical Connection
Subnetwork Connection
Virtual NE
Figure 4. Not supported topology
1AA 00014 0004 (9007) A4 ALICE 04.10
A Virtual NE can represent more than one RM domain. It can represent a whole RM domain independently
from its position into the topological hierarchy (contained in a subnetwork).
As workaround it is suggested:
to collapse into a single Virtual NE all the connected RM domains, or
to represent remote RM domains belonging to the same protection route with a single Virtual NE.
To avoid problem in the NN path allocation phase it is necessary also to disable passtrough on virtual
node ( see Use of Virtual Nodes during Path Allocation Phase ).
ED
03
957.130.882 U

198
95 / 198
In the case of a SNCP protection (QosProtection=full or partial protection on the 1354NN ) asked by
QnnAgent to the RM , if the RM is not able even to perform a partial protection the allocation fails (while
the Qnn foresee a successful allocation with a degraded protection ).
It is possible change manually the protection (no protection) of that path on the RM and try to perform the
redo operation from the 1354NN (only in the case of a path not corresponding ,on the Qnn, to a switchable
subnetwork connection).
12.6 Assigning Network Resources to 1354NN

Some restrictions apply on the Resource Assignment procedure to 1354NN:
a)
b)
c)
in order to assign an MSTrail it is necessary to have already assigned at least one HOLC;
in order to assign an HOTrail it is necessary to have already assigned at least one LOLC;
in order to assign a path, its NAPs shall be assigned.
So the suggested order to assign Network resources to 1354NN is the following (if the following
order is not respected by the operator the result could be unpredictable):
a)
b)
c)
d)
e)
f)
HOLCs;
MSTrail;
LOLCs;
HOTrail;
NAPs;
Path.
For deassigning resources from 1354NN the following applies:
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
b)
ED
in order to deassign an MSTrail it is necessary to have already deassigned all HOLCs;

in order to deassign an HOTrail it is necessary to have already deassigned all LOLCs.
03
957.130.882 U

198
96 / 198

12.5 Limitation of Qnn path provisioning lead by RM
13 EML SIMULATION
1AA 00014 0004 (9007) A4 ALICE 04.10

The 1354RM can handle simulated EML domains and mixed networks with real and simulated EMLs.
In particular 1354RM can work in a standalone configuration either populating RM DB with EML data only
or recovering a backup performed on a real RM plant.
13.1 Simulated EML data generation and EML registration

In the 1354RM a tool is provided to populate the RM database. The command is:
$ /usr/snml/databases/dbsnml/init/gen_load <simulated data file name>
where file name identifies the file that contains the data to load in the database.
N.B.
The RM database must be empty before to perform this operation.
N.B.
The RM doesnt execute any congruency checks about ports contained in specific NE.
After the DB population with the gen_load command all the EMLs must be registered as Simulated.
for TSDIM Network: execute in a root UNIX user window the command AddEML <EML domain>
(present in the /usr/snml/bin directory), then exit from PMC (Process Monitor) application and start
it again. At the end execute the manual startup of the FEP agents.
for SENIM Network: execute in a root UNIX user window the command RegisterAllEmlSim
(present in the /usr/snml/bin directory).
ED
03
957.130.882 U

198
97 / 198
The directory /usr/snml/databases/dbsnml/init contains a set of TSDIM Simulated data files and a set
of SENIM data files which can be used for the generation. In addition, an offline tool can be used to create
the desired network file. The procedure to create a simulated data file is described in the following:
a)
Create the simulated data file by means of the command:

/usr/snml/databases/offline_conf/conf_NE
b)
The system asks for:

File name.
Enter the filename and press Return.
c)
The system asks: Is filename a new file? . If you answer Yes you will have to enter all values,
otherwise the system wiil present you the actual file values, in order to modify them.
d)

EML domain
Enter the EML domain id and press Return.
EML userLabel
SHversion
e)
f)
Enter the EML userLabel and press Return.

press Return.

neType.
Return.
Enter the number correspondent to the desired equipment type and press
NEuserlabel
Enter the NE userLabel and press Return.
sitename
Enter the NE sitename and press Return.
Per each slot the following mask is presented:

SLOT n. ... List of boards
1
Board name 1
Board name 2
Board name n
1AA 00014 0004 (9007) A4 ALICE 04.10
To select the board, enter the number correspondent to the desired board and press Return.
g)
Execute steps e ) to f ) for all the network elements to specify.
h)
If you press Enter at the end of step f ), the application closes.
i)
The file created is placed under /usr/snml/databases/offline_conf
j)
Move or copy the file to the directory /usr/snml/databases/dbsnml/init, in order to render it

executable.
ED
03
957.130.882 U

198
98 / 198

13.1.1 Available Simulated data files
13.1.2 Simulated data file syntax

The syntax used in the simulated data file is as follows:

EML emlDomId=<eml domain Id> userLabel=<eml domain name> imType=<im type>
senImVersion=<senim version supported> reachable=<reachable flag> virtualEML=<virtual eml>
eml domain Id = Identifier of EML domain
eml domain name = EML Domain User Label
im Type = tsdIm or senIm
senim version supported (if imType=senIm) = Identifies the SENIM version that should be
supported by the defining EML. Its values must be set equal to v40
reachable flag = It specifies if the EML is reachable or not (its value can be True or False)
virtual eml = It specifies if the EML is virtual or normal.
NE neType=<ne type> userLabel=<ne name> tsdImVersion=<tsd version> siteName=<site name>
confType=<configuration type> version=<ne version>
ne type = Type of NE. Its value can be : ne1641sm, ne1651sm, ne1641smC, ne1651smC,
ne1661smC, ne1664sm, ne1641sx, ne1631fox, ne1654sl, ne1664sl, ne9600luM &
ne9600luH
ne name = Network Element User Label
tsd version (if imType=tsdIm) = It specifies the tsd version used (default=5.5)
site name = Location of NE
configuration type = For all NE types, but 1651SM & 1661SMC, it assumes the same value of
ne type substituting ne with cnf (e.g. ne1641sm has configuration type cnf1641sm). For the
1651SM & 1661SMC it specifies if the NE is Full Matrix or Null Matrix (cnf1651smNull or
cnf1651smFull / cnf1661smCNull or cnf1661smCFull).
ne version = It specifies the NE version used to check NE connectivity constraints (if no version
is known it could assume the value 9.9).
PORT technology=<port techno> physicalPortType=<port rate> sdhPortType=<SDH port type>
userLabel=<port name> interfaceType=<cable or optGen>
(the following row allow to define the topology address of tsd ports only)
Rack=<rack id> Subrack=<subrack id> Board_p=<board id> PortNumber=<port number>
port techno = It specifies the port is sdh or pdh.
port rate = Its value depends on port techno attribute
(techno=sdh) the admitted values are : stm1, stm4, stm16, stm64 & stm0
(techno=pdh) the admitted values are : c12, c3 (34 Mbit), c345Mb (45 Mbit), c4, c3C12
(framed 34 Mbit), c3Conf & c3C12Conf (configurable framed 34 Mbit), c4Conf &
c4C12Conf (configurable framed 140 Mbit).
SDH port type = this parameter should be specified for sdh ports only. Its values are : westAggr,
eastAggr, tributary, master, slave & generic.
port name = This string is added to the NE name to generate the port user label (NE name +
/ + port name).
1AA 00014 0004 (9007) A4 ALICE 04.10
BOARD <board type> <port prefix name>

(this command allow to define in one shot more than one PDH ports)
board type = It specifies the board type (NxR means N ports of R Mbits). Its values are 21x2,
3x34 & 3x45.
port prefix name = This string is added to the NE name to generate the port user label plus a
sequential suffix number (NE name + / + port prefix name + sequential number).
The NEs under the EML definition are contained in the EML domain, the ports and the boards under the
NE are contained in the NE.
ED
03
957.130.882 U

198
99 / 198
It is possible to transfer data of a real live network on a standalone RM configuration in order to work
with 1354RM product on this data.
1AA 00014 0004 (9007) A4 ALICE 04.10
To reach this goal it is necessary to perform a RM backup of the real network and than restore it on the
RM standalone. Finally on the RM standalone workstation the EMLs are to be registered as Simulated:
for TSDIM Network: execute in a root UNIX user window the command AddEML <EML domain>
(present in the /usr/snml/bin directory), then exit from PMC (Process Monitor) application and start
it again. At the end execute the manual startup of the FEP agents.
for SENIM Network: execute in a root UNIX user window the command RegisterAllEmlSim
(present in the /usr/snml/bin directory).
ED
03
957.130.882 U

198
100 / 198

13.2 Real Network Simulation

14 HOW TO CHANGE THE USERLABEL OF NES

In this section it is described the procedure to align the userlabel of NEs to the values reported on the
EMLs.
It is supposed that the operator has already changed the userLabel on the EML.
Please take care of the differences between QB3* (SENIM) and QB3 (TSDIM) NEs.
14.1 NEs with SENIM interface

a)
Stop emlObjAgent by using the process control
b)
Stop the process control
c)
By snml, execute the following shell command

export NLnochecks=TRUE
d)
By using the same shell, launch the process control with the command
mngAgent&
e)
Start emlObjAgent
f)
Execute the EMLsynchronize for each EML which contain NEs with userLabels which are modified.
With NLnochecks environment variable set to TRUE, every change on the attributes of NEs and Ports
is admitted. So, it is preferable to check all the attribute value changes sent during this alignment
phase. Be sure all the EMLs are aligned (the attribute emlDomainAlignement has to be equal to normal).
g)
Stop the process control.
h)
Execute the following shell command

unset NLnochecks
i)
Launch the process control and start again emlObjAgent.
j)
Eventually align the userLabel of pmNes and pmTps objects (see below).
1AA 00014 0004 (9007) A4 ALICE 04.10
14.2 NEs with TSDIM interface

a)
Execute the EMLsynchronize for each EML which contain NEs with userLabels which are modified.
b)
Eventually align the userLabel of pmNes and pmTps objects (see below).
ED
03
957.130.882 U

198
101 / 198
a)
By using the process control, stop the pmMng agent.
b)
By using snml, execute the following SQL procedure

14.3 Aligning the userLabel of PMNEs and PMTPs
$ORACLE_HOME/bin/sqlplus $NXNL_DATABASE
SQL> @/usr/snml/databases/dbsnml/admin/conv/alignPmUserLabel
The procedure requires the userLabel of the migrated NE (with TSDIM interface).
14.4 Moving ET from Generic to Meshed

a)
By using the process control, stop the topMngAgent_csa agent.
b)
By using snml, execute the following command:

$ /usr/snml/databases/dbsnml/admin/conv/etMigrationFromGenericToMeshed.com
1AA 00014 0004 (9007) A4 ALICE 04.10
It is required the Identifier of the elementary topology.
ED
03
957.130.882 U

198
102 / 198
15 MIGRATION PROCEDURE

In this section the migration procedures between RM 2.4 and RM5.2.x are described.
Every procedure requires the following environment variables:
a)
NXNL_DATABASE: it points to the current RM database. This variable is usually set by the profile
of the user snml;
b)
MIG_TAR: it represent a temporary directory where the tar files are stored. This directory must be
created with the permission set to readable and writable from everyone. If you choose the directory
/mig as mig_tar directory, you have to execute the following UNIX commands (by snml user):
mkdir /mig
chmod 777
c)
login as root user (by command <su root> not <su root> otherwise your environment are modified)
and execute:
MIG_TAR=/mig
#export MIG_TAR
d)
MIG_PAR: it points to a directory where the parameter files are present. The following UNIX command must be executed to set the proper value for this variable:
MIG_PAR=$DB_ROOT/admin/conv
#export MIG_PAR
e)
MIG_BACKUP: it represents the directory where the data files produced/used during the export/import phase are stored. This directory has to be created before the execution of the migration procedure. For example, if you choose the directory /mig_backup as mig_backup directory, you must execute the following UNIX commands (by root):
#mkdir /tmp/mig_backup
MIG_BACKUP=/tmp/mig_backup
#export MIG_BACKUP
1AA 00014 0004 (9007) A4 ALICE 04.10
Every migration procedure checks if these variables are correctly set. If a check fails, an error message
is displayed and the executions stops.
ED
03
957.130.882 U

198
103 / 198
15.1 1354RM R2.4 (NR3.1) to 1354RM R5.2.x Migration Procedure

1354RM R2.4 already installed in /usr/snml (see $SNML_HOME)
a)
Be sure RM and EMLs are aligned (execute EMLsynchronize for each EML and the global consistency audit/download).
b)
If you want to export also OVWMAPs, save by DNM the maps to be converted by DNM (select menu
File>Distribute maps>Store map images).
c)
d)
Stop 1354RM system if necessary (the database must be on instead), log in as root users and change your current directory to the old delivery home directory:
$ mngAgent shutdown control
$ mngAgent shutdown system
$ su root
# cd /usr/snml
e)
Extract the export database procedures from the 1354RM R5.2.x installation kit:
# uncompress c <1354RM_inst_kit> | tar xvf ./databases/dbsnml/admin/conv
Particularly, the following files are used during the export phase:
./databases/dbsnml/admin/conv/expDbRmRel
./databases/dbsnml/admin/conv/expDbRm.par
and a couple of file with extension sql and ctl for each table of the RM database with a
schema incompatible between RM2.4 and RM5.2.x (node table).
# cd $DB_ROOT/admin/conv
# chmod +x expDRmRel
f)
(if necessary), create the directories (named migbackup and mig_tar directories) where the data
migration files will be copied.
For example, if you want to create the directory /tmp/mig_backup to collect the data migration files,
and the directory /mig where tar files are saved, the following command have to be executed:
# mkdir /tmp/mig_backup
# mkdir /mig
g)
Assign the name of the migbackup directory to the MIG_BACKUP environment variable, and the
name of the mig_tar directory to the MIG_TAR environment variable.
For example, if the migbackup directory is /tmp/mig_backup and /mig is the migtar directory, the
following command have to be executed:
1AA 00014 0004 (9007) A4 ALICE 04.10
# MIG_BACKUP=/tmp/mig_backup
# export MIG_BACKUP
#MIG_TAR=/mig
#export MIG_TAR
Then, you have to assign the value of the MIG_PAR directory as below:
#MIG_PAR=$DB_ROOT/admin/conv
export MIG_PAR
ED
03
957.130.882 U

198
104 / 198

Preconditions:
h)
Change your current directory to the conversion directory:

i)
Perform the export procedure:

# ./expDbRmRel release 2.4
The procedure asks the operator some confirmations concerning:
the database to be exported (environment variable $NXNL_DATABASE)
the migbackup directory (environment variable $MIG_BACKUP)
the migtar directory (environment variable $MIG_TAR)
the directory for the parameters files (environment variable $MIG_PAR).
If the variables are correctly set, the operator must press <Enter> twice, otherwise the operator can
press <CtrlC> and set again the uncorrect environment variable.
The procedure creates (if necessary) the directory $MIG_TAR where data to be exported will be
saved.
The directory $MIG_BACKUP is saved and the file databaseRM24.tar is created in the $MIG_TAR
directory. This tar file contains all data of the ORACLEdatabase of RM2.4.
Then the procedure asks the operator if the OVWMAPs are to be exported. The following message
appears
Do you want to export MAPDB ? [y/n default y]
If the operator press either <N> or <n> (followed by <Enter>), the directory $NXNL_MAPDBAREA
is not exported, otherwise the file mapdbRM24.tar is created in the $MIG_TAR directory.
Finally, the operator can save the $MIG_TAR directory on tape. This is necessary when the RM5.2.x
must be installed over the RM2.4 and no extra WS are available. The following message appears
Do you want to save EXPORTfiles on tape ? [y/n default y]
If the operator press either <N> or <n> (followed by <Enter>), the directory $MIG_TAR is not saved
on tape.
In this case, the files databaseRM24.tar and mapdbRM24.tar in the $MIG_TAR directory can be
saved on an extra WS using the ftp command. The option bin of the ftp must be used to copy the two
files.
If some errors occur the procedure stops itself and prints the log filename where the error is described
(expDbRm.log in the $MIG_BACKUP directory).
Every time the procedure is executed, the previous log file is automatically saved as expDbRm.log.save.
If you previously selected the copy of tar files on tape, the following message appears:
1AA 00014 0004 (9007) A4 ALICE 04.10
Do you want to save EXPORTfiles on tape again ? [y/n default y]

If the operator press either <N> or <n> (followed by <Enter>), the directory $MIG_TAR is not more
saved on tape, otherwise another copy of tar files are saved on a new tape (please remember to change the tape after every operation).
ED
03
957.130.882 U

198
105 / 198
Install 1354RM R5.2.x delivery (see 3.1), creating a new database (variable NEW_DBSNML must
be set to yes value in /usr/snml/env_snml file (see 3.1.3)).
k)
Execute again the steps h), i) and j) if necessary.
l)
Change your current directory to the conversion directory (after the 1354RM R2.4 installation
DB_ROOT is the directory name of the new database):
m ) Be sure the system is off, otherwise shutdown it using the Process control
n)
Be sure the database is running, otherwise startup it using the Process control
o)
Perform the import procedure

# ./impDbRmRel release 2.4
The procedure asks the operator some confirmations concerning:
the database to be exported (environment variable $NXNL_DATABASE)
the migbackup directory (environment variable $MIG_BACKUP)
the migtar directory (environment variable $MIG_TAR)
the directory for the parameters files (environment variable $MIG_PAR).
If all the variables are correctly set, the operator must press <Enter> twice, otherwise the operator
can press <CtrlC> and set again the uncorrect environment variable.
The procedure creates (if necessary) the directory $MIG_TAR where data to be imported will be
saved.
First, the operator can choose if data to be imported have been stored on tape. The following message appears
Do you want to restore IMPORTfiles from tape ? [y/n default y]
If the operator press either <N> or <n> (followed by <Enter>), no files are restored from tape (it is
supposed the files databaseRM24.tar and mapdbRM24.tar if the OVWmaps have to be imported
have been previously copied in the /mig directory by an extra ws using the ftp command with the
bin option set), otherwise the tar files are restored from tape.
Then, the operator can choose if the OVWMAPs must be imported too. In fact, the following command appears
Do you want to restore MAPDB ? [y/n default y]
If the operator press either <N> or <n> (followed by <Enter>), the OVWmaps will not be imported.
In this case, the OVWMAPs will be rebuilt after the migration of the ORACLEdatabase of the RM.
If some errors occur the procedure stops itself and prints the log filename where the error is described
(impDbRm.log in $MIG_BACKUP directory). If no errors occur the 1354RM R5.2.x database is populated with data stored in R2.4 one.
1AA 00014 0004 (9007) A4 ALICE 04.10
Every time the procedure is executed, the previous log file is automatically saved as impDbRm.log.save.
ED
03
957.130.882 U

198
106 / 198

j)
1AA 00014 0004 (9007) A4 ALICE 04.10

N.B.
p)
Execute the full backup

N.B.
ED
The import procedure creates a big ORACLE tablespace named large_rbs_tbs. This
tablespace is dropped at the end of the procedure. However, if the import procedure fails
because of an ORACLE error on large_rbs_tbs tablespace (or large_rbs rollback segment), the following commands must be executed:
# rm $DB_ROOT/data/large_rbs_tbs.dbf
$DB_ROOT/etc/create_db (to be executed by snml)
The last command resets the entire ORACLE database.
Moreover, PDL files produced in RM2.4 couldnt be properly executed with RM2.3
(because of the portuserLabel change between SH1.2 and SH3).
03
957.130.882 U

198
107 / 198
This procedure has to be executed after the migration steps described in (15.1).
It registers the EML simulator agent of 1354RM (emlSimulAgent.exe) as the process which answers to
CMISE services requests forwarded to virtual Eml domains.
Without this registration, you will get Object Manager Not Found error messages for actions/gets/etc.
involving virtual Nes.
15.2.1 Prerequisites
Prerequisite 1: you have to know the list of emlDomainIds of virtual eml.
This can be done using Browser user interface manager, making a get on 1354RM (yellow) object (the
child of MULTI SNMLIM, labeled SNMLIM). Ask for Eml Domain, press the Filter button, select
Virtual equal to Virtual on the filtering mask. You will find all virtual eml(s). For each of them, make a
show/set attribute (select one of them, then press the lens icon); the requested Id is EML Domain Id attribute.
Note: very often, the only virtual EML is the one with emlDomainId = 0.
Prerequisite 2: you have to know UNIX root (superuser) password.
1AA 00014 0004 (9007) A4 ALICE 04.10

a)
Login as snml user, then change current directory to $NXNL_PRD/bin with the command
cd $NXNL_PRD/bin
b)
Get superuser (i.e. root) privileges issuing the following command (you will need root password):
su root
(Note: this is not the same as su root)
c)
start the registration of virtual eml domain with emlDomainId = <n> issuing
./RegisterSim n
Answer y if you are prompted for creation of VEML<n>simul.vlrf file.
ovaddobj utility will be invoked in order to registrate emlDomain <n> objects.
d)
Repeat step c ) for every virtual EML domain.
ED
03
957.130.882 U

198
108 / 198

15.2 Virtual EML registration on Communication Infrastructure (CI)
1AA 00014 0004 (9007) A4 ALICE 04.10

15.3 Migration Procedure of NEs

In the following, the steps to be executed when an NEs is changed are described. These steps must
be executed on RM5.2.x when:
a)
a QB3* NE is migrated in a QB3 NE one
b)
a QB3* NE is migrated in a new NE one (tipically when an NE chages its EML domain)
c)
a QB3 NE is migrated in a QB3 NE one (tipycally when an NE changes its neGroup)

The last two points are implemented with the same utility (see neTranslation).
ED
03
957.130.882 U

198
109 / 198
15.3.1 NE migration between QB3* and QB3 interface
In the following, a brief description of the procedure to migrate one NE between QB3* and QB3 interface
is done.
Two different cases are foreseen, ADms and DXCs.
a)
in case of ADMs, stop the supervision (all the alarms are cleared). In case of DXC, a procedure to
clear alarm is available on RM (see below)
b)
Prepare a file with the association between the old and the new portId (NE migration file). In case
of DXC, this file is computed by RM. Instead, for ADMs, a procedure on SH will be available to do
this. The file name is equal to the userLabel of the NE to be migrated. The format of the file is:
BEGIN FDN_MAPPING_FILE
<neUserLabel>
<oldSdhPortIdId> <newSdhPortIdId>
END FDN_MAPPING_FILE
c)
Stop the FEPPN process corresponding to the neGroup of the NE (when migrated in QB3)
d)
Execute a full backup of DB RM
e)
Create the new neGroup (if necessary).
f)
Execute the neMigration procedure in order to change all the fdnMapper of Ports (and NE too). This
procedure changes the userLabel of the NE (if required) and all the Ports accordingly to the TSD naming rules.(See 1.3.2.2).
g)
Start supervision on SH.
h)
Execute on RM a synchronizeEml on neGroup at the end of the neMigration. If this operation is sucessfully terminated (emlDomainAlignment=normal), the equipment is well converted in TSDIM,
otherwise the error messages have to be carefully analyzed and a restore of RM DB is required.
i)
Execute a consistency audit (mark audit) of NE.

During the consistency audit all the fdnMappers of the newtork objects are completely aligned.
Particularly:
1AA 00014 0004 (9007) A4 ALICE 04.10
j)
1)
MSCtps, HOCTPs and NAPs have to be aligned to the fdnMapper of the physical port;
2)
CAPs are aligned when the connection CTPCAP is aligned
3)
LOCTPs are aligned when their CAP is aligned.
Execute an alarm synchronization of NE
At the end, the equipment configuration of NE is well known by RM (the consistency status of all the object
is equal to normal). During the execution of the procedure, the NE to be migrated is in download disable
mode. The procedure changes the status for you. Alarm activity is suspended (this is due to the fact all
the network objects belonging to the NE are not aligned inside the RM database).
ED
03
957.130.882 U

198
110 / 198

15.3.1.1 Overview

15.3.1.2 Use of neMigration Tool (Qb3*/Qb3)
The tool neMigration performs the migration of NE in a new version QB3 (SH5).
The tool is executed by starting the shell script neMigration as snml user.
It is located in /usr/snml/databases/dbsnml/admin/conv directory.
You must set the following environment variables:
a)
MIG_LOG: it contains the directorys name where you want to save the migration.log file.
b)
MIG_BACKUP: it contains the directorys name where are located the migration data file.
For example, the following UNIX commands can be used in order to set these environment variables:
c)
$ export MIG_LOG=/users/snml/log
d)
$ export MIG_BACKUP=/users/snml/backup
MIG_LOG variable is assumed to be equal to MIG_BACKUP value. The tool also saves its log file into
MIG_BACKUP directory.
The utility creates a new windows containing the following functions:
1)
Prepare DXC Ports : this function prepares a input data file with old portid and new portid to
migrate the DXC. For ADM, the data file is provoded by the SH system.
2)
Check Data : this function checks all data involved in migration, (Ne data, Eml, ports, negroup
versions). It is also checked all the connection are supported by the target version of TSDIM..
3)
TSD Convert : this function performs the migration of Ne in new neGroup. During this phase
checks previously described are executed again..
The new neGroup Before (supporting the TSDIM interface) must also be created in RM database before
executing the last two steps..
When you start the Prepare DXC Ports option, two options can be selected
1)
Continue: to insert the SENIM Userlabel of the NE to be migrated.
2)
Return to main menu : to go back to the main menu.
In case of DXC, this option creates a data file for DXC and saves it in MIG_BACKUP directory that you
have set previously. The file have following format:
BEGIN FDN_MAPPING_FILE
<neUserLabel>
<oldSdhPortIdId> <newSdhPortIdId>
END FDN_MAPPING_FILE
1AA 00014 0004 (9007) A4 ALICE 04.10
file name is the userlabel of DXC.
ED
03
957.130.882 U

198
111 / 198
1)
Check Ne data : this option alows to verify the data file (if it is correct and complete)
2)
Check connectivity of Ne : it checks if the protected multi point cross connections on SH have
been implemented. in this case, the path userLabel and the nodenames when these crossconnections are present are reported to the operator. Th
The operator must remove all th protected legs (except for one)
3)
All : this function performs the options at point 1) and 2)
4)
Return to main menu: to go back to the main menu.
When you start the TSD convert option , the following option can be choosen by the operator:
1)
Clear alarm : this function clears the elemntary alarms correlated to networks objects belonging
to the NE to be migrated . The userLabel of the NE is requested by the operator.
2)
Convert Ne : this function performs the Ne migration.
3)
All : this function performs the options at point 1),2,3)
The operator can enter the following data:
4)
a)
userLabel : SENIM userlabel of the NE to be migrated
b)
neGroup : neGroupId (with TSDIM interface) where the NE is to be migrated
c)
neId : ID of the Ne int the new SH (with TSDIM interface)
d)
TSD user label : new user label of Ne (optional)., If not specified by the operator, it is assumed the NE doesnt change its userLabel.
Return to main menu: to go back to the main menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
At the end of the procedure, two choices can be selected by the operator, regarding the log file procedure:
ED
1)
Read log file: the operator want to read the log file
2)
Skip log file: the operator is not interested in analyzing the log file. However, it will be possible
to read it by using a text editor. Remember that the log file is $MIG_LOG/migration.log.
03
957.130.882 U

198
112 / 198

Check data option is composed by four options:

15.3.1.2.1 Error codes:

1)
Generic system error ! : system error, header file corrupted, etc.
2)
Error in parameters number or parameters type ! : the list of input parameters is not correct
3)
Database error ! : connection with DB is lost or DB is not available.
4)
Memory allocation error ,check your free memory ! : an internal error on heap has been found
5)
Database read fault ! : a get on DB is failed
6)
Error in number of Ne retrieved ! : this error is generated when two or more Nes with the same
userlabe was found
7)
Error in number of Node retrieved ! : this error is generated when two or more Node with the
same Id was found
8)
Database read wrong attribute ! : a wrong attribute value was found.
9)
Generic error ! : this error is generated when a procedural error was found, tipically during the
Ex: prepareDXCPorts phase.
10 ) Error in number of Tp retrieved ! : a protected multipoint connection was found but its TP list
is corrupted
11 ) Found switch connections in topology ! : a protected multipoint connection was found.
12 ) Ne not found in the database ! : The Ne with the specified userlabel is not retrieved in RM database
13 ) Migration file not found ! : the data file has not been retrieved in $MIG_BACKUP directory.
14 ) neGroup not found in the database ! : the new neGroup (TSDIM) is not retrieved in RM DB (it
is to be created offline)
15 ) neGroup is not TSDIM ! : the new neGroup involved in migration supports SENIM interface
16 ) New userLabel duplicate ! : the new userlabel of Ne is not unique.
17 ) Error in IM version ! : the Ne involved in migration is already equipped by TSDIM interface
18 ) Database write fault ! : a DB write is failed
19 ) Database delete fault ! : this error is generated when a DB delete on observed port is failed
20 ) Migration file doesn not exist ! : the data file is not present in $MIG_BACKUP directory.
1AA 00014 0004 (9007) A4 ALICE 04.10
21 ) Error in clear alarm ! : the disable alarm correlate to the Ne failed.
ED
03
957.130.882 U

198
113 / 198
The neMigration procedure changes all the informations in the RMdatabase in order to allow the execution of the download activity. During this phase, the network element is set how all the object were directly
created with the TSDIM interface. So, the disabledAlarms attributes of NAPs, CAPs, CTPs boundary and
PDH physical ports are modified if the connections are implemented on them. In other words, it is necessary that the proper alarms are enabled on the physical end points of the paths/trails wich are implemented
on them This task is executed by the RM when the TSDIM interface is used.
However, the neMigration procedure is not able to compute the proper Q3disabledAlarms on the entire
paths/trails; in fact, the procedure only works on objects belonging to the migrated Ne.
Then, it is possible that the Q3DisabledAlarms attributes of the transport Servers are not correct after a
migration of one NE. These attributes can be computed by the following steps:
a)
check if the PL/SQL packages are already load on your Oracle instance by using the command (as
snml)
$ORACLE_HOME/bin/sqlplus $NXNL_DATABASE
SQL> SELECT COUNT(*) FROM user_source where name=ALIGNENABALARMS;
b)
if the select statement of the previous step returns 1 row, please execute the following step, else the
package has to be loaded with the SQL COMMANDS:
SQL> @/usr/snml/databases/dbsnml/admin/conv/alignQ3AlarmsPck_spec
SQL> @/usr/snml/databases/dbsnml/admin/conv/alignQ3AlarmsPck_body
Pratically, the PL/SQL package must be loaded just either the first time this procedure is executed
or when the database is created again.
c)
execute the SQL command

SQL> @/usr/snml/databases/dbsnml/admin/conv/alignQ3Alarms
1AA 00014 0004 (9007) A4 ALICE 04.10
The procedure requires the userLabel of the migrated NE (with TSDIM interface).
ED
03
957.130.882 U

198
114 / 198

15.3.1.3 How to align the Q3disableAlarms attributes of paths/trails

15.3.2 neGroup modification

In order to modify the emlDomain of NEs with QB3* and Qb3 interface, the utility neTranslation must be
executed.
This procedure allows you to change the emlDomain (neGroup in QB3 terminology) in the RMDB. It is
supposed that during the neGroup modification activity:
a)
the SENIM/TSDIM object Identifiers dont change;
b)
the EML interface doesnt change.
You must start a shell script named neTranslation as snml user.

This program is located in /usr/snml/databases/dbsnml/admin/conv directory.
Before starting this script the following environment variablesmust be set:
a)
MIG_LOG: it contains the directorys name where you want to save the migration.log file.
b)
MIG_BACKUP: it contains the directorys name where are located the migration data file.
For example, the following UNIX commands can be used in order to set these environment variables:
c)
$ export MIG_LOG=/users/snml/log
d)
$ export MIG_BACKUP=/users/snml/backup
If the MIG_LOG variable is not defined, all the log files are saved in the $MIG_BACKUP directory.
The utility creates a new windows containing the following functions:
1)
Check Data : this function checks all data involved in migration, (Ne data, Eml, ports, negroup
versions).
2)
neTranslation : this function performs the translation of Ne in new neGroup, during this phase
(all the checks of point a) are executed again).
Before starting the checkData you also must create a new neGroup before.
When you choose the checkData option, two options can be selected
1)
Continue: to checks all the data which are used in the next phase;
2)
When you start the NeTranslation , two options can be selected

1)
Continue: to execute the translation of the emlDomain;
2)
1AA 00014 0004 (9007) A4 ALICE 04.10
If you choose the option 1), you must enter the name of the file containing the data of the NEs to be translated (complete pathname, if the directory of the file is not the directory when the utility is executed).
ED
03
957.130.882 U

198
115 / 198
The format of the neFdnMapper is dependent on the interface (SENIM or TSDIM) of the NE itself.
At the end of the procedure, two choices can be selected by the operator, regarding the log file procedure:
1)
Read log file: the operator want to read the log file
2)
Skip log file: the operator is not interested in analyzing the log file. However, it will be possible
to read it by using a text editor.
15.3.2.1 Error codes

1)
Generic system error ! : system error, header file corrupted, etc.
2)
Database error ! : database corrupted, connection with DB lost, etc.
3)
Memory allocation error ,check your free memory ! : an internal error on heap has been found
4)
Database read fault ! : a get on DB is failed
5)
Generic error ! : this error is generated when a procedural error was found
6)
Translation file error ! : the input data file is not correctly formatted.
7)
Error in IM version ! : this error is generated when the Ne involved in migration have different
interfaces (TSDIM versus SENIM and viceversa).
8)
Database write fault !: a DB write is failed
9)
Error in parameters number or parameters type ! : this error is generated in case of wrong number or type program parameter.
10 ) Translation file not exist ! :the data file is not present in $MIG_BACKUP directory.
11 ) Ne not found in the database ! : the Ne to be moved ins not present in RMDB
1AA 00014 0004 (9007) A4 ALICE 04.10
12 ) neGroup not found in the database ! : the neGroup involved in the migration is not present in
DB
ED
03
957.130.882 U

198
116 / 198

The format of the file is the following:

EMLIM_MOVE_FILE
<oldNeFdnMapper1> <newNeFdnMapper1>
<oldNeFdnMapper2> <newNeFdnMapper2>
........
<oldNeFdnMapperN> <newNeFdnMapperN>
END_EMLIM_MOVE_FILE

15.4 OVW Map Conversion from 1354RM R2.4 to 1354RM R5.2.x

a)
Restore mapdbRM24.tar (RM2.4)
b)
Start RM5.2.x
c)
Start OVW (Netview)
d)
Create the new map
e)
Open a map with the DNM command
f)
Save the map selecting the DNM command File>Distribute Maps>Store Map Image
g)
Execute the full backup.
File>Distribute maps>Get/List Map Images
15.4.1 Recover Maps after migration when changing ntwDomld

When migrating a RM to another one, or after trying to recovered a distributed map in a different RM,
installed with ntwDomId different of the previous one, the OV maps are no more useful, as they use the
ntwDomId attribute as the root of the naming tree for the objects in the map.
A tool is provided to change the references to the new ntwDomId, in order to made the maps still usable.
These steps must be executed before point b) of the previous paragraph.
15.4.1.1 Change ntwDomId on saved Maps
a)
Execute the following commands:

# MapChangeNtwDom <mapname> <new_NtwDomId>
where <mapname> is the name of the map to be converted;
b)
Now yo have the map again as an distrubuted map. To recover it, proceed as usual.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
NOTE: The old map is copied as $NXNL_MAPDBAREA/<mapname>.db.OLD. You can recover it, in case of errors, or delete it otherwise, to save disk space.
03
957.130.882 U

198
117 / 198
This procedure has to be executed after the migration steps described in (15.1).
It registers the EML simulator agent of 1354RM (emlSimulAgent.exe) as the process which answers to
CMISE services requests forwarded to virtual Eml domains.
Without this registration, you will get Object Manager Not Found error messages for actions/gets/etc.
involving virtual Nes.
15.5.1 Prerequisites
Prerequisite 1: you have to know the list of emlDomainIds of virtual eml.
This can be done using Browser user interface manager, making a get on 1354RM (yellow) object (the
child of MULTI SNMLIM, labeled SNMLIM). Ask for Eml Domain, press the Filter button, select
Virtual equal to Virtual on the filtering mask. You will find all virtual eml(s). For each of them, make a
show/set attribute (select one of them, then press the lens icon); the requested Id is EML Domain Id attribute.
Note: very often, the only virtual EML is the one with emlDomainId = 0.
Prerequisite 2: you have to know UNIX root (superuser) password.
1AA 00014 0004 (9007) A4 ALICE 04.10

a)
Login as snml user, then change current directory to $NXNL_PRD/bin with the command
cd $NXNL_PRD/bin
b)
Get superuser (i.e. root) privileges issuing the following command (you will need root password):
su root
(Note: this is not the same as su root)
c)
start the registration of virtual eml domain with emlDomainId = <n> issuing
./RegisterSim n
Answer y if you are prompted for creation of VEML<n>simul.vlrf file.
ovaddobj utility will be invoked in order to registrate emlDomain <n> objects.
d)
Repeat step c ) for every virtual EML domain.
ED
03
957.130.882 U

198
118 / 198

15.5 Virtual EML registration on Communication Infrastructure (CI)

16 UPDATE OF MSSPRING INFOS (MSSPRING TAKEOVER)

In the following its described the procedure which is able to modify the MS_SPRINGrelated information
contained in the node objects that belong to an MSSPRING ring (=et).
This is required when 1354RM takes over an existing network previously administered by another OS with
MSSPRING rings containing paths/trails that you want to preserve without traffic hits. In this case, you
have to provide manually the informations (values of NODE.NODEINET and NODE.SEQNUMINET
database columns) that 1354RM automatically downloads to NEs (at ring implementation time); this infos
are used in squelching tables management (see below). If you dont provide this infos, RM will download
the default ones, so overwriting the correct ones and making squelching tables not consistent. The target
is to put in 1354RM database the same values that are stored in the NEs; this way, the
implementationtime download will have no effect.
16.1 Prerequisites
a)
The ring(s) that you want to update has(have) to be activated.

When all the steps of the procedure are completed, you will have to implement the ring(s).
b)
You have to know the NODE.NODEINET and NODE.SEQNUMINET actually stored in NEs. If you
dont know them, a way to obtain them using Craft Terminal equipment is suggested in the following.
Nodes in a MSSPRING are numbered clockwise starting from zero and ending in <number of nodes in
MSSPRING> 1). This is the SEQNUMINET of NODE table information in RM terminology, and the
nodePosition field of ringMapInfo attribute of mSSPRingProtection MOC in SENIM terminology.
Every node has a labeling number whose value is between 0 and 15. The only requisite is that no node
has this number equal to another one. This is called the NODEINET of NODE table in RM terminology,
and both the nodeId attribute of mSSPRingProtection MOC and the nodeId field of ringMapInfo attribute
of mSSPRingProtection MOC in SENIM terminology.
This labeling number is mainly used to identify nodes in squelching tables. If the values dont match, the
whole MSSPRING protection mechanism is compromised.
Every Network Elements knows this informations for all nodes, i.e. it has hardware registers containing
all the (SEQNUMINET, NODEINET) mapping for every node.
1AA 00014 0004 (9007) A4 ALICE 04.10
To retrieve this information from an existing network a possible way is to use a Craft Terminal connected
to Network Elements.
Please refer to document 1664 SMECT V2.0 : SYNCHRONOUS MULTIPLEXER 1664 SM RELEASE
2.0 EQUIPMENT CRAFT TERMINAL (and subsequent versions).
See MSSPRING CONFIGURATION chapter, MSSPRING CONFIGURATION table, Ring Map
sequence. In this table:
a)
the (SEQNUMINET, NODEID) infos are listed in ascending order of SEQNUMINET,

possibly starting with 1 instead of 0. In RM database, the first node has to be always zero,
so adapt this information accordingly.
b)
The name used for NODEINET is node Identifier.
ED
03
957.130.882 U

198
119 / 198
a)
b)
Stop 1354RM system if necessary (but not the database, which has to be on) using Process Control
facility.
c)
login as snml user.
d)
Enter the MSSPRING update procedure:

./updMsspring
First of all, the procedure displays some warnings and informations.
Check all, expecially this one:
the database to be managed (environment variable $NXNL_DATABASE)
Then, the procedure asks the operator for confirmation (message Do you want to continue ?).
If the variable $NXNL_DATABASE is correctly set, the operator must enter y, otherwise the operator
can enter n (feel free to press <CtrlC> if you like) , (re)set the uncorrect environment variable, and
restarts ./updMsspring. No operation on database is performed until you enter y.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.: if any errors occur the procedure will stop.

Check the logfile updMsspring.log (which is created in the current directory) to diagnose the error.
Every time the procedure is executed, the previous log file is automatically saved as
updMsspring.log.old.
e)
Select the option Dump all userlabels of MSSPRING.

The procedure will create a file (whose name you can find on the screen) containing all userlabels
of MSSPRING rings found into database. The format is simply the userlabels enclosed in double
quotes, one per line.
Delete the lines containing the userlabels of the rings(=et) you dont want to update.
f)
Reenter the procedure, then select the option Dump all nodes of all rings ....
Now you will have another file with all MSSPRING related informations of the nodes of the rings you
specified in the previous step.
This files (whose actual name you can find on the screen) will be called nodedata file in the following.
g)
Edit the nodedata file.

You have only to change NODEINET and SEQNUMINET values to reflect the new ones.
In more details, you will find lines like:
NODE WITH USERLABEL=node 3 of Northern Seattle MS ring: NODEINET=1 SEQNUMINET=0
If you want to make NODEINET=2 and SEQNUMINET=1, change to
NODE WITH USERLABEL=node 3 of Northern Seattle MS ring: NODEINET=2 SEQNUMINET=1
In other words, think this file as a form.
Dont change the file any other way, e.g. by deleting/adding lines. If you modify anything different from
the values of NODEINET and SEQNUMINET, the file will be refused.
Expecially, do NOT modify userlabels any way.
h)
Reenter the procedure, then select the option Load nodes data ... into database.
The nodedata file will be compiled in sql format then submitted to sqlplus Oracle(TM) utility.
If there is any error regarding the format of nodedata file, simply correct it, then repeat this step.
If all your efforts eventually fail, perform a full database restore.
ED
03
957.130.882 U

198
120 / 198

16.2 Procedure steps

i)
Now the datas are inserted in RM database. When you will implement the modified MSSPRING
rings(=ets), the datas you have just inserted will be used by RM system. Mainly, they will be forwarded
to lower OS layers (currently to SH system).
16.3 Format of nodedata file

Here is an example of the nodedata file required as input of step h ):
ET WITH USERLABEL ringA:
NODE WITH USERLABEL nodeA1: NODEINET=4 SEQNUMINET=0
NODE WITH USERLABEL nodeA2: NODEINET=5 SEQNUMINET=1
ET WITH USERLABEL ringB:
NODE WITH USERLABEL nodeB1: NODEINET=6 SEQNUMINET=1
NODE WITH USERLABEL nodeB2: NODEINET=14 SEQNUMINET=0
16.4 Loading of a prebuilt nodedata file
1AA 00014 0004 (9007) A4 ALICE 04.10
You have to execute all procedure steps until step f ) (included), set the environment variable
NXNL_EXTERNAL_NODEDATA to the name of the prebuilt nodedata file, then perform the same actions
as step h ) but selecting option Load nodes data from external source into database instead of option
Load nodes data ... into database. The procedure will ask you for data file name confirmation.
If something goes wrong, first of all compare your file with the one generated in step f ), to check if you
have made some syntax error. Note that the order of rows doesnt matter, as far as all NODE ... rows
regarding nodes of the same ring are grouped together under the ET .. row of the ring that they belong
to. Also note that white spaces (blanks) of userlabels are meaningful, i.e. ringNumber1 is not the same
as ringNumber1 (note the ending blank).
ED
03
957.130.882 U

198
121 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.882 U
198
122 / 198

APPENDIX A INTEGRATION OF 1354RM WITH A1330AS
A.1 Installing A1330 AS

This procedure must be executed each time a new delivery of A1330AS and 1354RM has to be installed.
After the execution of the following procedure the A1330 IM processes will be integrated in the 1354RM
PMC (see 7.2).
In order to integrate the 1330AS with the 1354RM you have to execute the script file present in the directory
/usr/snml/etc with the name install_A1330.
This procedure works only if no old AS installation is present (e.g. /usr/A1330 link is present).
Execute the following commands :
# su root
# export ALARM_DIR=<A1330_installation_root_directory>
# [/usr/snml/etc/trace] /usr/snml/etc/install_A1330 <full_pathname_1330AS_inst_kit> [IM | US]
N.B.
The procedure, in order to grant a proper installation, check that the $ALARM_DIR
directory is empty, otherwise it gives an error.
If the install_A1330 procedure is started with the etc/trace script, it will produce a trace file of the procedure
install_A1330 called /usr/snml/etc/install_A1330.trc.
The IM or US parameter is not related to RM, but to A1330AS product. IM means that IM 1330AS
processes will be installed on RM workstation, US means that on RM workstation only AS user interface
is installed and configured.
N.B.
It is necessary to verify the content of the im_host_conf file, since it is generated by the
install_A1330 procedure.
A.2 Deinstalling A1330 AS

In order to remove an AS installation the following procedure is available:
# su root
# /usr/snml/etc/deinstall_A1330 [IM | US]
The IM or US parameter is not related to RM, but to A1330AS product. IM means that IM 1330AS
processes will be configured to run on RM workstation, US means that on RM workstation only AS user
interface is configured to run.
To execute it the US processes of AS have to be stopped manually. The procedure executes the following
steps:
1AA 00014 0004 (9007) A4 ALICE 04.10
a)
b)
c)
d)
it stops the IM AS agents;

it deregistrates AS agents;
it removes the AS installation;
it removes the /usr/A1330 link.
After the running of the procedure 1354RM PMC do not handle any more the AS agents.
N.B.
ED
It is necessary to verify the contents of the im_host_conf file, since it is generated by the
deinstall_A1330 procedure.
03
957.130.882 U

198
123 / 198
1330AS is provided with a default US customization in order to see only alarms relevant in 1354RM
environment and to distinguish them by their typology. All the AS1330 users have the possibility to change
the default customizations (HMI Layout, Counter Customizations, Colors, etc.) and so to work in a own
customized AS environment. These customizations are not saved at the end of the work session in order
to not propagate them to all the AS users, even if at USM exit AS requests for customizations saving.
The only user that can make persistent changes to 1330AS customizations is snml and these changes
are effective for all the users.
When e new configuration is made effective by running us_config_A1330 all the changes made by snml
are lost and is restored the initial default customizations.
A.3.1 Swedish language
In order to let ASUSM Components manage alarms containing swedish chars in the right way do the
following operations as nnml user:
$ cp /usr/snml/conf/AS_graphicResources /usr/snml/conf/AS_graphicResources_english
$ cp /usr/snml/conf/AS_graphicResources_sv_SE /usr/snml/conf/AS_graphicResources
Now all the following start of ASUSM Components will be able to manage swedish chars using roman8
fonts.
In order to roll back the configuration to the default one (ASUSM displaying alarms in english) perform
the following commands as nnml user:
1AA 00014 0004 (9007) A4 ALICE 04.10
$ cp /usr/snml/conf/AS_graphicResources_english /usr/snml/conf/AS_graphicResources
ED
03
957.130.882 U

198
124 / 198

A.3 A1330 AS customization

APPENDIX B INTEGRATION OF 1354RM WITH GENERIC OSOS INTERFACE

B.1 Generic OSOS Interface Subsysystem

Generic OSOS Interface is a product that exports, to external applications, alarm informations managed
by AS1330 Subsystem.
In the following GENOS stays for Generic OSOS Interface.
Depending on AS1330 subsystem version there is a compatible Generic OSOS Interface version which
is able to communicate with it (see Release Notes of OSOS Interface).
B.2 Generic OSOS Interface Installation

Execute the following commands to launch the installation script:
# su root
# export GENOS_DIR=/alcatel/GENOS
# /usr/snml/etc/install_genos <tar_file_installation_kit> <ALL | SNMP | TCP/IP>
Where:
<Tar_file_installation_kit> is the full pathname of installation kit released for integration GENOS with
1354RM.
<ALL | SNMP | TCP/IP> specifies the type of protocol the Generic OSOS Interface Processes use
to export alarm informations:
SNMP : SNMP Protocol is used
TCP/IP : TCP/IP Protocol is used
ALL : All the above protocols are used to export alarm info.
After the procedure execution GENOS processes are integrated in the 1354RM PMC.
The procedure install also a graphical tool to configure the exported alarm format, the keyword for the
authentication and informations on GENOS Processes configuration. To execute it launch the script
/usr/1353sh/tools/genos/user_config.tcl.
1AA 00014 0004 (9007) A4 ALICE 04.10
With the GENOS installation are provided also graphical tools (dependingly on Protocol type) that simulate
external OS communicating with Generic OSOS processes to export alarm informations. To execute
these tools launch the scripts /usr/1353sh/tools/genos/snmp_eos.tcl for SNMP protocol and
/usr/1353sh/tools/genos/eos.tcl for TCP/IP protocol.
N.B.
GENOS product cannot be installed everywhere in 1354RM File System. The installation is
made under the area /usr/1353sh/genos, this limitation is due to specific conditions of GENOS
product. After the installation procedure the link /usr/genos is created and points to
/usr/1353sh/genos.
N.B.
GENOS product can be installed only on a 1354RMIM.
ED
03
957.130.882 U

198
125 / 198
B.3 Generic OSOS Interface deinstallation
# su root
# /usr/snml/etc/deinstall_genos <full_pathname_tar_file_deinstallation_kit>
1AA 00014 0004 (9007) A4 ALICE 04.10
The procedure, without using any configuration file, determines the installed product version and removes
the installation area, and the registrations inside the 1354RM PMC.
ED
03
957.130.882 U

198
126 / 198

Execute the following commands to launch the deinstallation script:

APPENDIX C INTEGRATION OF 1354RM WITH SEC SECURIYT SUBSYSTEM
C.1 SEC Architecture on 1354RM System

The SEC Subsystem is composed of two permanent processes:
secim process which is the agent of the Security Subsystem and keep all the informations related
to the users and the system;
secim process have to be running only on 1354RMIM.
lss process which is a kind of gate for applications who are interested on user Security profile. There
is one lss process for each workstation/server belonging to the 1354RM system (1 for each
presentation and each IM).
These permanent processes are configured to automatically run everytime just after the installation.
The SEC integration on 1354RM, as a first step, is intended only for the integration of Security
Management within AS (Alarm Survelliance). This means that each 1354RM operator using AS is able
to view/manage only alarms coming from Network resources that it can manage as in RM Browser
In order to have inside SEC Subsystem all the informations concerning Security, SEC is also integrated
in SMF, in order to get informations related to new users, user removal, and initiator mgt. Moreover the
integration of SEC in SMF is also related to the Operator Backup. Each time a new Operator backup is
performed also SEC database is backuped.
If on top of 1354RM is installed also 1353SH software (Master or Presentation) for cohosted or
presentation installations you have to install SEC for SH using the axinstallGui.ptk procedure and SEC
for RM as described below
1AA 00014 0004 (9007) A4 ALICE 04.10
Keep into account that the SEC installations for RM and SH are different, the integration schemas and the
configuration steps are different.
ED
03
957.130.882 U

198
127 / 198
C.2 Installing SEC Subsystem
After the execution of the following procedure the SEC processes will be integrated in the 1354RM System.
In order to integrate SEC with the 1354RM you have to execute the script /usr/snml/etc/install_SEC.
This procedure works only if no old SEC installations for RM are present (e.g. /usr/sec link is present).
SEC 5.0 is supported on 1354RM.
Execute the following commands :
# su root
#
[/usr/snml/etc/trace]
/usr/snml/etc/install_SEC
<Target_installation_full_pathname>
<full_pathname_SEC_inst_kit>
If the install_SEC procedure is started with the etc/trace script, it will produce a trace file of the procedure
install_SEC called /usr/snml/etc/install_SEC.trc.
N.B. The procedure, in order to grant a proper installation, check that the choosen target installation
directory is empty, otherwise it returns an error.
N.B. Due to SH installation procedure limitation, if SEC for RM has to cohexist with SEC installation for
1353SH (cohosted or SHPresentation) installation, install first SEC for SH using the axinstallGui.ptk tool.
N.B. If a different SEC instance is alredy installed (after cohosted or 1353SH presentation installation) on
the target 1354RM host STOP all the running SEC processes with the script
/usr/1353sh/install/script/stop_security.sh
After the SEC installation on top of RM restart the SEC processes installed on top of SH with the script
/usr/1353sh/install/script/start_security.sh . After the installation the link /usr/sec is created in order to point
to the target installation directory choosen.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B. In the case in which SEC is alredy installed on RM please do a Backup of Operator datatype, deinstall
old SEC, install the new version of SEC and perform a Restore of the Operator datatypes. If you want to
install a new version of SEC it is possible that the DB have to be migrated.
ED
03
957.130.882 U

198
128 / 198

This procedure must be executed each time a new delivery of SEC and 1354RM has to be installed.
C.3 Deinstalling SEC

In order to remove SEC installation the following procedure is available:

# su root
# /usr/snml/etc/deinstall_SEC
The procedure executes the following steps:
a)
it stops all the SEC processes running on the host (only related to RM installation);
b)
it removes the system configurations related to SEC;
c)
it removes the /usr/sec link;
d)
it removes all the files related to the SEC installation.
N.B.: Due to SEC installation limitation during this procedure all the installed SEC subsystems have to be
stopped.
If
SEC
on
top
of
SH
installation
is
installed
run
the
script
/usr/1353sh/install/script/stop_security.sh.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.: After the deinstallation all the other SEC subsystems installed have to be restarted at hand.
(/usr/1353sh/install/script/start_security.sh)
ED
03
957.130.882 U

198
129 / 198
SEC Subsystem is provided with a default customization for which on an RM is automatically configured
to run secim process if RMIM and lss process for each kind of RM (IM/US).
The default configurations are put in the directory /usr/sec/1354RM_<NTWDOMAIN>.
In order to distinguish 1354RM SEC processes from the 1353SH ones the RM processes are called
<process_name>_1354RM_<NTWDOMAIN>.
The SEC configuration is also related to the automatic start of SEC process: in the /etc/inittab file is inserted
1
line
for
each
permanent
SEC
process.
This
line
invokes
the
script
run_SECIM|LSS_1354RM_<NTWDOMAIN> that checks for SEC abilitation to run and launch the
secim|lss_1354RM_<NTWDOMAIN> process. The automatic start of SEC processes is set on runlevel
4 that is the 1354RM runlevel default. No checks are performed on the 1354RM effective runlevel (it
is supposed to be 4).
During Operator Backup and Restore the SEC subsystem is stopped in order to add to the Operator
Informations also Informations related to SEC. The actions related to SEC start and stop are automatically
launched by SMF.
If some problem occurs during SMF>Operator Administration and SEC DB is not updated on changes
executed on RM, it is possible to launch the script as snml user through the SMF:
/usr/sec/integration/script/alignsecdb
This procedure starts from the last well finished SEC commands and alignes the SEC DB to the actual
RM Security definitions.
If at login time the user receives a Message Box saying:
Security for 1354RM_<NTWDOMAIN> is not activated.
Please contact your System Administrator,
the problem is that the user is not defined in the SEC DB, or the SEC Subsystem has been stopped
(Restore proc.) or internal error.
N.B.: If the Message does not include the string 1354RM, this means that it belongs to the SEC installed
for SH.
Restrictions:
1AA 00014 0004 (9007) A4 ALICE 04.10
SEC 5.0 doesnt manage the scheduling time. This means that if an user has a scheduled rule this rule
is applied everytime. This limitation is not due to the integration level but to the fact that SEC 5.0 doesnt
support it.
ED
03
957.130.882 U

198
130 / 198

C.4 SEC Administration

C.5 Alarm Access Configuration

Even if SEC has to be not installed on top of 1354RM, in order to be able to use AS change the following
files:
/usr/A1330/data/ascurusm_<hostname>_<Ntw Domain>/param.cfg
/usr/A1330/data/ashistusm_<hostname>_<Ntw Domain>/param.cfg
/usr/A1330/data/ashistusm_<hostname>_rec<Ntw Domain>/param.cfg
in the following way:
SEC_ENABLED
True
have to be changed in
SEC_ENABLED
False
Depending on 1354RM user definitions the following AS Access Rights are granted:
System Profile
AS Access Rights
Alarm Access Rights
OSAdministrator
ADMIN
MGT
Administrator
ADMIN
MGT
Constructor
VIEW
MGT
PathBuilder
VIEW
MGT
LookOnly
VIEW
Where:
AS Access Rights means the AS accessability, by users, in terms of AS Administration:
ADMIN: Users can invoke AS Administration and Synchronization
VIEW: Users can invoke AS Synchronization but cannot interact with AS Administration functionalities
Alarm Access Rights shows the Alarm accessability rules that are allowed to user:
1AA 00014 0004 (9007) A4 ALICE 04.10
MGT: Users that have this capability, if allowed by the NAD Rule (see below), can manage accessible
alarms ( acknowledgement).
ED
03
957.130.882 U

198
131 / 198
Alarm Ac- Physical

cess Type Link
Alarms
MSTrail HoTrail
Alarms
Alarms
Path
ProcessAlarms
ing Alarms
AC_R_SNML
MGT
AC_R_PAYMAN
MGT
AC_R_PADMIN
MGT
AC_R_TOPMAN
MGT
AC_R_PATHRO
RO
AC_R_VPN
RO
X*
AC_R_EVPN
RO
X*
AC_R_RVPN
RO
X*
AC_R_PMSNML
RO
AC_R_PMADMIN
RO
AC_R_PMRO
RO
AC_R_PMVPN
MGT
AC_R_PMVPNRO
MGT
AC_R_NN
MGT
X*
AC_R_PATHALL
MGT

RM Rule
X
X
X
X
Where:
Alarm AccessType shows the alarm accessability
MGT means that user have the possibility to Acknowledge alarms (ManaGemenT)
RO means that user can only access alarms in a view mode (ReadOnly)
The MGT Alarm Accessability is granted if allowed by the System Profile (previous table) otherwise (for
LookOnly users) is set to RO.
X show which alarm types that can be accessed by user with the corresponding NAD Rule associated
X* show alarm types (only marked with user NAD) that can be accessed by user with the corresponding
NAD Rule associated
1AA 00014 0004 (9007) A4 ALICE 04.10
In order to provide a flexible way to configure AS Access on Alarm the configuration file
/usr/snml/conf/sec/1354RM_Ruler is provided.
This file drives the user Access Rights definition in the SECDB must be modified before the SEC
installation in order to keep coherent user creations.
ED
03
957.130.882 U

198
132 / 198

In particular in order to give to LookOnly users the possibility to manage all the Alarms without keeping
into account the RM Rule change the line:
System_Profile
:
LookOnly
ASHISTUSM_FAD@AsHistoricalUsm :
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,
as follows:
System_Profile
:
LookOnly
:ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm,
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm, ASHISTUSM_FAD@AsHistoricalUsm
On the other side, if the LookOnly users Accessability have to be extended to manage alarms depending
on 1354RM Access Rules (second table), change the line:
System_Profile
:
LookOnly
ASHISTUSM_FAD@AsHistoricalUsm :
as follows:
System_Profile
:
LookOnly
:
ASHISTUSM_FAD@AsHistoricalUsm : ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.: The remaining of the file have to be left unchanged.
ED
03
957.130.882 U

198
133 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.882 U
198
134 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10

APPENDIX D COMMAND FILE SPECIFICATION

This appendix contains a brief description of command file format which permits to manage paths and
trails. This command file will be used from 1354RM either to rebuild its database or to take over a network
previously managed with a different product of network management. A specific tool (named rmBatchUtil)
of the product scans the command file and give the agents the proper actions to execute the commands.
This tool will accept the command file name as input parameter. The commands are case sensitive.
ED
03
957.130.882 U

198
135 / 198
D.1 Command Description
a)
b)
c)
d)
e)
f)
g)
h)
i)
j)
k)
command to set the network where commands will be executed (called working network);
commands to define, delete, update, deallocate, (de)implement and protect/unprotect paths (with or
without constraints);
commands to define, delete, update, (de)allocate, (de)implement, protect/unprotect and configure
trail (with or without constraints);
commands to change NAD to paths, nap, trails and link connections;
commands to treat PM features ( e.g. creating and removing measures, relating a tp to some
measures);
commands to deal with objects of class aSAProfile;
commands to manage objects of class restRule;
command to manage connection in topology.
commands to create, remove, (de)implement topology and physical connection;
commands to upload, remove Nap;
commands to configure et and physical connection;
Comment lines can also be introduced in the command file (for example to document a particular
command).
1AA 00014 0004 (9007) A4 ALICE 04.10
A command file may contain all types of commands. However, it is important to set the work network before
executing the commands on paths and trails. It is possible to set the work network specifying an input
parameter.
ED
03
957.130.882 U

198
136 / 198

Some different types of commands are recognized by this specific tool:

D.1.1 Syntax Description

This document uses a BNF notation to describe the syntactic structure of the command. This notation uses
the punctuation showed below:
braces with vertical bars { | } means you must use one of the items in the braces separated by vertical
bars;
brackets [ ] means you can optionally use the item in the brackets. If the brackets enclose multiple
items separated by vertical bars |, you can use any one item or none at all;
ellipsis ... means you can optionally repeat the previous item multiple times.
underline means if you omit all bracketed items, the underlined item will be use by default.
We also use the definition showed below:
<string>: its a sequence of character between single quote or double quote . or numeric.
If double quote are used, then single quotes can be used inside the string.
Ex: userLabel di prova
userLabel di prova
userLabel di prova
The unadmitted characters are:
(tab)
|
(pipe)
\\
(backslash)
(tilde)
(backquote)
(double quotes)
<number>: it is a sequence of digits.

Ex: 32
:= it means an expression is defined.
<date>: the format of the date is: YYYY/MM/DDhh:mm:ss (YYYY four digit of year and > 1970; MM:
month (0112), DD: day of month (0131) hh: hour of day(0023); mm: minute (0059); second
(0059)). See the SET command for further information about time reference.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
In the previous text special characters are in bold to highlight them. In the following syntax
descriptions no bold fonts are use.
03
957.130.882 U

198
137 / 198
D.1.2 Setting time reference.
The SET command can be used to choose a time reference for dates. If the local time reference is chosen
then all dates are converted to GMT0 time (GMT0 and UTC are functionally equivalent). This is the typical
behavior of a US application. If the GMT0 time reference is set then no conversion is applied to dates. This
is the right behavior for executing a redolog operation.
The default behavior is to apply date conversion to GMT0 time.
D.1.2.2Syntax
SET local END
SET gmt0 END
D.1.3 Setting network
D.1.3.1Description
The SET command defines the number of the network where the commands will have effect.
D.1.3.2Syntax
1AA 00014 0004 (9007) A4 ALICE 04.10
SET ntwId <number> END
ED
03
957.130.882 U

198
138 / 198

D.1.2.1Description
D.1.4 Path commands
1AA 00014 0004 (9007) A4 ALICE 04.10

D.1.4.1Description
SETpath:
it permits to set default values for attributes o to be specified at the path creation
(definition) time.
CREATEpath:
it defines a path.
CONSTRpath:
it defines constraints on path for routing purposes. if the constraint list is void,
it deletes all constraints previously defined on the path.
ALLOCpath:
it allocates resources on defined path.
DEALLOCpath:
it deallocates resources on implemented path.
IMPLpath:
it implements an allocated path
DEIMPLpath:
it deimplements an implemented path.
DELETEpath:
it deletes a defined path.
UPDATEpath:
it updates the attribute of the paths.
PROTECTpath:
it changes the protection on an existing path.
ADDLEGpath:
it adds a leg (and/or simply a NAP) on an existing path.
REMOVELEGpath:
it removes a leg (and/or simply a NAP) on an existing path.
COMMISSIONpath:
an implemented path is declared commissioned (no change are possible).
UNCOMMISSIONpath:
a commissioned path has to become implemented (for example to reroute the

path).
UPDALRpath:
it updates the alarmPropagationRule of an existing path.
CONNECTpath:
it connects paths Tp.
DISCONNECTpath:
it disconnects paths Tp.
ELEMALARMNGpath:
it updates the Q3 PDH/SDH alarm enabling rule.
SPLITpath:
it splits an existing trail in two distinct paths.
JOINpath:
it joins two distinct paths.
ED
03
957.130.882 U

198
139 / 198
[ pathType unidirectionalPtoPto | pathType unidirectionalBroadcast |

pathType bidirectionalPtoPto ]
[ pathRate lo2Mb | pathRate lo34Mb | pathRate ho140Mb| pathRate lo45Mb]
{ protType notProtected | protType shSegmentProtected |
protType sh1Plus1EToEProt | protType enhancedProtected }
[ allocRule automatic | allocRule user ]
[ allocationConstraint notAlarmedResourcesOnly |
allocationConstraint noRestriction ]
[ implRule automatic | implRule user ]
{userId
<string>}
[ msProtProfile normal | msProtProfile protPref]

[ comment1 <string> ] [ comment2 <string> ] [ comment3 <string> ]
not_upd_path_attributes:= [alarmPropRule whenDefined |

alarmPropRule whenAllocated |
alarmPropRule whenImplemented | alarmPropRule whenCommissioned]]
[pmAutomatic false | pmAutomatic true]
[pathGroup <string>]
[ sdhAlrEnabRule onImplementation | sdhAlrEnabRule onCommissioning |
sdhAlrEnabRule manual ]
[ pdhAlrEnabRule onImplementation | pdhAlrEnabRule onCommissioning |
pdhAlrEnabRule manual ]
path_attributes:=
[<upd_path_attributes> | <not_upd_path_attributes> ]
SETpath
<path_attributes>
END
user_label := <string>
port_name := <string>
node_name := <string>
1AA 00014 0004 (9007) A4 ALICE 04.10
tp_path_list :=
ED
{ nap <port_name> usedDir bidirectional |

nap <port_name> usedDir source |
nap <port_name> usedDir sink |
nap <port_name> usedDir notMeaningful |
node <node_name> usedDir bidirectional [portName <port_name>] |
node <node_name> usedDir source [portName <port_name>] |
node <node_name> usedDir sink [portName <port_name>] |
node <node_name> usedDir notMeaningful [portName <port_name>] }
03
957.130.882 U

198
140 / 198

upd_path_attributes :=

CREATEpath
userLabel <user_label>
<path_attributes>
endTpList
<tp_path_list>
<tp_path_list>
[... <tp_path_list>]
END
END
ctp_list :=
[ ctp <port_name> payloadPos <string> constrainType useMain

|
ctp <port_name> payloadPos <string> constrainType useSpare
|
ctp <port_name> payloadPos <string> constrainType notUseMain |
ctp <port_name> payloadPos <string> constrainType notUseSpare |
ctp <port_name> payloadPos <string> constrainType useMainSpare |
ctp <port_name> payloadPos <string> constrainType notUse
|
ctp <port_name> payloadPos <string> constrainType useService |
ctp <port_name> payloadPos <string> constrainType notUseService |
ctp <port_name> payloadPos <string> constrainType useMainA |
ctp <port_name> payloadPos <string> constrainType useMainZ |
ctp <port_name> payloadPos <string> constrainType useSpareA |
ctp <port_name> payloadPos <string> constrainType useSpareZ |
ctp <port_name> payloadPos <string> constrainType useMainSpareA |
ctp <port_name> payloadPos <string> constrainType useMainSpareZ ]
N.B. the values useMainAZ, useSpareAZ, useMainSpareAZ are meaningful just for unidirectional
paths. Related to connections at node level, A is referred to the input CTP (sink for the Link Connection)
and Z to the output CTP (source for the Link Connection).
CONSTRpath
[... <ctp_list>]
END
ALLOCpath
END
DEALLOCpath
END
IMPLpath
END
1AA 00014 0004 (9007) A4 ALICE 04.10
DEIMPLpath
END
DELETEpath
END
UPDATEpath
ED
03
957.130.882 U

198
141 / 198
changeOpRes :=
{ keepingMain | keepingSpare}
changeOpType :=
{ immediate | deferred }
ttp_to_prot :=
{ nap <port_name> | ctp <port_name> payloadPos <string> }
protCmd :=
{protect | addEnhancedProt }
remCmd :=
{removeEnhancedProt | removeEnhancedProtWithCheck }
unprCmd :=
{unprotect | unprotectWitchCheck}
topLev :=
{ ntw | sbn | et }
topLevProt :=
{ ntw | sbn | et | node }
N.B.

updList
[userLabel <user_label>]
[<upd_path_attributes>]
END
END
Node topology is valid only for Drop & Continue One Node and Drop & Continue 2 Switch
connection.
connProtType :=
{ legProtected | legNotProtected }
endLegType :=
{nap <port_name> | node <node_name> [portName <port_name>] }
opNapType :=
{keepNap | releaseNap }
1AA 00014 0004 (9007) A4 ALICE 04.10
PROTECTpath
<protCmd> <changeOpType>
endTpList
[[<ttp_to_prot>
<ttp_to_prot>]
[topologyLevel <topLevProt>]]
END
END
PROTECTpath
{ <unprCmd> <changeOpRes> <changeOpType> |
<remCmd> <changeOpType> }
endTpList
[[<ttp_to_prot>
<ttp_to_prot>]
[topologyLevel <topLevProt>]]
END
END
ADDLEGpath
ED
03
957.130.882 U

198
142 / 198

[[allocRule automaticallyAllocated
[<changeOpType>]
[protRequired <connProtType>]] |
[allocRule onUserRequest ]]
<endLegType>
END
REMOVELEGpath
userLabel <userLabel>
[<changeOpType>]
[<opNapType>]
nap <port_name>
END
COMMISSIONpath
END
UNCOMMISSIONpath
END
UPDALRpath
{<alrPropRule> |
pdhAlrEnabRule manual | pdhAlrEnabRule onImplementation | pdhAlrEnabRule onCommissioning |
sdhAlrEnabRule manual | sdhAlrEnabRule onImplementation | sdhAlrEnabRule onCommissioning }
END
N.B. The ttp_to_prot in PROTECTpath and UNPROTECTpath command have to be on the boundary of
a topology. If the topology level is not specified, the trail is protected into the upper topology level.
Regarding enhancedProtected paths, it is preferable to make these paths starting from SNCP protected
paths (protType=sh1Plus1EToEProt) and then to add the service connection with the proper
PROTECTpath command (see examples).
1AA 00014 0004 (9007) A4 ALICE 04.10
CONNECTpath
<changeOpType>
endTpList
ctp <port_name> payloadPos <string>
END
END
DISCONNECTpath
endTpList
END
END
ED
03
957.130.882 U

198
143 / 198

ELEMALRMNGpath
{pdhElemAlr enable | pdhElemAlr disable |
sdhElemAlr enable | sdhElemAlr disable }
END
SPLITpath
operationalRule <opRule>
node <user_label>
END
1AA 00014 0004 (9007) A4 ALICE 04.10
JOINpath
userLabel <user_label1>
node <user_label>
END
ED
03
957.130.882 U

198
144 / 198
D.1.5 Trail commands
1AA 00014 0004 (9007) A4 ALICE 04.10

D.1.5.1Description
SETtrail:
it permits to set default values for attributes to be specified at the trail creation
(definition) time.
CREATEtrail:
it defines a trail. If payloadStructure attribute has a value different from

notMeaningful (default value), notTerminatedAu4 and notTerminatedAu3,
the trail is implemented and also configured.
CONSTRtrail:
it defines constraints to correctly allocate a trail. If the constraint list is void, it

deletes all constraints previously defined on the trail.
ALLOCtrail:
it allocates resources on defined trail.
DEALLOCtrail:
it deallocates resources on implemented trail.
IMPLtrail:
it implements an allocated trail
DEIMPLtrail:
it deimplements an implemented trail.
CONFIGtrail:
it configures the payload structure of trail.
UPDATEtrail:
it updates the attribute trails.
DELETEtrail:
it deletes the trail.
PROTECTtrail:
it changes the protection on an existing trail.
SPLITtrail:
it splits an existing trail in two distinct trails.
JOINtrail:
it joins two distinct trails.
UPDALRtrail:
it update the Q3 SDH alarm enabling rule.
ELEMALRMNGtrail:
it enables/disables Q3 SDH alarm.
CONFIGUREMsTrail:
it configure the payload of a MsTrail.
ED
03
957.130.882 U

198
145 / 198
D.1.5.2Syntax
{ trailType pointToPoint }
[ payloadStructure tu12Tu12Tu12 | payloadStructure tu12Tu12Tu3 |
payloadStructure tu12Tu3Tu12 | payloadStructure tu3Tu12Tu12 |
payloadStructure tu12Tu3Tu3
| payloadStructure tu3Tu12Tu3 |
| payloadStructure tu3Tu3Tu3
|
payloadStructure notTerminatedAu4 | payloadStructure notTerminatedAu3
payloadStructure tu12 | payloadStructure notMeaningful ]
|
protType sh1Plus1EToEProt | protType
[ protType notProtected
enhancedProtected]
[ msProtProfile normal | msProtProfile protPref]
{ flow bidirectional }
not_upd_trail_attributes:=[ sdhAlrEnabRule onImplementation | sdhAlrEnabRule onCommissioning |
sdhAlrEnabRule manual ]
trail_attributes:=
[ upd_trail_attributes | not_upd_trail_attributes ]
SETtrail
<trail_attributes>
END
ctp_list :=
node_list :=
node <node_name>
end_tp_list :=
{ <ctp_list> <ctp_list> |
<node_list> <node_list>}
CREATEtrail
userLabel <string>
[<trail_attributes>]
endTpList
<end_tp_list>
<end_tp_list>
END
END
1AA 00014 0004 (9007) A4 ALICE 04.10
ctp_constr_list :=
{ ctp <port_name> payloadPos <string> constrainType useMain |

ctp <port_name> payloadPos <string> constrainType useSpare |
ctp <port_name> payloadPos <string> constrainType notUseMain |
ctp <port_name> payloadPos <string> constrainType notUseSpare |
ctp <port_name> payloadPos <string> constrainType useMainSpare |
ctp <port_name> payloadPos <string> constrainType notUse |
ctp <port_name> payloadPos <string> constrainType useService |
ctp <port_name> payloadPos <string> constrainType notUseService }
CONSTRtrail
[... <ctp_constr_list>]
END
ED
03
957.130.882 U

198
146 / 198

upd_trail_attributes :=

ALLOCtrail
END
DEALLOCtrail
END
IMPLtrail
END
DEIMPLtrail
END
CONFIGtrail
[ payloadStructure tu12Tu12Tu12 | payloadStructure tu12Tu12Tu3 |
payloadStructure tu12Tu3Tu12 | payloadStructure tu3Tu12Tu12 |
| payloadStructure tu3Tu12Tu3 |
| payloadStructure tu3Tu3Tu3
|
payloadStructure notTerminatedAu4 | payloadStructure terminatedAu4 |
payloadStructure notMeaningful payloadStructure notTerminatedAu3 | payloadStructure tu12]
END
DELETEtrail
END
1AA 00014 0004 (9007) A4 ALICE 04.10
UPDATEtrail
updList
[userLabel <user_label>]
[<upd_trail_attributes>]
END
END
changeOpRes :=
{ keepingMain | keepingSpare }
changeOpType :=
{ immediate | deferred }
ttp_to_prot :=
{ cap <port_name> payloadPos <string> |

ctp <port_name> payloadPos <string> }
protCmd :=
{ protect | addEnhancedProt }
remCmd :=
{ removeEnhancedProt | removeEnhancedProtWithCheck }
unprCmd :=
{ unprotect | unprotectWithCheck }
PROTECTtrail
<protCmd> <changeOpType>
endTpList
[[<ttp_to_prot>
<ttp_to_prot>]
ED
03
957.130.882 U

198
147 / 198
PROTECTtrail
{ <unprCmd> <changeOpRes> <changeOpType> |
<remCmd> <changeOpType> }
endTpList
[[<ttp_to_prot>
<ttp_to_prot>]
[topologyLevel <topLev>]]
END
END
N.B. The ttp_to_prot in a PROTECTtrail command have to be on the boundary of a topology.
If the topology level is not specified, the trail is protected into the upper topology level.
Regarding enhancedProtected trails, it is preferable to make these trails starting from SNCP trails
(protType=sh1Plus1EToEProt) and then to add the service protection with the proper command.
opRule :=
{ user | automatic }
SPLITtrail
node <user_label>
END
JOINtrail
node <user_label>
END
UPDALRtrail
sdhAlrEnabRule manual | sdhAlrEnabRule onImplementation
END
ELEMALRMNGtrail
sdhElemAlr enable | sdhElemAlr disable
END
1AA 00014 0004 (9007) A4 ALICE 04.10
CONFIGUREmsTrail
Au4List
[ hoAu4 | hoAu4Conc4 | hoAu4Conc16 | hoAu4Conc64 ]
END
END
ED
03
957.130.882 U

198
148 / 198

[topologyLevel <topLev>]]
END
END

D.1.6 Port User Label

For NEs with TSDIM interface the port userlabel will be done by means of naming rules. No relationship
exists with TSDIM userLabel attribute. The computed usarlabel should respect the following form:
NE_userlabel/rxxsybzzpkk[cjj]
where:
xx = rack number,
y = subrack number,
zz = board number,
kk = port number,
jj = channel number (optional this component will be used only for transmux ports).
All the previous information can be retrieved by the identifier (FDN) of TSDIM objects.
For the other cases the port userlabel is done by SHWX systems.
D.1.7 CHOWN commands
These commands update the securityLabel of path, trail, nap and link connections.
D.1.7.1Syntax
objClass :=
{ nap | path | trail }
CHOWNonObj <objClass>
userLabel
<user_label>
securityLabel <number>
END
1AA 00014 0004 (9007) A4 ALICE 04.10
CHOWNonObj lc
userLabel
<user_label> payloadPos <string>
securityLabel <number>
END
ED
03
957.130.882 U

198
149 / 198
D.1.8 PM commands
SET:
It sets the performance monitoring Domain (pmDomain).

The default value of the pmDomain is read from the environment variable
NXNL_PMDOMAIN. The SET command can be used to choose a different
value.
CREATE:
It allows to create objects of the following classes :

measure of performance (pMeasure), threshold crossing alarm profile
(tCAProfile), threshold crossing report profile (tCRProfile) and performance
monitoring counter report (pmCountRep).
UPDATE:
It sets attribute values for one object of the same classes specified for CREATE.
DELETE:
It removes one object of the same classes specified for CREATE.
CONSmeas:
It checks a measure consistency.
CORRtransToMeas:
It correlates a measure to one or more paths/trails.
1AA 00014 0004 (9007) A4 ALICE 04.10
UNCORRtransToMeas: It deletes the correlation of a path/trail to one or more measures.

CORRTpToMeas:
It correlates a termnation point object (nap, cap, ctp) to one or more measures.
CORRrepToMeas:
It correlates one or more reports (objects of class pmCountRep or tCRProfile)

to one or more measures.
UNCORRrepToMeas:
It removes the correlation between of one or more reports and a measure.
CORRpmTpToTca:
It correlates a performance monitoring terminattion point (pmTp) to one or more

tCAProfile objects.
UNCORRpmTpToTca:
It deletes the correlation of a pmTp to a tCAProfile objects.
ED
03
957.130.882 U

198
150 / 198

D.1.8.1Description

D.1.8.2Syntax
SET pmDomId <number>
END
pmLay :=
{ lo | ho | bothLoHo }
pmGran :=
{ pm24Hours | pm15Min }
pmCount :=
{ false | true }
defEnd :=
{ false | true }
CREATE CLASS pMeasure

userLabel
pmGranularity
pmCollectCounter
[ pmStartTime
[ pmEndTime
[ pmLayer
[ defaultEnd
END
<user_label>
<pmGran>
<pmCount>
<date> ]
<date> ]
<pmLay> ]
<boolean> ]
UPDATE CLASS pMeasure

updList
[ userLabel
[ pmGranularity
[ pmLayer
[ pmCollectCounter
[ defaultEnd
[ pmStartTime
[ pmEndTime
END
END
<user_label> ]
<pmGran> ]
<pmLay> ]
<pmCount> ]
<defEnd> ]
<date> ]
<date> ]
DELETE CLASS pMeasure

userLabel
<user_label>
END
pmRepDesType := { file | mail | printer }
1AA 00014 0004 (9007) A4 ALICE 04.10
pmRepWin :=
ED
{ min15 | hour | day | week | month | year }
03
957.130.882 U

198
151 / 198
<user_label>
<pmGran>
<string>
<pmRepWin>
<pmRepDesType> ]
<number> ]
<number> ]
<number> ]
<number> ]
<number> ]
<number> ]
N.B. When one of the attributes which are not mandatory is not present in the above create request, its
value remains unspecified.
UPDATE CLASS tCRProfile
userLabel
<user_label>
updList
[ userLabel
<user_label> ]
[ pmReportDestType
<pmRepDesType>]
[ pmReportDestName
<string> ]
[ pmReportWindow
<pmRepWin> ]
[ pmThreBBE
<number> ]
[ pmThreES
<number> ]
[ pmThreSES
<number> ]
[ pmThreFEBBE
<number> ]
[ pmThreFEES
<number> ]
[ pmThreFESES
<number> ]
END
END
DELETE CLASS tCRProfile
userLabel
<user_label>
END
1AA 00014 0004 (9007) A4 ALICE 04.10
CREATE CLASS pmCountRep

userLabel
pmRepDestName
pmReportWindow
pmReportDestType
END
<user_label>
<string>
<pmRepWin>
<pmRepDesType>
UPDATE CLASS pmCountRep

userLabel
<user_label>
updList
[ userLabel
<userLabel> ]
[ pmReportDestType
<pmRepDesType> ]
[ pmRepDestName
<string> ]
[ pmReportWindow
<pmRepWin> ]
END
ED
03
957.130.882 U

198
152 / 198

CREATE CLASS tCRProfile

userLabel
pmGranularity
pmRepDestName
pmReportWindow
[ pmReportDestType
[ pmThreBBE
[ pmThreES
[ pmThreSES
[ pmThreFEBBE
[ pmThreFEES
[ pmThreFESES
END

DELETE CLASS pmCountRep

userLabel
<userLabel>
END
N.B. objects of class tCAProfile have no attributes to update.

CREATE CLASS tCAProfile
userLabel
<user_label>
pmTpForTca
<pmTpTca>
pmGranularity
<pmGran>
[ bBeHigh
<number> ]
[ bBeLow
<number> ]
[ eSHigh
<number> ]
[ eSLow
<number> ]
[ sESHigh
<number> ]
[ sESLow
<number> ]
[ fEBBEHigh
<number> ]
[ fEBBELow
<number> ]
[ fEESHigh
<number> ]
[ fEESLow
<number> ]
[ fESESHigh
<number> ]
[ fESESLow
<number> ]
END
DELETE CLASS tCAProfile
userLabel
<user_label>
END
STARTmeas
userLabel
END
<user_label>
STOPmeas
userLabel
END
<user_label>
CONSmeas
userLabel
END
<user_label>
pathTrail :=
[ pathUserLabel <user_label> | trailUserLabel <user_label> ]
1AA 00014 0004 (9007) A4 ALICE 04.10
CORRtransToMeas
measureUserLabel
{ <pathTrail> } ...
END
UNCORRtransToMeas
{ measureUserLabel
<pathTrail>
END
Tp :=
ED
<user_label>
<user_label> } ...
{ nap <port_name> | cap <port_name> payloadPos <string> |

ctp <port_name> payloadPos <string> }
03
957.130.882 U

198
153 / 198

CORRTpToMeas | UNCORRTpToMeas
{ measureUserLabel
<user_label> } ...
<Tp>
END
N.B. In the correlation case only measures with the same state can be specified.
Report :=
{ tcr <user_label> | countRep <user_label> }
CORRrepToMeas | UNCORRrepToMeas
measureUserLabel
<user_label>
{ <Report> } ...
END
CORRpmTpToTca
measureUserLabel
<Tp>
{ tca <user_label> } ...
END
<user_label>
N.B. The pmTp involved in the correlation is identified by the measure it belongs to and by the Tp related
to it.
UNCORRpmTpToTca
measureUserLabel
<Tp>
END
DELETEpmTp
measureUserLabel
<Tp>
END
<user_label>
<user_label>
N.B. The pmTp to delete is identified by the measure it belongs to and by the Tp related to it.
DELETEpmTransp
measureUserLabel
<pathTrail>
END
<user_label>
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B. In DELETEpmTransp <pathTrail> specifies the userLabel of the pmTransport object. If the
pmTransport is a pathimage the pathUserLabel token is used while if it is a trailimage the trailUserLabel
is used instead. Note that a pmTransport is created with the same userLabel of the corresponding
path/trail.
ED
03
957.130.882 U

198
154 / 198
D.1.9 aSAP commands

D.1.9.1 Description
Objects of class aSAProfile can be handled with the following commands:
CREATE:
creates one object;
UPDATE:
changes one object attribute values;
DELETE:
removes one object;
CORRtoaSAProfile
one object of class aSAProfile is bound with objects of class path, trail and
physical connection.
D.1.9.2 Syntax
AlarmSevCode:=
{ nonAlarmed | minor | major | critical | warning }
CREATE CLASS aSAProfile

userLabel
[ mediaEqFail
[ underProtDegr
[ rSFailure
[ exBer
[ degSignal
[ confMismatch
[ sdhFailure
[ pdhFailure
[ qualityTC15
[ qualityTC24
END
<user_label>
<AlarmSevCode> ]
<AlarmSevCode> ]
<AlarmSevCode> ]
<AlarmSevCode> ]
<AlarmSevCode> ]
<AlarmSevCode> ]
<AlarmSevCode> ]
<AlarmSevCode> ]
<AlarmSevCode> ]
<AlarmSevCode> ]
In making the just above specified create request the optional attributes have default values as follows:
mediaEqFail major, underProtDegr warning, rSFailure major, exBer major, confMismatch major,
sdhFailure major, pdhFailure warning, qualityTC15 and qualityTC24 minor.
DELETE CLASS aSAProfile
userLabel
END
asapClasses:=
{ path | trail | physicalConn }
objectUserLabel:= userLabel
1AA 00014 0004 (9007) A4 ALICE 04.10
toBindObject:=
<user_label>
CLASS asapClasses
{ objectUserLabel }.....
END
CORRtoaSAProfile
userLabel
{ toBindObject }.....
END
ED
<user_label>
<user_label>
03
957.130.882 U

198
155 / 198
D.1.10 restRule commands
1AA 00014 0004 (9007) A4 ALICE 04.10
Objects of class restoration Rule can be handled with the following commands:
SET:
set the working restoration domain that is the restoration domain which all the
subsequent commands related to object of class restoration Rule will be sent
to;
CREATE:
creates one object;
UPDATE:
changes one object attribute values;
DELETE:
removes one object;
ACT_UPDATE:
change the attribute restState for one object of class path or trail.
ED
03
957.130.882 U

198
156 / 198

D.1.10.1Description

D.1.10.2Syntax
SET restDomId <number>
END
ObjRestClass:=
{ path | trail }
RestorationStrategy:=
{ optimizedAddProt | eToEAddProt }
AllocationConstraint:=
{ notAlarmedResourcesOnly | noRestriction }
ConstrRule:=
{ dontUseConstraints | useDefConstraints }
CREATE CLASS restRule

userLabel
objClass
[ restStrategy
[ holdOffTime
[ usedResources
[ constraintRule
END
<user_label>
<ObjRestClass>
<RestorationStrategy> ]
<number> ]
<AllocationConstraint> ]
<ConstrRule> ]
In the above create request holdOffTime has a value of 300 as a default.

UPDATE CLASS restRule
userLabel
objClass
updList
[ restStrategy
[ holdOffTime
[ usedResources
[ constraintRule
END
END
DELETE CLASS restRule
userLabel
objClass
END
<user_label>
<ObjRestClass>
<RestorationStrategy> ]
<number> ]
<AllocationConstraint> ]
<ConstrRule> ]
<user_label>
<ObjRestClass>
N.B. In the above CREATE, UPDATE and DELETE the object of class restoration rule is identified via the
user label and the the class of the object related.
1AA 00014 0004 (9007) A4 ALICE 04.10
ACT_UPDATE CLASS ObjRestClass

userLabel
<user_label>
updList
restState
supervised
END
END
ED
03
957.130.882 U

198
157 / 198
Comments can be specified in a line of the command file beginning with the symbol !. Comments are
delimited with a new line character.
D.1.12 Sleep command
D.1.12.1Description
The execution of the SLEEP command permits the program to wait for a specified number of seconds
between two commands.
D.1.12.2Syntax
SLEEP <number>
D.1.13 Setting timeout
D.1.13.1Description
This commands sets the timeout (number of seconds) of CI messages (get and actions).
D.1.13.2Syntax
SETtimeout <number> END
D.1.14 Exit command
D.1.14.1Description
This command stops the utility and shows final statistics (useful when the utility is running with f option).
D.1.14.2Syntax
1AA 00014 0004 (9007) A4 ALICE 04.10
EXIT
ED
03
957.130.882 U

198
158 / 198

D.1.11 Comments
D.1.15 Connection command

D.1.15.1Description
IMPLconn:
This command is used to implement a connection in topology.
DEIMPLconn: This command is used to deimplement a connection in topology.

D.1.15.2Syntax
tpRole_value:={ RCV | RCV Main | RCV Spare | XMIT Main | XMIT Spare | XMIT Main RCV Main
| XMIT Main RCV Spare | XMIT Spare RCV Main | XMIT Spare RCV Spare | XMIT
RCV | XMIT Main RCV | XMIT Spare RCV | XMIT RCV Main | XMIT RCV Spare
| XMIT Service RCV Service | XMIT Service | RCV Service }
tp:=
{ ctp <port_name> payloadPos <string> tpRole <tpRole_value> |

nap <port_name> tpRole <tpRole_value> |
cap <port_name> payloadPos <string> tpRole <tpRole_value> }
conn_tp_list:= { <tp>
<tp>
[tp]
[tp] }
topolevel:=
N.B.
{ ntw | sbn | et | node }
The possible configuration are the following:
1AA 00014 0004 (9007) A4 ALICE 04.10
ctpctp
napctp
ctpnap
capctp
ctpcap
capcap
napnap
ctpctpctp
napctpctp
ctpctpnap
capcapcap
capctpctp
ctpctpctpctp
capctpctpctp
ctpcapctpctp
ctpctpcapctp
ctpctpctpcap
napctpctpctp
ctpnapctpctp
ctpctpnapctp
ctpctpctpnap
IMPLconn
topologyLevel <topolevel>
endTpList
<conn_tp_list>
END
END
ED
03
957.130.882 U

198
159 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
ED
Now those function can be used only at node level.
957.130.882 U
DEIMPLconn
topologyLevel <topolevel>
endTpList
<conn_tp_list>
END
END
03
198
160 / 198
D.1.16 Topology Commands

D.1.16.1Description
CREATEntw:
it creates a new network topology
CREATEsbn:
it creates a new subnetwork topology.
CREATEet:
it creates a new elementary topology.
CREATEnode:
it creates a new node.
CREATE physicalConnection: it creates a new physical connection.

REMOVE ntw:
it removes a network topology.
REMOVE sbn:
it removes a subnetwork topology.
REMOVE et:
it removes an elementary topology.
REMOVE physicalConnection: it removes a physical connection.

IMPL ntw:
it implement a network.
IMPL sbn:
it implement a subnetwork.
IMPL et:
it implement an elementary topology.
IMPL physicalConnection:it implement a physical connection.

DEIMPL ntw:
it deimplement a network.
DEIMPL sbn:
it deimplement a subnetwork.
DEIMPL et:
it deimplement an elementary topology.
DEIMPL physicalConnection: it deimplement a physical connection.

Update et:
it update the globalCfg attribute in et.
SPLITphysicalConnection: it split a defined physical connection.

JOINphysicalConnection: it join two physical connection.
1AA 00014 0004 (9007) A4 ALICE 04.10
OBJECTconnection:
ED
it connect/disconnect one or more physical connection.
03
957.130.882 U

198
161 / 198
etType_set:=
{ genericRing | msSpring | meshed | msSpring4f }
stmType_set:=
{ stm1 | stm4 | stm16 | notHomogeneus | stm64 | stm0 }
CREATEntw
userLabel
mapId
userId
[comment1
[comment2
END
<user_label>
<integer>
<string>
<string> ]
<string> ]
CREATEsbn
userLabel
includedIn
userId
[comment1
[comment2
END
<user_label>
ntw <user_label>
<string>
<string> ]
<string> ]
CREATEet
userLabel
includedIn
userId
etType
stmType
fiberNum
globalCfg
[comment1
[comment2
END
<user_label>
sbn <user_label>
<string>
<etType_set>
<stmType_set>
<integer>
<True | False>
<string> ]
<string> ]
1AA 00014 0004 (9007) A4 ALICE 04.10
CREATEnode
userLabel
includedIn
userId
neUserLabel
[seqNumInEt
[nodeInEt
[comment1
[comment2
END
ED

D.1.16.2Syntax
<user_label>
<sbn | et> <user_label>
<string>
<user_label>
<integer>]
<integer>]
<string> ]
<string> ]
03
957.130.882 U

198
162 / 198

CREATE physicalConnection
userLabel
userId
aSDHPort
zSDHPort
END
<user_label>
<string>
<user_label>
<user_label>
REMOVE ntw
userLabel
END
<user_label>
REMOVE sbn
userLabel
END
<user_label>
REMOVE et
userLabel
END
<user_label>
REMOVE physicalConnection
userLabel
<user_label>
END
IMPL <ntw | sbn | et | physicalConnection>

userLabel
<user_label>
END
DEIMPL <ntw | sbn | et | physicalConnection>

userLabel
<user_label>
END
1AA 00014 0004 (9007) A4 ALICE 04.10
Update et
userLabel<label>
globalCfg <True |False>
END
SPLITphysicalConnection
reqType
userLabelPhyConnToSplit
userLabelFirstPhyConn
userLabelOldFirstPort
userLabelNewFirstPort
userLabelSecondPhyConn
userLabelOldSecondPort
userLabelNewSecondPort
<split_phyConn_attr>
END
ED
<splitType>
<user_label>
<user_label>
<user_label>
<user_label>
<user_label>
<user_label>
<user_label>
03
957.130.882 U

198
163 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
OBJECTconnection
actionType
connectMode
{ physicalConnection
END
ED
<joinType>
<user_label>
<user_label>
<user_label>

JOINphysicalConnection
reqType
userLabelFirstPhyConn
userLabelSecondPhyConn
userLabelNewPhyConn
<join_phyConn_attr>
END
<actionConnection>
<modeConnection>
<user_label> }........
03
957.130.882 U

198
164 / 198
D.1.17 Upload and Remove NAP

D.1.17.1Description
UPLOADnap: it perform the naps upload in topology level defined.
REMOVEnap: it remove all naps in topology level defined or remove a single nap defined with portname.
D.1.17.2Syntax
UPLOADnap <ntw | sbn | et | node>
userLabel
<user_label>
END
REMOVEnap <ntw | sbn | et | node>

userLabel
<user_label>
END
REMOVEnap <nap>
portName
END
<string>
D.1.18 Configure et, physical connection.

D.1.18.1Description
CONFIGURE: it configure the payload in et or physical connection.
D.1.18.2Syntax
1AA 00014 0004 (9007) A4 ALICE 04.10
CONFIGURE <et | physicalConnection>

userLabel
<user_label>
payloadStructureList
vc3Num
<integer>
vc4Num
<integer>
vc12Num
<integer>
payloadStructureListEND
END
ED
03
957.130.882 U

198
165 / 198
D.2 tool description
file <string> (mandatory) to specify the command file name;

ntw <number> to set the default work network (it is equal to SET ntwid <number> END);
syntax to only check the syntax of the command file (without executing any command);
f to introduce commands from the standard input;
stop to force the EXIT command when an error occurs;
nochkconstr to disable checks about CTPs of CONSTRpath and CONSTRtrail commands.
D.2.1 Handling errors
The tool stops when a syntactical errors on keyword occurs. In this case the following message is printed
on standard output:
line no <number> token = <keyword>
If there is an error on an attribute value, the message:
line no <number> Value <string_value> not found in the NML d.b.
1AA 00014 0004 (9007) A4 ALICE 04.10
In this case, the tool only stops the execution of the commands if the wrong attribute value is specified in
SET, SETpath, SETtrail commands, otherwise the command is skipped and the tool execution goes on,
unless the utility is running with stop option on.
ED
03
957.130.882 U

198
166 / 198

The tool for executing command files accepts some input parameters:
D.3 Examples

VADM_16
VADM_38
VADM_15
Adm2
RING STM1
Adm5
X_27
VADM_18
NE_V1
VADM_37
VADM_17
X_26
VADM_34
RING STM16
VADM_4
VADM_2
VADM_3
ADM_1
VADM_5
VADM_11
Adm8
VADM_19
RING STM4
VADM_33
Adm7
Figure 5. Reference Network
1AA 00014 0004 (9007) A4 ALICE 04.10
In the following three examples it is supposed to have the Network showed at figure 5. NE_V1 is a virtual
NE, while all the others ADM are real NE.
ED
03
957.130.882 U

198
167 / 198
In this example a simple bidirectional 2Mb path between ADM_1 and VADM_2 is created, allocated (by
using constraints) and imlemented.
! ## DATE ## 14/12/98 15:05:16
SETpath
allocRule user
implRule user
allocationConstraint noRestriction
END
SET ntwId 1 END
CREATEpath
userLabel ADM001VADM_32M9
pathType bidirectionalPtoPto
pathRate lo2Mb
protType notProtected
allAlgType automatic
userId snmlr21
pmAutomatic false
alarmPropRule whenImplemented
endTpList
nap ADM_1/2M/109 usedDir bidirectional
nap VADM_3/2M06 usedDir bidirectional
END
END
1AA 00014 0004 (9007) A4 ALICE 04.10
!
!It is not necessary to define all the constraints.
!If the constaints are not defined, the routing algorithm
!will choose a route for you.
!However, the routing algorithm will use all the constraints
!related to the path when an allocation/addremove leg/
!addremove protection is executed
!
ED
03
957.130.882 U

198
168 / 198

D.3.1 Example on paths

CONSTRpath
ctp ADM_1/West payloadPos 01/1/5.2 constrainType useMain
ctp VADM_3/STM12 payloadPos 01/1/5.2 constrainType useMain
END
ALLOCpath
END
!
! It is not necessary to remove all the constraints
! related to the path.
! If you dont delete them, the constraints will be used for the
! next allocation phase
!
!
CONSTRpath
END
IMPLpath
END
1AA 00014 0004 (9007) A4 ALICE 04.10
CONNECTpath
immediate
endTpList
ctp ADM_1/2M/109 payloadPos 03/1.1/1
ctp VADM_3/2M06 payloadPos 03/1.1/1
END
END
DISCONNECTpath
endTpList
ctp ADM_1/2M/109 payloadPos 03/1.1/1
ctp VADM_3/2M06 payloadPos 03/1.1/1
END
END
ED
03
957.130.882 U

198
169 / 198
D.3.2 Example on paths protected with Drop & Continue
1) the unprotected path is implemented between Adm7 and Adm2. The path route is forced by using TP
constraints; the route is Adm2Adm5VADM_2VADM_3Adm8Adm7;
2) the path is SNCP protected. The spare path route is forced by using TP constraints; the spare route
is Adm2VADM_16VADM_15VADM_38VADM_34VADM_4VADM_5VADM_33Adm7; SNCP
connections are created on Adm2 and Adm7;
3) the path is enhanced protected in RING STM1 and RING STM4. The service path routes are forced
by using TP constraints. The first service route is Adm5VADM_17VADM_18VADM_15. Drop &
continue connections are created on Adm5 and VADM_15. The second service route is
Adm8VADM_11VADM_19VADM_33. Drop & continue connections are created on Adm8 and
VADM_33.
! ## DATE ## 30/09/97 09:04:19
!
! path enhanced protected
!
SETpath
allocRule user
implRule user
END
1AA 00014 0004 (9007) A4 ALICE 04.10
SET ntwId 1 END

!
! step 1 not protected path is created
!
CREATEpath
userLabel Adm7Adm22M15
pathRate lo2Mb
userId snmlr21
endTpList
nap Adm2/port2M102 usedDir bidirectional
nap Adm7/port2M115 usedDir bidirectional
END
END
CONSTRpath
ctp Adm2/West payloadPos 01/1/1.3 constrainType useMain
! ctp Adm5/East payloadPos 01/1/1.3
ctp Adm5/stm1 payloadPos 01/1/1.2 constrainType useMain
! ctp VADM_2/STM11 payloadPos 01/1/1.2
ctp VADM_2/West payloadPos 02/2/7.3 constrainType useMain
! ctp VADM_3/East payloadPos 02/2/7.3
! ctp Adm8/stm1 payloadPos 01/1/7.2
ED
03
957.130.882 U

198
170 / 198

In this example an enhanced protected 2Mb path is implemented in three steps:
1AA 00014 0004 (9007) A4 ALICE 04.10

ctp Adm8/East payloadPos 01/2/2.2 constrainType useMain

! ctp Adm7/West payloadPos 01/2/2.2
END
ALLOCpath
END
!
! step 2 protection SNCP is added
!
CONSTRpath
ctp Adm2/East payloadPos 01/1/1.3 constrainType useSpare
! ctp VADM_16/West payloadPos 01/1/1.3
ctp VADM_16/East payloadPos 01/1/5.3 constrainType useSpare
ctp VADM_15/STM11 payloadPos 01/1/1.2 constrainType useSpare
ctp VADM_38/West payloadPos 01/1/1.1 constrainType useSpare
! ctp Adm7/East payloadPos 01/2/2.2
END
!
! the allocation of spare route is executed with the following command
!
PROTECTpath
protect deferred
endTpList
nap Adm2/port2M102
nap Adm7/port2M115
topologyLevel ntw
END
END
!
! step 3 service protection is added
!
CONSTRpath
ctp Adm5/West payloadPos 01/1/2.3 constrainType useService
ctp VADM_17/West payloadPos 01/1/4.1 constrainType useService
END
!
ED
03
957.130.882 U

198
171 / 198

! the allocation of second spare route is executed with the following command
!
PROTECTpath
addEnhancedProt deferred
endTpList
ctp Adm5/stm1 payloadPos 01/1/1.2
ctp VADM_15/STM11 payloadPos 01/1/1.2
topologyLevel et
END
END
CONSTRpath
ctp Adm8/West payloadPos 01/1/2.2 constrainType useService
END
PROTECTpath
addEnhancedProt deferred
endTpList
ctp Adm8/stm1 payloadPos 01/1/7.2
ctp VADM_33/STM13 payloadPos 01/1/1.3
topologyLevel et
END
END
1AA 00014 0004 (9007) A4 ALICE 04.10
CONSTRpath
END
ED
03
957.130.882 U

198
172 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10

D.3.3 Example on broadcast path

In this example, a broadcast path with 2 legs is created between VADM_38 and NE_V1 (virtual NE). The
first leg allocated and protected too. On the second leg just the TP sink is defined. The first leg is created.
Please note the sink is related by the nodename + the portname. It could be enough to define just the
nodename. In this case, the system will choose for you the port and will create the virtual NAP. If necessary,
the system will create the virtual port.
! ## DATE ## 14/12/98 14:07:16
SETpath
allocRule user
implRule user
END
SET ntwId 1 END
CREATEpath
userLabel moni
pathType unidirectionalPtoPto
pathRate lo2Mb
userId lts4182/snmlr24
pmAutomatic false
endTpList
nap VADM_38/2M11 usedDir source
node NE_V1 usedDir sink portName NE_V1/2M21
END
END
!
!Constraints are inserted; the will be used during the
!allocation phase
!
CONSTRpath
userLabel moni
ctp VADM_38/West payloadPos 06/2/7.2 constrainType useMainZ
ctp X27/STM115 payloadPos 01/2/7.2 constrainType useMainA
ctp X27/STM114 payloadPos 01/2/7.2 constrainType useMainZ
ctp NE_V1/STM15 payloadPos 01/2/7.2 constrainType useMainA
END
ALLOCpath
userLabel moni
END
!
!Constraints are added to protect the first leg.
!(please note the constraintType is useSpare now)
! route of spare is:
! VADM_38,VADM_34,VADM_37,X26,NE_V1
!
CONSTRpath
userLabel moni
ctp VADM_38/East payloadPos 03/1/2.1 constrainType useSpareZ
ED
03
957.130.882 U

198
173 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

ctp VADM_34/West payloadPos 03/1/2.1 constrainType useSpareA

ctp VADM_34/West payloadPos 01/1/1.3 constrainType useSpareZ
ctp VADM_37/East payloadPos 01/1/1.3 constrainType useSpareA
ctp VADM_37/West payloadPos 02/1/7.2 constrainType useSpareZ
ctp VADM_38/East payloadPos 02/1/7.2 constrainType useSpareA
ctp VADM_38/STM12 payloadPos 01/2/7.3 constrainType useSpareZ
ctp X26/STM115 payloadPos 01/2/7.3 constrainType useSpareA
ctp X26/STM11 payloadPos 01/1/3.3 constrainType useSpareZ
ctp NE_V1/STM16 payloadPos 01/1/3.3 constrainType useSpareA
END
!
!The allocation of spare is executed by using the
!constraints.
!
PROTECTpath
userLabel moni
protect deferred
endTpList
nap VADM_38/2M11
nap NE_V1/2M21
topologyLevel ntw
END
END
!
!Onethor leg is just defined
!
ADDLEGpath
userLabel moni
allocRule onUserRequest
node NE_V1
END
03
957.130.882 U

198
174 / 198

D.3.4 Example on broadcast paths (2nd)

In this example a broadcast path with six legs is allocated. Five legs are SNCP protected too. In the
following the route of the legs is described. It is supposed to have the Network as in the figure:
VADM_16
VADM_15
Adm2
RING STM1
Adm5
VADM_18
VADM_17
Broadcast path circular1

leg1 from VADM_17 to VADM_17 (not protected)
route: VADM_17,VADM_18,VADM_15,VADM_16,Adm2,Adm5,VADM_17
leg2 from VADM_17 to Adm2 (protected)
route main: VADM_17,Adm5,Adm2
route spare: VADM_17,VADM_18,VADM_15,VADM_16,Adm2
A switch connection is created on Adm2
leg3 from VADM_17 to Adm5 (protected)
route main: VADM_17,Adm5
route spare: VADM_17,VADM_18,VADM_15,VADM_16,Adm2,Adm5
A switch connection is created on Adm5
leg4 from VADM_17 to VADM_15 (protected)
route main: VADM_17,VADM_18,VADM_15
route spare: VADM_17,Adm5,Adm2,VADM_16,VADM_15
1AA 00014 0004 (9007) A4 ALICE 04.10
A switch connection is created on VADM_15

route main: VADM_17,VADM_18,VADM_15,VADM_16
route spare: VADM_17,Adm5,Adm2,VADM_16
route main: VADM_17,VADM_18
route spare: VADM_17,Adm5,Adm2,VADM_16,VADM_15,VADM_18
! ## DATE ## 02/02/98 14:30:46
!
SETpath
allocRule user
implRule user
END
SET ntwId 2 END
!
ED
03
957.130.882 U

198
175 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
CONSTRpath
userLabel circular1
ctp VADM_18/East payloadPos 01/1/1.1 constrainType useMain
END
ALLOCpath
userLabel circular1
END
!
! Leg2
! nap Adm2/port2M101 is added to the path
!
ADDLEGpath
userLabel circular1
nap Adm2/port2M101
END
CONSTRpath
userLabel circular1
END
!
! Leg2 is allocated after the following command. A broadcast connection is created on node VADM_17
!
ED
03
957.130.882 U

198
176 / 198

! Leg1
!
CREATEpath
userLabel circular1
pathType unidirectionalPtoPto
pathRate lo2Mb
alarmPropRule whenCommissioned
pmAutomatic false
endTpList
nap VADM_17/2M101 usedDir source
nap VADM_17/2M102 usedDir sink
END
END
1AA 00014 0004 (9007) A4 ALICE 04.10

ADDLEGpath
userLabel circular1
allocRule automaticallyAllocated
deferred
nap Adm2/port2M101
END
CONSTRpath
userLabel circular1
END
!
! Leg2 is protected
!
PROTECTpath
userLabel circular1
protect deferred
endTpList
nap VADM_17/2M101
nap Adm2/port2M101
topologyLevel ntw
END
END
!
! Leg3
! nap Adm5/port2M101 is added to the path
!
ADDLEGpath
userLabel circular1
nap Adm5/port2M101
END
CONSTRpath
userLabel circular1
END
!
! Leg3 is allocated after the following command. A leg is added on the broadcast connection on node
VADM_17
!
ADDLEGpath
userLabel circular1
deferred
nap Adm5/port2M101
END
CONSTRpath
ED
03
957.130.882 U

198
177 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.882 U

198
178 / 198

userLabel circular1
ctp Adm2/West payloadPos 01/1/1.1 constrainType useSpare
END
!
! Leg3 is protected
!
PROTECTpath
userLabel circular1
protect deferred
endTpList
nap VADM_17/2M101
nap Adm5/port2M101
topologyLevel ntw
END
END
!
! Leg4
! nap VADM_15/2M101 is added to the path
!
ADDLEGpath
userLabel circular1
nap VADM_15/2M101
END
CONSTRpath
userLabel circular1
END
!
VADM_17
!
ADDLEGpath
userLabel circular1
deferred
nap VADM_15/2M101
END
CONSTRpath
userLabel circular1
1AA 00014 0004 (9007) A4 ALICE 04.10


END
!
! Leg4 is protected
!
PROTECTpath
userLabel circular1
protect deferred
endTpList
nap VADM_17/2M101
nap VADM_15/2M101
topologyLevel ntw
END
END
!
! Leg5
!
ADDLEGpath
userLabel circular1
nap VADM_16/2M101
END
CONSTRpath
userLabel circular1
END
!
VADM_17
!
ADDLEGpath
userLabel circular1
deferred
nap VADM_16/2M101
END
CONSTRpath
userLabel circular1
ED
03
957.130.882 U

198
179 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.882 U

198
180 / 198


END
!
! Leg5 is protected
!
PROTECTpath
userLabel circular1
protect deferred
endTpList
nap VADM_17/2M101
nap VADM_16/2M101
topologyLevel ntw
END
END
!
! Leg6
!
ADDLEGpath
userLabel circular1
nap VADM_18/2M101
END
CONSTRpath
userLabel circular1
END
!
VADM_17
!
ADDLEGpath
userLabel circular1
deferred
nap VADM_18/2M101
END
CONSTRpath
userLabel circular1
END
!
! Leg6 is protected
!

PROTECTpath
userLabel circular1
protect deferred
endTpList
nap VADM_17/2M101
nap VADM_18/2M101
topologyLevel ntw
END
END
CONSTRpath
userLabel circular1
END
SPLITpath
operationalRule automatic
node ADM0001
END
1AA 00014 0004 (9007) A4 ALICE 04.10
JOINpath
userLabel ADM0004
node ADM0001
END
ED
03
957.130.882 U

198
181 / 198
D.3.5 Example on trails

In the next examples it is supposed to have the Network as in the figure:
VADM_40
VADM_41
VADM_42
RING STM16
VADM_39
E VADM_11
VADM_19
W
RING STM4
Adm8
Adm7
VADM_33
VADM_29
Three trails are created and LO configured as follow:

1) trail trail829/1: Adm8,Adm7,VADM_29
2) trail trail829/2: Adm8,VADM_11,VADM_19,VADM_33,VADM_29
1AA 00014 0004 (9007) A4 ALICE 04.10
3) the last trail is SNCP protected:

trail trail_prot : VADM_42,VADM_40,VADM_41 main
trail trail_prot : VADM_42,VADM_39,VADM_41 spare
SET ntwId 3 END
!
!Trail 1
!
CREATEtrail
userLabel trail829/1
trailType pointToPoint
flow bidirectional
endTpList
ctp VADM_29/West payloadPos 02
ctp Adm8/East payloadPos 02
END
ED
03
957.130.882 U

198
182 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10

END
CONSTRtrail
ctp VADM_29/West payloadPos 02 constrainType useMain
ctp Adm7/East payloadPos 02 constrainType useMain
ctp Adm7/West payloadPos 02 constrainType useMain
ctp Adm8/East payloadPos 02 constrainType useMain
END
ALLOCtrail
END
CONSTRtrail
END
IMPLtrail
END
!
!Trail 1 is LO configured
!
CONFIGtrail
END
!
!Trail 2
!
CREATEtrail
flow bidirectional
endTpList
ctp Adm8/West payloadPos 02
ctp VADM_29/East payloadPos 02
END
END
CONSTRtrail
ctp Adm8/West payloadPos 02 constrainType useMain
ctp VADM_11/East payloadPos 02 constrainType useMain
END
ALLOCtrail
END
CONSTRtrail
END
ED
03
957.130.882 U

198
183 / 198
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

IMPLtrail
END
!
!
CONFIGtrail
END
!
!Trail 3
!
CREATEtrail
userLabel trailprot
flow bidirectional
endTpList
END
END
CONSTRtrail
userLabel trailprot
END
ALLOCtrail
userLabel trailprot
END
!
!Trail 3 is SNCP protected
!
CONSTRtrail
userLabel trailprot
END
PROTECTtrail
userLabel trailprot
protect deferred
endTpList
cap VADM_41/East payloadPos 01
cap VADM_42/West payloadPos 01
topologyLevel ntw
END
END
CONSTRtrail
userLabel trailprot
constrainType useMain
constrainType useSpare
03
957.130.882 U

198
184 / 198

END
IMPLtrail
userLabel trailprot
END
!
!
CONFIGtrail
userLabel trailprot
END
SPLITtrail
node ADM0001
END
JOINtrail
userLabel ADM0004
node ADM0001
END
1AA 00014 0004 (9007) A4 ALICE 04.10
CONFIGUREmsTrail
userLabel MSTRAILTOTEST
Au4List
hoAu4Conc4 4
END
END
ED
03
957.130.882 U

198
185 / 198
In this example it is supposed to have the three trails created in the previous example.An SNCP path is
implemented by using the trails.
1AA 00014 0004 (9007) A4 ALICE 04.10
The end points of the path are located on VADM_29 and VADM42.
SETpath
allocRule user
implRule user
END
SET ntwId 3 END
!
!First unprotected path is created
!
CREATEpath
userLabel testmig
pathRate lo2Mb
pmAutomatic false
endTpList
nap VADM_29/2M01 usedDir bidirectional
nap VADM42/2M1 usedDir bidirectional
END
END
!
!The path uses the trail trail829/1.
!Please note that is not necessary to define the TP on node Adm7, because this TP belongs to the trail.
!
CONSTRpath
userLabel testmig
ctp Adm8/stm1 payloadPos 01/1/1.1 constrainType useMain
END
ALLOCpath
userLabel testmig
END
!
!The path is SNCP protected.
!The spare route uses the other two trails of the previous example.
!
CONSTRpath
userLabel testmig
ED
03
957.130.882 U

198
186 / 198

D.3.6 Example of path that uses HO trails
1AA 00014 0004 (9007) A4 ALICE 04.10

ctp Adm8/stm1 payloadPos 01/1/1.1 constrainType useSpare

END
PROTECTpath
userLabel testmig
protect deferred
endTpList
nap VADM_29/2M01
nap VADM42/2M1
topologyLevel ntw
END
END
CONSTRpath
userLabel testmig
END
IMPLpath
userLabel testmig
END
ED
03
957.130.882 U

198
187 / 198
CREATE CLASS pMeasure

userLabel
Measure_1
pmStartTime
1998/12/1110:12:12
pmEndTime
1999/12/1110:12:12
defaultEnd
true
pmLayer
ho
pmGranularity
pm15Min
pmCollectCounter false
END
This command creates a measure named Measure_1. Measure_1 is planned on RM but nothing
happens during creation in the network equipments. Measure_1 will be active on network equipments
between pmStartTime and pmEndTime. It is possible to activate manually the measure with the command:
STARTmeas
userLabel
END
Measure_1
It is possible to stop the measure manually issuing the following command:

STOPmeas
userLabel
END
Measure_1
A performance measure aim is to describe the quality of service offered by a path or a trail, so therefore
once created, to reach its goal a measure must be correlated to a path or a trail. A correlation request can
be submitted as follows:
CORRtransToMeas
measureUserLabel
pathUserLabel
END
Measure_1
ADM_1ADM_39
Note that the end termination points of the object correlated will result automatically under measure if
attribute defaultEnd was set to true when creating the measure.
In order to have a more detailed monitoring of a path (trail) performances it is possible to correlate
some other path or trail termination points to the measure. This can be done with:
CORRTpToMeas
measureUserLabel
nap
END
Measure_1
ADM_104
1AA 00014 0004 (9007) A4 ALICE 04.10
As a measure has been bound to path, trail and their termination points so that relation can be broken using
commands UNCORR transToMeas and UNCORRTpToMeas.
Performance counters values can be reported via mail, printer or file. Doing that is achieved first creating
a new object of class pmCountRep and then correlating it to one measure. Next commands show how get
trough this job.
ED
03
957.130.882 U

198
188 / 198

D.3.7 Example on measures

CREATE CLASS countRep

userLabel
pmReportDestType
pmRepDestName
pmReportWindow
END
CountRep_1
file
/tmp/rep_1.tmp
day
CORRrepToMeas
measureUserLabel Measure_1
countRep
CountRep_1
END
Performance counters values can be checked against their overflowing a userselected edge and results
of this test can be sent by means of mail, printer or file as with showed just above.
Steps to take creating an object of class tCRProfile and, after that, establishing a liaison between this
object and a measure.
CREATE CLASS tCRProfile
userLabel
Tcr_1
pmGranularity
pm15Min
pmReportDestType mail
pmRepDestName /tmp/tcr_1.tmp
pmReportWindow hour
pmThreBBE
10
pmThreES
10
END
CORRrepToMeas
userLabel
tcr
END
Measure_1
Tcr_1
!The following command creates an object of class tCAProfile:

CREATE CLASS tCAProfile
userLabel
Tca_1
pmGranularity
pm15Min
pmTpForTca
vc4
bBeHigh
10
bBeLow
1
END
An alarm will be produced if the bBe counter exceeds the range of specified values.
To make a Tca working it is necessary to correlate it to a Tp. An example follows:
1AA 00014 0004 (9007) A4 ALICE 04.10
CORRpmTpToTca
measureUserLabel Measure_1
nap
ADM_104
tca
Tca_1
END
ED
03
957.130.882 U

198
189 / 198
Object of class aSAProfile can be created and associated to some other objects of class path, trail and
physicalConn to stress, in some way, the importance of the alarms these objects show up.
Here after a simple example give some hints.
CREATE CLASS aSAProfile

userLabel
asap_1
mediaEqFail
major
underProtDegr
warning
rSFailure
major
exBer
major
degSignal
warning
confMismatch
major
sdhFailure
warning
pdhFailure
warning
qualityTC15
major
qualityTC24
minor
END
1AA 00014 0004 (9007) A4 ALICE 04.10
CORRtoaSAProfile userLabel asap_1

CLASS physicalConn
userLabel
connec_1
userLabel
connec_2
END
CLASS path
userLabel
path_1
END
CLASS trail
userLabel
trail_1
END
END
ED
03
957.130.882 U

198
190 / 198

D.3.8 Example on aSAProfile

D.3.9 Example on restoration rule

The following command create an object of class restoration rule related to an object of class path
identified by its user label path_1.
CREATE CLASS restRule
userLabel
path_1
objClass
path
END
If the restoration rule object just created must be changed in its value attributes:
UPDATE CLASS restRule
userLabel
path_1
objClass
path
updList
holdOffTime
END
END
500
Related to objects of class restoration rule there may be the need to change the attribute restState value
for object of class path or trail.
1AA 00014 0004 (9007) A4 ALICE 04.10
ACT_UPDATE CLASS ObjRestRule

userLabel
path_1
updList
restState
supervised
END
END
ED
03
957.130.882 U

198
191 / 198
D.3.10 Example on implement, deimplement connection

IMPLconn
topologyLevel node
endTpList
cap ADM5/West payloadPos 01 tpRole XMIT RCV
cap VADM_17/East payloadPos 01 tpRole XMIT RCV
END
END
1AA 00014 0004 (9007) A4 ALICE 04.10
DEIMPLconn
topologyLevel node
endTpList
cap ADM5/West payloadPos 01 tpRole XMIT RCV
cap VADM_17/East payloadPos 01 tpRole XMIT RCV
END
END
ED
03
957.130.882 U

198
192 / 198

D.3.11 Example on create, remove, implement and deimplement topology.

CREATEntw
userLabel ntw1
mapId 1
userId snml1
comment1 Test to create a network
comment2 Test passed
END
CREATEsbn
includedIn ntw ntw1
userLabel sbn1
userId snml1
comment1 Test to create a subnetwork
END
CREATEet
includedIn sbn sbn1
userLabel et1
userId snml1
etType genericRing
stmType stm1
fiberNum 2
globalCfg True
END
CREATEnode
includedIn sbn sbn1
neUserLabel ne1
userLabel node1
userId snml1
seqNumInEt 2
nodeInEt 3
END
1AA 00014 0004 (9007) A4 ALICE 04.10
CREATE physicalConnection
userLabel phyConn1
userId snml1
aSDHPort portWest1
zSDHPort portEast1
END
N.B.
ED
The parameters order is not important in CREATE operation.
03
957.130.882 U

198
193 / 198

REMOVE ntw
userLabel ntw1
END
REMOVE sbn
userLabel sbn1
END
REMOVE et
userLabel et1
END
REMOVE physicalConnection
userLabel physicalConnection1
END
IMPL ntw
userLabel ntw1
END
IMPL sbn
userLabel sbn1
END
IMPL et
userLabel et1
END
IMPL physicalConnection
END
DEIMPL ntw
userLabel ntw1
END
1AA 00014 0004 (9007) A4 ALICE 04.10
DEIMPL sbn
userLabel sbn1
END
DEIMPL et
userLabel et1
END
ED
03
957.130.882 U

198
194 / 198

DEIMPL physicalConnection
END
Update et
userLabel STM1
globalCfg True
END
reqType undoSplit
userLabelPhyConnToSplit Phy_Conn_Split
userLabelFirstPhyConn Phy_Conn_1
userLabelOldFirstPort Old_Port_1
userLabelNewFirstPort New_Port_1
userLabelSecondPhyConn Phy_Conn_2
userLabelOldSecondPort Old_Port_2
userLabelNewSecondPort New_Port_2
END
reqType split
userLabelPhyConnToSplit Phy_Conn_Split
userLabelOldFirstPort Old_Port_1
userLabelNewFirstPort New_Port_1
userLabelOldSecondPort Old_Port_2
userLabelNewSecondPort New_Port_2
userLabelPhyConnToSplit4f Phy_Conn_Split_4f
userLabelFirstPhyConn4f Phy_Conn_1_4f
userLabelOldFirstPort4f Old_Port_1_4f
userLabelNewFirstPort4f New_Port_1_4f
userLabelSecondPhyConn4f Phy_Conn_2_4f
userLabelOldSecondPort4f Old_Port_2_4f
userLabelNewSecondPort4f New_Port_2_4f
END
N.B.
This syntax is used only in 4 fiber physical connection.
1AA 00014 0004 (9007) A4 ALICE 04.10
reqType undoJoin
userLabelNewPhyConn New_Phy_Conn
END
ED
03
957.130.882 U

198
195 / 198
N.B.

reqType join
userLabelNewPhyConn New_Phy_Conn
userLabelFirstPhyConn4f Phy_Conn_14f
userLabelSecondPhyConn4f Phy_Conn_24f
userLabelNewPhyConn4f New_Phy_Conn4f
END
This syntax is used only in 4 fiber physical connection.
1AA 00014 0004 (9007) A4 ALICE 04.10
OBJECTconnection
actionType connect
connectMode immediate
physicalConnection Phy_Conn_To_Connect
END
ED
03
957.130.882 U

198
196 / 198

D.3.12 Example on upload and remove nap.

UPLOADnap ntw
userLabel ntw1
END
UPLOADnap sbn
userLabel sbn1
END
UPLOADnap et
userLabel et1
END
UPLOADnap node
userLabel ntw1
END
REMOVEnap ntw
userLabel ntw1
END
REMOVEnap sbn
userLabel sbn1
END
REMOVEnap et
userLabel et1
END
REMOVEnap node
userLabel node1
END
1AA 00014 0004 (9007) A4 ALICE 04.10
REMOVEnap nap
portName port_name_1
END
ED
03
957.130.882 U

198
197 / 198
D.3.13 Example configure physical connection and et.

CONFIGURE et
userLabel et1
vc3Num 0
vc4Num 4
vc12Num 0
END
CONFIGURE physicalConnection
vc3Num 0
vc4Num 4
vc12Num 0
END
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
03
957.130.882 U

198
198 / 198

1354 RM

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

1354 RM

Enviado por

Direitos autorais:

Formatos disponíveis

QUESTA PAGINA NON VA INSERITA NEL MANUALE

All rights reserved. Passing on and copying of this

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK

U Ed.03 3AL 61260 AAAA Ed.03

No PAGINE TOTALI PER ARCHIVIAZIONE: 204

INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING

COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES:

TOTALE FOGLI A4 TOTAL A4 SHEETS:

WARNING FOR A-UNITS OTHER THAN A-ITALY

1AA 00014 0004 (9007) A4 ALICE 04.10

Labels are done according to A-Italy binder format.

3AL 61260 AAAA TQZZA

All rights reserved. Passing on and copying of this

ALCATEL OPTICS GROUP

1354RM REL.5.2B ADMINISTRATION GUIDE

ORIGINALE SU FILE: ALICE 6.10

1AA 00014 0004 (9007) A4 ALICE 04.10

Regional Network Manager for SDH and Optical Networks

3AL 61260 AAAA TQZZA

All rights reserved. Passing on and copying of this

3AL 61260 AAAA Ed.03

3AL 61260 AAAA Ed.03

3AL 61260 AAAA Ed.03

1300NM 1354RM Rel.5.2B

1AA 00014 0004 (9007) A4 ALICE 04.10

3AL 61260 AAAA Ed.03

3AL 61260 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT

3AL 61260 AAAA TQZZA

3AL 61260 AAAA Ed.03

3AL 61260 AAAA Ed.03

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

1354RM REL.5.2B ADMINISTRATION GUIDE

2 HARDWARE AND SOFTWARE REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3AL 61260 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

5 IPC RESOURCES CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 PROCESS MONITOR & CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9 SYSTEM MANAGEMENT FEATURES (SMF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3AL 61260 AAAA TQZZA

All rights reserved. Passing on and copying of this

4.2 Installation on Distributed Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

10.5 Consistency Download problem with transmux ports . . . . . . . . . . . . . . . . . . . . . . . . . . .

12 QNN INTERFACE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14 HOW TO CHANGE THE USERLABEL OF NES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3AL 61260 AAAA TQZZA

1AA 00014 0004 (9007) A4 ALICE 04.10

16 UPDATE OF MSSPRING INFOS (MSSPRING TAKEOVER) . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX A INTEGRATION OF 1354RM WITH A1330AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX B INTEGRATION OF 1354RM WITH GENERIC OSOS INTERFACE . . . . . . . . . . . .

APPENDIX C INTEGRATION OF 1354RM WITH SEC SECURIYT SUBSYSTEM . . . . . . . . . . . . .

APPENDIX D COMMAND FILE SPECIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3AL 61260 AAAA TQZZA

All rights reserved. Passing on and copying of this

14.4 Moving ET from Generic to Meshed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this