Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NCM: What is Compliance Attributed Test in NCM. How is the generated Results set evaluated. (304697)

Last Updated: 5/29/2020Categories: How toTotal Views: 2303Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

What is the Compliance Attributed Test in NCM and How do you evaluate the generated Result set .

The Compliance Attributed Test is based on the concept of running a Query to generate a Result Set, and then using various sets of rules to validate that the Result Set is compliant.

An Attributed Compliance Test is comprised of one or more Queries. There is one distinguished Query, called the Primary Query, which generates a (Primary) Result View that is to be tested. The testing is done by applying sets of Rules against the Primary Result View to see if the contents of the Primary Result View are valid.

There are (currently) three types of rules that are used to evaluate the content of the Results Set:

Must Contain Rules: these rules are a template of rows that must appear in the result set. The template is arranged in a spreadsheet-like display, and includes selected columns from the Query s Result Set. The non-null columns of each row in the Must Contain Rules specify a row that must appear in the Primary Result Set.

Must Not Contain Rules: similar to Must Contain Rules, the non-null columns of each row in the Must Not Contain Rules specify a row that must not appear in the Primary Result Set.

Match Each Row Rules: define a boolean expression, consisting of a set of boolean tests that must be matched by every row in the result set.

Additional Queries (other than the Primary Query) may optionally be added to the Attributed Compliance Test in order to generate variable values. Variable references can then be inserted into the rules or Primary Query, allowing values from the results of other Queries to be checked against the Primary Result Set.

Must Contain rules should be used to specify a list of things that need to be configured on the Device. For example, it might be a list of access-lists that need to be present on each Device. You can specify that the rules must be matched in order with the result set

Must Not Contain rules should be used to specify items that should not be configured on the Device. For example, you may want to check that no access-list has a  permit any  rule.

Match Each Row rules should be used to check that the configuration of several different items matches preset criteria; for example that all the Ospf areas are configured with the same set of parameters, or that all OspfRouterSettings have a consistent set of options enabled

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant