IDP Processes Reference
Specific IDP processes generate error messages. Knowing the process that encountered the error can often help you isolate and resolve the issue.
Table 1 provides a reference of IDP processes.
Table 1: Troubleshooting: IDP Processes Reference
Process | Function |
|---|---|
agent | Establishes the Transport Layer Security (TLS) channel to Network and Security Manager (NSM). Sends IDP status, logs, and profiled data to NSM. Receives policy, detector, and configuration commands from NSM. |
idpengine | The core IDP engine. |
idpHMD | Generates SNMP alerts when thresholds are crossed for tracked resources on the device. Responds to SNMP poll requests. Resources are CPU, memory, hard disk space, and session count. |
idpLogReader | Reads IDP logs and writes them to local hard disk. |
nicBypass | Controls the internal bypass feature. |
peerPortModulator | Controls peer port modulation. |
pkid | Inspects SSL traffic, if SSL inspection is turned on. |
profiler | Profiles network and application data collected by the device. |
recover.sh | Used in the auto-recovery process. |
schad | Performs load balancing and failover between sensors in a high availability (HA) configuration. IDP 4.2 does not support HA. |
sciod | Handles policy push, information retrieval, Profiler status, and so on. |
sessionFetcher | When packet logging is enabled, retrieves session data and sends it to NSM. |
slogd | Logs packet captures to the IDP hard disk. |
![]() | Note: You can use the Linux ps commands to display the process ID and other status information about IDP processes. |


