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 Not under consideration
Workspace IBM DS8000
Created by Guest
Created on Jan 27, 2021

Errors for RSYSLOG should show more detail.

We enabled RSYSLOG pointing to a test syslog server. The action appeared to work properly but very soon after the status of the server was shown as being offline. However, when I queried the syslog server data was being sent so it wasn't truly offline. After opening the PMR and having IBM collect a trace we were told that TCP resets were happening and most likely due to a firewall between the syslog server and the DS8K. When we eventually pointed to a production syslog server the rsyslog server stayed online from the DS8K's perspective. The OFFLINE status of the server was certainly confusing since data was still being received on the other end. We also would expect to have some additional details on the error itself. If we had been informed that TCP resets were happening we could dig deeper into our end and engage our network experts. Instead we needed to engage IBM and they needed to collect network traces before telling us why this happened.

Idea priority Low