Automated Actions not working After Upgrade 2.5.1 to 2.6

Unanswered Question
Apr 1st, 2007
User Badges:

I have setup to get automated actions for daily reports, port shutdown alert etc. by email, but after upgrading from 2.5.1 to 2.6 it is not working, I check the automated actions all are enable. ANY CLUE...

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Sun, 04/01/2007 - 21:55
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

For Automated Actions to work, a lot has to happen. First, the syslog messages need to make it from the devices to the syslog message file on the server (e.g. syslog.log on Windows and syslog_info on Solaris). Next, those messages need to be picked up by SyslogCollector, pass through all configured filters, and be sent to a subscribed SyslogAnalyzer. Once the SyslogAnalyzer receives the messages, it can then execute the automated action.


So if AAs are not working, something in that system is broken. More information is needed to figure out where. Are the messages making it to the syslog file on the server? Are they being written into the RME database such that you can see them in the Standard Report?

Actions

This Discussion