HP Insight Control for Linux 6.2 User Guide

25.27 Troubleshooting virtual media problems
Corrective actionCause/Symptom
Perform the following actions:
• Verify that port 60002 is open on the CMS.
• Run the Insight Control for Linux
Configure→IC-Linux→Configure Boot Method task.
Be sure to select Virtual Media for the boot method.
For more information, see “Changing the boot method”
(page 80)
Server attempts to PXE boot or boot from local disk
instead of booting using virtual media.
Obtain and apply the iLO Advanced License.While running a task, an error is displayed indicating
that the server is not licensed for virtual media.
Use a browser to connect to the iLO and grant the user
virtual media privileges. For more information, see
“Preparing for virtual media” (page 64).
While running a task, an error is displayed indicating
that the user is not authorized to use virtual media.
If the IP address specified by the REPOSITORY_HTTP_IP
parameter in the /opt/mx/icle/icle.properties
file is not accessible by the iLO because they are on
different networks, then set the value of the
VIRTUAL_MEDIA_REPOSITORY_IP parameter to the IP
address on the CMS that is reachable by the iLO.
While running a task, an error is displayed indicating
that a timeout has occurred and the virtual media could
not be mounted.
The problem might be that the server’s NIC is on a private
network, but its iLO is on a public network.
Perform the appropriate action:
• Verify that port 60002 is open on the CMS.
• Run the Network Configure Editor and verify that
the network parameters for the server are specified
correctly
For information on the Network Configure Editor,
see “Using the Network Configuration Editor”
(page 70).
Virtual media bare metal discovery fails
Ensure that the HTTPS port on the CMS (the default value
is 60002) is properly specified in the /opt/mx/icle/
icle.properties file and it open on the CMS.
See also the other corrective actions in this section.
Virtual media falls back to PXE boot.
If DHCP is configured in your environment and issues
arise when the server uses virtual media to boot, the server
might be booted using the PXE boot method instead.
260 Troubleshooting