Page History

...

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

...

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

...

          Flow: Xconf-server -> DCM -> Upload repository -> create ->save
          Name: <Unique Identifier>
          Description: <Unique Identifier>
          URL:  HTTP HTTPS: httphttps://35xconf.161rdkcentral.239.220com/xconf/telemetry_uploadlogupload.php

• Defining the formula

...

• Remove already existing DCM Settings config files under /tmp
             rm -rf /tmp/DCM*
• Restart the log upload service in Raspberry Pi using the command
            systemctl restart CcspTelemetry.service
            root@RaspberryPi-Gateway:~# systemctl restart CcspTelemetry.service
• Verify through CURL command
             curl -i 'https://xconf.rdkcentral.com:909219092/loguploader/getSettings?estbIP=<IP ADDRESS>'
             or
             curl -i 'https://xconf.rdkcentral.com:909219092/loguploader/getSettings?estbMacAddress=<MAC-Address>'

...

• The permanent profile must have the below entries
  • Name of the RPI device profile
  • Upload Repository (HTTP/TFTP, HTTP : httpHTTPS)(HTTPS:https://35xconf.161rdkcentral.239.220com/xconf/telemetry_upload.php)
  • Telemetry profile Entries(We can add multiple telemetry profiles using “+” button.
  • In the Telemetry Permanent Profile page, there will be a 5th column that allows a component name to be entered. The component name is optional and may be present for only some of the entries in the Telemetry profile.

...

• 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:909219092/loguploader/getSettings?estbMacAddress=<MAC-Address>'

...

• Logs and Telemetry markers are uploaded via HTTP HTTPS to the xconf server https://xconf.rdkcentral.com/xconf/upload/ (To view the page : https://xconf.rdkcentral.com/xconf/upload/display.php)
• 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

...

• Configure the below 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:909219092/loguploader/getSettings
  DCM_SCP_SERVER=xconf.rdkcentral.com
  DCM_LA_SERVER_URL=https://xconf.rdkcentral.com/xconf/logupload.php

...

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.0.1
3. dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.ConfigURL string https://xconf.rdkcentral.com:909219092/loguploader/getT2Settings
4. touch /nvram/enable_t2_debug
5. reboot the device
6. pidof "telemetry2_0" - check the running status of telemetry2
7. T2 DataModel will be loaded

...

• Telemetry Profiles
  Sample SingleTelemetryProfiles
  https://xconf.rdkcentral.com:909219092/loguploader/getTelemetryProfiles?estbMacAddress=B8:27:EB:22:16:36

...

• Verification via curl command
  curl -i 'https://xconf.rdkcentral.com:909219092/loguploader/getTelemetryProfiles?estbMacAddress=B8:27:EB:22:16:36'

Note : For T2 the profile validation using dmcli is available at the moment , For Configuring T2 profiles in XCONF UI ,webconfig support is mandatory.

Feature Validation: Remote Feature Control (RFC)

Note : For RFC Validation Webconfig cloud server support is needed ,Below details includes Client and Xconf Server side configurations only.

• Configuration In RPI
  configure the xconf server URL in below path
   File: /etc/rfc.properties     
   URL : RFC_CONFIG_SERVER_URL=https://xconf.rdkcentral.com:909219092/featureControl/getSettings

...

• Verification through Curl command
  Restart the rfc service: systemctl restart rfc.service
  curl -i 'http://<IP>:909219092/featureControl/getSettings?estbMacAddress=<MAC-Address>&model=RDKB_RPI’

...

• Pre-requisite
  • Access to Raspberry Pi terminal.
  • Locally installed HTTP/TFTP Server.
  • Access to Xconf server from browser https://xconf.rdkcentral.com:909319093/admin/

• TFTP Server Setup
  STEP 1:
  Install xinetd and tftpd-hpa application in your local PC to setup tftp server by using below command
  sudo apt-get install xinetd
  sudo apt-get install tftpd-hpa

...

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

...

• Change the Contents of /etc/dcm.properties File
  LOG_SERVER=xconf.rdkcentral.com
  DCM_LOG_SERVER=https://xconf.rdkcentral.com/xconf/logupload.php
  DCM_LOG_SERVER_URL=https://xconf.rdkcentral.com:909219092/loguploader/getSettings
  DCM_SCP_SERVER=xconf.rdkcentral.com
  DCM_LA_SERVER_URL=https://xconf.rdkcentral.com/xconf/logupload.php

...