Troubleshooting SA Provisioning

Server does not enter maintenance mode

Symptoms

• Server does not show up in SA
• "Wait for HPE SA Agent" fails with a timeout error

What to check for

• Check the server console
• Check that DHCP is working and the server is on the right network
• Check that the SA Agent was able to register

HPE ProLiant Gen8 or newer servers do not enter maintenance mode

Symptoms

• The "Boot" step fails
• The "Wait" step fails after a successful boot step

What to check for

• Check that DHCP is working and the server is on the correct network or that the network information is correct
• Check the error messages from the "Wait" step, they will contain additional information. Failure to download the SA Agent is often a sign that the network is not configured properly
• Consider upgrading "Intelligent Provisioning" on the server and try again
• Consider upgrading the iLO firmware on the server and retry
• Log in to the server's iLO interface of the server and perform an iLO reset

Failure before the OS Install starts

Symptoms

• Failures in "Set Media Source", "Create Stub Partition" or other scripts before the Reboot script

What to check for

• Ensure that the input parameters, such as the media path are correct
• Ensure that the server has a hard disk and that the hard disk is recognized by the service OS
• Ensure that the media server is online and functional
• Ensure that the network and DHCP are configured properly. For example, if the Media Server is specified by host name, check that DNS is configured properly and is working

Failure of the OS Installer

Symptoms

• "Monitoring" or "Run setup" scripts fail
• Other failures before rebooting into the installed OS

What to check for

• Ensure that the media is correct and complete and that it matches the OS, version and architecture of the Build Plan. For example, do not use a Build Plan that installs a 64-bit OS with 32-bit media
• If you customized the installation profile, ensure that it is correct and valid
• Check the server console and/or the output of the Build Plan for more information about the failure
• Check with the OS vendor for more troubleshooting tips

Failure when waiting for the production SA Agent

Symptoms

• The "Wait" step for the production SA Agent fails

What to check for

• Check the server console to verify that the OS was able to boot. Some installation failures are only detected on first boot. If the OS failed to boot, ensure that the installation profile was correct
• Check that any additional driver that was added during provisioning matches the server
• Check with the OS vendor for more troubleshooting tips. Ensure that the server has correct network drivers and that the server can communicate with the SA Core
• Ensure that a firewall setting is not preventing communication between the SA Agent and SA Core