Cloud Storage Solutions (Host Software Group)
Hi everyone, we have some great news for VMware SRM 4.1.x users.
The new IBM XIV Adapter for VMware vCenter SRM 4.1.x was released!
The IBM XIV Adapter version 4.1.0 adds support for XIV's GEN3 systems, and also fixes a couple of bugs.
So if you are using SRM 4.1 - you can now use it with both XIV GEN2 (microcode version 10.2.x) and XIV GEN3 (microcode version 11.x)!
You can download the IBM XIV adapter software package from the SRM 4.1.2 download page (after clicking the View Downloads button, the IBM XIV adapter is listed on the page).
Feel free to ask us any question.
Lihi Tikolsky from the IBM XIV Host Software team.
The new version adds the following enhancements for XIV users:
From now on, for each new volume you create on the storage system, the IBM storage plug-in enforces the chosen MP policy. Alternatively, if you choose Disable Multipath Policy Enforcement, no MP policy is enforced (in such a case, VMware’s default MP policy for the storage array will be in effect).
These enhancements also apply to other IBM storage systems that the plug-in supports. In addition, version 3.0.0 introduces support for IBM Storwize V7000 Unified and IBM Scale Out Network Attached Storage (SONAS) as well as various bug fixes. You can check out the release notes for more details.
After you’ve heard all that, you can now go ahead and download the IBM Storage Management Console for VMware vCenter version 3.0.0 along with its documentation from the IBM Fix Central.
We’d love to hear your thoughts and comments, so please share them with us!
The new and improved OpenStack Cinder driver for IBM SVC, Storwize Family, and FlashSystem V9000 storage systems has been released! This release complies with the OpenStack Mitaka specifications, enabling IBM storage customers to fully utilize the cutting-edge OpenStack data storage enhancements.
The new features include:
Moreover, the new SVC and Storwize Family microcode version (7.7) will be supported at its release on June 1, 2016 without any driver code change.
Upgrade and enjoy!
VMware administrator, provision new datastores for your applications yourself, using IBM Storage Enhancements for vSphere Web Client. Use abstracted storage services, provided by your storage administrator. The services are consistent with application requirements with extendable storage space and VVol support. IBM Storage Enhancements for vSphere Web Client come packaged with IBM Spectrum Control Base Edition, a nifty storage provisioning tool integrated with a variety of VMware solutions for automation, monitoring, orchestration and native support of VVols and VASA API. Check the solution overview on YouTube at https://youtu.be/tf-0LGABZK8.
To make this happen, IBM has teamed up with VMware, creating a better experience for administrators and end users. We are proud to be one of the first partners in VMware's Web Client Plug-in certification program.
We are happy to announce the release of an updated OpenStack Cinder driver for IBM Spectrum Virtualize, Storwize Family and FlashSystem V9000. This release complies with OpenStack Liberty specifications, emphasizing IBM's continuous commitment to making the cutting-edge OpenStack features available for IBM storage customers.
Another change is the enabling or disabling the fast format option during thick volume creation. As some volume operations are disabled until fast format is completed, the customer can now skip the fast format, when creating a thick volume. This makes the volume operational immediately after its creation.
Version 7.6 of IBM Spectrum Virtualize and Storwize Family will be supported after its release with no additional Cinder driver code change.
We are excited to announce release of IBM XIV SRA 2.1.0 that is compatible with VMware Site Recovery Manager 5.0.
About SRM 5.0:
Site Recovery Manager 5.0 includes three major additions to the workflow capabilities:
About IBM XIV SRA 2.1.0 with VMware SRM 5.0:
The IBM XIV SRA extends SRM capabilities and allows it to seamlessly employ XIV replication and mirroring as part of the SRM comprehensive Disaster Recovery Planning (DRP) solution.
Using the IBM XIV SRA, VMware administrators can automate the failover of an XIV system at the primary SRM site to an XIV system at a recovery (secondary) SRM site. Immediately upon a failover, the ESX/ESXi servers at the secondary SRM site start using the replicated datastores on the mirrored volumes of the secondary XIV system.
That's great ! But where can I get It ?
It's already available at the VMware download page of SRM 5.0.1 (You can click on the "Show Details" link inside the "Components" section to reveal the list of SRA components with IBM XIV SRA included)
We would love to hear from you, please leave you questions and comments below.
IBM XIV Host Software team
Alon Marx 270006TGYS 1,288 Views
We worked hard and it finally happened! Our own IBM XIV Storage Replication Adapter (SRA), version 2.2.2 is fully certified to operate with the following releases of the VMware vCenter Site Recovery Manager: 5.5, 5.5 Update1, 5.8, 6.0 and 6.1. Although this version is considered a minor release, making the SRA work with all the latest SRM versions was a challenging goal, involving a battery of compatibility tests and closely tied cooperation between the IBM and VMware interoperability teams.
Time to do some XIV mirroring :).
A new version of the IBM XIV Provider for Microsoft Windows Volume Shadow Copy Service (VSS), version 2.8.0, joins the ranks of the IBM's cloud storage solutions that support the newly introduced all-flash IBM FlashSystem A9000 and IBM FlashSystem A9000R.
We are proud to announce that the IBM XIV Host Attachment Kit has been recently upgraded to a new version - 2.5.0. This release brings support for XIV microcode version 11.6.x, IBM Spectrum Accelerate 11.5.1.x, and RHEL 7.1. In addition, this version introduces a hot feature - the host-side acceleration (HSA) for improved iSCSI communication between Spectrum Accelerate and a host.
Another change is a deprecation of the -L option of the xiv_iscsi_admin and xiv_fc_admin commands, reserving the ability to list the attached storage devices for the xiv_syslist -L command only.
Alon Marx 270006TGYS 2,003 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.
Alon Marx 270006TGYS 1,502 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
DmitriyIsayev 310000T63H 425 Views
A new version of the IBM Storwize Family Storage Replication Adapter is here. It's version 3.2.0, which adds support for the local HyperSwap for IBM SVC and Storwize systems, running IBM Spectrum Virtualize software. This new topology is used with VMware vSphere to enable transparent VMware vMotion migration and automatic VMware HA failover of virtualized workloads between physical data centers. This update:
IBM Storage Support for Microsoft Volume Shadow Copy Service and Virtual Disk Service, version 4.11.0.
A new version of IBM Storage Support for Microsoft Volume Shadow Copy Service and Virtual Disk Service has been released. This is version 4.11.0, which introduces support for the following storage system microcodes:
Also, version 4.11.0 adds support for temporary (non-persistent) read/write access to a snapshot.
ZivKalmanovich 2700044YXC 1,961 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
For nearly a year in development, a new version of IBM Storage Management Pack for Microsoft System Center Operations Manager (SCOM), 2.5.0, is out. This release brings support for the latest IBM's all-flash storage systems: super-fast IBM FlashSystem A9000 and IBM FlashSystem A9000R with microcode 12.0.x. In addition, it supports the newest releases of the following IBM storage products:
Note: FlashSystem V9000 will be supported in Q3 of 2016.
If you happen to be using one or more IBM storage systems that are serving your VMware environment, we invite you to check out our recently released ’IBM Storage Integration Server’, a software solution that consolidates all your IBM storage usage through a single backend deployment.
You can add your IBM storage arrays into the scope of IBM Storage Integration Server in just one step, by using your storage user credentials as shown in the following example from the web-based management interface:
Once added, the arrays would be available to all supported solutions, without having to re-add each storage array separately for each solution or for any future supported solution.
This single integration server reduces the amount of management traffic and shares the queried storage information with all the supported solutions. The first release, version 1.1.0, introduces support for ‘IBM Storage Enhancements for VMware vSphere Web Client’ and for ‘IBM Storage Provider for VMware VASA’.
‘IBM Storage Enhancements for vSphere Web Client’ enables native visibility and provisioning of IBM storage volumes (LUNs) within VMware vSphere Web Client. These enhancements bring the value of the already known and acclaimed IBM Storage vCenter plug-in, formally known as ‘IBM Storage Management Console for VMware vCenter’, to the new web-based VMware vSphere Web Client, which allows the integration of multiple vCenter servers instead of one.
VMware administrators who were previously daunted by the thought of the complex task of connecting and utilizing storage resources through vSphere Web Client – can now be much more relaxed with the ability to easily create and manage storage volumes in delegated storage pools, which were attached by the storage administrators on the IBM Storage Integration Server side.
‘IBM Storage Provider for VMware VASA’, previously a standalone plug-in, is now a feature of the IBM Storage Integration Server, adding the following enhancements:
· Supports the IBM Storwize family in addition to the existing IBM XIV support.
· Storage capabilities are automatically defined and assigned, eliminating the need for manual definition and assignment.
That’s about it, for now J
More to come soon!
You can download the IBM Storage Integration Server software package and the related documentation from the IBM Fix Central.
You can also view the online documentation at our information center.
As always, we would be happy to have your comments and thoughts.
The IBM Storage Host Software Group (HSG)
DmitriyIsayev 310000T63H 373 Views
We are proud to announce a new HAK release - version 2.6.0. Starting from this version, IBM XIV Host Attachment Kit has been renamed to IBM Storage Host Attachment Kit to indicate support for additional storage systems, including the newly announced all-flash IBM FlashSystem A9000 and IBM FlashSystem A9000R. In addition, this version introduces support for RHEL 7.2, SLES 12 and SLES 12 SP1. Moreover, selected Linux releases can now be run on IBM Power Systems servers, as detailed in the HAK release notes.
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,022 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