Question & Answer
Question
Capturing Boot Debug in one of these circumstances: * System has no HMC * System is running AIX 5.2 or earlier version
Answer
This document can be used to assist in capturing boot debug information which may help determine why a system is hanging during IPL. These steps are also valid for higher AIX versions for systems without an HMC.
In a non-HMC environment:
Setting up the software
Booting into maintenance mode
Determining boot disc
Enabling the debug boot image
AIX 5L
Preparing the system for shutdown
Setting up the hardware
Hardware requirements for interfacing your AIX box
with a client
Setting up the interfacing system
Hardware requirements for interfacing your PC system
with a client
Setting up HyperTerminal with client
Capturing the debug information
Stopping the KDB after debug is obtained
Non-HMC environment
Setting up the software
Booting into maintenance mode
- Boot into maintenance mode using the system AIX OS cdrom, a mksysb on tape or CD, or a NIM SPOT..
- At the installation screen select 3, Maintainence mode for system recovery.
- Select 1, Access a root volume group.
- Select 0 to continue.
- Select the drive(s) associated with rootvg.
- Select to access the volume group and start a shell.
Determining your boot disc.
Use the lslv command to determine boot disc run.lslv -m hd5NOTE: PV1 is your boot hdisk#.
Enabling the debug boot image
- Use the bosboot command. Enter:
bosboot -I -ad /dev/hdisk#
Preparing the system for shutdown
Use the bootlist command to boot into hdisk# on reboot. Enter:bootlist -m normal hdisk#
Setting up the hardware
During installation with debug mode enabled, debug output is sent to the S1
serial port
of the machine. This output can then be captured to a tty or other
serial connection.
The preferred method for capturing debug mode output is to have another system
near to
the client machine that can interface with it via an rs232 serial
connection.
Debug output is obtained when system hangs. If machine boots normal, the
KDB debugger can be
stopped by doing the following,
Hardware requirements for interfacing your AIX box with a client
Connect the hardware as shown in the schematic below:
[S1]--[X]----[R]----[I][G]----[R]----[X]--[Sx]
Note:
S1 = first serial port on the machine being installed
Sx = any serial port on the connecting AIX box
X = any extra cables needed to connect the DB25-RS232 cable to the serial
port
R = DB25-RS232 cable
I = interposer
G = gender changer (female) to get the right connection to Sx
Setting up the interfacing system
lslpp -l bos.net.uucp
Note: If not If you do not have this installed, you must install it from
the AIX
base installation media.
Note: Defaults
Direct tty0 - 9600 direct
cu -ml tty0 | tee /tmp/boot.debuglog
Hardware requirements for interfacing a PC with your client
The following hardware is needed:
Connect the hardware as shown in the schematic below:
[S1]--[X]----[R]----[I][G]----[R]----[X]--[Sx]
Note:
S1 = first serial port on the machine being installed
Sx = any serial port on the connecting PC
X = any extra cables needed to connect the DB25-RS232 cable to the serial
port
R = DB25-RS232 cable
I = interposer
G = gender changer (female) to get the right connection to Sx
Setting up HyperTerminal with client
Start up a HyperTerminal from your PC by doing the following:
Bits per second 9600
Capturing the debug information
sync
sync
reboot
KDB(0)> mw enter_dbg
Note: The debug is captured in the file /tmp/boot.debuglog on the
AIX
system or in the file name you specified in the hyperterminal session.
enter_dbg+000000: 00000000 = 42
enter_dbg+000004: 00000000 = .
KDB(0)> g
Stopping the KDB after debug is obtained
Note: Running the KDB causes a decrease in performance, it is
recommended that the boot
image be rebuilt and system rebooted. To prevent KDB from running on
next boot up, enter:
bosboot -ad /dev/hdisk#
Historical Number
isg1pTechnote1393
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
isg3T1000628