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.
Delivered in 8.3.0
We have the same request in a V9000 environment that is also based on SVC code.
As NPIV gets widly used not only on AIX but also on HyperV partitions, this functionality is really missing.
For an NPIV enabled host, a DEGRADED status is no longer acceptable if it is logged in to all fabrics and 50% of its known WWPN are actif.
The status should only switch to DEGRADED if there are less than 50% of the known WWPN logged in, or if all the WWPN of one fabric are down.
I was looking to create a new request, but being able to mark a port as "having a normal status" would be a good solution for my request. The problem is similar, I have a production LPAR where we zoned to have only 4 paths to the hosts so end up with each of the host paths to one node so they show as degraded in the SVC. While we all know it works our concern is that in the event of a problem we will be told we should "fix" this issue or just as bad that our management sees the degraded message and is concerned. So this is cosmetic but a real problem for those of us who work with storage. More to the point all the IBM materials tell us to get to four paths but the solution they present is to only use two HBAs and one port on each which is not fully redundant across the SAN Fabrics.
We have exactly the same requirement and it's visible to the customer. They are complaining that this feature is not provided by the SVC. Hope this will be implemented soon.
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