NMS5UX,

NMS5UX-B
release 6.4
Network Management System 5 UNIX

Administrator manual

Volume 1/1
MN.00145.E - 003
The information contained in this handbook is subject to change without notice.
Property of Siae Microelettronica S.p.A. All rights reserved according to the law and according to the
international regulations. No part of this document may be reproduced or transmitted in any form or
by any means, electronic or mechanical, without written permission from Siae Microelettronica S.p.A.
Unless otherwise specified, reference to a Company, name, data and address produced on the screen
displayed is purely indicative aiming at illustrating the use of the product.
Hewlett Packard, HP, HP OpenView Windows, Vectra and HP-UX are Hewlett Packard Company
registered trademarks.
UNIX is a Unix Systems Laboratories registered trademark.
Oracle is a Oracle Corporation registered trademark.
OSF Motif is a Open Software Foundation registered trademark.
Other products cited here in are constructor registered trademarks.
 NMS5UX, NMS5UX-B 6.4
ADMINISTRATOR MANUAL

CONTENTS

PREFACE.......................................................................................................................3
1. NMS5UX ADMINISTRATOR RESPONSABILITIES...........................................................4
1.1 Provide suitable hardware for running NMS5UX.........................................................4
1.2 Provide software components for running NMS5UX....................................................4
1.3 Dimensioning file systems ......................................................................................5
1.4 Modify kernel parameters .......................................................................................6
1.4.1 HP-UX 11.0 ..............................................................................................6
1.4.2 HP-UX 11.i ...............................................................................................7
1.5 Enable correct network services ..............................................................................8
1.6 Provide correct codewords and licenses ...................................................................8
1.7 Install and configure sw components .......................................................................8
1.8 Create NMS5UX environment and users ...................................................................9
1.9 Start and stop NMS5UX base processes ...................................................................9
1.10 Backup and restore information ..............................................................................9
1.11 Maintaining NMS5UX..............................................................................................9
1.12 Troubleshooting ....................................................................................................9
1.13 Shutdown/Restart HP Server ..................................................................................9
1.14 Data Backup Tools and Policy................................................................................ 10
2. INSTALLING NMS5UX.................................................................................................11
2.1 Unloading NMS5UX directories .............................................................................. 11
2.2 Setting the environment....................................................................................... 11
3. CONFIGURING A CLIENT-SERVER ARCHITECTURE .....................................................19
4. CONTROLLING ACCESS TO NMS5UX ...........................................................................21
5. USING nmsWinMenu TO START AND STOP NMS5UX ..................................................22
6. LOCALIZATION...........................................................................................................24
7. UPDATING NMS5UX RELEASE.....................................................................................25
8. CUSTOMIZING NMS5UX..............................................................................................26
9. MODIFYING WORKSTATION IP-ADDRESS ..................................................................29
10. MODIFYING WORKSTATION NAME.............................................................................30
11. BACKING UP AND RESTORING NMS5UX DATABASE ...................................................31

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 1

 12. RESETTING NMS5UX DATABASES ..............................................................................32
13. CONFIGURING I/O SERIAL LINES..............................................................................34
14. TROUBLESHOOTING ...................................................................................................35
14.1 NMS5UX architecture ........................................................................................... 35
14.2 TROUBLESHOOTINGS .......................................................................................... 36
15. Annex-A .....................................................................................................................37
16. Annex-B .....................................................................................................................41
17. Annex-C .....................................................................................................................45
17.1 NMS5UX Server - STARTUP procedure ................................................................... 45
17.2 NMS5UX Server - shutdown procedure .................................................................. 46
18. Annex-D .....................................................................................................................48
18.1 DATA BACKUP PROCEDURES ................................................................................ 48
18.1.1 FULL DATA BACKUP PROCEDURES ............................................................ 48
18.1.2 REDUCED DATA BACKUP PROCEDURES ..................................................... 50
18.2 SAVING AND RECOVERING DATA FROM TAPE......................................................... 51
18.3 DATA RESTORE PROCEDURES .............................................................................. 52
18.4 DATA BASE BACKUP POLICY ................................................................................. 53

2 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 PREFACE

The purpose of this manual is to give the administrator of the NMS5UX system the necessary
information to put the application into service, perform maintenance during NMS5UX use and
achieving good performance for the operators.
This manual covers the following topics:
1. Hardware characteristics
2. Software characteristics
3. Resource dimensioning
4. System tuning
5. NMS5UX installation
6. Maintenance
7. Troubleshooting

This manual covers both NMS5UX and NMS5UX-B applications. Main difference is the use of HP
OpenView NNM in NMS5UX respect to NMS5UX-B which uses a SIAE proprietary graphical interface.
A note will be reported in each section that is specific for one of the two applications whilst
remaining sections are intented to be valid for both applications.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 3

 1. NMS5UX ADMINISTRATOR RESPONSABILITIES

The Network Management System 6 has been developed by SIAE Microelettronica over the power of
the Unix operating system in order to increase performance and capabilities of network monitoring
and management.
The large amount of information involved during NMS5UX activity is managed using the Oracle
DBMS. The NMS5UX administrator should be aware of these three components (HPUX, Oracle and
NMS5UX) and their properties and relationships in order to ensure the maximum throughput in
managing his telecommunication network.
The main administrator tasks, with a detailed description of each activity, follows.

1.1 Provide suitable hardware for running NMS5UX

Before installing the application, you must take care that your workstation is suited for the task it is
proposed for.
Running NMS5UX in fact involves a high demand of machine resources, for graphics, database
operations, speedy event handling and general performances.
So, in order to get the best results in managing your network with NMS5UX, the following is the
minimum configuration.

Main memory: 1024 MB (64 MB for each operator requested)

Hard disk: 34 GB

Installing NMS5UX requires a minimum of 16 GB of disk space.

1.2 Provide software components for running NMS5UX

NMS5UX form rel 6.4.0 onwards support different HW/SW configuration.

It can be installed either on server based on PA-RISC architecture running both HP-UX 11.0 and HP-
UX 11.i v1 operating system either on server based on Itanium architecture running HP-UX 11.i v2
operating system.
Depending on the operating system installed on your server different software components are
required to run NMS5UX.

4 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 Software requirements for HP-UX 11.0

Running NMS5UX requires the following software:

Oracle 8.1.7.0.0

OpenView NNM rel 6.2 (*) only for NMS5UX

OSF Motif 2.1, X11 r.6

SNMP library (*) only dor NMS5UX-B

Software requirements for HP-UX 11.i v1/v2

Running NMS5UX requires the following software:

Oracle 10.g

OpenView NNM rel 7.5 for HP-UX 11.11 (PA-RISC) or for HP-UX 11.23 (Itanium) (*) only for
NMS5UX

OSF Motif 2.1, X11 r.6

SNMP library (*) only dor NMS5UX-B

On the rest of this document two different sections are reported for each configuration that is
differend for the two operating systems. To install correctly NMS5UX on your server please follow
the instructions reported on the section that fits your configuration.

1.3 Dimensioning file systems

The installation and utilization of NMS5UX and its components requires following constraints as
regards file system dimensioning:
/tmp 512 MB
/home 512 MB
/var 1,5 GB
/etc 1,5 GB
We recommend to place Oracle and OpenView (* only for NMS5UX ) Data on a separate file system
respect to /opt. In this case you should configure following file systems
/opt 8 GB
/nmsData 8 GB
Otherwise you need /opt dimension to be at least 16 GB.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 5

 1.4 Modify kernel parameters

NMS5UX utilisation requires the administrator to modify kernel parameters; following, the SAM
output of the parameters and requested values depending on the operating system.

1.4.1 HP-UX 11.0

- bufpages 0
- dbc_max_pct 5
- dbc_min_pct 1
- ksi_alloc_max 8352
- max_thread_proc 260
- maxdsiz 256M=0x10000000
- maxdsiz_64 256M=0x10000000
- maxfiles 2048
- maxfiles_lim 2048
- maxswapchunks 4096
- maxuprc 1000
- maxusers 200
- msgmap 6642
- msgmax 32768
- msgmnb 32768
- msgmni 1044
- msgseg 7168
- msgssz 8
- msgtql 6640
- nbuf 0
- ncallout 2064
- nclist 3300
- ncsize 8384
- nfile 8000
- nflocks 664
- ninode 7360
- nkthread 6000
- npty 128
- semmap 3322
- semmni 3320
- semmns 6640
- semmnu 660
- semume 64

6 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 - shmmni 512
- shmmax 1GB(0x40000000)
- shmseg 120
- shmem 1
- swchunk 4096

1.4.2 HP-UX 11.i

bufpages 0
dbc_max_pct 3-10% system memory (<= 128MB)
dbc_min_pct 2-5% system memory
ksi_alloc_max (nproc*8)
maxusers 300
max_thread_proc 1024
maxdsiz 1GB
maxdsiz_64 2GB
max_files 2048
max_files_lim 2048
maxssiz 128MB
maxssiz_64 1GB
maxtsize 128MB
maxswapchunk 16384 (PA-RISC only)
maxuprc ((nproc*9)/10)
msgmap (2+msgtql)
msgmni nproc
msgseg 32767
msgtql nproc
msgssz 8
msgmnb 32768
msgmax 32768
nclist 3300
nbuff 0
ncsize (ninode+vx_ncsize) (PA-RISC)
ncsize (ninode+1024) (Itanium)
nfile (15*nproc+2048)
nflocks nproc
ninode (8*nproc+2048)
nkthread (((nproc*7)/4)+16)
nproc 4096
npty 128

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 7

 nstrpty 128
semmap (semmni+2) (PA-RISC only)
semmni nproc
semmns (semmni*2)
semmnu (nproc-4)
semvmx 32767
semaem 16384
semume 512
shmmax 1GB(0x40000000)
shmem 1
shmmni 512
shmseg 120
swchunck 4096
swapmem_on 1
vps_ceiling 64

1.5 Enable correct network services

In order to allow new releases of firmware for SNMP Equipment enable Anonymous FTP services
using SAM Networking and Communications Network services.

1.6 Provide correct codewords and licenses

Installation of NMS5UX requires a codeword that is requested from

NMS5UX - from SIAE Microelettronica S.P.A.

OpenView NNM ( 6.2 or 7.5) - for HP on the specific forms (*) only for NMS5UX

Also a license for Oracle Standard Edition ( rel 8i or 10.g ) is needed.

1.7 Install and configure sw components

See Chapter 2 for detailed information

8 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 1.8 Create NMS5UX environment and users

See Chapter and 2, 3 and 4 for detailed information

1.9 Start and stop NMS5UX base processes

See Chapter 5 for detailed information

1.10 Backup and restore information

See Chapter 10 for detailed information

1.11 Maintaining NMS5UX

To ensure the conditions demanded for the correct operation of NMS5UX do not loose their validity
along with system utilisation, the System Administrator must take care of Alarm History dimension,
file system occupation, log files dimension or looping processes.

1.12 Troubleshooting

See Chapter 14 for detailed information

1.13 Shutdown/Restart HP Server

See Annex C for detailed information

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 9

 1.14 Data Backup Tools and Policy

See Annex D for detailed information

10 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 2. INSTALLING NMS5UX

2.1 Unloading NMS5UX directories

If you are using a tape follow this procedure:

Insert the NMS5UX rel 6.x.x cassette in server tape drive and enter the following
commands:
cd /opt
tar xv

If you are using a CD follow this procedure:

Insert CD ROM for NMS5UX rel 6.x.x in server tape drive, mount it on a local file system
(i.e /mnt_cdrom):
cd /opt
copy /mnt_cdrom/nms_install_6xx.tar.z nms_install_6xx.tar.Z
uncompress nms_install_6xx.tar.Z
tar xvf nms_install_6xx.tar ./nms5ux
rm nms_install_6xx.tar

WARNING
Before going further with the installation of NMS5UX please verify you have the software activation
codewords from SIAE.

2.2 Setting the environment

Configuring default parameters

Set the default values for some NMS5UX system parameters executing the command:
cd /opt/nms5ux/install
./nms5ux_createlink.sh

Codewords

Activate the NMS5UX codewords provided by SIAE by creating and editing the file
/opt/tmn5ux/.tmn5ux.cw
/opt/tmn5ux/.ems6d.cw

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 11

 Editing ad hoc files
In the following, <machine name> represents the computer name where the Agent part of NMS5UX
runs on; in most cases both Agent and Manager components of NMS5UX are installed on the same
machine.

The machine name must be the same as referenced to in the /etc/hosts file.

The "port_tab" file contains as many lines as the number of workstation RS232 asynchronous
serial lines to be used for the management of the network elements ; each line contains the
port identification number and the relevant Unix device file
Rename port_tabHOSTNAME file present in dir /opt/tmn5ux/agent to file port_tab<machine
name> and then edit it to correctly map each serial port with its correspondent device file:
Use the command
-ioscan -f -n -Ctty
to get the correct device file to insert in the previous file

Edit the new file substituting each entry with the relevant device file name.

The "rapi.cfg" file allows the NMS5UX software to identify the computer referenced to as
machine name; it contains two lines defining the computer name and IP address that can be
normally left set to 0.0.0.0.
Edit the new file and enter the current machine name (IP address only if SIAE support
suggest to insert it).

Open the file /etc/services and append the following lines, required by the software that
manages communication with ComServers and by Remote Graphical Application:
r_hdlc 4210/tcp
s_hdlc 4211/tcp
Z_MM 22377/tcp
Z_BMF 22378/tcp
Z_EB 22379/tcp
Z_RMSG 22380/tcp
Z_SPMD 22381/tcp
Z_DB 22382/tcp
Z_EMS6D 22385/tcp
Z_EXTMA 22386/tcp
RemPortSNMP 22400/tcp
RemPort 22300/tcp
RemPortLegacySwdl 22600/tcp
RemPortRm 22700/tcp
SmitPort 22500/tcp
OvTrapd 22800/tcp
RemManager 22900/tcp
RemPortDataStore 22950/tcp
Siaew 24000/tcp
SiaewEvn 24100/tcp

If you find any port ( in particular the values "4210" and "4211" ) already used in the file,
please contact SIAE Microelettronica.

12 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 Edit /opt/nms5ux/local_env/Nms5uxProfileSuperuser and file
/opt/nms5ux/local_env/Nms5uxProfileUser and properly modify the line which sets variables
TMN5DR and EMS6D and put them to result of uname -n Unix command.

Edit /opt/nms5ux/conf/app-defaults/Nms5ux and properly modify the line which sets the
*ipHost variable and enter the IP ADDRESS of your workstation. In same file look for variable
clientList and set it to result of uname a unix command followed by ;.

Add environment variables necessary for running NMS5UX to the root user .profile file; edit
file /.profile and enter new line:
. /opt/nms5ux/local_env/Nms5uxProfileSuperuser

Log out and then login again as root in order to set the current environment variables.

Open the file /.dtprofile and activate the DTSOURCEPROFILE=TRUE line by uncommenting the
correspondent line. This tells the CDE graphical environment to read the environmental
settings contained in each user's .profile file.

Repeat the same operation for file /etc/skel/.dtprofile

Edit file /etc/skel/.profile and add line:

. /opt/nms5ux/local_env/Nms5uxProfileUser

Installing OpenView

N.B.: This section is intented to be valid only for NMS5UX application

Use appropriate OpenView NNM Installation CD to install application following standard procedure.
Require and activate a correct codeword from HP.

After having completed OpenView Installation please execute following modification:

If are using a separate file system /nmsData for Oracle and OpenView data please execute
following commands:
o A unix user root stop OpenView platform with command ovstop
o As unix user root create two new directories OV/etc and OV/var under
/nmsData file system
cd /nmsdata
mkdir p OV/etc
mkdir p OV/var
o As unix user root move directories /etc/opt/OV and /var/opt/OV under the two new
directories and then create a link to the new paths
cd /etc/opt
mv OV /nmsdata/OV/etc/.
ln s /nmsdata/OV/etc/OV OV
cd /var/opt
mv OV /nmsdata/OV/var
ln s /nmsdata/OV/var/OV OV

Edit file /usr/lib/X11/app-defaults/OVw and modified values for following resources

according to the ones reported below.
o OVw*testingStatusColor: #ffff9292aaaa

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 13

 o OVw*restrictedStatusColor: #aaaa6d6d5555
o OVw*disabledStatusColor: #666633330000
o OVw*unknownStatusColor: #55559292ffff
Before setting new values we recommend to comment the current ones using the character
! at the beginning of the commented line.

Installing Oracle 8.i

Create Unix group dba using SAM.

Create Unix user oracle using following procedure

Create the new oracle Unix user via SAM (new user must belong to Unix group dba). Home
directory for this user should be /opt/oracle/product/8.1.7

Oracle databases locations: in preconfigured files for NMS5UX oracle environment variables
are supposed to be :
ORACLE_HOME: /opt/oracle/product/8.1.7
ORACLE_BASE: /opt/oracle
ORACLE_SID: NSM5UX
NLS_LANG: AMERICAN_AMERICA.WE8ISO8859P1
N.B. Any differences with respect to those values must be reported in files:
/opt/nms5ux/local_env/Nms5uxProfileSuperuser and
/opt/nms5ux/local_env/Nms5uxProfileUser.

