• Home
• About
• Animals and Rescues
• Computer Issues
• Computer parts
• Computer parts install instructions
• Contact
• Definitions
• DOS Commands
• Downloads
• Hardware questions
• How to use software
• How to use Windows
• How to perform tasks and other information
• Humor
• Internet info and help
• Madison High School Yearbooks
• Madison High School Alumni and teacher's deaths
• Military reunions, events and other info
• How to use Microsoft Office
• Network setup, and other info
• Information on operating systems
• Reinstall operating system
• Remote Services
• Service cost           
• Safety Tips
• Tips
• Troubleshooting Tools
• Info on Websites and/or Businesses
• 
  I have put this website up for your convenience.  The website and email service is free, but if you find this site helpful and would like to make a donation, click on the donate button above. Thank you!
  

cluster

This page is from Microsoft

Syntax

Parameters

Return to Top

Remarks

• Using the cluster command

  The cluster name is optional except when using the /changepass[word] command. If you do not specify a cluster, Cluster.exe attempts to connect to the cluster running on the node that is running Cluster.exe.

  If the name of your cluster is also a cluster command or its abbreviation, such as "cluster" or "c", use /cluster: to explicitly specify the cluster name. For a list of all the cluster commands, see Related Topics.

• Using command-line options with cluster /create

  Unless you are invoking the Cluster Configuration Wizard (by using the /wiz[ard] option), you must supply a name and static IP address for the cluster and the user name for the Cluster service account. If you do not use the /unattend[ed] option, you must also supply the password for the user account used to run the Cluster service on the first node. If possible, the program will use the information from the network connection with the same subnet mask as the node to supply the subnet mask, and network connection name. The cluster will be created in the same domain to which the first server belongs. See the table below for details on the other optional parameters.

• Using the cluster command for unattended setup.

  You can create and configure a cluster during an unattended setup by including the cluster.exe command in the [GuiRunOnce] section of the Unattend.txt file. The cluster.exe command must include all the command line options required for creating and configuring a cluster. For more information on unattended installs, see the Microsoft Windows Corporate Deployment Tools User's Guide (deploy.chm) in the support folder on your installation media.

• Using the /prop[erties] [PropertyList] command-line option

  For more information on property lists, see Related Topics.

• Using the /priv[properties] [PropertyList] command-line option

  For more information on property lists, see Related Topics.

• Using the /setfail[urereactions][:NodeName[,NodeName ...]] command-line option

  This option resets the Cluster service restart settings for one or more nodes to the following values:

  Service Restart Option	Setting
  First failure	Restart the service
  Second failure	Restart the service
  Subsequent failure	Restart the service
  Reset fail count after N days	0 days
  Restart service after N minutes	1 minute

• Command options for creating a cluster

  Option	Description	Default
  [/node: NodeName]	The name of the server to be configured as the first cluster node.	The command will use the name of the current computer if you do not supply a node name.
  [/min[imum]]	This option creates a cluster using the Advanced (minimum) Configuration option. Use this option when creating clusters with complex storage configurations. For more information, see Storage configuration options .	n/a
  [/verb[ose]]	This option writes all event messages to the cluster log. Use this option for troubleshooting cluster configuration issues.	n/a
  /unattend[ed]	If you use this option, you will not be prompted for passwords not supplied at the command prompt.	n/a

• Command options for changing the Cluster service account password

  Option	Description	Default
  [/skipdc]	This option will change the Cluster service account password only on the cluster nodes. It will not change the password on the domain controller. Use this option to complete a previous password update that was only partially completed. For example, use this option if you previously issued a cluster /changepass command for multiple clusters and the Cluster service account password was not updated on all the clusters, for whatever reason. Note If you use this option, you do not have to supply the OldPassword.	n/a/
  [/force]	This option will force execution of the password change command on the available nodes in a cluster even if some of the cluster nodes are not available (that is, some nodes are in the Down, Joining, or Unknown states).	n/a
  [/test]	This option will open a connection to the specified cluster(s), verify that an appropriate domain controller is available, check the version of the operating system installed on each node, and verify that all the cluster nodes are online and use the same Cluster service account.	n/a
  [/quiet]	This option will result in no output, unless an error occurs.	n/a
  [/verb[ose]]	This option outputs detailed information about the cluster nodes (for example, node names and Cluster service account names) to the screen. Use this option for troubleshooting password change issues.	n/a
  /unattend[ed]	If you use this option, you will not be prompted for passwords not supplied at the command prompt.	n/a
  [/help]	This option displays help for the cluster /changepass command only.	n/a

