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 Jul 1, 2016

PowerVC odd behavior with Cisco enhanced zoning

PowerVC doesn't manage uncommited zones in a Cisco Enhanced Fabric Zoneset. To me, this should be a defect, not a new feature request. Please review the associated PMR.

I believe that PowerVC should know that a zone is uncommited and work within those constraints. The whole point is to have validations so that SAN admins working on the Fabric outside of PowerVC (we have many other users using our fabrics) can do work and PowerVC would be smart enough to know to either fail immediately or retry until the previous work on zoning is commited. The same should apply when deleting a VM. If a zone is uncommited, it should wait until it is commited to delete or timeout after X minutes with an error, not through a "vm successfully deleted' and leave dozens of zones stranded.

Are we expected to go to a SAN administrator each time to make sure there's no zoning work in progress? This is not feasible and defeats the purpose of using PowerVC to simplify VM builds.

Idea priority Urgent
  • Guest
    Reply
    |
    Jan 27, 2017

    Thank you for the report on this issue. This issue has been fixed and should be available in the latest version of PowerVC 1.3.2.

  • Guest
    Reply
    |
    Jul 2, 2016

    Creating a new RFE based on Community RFE #90893 in product PowerVC.