Skip to Main Content

This is an IBM Automation portal for Integration 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 Not under consideration
Created by Guest
Created on Jan 31, 2023

VLAN interface as a local interface for floating IP of HA queue manager on MQ Appliance platform

Currently in MQ Appliance version 9.3.0 LTS  use of VLAN interface supporting tagged VLAN networks as a local interface for floating IP address for high availiblity queue manager is not possible. This limits use of VLAN interfaces only to standalone queue managers. Extending support of VLAN networks also for high availiblity queue managers would bring benefits in the form of more efficient use of high througoutput Ethernet ports as each of these queue managers could have been located in different IP subnet. This in consequence allows more elastic approach in designing MQ network architecture in company's infrastructure. As the maximum througoutput of Ethernet ports grows from year to year use of VLAN-tagged networks becomes more and more common limiting number of physical ports and required cabling to achieve the same network efficiency.

Idea priority Medium
  • Admin
    Mark Taylor
    Jun 5, 2023

    We recognise that this is a valid requirement. However it doesn't fit with our prioritised delivery plans for the next couple of years.

    As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.

  • Guest
    Apr 25, 2023

    I agree with this requirement! This will be more useful as company infrastructure needs to deploy single VPC on ethernet ports and does not need multiple ports to be connected from physical infrastructure to support different subnet.

    We can run multiple subnet on single Link aggregation, and align floating IP to level 3 network and (VLAN). Kindly let us know how we can get this feature enabled soon!