Troubleshooting; Bootcfg Usage Information; Potential Kickstart Installation Issues - Compaq BL10e - HP ProLiant - 512 MB RAM Troubleshooting Manual

Setting up a linux pxe server and integrating clients
Hide thumbs Also See for BL10e - HP ProLiant - 512 MB RAM:
Table of Contents

Advertisement

Alternative methods include:
Press F12 during POST to boot to PXE.
If the HP Server Management Drivers and Agents (hpasm) are loaded on the server being
reprovisioned, set the server to a one-time PXE boot by typing:
/sbin/bootcfg -P
This setting allows for changes in the boot process without updating the BIOS or the need to
press F12.
Note
For bootcfg usage information, refer to the "Troubleshooting"
section.

Troubleshooting

This section contains usage information, potential issues, and additional configuration steps to aid in
troubleshooting.

Bootcfg usage information

Usage commands for bootcfg include:
[root root]# bootcfg -?
USAGE: bootcfg [-F -C -H -T] [-S -Q -R -P] [-r -d -n -b]
-D Set Defaults everywhere
-F Floppy first
-C CD ROM first
-H Harddrive first
-T Tape first
-S one time boot to system configuration utility
-Q one time boot to quick configuration utility
-R one time boot to RBSU
-P one time boot to PXE
-r one time remote
-d one time remote dial out
-n one time remote network
-b bypass F1/F2

Potential kickstart installation issues

Kickstart installations might fail due to the client system being unable to mount the NFS directory that
contains the ks.cfg file. The client will report "cannot find ks.cfg" on the console to the user. This error
can be viewed on the NFS server by looking at /var/log/messages or virtual terminal #3 on the
client.
10

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the BL10e - HP ProLiant - 512 MB RAM and is the answer not in the manual?

Questions and answers

This manual is also suitable for:

Bl10e - proliant - g2Bl10e 512

Table of Contents