I got these results this afternoon (10/21) with RME 3.5 IDU 11.0.
1. In Severity Level Summary, with all devices and 10/21 chosen, I get No records found.
2. In Severity Level Summary, with all devices and 10/16 through 10/21 chosen, I get No records found.
3. In Severity Level Summary, with all devices and 10/16 through 10/20 chosen, I get the regular report with syslogs up to 23:5x from 10/20.
4. In Standard Reports, with all devices and 10/20 through 10/21 chosen, I get "Invalid records received from server."
5. In Standard Reports, picking top half of the devices (alphabetically) and 10/20 through 10/21, I get the same "Invalid records received from server."
6. In Standard Reports, picking bottom half of the devices (alphabetically) and 10/20 through 10/21, I get a report back, with newest syslog messages from 00:58 today (10/21/2005) for only one device (a cat6k IOS). That means no other devices have any syslog messages for 10/21.
Based on these observations, I think either there's something wonky with the RME database that stores the syslog analysis or RME is falling terribly behind analyzing the messages. RME appears to have no problem reading syslog messages, as Syslog Collector Status "Last Activity" is only 5-7 mins behind real-time.
It seems to have worked! I think I tried the same steps a few weeks ago that cured it for a while until this last instance. Now I recall I had seen somewhere in the CiscoWorks admin guide that it could support with local7.info. I guess local7.debug is too much for it to handle after a few weeks.
Can I have the following in syslog.conf, 1) to get more detailed logs to nmslog, and 2) to satisfy CiscoWorks?
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.