NCM resources should support filtering (SQL)

We have an issue regarding the "Overall Running vs. Startup Config Conflicts" resource. All JUNOS devices (Since JUNOS doesn't support running and startup config) are being displayed as unknown. This issue has been known for quite some time and yet no action has been taken.

Suggested solution: JUNOS devices can be discarded with filtering the resource as shown below. Also it is a good idea to support "Filter Nodes (SQL)" all the other resources in NCM.

Find more posts tagged with

filter

support

sql

ncm

resource

Status: None

Comments

ctopaloglu

Also NCM resources should have "Auto-Hide resource" option. For example some switches don't have policies on them. But the resource is displayed anyway.

FormerMember

This should be standardized across all fields where we can Regex match. I am fine with using sql query structure but simple regex pattern matching is far more powerful. With a field drop down that you want to get granular on.

Currently NPM node management supports regex like nodename[125][1-9] etc. I love this idea but I would like to ensure criteria matching consistency across the WebUI

garystorr

At the top of this page it says this feature has been implemented? Could anyone advise what version this is in as im running NCM 7.3.2 and its not in there.

Thanks

cvachovecj

This was added in NCM 7.4. Mentioned e.g. here: Network Configuration Manager v7.4 Beta2 is Available!