Check that the file $ORACLE_HOME/.profile exists and then edit it adding after the line:
. /opt/nms5ux/local_env/Nms5uxProfileUser
the new line
unset TWO_TASK

Login as Unix user oracle and install Oracle to run as a DBMS Server.

In Annex A you find a brief explanation on how to install Oracle 8.i from CD

N.B.: Oracle patch that upgrades release up to 8.1.7.4 must be also installed on server.

Installing Oracle 10.g

Create Unix group dba using SAM.

Create Unix user oracle using following procedure

Create the new oracle Unix user via SAM (new user must belong to Unix group dba). Home
directory for this user should be /opt/oracle/product/10.1.0

Oracle databases locations: in preconfigured files for NMS5UX oracle environment variables
are supposed to be :
ORACLE_HOME: /opt/oracle/product/10.1.0

14 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 ORACLE_BASE: /opt/oracle
ORACLE_SID: NSM5UX
NLS_LANG: AMERICAN_AMERICA.WE8ISO8859P1
ORA_NLS33 $ORACLE_HOME/ocommon/nls/admin/data ( Itanium only )

N.B. Any differences with respect to those values must be reported in files:
/opt/nms5ux/local_env/Nms5uxProfileSuperuser and
/opt/nms5ux/local_env/Nms5uxProfileUser.

Check that the file $ORACLE_HOME/.profile exists and then edit it adding after the line:
. /opt/nms5ux/local_env/Nms5uxProfileUser
the new line
unset TWO_TASK

Login as Unix user oracle and install Oracle to run as a DBMS Server.

In Annex B you find a brief explanation on how to install Oracle 10.g from CD.

N.B.: Oracle patch that upgrades release up to 10.1.0.3.0 is also recommended on server.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 15

 Installing Acrobat Reader to visualize help

As Unix user root change directory to /opt/nms5ux/help

Execute command
gunzip hpux-rs-405.tar.gz
tar xvf hpux-rs-405.tar
cd HPUXRS.install
./INSTALL
type accept to accept the terms and conditions license agreement
press >enter< to confirm directory installation
Enter installation directory for Acrobat 4.0 [/opt/Acrobat4]
press >enter< to create directory:
Directory "/opt/Acrobat4" does not exist.
Do you want to create it now? [y]
cd /opt/nms5ux/help
rm -r HPUXRS.install
gzip hpux-rs-405.tar

Installing SNMP Libraries

N.B.: This section is intented to be valid only for NMS5UX-B application

As Unix user root change directory to /opt/nms5ux/install/snmp_libs

Execute command
gunzip libnetsnmp.tar.gz
tar xvf libnetsnmp.tar ./libs
gzip libnetsnmp.tar
cd libs
mv libnetsnmp* /usr/local/lib/.

Configuring NMS5UX

Login as unix user Oracle and:

Startup oracle listener and NMS5UX database with commands:
N.B.: Before executing following commands please verify that file /etc/oratab has
been correctly modified as described in ANNEX-A/B at the end of NMS5UX Oracle
Database procedure.
cd $ORACLE_HOME/bin
./lsnrctl start
dbstart

16 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 As unix user root execute the following scripts sequence and monitor possible malfunctions
(failure in dropping database tables is not to be considered as an error):
./nms5ux_openviewregister.sh (*) only for NMS5UX
./nms5ux_createdb.sh

Create Unix group nms5ux using SAM.

Create Unix user nms5ux using following procedure

Create the new nms5ux Unix user via SAM (new user must belong to Unix group
nms5ux).

Edit file /home/nms5ux/.profile and substitute the line

. /opt/nms5ux/local_env/Nms5uxProfileUser
with the line
. /opt/nms5ux/local_env/Nms5uxProfileSuperuser

Log out and log in as the new user nms5ux.

change directory to /opt/nms5ux/start

start application ./nmsWinMenu

stop/restart Oracle and then stop/restart NMS5UX Platform (see chapter 5 for details in using
nmsWinMenu application)

for NMS5UX

q from an hpterm enter commands

cd /opt/nms5ux/install
./nms5CreateFirstMap.sh

q select Map->Properties Menu Item setting Propagate most critical as Compound Status

q enter Siae World (call SIAE to get the first login and password) and create a new
Nms5ux User (Menu Option->System Users) related to Unix user nms5ux with privileged
Superuser creating new map nms5ux.

for NMS5UX-B

q from an hpterm enter commands

cd /opt/nms5ux/bin
./lxMapManager map nms5ux &

q (call SIAE to get the first login and password) Enter main map and create a new
Nms5ux User (Menu Option->System Users) related to Unix user nms5ux with privileged
Superuser creating new map nms5ux.

Log out; from now on, you can log into your Unix system as the nms5ux user and run
NMS5UX by entering the following command:
cd /opt/nms5ux/start
./nmsWinMenu

Creating other NMS5UX users

To create other accounts for NMS5UX use following procedure:

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 17

 Create a new Unix (i.e. peter) user via SAM (new user must belong to Unix group user).

As NMS5UX Superuser create a new user from NMS5UX System User application, associated
to new Unix user (peter) with desired privileges and map.

Log out from workstation and log in as the new user peter.

change directory to /opt/nms5ux/start

start application ./nmsWinMenu

18 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 3. CONFIGURING A CLIENT-SERVER ARCHITECTURE

N.B.: This section is intented to be valid only for NMS5UX application

N.B.: YOU HAVE TO PERFORM THESE STEPS ONLY IF YOU HAVE A CLIENT_SERVER
ARCHITECTURE, OTHERWISE SKIP THIS SECTION

NMS5UX can be configured to run in a client-server architecture. To do this you need a workstation
configured to run as a server and at least another workstation to run as a client. This architecture
saves CPU demand on Server machine and X-protocol messages on your LAN; only a few messages
will be exchanged between client and server to get DB Data.
On Server workstation there will be all OpenView, Oracle Server and NMS5UX base platform
processes. Graphical and Oracle data will be kept only on this server.
On Client workstation there will be all OpenView base processes, an Oracle DBMS client platform and
a NMS5UX client platform.
You will need to perform a complete OpenView and NMS5UX installation on both server and client
workstation.
On server workstation you will have to perform a DBMS Server installation while on client youll have
to install a DBMS client.
Server workstation must be configured following the standard procedures to install NMS5UX and
Oracle.
Register new process rmsg to be started by ovstart using command (as root Unix user):
ovaddobj /opt/nms5ux/conf/lrf/rmsg.lrf
On server machine, export via NFS these two directories:
/etc/opt/OV/share
/var/opt/OV/share
/opt/nms5ux
adding client workstation name in Access List for User Root.
On client workstation you have to execute following commands:
- mount server_name:/etc/opt/OV/share /mnt/server_name/etc/opt/OV/share

- mount server_name:/var/opt/OV/share /mnt/server_name/var/opt/OV/share

- mount server_name:/opt/nms5ux/cmip_world/manager/db /opt/nms5ux/cmip_world/manager/db

- mount server_name:/opt/nms5ux/cmip_world/manager/app-defaults /opt/nms5ux/cmip_world/manager/app-defaults

- mount server_name:/opt/nms5ux/cmip_world/agent/sw_download /opt/nms5ux/cmip_world/agent/sw_download

- mount server_name:/opt/nms5ux/cmip_world/conf /opt/nms5ux/cmip_world/conf

- mount server_name:/opt/nms5ux/conf /opt/nms5ux/conf

- mount server_name:/opt/nms5ux/err_log /opt/nms5ux/err_log

N.B.: do it using SAM to set them permanent to every machine reboot.

- /opt/OV/bin/ovwsetupclient /mnt/server_name
Modify file /etc/opt/OV/share/conf/ovwdb.auth on server workstation to accept connection by any
user of client machine (i.e. add line client_name + )

To configure Oracle to share data between server and client, use netasst ( Oracle 8.i) or netmgr
(Oracle 10g) utility to configure a new Service in Service Naming section characterized by following
parameters:

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 19

 Service Identification
Service Name: NMS5UX
Connection Type: Database Default

Address Configuration:
Protocol TCP/IP:
Hostname: <server hostname>
Port Number: 1521:
Do it both on client and server machine.

Using the same application on server machine you also have to configure a new listener location
address and new database services having the following parameters (if they dont already exist):

Listener Location:
AddressX
Network Address:
Protocol: TCP/IP
Host: <server_hostname>
Port: 1521

Database Services:
DatabaseX
Global Database Name: NMS5UX
Oracle Home Directory: /opt/oracle/product/10.1.0
SID: NMS5UX

On server workstation edit file /opt/nms5ux/conf/app-defaults/Nms5ux, search for resource

