Set-HpcNode

Indicates how affinity is managed for tasks that run on the node. By default, the value is $Null, which means that affinity is managed according to the job scheduler affinity policy. If this property is set, node affinity overrides the job scheduler affinity settings. A value of 0 or $False specifies that affinity on the node is not managed by the HPC services, and the operating system or the application manages placement of tasks on physical cores. A value of 1 or $True specifies that the HPC Node Manager Service sets affinity for tasks (assigns tasks to specific cores).

For more information relating to affinity, see Understanding Affinityhttp://technet.microsoft.com/library/ff919424(WS.10).aspx.

This parameter was introduced in HPC Pack 2008 R2 with Service Pack 2 (SP2). It is not supported in previous versions.

Specifies the chassis in which the node is located. If you specify the Chassis parameter, you must also specify the DataCenter and Rack parameters.

This parameter is deprecated as of Microsoft® HPC Pack 2012. Use the Location parameter instead.

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.

Specifies the data center in which the node is located.

This parameter is deprecated as of Microsoft® HPC Pack 2012. Use the Location parameter instead.

Specifies a description for the node.

Specifies the location of the node as a string with a format of \<DataCenter>[\<Rack>[\<Chassis>]].

The location must begin with a backslash (\). If you specify the <Rack> part of the string, you must also specify the <DataCenter> part. If you specify the <Chassis> part of the string, you must also specify the <Rack> and <DataCenter> parts. Each part of the string has a maximum length of 256 characters.

If you specify a location string with more than three parts, such as \center1\rack3\chassis5\location7\sublocation9, no error occurs and the location is truncated after the third part of the string. So, the value of \center1\rack3\chassis5\location7\sublocation9 becomes \center1\rack3\chassis5.

This parameter was introduced in HPC Pack 2008 R2.

Specifies an IP address that Intelligent Platform Management Interface (IPMI) tools can use to manage power on the node. The format of the value for this parameter is the same as the format of a valid IP address.

Specifies an array of names for the nodes for which you want to change the properties. You cannot specify both the Name and Node parameters.

Specifies an array of HpcNode objects for the nodes for which you want to change the properties. Use the Get-HpcNode cmdlet to get the HpcNode object for a node. You cannot specify both the Node and the Name parameters.

Specifies the product key for Windows Server 2008 to use when you provision the node. The product key should be in the format of xxxxx-xxxxx-xxxxx-xxxxx-xxxxx, where x is a letter of either case or a digit.

Specifies a rack position for the node. If you specify the Rack parameter, you must also specify the DataCenter parameter.

This parameter is deprecated as of Microsoft® HPC Pack 2012. Use the Location parameter instead.

Specifies an array of roles for the node. Valid values are:

• None
• ComputeNode
• BrokerNode
• WorkstationNode

You muset take a node offline before you can change the role of the node. Use the Set-HpcNodeState cmdlet to take nodes offline.

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\>

Specifies the number of cores that you want the HPC job scheduler service to use when it is allocating tasks to the node. This value may be smaller than, or exceed the number of physical cores. To clear this property, set the value to $Null. If this value is $Null, the number of physical cores is used.

You should ensure that the number of subscribed cores is divisible by the number of subscribed sockets. Therefore, each socket must have the same number of cores (for example 4 cores and 2 sockets are valid, but 10 cores and 4 sockets are not).

This parameter was introduced in HPC Pack 2008 R2 with Service Pack 2 (SP2). It is not supported in previous versions.

Specifies the number of sockets that the HPC job scheduler service should use when it is allocating tasks to the node. This value may be smaller than, or exceed the number of actual physical sockets. To clear this property, set the value to $Null.

You should ensure that the number of subscribed cores is divisible by the number of subscribed sockets. Therefore, each socket must have the same number of cores (for example 4 cores and 2 sockets is valid, but 10 cores and 4 sockets is not).

This parameter was introduced in HPC Pack 2008 R2 with Service Pack 2 (SP2). It is not supported in previous versions.