This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.
This is same/similar request as in RFE 119869 to provide DLPAR virtual adapter option from GUI for vios.
Previous versions allowed us to add a vSCSI adapter to a VIOS. That option was removed. Yes we would like to add a vSCSI and storage latter. Would be nice if the HMC would then add the vSCSI adapter to the client LPAR. Even though the HMC is supposed to see new storage it does not. This means we are not able to use the GUI to add disk to a client, because the HMC does not see the new disk.
Because of this we must:
1) Add the vSCSI to the VIOS profile.
2) Shutdown the VIOS.
3) Activate the VIOS.
4) Via VIOS CLI add disk to the VHOST/vSCSI addapter for the client.
This means, during the shutdown/activate, we have one VIOS managing the clients instead of two. This is a performance hit and an a availability problem if the second VIOS fails or has a configuration issue during the shutdown/activate of the other VIOS.
Second question; Yes we have had several instances, while adding the first disk to a client, where the vSCSI/Vhost was created on one VIOS and not the other. When that happens we must perform the above steps on the failed VIOS assignment.
Thanks for the info.
When a vSCSI adapter is added to a VIOS, guess the intention is to add a client adapter and attach storage eventually. That's why the previous comment was about attaching a storage which creates the vSCSI adapters in VIOS as well as the client partition. Is there any specific use case to create a vSCSI adapter only in VIOS without a corresponding client adapter or storage mapping?
Also, on the point of "Note that the HMC did assign a vSCSI to VIO1, so the process is broken" -- Can you please specify what was broken? Was it a case that HMC assigned only the server adapter but client adapter was not created when attaching storage or any failure case where the vSCSI of VIO1 was left over?
Missed the point! I want to create a new vSCSI adapter for a VIOS!! That is what I stated in the beginning! This was taken away from us to dynamically allocate a vSCSI adapter for a VIOS!
Hi,
With the Enhanced UI, you can directly attach the vSCSI storage to the partition and adapters are created by the HMC automatically (or you can choose an existing server adapter). Please see the blog at https://www.ibm.com/developerworks/community/wikis/home?lang=en_us#!/wiki/Power%20Systems/page/Partition%20Virtual%20Storage%20Management%20using%20HMC%20Enhanced%20UI for mode details.
In your case, are you not able to attach storage to the partition even with the VIOS in active state with rmc connection to HMC ? On the "new hdisk as available" - is this a case where your provision a disk from SAN to the vios and VIOS configuration is not yet refreshed to see the new disk ?
Thanks.