In a Glance

The CPE controller system of the ISP must be able to set the configurations specific to each device, right when it realizes the CPE connection to the network infrastructure.
The customer or technician will plug-in the CPE and everything must work: the PPPoE credentials, VoIP service, Wi-Fi SSID, password, Guest network... In resume: seamless experience for the customer and cost savings for the ISP with reduced provisioning time and human failure.

How to create a ZTP workflow at your ISP

To learn more, check the complete documentation at: https://docs.oktopus.app.br/getting-started/enterprise-edition/services

Pre-attach a service to the CPE

The service is a definition of configurations to be applied in the CPE once it wakes up.

Connection to the Controller / ACS

There are a few options for the CPE to connect to the remote manager:

• Controller configured in the CPE by the vendor at the fabric.
• CPE first connection to a default DHCP server and receive the server URL in an option.
• ISP manual configuration of the remote server

Choose the right partners

As you have probably already realized, the two main actors on this scenario are the CPE and the ACS/Controller vendors.
To ensure long-term support and no friction, you must pick up the vendors who support this kind of workflow and are willing to work hand-in-hand providing the best solution to enable ZTP and all other requirements — in the edge with the CPE and on the control plane with the ACS.