I'm not getting any RTN of config changes, so I tried to change my Node monitoring to rediscover every 59 minutes, but NONE of my node's "Next Discovery" time has changed since Friday
Is there a way I can *force* rediscovery ??
Doug
The RTN feature is triggered based off an external monitoring tool, like the Orion Syslog Server, notifying Cirrus of a configuration change. I recommend ensuring that the network devices are configured to send the desired notifications (either traps or syslog messages) to the appropriate server, that the external monitoring tool is configured to notify the RTN feature of a change, and that RTN is enabled within Cirrus. You can find out more about configuring the RTN feature within the Admin Guide at http://www.solarwinds.com/CirrusDocs/CirrusAGRTCCD.htm.
FYI, the rediscovery setting does not impact the RTN feature.
I hade RTN working fine under Cirrus 3.5.1, but it "broke" when I upgraded to Cirrus v 4.0 I have had a ticket open with support since 12/21
I am reveiving Syslog entries when I make a config change, and when I manually download the config (after making a change) and compare it to the last config, the differences do show up.
There has not been a change to my RTN.log file since I upgraded to Cirrus version 4.0 even though I have made changes, they appear in the syslog, and RT change detection is enabled within Cirrus
