HP Insight Control for Linux 6.3 Release Notes

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 or Repair Agents might fail 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.3 pdsh command might fail for the CMS if the CMS host name is not fully
qualified
The CMS host name attribute in the SIM database might change between its fully qualified name
(for example, venus.example.com) and its simple name (for example, venus).
This might occur if the PSP components required by Insight Control for Linux are not installed or
configured on the CMS.
Corrective action: If the pdsh command fails for the CMS, replace the fully qualified name in the
/opt/hptc/pdsh/nodes file (venus.example.com) with the simple name (venus).
2.7.4 Might see CRITICAL or WARNING Nagios alerts for the NodeInfo service
The Nagios default threshold values for total processes, user processes, and zombie
processes might be too small for certain system configurations, particularly those with virtualization
operating systems. If so, you will encounter CRITICAL or WARNING alerts for the NodeInfo
service.
Corrective action: Use the following procedure to update the default thresholds in the /opt/hptc/
nagios/etc/nagios_vars.ini file. HP recommends saving a copy of the original file before
making any updates.
1. Save a copy of the original file:
# cp /opt/hptc/nagios/etc/nagios_vars.ini /opt/hptc/nagios/etc/nagios_vars.ini.orig
2. Edit the nagios_vars.ini file to update the values for the *_procs_warning and
*_procs_critical parameters to values that apply to your environment. For example:
12 Issues and suggested actions