Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Device Fault Manager 3.0.5 starts, but have issues with alerts portlet

Hello

We have windows 2003 server running LMS 1.0.1 and DFM 3.0.5, and have error messages on the "High Severity Alerts" DFM portlet says : "An exception occurred. Please check the AAD.log file for further details". AAD.log attached. Also "netstat -anob" attached.

Previously it works fine. dmgtd restart doesn't help. No problem with device management in DFM.

Any help will be really appreciated.

Regards,

Cedric.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Device Fault Manager 3.0.5 starts, but have issues with aler

Your EPM database is down.  This could be due to a corrupt transaction log, or a corrupt database.  First, shutdown Daemon Manager, then delete the NMSROOT/database/dfmEpm/dfmEpm.log if it exists.  Then run the following command:

NMSROOT/objects/db/win32/dbsrv9 -f NMSROOT/databases/dfmEpm/dfmEpm.log

Then try restarting Daemon Manager.  If the EPMDbEngine process is still down, you will need to restore LMS from a known good backup, or reinitialize this database with the command:

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=epm dmprefix=EPM
4 REPLIES
Cisco Employee

Re: Device Fault Manager 3.0.5 starts, but have issues with aler

Post the output of the pdshow command.

New Member

Re: Device Fault Manager 3.0.5 starts, but have issues with aler

Here it is.

Cisco Employee

Re: Device Fault Manager 3.0.5 starts, but have issues with aler

Your EPM database is down.  This could be due to a corrupt transaction log, or a corrupt database.  First, shutdown Daemon Manager, then delete the NMSROOT/database/dfmEpm/dfmEpm.log if it exists.  Then run the following command:

NMSROOT/objects/db/win32/dbsrv9 -f NMSROOT/databases/dfmEpm/dfmEpm.log

Then try restarting Daemon Manager.  If the EPMDbEngine process is still down, you will need to restore LMS from a known good backup, or reinitialize this database with the command:

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=epm dmprefix=EPM
New Member

Re: Device Fault Manager 3.0.5 starts, but have issues with aler

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=dfmEpm dmprefix=EPM

This command helps. Thank you.

268
Views
0
Helpful
4
Replies