Odd-Magne,

If it's really the clustnode parm causing the client to fail then you should
definitely open a ticket with support. I've not seen that problem before, what
kind of failure message do you get?

As I mentioned, I would try the password generate parm also, it works in our
environment.

Jim

Odd-Magne Sekkingstad wrote:

> I have already changed the smsrun.bas file, my problem is simply that the
> client wont start if I specify 'clusternode yes' in the option file. My
> setup is more or less identical to the procedure from David, except I use
> or should I say want to use 'clusternode yes'.
>
> I don't really see setting 'clusternode no' as an option, one reason is
> mention by Jim, the other reason is that with 'clusternode no' the
> scheduler ask for the TSM password everytime its failed over to a new node.
> (I belive this has to do with TSM using the hostname to encrypt the client
> password, unless you specify 'clusternode yes'.)
>
> --
> Regards,
> Odd-Magne
>
> On Mon, 17 Mar 2003 16:36:22 -0500, Jim Kirkman <jmk AT EMAIL.UNC DOT EDU> 
> wrote:
> > Interesting.
> >
> > I use the 'cluster=off' switch in the smsrun file, you have to for TSM to
> > recognize the clustered volumes. I also, however,
> > user clusternode yes in the option file. I've found that using that is
> > what triggers the common file space naming for the
> > volumes. Without it each volume has the netware nodename assigned to the
> > filespace, which defeats the 'cluster aware' aspect
> > of backups if and when there is a failover. With it you're supposed to
> > get the cluster name as a prefix to the volumes. I
> > say 'supposed to' because I get the container name instead, but as long
> > as it's consistent that's fine.
> >
> > So, my advice to Odd-Magne would be to edit your smsrun.bas file (SYS:
> > NSN\USER\SMSRUN.BAS) and add the switch David has
> > documented but leave clusternode yes in the option file and see what you
> > get.
> >
> > Also, you need password generate in the option file to avoid having to
> > retype the password continually.
> >
> > "Marsh, David" wrote:
> >
> >> Actually on a Novell Cluster, Cluster node should =no. Here is an
> >> instruction sheet I created while I was setting up my clustered nodes.
> >> It
> >> works very well.
> >>
> >> Dave Marsh
> >> LAN Engineer
> >> Scottsdale Healthcare, Network Services
> >> dmarsh AT shc DOT org
> >>
> >> -----Original Message-----
> >> From: Odd-Magne Sekkingstad [mailto:oddmagne AT BLUEYONDER.CO DOT UK]
> >> Sent: Monday, March 17, 2003 1:14 PM
> >> To: ADSM-L AT VM.MARIST DOT EDU
> >> Subject: Netware6 Cluster problem
> >>
> >> Hi,
> >>
> >> I have a Netware6 cluster where I can't get the TSM client (v5.1.5.15)
> >> to
> >> work properly.
> >> I have manage to set up a client to backup the non clustered disk (SYS:)
> >> ,
> >> but when I try to configuered the backup of clustered volumes I run into
> >> some strange problems.
> >>
> >> The option file is located at cd1shr1:/tsm/dsm.opt with the following
> >> changes from the default dsm.opt that is used for backing up SYS:
> >> clusternode yes
> >> nodename hwcd1shr1p
> >> httpport 1582
> >> domain cd1shr1:
> >> nwpwfile yes
> >> passworddir cd1shr1:/tsm
> >> schedlogname cd1shr1:/tsm/log/dsmsched.log
> >> errorlogname cd1shr1:/tsm/log/dsmerror.log
> >>
> >> When I load the client with "dsmc q sched -optfile=cd1shr1:/tsm/dsm.opt"
> >> I
> >> get the following error message:
> >>
> >> ANS1036S Invalid option '' found in option file '' at line : 0
> >> Invalid entry ''
> >>
> >> This error message is logged in cd1shr1:/tsm/log/dsmerror.log, so at
> >> least
> >> the client is reading the option file.
> >>
> >> If I remove the line 'clusternode yes' from the option file the client
> >> works fine, except you have to retype the password everytime the cluster
> >> failsover.
> >>
> >> Do anybody have an idea what is wrong, and how to fix it?
> >> (Will call Tivoli support tomorrow, since it past office hour today)
> >> --
> >> Regards,
> >> Odd-Magne
> >>
> >> ------------------------------------------------------------------------
> >> Name: Procedure for setting TSM on a NetWare Cluster.doc
> >> Procedure for setting TSM on a NetWare Cluster.doc           Type:
> >> WINWORD File (application/msword)
> >> Encoding: base64
> >> Download Status: Not downloaded with message
> >
> > --
> > Jim Kirkman
> > AIS - Systems
> > UNC-Chapel Hill
> > 966-5884

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884