guides:user:nccm:overview
LDAP: couldn't connect to LDAP server
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
guides:user:nccm:overview [2020/03/17 20:30] – yspeerte | guides:user:nccm:overview [2020/05/25 13:18] (current) – [NCCM Overview] pgels | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{indexmenu_n> | ||
+ | |||
+ | ====== NCCM Overview ====== | ||
+ | |||
+ | NCCM is a Network Management term that refers to configuration backups and stands for //" | ||
+ | |||
+ | Additionally, | ||
+ | |||
+ | The NCCM can retrieve the configuration from the device when: | ||
+ | |||
+ | * A NetYCE job changes the configuration. Every job will retrieve the configuration before and after the change. Both configurations will be incorporated in the NCCM history of that device. | ||
+ | * The device sends a syslog message to the NetYCE server to inform of a configuration change. The configuration is then retrieved and appended to the NCCM history. | ||
+ | * The device is scheduled to have its configuration periodically fetched by the NCCM poller. | ||
+ | |||
+ | |||
+ | An operational NCCM is a prerequisite to use the NetYCE Compliance. Only devices with at least one entry in the NCCM can be validated using Compliance Policies. Please refer to the [[guides: | ||
+ | |||
+ | NetYCE refers to the NCCM as a repository of all historic configurations of a device within the time and storage limits set on it. To permit effective storage of this potentially vast amount of data a schema is used to store only occasionally the full configuration text and for each subsequent configuration only the differences. A set of policies control how often these base configurations must be made and how large the resulting differences. | ||
+ | |||
+ | The resulting schema allows for very fast retrieval of any configuration at a given time and being able to compare the differences between any two points in time. De default history of the NCCM is set at 800 days. | ||
+ | |||
+ | For details on the NCCM policies and settings, please refer to the [[guides: | ||
+ | |||
+ | Any historic configuration in the NCCM, or the very latest, can be restored to the device using jobs or manual download. | ||
+ | |||
+ | |||
+ | ===== NCCM setup ===== | ||
+ | |||
+ | The NCCM can only work with configured nodes (devices) in NetYCE. There are two types of nodes it can work with. | ||
+ | |||
+ | Firstly the fully modelled NetYCE nodes that are created using Service-types based on Node-types, normally referred to as //" | ||
+ | |||
+ | Secondly nodes that are defined in the NetYCE CMDB, normally referred to as //" | ||
+ | |||
+ | |||
+ | ===== Polling Groups ===== | ||
+ | |||
+ | The NCCM uses " | ||
+ | |||
+ | By entering node-names or node-name wildcards all matching nodes can be assigned directly the the Polling Group. And unwanted nodes can simply be removed from the list. | ||
+ | |||
+ | The " | ||
+ | |||
+ | To achieve the dynamic inclusion of nodes in a Polling Group, its type must be set to "Node groups" | ||
+ | |||
+ | |||
+ | ===== Prerequisites ===== | ||
+ | |||
+ | Both the CMDB-nodes and the YCE-nodes rely on a " | ||
+ | |||
+ | Additionally the CMDB-nodes need to have a valid IP-address to the node. This can be an IPv4, IPv6 or a FQDN (full-qualified domain name) that is DNS resolvable. For the YCE-nodes usually both are available. | ||
+ | |||
+ | The configuration is retrieved using the NetYCE vendor modules. The Vendor_type set in the YCE-node or CMDB-node must match that of the device and must be a supported vendor module. Mismatches will cause the sessions to fail. | ||
+ | |||
+ | As syslog messages from devices might not have their hostname included in the message, a means to resolve the included IP-address in its fqdn or hostname is then required. NetYCE NCCM relies on the reverse lookup capabilities of the resident DNS to provide the fqdn. When needed the ''/ | ||
+ | |||
+ | To retrieve the configuration from the device the file is pushed (uploaded) from the device to the NetYCE server. The transfer method selected is dependent on the vendor-type and can be modified using the "Admin - Custom data" tool for the YCE table " | ||
+ | |||
+ | |||