NSS Mirroring with NWCS

Setting it up

Prerequisites

• NetWare 5.1 installed on all servers– Upgrade to SP1– Or use International version

• All servers connected to SAN• SAN Storage

– Create one or more drive arrays– Always reserve 10MB free space for SBD partition

1. Assign Server ID’s to all nodes

• To assign server ID– Edit AUTOEXEC.NCF on each server

– Add the following new lines before NSS loads• mm assign server id=<serverid>• scan for new partitions on FFFFFFFF

– ensures all partition information is reset

– <serverid>• 16 byte ASCII variable• Must be unique for all servers• Suggested naming convention

– use ClusterNode1, ClusterNode2, ClusterNode3….– OR use the servers name

2. Create Virtual Device Partitions

• At one server ONLY• Load NWCONFIG

– Select Storage Array #1• Create Virtual Drive Partition #1

– Select Storage Array #2• Create Virtual Drive Partition #2 (same size as #1)

– Mirror together and allow to sync, if necessary– Repeat procedure is other arrays require mirroring

• Quit NWCONFIG

3. Label Virtual Disk Partitions

• Use same server in Step 2.– Assumes only one mirrored partition being setup

• System Console– :vrdev /list partitions– Note down the two Partition ID values

• One Partition ID shown per Virtual Disk Partition

– Label each partition with the same name• :mm assign partition label <pid#1>=<partition_name>• :mm assign partition label <pid#2>=<partition_name>

3. Label Virtual Disk Partitions (cont..)

• Example:– Using vrdev /list partitions shows that:

• Partition ID #1 = 0xD and Partition ID #2 = 0x10

– Suggestion• Name the Partition the same as the NSS volume name

– Even though the NSS volume has not been created yet

• Example:– mm assign partition label 0xD=nssmirror– mm assign partition label 0x10=nssmirror

– Use “vrdev /list partitions again• to check partition name has been assigned

4. Create NSS Volume

• NWCONFIG (on server in Step 2.)– Assign NSS ownership to the Virtual Partition

• Which is mirrored (so only one entry seen)

– Create a single storage group– Create a single volume for the storage group

• Name this volume “NSSMIRROR” (example)

• Edit AUTOEXEC.NCF on all servers– NSS /AutoDeactivateVol=ALL

• must be after ‘mm assign…’ and ‘scan for…’ commands• in Step 1.

5. Add VRDEV to all servers

• Check all server’s• Add “LOAD VRDEV.NLM”

– To startup.ncf– Last line, after HAM driver load statements

• Restart all servers

6. Install NetWare Cluster Services

• NO change in the install procedure.

• After installation– make sure all servers join cluster– load ConsoleOne at Client

• convert “nssmirror” volume to become a cluster resource

7. Update LOAD script (“nssmirror”)

• Modify the LOAD script as follows:– Items in red are the additions

• vrdev /ASSIGN OWNER=nssmirror• nss /activate=NSSMIRROR• mount NSSMIRROR VOLID=254• trustmig NSSMIRROR watch• NUDP ADD <clustername>_NSSMIRROR_SERVER

<ipaddr>• add secondary ipaddress <ipaddr>

8. Update UNLOAD script

• Modify the UNLOAD script as follows:– Items in red are the additions

• del secondary ipaddress <ipaddr>• NUDP DEL <clustername>_NSSMIRROR_SERVER

<ipaddr>• trustmig NSSMIRROR unwatch• dismount NSSMIRROR /force• nss /forcedeactivate=NSSMIRROR• vrdev /RELEASE OWNER=nssmirror

9. Test Procedure

• Bring Cluster Volume resource on-line– Check that volume mounts on server– Check Mirror status

• should be 100%

• Migrate volume to another server– Check that volume mounts– Check Mirror status

• should be still 100%