Server Management - Systems Insight Manager
1748080 Members
5382 Online
108758 Solutions
New Discussion юеВ

Can't run Configure or Repair Agents on Linux VM - Linux SIM 5.2

 
kschafer
Advisor

Can't run Configure or Repair Agents on Linux VM - Linux SIM 5.2

I'm trying to Configure a new server, it's a Linux (SLES 10 SP2) VM running on vmware.

I'm getting the following errors when trying to run Configure / Repair:

Configuration of agents started, waiting for it to be completed.
Configure Agents and Providers (START) ...
Windows configuration command (START)...
Running the Windows based repair tool (DONE).......................... [ERROR]
Could not create repair directory on the target system. Check username/password,
user┬┤s privileges and whether administrative share is enabled on the target syst
em.

From the stderr tab:

Error connecting to 10.240.14.28 (Connection refused)

From mxagentconfig:

Error: Configuration failed to complete due to the following exception:
SSH Password authentication failed for target system: pluxv007.Check password and try again.
Completed with errors.

Everything from those errors points to a SSH configuration issue, or firewall issue. There is no firewall, and SSH works fine between the CMS and the server in question.

Any ideas? Thanks in advance.
2 REPLIES 2
Rob Buxton
Honored Contributor

Re: Can't run Configure or Repair Agents on Linux VM - Linux SIM 5.2

What agents?
If they're the HP Management Agents then these are usually installed on phyiscal servers as their main aim is reporting hardware issues.
In a VMware environment that's typically done from the agents on the VMware Host, not the guests.
Likewise the HP VMM Agents run on the VMware host, not the guests.
kschafer
Advisor

Re: Can't run Configure or Repair Agents on Linux VM - Linux SIM 5.2

There is no agent running on the VM.

I was trying to add the VM into HP SIM so I could avoid having to manage it using VMM. VMM isn't supported on SIM under Linux.

I assume that in order for this to work that there would have to be some sort of agent installed on the VM I want to manage.

Unless there is some sort of generic agent I assume I'm out of luck.