*clientList and add to the list of managed server after the localhost indication, all client names
with each element separated by semicolons. An example is reported below:
*clientList: localhost;client1;client2;
On client workstation edit file /opt/nms5ux/local_env/Nms5uxProfileUser and
/opt/nms5ux/local_env/Nms5uxProfileSuperuser to set variables TMN5DR and EMS6D to <server
hostname>.
To start platform on both server and client machine follow these step (use nmsWinMenu tool on both
client and server workstation).
First of all youll have to start Oracle Platform and NMS5UX Platform on server machine. Afterwards
start NMS5UX platform on client machine.
You can enter graphical interface on both machines using menu label
7 - NMS5UX Application Login

N.B.
Unix group nms5ux and Unix user nms5ux must have the same ID on both server and
client machine.

20 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 4. CONTROLLING ACCESS TO NMS5UX

The NMS5UX system can be started at various operating levels; each level (in a bottom-up
sequence) gives the operator a growing visibility over NMS5UX functionality, enabling the use of
options, procedures etc.

The NMS5UX system has 5 operative levels:

Superuser Is the administrator of the system. Only this user can create, delete or modify
users, passwords and their operating level.

Privileged
Advanced
Normal
Entry These four levels are assigned with the visibility of only some of the NMS5UX
system functions

Review the Appendix section of the NMS5UX users manual for complete listing of all functions
available for each level.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 21

 5. USING NMSWINMENU TO START AND STOP NMS5UX

NMS5UX activity takes place by mean of a pool of daemons that, interacting with each other perform
all the communications, data management and event handling tasks.
This pool of processes needs to be active to run NMS5UX

/* *************************************** */
/* HOW TO USE nmsWinMenu */
/* *************************************** */

NMS5UX from rel 6.1 has a new graphical application to start and stop all the processes needed to
run the system.

If you want to use this script to start Oracle you must know password for unix user "oracle".
If you want to use this script to start NMS5UX you must know password for unix user "root".

Otherwise if you just want to start NMS5UX graphical interface you can be the Unix user you have
configured (see the last part of this document).

How to start the script:

- cd /opt/nms5ux/start
- ./nmsWinMenu

A graphical interface will be displayed with following items:

Startup Functions
Shutdown Functions
Check Functions
Proxy Functions
OSI Stack functions
System Utility
NMS5UX application Login
NMS5UX Application Login Read/Only

22 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 If you select Shutdown Functions a new interface is displayed with following icons
Oracle Platform Restart (to startup Oracle daemons)
ALL OpenView&NMS5UX platform Stop&Restart (to restart OpenView and NMS5UX
daemons) (*) only in NMS5UX use this function to perform a normal application
shutdown.
ALL NMS5UX platform Stop&Restart (to restart all NMS5UX daemons) (*) in NMS5UX-B
use this function to perform a normal application shutdown.
Legacy NMS5UX platform Stop&Restart (to restart only legacy part of NMS5UX daemons)
Processes soft restart (to restart only not running daemons)

If you select Startup Functions a new interface is displayed with following icons
Oracle Platform Stop (to stop Oracle daemons)
ALL OpenView&NMS5UX platform Stop (to stop OpenView and NMS5UX daemons). (*)
only in NMS5UX use this function to perform a normal application shutdown.
ALL NMS5UX platform Stop (to stop all NMS5UX daemons). (*) in NMS5UX-B use this
function to perform a normal application shutdown.
Legacy NMS5UX platform Stop (to stop only legacy part of NMS5UX daemons)

If you select Check Functions a new interface is displayed with following icons
Oracle Check Platform (to check Oracle daemons)
NMS5UX Check platform (to check NMS5UX daemons)

If you select Proxy Functions a new interface is displayed with following icons (Significant only if you
have NMS5UX proxy application installed)
Proxy Startup (to startup all NMS5UX proxy daemons)
Proxy Shutdown (to stop all NMS5UX proxy daemons)
Proxy Check (to check all NMS5UX proxy daemons)

If you select OSI Functions a new interface is displayed with following icons (Significant only if you
use an SIAE OSI interface installed)
OSI Stack Check (to check OSI daemons)
OSI Stack Routing Table Reload (to reload from NMS5UX DB IP-OSI mapping information)

If you select System Utility a new interface is displayed with following icons.
N.B. All these functions must be used with SIAE Support to investigate on possible
NMS5UX application fault.

Select NMS5UX Application Login to start a normal NMS5UX graphical session.

Select NMS5UX Application Login R/O to start a NMS5UX graphical session with read/only
priviledges.

Before the NMS5UX graphical session startup, if the user have been configure to be at least
priviledge, it will be ask which map he want to open. Press >enter< to start on default map,
otherwise enter desired map name.

In a client-server architecture, the functions of this MENU change from client to server and perform
different operations to start and stop the Oracle and NMS5UX Platforms . This will be hidden to user
and will depend on a configuration parameter.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 23

 6. LOCALIZATION

If you want to change the localization of your workstation you have to modify the default fonts used
by NMS5UX application:
1. Remove file /etc/kbdlang (if you need to modify you keyboard type)
2. copy ksh in /sbin directory
3. Using SAM modify Start-up program for root and all NMS5UX Unix user, setting /sbin/ksh
4. Shutdown your workstation
5. Change your keyboard (if you need to modify your keyboard type)
6. Select the right keyboard type when you are asked for (only if you removed /etc/kbdlang
file)
7. From CDE login window, select button Option->Language and choose the correct language
(i.e.: es_ES.iso88591)
8. change directory to /usr/lib/X11/fonts and choose the character set you need. Change
directory to character set/75dpi (i.e.: cd iso8859.1/75dpi)
9. copy /usr/dt/config/Xconfig file in /etc/dt/config
10. edit /etc/dt/config/Xconfig file and uncomment line
Dtlogin*language: selected language (i.e.: es_ES.iso88591)

24 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 7. UPDATING NMS5UX RELEASE

Each release of NMS5UX is related also to specific versions of HP-UX, and Oracle. So, when updating
NMS5UX it could be necessary to upgrade the other software components as specified also.

NMS5UX is not certified to work with software component

versions different from those specified.

The upgrading process of NMS5UX takes place in different ways dependant on the amount of new
features found in the new release
The simplest form of upgrade will require just an update of the applications and/or base platform
processes so that a simple file substitution will suffice

A more complex procedure has to take place in the case where a new NMS5UX release requires a
modification to the database structure; in this case it advisable to backup the information previously
stored.

In this case youll have to perform the following procedure:

SIAE will prepare script files to upgrade the structure of the tables of your db from
your old version to the new one.

Run these script files on your target machine in order to obtain the new structure
with the old content

SIAE will supply a tape containing the new executable files and a complete set of instructions to
follow to upgrade your system and your data.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 25

 8. CUSTOMIZING NMS5UX

The customization of the NMS5UX system consists in the re-definition of some of the parameters
used by SIAE applications.
The following tables lists some of the system parameters that might be of any interest for the
system administrator; all of them are contained in the 2 files:
/opt/tmn5ux/manager/app-defaults/Tmn5ux (*) only for NMS5UX
/opt/nms5ux/conf/app-defaults/Nms5ux
/opt/nms5ux/conf/app-defaults/Nms5lx (*) only for NMS5UX-B
In any case we suggest that modification of parameters present in these files should be done with
support of SIAE personnel.
In file /opt/nms5ux/conf/app-defaults/Nms5ux you will find following parameters

Reference string Meaning Default value Value range

DateFormat It represents the format 1 - ddmmyyyy 0 - Extended 1

used to display date/time - ddmmyyyy 2
in applications - mmddyyyy 3
- yyyymmdd

MaxRecPrim It represents the max 100 >0

number of PM primary
record to be exported

MaxRecGio It represents the max 100 >0

number of PM daily record
to be exported

nms5trapd*autoDeleteTimeOffsetHistory It represents how many 90 >0

days of Alarm History are
maintained in DataBase

nms5trapd*maxRecordInHistory It represents how many 50000 >0

Alarms are maintained in
DataBase

nms5trapd*maxRecordInTrLog It represents how many 1000 >0

log records are maintained
in DataBase

*warningEvents:
It represents the max 1000 >0
number of records loaded
by alarm history browser
without any warning
message

*maxEvents:
It represents the max 5000 >0
number of records loaded
by alarm history browser

*MaxSmnpSameTime:
It represents the max 10 >0
numbers of SNMP
operation managed
simultaneously by
basement process: (e.g..
polling operation, Alarm

26 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 Reference string Meaning Default value Value range

Realignment )

*NumEqReadTable:
It represents the number 10 >0
of equipments managed
each TimeReadTable
seconds to execute SNMP
operations. If this number
is higher then
MaxSnmpSameTable
operation on NEs are
queued.

