Contents

1   Introduction

This instruction concerns the handling of an alert that does not require intervention.

1.1   Alert Description

The Compute Host Restarted alert is issued by the Managed Object (MO) Node.

The alert is issued if one of the following conditions apply:

• The periodic supervision algorithm detects that one of the compute nodes has failed the availability test three consecutive times, and, following that, it passes the test and becomes available again.
• Or a previously unknown compute node passes the availability test for the first time.

The severity of the alert is WARNING.

The alert attributes are listed in Table 1.

Table 1    Alert Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	2031703
Managed Object Class	Node
Managed Object Instance	Region=<name_of_the_region>, CeeFunction=1, Node=<hostname_of_the_node>
Specific Problem	Compute Host Restarted
Event Type	other (1)
Probable Cause	m3100Indeterminate(0)
Additional Text	;uuid=<hw_uuid_of_failed_server>
Severity	WARNING (6)

1.2   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.1   Documents

Not applicable.

1.2.2   Tools

No tools are required.

1.2.3   Conditions

Before starting this procedure, ensure that the alert was not issued due to ongoing planned maintenance.

If the alert was issued due to ongoing planned maintenance, no further actions are required.

2   Procedure

This section describes the procedure to follow when this alert is received.

2.1   Actions

When this alert is issued, the host has already recovered. Normally, no further actions are necessary. In this case, exit this procedure.

If the alert is issued for the same compute node frequently, perform the following:

1. Collect troubleshooting data as described in the Data Collection Guideline.
2. Consult the next level of maintenance support.

   Further actions are outside the scope of this instruction.

3. The job is completed.