FATAL error "vmonapi" while migrating from Windows 6.0 to Appliance 6.5

[factroy]

Hi,

we would like to move from our Windows vCenter 6.0 installation to the new vCenter Appliance 6.5 as documented.

All went well until the new instance is goging to start where we get an error:

"An error occurred while starting service "vmonapi" (Failed to start VMware Service lifecycle manager API service)"

There was some hint in the release notes:

"vmon-api firstboot"

Workaround: Verify that the source vCenter Server SSL certificate SAN field contains the valid IP address of the source vCenter Server instance.

but I really dont understand how or what to fix on the original vCenter Windows server if this is really causing the issue.

a) Any additional help would be great. Could this really be the issue. But how do I fix this "SAN field"?

b) How can I verify that this is really the issue? I have inspected the "vm-supported.tgz", but dont know where to look?

Anyone else seeing this?

Thanks for any help.

PS: Of course a new installation of the  6.5 appliance works just fine.

[PuliSukumar]

HI,

     Can we get below details so that we can check what's wrong with certificates.

1) support bundle from 6.5 appliance

2) 6.0 Windows IP, Host name and contents of SAN field.

[sanjeebkumar]

See if the vcenter certificate SAN field has correct vcenter server IP.

Please refer the release note VMware vSphere 6.5 Release Notes

Upgrading to vCenter Server 6.5 may fail at vmon-api firstboot phase because of an invalid IPv6 address in the SAN field of the SSL certificate
The vCenter Server SSL certificate takes an IPv6 address in the SAN field when you install vCenter Server and enable both IPv4 and IPv6. If you disable IPv6 after the installation and then attempt to upgrade vCenter Server to version 6.5, the upgrade fails at vmon-api firstboot phase.

Workaround: Verify that the source vCenter Server SSL certificate SAN field contains the valid IP address of the source vCenter Server instance.

[factroy]

Thanks for the info, but as I was already telling:

Workaround: Verify that the source vCenter Server SSL certificate SAN field contains the valid IP address of the source vCenter Server instance.

but I really dont understand how or what to fix on the original vCenter Windows server if this is really causing the issue.

So,  I need some more advise how to check this "SAN" field on the original server's certificate.

Thanks

[peterriederer]

we have been running in the same issue.

1. Upgrade Windows vCenter 5.5 to VCSA 6.5 failed.

2. Upgrade Windows vCenter 5.5 to VCSA 6.0 success

3. Upgrade VCSA 6.0 to VCSA 6.5 failed.

Already opend a Support Request. Any News so far?

Regards

Peter

[cliffcahill]

Had the same issue of the weekend and this KB resolved it.

Replacing the Lookup Service SSL certificate on a Platform Services Controller 6.0 (2118939) | VMwar...

You should be able to view your current cert at C:\ProgramData\VMware\vCenterServer\runtime\VMwareSTSService\conf\ssoserver.p12