Before starting the upgrading to version 5.1 of the vCenter Server, the following steps can be taken to be able to successfully upgrade. The first step is reading the upgrade guides:
- vSphere 5.1 upgrading guide, found here
- Upgrading to vCenter 5.1 best practices, found here
- Overview of upgrading from vCenter Server 5.0 to vCenter Server 5.1, found here
After the RTFM stuff check the following:
- Make sure the SQL Server authentication checkbox is set to SQL Server and Windows Authentication mode on the SQL server. More info found here.
- The SQL server service is listening to port 1433. You can check this by using the following command:
netstat –a | find “1433”
if the SQL Server is not listening on port 1433, use the following steps:
- Open SQL Server Configuration Manage
- Expand the SQL Server Network configuration
- Click on the “Protocols for SQLEXP_VIM”. SQLEXP_VIM is the name of the SQL instance
- Select TCP/IP – Properties – IP Addresses tab an scroll down to IPALL, enter value 1433 in the TCP Port field
- Restart the SQL Server service
- Open the sql script called “rsaIMSLiteMSSQLSetupTablespaces.sql” (found in the vCenter ISO in …..\Single Sign On\DBScripts\SSOServer\schema\mssql\) and customize the location of the *.mdf, *.ndf and *.lfd file to your needs. After customizing the SQL file execute it and make sure the RSA database is created.
- If installing Single Sign On in a IPv6 environment check this KB article
- If after upgrading the vCenter services hangs on startup check this KB article
- The warning “The Fully Qualified Domain Name cannot be resolved. If you continue the installation, some features might not work correctly” appear during the installation. Make sure the reverse DNS record exist in the Reverse lookup Zones. Test this with the nslookup command
- The vCenter Server services hang on starup after upgrading to vCenter Server 5.1. More info can be found here.
2 thoughts on “Tips for upgrading to VMware vCenter 5.1”
Awesome! I had been running into the issue of connecting to a named instance and had set the IP1 port to 1433, but actually setting IPALL to 1433 worked. Thanks you!
Thank you for this post! Maybe you should mention that, besides using the SQL script “rsaIMSLiteMSSQLSetupTablespaces” you need to create the RSA database users with the SQL script “rsaIMSLiteMSSQLSetupUsers”.
Best regards, Jeroen