Page History

Table of Contents

...

printable

...

false

Pre-requisite

• Access to Raspberry Pi terminal.
• Access to Xconf server from browser https://xconf.rdkcentral.com:9093/admin/ 
  • For Admin mode(read and writ permission) -> username : admin, password: RdkXcadm$2120
  • For User mode(only read mode) -> username: user ,password: RdkXcusr@2210          

...

• In Raspberry Board, add the server details for log upload.
• Configure the Bellow details to dcm.properties and comment out the other details .

            File :  /etc/dcm.properties

           LOG_SERVER=xconf.rdkcentral.com
           DCM_LOG_SERVER=https://xconf.rdkcentral.com/xconf/logupload.php
           DCM_LOG_SERVER_URL=https://xconf.rdkcentral.com:9092/loguploader/getSettings
           DCM_SCP_SERVER=xconf.rdkcentral.com
           DCM_LA_SERVER_URL=https://xconf.rdkcentral.com/xconf/logupload.php

...

           Flow: Xconf-server -> DCM -> Formulas -> Create
           Name: <unique name for log upload>
           Description: <Short description for log upload>
           Percentage: 100
           Build condition:  estbMacAddress IS <MAC Address> OR estbIP IS <IP Address> 
                                    (or)  estbMacAddress IS <MAC Address>  AND model is <Model Name>   (Model name is already configured under Common Tab)

           Image Modified

• As soon as the formula is saved, then a ‘define Settings’ ‘define Settings’ tab with ‘Create ‘Create Device Settings’Settings’, ‘Create ‘Create log settings’settings’, Create VOD settings’ settings’ will be available.

...

• Verify the logs in /rdklogs/logs/dcmscript.log file
• The log file contains the details of
  • Service status, tftp details, reboot flag , check on reboot flag ,
  • Upload settings details – location, protocol.
• Shows list of files which are to be uploaded to the server as a tar file (logs will be zipped and creates a tar file on every bootup/service restart), Backup folder details (/rdklogs/logs/PreviousLogs_backup)
• HTTP request processing status.   
• Log files are stored in .tgz format and markers are stored in <mac_address>-TELE-<date>.json

• Json response on server

...

• Telemetry configuration can be done by adding a permanent profile which contains below objects
  • Upload repository
  • Profile options (Header, content, frequency etc.)
• Creating a targeting rule which is basically mapping the profile to a set of MAC/IP/Device etc
• Note: DCM settings should be already done for the devices that you are going to set telemetry configuration.

...

• Verification via curl command
  The same url used for logupload verification can be used here too, the response will have telemetry settings data like below (urn:settings:TelemetryProfile)   
  curl -i 'https://xconf.rdkcentral.com:9092/loguploader/getSettings?estbMacAddress=<MAC-Address>'

...

         Sample Output

...

• Logs and Telemetry markers are uploaded via HTTP to the xconf server https://xconf.rdkcentral.com/xconf/upload/
• Log files are stored in .tgz format and markers are stored in <mac_address>-TELE-<date>.json

• Sample Log is as below

  root@RaspberryPi-Gateway:/rdklogs/logs# root@RaspberryPi-Gateway:/rdklogs/logs# tail -f telemetry.log 211110-06:10:14.269011 dca: Using Direct commnication •    Sample number of proUPdel1:42 Upload protocol telemetry is:HTTP before HTTP upload number of httpdeli:42 HTTPTELEMETRYURL:http://35.161.239.220/xconf/telemetry_upload.php ------CURL_CMD:curl --tlsv1.2 -w '%{http_code}\n' -H "Accept: application/json" -H "Content-type: application/json" -X POST -d @/nvram/rtl_json.txt 'http://35.161.239.220/xconf/telemetry_upload.php' --connect-timeout 30 -m 30 number of proUPdel2:42 Upload protocol logupload is:HTTP before HTTP log upload HTTPLOGUPLOADURL:http://35.161.239.220/xconf/logupload.php upload log file is:11-10-21-06-08AM.tgz ------CURL_CMD2:curl -w '%{http_code}\n' -F filename=@/rdklogs/logs//PreviousLogs/B8:27:EB:22:16:36-Logs-11-10-21-06-08AM.tgz 'http://35.161.239.220/xconf/logupload.php' --connect-timeout 100 -m 100 http code in telemetry is :200 HTTP telemetry curl upload succeded!!!!!!!!!!!!!!!!! http_code is :200 HTTP log upload succeded!!!!!!!!!!!!!!!!! number of proUPdel2:42 Upload protocol logupload is:HTTP before HTTP log upload HTTPLOGUPLOADURL:http://35.161.239.220/xconf/logupload.php upload log file is:11-10-21-06-08AM.tgz ------CURL_CMD2:curl -w '%{http_code}\n' -F filename=@/rdklogs/logs//PreviousLogs/B8:27:EB:22:16:36-Logs-11-10-21-06-08AM.tgz 'http://35.161.239.220/xconf/logupload.php' --connect-timeout 100 -m 100 http_code is :200 HTTP log upload succeded!!!!!!!!!!!!!!!!! Done Uploading Logs and removing rtl_json.txt file Done Uploading Logs and removing rtl_json.txt file

• Telemetry Log Markers

...

• DMCLI SET Command for T2 Report Profile

• DMCLI GET

• Telemetry 2.0 Report Profiles Generation in xconf,
  Flow: xconf Server UI -> Telemetry -> Telemetry 2.0 Profiles -> create

...

• • Copy both (image as well as the checksum) to tftp server
    for Ex:
    md5sum "rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic" >rdkb-generic-broadband-image_rdk-next_20211118174413.txt
    cp -r rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic  rdkb-generic-broadband-image_rdk-next_20211118174413.txt  /home/xyz/tftphome

Xconf Server UI Configurations

• Create Model
  Flow: Xconf-Server ->Common ->Models
  Give ID and Description to setup Model for your device and save that details in xconf server.

• Create MAC List
  Flow: Xconf-Server->Common->MAC Lists
  After entered MAC Lists page press create button to add your device MAC detail and save the details.

...

• Verification of Firmware test page
  Flow : Xconf-server -> Firmware -> Test Page
  Parameters : eStbMac <MAC-Address>

• Client end Configurations and verification (in RPI)
  Change the CLOUDURL URL in /etc/include.properties File
  CLOUDURL=https://xconf.rdkcentral.com:9092/xconf/swu/stb?eStbMac=

...