Command Line Interface(CLI)

• Allows to perform Data Model related operations from the device console. Some of the basic operations by CLI in RDK-B are:
  • Get the value of a parameter
  • Set the value of a parameter
  • Add an entry to the table
  • Delete an entry to the table
• Component : CcspDmCli

Common Data Model

• RDK-B uses TR-181 as a common data model
• All Protocol Agents (SNMP/TR069) and WebUI internally use this common data model

eMTA

• RDK-B supports embedded Multimedia Terminal Adapter (MTA stack itself not included as part of RDK-B - provided by OEM)

• Various OEM's can use their own MTA modules in collaboration with RDK-B middle ware
• RDK-B provides various monitoring metrics and a data model parameters to enable and monitor the MTA module provided by the OEM

Routing Information Protocol (RIP)

• RDK-B uses RIP as the routing mechanism
• RIP is a  distance-vector routing protocols which employ the hop count as a routing metric. RIP prevents routing loops by implementing a limit on the number of hops allowed in a path from source to destination

Protocol

• RIP routes are redistributed into primary Routing table.
• RIPv2 runs as PE-CE routing protocol between CM and CMTS. In order to have the RIP routes into main routing table, RIP routes are further redistributed into Main routing table.

RIP protocol usage in RDK-B

In RDK-B the RIP protocol is used to exchange the routing information between the gateway and headend.

• Support for RIPv2 (RFC 2453) on the WAN
• Needed for static provisioning support
• If RIP is enabled on WAN
  • Need to allow multicast udp port 520 and unicast
• Object in it’s DML Layer: Device.Routing.RIP.

Self Heal

• Continuously monitors the running CCSP processes and takes necessary actions
• Monitors and restarts processes when required
• For more details on feature SelfHeal