VC 5.5 to 6.0 U2 upgradation failed

[chirag20]

Hi;

we have VC 5.5 u3b in environment with external sql 2k8 r2 sp2 db (db owner permission), tried to upgrade 6.0 u2 and getting failed number of time with different errors.

1) missing indexes - follow article and created indexes

2) view server list permision - set at sql level with help of DBA

3) now getting component not registered - checked and found PTR record not created for VC.

i have question that does PTR required for VC? we have already reffered interoperatibility and compatibility matrix which looks fine.

[rcporto]

vCenter installation requires reverse lookup, see: vSphere DNS Requirements

vSphere DNS Requirements

You install or upgrade vCenter Server, like any other network server, on a host machine with a fixed IP address and well-known DNS name, so that clients can reliably access the service.

Assign a static IP address and host name to the Windows server that will host the vCenter Server system. This IP address must have a valid (internal) domain name system (DNS) registration. When you install vCenter Server and the Platform Services Controller, you must provide the fully qualified domain name (FQDN) or the static IP of the host machine on which you are performing the install or upgrade. The recommendation is to use the FQDN.

When you deploy the vCenter Server Appliance, you can assign a static IP to the appliance. This way, you ensure that in case of system restart, the IP address of the vCenter Server Appliance remains the same.

Ensure that DNS reverse lookup returns an FQDN when queried with the IP address of the host machine on which vCenter Server is installed. When you install or upgrade vCenter Server, the installation or upgrade of the Web server component that supports the vSphere Web Client fails if the installer cannot look up the fully qualified domain name of the vCenter Server host machine from its IP address. Reverse lookup is implemented using PTR records.

If you use DHCP instead of a static IP address for vCenter Server, make sure that the vCenter Server computer name is updated in the domain name service (DNS). If you can ping the computer name, the name is updated in DNS.

Ensure that the ESXi host management interface has a valid DNS resolution from the vCenter Server and all vSphere Web Client instances. Ensure that thevCenter Server has a valid DNS resolution from all ESXi hosts and all vSphere Web Clients.

[chirag20]

yes, I read and required changes in place, will see.

thanks for info.