HP Insight Control Software for Linux User Manual

Page 206

Advertising
background image

Corrective actions

Cause/Symptom

Console command cannot connect to console.

Verify that cmfd is running on each of the

management

hub

s; the console command searches for the cmfd

daemon that has the connection to the console.

Verify that the dates on the management hubs are
synchronized.

Make sure that:

Console command connects to cmfd but there is no output.

The BIOS on the managed system is configured to
redirect the serial port to the management processor.
For more information, see

Section 8.3.5 (page 83)

.

The /boot/grub/menu.lst and /etc/inittab
files on the managed system are configured to redirect
console output to the serial port. For more information,
see

Section 8.3.5 (page 83)

.

The serial port settings are correct:

If the BIOS is set up to use COM1 as the serial port,
then /boot/grub/menu.lst and /etc/inittab
must use ttyS0.

If the BIOS is set up to use COM2 as the serial port,
then /boot/grub/menu.lst and /etc/inittab
must use ttyS1.

Can't log in as root.

Make sure that the /etc/securetty file contains
ttyS0

or ttyS1, depending whether COM1 or COM2

is used as the serial port.

Can't quit out of the console command.

Press ESC-SHIFT-Q

Examine the /opt/hptc/cmf/logs/cmfd.log file for
any errors.

CMF encounters a fatal error.

Perform the appropriate action:

Console output is not being collected for the managed
system.

Ensure that the target system’s VSP (Virtual Serial Port)
is properly configured in its management processor.

Follow these steps:
1.

Ensure that the target system’s console is being
redirected to ttyS0 (COM1) or ttyS1 (COM2).
This is done by setting console=ttyS0 or
console=ttyS1

in the /boot/grub/menu.lst

file.

2.

Log on to the target system and echo sample text
to /dev/console. Verify that the output appears
in the console log for the target system.

3.

If the problem persists, stop cmfd with the
/etc/init.d cmfd stop

command and

manually ssh or telnet to the management port.

4.

Log in.

If the management processor of the target system
is iLO-based, type vsp to access the Virtual Serial
Port; For LO100 management processors, enter
ESC-Q.

5.

Log on to the target system and echo sample text
to /dev/console.

If nothing appears in your ssh or telnet session,
either the Virtual Serial Port was not properly
configured in the BIOS or serial port redirection
was not properly configured in the OS.

206 Troubleshooting

Advertising