Hi John,
We have about 30 clustered volumes so I typically get unimaginative and call
the nodes a variation of NetWare volume name and then either server or cluster.
For example, admin_server or print_cluster. We're a smallish shop in TSM terms
and all in one location so I can keep things
Hello, we are using Netware 6.5 OS and Tivoli 5.3.2 on clustered servers.
There is something in the opt file that we are missing. It sees the local
drives but not the netware volumes. Do you have a sample opt file that shows
how to configure the opt file correctly for clustering to be able
Of
John Bortscheller
Sent: Monday, April 10, 2006 1:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Clustered Servers and Tivoli
Hello, we are using Netware 6.5 OS and Tivoli 5.3.2 on clustered
servers. There is something in the opt file that we are missing. It
sees the local drives
Hello, we are using Netware 6.5 OS and Tivoli 5.3.2 on clustered servers.
There is something in the opt file that we are missing. It sees the local
drives but not the netware volumes. Do you have a sample opt file that shows
how to configure the opt file correctly for clustering to be able
Oh and one more thing. You'll want to edit Sys:/ETC/SMS/TSA.cfg file and change
the Disable Cluster value to yes from no. Then you will have to start and
stop SMS. That will also block cluster node visibility.
Andrew Ferris
Network Support Analyst
iCAPTURE Research Centre
University of British
Hey Andrew, thanks for the help on this. What are you using for a node name.
We were using the server name in this instance SDFP04c but now we are going to
have our Tivoli Administrator change it to FPCLUSTER_NDPS_SERVER. Also, below
I have cut and pasted our opt file. Anyway you could take
