23.4 - Data to capture when there is a discrepancy in polled data using mcs with a robot
search cancel

23.4 - Data to capture when there is a discrepancy in polled data using mcs with a robot

book

Article ID: 279222

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

A robot that is still sending QOS data after all mcs profiles are removed from it, or new profiles, and that data is not reflected in Operator Console. What log data can be reviewed to understand the issue?

Environment

Version: 23.4
Component: mcs

Resolution

1. On the robot we need to raw config the spooler and set:

debug=5
logsize=20000 (this will likely need to be added)

2. Run the ‘metric_plugin_get_profile_policy_checksums’ against the spooler on the problem robot and capture the output

3. Raw configure the configuration_reader_service on the hub that it reports to and set the follow under setup

dumpDataFromRobot=true
loglevel=5
logsize=20000

Note: Allow this to run for about 15 minutes

4. Capture the following data for support, after the 15 minutes:

(from the problem robot)
- output of the metric_plugin_get_profile_policy_checksums callback
- cdm.cfg
- complete ..nimsoft/plugins directory and contents
- _spooler.log, spooler.log, spooler.cfg (from the robot directory)

(from the hub it reports to)
- _configuration_reader_service.log, configuration_reader_service.log, configuration_reader_service.cfg
- ..configuration_reader_service/robot_logs/<deviceid>_req.txt
- ..configuration_reader_service/robot_logs/<deviceid>_resp