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 (https://ideas.ibm.com).


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 (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.

Status Not under consideration
Workspace PowerVM
Created by Guest
Created on May 3, 2016

SR-IOV with VLAN list should allow NIB

There is great potential for enhancemnet in the use of SR-IOV in failover scenarios, where the control within each LPAR is realized by using an Etherchannel over two physical adapters.

It's a pity, but nowadays such a failover scenario is only possible if on the virtual Ethernet port of the LPAR all VLAN-IDs of the physical ports are transferred without restrictions.
So the exclusion of all VLAN-tagged packets, i.e. the exclusive use of a virtual Ethernetport for „untagged“ packets (= PVID 1) is impossible with this configuration setup.

It is also impossible to explicitly select multiple VLAN-IDs of a virtual Ethernetport ; multiple VLAN-IDs can be defined, but only one activated (configured) and a n Etherchannel can't be setup in this constellation.

The work-around proposed by the IBM Support to manually define and AC Level addresses for the Etherchannel is very cumbersome and error prone (e.g. having by accident two port with the same MAC level Address on the network!!), especially with the pure bulk of necessary Etherchannel definitions (2x Etherchannel per LPAR and in sumt > 80 LPARs distributed) and not really deployable in a production environment..

Idea priority High
  • Guest
    Reply
    |
    Dec 13, 2018

    .It is correct that if a logical port's VLAN ID Restrictions is set to an option other than "Allow all" the OS MAC Address Restrictions must be set to an option other than "Allow All" for the EN0H, EN0J, EN0K, EN0L, EN0M, EN0N, EN15, EN16, EN17, and EN18 adapters. It is also correct a NIB configuration with logical ports with VLAN ID Restrictions set to an option other than "Allow All" will require the NIB MAC address to be configured in OS MAC Address Restrictions "Allow Specified" list.

    The dependancy between the VLAN ID Restrictions and the OS MAC Address Restrictions is a adapter requirement and can't be changed for the adapters specified above. However, for POWER9 based servers we've introduced SR-IOV support for the EC2R, EC2S, EC2T, EC2U, EC3L, and EC3M adapters. These adapters do not have the same dependency between the VLAN ID Restrictions and the OS MAC Address Restrictions. When a user configures a logical port for these adapters they can set the OS MAC Address restriction to "Allow ALL" and still set the VLAN ID Restriction to an option other than "Allow ALL".

    Thank you again for your RFE, it was valuable input to our development team.

  • Guest
    Reply
    |
    Jul 6, 2018

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - PowerVM
    Component - PowerVM
    Operating system - Not Applicable
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - PowerVM VIOS
    Component - Product functionality
    Operating system - IBM AIX
    Source - None

  • Guest
    Reply
    |
    May 4, 2016

    Creating a new RFE based on Community RFE #87755 in product PowerVM VIOS.