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.
See this idea on ideas.ibm.com
We use LPARS with DualVIO on Power Systems. We need to track Diskmappings to Hosts in Dokumentation, also need to add an delete disk mappings als Virtual Target Device on VIO for the LPAR.
At start we get 3 vhosts per LPAR in ascending order, the order is the same on borh VIOS.
If we use Live Partition Mobility (LPM), we always lose this order and in addidtion we get a different order on boith VIOS. This makes it more complex an increase human Error possibility. We want to keep a well documented and simple as possible Landscape.
Here is what happend:
In addition one more clarification (output from lsdev –slots) :
At Start:
SOURCE - VIO1
U8408.E8D.214810V-V1-C38 Virtual I/O Slot vhost6
U8408.E8D.214810V-V1-C39 Virtual I/O Slot vhost7
U8408.E8D.214810V-V1-C40 Virtual I/O Slot vhost8
SOURCE – VIO2
U8408.E8D.214810V-V1-C38 Virtual I/O Slot vhost6
U8408.E8D.214810V-V1-C39 Virtual I/O Slot vhost7
U8408.E8D.214810V-V1-C40 Virtual I/O Slot vhost8
After Live Partition Mobility to TARGET System
TARGET – VIO1
U8284.22A.21E150V-V1-C38 Virtual I/O Slot vhost6
U8284.22A.21E150V-V1-C39 Virtual I/O Slot vhost8
U8284.22A.21E150V-V1-C40 Virtual I/O Slot vhost7
TARGET – VIO2
U8284.22A.21E150V-V2-C38 Virtual I/O Slot vhost7
U8284.22A.21E150V-V2-C39 Virtual I/O Slot vhost6
U8284.22A.21E150V-V2-C40 Virtual I/O Slot vhost8
In conclusion – we would like to preserve the vhost configuration from the source VIO servers.
Idea priority | High |
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.
The LPM feature to preserve virtual slot numbering across the LPM operations was added several years ago (p6 timeframe?). If the slot is available on the destination, it will be used / preserved, as well as the device name. Please resubmit if your seeing different behavior.
The LPM feature to preserve virtual slot numbering across the LPM operations was added several years ago (p6 timeframe?). If the slot is available on the destination, it will be used / preserved. If you prefer that the LPM fail if the same slot is not available, then specify the slot number during LPM setup.
Creating a new RFE based on Community RFE #89898 in product PowerVM VIOS.