Single CPE Provisioning
1. Overview
This screen allows manual provisioning of a single CPE device through a guided, step-by-step interface.
2. Functionality and usage
2.1. Search
-
Select CPE ID type (Serial or MAC). Note that MAC refers to the MAC address in the CPE’s active WAN connection (not LAN interface). Enter CPE ID (Serial or MAC)
| Additional parameters might be used for search execution: “Product class” and “Manufacturer OUI”. When these values are used and combination exists in system configuration files (see Friendly TR69 Provision Portal Configuration for more details) – only relevant data will be displayed, otherwise all default data is displayed. |
| “Product class” and “Manufacturer OUI” parameters became mandatory in case “createDevice” parameter in “Configuration.xml” file is set to “true”, because these parameters are required for creation of pre-provisioned CPEs. |
| In order to processed correctly the data, that added to prov.db by MAC, make sure that the <retrieveMacAddressesOnNewDeviceArrive> flag is enabled in the ACS settings. |
-
Click Search to check if the CPE already exists in the provisioning DB – the data will be auto populated if it exists or will show fields with default values if the CPE is not in the provisioning DB.
-
Delete provision data button is used to clear existing CPE provision data from provision and production DB.
2.2. Device Info
-
For input of CRM related data to be associated with the CPE (e.g. Location, Telephone etc.). “Clear” button removes this data
2.3. Domain
-
Dropdown in “Device Info” area contains a full list of all Domains currently available in a system. It will be hidden in case enable attribute of <domain> in Configuration.xml file will be set to "false". This dropdown is mandatory
2.4. Provisioning Parameters
-
Service checkbox defines group/groups of parameters that will be sent upon “Submit” usage. If service checkbox is unselected, all related parameters will be excluded from procedure
-
Mandatory parameter input fields are highlighted in red until value is entered
-
Predefined parameter values displayed due to either default values specification in params.xml system configuration file or because corresponding entries are in provisioning DB
-
Parameters with values in drop down lists display an array of values, predefined in params.xml system configuration file
2.5. Provisioning Objects
-
Object checkbox defines objects and related parameters that will be sent upon “Submit” usage. If object checkbox is unselected, all related parameters will be excluded from procedure
-
Sub-object checkbox defines objects and related parameters that correspond to parent object which will be sent upon “Submit” usage.
-
Mandatory parameter input fields are highlighted in red until value is entered
-
Predefined parameter values displayed due to either default values specification in “params.xml” system configuration file or because corresponding entries are in provisioning DB
-
Parameters with values in drop down lists display an array of values, predefined in params.xml system configuration file
-
“Instance” defines object related instance and varies from 0 to 9. 0 value means that procedure will be performed according to standard TR069 protocol specification (for example if 1 “PortMapping” object already exists, next created similar object doesn’t necessarily get “next in line” instance number). In case of instance number set to specific value from 1 to 9, Portal will check if object with specified instance already exists and perform SET/UPDATE parameters to that particular object. If it doesn’t exist, Portal will try to create the new object with all related parameters (Due to TR-069 protocol limitation it is impossible to define the instance for new object)
-
When it is required to create object or sub-object with specific instance it is required to specify an object related parameter(s)
2.6. General Options
-
If a blank value needs to be sent to the CPE, use the $$ (literal characters)
-
Reprovision – select in case you want to set the provisioning values as recurring upon 0 BOOTSTRAP CPE event. Otherwise leave this checkbox unmarked to set the provisioning values as “one-time-only”
-
Secondary Provision – select in case you want to set the provisioning values as recurring upon 0 BOOTSTRAP CPE event without immediate creation of related tasks
| “Reprovision” and “Secondary Provision” are mutually exclusive options |
| It is not recommended to perform procedure with secondary provision for object which contains sub-object due to system limitations |
-
Delete previous – if selected, the provisioning system will delete any previous provisioning data for the CPE prior to sending the new values. Otherwise previous provisioning data will not be deleted. However, it may be overwritten if the same values already exist
-
Reboot – if selected, reboot will be performed on device before the end of provisioning process
-
Current only – if selected, all data previously added to Provision DB will be ignored and only currently specified data will be sent to CPE
-
Batch ID – Read-only value returned by ProvisioningForDevice as a reference identifier to this provisioning transaction. The Batch ID status can be viewed in the forth tab “Get status”
-
Submit – Activate the ProvisioningForDevice WS with the current values
| In case "createDevice" parameter in Configuration.xml file is set to "true" and current device was not found in production DB during search procedure, new pre-provisioned CPE will be created upon using "Submit" button. |