...
/pingrequest done by nim to verify connectivity for the latest DPC (testing of older DPCs is never traced). Packet capture is also enabled and the obtained pcap files are included in the published netdumps. To limit the overhead associated with tracing and packet capture, nim is only allowed to enable them and produce netdump at most once per day (configurable bynetdump.topic.publishpostonboard.interval). However, before device is fully onboarded this interval is lowered to one netdump per hour a much lower interval configured bynetdump.topic.preonboard.interval(by default one hour) is applied to get more frequent diagnostics for initial connectivity troubleshooting./configand/inforequests done by zedagent to obtain device configuration and publish info messages, respectively. Packet capture is not enabled in this case. Follows the same interval as given bynetdump.topic.publishpostonboard.interval. For/inforequests, tracing only covers publication of theZInfoDevicemessage. Moreover, tracing is enabled only if the highest priority DPC is currently being applied and is reported by nim as working. Otherwise, we will eventually getnim-fail*netdump which should be sufficient for connectivity troubleshooting. The purpose of zedagent netdumps is to debug issues specific to/configan/inforequests (which are essential to keep the device remotely manageable). Netdumps are published separately into topicszedagent-config-<ok|fail>andzedagent-info-<ok|fail>.- every download request performed by downloader using the HTTP protocol is traced and netdump is published into the topic
downloader-okordownloader-fail, depending on the outcome of the download process. By default, this does not include packet captures. However, a limited PCAP can be enabled with config optionnetdump.downloader.with.pcap. Limited in the sense that it will not include TCP segments carrying non-empty payload (i.e. packets with the downloaded data). The total PCAP size is also limited to 64MB (packets past this limit will not be included).
...