Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Basic principles

ProtocolUsageProvisioning of
TR-69protocol for remote management of customer-premises equipment (CPEs)CPEs only!
PPPoEThe Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol for encapsulating PPP frames inside Ethernet frames. (wikipedia)speed provisioning of any device (DSL, PGON, AE, ..)



The problem

TR-69 is a provisioning protocol for CPE's only. This implies there is now standardised way of how to set Modem speed rates (e.g. Downstream/Upstream rate 100MBit/s to 10MBit/s). Many operator address this by using a quick-and-dirty method of setting internet speeds at the OLT directly via CLI. The next logical step is easy but also dirty: using the CRM to somehow "connect via telnet or SSH and push the required speed rates via CLI (or better SNMP)". This will work but it comes at a high price, imagine:

disadvantages for setting the modem speed via CLI directly at the OLT:

  1. vendor specific CLI commands (or SNMP MIBs) makes life hard for a generic implementation approach
    switching OLT vendor will cause pain!
  2. ONU –> OLT port mapping required
    support team needs knowledge of FTTH connection circuits (ineffective/bad workflow!)
  3. potential config race conditions / hazards
    Assume you are connected via SSH towards your OLT, while the provisionig system pushes also config changes via telnet/SSH. This could lead to race conditions, especially while saving configs.

The solution: Traffic shaping via PPPoE in the core network


  • No labels