HP Insight Remote Support 7.0.9 Monitored Devices Configuration Guide

Note: HP Sustaining Engineering maintains a schedule of support for the Tru64 UNIX
operating system. HP does not commit to supporting Insight Remote Support when installed
on an operating system version that has exceeded its end-of-support date.
l Minimum 20 MB free disk space for installation of all components.
l TCP/IP services must be installed and running.
l Upgrade to V1.22 or higher of the Emulex (EMX) driver if you have an EMX LP6000, LP7000, or
LP8000 adapter (KGPSA–xx) using the SLI2 programming interface. Use of an EMX driver prior to
V1.22 may result in data not being processed correctly.
l System firmware: The prerequisite system firmware supports the logging of events according to the
FRU Table Version 5 Specification, which is required for Insight Remote Support FRU configuration
tree processing.
n All DSxx and ES40 systems must have firmware V5.7–4 or higher.
n All other systems (currently ES45, GSxx, and TS202c) ship with a compatible firmware version.
In general, users should take advantage of the latest improvements by obtaining the most recent
firmware version available for their platform.
Required Permissions and Access
To install, upgrade, or uninstall ELMC, you must be logged on as the root user. The
/usr/opt/hp/svctools directory is owned by root, and has rwx (read, write, and execute) permissions
for root (owner), and no permissions for any other user (group or world).
Archiving and Cleaning the Error Log
After Insight Remote Support is installed on the Hosting Device, it uses ELMC to analyze all events
stored in the error log, which can result in high CPU usage over an extended period. To control this
operation, you are encouraged to archive and clean the error log before installing. This reduces the size of
the log and the time required for the initial scan.
Follow these guidelines for cleaning the error log. If ELMC is installed and running when you clean the log,
you do not need to stop and restart the Director process. Also, do not stop and restart the ERRFMT system
event logging process.
Tru64 UNIX Version 4.0F
1.
Stop the binlogd process: # /sbin/init.d/binlog stop
2. If desired, move the original error log to any appropriate name, for example:
# mv /var/adm/binary.errlog /var/adm/binary.errlog.2002_06_11
Saved logs can be analyzed at a later time.
3.
If you skipped step 2, remove the original error log: # rm /var/adm/binary.errlog
4.
Restart the server. During restart, the server creates a new binary.errlog file containing a new
configuration event. The server also restarts the binlogd process.
HP Insight Remote Support 7.0.9:Monitored Devices Configuration Guide Page 122 of 267
Chapter 14: Configuring Tru64 UNIX Servers