ISIS/4/PEER_DWN_HLDTMR_EXPR

Message

ISIS/4/PEER_DWN_HLDTMR_EXPR:ISIS [process-id] neighbor [neighbor] was Down on interface [interface-name] because hold timer expired. The Hello packet was received at [hello-time] last time; the maximum interval for sending Hello packets was [max-interval]; the local router sent [send-number] Hello packets and received [receive-number] packets; the type of the Hello packet was [packet-type]; CPU usage was [cpu-percent]%.

Description

The IS-IS neighbor went Down on the interface because the Hold timer expired.

Parameters

Parameter Name	Parameter Meaning
[process-id]	Indicates the ID of an IS-IS process.
[neighbor]	Indicates the system ID of a neighbor.
[interface-name]	Indicates the name of an interface.
[hello-time]	Indicates the time when a Hello packet was received last time.
[max-interval]	Indicates the maximum interval for sending Hello packets.
[send-number]	Indicates the number of Hello packets that were sent.
[receive-number]	Indicates the number of Hello packets that were received.
[packet-type]	Indicates the type of the Hello packet. The type can be P2P: indicates the P2P Hello packet. Lan Level-1: indicates the Hello packet in the Level-1 broadcast network. Lan Level-2: indicates the Hello packet in the Level-2 broadcast network.
[cpu-percent]	Indicates the CPU usage.

Possible Causes

A Hello packet was not received from the neighbor within the time period specified by the Hold timer, and thus the IS-IS neighbor became Down.

Procedure

Judge whether the neighbor relationship needs to be established on the interface. If so, go to Step 2; if not, go to Step 4.
Check the status of the devices between which the neighbor relationship is established.
Collect log information and configuration information, and then contact technical support personnel.
End.