- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Firmware 3.x Initiator Group creation using the vC...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2016 04:42 AM
тАО11-18-2016 04:42 AM
I noticed that since firmware 3.x when creating a volume using the vCenter plugin something changed with the initiator groups usage.
In the previous firmware when I would create a volume and selected a cluster in the vCenter plugin then the volume would be added to a initiator group that matched the cluster or a new initiator group would be created for this cluster.
This is really nice in case a host is moved to a different cluster, as you only have to edit one initiator group and all volumes in that group would be accessible or inaccessible).
In firmware 3.x I noticed that when creating a new volume a new initiator "group" is created for each individual host in that cluster (even when a initiator group that matching this cluster exists).
This means that one volume is now added to in this case 9 "initiator groups" instead of a single one.
If I now move a host to a different cluster I have to remove this "initiator group" from all volumes and add it to the volumes in the other cluster.
This is a really time consuming business.
I spoke to support and this is by design to match the workflow with iSCSI and FC arrays, but for me this is a real setback leaving me with lots extra work.
Are any of you experiencing the same?
I would like to see the previous workflow back in place or at least a possibility to choose how one would like the workflow to be.
I would also like to know how others think about this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2016 05:32 AM
тАО11-18-2016 05:32 AM
SolutionHi Rick, I understand the time spent over this task and the frustration that you get out of it, apologies for that.
As a side note, we do have an RFE that will allow unmount of a datastore operation via the plugin, and not just deletion.
Such operation can also remove the initiator group from the Nimble volume.
You can use the mount datastore option to mount the datastore on a host in order to avoid the adding of inititator group task.
Additional note: the mapping of 1-1 initiator group and host iqn is also driven by our VVol integration and we had to perform the change.
I hope you find this information useful.
Thanks,
Moshe.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2016 05:45 AM
тАО11-18-2016 05:45 AM
Re: Firmware 3.x Initiator Group creation using the vCenter plugin
Hoi Moshe,
Thanks for your reply.
"Additional note: the mapping of 1-1 initiator group and host iqn is also driven by our VVol integration and we had to perform the change."
I didn't know that yet, if this is indeed needed then so be it, as we would like to migrate to vVols then we just have to accept this for now.
Additional question: Do you possibly know if the max volume limit will be upped, as we have about 1500 VM and the current volume limit is 1024 we can't use vVols yet.
Thnx,
Rick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2016 06:15 AM
тАО11-18-2016 06:15 AM
Re: Firmware 3.x Initiator Group creation using the vCenter plugin
That's correct we're increasing the volume number limit in the next major release, like all vendors that integrate with VMware and VVol, this limitation needed to be removed
Thanks!