cisco Model-Driven Telemetry — Prerequisites for Model-Driven Telemetry

ndbmand : Running pubd : Running gnmib : Running The process pubd is the model-driven telemetry process, and if it is not running, model-driven telemetry will not work. Note The following table provides details about each of the Device Management Interface (DMI) processes. Table 1: Field Descriptions NETCONF-Specific Prerequisites • Knowledge of NETCONF and how to use it, including: • Establishing a NETCONF session. • Sending and receiving hello and capabilities messages. • Sending and receiving YANG XML RPCs over the established NETCONF session. For more information, see the Configure NETCONF/YANG and Validate Example for Cisco IOS XE 16.x Platforms document.

Enabling and Validating NETCONF The NETCONF functionality can be verified by creating an SSH connection to the device using a valid username and password and receiving a hello message, which contains the capability of the device: Model-Driven Telemetry Prerequisites for Model-Driven Telemetry Device Management Interface Process Name Primary Role confd Configuration daemon. nesd Network element synchronizer daemon. syncfd Sync daemon (maintains synchronization between the running state and corresponding models). ncsshd NETCONF Secure Shell (SSH) daemon. dmiauthd DMI authentication daemon. nginx NGINX web server. Acts as a web server for RESTCONF. ndbmand NETCONF database manager.

pubd Publication manager and publisher used for model-driven telemetry. gnmib GNMI protocol server. Model-Driven Telemetry 2