This is the built-in help made by Microsoft for the command 'Start-ClusterNode', in PowerShell version 5 - as retrieved from
Windows version 'Microsoft Windows Server 2012 R2 Standard' PowerShell help files on 2016-06-23.
For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.
Starts the Cluster service on a node in a failover cluster.
Start-ClusterNode [[-Name] <StringCollection>] [-Cluster <String>] [-ForceQuorum] [-IgnorePersistentState] [-InputObject <PSObject>] [-PreventQuorum] [-Wait <Int32>]
[<CommonParameters>]
The Start-ClusterNode cmdlet starts the Cluster service on a node in a failover cluster. If this is the first node started, then it will wait for other nodes to join. The
cluster will begin to run when a quorum has formed.
This cmdlet with the FixQuorum parameter can be used to force quorum, that is, force the start of a cluster node even if quorum has not been achieved. When quorum is forced
on a given node, the copy of the cluster configuration that is on that node will be treated as the authoritative copy and will be replicated to all other nodes. Therefore,
forcing quorum should be considered a last resort, because some cluster configuration changes could be lost. The ability to force quorum can be especially useful in a
multi-site cluster if the primary site, with the majority of nodes, becomes unavailable, and the secondary site, with a minority of nodes, need to be brought into service.
Similarly, the ability to force quorum makes it possible to start a cluster that uses the Node and File Share Majority quorum option when none of the available cluster nodes
contains a current copy of the cluster configuration.
Note: This cmdlet cannot be run remotely without Credential Security Service Provider (CredSSP) authentication on the server computer.
<
Online Version: http://go.microsoft.com/fwlink/?LinkId=321071
Add-ClusterNode
Get-ClusterNode
Remove-ClusterNode
Resume-ClusterNode
Stop-ClusterNode
Suspend-ClusterNode
<
EXAMPLE 1
PS C:\>Start-ClusterNode –Name node3
Name State
---- -----
node3 Joining
This example starts the Cluster service on the node named node3 on the local cluster.
EXAMPLE 2
PS C:\>Start-ClusterNode –Name node1 -Cluster cluster2
Name State
---- -----
node1 Joining
This example starts the Cluster service on the node named node1 on the cluster named cluster2.
EXAMPLE 3
PS C:\>Start-ClusterNode -FixQuorum
Name State
---- -----
node1 Joining
This example forces the local node and the local cluster to start, even if quorum has not been achieved. If quorum has not been achieved, then the copy of the cluster
configuration that is on the local node will be treated as the authoritative copy and will be replicated to all other nodes. This cmdlet should be considered a last resort,
because some cluster configuration changes could be lost.