HPUX ovaddobj[1m]
ovaddobj(1M) ovaddobj(1M)
NAME
ovaddobj - HP OpenView object registration utility
SYNOPSIS
ovaddobj [-O] [-t name string] filename.lrf [system identifier]
DESCRIPTION
ovaddobj performs two functions. It is used to register the
information necessary to start up object managers (i.e. agents) with
the HP OpenView process management daemon ovspmd, and it is used to
register in the HP OpenView DM Platform's Object Registration Service
(ORS) database information about the object managers and the objects
they represent. This information is used to provide the location
transparency feature of the HP OpenView DM Platform. If specific
address information for an operation is not provided by an application
through the HP OpenView programmatic interface, the address is
supplied from the information registered in the ORS database.
filename.lrf specifies a Local Registration File (LRF), which must
contain information about a single object manager and the objects it
manages. LRF syntax is described in lrf(4).
system identifier indicates the system on which the object manager
will be running. If the object manager is to be accessed via CMOT or
SNMP protocols, the system identifier is interpreted as a hostname. If
the object manager is accessed by the CMIP protocol, the system
identifier is the OSI presentation address used by the DM
Communications Infrastructure for the system on which the object
manager is running. An LRF may contain objects to be accessed by
multiple management protocols.
The format of the field is as follows:
hostname
or
hostname:presentation address
or
:presentation address
where a presentation address is entered as
:P-Selector,S-Selector,T-Selector,NSAP
The DM Communications Infrastructure requires that the first three
fields must be:
Hewlett-Packard Company - 1 - NNM Release 4.0: August 1995
ovaddobj(1M) ovaddobj(1M)
P-Selector=OPENVIEW S-Selector=ses0 and T-Selector=tp0
when the presentation address refers to another OpenView node.
For example:
ovaddobj filename.lrf :OPENVIEW,ses0,tp0,<NSAP>
Use the NSAP name being used by the OSI stack. Refer to the OTS
documentation for details on how to configure this for HP systems. For
information about valid OSI presentation addresses, refer to the
local_p_addr(4) man page.
A hostname specifies a system name that must be defined in the hosts
database used by the system (see gethostent(3n) and hosts(4)).
If the system identifier is not specified, it is assumed to be the
system on which ovaddobj is being run. The local
To change information about the object manager, edit the LRF and re-
run ovaddobj. All previous information in the ORS database about this
object manager will be replaced by the information in the current LRF.
NOTE:
All objects managed by the object manager must be specified in the
same LRF. Running ovaddobj against an LRF containing additional not
result in adding those objects, but rather in replacing those objects
previously registered with these new objects.
Parameters
-t name string
The name string in this option is used by ovaddobj to expand
the " ~" and " !" metacharacters in an instance name of an
object in the LRF.
In the case of " ~" expansion, the name string is
interpreted as the host on which the object to be accessed
resides (i.e. target hostname). This may be different from
the system identifier argument to this command, which
indicates where the object manager (agent) resides. Target
hostname is used for SNMP proxy lookups in the ORS database
and for expansion of the " ~" character, which may be used
in the object instance field of the LRF to indicate the IP
address of the target host. If the indicated host is multi-
homed (i.e. assigned multiple IP addresses) and the " ~" is
used in the object instance field, ovaddobj will expand the
~" with each IP address, adding an entry to the ORS database
for each expansion.
Hewlett-Packard Company - 2 - NNM Release 4.0: August 1995
ovaddobj(1M) ovaddobj(1M)
In the case of " !" expansion, the object is registered with
the " !" character in the instance name replaced directly
with the name string.
-O Indicates to ovaddobj that the default STACK to be
registered for the objects declared in the LRF is to be
OVs_ACMIP. The "~" expansion is inhibited when using this
option.
EXAMPLES
ovaddobj mylrf
This registers the object manager and all the objects described in the
LRF mylrf into the ORS database. The object manager location is
registered to be on the current system.
ovaddobj mylrf spock
This registers the object manager and objects described in the LRF
mylrf. The object manager location is registered to be on the system
named spock.
ovaddobj -t system_A mylrf system_B
In this case, the object manager resides on system_B and is proxying
for objects on system_A.
AUTHOR
ovaddobj was developed by the Hewlett-Packard Company.
FILES
HP-UX 9.x and SunOS 4.1.x
/usr/OV/bin/ovaddobj
HP-UX 10.x and Solaris 2.3, 2.4
/opt/OV/bin/ovaddobj
Universal Pathname $OV_BIN/ovaddobj
Universal pathname paths are established according to your shell and
platform requirements. See the file that applies to your platform and
shell for more information about the script used to set HP OpenView
Network Node Manager environment variables:
HP-UX 9.x and SunOS 4.1.x
/usr/OV/bin/ov.envvars.sh (k shell)
/usr/OV/bin/ov.envvars.csh (c shell)
HP-UX 10.x and Solaris 2.3, 2.4
/opt/OV/bin/ov.envvars.sh (k shell)
Hewlett-Packard Company - 3 - NNM Release 4.0: August 1995
ovaddobj(1M) ovaddobj(1M)
/opt/OV/bin/ov.envvars.csh (c shell)
SEE ALSO
ovdelobj(1M), ovspmd(1M), ovstart(1M), ovstop(1M), gethostent(1M),
hosts(4), lrf(4), local_p_addr(4).
Hewlett-Packard Company - 4 - NNM Release 4.0: August 1995