You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

WIP

Intro

As a Field Triage Engineer and Developer responsible for debugging field issues, having the ability to collect diagnostic/ debug data from the device without requiring SSH access would be beneficial. The Triage Engineer can use WebPA communication to initiate the data reporting process and retrieve the report from the S3 log service

Architecture

Use case diagram

  • rdbg

Samples

  • Upload scripts location

    • /lib/rdk/uploadRRDLogs.sh
      /rdklogger/uploadRDKBLogs.sh
  • Report generation location

    • /tmp/rrd
  • Log files

    • /rdklogs/logs/remote-debugger.log.0 
  • static json file location

    • Path in CPE
         /etc/rrd/remote_debugger.json
      Path in code base
         https://github.com/rdkcentral/remote_debugger/blob/develop/remote_debugger.json
  • Datamodel command

    • dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.RDKRemoteDebugger.IssueType string "Device.Uptime"

Removed existing rdm in rdkb builds

  • meta-cmf/recipes-core/packagegroups/packagegroup-rdk-ccsp-broadband.bbappend # Comment out or remove the line: RDEPENDS_packagegroup-rdk-ccsp-broadband_append = " rdm"

Distro

  • rrd to be enabled

RFC

  • DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.RDKRemoteDebugger.Enable

Enable service from yocto

  • remote-debugger.service 

Image install

  • Install remote debugger & rdm-agent in monolithic image

Code base

Dependencies removal

  • remove utopia dependencies from remote debugger service file

Roles and responsibilities of ISP

  • Develop your own triaging tool on top of webpa/usp/tr69


  • No labels