RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Network < -- > ONU < -- > EthWAN XB6
Important Data models
DM | Description |
---|---|
Device.Ethernet.X_RDKCENTRALCOM_WAN.Enabled | The DML is used to ON/OFF the EthWan Feature. The default value is OFF. |
Device.Ethernet.X_RDKCENTRALCOM_WAN.Port | The DML provides the port number that is configured if the feature is ENABLED with Device.Ethernet.X_RDKCENTRAL-COM_WAN.Enabled |
Device.DeviceInfo.X_RDKCENTRALCOM_EthernetWAN.CurrentOperationalMode | The DML is used to verify in which MODE the box is currently operating |
TR-69 Data model:
dmcli eRT setv Device.Ethernet.X_RDKCENTRAL-COM_WAN.Enabled bool True
dmcli eRT setv Device.Ethernet.X_RDKCENTRAL-COM_WAN.Port uint 0
WebUI:
To support manual configuration via local GUI (user side) to change configuration to Ethernet WAN or DOCSIS WAN is under Gateway> Connection > WAN Network
screenshot of Xfinity page
Ccsp EthAgent DMCLI Code flow
dgm
GW Prov Ethwan Code flow
dgm
Command | Description |
---|---|
hal_test ethwan enableEthwan | To enable EthWan |
hal_test ethwan disableEthwan | To disable EthWan |
hal_test ethwan GetEthWanInterfaceName | To get the EthWan Interface name |
hal_test ethwan getEthWanEnabled | To get the EthWan status (enabled or disabled) |
hal_test ethwan getEthWanPort | To know which port is enabled for EthWan feature |
hal_test ethwan setEthWanPort_eth0 | Set eth0 port as EthWan interface |
hal_test ethwan setEthWanPort_eth1 | Set eth1 port as EthWan feature |
*All are Broadcom specific commands
Once we get the interface name from HAL, below are the steps to create the interface.
Below is the example for eth0 interface.
# ifconfig eth0 down //Bring down the eth0 interface
# vlan_util del_interface brlan0 eth0 // Delete interface eth0 under brlan0
# ip link set erouter0 name dummy-rf // Rename erouter0 interface to “dummy-rf”
# brctl addbr erouter0; // Add a new bridge erouter0
# brctl addif erouter0 eth0; // Add interface eth0 under erouter0
# ifconfig erouter0 down; // Bring down the erouter0 interface
# ifconfig erouter0 hw ether //Assign the mac address to erouter0 interface
# sysevent set eth_wan_mac //Set eth_wan interface mac as erouter0 mac
# ifconfig erouter0 up // Bring up the erouter0 interface
Once completed, the interface status can be verified by the below commands.
# brctl show
erouter0 8000.021018d8443c no cm0
eth0
The below DM’s shows the same erouter0 ip address as output
Even after reboot and firmware upgrade, The EthWAN feature remains enabled.
Can be verified using the below DM’s
When the configuration is set to EthWAN, a telemetry marker must be sent to report that the device is operating in Ethernet WAN mode and to report the PHY rate of the Ethernet link during each power up/reboot
The PHY rate must be reported in mbps (example: 10, 100, 1000) Suggested telemetry marker is WAN_MODE: Ethernet $phyrate
Remove parodus2ccsp, xsmart ,ccsp LM lite and WebPA dependencies from CM agent.To get the CM mac query the sysevent variable instead of CMAgent
MTA Functionality is supported in ETH WAN Mode
No CM IP available in ETHWAN Mode. Hence, MSO WebUI is not accessible over CM IP. ( MSO WebUI is accessed by mapping erouter IP to CM IP )
SNMP walk on CM OIDs will fail in EthWan mode
No compile time configuration is needed to enable the EthWan to build (it is suppose to be run time)
In EthWan mode, the Docsis path is un-available, so it is not possible to use Ethwan as backhaul network with Docsis
EthWAN | Docsis |
---|---|
GwProvApp-EthWan is used for EthWan configuration | GwProvApp is used for Docsis configuration |
Default CR device profile used is cr-ethwandeviceprofile.xml | There is a dependency on CM agent. |
parodus2ccsp, xsmart ,ccsp LM lite and webpa are not having dependencies on CM agent | DML is used to verify in which MODE the box is currently operating |
WEBPA & Reverse SSH is working over WAN MAC assigned to ifconfig erouter0 interface | The Device is using CM MAC as defined in hardware system |
XB6 Ethernet Port 1 must not be available for LAN side connections | Ethernet Port 1 must be usable for LAN side client connectivity |
The Cable Modem is not active and there is no active CM IP address | Cable Modem is active and there is active CM IP Address |