The version of LMS is 2.6.

Below is the sample of email notification that we have received.

From: pcgnm2001

Sent: Saturday, January 24, 2009 5:32 AM

To:

Subject: 00026QB ; pcgsw1011 ; Thu 22-Jan-2009 21:20:48 CST ; Critical ;

OperationallyDown ; Active

EVENT ID = 00026QB

ALERT ID = 000064L

TIME = Thu 22-Jan-2009 21:20:48 CST

STATUS = Active

SEVERITY = Critical

MANAGED OBJECT = pcgsw1011

MANAGED OBJECT TYPE = Switches and Hubs

EVENT DESCRIPTION = OperationallyDown::Component=PORT-pcgsw1011/10101 [Gi1/0/1] [*** Connection To PCGRT9011 ***];Type=ETHERNETCSMACD;OperStatus=DOWN;InterfaceCode=CODEUNKNOWN;DuplexMode=FULLDUPLEX;AdminStatus=UP;LastChangedAt=22-Jan-2009 9:20:48 PM;IsFlapping=false;Max

So is the problem that email notifications are being delayed, or that these events are not showing up in DFM's Alerts and Activities Display? From this particular event, it appears that it should be showing up in AAD around 1/22/09 21:20.

Most of the alerts from Alerts and activities feature are delayed, not only in email notification.

Any suggestions?

Enable Event Promulgation Module and Adapter debugging under DFM > Configuration > Other Configurations > Logging. When the problem occurs again, post the logs under NMSROOT\log\dfmLogs\EPM and epa along with a sample delayed event.

If we enable the debugging on ciscoworks, this will not incur high utilization on the server? Our syslog file occupies large disk space because the logrot is not working.. Please advise..

Thank you very much for your assistance..

It depends on how active DFM is (i.e. the number of devices and number of events) as to the CPU impact this debugging will incur. Typically, the impact will be minimal.

Thank you very much!

I'll post the logs and the sample delayed events when the problem reoccurs..