NCPCON supports the commands in this section for use with Dynamic Storage Technology in combination with Novell Cluster Services for Linux clusters.
Use the syntax examples in this section in cluster load scripts to mount the volume in a cluster. With clustering, no changes are needed to the ncpserv.conf file for shadowing. The primary volume information should not be manually added to the ncpserv.conf file.
When the primary volume has a state of Shadowed, the volume ID that you assign as its NCP volume ID represents the DST shadow volume pair of volumes. The secondary volume does not have a separate volume ID when it is in the shadow relationship.
Use this command in a cluster load script when the primary volume is an NSS volume and the secondary volume is an NSS volume. Both NSS volumes must already exist. The secondary NSS volume must already exist on the system and be mountable in NSS, but not available to NCP (that is, its NCP/NSS bindings are disabled by using OES Remote Manager). The primary pool must be cluster-enabled. The secondary pool must be shared. The secondary pool can be clustered, but its Cluster object and resource IP address are not used while its volume is used in a clustered DST volume.
Replace volID with a value from 0 to 254 as the server volume ID to ensure that the volume has the same ID on all servers when it is mounted in a cluster resource.
EXAMPLE
Mounts the NSS volume named VOL1 with a volume ID of 254. The primary volume is an existing NSS volume named VOL1 (/media/nss/VOL1). The secondary volume is an existing NSS volume named ARCVOL1 (/media/nss/ARCVOL1).
Use this command when the primary volume is a non-NSS volume and the secondary volume is a non-NSS volume.
Replace volID with a value from 0 to 254 as the server volume ID to ensure that the volume has the same ID on all servers when it is mounted in a cluster resource.
EXAMPLE
Mounts the NCP volume named VOL1 with a volume ID of 254. The primary volume’s path is /media/ncpvolumes/VOL1. The secondary volume’s path is /media/ncpvolumes/ARCVOL1.
Use this command when the primary volume is a non-NSS volume and the secondary volume is an NSS volume. The secondary NSS volume must already exist on the system and be mounted in NSS, but not available to NCP (that is, its NCP/NSSNCP/NSS bindings are disabled by using OES Remote Manager).
Replace volID with a value from 0 to 254 as the server volume ID to ensure that the volume has the same ID on all servers when it is mounted in a cluster resource.
EXAMPLE
Mounts the NCP volume named VOL1 with a volume ID of 254. The primary volume’s path is /media/ncpvolumes/VOL1. The secondary volume is an existing NSS volume named ARCVOL1 (mounted at /media/nss/ARCVOL1).
Use this command when the primary volume is an NSS volume and the secondary volume is a non-NSS volume. The NSS volume must already exist on the system. The remote server must reside in the same eDirectory partition and tree as the DST server.
Replace volID with a value from 0 to 254 as the server volume ID to ensure that the volume has the same ID on all servers when it is mounted in a cluster resource.
EXAMPLE
Mounts an NSS volume named VOL1 with a volume ID of 254. The primary volume is an existing NSS volume named VOL1 (/media/nss/VOL1). The secondary volume is an NCP volume named ARCVOL1 that is mounted at /media/ncpvolumes/ARCVOL1.