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
CISCO ACI in conjunctions with VMWARE have developed the ability to apply multiple Private VLAN configurations (micro-segmentation) onto a single switchport.
Normal Private VLAN implementations require the creation of the Primary VLAN (200) which is promiscuous and designed to carry the traffic for its subdomain vlans categorized as Isolated (201) and Community (202). VLAN 201 and 202 communicate through the promiscuous port which forwards the traffic through the network. The current implementation of SEAs requires dedicated switchport configuration to handle the translation from the primary VLAN (200) to its subdomain vlans (201 and 202).
It is requested that IBM implement the ability for Trunking VEA's or the SEA, be configurable to partake of this implementation to remain compatible. We require the ability to capture dedicated Private VLAN communications over a specified Promiscuous VLAN for specific Sub VLANS for this implementation to work. I.E., we need to be able to specify in the Trunking VEA that a Specific VLAN is the promiscuous VLAN, and all control traffic should be translated over to its client VLAN. Additionally, we should be able to flag this client VLAN as Isolated (should only speak to the gateway and not others in its subnet) or Community (normal VLAN communications allowed within the subnet).
Idea priority | Urgent |
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.