Start-HpcNode

Turns on nodes by using an Intelligent Platform Management Interface (IPMI) script.

Syntax

Start-HpcNode
     [-Name] <String[]>
      [-Scheduler <String[]>]
     [<CommonParameters>]
Start-HpcNode
     -Node <HpcNode[]>
      [-Scheduler <String[]>]
     [<CommonParameters>]

Description

The Start-HpcNode cmdlet turns on one or more nodes by using a preconfigured Intelligent Platform Management Interface (IPMI) script. Your computer vendor should have configured the IPMI script for your computer. If the IPMI script is not configured, Start-HpcNode generates an error.

Examples

Example 1: Start a node

PS C:\>Start-HpcNode -Name "hpc01cn02"

This command turns on a node named hpc01cn02.

Example 2: Get nodes by group name and start them

PS C:\>Get-HpcNode -GroupName "Maintenance" | Start-HpcNode

This command gets the HpcNode objects for all of the nodes in the group named Maintenance, and starts those nodes.

Parameters

-Name

Specifies a list of the names of the nodes that you want to turn on. You cannot specify both the Name and Node parameters.

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

-Node

Specifies one or more HpcNode objects for the nodes that you want to turn on. You cannot specify both the Node and Name parameters.

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

-Scheduler

Specifies the host name or IP address of the head node for the cluster that includes the nodes. 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
Required:False
Accept pipeline input:False
Accept wildcard characters:False

Inputs

HpcNode[]

Outputs

None

Notes

  • You must be a cluster administrator to run this cmdlet successfully.