HP 1032 ClusterPack V2.4 Tutorial - Page 28

Step 10 Run manager_config on the Management Server, Background

Page 28 highlights

z Using the ClusterPack DVD, mount and register the DVD as a software depot. z Install the ClusterPack Manager software (CPACK-MGR) on the Management Server using swinstall. On the Management Server: % /usr/sbin/swinstall -s :/mnt/dvdrom CPACKMGR z The ClusterPack DVD will be referenced again in the installation process. Please leave it in the DVD drive until the "Invoke /opt/clusterpack/bin/manager_config on Management Server" step has completed. Back to Top Step 10 Run manager_config on the Management Server Background This program is the main installation and configuration driver. It should be executed on the Management Server. Some of the steps are: z Install the appropriate license files (i.e. ONE Base Edition license file or TWO Clusterware Edition license files), and start the licensing services z Assign DNS domain name and NIS domain name based on inputs provided z Select and configure the cluster LAN interface on the Management Server that interfaces with the Compute Nodes z Specify how many Compute Nodes are in the cluster and the starting IP address of the first Compute Node. This information is used to assign names and IP addresses when Compute Nodes are brought up. The first 5 characters of the Management Server's hostname are used for a base for the Compute Nodes. For example, if the starting IP address is 10.1.1.1, and there are 16 Compute Nodes, and the name of the Management Server is hpnode, then the first Compute Node will be called hpnod001 with address 10.1.1.1, the next hpnod002 with address 10.1.1.2, and so on. If the tool is invoked with the -f option, the input file will be the source for this information. z Set up the Management Server as NTP server, NIS server, NFS server, Ignite-UX server, and Web server. z Install all of the dependent software components from the ClusterPack DVD: { This step looks for the source of the CPACK-MGR install and queries for an alternate source, if the source is not found. A local depot is setup. All of the agent components are copied. Other dependent software pieces in the Management Server are validated and installed. z Modify configuration files on the Management Server to enable auto-startup of the

  • 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

Using the ClusterPack DVD, mount and register the DVD as a software depot.
Install the ClusterPack Manager software (CPACK-MGR) on the Management Server
using swinstall.
On the Management Server:
%
/usr/sbin/swinstall -s <source_machine>:/mnt/dvdrom CPACK-
MGR
The ClusterPack DVD will be referenced again in the installation process. Please leave it
in the DVD drive until the "Invoke /opt/clusterpack/bin/manager_config on Management
Server" step has completed.
Back to Top
Step 10 Run manager_config on the Management Server
Background
This program is the main installation and configuration driver. It should be executed on the Management
Server.
Some of the steps are:
Install the appropriate license files (i.e. ONE Base Edition license file or TWO
Clusterware Edition license files), and start the licensing services
Assign DNS domain name and NIS domain name based on inputs provided
Select and configure the cluster LAN interface on the Management Server that interfaces
with the Compute Nodes
Specify how many Compute Nodes are in the cluster and the starting IP address of the
first Compute Node. This information is used to assign names and IP addresses when
Compute Nodes are brought up. The first 5 characters of the Management Server's
hostname are used for a base for the Compute Nodes. For example, if the starting IP
address is 10.1.1.1, and there are 16 Compute Nodes, and the name of the Management
Server is hpnode, then the first Compute Node will be called hpnod001 with address
10.1.1.1, the next hpnod002 with address 10.1.1.2, and so on. If the tool is invoked with
the -f option, the input file will be the source for this information.
Set up the Management Server as NTP server, NIS server, NFS server, Ignite-UX server,
and Web server.
Install all of the dependent software components from the ClusterPack DVD:
This step looks for the source of the CPACK-MGR install and queries
for an alternate source, if the source is not found. A local depot is
setup. All of the agent components are copied. Other dependent
software pieces in the Management Server are validated and installed.
Modify configuration files on the Management Server to enable auto-startup of the