Page History

...

• Json response on server

         Attaching sample file :  B8_27_EB_22_16_36-Logs-11-10-21-07-00AM.tgz

Feature Validation: Telemetry

• 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.

• Create a new Telemetry Profile.
  Flow: X-conf-server -> Telemetry -> Permanent Profiles -> Create button

           Image Removed

• Sample log

  root@RaspberryPi-Gateway:/rdklogs/logs# tail -f dcmscript.log & [1] 6839 root@RaspberryPi-Gateway:/rdklogs/logs#  Starting execution of DCMscript.sh TFTP_SERVER: xconf.rdkcentral.com Telemetry Profile File Being Used : /tmp/DCMSettings.conf 230411-07:01:54.887232 dca upload url from dcmresponse is https://xconf.rdkcentral.com/xconf/telemetry_upload.php Build Type: dev Log file: 04-11-23-07-01AM.tgz TFTP Server

  The permanent profile must have the below entries
• Name of the RPI device profile
Upload Repository (HTTP/TFTP, HTTPS)(HTTPS

: https://xconf.rdkcentral.com/xconf/

telemetry_upload

logupload.php Protocol: 0 UploadHttpLink: 0 The Previous Logs folder is missing 230411-07:01:55.237896 dca : Only Direct connection is available 230411-07:01:55.259956 dca: Sleeping for 9 before upload. Uploading Logs with DCM UploadOnReboot set to true Build Type: dev Log file: 04-11-23-07-01AM.tgz TFTP Server: https://xconf.rdkcentral.com/xconf/logupload.php Protocol: 0 UploadHttpLink: 0 Uploading Logs with DCM UploadOnReboot set to true 230411-07:02:05.562055 dca: Direct connection success - ret:0 230411-07:02:05.574482 dca: Json message successfully submitted. /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-ArmConsolelog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-BootTime.log /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-CRlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-Consolelog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-FirewallDebug.txt /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-LM.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-MnetDebug.txt /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-PAMlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-PARODUSlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-PSMlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-TDMlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-TR69log.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-WEBPAlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-WiFilog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-dcmscript.log /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-swupdate.log /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-02AM-version.txt 04-11-23-07-02AM-ArmConsolelog.txt.0 04-11-23-07-02AM-BootTime.log 04-11-23-07-02AM-CRlog.txt.0 04-11-23-07-02AM-Consolelog.txt.0 04-11-23-07-02AM-FirewallDebug.txt 04-11-23-07-02AM-LM.txt.0 04-11-23-07-02AM-MnetDebug.txt 04-11-23-07-02AM-PAMlog.txt.0 04-11-23-07-02AM-PARODUSlog.txt.0 04-11-23-07-02AM-PSMlog.txt.0 04-11-23-07-02AM-TDMlog.txt.0 04-11-23-07-02AM-TR69log.txt.0 04-11-23-07-02AM-WEBPAlog.txt.0 04-11-23-07-02AM-WiFilog.txt.0 04-11-23-07-02AM-dcmscript.log 04-11-23-07-02AM-swupdate.log 04-11-23-07-02AM-version.txt Uploading logs 04-11-23-07-01AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php tar: 04-11-23-07-01AM.tgz: file is the archive; skipping 04-11-23-07-02AM-ArmConsolelog.txt.0 04-11-23-07-02AM-BootTime.log 04-11-23-07-02AM-CRlog.txt.0 04-11-23-07-02AM-Consolelog.txt.0 04-11-23-07-02AM-FirewallDebug.txt 04-11-23-07-02AM-LM.txt.0 04-11-23-07-02AM-MnetDebug.txt 04-11-23-07-02AM-PAMlog.txt.0 04-11-23-07-02AM-PARODUSlog.txt.0 04-11-23-07-02AM-PSMlog.txt.0 04-11-23-07-02AM-TDMlog.txt.0 04-11-23-07-02AM-TR69log.txt.0 04-11-23-07-02AM-WEBPAlog.txt.0 04-11-23-07-02AM-WiFilog.txt.0 04-11-23-07-02AM-dcmscript.log 04-11-23-07-02AM-swupdate.log 04-11-23-07-02AM-version.txt Uploading logs 04-11-23-07-01AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php Moving to Previous Logs Backup Folder Moving to Previous Logs Backup Folder tail: dcmscript.log: file truncated Uploading Logs with DCM UploadOnReboot set to true Telemetry Profile File Being Used : /tmp/DCMSettings.conf 230411-07:05:11.424110 dca upload url from dcmresponse is https://xconf.rdkcentral.com/xconf/telemetry_upload.php Build Type: dev Log file: 04-11-23-07-05AM.tgz TFTP Server: https://xconf.rdkcentral.com/xconf/logupload.php Protocol: 0 UploadHttpLink: 0 230411-07:05:11.667428 dca : Only Direct connection is available 230411-07:05:11.685759 dca: Sleeping for 9 before upload. Uploading Logs with DCM UploadOnReboot set to true 230411-07:05:22.145133 dca: Direct connection success - ret:0 230411-07:05:22.154718 dca: Json message successfully submitted. /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-ArmConsolelog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-BootTime.log /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-CRlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-Consolelog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-FirewallDebug.txt /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-LM.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-MnetDebug.txt /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-PAMlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-PARODUSlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-PSMlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-TDMlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-TR69log.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-WEBPAlog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-WiFilog.txt.0 /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-dcmscript.log /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-swupdate.log /lib/rdk/uploadSTBLogs.sh: line 167: /bin/timestamp: No such file or directory  Processing file...04-11-23-07-05AM-version.txt 04-11-23-07-05AM-ArmConsolelog.txt.0 04-11-23-07-05AM-BootTime.log 04-11-23-07-05AM-CRlog.txt.0 04-11-23-07-05AM-Consolelog.txt.0 04-11-23-07-05AM-FirewallDebug.txt 04-11-23-07-05AM-LM.txt.0 04-11-23-07-05AM-MnetDebug.txt 04-11-23-07-05AM-PAMlog.txt.0 04-11-23-07-05AM-PARODUSlog.txt.0 04-11-23-07-05AM-PSMlog.txt.0 04-11-23-07-05AM-TDMlog.txt.0 04-11-23-07-05AM-TR69log.txt.0 04-11-23-07-05AM-WEBPAlog.txt.0 04-11-23-07-05AM-WiFilog.txt.0 04-11-23-07-05AM-dcmscript.log 04-11-23-07-05AM-swupdate.log 04-11-23-07-05AM-version.txt Uploading logs 04-11-23-07-04AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php 04-11-23-07-04AM.tgz 04-11-23-07-05AM-ArmConsolelog.txt.0 04-11-23-07-05AM-BootTime.log 04-11-23-07-05AM-CRlog.txt.0 04-11-23-07-05AM-Consolelog.txt.0 04-11-23-07-05AM-FirewallDebug.txt 04-11-23-07-05AM-LM.txt.0 04-11-23-07-05AM-MnetDebug.txt 04-11-23-07-05AM-PAMlog.txt.0 04-11-23-07-05AM-PARODUSlog.txt.0 04-11-23-07-05AM-PSMlog.txt.0 04-11-23-07-05AM-TDMlog.txt.0 04-11-23-07-05AM-TR69log.txt.0 04-11-23-07-05AM-WEBPAlog.txt.0 04-11-23-07-05AM-WiFilog.txt.0 04-11-23-07-05AM-dcmscript.log 04-11-23-07-05AM-swupdate.log 04-11-23-07-05AM-version.txt Uploading logs 04-11-23-07-05AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php Moving to Previous Logs Backup Folder Moving to Previous Logs Backup Folder Telemetry Profile File Being Used : /tmp/DCMSettings.conf 230411-07:10:11.594295 dca upload url from dcmresponse is https://xconf.rdkcentral.com/xconf/telemetry_upload.php Build Type: dev Log file: 04-11-23-07-10AM.tgz TFTP Server: https://xconf.rdkcentral.com/xconf/logupload.php Protocol: 0 UploadHttpLink: 0 230411-07:10:11.968455 dca : Only Direct connection is available 230411-07:10:11.997319 dca: Sleeping for 9 before upload. Uploading Logs with DCM UploadOnReboot set to true 230411-07:10:22.212030 dca: Direct connection success - ret:0 230411-07:10:22.222547 dca: Json message successfully submitted. 04-11-23-07-10AM-ArmConsolelog.txt.0 04-11-23-07-10AM-BootTime.log 04-11-23-07-10AM-CRlog.txt.0 04-11-23-07-10AM-Consolelog.txt.0 04-11-23-07-10AM-FirewallDebug.txt 04-11-23-07-10AM-LM.txt.0 04-11-23-07-10AM-MnetDebug.txt 04-11-23-07-10AM-PAMlog.txt.0 04-11-23-07-10AM-PARODUSlog.txt.0 04-11-23-07-10AM-PSMlog.txt.0 04-11-23-07-10AM-TDMlog.txt.0 04-11-23-07-10AM-TR69log.txt.0 04-11-23-07-10AM-WEBPAlog.txt.0 04-11-23-07-10AM-WiFilog.txt.0 04-11-23-07-10AM-dcmscript.log 04-11-23-07-10AM-swupdate.log 04-11-23-07-10AM-version.txt Uploading logs 04-11-23-07-10AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php Moving to Previous Logs Backup Folder Telemetry Profile File Being Used : /tmp/DCMSettings.conf 230411-07:15:11.910473 dca upload url from dcmresponse is https://xconf.rdkcentral.com/xconf/telemetry_upload.php Build Type: dev Log file: 04-11-23-07-15AM.tgz TFTP Server: https://xconf.rdkcentral.com/xconf/logupload.php Protocol: 0 UploadHttpLink: 0 230411-07:15:12.207803 dca : Only Direct connection is available 230411-07:15:12.235454 dca: Sleeping for 9 before upload. Uploading Logs with DCM UploadOnReboot set to true 230411-07:15:22.507326 dca: Direct connection success - ret:0 230411-07:15:22.516624 dca: Json message successfully submitted. 04-11-23-07-15AM-ArmConsolelog.txt.0 04-11-23-07-15AM-BootTime.log 04-11-23-07-15AM-CRlog.txt.0 04-11-23-07-15AM-Consolelog.txt.0 04-11-23-07-15AM-FirewallDebug.txt 04-11-23-07-15AM-LM.txt.0 04-11-23-07-15AM-MnetDebug.txt 04-11-23-07-15AM-PAMlog.txt.0 04-11-23-07-15AM-PARODUSlog.txt.0 04-11-23-07-15AM-PSMlog.txt.0 04-11-23-07-15AM-TDMlog.txt.0 04-11-23-07-15AM-TR69log.txt.0 04-11-23-07-15AM-WEBPAlog.txt.0 04-11-23-07-15AM-WiFilog.txt.0 04-11-23-07-15AM-dcmscript.log 04-11-23-07-15AM-swupdate.log 04-11-23-07-15AM-version.txt 04-11-23-07-15AM-wifihealth.txt Uploading logs 04-11-23-07-15AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php Moving to Previous Logs Backup Folder Telemetry Profile File Being Used : /tmp/DCMSettings.conf 230411-07:20:11.916415 dca upload url from dcmresponse is https://xconf.rdkcentral.com/xconf/telemetry_upload.php Build Type: dev Log file: 04-11-23-07-20AM.tgz TFTP Server: https://xconf.rdkcentral.com/xconf/logupload.php Protocol: 0 UploadHttpLink: 0 230411-07:20:12.155150 dca : Only Direct connection is available 230411-07:20:12.173850 dca: Sleeping for 9 before upload. Uploading Logs with DCM UploadOnReboot set to true 230411-07:20:22.367094 dca: Direct connection success - ret:0 230411-07:20:22.375902 dca: Json message successfully submitted. 04-11-23-07-20AM-ArmConsolelog.txt.0 04-11-23-07-20AM-BootTime.log 04-11-23-07-20AM-CRlog.txt.0 04-11-23-07-20AM-Consolelog.txt.0 04-11-23-07-20AM-FirewallDebug.txt 04-11-23-07-20AM-LM.txt.0 04-11-23-07-20AM-MnetDebug.txt 04-11-23-07-20AM-PAMlog.txt.0 04-11-23-07-20AM-PARODUSlog.txt.0 04-11-23-07-20AM-PSMlog.txt.0 04-11-23-07-20AM-TDMlog.txt.0 04-11-23-07-20AM-TR69log.txt.0 04-11-23-07-20AM-WEBPAlog.txt.0 04-11-23-07-20AM-WiFilog.txt.0 04-11-23-07-20AM-dcmscript.log 04-11-23-07-20AM-swupdate.log 04-11-23-07-20AM-version.txt 04-11-23-07-20AM-wifihealth.txt Uploading logs 04-11-23-07-20AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php Moving to Previous Logs Backup Folder Telemetry Profile File Being Used : /tmp/DCMSettings.conf 230411-07:25:16.689426 dca upload url from dcmresponse is https://xconf.rdkcentral.com/xconf/telemetry_upload.php Build Type: dev Log file: 04-11-23-07-25AM.tgz TFTP Server: https://xconf.rdkcentral.com/xconf/logupload.php Protocol: 0 UploadHttpLink: 0 230411-07:25:16.919765 dca : Only Direct connection is available 230411-07:25:16.938127 dca: Sleeping for 9 before upload. Uploading Logs with DCM UploadOnReboot set to true 230411-07:25:27.298600 dca: Direct connection success - ret:0 230411-07:25:27.307538 dca: Json message successfully submitted. 04-11-23-07-25AM-ArmConsolelog.txt.0 04-11-23-07-25AM-BootTime.log 04-11-23-07-25AM-CRlog.txt.0 04-11-23-07-25AM-Consolelog.txt.0 04-11-23-07-25AM-FirewallDebug.txt 04-11-23-07-25AM-LM.txt.0 04-11-23-07-25AM-MnetDebug.txt 04-11-23-07-25AM-PAMlog.txt.0 04-11-23-07-25AM-PARODUSlog.txt.0 04-11-23-07-25AM-PSMlog.txt.0 04-11-23-07-25AM-TDMlog.txt.0 04-11-23-07-25AM-TR69log.txt.0 04-11-23-07-25AM-WEBPAlog.txt.0 04-11-23-07-25AM-WiFilog.txt.0 04-11-23-07-25AM-dcmscript.log 04-11-23-07-25AM-swupdate.log 04-11-23-07-25AM-version.txt 04-11-23-07-25AM-wifihealth.txt Uploading logs 04-11-23-07-25AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php Moving to Previous Logs Backup Folder Telemetry Profile File Being Used : /tmp/DCMSettings.conf 230411-07:30:11.690231 dca upload url from dcmresponse is https://xconf.rdkcentral.com/xconf/telemetry_upload.php Build Type: dev Log file: 04-11-23-07-30AM.tgz TFTP Server: https://xconf.rdkcentral.com/xconf/logupload.php Protocol: 0 UploadHttpLink: 0 230411-07:30:11.924824 dca : Only Direct connection is available 230411-07:30:11.943922 dca: Sleeping for 9 before upload. Uploading Logs with DCM UploadOnReboot set to true 230411-07:30:22.136394 dca: Direct connection success - ret:0 230411-07:30:22.145563 dca: Json message successfully submitted. 04-11-23-07-30AM-ArmConsolelog.txt.0 04-11-23-07-30AM-BootTime.log 04-11-23-07-30AM-CRlog.txt.0 04-11-23-07-30AM-Consolelog.txt.0 04-11-23-07-30AM-FirewallDebug.txt 04-11-23-07-30AM-LM.txt.0 04-11-23-07-30AM-MnetDebug.txt 04-11-23-07-30AM-PAMlog.txt.0 04-11-23-07-30AM-PARODUSlog.txt.0 04-11-23-07-30AM-PSMlog.txt.0 04-11-23-07-30AM-TDMlog.txt.0 04-11-23-07-30AM-TR69log.txt.0 04-11-23-07-30AM-WEBPAlog.txt.0 04-11-23-07-30AM-WiFilog.txt.0 04-11-23-07-30AM-dcmscript.log 04-11-23-07-30AM-swupdate.log 04-11-23-07-30AM-version.txt 04-11-23-07-30AM-wifihealth.txt Uploading logs 04-11-23-07-30AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php Moving to Previous Logs Backup Folder Telemetry Profile File Being Used : /tmp/DCMSettings.conf 230411-07:35:13.203201 dca upload url from dcmresponse is https://xconf.rdkcentral.com/xconf/telemetry_upload.php Build Type: dev Log file: 04-11-23-07-35AM.tgz TFTP Server: https://xconf.rdkcentral.com/xconf/logupload.php Protocol: 0 UploadHttpLink: 0 230411-07:35:13.427803 dca : Only Direct connection is available 230411-07:35:13.446079 dca: Sleeping for 9 before upload. Uploading Logs with DCM UploadOnReboot set to true 230411-07:35:24.082882 dca: Direct connection success - ret:0 230411-07:35:24.092352 dca: Json message successfully submitted. 04-11-23-07-35AM-ArmConsolelog.txt.0 04-11-23-07-35AM-BootTime.log 04-11-23-07-35AM-CRlog.txt.0 04-11-23-07-35AM-Consolelog.txt.0 04-11-23-07-35AM-FirewallDebug.txt 04-11-23-07-35AM-LM.txt.0 04-11-23-07-35AM-MnetDebug.txt 04-11-23-07-35AM-PAMlog.txt.0 04-11-23-07-35AM-PARODUSlog.txt.0 04-11-23-07-35AM-PSMlog.txt.0 04-11-23-07-35AM-TDMlog.txt.0 04-11-23-07-35AM-TR69log.txt.0 04-11-23-07-35AM-WEBPAlog.txt.0 04-11-23-07-35AM-WiFilog.txt.0 04-11-23-07-35AM-dcmscript.log 04-11-23-07-35AM-swupdate.log 04-11-23-07-35AM-version.txt 04-11-23-07-35AM-wifihealth.txt Uploading logs 04-11-23-07-35AM.tgz  onto https://xconf.rdkcentral.com/xconf/logupload.php Moving to Previous Logs Backup Folder

         Attaching sample file :  B8_27_EB_22_16_36-Logs-11-10-21-07-00AM.tgz

Feature Validation: Telemetry

• 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.

• Create a new Telemetry Profile.
  Flow: X-conf-server -> Telemetry -> Permanent Profiles -> Create button

           Image Added

• The permanent profile must have the below entries
  • Name of the RPI device profile
  • Upload Repository (HTTP/TFTP, HTTPS)(HTTPS:https://xconf.rdkcentral.com/xconf/telemetry_upload.php)
  • Telemetry profile Entries(We can add multiple telemetry profiles using “+” button.
  )
  • 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.

...

• DMCLI GET

Image Removed

Image Removed

...

• DMCLI GET

Image Added

Image Added

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

           Image Added

• Once you save the Telemetry 2.0 profile, you will get a message overlay ‘Profile added to the pending changes’. Then go to Changes -> select the profile you create -> Click on “Approve selected changes”.

           Image Added

• Create Telemetry 2.0 Targeting Rule
  Flow: Xconf Server -> Telemetry > Telemetry 2.0 Rules > create

           Image Added

• Verification
  Flow: Xconf -Server -> Telemetry > Telemetry 2.0 Test page

          Image Added

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

          Image Added          

• Log Verification in RPI
  Path: rdklogs/logs/
  file: telemetry2_0.txt.0

          Image Added

          Image Added

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

           Image Added

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=

           Image Removed

• Once you save the Telemetry 2.0 profile, you will get a message overlay ‘Profile added to the pending changes’. Then go to Changes -> select the profile you create -> Click on “Approve selected changes”.

           Image Removed

• Create Telemetry 2.0 Targeting Rule
  Flow: Xconf Server -> Telemetry > Telemetry 2.0 Rules > create

           Image Removed

• Verification
  Flow: Xconf -Server -> Telemetry > Telemetry 2.0 Test page

          Image Removed

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

           Image Added

• Verify the existing(default) value of TR181 parameters

          Image Removed   root@RaspberryPi-Gateway:~# dmcli eRT getv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.TR069support.Enable
           

• Log Verification in RPI
  Path: rdklogs/logs/
  file: telemetry2_0.txt.0

CR component name is: eRT.com.cisco.spvtg.ccsp.CR
            Image Removedsubsystem_prefix eRT.
          Image Removed

...

  getv from/to component(eRT.com.cisco.spvtg.ccsp.pam): Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.TR069support.Enable
            Execution succeed.
            Image Removed

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:19092/featureControl/getSettings

           Image Removed

...

Parameter    1 name: Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.TR069support.Enable
                                type:       bool,    value: true

            root@RaspberryPi-Gateway:~# dmcli eRT getv   Device.X_Comcast_com_ParentalControl.ManagedSites.Enable Device.X_Comcast_com_ParentalControl.ManagedServices.Enable
            CR component name is: eRT.com.cisco.spvtg.ccsp.CR
            subsystem_prefix eRT.
            getv from/to component(eRT.com.cisco.spvtg.ccsp.pam): Device.X_Comcast_com_ParentalControl.ManagedSites.Enable
            Execution succeed.
            Parameter    1 name: Device.X_Comcast_com_ParentalControl.ManagedSites.Enable
                      type   type:       bool,    value: false   value: false

           root@RaspberryPi-Gateway:~#  dmcli eRT getv Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.PresenceDetect.Enable
          CR component name is: eRT.com.cisco.spvtg.ccsp.CR
          subsystem_prefix eRT.
          getv from/to component(eRT.com.cisco.spvtg.ccsp.pam): Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.PresenceDetect.Enable
          Execution succeed.
            Parameter    2  1 name: Device.DeviceInfo.X_Comcast_com_ParentalControl.ManagedServicesRDKCENTRAL-COM_RFC.Feature.PresenceDetect.Enable
            type         type:       bool,    value: truefalse

            Image Removed  

• Xconf Server UI Configuration
  Change Application to stb in top right corner of the window.

...

• Define the Feature
  Flow : Xconf-Server -> RFC -> Feature ->Create
  Feature Instance: <Unique Identifier>
  Name: <Unique Identifier>
  Config Data: < tr181 parameter with its new value>
  Effective immediate: true
  Enable: true

          Image Added

          Image Removed Image Added

• Define the Feature Rule
  Flow: Xconf-server -> RFC -> Feature Rule -> Create
  Name : <Unique Identifier>
  Priority: 1
  Feature : choose your RFC feature ( Previously created)
  Rule : estbMacAddress IS <MAC Address>
  OR
  estbIP IS <IP Address>

          Image Removed Image Added

• RFC- Test Page
  Flow: Xconf-server -> RFC -> Test Page
  Parameter : estbMacAddress IS <MAC Address>
  OR
  estbIP IS <IP Address>

           Image RemovedImage Added

• Verification through Curl command
  Restart the rfc service: systemctl restart rfc.service
  curl -i 'http://<IP>:19092/featureControl/getSettings?estbMacAddress=<MAC-Address>&model=RDKB_RPI’
  
  Example :curl -i 'https://xconf.rdkcentral.com:19092/featureControl/getSettings?estbMacAddress=E4:5F:01:FB:13:4B&estbIP=192.168.225.58'

           Image RemovedImage Added

• Once it is successful, rfc-parsed.txt will be created under /tmp directory.
• Configured data’s that are parsed to the client can be verified at /tmp/rfc_configdata.txt

           Image RemovedImage Added

• Verify with DM

          Image Removed Image Added

• Verify the logs in /rdklogs/logs/dcmrfc.log file
  

           Image Removed

           Image Removed

           Image Removed

...

• Attaching the log file :     dcmrfc_log.txt

Firmware Upgradation for RPI using Xconf Server

...

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

          Image Removed Image Added

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

         Image RemovedImage Added

• Change the TFTP address in /etc/device.properties

...

• Sample Log

• root@RaspberryPi-Gateway:/rdklogs/logs# root@RaspberryPi-Gateway:/rdklogs/logs# cat swupdate.log Started executing swupdate_utility.sh and device type is :broadband Main app & Triggering deviceInitiatedFWDnld.sh URL_CMD: curl -w %{http_code} 'https://xconf.rdkcentral.com:9092/xconf/swu/stb?eStbMac=B8:27:EB:22:16:36' -o /tmp/cloudurl.txt >> /tmp/cloudhttpresp.txt No error in curl command and curl http code is:200 cloud version is rdkb-generic-broadband-image_rdk-next_20211118174413 RPI version is rdkb-generic-broadband-image_rdk-next_20211118184509 Active bank is:2 rpiimageModel in dev is :rdkb cloudimageModel  is :rdkb no of parts is :4 active bank is 0 so fetch info from passive and partition is:2 rpipassivebankimageModel: passivebankVersion: since bank1 p3 is broadband and pass bank is rdkv cloud is broadband check broadband version and upgrade if mismatches check broadband versions and upgrade if mismatches !! Device type is broadband !! Image Upgrade During Bootup ..! Main APP of devinitFWDNLD--- 2021-11-22 07:15:14 version = rdkb-generic-broadband-image_rdk-next_20211118184509 2021-11-19 07:15:14 buildtype = dev Mac in jsonstr:B8:27:EB:22:16:36&model=RPI&capabilities=RCDL&capabilities=supportsFullHttpUrl 2021-11-22 07:15:14 JSONSTR: B8:27:EB:22:16:36&model=RPI&capabilities=RCDL&capabilities=supportsFullHttpUrl Trying to communicate with XCONF server URL_CMD: curl -w %{http_code} 'https://xconf.rdkcentral.com:909219092/xconf/swu/stb?eStbMac=B8:27:EB:22:16:36&model=RPI&capabilities=RCDL&capabilities=supportsFullHttpUrl' -o /rdklogs/logs/response.txt >> /rdklogs/logs/xconf_curl_httpcode CKP: got no error in curl command!!!!!!!!!!!!!200 Curl return code : 0 ret = 0, http_code: 200 for XCONF communication 2021-11-22 07:15:15 HTTP request success. Processing response.. OUTPUT1 : 2021-11-22 07:15:16 cloudFWFile: rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic 2021-11-22 07:15:16 cloudFWLocation: 192.168.1.4 2021-11-22 07:15:16 cloudFWVersion: rdkb-generic-broadband-image_rdk-next_20211118174413 2021-11-22 07:15:16 cloudProto: tftp 2021-11-22 07:15:16 cloudImmediateRebootFlag: false 2021-11-22 07:15:16 myFWVersion = rdkb-generic-broadband-image_rdk-next_20211118184509 2021-11-22 07:15:16 myFWFile = 2021-11-22 07:15:16 lastDnldFile: 2021-11-22 07:15:16 cloudFWVersion: rdkb-generic-broadband-image_rdk-next_20211118174413 2021-11-22 07:15:16 cloudFWFile: rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic Xconf image Check Firmware versions are different myFWVersion : rdkb-generic-broadband-image_rdk-next_20211118184509 cloudFWVersion : rdkb-generic-broadband-image_rdk-next_20211118174413 cloudFWLocation192.168.1.4 cloudfile :rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic protocol1 2021-11-22 07:15:16 Starting Image Flashing ... 2021-11-22 07:15:16 Upgrade Server = 192.168.1.4 2021-11-22 07:15:16 Upgrade File = rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic 2021-11-22 07:15:16 Reboot Flag = 0 2021-11-22 07:15:16 Upgrade protocol = 1 2021-11-22 07:15:16 PDRI Upgrade = CKP !!!!!!!!! calling rpi_sw_install Checking available partition for bank switch and image upgrade... Creating additional partition for storage area and box will go for reboot... storage partition mmcblk0p4 is available file system type check count partition p3 is 0 Creating ext4 file system for partition mmc0blkp3... Discarding device blocks: done Creating filesystem with 524288 4k blocks and 131072 inodes Filesystem UUID: 2fbcfc3a-6b84-48b0-a171-86dd13cbf82b Superblock backups stored on blocks:         32768, 98304, 163840, 229376, 294912 Allocating group tables: done Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done file system type check count partition p4 is 0 Creating ext4 file system for partition mmc0blkp4... Discarding device blocks: done Creating filesystem with 524288 4k blocks and 131072 inodes Filesystem UUID: 1c2075c1-9de9-4fb0-b9ab-f9ca277f54d7 Superblock backups stored on blocks:         32768, 98304, 163840, 229376, 294912 cloud proto is :1 set IPtable rules for tftp !! cloudfile is:rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic cloudlocation is:192.168.1.4 Downloading already deployed checksum file from server rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic tftp download checksum file checksum file to download is rdkb-generic-broadband-image_rdk-next_20211118174413.txt Downloading rdkb-generic-broadband-image_rdk-next_20211118174413.rootfs.wic ...

• Verify the tftp download is happening by noticing the change of file size using below command:
  ls /extblock/tftpimage/imagedwnldls -sh  (use this command frequently to verify the file size change)

...