 |
» |
|
|
|
If HPCS is not preinstalled on your server, you must install
it from the CDs that came with your server. Follow these instructions
to complete the installation. Verify the hardware is configured appropriately. See Chapter 3 for more information. Install your base OS; Windows 2008 HPC Edition or
Windows 2008 x64. Follow the Windows Operating System installation
instructions to complete the installation. Install HP drivers and/or ProLiant Support Pack. The
latest drivers and ProLiant Support Pack for your hardware are on www.hp.com in the Support and Drivers
section. Select the Windows 2008 x64 platform. Join the head node to an existing enterprise domain.
If you cannot join an exisiting domain, promote the head node to a
domain controller. For information on promoting your server to a domain
controller, see Appendix A . Install HPC 2008. Run setup.exe. Accept terms, and select Create a new
HPC cluster by creating a head node. Create New Database instance, and accept defaults.
If you have a Windows Server Update Service (WSUS)
setup for your active directory, or your servers do not need a Proxy
server to directly access Microsoft websites, you can save some time
by having updates installed. But if you do not, click I don't want to use Microsoft Update. In Install Required Components, click Install. The installation starts. After the cluster is installed, start the console
by clicking Finish. The To-do list window appears. You must complete each
of the four configuration steps. Begin with Configure
your network. Select the desired network topology
for your cluster. For HP Cluster Platform configured hardware, select Compute nodes isolated on a private network. For clusters
with InfiniBand, select Compute nodes isolated on private
and application networks. Click Next. Select the appropriate ethernet network adapter for
the public connection. Click Next. Select the appropriate ethernet network adapter for
the private connection. Click Next. You are prompted to provide private network IP configuration
parameters. You can select your own IP ranges, but HP recommends that
you accept the defaults. HP also recommends that you select NAT and
DHCP. If you do not select DHCP, you will not be able to provision
your compute nodes. If you restrict your IP range to what is allocated
to DHCP, make sure you allow for more IP addresses than compute nodes.
Typical IP settings are as follows: Click Next. Select the appropriate network adapter for the application
connection. This should be your InfiniBand adapter. Click Next. You will be asked to provide application network IP
configuration parameters. You can select your own IP ranges, but HP
recommends that you accept the defaults. For the application
network, you do not need to select NAT, and you can choose to DHCP
the application network addresses. If you do not select DHCP, you
need to individually configure the IB network adapter for each compute
node. Typical IP settings are as follows: For more information on configuring and troubleshooting IB network
connections, see the documentation at: http://www.docs.hp.com/en/highperfcomp.html. Click Next. Configure your firewall settings. Typically, you select
the defaults. Public is firewalled, private is not. We recommend
you do not firewall your private network. Click Next. After making all your network selections, review your
selections. After verifying your selections, click Configure. This takes several minutes to complete.
In the To-do List, select Provide installation
credentials. Enter the credentials for a domain user
who has permissions to create new nodes in the active directory.
(Many enterprises also use a special account with restricted privileges
for this purpose. Use the appropriate account for your domain.) Add
the user to the cluster user list. Configure the node-naming scheme. Select Configure the naming of new nodes. This presents a pattern
to use for compute node names as they join the cluster. Follow the
instructions and name your compute nodes as desired. In the To-do List, select Create a node
template. Enter a name for the template. Click Next. Select With operating system. Click Next. This image is found on the Windows HPC 2008 Edition
OEM disk. Select the first option Create a new operating
system image and locate the setup.exe on the OEM DVD. Include a name for the image. Click OK. After the image is added, select the appropriate OS
image. If you are using an OEM image with new HP hardware, you do
not need to enter a key. The key is automatically encoded into the
image. If you are using older hardware, or are using a non-OEM image,
you can enter your OS key. The local administrator password can be automatically
generated or manually set. HP recommends automatically generated passwords. If you have your WSUS server setup, or if your nodes
have access to the internet, you can select to include Windows updates
. You can also add additional hot-fixes to the installation if you
wish. Review the settings, and create the template. Click Create.
After the template is created, all the To-do List
items have green checks. To finish the configuration and start provisioning
nodes, go to the Configuration tab, and
select Images. Select Manage Drivers,
and add the multi-function NIC drives from the ProLiant Support Pack
(PSP) for DL3xx, DL5xx and blXXX. For DL1xx, download the appropriate
NIC driver for your hardware, and add this driver to the NIC. | | | |  | IMPORTANT: The WinPE environment for Windows 2008 does not contain drivers
for virtual bus drivers. Therefore, the network drivers for your compute
nodes must be added to the image, even though they may be a part of
the full Windows 2008/2008 HPC Edition operating system. You must
add the network drivers to the images, or provisioning compute nodes
will fail. | | | | |
For the compute nodes to properly provision, these drivers must
be added to the image. If you see the operating system copy fail while
watching the compute node consoles, the WinPE image does not contain
the correct NIC drivers. To find the correct drivers in the PSP: Examine a PSP CD or an unpacked PSP file. Review the
contents of the bp00XXXX.txt file and search
for the entry regarding the Multi-function driver: cp009194.exe
HP NC-Series Broadcom 1Gb Multifunction Driver for Windows Server
2008 x64 Editions Run the file listed here, and extract the contents
into a directory. Point the Add location
to this directory. Select all the drivers listed.
Provision the compute nodes. Select Node
Management and show all the nodes. The head node should
be listed, with a warning. Select this node, and the bottom of the
screen displays Failed Diagnostics View failed diagnostic
tests. If you view this and the test All Services Running is the only failure, this is a false error. The HPC services did
not start before the diagnostic tests started to run. To clear the
error, on the diagnostic tab, select the head node, right click on
the error, and select Clear Alert. Rerun the diagnostic tests if you wish. To start provisioning compute nodes, return to the Node Management tab, and select Add Nodes. Select Deploy compute nodes from bare metal using
an operating system image. Click Next. Select the template you want to apply to the compute
nodes. You cannot continue until at least one compute node is PXE
booted and starts provisioning. Power on at least one of the compute
nodes, or all of the compute nodes, and wait for them to display in
the Select New Nodes window. | | | |  | NOTE: Compute nodes should arrive with no data on the hard drive.
In this state, the nodes will automatically PXE boot when they are
powered up. If your hard drive contains a partition or data, it may
attempt to boot from the hard drive. If this occurs, wipe the hard
drive clean by deleting all disk partitions, or manually select PXE
boot at node startup time. | | | | |
Click Deploy. You are asked
if you want the head node to respond only to PXE requests from existing
nodes, or respond to all PXE requests. Responding to only PXE requests
for existing compute nodes is the secure thing to do. However, if
your compute nodes are on a private network, you can securely select
the second option and nodes can be provisioned from the Node Management Console. Click Finish. To monitor the provisioning progress, go to the Node Management Console, highlight the node you want
to monitor, and select the Provisioning Log tab at the bottom of the screen. This provisioning progress displays,
and shows any errors. Provisioning might take approximately an hour. It might take
longer if a large number of nodes are being provisioned at the same
time without multi-cast being enabled. After the nodes are provisioned,
you can see all the nodes in the node list.
Your cluster is ready for use. For information on troubleshooting, see Chapter 9. |
Printable version
