psarsfield

Is anyone from Solarwinds available to further explain why the above will not work, given the RegEx matches for each line?

The four lines above were created as separate regex filters in the config change report; I would think that each line would be treated and processed individually. On Cirrus 4.01, it appears that the regular expressions may be broken (Unless you can spot a problem).

Does Cirrus V4 not support true regex? I've tried creating all of the following strings, but it does not ignore the cert (And even more basic variations of the regex, such as [A-F0-9]+ don't seem to match): certificate self-signed [A-F0-9]{8} [A-F0-9]{8} [A-F0-9]{8} [A-F0-9]{8} [A-F0-9]{8} [A-F0-9]{8} [A-F0-9]{8}…

We use the built-in nightly config backup tasks. In settings, under Configs->Config Archive, the Save a copy of each config...when it is downloaded option is checked. We then use the following for naming the files: ${NodeGroup}\${Caption}\${Date}\${Caption}-${ConfigType}.Config

You could just unmanage the old nodes, remove them from any relevant maps, and leave them in Orion until such time that you no longer need the data from them. This is only particularly tricky if you are reusing the same IP addressing for management (But they could be changed to something bogus). Just be sure that you have…

The 9000 series is SanOS rather than IOS. It's a similar interface, but not entirely the same. It's likely a new template will need to be made (Which the Session-Trace will help with).

We run a scheduled task each night that saves the running and startup config of each device to a dated folder (Under the device name) on a network share. This is relatively easy to setup and may be a simple workaround for you going forward. It's also a easier to work with if something were to ever happen to the cirrus…