Cisco Systems 78-16845-01 appendix XML Schema for Alarm Rules

Appendix J Troubleshooting

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

Figure J-2 Client/Server Architecture for Alarm Components

Alarm Client

Alarm Service	Alarm Observer
Client
	Network Monitor Server
	(Alarm Components)
Alarm Service	Client Handler
Alarm Repository	Object Tree
	120750

J.10.5.5.2 XML Schema for Alarm Rules

Alarm rules are defined in XML, specifically, in a file named $HOME/xml/ruledata.xml. These alarm rules are read once when NMServer starts. When events are processed, the rules are queried from memory to determine what action, with regard to alarms, should be taken on the event. There are three types of alarm rules defined in the XML schema: Correlated, Correlated Bitmap, and Transient. Specifics on each of these three types are as follows.

1.Correlated Alarm Rule Type

The correlated alarm rule type is the most common in ruledata.xml. This rule is used when a network element can be in only one of many states at any one time. If the entity were to change states, then the previous alarm state would be cleared. Most network elements managed by CTM fall into this category. A simple example is the database sync-up status of a node. The sync-up status can be one of Partial Sync-Up, Sync-Up Failed, or In Sync. Any one of these states correlates out any other. See Figure J-3.

Cisco Transport Manager Release 6.0 User Guide

78-16845-01 J-63