2 custom os installations – HP Insight Control Software for Linux User Manual
Page 243
Corrective actions
Cause/Symptom
Verify that a proxy is not used to communicate between
the CMS and the managed system.
Insight Control for Linux does not have proxy server
support; the Insight Control for Linux features do not
communicate through proxy servers, and require direct
network connectivity between the CMS and the managed
systems.
Proxy information can be defined using an environment
variable or various configuration files. Examine the output
of the env command as well as the contents of the /etc/
wgetrc
file to ensure that you do not have any proxy
variables set in your environment that may interfere with
Insight Control for Linux.
OS Installations fail, cannot connect to managed system
Verify that a proxy is not used to communicate between
the CMS and the managed system.
Insight Control for Linux does not have proxy server
support; the Insight Control for Linux features do not
communicate through proxy servers, and require direct
network connectivity between the CMS and the managed
systems.
Proxy information can be defined using an environment
variable or various configuration files. Examine the output
of the env command as well as the contents of the /etc/
wgetrc
file to ensure that you do not have any proxy
variables set in your environment that may interfere with
Insight Control for Linux.
OS Installations hang
23.15.2 Custom OS installations
Corrective actions
Cause/Symptom
Select an OS version that is compatible with the server
hardware architecture.
The selected OS is incompatible with the server
hardware.
Correct the “kernel append” line and rerun the tool.
The selected OS does not support network based
installations.
Verify that the kernel and initrd file names as used in
the repository.
The kernel or initrd (RAM disk) names are not correct.
Verify that the configuration file is accessible over the
network from the target managed system and verify the
proper kernel append line syntax.
The installation configuration file could not be accessed
at the location specified on the kernel append line.
Copy the correct boot image and RAM disk files into the
appropriate /opt/repository subdirectory.
The correct boot image was not copied into the
appropriate /opt/repository/boot subdirectory.
Correct the installation configuration file and copy it to
the appropriate /opt/repository subdirectory.
The user-edited installation configuration file was
invalid.
Ensure that the OS exists in the Insight Control for Linux
repository.
The selected OS has been deleted from the Insight
Control for Linux repository.
Copy the proper OS files into the appropriate /opt/
repository
subdirectories.
The proper files were not copied from the installation
media into the appropriate /opt/repository/custom
subdirectories
For the corrective action, see
The target server has lost association with its
management processor.
23.15 Troubleshooting OS installation and image deployment problems
243