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.
See this idea on ideas.ibm.com
With situations in which client changes zoning, this also includes when they are implementing NPIV from just physical ports (transitional), it is common to have bad manipulation from the multipath driver over the host paths which causes previous paths to show as "inactive" status in the lsfabric even after correcting the zoning and the multupath side or hosts or even cause the host object to stay permanently in degraded state due to false reporting of amount of paths / balance number of paths across nodes.
The only ways to remove a permanent inactive entry from lsfabric are the following:
- Recreate the host object by removing mappings, wwpns and deleting the host object then recreate. / The cons of doing this is that this requires host downtime and if the config in regards of mappings and ports is big, requires great effort from client in order to solve this cosmetic bug.
- The other way is to reboot both nodes from the same IOGroup where the situation is observed. This will reload the FC logins on the ports and recreate the lsfabric entries forcing the permanent inactive paths to be gone. Clients tend to complain about this stating that taking a node reboot is too aggressive to solve a cosmetic thing or do a clearance on the lsfabric table.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you for submitting this enhancement request. We have reviewed with the architects and support team.
We have an automatic poll to auto-close logins if they've been un-zoned. However some switch vendors allow "test packets" through even if the devices aren't zoned any more. At this point lsfabric is correctly reporting that we have a login resource tied up - so this is actually useful information. There is not much more we can do here.
However, there is a related request to let people disable/re-enable a single FC port using the CLI, which will give you some other options to clean up with less disruption than rebooting a node.
We appreciate your input and hope that you will continue to submit enhancement requests, as this feedback is a key component to shaping the future direction of Spectrum Virtualize and FlashSystem family.
Thanks,
FlashSystem Team
philipclark@ibm.com
Thank you for submitting this Idea. We are currently evaluating your request.
Thanks,
SpecV Team
philipclark@ibm.com