If you want to force it to use the cluster ip for the cluster node, set the tcpclientaddress in the dsm.opt file used by the cluster node client acceptor & scheduler... but if those follow the cluster OK, it really shouldn't matter if they use the cluster address or the address of the server currently serving the cluster since they technically are one and the same...
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lee, Gary D. Sent: Friday, April 16, 2010 1:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tcp/ip address not correctly associated to cluster node Microsoft windows 2008, tsm client 6.2 tsmserver 5.5.4. under suse sles9 under zvm 5.3. We have a two node cluster with clustername sqltestcluster. There is one group (win 2008 no longer refers to them as groups) called sqltsmcluster. Cluster nodes are called sqltestcl01 and sqltestcl02. Sqltestcl01 and 02 back up local file resourses fine. Tried to create a cluster tsm node called sqltestcluster to match the cluster name. Defined all the schedulers, and acceptors. Services fail over correctly. However, the ip address for the cluster is never associated with tsm node sqltsmcluster. It gets its ip address as whichever node is active. Yes, there is a network name and ip address resource defined within the group sqltsmcluster. I am at a loss. Where is the link established between the tsm node_name and the tcp/ip addresss resource which moves between cluster nodes? Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 =
