Applies to
Operator Open Access
Operator Single Provider
Service Provider
Contractor
Introduction
The Auto provisioning flow consists of three main steps, as shown below.
This guide helps troubleshoot errors that can occur in each of those steps and how to handle them. If you prefer to download a document with the content in this article, click here.
To enlarge the images, right click and select "Open in new tab".
Order status related to steps in provisioning and installation
Connection errors
The Connection errors occur when there is a failure in the process of connecting an ONT to an Object.
If you see an error in COS showing “the ONT has no connection to the OLT or is missing in the network”, this needs to be checked in the provisioning system/NMS. The ONT (or its OLT) cannot found in the provisioning system by Business Engine.
To enlarge the image, right click and select "Open in new tab".
Provisioning errors
The Provisioning errors occur when there is a failure in the process of provisioning the ONT.
To enlarge the image, right click and select "Open in new tab".
Provisioning - Configuration missing
If the message Provisioning configuration missing appears, possible reasons could be:
- New ISP but incorrectly configured (VLAN missing)
- New service added, but Network service missing.
- Incorrectly configured Service type.
Provisioning - Mismatch
If the Mismatch message appears, it means that the provisioning information in Business Engine does not match the data in the provisioning system/NMS.
After verifying, you can resend provisioning from BE to update the information.
Provisioning - Other Errors
