12.15 Changing the Name Space for a Clustered NSS Volume

The load script for an NSS volume assumes that the default name space of LONG is used when mounting the clustered NSS volume. If you change the name space setting for shared volume by using NSSMU or the Storage plug-in for iManager, you must modify the load script for the pool cluster resource to add the name space to the ncpcon mount command for the volume. See Section 12.6.3, Specifying Custom Mount Options.

  1. Open Novell iManager in a web browser, then log in as a cluster administrator user.

  2. In Roles and Tasks, select Clusters > My Clusters, select the cluster, then click the Cluster Manager tab.

  3. Modify the mount point path value in the load scripts for the pool cluster resource:

    1. On the Cluster Manager page, select the resource’s name link to open its Cluster Properties page, then click the Scripts tab.

      The Scripts tab automatically displays the load script.

    2. Modify the load script:

      1. In the load script, add the /opt=ns=<long|unix|dos|mac> option for the ncpcon mount command and specify the custom name space to use for the volume. For example:

        exit_on_error ncpcon mount USERS=254 /opt=ns=unix
        
      2. Click Apply, then click OK to acknowledge the confirmation message.

    3. At the bottom of the page, click OK to close the Properties page and save your changes.

      The changes do not take effect until the resource is taken offline and brought online.

  4. Take the resource offline, and bring the resource online in order for the script changes to take effect.

    1. On the Cluster Manager page, select the check box next to the resource, then click Offline. Wait for the status to report that it is offline, then continue.

    2. Select the check box next to the resource, then click Online.

    3. Verify that the resource comes online and reports a Running state.

      If the resource goes into a Comatose state, it is probably because you made a mistake in the lines you added or modified in the script. Take the resource offline, then go back to correct the scripts, and try to bring it online again.