Compaq BL10e Setting up a Linux PXE server and integrating clients - Page 10

Troubleshooting, Bootcfg usage information, Potential kickstart installation issues

Page 10 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21

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