Pre-requisite

• Configure the XCONF server with the values 

  • Update the rules and configs in XCONF server. Please refer this 
  Xconf Server - User guide for configuration and feature validation#FeatureValidation(RFC) how to configure RFC rules and configurations in the RDKM XCONF server.
  • Feature Validation(LogUpload)  on configuring DCM configurations in the RDKM XCONF server.

  Client side

  1) Make sure that required RFC parameters are configured before starting the validation and file community-rfc-configs.ini is present in /etc/rfcdefaults/ path to do so. 

  /etc/rfcdefaults# ls -l
  -rw-r--r--    1 root     root           352 Jan 30 05:11 community-rfc-configs.ini

  2) Ensure telemetry process is running by checking the pid

  
  

  root@raspberrypi4-64-rdke:~# pidof telemetry2_01312

  Invoke system service query for setting timezone
   

  curl -H"Authorization: Bearer `WPEFrameworkSecurityUtility | cut -d '"' -f 4`" -d '{"jsonrpc":"2.0","id":"3","method": "org.rdk.System.setTimeZoneDST","params": {"timeZone": "America/New_York"}}' http://127.0.0.1:9998/jsonrpc {"jsonrpc":"2.0","id":3,"result":{"success":true}} root@raspberrypi4-64-rdke:/opt/persistent# cat timeZoneDST America/New_Yorkroot@raspberrypi4-64-rdke:/opt/persistent#

  Set the Telemetry URL
   

  tr181 -s -t string -v https://xconf.rdkcentral.com/loguploader/getT2Settings Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.ConfigURLtr181 -g Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.Telemetry.ConfigURL

Steps to validate 

curl --header "Content-Type: application/json" --request POST --data '{"jsonrpc":"2.0","id":"3","method":"Controller.1.activate","params":{"callsign":"org.rdk.MaintenanceManager"}}' http://127.0.0.1:9998/jsonrpc

Maintanencemanager invocation is handling through UI side. For current validation, we are following this approach.

Success Logs