Cluster resource mounts in NSS but Fails to mount in NCP with no errors.

An NSS Cluster resource would come online without any errors but was not accessible through NCPCON volumes command.  The volume was physically mounted in /media/nss/<volumename>, however it was not truly mounted in NCP.

Modify NSS Cluster resource load script to have a valid VOLID=xxx to a valid and unique number (0-254).   This number is automatically populated when creating a cluster resource through NSSMU or iManager.  For clustered NCP volumes we start at 254 and work our way down.

It was noticed the volume ID was set to 255:

An invalid Volume ID was used in the manual creation of the cluster resource load script.
Documentation states:
Volume ID    252 (valid values are 0 to 254)

Excerpt The resource load.out file:
Mon Sep 16 23:04:29 EDT 2013
+ '[' '!' 0 -eq 0 ']'
+ return 0
+ exit_on_error ncpcon mount Test=255
+ eval ncpcon mount Test=255
++ ncpcon mount Test=255
... Executing " mount Test=255"
The following volume[s] were mounted:
    Test    ID:255
1 volume[s] were mounted.
... completed OK [elapsed time = 212 msecs 59 usecs]
+ rc=0
+ date
Mon Sep 16 23:04:29 EDT 2013
+ '[' '!' 0 -eq 0 ']'
+ return 0
+ exit_on_error ncpcon bind --ncpservername=Test --ipaddress=10.0.0.10
+ eval ncpcon bind --ncpservername=Test --ipaddress=10.0.0.10
++ ncpcon bind --ncpservername=Test --ipaddress=10.0.0.10
... Executing " bind"
... completed OK [elapsed time = 498 usecs]
+ rc=0
+ date
Mon Sep 16 23:04:29 EDT 2013
+ '[' '!' 0 -eq 0 ']'
+ return 0
+ exit_on_error service grpwise start Test
+ eval service grpwise start Test
++ service grpwise start Test
Starting  [Test]..done
+ rc=0
+ date
Mon Sep 16 23:04:31 EDT 2013
+ '[' '!' 0 -eq 0 ']'
+ return 0
+ exit 0