HP 1032 ClusterPack V2.4 Tutorial - Page 62

Step 2 Invoke mp_register on Management Server

Get HP 1032 PDF manuals and user guides View all HP 1032 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 62 highlights

The steps in this section have to be followed in the specified order to ensure that everything works correctly. Step 1 Invoke /opt/clusterpack/bin/manager_config on Management Server Invoke /opt/clusterpack/bin/manager_config with a "add node" option -a. % /opt/clusterpack/bin/manager_config -a : This command adds the new node with the specified hostname and IP address to the cluster. It also reconfigures all of the components of ClusterPack to accommodate the new addition. The '-a' option can include multiple host:ip pairs if more than one node needs to be added to the system. If a large number of changes will be made to the cluster membership, the '-m' option can be used with a file. For more information on the use of manager_config, refer to the man pages. % man manager_config Step 2 Invoke mp_register on Management Server If the host being added to the cluster has an MP interface, it should be registered and possibly configured with mp_register: % /opt/clusterpack/bin/mp_register -a The '-a' option can be repeated when adding multiple hosts at one time. The mp_register utility will prompt you for information to configure and/or register an MP card for the host being added. The '-f' option can be used to provide a file containing all the MP card information required by mp_register. Step 3 Invoke clbootnodes on Management Server Boot the node. To assist in booting the node, you may use clbootnodes. If the node is already booted, ensure that it has the IP address you indicated when running manager_config. Nodes can be booted from a "first boot" state or an image of another compute node can be installed on any new node(s). To boot a single node which has HP-UX installed on it, use: % clbootnodes To boot multiple nodes, use: % clbootnodes

  • 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
The steps in this section have to be followed in the specified order to ensure that everything
works correctly.
Step 1 Invoke /opt/clusterpack/bin/manager_config on Management Server
Invoke /opt/clusterpack/bin/manager_config with a "add node" option -a.
%
/opt/clusterpack/bin/manager_config -a
<new_node_name>:<new_node_ip_addr>
This command adds the new node with the specified hostname and IP address to the cluster. It
also reconfigures all of the components of ClusterPack to accommodate the new addition.
The '-a' option can include multiple host:ip pairs if more than one node needs to be added to the
system.
If a large number of changes will be made to the cluster membership, the '-m' option can be used
with a file.
For more information on the use of manager_config, refer to the man pages.
%
man manager_config
Step 2 Invoke mp_register on Management Server
If the host being added to the cluster has an MP interface, it should be registered and possibly
configured with mp_register:
%
/opt/clusterpack/bin/mp_register -a <new_node_name>
The '-a' option can be repeated when adding multiple hosts at one time.
The mp_register utility will prompt you for information to configure and/or register an MP card
for the host being added.
The '-f' option can be used to provide a file containing all the MP card information required by
mp_register.
Step 3 Invoke clbootnodes on Management Server
Boot the node. To assist in booting the node, you may use clbootnodes. If the node is already
booted, ensure that it has the IP address you indicated when running manager_config. Nodes can
be booted from a "first boot" state or an image of another compute node can be installed on any
new node(s). To boot a single node which has HP-UX installed on it, use:
%
clbootnodes <new_node_name>
To boot multiple nodes, use:
%
clbootnodes