This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Storage
Product - IBM System Storage SAN Volume Controller (SVC) / Spectrum Virtualize
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - IBM System Storage SAN Volume Controller (SVC) / Spectrum Virtualize
#Publish Today, we have VMware hosts configured to round-robin over all the paths to the volume. We're quite happy with this because there is only theoretical performance benefits to using the preferred node in most scenarios. However. With SVC stretch cluster, we have the scenario where a volume is available via two nodes, one on each site, and is being accessed by two hosts, one on each site. And we really want the host on site A to use the node on site A, and the host on site B to use the node on site B. The way we'd do this, agreeing with the suggestion in the RFE, is by having SVC report a different preferred node for the volume depending on who was asking. Today, SVC does not know it is in a stretched configuration: it does not know what hosts are where etc. If we had this feature then we would really benefit from having VMware understand our ALUA state. So, we think that the ALUA/VMware qualification work would fit best as part of making SVC stretched-cluster aware. This would be part of a future "stretched cluster enhancement" bundle item on the roadmap that we are looking to prioritize but it will not likely be in this or the following release cycle. I'll continue to keep this RFE active so that others might comment on it and provide further input.
Agreed with the RFE - I was going to submit the same request when I saw this.
,
#Publish I have discussed this with development and will size and evaluate priority in the coming weeks.