HP Insight Control for Linux 6.1 Release Notes

2.6.1 Benign font error message during firmware update
The following error message appears in the log of the firmware update:
Fontconfig error: Cannot load default config file
This message can be safely ignored.
2.7 Management and monitoring notes
This section contains notes that apply to Insight Control for Linux management and monitoring
features.
2.7.1 Metrics for HP ProLiant DL100 series servers might not be individually reported
Some HP ProLiant DL100 series servers temperature and fan sensor metrics are not individually
reported by default. Instead, they are tallied in the "Sensor Count" metric. The temperature and
fan sensor metrics are monitored correctly and are individually reported if they exceed the
warning or critical thresholds.
Corrective action: To archive metrics on an individual basis, follow the procedure in the HP
Insight Control for Linux User Guide to modify the /opt/hptc/nagios/etc/nagios_vars.ini
file.
2.7.2 Configure Insight Control for Linux management services or install agents might
fail
An intermittent SIM SSH delay by Configure→Configure or Repair Agents might cause
Options→Configure Insight Control for Linux Management Services and Deploy→Deploy
Drivers, Firmware and Agents→Insight Control for Linux Management→Install Agents...
to fail.
Corrective action:
1. Select Tasks & Logs→View Task Results... and view the task results to ensure that the
Identify Systems task is running, and wait for the task to complete.
2. When the system identification is complete, rerun the tool:
Options→Configure Insight Control for Linux Management Services
or
Deploy→Deploy Drivers, Firmware and Agents→Insight Control for Linux
Management→Install Agents...
2.7.3 Configure or Repair Agents failure for managed systems running Red Hat 4.8
When running the Configure→Configure or Repair Agents on a managed system running
RHEL 4.8, you might encounter the following message:
"Configuration of Agents" timed out since it reached the maximum configuration
time allocated for it per system.
It is currently set to 360 seconds for each system.
If you need to increase this time out,
set it as property "CRAConfigureTimeout" in the globalsetting.props file.
The value needs to be in seconds.
NOTE: This message was reformatted for readability.
This stems from a firewall issue with the RHEL 4.8 kernel.
Corrective action: To resolve this issue, run the following command on the managed system;
this command adds a new rule that accepts all TCP packets with destination port 22:
# iptables -I RH-Firewall-1-INPUT 1 -p tcp --dport 22 -j ACCEPT
2.7 Management and monitoring notes 13