How to map drives with Novell Clustering Services

  • 7014886
  • 09-Apr-2014
  • 29-Apr-2014

Environment

Novell NetWare Cluster Services
Novell NetWare 5.0
Novell NetWare 5.1
Novell NetWare 6.0
Novell NetWare 6.5

Situation

How to map drives with Novell Clustering Services.

Resolution

You must use map the drive to the cluster volumes (Virtual Server Objects), not to the Cluster Master IP Resource.

Login Script Command Syntax
map l:=.Clustername_volumename.context

Examples:
map o:=.my-cluster_vol2.Corp.EMA:
map root p:=.my-cluster_vol6.CORP.EMA:\home

Or you can use the secondary IP address of the volume followed by the volume name only (again, map to the virtual server object and not the cluster object).
Example:
map h:= \\137.46.52.1\NSSVOL1
map g:=\\137.46.52.2\NSSVOL2


When the workstation is already up, but no drives are mapped to Cluster volumes, here are the preferred methods to map the drives:
1.  Browse to find the Cluster enabled volume through Network Neighborhood and map to that.
2.  \\<IP ADDRESS>\<VOLUME NAME>

You can map a drive to the server that is hosting the volume currently, but the mapping will not be available in the event of a failover.  If the hosting server of that volume crashes or drops out of the cluster for any reason, the drive mapping will be lost.  The drive mapping either needs to follow the IP address or the DS object, either of which can be resolved anew when a failover occurs.  

Additional Information

For NetWare:

CVSBIND.NLM can also be used to ensure short names are propagated in SLP.

To use CVSBIND.NLM, follow these steps:
Edit the LDNCS.NCF (load NetWare cluster services) and ULDNCS (unload NetWare cluster services) scripts. Add commands to load and unload CVSBIND.

SYS:\SYSTEM\LDNCS.NCF

Add this command
 CVSBIND
after this command
 CMON
but before this command
 CLUSTER JOIN

SYS:\SYSTEM\ULDNCS.NCF

Add this command
  unload CVSBIND
after this command
  CLUSTER LEAVE
but before this command
  unload CMON

CVSBIND commands should be added to cluster volume resource load and unload scripts as described below.  The syntax is similar to the NUDP ADD and DEL commands.  

Add the CVSBIND ADD command to the cluster volume resource load script before the NUDP command.

Add the CVSBIND DEL command to the cluster volume resource unload script after the NUDP command.

The CVSBIND command is case insensitive but the server name should be entered in upper case.

Example cluster volume resource load script

nss /activate=TESTVOL
mount TESTVOL VOLID=254
trustmig TESTVOL watch
CVSBIND ADD CLUSTER_TESTVOL_SERVER 10.10.10.10
NUDP ADD CLUSTER_TESTVOL_SERVER 10.10.10.10
add secondary ipaddress 10.10.10.10

Example cluster volume resource unload script

del secondary ipaddress 10.10.10.10
NUDP DEL CLUSTER_TESTVOL_SERVER 10.10.10.10
CVSBIND DEL CLUSTER_TESTVOL_SERVER 10.10.10.10
trustmig TESTVOL unwatch
dismount TESTVOL /force
nss /forcedeactivate=TESTVOL

The CVSBIND ADD and DEL commands will add or delete bindery service entries in the SLP namespace for the supplied virtual server name and its corresponding IP address. NetWare bindery emulation is implemented via the SLP URL service:bindery.novell. You can inspect the SLP namespace with the following console commands:

display slp services
display slp attributes service:bindery.novell:

Example of Mapping when using CVSBIND.NLM
Windows Explorer: \\cluster_volume_server\volume

Example of Windows Explorer mapping using UNC without CVSBIND.NLM
\\TreeName\context\volumename
\\Novell_tree\novell\cluster_share
In the above example:
TreeName=Novell_tree
Context=novell
cluster volume=cluster_share

Note:  Always execute CLUSTER LEAVE or ULDNCS before downing a cluster node when using CVSBIND.  There have been reported instances of server abends when issuing the DOWN command first.

Formerly known as TID# 10027333

Change Log

29Apr2014 - Earle Wells- Reworded and reorganized without changing content, released TID