Server Migration Pack Error

[helpme!]

Hi I am using the HP Server migration pack (v3) to try and do a P2V migration. The source server is W2K3 SP2 and the host server is ESX3.02. I have installed the SMP agent on the source server with no problems. I have also installed the SMP agent on the VM host (ESX server). However when i go through the migration wizard, at step 3, the process fails with the error message "The SMP agent cannot be connected. Install the SMP agent from the Deploy agent Tab before starting the migration". I have checked on the ESX server and the HPSMPCNTSVC service is definitely running.

Has anyone seen this problem before? I thought that the SMP could be run independently without SIM or VMM as these are not needed according to the documentation. Is this definitely the case.

Any help would be greatly appreciated

Thanks

Chris

[Adrian Clint]

I'm not up to speed on the new Universal SMP

But it used to be that P2P did not require SIM or VMM.

But P2V, V2V & V2P did.

Check

[helpme!]

Thanks for your response Adrian. You're right that the SMP can be ran without SIM or VMM.

I've actually found the problem and it was VMWare related. I'm not sure whether it's a bug in the SMP but when i deployed the host agent to the ESX server, it opened up ports on the firewall by changing the firewall configuration xml file. However, it actually created a syntax error in the configuration file meaning that the firewall was not functioning correctly. VMWare idenitified this problem after looking at my ESX server and fixed the issue (it was just a couple of extra colons in the syntax). I was then able to stop the firewall service on the ESX server temporarily whilst I completed the P2V migration (which then worked remarkably smoothly). When everything is working properly its a really smooth process and great bit of software.

All the best

Chris

[helpme!]

I've actually found the problem and it was VMWare related. I'm not sure whether it's a bug in the SMP but when i deployed the host agent to the ESX server, it opened up ports on the firewall by changing the firewall configuration xml file. However, it actually created a syntax error in the configuration file meaning that the firewall was not functioning correctly. VMWare idenitified this problem after looking at my ESX server and fixed the issue (it was just a couple of extra colons in the syntax). I was then able to stop the firewall service on the ESX server temporarily whilst I completed the P2V migration (which then worked remarkably smoothly). When everything is working properly its a really smooth process and great bit of software.