Server Management - Systems Insight Manager
1833776 Members
2317 Online
110063 Solutions
New Discussion

Re: Deploying VMM agent on 5.1

 
titn003
Occasional Advisor

Deploying VMM agent on 5.1

I would like to do a v2v migration and when i select the source virtual machine to deploy it say in the Tool launch OK? field

No, Not managed by VMM

so i go to Deploy\ Deploy drivers, firmware Agents\Install VMM

i get the the error message detailed in the screen shot.


I have installed OpenSSh on the target server

How do i fix this ?


6 REPLIES 6
Riders
Occasional Advisor

Re: Deploying VMM agent on 5.1

May be the the Server which you would do V2V is not identified properly as server in HPSIM. Re-discover the system or identify as server. Install openSSh if it not installed.This might work.......
loooolaaaaa
Frequent Advisor

Re: Deploying VMM agent on 5.1

The warning message shows SSH is not installed. If u have installed try re identifying the machine again.
titn003
Occasional Advisor

Re: Deploying VMM agent on 5.1

when i try to install ssh it fails


Tool ran on: CMS (Central Management Server)
Exit code: 0
Stdout:

1 file(s) copied. 1 file(s) copied. 1 file(s) copied. Running tool Store Information with job id 7795. Task Name :defRunNowTaskId_1173087436159_1 Job ID :7795 Tool Name :Store Information Job State :Complete User Name :FUTURESLAB\mroe Execute As User :Administrator Start Time :05 March 2007 09:37:16 GMT End Time :05 March 2007
09:37:17 GMT Elapsed Time : 1000 milliseconds Node :tda-vc-01.futureslab.local Status :Complete Exit Code :0 STDOUT : Running tool Run Remote Deployment Utility with job id 7796. Task Name :defRunNowTaskId_1173087437909_2 Job ID :7796 Tool Name :Run Remote Deployment Utility Job State :Complete User Name :FUTURESLAB\mroe Execute As User :Administrator Start Time :05 March 2007 09:37:18 GMT End Time :05 March 2007 09:37:21 GMT Elapsed Time :3 seconds 359 milliseconds Node :tda-vc-01.futureslab.local Status :Complete Exit Code :1 STDOUT : Deploying to: tda-qc-13.futureslab.local HP Remote Deployment Console Utility ------------------------------------------------------------------------------- Initializing...
Unable to connect to the target computer. All available connection methods were attempted with no success. A possible reason is that the operating system of the target computer is not sup ported. Either the username is unknown, or a bad password was provided. Unknown Initialization Error! Running tool Run Agent Configuration with job id 7797. Task Name :defRunNowTaskId_1173087442862_3 Job ID :7797 Tool Name :Run Agent Configuration Job State :Complete User Name :FUTURESLAB\mroe Execute As User :Administrator Start Time :05 March 2007 09:37:22 GMT End Time :05 March 2007 09:37:25 GMT Elapsed Time :2 seconds 812 milliseconds Node :tda-vc-01.futureslab.local Status :Complete Exit Code :122 STDOUT : Successfully unregistered from localhost Failed to
register as an agent to: tda-qc-13.futureslab.local Error: Configuration failed to complete due to the following exception: SSH Password authentication failed for target system: tda-qc-13.futureslab.l ocal.Check password and try again. STDERR : Completed with errors. Running tool Identify Systems with job id 7798. Task Name :defRunNowTaskId_1173087446549_4 Job ID :7798 Tool Name :Identify Systems Job State :Complete User Name :FUTURESLAB\mroe Execute As User :FUTURESLAB\mroe Start Time :05 March 2007 09:37:26 GMT End Time :05 March 2007 09:37:57 GMT Elapsed Time :31 seconds 44 milliseconds Node :tda-qc-13 Status :Complete Exit Code :0 STDOUT : startId idPluginStart.HttpPort idPluginStart.HmmoLinks smh.notsupported idPluginStart.MxWBEMIdentifier wbemidentifier.nosmiscimom
wbemidentifier.noservercimom idPluginStart.MxWBEMRuleBasedIdentifier wbem.cssupported idPluginStart.MxWSMANIdentifier idPluginStart.SnmpProto snmp.noresponse idPluginStart.CommonCluster snmp.clusternotsupported idPluginStart.SnmpProliant snmp.notsupported idPluginStart.SnmpNetserver snmp.notsupported idPluginStart.SnmpHPUX snmp.notsupported idPluginStart.SnmpSTM snmp.notsupported idPluginStart.DmiProto dmi.nowindmi idPluginStart.DmiSTM dmi.nowindmi idPluginStart.DmiHpUX dmi.nohpuxdmi idPluginStart.DmiCpq dmi.nowindmi idPluginStart.DmiHpMif dmi.nohpdmi idPluginStart.DmiGeneric dmi.nogenericdmi idPluginStart.MxSSHIdentifier ssh.hasssh idPluginStart.StorageIdentification smi.notwbem smi.stidentifdone idPluginStart.IdentifyHPSGMembers svcguard.wbem.notsupported idPluginStart.IPMCompatible idPluginStart.VmHost licMgr smhNotTrusted limitedDc limitedDcDone
sysRelationship done Running tool Remove Entry with job id 7800. Task Name :defRunNowTaskId_1173087478375_5 Job ID :7800 Tool Name :Remove Entry Job State :Complete User Name :FUTURESLAB\mroe Execute As User :Administrator Start Time :05 March 2007 09:37:58 GMT End Time :05 March 2007 09:37:58 GMT Elapsed Time : 484 milliseconds Node :tda-vc-01.futureslab.local Status :Complete Exit Code :1 STDOUT :

Ian Kirvell
Frequent Advisor

Re: Deploying VMM agent on 5.1

Hi there,

you don't have to have OpenSSh setup. Just copy the relevant hp executable file to the virtual machine host and install it. That saves using the remote deployment tool for something that you can do just as easily manually.
titn003
Occasional Advisor

Re: Deploying VMM agent on 5.1

appologies but how do i do that ?
Rob Buxton
Honored Contributor

Re: Deploying VMM agent on 5.1

FTP
FTP to a n internal ftp server that has the file copied.

SMB disk mount

Ensure the SMB service is allowed through the ESX firewall.

create a mount point;. mkdir /mnt/windows
mount the device;
mount -t smbfs -o username=localacc,password=mypass //myserver/c$ /mnt/windows

copy the file from one device to another.

You'll find the agent in the directory:
C:\Program Files\HP\HP Virtualization Management Software\Agents\Linux

on the HPSIM server.