Troubleshooting > Troubleshoot adding and booting servers

  

 next

Troubleshoot adding and booting servers

Unable to add a server via iLO

The symptom in all cases is the inability to add a server using iLO. Possible causes are the items in the right-hand column, with suggested resolutions shown. See OS Build Plan or add iLO fails at Wait for HP SA Agent step.

Symptom Possible cause and resolution
Unable to add a server via iLO

  • iLO is unresponsive

    • Use ssh to access the iLO and reset it using the reset map1 command. Make sure you allow enough time for the iLO to reboot before trying to add it again.

  • iLO IP address is incorrect

    • Verify the iLO IP address.

  • The iLO is not accessible from the appliance

    • Verify the iLO NIC is reachable from the appliance.

  • Incorrect iLO credentials

    • Verify the iLO credentials on the Add server screen.

  • Insufficient iLO permissions

    • The iLO account specified on the Add server screen requires all permissions except “admin”.

  • Target system is at the BIOS screen or powering on

    • If the target server is at the RBSU screen or if the server is running its power on self test, the proper boot parameters cannot be set automatically by the appliance. Exit RBSU, power off the target server, and try again.

  • iLO password uses illegal characters

    • Certain special characters might cause problems if they are used in your iLO user name or password. The double quote (“) is one of these. If you see errors relating to illegal characters, change your iLO password and try again.

When adding servers using PXE some servers not properly registered

Symptom Possible cause and resolution
When adding servers by PXE booting them into the service OS, a small percentage of the servers fail to show up in the UI, or their iLO fails to register properly which shows as a failed iLO registration job on the Jobs screen. The failure rate might be elevated when bulk adding servers. If any server fails to register properly repeat the registration process as follows:

  • If the server shows up in the appliance UI, delete it. Then re-PXE boot the server to initiate the discovery again.

  • To reduce the occurrence of this issue only add single enclosure at a time (16 servers) and wait until their registrations are complete before adding the next enclosure.

Target servers cannot PXE boot into the appliance

Symptom Possible cause and resolution
There is no PXE or DHCP response when a target server is trying to boot into Insight Control server provisioning.

  1. There is no DHCP server on your network.

    • Make sure the appliance DHCP server is enabled or an external DHCP server is configured properly. External DHCP servers require special configuration to work with IC server provisioning. For details, see the Insight Control server provisioning Installation Guide.

  2. Incorrect gateway and DNS information.

    • Update the appliance Gateway address and Preferred DNS server information on the Settings Appliance Networking screen.

  3. A firewall is blocking PXE/TFTP requests.

    • Make sure the following ports are open:

      • Port 67 (UDP) – DHCP

      • Port 69 (UDP) – TFTP

      • Port 4011 (UDP) – PXE

Error: Cannot add user. The login/user name already exists

Symptom Possible cause and resolution
When adding a server using PXE, theRegisters IloManagerService job might fail with the error: Cannot add user. The login/user name already exists. Server’s iLO may not get registered when server is PXE booted.

This can occur if there is an existing iLO user account and the User Name or Login Name field contain a <, >, or double quote character.

  1. Use a browser to connect to the iLO and in the User Administration screen, edit the user accounts containing the <, >, or double quote characters in the User Name or Login Name field, and remove the characters.

  2. Add the server to Insight Control Server Provisioning by selectingAdd Server in the Servers screen and entering the iLO’s IP address and credentials.

Error: Mid and crypto not found

Symptom Possible cause and resolution
Error: Mid and crypto not found This error is often seen when a server that was previously installed and managed is booted into a service OS that cannot access the server identification information stored on the server’s hard drive.

  • If you are trying to reprovision the server, either run one of the Prepare Server for Reprovisioning Build Plans to clear the managed status of the server or be sure the decommission server Build Plan step is part of your Build Plan in the appropriate location.

  • When you see this error while trying to add a server, it is likely the target server is already registered in Insight Control server provisioning. In this case, you will see the target server on the Servers Overview screen and you can delete it.

Processing of response file failed ...

Symptom Possible cause and resolution
Processing of response file failed ... When booting WinPE, you see a terminal window, and you may see a message: “Processing of response file failed: Can’t find a response file on the floppy drives.”

No action is required; this is normal and may be ignored.

Error: can’t get packet

Symptom Possible cause and resolution
When booting WinPE with an external DHCP server, you might see a message in the terminal window that reads, “Error, can’t get packet.” No action is required; this is normal and may be ignored.

Frequent call to Add Server REST API may fail

Symptom Possible cause and resolution
Frequent call to Add Server REST API may fail Calling Add server REST API within 30 seconds of previous Add server REST call may fail with timeout. 

Use minimum of 30 seconds delay between subsequent Add Server REST API calls when adding multiple servers.

prev

 

up

 next

ESXi installation fails with Read only filesystem error 

home

 Troubleshoot OS Build Plan and Build Plan step failures

Copyright © 2012, 2016 Hewlett Packard Enterprise Development LP