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
Created by Guest
Created on Jun 9, 2015

Expand "SET FAILOVERHLADDRESS" to node granularity

On Server Version 7.1 a function "SET FAILOVERHLADDRESS " was introduced to allow the failover IP to be different then the IP used for replication, this is a step in the right direction.
However on TSM Servers with multiple IP's with clients in different subnets it would be good to be able to configure a "FAILOVERHLADDRESS" on a per node basis using the "update node" command. This way all clients can use automatic failover using IP's they can actually reach and not just the ones being in the same subnet as the IP configured using "SET FAILOVERHLADDRESS"

Idea priority High
  • Guest
    Reply
    |
    Jul 29, 2015

    When multiple clients connect to the same server - maybe through different types of connections (and some using NAT, others not, and those who do - might be on different connections with differetnt target IP addresses), then having a single HLFAILOVERADDRESS is problematic.
    It would be great, if the system HLFAILOVERADDRESS would be used by default - unless a HLFAILOVERADDRESS has been set on a node level.

  • Guest
    Reply
    |
    Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family