[Solved] Unimus results versus RANCID's

[jktucker58]

Hello,

Newbie here evaluating Unimus to replace RANCID. I have a Cisco switch configured in Unimus and it is getting the configs fine at 3AM. RANCID is detecting a configuration change at 3AM each time indicating that the login from Unimus (Network_Service) made it.

Code: Select all

@@ -33,7 +33,7 @@
  !
  config-register 0x2102
  !
- ! Last configuration change at 03:00:11 EST Thu Feb 3 2022 by Network_Service
+ ! Last configuration change at 03:00:11 EST Fri Feb 4 2022 by Network_Service
  ! NVRAM config last updated at 16:11:08 EST Fri Jan 21 2022 by admin_user
  !

But Unimus doesn't report any change at all each run, just showing the date range in the Backups window.

Here is the output from a SSH session.

Code: Select all

#show running-config 
Building configuration...

Current configuration : 49108 bytes
!
! Last configuration change at 03:00:11 EST Fri Feb 4 2022 by Network_Service
! NVRAM config last updated at 16:11:08 EST Fri Jan 21 2022 by admin_user

Firstly, what would be Unimus be doing that would appear to be a change? The network team is uncomfortable this is occuring. Secondly, why the conflicting views? Thanks in advance!

[Tomas]

Hi,

Firstly, what would be Unimus be doing that would appear to be a change? The network team is uncomfortable this is occuring.

Unimus never does any changes to the device config during Discovery nor Backup - we have a very strong philosophy that Unimus (well, any system in fact) should not change anything without the operator's explicit instructions.

You can inspect the full CLI interaction by enabling "Zones > YourZone > Debug Mode > Device output logging". This will enable logging of anything sent/received to/from devices by Unimus, so you can review exactly what Unimus sends to the device.

From the logs you should be able to check and verify that Unimus doesn't perform any configuration on the device during scheduled jobs

Secondly, why the conflicting views?

As for why Unimus doesn't trigger a change when Rancid does - we have a built-in filter for Cisco IOS for this (docs: Backups + Backup Filters).

We added a filter for this timestamp, exactly because IOS behaves rather ... strangely with this timestamp. For example, just doing "wr mem", even if there is NO change in running vs. startup will trigger this timestamp to change. This created many false-positive change notifications (like you see in your use).

I don't know if Rancid has some built-in filtering (I know Oxidized does). Since Rancid doesn't filter this change, you get a change detected by Rancid, but not by Unimus (due to our filters).