Page History

...

• When device is in EthWAN Mode, WebPA & Reverse SSH works over WAN MAC assigned to erouter0 interface ,where as in DOCSIS Mode, device is using CM MAC as defined in hardware system.
• In EthWAN Mode, the Cable Modem is not active and device will not be having CM IP since CcspCMAgentSsp is down so erouter0 IP is mentioned as CM IP.

The below DM’s shows the same erouter0 ip address as output

• Device.DeviceInfo.X_COMCAST-COM_CM_IP                                                   // CM ip is changed to erouter0  ip
• Device.DeviceInfo.X_COMCAST-COM_WAN_IPv6                                            // erouter0 ip

Even after reboot and firmware upgrade, The EthWAN feature remains enabled.Can be verified using the below DM’s

• Device.Ethernet.X_RDKCENTRAL-COM_WAN.Enabled                                   // value is true
• Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.PartnerId                      //syndication partners

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

• Example to report 1 Gbps Ethernet WAN mode- WAN_MODE: Ethernet 1000

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