Root-cause problems diagnosed by Network Protocol Manager for IS-IS lists the root-cause problems that are diagnosed by Network Protocol Manager for IS-IS. For each problem, Table 7 identifies the managed object for which the problem is diagnosed, the condition for the problem, and the events that are correlated by Network Protocol Manager for IS-IS to diagnose the problem.

Table 1. Root-cause problems diagnosed by Network Protocol Manager for IS-IS

Managed object

Root cause

Condition

Events (symptoms) of root cause 1

1**Interpret event entries as <object name>::<event name>.

ISISNetwork

AreaIDMismatch

Misconfiguration symptoms exist on this IS-IS network.

ISISNetwork::AreaIDMismatchSymptom

ISISAdjacency::NeighborStateAlarm

DuplicateSystemID

Misconfiguration symptoms exist on this IS-IS network.

ISISNetwork::DuplicateSystemIDSymptom

ISISAdjacency::NeighborStateAlarm

HelloIntervalMismatch

Misconfiguration symptoms exist on this IS-IS network.

ISISNetwork::HelloIntervalMismatchSymptom

ISISAdjacency::NeighborStateAlarm

MTUMismatch

Misconfiguration symptoms exist on this IS-IS network.

ISISInterface::MTUMismatchSymptom

ISISAdjacency::NeighborStateAlarm

NetmaskMismatch

Misconfiguration symptoms exist on this IS-IS network.

ISISInterface::NetmaskMismatchSymptom

ISISAdjacency::NeighborStateAlarm

ISISInterface

Disabled

This interface or its associated physical interface is administratively down (manually disabled), and at least one IS-IS adjacency on this interface is reporting an improper state.

ISISInterface::DisabledAdminSymptom

Down

This interface is operationally down when two or more IS-IS adjacencies exist on this interface and all of them are down.

ISISAdjacency::NeighborStateAlarm

All IS-IS adjacencies associated with this interface have NeighborStateAlarms.

ISISAdjacency

Down

This IS-IS link between neighboring endpoints is down.

ISISAdjacency::NeighborStateAlarm