I've been using this code and works great. I would like to ask if there's a way to get (during the audit process or after) the list of the lines used for auditing the backed up configurations.
Since our Rules files ares big and used for many devices we would like to identify the lines that we do use for our audits. Of course, I can identify them looking at the rules, but I think it can be automated.
Our goal is to have our baseline files like this: (lines starting with % are the audited ones)
% interface Vlan16
description SRV_16
% vrf forwarding V203
ip address 10.10.16.2 255.255.248.0
% no ip redirects
% no ip proxy-arp
% standby delay minimum 0 reload 60
% standby version 2
% standby 0 ip 10.10.16.1
% standby 0 priority 110
% standby 0 preempt delay minimum 300 reload 300
shutdown
bfd interval 750 min_rx 750 multiplier 3
arp timeout 300
So we can know exactly what is audited in every file.
I hope this is clear.
I've been using this code and works great. I would like to ask if there's a way to get (during the audit process or after) the list of the lines used for auditing the backed up configurations.
Since our Rules files ares big and used for many devices we would like to identify the lines that we do use for our audits. Of course, I can identify them looking at the rules, but I think it can be automated.
Our goal is to have our baseline files like this: (lines starting with % are the audited ones)
% interface Vlan16 description SRV_16 % vrf forwarding V203 ip address 10.10.16.2 255.255.248.0 % no ip redirects % no ip proxy-arp % standby delay minimum 0 reload 60 % standby version 2 % standby 0 ip 10.10.16.1 % standby 0 priority 110 % standby 0 preempt delay minimum 300 reload 300 shutdown bfd interval 750 min_rx 750 multiplier 3 arp timeout 300
So we can know exactly what is audited in every file. I hope this is clear.
Thank you for your help.