HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

Export the NNM file systems

/var/opt/

OV /share and

/etc/opt/

OV /share .[1]

[1] NFS processes must be running on the UNIX client and server systems to configure a remote console. To check the processes, type ps ef | grep nfsd. If the nfsd process is not running, enable nfs on HP-UX by modifying /etc/rc.config.d/nfsconf file with these entries:

NFS_CLIENT=1

NFS_SERVER = 1

NUM_NFSD = 32

NUM_NFSIOD = 16

Turn on NFS v3

After modifying nfsconf, execute the command /sbin/init.d/nfs.server start on the server and /sbin/init.d/nfs.client start on the client system. For more detailed information on NFS, refer to the UNIX man pages for nfs, nfsd, exportfs, and mount.

Add the following entries to

/etc/exports on the management server:

/var/opt/OV/share root=

client
/etc/opt/OV/share root=

client

Execute the command

exportfs -av .

Add the hostname of the client to the

ovwdb.auth and

ovw.auth files to provide access to the database. Both files are located in the $OV_CONF directory. The "+" indicates any user can have access to the database.

client +

Install NNM on the client system, including all file sets.

Mount the server's exported file system.[2]

[2] You can actually mount a file system on top of an existing file system and files will not be deleted or destroyed. However, if the server file systems become unmounted you will be using a local database. If you plan on using the remote console permanently you should remove the contents of /var/opt/OV, /etc/opt/OV, and /opt/OV on the client before mounting the server's file systems.

Add the following entries to the /etc/fstab file where server is the hostname of the management server:

server: /var/opt/OV /var/opt/OV

server: /etc/opt/OV /etc/opt/OV

Execute the command

mount -av .

Run the

ovwsetupclient script

ovwsetupclient

server .

Start NNM on the client system and open a custom map that was created on the management server to verify access to the NNM database. Run

ovw -server from the command line to display the hostname of the NNM database server.

Share the OpenView file system on the NNM management server. Typically, NNM resides in

\Program Files\HP OpenView directory but it can be stored in a different location on your system. Make sure to share the directory in which NNM was installed. To share the directory, right-click the %install_dir% directory from the Windows Explorer. Select

Sharing… and click the radio button

Share this folder and click

[OK] . Make sure the permissions are set to allow Full Control, Change, and Read access.

Add the client hostname followed by a plus sign to the

ovwdb.auth file. The "+" grants access to any user on the client system.

client +

Verify that name resolution of the server is functioning on the client:

nslookup

hostname

Install NNM on the client using the Remote Console option. You will be prompted for the hostname of the server. NNM will establish connectivity to the server and provide access to the database.

Start NNM on the client and verify access by opening a custom submap that exists on the server.

Export the NNM file systems /var/opt/OV/share and /etc/opt/OV/share.

Add the following entries to /etc/exports on the management server:

/var/opt/OV/share root=

client

/etc/opt/OV/share root=

client

Execute the command

exportfs av .

Add the hostname of the client to the

ovwdb.auth and

ovw.auth files to provide access to the database. Both files are located in the $OV_CONF directory. The "+" indicates any user can have access to the database.

client +

On each system to be made an HP OpenView Remote Console (Windows), use your NFS software on the PC Remote Console to map the UNIX directories. Use Windows Explorer's "Map Network Drive" function. Be sure to consult your NFS software documentation about how to enable locking.

On each HP OpenView Remote Console system, insert the NNM installation CD, run setup.exe, and select "Remote Console Installation". Supply the two mapped drive letters configured in step 1.