When we add or remove a Network Object from a Cisco ASA, the NCM Daily Config Change Report grows very long.
This is apparently due to the ASA removing or inserting that Network Object, and NCM seeing subsequent lower lines shifting up or down by as many rows as there are new or removed Network Objects. Here's an example:
- Add a new network object at the top right.
- All following Network Objects shift down one row
- NCM sees a Network Object on a line on the left go missing on the right, and lists this as a change--something was removed.
- But that Network Object was simply shifted down one line. Now NCM sees it as a newly added line and Network Object and reports on it.
- This extended all the way down through a long ASA configuration--all the Network Objects move down (or up) a row, resulting in a very large Configuration Change Report.
Is there a way to prevent this activity so NCM only reports on the actual changed item, and is not fooled into thinking multiple items have changed simply because they won't show up in the same row that they were in previously?