https://wiki.netyce.com/ 2026-05-07T02:31:11+00:00 https://wiki.netyce.com/ https://wiki.netyce.com/lib/exe/fetch.php?media=wiki:logo.png text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:compliance:cmpl_fields&rev=1720009873&do=diff Policies, rules & conditions Policies A policy is coupled to a number of node groups. Whenever a node is checked for compliance, we therefore first check its node groups, and then all policies coupled to those node groups, and all those policies get validated on this node. A policy has the following attributes: text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:compliance:cmpl_multiconfig&rev=1720009873&do=diff Multiconfig compliance The Multiconfig compliance is intended for a group of two to four nodes, whose configuration needs to be equal at all times. The Multiconfig compliance uses it own Rule types as they will compare the node's new config to each of the current configs in its node group. A number of restrictions apply: text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:compliance:cmpl_parsing&rev=1720009873&do=diff Config blocks In order to parse parts of a config, configs are split up into blocks. Conditions with the type ConfigBlock will then parse against these blocks. These blocks can be selected by the Rule_start and Rule_end properties of the rule. These string can also be regular expressions. If multiple blocks match, all of them will be evaluated for compliance. Rule_start will match the first line of the block. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:compliance:cmpl_signalling&rev=1720009873&do=diff Compliance signalling Signalling A compliance check can have one of the following results: * A compliant node becomes non compliant * A non-compliant node becomes compliant * A non-compliant node stays non-compliant * A compliant node stays compliant text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:compliance:cmpl_xch&rev=1720009873&do=diff Compliance XCH API At the moment we support four different API calls for NCCM and compliance: * nccm_run: force an NCCM poll * nccm_submit: Push a configuration to the NCCM * cmpl_run: force a compliance check * cmpl_report: retrieve a report for compliance on a policy, node group, shown per policy or per node text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:compliance:compliance&rev=1720009873&do=diff Compliance reference Policies, Rules and Conditions Main article Policies, rules & conditions Config blocks Main article Config blocks Signaling Main article Compliance signaling XCH API commands Main article Compliance XCH API commands Multiconfig Compliance Main article Multiconfig compliance The NCCMD Daemon Main article The NCCMD Daemon Compliance Scenarios text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:compliance:compliance_scenarios&rev=1720009873&do=diff Compliance scenarios This is an overview of the four main scenarios for netYCE compliance: through polling groups, a config change, through the xch API and multiconfig compliancy. The purpose of this page is to give an overview from start to finish of the whole compliance process. text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:compliance:nccmd_daemon&rev=1720009873&do=diff The NCCMD Daemon The yce_nccmd daemon is responsible for handling both the NCCM and Compliance. It works in cycles of 5 minutes, spawning child processes who handle the bulk of its work and finishing when done. It supports multiple servers, so you can have multiple daemons running on different servers and they will not interfere (though only one master daemon can run per server).