*TimeReadTable:
It represents the numbers 5 >0
of seconds when basement
reloads NumEqReadTable
equipment to be managed
for polling or other SNMP
operations (e.g. Software
Download). For example if
you want to set:

7 NEs polled each 5

seconds write:

MaxSmnpSameTime: 7

NumEqReadTable: 7

TimeReadTable: 5

In file /usr/tmn5ux/manager/app-defaults/Tmn5ux you will find following parameters

Reference string Meaning Default value Value range

ExpirationTimeOffset It Represents the period in days 0 >0

how often the NMS5UX operator
is asked to refresh its password.
The value 0 means no refresh
required

AckLightLom Set to 1 it sets NMS5UX to 0 0 No

visualize with a star above the 1- Yes
Equipment symbol the LOM
presence not Ack condition

AckLightAlarms Set to 1 it sets NMS5UX to 0 0 No

visualize with a star above the 1- Yes
Equipment symbol the Alarms
presence not Ack condition

AckLightUndefined Set to 1 it sets NMS5UX to 0 0 No

visualize with a star above the 1- Yes
Equipment symbol the Incorrect
Upload not Ack condition

AckLightFlash Set to 1 it sets NMS5UX to 0 0 Star

modify the visualization of above 1 Flash
contions from a star above the
Equipment symbol with a symbol
flashing

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 27

 In file /opt/nms5ux/conf/app-defaults/Nms5lx you will find following parameters

Reference string Meaning Default value Value range

expirationTimeOffset It Represents the period in days 0 >0

how often the NMS5UX operator
is asked to refresh its password.
The value 0 means no refresh
required

ackLct Set to 1 it sets NMS5UX to 0 0 No

visualize with a star above the 1- Yes
Equipment symbol the LOM
presence not Ack condition

ackAlr Set to 1 it sets NMS5UX to 0 0 No

visualize with a star above the 1- Yes
Equipment symbol the Alarms
presence not Ack condition

ackUndef Set to 1 it sets NMS5UX to 0 0 No

visualize with a star above the 1- Yes
Equipment symbol the Incorrect
Upload not Ack condition

28 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 9. MODIFYING WORKSTATION IP-ADDRESS

N.B. In case of NMS5UX application you have to migrate you HP OpenView NNM license to
the new IP Address.

If you need to modify your workstation IpAddress please follow this procedure:

stop NMS5UX Platform

stop Oracle Platform

modify workstation IpAddress

edit file /usr/tmn5ux/agent/rapi.cfg modifying LOCAL_IP_ADDRESS value

restart Oracle Platform

modified all Oracle network parameters using application netasst for Oracle 8.i or netmgr
for Oracle 10g.

execute command /opt/nms5ux/tools/routeTab_generator

edit file /opt/nms5ux/conf/app-defaults/Nms5ux and modified value of variable *ipHost

with new WS ip address.

edit file /opt/nms5ux/conf/SiaeRoutingTable.manual and modified all routing information

changed by Ip Addresses modification

restart NMS5UX platform.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 29

 10. MODIFYING WORKSTATION NAME

If you need to modify your workstation name please follow this procedure:

stop NMS5UX Platform

stop Oracle Platform

modify workstation hostname

restart Oracle Platform

only in case of HP OpenView NNM edit file

/var/opt/OV/share/database/openview/ovserver and insert new hostname.

edit file /opt/nms5ux/cmip_world/agent/rapi.cfg and enter new hostname value for variables

LOCAL_NAME

edit file /opt/nms5ux/local_env/Nms5uxProfileUser

/opt/nms5ux/local_env/Nms5uxProfileSuperuser and and enter new hostname value for
variables

EMS6D

TMN5DR

SNMP_EXECUTOR

restart NMS5UX platform.

30 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 11. BACKING UP AND RESTORING NMS5UX DATABASE

NMS5UX gives the operator the possibility to save his data for security; the system stores all
information regarding network topology and equipment configuration (Oracle NMS5UX database). In
addition, it is also possible to backup and restore the Alarm History or Performance Monitoring tables
only. It is recommended to perform a weekly backup, but take care of situations where a large
amount of changes occur in the network.
The "Database Backup" (and similarly the Alarm History backup) feature behave as described
below:

Step 1. Hard disk backup

In order to backup the system database tables contents onto the hard disk, the user has to select
the 'Backup to disk' toggle button and press the OK button which initiates the backup procedure. The
backed up files are created in the directory shown in the window.

Step 2. Tape backup

In order to backup the system database tables contents onto the tape, the user has to select the
'Backup to tape' toggle button and press the OK button which initiates the backup procedure.

Step3. Hard disk and tape backup

Select both the 'Backup to disk' and 'Backup to tape' toggle buttons and press the OK button which
initiates the backup procedure. The backed up files are created in the directory shown in the window
and then copied onto the tape.

In order to restore the Alarm History select the relevant menu item and enter a the filename as
requested; for the NMS5UX database files (tmn5ux database and OV files) you should follow these
steps:
login as root
stop NMS5UX platform processes
change directory /usr/tmn5ux/manager/tools
execute ./TmnDbRestore (*) only for NMS5UX
or
execute TmnDbRestoreUxB.sh (*) only for NMS5UX-B
restart NMS5UX platform processes
you don't need to be "root" any more
restart the graphical application

The Database backup procedure copies database files onto a specific directory and possibly onto a
tape.
The Restore database procedure restores database files for the directory only: it is not
possible to directly restore files from the tape: an explicit "tar xv" Unix command is
needed from root directory in order to restore files from tape to the specified directory.
(/opt/nms5ux/cmip_wolrd/manager/db/DbBackup)

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 31

 12. RESETTING NMS5UX DATABASES

The following procedure gives the NMS5UX administrator the ability to recover an abnormal situation
when a complete reset of the whole network is necessary.
N.B.: Following commands completely delete all NEs present in network.

Step1. Stop NMS5UX platform processes

Use /opt/nms5ux/start/nmsWinMenu

Step2. Resetting Oracle databases

Re-build the empty Oracle environment with:

cd /opt/nms5ux/install
./nms5ux_createdb.sh

Step3. Resetting Openview databases

N.B.: This section is intented to be valid only for NMS5UX application

Re-build the empty OpenView environment with:

cd /opt/nms5ux/install
./nms5ux_openviewresetdb.sh

Step4. Restart platform processes

Restart NMS5UX platform using nmsWinMenu

for NMS5UX

q from an hpterm enter commands

cd /opt/nms5ux/install
./nms5CreateFirstMap.sh

q select Map->Properties Menu Item setting Propagate most critical as Compound Status

q enter Siae World (call SIAE to get the first login and password) and create a new
Nms5ux User (Menu Option->System Users) related to Unix user nms5ux with privileged
Superuser creating new map nms5ux.

for NMS5UX-B

q from an hpterm enter commands

cd /opt/nms5ux/bin
./lxMapManager map nms5ux &

32 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 q (call SIAE to get the first login and password) Enter main map and create a new
Nms5ux User (Menu Option->System Users) related to Unix user nms5ux with privileged
Superuser creating new map nms5ux.

Log out; from now on, you can log into your Unix system as the nms5ux user and run
NMS5UX by entering the following command:
cd /opt/nms5ux/start
./nmsWinMenu

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 33

 13. CONFIGURING I/O SERIAL LINES

If you have planned to communicate with your network elements through an RS 232 connection you
need to know the names of the device files that manage the physical ports.
As previously shown in Chapter 2 these file names must be specified in the port_tab<WSNAME> file.
You must be careful in determining the exact device file names because of the great variety of cards
and multiplex boards associated to different HP workstation or server models.

If you need to use the RS232 ports of a machine different from the one NMS5UX is installed on you
are requested to:

Login as root

Ensure that your environment is similar to the one in the host server

Install the files:

/opt/tmn5ux/agent/bin/hdlc_server
/opt/tmn5ux/agent/bin/port_server
/opt/tmn5ux/agent/port_tab<WSNAME> (cfr. Section 2.4.)
In the most cases SAM will be enough for getting machine device file names

Start the hdlc process by typing the following commands as root:

cd /opt/tmn5ux/agent/bin/
nohup hdlc_server &

34 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 14. TROUBLESHOOTING

14.1 NMS5UX architecture

During NMS5UX system use each operator should pay close attention to the tasks he is performing
so in the case of a problem, it is possible to recover the system as soon as possible.

In any case it is absolutely necessary to clearly identify the particular application that is currently
causing the problem: Oracle database, NMS5UX managers or base platform processes.

This kind of skill cannot be automatically achieved; a lot of experience needs to be gathered to
understand NMS5UX architecture, interpreting log files and contacting SIAE technicians at the
following telephone number:

