NCM Summary Reports and "As of Last Update"

shawn_b

Looking at the NCM Config summary page there are some default charts that show config comparison summary info, for example

Overall Running vs. Startup Conflicts

Overall Baseline vs Running Config Conflicts

I am not sure if these reports are accurate

I am seeing "As of Last Update" as one of the options

what exactly does As of Last Update mean?

I am trying to figure out how this works, since some of the nodes that show up in the conflicted baseline vs running config report, have the latest running config backed up and set to baseline

Admin_Storage_1

Admin1_3

shawn_b

So I did some further digging around on this and have discovered that I had the following issues:

1. Not having a running-config newer than the baseline config for comparison

observe the node Dis_Recov_1 is listed in the Overall baseline vs Running Config conflicts

Looking at the configs for this node, the baseline config was the most recent running-config

download a new running config for this node (running config is same as baseline). The lastest running config is NOT marked as the baseline

now the node shows up in the No Conflict list

2. DELL PowerConnect 6200 series switches change SFlow receiver timeout values on their own, so while configs are essentially the same, the actual line is different between configs, which would cause a comparison difference,. As jeff.stewart‌ suggested, an ignore rule has to be configured to ignore this line. I have several of these and they are all showing as conflicts.

This does not happen on DELL PCT 7000 and N series, since you can use "no timeout" in the config

in the following screenshot, the left is the baseline and the right is the running config. this is the only conflict as all else is the same. the timeout value was NOT manually changed, the switch OS did that.

I was able to clear al nodes in the Unknown list and reduce the number of nodes in the Conflict list