FTTH implementation

Overview

This is the coding guideline of how FTTH + DSL + WiFi is (will be) implemented in NMS Prime.

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:

1. Every network architecture (GPON, Active Ethernet, DSL, WiFi) requires a different provisioning implementation
2. vendor specific CLI commands (or SNMP MIBs) makes life hard for a generic implementation approach
   switching OLT vendor will cause pain!
3. ONU –> OLT port mapping required
   support team needs knowledge of FTTH connection circuits (ineffective/bad workflow!)
4. 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.

Naming conventions

The solution:

The solution is PPPoE with the following architecture

1. OLT / AE / DSLAM serves all ONUs with a default profile of maximum speed, e.g. 1GBit/s down and upstream
2. a normal core router with PPPoE is used for traffic shaping
3. customer devices requires to use PPPoE protocol for dial-in

Dial-in Workflow

TODO: from ONU registration to establishing the ip/speed-tunnel provisioning