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 (

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 Future consideration
Created by Guest
Created on Feb 10, 2022

Well-known tcp ports are run out by TIME_WAIT state if recalls are distributed to cluster nodes

Product: IBM Spectrum Protect for Space Management
Actor: User needs improvement of TCP port usage

The product is bundled in our product IBM Spectrum Archive Enterprise Edition for space management of IBM Spectrum Scale.

Description: In multi-nodes cluster environment,
dsmrecalld on owner node distributes transparent recall requests to other nodes by default. Then distributer dsmrecalld daemon polls other nodes for completion of the recalls by every 100msec using ports provided by rpcbind of the system. It uses many well-known ports and makes all the well-known port range ( 512 - 1023 ) into TIME_WAIT state. It disturbs other service like rshd to obtain ports from rpcbind.

We need mitigation of this matter in distributed recall environment.

Idea priority Medium
  • Guest
    Feb 13, 2022

    submission of this RFE was suggested by HSM development.

  • Guest
    Feb 13, 2022

    There is no firewall between the nodes.
    also, there are no Spectrum Protect server/client ( a.k.a TSM).
    HSM clients are running with IBM Spectrum Archive Enterprise Edition (LTFSEE) as a bundled component on multi-node cluster environment.
    Development has already determined in CSP skill case specified on this RFE item that inter-node communication between dsmrecalld uses so many ports
    to check completion of recalls that were requested to other cluster nodes. and it is by current design and it should be re-considered for improvement.

  • Guest
    Feb 12, 2022

    Are there any firewalls between the nodes?
    Spectrum Protect uses meta data communications and data communications on different sessions if client side deduplication is being used.
    And if there are too little traffic going over the meta data session, than a firewall might terminate the session.

    Other solutions?
    At spictera we have created a filesystem for IBM Spectrum Protect, making it possible to mount the IBM Spectrum Protect storage data as a mountpoint on your server.
    The benefits of this is that there are no need for local stubfiles, which can be out of sync with the actual data. There is built in failover, and utilizes allmost all features available on a normal BA-client, such as filtering (inclexcl), encryptions, dedup, compression, ...

    # mount -t spfs /archive
    Or as a drive letter on Windows

    Regards Tomas Dalebjörk