Skip to Main Content
IBM Power Ideas Portal

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 (

Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace PowerVC
Created by Guest
Created on Nov 24, 2022

Adding support to deploy LPARs with VNIC failover and 4 backing devices

A couple of customers raised the question, how they can deploy LPARs with more than 2 backing devices through the PowerVC guy. From my actual state of information, this is only possible by using the the OpenStack API of PowerVC.

The customers who had asked for this, usually want to deploy LPARs with 4 backing devices to archive the same level of redundancy like they had before with SEA failover technology and LACP with 2 ports through the GUI.

They want to have the VNIC failover deployed the following way:

- 2 VFs must be created on NIC ports attached to network switch A

- 2VFs must be created on NIC ports attached to network switch B

- In a dual VIOS architecture, the VNIC Server adapter of 1 VF from switch A and B must be served by each VIOS

In my opinion, the easiest way to implement this would be a logic like (would apply for API and GUI):

- Label all ports attached to switch A with: SW_A

- Label all ports attached to switch B with: SW_B

- In the PowerVC network definition I define the primary SR-IOV label with SW_A and for the redundancy SW_B

- During deployment (GUI, or API) I request the overall amount of VFs I want to have and PowerVC equally distributes them across the ones I defined in the network as primary and redundant adapter. Then it ensures that 1 VFs per primary and redundant adapter are attached to each VIOS. 

Maybe we can define how PowerVC is distributing VFs by something like we have it for "Fabric Redundancy" in the Storage Connectivity Group, to offer more flexibility in the future?

Idea priority Urgent
  • Guest
    Jan 9, 2023
    Thanks for the RFE, we will consider this in future release