ZTP Event Tracker

The ZTP Event Tracker provides a centralized view for monitoring and tracking ZTP-related syslogs received from DHCP servers. It helps administrators follow the complete lifecycle of a Zero Touch Provisioning (ZTP) event—from the moment a syslog is received through discovery, configuration download, and the creation of an upload job.

This module acts as a traceability and troubleshooting layer for ZTP, enabling users to identify where a syslog currently resides in the processing pipeline and quickly detect failures or duplicate events.

The ZTP Event Tracker is available only when:

• The ZERO_TOUCH_PROVISIONING license is enabled, and

• The Infraon_NCCM feature flag is active.

How It Works

1. A DHCP server sends a ZTP-related syslog to the Infraon Data Collector.

2. Syslog messages are ingested into Kafka and assigned a unique Track ID.

3. The syslog progresses through multiple internal processing stages:

• Event ingestion

• Trigger processing

• Discovery creation

• Download job handling

• Upload job creation

1. Each stage updates the Status of the syslog in real time.

2. If a failure occurs at any stage, the error is captured and displayed in the tracker.

3. On successful completion, the tracker confirms whether:

• A discovery job was completed, and

• A download/upload job was created or already existed.

This visibility allows administrators to validate ZTP behavior, diagnose failures, and confirm automation outcomes without switching across modules.

ZTP Processing Status

As a syslog moves through the ZTP pipeline, the Status field is updated sequentially to reflect its current processing stage. Common statuses include:

ZTP Event | State | Status

Status	State	Description
Received in Kafka	Not Started	The ZTP syslog message is received from the DHCP server and successfully ingested into Kafka via the data collector. This is the initial state of ZTP event tracking.
Sent To Event	Not Started	The syslog event is forwarded from Kafka to the event consumer for further ZTP processing.
Received In Trigger	Not Started	The event consumer passes the syslog to the trigger service, where ZTP workflow validation begins.
Sent To Discovery Celery	Not Started	The trigger service sends the ZTP event to the discovery celery worker for device discovery processing.
Processing Discovery Request	In Progress	The discovery celery worker is actively processing the ZTP request to identify the device and validate discovery prerequisites.
Discovery Configuration Added	In Progress	The discovery configuration for the identified device is created or mapped during the ZTP workflow.
Discovery Job Added	In Progress	A discovery job is created and queued for execution on the agent for the detected device.
Discovery Completed	Completed	The discovery job execution is completed successfully, and the device is discovered as part of the ZTP process.
Download Job Already Exist	In Progress	A configuration or image download job already exists for the detected device, so no new job is created.
Download Job Created	In Progress	A new download job is created for the device during ZTP onboarding.
Added Download Job To Agent	In Progress	The download job is successfully assigned to the agent for execution on the device.
Adding Upload Job	In Progress	The system is creating an upload job to collect configuration or operational data from the device after discovery.
Upload Job Created	Completed	The upload job is successfully created and linked to the ZTP workflow.
Upload Job Created	Completed	The ZTP workflow completes after a successful upload job is created.
Error (Hover Details)	Error	If an error occurs at any stage of the ZTP workflow, an error icon is displayed. Hovering over the icon shows the available error details.

What You See on the Screen

The ZTP Event Tracker page provides a single consolidated view to monitor, track, and control the lifecycle of ZTP syslog events received from DHCP servers.**Syslog Events |**Basic Details

Label	Action	Description / Example
Search	Filter	Allows users to filter ZTP events based on selected columns and conditions (in, not in, equal, not equal, contains).Fields: Track ID, Syslog, DHCP Server ID, Status, Device IP Address, Reference Key, and State.
Track ID	View	Unique identifier generated for each ZTP syslog event. Used to trace the full ZTP workflow across stages. Example: 257ea3f5b77c49b...
Syslog	View	Displays the raw syslog message received from the DHCP server, including DHCPACK details. Example: DHCPACK on 192.168.50.14 to bd:f8:f2:0d:c5:cf via 10.0.4.1
Received Time	View	Timestamp indicating when the syslog was received by the data collector. Example: Oct 30, 2025 03:42 PM
DHCP Server IP	View	IP address of the DHCP server from which the syslog was received. Example: 10.0.4.88
Data Collector	View	Shows the data collector (agent) that ingested the syslog event. Example: Test – 10.0.4.88
State	View	Represents the high-level execution state of the ZTP process. Example: Not Started, Completed
Status	View	Indicates the current processing stage of the ZTP workflow. Example: Sent To Event, Upload Job Created, Discovery Completed
Device IP Address	View	IP address assigned to the device through ZTP DHCP process. Example: 192.168.50.14
Reference Key	View	Device identifier (typically MAC address) used to correlate the ZTP event. Example: bd:f8:f2:0d:c5:cf
Last Update Time	View	Timestamp of the most recent status update for the ZTP event. Example: Oct 30, 2025 03:42 PM
Export	Action	Exports the ZTP Event Tracker data to an XLSX file for analysis or audit purposes.
Re-Initiate	Action	Re-triggers the ZTP process from the beginning for the selected event, subject to permissions and status conditions. Example: Restart ZTP when the process stops due to an error or exceeds the configured delta time.

ZTP Syslog Re-Trigger

The Re-Initiate action allows authorized users to manually restart the ZTP workflow for a selected syslog event when reprocessing is required.

Availability

• Visible only to users with Edit permission for the ZTP license.

• Not available when the status is Upload Job Created or Download Job Already Exist.

When It Is Enabled

• The ZTP process stopped due to an error.

• The Last Update Time exceeds the configured delta interval (ZTP_RE_TRIGGER_DELTA_INTERVAL).

• The event is in an intermediate or failed state.

Execution

• Clicking Re-Initiate opens a confirmation dialog.

• On confirmation, the ZTP process restarts from the beginning.

• Each action is captured in the audit log.

How It Works

When a ZTP-related syslog is received, the system tracks its progress through each processing stage. If the workflow fails or becomes inactive beyond the configured threshold, the Re-Initiate option becomes available.

Triggering this action re-queues the event and restarts the ZTP process from the initial stage, enabling recovery without waiting for a new syslog.