Alexandre Takacs
asked on
P2V VMware converter issue - unable to submit job: converter.fault.ManagedDiskOpenFault
Hello
I guess title says it all....
Trying to convert a fairly plain vanilla Win7 machine to ESXi vCenter 5.5 - the job never gets to the point of starting as I get the error at submission.
Any help / suggestion most welcome, especially as the vmWare forums are in maintenance over the whole week-end !
I guess title says it all....
Trying to convert a fairly plain vanilla Win7 machine to ESXi vCenter 5.5 - the job never gets to the point of starting as I get the error at submission.
Tried both with converter 5.5.3 and 6.0 to no avail.
There is no (known ?) other connection to vCenter (apparently that might be an issue).
Log bundle available here (EE uploader is blocking it): https://www.dropbox.com/s/tu9gpefjktbyoxy/ConverterDiagnostics20150606005624.zip
Any help / suggestion most welcome, especially as the vmWare forums are in maintenance over the whole week-end !
What is the error message ?
ASKER
In the GUI it just say "unable to connect to ."
However just spend some time reviewing the logs and found something more relevant in the converter worker log:
Seems the is some networking issue with vSphere - yet converter does connect and retrieve environment data just fine in the early stages of the process... strange
However just spend some time reviewing the logs and found something more relevant in the converter worker log:
Get disklib file name as vpxa-nfcssl://[VSA-LUN01] LR-3CX/LR-3CX.vmdk@192.168.80.3:902!52 b0 c0 27 a4 ff 4a eb-cf 31 7f 2f 66 b8 a5 13
2015-06-06T00:55:16.993+02:00 warning vmware-converter-worker[02740] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Failed to connect to server 192.168.80.3:902
2015-06-06T00:55:16.993+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)
2015-06-06T00:55:16.993+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Error 2338 opening disk vpxa-nfcssl://[VSA-LUN01] LR-3CX/LR-3CX.vmdk@192.168.80.3:902!52 b0 c0 27 a4 ff 4a eb-cf 31 7f 2f 66 b8 a5 13.
2015-06-06T00:55:16.993+02:00 warning vmware-converter-worker[02740] [Originator@6876 sub=Default] ERROR 2338 opening disk disk-2000.
2015-06-06T00:55:16.993+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Attempt to opening disk disk-2000 again [rest 2] (sleep for 5 sec).
2015-06-06T00:55:21.993+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Reusing existing VIM connection to 192.168.81.9
2015-06-06T00:55:22.003+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] GetManagedDiskName: Get virtual disk filebacking [VSA-LUN01] LR-3CX/LR-3CX.vmdk
2015-06-06T00:55:22.003+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] GetManagedDiskName: updating nfc port as 902
2015-06-06T00:55:22.003+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] GetManagedDiskName: get protocol as vpxa-nfcssl
2015-06-06T00:55:22.003+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[VSA-LUN01] LR-3CX/LR-3CX.vmdk@192.168.80.3:902!52 90 7f 1b f2 6a 5f bb-29 c0 ca 9c 28 0b 51 e6
2015-06-06T00:55:43.004+02:00 warning vmware-converter-worker[02740] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Failed to connect to server 192.168.80.3:902
2015-06-06T00:55:43.004+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)
2015-06-06T00:55:43.004+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Error 2338 opening disk vpxa-nfcssl://[VSA-LUN01] LR-3CX/LR-3CX.vmdk@192.168.80.3:902!52 90 7f 1b f2 6a 5f bb-29 c0 ca 9c 28 0b 51 e6.
2015-06-06T00:55:43.004+02:00 warning vmware-converter-worker[02740] [Originator@6876 sub=Default] ERROR 2338 opening disk disk-2000.
2015-06-06T00:55:43.004+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Attempt to opening disk disk-2000 again [rest 1] (sleep for 10 sec).
2015-06-06T00:55:53.004+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Reusing existing VIM connection to 192.168.81.9
2015-06-06T00:55:53.019+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] GetManagedDiskName: Get virtual disk filebacking [VSA-LUN01] LR-3CX/LR-3CX.vmdk
2015-06-06T00:55:53.019+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] GetManagedDiskName: updating nfc port as 902
2015-06-06T00:55:53.019+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] GetManagedDiskName: get protocol as vpxa-nfcssl
2015-06-06T00:55:53.019+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[VSA-LUN01] LR-3CX/LR-3CX.vmdk@192.168.80.3:902!52 b7 ff fb 76 a2 3b 10-92 fd e8 d1 03 8e 25 a8
2015-06-06T00:56:14.019+02:00 warning vmware-converter-worker[02740] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Failed to connect to server 192.168.80.3:902
2015-06-06T00:56:14.019+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)
2015-06-06T00:56:14.019+02:00 info vmware-converter-worker[02740] [Originator@6876 sub=Default] Error 2338 opening disk vpxa-nfcssl://[VSA-LUN01] LR-3CX/LR-3CX.vmdk@192.168.80.3:902!52 b7 ff fb 76 a2 3b 10-92 fd e8 d1 03 8e 25 a8.
2015-06-06T00:56:14.019+02:00 warning vmware-converter-worker[02740] [Originator@6876 sub=Default] ERROR 2338 opening disk disk-2000.
Seems the is some networking issue with vSphere - yet converter does connect and retrieve environment data just fine in the early stages of the process... strange
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks it turned out to be a firewall issue, not to the vcenter (that was ok) but to the ESX host machine I wanted to deploy to...
ASKER
Well I think this definitely falls into "the grade given for acceptable solutions, or a link to an acceptable solution. A B grade means the solution given lacked some information or required you to do a good amount of extra work to resolve the problem". I got a hint to the right solution (a firewall issue at the end of the day) but not the specifics (that one has to check for network connectivity on port 902 both from Converter Server machine and the source machine to the destination ESX server (note it is not the vCenter server). So yes the answer was useful in pointing me in the right direction but still needed extra research.