Some of the clustering solutions alias an IP address that travels with the
resource group. The scheduler can be configured to listen on this specific
address instead of "*".

The easiest way to check is to look at the output from "netstat -an | grep
-i list".

[RC]



From:
Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
07/16/2010 07:16 AM
Subject:
[ADSM-L] multiple schedulers
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



We have a bunch of AIX clusters, all setup in TSM with the standard 3 node
config
(local node/scheduler for local disk, and cluster node/scheduler for
shared
disk filesystems).
So, where the application is currently running there are 2 schedulers
(dsmcad) running.

I working on another problem I notice that all client setups are set for
PROMPTED, but do NOT
specify TCPCLIENTPORT.  So on the cluster node with 2 schedulers running,
both
schedulers must be listening on 1501.

Isn't this wrong?  If using PROMPTED mode, shouldn't each scheduler have
it's
own port to listen on specified by TCPCLIENTPORT?   I wonder how our setup
is working?  All three tsm nodes are set to the same schedule time, and
all
backups
are working good . . .somehow.

Rick

-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.



U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



---------------------------------------------------------------------