Contents

1   Introduction

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

1.1   Alert Description

The Fuel Restarted alert is issued by the Managed Object (MO) Fuel.

The alert is issued if the following conditions apply:

• The periodic supervision algorithm detects that the vFuel node has failed the availability test at least three consecutive times, and, following that, it passes the test and becomes available again.
• A previously unknown vFuel 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	2031705
Managed Object Class	Fuel
Managed Object Instance	Region=<name_of_the_region>, CeeFunction=1, CtrlDomain=1, Fuel=<fuel_master_ip>
Specific Problem	Fuel Restarted
Event Type	other (1)
Probable Cause	m3100Indeterminate(0)
Additional Text	N/A
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 vFuel node has already recovered. Normally, no further actions are necessary.

If the alert is issued 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.

3   Additional Information

For information about the manual failover on the cold standby Fuel VM, refer to Fuel Synchronization.