Appendix J Troubleshooting

J.10.5 Configuration Center, Chassis View, Diagnostics Center, and Statistics Report Problems

A CorrelatedBmRule can have any of the following:

0 or more ClearAlarmCondIds

1 new alarm (which consists of NewAlarmConditionID, NewAlarmServAffect, and so on)

3.Transient Alarm Rule Type

The transient alarm rule type is used to distinguish events from alarms. The alarm list shows some events. Events are normally associated with the NMS itself. Examples of events are Process Restarted or Primary Gateway Disconnected. These are NMS events that are not correlated, but are displayed in the alarm list. Another example of a transient event that is not related to the NMS is a card switchover. If automatic protection switching (APS) is enabled on a card and there is an APS switchover, an event will be displayed in the alarm list. The primary distinction between transient events and correlated alarms is that transient events are not cleared by the network, whereas correlated alarms are. See Figure J-5.

Figure J-5 Transient Alarm Rule Diagram

A transient alarm rule can have only one new alarm associated with it.

Note There is no ClearAlarmCondID associated with a transient rule. Transient alarms can be manually cleared by the user, cleared by the same transient alarm occurring twice, or purged by NMServer when a high threshold is hit.

J.10.5.5.3 Alarm Severity and Object Severity

Every alarm in an alarm rules XML file is assigned two severities: object and alarm. The two severities are called Object and Alarm severity. These severities do match for most alarms. There are some cases, however, where these severities are different. The following is an example of an XML alarm rule where object and alarm severity do not match:

<CorrelatedRule State="1 -1"> <ClearAlarmCondID>10302</ClearAlarmCondID> <ClearAlarmCondID>10303</ClearAlarmCondID> <ClearAlarmCondID>10304</ClearAlarmCondID> <NewAlarmCondID>10301</NewAlarmCondID> <NewAlarmServAffect>0</NewAlarmServAffect> <NewAlarmTransient>0</NewAlarmTransient> <NewAlarmDbPersistent>0</NewAlarmDbPersistent>

Cisco Transport Manager Release 6.0 User Guide

 

78-16845-01

J-65

 

Page 65
Image 65
Cisco Systems 78-16845-01 appendix Alarm Severity and Object Severity, Figure J-5 Transient Alarm Rule Diagram