HP XC System Software Release Notes for Version 3.0

11 Cluster Platform 4000 Notes
This chapter contains information that applies only to Cluster Platform 4000 systems.
11.1 HP ProLiant DL145 G2 Console Port Might Lose Connectivity to the
Administration Network
During normal operation of an HP ProLiant DL145 G2 node, the console port may lose connectivity
to the administration network for periods of tens of seconds to several minutes. This loss of
connection causes a disruption in node management and monitoring.
The connection loss is characterized by "no route to host" messages when using the ping
command to contact the node.
In most cases, the connection loss is related to a power action performed on the node, for instance,
when issuing a command to turn power on or off to a node, a shut down sequence performed
by the operating system, and so on.
The power command and some of the monitoring facilities do not operate properly when this
condition exists. For example,
• If a node's console port loses connectivity to the administration network, you will see the
message “NO_RESPONSE_ERROR” when running the power [--on | --off
|--status] command.
• You may also see the following error in the output of the shownode metrics sensor
command:
# shownode metrics sensors
2005-10-17 06:44:56 |n446 |Error |0 |Unable to retrieve sensor information
• The CMF daemon, cmfd, will also lose its connection to the node's console port and console
logging for that node will temporarily cease. However, cmfd tries to reconnect to the node's
console port every 60 seconds until successful.
11.2 Benign Message During Reboot
You can safely ignore the following message, which you might see when an Opteron-based
system reboots:
microcode /dev/cpu/0/microcode doesn't exist?
11.1 HP ProLiant DL145 G2 Console Port Might Lose Connectivity to the Administration Network 57