![[DIGITAL logo]](LOGO.GIF){kind=logo}
![[burgundy bar]](REDBAR.GIF)
This appendix describes the NTDS commands that you use to configure the nodes in your OpenVMS Cluster to provide disk services. You can execute an NTDS command in one of two ways:
$ NTDS STOP SERVICE "Sports"
$ NTDS NTDS> STOP SERVICE "Sports" NTDS> EXIT
You can get online help on NTDS commands by entering either HELP NTDS at the $ prompt, or HELP at the NTDS> prompt.
The following table gives a summary of NTDS commands.
| Command | Description |
|---|---|
| NTDS CREATE CONTAINER | Creates a container file that can be used to provide a disk service to a Windows NT computer |
| NTDS SHOW SERVER | Shows the cluster name and summary information about the disk services that are currently available on the local node |
| NTDS SHOW SERVICES | Shows more information about the disk services that are currently available on the local node |
| NTDS SPAWN | Creates a subprocess and optionally executes a DCL command |
| NTDS START SERVER | Starts the server software and defines the cluster name on the local node |
| NTDS START SERVICE | Starts a disk service on the local node, allowing the local node to provide that service to a Windows NT computer |
| NTDS STOP SERVER | Stops all the disk services on the local node, then stops the server software on the local node |
| NTDS STOP SERVICE | Stops a disk service on the local node |
Creates a container file for a disk service.
Requires SYSPRV privilege, and read and write access to the directory in which you are creating the container file.
NTDS CREATE CONTAINER filespec
If you omit the device or directory, the file is created on your current default device or in your current default directory. If you omit the file type, it is created with a file type of .NTDS. If you omit the version number and the file already exists, a new version is created.
The container file is created with its protection mask set to (S:RW, O:, G:, W:) and its ownership set to the system UIC.
The NTDS CREATE CONTAINER command can take some time to execute if high-water marking is enabled for the volume in which you are creating the container file.
The minimum size is 2048 blocks, which is too small to be formatted with the NTFS file system but can be formatted with the FAT file system. If you omit the /SIZE qualifier, the size defaults to 2048 blocks.
Note that you can't change the size of the container file once you have created it.
NTDS> CREATE CONTAINER - _NTDS> DISK$MEDIA:[NTDS$CONT]SPORTS.NTDS /SIZE=200000This command creates a 200,000 block container file called SPORTS.NTDS in DISK$MEDIA:[NTDS$CONT].
Shows the cluster name and summary information about the disk services that are currently available on the local node.
Requires SYSPRV privilege.
NTDS SHOW SERVER
NTDS> SHOW SERVER
DIGITAL OpenVMS Disk Services for Windows NT
Cluster name: Media
PID of server process: 222000D2
Active disk services: 2
Connections: 1
Standby disk services: 1
In this example, an NTDS START
SERVER command that specified a cluster name of Media has
been issued on the local node. Two active services and one standby
service are available on the local node, and a Windows NT computer
is currently connected to one of the active services. Shows information about the disk services that are currently available on the local node.
Requires SYSPRV privilege.
NTDS SHOW SERVICES [servicename]
This parameter can include wildcard characters.
Lowercase characters are automatically converted to uppercase unless you enclose the string in quotation marks. The search is case sensitive, so for example, if a service called Sports is available on the local node, the following command does not show information about it:
$ NTDS SHOW SERVICES Sports
To show information about Sports, you can use any of the following commands:
$ NTDS SHOW SERVICES "Sports" $ NTDS SHOW SERVICES $ NTDS SHOW SERVICES S*
The services are listed in the order in which they were started on the local node.
For each service, the command shows the following information:
The Transition status means that the service is either in the process of starting, stopping, or failing over from another node in the OpenVMS Cluster.
For a standby service, these fields contain the value 0.
NTDS> SHOW SERVICES
DIGITAL OpenVMS Disk Services for Windows NT
Disk services available on this node:
Service name: Music
Status: Active
Computer connected: (none)
Container file: DISK$MEDIA:[NTDS$CONT]MUSIC.NTDS;1
Service name: Sports
Status: Standby
Computer connected: (none)
Container file: DISK$MEDIA:[NTDS$CONT]SPORTS.NTDS;1
Service name: Movies
Status: Active
Computer connected: NTSERVER5
Container file: DISK$MEDIA:[NTDS$CONT]MOVIES.NTDS;1
This command shows information about all the disk services currently
available on the local node.
NTDS> SHOW SERVICES "Movies" /FULL
DIGITAL OpenVMS Disk Services for Windows NT
Disk services available on this node:
Service name: Movies
Status: Active
Computer connected: NTSERVER5
Container file: DISK$MEDIA:[NTDS$CONT]MOVIES.NTDS;1
Read operations: 14350
Blocks read: 651367
Write operations: 43018
Blocks written: 4200499
This command shows full information about the disk service called
Movies. Creates a subprocess and optionally executes a DCL command.
Requires TMPMBX privilege.
NTDS SPAWN [dcl-command]
If you omit the parameter, it creates an interactive subprocess into which one or more DCL commands can be typed. To return to the NTDS> prompt from the interactive subprocess, type LOGOUT.
NTDS> SPAWN SHOW DEFAULT DISK$USER2:[SMITH] NTDS>This command spawns a subprocess to execute a SHOW DEFAULT command.
NTDS> SPAWN $ SHOW DEFAULT DISK$USER2:[SMITH] $ LOGOUT NTDS>This command spawns an interactive subprocess in which a SHOW DEFAULT command is executed.
Starts the server software and defines the cluster name on the local node.
Requires SYSNAM and SYSPRV privileges.
NTDS START SERVER
You must use the /CLUSTERNAME qualifier to define the cluster name on the local node.
Note that the cluster name is case sensitive, and that this command automatically converts the string you supply to uppercase unless you enclose it in quotation marks.
You can choose any name you want, provided that it is no longer than 24 characters and does not contain a backslash character (\). For example, you may choose the same name as your OpenVMS Cluster alias.
Be careful to use the same cluster name whenever you issue NTDS START SERVER commands on different nodes in your OpenVMS Cluster. If you use different cluster names within a single OpenVMS Cluster, when a service fails over from one node to another, the Windows NT computer connected to the service might lose its connection and be unable to reconnect. If this happens, stop the server using NTDS STOP SERVER then start it again using the right cluster name.
NTDS> START SERVER /CLUSTERNAME="Media"This command starts the DIGITAL OpenVMS Disk Services for Windows NT server software and defines the cluster name to be Media.
Starts a disk service on the local node.
Requires SYSNAM and SYSPRV privileges.
NTDS START SERVICE servicename
Note that the service name is case sensitive, and that this command automatically converts the string you supply to uppercase unless you enclose it in quotation marks.
The service name can be up to 24 characters long.
The parameter of the NTDS START SERVICE command specifies the name you want to give to the service. The /CONTAINER qualifier specifies the container file that you want to associate with that service name.
To avoid these problems we recommend that you make the file name of the container file the same as its service name. For example, if the container file is SPORTS.NTDS, call the service Sports.
We also recommend that you issue NTDS START SERVICE commands:
For example, the following command sequence starts the Sports service on three nodes; it starts the active service on GREEN, and standby services on BLUE and YELLOW:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT /NODE=(GREEN,BLUE,YELLOW) SYSMAN> SET PROFILE /PRIVILEGES=(SYSNAM,SYSPRV) SYSMAN> DO NTDS START SERVICE "Sports" - _SYSMAN> /CONTAINER=DISK$MEDIA:[NTDS$CONT]SPORTS.NTDS
The NTDS START SERVICE command starts an active disk service on the local node if this is the first node in the OpenVMS Cluster to start a service with the specified name. When a Windows NT computer subsequently tries to connect to the service, the local node accepts the connection and provides the service to that Windows NT computer.
If another node in the OpenVMS Cluster has already started a service with the specified name, the command starts a standby disk service on the local node. The local node automatically takes over the job of providing the service if:
There is no limit to the number of standbys you can have for any particular disk service.
You must give a full file specification, including the device name. The volume that contains the container file must be mounted systemwide on the local node.
NTDS> START SERVICE "Sports" - _NTDS> /CONTAINER=DISK$MEDIA:[NTDS$CONT]SPORTS.NTDSThis command starts a disk service called Sports that is associated with the container file SPORTS.NTDS in DISK$MEDIA:[NTDS$CONT].
Stops all disk services on the local node, then stops the server software on the local node.
Requires SYSNAM and SYSPRV privileges.
NTDS STOP SERVER
If an active service on the local node has a standby service on another node in the OpenVMS Cluster, the service automatically fails over to the other node; the standby service on the other node automatically becomes the active service. If there are several standby services, the service fails over to the one that was started first.
If a Windows NT computer is currently connected to the service, the failover is transparent; users carry on using the service, unaware that it is being provided by a different node in the OpenVMS Cluster.
By default, the NTDS STOP SERVER command fails if the local node has an active disk service to which a Windows NT computer is currently connected. You can use the /OVERRIDE qualifier to override this behavior.
The Windows NT computer automatically tries to reconnect to the service. If it crashes or is shut down before it manages to reconnect to the service, you lose the data in its local cache that has not yet been written to disk.
Use the /OVERRIDE qualifier to force the command to stop all disk services and the server software, even though a Windows NT computer is currently connected to an active disk service on the local node.
The Windows NT computer loses its connection. If there is a standby service on another node in the OpenVMS Cluster, the service automatically fails over to it, and the Windows NT computer automatically reconnects to the service, transparently to users.
If there is no standby service in the OpenVMS Cluster, the Windows NT computer keeps on trying to reconnect to the service because it needs to write the dirty data in its cache to disk. Use the NTDS START SERVICE command to restart the service on any node in your OpenVMS Cluster, so that the Windows NT computer can reconnect to it.
Until the Windows NT computer manages to reconnect to the service, it stalls all read and write I/O requests to the container file. If the Windows NT computer's cache becomes full because it cannot issue writes to the container file, the Windows NT computer may hang until the service is restarted on the OpenVMS Cluster.
If the Windows NT computer fails or is shut down before it manages to reconnect:
Running NTDS Administrator sets the status of the disk service to Disconnected. This stops the computer from reconnecting to the service the next time it restarts.
If the local node has an active service that a Windows NT computer is currently connected to, and you want to find out if it has any standbys, use the Sysman Utility's DO command to execute NTDS SHOW SERVICES commands. For example:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT /CLUSTER SYSMAN> SET PROFILE /PRIVILEGES=SYSPRV SYSMAN> DO NTDS SHOW SERVICES "Music"
NTDS> STOP SERVERThis command stops all disk services on the local node, then it stops the DIGITAL OpenVMS Disk Services for Windows NT server software on the local node, provided that a Windows NT computer is not currently connected to an active disk service on the local node.
NTDS> STOP SERVER /OVERRIDEThis command stops all disk services on the local node, then it stops the DIGITAL OpenVMS Disk Services for Windows NT server software on the local node, even if Windows NT computers are currently connected to active disk services on the local node.
Stops a disk service on the local node.
Requires SYSNAM and SYSPRV privileges.
NTDS STOP SERVICE servicename
Note that the service name is case sensitive, and that this command automatically converts the string you supply to uppercase unless you enclose it in quotation marks.
If the service is an active service that has a standby service on another node in the OpenVMS Cluster, the service automatically fails over to the other node; the standby service on the other node automatically becomes the active service. If there are several standby services, the service fails over to the one that was started first.
If a Windows NT computer is currently connected to the service, the failover is transparent; users carry on using the service, unaware that it is being provided by a different node in the OpenVMS Cluster.
By default, the NTDS STOP SERVICE command fails if the service is active on the local node and a computer is currently connected to it. You can use the /OVERRIDE qualifier to override this behavior.
The Windows NT computer automatically tries to reconnect to the service. If it crashes or is shut down before it manages to reconnect to the service, you lose the data in its local cache that has not yet been written to disk.
Use the /OVERRIDE qualifier to force the command to stop the service even though it is active on the local node and a Windows NT computer is currently connected to it.
The Windows NT computer loses its connection. If there is a standby service on another node in the OpenVMS Cluster, the service automatically fails over to it, and the Windows NT computer automatically reconnects to the service, transparently to users.
If there is no standby service in the OpenVMS Cluster, the Windows NT computer keeps on trying to reconnect to the service because it needs to write the dirty data in its cache to disk. Use the NTDS START SERVICE command to restart the service on any node in your OpenVMS Cluster, so that the Windows NT computer can reconnect to it.
Until the Windows NT computer manages to reconnect to the service, it stalls all read and write I/O requests to the container file. If the Windows NT computer's cache becomes full because it cannot issue writes to the container file, the Windows NT computer may hang until the service is restarted on the OpenVMS Cluster.
If the Windows NT computer fails or is shut down before it manages to reconnect:
Running NTDS Administrator sets the status of the disk service to Disconnected. This stops the computer from reconnecting to the service the next time it restarts.
If a service is active on the local node and a Windows NT computer is currently connected to it, and you want to find out if there are any standbys for the service, use the Sysman Utility's DO command to execute NTDS SHOW SERVICES commands. For example:
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT /CLUSTER SYSMAN> SET PROFILE /PRIVILEGES=SYSPRV SYSMAN> DO NTDS SHOW SERVICES "Music"
NTDS> STOP SERVICE "Sports"This command stops the disk service Sports on the local node, unless the service is active on the local node and a Windows NT computer is currently connected to it.
NTDS> STOP SERVICE "Sports" /OVERRIDEThis command stops the disk service Sports on the local node, even if the service is active on the local node and a Windows NT computer is currently connected to it.
Copyright © Digital Equipment Corporation 1997. All Rights Reserved.