Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. 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 Delivered
Workspace IBM Turbonomic ARM
Created by Guest
Created on Nov 23, 2022

Turbonomic VLAN ID Merge and Mapping for vCenter portgroups with different names but same VLAN IDs

Our superclusters are spread between two VDS within vCenter, 1 for our legacy 10gbe network and the other for our 25gbe ACI network. vCenter requires the port group names to be unique and the unique naming is preventing Turbonomic from merging these clusters even though the VLAN ID tag and network are the same. Would like Turbonomic to identify networks off of VLAN ID vs. portgroup name so this is no longer a boundary in our superclusters.

We would like Turbonomics to be able to move VMs between the vDS example below.



Portgroup name = VPG1234


Portgroup name = VPG1234-ACI

Idea priority Urgent
  • Guest
    Nov 30, 2022

    Fully agree with this, both as a customer over 8 years ago setting up superclusters on VDI at Aetna and having seen this across multiple customers. Regardless of whether the VLAN TAG mis-matches intentionally or due to configuration typo the backing VLAN is what's actually important to understand in terms of where a VM can live. This leads down the path of reconfiguring the VLAN on a VM during a move and whatever nuance comes with that but is also a large differentiator in terms of understanding a datacenter and managing workloads.

  • Guest
    Nov 30, 2022

    Also agree here, our naming across clusters is generally based on Distributed Switch per cluster, not per multiple clusters, while backing vlan stay the same names often differ. Additionally, we have started to see much more pvlan configurations on newer vsphere deployments.

  • Guest
    Nov 28, 2022

    This has come up in the past and one broad solution would be to allow the merging of networks within our platform. Since naming is often arbitrary, allowing our clients to merge networks in policy gives them the ability to define what networks are related.