RTFM's "Upgrading to ESX 3.5 and VirtualCenter 2.5 Experiences"
Mike Laverick again shares another screenshot-filled pdf guide, this time with his upgrade notes. Overall it went OK, but he had a few issues with the VC upgrade. As always, you should backup, snapshot, and try it on non-production machines first.
Link: RTFM Education » Blog Archive » Upgrading to ESX 3.5 and VirtualCenter 2.5 Experiences.
The ESX upgrade part is relatively easy – given that the upgrade process can modify your configuration (as in my SSH example) and that moving a VM off an ESX host is simple. I think I would still prefer to wipe my ESX hosts and do a clean install – adding them back into VirtualCenter. This is not without consequences. It means losing some of that precious performance data collected over a number of weeks or months.

I'm not sure if he uses ISCSI - we ran into a major problem with both of our ESX servers (one which had been running 3.0 for awhile; another which was a fresh 3.0 install upgraded to 3.5 before going into production) where the software firewall was configured to block iSCSI traffic, causing all sorts of fun when the system rebooted until I could SSH in and enable it:
esxcfg-firewall -e swISCSIClient
Posted by: Chris Adams | January 29, 2008 at 09:19 PM
Have completed our first major upgrade for one of our larger customers from VC 2.0.2 to VC 2.5 and ESX 3.0.2 to ESX 3.5. No major issues (backup everthing!), but an odd issue when the upgrade of VC completed successfully. We could not connect using the VI client even though VC service/SQL etc,, were all started successfully. After about 2 hrs of troubleshooting turns out that IIS was previoulsy using port 80 and 443, so VC was installed using 8080 and 4343 originaly!! Ahhh. Went into add/remove programs and did a repair or VC. As part of the repair it asks what ports you want to use. I disabled IIS and changed ports to 80 and 443 and wholla!! All worked a treat after that with no more issues. Hipe this helps anyone with same issue.
Posted by: Eric Daly | February 17, 2008 at 04:31 AM