DHCPv4, Failover Time Skew

Contents

1Introduction
1.1Alarm Description
1.2Prerequisites

2
Procedure
2.1Synchronizing Time

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

This alarm is issued when time on the primary and secondary DHCPv4 servers is out of synchronization.

The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.

Table 1    Alarm Causes

Alarm Cause

Description

Fault Reason

Fault Location

Impact

Solution

Time on the primary and secondary DHCPv4 servers is out of synchronization.

The time difference between primary and secondary DHCPv4 servers should not more than 60 seconds. Otherwise, the failover mechanism between two servers cannot implement.

Timing within the servers is disrupted because of maintenance activities.

DHCPv4 server

The failover mechanism of DHCPv4 server cannot implement.

See Section 2.1 Synchronizing Time

Note:  
An alarm can appear as a result of the maintenance activity.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name

Attribute Value

Major Type

193

Minor Type

872452

Managed Object Class

IpworksDhcpv4

Source

ManagedElement=<Node Name>,SystemFunctions=1,Fm=1,FmAlarmModel=ipworksDHCPv4,FmAlarmType=ipworksDhcpv4FailoverTimeSkew,HostName=<PL hostname>

Specific Problem

DHCPv4, Failover Time Skew

Event Type

ENVIRONMENTALALARM <read-only>

Probable Cause

x733TimingProblem(66)

Additional Text

This alarm is raised when the time on the primary and secondary is out of synchronization and the servers are not operating in failover mode.;uuid:<Product_UUID>(1)

Perceived Severity

Major

(1)  <Product_UUID> is the universally unique identifier (UUID) of machine that generates the alarm. The value can be fetched from /sys/devices/virtual/dmi/id/product_uuid on the PL node.


1.2   Prerequisites

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

1.2.1   Documents

Before starting this procedure, ensure that you have read the following documents:

1.2.2   Tools

No tools are required.

1.2.3   Conditions

No conditions.

2   Procedure

This section describes the procedure to clear this alarm.

2.1   Synchronizing Time

Do the following:

  1. Check the alarm list, make sure the alarm "LOTC Time Synchronization" also exists on the DHCPv4 server machine.
  2. Try to clear the alarm "LOTC Time Synchronization" first. For more information, refer to LOTC Time Synchronization.
  3. If the alarm “LOTC Time Synchronization” is cleared successfully, this alarm should be cleared automatically.
  4. Confirm that the alarm has ceased. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction.


    DHCPv4, Failover Time Skew