Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage 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 (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 Submitted
Created by Guest
Created on Sep 29, 2026

Property for direct connected servers

Problem Statement:
Customers using IBM i systems are one example of environments where direct Fibre Channel (FC) connections are deployed. When such a server reboots, the FC connection is temporarily lost. In a SAN fabric environment, this is a normal and expected condition, and the storage system does not treat it as an error. However, with a direct FC connection, the storage system currently raises error 1061 ("Port Down") instead of reporting an informational or warning event.

This behaviour differs from the suppressOfflineAlert scenario. In that case, the host itself goes offline, but the FC port remains electrically and logically online because it is connected to a switch that continues to provide link connectivity. As a result, the storage system does not detect a port-down condition.

Error 1061 was originally designed to indicate a SAN fabric or physical connectivity problem. A host reboot on a directly attached FC connection is a normal operational event and should not be reported in the same way as an actual fabric failure.

Suggested solution:
Introduce a mechanism to identify hosts that are directly attached via Fibre Channel rather than connected through a SAN fabric.

For such hosts, the storage system should distinguish between an expected host reboot and an actual connectivity or fabric failure. Possible implementations could include:

  • A host-level setting that marks a connection as direct-attached.
  • Suppression or delayed generation of error 1061 ("Port Down") for direct-attached hosts.
  • Integration with the existing suppressOfflineAlert functionality, so that when both settings are enabled, a temporary loss of connectivity caused by a host reboot does not generate error 1061.
  • Reclassification of error 1061 from an error to an informational or warning event for direct-attached hosts.

The specific implementation is less important than the desired behaviour: routine host reboot operations on directly attached FC connections should not be reported as storage or fabric errors.

Idea priority Medium