Tools – HP Systems Insight Manager User Manual
Page 576
1.
Edit the host's file in \etc directory.
Note: You can use a text editor or vi to edit this file.
Add an entry in the host file:
•
server>
For example, an HP SIM system with IP address
170.50.1.201, fully qualified domain name
perf760g2.wbem.com, and name perf760g2 displays the following entry in the host file of the
managed node on the Linux VCA system:
170.50.1.201 perf760g2.wbem.com perf760g2
2.
Save the file.
All automatic event handling tasks fail with the following error on the Tasks Results page: Send failed.
class Could not connect to SMTP host: ipaddress, port
25;java.net.SocketException: Software caused connection abort:connect
.
Solution: If you have antivirus software installed and it is configured to block port 25, configure the antivirus
software to unblock port 25 or disable it for the automatic event handling tasks (e-mail) to run correctly.
When deploying the Software and Firmware task on HP-UX or Linux, the task might fail with an error unable
to contact system
. To successfully execute the task, change the System Link Configuration to use the
system IP address and then execute the task.
Solution: Select Options
→Security→Security Link Configuration. The System Link Configuration
page appears. Select Use the system IP Address.
Tools
I am receiving the HTTP - 404 error when trying to launch a tool.
Solution: This error is received when you try to access any tool that you are not authorized to use.
An mxauthenticationexception is generated when a tool is run from the GUI or the CLI.
Solution:
1.
Be sure that you have privileges to run the tool on the system. See
to verify
and grant privileges.
2.
Be sure that the SSH daemon is accessible on the target system.
a.
Try to log in as an administrative user to a Windows system and as root to an HP-UX or Linux
system.
b.
From an HP-UX or Linux CMS, enter:
ssh root@
or
ssh Administrator@
From a Window CMS:
If you are prompted to accept a host key or enter a password, then the SSH daemon is accessible.
3.
Run mxagentconfig again to verify that the keys are transferred:
mxagentconfig -a -n
576 Troubleshooting