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 Delivered
Workspace PowerVC
Created by Guest
Created on Aug 7, 2017

Enhance Zoning Algorithm in PowerVC to prevent ISL hops

This enhancement is based on using PowerVC 1.3.3 in our environment that uses PowerVM, dual VIOS (each with a Fibre Channel Port to Fabric A and B), Cisco FC Switches (multiple switches with ISL between) and IBM SVC clustered storage subsystem. Currently when PowerVC does zoning for NPIV attached disks from an SVC, the target port selection is done by using a hash algorithm to spread usage across available targets from each side of an IO group within a fabric. In a larger fabric that includes multiple core and edge switches this can lead to selection of ports that cause undesired ISL hops between the VIOS and the SVC IO Group. Currently there is no logic in PowerVC to check for coexistence of VIOs port and SVC port within the same Domain ID within the fabric. Ideally we would like PowerVC to check and use the least number of hops and continue spread of port usage to keep a balanced load.

Idea priority High