Virtualization Pro

May 8 2008   8:41PM GMT

Why you should upgrade to VI3 Update 1

Rick Vanover Rick Vanover Profile: Rick Vanover

VMware Infrastructure 3 Update 1, made available on April 10 2008, introduces some core updates to ESX Server 3.5, VirtualCenter 2.5, and the VMware Infrastructure Management Installer. The biggest reason to upgrade, however, is the inclusion of Storage VMotion.

Among the core features now available with ESX 3.5 Update 1 are the addition of the Intel 82598 10 GB Ethernet controller, support of Jumbo Frames and NetQueue, additional Microsoft Clustering Services (MSCS) support, additional backup product and management agent support, additional guest operating systems, and additional server models.

I’ve been working with ESX 3.5 Update 1 for a few weeks, and the installation and behavior are indistinguishable from both ESX 3.5’s base release and ESX 3.02, with the exception of context sensitive tasks or options.

When I test upgrades, I make a point to test the upgrade in an environment with dissimilar ESX host server releases. For example, most of my hosts are ESX 3.02. When I upgrade the first one to ESX 3.5, I want to make sure that nothing goes wrong. I want to know that I’ll be able to sustain a mixed environment with all functionality. When I migrate running virtual machines through host-based VMotion to the ESX 3.5 host, and the reverse, I want to make sure to the best of my ability that nothing will fail. I also want to ensure that all of the VMware DRS and VMware High Availability rules are still enforceable with the mixed-host inventory.

Outlining a functionality matrix and the verification of the behavior is key to having no surprises during a live upgrade. Testing the update to VirtualCenter is a little more difficult but I am setting up a test environment soon to ensure that everything functions as expected in my environment. Overall, the fixes and new features make ESX 3.5 Update 1 an attractive upgrade for systems that are not there already.

4  Comments on this Post

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.
  • Slowe
    Rick, Unless I am mistaken--which is certainly very possible--Storage VMotion was first introduced with version 3.5 of VI3.
    0 pointsBadges:
  • Rick Vanover
    You are correct, Scott. But what I am getting at is that since ESC 3.5/VC 2.5 have been released many organizations have not jumped up to the new versions. Now with update 1 correcting some issues and adding some new features, the enticement is greater.
    20 pointsBadges:
  • Slowe
    I see--from the perspective of a user or organization still on ESX 3.0.x, then Storage VMotion would be a "new feature" of VI 3.5 Update 1. Sorry, the wording made it seem like Storage VMotion was new to Update 1 specifically. Thanks for the clarification!
    0 pointsBadges:
  • Shokk
    That is our case. We are only now making the move to 3.5U1 from 3.0.2 because of the parade of scary bulletins that appeared with each patch. Something seemed amiss so we decided to wait. Good things come...
    15 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network: