HP Insight Control Software for Linux - Manual (Page 205)

Corrective actions Cause/Symptom
•
Examine the /opt/hptc/cmf/logs/cmfd.log for
errors.
• Verify cmfd -h for the usage and default startup
parameters.
Perform the appropriate action: The CMF retries failed connections periodically
•
Verify the BIOS configuration.
•
Verify that the management processor user name and
password were not changed.
• Verify the management processor's IP address.
Perform the appropriate action: Faulty or no connection
• Run the following command to check the connection
status:
# cmfmgr -s `headnode` console
•
Send a test message to /dev/console on the
managed system, then examine the log for that
message.
# pdsh -w server 'echo "Hello, world" >
/dev/console'
# ls -l
/hptc_cluster/adm/logs/cmf.dated/current/
Determine if another connection to the VSP exists. Connection is blocked
The management processor allows only one connection at
a time to the virtual serial port (VSP) • Stop the cmfd daemon, then use the ssh or telnet
command to connect to the management processor.
After logging in, enter vsp to access the VSP. If a
Console is not accessible error
message
occurs, it might be that someone else already has a
console connection.
• Ensure that you can log into the management processor
to verify the IP address, the user name, and the
password are correct. Use either the telnet or ssh
command with the IP address of the management
processor as its argument.
•
In an extreme case, power off the managed system to
reset the management processor.
This is not related to the CMF. Do not use function keys. Function keys do not work with some terminal emulators
List the cmfd daemon's debug mode options with the cmfd
-h
command, then run the cmfd daemon with the
appropriate options.
Debug the cmfd daemon
The output is logged in the /opt/hptc/cmf/logs/
cmfd.log
file.
For example, to see the connection attempts and output:
# /etc/init.d/cmfd stop
# /opt/hptc/cmf/sbin/cmfd -d 00000102
25.4 Troubleshooting CMF problems 205