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 (

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 PowerVC
Created by Guest
Created on Apr 25, 2017

Add SVC port selection used by PowerVC for zoning

Expand "Storage Connectivity group" or "Zoning Policy" (wherever is more appropriate) configuration details and granularity around Target Storage. Today PowerVC connects to the SVC cluster via it's service account, collects the nodes' fabric (FC) connectivity details and uses ALL OF THE AVAILABLE SVC FC node ports connected to the fabric to choose from for creating zone(s) with the VM and storage - in an "Initiator" Zoning Policy mode system port selection used by PowerVC for zoning.
In the case where SVC cluster nodes have more than the minimum (more than 4 per node) ports connected to the fabric, the SVC IO types typically is segregated among the ports for proper SVC load balance and traffic isolation - a set of the SVC ports are dedicated for Host IO, storage back-end , a set dedicated for SVC cluster inter-node communication, set dedicated for SVC replication.

PowerVC today randomly or in a round-robin fashion selects any of all of the fabric connected SVC's node ports to zone with VMs without consideration SVC port traffic type designation, ending up creating zones with SVC target ports dedicated for non Host based IO traffic and violating the port designation customer policy.

Example PowerVC LPARs are zoned with set of SVC target ports which the customer have dedicated for SVC Cluster inter-node IO only or SVC to storage back-end only IO.

Idea priority Urgent
  • Guest
    Jun 24, 2017

    The ability to "blacklist" WWPN ports from a target storage array was added in PowerVC 1.3.3, which was released on June 23, 2017.
    Thanks again for the suggestion!

  • Guest
    Apr 29, 2017

    Thanks for the suggestion - this will be considered for a future release.