• Cluster common property names

  The following table describes the common cluster property names, their uses, and valid settings:

  Common property names	Use
  Admin Extensions	Describes one or more class identifiers (CLSIDs) of Cluster Administrator extension for the cluster object.
  Default NetworkRole	Specifies the default role to assign to networks.
  Description	Specifies administrative description of the cluster.
  Security	Describes the Windows Server 2003 family-compatible security descriptor.
  Security Descriptor	Describes Windows NT-SP4 and the Windows Server 2003 family-compatible security descriptor.
  Groups\ AdminExtensions	Describes one or more class identifiers (CLSIDs) of Cluster Administrator extensions for the groups.
  NetworkInterfaces\ AdminExtensions	Describes one or more class identifiers (CLSIDs) of Cluster Administrator extensions for the netinterfaces.
  Networks\ AdminExtensions	Describes one or more class identifiers (CLSIDs) of Cluster Administrator extensions for the networks.
  Nodes\ AdminExtensions	Describes one or more class identifiers (CLSIDs) of Cluster Administrator extensions for the nodes.
  Resources\ AdminExtensions	Describes one or more class identifiers (CLSIDs) of Cluster Administrator extensions for the resources.
  ResourceTypes\ AdminExtensions	Describes one or more class identifiers (CLSIDs) of Cluster Administrator extensions for the resource types.
  EnableEventLog Replication	Specifies if Event Log Replication is enabled or disabled cluster wide. (True (1) means enabled; False (0) means disabled.)
  QuorumArbitration TimeMin QuorumArbitration TimeMax	Determines the minimum and maximum time, in seconds, a node is allowed to spend arbitrating for the quorum resource before giving up. The range of values allowed is 0 to 3600 seconds for QuorumArbitrationTimeMin and 1 to 3600 seconds for QuorumArbitrationTimeMax. For a single quorum device server cluster, the default values are 7 seconds for QuorumArbitrationTimeMin and 60 seconds for QuorumArbitrationTimeMax. For a majority node set server cluster, the default values are 7 seconds for QuorumArbitrationTimeMin and 180 seconds for QuorumArbitrationTimeMax.

  DisableGroup PreferredOwner Randomization	If you do not specify a preferred owner list for resource groups, the Cluster service randomizes the list it uses internally to decide which node to fail over the groups to, as described in Determining failover and move policies for groups . That is, by default, this property is set to FALSE (0). If you want to disable this randomization and instead follow the internal ordered list of nodes for failover, set the DisableGroupPreferred Owner Randomization property to be TRUE (or 1).
  EnableEventDelta Generation	When a set of events in the Event Log is replicated across cluster nodes, this property generates a delta event in the Event Log to indicate the time difference between nodes. True (1), the default, means enabled; False (0) means disabled.
  ClusSvcHeartbeat Timeout	Used by the Cluster Network driver, ClusNet.sys, to monitor the health of the Cluster service.
  HangRecoveryAction	Describes the recovery action taken if ClusNet.sys detects a failure in the Cluster service.
  EnableResourceDll DeadlockDetection ResourceDllDeadlock Timeout ResourceDllDeadlock Threshold ResourceDll DeadlockPeriod	Used by the Cluster service to monitor if the entry points to the Resource DLLs are deadlocked (a condition that occurs when two processes are each waiting for the other to complete before proceeding).

• Using cluster private property names

  To view the private properties for a cluster, use the /priv[properties] parameter without any options. For example, to see the private properties for the cluster OpsClust, type the following at a command prompt:

  cluster opsclust /priv

  The following table describes a cluster private property for cryptographic checkpoints. This private property is useful in two scenarios:

  • If there is a third-party resource or application that uses a third-party cryptographic provider that is not supplied by Microsoft.

    For information on troubleshooting this issue, see "A third-party resource fails to come online in a mixed-version cluster or while upgrading a cluster" in Group and resource failure problems .

  • If you have security concerns about the cryptographic checkpoint data that is written to the quorum when you import resource data to a cluster node before bringing the resource online.
  • You can use this private property to change the encryption levels for any of the cryptographic providers (supplied by third-party developers or by Microsoft) that are used by the Cluster service.

    Private property names

    Use

    "CSP"

    Sets the encryption levels (key lengths) for a cryptographic key that is used to export (encrypt) and import (decrypt) resource data (cluster and cluster application cryptographic checkpoints). The imported and exported resource data is saved to the quorum. The cryptographic key is generated by a cryptographic provider that uses the RC2 block encryption method. Usage: "CSP"=key_length,effective_key_length :MULTISTR "CSP" is the name of the cryptographic provider. For example, one of the standard cryptographic providers supplied with the Windows Server 2003 family is "Microsoft Enhanced Cryptographic Provider v1.0." For more information, see CLUSCTL_RESOURCE_ADD_CRYPTO_ CHECKPOINT in the Microsoft Platform Software Development Kit (SDK). key_length is the RC2 key length, in bits. effective_key_length is the RC2 effective key length, in bits For example, to change the RC2 key length for a third-party cryptographic provider named "Database CSP v2.0" in cluster opsclust to 128 bits, type: cluster opsclust /priv "Database CSP v2.0"=128,40:MULTISTR Notes For this property to take effect, the resource DLL must add the cryptographic checkpoint for the property. This is because the cryptographic key is exported and saved to the quorum when the checkpoint is added for the very first time; prior to the resource coming online the key is imported from the file saved in the quorum. Review the documentation for your cryptographic provider to obtain the correct procedure for adding the cryptographic checkpoint. Review the documentation for your cryptographic provider to obtain valid values for the following RC2 encryption algorithm parameters: key_length and effective_key_length.

Examples