Cloud Storage Solutions (Host Software Group)
We’ve recently released a new version of the Storage Enabler for Windows Failover Clustering. As you may know, it is a software agent that runs as a Microsoft Windows Server service on two geographically dispersed cluster nodes, providing failover automation for IBM XIV storage provisioning on these nodes, and enabling deployment of these nodes in a geo-cluster configuration.
The new version, 1.2.0, is mainly a maintenance release that resolves some previous limitations and provides support for the new IBM XIV and Microsoft Windows Server versions that have been released since version 1.1.0.
So, what's new in version 1.2.0? Here are the main things:
Support for Microsoft Windows 2012 R2
Support for XIV microcode versions 11.2, 11.3 and 11.4
Support for post-migrated Hyper-Scale Mobility volumes (supported in XIV microcode version 11.3 or later)
The IBM Hyper-Scale Mobility feature is used for online migration of volumes from one XIV storage system to another (for more detailed information, see "IBM XIV Storage System: IBM Hyper-Scale Mobility Overview and Usage" here: http://www.redbooks.ibm.com/abstracts/redp5007.html).
An important note to make is that previous IBM Storage Enabler versions (1.1.0 or earlier) could not be used to protect volumes that have been migrated through the Hyper-Scale Mobility feature. In such cases, you could no longer use the IBM Storage Enabler with these volumes.
Now, version 1.2.0 of the IBM Storage Enabler resolves this limitation by allowing protection after the final migration state (after performing ‘End Proxy’). Starting from this version, the IBM Storage Enabler can be reconfigured with the migrated volume and resume its protection in just a few steps.
Here is what you will need to do before the protection of the IBM Storage Enabler can be resumed on the migrated volume:
First, upgrade the IBM Storage Enabler on all the cluster nodes to version 1.2.0. Then, remove from the cluster any XIV volume that you want to migrate with Hyper-Scale Mobility. Once removed from the cluster, you can start the migration of these volumes.
When the migration process is complete, ensure that the original XIV proxy volume (which was migrated) is removed from the original XIV storage system. Also ensure that a mirror relationship between the source and XIV destination volumes exists.
You can then add the migrated XIV volumes back to the MSCS cluster.
Finally, run the following commands to add the XIV mirror resource dependency to the newly added (migrated) volumes, and to verify the configuration:
That’s it. As always, we are happy to receive any feedback!
The IBM Storage Host Software Group (HSG)
ZivKalmanovich 2700044YXC 2,024 Views
We have just made the latest version of IBM Storage Enabler for Windows Fail-over Clustering publicly available on IBM Fix Central.
I would like to highlight some of the new features and improvements introduced in version 1.1.0:
In addition several major issues were resolved, such as those related to deployments where XIV disks resided in the 'Available Storage' cluster group and issues related to XIV Mirror resource behavior upon Cluster Service failure.
The new version of the IBM Storage Enabler for Windows Fail-over Clustering and the related documentation can be found here.
Happy Clustering !
The IBM Host Software Group
Alon Marx 270006TGYS 2,007 Views
It's been a long 9 months since the release of the IBM XIV HAK 2.2.0 and we're back with a new exciting release - IBM XIV HAK 2.3.0 .
Example 1: Cleaning up a stale device
The next feature is also a response to customers needs. People using Veritas Dynamic Multi-Pathing (DMP) had issues running xiv_attach, as it always configured and initiated the native multipath framework. Two multipath frameworks on the same host is like having two managers not speaking to each other, each pulling in another direction.
Example 2: xiv_attach in presence of Veritas DMP
A third feature relates to the new release of XIV Microcode 11.5 and a feature we call Multi-Tenancy. Let's say you have two companies working on the same storage, each with it's own data that should never ever get to the other company. The storage can be divided into domains so that each is maintained by separate people, unaware of each others work. From the point of view of the storage administrator running xiv_attach or xiv_iscsi/fc_admin, he just uses his credentials to connect to the storage and everything behaves as expected. In case a user is able to see more than one domain (e.g. in case of domain per department) he is able to specify the domain the host should be using via a flag in the xiv_iscsi/fc_admin command line.
ZivKalmanovich 2700044YXC 1,964 Views
A few days ago we have a released a new version of our VASA Provider for the XIV Storage System.
For those unfamiliar with VMware VASA or with the previous version of IBM Storage Provider for VMware VASA , here is some background:
VASA stands for vStorage API for Storage Awareness, and it is an API specified by VMware and implemented by storage vendors to standardize communication between the various storage systems and the vCenter Server. The Storage Provider is a web server that handles requests from the vCenter Server in which it is registered.
The IBM Storage Provider provides a standard interface for any connected VMware vCenter Server using VMware APIs for Storage Awareness (VASA), delivering information about XIV storage topology, capabilities and state, as well as storage events and alerts to vCenter Server in real time. VMware administrators can view this information on the vSphere Client management station, and can configure storage-related operations accordingly
For example an IBM VASA Provider registered in a VMware vCenter will provide the following information in the "Storage View" tab of the vShpere Client (both web and c#)
Screenshot from vShpere Client 5.1
In version 1.1.5 several major enhancements and changes were introduced:
The IBM Storage Provider for VMware v1.1.5 and the associated documentation can be downloaded from IBM Support Fix Central here (You'll need an IBM ID to download the files).
Your comments are always welcome,
IBM HSG Team
We have just released the IBM Storage Driver for OpenStack v1.2.0 and would like to share some of the more important features in this release.
The IBM Storage Driver for OpenStack is a software component that integrates with the OpenStack cloud environment and enables utilization of storage resources provided by the IBM XIV Storage System.
So what's new in our latest release?
Support for the OpenStack Grizzly release, which adds support for multiple storage backends on a single Cinder node. During the installation of the IBM Storage Driver for OpenStack v.1.2.0 on the Cinder node, the installation wizard will enable the configuration of multiple XIV storage backends, may it be two or more separate XIV systems or storage pools on the same XIV system.
Our Storage Driver now supports Fibre Channel (FC) storage connectivity to the compute node, in addition to the already supported iSCSI protocol.
To ease the installation and setup process of the new IBM Storage driver, we have enhanced the unattended installation of the IBM Storage Driver for Open Stack with the option to use a pre-configured ini file which includes the parameters of all the storage backends to be configured during the installation process.
In addition we introduced several fixes and code stability improvements.
The software and the related documentation can be downloaded from IBM Fix Central
The IBM HSG Team
We are pleased to let you know about our recently launched IBM Storage Host Software Solutions Information Center!
In this information center, or IC, you can find the relevant documentation of all the solutions that we offer, including information of both past versions and the latest versions.
Whether our host software solution is for XIV, DS8000, Storwize, or any other IBM storage system – the release notes, user guide, or installation guide are available on the IC in either PDF or HTML format (whatever suits you best).
The solutions are categorized on the navigation tree under four main categories: business continuity, management, host connectivity, and virtualization. Keep in mind, however, that some solutions could belong in more than one category. For example, a solution such as IBM Storage Management Console for VMware vCenter is placed under the virtualization category, but it may also be regarded as a powerful management solution. For another example, our XIV and SVC adapters for VMware vCenter Site Recovery Manager, also placed under virtualization, may also be regarded as business continuity solutions.
In any case, we hope that the organization of our solutions on the IC makes sense to you, and that the information is helpful. If not, please let us know! You can use the online feedback form that is available on the IC.
Each solution has its own welcome page from which you can have quick access to the information of the available versions. The PDF publications are available on the Publications page of each solution.
If you'd like to see our list of solutions per independent software vendor (ISV), check out the Solutions by ISV page. Alternatively, to see which solutions are available for a specific IBM storage system, check out the Solutions by storage system page.
And, of course, the IC is regularly being updated and improved. You can always check what's new on the IC by visiting the What's new page.
Lastly, we would like to thank our Information Development team for making it happen.
The HSG Team
ZivKalmanovich 2700044YXC 1,730 Views
It's raining new releases here at IBM HSG, the latest software released from our team is the IBM XIV HAK v2.1.0.
The HAK is already a well known, widely used toolkit, therefore in this post we will focus on what's new in this latest release, and what will you gain by installing or upgrading to this version.
The first feature to note is the added support for version 11.3.0 of XIV microcode and more importantly for the Online Volume Migration (OLVM) feature. Now the "good old" xiv_devlist utility also presents the OLVM state of each and every volume exposed to the server, providing the host and storage administrators an easily accessible tool to stay updated with the migration state of the volumes under their responsibility, without the need to access the XIV Management GUI.
In addition, the recently introduced host diagnostic utility, the XIV Host Profiler , can now be defined as a scheduled task right from the Host Attachment Kit Wizard - xiv_attach. No need to remember to set it separately, the user will be asked during host configuration if a task should be scheduled to run the utility periodically.
We've also improved the xiv_devlist and xiv_syslist commands' CSV file format output utilities. From this release, by adding the --no-headers argument, the column headers will be omitted from the generated CSV file.
On top of the above-mentioned features and enhancements several stability issues were also fixed. The detailed list of those issues can be found in the Release Notes document coupled with the software package.
To download the IBM XIV Host Attachment Kit v2.1.0 and the related documentation , please visit IBM Fix Central. You will need an IBM ID to download the files.
The IBM Host Software Group
Alon Marx 270006TGYS 1,506 Views
It's been 4 months since the release of the IBM XIV HAK 2.1.0 and we're back with a new release - IBM XIV HAK 2.2.0.
So what's new in this release? We won't bother you with all the changes and fixes - you can find the detailed list in the Release Notes document coupled with the software package. We would however like to point out that the new release supports a new operating system - Microsoft Windows Server 2012 R2 - an important step by itself. But the main feature of this release is related to xiv_host_profiler and the way 'analyze' operates.
Since the addition of xiv_host_profiler utility in the HAK 2.0.0 release, we see growing interest in this application. Administrators want to know that the system they are working on is configured right and how to improve their settings. Makes sense, doesn't it?
The problem was that the analysis was based on the latest microcode released, and this is not the common situation in the field. Following the famous "if it ain't broken don't fix it" approach, upgrading the storage microcode is not done as frequent as we'd like it to happen. So for example, although a microcode version 11.1.x is used, the administrator would get the analysis results of 11.2.0 (HAK 2.0.0) or 11.3.0 (HAK 2.1.0) which have different rules.
To solve this problem in the new HAK release we collect the microcode versions of the connected XIV storage and the analysis is based on these versions. So if your host is connected to 10.2.4 or to 11.2.0 or 11.3.0, you can expect different results. In the following example you can see the same host running against two different microcode versions with two different analysis results.
And what about testing your configuration against a different microcode version? For example, if you have an XIV system running microcode 11.2.0 and you want to upgrade to 11.4.0 - will your host configurations still be valid? So we added an option for the user to specify the microcode version he is interested in.
To download the IBM XIV Host Attachment Kit version 2.2.0 and the related documentation, please visit IBM Fix Central.You will need an IBM ID to download the files.
The IBM Host Software Group
Lihi Tikolsky 2700057XTN 1,431 Views
We've just released the IBM Storage Driver for OpenStack v.1.3.0, get it
now while it's hot from the oven!
IBM Storage Driver for OpenStack v1.3.0 package now includes:
* OpenStack Havana Support (Including Volume migration)
* IBM DS8000 Storage System in addition to the IBM XIV Storage System
* In addition to Ubuntu 12.04 x64, we now also support RHEL 6.4 x64
* The driver package now includes a script for creating OpenStack Cinder Volume types. Read about Openstack Cinder volume types here.
Lets look at an example of the Volume types script we mentioned:
Assuming you have the following two backends configured in your cinder.conf file:
You can now run the 'create_volume_types.sh' script, to automatically create volume types to point to these backends.
After running this script, you can see your automatically created Volume types by running:
This is it!, your volume types are set and you can now use them when creating volumes:
#cinder create --volume-type IBM-XIV_hostdev31f.xiv.ibm.com_vwc_iscsi --display-name vol_hostdev31f 5
For further details, the software and related documentation can be downloaded from IBM Fix Central
orenhe 270001V1S7 1,364 Views
In this blog we'll try to provide you with the latest news from our XIV Host Software team.
We'll focus on the following products, which we develop for XIV Storage System customers:
More info to follow!