ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

P2P - driver injection problem

Greyhair
Occasional Contributor

P2P - driver injection problem

Hi there
I'm testing this nice looking piece of software, but am coming across a driver injection problem after all the data seems to have copied. I am going from a DL380G3 to a DL385G2 so both on the compatibility matrix. The first attempt to inject drivers fails and then the second attempt never injects or times out. from the log:

... 8 more
2007/05/13 22:19:38 | WARN - The job failed
2007/05/13 22:19:38 | com.hp.mx.vmm.vmtools.grid.transport.TransportException: Failed: Drivers could not be injected into boot disk HP P600, Logical Volume 0, Controller Slot 3 Bus 0. For a list of possible causes, see the Troubleshooting section of the User Guide.
2007/05/13 22:19:38 | at com.hp.mx.vmm.vmtools.grid.transport.MigrationJob.heteroInjectDrivers(MigrationJob.java:704)
2007/05/13 22:19:38 | at com.hp.mx.vmm.vmtools.grid.transport.MigrationJob.heterogenousCopy(MigrationJob.java:423)
2007/05/13 22:19:38 | at com.hp.mx.vmm.vmtools.grid.transport.MigrationJob.copy(MigrationJob.java:164)
2007/05/13 22:19:38 | at com.hp.mx.vmm.vmtools.grid.transport.TransportJob.transportJobMain(TransportJob.java:536)
2007/05/13 22:19:38 | at com.hp.mx.vmm.vmtools.grid.transport.TransportJob.run(TransportJob.java:755)
2007/05/13 22:19:38 | at java.lang.Thread.run(Unknown Source)
2007/05/13 22:19:48 | WARN - Cannot grant access on x.x.x.x for [x.x.x.x]
2007/05/13 22:19:48 | java.rmi.ConnectException: Connection refused to host: x.x.x.x; nested exception is:
2007/05/13 22:19:48 | java.net.ConnectException: Connection timed out: connect

Any help appreciated.
2 REPLIES
Prashant (I am Back)
Honored Contributor

Re: P2P - driver injection problem

I will not sugges you to use P2P tool from HP becuase i find didn't find it work of using it.
REfer to this link and try to follow the steps. It Good and FAST also.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1028297

And this is a gr8 solution and it worked for me and saved time for me also.

Prashant S.
Nothing is impossible
Greyhair
Occasional Contributor

Re: P2P - driver injection problem

Thanks for the reply. A few points though:
- the process is assuming that the disks are similar. Going to a 385G2 they are dissimilar disks (SAS, not SCSI)which is a problem
- The P2P process seems to copy the data, but you are unable to boot to any part of windows (recovery/safe mode). also registry is not available as disks are not seen
- We need the tool in unsupported places so swapping hardware is not an option. Also, if we pay for the software then it should do what it say it does.