siae microelettronica 0039-2-273251

The next sections and descriptions can be the starting point in NMS5UX architecture comprehension.
Please pay close attention to them.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 35

 14.2 TROUBLESHOOTINGS

In case of a problem, you are kindly requested to give SIAE precise and clear information in order to
minimize response time.
First of all, try to discriminate between the nature of the problem; if you suspect the trouble is a
bug,

Try to reproduce the malfunctioning situation

Compile and send a detailed customer trouble report

The clearer the problem description, the quicker SIAE will be able to provide a patch to resolve the
problem.

If you find problems regarding base processes or communication with network elements

Identify the specific process that is faulty using nmsWinMenu NMS5UX check
processes function

Try to recover for example stopping and restarting base processes

If this is unhelpful please store HPUX and the NMS5UX log files in a tape and send them to SIAE for
examination, using procedure
su - root
cd /opt/nms5ux/tools
./save_nms5ux_log.sh
then send SIAE the files NMS5.LOG.Z and TMN5.LOG.Z

36 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 15. ANNEX-A

/*--------------------------------------------------------------------------------------*/
* PREPARING FOR ORACLE INSTALLATION *
/*--------------------------------------------------------------------------------------*/
Execute following commands to install Oracle rel 8.1.7.0.0 on your server.

As root Unix user:

Execute commands:
nohup /usr/sbin/pfs_mountd &
nohup /usr/sbin/pfsd &
/usr/sbin/pfs_mount o xlat=unix /dev/rdsk/cxtxdx /cdrom

where /dev/rdsk/cxxxx is obtained with command

ioscan -fnC disk
looking for CD-ROM device

chown R oracle:dba /opt/oracle

/*------------------------------------------------*/

Login as oracle unix user

cd $ORACLE_HOME
umask 022
cd /cdrom

FOR CLIENT INSTALLATION

-----------------------
./runInstaller
select
. Oracle Client
then
. Administrator
then
. install

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 37

 FOR SERVER INSTALLATION
-----------------------
./runInstaller
select
. Oracle
then
. custom
deselect from installation list
- HTTP
- Security
- Legato
- Java

Set dba/dba as administrator.

Chose to create a new database with files under directory
/nmsData/oradata (if you are placing Oracle data on a separate file system /nmsData respect
to /opt )
or
/opt/oradata (if you are placing Oracle data under /opt file system)

N.B. Please check that in all following steps all references to /.../oradata directory are
correctly linked to desidered path ( /nmsData/oradata or /opt/oradata). In particoular
check the path for all following files:
Control Files
All Tablespaces Files
o System
o Tools
o Users
o Rollback
o Idex
o Temporary
Redo Log Files

Then install and when asked choose

. run $ORACLE_HOME/root.sh
. netconfig
choose -> perform typical configuration
. upgrade migration
choose -> cancel
. create a database
choose -> custom
-> create new database file
-> multipurpose
-> concurrently connected user = 50
-> Dedicated Server Mode

38 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 -> choose to enable sqlplus help only
-> Global database name = NMS5UX
-> SID = NMS5UX
-> Compatible par = 8.1.0
-> Change Char Set = WE8ISO8859P1(both)
-> Cntrl Files ok
-> TABLESPACES
-> SYSTEM ok
-> TOOLS ok
-> USERS
change tablespace name into DATA and set size=1000MB;
set extents AUTOEXT=on and NEXT=100000KB;
set storage unlimited ON;
-> RBS ok
-> INDX
set size=1000MB;
set extents AUTOEXT=on and NEXT=100000KB;
set storage unlimited ON;
-> TMP ok
-> redo logs 1,2 3 size=5000k
-> checkpoint interval = 10000000
-> checkpoint timeout = 1800000
-> archive NOT ENABLE
-> shared pool size=90485760M
-> block buffer=40480

-> create now

(sys_account_password = change_on_install
system_account_password = manager )

Edit file /etc/oratab setting "Y" for NMS5UX DB to start

Configure script for starting/stopping Oracle at system boot/shutdown:

if it doesnt exist create file /sbin/init.d/oracle_script copying it from directory
/opt/nms5ux/install/oracle_db
cd /sbin/rc2.d
ln -s /sbin/init.d/oracle_script ./S950oracle
cd /sbin/rc0.d
ln -s /sbin/init.d/oracle_script ./K950oracle

Use netasst utility to modify ( or create if not already present) Service nms5ux in Service Naming
section characterized by following parameters:

Service Identification

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 39

 Service Name: NMS5UX
Connection Type: Database Default

Address Configuration:
Protocol TCP/IP:
Hostname: <machine ip address> (in dot notation)
Port Number: 1521:

Usually service is already created after installation but parameter hostname in Address Configuration
must be modified from value of hostname to value of ip address
In the same application if they dont already exist configure a new listener location address and a
new database services having following parameters:
Listener Location:
AddressX
Network Address:
Protocol: TCP/IP
Host: <machine_hostname>
Port: 1521

Database Services:
DatabaseX
Global Database Name: NMS5UX
Oracle Home Directory: /opt/oracle/product/8.1.7
SID: NMS5UX

Start database executing

dbstart

40 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 16. ANNEX-B

/*--------------------------------------------------------------------------------------*/
* PREPARING FOR ORACLE INSTALLATION *
/*--------------------------------------------------------------------------------------*/
Execute following commands to install Oracle rel 8.1.7.0.0 on your server.

As root Unix user:

Execute commands:
nohup /usr/sbin/pfs_mountd &
nohup /usr/sbin/pfsd &
/usr/sbin/pfs_mount o xlat=unix /dev/rdsk/cxtxdx /cdrom

where /dev/rdsk/cxxxx is obtained with command

ioscan -fnC disk
looking for CD-ROM device

chown R oracle:dba /opt/oracle

/*------------------------------------------------*/

Login as oracle unix user

cd $ORACLE_HOME
umask 022
cd /cdrom

Before executing ./runInstaller program verify Oracle databases locations: in preconfigured files for
NMS5-LX oracle environment variables are supposed to be :
ORACLE_HOME: /opt/oracle/product/10.1.0
ORACLE_BASE: /opt/oracle
ORACLE_SID: NSM5UX
NLS_LANG: AMERICAN_AMERICA.WE8ISO8859P1
ORA_NLS33 $ORACLE_HOME/ocommon/nls/admin/data ( Itanium only )

Edit files /etc/profile.d/oracle.* and configure the environment variables as reported above.

N.B. Any differences with respect to those values must be reported in file:
/opt/nms5ux/local_env/Nms5uxProfileUser.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 41

 FOR CLIENT INSTALLATION
-----------------------
./runInstaller
select
. Oracle Client
then
. Administrator
then
. install

FOR SERVER INSTALLATION

-----------------------
./runInstaller
select
. Oracle
then
. custom
deselect from installation list
- HTTP
- Security
- Legato
- Java

Set dba/dba as administrator.

At the end of the ./runInstaller execution create a new databases related to SID NMS5UX
placing files in directory /nmsData and using following settings:
-> custom
-> create new database file
-> multipurpose
-> concurrently connected user = 50
-> Dedicated Server Mode
-> choose to enable sqlplus help only
-> Global database name = NMS5UX
-> SID = NMS5UX
-> Compatible par = 8.1.0
-> Change Char Set = WE8ISO8859P1(both)
-> Cntrl Files ok
-> TABLESPACES
-> SYSTEM ok
-> TOOLS ok
-> USERS
change tablespace name into DATA and set size=1000MB;
set extents AUTOEXT=on and NEXT=100000KB;

42 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 set storage unlimited ON;
-> RBS ok
-> TMP ok
-> create new tablespace INDX
set size=250MB;
set extents AUTOEXT=on and NEXT=10000KB;
set storage unlimited ON;
-> redo logs 1,2 3 size=5000k
-> checkpoint interval = 10000000
-> checkpoint timeout = 1800000
-> archive NOT ENABLE
-> shared pool size=90485760M
-> block buffer=40480
-> create now
(sys_account_password = change_on_install
system_account_password = manager )

N.B.: In case your server is based on Itanium architecture copy directory

/opt/nms5ux/install/ocommon under directory $ORACLE_HOME executing command as
uni user oracle:
cd /opt/nms5ux/install
cp r ocommon $ORACLE_HOME/.

Edit file /etc/oratab setting "Y" for NMS5UX DB to start

Configure script for starting/stopping Oracle at system boot/shutdown:

if it doesnt exist create file /sbin/init.d/oracle_script copying it from directory
/opt/nms5ux/install/oracle_db
cd /sbin/rc2.d
ln -s /sbin/init.d/oracle_script ./S950oracle
cd /sbin/rc0.d
ln -s /sbin/init.d/oracle_script ./K950oracle

