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 Sep 7, 2014

Client Deployment Request

I understand it is a requirement of automatic client deployment that clients contact the server on the address as configured by the SERVERHLADDRESS.

In our environment, the SERVERHLADDRESS set on the TSM Server cannot be contacted by the client being deployed.

Sydney Waters production TSM Server has two NICs, one with a "Corporate network" IP address, the other with a "Replication network" IP address.
The two NICs are on separate 10.x.x.x subnets. It is set up this way to ensure TSM replication is separate and does not impact the "Corporate network", ie - production.

The SERVERHLADDRESS is set to the "Replication network" IP.

Clients cannot use the "Replication network", they use the "Corporate network" to contact the TSM server.

Clients using the "Replication network" are failing automatic client deployment because the SERVERHLADDRESS subnet is not correct for their address.

Manually upgrading approximately 700 clients is extremely time consuming to say the least. Automating this process would be more productive.
After all, this is what client deployment achieves.

I would like to get automatic client deployment to work with multiple NICs/IP/subnets.

If there is any other information we can provide please let me know.


Cheers
Nev

Idea priority Medium
  • Guest
    Reply
    |
    Jun 26, 2015

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.

  • 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

  • Guest
    Reply
    |
    Sep 7, 2014

    This is critical for dual networked servers.

  • Guest
    Reply
    |
    Sep 7, 2014

    Attachment (Description)

  • Guest
    Reply
    |
    Sep 7, 2014

    Attachment (Use case)

  • Guest
    Reply
    |
    Sep 7, 2014

    Attachment (Use case)