Categories

Archive

May 2025
M T W T F S S
 1234
567891011
12131415161718
19202122232425
262728293031  

Most viewed posts

Upgrade path to vSphere 5 – The hardware part

9 November 2011
Comments off
Reading Time: 3 minutes

As written in the previous post, the HCL check is a mandatory step in each major upgrade (and of course also in each new implementation). And one of the aspect to verify is the firmware version that must match the minimum required for the particular version of vSphere:

  • BIOS of physical servers: my recommendation is use always the latest stable version. The issues with old and unsupported (from vSphere) versions could be really hard to identify and troubleshoot… for example on a old IBM server with an unsupported firmware, there was a really strange and silly issue where only one 64-bit VM was working at one time…
  • Other firmware of physical servers: BIOS is only one of the server’s firmware, some servers have a different firmware for the motherboard (for example on old Dell it is call BMC firmware and must be also upgraded to latest version), most servers have an off-band management interface (DRAC/iDRAC on Dell, iLOE on HP, …) with a related firmware… And of course there are some firmwares on storage card (really important if you use local storage) or storage/network adapters.
  • Storage’s firmware: the VMware HCL specify also the minimum firmware level for storage solutions. Some functions (VAAI, VASA, …) may require firmware really new (sometime marked as experimental or early production).
  • Switches’s firmware: network switches (included SAN switches) are usually not listed in the HCL, but they must be considered and keep up-to-date.

How manage the firmware updates? For storage and network devices it’s usually easy: the vendor defines the specific producer and in most case is also easy to apply (for example with a simple browser). If the infrastructure is well designed for availability a storage processor or physical switch modules upgrade must not impact on the production.

But for physical servers the upgrade procedure could be not so easy: the upgrade packages are usually for Windows, Linux or DOS (this one to be used with a bootable floppy or USB keys)… Nothing specific for ESXi.

For Dell PowerEdge servers there are some options to perform a firmware upgrade:

  • Dell Unified Server Configurator (USC): available only from the 10th generation… during the POST phase it can be activated with F10 (for more information see this doc).
  • Dell Server Update Utility (SUU): a bootable DVD to handle all the firmware upgrade.. the download is available from Dell Support site (note that HP and IBM have also similar solutions).
  • Dell OpenManage IT Assistant: free tool for a central management (for more information see this doc). It includes also a patching function, but seems that does not work with ESXi hosts.
  • Dell Management plugin for VMware vCenter: tool (with a fee) for a central hardware management integrated with vCenter Server (for more information see this doc).

In my case, with the old Dell PowerEdge 2950 servers (9th generation, but compatible with vSphere 5), the new and useful USC function is not available. The SSU or a floppy/USB was a solution, but in my case, with ESX 4.1, was also possible (with a little trick) use the service console and the Linux version of the patches.

VMware

Upgrade path to vSphere 5

8 November 2011
Comments off
Reading Time: 3 minutes

The upgrade path to vSphere 5 is well described in the specific guide (vSphere Upgrade Guide) and in the vSphere Upgrade Best Practices white paper..

In some cases an in-place upgrade can be applied with the advantage to require less time and to keep all (or most) of the settings and configurations. For example, a vCenter Server 4.1 can be updated to the 5.0 version (the requirements of the two versions are quite the same) or an old ESXi can be updated to ESXi 5.

But in most cases, also when the in-place upgrade is possible, could be interesting considering a full reinstallation, that give the advantage of the new clean situation. Also it can require more time (and more effort), but can give less downtime, because for example you can build a new vCenter Server, configure it and then simple re-connect the hosts to this new one.

Anyway, some points are quite common for each major vSphere upgrade:

  • HCL: the Hardware Compatibility List must be checked before each upgrade (each vSphere major release as a specific HCL that could be different). Also the software part must be checked (on the VMware Product Interoperability Matrix) to verify the compatibility of some specific part (like for example the DBMS).
  • Firmware: this aspect is related to the previous point… each major release can require a minimum firmware level (especially for servers and storage)… usually a good approach could be update to latest stable firmware (but check with vendor recommendation).
  • ESX: in can be upgrade (with an in-line process) to ESXi 5… but only in some cases (for example not when ESX was upgraded from version 3.x)… and is not possible change the destination of the installation (that goes in the boot partition). Usually a rebuild could be a better option.
  • Drivers and modules: some 3rd part modules or drivers can prevent an upgrade of ESXi /ESX. Check their compatibily with ESXi 5 and, if needed, remove them before the upgrade.
  • Plugin: the vCenter plugins must be verified before the upgrade of vCenter Server… both on the server-side and the client-side. In most cases, could be better remove them before the upgrade.
  • Converter Enterprise e Guided Consolidation: those plugin does no more exist in vSphere 5. Remove them before upgrade the vCenter Server.
  • VDR: there can be some issue during the upgrade of the destinations… If the integrity check fail, consider to build a new VDR with new and clean destination.
  • View: View 4.x is not compatible with vSphere 5. See specif upgrade guide.
  • SRM: SRM 4.x is not compatible with vSphere 5. See the specif upgrade guide.

