EMC have released XIOS version 4.1.10-33 and XMS version 4.2 recently, and although they look like minor point releases, there are some long awaited improvements that I certainly have been pleased with.
The first one is a PowerShell support. Readers of this blog will now I’m a big PowerShell guy. I use it for automation, workflows, provisioning…..and loads more.
Download HERE and install in just a few clicks and next, next, next..
I suggest you also install the root certificate from your array(s) also, to avoid any verification warnings or issues. Load the XMS splash screen and click on and install the certificate into the local Trusted Root Certification Authorities cert store.
Check if the module has installed correctly (the installer finishes kind of abruptly) by running a list available, checking for the XtremLib module;
|
1 |
Get-Module -ListAvailable | Select-String -pattern Xtremlib |
So we’re all good, let do some common tasks; Connect a session to your XMS with the following command; I manage 2 x clusters from a single XMS as detailed HERE.
|
1 |
New-XtremSession -XmsName MYXIO01 -Username u-name -Password p-word |
There’s 122 included functions in this release so let’s take a quick look at some common tasks;
Check Array health; (all that are connected to the XMS in session)
|
1 |
Get-XtremClusters -Properties sys-health-state | ft -autosize |
Get-XtremVolumes will return all the properties for all created volumes on all connected arrays;
With lots of data this result-set is typically in-elegant, so filtering via index id’s or sys-names can help tidy it up.
Here I’m going to retrieve all the Volumes that are < 2TB, sort them via Cluster and show how much space is in use and then sort them by index number;
|
1 |
Get-XtremVolumes | sort index | Where {'$_.vol-size' -lt '2147483648'} | ft index, name, logical-space-in-use -AutoSize |
So now we’re seeing things a little more interesting, but of course we want more.
Let’s see the realtime iops stats and the latency (rw) for the Volume with index 11. ( i’m using a cluster index number as I have multiple Clusters attached, Latency is measured in microseconds)
|
1 |
Get-XtremVolume -XtremClusterName 2 -VolName 11 -properties ('avg-latency','iops') | ft name, avg-latency, iops -AutoSize |
Now let’s create a volume; This will be called ‘XIO-500test‘ and be 500GB. I’ll also give it a tag (must be an existing tag).
|
1 |
New-XtremVolume -XtremeClusterName 2 -VolName XIO-500test -VolSize 500G -TagList ('/Volume/Testing123') |
Of course, it’s only good if we can map said volume to a Intitiator Group. You can retrieve the list of exiasting Initiator Groups using Get-XtremInitiatorGroups or create a new group with New-XtremInitiatorGroup.
How about we create 10 volumes and map to an initiator Group and again, assign a tag ? While there doesn’t appear to be a parameter or property for this yet, it’s easy to do with a simple loop;
|
1 2 3 4 5 6 |
$pre = "XIOtest" $vols=@(1..10) | %{"$pre"+$_} foreach ($vol in $vols) { New-XtremVolume -XtremClusterName 2 -VolName $vol -VolSize 10G -TagList ('/Volume/Testing123') New-XtremVolumeMapping -XtremClusterName 2 -VolName $vol -InitiatorGroup XIO-test } |
Did it work ? Of course.
Notice anything different about the ui ? *
There’s a heap more in this, and I’m quite happy with it so far. I’ll write more as I use more of the functionality.
GO. AND. GET. IT.
*…up next HTML5 goodness.