Use netmgr utility to modify ( or create if not already present) Service nms5ux in Service Naming
section characterized by following parameters:

Service Identification
Service Name: NMS5UX
Connection Type: Database Default

Address Configuration:
Protocol TCP/IP:
Hostname: <machine ip address> (in dot notation)
Port Number: 1521:

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 43

 Usually service is already created after installation but parameter hostname in Address Configuration
must be modified from value of hostname to value of ip address
In the same application if they dont already exist configure a new listener location address and a
new database services having following parameters:
Listener Location:
AddressX
Network Address:
Protocol: TCP/IP
Host: <machine_hostname>
Port: 1521

Database Services:
DatabaseX
Global Database Name: NMS5UX
Oracle Home Directory: /opt/oracle/product/10.1.0
SID: NMS5UX

Start database executing

dbstart

44 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 17. ANNEX-C

In this annex it is described the procedure to startup/shutdown HP server, Oracle and NMSUX
platform.
To manage all NMS5UX applications startup/shutdown procedures you have to use the nmsWinMenu
graphical application described in chapter 5.
In order to run nmsWinMenu execute following commands from a Unix shell:

cd /opt/nms5ux/start

./nmsWinMenu

17.1 NMS5UX Server - STARTUP procedure

In order to correctly startup HP Server and NMS5UX application execute following steps:

Switch the power on for the server and wait for the startup procedure to finish.

Start ORACLE platform

Start NMS5UX platform

Start PROXY functions

START ORACLE PLATFORM

To start ORACLE Platform execute following steps:

From NMSWINMENU select (with double click) STARTUP Functions: a new window appear;

From the STARTUP Functions window select (with double click) ORACLE Platform Restart
(if you are not logged as oracle user the system will ask you the oracle user password).

NOTE: If Oracle is configured to automatically start-up after a server reboot you get following
warning message:
Oracle processes are already running

START NMS5UX PLATFORM

To start NMS5UX platform execute following steps:

From NMSWINMENU select (with double click) STARTUP Functions: a new window appear;

From the STARTUP Functions window select (with double click)

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 45

 For NMS5UX
All OpenView/NMS5UX Platform Restart (if you are not logged as root user the system
will ask you the root user password)
For NMS5UX-B
All NMS5UX Platform Restart (if you are not logged as root user the system will ask you
the root user password)

START PROXY FUNCTIONS

To start PROXY functions execute following steps:

From NMSWINMENU select (with double click) PROXY Functions: a new window appear;

From the PROXY Functions window select (with double click) PROXY COLD Startup (if you
are not logged as root user the system will ask you the root user password).

17.2 NMS5UX Server - shutdown procedure

In order to correctly shutdown NMS5UX application and HP Server execute following steps:

Stop PROXY functions

Stop NMS5UX platform

Stop ORACLE platform

Shutdown the server

STOP PROXY FUNCTIONS

To stop PROXY functions execute following steps:

From NMSWINMENU select (with double click) PROXY Functions: a new window appear;

From the PROXY Functions window select (with double click) PROXY Stop (if you are not
logged as root user the system will ask you the root user password).

STOP NMS5UX PLATFORM

To stop NMS5UX platform execute following steps:

From NMSWINMENU select (with double click) SHUTDOWN Functions: a new window
appear;

From the SHUTDOWN Functions window select (with double click)

For NMS5UX
All OpenView/NMS5UX Platform Stop (if you are not logged as root user the system will
ask you the root user password).

46 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 For NMS5UX-B
All NMS5UX Platform Stop (if you are not logged as root user the system will ask you
the root user password).

STOP ORACLE PLATFORM

To stop ORACLE platform execute following steps:

From NMSWINMENU select (with double click) SHUTDOWN Functions: a new window
appear;

From the SHUTDOWN Functions window select (with double click) ORACLE Platform Stop
(if you are not logged as oracle user the system will ask you the oracle user password).

SERVER SHUTDOWN

From a UNIX shell enter the following command as Unix user root:

shutdown yh 0

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 47

 18. ANNEX-D

This annex describes the procedures for periodical NMS5UX Data backup and all the provided Data
restore policies.

18.1 DATA BACKUP PROCEDURES

NMS5UX application provides two different Data backup procedures:

A full Oracle and OpenView (* only for NMS5UX) Data backup

A reduced backup of a minimun set of data for Oracle database and a full backup for
OpenView (* only for NMS5UX) data base.
The differences between the two policies mainly regard the backup of alarm history and Performance
Monitoring data that are saved only with the first set of procedures.
On the other hand the second type of backup policy allows a minimum disk space occupation in front
of an almost complete data saving.
All files generated on disk with the previously described backup procedures can be saved on external
tape using a single or an incremental tar on tape backup. Both these procedures are described
below.

18.1.1 FULL DATA BACKUP PROCEDURES

All the script files implementing this backup policy are installed under directory:

/opt/nms5ux/cmip_world/manager/tools/FullBackupRestore
The backup files generated by this procedures are generated under a specific directory depending on
procedure used (see description below).
The structure of all these directories is always the same:
In case of NMS5UX it provides two subdirectories:

Ovdatabases: it contains a compressed file OVdatabases.tar.gz that is a tar of the directory

/var/opt/OV/share/databases/openview
containing the set of data files of OpenView database used by NMS5UX.

Tmn5uxDb: it contains a compressed file NMS_DB_BACKUP.dmp.gz that is the result of the

export operation for the data of Oracle user tmn which contains all NMS5UX data. A second
file NMS_DB_BACKUP.log is contained in directory and it is the log file of the export
operation.
In case of NMS5UX-B it provides one subdirectory:

Tmn5uxDb: it contains a compressed file NMS_DB_BACKUP.dmp.gz that is the result of the

export operation for the data of Oracle user tmn which contains all NMS5UX data. A second
file NMS_DB_BACKUP.log is contained in directory and it is the log file of the export
operation.

48 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 The set of procedures provides by full Data backup and restore policy includes two kinds of backup
operations:

The first type is a backup that generates disk files always on same directory where data are
overwritten each time the operation is invoked:
/opt/nms5ux/cmip_world/manager/db/DbBackup.0
The script file to be used to implement this kind of backup is
TmnSingleFullDbBackup.sh
while the script file to recover data from this backup is:
TmnSingleFullDbRestore.sh
The results of these operation are written in a log file
TmnSingleFullDb.log
that is switched to an old log file
TmnSingleFullDb.log.old
when its dimensions reaches 100kB
Warning:
This procedure requires that the generated files must be saved every time on
the tape and the tape must be periodically replaced (refer to the following
paragraph).
Otherwise any problem on the backup procedure could cause the data lost.

The second type is a backup that generates disk files in two different directories that are
cyclically used overwriting only older files. The two used directories are:
/opt/nms5ux/cmip_world/manager/db/DbBackup.1
/opt/nms5ux/cmip_world/manager/db/DbBackup.2
The script file to be used to implement this kind of backup is:
TmnAlternatedFullDbBackup.sh
The directory number used by last alternated backup operation is written in file
TmnAlternatedFullDirectoryNumber.txt
while the script file to recover data from this backup is:
TmnAlternatedFullDbRestore.sh #directory_number
where #directory_number is a parameter representing the number (1,2) related to directory
from which data must be recovered. In order to get right parameter to be used see file
TmnAlternatedFullDirectoryNumber.txt to see the directory number used by last backup and
information reported in log file to see the result of last backup operation.
The results of all previously described operation are written in a log file
TmnAlternatedFullDb.log
that is switched to an old log file
TmnAlternatedFullDb.log.old
when its dimensions reaches 100kB
Warning:
These second procedure set doesn't avoid to save the files on the tape, the only
advantage is that more time is available to identify backup problem.

Under directory FullBackupRestore there is subdirectory tools containing script files used by
previously described procedures.

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 49

 18.1.2 REDUCED DATA BACKUP PROCEDURES

All the script files implementing this backup policy are installed under directory:

/opt/nms5ux/cmip_world/manager/tools/ReducedBackupRestore
The backup files generated by this procedures are generated under a specific directory depending on
procedure used (see description below).
The structure of all these directories is always the same:
In case of NSM5UX-A it provides two subdirectories:

Ovdatabases: it contains a compressed file OVdatabases.tar.gz that is a tar of the directory

/var/opt/OV/share/databases/openview
containing the set of data files of OpenView database used by NMS5UX.

Tmn5uxDb: it contains a compressed file NMS_DB_BACKUP.tar.gz that is a tar of the files

resulting from the export operations of a minimum set of tables containing NMS5UX data
related to users and equipment configuration.
In case of NSM5UX-B it provides one subdirectory:

