HP Insight Control for Linux 6.0 Release Notes

2.6.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.6.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.6.4 pdsh command fails 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.6.5 Nagios nsca daemon might fail to start on the CMS
The nsca daemon might fail to start on the CMS.
Every time you run Options→Configure Insight Control for Linux Management Services,
verify that the nsca daemon is running on the CMS:
# /etc/init.d/nagios status_nsca
If the nsca daemon is not running, enter the following command to start it:
# /etc/init.d/nagios start_nsca
2.6 Management and monitoring notes 17