Events detected by Network Protocol Manager for IS-IS lists the events that are detected by Network Protocol Manager for IS-IS and used as symptoms to diagnose root-cause problems. For each event, Table 8 identifies the managed object for the event, the condition that triggers the event, and whether the event is imported by the Global Manager.

Table 1. Events detected by Network Protocol Manager for IS-IS

Managed object

Event (symptom)

Condition

1**Imported by the Global Manager.

2**Informational only, that is, this event is not used to diagnose IS-IS root-cause problems.

ISISNetwork

AllRouterPrioritiesZero 1,2

No device on this broadcast or NBMA network has a priority greater than 0.

AreaIDMismatchSymptom

An area ID misconfiguration exists on neighboring interfaces of this IS-IS network.

DuplicateSystemIDSymptom

A duplicate system ID misconfiguration exists on neighboring interfaces of this IS-IS network.

HelloIntervalMismatchSymptom

A Hello interval misconfiguration exists on neighboring interfaces of this IS-IS network.

ISISInterface

DisabledAdminSymptom

This IS-IS interface or its associated physical interface is administratively down (manually disabled), and IS-IS adjacencies exist on this interface.

MTUMismatchSymptom

An MTU misconfiguration exists on this IS-IS interface, propagated from IS-IS adjacencies associated with this interface.

NetmaskMismatchSymptom

A netmask misconfiguration exists on this IS-IS interface, propagated from IS-IS adjacencies associated with this interface.

ISISAdjacency

NeighborStateAlarm 1

One of the two neighbors for this IS-IS link is reporting an improper neighbor state.

RedundancyGroup

(described in “RedundancyGroup” on page 46)

AllComponentsDown 1

None of the member objects in the IS-IS redundancy group are responsive or operational.

AtRisk 1

Only one of the member objects in the IS-IS redundancy group is responsive or operational.

ReducedRedundancy 1

Applies only to IS-IS redundancy groups that contain three or more member objects: At least one member object in the redundancy group is unresponsive or not operational, but the number of responsive or operational member objects is at least two.