Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP XC System Software : XC Version 3.1 Release Notes > Chapter 5 System Configuration

Notes That Apply to the Discover Process

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The notes in this section apply to the discover utility.

Segmentation Fault Observed with Enclosure-Based discover Command

This note applies only to hardware configurations containing HP server blades and enclosures.

You might see a segmentation fault during processing of the enclosure-based discover command (discover --enclosurebased). This fault occurs after the database and system files have been written. Thus, the segmentation fault is benign.

Benign Messages with Enclosure-Based discover Command

This note applies only to hardware configurations containing HP server blades and enclosures.

The discovery process for HP server blades and enclosures is performed incrementally with the --network , --enclosures , and --nodes options.

The discover command sometimes reports that these are illegal options. You can safely ignore these warnings ignored.

ProLiant DL145 G2 2 Console Port Might Lose Connectivity to the Administration Network

This note applies only if the HP ProLiant DL145 G2 node is installed with BMC firmware version 1.03 or earlier.

During normal operation of an ProLiant DL145 G2 node, the console port may lose connectivity to the internal 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.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2006 Hewlett-Packard Development Company, L.P.