After upgrading vSphere 4 to 5 the Fusion-IO card is in minimal mode

Last week I did a VMware vSphere and VMware View 4 to 5 upgrade.  The ESXi servers for the VMware View environment uses Fusion-IO (HP IO Accelerators) PCI flash cards for there non-persistent VDI pools. After the upgrade  to vSphere 5.1 I imported the latest Fusion-IO drivers and created a baseline in vSphere Update Manager (VUM) and deployed the new drivers to the cluster.

image image

After the installation of the Fusion-IO drivers on the ESXi hosts, the Fusion-IO card was not listed in the vSphere (Web) client. Via SSH I make a connection the the ESXi servers. When i run the fio-status command the following warning appeared:

Driver is in Minimal mode: The firmware on this device is not compatible with the currently installed version of the driver.

ACTIVE WARNINGS: The ioMemory is currently running in a minimal state.

image

The warning means that the firmware needs to be upgraded. I uploaded the firmware to a central datastore and run the following command:

fio-update-iodrive firmwarefilename.fff

image

When the firmware upgrade completed, the ESXi servers needed to restart.

image

After the rebootI checked the status with the fio-status command again.  The Fusion-IO card is out of minimal mode.

image

image

After the firmware upgrade the Fusion-IO card is listed again.

Upgrading to vSphere 5.1? Check your third party software

Before upgrading to vSphere 5.1 it is important to check your existing hardware, firmware levels, drivers, vSphere versions, other VMware products that integrates and third party software if it is compatible with vSphere 5.1. Here is a list of  third party software and it’s support for vSphere 5.1 .

Software Version vSphere 5.1 Support Comment
Veeam Backup & Replication 6.5 yes  
CommVault 9 SP8 yes 3 extra SP8 post patches needed
PHDVB 6.1 yes  
Trilead Explorer 4.1.010 yes  
Quest vRanger Backup & Replication 6 no  
Trend Micro Deep Security 8 SP2 yes *4
NetApp Virtual Storage Console 4.1 yes Including SnapManger for Virtual Infrastructure (SMVI)
Symantec NetBackup 7.5.0.4 yes *3
Symantec Backup Exec 2010
2012
no Beta for Backup Exec 2010 R3 SP3 and Backup Exec 2012 SP2*2
HP Insight Control for VMware vCenter server 7.1 yes  
EMC NetWorker 8.0 SP1 Yes  
Citrix VDI-in-a-Box 5.2 Yes  
Citrix XenDesktop 5.6 No *1
IBM Tivoli Storage Manager 6.4 Yes  

 *1 Citrix XenDesktop and Provisioning Services support for vSphere can be found here: Link

*2 More information can be found here: Link 

*3 More information: Link

*4 Trend Micro Deep Security vSphere support: Link 

If other third party software vendors have support for vSphere 5.1 please let me know so I could add them to the list.

 

Last Updated:

February 2 2013, Added Trend Micro Deep Security support link

Upgrade Windows Server 2012 Release Candidate (RC) to RTM

Now Windows Server 2012 is release I tried to upgrade my lab environment from Microsoft Windows Server 2012 RC 8400 to Windows 2012 RTM. It is not officially supported to upgrade from Windows Server 2012 RC to Windows Server 2012 RTM by Microsoft.

I did the following steps to upgrade:

  • Downloaded  the Windows Server 2012 ISO
  • Mount or extract the ISO
  • Executed setup.exe
  • After several screens it is possible to choose for “Upgrade: Install Windows and keep files, settings and applications” option

image

  • Now the he following error appeared:

The upgrade cannot continue. The upgrade you needs to be running the following Windows Server 2012 build number of higher: 8508.0

image

  • use the work around by editing  the file “cversion.ini”  found in the “sources” folder. Change the “MinServer=8508.0”  line in “MinServer=8400.0

image

  • Start the setup process  again. Now repeat the above steps.  The installation checks the compatibility. In my case the following errors are displayed:

image

  • To solve the above errors I did the following things:

– Uninstall the Intel Wired PROset for Windows software

– Because the Active Directory (AD) role is installed, I needed to upgrade the AD schema by using the ADPREP /FORESTPREP and ADPREP / DOMAINPREP commands

– Reboot the system

  • Again the setup process must be started and the upgrades completes. After the upgrade the Windows Server 2012 version is Build 9200 (RTM).

image