HP UX B6941-90001 - Manual (Page 256)

256 Chapter 5
Configuring ITO
Preconfigured Elements
❏ A parent instance may or may not exist. If there is no parent
instance, simply omit it from the syntax. If there were no parent
instance for the example in Figure 5-2 on page 255, the line would
look like this:
NTPerfMon\\LogicalDisk\\% Free Space\\C:
ITO will attempt to locate the objects when the agent is started, or when
a new template is assigned to the node. If ITO cannot immediately locate
the object, it will wait for two minutes and then search again. If ITO
cannot locate the object after five attempts, it will send a message to the
message browser, notifying the administrator that the object could not be
found. The monitor will not begin to search again until the agent is
restarted, or the template is reinstalled.
Monitoring MIB Variables of TME NetFinity on OS/2
Managed Nodes
The ITO monitor agent can be configured to monitor MIB variables
provided by the TME NetFinity product. The following prerequisites
must be met on the OS/2 managed node:
❏ TME NetFinity must be installed (TME NetFinity is pre-installed
with OS/2 Warp 4.0)
❏ the file NETVIEW_PATH\BIN\AGENT\DMISA.MAP must contain the
following entry:
“1.3.6.1.4.1.2.5.11.1.10” 1 1 1 1 “TME 10 NetFinity Services” 0 0
where NETVIEW_PATH is the directory where the SystemView agent
is installed (OS/2 Warp 4.0 SNMP daemons)
If the MIB OID (Object Idenitifer) 1.3.6.1.4.1.2.5.11.1.10 is already
used, use the next free one (only the last number will differ), but
make sure that the template on the management server reflects that
change.
❏ Start the DMI subagent (DMISA.EXE, part of SystemView agent); if
it is already running, stop and restart it.
Table 5-34 on page 257 gives an overview of all MIB variable attributes
of TME NetFinity. You can retrieve the same information by entering:
snmpwalk -c public < myhost.domain.com > \
1.3.6.1.4.1.2.5.11.1.10
where <myhost.domain.com> is the name of your system.