HP zl - Manual (Page 67)

hp toptools for openview nnm user guide
From the OpenView NNM map, use the Find Object By Attribute menu item to find all nodes that have
"isHPKayak", "isHPVectra", "isHPNetserver", or "isHPPrinter". After locating an HP device, verify that the icon is
an HP icon. (Each HP icon has an HP logo in the upper corner.) This verifies that the hpttBrdgMgr process is
running properly. (Note that if any devices have a non-public community name, NNM must be configured. Consult
section 5.3 and the NNM documentation for more information.)
Try selecting an HP device and launching a toptools menu action. The browser should be launched with the
appropriate URL. Select a second HP device and then launch another toptools menu action. The existing instance
of the browser should be reused for this new URL.
6.6 Useful Log Files
The bridge creates log files on both the toptools server system and the OpenView NNM system. A separate log file
is created for each executable. The log file name will be where "filename” is the name of the
executable. Information will be saved to the log file based on the debug level set for each executable. Error
messages and Mode 0 activation messages will always be logged. Additional mode activation information will be
logged depending on the debug level set for the executable. (hpttBrdgInstall and hpttBrdgRemove do not have
DEBUGMODE settings.)
Table 6. Program Executables and their Log Files.
Function NNM-NT
Executable NNM-UX, Solaris
Executable Log File Name
Discovery hpttBrdgDisc.exe hpttBrdgDisc hpttBrdgDisc.log
HP Toptools Bridge hpttBrdgMgr.exe hpttBrdgMgr hpttBrdgMgr.log
Bridge Installation hpttBrdgInstall.exe hpttBrdgInstall hpttBrdgInstall.log
Bridge Removal hpttBrdgRemove.exe hpttBrdgRemove hpttBrdgRemove.log
Launch Action hpttLaunchAction.exe hpttLaunchAction hpttLaunchAction.log
Server Status nsaAgentStatus.exe nsaAgentStatus nsaAgentStatus.log *
* On HPUX and Solaris systems nsaAgentStatus is a script file and no log file is created.
6.6.1 Log Files for Multiple Users
On Unix systems there can be multiple users. In this case there is a separate log file for each user accessing the
hpttBrdgMgr executable. The hpttBrdgMgr log information is written to a log file in the OV_PRIV_LOG directory.
The log file is named hpttBrdgMgr..log where is the process ID for the specific hpttBrdgMgr instance.
6.6.2 Log File States
Log files that are empty when the hptttBrdgMgr executable terminates will be deleted. Otherwise the log files will
be deleted when the bridge is removed (uninstalled).
6.6.3 Log File Debug Levels
You can set the debug mode (level) for a bridge executable to 0-15. 0 logs only base level program events and
errors. Level 15 provides the maximum amount of information. This information is primarily for use of Hewlett-
Packard support personnel in diagnosing system problems.
6.6.4 Setting Debug Levels
The debug level for an executable is stored as follows:
• NNM-NT/WINDOWS 2000 - in a registry setting under HKEY_LOCAL_MACHINE for the executable,
"DEBUGMODE".
• On Unix systems the DEBUGMODE setting is set through file "/etc/.debug".
Sample NNM-NT/WINDOWS 2000 Debug entry
Page 67