Category Archives: XIV
Actually all of them are my fault , sure %100
For to do a test vVOLs on IBM XIV IBM Spectrum Control installed , XIV added to it and related configurations done by it.
I dont know how but i made some mistakes about Service creation via IBM Spectrum Control and also after all test over destroyed all vCenter environment without clear something on IBM Spectrum Control and XIV but i know that i will be back (Terminator)
When i back and try to remove group pool from new installed IBM Spectrum Control, i faced an issue like below !
After long conversation with IBM support also find out another effect like in this link
To solve the problem the way is ;
First list the volumes from XIV (under root domain or new created domain)
Then delete such volumes in the error or you can delete whole vols which belong to same group pool if you will delete the group pool later
After all this i believe the instruction in link can be fallow but also another way
Login to IBM Spectrum Control , actually i restarted service of IBM Spectrum Control but i guess its no mandatory but like how Obi-Wan you should learn patience
Then from IBM Spectrum Control remove the group pool
Before start to create an article about storage automation with IBM XIV in VMM need to summarize something.
We are using storage systems and to manage them all need a software or cli access.Everybody know that if you are using Netapp, you have different software, different software too for EMC , also for IBM and others too ! There is not single softwate, framework or others to manage them all via single interface and there is no standards.
SNIA, they are very important because they are trying to model and create a framework for storage world. They developed SMI-S which aim is very clear “SMI-S standardizes and streamlines storage management functions and features into a common set of tools that address the day-to-day tasks of the IT environment” to read more go to this link.
Microsoft with Windows Server 2012 introduce storage management and they create a model or framework about it too. They are member or fallowing SNIA. With Storage Management API (SMAPI) using SMI-S they can manage storage systems. Not only SMI-S also its possible to manage other storage systems with SMP or storage vendor specific agent. SMP is WMI based provider, which means storage vendor put something inside their storage understand WMI request and response. You can find out development link here.
On the XIV site you have to learn more, CIM , DMTF, WBEM. CIM is common information model and its defined and published by the Distributed Management Task Force (DMTF). On WIKIPEDIA very good overview you can find out “One way to describe CIM is to say that it allows multiple parties to exchange management information about these managed elements. However, this falls short in expressing that CIM not only represents these managed elements and the management information, but also provides means to actively control and manage these elements. By using a common model of information, management software can be written once and work with many implementations of the common model without complex and costly conversion operations or loss of information. ”
WBEM as being “web-based.”
On IBM storage systems like Storwize, XIV , SVC you could face embedded CIM agents, enabled automaticly and preconfigured. You can manage the XIV system from the CIM agent that is bundled with the admistrative module.
CIM agent services in the fallowing form
Okay, ready to go …
Open VMM console, access Fabric –> Storage section and add a provider
To find out all SCVMM supported storage arrays , pls google like “Supported Storage Arrays for System Center 2012 VMM”
Choose option two “SAN and NAS devices dicovered and managed by a SMI-S provider”
Keep protocol “SMI-S CIMXML”
Set ip address of your storage system , https is mostly used one
Also you should create a Run As Account which credentials should be admin username and password of XIV
Device is discovered
You should see the all storage pools on XIV, select what pool you would like to create logical units
Choose the pool which VMM will involve and set the classification like gold,silver like usual
Fallow the process from Jobs
Now its okay , check it everything is fine in GUI or via powershell
To test everything is going well create small LUN on the pool Click to Array and top of the screen click “Create Logical Unit”
Choose the pool, set the name , size , fixed (Thick) or dynamic (Thin) and OK
Fallow the Jobs
Check from both site VMM and Storage
Not over, you can want to assign the LUN to host or something , via VMM Classifications and Pools –> Choose the LUN –> Properties –> Logical Unit Assignment –> Add
😀 ISCSI 😀 HEHHEHEHE Sorry, looks like before i have to configure Fabric Channel maybe to see the SAN informations there
Another note, related pool will be not appear when you go to one of cluster and try to add Logical Unit there …
In VMM, Storage tab click Allocate Capacity
Choose the Host groups to assign , click Allocate Storage Pools
You will see the available storage pool there , click add to send it bottom
Please care about SAN zoning manually
For a long time i was wondering how can i monitor and see the effect of VAAI in cloud environment
Simply i installed vSphere 5.1 and assign a lun to ESXi node then uploaded Windows 2008 R2 iso and installed test VM (200GB Disk) for testing cloning and zero handling.
Then remote the VM from inventory , unmount the datastore and execute the commands below from ESXi cli to disable VAAI
# esxcli system settings advanced set --int-value 0 --option /DataMover/HardwareAcceleratedMove
# esxcli system settings advanced set --int-value 0 --option /DataMover/HardwareAcceleratedInit
# esxcli system settings advanced set --int-value 0 --option /VMFS3/HardwareAcceleratedLocking
Mount the datastore again, add the VM to Inventory then try to clone the VM with choosing such disk option
its take 3 minutes : 31 seconds : 39 millisecond
then back to VAAI enable, remote the VMs from inventory, unmount datastore and execute the commands like below
# esxcli system settings advanced set --int-value 1 --option /DataMover/HardwareAcceleratedMove
# esxcli system settings advanced set --int-value 1 --option /DataMover/HardwareAcceleratedInit
# esxcli system settings advanced set --int-value 1 --option /VMFS3/HardwareAcceleratedLocking
Mount the datastore again, add the VM to Inventory then try to clone the VM with choosing disk option like above again
Before from the console execute esxtop, press u and then press f to remove some columns with pressing B, F, G, I and add VAAI things with pressing O and then enter.
Check the CLONE_RD, CLONE_WR,ZERO columns like below , all values should be increase 😀
its take 18 seconds : 90 millisecond, perfect 😀
Like it, now i can understand how Microsoft new data transfer technology (ODX) can help us !
Some helpful documents
Yesterday i was testing none XIV storage to XIV migration. Very interesting that LUN is somehow discovered but no way to see it as a datastore.
I tried to recognize datastore with existing signature or push to re-signature it but still datastore was not available.
I checked the log file vmkernel under /var/log and understand there is an issue with reservation somehow.
3th article on list said that this issue caused VAAI enabled and ATS Only datastores, but it should be fixed with 5.0 Update 1 and 5.1 but i was using 5.1 and not yet tested with 5.5
After disable VAAI like below vmware recognized the datastore.
esxcli system settings advanced set -i 0 -o /VMFS3/HardwareAcceleratedLocking
I guess for vmware point of view or virtualization point of view still storage vmotion is better way to migrate.
Some articles from vmware