Chime In If your RTD Works

I'm in desperate need of help. I've had NCM for about 3 months now and have yet to get the real-time change detection working properly. I've had an ongoing case opened with tech support, but I think they're ignorning me now since they can't find a solution. Here is my situation...

Scheduled config backups once a weak (runnning & startup). Download options are set to monitor running and compare to "Last Config". I've selected "Cache Results". RTD is configured to email me with any results. I've made countless changes to configs, all of which are logged successfully in the RTN.log file. Each entry in the log states, "downloaded and discarded running config - no change". If I manually download the new config and compare to the previous running config, the changes are highlighted.

Support has had me try numerous things including select "Startup" rather than "Running" from teh download options, slecting "Baseline" rather than "Last Config". I have even completely moved NCM to a totally new server. Please let me know if anyone has any ideas or thoughts. This is one of many issues I'm having with NCM that I'd really like to get resolved. Many of the features I was counting on are not working.

Find more posts tagged with

Accepted answers

All comments

Gustelj

It is kinda working for me, although I'm not comfortable to wide deploy it to my production environment, yet. I have some issues, but support is quite helpful. Why would you need regular scheduled config backups with working RTD?

DirtySouth

Thanks for the reply. We use the weekly config downloads just for archive purposes. It's always nice to have full copies of configurations. Also, I'm not sure that RTD will even work if you're downloading configs regularly.

Even though I'm regularly downloading configs the "Devices Backed Up vs All devices" graph is always solid blue. I've got a case for that as well.

mark_wiggans

I think this is a bug that will be addressed in the next release. Have you tried removing the snippets as a workaround?

Gustelj

Currently I am downloading configurations manually at occasions. My plan is to employ real time configuration change detection to automatically download configuration at every change and only then. Following the procedure in NCM Administration Guide (pages 47-50), I configured the Syslog rule to detect messages that are sent by my devices, when someone changes their configurations, and the action to download the configuration. My problem was (is) that the action triggered the same type of message that started it at the first place and I ended up in a loop. The additional action that should stop processing Syslog rules doesn’t work as expected. The support suggested changing the protocol for requesting and downloading the configuration. It helped. I am sure that different devices behave differently when changing their configurations.

DirtySouth

Bump....anyone else have any ideas, thoughts, suggestions?