Provisioning Issues

Provisioning can fail for any number of reasons. Watch the provisioning log on the head node to see each node's progress. If the node fails to provision, check the following items:

Watch the node console as the node boots. The node should PXE boot and get an IP address through DHCP from the head node. If neither of these happen, check the following:
- The BIOS is selecting the correct NIC to PXE boot. This must be the NIC connected to the private network.
- The head node is connected to the private network, and the Private NIC on the head node is properly configured with a private IP address. For preconfigured clusters, this should be 10.1.3.1.
- Verify the NIC is obtaining an IP address through DHCP. It should indicate the NIC obtained an address and list the head node's private NIC IP as the DHCP server. For preconfigured clusters, this is 10.1.3.1.
- Verify the DHCP service is running on the head node.
Continue monitoring the compute node console. If the correct NIC is PXE booting and getting a correct IP address through DHCP from the head node private IP, verify the boot record is being sent to the compute node:
- If you see an error indicating no boot record/file was sent, verify that the head node WDS (Windows Deployment Server) service is running.
- Verify the firewall on the head node for the private network is turned off.
- Check the event log for any WDS errors.
- Check that the head node is actively provisioning the specified compute node. If not, right-click the node and assign the desired template to the node for preconfigured nodes. For non-preconfigured nodes, click Add Node and wait for the node to respond. Then select and assign a template.
The compute node fails to copy the operating system from the WDS server. When the compute node starts the WinPE environment, a command window displays. You should see it add any drivers (if you injected drivers into the OS), then start the provisioning. One of the early steps is copying the OS image to the compute node. If this copy fails, an error appears in the command window and commands will stop.
- Make sure you added the correct network drivers for your compute node into the image. Check/Add drivers using the HPC Management Console. Select Configuration tab, and Images on the right side. Select Manage drivers.
The compute node may fail to join the domain.
- Verify the username/password for domain credentials are correct.
- Verify the username supplied has correct privileges to add domain accounts/machines.
- Verify the DNS on the head node is correct.
- Check the list of machines in the domain. Verify there are no machine name conflicts in the domain.
  NOTE: Sometimes removing the domain machine information from the domain and restarting the provisioning will cleanup artifact information on the machine.
The provisioning might appear to fail. Check the compute node console for reasons why the provisioning might appear to be stalled. Possible reasons include:
- Looking for a license key or waiting for a license key to be entered. Enter a key at the console, or just click Next to continue.
- Unsigned driver loading. Unsigned drivers added to the OS image might cause a hang on reboot. The screen will indicate this error and list the unsigned driver causing the issue. Remove the driver from your OS image.

Provisioning Issues

Technical documentation

» Table of Contents

» Glossary

» Index