I have four processes that are "Never started". Of these, UTMajorAcquisition and DeviceDiscovery surely should not have been, since Data Collection and User Tracking Acquisition have been running successfully every night.
14. DeviceDiscovery Never started 0 0 0 N/A Not applicable
18. EDS-TR Never started 0 0 0 N/A Not applicable
22. FDRewinder Never started 0 0 0 N/A Not applicable
40. UTMajorAcquisition Never started 0 0 0 N/A Not applicable
A second concern is, one of the cat6k running CatOS started failing in the Inventory Collection job (as well as the Inventory Polling job it spawned in turn) scheduled via RME - Admin - Inventory - System Job Schedule:
RICS0001:Internal Error,unable to process the collected data from the device.
Yes. Device Discovery's only purpose is to add devices to DCR. It is not required to put devices on the Topology Map or perform User Tracking acquisitions.
DeviceDiscovery is a transient process which means its healthy states are "Program started - No mgt msgs received", "Transient terminated", or "Never started".
EDS-TR should never be running. It is unused, and will be removed in a future release.
FDRewinder is used to aid in the rotation of daemons.log. It is also a transient, and its healthy states are "Program started - No mgt msgs received", "Administrator has shut down this server", or "Never started".
UTMajorAcquisition is also a transient just like DeviceDiscovery.
If these processes are never started, that means dmgtd has since been restarted.
The RICS0001 error could be related to a known inventory collection bug that affects a lrge number of devices (CSCse52700). A patch is available by calling the TAC, and referencing this bug. However, before a conclusion can be drawn, the IC_Server.log must be collected to confirm that this is the correct bug.