The NCP Server Console (ncpcon(8)) is a management utility for NCP Server on Novell Open Enterprise Server 2 Linux. The man page for NCPCON is located in the /usr/share/man/man8 directory. To view the man page when you are at the server console, enter man ncpcon at the terminal console prompt.
Section A.1.3, Starting and Stopping NCPCON Interactive Mode
Section A.1.8, Managing File System Trustees and Trustee Rights for NCP Volumes
Section A.1.10, Purging Deleted Files on NSS Volumes on Linux
Section A.1.16, Managing Dynamic Storage Technology on Novell Cluster Services for Linux Clusters
The NCPCON utility can be used in three modes:
Open a terminal console, log in as the root user, then enter
ncpcon
This opens the NCPCON interactive console in the terminal console where you can enter the NCP Server console commands. Enter exit to stop the interactive mode.
For command line mode, issue an NCP Server command at a terminal console prompt by prefacing the command with ncpcon:
ncpcon [command]
For example:
ncpcon mount sys
When using ncpcon to issue commands directly from the console command prompt, you must escape the quote character (") by preceding the character with a backslash (\). For example, a send command is entered as follows from the console command line prompt:
ncpcon send \"hello world\" to all
Escaping the quote character is not required when entering the command from the ncpcon prompt. For example, the send command is entered as followed from the ncpcon prompt:
send "hello world" to all
For scripting mode, issue the NCP Server command in the script by prefacing the command with ncpcon, then placing double-quotation marks around the NCP Server command:
ncpcon "[command]"
For example:
ncpcon "mount sys"
Use this command to list the ncpcon console commands. To get specific help for a command, type help and the command.
EXAMPLES
help
help mount
help remove volume
Use this command to start the ncpcon interactive mode.
EXAMPLE
ncpcon
Use this command to exit out of the NCPCON application when you are using it in the interactive mode. The command is not used in the command line/scripting mode.
EXAMPLE
exit
Use the commands in this section to manage the NCP Server service on your OES server.
Displays the NCP Server configuration information such as the server name, server version, product version, NCP version, mixed-mode paths status (yes/no), and commit files status (yes/no).
EXAMPLE
config
Use this command to display NCP statistics, including the following:
Server up time
Packets in
Packets dumped
Packet receive buffer memory
Packet reply buffer memory
NCP requests
NCP connections in use
Connection table memory
Mounted volumes
Number of open files
Local ID tracking
File handle memory
Volume SYS: file and subdirectory caching memory
Volume SYS: trustee and inherited rights mask tracking memory
EXAMPLE
stats
This command displays version information for all currently running Novell NCP Server components, the OES build, and the hardware platform.
EXAMPLE
version
NCPCON supports the bind and unbind commands for use with Novell Cluster Services for Linux on an OES 2 Linux server.
Use these commands in load or unload scripts when you want to configure the NCP access for files in a cluster resource that can be moved or failed over to another node in the cluster. NCP is required for NSS volumes, NCP volumes on Linux POSIX file systems, and Dynamic Storage Technology shadow volumes.
SLP must be configured on the server where the bind command is issued. When the SLP daemon (slpd) is not installed and running on a cluster node, any cluster resource that contains the ncpcon bind command goes comatose when it is migrated or failed over to the node because the bind cannot be executed without SLP.
For information about configuring and managing Novell Cluster Services for Linux, see the OES 2 SP3: Novell Cluster Services 1.8.8 Administration Guide for Linux.
Binds the specified cluster resource name. Use this command to assign an IP address to the NCP Server cluster resource name.
EXAMPLE
bind oes_2_cluster 192.168.1.1
In a cluster load script, use the following syntax:
exit_on_error ncpcon bind --ncpservername=oes_2_cluster --ipaddress=192.168.1.1
Unbinds the specified cluster resource name. Use this command to remove the assignment of an IP address from the NCP Server cluster resource name.
EXAMPLE
unbind oes_2_cluster 192.168.1.1
In a cluster unload script, use the following syntax:
ignore_error ncpcon unbind --ncpservername=oes_2_cluster --ipaddress=192.168.1.1
Use the commands in this section to configure the larger number of concurrent NCP threads and to verify the current NCP utilization.
Sets the number of additional SSG Threads (over and above the fixed 25 NCP threads) that can be used to serve incoming NCP file service requests. These threads are used when the fixed 25 NCP threads are busy and taking more than expected time to finish.
Default: 7, Valid Range: 7 to 103.
Sets the maximum number of the Async eDirectory NCP request threads that can be created. Default: 15, Valid Range: 15 to 128.
Allows you to verify the current number of concurrent NCP threads running on the server. Use this command to verify the settings that you make for the ADDITIONAL_SSG_THREADS and CONCURRENT_ASYNC_REQUESTS settings.
Example - NCP SSG Thread Statistics
Total Number of Active SSG Threads: 13
Max Number of Additional SSG Threads (over and above fixed 25 NCP Threads): 12
Total Number of NCP Streams: 20
Current Average Load per Thread: 1.54
Peak Number of Active SSG Threads: 25
Peak Number of NCP Streams: 2148
Peak Average Load per Thread: 85.92
Total Number of Active SSG Threads: The currently active SSG threads.
Max Number of Additional SSG Threads (over and above fixed 25 NCP Threads): When all 25 fixed SSG threads are exhausted, then this number defines the additional number of threads that can be created to serve other incoming NCP file service requests. This value can be modified using the ncpcon set ADDITIONAL_SSG_THREADS=value command. Default=7, Valid Range: 1 to 103.
Total Number of NCP Streams: The current number of NCP connections that have been handled by the Active SSG threads.
Current Average Load per Thread: The current average load of NCP connections on the Active SSG threads.
Peak Number of Active SSG Threads: The highest number (peak) of the Active SSG threads.
Peak Number of NCP Streams: The highest number (peak) of NCP streams.
Peak Average Load per Thread: The highest number (peak) of streams per thread.
Example - Async (eDir) Threads and Requests Statistics
Number of Running Threads: 0
Max Thread Size: 25
Thread Peak Size: 25
Number of Queued Requests: 0
Queued Requests Peak Size: 174
Number of Running Threads: The currently running number of Async threads that can handle eDir Requests.
Max Thread Size: The maximum number of the Async threads that can be created. This value can be modified using the ncpcon set CONCURRENT_ASYNC_REQUESTS=value command. Default: 15, Valid Range: 15 to 256.
Thread Peak Size: The highest number (peak) of Async threads the server required so far. This number is reset when the service is restarted.
Number of Queued Requests: The number of queued eDir requests (after the Async threads got exhausted).
Queued Requests Peak Size: The highest number (peak) of eDir requests that have been queued so far (after the Async threads got exhausted).
Use the commands in this section to create, manage, or remove NCP volumes on Linux POSIX file systems on your OES 2 Linux server. NCP volumes use the Novell Trustee Model for controlling user access to files. Users access the volume through the Novell Client.
Display the current volume options setting for the specified volume, or change the setting for a specified option on the specified volume. You must dismount the NCP volume before you can change its options settings with this command.
This command cannot be added to a cluster load script.
OPTION
This is disabled by default. When this setting is disabled, only the root user and the owner of the file can access the volume as local users in a Linux environment. Disabling the POSIX inheritance is the most secure setting because NCP volumes use the Novell Trustee Model for file system access control.
If this option is enabled on a volume, the POSIX permissions are permitted to be inherited from parent directories. If POSIX inheritance is enabled, local access in the Linux environment by users who are not authenticated via Novell eDirectory can create security problems.
EXAMPLES
To view the current setting, enter the following at the console command prompt:
ncpcon change volume sys
To enable Inherit POSIX Permissions on the sys volume, start NCPCON by entering ncpcon at the console command prompt, then enter the following at the ncpcon prompt:
dismount sys
change volume sys Inherit_POSIX_Permissions on
mount sys
exit
Use this command to create an NCP volume by defining an NCP share on an existing POSIX file system on your Linux server. This command creates a Volume object in Novell eDirectory, and associates the volume name to a path on your server when using file system types other than the Novell Storage Services (NSS) file system.
This command does not remove or delete data in the mount point location. It adds the NCP volume’s volume name and mount information to the NCP Server configuration file (/etc/opt/novell/ncpserv.conf).
Replace ncp_volumename with the name for the volume.
Replace path with the path to an existing folder on the Linux server that is used as the mount point for the NCP volume. The folder must be on a Linux POSIX file system volume.
After creating the NCP volume, you must mount it to make it accessible to NCP clients.
EXAMPLE
create volume vol1 /media/ncpvolumes/vol1
Use this command to dismount a specified NCP volume on your Linux server, or to dismount all NCP volumes on your Linux server.
EXAMPLES
To dismount the NCP volume named VOL1, enter
dismount VOL1
To dismount all NCP volumes, enter
dismount all
Use this command to mount an NCP volume on your Linux server. This command makes the NCP volume accessible to NCP clients. Replace volumename with the name of the volume, such as VOL1. To mount all volumes, replace the volume name with all.
Replace volume_id with a value from 0 to 254 as the server volume ID when you want to ensure that the volume has the same ID on all servers when it is mounted in a cluster resource. Replace /volume_mntpoint with the Linux mount point for the NCP volume, such as /media/ncpvolumes/VOL1.
In a cluster load script, use the following syntax:
exit_on_error ncpcon mount volumename=volume_ID,path=/volume_mntpoint
For example:
exit_on_error ncpcon mount USERS=254,path=/media/ncpvolumes/USERS
EXAMPLES
mount sys
mount all
mount VOL1=254,path=/media/ncpvolumes/VOL1
Use this command to remove the NCP volume and path association. This command does not remove or delete data from the mount location. This command removes the NCP volume mount information from /etc/opt/novell/ncpserv.conf configuration file.
EXAMPLE
remove volume VOL1
Displays a list of currently mounted NCP volumes. You can also specify a specific volume name with the command to get information about that volume.
EXAMPLES
volumes
volume VOL1
Displays a list of currently mounted NCP volumes and information about them. For example, if the volume is a Dynamic Storage Technology shadow volume pair, it identifies the Linux paths of its primary and secondary volumes.
EXAMPLE
volume data
This command disables write permission on files in the specified volume. The broadcast message is optional but if specified the message is sent to all the clients accessing the specified volume.
NOTE:This command when executed closes any files that are opened for writing.
Example
disable write VOL1 Closing all open files on this volume.
Use this command to enable write permissions on a volume that has been previously disabled for writing using the disable write command.
The broadcast message is optional but if specified the message is sent to all the clients accessing the specified volume.
Example
enable write VOL1 Files on this volume can now be edited.
Use the commands in this section to manage file system trustees and trustee rights for NCP volumes for Linux POSIX file systems on your OES 2 Linux server. NCP volumes use the Novell Trustee Model for controlling user access to files.
Allows you to view, add, or remove trustees and trustee rights for a specified path. Replace fdn with the typeless fully distinguished name (username.context) of the trustee, such as bob.example. Replace options with all, none, or the combination of rights to assign for the specified trustee. List the rights together without spaces or commas, such as RF. For visibility, users need the Read and File Scan rights.
OPTIONS
All rights
No rights
Supervisor
Read
Write
Create
Erase
Modify
File scan
Access control
EXAMPLES
rights view sys:login
rights add users:bob bob.example RF
rights remove users:bob bob:example
Displays or sets the inherited rights mask on the specified path. Specify both the NCP volume and directory in the NetWare path format, such as volname:dir1/dir2. Replace mask with the mask options all, none, or the combination of rights to block from being inherited. List the rights together without spaces or commas, such as SAE.
MASK OPTIONS
All rights
No rights
Supervisor
Read
Write
Create
Erase
Modify
File scan
Access control
EXAMPLES
irm view sys:login
irm set users: SA
irm set users:bob RF
Use the following load script to mount NSS volumes in a cluster resource.
ncpcon mount <VOLUMENAME>=<VOLUMEID>
ncpcon mount /opt=ns=LONG <VOLUMENAME>=<VOLUMEID>
ncpcon mount /opt=ns=UNIX <VOLUMENAME>=<VOLUMEID>
Use this command to purge, or permanently remove, deleted files from an NSS volume on Linux. This command works only with NSS volumes where the Salvage attribute has been previously enabled.
EXAMPLE
purge volume vol1
Use the commands in this section to enable or disable login for NCP clients to the Linux server.
Use this command to prevent NCP clients from logging in to the Linux server.
EXAMPLE
disable login
Use this command to allow NCP clients to log in to the Linux server.
EXAMPLE
enable login
Use this command to send a message to logged-in NCP clients. Replace text_message with a message of up to 252 characters and spaces. Specify multiple logged-in stations by separating the connection numbers with commas and no spaces. Specify to send the message to all logged-in users.
To find the connection number assigned to a user’s connection, use the connection commands in Section A.1.13, Managing NCP Server Connections.
EXAMPLE
To issue the command at the ncpcon prompt:
send "Hello, world" to 1 send "Hello, world" to 1,2,4 send "Hello, world" to all
To issue the command at the terminal console prompt:
ncpcon send \"Hello, world\" to 1 ncpcon send \"Hello, world\" to 1,2,4 ncpcon send \"Hello, world\" to all
Use the connection commands in this section to display the NCP Server connection information for all current connections, or for a given connection. You can also display a list of the connections and clear the connections. The general syntax is:
connection [list | connection_number | clear connection_number]
Displays an overview of current NCP Server connection information.
|
Parameter |
Description |
|---|---|
|
Connection Slots Allocated |
Displays the number of slots currently allocated for use. As connection slots are required on this server that exceed the current number of slots displayed here, new slots are allocated. Depending on the server’s memory, connection slots are usually allocated in blocks of 16. Connection slots are allocated as needed by users, NetWare Loadable Module (NLM) programs, and other services. |
|
Connection Slots Being Used |
Displays the number of connection slots currently in use. As this number matches or exceeds the Connection Slots Allocated entry, more connection slots are allocated to the connection table. |
|
Signing Level |
Displays the level at which NCP packet signature signing is set on the server. NCP packet signatures prevent packet forgery by requiring the server and the workstation to sign each NCP packet. A higher packet signature number impacts the performance of your server. At some point, the need for security might outweigh certain performance issues. |
|
Login State |
Displays whether users are allowed to log in to the server. To disable users from being able to log in to the server (for server maintenance or other reasons), enter disable login at the NCPCON prompt, or enter ncpcon disable login at a terminal console prompt. To allow users to log in to the server, enter enable login at the NCPCON prompt, or enter ncpcon enable login at a terminal console prompt. |
|
Licensed Connections |
Displays the number of connections that are currently licensed. Licensed connections are authenticated, logged in, and consume a license. An unlicensed connection does not consume a license and can be authenticated or not. An unlicensed, authenticated connection can access the Novell eDirectory database but cannot access any other resources. |
|
Not Logged In Connections |
Clears all user connections that are open but not currently authenticated to the server. The connections can be cleared whether they are based on an NLM or based on a user. Use this parameter to clear all user or NLM connections that are not logged in. IMPORTANT:Some connections based on an NLM, such as backup NLM programs, maintain a Not Logged In connection until it is time to log in and perform the specified service. If the connection is cleared, the NLM might not be able to re-establish a connection to the server unless it is unloaded and reloaded. This might prevent the NLM from performing the required task. |
EXAMPLE
connection
Displays a list of all current NCP Server connections.
|
Parameter |
Description |
|---|---|
|
|
Shows the connection number for each connection. Connection 0 is the connection used by the server. The server’s operating system uses connection numbers to control each station’s communication with other stations. Remote Manager does not distinguish connections that don’t count against the server’s connection limit. |
|
|
Shows the name of the user, server, service, or login status and links to specific information about that user connection such as the login time, connection number, network address, login status, number of NCP requests, files in use, and security equivalence. Connections with an asterisk (*) displayed next to the name indicate an unlicensed connection (it does not consume a license). These licenses can be either authenticated or not authenticated. An unlicensed, authenticated connection can access the Novell eDirectory database but not other server resources. From this detailed Connection Information page, you can also clear the connection or send a message to the user. |
|
|
Shows the number of reads and writes (in bytes) made by the connection. |
|
|
Shows the number of NCP requests made by the connection. |
|
|
Shows the login day, date, and time for the connection. |
EXAMPLE
connection list
Displays detailed information about a specified NCP Server connection. Replace connection_number with the station of interest. You can find the station’s connection number from the report displayed by issuing the connection list command.
|
Parameter |
Description |
|---|---|
|
Connection |
The station number for the connection. |
|
Login Status |
Shows whether the connection is Authenticated or Not Logged In. |
|
Authentication Method |
Shows the authentication method used if the connection is logged in. |
|
Login Time |
Shows the login day, date, and time for the connection. |
|
Privileges |
Shows whether the connection has privileges, such as Supervisor or Console Operator. |
|
Connection Type |
Shows whether the connection is internal or external. |
|
Bytes Read |
Shows the total number of reads made by the connection. |
|
Bytes Written |
Shows the total number of writes made by the connection. |
|
NCP Requests |
Shows the total number of NCP requests made by the connection. |
|
IP Address |
Shows the IP address where the connection originates. |
|
Open Files |
Shows the files open for the connection. |
|
Security Equivalence |
Shows the name of the user, server, or service if it is logged in. |
EXAMPLE
connection 1
Clears the NCP Server connection for a specified station. Replace connection_number with the station of interest. You can find the station’s connection number from the report displayed by issuing the connection list command.
EXAMPLE
connection clear 1
Use this command to list or close open files on an NCP volume by volume, filename, or connection number.
To find the connection number assigned to a user’s connection, use the connection commands in Section A.1.13, Managing NCP Server Connections.
OPERATION OPTIONS
Lists the open files for a specified NCP volume by volume, filename, or connection number.
Closes the open files for a specified NCP volume by volume, filename, or connection number.
OPTIONS
Replaces volumename with the name of the NCP volume.
Replaces filename with path on the Linux file system of the file you want to close, such as /usr/novell/sys/filename.ext.
Replaces connection_number with the station number of the connection whose open files you want to close.
EXAMPLES
files list v=sys
files list f=/usr/novell/sys/test.txt
files list c=9
files close v=sys
files close f=/usr/novell/sys/test.txt
files close c=9
NCPCON supports the commands in this section for use with Novell Dynamic Storage Technology. For information about configuring and managing shadow volumes and file systems, see the OES 2 SP3: Dynamic Storage Technology Administration Guide.
Creates a shadow association between an NCP volume and an NCP shadow volume. Specify the volume name for the primary volume and the path of mount location for the NCP shadow volume. Adds the SHADOW_VOLUME mount information to the /etc/opt/novell/ncpserv.conf file.
By using ncpcon to issue the command, you do not need to restart ndsd in order for the changes to take effect.
OPTIONS
Causes the shadow volume to be created in NCP, but does not add a shadow volume entry to the /etc/opt/novell/ncpserv.conf file. The absence of the entry is desired in order to allow the NCP volume to fail over to other nodes in a Novell Cluster Services for Linux cluster.
Use this option in the cluster load script to create a shadow volume for a cluster resource. Because the volume is not defined in ncpserv.conf, you do not need the ncpcon remove shadow_volume command in the cluster unload script.
Use this option in combination with the /ID=volume_id option.
Specifies the server volume ID (0 to 254) to use when mounting the shadow volume. Use this option to ensure that the volume has the same ID on all servers when it is mounted in a cluster resource on any node in the cluster.
Use this option in combination with the /Cluster_Resource option.
EXAMPLES
Creates a shadow volume where vol1 is the primary storage area and /home/shadows/vol1 is its mount point as a shadow volume.
Creates a shadow volume where vol1 is the primary storage area and /home/shadows/vol1 is its mount point as a shadow volume. The shadow volume is created in NCP, but no entry is added to the ncpserv.conf file. The server volume ID is 254 on any node in the cluster where it is mounted.
Removes the shadow association between the primary storage area and secondary storage area. The shadow volume must be dismounted before this operation can be done.
This command removes the SHADOW_VOLUME command from the /etc/opt/novell/ncpserv.conf file. If the /l option is specified, it then leaves files where they are on either on the primary and secondary volumes. If the /l option is not specified, it then moves all files from the secondary storage area back to the primary storage area. Make sure that the primary volume has sufficient space to accommodate all the files before you remove the shadow relationship.
Because it is moving files back to the primary, the removal process can take some time, depending on how much data must be moved. After completion, a summary report is created and displayed.
This command can be added to a cluster load script.
EXAMPLES
Issue the following commands from the NCP Console, or prepend the command with ncpcon when issuing from a script or at a terminal console prompt.
Removes the shadow relationship for shadow volume vol1, and moves all files from the secondary storage area to the primary storage area. You must dismount vol1 before you issue this command.
Removes the shadow relationship for shadow volume vol1, and leaves files where they currently are on the secondary storage area and the primary storage area. You must dismount vol1 before you issue this command.
Allows you to list files on the shadow volume, or to move files between the primary storage area and the secondary storage area based on specified criteria. All files on the selected shadow volume that match the criteria are moved. Use the command from within cron jobs to automate data partitioning.
OPERATION OPTIONS
Lists primary files. Lists all files currently residing on the primary storage area.
Lists shadow files. Lists all files currently residing on the secondary storage area.
Moves files to primary. Moves files that match the specified criteria to the primary storage area from the secondary storage area.
Moves files to shadow. Moves files that match the specified criteria to the secondary storage area from the primary storage area.
OPERATIONS
Specifies the file pattern to match against.
Specifies the Novell eDirectory username and context of the owner of the files to match against.
Specifies the Linux user ID to match against.
Specifies which time field to match against, where the time_field is:
[m][a][c]
m: Last time modified (content)
a: Last time accessed
c: Last time changed (metadata)
Specifies which time period to match against, where the time_period is:
[a][b][c][d][e][f][g][h][i][j]
a: Within last day
b: 1 day to 1 week
c: 1 week to 2 weeks
d: 2 weeks to 1 month
e: 1 month to 2 months
f: 2 months to 4 months
g: 4 months to 6 months
h: 6 months to 1 year
i: 1 year to 2 years
j: More than 2 years
Specifies the size differential to match against, where the size_differential is:
[a][b][c][d][e][f][g][h][i][j][k]
a: Less than 1 KB
b: 1 KB to 4 KB
c: 4 KB to 16 KB
d: 16 KB to 64 KB
e: 64 KB to 256 KB
f: 256 KB to 1 MB
g: 1 MB to 4 MB
h: 4 MB to 16 MB
i: 16 MB to 64 MB
j: 64 MB to 256 MB
k: More than 256 MB
Output the search results to the specified file.
EXAMPLES
Lists all files of type EXE that currently reside on the secondary storage area for the shadow volulme vol1.
Lists all files of sizes between 1 MB to 4 MB that currently reside on the primary storage area for the shadow volulme vol1.
Moves all files on the primary storage area that have not been modified, accessed, or changed in more than 2 years from the primary storage area to the secondary storage area for the shadow volulme vol1.
Returns the specified file’s location as being on the primary storage area or secondary storage area. Specify the primary or secondary options to move the specified file from its current location to the specified storage area.
OPTIONS
Moves the specified file from the secondary storage area to the primary storage area. The file must be closed when you issue the command; otherwise, the command fails.
Moves the specified file from the primary storage area to the secondary storage area. The file must be closed when you issue the command; otherwise, the command fails.
EXAMPLES
Show the specified file’s storage area location in the shadow volume as primary (the primary storage area) or shadow (the secondary storage area) for the shadow volume sys.
Move the specified file’s storage area location from the secondary storage area to the primary storage area for the shadow volume sys.
Move the specified file’s storage area location from the primary storage area to the secondary storage area for the shadow volume sys.
NCPCON supports the commands in this section for use with Novell Dynamic Storage Technology in combination with Novell Cluster Services for Linux clusters. For information about configuring and managing shadow volumes and file systems in a cluster, see the OES 2 SP3: Dynamic Storage Technology Administration Guide.
Use the following syntax 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 is also not added to the ncpserv.conf file.
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 and be mounted in NSS.
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 ARCHIVE1 (/media/nss/ARCHIVE1).
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/ARCHIVE1.
Use this command when the primary volume is a non-NSS volume and the secondary volume is an NSS volume. The NSS volume must already exist on the system and be mounted in NSS.
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 ARCHIVE1 (mounted at /media/nss/ARCHIVE1).
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 and be mounted in NSS.
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 ARCHIVE1 that is mounted at /media/ncpvolumes/ARCHIVE1.