DFM: when does the "Alert ID" change for a device?

Unanswered Question
May 25th, 2009

If an Event occures for device_A a corresponding Alert-ID x is generated. All Events for device_A are grouped together under this Alert-ID x.

Is there a corresponding time window in which all incomming Events for device_A will be grouped under this Alert-ID x or - if generated once this Alert-ID x is bound to device_A for eternity? (or just until the next restart of dmgtd?)

Does anybody know the sense behind these not rememberable Alert-IDs which are also useless for Notification Services?

The only thing I found was this:

========

Terminology has changed since DFM 1.2.x as follows:

•Symptom is replaced by event. Events are rolled up into alerts.

•Compound is not used and there is no replacement. A compound differs from an alert; there could be multiple compounds on a single device, whereas an alert is a roll-up of all events for a device.

=======

from this Install Guide:

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/2.0_IDU_2.0.6/installation_solaris/guide/newNav.html#wp1014226

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Mon, 05/25/2009 - 11:22

All events will be rolled into one alert as long as the alert stays active. Once the alert clears, and is moved to Fault History, then a new active event will create a new alert.

No, there is no significance to the Alert IDs. In fact, I typically recommend to customers not to do any notifications of alerts since events have all the juicy details.

Actions

This Discussion