Embed Size (px)
DESCRIPTION
1354rm alcatel
Citation preview
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
Y 1
03
957.130.882 TQZZA
RELEASED
/3AL 61260 AAAA TQZZA
4
4
QUESTA PAGINA NON VA INSERITA NEL MANUALETHIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
COD.MANUALE HDBK P/N: 957.130.882 U Ed.03 3AL 61260 AAAA Ed.031300NM1354RM 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)
numeratenumbered(facciate)
No pages da from a to
TARGHETTE - LABELS
957.130.882 U Ed.03frontespiziofront
2957.130.882 U Ed.033AL 61260 AAAA Ed.03 manuale
manual198 1/198 198/198
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 200
TOTALE FOGLI A4 TOTAL A4 SHEETS: 100
WARNING FOR A-UNITS OTHER THAN A-ITALY
• Labels are done according to A-Italy binder format.• Source file ALICE 6.10
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
Y 2
03
957.130.882 TQZZA
RELEASED
/3AL 61260 AAAA TQZZA
4
4
ALCATEL OPTICS GROUPSite
Originators
VIMERCATE
:
Domain
1354RM REL.5.2B
Division
Rubric
ADMINISTRATION GUIDE
TypeDistribution Codes Internal External
::::
TND 1354RM REL.5.2B ADMINISTRATION GUIDE
:
M.VARISCO
Approvals
NameApp.
App.Name
M.RAGNI
INFORMAZIONI EDITORIALI
– ORIGINALE SU FILE: ALICE 6.10• sistemazione ’figlist’
957.130.882 U3AL 61260 AAAAEd.031300NM1354RM Rel.5.2B
Regional Network Manager for SDH and Optical NetworksADMINISTRATION GUIDE
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
Y 3
03
957.130.882 TQZZA
RELEASED
/3AL 61260 AAAA TQZZA
4
4
1300NM1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks
ADMINISTRATION GUIDE
957.130.882 U Ed.03 3AL 61260 AAAA Ed.03
VOL.1/1
1300NM1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks
ADMINISTRATION GUIDE
957.130.882 U Ed.03 3AL 61260 AAAA Ed.03
VOL.1/1
1300NM1354RM Rel.5.2B
Regional Network Manager for SDH and Optical Networks
957.130.882 U Ed.03 3AL 61260 AAAA Ed.03 ADMINISTRATION GUIDE VOL.1/1
1300NM 1354RM Rel.5.2BRegional Network Manager for SDH and Optical Networks
957.130.882 U Ed.03 3AL 61260 AAAA Ed.03 ADMINISTRATION GUIDE VOL.1/1
1300NM
1354RM Rel.5.2BRegional Network Manager for SDH and Optical Networks
957.130.882 U Ed.03 3AL 61260 AAAA Ed.03 ADMINISTRATION GUIDE VOL.1/1
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
Y 4
03
957.130.882 TQZZA
RELEASED
/3AL 61260 AAAA TQZZA
4
4
FINE DEL DOCUMENTO INTERNO – END OF INTERNAL DOCUMENT
957.130.882 U Ed.03 3AL 61260 AAAA Ed.03
Administration Guide
Alcatel 1300NMNetwork Management
1354RM Rel.5.2BRegional Network Manager for SDH and Optical Networks
957.130.882 U Ed.03 3AL 61260 AAAA Ed.03
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
1
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
1354RM REL.5.2B ADMINISTRATION GUIDE
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HISTORY 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REFERENCED DOCUMENTS 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 General information 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Handbook applicability 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Product-release handbooks 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Handbooks related to the specific software application 10. . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 Handbooks related to the product’s hardware 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Purpose of the Document 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5 Intended audience 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6 Required skill 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7 Conventions 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 HARDWARE AND SOFTWARE REQUIREMENTS 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Hardware Requirements 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 IM configuration 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2 US configuration 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Software Requirements 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 IM configuration 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 US configuration 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 INSTALLATION 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Installation and Customization of Complete delivery Packages 20. . . . . . . . . . . . . . . . . . . .
3.1.1 SMF installation 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 Re–configure SMF installation 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3 1354RM Installation Environment Variable Definition 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Installation of Patches 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 RM DB resizing after installation patch 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Multi–IM Configuration 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 HP–OV DM CUSTOMIZATION 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 PMD Configuration 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01 000414 M. Ragni ITAVE M. Varisco ITAVE
02 000721 SC00072405 M. Ragni ITAVE M. Varisco ITAVE
00120603 SC00120501 M. Ragni ITAVE M. Varisco ITAVE
1354RM R5.2.xSystem AdministratorReference Guide
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
2
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
4.2 Installation on Distributed Platform 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 Remote Event Sieve configuration 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Object Registration 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 IPC RESOURCES CONFIGURATION 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 USERS MANAGEMENT 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 1354RM Operators Managing 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 User Profiles 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 HP–OVw Users Profile for NetView application 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.2 CDE Customization 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.3 Unix Shell Profile (.profile) 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Network Access Domain Management 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.1 Adding an RM Operator 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.2 Defining a new RM Initiator 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.3 Access Rules description 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.4 Delivered set of Initiators 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.5 Default mapping between User Profiles and Initiators 48. . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 PROCESS MONITOR & CONTROL 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Maintenance Commands 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 Integration of IM Agent in 1354RM PMC 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 DATABASE MANAGEMENT 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1 Database Creation 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 Database disk usage 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3 Database extension 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4 Backup and Restore 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5 DB realignment via “redo log” 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6 Identifier Defragmentation Procedure 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6.1 Procedure steps 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6.2 idDefrag procedure – structure of log file 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 DB configuration for huge networks 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8 Managing indexes 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 SYSTEM MANAGEMENT FEATURES (SMF) 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 EMLs Data Definition for SMFs 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Description of ”smf_conf” file parameters 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.2 Network’s configuration file generation 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 1354RM Scheduled Operations 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3 Multi–Screen Installation 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 1354RM BEHAVIOR 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1 EMLs management 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.1 Procedures to define EMLs managing Q3 NEs 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1.2 Procedures to create EMLs managing QB3* NEs 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1.3 Procedures to delete EMLs managing QB3* NEs 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Path / HO–Trail allocation algorithm failures 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3 Distributed Network Maps (DNM) application customization 74. . . . . . . . . . . . . . . . . . . . .
10.3.1 Environment Variables 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.2 Registration Files 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3.3 Resources Files 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 Trace management 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4.1 User Interface applications 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4.2 Information Manager Applications 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
3
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
10.5 Consistency Download problem with transmux ports 76. . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5.1 RM with 2Mb ports and WX with a single port 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5.2 RM with a single port and WX with 2Mb ports 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 1354RM CUSTOMIZATION 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Environment variables changes 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Users Services 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.1 Counters refresh rate on agent response 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.2 Browser 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 EML–NML Alignment Process 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 Inventory Processes 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5 Map Management 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6 Path/HO–Trail Management 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6.1 Path/Trail allocation algorithm 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.2 Reuse already allocated resources in Broadcast paths. 82. . . . . . . . . . . . . . . . . . . . . . . . . 11.6.3 Using Virtual Nodes during Path Allocation Phase 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.4 Configurable switch in Drop&Continue 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.5 Changing timeout for Cross Connection management actions 83. . . . . . . . . . . . . . . . . . . . 11.6.6 Configuring consistency flow control 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Alarm management 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.7.1 Flooding protection mechanism 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.7.2 Alarm clearing hysteresis period 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.8 Nap uploading timer 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.9 SNCP switch timer 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.10 Printer Commands 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.11 Unused Virtual PDH ports garbage collection 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.12 Setting Linked Get Replies Maximum Number 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.13 NetView Symbol’s Labels 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.14 Performance Monitoring Customization 88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.14.1 PM Data Collection Customization 88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.14.2 PM Data Archive Customization 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.14.3 PM Scheduled Report 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.14.4 PM Automatic Start/Stop Measures 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.15 How to change the default ASAP 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.16 Procedure to set Swedish language 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12 QNN INTERFACE MANAGEMENT 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 Enabling / Disabling Qnn Agent Management 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 RM user definition for Qnn Zoom–In 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1 RM users definition script 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 RM Zoom–In from NN using RM USM 94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4 Limitation of Network Construction lead by Qnn Agent 95. . . . . . . . . . . . . . . . . . . . . . . . . . 12.5 Limitation of Qnn path provisioning lead by RM 96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.6 Assigning Network Resources to 1354NN 96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 EML SIMULATION 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1 Simulated EML data generation and EML registration 97. . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1.1 Available Simulated data files 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1.2 Simulated data file syntax 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 Real Network Simulation 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 HOW TO CHANGE THE USERLABEL OF NES 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 NEs with SEN–IM interface 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2 NEs with TSD–IM interface 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3 Aligning the userLabel of PMNEs and PMTPs 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
4
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
14.4 Moving ET from Generic to Meshed 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15 MIGRATION PROCEDURE 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1 1354RM R2.4 (NR3.1) to 1354RM R5.2.x Migration Procedure 104. . . . . . . . . . . . . . . . . . . . . 15.2 Virtual EML registration on Communication Infrastructure (CI) 108. . . . . . . . . . . . . . . . . . .
15.2.1 Prerequisites 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.2 Procedure steps 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3 Migration Procedure of NEs 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.1 NE migration between QB3* and QB3 interface 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.2 neGroup modification 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.4 OVW Map Conversion from 1354RM R2.4 to 1354RM R5.2.x 117. . . . . . . . . . . . . . . . . . . . . . 15.4.1 Recover Maps after migration when changing ntwDomld 117. . . . . . . . . . . . . . . . . . . . . . . .
15.5 Virtual EML registration on Communication Infrastructure (CI) 118. . . . . . . . . . . . . . . . . . . 15.5.1 Prerequisites 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5.2 Procedure steps 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16 UPDATE OF MSSPRING INFOS (MS–SPRING TAKEOVER) 119. . . . . . . . . . . . . . . . . . . . . . . . . . . 16.1 Prerequisites 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2 Procedure steps 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3 Format of nodedata file 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.4 Loading of a prebuilt nodedata file 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX A INTEGRATION OF 1354RM WITH A1330AS 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1 Installing A1330 AS 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2 Deinstalling A1330 AS 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.3 A1330 AS customization 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3.1 Swedish language 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX B INTEGRATION OF 1354RM WITH GENERIC OS–OS INTERFACE 125. . . . . . . . . . . . B.1 Generic OS–OS Interface Subsysystem 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2 Generic OS–OS Interface Installation 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3 Generic OS–OS Interface deinstallation 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX C INTEGRATION OF 1354RM WITH SEC SECURIYT SUBSYSTEM 127. . . . . . . . . . . . . C.1 SEC Architecture on 1354RM System 127. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.2 Installing SEC Subsystem 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.3 Deinstalling SEC 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.4 SEC Administration 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.5 Alarm Access Configuration 131. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX D COMMAND FILE SPECIFICATION 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1 Command Description 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1.1 Syntax Description 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.2 Setting time reference. 138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.3 Setting network 138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.4 Path commands 139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.5 Trail commands 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.6 Port User Label 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.7 CHOWN commands 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.8 PM commands 150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.9 aSAP commands 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.10 restRule commands 156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.11 Comments 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.12 Sleep command 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.13 Setting timeout 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
5
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.14 Exit command 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.15 Connection command 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.16 Topology Commands 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.17 Upload and Remove NAP 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.1.18 Configure et, physical connection. 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.2 tool description 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.2.1 Handling errors 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.3 Examples 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.1 Example on paths 168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.2 Example on paths protected with Drop & Continue 170. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.3 Example on broadcast path 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.4 Example on broadcast paths (2nd) 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.5 Example on trails 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.6 Example of path that uses HO trails 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.7 Example on measures 188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.8 Example on aSAProfile 190. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.9 Example on restoration rule 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.10 Example on implement, deimplement connection 192. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.11 Example on create, remove, implement and deimplement topology. 193. . . . . . . . . . . . . . . D.3.12 Example on upload and remove nap. 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D.3.13 Example configure physical connection and et. 198. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
6
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
LIST OF FIGURES AND TABLES
FIGURESFigure 1. Example of directories allocation with at least two physical disks 23. . . . . . . . . . . . . . . . . . . . Figure 2. Distribution of files in two application disks 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. Supported topology 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. Not supported topology 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. Reference Network 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLESTable 1. Handbooks related to the specific software application 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. NR 5.0B Related Handbooks 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. Documentation on CD–ROM 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4. Access Rules Description 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5. NAD / FAD 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
7
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
HISTORYAs internal document 3AL 61217 ACAA TCZZA
01 on March 1st, 2000 – Ed.1Creation – 1354RM R5.2.0 – First delivery
02 on April 27th, 2000 – Ed.21354RM R5.2.0 – Integration with SEC, migration ET from generic to meshed, new user “qnnpmop” forQNN and installation kit and patch procedures modified.
03 on June 1st, 2000 – Ed.31354RM R5.2.1 – EML simulation, enable of SEC with AS, Map Management features and migrationprocedure.
04 on August 24th, 2000 – Ed.41354RM R5.2.1 – Set of Swedish language and new batch commands.
05 on September 19th, 2000 – Ed.51354RM 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(For Alcatel internal use only)
[1] HP OpenView Distributed Management Agent Platform Administrator’s ReferenceHP Part No. J1064–90016
[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.1–It.1 July 20th, 1998 ; 3AL 71002 ABAA BHZZA
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
8
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
9
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
1 INTRODUCTION
1.1 General information
WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims theimplied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liablefor errors contained herein or for damages, whether direct, indirect, consequential, incidental, orspecial, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for informationpurposes only and are subject to change without notice. They do not represent any obligation on thepart of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied,reproduced or disclosed to a third party without written consent.
1.2 Handbook applicability
This handbook applies to the following product-releases:
PRODUCT ANV P/N 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. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONSHandbooks relevant to software applications (typically the Operator’s Handbooks) are notmodified unless the new software ”version” distributed to Customers implies man–machineinterface changes or in case of slight modifications not affecting the understanding of theexplained procedures.Moreover, should the screen prints included in the handbook contain the product-release’s”version” marking, they are not replaced in the handbooks related to a subsequent version, ifthe screen contents are unchanged.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
10
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
1.3 Product-release handbooks
The list of handbooks given here below is valid on the issue date of this Handbook andcan 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 thisHandbook.
The standard Customer Documentation in the English language for the equipment whoseproduct-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.FACTORYPart No.
THISHANDBOOK
[1]1354RM Rel.5.2BInstallation Guide
3AL 61261 AAAA 957.130.892 W
[2]1354RM Rel.5.2BOperator’s Handbook
3AL 61259 AAAA 957.130.872 H
[3]1354RM Rel.5.2BAdministration Guide
3AL 61260 AAAA 957.130.882 U
Table 2. NR 5.0B Related Handbooks
REF HANDBOOK ANV Part No.FACTORYPart No.
THISHANDBOOK
or note
[4]1330AS Rel.5.1Operator’s Handbook
3AL 71109 AAAA 957.130.722 A
Table 3. Documentation on CD–ROM
REF ANV Part No. FACTORY Part No. NOTE
[5]3AL 61262 AAAA 417.100.028
Envisaged after the release of allHandbooks
[5]
Contains, in electronic format, the following handbooks: REF.[2] to [4]
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
11
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
1.3.2 Handbooks related to the product’s 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• Heat–radiating 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 inter–working 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 configurethe product.
1.6 Required skill
A good knowledge of HP–UX 10.20, Oracle 7.x Database Management System and HP–OV DM platformis considered a mandatory prerequisite.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
12
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
1.7 Conventions
In this document the installation procedure and maintenance operations are described with all the shellcommands needed by this procedure. Either Korn Shell (ksh) or Bourne Shell (sh) are supposed to beused by the operator.
N.B. Normally are described commands that can be used with a Korn Shell. If you are using a BourneShell you have to pay attention to the symbol definition command. In Korn Shell you can definea 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 useror 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 thecommand:
su root
instead of ”su – root”, because with the recommended command all the RM environmentvariables are kept.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
13
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 acomplete one and supports DB, agents and user interface; US configuration supports only user interfaceproviding network access to IM hosts via CMISE and SQL–Net interface.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
14
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
2.1 Hardware Requirements
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 andmirrored database information.
2 ) the second disk contains the 1354RM product,
N.B. the bdf HP–UX command, specifying the directory as a parameter, can be used toverify 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 bemanaged:– small: ~ 1 Gb– medium: ~ 1.5 Gb– large: ~ 1.9 GbIf 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 thatmust 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 sortingcriteria):– 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 MbPlease note that the previously specified snapshot backup area size do not take into accountthe disk space required by SH backup and it depends on the number of SH managed by the1354RM.
N.B. In order to guarantee Oracle data consistency, Data Disk (1354RM installation) must belocal to the workstation on which 1354RM system will run, and can not be stored in afilesystem reached via NFS.
The following data have to be also taken into account to evaluate a correct 1354RM disk occupation:
• Installation kit g–zipped tar file (if no mass storage device is used): ~ 200 Mb• Swap File on Disk: ~ 512 Mb
N.B. The previous disk occupation data do not take into account the table space created in the1354RM Oracle DB by other subsystems (e.g. 1330 AS – Alarm Surveillance).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
15
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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:
• Installation kit g–zipped tar file (if no mass storage device is used): ~ 200 Mb• Swap File on Disk: ~ 512 Mb
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
16
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
2.2 Software Requirements
2.2.1 IM configuration
1354RM IM have to be installed on Almap HP4 platform updated with the HP4.2 patch level plus thePHSS_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 OSF–Motif 1.2 must be installedwithin HP–UX 10.20 ):
– Bundle(s):B3560CBEng C.05.25 English C SoftBench S700 10.x B3691AA_APZ B.10.20.89 HP GlancePlus/UX for s700 10.20 B3782EA B.10.20 HP–UX Media Kit (Reference Only. See Description) DMPlatDKHP10man B.05.01 DM TMN Manager Developer’s Kit man pages DMPlatDKHPUX10x B.05.01 DM TMN Manager Developer’s Kit DMPlatEngHP10man B.05.01 DM TMN Manager Platform Man Pages DMPlatEngHPUX10x B.05.01 DM TMN Manager Platform HPUXEngCR700 B.10.20 English HP–UX CDE Runtime Environment J2160A_APZ C.07.00 OSI Trnspt and Srvcs for 9000/700 J2655AA_APZ B.10.20.02 100VG–AnyLAN/9000 EISAOVLicenseSvrHP10 B.05.01.00 OpenView License Server for HPUX10.x SoftBenchRef C.05.25 SoftBench 5.0 (Reference Only. See Description)XSW700CR1020 B.10.20.36 Extension Software Patch Bundle XSW700GR1020 B.10.20.36 Extension Software Patch Bundle
– Product(s) not contained in a Bundle:OTS–LITE9000 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 100VG–AnyLAN productPHNE_8830 B.10.00.00.AA OTS C.07.00 cumulative mega patchPHSS_15076 B.10.00.00.AA OV NNM5.0x Consolidated Patch 6–16–98
– 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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
17
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
– 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 (these values are recommended by ORACLE installation)• semmni = 50• semume = 25• semmns = 200• semmnu = 200
– In order to improve performances, it is suggested to remove the following HP–OV DM processes(using the following commands):
• $OV_BIN/ovdelobj $OV_LRF/netmon.lrf• $OV_BIN/ovdelobj $OV_LRF/ovtopmd.lrf• $OV_BIN/ovdelobj $OV_LRF/ovtrapd.lrf• $OV_BIN/ovdelobj $OV_LRF/ovactiond.lrf• $OV_BIN/ovdelobj $OV_LRF/snmpCollect.lrf
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
18
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
2.2.2 US configuration
1354RM US have to be installed on Almap HP4 platform updated with the HP4.2 patch level plus thePHSS_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 OSF–Motif 1.2 must be installedwithin HP–UX 10.20 ):
– Bundle(s):B3560CBEng C.05.25 English C SoftBench S700 10.x B3691AA_APZ B.10.20.89 HP GlancePlus/UX for s700 10.20 B3782EA B.10.20 HP–UX Media Kit (Reference Only. See Description) DMPlatDKHP10man B.05.01 DM TMN Manager Developer’s Kit man pages DMPlatDKHPUX10x B.05.01 DM TMN Manager Developer’s Kit DMPlatEngHP10man B.05.01 DM TMN Manager Platform Man Pages DMPlatEngHPUX10x B.05.01 DM TMN Manager Platform HPUXEngCR700 B.10.20 English HP–UX CDE Runtime Environment J2160A_APZ C.07.00 OSI Trnspt and Srvcs for 9000/700 J2655AA_APZ B.10.20.02 100VG–AnyLAN/9000 EISAOVLicenseSvrHP10 B.05.01.00 OpenView License Server for HPUX10.x SoftBenchRef C.05.25 SoftBench 5.0 (Reference Only. See Description)XSW700CR1020 B.10.20.36 Extension Software Patch Bundle XSW700GR1020 B.10.20.36 Extension Software Patch Bundle
– Product(s) not contained in a Bundle:OTS–LITE9000 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 100VG–AnyLAN productPHNE_8830 B.10.00.00.AA OTS C.07.00 cumulative mega patchPHSS_15076 B.10.00.00.AA OV NNM5.0x Consolidated Patch 6–16–98
– 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 HP–OV DM processes(using the following commands):
• $OV_BIN/ovdelobj $OV_LRF/netmon.lrf• $OV_BIN/ovdelobj $OV_LRF/ovtopmd.lrf• $OV_BIN/ovdelobj $OV_LRF/ovtrapd.lrf• $OV_BIN/ovdelobj $OV_LRF/ovactiond.lrf• $OV_BIN/ovdelobj $OV_LRF/snmpCollect.lrf
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
19
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
3 INSTALLATION
WARNING The following is the Installation procedure that have to be used only internallyby Alcatel Units during Integration phase. Customers and Alcatel Installationpost DR4 must follow the Installation Procedure described in document NR3Installation Guide.
In the following paragraph, the shell commands needed to perform installation, customization andactivation of 1354RM are given.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
20
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
3.1 Installation and Customization of Complete delivery Packages
In the following you can find the procedure to install a complete 1354RM delivery.
a ) If there is an old version installed, shutdown the 1354RM system, the 1354RM Oracle instance andall user service manager instances (ovw, browser and mngAgent).
Since the 1354RM installation performs a reset of OVw–DB (even if the Old Mib option ischosen) no maps will be present at the end of installation. It’s mandatory to save the maps to bekept using DNM application.
b ) Exit from normal user CDE space and log–in 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 bepart of ”dba” group; ”dba” is the same group of the user ”oracle”. This ”snml” user will be the 1354RMsystem administrator.
# sam ....
N.B. Please, do not use as ”snml” user home directory the same directory that will be used asinstallation directory of 1354RM product (see d ))
d ) Create (if it does not exist) an empty directory for 1354RM installation tree root :
# mkdir <your–snml–inst–root>
e ) Change current directory to the SNML installation root and extract ”restore_gz” file from 1354RMinstallation 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 someinconsistencies during the ”etc/restore_gz” procedure.
# cd <your–snml–inst–root>
# gunzip –d –c <1354RM...your–media–device or tar file> | tar xvf – ./etc/restore
N.B. Please, note that ”1354RM...” is the standard prefix of each RM complete delivery orpatches.
f ) Execute restore_gz script running the following command:
# etc/restore <1354RM...your–media–device or tar file>
N.B. The installation procedure creates a link ”/usr/snml” that is linked to 1354RM installationroot directory.
g ) A graphical window with all the needed environment variables (etc/env_snml file) is presented to theuser. The variables, if possible, are initialized with the values assigned to them by the operator inprevious 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).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
21
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
h ) Execute customize script pressing the ”Customize” button, a window will be opened containing thetraces of the Customize execution. If some errors occur during ”customize” execution, it signals tothe operator the log file where he can find information on the occurred error. The customize procedurewill 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, sinceit 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 DBparameters 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
Log–in as “root” user and launch the swinstall procedure:$ swinstall –s <package full path name> SMF
3.1.2 Re–configure SMF installation
After a 1354RM new installation the SMF icon is no longer present on the vertical palette of the desktop.
Execute the following command:$ swconfig –x reconfigure=true SMF
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
22
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
3.1.3 1354RM Installation Environment Variable Definition
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> HP–UX commandcan be used.
3.1.3.1 Application Variables
SNML_HOME Root directory of 1354RM product installation tree. The directory must existbefore installation.The directory must have ”snml” as owner and ”dba” as group and its group writeaccess enabled (i.e. –rwxrwxr–x)
HOST_TYPE It specifies if the host is an Information Manager (IM), with a complete 1354RMinstallation, or an User Service (US), where the User Interface Application onlyis installed. In the former installation type the database is created and agentscan be started, in the second type can be started User Interface Applicationonly, that are connected with a remote database.
N.B. In a multi–workstation installation only one can be defined asInformation Manager. In the following chapter this workstation will bereferred as the IM host.
MIB Meaningful for IM configuration only.This variable specifies if the old 1354RM database must be saved or not. Itsvalues can be ”NEW” (create new DB), ”OLD” (save the current DB or recoverit 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 isperformed on a new installation tree) or keep the oldDB (if the installation is performed on the oldinstallation tree).
REC : this option should be used after a disk failure thatcauses the re–installation of 1354RM application.The customize procedure will not create a new DB inorder to save the mirrored DB information to permitthe recover of DB from an incremental backup.
SNML_MIRROR Meaningful for IM configuration only.This variable specifies the directory that contains the database mirrored dataand Oracle Archive Log data.
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 createdon a different physical disk than the one where 1354RM producthas to be installed.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
23
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Configuration with two disks
SNML_HOMESNML_MIRROR/backup/snml
DIRECTORIES ALLOCATION
Figure 1. Example of directories allocation with at least two physical disks
NTWDOMAIN Meaningful for IM configuration only.This variable specifies the identifier of the network domain handled by the1354RM (by default the variable value is 1).
IM_SERVER Meaningful for US configuration only.This variable specifies the host–name of the IM workstation.
REMOTE_SERVER Meaningful for IM configuration only.This variable has to be set to allow the transfer of all 1354RM backup to a remoteserver. This server must be a 1354RM–IM workstation. These two 1354RMsystem must to have identical value of the variables that specifies the Oracleroot directory (ORACLE_HOME) and the RM–DB Mirror directory(SNML–MIRROR); moreover the directory /tmp must to have enough space totake up the g–zipped backup transfer.
AC_INFO_FLAG Meaningful for IM configuration only.This variable specifies if the old AC_INFO directory must be saved or not. Itsvalue 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
In the following the environment variables that have to be defined to allows the installation procedure toconfigure in the proper way the Oracle database are listed.
ORACLE_HOME This variable specifies the Oracle root directory.
DB_SIZE Meaningful for IM configuration only.It indicates the 1354RM Oracle database size. Possible values are small,medium (default) and large.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
24
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
3.1.3.3 HP–OV Variables
The following environment variables are used to configure properly HP–OV during the 1354RM installationprocedure.
AGENT_REGISTRATION Meaningful for IM configuration only.It specifies if the agent LRF file static registration must be performed during the1354RM installation phase. Its values can be ”yes” (perform the staticregistration – 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 separatedtuples giving printer network names.
a ) Login as snml user and execute:$ vi $XAPPLRESDIR/$LANG/Iview and press [Enter]
b ) type /printerConfig: press [Enter]c ) 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 |;
d ) save and quit the file pressing [Esc] and typing :x! and [Enter].
TAPE_SERVER Meaningful for IM configuration only.This variable specifies the host to which the tape is connected. Its default valueis ”none” and it means no tape driver is installed and, when the backup isperformed, data are saved on disk only.If the tape server is local to the IM workstation, the host name of IM workstationhas 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 existwith an entry composed as the following:
<IM host name> snml
X_CONSOLE Meaningful for IM configuration only.This variable specifies the name of the workstation that will be used as consolein a plant where a server has been adopted.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
25
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 therelated 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 OVw–DB, no maps will be present atthe end of installation. It’s mandatory to save the maps to be kept using DNM application.
b ) Exit from normal user CDE space and log–in again as ”root” user in CDE login form.
c ) Change current directory to the SNML installation root and extract “install_patch” file from 1354RMpatch package.
# cd <your–snml–inst–root>
# gunzip –d –c <1354RM...your tar file g–zipped> | tar xf – ./etc/install_patch
d ) Execute the install patch script running the following commands:
# ./etc/install_patch <1354RM...full path name tar file g–zipped>
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 anindependent window, during this operation the files that have been corrected and that have beenincluded 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 ) execute a backup of the RM database and the AS database (only if you want to save the AS data)b ) execute the step of the chapter [8.1]c ) execute the following command
# mv /backup/snml/Ntwk/tablespaces.dat /tmp/tablespaces.dat
d ) execute the restore.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
26
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
3.3 Multi–IM Configuration
At the end of 1354RM installation in the file ”/usr/snml/conf/<hostname>/ntwDomains” is described thedefault Network Domain (with the Identifier specified in env_snml file) that will be used by RM userinterface. The information will have the following format:
• loc <n> on RM–IM workstation
• far <n> <hostname> on RM–US workstation
where <n> is the Network Domain Identifier and <hostname> is the name of the host where therelevant RM–IM 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 insertmanually 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 RM–IM workstation address and theAGENT_REGISTRATION environment variable, in /usr/snml/etc/env_snml file, must be set to ”yes”.
When the Multi–IM configuration is enabled, opening an empty map in NetView will present a dialog boxto the user in order to associate a Network Domain to the map (info taken into account when normaloperation are executed), on the other side opening the Browser application a Multi–RM icon is presentedas root object and, with the ”Main related item” operation, the user can view all the defined NetworkDomains.
To have got access to the whole network domain, in a multi–master network configuration (i.e. 3 IM WSsand 1 USM WS), it is necessary to do the following steps:
1 ) Add ”user1” on USM and IM_1 (assuming you are working on USM ws);2 ) Add the USM ws console on all IM WSs by ”Add console” function (working on each IM);3 ) Add the ”user1” on IM_2 and IM_3 by ”Add Operator” function (working on each IM).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
27
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
4 HP–OV DM CUSTOMIZATION
4.1 PMD Configuration
Meaningful for IM configuration only.
The adopted stack for the communication between RM–US and RM–IM processes (RM F interface) is theRFC 1006 (OTS light). With RM delivery is distributed a file pmd.lrf (in the directory ”/usr/snml/lrf/OV”)where HP–OV CI configuration parameters are set by 1354RM. These parameters specify the size ofstack’s or the time–out in seconds to wait for response to confirmed operations. This file is automaticallyregistered in place of the default pmd.lrf file by the customize and customize_patch procedures. If thesystem administrator wants to change these values, he has to execute the following procedure with rootuser 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 HP–OV 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
The previous options change for CMIP and XMPV7 stack:O : the time–out value (in seconds) for confirmed requests;Q : the unsent operations queue size;I : the ”active” confirmed operations queue size.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
28
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
4.2 Installation on Distributed Platform
4.2.1 Remote Event Sieve configuration
Meaningful for IM configuration only.
This configuration is based on a configuration file (”/usr/snml/conf/im_host_conf”), where host names ofworkstation are described giving also their product supported (EML, AS or RM). This file is automaticallyused by applications to create Remote Event Sieve in order to enable sending events only on workstationsreally involved in the event handling.The file is update in automatic way by the RM and AS installation procedures. When a new EML’sworkstation 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 ForwardingDiscriminator shall be created on WX.
N.B. In order to allow the interworking between ”HP–UX 10.10 / HP–OV 4.2” workstations and”HP–UX 9.5 / HP–OV 4.01” ones, the user have to modify manually the ”im_host_conf” fileadding after the name of HP–UX 9.5 workstations the tag ”DM40” (please, note that asseparator between host–names 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 anddeinstall_A1330 procedures the ”im_host_conf” file is automatically rebuilt, so the DM40 tagsare lost.
4.3 Object Registration
Meaningful for IM configuration only.
In the directory $NXNL_PRD/lrf are present the local registration files, used by the installation procedureto register the objects managed by agent process. A ”lrf” file exists for each agent and has the same agentname with the ”.lrf” tag.
In directory /usr/snml/etc are present two procedures: addobj and delobj. These procedures have to beexecuted with root user privileges and register (addobj) and deregister (delobj) all the 1354RM localregistration files.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
29
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
5 IPC RESOURCES CONFIGURATION
Meaningful for IM configuration only.
Agent processes of 1354RM product use some IPC resources that are specified by the following symbolsdefined in $NXNL_PRD/.nxnlenv (in brackets default values are specified):
1 ) Queues : Five queues are used and their identification numbers are specified byTOPMNGQUE (62), TRSMNGQUE (63), ALRMGRQUE (64), PMCONSISTQUE (65) andQNNERQUE (90) symbols.
2 ) Semaphores : A semaphore is used and its identification number is specified by ALRMGRSEM(64) symbol.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
30
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
31
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 whichis possible to start 1354RM application (see 6.2.2).To handle 1354RM operators data on US or IM node the system administrator must:
a ) select in 1354RM subpanel the SMF Button,b ) select the Operator Admin application, by means of this functionality the System Administrator can:
1 ) Add a new operator;2 ) Remove an operator;3 ) Change an operator password;4 ) NAD Management;5 ) List all the defined operator;6 ) List successful login;7 ) List unsuccessful login;8 ) List the currently logged in operator.
This procedure handle the users on all the workstation belonging to the 1354RM distributed architecture.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
32
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
6.2 User Profiles
Five user profiles are defined: OS Administrator, Administrator, Constructor, Path Builder & Look OnlyUsers. This profiles specify the operations that an operator can execute. In order to define the correct FADsfive environments have been defined specifying five versions for:
• HP–OVw Registration files.• CDE initialization files.• X Application Resources directory.• Browser Toolbar configuration files.• Unix user profile file (.profile).
6.2.1 HP–OVw Users Profile for NetView application
In the SNML delivery five HP–OVw 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 allNetView 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 eventlogger 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 synchronizationprocess should be defined. The constraints are specified by means of a synchronization level that is givenas an input parameter to the NetView application. It is specified in the file nxnlOus of the relevant user inthe command line (by default all the profiles have no constraints defined):
Command –Initial –Restart –Shared ”$NXNL_PRD/bin/nxnlOus –syncroLevel 0”
The system administrator can specify, if it is necessary, the synchronization level for a whole users profilemodifying 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 themap and it will add in the map new discovered topological object contained in the constraints levelpreviously specified.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
33
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 for Constructor user
/usr/snml/conf/users/PathBuilder/dt/C/dtwmrc for Path Builder user
/usr/snml/conf/users/LookOnly/dt/C/dtwmrc for Look Only user
From the vertical subpanel these users can start the TMN–OSs, System Management Features, AlarmList, Browser and NetView (ovw) applications. It is also available a customized pop–up menu (associatedto 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 FileManager, 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 printterminal hardcopy.
From the horizontal panel the Path Builder user can open a File Manager, start the Mailer and functionsto print terminal hardcopy.
The print terminal hardcopy functions use the standard PRINTER variable (that can be defined for all usersin .nxnlenv file) to determine the printer device to use, that must be able to print ASCII text and Hardcopypostscript.
6.2.3 Unix Shell Profile (.profile)
Meaningful for IM configuration only
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:
/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 for Constructor user
/usr/snml/conf/users/PathBuilder/profile for Path Builder user
/usr/snml/conf/users/LookOnly/profile for Look Only user
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
34
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
6.3 Network Access Domain Management
The combination between a UNIX user and the workstation on which he is logged–in is identified in RMby 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 UserProfile (see 6.2) on group of network objects like group of paths, NAP’s etc.
This definition implies that a UNIX operator can have different rights depending on theworkstation used.
A command allowed by the User Profile can be denied by the Access Rules either completely oronly on specific objects. The User’s FAD is identified by the combination of the User’s 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. SMFsdepends only by User’s 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, NAP’s,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 !).
The currently defined Access Rules allow to define initiators beloging to the following categories :
• administrators able to work on all the resources independently from their NAD
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
35
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
• non VPN initiators able to see all the resources and to operate only on resources not relatedto VPN operators. In this category is possible to define Network Constructor and / or PathBuilder Initiators.
• VPN initiators able to operate on and to visualize only assigned resources (with possibleexceptions on free resources – see 6.3.3.1). These initiators can normaly perform only pathconfiguration 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 OperatorAdministration 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 theAdd operator function is mandatory to select the User Profile (i.e. the set of Menus displayed for that useron 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 VPNInitiator.
If two UNIX users are mapped to the same Initiator they will share the same NetworkResources and capabilities.
If the created user shall be related to a not existing Initiator, it is mandatory to edit, manually a file (see6.3.2).
Once the initiator is created (if necessary), it has to be mapped to the user by means of the NetworkAccess 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 pop–up menu. In the pop–up menuall the defined initators are listed.
The Access Rules are described in paragraph 6.3.3.1 & 6.3.3.2.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
36
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
6.3.2 Defining a new RM Initiator
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 attributeis used to “mark” Network Resources (using the change NAD command) and to evaluateAccess 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 : Rules 50 : Path Administrator : AC_R_PADMIN 55 : PathWatcher : 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.
The rules are evaluated sequentially and in case of duplication or inconsistency only the first istaken into account.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
37
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
6.3.3 Access Rules description
List of Rules
RM INITIATOR
Customer Rules
Embedded Rules
– Id– Name
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 completelyfree but some logical limitations exist.
The available rules are (more datails are present in 6.3.3.3) :
– AC_R_SNML: RM Administrator.
It’s able to perform all the operations without any limit.
It must be assigned very carefully because an Initiator with this capability can modifyoperations 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 ismandatory do not change the snml initiator.
– AC_R_PADMIN: Path Administrator.
It can manage paths and releated resources (NAPs and LCs) not explicitely assigned toVPN domains.This rule can be composed with AC_R_TOPMAN and/or AC_R_PAYMAN in order toachieve the needed level of functionality.
the AC_R_PADMIN rule cannot be used for VPN Initiator.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
38
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
– AC_R_PATHALL: Path Allocator.
It can allocate/deallocate paths and manage the resources (NAPs and LCs) not explicitelyassigned to VPN domains.This rule can be composed with AC_R_TOPMAN and/or AC_R_PAYMAN in order toachieve the needed level of functionality.
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 toachieve the needed level of functionality.
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 toachieve the needed level of functionality.
the AC_R_PAYMAN rule cannot be used for VPN Initiator.
– RVPN: Restricted Virtual Private Network Operator.
It’s able to create, view, modify paths only using resources (NAPs & LCs) assigned to hisNAD.
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
No check is performed to avoid the assignment of a VPN rule to non VPN Initiators andviceversa.
– AC_R_NN: NN Operator.
As VPN except that you can assign free objects too (path,trail,lc and NAP).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
39
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 WeeklyScheduling.
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 containsthe corrispondent embedded rule and the time scheduling.
The information included in the file is :
– Name of the Customer Rule
– Daily Scheduling: it’s the validity start & end time of the Rule. Starting and Ending Time has theformat hh.mm–hh.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. Possiblevalues are in the range from 0 (Sunday) to 6 (Saturday). An empty value enables the rule in all thedays.
– 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 : Embedded RuleAC_R_NEWPADMIN : 08.00–19.00 : 1 , 2 , 3, 4 , 5 : 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
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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
40
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Table 4. Access Rules Description
C Operation RULE NotesLASS
RVPN
VPN
EVPN
PTH–ADM
PTH–ALL
PTH–R/O
TOP
PAYLOAD
SNML
NN–OP
P allocate, deallocate, O O O N N A OATH
implement, deimple-ment, commission,decommission, add/remove protection.....
O O O N A O
get O O O A A A A O
Add / remove leg O O O N A O For the add leg, the checkis performed also on theNAP (see Use in Path)
Create A A A A A A A The initiator ID is taken asNAD of the created object.In the redolog, the pathcreation is followed by achange of NAD in order tobe able to replicate the fi-nal result in term of NAD.The check to allow or not apath creation is made onthe path and on the speci-fied NAPs; the path iscreated if the NAPs can berelated to the path (seeNAP class)
Change Owner O O O N N A OF
It is the action to changethe NAD. The operation isregistered in the redolog
Delete O O O N N A O The check is done on thepath and NOT on the usedNAPs (unset of the pathPtrattribute)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
41
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Table 4. Access Rules Description
NA
remove nap O O OF
A O
Pget O O O
FA A A A O
change owner O O O N N A OF
The operation is register
Use in path (create apath or add leg)
O O OF
N N A O The command is not pres-ent at the user interfacebut is embedded in createpath and add leg. It is de-fined as set on pathPtr at-tribute
LC
Change owner O O O N N A OF
The command is regis-tered in the redolog.As a consequence of thisoperation the LC is alsomoved from the originalRouting Link bundle to theappropriate one. A newrouting links is created ifneeded.
Use in path O OF
OF
N N A OF
The command is not pres-ent at the user interfacebut is embedded in path ortrail allocation. It is definedas set on the belongTrailIdattribute.
The allocation algorithmduring the search onlyuses the Routing Linksmatching the condition forLC’s
Delete N N A The command is not pres-ent at the user interfacebut is embedded in thepayload configuration ofphysical connections andHO–Trails.
get A A A A A A A A A
Configure Payload A A Only for HO–Trails
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
42
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Table 4. Access Rules Description
TR
Change owner O O O N N A OF
The command is regis-tered in the redolog
AI Configure Payload A AIL Create A A It is the creation of the HO–
Trail
Remove A A It is the action to removethe HO–Trail; as a conse-quence a payload de–con-fig. is started.
TRA
Set Qnn Info A A A A
AIL
Get A A A A A A A A A
TOPO
Create A A It is the operation to acti-vate topologies, Nodes,physical Connection (ac-tion)
L./P
Implement A A It includes the configura-tion at HOP
H De–implement A ACO Upload NAPs A A A ANN Remove A A
Start Network Activ. A A
Configure Payload A A
Get A A A A A A A A A A
MS–SP
Operate on protectionblocks
A A Operation are : modify theWTR, force, manu-al,...synchronize
RING
Get A A A A A A A A A A
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
43
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Table 4. Access Rules Description
CTP/
Change defaults forUPA propagation
A A
/TTP
Get A A A A A A A A A A
PDH
Configurate PDH port A A It is the action to modify theconfiguration of a trans-mux board
–PORT
Loop Back A A A A It is the action to loopbacka PDH port for testing. Theaction can also be startedon a NAP but only as anextension at US level.
Get A A A A A A A A A A
EML
Configuration Down-load
A A It is the action to enable /disable the configuationdownload from RM to NEs.The check is performedalso for operation startedon single NEs
Start Audit A A It is the action to start Au-diting differences betweenNE and EML view. Thecheck is performed also onoperations started onsingle NEs.
Get A A A A A A A A A A
OTH
Get A A A A A A A A A A Eventually restricted byFAD at the user Interface
HERS
Operations A Restricted by FAD imple-mented at the user inter-face
RVPN
VPN
EVPN
PTH–ADM
PTH–ALL
PTH–R/O
TOP
PAYLOAD
SNML
NN–OP
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
44
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
6.3.3.4 Embedded Rules for PM
New rules have been added to manage Performance Monitoring activities. They are described in thefollowing paragraphs.
– AC_R_PMSNML: Performance Monitoring SNML
PMSNML is the rule allowing full capability of managing PM domain objects. This rule allows to operateon 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 ruleallows 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 pmTransportof 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 allowsto fully operate on PM domain related to “non VPN” measures, PM transport etc. and visualize allthe PM data even if belonging to VPN domains.
Non VPN domain is the set of all RM objects with nad<300.
– AC_R_PM–RO: Performance Monitoring Read Only
PMREAD is the read only rule on PM domain. This rule allows to visualize all the PM relatedinformation regardless to the ownership.
– AC_R_PMVPN–RO: Performance Monitoring Read Only VPN
PMREAD is the read only rule on a given NAD. This rule allows to visualize the PM related informationrelated to a given NAD.
6.3.3.5 Default mapping between Access Rules for PM and Object Class
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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
45
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Table 5. NAD / FAD
C Operation RULE NotesLASS
PMVPN–RO
PMVPN
PMADMIN
PM–RO
PMSNML
ME
Create A A A This is the first step to start a mea-sure session.
AS Delete O N ASU Set O N ARE Get O O A A A
Activate, Stop and Consis-tency
O N A
Correlate Transport to Mea-sure
O N A This action correlates a Measure toa Path or Trail.The check is performed on thePath/Trail too.
Correlate Tp to Measure O N A The check is performed on the Tp(nap, cap, ctp) too.
Correlate Report to Measure O N A The check is performed on the re-port (Counter Report or TCR) too.
CO
Create A A A
UNT
Delete O N A
ER
Set O N A
RE
Get O O A A A
PORT
Correlate Report to Measure O N See the note about this action in theMeasure class context.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
46
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Table 5. NAD / FAD
T Create A A ACA Delete O N A
Pr
Set O N A
of
Get O O A A A
ile
Correlate pmTp To TCA O N A The check is performed on thepmTp too.
T Create A A ACR Delete O N AR
Set O N A
Get O O A A A
Correlate Report to Measure O N A See the note about this action in theMeasure class context.
PM T
Create A A A This command is not present at theuser interface. It is a consequenceof the Correlation of a Path/Trail toa Measure.
RA Delete O N ANS Get O O A A A
PM T
Create O N A This command is not present at theuser interface. It is a consequenceof the Correlation of a Tp to a Mea-sure
PDelete O N A
Get O O A A A
Correlate pmTp To TCA O N A See the note about this action in theTCA class context.
PATH
Correlate Transport to Mea-sure
O N A
NAP
Correlate Tp to Measure O N A
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
47
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Table 5. NAD / FAD
TRAIL
Correlate Transport to Mea-sure
O N A
CTP/TTP
Correlate Tp to Measure OF N A
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
48
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
6.3.4 Delivered set of Initiators
A set of Initiators is provided with 1354RM delivery. They represent the most typical operator profiles forthe 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 PAYLOADPTH–ADM
Network Constructor TOPPTH–ADMPAYLOAD
Path Watcher PTH–R/O User profile for read–only op-erations on path trail.
Path Administrator PTH–ADM Operator for working on path.
Path Allocator PTH–ALL Path create and allocate/deallo-cate allowed.
1354 NN VPN Qnn Agent.
R–VPN Operator RVPN It is the restricted Virtual PrivateOperator.
VPN Operator VPN It is the Virtual Private Operator.
E–VPN Operators EVPN It is the enhanced Virtual Pri-vate Operator.
Payload Manager PAYLOAD
cnm_pathbuilder VPN
PMVPN
cnm_lookonly PMVPN–R/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).
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 E–VPN or VPN or R–VPN
Path allocator Path Allocator
Look Only Path watcher on whole RM
cnm_pb cnm_pathbuilder
cnm_lo cnm_lookonly
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
49
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
7 PROCESS MONITOR & CONTROL
7.1 Maintenance Commands
Meaningful for IM configuration only
1354RM Agents and Oracle database can be handled using mngAgent utility. It can be used in a graphicor not graphic mode. Not graphic mode is useful if you want to use it in a shell command (e.g. systemstartup 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 ] databaseThe 1354RM system must be stopped in order to shutdown database instance.
b ) Start or stop 1354RM system:$ mngAgent [ startup | shutdown ] systemThe 1354RM system can be started only if database instance is already active.
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 thecurrent run–level.
d ) Enable or disable 1354RM control function:$ mngAgent [ startup | shutdown ] control
e ) Check 1354RM system status:$ mngAgent checkThe 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 notbelonging to the selected run level and starting stopped processes belonging to the selected runlevel.
g ) Get the current run level:$ mngAgent get_run_levThe command set the Unix system variable ’?’ with the currently set run level.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
50
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
7.2 Integration of IM Agent in 1354RM PMC
Meaningful for IM configuration only
Other Alcatel network applications can enable 1354RM PMC to start and to control their own Agents. Todo this a file named mng_agent_conf must be placed on the installation home directories of the involvedapplications in which they have to specify the characteristics of their agents. In particular in this file mustbe specified the agent parameters, if the process has ”child processes” (and if it has, their names), whereis 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 modificationsthe 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 andovstop HP–OV 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 thatstarts 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 parametersdescription spaces are replaced by commas.
• agent_child (n lines) : child processes name, number of its instances that are controlled by PMCand 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”)time–out (number of seconds) to wait before PMC can check the correct agent initialization afterits startup.
• agent_shut_wait : (this entry is meaningful only for agent with agent_type = ”general”)time–out (number of seconds) to wait before PMC can check the correct agent termination afterits shutdown.
• agent_mon_interval : number of seconds between two consecutive polling operation on theagent.
• agent_max_size : maximum memory size (in Kb) that can be reached by the agent. If this valueis reached and the monitor function is enabled an automatic agent shutdown and restart isexecuted, if it is reached but the monitor function is disabled, the agent is displayed with theWRONG status.
• agent_trace_location : directory or file containing the trace information associated to theprocess.
• agent_trace_default : it specifies the default trace file to be visualized, between the onesdisplayed to the operator. Typically this multiple trace files selection is between agent trace fileand 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
51
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
N.B. The relation between Action and command to be executed is done by means of the orderingnumber.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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
52
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
53
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
8 DATABASE MANAGEMENT
8.1 Database Creation
Meaningful for IM configuration only
In order to create a new database the following procedure shall be executed:
$ $DB_ROOT/etc/create_db
After the database re–creation you can perform a restore of network configuration, alarms and PM datafrom a backup (if any).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
54
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
8.2 Database disk usage
It is advisable to run periodically the script db_report, to check the use of disk space made by Oracle.
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 infile /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 avail %used Mounted on
/dev/dsk/c0t6d0 1851289 935444 730716 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 97.34375
rbs01.dbf RBS 8388608 7948288 440320 5.24902344
system01.dbf SYSTEM 15728640 8220672 7507968 47.734375
temp01.dbf TEMP 10485760 2048 10483712 99.9804688
STORAGE ALLOCATED FOR ALL TABLE SEGMENTS
LEGENDA
size: allocated extents in bytes
owner table_segment size extents
–––––––––– ––––––––––––––––––––––––– –––––––––– ––––––––––
SNML AG 532480 1
SNML CAP 266240 1
...
SNML TRANS 1054720 1
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
55
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ALLOCATED EXTENTS TO ALL TABLES
tables_tot_size (bytes)
–––––––––––––––––––––––
27447296
STORAGE ALLOCATED FOR INDEX SEGMENTS STORED WITH DATA
LEGENDA
size: allocated extents in bytes
owner index_segment size extents
–––––––––– ––––––––––––––––––––––––– –––––––––– ––––––––––
SNML COUNT_INDEX 15308800 1
SNML PMLDST_INDEX 266240 1
...
SNML UNIQUE_TRAIL_USERLABEL 266240 1
ALLOCATED EXTENTS TO INDEXES STORED WITH DATA
indexes_total_1 (bytes)
–––––––––––––––––––––––
21964800
STORAGE ALLOCATED FOR INDEX SEGMENTS STORED SEPARATELY
LEGENDA
size: allocated extents in bytes
owner index_segment size extents
–––––––––– ––––––––––––––––––––––––– –––––––––– ––––––––––
SNML CAP_IDX1_INDEX 1054720 1
SNML CTP_IDX2_INDEX 1054720 1
...
SNML PK_TRANPK_TRANCONNID 51200 1
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)
table num_rows avg_row_len blocks empty_blocks avg_space
––––––––––––––– –––––––––– ––––––––––– –––––––––– –––––––––––– ––––––––––
AG 0 0 0 259 0
CAP 52 56 2 127 442
...
TRANS 843 14 10 504 632
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
56
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
STATISTICS FOR SCHEMA OBJECTS/2
LEGENDA
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 52 1271 0 0 515
COUNT_INDEX 366968 7115386 0 0 7475
...
UNIQUE_TRAIL_USERLABEL 205 5571 0 0 130
It is also advisable to run periodically the script db_memory, to check the use of RAM memory made byOracle.
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 infile /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
–––––––––– –––––––––––– ––––––––––
698191 7678 1.09968648
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
57
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 10–15% 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 60–70% for optimum performance
db block gets 273088
consistent gets 3116137
physical reads 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: willing–to–wait requests successful the first time
WTW Misses: willing–to–wait 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 535426 11 0 0
redo copy 0 0 0 0
0% WTW ratio for redo allocation latch
0% WTW ratio for redo copy latch
0% IMM ratio for redo allocation latch
0% IMM ratio for redo copy latch
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
58
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
2 USER AND SYSTEM SESSIONS
SESSIONS CURRENTLY OPEN
user schema osuser PID machine program
–––––––– –––––––– –––––––– –––––––– –––––––– ––––––––––––––––––––––––––––––
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)
SYS oracle72 9422 tlvhhk oracle@tlvhhk (RECO)
SNML5 SNML5 snmlr50 6292 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6974 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 7201 tlvhiu ? @tlvhiu (TNS interface)
SNML5 SNML5 snmlr50 6440 tlvhhk ? @tlvhhk (TNS interface)
SYSTEM SYSTEM snmlr50 7526 tlvhhk sqlplus@tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6928 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6449 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6282 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6443 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6446 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6397 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6439 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6441 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6243 tlvhhk sqlplus@tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6605 tlvhhk ? @tlvhhk (TNS interface)
SNML5 SNML5 snmlr50 6613 tlvhhk ? @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
––––––––––––––––––––––––––––––––––––––––––––––
696004 bytes
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
59
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
3 CONTENTION FOR RESOURCES
ROLLBACK SEGMENTS
Note: hits should be more than 95%
NAME GETS WAITS hits
–––––––––––––––––––––––––––––– –––––––––– –––––––––– ––––––––––
SYSTEM 4101 0 100
LARGE_RBS 7832 0 100
R01 7824 0 100
R02 7932 0 100
R03 7794 0 100
R04 7780 0 100
The administrator must check that for each tablespace there is at least a data file with over than 30% freespace. If not so, the administrator must consider for that tablespace the database extension proceduredescribed in the next paraghraph.
The administrator must also check that for each table or index segment, the associated number of extentsdoesn’t exceed 10 otherwise he must consider the full backup and restore procedure described inparagraph [8.4].
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
60
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
8.3 Database extension
Oracle uses pre–allocated and not extendible tablespaces, so it could happen some RM functions failsand in trace files could be found messages as the following:
Message: ORA–01653: 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 namecan be found.
To solve this problem the tablespace must be extended using the following procedure (it’s no necessaryto 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 executeas 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 datafilewith the same size of the previous ones.
It is strongly reccomended to execute a backup and a restore on the RM database.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
61
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 relevantdata on user interface.
The first three subsystems backup/restore procedure are based on the Oracle import/export features, soonly table data are saved and not the table structure. This imply to recreate the Oracle DB (see 8.1) beforerestoring them.
The Figure 2. illustrates the information distributed in the two disks.
EXTERNAL DISK
APPLICATION / OP. SYS.
INTERNAL DISK
BACKUP / MIRROR
Operating System
Base Software
Application SW ( RM )
Oracle DBredologs & control
/backup
archives files( /mirror/arch )
reference base( /mirror/db_ref_base )
redologs & control
( /mirror/mirror )
Figure 2. Distribution of files in two application disks
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
62
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Prior to execute the backup / restore feature for NR2 EMLs (SH and WX) it is necessary toexecute the following manual workaround procedure:
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 logicalnumber of the EML (EML Domain Id). The EML name (1353<sys>_<nn>) couldbe 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 it’s guaranteed the saved dataintegrity.
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 Oracledatabase) and optionally on a tape (see Figure 2. ).
Different backups are stored on an unique tape.
The suggested frequency is once per day.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
63
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 ) To realign the DB, copy the redo log file in the user’s home directory (i.e. /users/snml) creating a newfile with ”.rmCmd” extension and empty the current redo log file, using the following commands :
– $ cp $NLredolog <user_home_dir>/<filename>.rmCmd– $ >$NLredolog
b ) Perform the “Upload NAPs” operation. The uploaded NAP are not traced in the redo log file, but pathoperations executed by the rmBatchUtil procedure refer them by means of their userlabel. This is thereason why the “Upload NAPs” can be executed manually after the restore.
c ) Set to ”False” the global configuration of the ETs involved in payload configuration operations.Payload configuration is re–built by creating and configuring / re–configuring HO–trails. HO–Trailsin a ring can only be created if the global configuration is set to ”False”.
d ) Start the batch procedure opening the CDE file manager from the CDE panel and selecting frompop–up menu of the saved file the ”Execute–batch” command. Please note that the output of thebatch procedure will be redirected to a file (which name is <filename>.rmCmd.log) in order to be ableto analyze the results at the end of the execution.
During the execution, the performed operations print on the terminal their results. The results ofthe batch execution may depend from external conditions (time–outs, concurrences...) so, mayhappen that a small number of operations in a large batch file can fail when repeated. This canbe recovered taking into account that the output file of rmBatchUtil reports either the commandsand the results. Failed commands may be saved in an other file and executed later. Payattention in case of failure on allocation, add protection or remove protection, that also previousconstraints 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 configurationof the ET will be automatically re–calculated.
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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
64
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
8.6 Identifier Defragmentation Procedure
In the following it’s described the procedure needed to defrag the primary keys identifiers of RM databasetables.After the procedure execution, the primary key column value of every table will be in the range 1..n, wheren 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 Controlfacility.
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 atemporary 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 normallyenough; 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 filename 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)
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 operatorcan enter ”n” (feel free to press <Ctrl–C> if you like) , (re)set the uncorrect environment variable, andrestarts ”./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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
65
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
N.B. If any error occurs during execution of ”./idDefrag” (after your ”y” confirmation) thedatabase is left in an unconsistent state.After fixing the problem, you have to perform a RM database full restore and thenrepeat this whole sequence of operations (i.e. starting from point b)). *** It’s 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 <ctrl–c> 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 fractionof the database itself. In addition, you are incouraged not to perform it since it needs some criticaldatabase operations. Only if you are an Oracle expert, check ”Oracle Server: Administrator’s 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 RMwhose 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 automaticallyrealign itself with RM at restart.
8.6.2 idDefrag procedure – structure of log file
(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 new–old 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) aredefragmented by this procedure. Currently (19 December 1997) they are:– TP.tpId– TRANPK.tranconnId– PMTROP.pmTranOpId– PMREOP.pmReportOpidOther primary keys will be added if necessary.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
66
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
8.7 DB configuration for huge networks
The Configurable Parameter shmmax must be set to 100000000 (100 Mb).
The Oracle start–up parameter shared_pool_size must be set to 64 M. The procedure is as follows:
a ) shutdown the system and the database;b ) cd $DB_ROOT/admin/pfilec ) su oracled ) vi init1.orae ) change the value of shared_pool_size to 64000000 (64 Mb).f ) restart the database and the system.
Every time that the customize procedure has been done this procedure must be re–executed.
8.8 Managing indexes
Some problems of performances can arise when a lot of network objects are updated and/or a lot of alarmsare received and cleared. In fact, in this case the structures of indexes inside the RM database are brokeninto fragments; unfortunately ORACLE is not able to manage this situation automatically.
As work–around, 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
67
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
9 SYSTEM MANAGEMENT FEATURES (SMF)
9.1 EMLs Data Definition for SMFs
Meaningful for IM configuration only
In order to handle management features commands a file named smf_conf must be placed on theinstallation home directory of 1354RM and 1353SH both on RM and SH workstations. In smf_conf fileeach product must specify its own characteristics and features procedures.
Each specified procedure should respect the following requirements:
a ) it should be an absolute path name of a file executable and readable by each user;b ) if not differently specified (see paragraph 9.1.1), the procedure returns:
– a code = 0 in case of success;– a code � 0 in all other cases;
c ) it should provide, on standard error, information describing the occurred errors;d ) commands and parameters (if any) should be separated by coma character (”,”) instead of blank;e ) not supported commands have to be inserted giving as parameter the string ”none”;f ) labels which require necessarily a command expression, are marked by the word mandatory;g ) it should be able to trap the SIGTERM signal for aborting request;h ) it should be able to log the executed operation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
68
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
9.1.1 Description of ”smf_conf” file parameters
In the following the needed smf_conf labels and related commands are described:
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 TMNnetwork.
– sys_check_comm : <check–proc–name> mandatory.this is the procedure that determines the system state, used to visualize the right icon inside theOSs _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 : <start–proc–name> mandatory.this is the procedure that starts the system.
– sys_stop_comm : <stop–proc–name> mandatory.this is the procedure that stops the system.
– sys_log_comm : <log–proc–name> mandatory.this is the procedure that starts on current display graphic (TCL/TK) log view utility.
– sys_check_control : <check–processes–autostart–proc–name> mandatory.this procedure allows to check the processes autostart status: the procedure returns 0(autostart ON), or 1 (autostart OFF).
– sys_start_control : <put–ON–autostart–proc–name> mandatory.this procedure puts ON the processes autostart status.
– sys_stop_control : <put–OFF–autostart–proc–name> mandatory.this procedure puts OFF the processes autostart status.
– sys_print_control : <print–proc–name>.this is a customized procedure to execute print actions requested by an operator using SMFapplication functions. If the command is given, it is the same for all the functions which providethe possibility to print.
SUBSYSTEM parameters– subsys_name : <name> mandatory.
It is the subsystem name (e.g. 1354RM, 1354NN, node name of 1353SH workstation ...). It mustbe unique among subsystems which are part of the same TMN network.
– subsys_check_comm : <check–proc–name> mandatory.this is the procedure that determines the subsystem state, used to visualize the right icon insidethe 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 : <start–proc–name> mandatory.this is the procedure that starts the subsystem.
– subsys_stop_comm : <stop–proc–name> mandatory.this is the procedure that stops the subsystem.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
69
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 thefollowing:
– subsys_bck_<data type> : <backup–proc–name>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> : <rollback–proc–name>it is the procedure that executes rollback of backup actions; it is automatically executed in caseof failure of one subsystem backup command.
– subsys_res_<data type> : <restore–proc–name>it is the procedure that executes restore from data stored in the directory /backup/<subsystemname>/<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 initializedafter the initial backup at the end of the first installation. The backup time measurement will be usedto have a restore time estimation.
– end_subsys
9.1.2 Network’s configuration file generation
Once a new installation of managed subsystem (EML or A1330) has been completed (and due to this anew smf_conf file is available), the users has to execute the following command (as ’root’ user):
# /usr/snml/etc/update_network
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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
70
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
9.2 1354RM Scheduled Operations
Using the ”Periodic Action” function defined inside the SMF application in 1354RM subpanel, is possibleto book specific action to be executed periodically.
1 ) select in 1354RM subpanel the SMF Button,2 ) 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 networkconfiguration data.
2 ) Save and Clean Log&Trace files: it enables a periodical cleaning of the agent’s trace files toavoid 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 blocksnumber) that the trace file can reach (default MAXTRACESIZE=1000 disk blocks).
3 ) Clean DB archives: it enables a periodical cleaning of the oracle archived redo log files. It wouldbe mandatory to enable this function if the Incremental DB archive backup is not used.
4 ) Incremental DB Archive Backup: it allows to specify the execution frequency of the incrementalbackup.
5 ) Save and Clean Events Log: it enables a periodical archive of the Events Log.6 ) 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 ina backup copy and a new empty one is created. The function mantains a pool of the last 10archived files.
N.B. During the installation phase the Save and Clean Log&Trace files and the Clean DBarchives (this one only when the installation is done with the parameter MIB differentby ”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 relatedoperation.
2 ) Set scheduled time : it allows to the administrator to insert, or to change, the scheduling timeof the related operation.
3 ) Cancel scheduled time : it removes the previous inserted booking time for the related operation.
9.3 Multi–Screen Installation
In order to permit to System Management Features to work properly in 1354RM with distributedarchitecture (IM–US workstations or X–terminals) a tools is available to declare all nodes. The tool iscontained in the SMF application in 1354RM subpanel and it is named Console Administration. This utilitycan be used to add, remove, lock or unlock a specific node and list all the 1354RM nodes. It can be usedfrom any node of 1354RM distributed architecture.
N.B. No automatic discovery of existing workstations or X–terminal is performed, but the applicationwill display only data inserted manually buy 1354RM administrators.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
71
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
10 1354RM BEHAVIOR
10.1 EMLs management
10.1.1 Procedures to define EMLs managing Q3 NEs
Meaningful for IM configuration only
EMLs that are managed by 1354RM can be created/deleted on–line in RM database using the followingcommands:
– # /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 tothe PMC.
10.1.2 Procedures to create EMLs managing QB3* NEs
Meaningful for IM configuration only
EMLs that are managed by 1354RM can be created in RM database using the following command:
– $ usr/snml/bin/nlCreateInDb –eml [ –id <EML_id> ] –f
N.B. Identifier parameter will be requested explicitly by the procedure if it is not indicated. The EMLidentifier must not be reserved by 1354RM (see next paragraph). The creation of a “virtual“ EMLdoesn’t require the –f option.
EMLs are created with ”dummy” userlabel with the format ”EML_<id>”, that will be replaced by the realEMLs userlabel during the EML–NML alignment process (see 11.3).
Using the –h option, as indicated below, the command prints on the screen its syntax:
– $ nlCreateInDb –h
N.B. The emlDomain 0 is reserved by RM, that use it as a ”virtual” EML.
10.1.3 Procedures to delete EMLs managing QB3* NEs
Meaningful for IM configuration only
EMLs which have been accidently created in the RM database and are not needed can be removed withthe following command:
– $ usr/snml/bin/nlCreateInDb –del –fdn ntwDomId=1/emlDomId=13 –f
You can find the fdn for the eml you want to delete by going into the network view, upload available EMLsand 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
72
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
10.2 Path / HO–Trail allocation algorithm failures
When a path allocation is asked from the User Interface, a first consistency analysis is performed and theresult is reported to the user. If the allocation activity does not succeed, the path ”working state” attributeis set to ”Failed to Allocate” and using the event logger (from the event log file) the error code (and therelated message) can be retrieved.
The possible error codes are :
a ) Not enough resources in the network; this covers many cases:
1 ) there are no more free link connections in a physical connection;2 ) a physical connection has been configured with different payload;3 ) a connection inside an NE is not possible due to an NE constraint;4 ) a connection inside an NE is not possible due to an NE limitation (e.g. HO drop–insert or bridge
& switch connections in 1661SMC):5 ) a physical connection has been impacted by an alarm and the path has been defined with
notAlarmedResourcesOnly attribute;
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 (NEconstraint);
In a protected path/trail, the routing algorithm has found both main and spare routes, but there areno main and spare idle CTPs in a protected connections with the same payload position and this isnot compliant with some NEs (all ADMs);
Suggestion for analyzing the problem:• 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 least1 common routing link, but after has discovered that it is not possible neither to use 2 different linkconnections in the common routing links, nor to create 2 protected connections at the boundary ofthese common routing links;
Suggestion for analyzing the problem:• 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 another route
d ) The spare route completely overlaps the main route (only path/trail allocation);
The routing algorithm has found only 1 possible route (main) between origin and destination; thereasons why the spare route has not been found can be that one or more of conditions describedin a ) occur;
Suggestion for analyzing the problem:• unprotect the path/trail and allocate in order to have more information on the main route, then
check if one or more of conditions described in a ) occur;
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
73
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
e ) Protecting this route wouldn’t improve the protection level (only path/trail add protection);
The routing algorithm has not found the spare route between origin and destination; the reasons canbe 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 reasonswhy the routes for the other legs have not been found can be one or more of conditions describedin 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 alreadyused in another path/trail or configured or in a wrong state;
Suggestion for analyzing the problem:• 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.
Suggestion for analyzing the problem:• 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 constrainton a link connection not compatible with one of two CTPs.
Suggestion for analyzing the problem:• 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;• ....
Suggestion for analyzing the problem:• restart the trsMngAgent using process control.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
74
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
10.3 Distributed Network Maps (DNM) application customization
10.3.1 Environment Variables
The following three environment variables are defined to identify the directory where the DNM Managersave or get the map image:
NXNL_MAPDBHOST : it specifies the host where the MAP DB area is placed.NXNL_MAPDBUSER : it specifies the owner username of the MAP DB area.NXNL_MAPDBAREA : 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 pulldownmenu. 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 containslanguage–dependant directories (default language is ”C”). In this directory is present the DNM resourcefile that is called mngmap, in which three variables are defined to permit to the Administrator to customizethe Mail Message sent when a map image is saved to users that can use it.
mailMsg : it contains the mail text that is sent to enabled usersmailCommand : 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.mailAllUser : 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 performedon a map image visible by all users.
To improve the customization flexibility of the mail message text, can be used four environment variablesthat are initialized with the proper values each time :
map_action : it is initialized with the action performed on the map image.map_name : it is initialized with the name of the map image involved in the operation.map_comment : it is initialized with the memo text related to the involved map image.map_subject : it is initialized with a string indicating the mail subject consistent with the
performed operation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
75
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 listedin 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 variablesin a normal Unix window, and then start manually the User Interface application. The two environmentvariables 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 thefollowing 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) thetrace group number.
2 ) Signal to the process to get the new trace level using:kill –17 <process_PID>
or using the appropriate pull–down 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/
N.B. Trace for children agents (i.e. pathImp) are placed in the directory of the parentprocess (in this case trsMngAgent).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
76
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
10.5 Consistency Download problem with transmux ports
Hereafter are listed two alignment procedure between 1354RM and 1353WX to recover from transmuxports 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 single140Mb port).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
77
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 theWX has a single 140Mb (34Mb) port:
1 ) perform a restore of the network (if WX MIB is corrupted, delete the WX persistency, if not andit 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 ) if the synchronization result of the EML is “misaligned” means that WX and RM havedifferent physical ports configuration, so it is necessary to check if in WX MIB themisaligned ports have some connections (this case cannot be handeled by RM):
1 ) start the Consistency Procedure (either global or on connections only). At the endRM should have deleted all not foreseen connections (also the ones supported by140Mb or 34 Mb not aligned ports);
2 ) start (again) the Consistency Procedure (either global or on ports only). At the endRM should have de–assigned all the not aligned ports. It is so possible to jump to nextpoint without deleting the WX persistency;
3 ) then the synchronisation of the EML will be misaligned (and the operator can be surethat 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 (NML–observed, with same FDNs as RM ones);– the 140Mb port is deleted;
b ) 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 contentare 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 anddecide if you can interrupt traffic or not. If you may not interrupt traffic, modify the RM tillall connections are aligned.
After this set Configure Enable on the WX node.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
78
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
10.5.2 RM with a single port and WX with 2Mb ports
This is a special case, because RM has the 140Mb (34Mb) port which is assigned and the WX not. The1641SX has a structured 140Mb (34Mb) port and it could have also connections on it. The RM cannotremove the NAP related to this 140Mb (34Mb) port because WX has not this NAP and RM cannot managea cross–connection on a TTP which is only seen by the WX. To align this situation it shoul be mademanually 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) portsare misaligned. It means that WX and RM have different physical ports configuration, so it isnecessary to check if in WX MIB the misaligned ports have some connections (this case cannotbe handeled by RM). In this case delete WX persistency, start WX again (on AU) and performa 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 contentare 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 anddecide if you can interrupt traffic or not. If you may not interrupt traffic, modify the RM tillall connections are aligned (this means in this case structure the transmux port andimplement the lost path).
After this set Configure Enable on the WX node.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
79
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11 1354RM CUSTOMIZATION
11.1 Environment variables changes
In the following paragraphs are described some customizations possible in RM. Hereafter is describedthe standard way to change and to take effect them, and it should be applied if some variables arechanged. For non–standard variables the change procedure is described directly in the relevantparagraph.
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 anothername in brackets, it means that it is a child process and its father shall be restarted to activate the variablevalue.
”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 start–up the ”Relevant Agent” (or its father).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
80
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.2 Users Services
11.2.1 Counters refresh rate on agent response
Meaningful for US configuration only.
– Relevant Process: browser– Variable Name: NXNL_COUNTERTIME (unset)
This variable defines the rate on which the browser has to refresh its item counters when the operator hasperformed 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
Meaningful for US configuration only.
– Relevant Process: browser– Variable Name: 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 numberof objects displayed in the browser.
11.3 EML–NML Alignment Process
Meaningful for IM configuration only.
– Relevant Process: emlObjAgent– Variable Name: NLhbp (180)
This variable enables the polling mechanism toward EMLs. Its value indicates the time–out (in secondsbetween two different polling activity.
N.B. If the environment variable is not set (or set with value 0) the EML data alignment polling activityis disabled.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
81
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.4 Inventory Processes
Meaningful for IM configuration only.
– Relevant Process: topBrwAgent– Variable Name: NXNL_INVPROCESS (1,2,100,2)
This variable configures the number of processes dedicated to inventory actions (e.g. path list, physicalconnection structure, ...) and must be set in nxnlenv_make file before to start the customize_patchprocedure.
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 twoprocesses 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.,
It’s clear that by default four lrf files are created in lrf directory; in the example eight lrf files are created inlrf 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 highlightof a path on the Map. This is possible also if they do not have the right to write on a map, because atemporary map is atomatically created (and deleted) by the system.
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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
82
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.6 Path/HO–Trail Management
11.6.1 Path/Trail allocation algorithm
Meaningful for IM configuration only.
– Relevant Process: pathAll (trsMngAgent)– Variable Name: K2 (2)
K34 (1)K140 (1)
N.B. 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 followingformula :
Cost = C ( 1 + K / F )
Where :
C : cost of the routing link without taking into account any usage factorF : number of free link–connections in the routing linkK : 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.
Meaningful for IM configuration only.
– Relevant Process: pathAll (trsMngAgent)– Variable Name: SAME_RES_TYPE (20)
DIFF_RES_TYPE (40)
By means of these variables is reduced the cost of routing link already allocated by the relevant broadcastpath, in order to force the allocation algorithm to reuse as much as possible the resources. The costcalculated in the previous paragraph is multiplied by SAME_RES_TYPE/100 (default 20%) if the pathalready 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%).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
83
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.6.3 Using Virtual Nodes during Path Allocation Phase
Meaningful for IM configuration only.
– Relevant Process: pathAll (trsMngAgent)– 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 PathAllocation phase. If the environment variable DISABLEVIRTUALCTPTOCTP is defined and has a valuedifferent by 0 the Virtual Nodes are taken into account during the Implementation phase only if the pathterminates on them (no pass–trough can be defined on virtual nodes). If the variable is not defined ordefined with value equal to 0 all virtual nodes are taken into account as normal nodes during the allocationphase.
N.B. When there is interworking RM–NN it is necessary setting (see 12.4 paragraph):export DISABLEVIRTUALCTPTOCTP=1
11.6.4 Configurable switch in Drop&Continue
Meaningful for IM configuration only.
– Relevant Process: pathAll (trsMngAgent)– Variable Name: DROPCONTSWITCHCONF (0)
By means of this variable it is possible to set the nominal position of the switches in Drop&Continueconnections 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 thepath, 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
Meaningful for IM configuration only.
– Relevant Process: pathImp (trsMngAgent)– Variable Name: 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 CTP–HO CAP creation/deletionwhich 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.
N.B. Normally NLtimeoutReq is zero so the timeout is fixed and equal to NLtimeoutBase.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
84
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.6.6 Configuring consistency flow control
Meaningful for IM configuration only.
– Relevant Process: consChkAge– Variable Name: IMP_FLOWCONTROL_MAX_OUTSTANDING (15)
By means of this variable you can set the maximum number of create/delete/update_squelchingmessages concurrently sent to NEs during consistency download. If the number of sent messages equalsthe threshold specified by this variable, the consistency process will wait until a message is answeredbefore sending another one.
N.B. This simple mechanism of flow control overcomes internal message queues overflow in OSes(like WX) which don’t use HO OpenView CI built–in flow control feature.
11.7 Alarm management
11.7.1 Flooding protection mechanism
Meaningful for IM configuration only.
– Relevant Process: emlAlrMng– Variable Name: 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 protectionmechanism.
When RM receives more than HP_almthreshold high priority alarms in HP_TOthreshold time (sec) it stopsto analyze them (no propagation is done) and emits a “High Priority Alarm Flooding” alarm for the relevantEML. It doesn’t analyze alarms until a HP_TOthreshold period terminates with an alarm rate lower thanHP_almthreshold. The same mechanism is implemented for low priority alarms with the “Low PriorityAlarm Flooding” issuing.
The alarm synchronization isn’t automatically performed but it’s up to the operator to require it.
11.7.2 Alarm clearing hysteresis period
Meaningful for IM configuration only.
– Relevant Process: pathAlrMng (emlAlrMng)– Variable Name: NLdeltatime (5)
This variable set a hysteresis period on clear–emission time of an alarm. It means that when an alarm iscleared the RM process wait NLdeltatime seconds before starting the propagation phase, if the samealarm raise up again (same object with same probable cause) in this period the RM doesn’t propagateneither the clear nor the new raise of the alarm, leaving the previous alarms as they are.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
85
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.8 Nap uploading timer
Meaningful for IM configuration only.
– Relevant Process: objImpCnf (topMngAgent_csa)– Variable Name: NLnaptim (1200)
This variable defines the default time–out value (in seconds) for the NAP upload of a single node. If a nodecontains a large number of PDH ports (e.g. more than 300) it is suggested to set a bigger time–out value.
11.9 SNCP switch timer
Meaningful for IM configuration only.
– Relevant Process: pathImp (trsMngAgent)tsdFepCfg
– Variable Name: NL_TIMER_WATCHSW (600)NL_TIMER_MNGSW (60)
The NL_TIMER_WATCHSW variable defines the watching period lenght (in seconds) of switch state, thewatching period begin from synchronize switch command. During this period all switch events aremanaged.
The NL_TIMER_MNGSW variable defines the time–out value (in seconds) for the execution of a manageSNCP 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 pop–up menu) use theenvironment 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 thecommand described in the variable.Using the default command the print–outs have landscape orientation and each row contains up to 180characters.
When this variable is changed, to take it effective it is required to exit from CDE workspace and then loginagain.
N.B. This commands is used only for ASCII print–out, not for Hardcopy pop–up menu commands.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
86
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.11 Unused Virtual PDH ports garbage collection
Meaningful for IM configuration only.
– Relevant Process: trsMngAgent– Variable Name: 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 thetrsMngAgent startup. This feature can be enabled or disabled by means of this environment variable. Ifthe variable is defined the check is performed, if it is not defined the check is skipped.
11.12 Setting Linked Get Replies Maximum Number
Meaningful for IM configuration only.
– 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 amountof linked replies (e.g. not filtered full scope get operation). In any case is provided the possibility to definea 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 inthe 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 isindicated the number 0 no limit is set. If during a get operation the reply limit is reached a warning messageis displayed to the operator.
N.B. The string described in this paragraph as <xxx> is the suffix of the agent’s instances and mustnot be changed.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
87
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.13 NetView Symbol’s 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: –*–helvetica–medium–r–*–140–**size20Font: –*–helvetica–medium–r–*–120–**size10Font: –*–helvetica–medium–r–*–100–**smallFont: –*–helvetica–medium–r–*–80–*
They are automatically referenced by HP–OVw depending on the number of symbols to be displayed ina submap.If the symbol labels are too small the System Administrator could change the size of this fonts (i.e. the smallfont could be changed from ”–*–helvetica–medium–r–*–80–*” into ”–*–helvetica–medium–r–*–120–*”and then restart NetView application (close all the HP–OVw windows and start again the application).In the following an alternative font set with respect to the delivered one is listed:
*size30Font: –*–helvetica–medium–r–*–140–**size20Font: –*–helvetica–medium–r–*–120–**size10Font: –*–helvetica–medium–r–*–120–**smallFont: –*–helvetica–medium–r–*–120–*
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
88
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.14 Performance Monitoring Customization
11.14.1 PM Data Collection Customization
11.14.1.1 EML’s configuration file
Meaningful for IM configuration only.
– Relevant Process: pmCollMng (pmMng)
It is on User responsibility to specify in a configuration file ”eml_PM_nodes” the host machines where theEML–IM 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 theoperator.
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>: it is the EML identifier .<host1>: it is the logical host name where EML–IM application runs .<host2>: 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 sub–directory where EML provides files for 15 minutes
granularity.<dir 24H>: it is the name of the sub–directory 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 time–out
Meaningful for IM configuration only.
– Relevant Process: pmCollMng (pmMng)
To customize the time–out between two different file collection operations the following options can beinserted in the process starting command in the file /usr/snml/bin/pmCollMng :
– timeout15m <n>: it allows to customize the time–out value representing the collection frequency ofthe 15 minutes transfer files from the EMLs to RM. The value <n> must be expressed in minutes andit must be included between 15 (i.e. a quarter) and 225 (i.e. 3 hours and 45 minutes). If the optionis not specified the default value is 15 minutes;
– timeoutday <n>: it allows to customize the time–out value representing the collection frequency ofthe 24 hours transfer files from the EMLs to RM. The collection activity has anyway a built–in time–outof 4 hours after midnight to collect data file relevant for the last elapsed day. The value <n> must beexpressed 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);
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
89
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.14.1.3 TSD data file collection time–out
Meaningful for IM configuration only.
– Relevant Process: tsdFepColl.exe
T–FEP/COLL acts on a periodic basis: the collection frequency could be provisioned from a user by meansof 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 fromEML 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 enviornmentvariable PM_DATA_WORK; at the moment a COLL_CFG.make file is present as templete. It’s in chargeof 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:
– G 24: freqency one hour
– G 15: frequency 15 minutes
11.14.1.4 SENIM Maximum number of data collection processes
Meaningful for IM configuration only.
– Relevant Process: lpmCollMng
To define the maximum number of parallel collection activity that can be executed the following option canbe 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 inparallel 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
Meaningful for IM configuration only.
– Relevant Process: tsdFepColl.exe
To define the maximum number of parallel collection activity that can be executed the following variablecould be used NLcollMaxScript. If it is not specified the default value is 3
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
90
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.14.2 PM Data Archive Customization
11.14.2.1 Create ORACLE User for Archive purpose
To allow the PM data archive function a new ORACLE user environment is required. The followingprocedure 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 (itmust 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 iscalculated using the variables described in 11.14.2.2 paragraph.
11.14.2.2 PM Data Archive Period Granularity
Meaningful for IM configuration only.
– 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 firstone indicates the number of days (by default a week) that has to be elapsed before enable the archiveactivity on 15 min. The latter variable indicates the number of months (by default a month) that has to beelapsed 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 elapsedperiod. Once the archive activity is executed a new period shall be elapsed to enable again the archiveactivity.
N.B. When the archive request is issued by the operator, if more than one archive periods areelapsed (difference between current time and end archive period is bigger that the durationindicated by these variables), all data relevant for these elapsed archive periods will be archivedin one shot.
When these variables are changed, to take them effective, it is required to exit from CDE workspace andthen login again.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
91
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.14.2.3 Delete prevention of Archived PM Data in the RM DB
Meaningful for IM configuration only.
– 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 firstone indicates the number of days (by default a week) in which is granted that archived data relevant for15 min will not be removed from RM DB. The latter variable indicates the number of months (by defaulta 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 andthen login again.
11.14.3 PM Scheduled Report
Meaningful for IM configuration only.
– Relevant Process: pmMng– Variable Name: 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 valueused in order to grant that when a report has to be generated, the meaningful counters have been alreadycollected and analyzed (i.e. stored in the DB). They allow to synchronize the collect & analysis and thereport generation activities.
e.g. PM_DELAY_MIN= 30 – the fifteen minutes report of the period 25/08/2000–23.00 to 23.15 will begenerated 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
Meaningful for IM configuration only.
– Relevant Process: pmMng– Variable Name: NLschedule15 (600)
NLschedule24 (600)
These variables allow to set the time–out 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 time–out for 15 minmeasures elapses each minute).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
92
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
11.15 How to change the default ASAP
In 1354RM a default ASAP for paths,trails and physical connections is created at the installation time andit is identified by the value ’default ASAP’ as userLabel (its asapId is always equal to 0).
An off–line 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 RM–DB);
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 errormessage
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 nnmluser:
$ 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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
93
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 commandhas 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 thenew 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 QnnAgentManagement.
12.2 RM user definition for Qnn Zoom–In
The zoom–in operation from 1354NN to RM can be performed with three different profiles according tothe definitions given in the Qnn interface. The defined profiles are:
a ) NN administrator;b ) NN user;c ) 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 zoom–in from NN cannot work and it is notdisplayed any additional message.
12.2.1 RM users definition script
After plug–in installation, in order to create the four gateway users (qnnmng, qnnagent, qnnview andqnnpmop) to zoom–in from NN the following command has to be executed (using the ”root” Unixusername) on all the RM workstations:
– # cd /usr/snml/etc# ./AddQnnUser
The command will define the users with the following characteristics:
RM user : Profile : NAD qnnmng : OSadmin : 1 qnnagent : PathBuilder : 301 qnnviewer : LookOnly : 40 qnnpmop : PathBuilder : 301 (to permit ftp operation from NN)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
94
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
12.3 RM Zoom–In from NN using RM USM
The 1354RM zoom–in execute from 1354NN is usually performed running the required application on1354RM Master system. If there are many 1354NN operators, this activity can overload the 1354RMMaster system.
In order to reduce the amount of activities on RM Master it is possible to specify which 1354RM USM ofthe same 1354RM cluster have to execute the zoom–in application instead of the 1354RM Master.
The “/usr/snml/conf/qnnDispMapping” file contains the relationship between the 1354NN X Displayrequire the zoom–in and the 1354RM USM that have to execute the application. To request this featureadd one line for each display that have to be served by 1354RM USM in the “qnnDispMapping” with thefollowing 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 theRM USM of the same 1354RM cluster of the 1354RM Master.
N.B. In case of 1354RM USM failure, the 1354RM zoom–in will fail also.
N.B. If the 1354RM USM is removed from the network also the related line(s) have to beremoved from “/usr/snml/conf/qnnDispMapping”.
Example of “/usr/snml/conf/qnnDispMapping”:nnmst1:0.0 rmusm1nnxt01:0.0 rmusm2nnmst1:1.0 rmusm3
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
95
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 NEsrepresenting other RM domains. It means that it doesn’t manage properly topologies with directconnections between two Virtual NEs (RM domains).
Physical ConnectionSubnetwork ConnectionVirtual NE
CTPA’ CTPB’
CTPB’’CTPA’’
1354RM
Network Domain n
Figure 3. Supported topology
Physical ConnectionSubnetwork ConnectionVirtual NE
CTPA’ CTPB’
CTPB’’CTPA’’
1354RM
Network Domain n
Figure 4. Not supported topology
A Virtual NE can represent more than one RM domain. It can represent a whole RM domain independentlyfrom 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 pass–trough on virtualnode ( see Use of Virtual Nodes during Path Allocation Phase ).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
96
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
12.5 Limitation of Qnn path provisioning lead by RM
In the case of a SNCP protection (QosProtection=full or partial protection on the 1354NN ) asked byQnnAgent to the RM , if the RM is not able even to perform a partial protection the allocation fails (whilethe 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 theredo operation from the 1354NN (only in the case of a path not corresponding ,on the Qnn, to a switchablesubnetwork connection).
12.6 Assigning Network Resources to 1354NN
Some restrictions apply on the Resource Assignment procedure to 1354NN:
a ) in order to assign an MS–Trail it is necessary to have already assigned at least one HO–LC;b ) in order to assign an HO–Trail it is necessary to have already assigned at least one LO–LC;c ) 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 followingorder is not respected by the operator the result could be unpredictable):
a ) HO–LCs;b ) MS–Trail;c ) LO–LCs;d ) HO–Trail;e ) NAP’s;f ) Path.
For deassigning resources from 1354NN the following applies:
a ) in order to deassign an MS–Trail it is necessary to have already deassigned all HO–LCs;b ) in order to deassign an HO–Trail it is necessary to have already deassigned all LO–LCs.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
97
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
13 EML SIMULATION
The 1354RM can handle simulated EML domains and mixed networks with real and simulated EMLs.
In particular 1354RM can work in a stand–alone configuration either populating RM DB with EML data onlyor 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 doesn’t 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 TSD–IM 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 startit again. At the end execute the manual start–up of the FEP agents.
– for SEN–IM Network: execute in a ”root” UNIX user window the command RegisterAllEmlSim(present in the /usr/snml/bin directory).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
98
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
13.1.1 Available Simulated data files
The directory /usr/snml/databases/dbsnml/init contains a set of TSD–IM Simulated data files and a setof SEN–IM data files which can be used for the generation. In addition, an offline tool can be used to createthe 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 ) The system asks for:
EML domain Enter the EML domain id and press Return.
EML userLabel Enter the EML userLabel and press Return.
SHversion press Return.
e ) The system asks for:
neType. Enter the number correspondent to the desired equipment type and pressReturn.
NEuserlabel Enter the NE userLabel and press Return.
sitename Enter the NE sitename and press Return.
f ) Per each slot the following mask is presented:
SLOT n. ... List of boards
1 Board name 1
2 Board name 2
n Board name n
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 itexecutable.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
99
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 domaineml domain name = EML Domain User Labelim Type = tsdIm or senImsenim version supported (if imType=senIm) = Identifies the SEN–IM version that should besupported 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 &ne9600luHne name = Network Element User Labeltsd version (if imType=tsdIm) = It specifies the tsd version used (default=5.5)site name = Location of NEconfiguration type = For all NE types, but 1651SM & 1661SMC, it assumes the same value ofne type substituting ”ne” with ”cnf” (e.g. ne1641sm has configuration type cnf1641sm). For the1651SM & 1661SMC it specifies if the NE is Full Matrix or Null Matrix (cnf1651smNull orcnf1651smFull / cnf1661smCNull or cnf1661smCFull).ne version = It specifies the NE version used to check NE connectivity constraints (if no versionis 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).
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 asequential 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 theNE are contained in the NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
100
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
13.2 Real Network Simulation
It is possible to transfer data of a real ”live” network on a stand–alone RM configuration in order to workwith 1354RM product on this data.
To reach this goal it is necessary to perform a RM backup of the real network and than restore it on theRM stand–alone. Finally on the RM stand–alone workstation the EMLs are to be registered as ”Simulated”:
– for TSD–IM 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 startit again. At the end execute the manual start–up of the FEP agents.
– for SEN–IM Network: execute in a ”root” UNIX user window the command RegisterAllEmlSim(present in the /usr/snml/bin directory).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
101
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 theEMLs.
It is supposed that the operator has already changed the userLabel on the EML.
Please take care of the differences between QB3* (SEN–IM) and QB3 (TSD–IM) NEs.
14.1 NEs with SEN–IM 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 Portsis admitted. So, it is preferable to check all the attribute value changes sent during this alignmentphase. Be sure all the EMLs are aligned (the attribute emlDomainAlignement has to be equal to nor-mal).
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).
14.2 NEs with TSD–IM 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).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
102
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
14.3 Aligning the userLabel of PMNEs and PMTPs
a ) By using the process control, stop the pmMng agent.
b ) By using snml, execute the following SQL procedure
$ORACLE_HOME/bin/sqlplus $NXNL_DATABASESQL> @/usr/snml/databases/dbsnml/admin/conv/alignPmUserLabel
The procedure requires the userLabel of the migrated NE (with TSD–IM 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
It is required the Identifier of the elementary topology.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
103
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 profileof the user snml;
b ) MIG_TAR: it represent a temporary directory where the tar files are stored. This directory must becreated 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 /migchmod 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 com-mand 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/im-port phase are stored. This directory has to be created before the execution of the migration proce-dure. For example, if you choose the directory /mig_backup as mig_backup directory, you must exe-cute the following UNIX commands (by root):
#mkdir /tmp/mig_backupMIG_BACKUP=”/tmp/mig_backup”#export MIG_BACKUP
Every migration procedure checks if these variables are correctly set. If a check fails, an error messageis displayed and the executions stops.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
104
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
15.1 1354RM R2.4 (NR3.1) to 1354RM R5.2.x Migration Procedure
Pre–conditions: 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 consisten-cy audit/download).
b ) If you want to export also OVW–MAPs, save by DNM the maps to be converted by DNM (select menuFile–>Distribute maps–>Store map images).
c ) Perform a system full backup.
d ) Stop 1354RM system if necessary (the database must be on instead), log in as ”root” users and chan-ge 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 aschema 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 mig–backup and mig_tar directories) where the datamigration 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 mig–backup directory to the MIG_BACKUP environment variable, and thename of the mig_tar directory to the MIG_TAR environment variable.
For example, if the mig–backup directory is /tmp/mig_backup and /mig is the mig–tar directory, thefollowing command have to be executed:
# 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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
105
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
h ) Change your current directory to the ”conversion” directory:
# cd $DB_ROOT/admin/conv
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 mig–backup directory (environment variable $MIG_BACKUP)the mig–tar 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 canpress <Ctrl–C> and set again the uncorrect environment variable.
The procedure creates (if necessary) the directory $MIG_TAR where data to be exported will besaved.
The directory $MIG_BACKUP is saved and the file databaseRM24.tar is created in the $MIG_TARdirectory. This tar file contains all data of the ORACLE–database of RM2.4.
Then the procedure asks the operator if the OVW–MAPs are to be exported. The following messageappears
Do you want to export MAP–DB ? [y/n – default y]
If the operator press either <N> or <n> (followed by <Enter>), the directory $NXNL_MAPDBAREAis 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.xmust be installed over the RM2.4 and no extra WS are available. The following message appears
Do you want to save EXPORT–files on tape ? [y/n – default y]
If the operator press either <N> or <n> (followed by <Enter>), the directory $MIG_TAR is not savedon tape.
In this case, the files databaseRM24.tar and mapdbRM24.tar in the $MIG_TAR directory can besaved on an extra WS using the ftp command. The option bin of the ftp must be used to copy the twofiles.
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 expDbR-m.log.save.
If you previously selected the copy of tar files on tape, the following message appears:
Do you want to save EXPORT–files on tape again ? [y/n – default y]
If the operator press either <N> or <n> (followed by <Enter>), the directory $MIG_TAR is not moresaved on tape, otherwise another copy of tar files are saved on a new tape (please remember to chan-ge the tape after every operation).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
106
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
j ) Install 1354RM R5.2.x delivery (see 3.1), creating a new database (variable NEW_DBSNML mustbe 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 installationDB_ROOT is the directory name of the new database):
# cd $DB_ROOT/admin/conv
m ) Be sure the system is ”off”, otherwise shutdown it using the Process control
n ) Be sure the database is running, otherwise start–up 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 mig–backup directory (environment variable $MIG_BACKUP)the mig–tar 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 operatorcan press <Ctrl–C> and set again the uncorrect environment variable.
The procedure creates (if necessary) the directory $MIG_TAR where data to be imported will besaved.
First, the operator can choose if data to be imported have been stored on tape. The following mes-sage appears
Do you want to restore IMPORT–files from tape ? [y/n – default y]
If the operator press either <N> or <n> (followed by <Enter>), no files are restored from tape (it issupposed the files databaseRM24.tar and mapdbRM24.tar – if the OVW–maps have to be imported– have been previously copied in the /mig directory by an extra ws using the ftp command with thebin option set), otherwise the tar files are restored from tape.
Then, the operator can choose if the OVW–MAPs must be imported too. In fact, the following com-mand appears
Do you want to restore MAP–DB ? [y/n – default y]
If the operator press either <N> or <n> (followed by <Enter>), the OVW–maps will not be imported.In this case, the OVW–MAPs will be rebuilt after the migration of the ORACLE–database 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 popu-lated with data stored in R2.4 one.
Every time the procedure is executed, the previous log file is automatically saved as impDbR-m.log.save.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
107
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
N.B. The import procedure creates a big ORACLE tablespace named large_rbs_tbs. Thistablespace is dropped at the end of the procedure. However, if the import procedure failsbecause of an ORACLE error on large_rbs_tbs tablespace (or large_rbs rollback seg-ment), 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.
p ) Execute the full backup
N.B. Moreover, PDL files produced in RM2.4 couldn’t be properly executed with RM2.3(because of the port–userLabel change between SH1.2 and SH3).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
108
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
15.2 Virtual EML registration on Communication Infrastructure (CI)
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 toCMISE 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 (thechild of ’MULTI SNML–IM’, labeled ’SNML–IM’). 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’ at-tribute.Note: very often, the only virtual EML is the one with emlDomainId = 0.
Prerequisite 2: you have to know UNIX root (superuser) password.
15.2.2 Procedure steps
a ) Login as ’snml ’ user, then change current directory to $NXNL_PRD/bin with the commandcd $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 nAnswer ’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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
109
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
15.3 Migration Procedure of NEs
In the following, the steps to be executed when an NEs is changed are described. These steps mustbe 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).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
110
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
15.3.1 NE migration between QB3* and QB3 interface
15.3.1.1 Overview
In the following, a brief description of the procedure to migrate one NE between QB3* and QB3 interfaceis 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 toclear 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 caseof DXC, this file is computed by RM. Instead, for ADMs, a procedure on SH will be available to dothis. 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 FEP–PN 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). Thisprocedure changes the userLabel of the NE (if required) and all the Ports accordingly to the TSD nam-ing 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 su-cessfully terminated (emlDomainAlignment=normal), the equipment is well converted in TSD–IM,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:
1 ) MSCtps, HO–CTPs and NAPs have to be aligned to the fdnMapper of the physical port;
2 ) CAPs are aligned when the connection CTP–CAP is aligned
3 ) LO–CTPs are aligned when their CAP is aligned.
j ) 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 objectis equal to normal). During the execution of the procedure, the NE to be migrated is in download disablemode. The procedure changes the status for you. Alarm activity is suspended (this is due to the fact allthe network objects belonging to the NE are not aligned inside the RM database).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
111
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 directory’s name where you want to save the migration.log file.
b ) MIG_BACKUP: it contains the directory’s 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 intoMIG_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 tomigrate 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, negroupversions). It is also checked all the connection are supported by the target version of TSD–IM..
3 ) TSD Convert : this function performs the migration of Ne in new neGroup. During this phasechecks previously described are executed again..
The new neGroup Before (supporting the TSD–IM interface) must also be created in RM database beforeexecuting the last two steps..
When you start the Prepare DXC Ports option, two options can be selected
1 ) Continue: to insert the SEN–IM 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 youhave set previously. The file have following format:
BEGIN FDN_MAPPING_FILE<neUserLabel><oldSdhPortIdId> <newSdhPortIdId>END FDN_MAPPING_FILE
file name is the userlabel of DXC.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
112
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
Check data option is composed by four options:
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 havebeen implemented. in this case, the path userLabel and the nodenames when these cross–con-nections 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 belongingto 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:
a ) userLabel : SEN–IM userlabel of the NE to be migrated
b ) neGroup : neGroupId (with TSD–IM interface) where the NE is to be migrated
c ) neId : ID of the Ne int the new SH (with TSD–IM interface)
d ) TSD user label : new user label of Ne (optional)., If not specified by the operator, it is as-sumed the NE doesn’t change its userLabel.
4 ) Return to main menu: to go back to the main menu.
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 possibleto read it by using a text editor. Remember that the log file is $MIG_LOG/migration.log.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
113
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 sameuserlabe was found
7 ) Error in number of Node retrieved ! : this error is generated when two or more Node with thesame 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 theEx: prepareDXCPorts phase.
10 ) Error in number of Tp retrieved ! : a protected multi–point connection was found but its TP listis corrupted
11 ) Found switch connections in topology ! : a protected multi–point connection was found.
12 ) Ne not found in the database ! : The Ne with the specified userlabel is not retrieved in RM data-base
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 (TSD–IM) is not retrieved in RM DB (itis to be created off–line)
15 ) neGroup is not TSD–IM ! : the new neGroup involved in migration supports SEN–IM 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 TSD–IM 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.
21 ) Error in clear alarm ! : the disable alarm correlate to the Ne failed.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
114
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
15.3.1.3 How to align the Q3disableAlarms attributes of paths/trails
The neMigration procedure changes all the informations in the RM–database in order to allow the execu-tion of the download activity. During this phase, the network element is set how all the object were directlycreated with the TSD–IM interface. So, the disabledAlarms attributes of NAPs, CAPs, CTPs boundary andPDH physical ports are modified if the connections are implemented on them. In other words, it is neces-sary that the proper alarms are enabled on the physical end points of the paths/trails wich are implementedon them This task is executed by the RM when the TSD–IM interface is used.
However, the neMigration procedure is not able to compute the proper Q3disabledAlarms on the entirepaths/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 amigration 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 (assnml)
$ORACLE_HOME/bin/sqlplus $NXNL_DATABASESQL> 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 thepackage has to be loaded with the SQL COMMANDS:
SQL> @/usr/snml/databases/dbsnml/admin/conv/alignQ3AlarmsPck_specSQL> @/usr/snml/databases/dbsnml/admin/conv/alignQ3AlarmsPck_body
Pratically, the PL/SQL package must be loaded just either the first time this procedure is executedor when the database is created again.
c ) execute the SQL command
SQL> @/usr/snml/databases/dbsnml/admin/conv/alignQ3Alarms
The procedure requires the userLabel of the migrated NE (with TSD–IM interface).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
115
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
15.3.2 neGroup modification
In order to modify the emlDomain of NEs with QB3* and Qb3 interface, the utility neTranslation must beexecuted.
This procedure allows you to change the emlDomain (neGroup in QB3 terminology) in the RM–DB. It issupposed that during the neGroup modification activity:
a ) the SEN–IM/TSD–IM object Identifiers don’t change;
b ) the EML interface doesn’t 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 directory’s name where you want to save the migration.log file.
b ) MIG_BACKUP: it contains the directory’s 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, negroupversions).
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 ) Return to main menu : to go back to the main menu.
When you start the NeTranslation , two options can be selected
1 ) Continue: to execute the translation of the emlDomain;
2 ) Return to main menu : to go back to the main menu.
If you choose the option 1), you must enter the name of the file containing the data of the NEs to be trans-lated (complete pathname, if the directory of the file is not the directory when the utility is executed).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
116
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
The format of the file is the following:EMLIM_MOVE_FILE<oldNeFdnMapper1> <newNeFdnMapper1><oldNeFdnMapper2> <newNeFdnMapper2>........<oldNeFdnMapperN> <newNeFdnMapperN>END_EMLIM_MOVE_FILE
The format of the neFdnMapper is dependent on the interface (SEN–IM or TSD–IM) 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 possibleto 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 differentinterfaces (TSD–IM versus SEN–IM 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 num-ber 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 RM–DB
12 ) neGroup not found in the database ! : the neGroup involved in the migration is not present inDB
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
117
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 File–>Distribute maps–>Get/List Map Images
f ) Save the map selecting the DNM command File–>Distribute Maps–>Store Map Image
g ) Execute the full backup.
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 thentwDomId 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:
# cd $DB_ROOT/admin/conv# MapChangeNtwDom <map–name> <new_NtwDomId>
where <map–name> 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.
N.B. NOTE: The old map is copied as $NXNL_MAPDBAREA/<map–name>.db.OLD. You can re-cover it, in case of errors, or delete it otherwise, to save disk space.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
118
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
15.5 Virtual EML registration on Communication Infrastructure (CI)
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 toCMISE 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 (thechild of ’MULTI SNML–IM’, labeled ’SNML–IM’). 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’ at-tribute.Note: very often, the only virtual EML is the one with emlDomainId = 0.
Prerequisite 2: you have to know UNIX root (superuser) password.
15.5.2 Procedure steps
a ) Login as ’snml ’ user, then change current directory to $NXNL_PRD/bin with the commandcd $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 nAnswer ’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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
119
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
16 UPDATE OF MSSPRING INFOS (MS–SPRING TAKEOVER)
In the following it’s described the procedure which is able to modify the MS_SPRING–related informationcontained in the node objects that belong to an MS–SPRING ring (=et).This is required when 1354RM takes over an existing network previously administered by another OS withMS–SPRING rings containing paths/trails that you want to preserve without traffic hits. In this case, youhave to provide manually the informations (values of NODE.NODEINET and NODE.SEQNUMINETdatabase columns) that 1354RM automatically downloads to NEs (at ring implementation time); this infosare used in squelching tables management (see below). If you don’t provide this infos, RM will downloadthe default ones, so overwriting the correct ones and making squelching tables not consistent. The targetis to put in 1354RM database the same values that are stored in the NEs; this way, theimplementation–time 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 youdon’t know them, a way to obtain them using Craft Terminal equipment is suggested in the following.
Nodes in a MS–SPRING are numbered clockwise starting from zero and ending in <number of nodes inMS–SPRING> –1). This is the SEQNUMINET of NODE table information in RM terminology, and thenodePosition 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 nodehas 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 attributeof mSSPRingProtection MOC in SENIM terminology.This ”labeling number” is mainly used to identify nodes in squelching tables. If the values don’t match, thewhole MS–SPRING protection mechanism is compromised.
Every Network Elements knows this informations for all nodes, i.e. it has hardware registers containingall the (SEQNUMINET, NODEINET) mapping for every node.
To retrieve this information from an existing network a possible way is to use a Craft Terminal connectedto Network Elements. Please refer to document ”1664 SMECT V2.0” : ”SYNCHRONOUS MULTIPLEXER 1664 SM RELEASE2.0 EQUIPMENT CRAFT TERMINAL” (and subsequent versions). See ”MS–SPRING CONFIGURATION” chapter, ”MS–SPRING 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”.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
120
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
16.2 Procedure steps
a ) Perform a system full backup.
b ) Stop 1354RM system if necessary (but not the database, which has to be on) using Process Controlfacility.
c ) login as ”snml” user.
d ) Enter the MS–SPRING 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 operatorcan enter ”n” (feel free to press <Ctrl–C> if you like) , (re)set the uncorrect environment variable, andrestarts ”./updMsspring”. No operation on database is performed until you enter ”y”.
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 asupdMsspring.log.old.
e ) Select the option ”Dump all userlabels of MS–SPRING”.The procedure will create a file (whose name you can find on the screen) containing all userlabelsof MS–SPRING rings found into database. The format is simply the userlabels enclosed in doublequotes, one per line.Delete the lines containing the userlabels of the rings(=et) you don’t 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 MS–SPRING related informations of the nodes of the rings youspecified 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=0If you want to make NODEINET=2 and SEQNUMINET=1, change toNODE WITH USERLABEL=”node 3 of Northern Seattle MS ring”: NODEINET=2 SEQNUMINET=1In other words, think this file as a ”form”.Don’t change the file any other way, e.g. by deleting/adding lines. If you modify anything different fromthe 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
121
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
i ) Now the datas are inserted in RM database. When you will implement the modified MS–SPRINGrings(=ets), the datas you have just inserted will be used by RM system. Mainly, they will be forwardedto 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=0NODE WITH USERLABEL ”nodeA2”: NODEINET=5 SEQNUMINET=1ET WITH USERLABEL ”ringB”:NODE WITH USERLABEL ”nodeB1”: NODEINET=6 SEQNUMINET=1NODE WITH USERLABEL ”nodeB2”: NODEINET=14 SEQNUMINET=0
16.4 Loading of a prebuilt nodedata file
You have to execute all procedure steps until step f ) (included), set the environment variableNXNL_EXTERNAL_NODEDATA to the name of the prebuilt nodedata file, then perform the same actionsas 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 youhave made some syntax error. Note that the order of rows doesn’t matter, as far as all ’NODE ...” rowsregarding nodes of the same ring are grouped together under the ’ET ..” row of the ring that they belongto. Also note that white spaces (blanks) of userlabels are meaningful, i.e. ”ringNumber1” is not the sameas ”ringNumber1 ” (note the ending blank).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
122
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
123
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 1354RMPMC (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_DIRdirectory 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 procedureinstall_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 1330ASprocesses will be installed on RM workstation, US means that on RM workstation only AS user interfaceis 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 1330ASprocesses will be configured to run on RM workstation, US means that on RM workstation only AS userinterface is configured to run.
To execute it the US processes of AS have to be stopped manually. The procedure executes the followingsteps:
a ) it stops the IM AS agents;b ) it deregistrates AS agents;c ) it removes the AS installation;d ) it removes the /usr/A1330 link.
After the running of the procedure 1354RM PMC do not handle any more the AS agents.
N.B. It is necessary to verify the contents of the ”im_host_conf” file, since it is generated by the”deinstall_A1330” procedure.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
124
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
A.3 A1330 AS customization
1330AS is provided with a default US customization in order to see only alarms relevant in 1354RMenvironment and to distinguish them by their typology. All the AS1330 users have the possibility to changethe default customizations (HMI Layout, Counter Customizations, Colors, etc.) and so to work in a owncustomized AS environment. These customizations are not saved at the end of the work session in orderto 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 changesare effective for all the users.
When e new configuration is made effective by running us_config_A1330 all the changes made by snmlare lost and is restored the initial default customizations.
A.3.1 Swedish language
In order to let AS–USM Components manage alarms containing swedish chars in the right way do thefollowing 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 AS–USM Components will be able to manage swedish chars using roman8fonts.
In order to roll back the configuration to the default one (AS–USM displaying alarms in english) performthe following commands as nnml user:
$ cp /usr/snml/conf/AS_graphicResources_english /usr/snml/conf/AS_graphicResources
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
125
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
APPENDIX B INTEGRATION OF 1354RM WITH GENERIC OS–OS INTERFACE
Meaningful for IM configuration only
B.1 Generic OS–OS Interface Subsysystem
Generic OS–OS Interface is a product that exports, to external applications, alarm informations managedby AS1330 Subsystem.
In the following GENOS stays for Generic OS–OS Interface.
Depending on AS1330 subsystem version there is a compatible Generic OS–OS Interface version whichis able to communicate with it (see Release Notes of OS–OS Interface).
B.2 Generic OS–OS 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 with1354RM.<ALL | SNMP | TCP/IP> specifies the type of protocol the Generic OS–OS Interface Processes useto export alarm informations:
SNMP : SNMP Protocol is usedTCP/IP : TCP/IP Protocol is usedALL : 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 theauthentication and informations on GENOS Processes configuration. To execute it launch the script/usr/1353sh/tools/genos/user_config.tcl.
With the GENOS installation are provided also graphical tools (dependingly on Protocol type) that simulateexternal OS communicating with Generic OS–OS processes to export alarm informations. To executethese 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 ismade under the area /usr/1353sh/genos, this limitation is due to specific conditions of GENOSproduct. 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 1354RM–IM.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
126
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
B.3 Generic OS–OS Interface deinstallation
Execute the following commands to launch the deinstallation script:
# su – root# /usr/snml/etc/deinstall_genos <full_pathname_tar_file_deinstallation_kit>
The procedure, without using any configuration file, determines the installed product version and removesthe installation area, and the registrations inside the 1354RM PMC.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
127
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 relatedto the users and the system;
secim process have to be running only on 1354RM–IM.
– lss process which is a kind of gate for applications who are interested on user Security profile. Thereis one lss process for each workstation/server belonging to the 1354RM system (1 for eachpresentation 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 SecurityManagement within AS (Alarm Survelliance). This means that each 1354RM operator using AS is ableto 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 integratedin SMF, in order to get informations related to new users, user removal, and initiator mgt. Moreover theintegration of SEC in SMF is also related to the Operator Backup. Each time a new Operator backup isperformed also SEC database is backuped.
If on top of 1354RM is installed also 1353SH software (Master or Presentation) for cohosted orpresentation installations you have to install SEC for SH using the axinstallGui.ptk procedure and SECfor RM as described below
Keep into account that the SEC installations for RM and SH are different, the integration schemas and theconfiguration steps are different.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
128
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
C.2 Installing SEC Subsystem
This procedure must be executed each time a new delivery of SEC and 1354RM has to be installed.
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 <full_pathname_SEC_inst_kit><Target_installation_full_pathname>
If the install_SEC procedure is started with the etc/trace script, it will produce a trace file of the procedureinstall_SEC called /usr/snml/etc/install_SEC.trc.
N.B. The procedure, in order to grant a proper installation, check that the choosen target installationdirectory 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 for1353SH (cohosted or SH–Presentation) 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) onthe 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 pointto the target installation directory choosen.
N.B. In the case in which SEC is alredy installed on RM please do a Backup of Operator datatype, deinstallold SEC, install the new version of SEC and perform a Restore of the Operator datatypes. If you want toinstall a new version of SEC it is possible that the DB have to be migrated.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
129
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 bestopped. If SEC on top of SH installation is installed run the script/usr/1353sh/install/script/stop_security.sh.
N.B.: After the deinstallation all the other SEC subsystems installed have to be restarted at hand.(/usr/1353sh/install/script/start_security.sh)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
130
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
C.4 SEC Administration
SEC Subsystem is provided with a default customization for which on an RM is automatically configuredto run secim process if RM–IM 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 inserted1 line for each permanent SEC process. This line invokes the scriptrun_SECIM|LSS_1354RM_<NTWDOMAIN> that checks for SEC abilitation to run and launch thesecim|lss_1354RM_<NTWDOMAIN> process. The automatic start of SEC processes is set on run–level4 that is the 1354RM run–level default. No checks are performed on the 1354RM effective run–level (itis supposed to be 4).
During Operator Backup and Restore the SEC subsystem is stopped in order to add to the OperatorInformations also Informations related to SEC. The actions related to SEC start and stop are automaticallylaunched by SMF.
If some problem occurs during SMF–>Operator Administration and SEC DB is not updated on changesexecuted 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 actualRM 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 installedfor SH.
Restrictions:
SEC 5.0 doesn’t manage the scheduling time. This means that if an user has a scheduled rule this ruleis applied everytime. This limitation is not due to the integration level but to the fact that SEC 5.0 doesn’tsupport it.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
131
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 followingfiles:
/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:
MGT: Users that have this capability, if allowed by the NAD Rule (see below), can manage accessiblealarms ( acknowledgement).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
132
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
RM Rule Alarm Ac-cess Type
PhysicalLinkAlarms
MS–TrailAlarms
Ho–TrailAlarms
PathAlarms
Process-ing Alarms
AC_R_SNML MGT X X X X X
AC_R_PAYMAN MGT X X X X
AC_R_PADMIN MGT X
AC_R_TOPMAN MGT X X X X
AC_R_PATHRO RO X
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 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 (Read–Only)
The MGT Alarm Accessability is granted if allowed by the System Profile (previous table) otherwise (forLook–Only 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 correspondingNAD Rule associated
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 SEC–DB must be modified before the SECinstallation in order to keep coherent user creations.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
133
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
In particular in order to give to Look–Only users the possibility to manage all the Alarms without keepinginto account the RM Rule change the line:
System_Profile : LookOnly : ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,ASHISTUSM_FAD@AsHistoricalUsm :
as follows:
System_Profile : LookOnly :ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm,ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm, ASHISTUSM_FAD@AsHistoricalUsm
On the other side, if the Look–Only users Accessability have to be extended to manage alarms dependingon 1354RM Access Rules (second table), change the line:
System_Profile : LookOnly : ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,ASHISTUSM_FAD@AsHistoricalUsm :
as follows:
System_Profile : LookOnly : ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,ASHISTUSM_FAD@AsHistoricalUsm : ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm
N.B.: The remaining of the file have to be left unchanged.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
134
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
135
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
APPENDIX D COMMAND FILE SPECIFICATION
This appendix contains a brief description of command file format which permits to manage paths andtrails. This command file will be used from 1354RM either to rebuild its database or to take over a networkpreviously 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
136
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1 Command Description
Some different types of commands are recognized by this specific tool:
a ) command to set the network where commands will be executed (called ”working network”);b ) commands to define, delete, update, deallocate, (de)implement and protect/unprotect paths (with or
without constraints);c ) commands to define, delete, update, (de)allocate, (de)implement, protect/unprotect and configure
trail (with or without constraints);d ) commands to change NAD to paths, nap, trails and link connections;e ) commands to treat PM features ( e.g. creating and removing measures, relating a tp to some
measures);f ) commands to deal with objects of class aSAProfile;g ) commands to manage objects of class restRule;h ) command to manage connection in topology.i ) commands to create, remove, (de)implement topology and physical connection;j ) commands to upload, remove Nap;k ) commands to configure et and physical connection;
Comment lines can also be introduced in the command file (for example to document a particularcommand).
A command file may contain all types of commands. However, it is important to set the work network beforeexecuting the commands on paths and trails. It is possible to set the work network specifying an inputparameter.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
137
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.1 Syntax Description
This document uses a BNF notation to describe the syntactic structure of the command. This notation usesthe punctuation showed below:
braces with vertical bars { | } means you must use one of the items in the braces separated by verticalbars;
brackets [ ] means you can optionally use the item in the brackets. If the brackets enclose multipleitems 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>: it’s 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”
“user’Label 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/DD–hh:mm:ss (YYYY four digit of year and > 1970; MM:month (01–12), DD: day of month (01–31) – hh: hour of day(00–23); mm: minute (00–59); second(00–59)). See the SET command for further information about time reference.
N.B. In the previous text special characters are in bold to highlight them. In the following syntaxdescriptions no bold fonts are use.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
138
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.2 Setting time reference.
D.1.2.1Description
The SET command can be used to choose a time reference for dates. If the local time reference is chosenthen all dates are converted to GMT0 time (GMT0 and UTC are functionally equivalent). This is the typicalbehavior of a US application. If the GMT0 time reference is set then no conversion is applied to dates. Thisis 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
SET ntwId <number> END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
139
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.4 Path commands
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 thepath).
UPDALRpath: it updates the alarmPropagationRule of an existing path.
CONNECTpath: it connects path’s Tp.
DISCONNECTpath: it disconnects path’s 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
140
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
upd_path_attributes := [ 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>
tp_path_list := { 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>] }
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
141
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
CREATEpath userLabel <user_label> <path_attributes> endTpList <tp_path_list> <tp_path_list> [... <tp_path_list>] ENDEND
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 “useMainA–Z, useSpareA–Z, useMainSpareA–Z“ are meaningful just for unidirectionalpaths. 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 userLabel <user_label> [... <ctp_list>]END
ALLOCpath userLabel <user_label> END
DEALLOCpath userLabel <user_label> END
IMPLpath userLabel <user_label> END
DEIMPLpath userLabel <user_label> END
DELETEpath userLabel <user_label> END
UPDATEpath userLabel <user_label>
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
142
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
updList [userLabel <user_label>] [<upd_path_attributes>] ENDEND
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. Node topology is valid only for Drop & Continue One Node and Drop & Continue 2 Switchconnection.
connProtType := { legProtected | legNotProtected }
endLegType := {nap <port_name> | node <node_name> [portName <port_name>] }
opNapType := {keepNap | releaseNap }
PROTECTpath userLabel <user_label> <protCmd> <changeOpType> endTpList [[<ttp_to_prot> <ttp_to_prot>] [topologyLevel <topLevProt>]] ENDEND
PROTECTpath userLabel <user_label> { <unprCmd> <changeOpRes> <changeOpType> | <remCmd> <changeOpType> } endTpList [[<ttp_to_prot> <ttp_to_prot>] [topologyLevel <topLevProt>]] ENDEND
ADDLEGpath userLabel <user_label>
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
143
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
[[allocRule automaticallyAllocated [<changeOpType>] [protRequired <connProtType>]] | [allocRule onUserRequest ]] <endLegType>END
REMOVELEGpath userLabel <userLabel> [<changeOpType>] [<opNapType>] nap <port_name>END
COMMISSIONpath userLabel <user_label>END
UNCOMMISSIONpath userLabel <user_label>END
UPDALRpath userLabel <user_label> {<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 ofa 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 protectedpaths (protType=sh1Plus1EToEProt) and then to add the service connection with the properPROTECTpath command (see examples).
CONNECTpath userLabel <user_label> <changeOpType> endTpList ctp <port_name> payloadPos <string> ctp <port_name> payloadPos <string> ENDEND
DISCONNECTpath userLabel <user_label> endTpList ctp <port_name> payloadPos <string> ctp <port_name> payloadPos <string> ENDEND
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
144
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ELEMALRMNGpath userLabel <user_label> {pdhElemAlr enable | pdhElemAlr disable | sdhElemAlr enable | sdhElemAlr disable }END
SPLITpath userLabel <user_label> operationalRule <opRule> node <user_label>END
JOINpath userLabel <user_label1> userLabel <user_label2> operationalRule <opRule> node <user_label>END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
145
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.5 Trail commands
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, itdeletes 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
146
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.5.2Syntax
upd_trail_attributes := { trailType pointToPoint }
[ payloadStructure tu12Tu12Tu12 | payloadStructure tu12Tu12Tu3 | payloadStructure tu12Tu3Tu12 | payloadStructure tu3Tu12Tu12 | payloadStructure tu12Tu3Tu3 | payloadStructure tu3Tu12Tu3 | payloadStructure tu3Tu3Tu12 | payloadStructure tu3Tu3Tu3 | payloadStructure notTerminatedAu4 | payloadStructure notTerminatedAu3 payloadStructure tu12 | payloadStructure notMeaningful ] [ protType notProtected | protType sh1Plus1EToEProt | protTypeenhancedProtected]
[ 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 := ctp <port_name> payloadPos <string>
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> ENDEND
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 userLabel <user_label> [... <ctp_constr_list>]END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
147
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ALLOCtrail userLabel <user_label>END
DEALLOCtrail userLabel <user_label>END
IMPLtrail userLabel <user_label>END
DEIMPLtrail userLabel <user_label>END
CONFIGtrail userLabel <user_label> [ payloadStructure tu12Tu12Tu12 | payloadStructure tu12Tu12Tu3 | payloadStructure tu12Tu3Tu12 | payloadStructure tu3Tu12Tu12 | payloadStructure tu12Tu3Tu3 | payloadStructure tu3Tu12Tu3 | payloadStructure tu3Tu3Tu12 | payloadStructure tu3Tu3Tu3 | payloadStructure notTerminatedAu4 | payloadStructure terminatedAu4 | payloadStructure notMeaningful payloadStructure notTerminatedAu3 | payloadStructure tu12]END
DELETEtrail userLabel <user_label> END
UPDATEtrail userLabel <user_label> updList [userLabel <user_label>] [<upd_trail_attributes>] ENDEND
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 userLabel <user_label> <protCmd> <changeOpType> endTpList [[<ttp_to_prot> <ttp_to_prot>]
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
148
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
[topologyLevel <topLev>]] ENDEND
PROTECTtrail userLabel <user_label> { <unprCmd> <changeOpRes> <changeOpType> | <remCmd> <changeOpType> } endTpList [[<ttp_to_prot> <ttp_to_prot>] [topologyLevel <topLev>]] ENDEND
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 userLabel <user_label> operationalRule <opRule> node <user_label> END
JOINtrail userLabel <user_label1> userLabel <user_label2> operationalRule <opRule> node <user_label> END
UPDALRtrail userLabel <user_label> sdhAlrEnabRule manual | sdhAlrEnabRule onImplementation END
ELEMALRMNGtrail userLabel <user_label> sdhElemAlr enable | sdhElemAlr disable END
CONFIGUREmsTrail userLabel <user_label> Au4List [ hoAu4 | hoAu4Conc4 | hoAu4Conc16 | hoAu4Conc64 ] ENDEND
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
149
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.6 Port User Label
For NEs with TSD–IM interface the port userlabel will be done by means of naming rules. No relationshipexists with TSD–IM 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 TSD–IM objects.
For the other cases the port userlabel is done by SH–WX 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
CHOWNonObj lc userLabel <user_label> payloadPos <string> securityLabel <number>END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
150
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.8 PM commands
D.1.8.1Description
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 performancemonitoring 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.
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 moretCAProfile objects.
UNCORRpmTpToTca: It deletes the correlation of a pmTp to a tCAProfile objects.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
151
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 <user_label>pmGranularity <pmGran>pmCollectCounter <pmCount>[ pmStartTime <date> ][ pmEndTime <date> ][ pmLayer <pmLay> ][ defaultEnd <boolean> ]
END
UPDATE CLASS pMeasure userLabel <user_label>updList
[ userLabel <user_label> ][ pmGranularity <pmGran> ][ pmLayer <pmLay> ][ pmCollectCounter <pmCount> ][ defaultEnd <defEnd> ][ pmStartTime <date> ]
[ pmEndTime <date> ] ENDEND
DELETE CLASS pMeasureuserLabel <user_label>
END
pmRepDesType := { file | mail | printer }
pmRepWin := { min15 | hour | day | week | month | year }
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
152
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
CREATE CLASS tCRProfileuserLabel <user_label>pmGranularity <pmGran>pmRepDestName <string>pmReportWindow <pmRepWin>[ pmReportDestType <pmRepDesType> ][ pmThreBBE <number> ] [ pmThreES <number> ] [ pmThreSES <number> ] [ pmThreFEBBE <number> ] [ pmThreFEES <number> ] [ pmThreFESES <number> ]
END
N.B. When one of the attributes which are not mandatory is not present in the above create request, itsvalue 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> ]
ENDEND
DELETE CLASS tCRProfileuserLabel <user_label>
END
CREATE CLASS pmCountRepuserLabel <user_label>pmRepDestName <string>pmReportWindow <pmRepWin>pmReportDestType <pmRepDesType>
END
UPDATE CLASS pmCountRepuserLabel <user_label>updList
[ userLabel <userLabel> ][ pmReportDestType <pmRepDesType> ][ pmRepDestName <string> ][ pmReportWindow <pmRepWin> ]
END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
153
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
DELETE CLASS pmCountRepuserLabel <userLabel>
END
N.B. objects of class tCAProfile have no attributes to update.
CREATE CLASS tCAProfileuserLabel <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 tCAProfileuserLabel <user_label>
END
STARTmeasuserLabel <user_label>
END
STOPmeasuserLabel <user_label>
END
CONSmeasuserLabel <user_label>
END
pathTrail := [ pathUserLabel <user_label> | trailUserLabel <user_label> ]
CORRtransToMeasmeasureUserLabel <user_label>{ <pathTrail> } ...
END
UNCORRtransToMeas{ measureUserLabel <user_label> } ...<pathTrail>
END
Tp := { nap <port_name> | cap <port_name> payloadPos <string> | ctp <port_name> payloadPos <string> }
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
154
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 | UNCORRrepToMeasmeasureUserLabel <user_label>{ <Report> } ...
END
CORRpmTpToTcameasureUserLabel <user_label><Tp>{ tca <user_label> } ...END
N.B. The pmTp involved in the correlation is identified by the measure it belongs to and by the Tp relatedto it.
UNCORRpmTpToTcameasureUserLabel <user_label><Tp>
END
DELETEpmTpmeasureUserLabel <user_label><Tp>
END
N.B. The pmTp to delete is identified by the measure it belongs to and by the Tp related to it.
DELETEpmTranspmeasureUserLabel <user_label><pathTrail>
END
N.B. In DELETEpmTransp <pathTrail> specifies the userLabel of the pmTransport object. If thepmTransport is a path–image the pathUserLabel token is used while if it is a trail–image the trailUserLabelis used instead. Note that a pmTransport is created with the same userLabel of the correspondingpath/trail.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
155
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 andphysical connection.
D.1.9.2 Syntax
AlarmSevCode:= { nonAlarmed | minor | major | critical | warning }
CREATE CLASS aSAProfileuserLabel <user_label>[ mediaEqFail <AlarmSevCode> ][ underProtDegr <AlarmSevCode> ][ rSFailure <AlarmSevCode> ][ exBer <AlarmSevCode> ][ degSignal <AlarmSevCode> ][ confMismatch <AlarmSevCode> ][ sdhFailure <AlarmSevCode> ][ pdhFailure <AlarmSevCode> ][ qualityTC15 <AlarmSevCode> ][ qualityTC24 <AlarmSevCode> ]
END
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 aSAProfileuserLabel <user_label>
END
asapClasses:= { path | trail | physicalConn }
objectUserLabel:= userLabel <user_label>
toBindObject:= CLASS asapClasses{ objectUserLabel }.....END
CORRtoaSAProfileuserLabel <user_label>{ toBindObject }.....
END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
156
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.10 restRule commands
D.1.10.1Description
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 thesubsequent commands related to object of class restoration Rule will be sentto;
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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
157
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.10.2Syntax
SET restDomId <number>END
ObjRestClass:= { path | trail }
RestorationStrategy:= { optimizedAddProt | eToEAddProt }
AllocationConstraint:= { notAlarmedResourcesOnly | noRestriction }
ConstrRule:= { dontUseConstraints | useDefConstraints }
CREATE CLASS restRuleuserLabel <user_label>objClass <ObjRestClass>[ restStrategy <RestorationStrategy> ][ holdOffTime <number> ][ usedResources <AllocationConstraint> ][ constraintRule <ConstrRule> ]
END
In the above create request holdOffTime has a value of 300 as a default.
UPDATE CLASS restRuleuserLabel <user_label>objClass <ObjRestClass>updList
[ restStrategy <RestorationStrategy> ][ holdOffTime <number> ][ usedResources <AllocationConstraint> ][ constraintRule <ConstrRule> ]
ENDEND
DELETE CLASS restRuleuserLabel <user_label>objClass <ObjRestClass>
END
N.B. In the above CREATE, UPDATE and DELETE the object of class restoration rule is identified via theuser label and the the class of the object related.
ACT_UPDATE CLASS ObjRestClassuserLabel <user_label>updList
restState supervisedEND
END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
158
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.11 Comments
Comments can be specified in a line of the command file beginning with the symbol !. Comments aredelimited 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 secondsbetween 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
EXIT
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
159
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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 | XMITRCV | 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:= { ntw | sbn | et | node }
N.B. The possible configuration are the following:
ctp–ctpnap–ctpctp–napcap–ctpctp–capcap–capnap–napctp–ctp–ctpnap–ctp–ctpctp–ctp–napcap–cap–capcap–ctp–ctpctp–ctp–ctp–ctpcap–ctp–ctp–ctpctp–cap–ctp–ctpctp–ctp–cap–ctpctp–ctp–ctp–capnap–ctp–ctp–ctpctp–nap–ctp–ctpctp–ctp–nap–ctpctp–ctp–ctp–nap
IMPLconn topologyLevel <topolevel> endTpList <conn_tp_list> ENDEND
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
160
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
DEIMPLconn topologyLevel <topolevel> endTpList <conn_tp_list> ENDEND
N.B. Now those function can be used only at node level.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
161
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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.
OBJECTconnection: it connect/disconnect one or more physical connection.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
162
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.1.16.2Syntax
etType_set:= { genericRing | msSpring | meshed | msSpring4f }
stmType_set:= { stm1 | stm4 | stm16 | notHomogeneus | stm64 | stm0 }
CREATEntwuserLabel <user_label>mapId <integer>userId <string>[comment1 <string> ][comment2 <string> ]
END
CREATEsbnuserLabel <user_label>includedIn ntw <user_label>userId <string>[comment1 <string> ][comment2 <string> ]
END
CREATEetuserLabel <user_label>includedIn sbn <user_label>userId <string>etType <etType_set>stmType <stmType_set>fiberNum <integer>globalCfg <True | False>[comment1 <string> ][comment2 <string> ]
END
CREATEnodeuserLabel <user_label>includedIn <sbn | et><user_label>userId <string>neUserLabel <user_label>[seqNumInEt <integer>][nodeInEt <integer>][comment1 <string> ][comment2 <string> ]
END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
163
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
CREATE physicalConnectionuserLabel <user_label>userId <string>aSDHPort <user_label>zSDHPort <user_label>
END
REMOVE ntwuserLabel <user_label>
END
REMOVE sbnuserLabel <user_label>
END
REMOVE etuserLabel <user_label>
END
REMOVE physicalConnectionuserLabel <user_label>
END
IMPL <ntw | sbn | et | physicalConnection>userLabel <user_label>
END
DEIMPL <ntw | sbn | et | physicalConnection>userLabel <user_label>
END
Update et userLabel<label> globalCfg <True |False>END
SPLITphysicalConnection reqType <splitType> userLabelPhyConnToSplit <user_label> userLabelFirstPhyConn <user_label> userLabelOldFirstPort <user_label> userLabelNewFirstPort <user_label> userLabelSecondPhyConn <user_label> userLabelOldSecondPort <user_label> userLabelNewSecondPort <user_label> <split_phyConn_attr>END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
164
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
JOINphysicalConnection reqType <joinType> userLabelFirstPhyConn <user_label> userLabelSecondPhyConn <user_label> userLabelNewPhyConn <user_label> <join_phyConn_attr>END
OBJECTconnection actionType <actionConnection> connectMode <modeConnection> { physicalConnection <user_label> }........END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
165
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 <string>
END
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
CONFIGURE <et | physicalConnection>userLabel <user_label>payloadStructureList
vc3Num <integer>vc4Num <integer>vc12Num <integer>
payloadStructureListENDEND
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
166
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.2 tool description
The tool for executing command files accepts some input parameters:
–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 printedon 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.
In this case, the tool only stops the execution of the commands if the wrong attribute value is specified inSET, SETpath, SETtrail commands, otherwise the command is skipped and the tool execution goes on,unless the utility is running with ’–stop’ option on.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
167
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3 Examples
VADM_16
Adm2
Adm5
VADM_15
VADM_18
VADM_17
VADM_2
VADM_3
VADM_11 VADM_19
VADM_33
VADM_4
VADM_5
VADM_34VADM_37
VADM_38
X_27
X_26
ADM_1
Adm7
Adm8
NE_V1
RING STM–1
RING STM–4
RING STM–16
Figure 5. Reference Network
In the following three examples it is supposed to have the Network showed at figure 5. NE_V1 is a virtualNE, while all the others ADM are real NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
168
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3.1 Example on paths
In this example a simple bidirectional 2Mb path between ADM_1 and VADM_2 is created, allocated (byusing constraints) and imlemented.
! ## DATE ## 14/12/98 15:05:16SETpath allocRule user implRule user allocationConstraint noRestriction ENDSET ntwId 1 END
CREATEpath userLabel ”ADM001–VADM_3–2M–9” pathType bidirectionalPtoPto pathRate lo2Mb protType notProtected allAlgType automatic userId ”snmlr21” pmAutomatic false alarmPropRule whenImplemented endTpList nap ”ADM_1/2M/1–09” usedDir bidirectional nap ”VADM_3/2M–06” usedDir bidirectional ENDEND
!!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/add–remove leg/!add–remove protection is executed!
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
169
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
CONSTRpath userLabel ”ADM001–VADM_3–2M–9” ctp ”ADM_1/West” payloadPos ”01/1/5.2” constrainType useMain ctp ”VADM_3/STM1–2” payloadPos ”01/1/5.2” constrainType useMain ENDALLOCpath userLabel ”ADM001–VADM_3–2M–9” END!! It is not necessary to remove all the constraints ! related to the path.! If you don’t delete them, the constraints will be used for the ! next allocation phase !!CONSTRpath userLabel ”ADM001–VADM_3–2M–9” ENDIMPLpath userLabel ”ADM001–VADM_3–2M–9” END
CONNECTpath userLabel ”ADM001–VADM_3–2M–9” “immediate” endTpList ctp ”ADM_1/2M/1–09” payloadPos “03/1.1/1” ctp ”VADM_3/2M–06” payloadPos ”03/1.1/1” ENDENDDISCONNECTpath userLabel ”ADM001–VADM_3–2M–9” endTpList ctp ”ADM_1/2M/1–09” payloadPos “03/1.1/1” ctp ”VADM_3/2M–06” payloadPos ”03/1.1/1” ENDEND
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
170
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3.2 Example on paths protected with Drop & Continue
In this example an enhanced protected 2Mb path is implemented in three steps:
1) the unprotected path is implemented between Adm7 and Adm2. The path route is forced by using TPconstraints; the route is Adm2–Adm5–VADM_2–VADM_3–Adm8–Adm7;
2) the path is SNCP protected. The spare path route is forced by using TP constraints; the spare routeis Adm2–VADM_16–VADM_15–VADM_38–VADM_34–VADM_4–VADM_5–VADM_33–Adm7; SNCPconnections are created on Adm2 and Adm7;
3) the path is enhanced protected in RING STM–1 and RING STM–4. The service path routes are forcedby using TP constraints. The first service route is Adm5–VADM_17–VADM_18–VADM_15. Drop &continue connections are created on Adm5 and VADM_15. The second service route isAdm8–VADM_11–VADM_19–VADM_33. Drop & continue connections are created on Adm8 andVADM_33.
! ## DATE ## 30/09/97 09:04:19!! path enhanced protected!SETpath allocRule user implRule user allocationConstraint noRestriction END SET ntwId 1 END!! step 1– not protected path is created!CREATEpath userLabel ’Adm7–Adm2–2M–15’ pathType bidirectionalPtoPto pathRate lo2Mb protType notProtected alarmPropRule whenImplemented allAlgType automatic userId ’snmlr21’ endTpList nap ’Adm2/port2M–102’ usedDir bidirectional nap ’Adm7/port2M–115’ usedDir bidirectional ENDEND CONSTRpath userLabel ’Adm7–Adm2–2M–15’ ctp ’Adm2/West’ payloadPos ’01/1/1.3’ constrainType useMain ! ctp ’Adm5/East’ payloadPos ’01/1/1.3’ ctp ’Adm5/stm–1’ payloadPos ’01/1/1.2’ constrainType useMain ! ctp ’VADM_2/STM1–1’ 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 ’VADM_3/STM1–3’ payloadPos ’01/1/7.2’ constrainType useMain ! ctp ’Adm8/stm–1’ payloadPos ’01/1/7.2’
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
171
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ctp ’Adm8/East’ payloadPos ’01/2/2.2’ constrainType useMain ! ctp ’Adm7/West’ payloadPos ’01/2/2.2’ END ALLOCpath userLabel ’Adm7–Adm2–2M–15’ END!! step 2 – protection SNCP is added!CONSTRpath userLabel ’Adm7–Adm2–2M–15’ 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/West’ payloadPos ’01/1/5.3’ ctp ’VADM_15/STM1–1’ payloadPos ’01/1/1.2’ constrainType useSpare ! ctp ’VADM_38/STM1–1’ payloadPos ’01/1/1.2’ ctp ’VADM_38/West’ payloadPos ’01/1/1.1’ constrainType useSpare ! ctp ’VADM_34/East’ payloadPos ’01/1/1.1’ ctp ’VADM_34/STM1–2’ payloadPos ’01/1/1.3’ constrainType useSpare ! ctp ’VADM_4/STM1–2’ payloadPos ’01/1/1.3’ ctp ’VADM_4/East’ payloadPos ’02/2/7.3’ constrainType useSpare ! ctp ’VADM_5/West’ payloadPos ’02/2/7.3’ ctp ’VADM_5/STM1–1’ payloadPos ’01/1/1.3’ constrainType useSpare ! ctp ’VADM_33/STM1–3’ payloadPos ’01/1/1.3’ ctp ’VADM_33/West’ payloadPos ’01/2/2.2’ constrainType useSpare ! ctp ’Adm7/East’ payloadPos ’01/2/2.2’ END!! the allocation of spare route is executed with the following command!PROTECTpath userLabel ’Adm7–Adm2–2M–15’ protect deferred endTpList nap ’Adm2/port2M–102’ nap ’Adm7/port2M–115’ topologyLevel ntw ENDEND!! step 3 – service protection is added!CONSTRpath userLabel ’Adm7–Adm2–2M–15’ ctp ’Adm5/West’ payloadPos ’01/1/2.3’ constrainType useService ! ctp ’VADM_17/East’ payloadPos ’01/1/2.3’ ctp ’VADM_17/West’ payloadPos ’01/1/4.1’ constrainType useService ! ctp ’VADM_18/East’ payloadPos ’01/1/4.1’ ctp ’VADM_18/West’ payloadPos ’01/1/5.2’ constrainType useService ! ctp ’VADM_15/East’ payloadPos ’01/1/5.2’ END!
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
172
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
! the allocation of second spare route is executed with the following command!PROTECTpath userLabel ’Adm7–Adm2–2M–15’ addEnhancedProt deferred endTpList ctp ’Adm5/stm–1’ payloadPos ’01/1/1.2’ ctp ’VADM_15/STM1–1’ payloadPos ’01/1/1.2’ topologyLevel et ENDEND CONSTRpath userLabel ’Adm7–Adm2–2M–15’ ctp ’Adm8/West’ payloadPos ’01/1/2.2’ constrainType useService ! ctp ’VADM_11/East’ payloadPos ’01/1/2.2’ ctp ’VADM_11/West’ payloadPos ’01/1/3.3’ constrainType useService ! ctp ’VADM_19/East’ payloadPos ’01/1/3.3’ ctp ’VADM_19/West’ payloadPos ’01/1/3.3’ constrainType useService ! ctp ’VADM_33/East’ payloadPos ’01/1/3.3’ END PROTECTpath userLabel ’Adm7–Adm2–2M–15’ addEnhancedProt deferred endTpList ctp ’Adm8/stm–1’ payloadPos ’01/1/7.2’ ctp ’VADM_33/STM1–3’ payloadPos ’01/1/1.3’ topologyLevel et ENDEND CONSTRpath userLabel ’Adm7–Adm2–2M–15’ END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
173
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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). Thefirst 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 thenodename. 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:16SETpath allocRule user implRule user allocationConstraint noRestriction ENDSET ntwId 1 END
CREATEpath userLabel ”moni” pathType unidirectionalPtoPto pathRate lo2Mb protType notProtected allAlgType automatic userId ”lts4182/snmlr24” pmAutomatic false alarmPropRule whenImplemented endTpList nap ”VADM_38/2M–11” usedDir source node ”NE_V1” usedDir sink portName ”NE_V1/2M–21” ENDEND
!!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/STM1–15” payloadPos ”01/2/7.2” constrainType useMainA ctp ”X27/STM1–14” payloadPos ”01/2/7.2” constrainType useMainZ ctp ”NE_V1/STM1–5” payloadPos ”01/2/7.2” constrainType useMainA ENDALLOCpath 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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
174
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
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/STM1–2” payloadPos ”01/2/7.3” constrainType useSpareZ ctp ”X26/STM1–15” payloadPos ”01/2/7.3” constrainType useSpareA ctp ”X26/STM1–1” payloadPos ”01/1/3.3” constrainType useSpareZ ctp ”NE_V1/STM1–6” 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/2M–11” nap ”NE_V1/2M–21” topologyLevel ntw ENDEND!!Onethor leg is just defined!ADDLEGpath userLabel ”moni” allocRule onUserRequest node ”NE_V1” END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
175
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 thefollowing the route of the legs is described. It is supposed to have the Network as in the figure:
VADM_16
Adm2
Adm5
VADM_15
VADM_18
VADM_17
RING STM–1
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,Adm2A 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,Adm5A 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
A switch connection is created on VADM_15 – leg5 – from VADM_17 to VADM_16 (protected) route main: VADM_17,VADM_18,VADM_15,VADM_16 route spare: VADM_17,Adm5,Adm2,VADM_16A switch connection is created on VADM_16 – leg6 – from VADM_17 to VADM_18 (protected) route main: VADM_17,VADM_18 route spare: VADM_17,Adm5,Adm2,VADM_16,VADM_15,VADM_18A switch connection is created on VADM_18
! ## DATE ## 02/02/98 14:30:46!SETpath allocRule user implRule user allocationConstraint noRestriction ENDSET ntwId 2 END!
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
176
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
! Leg1!CREATEpath userLabel ’circular1’ pathType unidirectionalPtoPto pathRate lo2Mb protType notProtected alarmPropRule whenCommissioned allAlgType automatic userId ’lts4182/snmlr23’ pmAutomatic false endTpList nap ’VADM_17/2M–1–01’ usedDir source nap ’VADM_17/2M–1–02’ usedDir sink ENDEND
CONSTRpath userLabel ’circular1’ ctp ’VADM_17/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_18/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_18/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_15/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_15/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_16/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_16/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’Adm2/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’Adm2/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’Adm5/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’Adm5/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_17/East’ payloadPos ’01/1/1.1’ constrainType useMain ENDALLOCpath userLabel ’circular1’ END!! Leg2! nap ’Adm2/port2M–101’ is added to the path!ADDLEGpath userLabel ’circular1’ allocRule onUserRequest nap ’Adm2/port2M–101’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’Adm5/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’Adm5/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’Adm2/West’ payloadPos ’01/1/1.1’ constrainType useMain END!! Leg2 is allocated after the following command. A broadcast connection is created on node VADM_17!
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
177
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ADDLEGpath userLabel ’circular1’ allocRule automaticallyAllocated deferred nap ’Adm2/port2M–101’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_18/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_18/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_15/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_15/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_16/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_16/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/East’ payloadPos ’01/1/1.1’ constrainType useSpare END!! Leg2 is protected!PROTECTpath userLabel ’circular1’ protect deferred endTpList nap ’VADM_17/2M–1–01’ nap ’Adm2/port2M–101’ topologyLevel ntw ENDEND!! Leg3! nap ’Adm5/port2M–101’ is added to the path!ADDLEGpath userLabel ’circular1’ allocRule onUserRequest nap ’Adm5/port2M–101’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’Adm5/West’ payloadPos ’01/1/1.1’ constrainType useMain END!! Leg3 is allocated after the following command. A leg is added on the broadcast connection on nodeVADM_17!ADDLEGpath userLabel ’circular1’ allocRule automaticallyAllocated deferred nap ’Adm5/port2M–101’ENDCONSTRpath
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
178
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
userLabel ’circular1’ ctp ’VADM_17/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_18/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_18/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_15/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_15/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_16/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_16/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm5/East’ payloadPos ’01/1/1.1’ constrainType useSpare END!! Leg3 is protected!PROTECTpath userLabel ’circular1’ protect deferred endTpList nap ’VADM_17/2M–1–01’ nap ’Adm5/port2M–101’ topologyLevel ntw ENDEND!! Leg4! nap ’VADM_15/2M–1–01’ is added to the path!ADDLEGpath userLabel ’circular1’ allocRule onUserRequest nap ’VADM_15/2M–1–01’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_18/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_18/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_15/East’ payloadPos ’01/1/1.1’ constrainType useMain END!! Leg4 is allocated after the following command. A leg is added on the broadcast connection on nodeVADM_17!ADDLEGpath userLabel ’circular1’ allocRule automaticallyAllocated deferred nap ’VADM_15/2M–1–01’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm5/West’ payloadPos ’01/1/1.1’ constrainType useSpare
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
179
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ctp ’Adm5/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_16/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_16/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_15/West’ payloadPos ’01/1/1.1’ constrainType useSpare END!! Leg4 is protected!PROTECTpath userLabel ’circular1’ protect deferred endTpList nap ’VADM_17/2M–1–01’ nap ’VADM_15/2M–1–01’ topologyLevel ntw ENDEND!! Leg5! nap ’VADM_16/2M–1–01’ is added to the path!ADDLEGpath userLabel ’circular1’ allocRule onUserRequest nap ’VADM_16/2M–1–01’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_18/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_18/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_15/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_15/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_16/East’ payloadPos ’01/1/1.1’ constrainType useMain END!! Leg5 is allocated after the following command. A leg is added on the broadcast connection on nodeVADM_17!ADDLEGpath userLabel ’circular1’ allocRule automaticallyAllocated deferred nap ’VADM_16/2M–1–01’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm5/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm5/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/East’ payloadPos ’01/1/1.1’ constrainType useSpare
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
180
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ctp ’VADM_16/West’ payloadPos ’01/1/1.1’ constrainType useSpare END!! Leg5 is protected!PROTECTpath userLabel ’circular1’ protect deferred endTpList nap ’VADM_17/2M–1–01’ nap ’VADM_16/2M–1–01’ topologyLevel ntw ENDEND!! Leg6! nap ’VADM_18/2M–1–01’ is added to the path!ADDLEGpath userLabel ’circular1’ allocRule onUserRequest nap ’VADM_18/2M–1–01’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/West’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_18/East’ payloadPos ’01/1/1.1’ constrainType useMain END!! Leg6 is allocated after the following command. A leg is added on the broadcast connection on nodeVADM_17!ADDLEGpath userLabel ’circular1’ allocRule automaticallyAllocated deferred nap ’VADM_18/2M–1–01’ENDCONSTRpath userLabel ’circular1’ ctp ’VADM_17/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm5/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm5/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’Adm2/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_16/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_16/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_15/West’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_15/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_18/West’ payloadPos ’01/1/1.1’ constrainType useSpare END!! Leg6 is protected!
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
181
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
PROTECTpath userLabel ’circular1’ protect deferred endTpList nap ’VADM_17/2M–1–01’ nap ’VADM_18/2M–1–01’ topologyLevel ntw ENDENDCONSTRpath userLabel ’circular1’ END
SPLITpath userLabel “ADM001–VADM_3–2M–9” operationalRule automatic node “ADM0001”END
JOINpath userLabel “ADM001–VADM_3–2M–9” userLabel “ADM0004” operationalRule automatic node “ADM0001”END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
182
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3.5 Example on trails
In the next examples it is supposed to have the Network as in the figure:
VADM_11 VADM_19
VADM_33
Adm7
Adm8 RING STM–4
VADM_40
VADM_41 VADM_42
VADM_39
RING STM–16
VADM_29
W
E
Three trails are created and LO configured as follow: 1) trail trail8–29/1: Adm–8,Adm7,VADM_29
2) trail trail8–29/2: Adm–8,VADM_11,VADM_19,VADM_33,VADM_29
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 ’trail8–29/1’ trailType pointToPoint flow bidirectional protType notProtected endTpList ctp ’VADM_29/West’ payloadPos ’02’ ctp ’Adm8/East’ payloadPos ’02’ END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
183
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ENDCONSTRtrail userLabel ’trail8–29/1’ 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 ENDALLOCtrail userLabel ’trail8–29/1’ ENDCONSTRtrail userLabel ’trail8–29/1’ ENDIMPLtrail userLabel ’trail8–29/1’ END!!Trail 1 is LO configured!CONFIGtrail userLabel ’trail8–29/1’ payloadStructure tu12Tu12Tu3 END!!Trail 2!CREATEtrail userLabel ’trail8–29/2’ trailType pointToPoint flow bidirectional protType notProtected endTpList ctp ’Adm8/West’ payloadPos ’02’ ctp ’VADM_29/East’ payloadPos ’02’ ENDENDCONSTRtrail userLabel ’trail8–29/2’ ctp ’Adm8/West’ payloadPos ’02’ constrainType useMain ctp ’VADM_11/East’ payloadPos ’02’ constrainType useMain ctp ’VADM_11/West’ payloadPos ’02’ constrainType useMain ctp ’VADM_19/East’ payloadPos ’02’ constrainType useMain ctp ’VADM_19/West’ payloadPos ’02’ constrainType useMain ctp ’VADM_33/East’ payloadPos ’02’ constrainType useMain ctp ’VADM_33/West’ payloadPos ’02’ constrainType useMain ctp ’VADM_29/East’ payloadPos ’02’ constrainType useMain ENDALLOCtrail userLabel ’trail8–29/2’ ENDCONSTRtrail userLabel ’trail8–29/2’ END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
184
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
IMPLtrail userLabel ’trail8–29/2’ END!!Trail 2 is LO configured!CONFIGtrail userLabel ’trail8–29/2’ payloadStructure tu12Tu12Tu3 END!!Trail 3 !CREATEtrail userLabel ’trail–prot’ trailType pointToPoint flow bidirectional protType notProtected endTpList ctp ’VADM_41/East’ payloadPos ’01’ ctp ’VADM_42/West’ payloadPos ’01’ ENDENDCONSTRtrail userLabel ’trail–prot’ ctp ’VADM_41/East’ payloadPos ’01’ constrainType useMain ctp ’VADM_40/West’ payloadPos ’01’ constrainType useMain ctp ’VADM_40/East’ payloadPos ’01’ constrainType useMain ctp ’VADM_42/West’ payloadPos ’01’ constrainType useMain ENDALLOCtrail userLabel ’trail–prot’ END!!Trail 3 is SNCP protected!CONSTRtrail userLabel ’trail–prot’ ctp ’VADM_41/West’ payloadPos ’01’ constrainType useSpare ctp ’VADM_39/East’ payloadPos ’01’ constrainType useSpare ctp ’VADM_39/West’ payloadPos ’01’ constrainType useSpare ctp ’VADM_42/East’ payloadPos ’01’ constrainType useSpare ENDPROTECTtrail userLabel ’trail–prot’ protect deferred endTpList cap ’VADM_41/East’ payloadPos ’01’ cap ’VADM_42/West’ payloadPos ’01’ topologyLevel ntw ENDENDCONSTRtrail userLabel ’trail–prot’
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
185
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ENDIMPLtrail userLabel ’trail–prot’ END!!Trail 3 is LO configured!CONFIGtrail userLabel ’trail–prot’ payloadStructure tu12Tu12Tu3 END
SPLITtrail userLabel “ADM001–VADM_3–2M–9” operationalRule automatic node “ADM0001”END
JOINtrail userLabel “ADM001–VADM_3–2M–9” userLabel “ADM0004” operationalRule automatic node “ADM0001”END
CONFIGUREmsTrail userLabel “MSTRAIL–TO–TEST” Au4List hoAu4Conc4 4 ENDEND
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
186
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3.6 Example of path that uses HO trails
In this example it is supposed to have the three trails created in the previous example.An SNCP path isimplemented by using the trails.
The end points of the path are located on VADM_29 and VADM42.
SETpath allocRule user implRule user allocationConstraint noRestriction ENDSET ntwId 3 END!!First unprotected path is created!CREATEpath userLabel ’test–mig’ pathType bidirectionalPtoPto pathRate lo2Mb protType notProtected alarmPropRule whenImplemented allAlgType automatic userId ’lts4182/snmlr23’ pmAutomatic false endTpList nap ’VADM_29/2M–01’ usedDir bidirectional nap ’VADM42/2M–1’ usedDir bidirectional ENDEND!!The path uses the trail ’trail8–29/1’.!Please note that is not necessary to define the TP on node Adm7, because this TP belongs to the trail.!CONSTRpath userLabel ’test–mig’ ctp ’VADM_29/West’ payloadPos ’02/1/1.1’ constrainType useMain ctp ’Adm8/East’ payloadPos ’02/1/1.1’ constrainType useMain ctp ’Adm8/stm–1’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_41/STM1–1’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_41/East’ payloadPos ’01/1/1.1’ constrainType useMain ctp ’VADM_42/West’ payloadPos ’01/1/1.1’ constrainType useMain ENDALLOCpath userLabel ’test–mig’ END!!The path is SNCP protected.!The spare route uses the other two trails of the previous example.!CONSTRpath userLabel ’test–mig’ ctp ’VADM_29/East’ payloadPos ’02/1/1.1’ constrainType useSpare ctp ’Adm8/West’ payloadPos ’02/1/1.1’ constrainType useSpare
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
187
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
ctp ’Adm8/stm–1’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_41/STM1–1’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_41/East’ payloadPos ’01/1/1.1’ constrainType useSpare ctp ’VADM_42/West’ payloadPos ’01/1/1.1’ constrainType useSpare ENDPROTECTpath userLabel ’test–mig’ protect deferred endTpList nap ’VADM_29/2M–01’ nap ’VADM42/2M–1’ topologyLevel ntw ENDENDCONSTRpath userLabel ’test–mig’ ENDIMPLpath userLabel ’test–mig’ END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
188
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3.7 Example on measures
CREATE CLASS pMeasureuserLabel “Measure_1”pmStartTime ’1998/12/11–10:12:12’ pmEndTime ’1999/12/11–10:12:12’ defaultEnd truepmLayer hopmGranularity pm15MinpmCollectCounter 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:
STARTmeasuserLabel “Measure_1”
END
It is possible to stop the measure manually issuing the following command:
STOPmeasuserLabel “Measure_1”
END
A performance measure aim is to describe the quality of service offered by a path or a trail, so thereforeonce created, to reach its goal a measure must be correlated to a path or a trail. A correlation request canbe submitted as follows:
CORRtransToMeasmeasureUserLabel “Measure_1”pathUserLabel “ADM_1–ADM_39”
END
Note that the end termination points of the object correlated will result automatically under measure ifattribute ’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:
CORRTpToMeasmeasureUserLabel “Measure_1”nap “ADM_1–04”
END
As a measure has been bound to path, trail and their termination points so that relation can be broken usingcommands UNCORR transToMeas and UNCORRTpToMeas.Performance counters values can be reported via mail, printer or file. Doing that is achieved first creatinga new object of class pmCountRep and then correlating it to one measure. Next commands show how gettrough this job.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
189
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
CREATE CLASS countRepuserLabel ’CountRep_1’pmReportDestType filepmRepDestName ’/tmp/rep_1.tmp’pmReportWindow day
END
CORRrepToMeas measureUserLabel ’Measure_1’countRep ’CountRep_1’
END
Performance counters values can be checked against their overflowing a user–selected edge and resultsof 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 thisobject and a measure.
CREATE CLASS tCRProfileuserLabel ’Tcr_1’pmGranularity pm15MinpmReportDestType mailpmRepDestName ’/tmp/tcr_1.tmp’pmReportWindow hourpmThreBBE 10pmThreES 10
END
CORRrepToMeasuserLabel ’Measure_1’tcr ’Tcr_1’
END
!The following command creates an object of class tCAProfile:
CREATE CLASS tCAProfileuserLabel ’Tca_1’pmGranularity pm15MinpmTpForTca vc4bBeHigh 10bBeLow 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:
CORRpmTpToTcameasureUserLabel ’Measure_1’nap ’ADM_1–04’tca ’Tca_1’
END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
190
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3.8 Example on aSAProfile
Object of class aSAProfile can be created and associated to some other objects of class path, trail andphysicalConn to stress, in some way, the importance of the alarms these objects show up.Here after a simple example give some hints.
CREATE CLASS aSAProfileuserLabel ’asap_1’mediaEqFail majorunderProtDegr warningrSFailure majorexBer majordegSignal warningconfMismatch majorsdhFailure warningpdhFailure warningqualityTC15 majorqualityTC24 minor
END
CORRtoaSAProfile userLabel ’asap_1’CLASS physicalConn
userLabel ’connec_1’userLabel ’connec_2’
ENDCLASS path
userLabel ’path_1’ENDCLASS trail
userLabel ’trail_1’END
END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
191
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3.9 Example on restoration rule
The following command create an object of class restoration rule related to an object of class pathidentified by its user label ’path_1’.
CREATE CLASS restRuleuserLabel ’path_1’objClass path
END
If the restoration rule object just created must be changed in its value attributes:
UPDATE CLASS restRuleuserLabel ’path_1’objClass pathupdList
holdOffTime 500END
END
Related to objects of class restoration rule there may be the need to change the attribute ’restState’ valuefor object of class path or trail.
ACT_UPDATE CLASS ObjRestRuleuserLabel ’path_1’updList
restState supervisedEND
END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
192
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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’ ENDEND
DEIMPLconn topologyLevel node endTpList cap ’ADM5/West’ payloadPos ’01’ tpRole ’XMIT RCV’ cap ’VADM_17/East’ payloadPos ’01’ tpRole ’XMIT RCV’ ENDEND
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
193
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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’ comment2 ’Test passed’END
CREATEet includedIn sbn ’sbn1’ userLabel ’et1’ userId ’snml1’ etType genericRing stmType stm1 fiberNum 2 globalCfg True comment1 ’Test to create a network’ comment2 ’Test passed’END
CREATEnode includedIn sbn ’sbn1’ neUserLabel ’ne1’’ userLabel ’node1’ userId ’snml1’ comment1 ’Test to create a network’ comment2 ’Test passed’’ seqNumInEt 2 nodeInEt 3END
CREATE physicalConnection’ userLabel ’phyConn1’’ userId ’snml1’’ aSDHPort ’portWest1’’ zSDHPort ’portEast1’’END
N.B. The parameters order is not important in CREATE operation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
194
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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 userLabel ’physicalConnection1’END
DEIMPL ntw userLabel ’ntw1’END
DEIMPL sbn userLabel ’sbn1’END
DEIMPL et userLabel ’et1’END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
195
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
DEIMPL physicalConnection userLabel ’physicalConnection1’END
Update et userLabel ’STM1’ globalCfg TrueEND
SPLITphysicalConnection 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
SPLITphysicalConnection reqType split 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’ 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.
JOINphysicalConnection reqType undoJoin userLabelFirstPhyConn ’Phy_Conn_1’ userLabelSecondPhyConn ’Phy_Conn_2’ userLabelNewPhyConn ’New_Phy_Conn’END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
196
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
JOINphysicalConnection reqType join userLabelFirstPhyConn ’Phy_Conn_1’ userLabelSecondPhyConn ’Phy_Conn_2’ userLabelNewPhyConn ’New_Phy_Conn’ userLabelFirstPhyConn4f ’Phy_Conn_14f’ userLabelSecondPhyConn4f ’Phy_Conn_24f’ userLabelNewPhyConn4f ’New_Phy_Conn4f’END
N.B. This syntax is used only in 4 fiber physical connection.
OBJECTconnection actionType connect connectMode immediate physicalConnection ’Phy_Conn_To_Connect’ END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
197
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
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
REMOVEnap nap portName ’port_name_1END
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
198
03
957.130.882 U
/3AL 61260 AAAA TQZZA
198
198
D.3.13 Example configure physical connection and et.
CONFIGURE et userLabel ’et1’ payloadStructureList vc3Num 0 vc4Num 4 vc12Num 0 payloadStructureListENDEND
CONFIGURE physicalConnection userLabel ’physicalConnection1’ payloadStructureList vc3Num 0 vc4Num 4 vc12Num 0 payloadStructureListENDEND
END OF DOCUMENT