In the next posts I will describe the upgrade steps for a simple infrastructure composed by the following parts:

  • host ESX 4.1 with Dell PowerEdge 2950 III
  • vCenter Server 4.1 (in a VM)
  • VMware View 4.6
  • iSCSI Storage with Dell Equallogic PS5000XV

Update phases:

VMware , ,

VMTN Subscription

7 November 2011
Comments off
Reading Time: 2 minutes

Mike Laverick has started something of a petition to bring back the VMTN Subscription option:

I would like to see VMware re-instate the “VMTN Subscription”. You might ask, what the hell is that? That would be fair enough because it was withdrawn many years ago, and never re-instated by VMware.

The VMTN Subscription was similar to Microsoft MSDN or TechNet – where for relatively small yearly fee you could download the core enterprise software and run it for 1year. Right now there is whole legion of home-labbers out there that have to make do and mend with evaluations that expire after 60-days. Of course this is a non problem for people working for VMware Partner, due to the NFR license, but what about other people? The VMTN Subscription program was cancelled in 2007 and never re-instated.

The announcement of the VMware Labs going public in 2012 is a step in the right direction, as also some existing benefit for vExper people (some beta program, for example).

IMHO, a new version of VMTN Subscription that include all products, early access at beta or RTM (already present in Microsoft and other similar programs), some labs and some useful material and course (for example the courses included in Partner University) could be a good and valuable solution.

But I prefer that this “package” will also a free benefit for some program where people has spend time or money or simple where they deserve it… for example for vExpert people, VMUG Advantage package, VCAP or VCDX certified, …

More information:

General, VMware

VCP5 Blueprint with study notes – Updated

3 November 2011
Comments off
Reading Time: < 1 minute

The VCP5 Blueprint with study notes has been updated with new links. Also the PDF version has been updated:

vCertification, VMware ,

VMware vSphere e View Client for Android

2 November 2011
Comments off
Reading Time: < 1 minute

After the View and vSphere clients for Apple iOS, let’s see some clients for the Android devices:

 

VMware , , ,

VMware vSphere Client for iOS

1 November 2011
Comments off
Reading Time: < 1 minute

For the View client for iPad there is any other alternative application (at least with PCoIP support), but for the vSphere client for iPad there are some other applications that can work as well of the official VMware application… With the advantage to do not require any silly virtual appliance to act as a “mobiel proxy” and also to be able to work on iPhone and not only on iPad (IMHO I think that also the vSphere Client for iPad could be adapted to the iPhone screen).

From the possible iOS applications there are:

  • iVMControl: Control VMware® vCenter and ESX devices from your iPhone and iPad – Not free and (IMHO) quite limited
  • OPS1: Operations Management on your iPhone (not designed for iPad) – Free with upgrade to Enterprise fee based

IMHO I fould OPS1 very nice and useful… the features list seems also bigger than the VMware application (but note that most features are only the the Enterprise version of this application).

VMware , ,

VMware vSphere Client for iPad

31 October 2011
Comments off
Reading Time: 2 minutes

The vSphere Client for iPad is an application created by VMware to give a minimum vSphere management ability also from a tablet (at least for some operational management tasks). The first official release was on March 2011.

But this application require a special architecture on infrastructure side, ad well described in one Jason Boche post: there must be a special “proxy” server that convert the output of vCenter Server in a simple way useful to be managed from mobile device. This “proxy” is available from VMware as a virtual appliance and can be downloaded from VMware Labs (vCenter Mobile Access Server).

With the vSphere 5, the new vSphere Web Client can replace this application? The answer is simple: no, because the Web Client is not designed for small screen and also because it’s Adobe Flash based… and the Apple iOS does not support it… Also note that the features available from the vSphere Client for iPad are only a small subset of features available from vSphere Web Client (and they are only a subset of all the features available with vSphere Client).

Same day ago giorno was release on iTunes the new version 1.2 of vSphere Client for iPad that include the following improvements:

  • Support of ESX 3.5
  • Support for vSphere 5.0
  • Migrate virtual machines without downtime using vMotion
    This feature is available via Host & VM action menus.  Virtual machines can also be two-finger flicked/dragged from the Host detail view to enter vMotion mode.
  • Ability to email vMotion validation error details to others
  • View task progress reporting on VM cards
  • Ability to refresh vCenter host list

Requirements:

  • vCMA 1.2, available at VMware Labs
  • iOS version 4.0 or later

See the videos below for an overview on setup and usage:

Step 1: Setup the vCMA
virtual appliance		 Step 2: Configure and use the
vSphere Client for iPad

For more information see also the Community page.

VMware , ,
© 2025-2011 vInfrastructure Blog | Disclaimer & Copyright