Cisco Systems 12000/10700 V3.1.1 manual Heartbeat Polling, Connectivity Management, 18-7

Chapter 18 Fault Management

Heartbeat Polling

An example Configuration Management Event Alarm Description is:

“Config Change, Command Source: commandLine, Config Source: running, Config Destination: commandSource”.

This would be received when a <write memory> command was issued.

Alarms are raised against the Chassis object with Informational Severity.

Heartbeat Polling

Heartbeat polling begins automatically when you commission a chassis. The chassis and all objects within the chassis are polled every five minutes. There are two types of heartbeat polling: Connectivity Management and Operational Status Polling.

The Heartbeat Polling section covers the following areas:

•Connectivity Management

•Operational Status Polling

•Disabling Heartbeat Polling

•Performance Logging

Connectivity Management

Cisco 12000/10720 Router Manager polls the management interface on the Cisco 12000/10720 Router every 60 seconds to determine network connectivity. If management connectivity is lost, the chassis enters into a lost comms state and this state ripples down to all subchassis objects. A major lost comms alarm is raised against the chassis. The chassis continues to poll. If it detects re-establishment, it puts the chassis state back to the relevant state and this state ripples down to all subchassis objects as well. An alarm of Normal severity is then raised which clears the major lost comms alarm.

Operational Status Polling

Operational Status Polling—Occurs at module and interface levels. Each module and interface polls for its own operational status. For modules or interfaces, this is every 5 minutes. If a module or interface detects that its operational status is down, it enters into the Errored state and raises a Major alarm. In the Errored state the module or interface will continue to poll if the condition has been rectified. If it detects that the operational state has moved back to healthy then the object will transition into the Normal state and raise an alarm of Normal severity which will clear the previous Major alarm.

Disabling Heartbeat Polling

You can stop heartbeat polling on an individual interface by decommissioning the interface. You might want to do this if you have interfaces that are not yet connected or live. For example, when you commission a chassis, subchassis discovery is automatically initiated. If you have pre-deployed interfaces that are not yet live, these are discovered and put into an Errored state, after no connectivity is detected on them. An alarm is also be raised on the interface. To correct this situation, you need to decommission the inactive interface and clear the alarm manually.

Cisco 12000/10700 v3.1.1 Router Manager User Guide

OL-4455-01 18-7