HP 1032 ClusterPack V2.4 Tutorial - Page 150

remotely manageable PDU or by their management card.

Page 150 highlights

Many management actions such as boot, reboot, halt, or monitoring will be applied to all of the selected nodes. z Halt This sub-menu allows a system administrator to issue the halt command on all of the selected nodes. The halt command can be performed immediately (this is the default), or delayed for a given time (between 1 to 60 minutes). The administrator can also have a message sent to all the users on the selected nodes by typing in the "Message" edit box. Note: The halt command is performed on the nodes using "rsh". This implies that on the Compute Node, permission must be given to perform commands as superuser/root from the Management Server. If not, the halt command will not work properly. z Power Off This feature allows the user to power off the nodes that have a management card, or that are linked to a remotely manageable PDU. All the nodes to be booted must have the same management card password and the same PDU password. If a node is linked with both a PDU and a management card, the power off will be performed using the management card. The PDU will be used only if the management card power off has failed. Note: If the nodes are not halted, they will be powered off by the remotely manageable PDU or by their management card. This can damage the file system. If unsure, use "Halt" before powering off. z Boot This feature allows the user to boot a collection of nodes on their own local disk or over the network. The user needs to select the node or nodes to be booted prior to launching this command. The boot procedure can use the management card of each node or the remotely manageable PDU connected to the nodes. In this case the password for the management card or for the PDU must be entered. All the nodes to be booted must have the same management card password and the same PDU password. Note: If the nodes are already up, they will be reset by the remotely manageable PDU or by their management card. This can damage the file system. If unsure, use "Halt"

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173

Many management actions such as boot, reboot, halt, or
monitoring will be applied to all of the selected nodes.
Halt
This sub-menu allows a system administrator to issue the halt command on
all of the selected nodes. The halt command can be performed immediately
(this is the default), or delayed for a given time (between 1 to 60 minutes).
The administrator can also have a message sent to all the users on the
selected nodes by typing in the "Message" edit box.
Note:
The halt command is performed on the nodes using "rsh".
This implies that on the Compute Node, permission must
be given to perform commands as superuser/root from the
Management Server. If not, the halt command will not
work properly.
Power Off
This feature allows the user to power off the nodes that have a management
card, or that are linked to a remotely manageable PDU. All the nodes to be
booted must have the same management card password and the same PDU
password. If a node is linked with both a PDU and a management card, the
power off will be performed using the management card. The PDU will be
used only if the management card power off has failed.
Note:
If the nodes are not halted, they will be powered off by the
remotely manageable PDU or by their management card.
This can damage the file system. If unsure, use "Halt"
before powering off.
Boot
This feature allows the user to boot a collection of nodes on their own local
disk or over the network. The user needs to select the node or nodes to be
booted prior to launching this command. The boot procedure can use the
management card of each node or the remotely manageable PDU
connected to the nodes. In this case the password for the management card
or for the PDU must be entered. All the nodes to be booted must have the
same management card password and the same PDU password.
Note:
If the nodes are already up, they will be reset by the
remotely manageable PDU or by their management card.
This can damage the file system. If unsure, use "Halt"