Installation Manual

1. Verify the following:
For ProLiant Gen8 servers: iLO firmware 1.20 or later (Insight Remote Support central
connect) or 1.40 or later (Insight Online direct connect) is installed.
For ProLiant Gen9 servers: iLO firmware 2.00 or later is installed.
AMS is enabled and the OS is running.
For Insight Remote Support central connect only: A supported version of Insight RS is
installed on the host server. For more information, see http://www.hpe.com/support/
InsightRS-Support-Matrix.
For Insight Remote Support central connect only: The RIBCL credentials for the server
have been entered in the Insight RS Console and are associated with the ProLiant
server.
2. Initiate the data collection process from the Remote SupportData Collections page in
the iLO web interface. For instructions, see “Sending data collection information” (page 139).
The OS name and version are forwarded to Insight RS and Insight Online during the data
collection process.
3. If you had an active Insight Online session when you performed Step 2, click the refresh
button ( ) to update the Insight Online view.
If AMS is installed and the OS was running during the most recent data collection
transmission, the OS name and version are listed on the Insight Online Device Configuration
Details page.
Connection error during Insight Online direct connect registration
Symptom
The following error occurs when you try to register a server for Insight Online direct connect:
Cannot connect to remote host.
Cause
The DNS settings are not configured correctly in iLO.
Action
Verify that the DNS information is configured correctly in iLO.
For instructions, see “iLO network settings” (page 96).
iLO session ends unexpectedly during iLO Insight Online direct connect registration
Symptom
The iLO web interface session ends unexpectedly with the error Session Expired when you
try to register a server for Insight Online direct connect.
Cause
The DNS settings are not configured correctly in iLO.
Action
Verify that the DNS settings are configured correctly.
350 Troubleshooting