Tmn5uxDb: it contains a compressed file NMS_DB_BACKUP.tar.gz that is a tar of the files

resulting from the export operations of a minimum set of tables containing NMS5UX data
related to users and equipment configuration.

The set of procedures provides by reduced Data backup and restore policy includes two kinds of
backup operations:

The first type is a backup that generates disk files always on same directory where data are
overwritten each time the operation is invoked:
/opt/nms5ux/cmip_world/manager/db/ReducedDbBackup.0
The script file to be used to implement this kind of backup is
TmnSingleReducedDbBackup.sh
While the script file to recover data from this backup is:
TmnSingleReducedDbRestore.sh
The results of these operation are written in a log file
TmnSingleReducedDb.log
that is switched to an old log file
TmnSingleReducedDb.log.old
when its dimensions reaches 100kB
Warning:
This procedure requires that the generated files must be saved every time on the
tape and the tape must be periodically replaced (refer to the following paragraph).
Otherwise any problem on the backup procedure could cause the data lost.

The second type is a backup that generates disk files in two different directories that are
cyclically used overwriting only older files. The two used directories are:
/opt/nms5ux/cmip_world/manager/db/ReducedDbBackup.1
/opt/nms5ux/cmip_world/manager/db/ReducedDbBackup.2
The script file to be used to implement this kind of backup is
TmnAlternatedReducedDbBackup.sh
The directory number used by last alternated backup operation is written in file
TmnAlternatedReducedDirectoryNumber.txt
While the script file to recover data from this backup is:

50 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 TmnAlternatedReducedDbRestore.sh #directory_number
Where #directory_number is a parameter representing the number (1,2) related to
directory from which data must be recovered. In order to get right parameter to be
used see file TmnAlternatedReducedDirectoryNumber.txt to see the directory number
used by last backup and information reported in log file to see the result of last backup
operation.
The results of all previosly described operation are written in a log file
TmnAlternatedReducedDb.log
that is switched to an old log file
TmnAlternatedReducedDb.log.old
when its dimensions reaches 100kB
Warning:
These second procedure set doesn't avoid to save the files on the tape, the only
advantage is that more time is available to identify backup problem.
Under directory ReducedBackupRestore there is subdirectory tools containing some script files
used by previously described procedures.

18.2 SAVING AND RECOVERING DATA FROM TAPE

The procedures described in this sections just implement functionality to save/recover from tape the
information generated by Backup operations described in previous sections of this document. This
means they must be used in addiction to the desired backup procedure and they do not substitute
them at all.
All the script files implementing the functionalities to save and recover data from tape are installed
under directory:

/opt/nms5ux/cmip_world/manager/tools/BackupRestoreOnTape
In order to save backup information on tape you have to use one of the following
procedures depending of which kind of data backup you have implemented:

TmnSaveSingleFullDbOnTape.sh #deviceType: to save on tape the backup generated in

directory
/opt/nms5ux/cmip_world/manager/db/DbBackup.0
by script TmnSingleFullDbBackup.sh

TmnSaveAlternatedFullDbOnTape.sh #deviceType: to save on tape the backup generated in

directory
/opt/nms5ux/cmip_world/manager/db/DbBackup.#
by script TmnAlternatedFullDbBackup.sh. This procedure automatically save on tape the last
backup directory as get from file TmnAlternatedFullDirectoryNumber.txt

TmnSaveSingleReducedDbOnTape.sh #deviceType: to save on tape the backup generated in

directory
/opt/nms5ux/cmip_world/manager/db/ReducedDbBackup.0
by script TmnSingleReducedDbBackup.sh

TmnSaveAlternatedReducedDbOnTape.sh #deviceType: to save on tape the backup

generated in directory
/opt/nms5ux/cmip_world/manager/db/ReducedDbBackup.#
by script TmnAlternatedReducedDbBackup.sh. This procedure automatically save on tape the
last backup directory as get from file TmnAlternatedReducedDirectoryNumber.txt
The parameter #deviceType present in all previously described procedures, indicates whether on
incremental tape writing is required. This parameter can be set to two values:

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 51

 Simple: if information on tape is always overwritten

Incremental: if information on tape are written one after the other.

Obviuosly, in this second case, the number of writing operations that can be performed subsequently
on the same tape depends on backup data dimension and tape capacity.
All previous described procedures trace their activity in log file:

TmnSaveDbOnTape.log
that is switched to an old log file

TmnSaveDbOnTape.log.old
when its dimensions reaches 100kB.
In order to recover backup from tape you have to insert correct tape on device and then select
which kind of recover you desire depending on the how you saved information on tape

TmnRecoverBackupFromTape.sh: if you save information on tape not using incremental tape

writing

TmnRecoverBackupFromIncrementalTape.sh #backup_number: if you save information on

tape using incremental tape writing. The parameter #backup_number represent the position
on tape from which the backup must be extracted.
0: to extract first backup written on tape
1: to extract second backup written on tape
....
Both the two described recover procedures extract the information they found on tape and place
them on the original disk directory. After having extracted information you have to execute the
corresponding restore procedure as described in following section.
Both previous described procedures trace their activity in log file:

TmnRestoreDbFromTape.log
that is switched to an old log file

TmnRestoreDbFromTape.log.old
when its dimensions reaches 100kB

18.3 DATA RESTORE PROCEDURES

The data restore policy to be used in case of data corruption depends on the kind of
detected fault and on the kind of implemented backup policy.
The various scenarios that can lead to the need of a data restore can be summarized in two main
categories:

Necessity to reload data from an old backup for some reason ( lost of useful data, data
corruption detected inside NMS5UX application, etc)

Necessity to completely recreate Openview (* onlyd for NMS5UX) and Oracle NMS5UX due to
unrecoverable error on DB consistency ( caused for example by an unintentional file deletion
etc. ).
The first type of fault can be recovered following these steps:

Stop NMS5UX processes using appropriate command form NMS5UX Men under directory
/opt/nms5ux/start

52 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003

 Execute appropriate Data Restore procedure depending on implemented backup policy:
TmnSingleFullDbRestore.sh
TmnAlternateFullDbRestore.sh #directory_number
TmnSingleReducedDbRestore.sh
TmnAlternateReducedDbRestore.sh #directory_number
See previous paragraphs to see when to use each procedure depending on implemented
backup and to eventually recover data from tape in advance.

Restart NMS5UX processes using appropriate command form NMS5UX Men under directory
/opt/nms5ux/start
The second kind of fault can be recovered following these steps:

Stop NMS5UX processes using appropriate command form NMS5UX Men under directory
/opt/nms5ux/start

Stop Oracle processes using appropriate command form NMS5UX Men under directory
/opt/nms5ux/start

Login as Oracle unix user and delete NMS5UX database using application dbassist. From
graphical interface perform the following steps::
1. Select "Delete a database" option
2. Press button Continue
3. Select database instance NMS5UX
4. Press button Finish

Launch again application dbassist as unix user oracle to recreate NMS5UX database. Please
follow instructions described starting from the section create a database of the Annex A of
NMS5UX System Administrator Manual.

Execute appropriate Data Restore procedure depending on implemented backup policy:

TmnSingleFullDbRestore.sh
TmnAlternateFullDbRestore.sh #directory_number
TmnSingleReducedDbRestore.sh
TmnAlternateReducedDbRestore.sh #directory_number

See previous paragraphs to see when to use each procedure depending on implemented
backup and to eventually recover data from tape in advance.

Restart Oracle processes using appropriate command form NMS5UX Men under directory
/opt/nms5ux/start

Restart NMS5UX processes using appropriate command form NMS5UX Men under directory
/opt/nms5ux/start

18.4 DATA BASE BACKUP POLICY

The right periodical backup policy must be obviously decided according to the customer
requirements (i.e.: minimum time for data lost considering network data, alarms, performance
monitoring) and constraints (i.e.:disk space or possibility to manually change external tape).
As a minimum recommended policy SIAE suggests to:

Scheduled two Alternate Full Backup operations each week (i.e. one Wednesday night the
other Sunday night)

NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003 53

 Scheduled one Alternate Reduced Backup operations each week (i.e. Saturday night)
This policy should guarantee that if the data corruption event is detected with a delay of less than
one week there is the possibility to recover full data (including alarm history and performance
monitoring) related to a maximum of one week before.
If the data corruption event is detected with a delay of more than one week there is still the
possibility to recover at least users and equipment configuration data related to a maximum of two
week before
This policy should be integrated at least with an incremental saving procedure on tape setting
changing tape substitution frequency depending on backup data dimension and tape capacity.

54 NMS5UX, NMS5UX-B 6.4 Administrator manual MN.00145.E - 003