Monthly Archives: October 2014


If you want to unmount a Datastore from Datastore Cluster make sure you satisfied the following conditions:

  • No Virtual machines resides on the datastore.
  • The datastore is not part of a Datastore Cluster.
  • The datastore is not managed by storage DRS.
  • Storage I/O control is disabled for the datastore.
  • The datastore is not used for vSphere HA heartbeat.

Step 1: Migrate all VMs form the datastore you want to unmount to other datastore.

Step 2: Drag the datastore you want to unmount and drop on the Datacenter name, you can drop outside the cluster but you will not get a space to drop if you have multiple datacenters in a vCenter.

Step 3: Select the datastore, click configuration tab, on the Datastore Details click properties and then uncheck the box to disable Storage I/O control.

io disable

Step 4: Right Click the datastore and select unmount.

Step 5: Select the hosts you want to unmount.

Step 6: Once you get all green, you are ready to go.

unmount datastore

Step 7: Double check the host you want to unmount and click finish.


Disable Storage IO Control (SIOC) on LUNs before a Planned Failover


DISABLING SIOC in Site Recovery Manager Plan

As I haven’t quite got the hang of blogging I’m attaching a word document with the pictures…maybe tomorrow I’ll poke around with doing it right in the post, but for now here’s an attachment.

**Use at your own Risk I’ve only tested in my environment.

Disabling SIOC in SRM Plan


1)      PowerCLI installed on each of your SRM servers. (VMware, 2011

2)      Set your execution policy in Powershell under the service account that is starting your SRM service to “remote-signed”

3)      SRM user must have rights within vSphere to change SIOC setting on datastores (Administrator works. It may be possible to do it with less permissions, but I haven’t tested that)

4)      To change the account from the default “local system” account to a service account of some kind see the following article

(Waldrop, 2009

5)      Configure User…

View original post 494 more words

Enable EVC mode on an Existing Cluster

When you  tried to enable EVC mode on an existing cluster you might see the below error:

evc mode

Virtual Machines uses more CPU features when you disable EVC mode on a cluster . When you try to enable EVC mode on a cluster it will pop up an error because the comparability mode will not match, which means you are using less features than normal.

In simple, we have to power off all the VMs on that cluster to enable EVC mode.

Enable EVC on an existing cluster to help ensure vMotion compatibility between the hosts in the cluster.


  1. Select the cluster for which you want to enable EVC.
  2. If virtual machines are running on hosts that have feature sets greater than the EVC mode you intend to enable, ensure that the cluster has no powered-on virtual machines.
    • Power off all the virtual machines on the hosts with feature sets greater than the EVC mode
    • Migrate the cluster’s virtual machines to another host using vMotion.
    • Because these virtual machines are running with more features than the EVC mode you intend to set, power off the virtual machines to migrate them back into the cluster after enabling EVC.
  3. Ensure that the cluster contains hosts with CPUs from only one vendor, either Intel or AMD.
  4. Edit the cluster settings and enable EVC.
  5. Select the CPU vendor and feature set appropriate for the hosts in the cluster.
  6. If you powered off or migrated virtual machines out of the cluster, power on the virtual machines in the cluster, or migrate virtual machines into the cluster.
  7. Any virtual machines running with a larger feature set than the EVC mode you enabled for the cluster must be powered off before they can be moved back into the cluster.

Reference :


Cisco UCS Boot from Flex Flash SD Card

Things  to check when you want to boot Cisco UCS B-Series blades with Flex Flash SD, If the FlexFlash settings are not configured properly you might see an error like below:

raid degraded

Step 1: Check “Local Disk Configuration Policy”

If you are using RAID 1, make sure you have selected Mode: “Any Configuration” and uncheck Protect Configuration.


Step 2: Boot Policy

Make sure you have selected boot mode: legacy and select sd card in your boot order


Step 3: Scrub Policy:

Make sure you have selected FlexFlash Scrub: Yes and No to other options.


Once you have selected all above option then go to Equipment->Chassis->Servers and select your server which you want boot from SD , Click Server Maintenance and Re-acknowledge.


Continue reading