Introduction

          This page describes  the  bring-up of RdkWanManager on Raspberry-pi platform using  rdk-next branch. Also, we captured  list of the issues that are faced during bring up and resolution for the same. 

Components

The following components are newly introduced for Porting of  RdkWanManager in RPI Target Platform ,

•  RdkWanManager 
• JSON RPC

The following  are the dependent components & meta-layers which are modified, 

• Utopia 
• PandM 
• LogAgent
• CcspCommonLibrary 
• meta-rdk-broadband 
• meta-cmf-broadband 
• CcspEthAgent
• JSON ETHSW
• rdk_logger
• meta-cmf-raspberrypi

RPI Build Steps 

Please refer the below link for host environment set-up & flashing procedure for yocto build ,

Dunfell :

RPI 3B/3B+ Model Reference Platform

Morty:

RDK-B Raspberrypi - Host SetUp and Build Instructions#BRaspberrypi-HostSetUpandBuildInstructions-YoctoBuildSteps

Repo Steps

To  build, follow below instructions

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init -u https://code.rdkcentral.com/r/manifests -b dunfell -m rdkb-extsrc.xml 
$ repo sync -j`nproc` --no-clone-bundle

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init -u https://code.rdkcentral.com/r/manifests -b rdk-next -m rdkb-extsrc.xml
$ repo sync -j`nproc` --no-clone-bundle

Image Generation Steps

$ MACHINE=raspberrypi-rdk-broadband source meta-cmf-raspberrypi/setup-environment
$ bitbake rdk-generic-broadband-image

Control Flow

Following diagram depicts the flow of control among the components,

• platform-hal (i.e. hal-ethsw) will send the callbacks(pGWP_act_EthWanLinkUP /pGWP_act_EthWanLinkDOWN) whenever physical link event change to EthAgent.
• CcspEthAgent will pass the link change event to Wan Manager,
                     It will set the value for Wan Manger DM ‘Device.X_RDK_WanManager.CPEInterface.1.Wan.LinkStatus’  

Approach

Integration Approach

Manifest Changes

<project name="rdkb/components/opensource/ccsp/RdkWanManager" revision="rdk-next"/>
<project name="rdkb/components/generic/json-rpc" revision="rdk-next"/>

Global CFLAGS

• FEATURE_RDKB_WANMANAGER is the global CFLAG used in other components to use with WANMANAGER feature.
• All the changes are enclosed inside FEATURE_RDKB_WAN_MANAGER compilation flag, this CFLAG can be used to control whether or not to
  compile the WanManager code changes.

We enabled WanManager CFLAGS in below file in rpi(meta-cmf-raspberrypi) layer,

CFLAGS_append += "${@bb.utils.contains('DISTRO_FEATURES', 'rdkb_wan_manager', ' -DFEATURE_RDKB_WAN_MANAGER ', '', d)}"

Distro Features

We are using the following distro features to enable rdkb wanmanager in RPI machine configuration file,

• rdkb_wan_manager : Used to enable RDK WanManager and json hal

DISTRO_FEATURES_append = "  rdkb_wan_manager"

Also , we need to disable the GwProvapp-EthWan component in ccsp packagegroup . 

GWPROVAPP = ""

Package Group

To enable the RDKB Wanmanager components, added those components into the final build target.  So, We have added those components into the  ccsp packagegroup(58865),

RDEPENDS_packagegroup-rdk-ccsp-broadband_append = " ${@bb.utils.contains('DISTRO_FEATURES', 'rdkb_wan_manager', ' rdk-wanmanager json-hal-lib hal-json-ethsw', '', d)} "

ethsw(platform-hal)

• Developed C HAL API's to support the ETH Agent for WanManager Feature .

Utopia CFLAG

• To disable the utopia service_wan execution , we need to enable the utopia _WAN_MANAGER_ENABLED_ flag would mean that the RdkWanManager controls the Wan Management.   

  
  

  CFLAGS_append += "${@bb.utils.contains('DISTRO_FEATURES', 'rdkb_wan_manager', ' -D_WAN_MANAGER_ENABLED_', '', d)}"

                       

Persistent (PSM) configuration changes

For wanmanager, the default configurations are stored in PSM. As of now, we have 1 interfaces defined for WAN in wanmanager modules (i,e) wanoe.

For WANOE, by default we are using `eth0 `port for WAN connection. 

Example PSM Configurations

Major Errors and Challenges 

Validation Test Results

• Flash the latest generated build
• Goto RG console

erouter0 IPv4 address

                    erouter0 should have valid IP based on the wan configuration (Eg 192.168.0.11/24)

brlan0 IPv4 Address

                         brlan0 IPv4 should be 10.0.0.1 ( i,e Default IP Address )

Able to take SSH from WAN IP

                     ssh from WAN to eRouter IP should be successful

Internet Testing on RPI

•  erouter0 Interface should have Ipv4 Address
• verify the ping www.google.com on RPI
• RPI shouldn't lose the Internet

LAN client IPv4 and Internet 

                   Lan clients should get IPv4 address in the range of 10 series(i,e default DHCP server pool range) and captive portal page should be loaded.

CCSP Process Status

                All ccsp process should be Up and corresponding DataModel parameters should be loaded properly.

RdkWanManager systemd Status

•   RdkWanManager process should be up . We can verify the status by using the below screenshot command,

• RdkWanManager  DataModel Parameters should be loaded properly, we can use the below command to verify the status, 

WanManager Logs

                 WanManager logs will be generated in /rdklogs/logs folder in RPI

Systemd Status

          Following systemd service file's status needs to be verfiy,

1.  utopia
2.  CcspEthAgent
3. CcspPandMSsp

Using dmcli commands to verify the LinkStatus(CcspEthAgent will pass the LinkStatus to WanManager )

WebUI Test on RPI

                 WebUI should be loaded in Webbrowser by using erouter0 IPv4 Address(i,e erouter0ip:8080) and login should be successful

Internet check should be successful,

Known Issues

              Sometimes , erouter0 interface is not getting the WAN IP .