Unable to connect to ilo ip address, Blocked ilo ports, Troubleshooting alert and trap issues – HP Integrated Lights-Out 4 User Manual
Page 305
NOTE:
If a network connection is established, you might have to wait up to 90 seconds for
the DHCP server request.
Unable to log in to iLO after installing iLO certificate
Solution: Do not install the iLO self-signed certificate in the browser certificate store. If you want to
install the iLO certificate, request a permanent certificate from a CA and import it to iLO. For
instructions, see
“Administering SSL certificates” (page 67)
.
When you reset iLO to the factory defaults or change the iLO host name, a new self-signed certificate
is generated. If the iLO self-signed certificate is installed permanently in some browsers, you might
not be able to log back in to iLO after the new self-signed certificate is generated.
Unable to connect to iLO IP address
Solution: If the web browser software is configured to use a proxy server, it will not connect to the
iLO IP address. To resolve this issue, configure the browser not to use the proxy server for the IP
address of iLO. For example, in Internet Explorer:
1.
Select Tools
→Internet Options.
2.
Click Connections.
3.
Click LAN settings.
4.
Click Advanced in the Proxy server section.
5.
Enter the iLO IP address or DNS name in the Exceptions box.
6.
Click OK to save the changes.
Blocked iLO ports
Solution: iLO communicates through several configurable TCP/IP ports. If these ports are blocked,
the administrator must configure the firewall to allow for communications on these ports. For
information about viewing and changing the iLO port configuration, see
.
Troubleshooting alert and trap issues
lists the alerts and traps that might occur.
Table 18 Alerts
Description
Alert
This trap is generated when you click the Send Test Alert button on the
Administration
→Management page in the iLO web interface.
Test Trap
The server lost power.
Server Power Outage
The server was reset.
Server Reset
A remote user login attempt failed.
Failed Login Attempt
This is an error condition that is not predefined by the hard-coded MIB.
General Error
The circular log has been overrun.
Logs
The state of the Security Override Switch changed (On/Off).
Security Override Switch
Changed: On/Off
The server could not power on because of insufficient power.
Rack Server Power On Failed
The server was forced to power on manually despite reporting insufficient
power.
Rack Server Power On Manual
Override
The name of the rack was changed.
Rack Name Changed
Troubleshooting alert and trap issues 305