Introduction

RDKB Telemetry Components

1. Xconf Server
2. RPI with rdkb image

Environment Setup

2.1.  Build procedure

Follow the wiki page to make yocto's RDK-B image from yocto workspace in your PC.

RDK-B R-Pi Yocto 3.1 - Dunfell

Note: Proceed the build procedure in Ubuntu18 version VM

2.2.  Pre- requisites for enabling Telemetry2_0

1. dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.Enable bool true
2. dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.Version string 2
3. dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.ConfigURL string https://xconf.rdkcentral.com:9092/loguploader/getT2Settings
4. touch /nvram/enable_t2_debug
5. reboot the device
6. pidof "telemetry2_0"

 Xconf server

• Xconf server page :  https://xconf.rdkcentral.com:9093/admin/ux/

Configuring Telemetry on Xconf server

Change Application to stb in top right corner of the window

Create Formula

 Login to Xconf Server and go to DCM menu item and click on “Formulas” sub menu and create Formula

Create Device Settings

Xconf Server → DCM → Device Settings 

Create LogUpload Settings

Xconf Server → DCM → LogUpload Settings

 Create Upload Repository

Xconf Server → DCM → Upload Repository

Upload Repository : HTTP Server

Repository URL:  http://35.155.171.121/xconf/logupload.php

Test Page

Xconf Server → DCM → Test Page

In the Test Page, give estbMacAddress(D8:58:D7:00:A5:D6 → Mac Address of Turris Omnia) and ensure the parameters that has been configured in the DCM.

Create Permanent Profiles

Xconf Server → Telemetry → Permanent Profiles

Create Targeting Rules

Xconf Server → Telemetry → Targeting Rules

Test Page

Xconf Server → Telemetry → Test page

In the Test Page, give estbMacAddress(D8:58:D7:00:A5:D6 → Mac Address of Turris Omnia) 

JSON Response

http://35.155.171.121:9092/loguploader/getSettings?estbMacAddress=D8:58:D7:00:A5:D6&model=Turris

Configuring Telemetry on Turris Omnia

• Once the board is up , go to /etc/dcm.properties and add the below detail

DCM_LOG_SERVER_URL=http://35.155.171.121:9092/loguploader/getSettings
DCM_HTTP_SERVER_URL=http://35.155.171.121/xconf/telemetry_upload.php
DCM_LA_SERVER_URL=http://35.155.171.121/xconf/logupload.php

• After board boot up, disable log rotation by using the command: 

$ systemctl disable rdkbLogMonitor

1. Restart the dcm-log service using “systemctl restart dcm-log”
2. To check the status of the service “systemctl status dcm-log”
3. By triggering the service , Turris-Omnia starts uploading the logs to the xconf-server
4. The log upload and Telemetry markers can be uploaded via http
5. The profile can be verified using curl, conf file , through logs and in server as below

Curl Response

Execute the following command in turris board, and ensure the output

$ curl 'http://35.155.171.121:9092/loguploader/getSettings?estbMacAddress=D8:58:D7:00:A5:D6&model=Turris'

 Configuration file

• Once the profile details are successfully retrieved , the conf file will be created under /tmp which has the server configurations 

Log File

$ cat /rdklogs/logs/telemetry.log

$ cat /rdklogs/logs/dcmscript.log

$ cat /rdklogs/logs/dcmProcessing.log

Log upload onto HTTP Server

Verify that Json file and zipped log files for all other logs displayed in HTTP server → http://35.155.171.121/xconf/upload/

JSON file upload

• open the uploaded json file and ensure the parameters

http://35.155.171.121/xconf/upload/D858D700A5D6_TELE_11-30-2020-12-31PM.json

Log Upload

Ensure all the log files present in the zipped file

Known Issues/ Limitations

1. Yet to have TFTP server support for log upload
2. Using dmcli command to fetch the IP address, its retrieving in reverse format → for this hal api should be updated
3. Cron job support to be done