There are cases where certain lines in a running config will not show up in a startup config. I need to be able to see when someone adds the line, but not be flagged for comparing running and startup configs. If there were configuration comparison profiles, I could choose which profile to use when comparing running to running or startup to startup, and when comparing running to startup.
The specific case I'm working on is on an ADTRAN device. This interface line "no lldp send 802.3-info mac-phy-config" only shows up on the running config, but not the startup config. I would like to be able to ignore this between running and startup checks, but want to be able to catch it when comparing running configs.
I'm being told that there are some other cases where the running and start won't match, so I thought I could solve this if I had different comparison profiles to use between different config types. If I run into more specific examples, I'll come back and add them to this FR.
*I checked a larger sample, and I may have my example backwards, the line shows up on startup configs, but not running configs
