Start-HpcAzureNode

Starts Azure nodes.

Syntax

Start-HpcAzureNode
     [-Async <Boolean>]
     [-Name] <String[]>
     [-ClusterConnectionString <String[]>]
     [-Scheduler <String[]>]
     [<CommonParameters>]
Start-HpcAzureNode
     [-Async <Boolean>]
     -Node <HpcNode[]>
     [-ClusterConnectionString <String[]>]
     [-Scheduler <String[]>]
     [<CommonParameters>]

Description

The Start-HpcAzureNode cmdlet starts one or more Azure nodes. Starting the nodes provisions the corresponding role instances in Azure.

Examples

Example 1: Start an Azure node by name

PS C:\>Start-HpcAzureNode -Name "AzureCN-0114" -Async $True

This command starts the Azure node named AzureCN-0114 and returns without waiting for the node to start.

Example 2: Get Azure nodes by state and start them

PS C:\>Get-HpcNode -GroupName "AzureNodes" -State Not-Deployed | Start-HpcAzureNode

This command gets an HpcNode object for the Azure nodes that are in the Not-Deployed state, and then starts those Azure nodes.

Required Parameters

-Name

Specifies an array of names, separated by commas, of the nodes that you want to start. You cannot specify both the Name and Node parameters.

Type:String[]
Position:1
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-Node

Specifies an array of HpcNode objects, separated by commas, for the nodes that you want to start. You cannot specify both the Node and Name parameters.

Type:HpcNode[]
Position:Named
Default value:None
Accept pipeline input:True (ByValue)
Accept wildcard characters:False

Optional Parameters

-Async

Indicates whether the cmdlet should return immediately without waiting for the nodes to start.

A nonzero or $True value specifies that the cmdlet should return immediately without waiting for the nodes to start. A 0 or $False value specifies that the cmdlet should wait for the nodes to start before returning.

Type:Boolean
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-ClusterConnectionString

Specifies an array of cluster connection strings for the cluster to which you want to add the device drivers. The value format is host1,host2,host3. If you do not specify the ClusterConnectionString parameter, this cmdlet uses the connection string on the head node that the CCP_CONNECTIONSTRING environment variable specifies. To set this environment variable, run the following cmdlet: Set-Content Env: CCP_CONNECTIONSTRING \<head_node_name\>.

This parameter was introduced in HPC Pack 2016.

Type:String[]
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-Scheduler

Specifies the host name or IP address of the head node for the cluster that includes the Azure nodes that you want to start. The value must be a valid computer name or IP address. If you do not specify the Scheduler parameter, this cmdlet uses the scheduler on the head node that the CCP_SCHEDULER environment variable specifies. To set this environment variable, run the following cmdlet:

Set-Content Env:CCP_SCHEDULER \<head_node_name\>

Type:String[]
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False

Inputs

HpcNode[]

Outputs

None

Notes

  • Azure nodes that are stopped automatically by an availability policy that is configured in the node template cannot be started by this cmdlet.
  • If a problem exists with your Internet connection, the process of starting the nodes can fail.
  • You must be a cluster administrator to run this cmdlet successfully.
  • This cmdlet was introduced in HPC Pack 2012 R2 Update 1. It is not supported in previous versions.