Help with the steps to setup a 2 Server NW6.5 cluster

[Beck1]

I am setting up a 2 server netware 6.5 clustering a SAN with 3 volumes.
What are the steps to go about this,ie
Do I install NW6.5 then cluster services software and then run NSSMU
for pools.partitions volumes etc.
Basically do I configure the SANs volumes using NSSMU first or do I install cluster services software first.

Regards and thanks for the advise.

 

[terry712]

install both servers as 6.5
install the products that you want on them
if you are going to host dns / dhcp or slp from these then read the appnote of oct 2003.
install cluster services - use nwdeploy from cd - nice and easy and it takes you through. - this will setup a sbd partition - which is on the shared storage.
then you create the partition
create the clustered enabled pool - it will ask to to give it a virtual ncp server address
create volumes - clustered enabled of course

if you are using iscsi - then read the appnote from last month - setting up a 2 node 6.5 sp1 cluster
download the clustering services pdf for 6.5 from docs site - it's only about 20 pages but it's step by step

 

[terry712]

forgot to say - remember it's different from 5 - were it was the volume that was clustered

the pool is clustered so you may be best with 3 pools for the 3 volumes

and remember always use the virtual address in scripts

 

[Beck1]

Thanks for the advise Terry.

Just one thing can I install the nw6.5 Servers
and install cluster services software without the
SAN being present, because it hasnt arrived yet.
Basically how far can I go without the SAN.

 

[terry712]

what type of san?

basically you can go as much as usual - ie server's fully build , patched updated and playing in tree. you can only do the sys - you cant do cluster bit but thats 20 secs - it will check for shared storage and you will have none

if the san is a fibre solution then i would recommend taking a day to play especially if use securepaths or such like - if it's a isci shot then it's just a pci card and slap that in as norm

play with the rolling across and dont just check from your side of router - check from another site if applicable. the your cisco router has specific default settings the the arp cache is stuck for 4 hours and you can see when rolled