Status Codes Reference
1. Overview
Every step of a provisioning flow writes a status code. The flow writes the code to the DebugLog and to the status record of the CPE. For details, see Status Codes and Logs. The last code of a CPE is its final operation code. You see this code on the Get status tab.
The number of digits shows the type of a code:
-
A 3-digit code is a step. Some 3-digit codes are final success codes.
-
A 4-digit code is an error. The flow stops at the step with this code.
Code 1460 is the only exception. Code 1460 is a final success code of the ACS Event Flow. The Result column marks the final codes.
The descriptions below are the exact log texts.
Status.java defines the codes.
Each table lists the codes of one flow.
2. Input Flow
Codes of the Input Flow.
| Code | Description | Result |
|---|---|---|
108 |
Successfully called FTUpdateDeviceInfo |
|
110 |
At least one 'Info' record was found in provision DB |
|
112 |
No 'Info' records were found in provision DB |
|
113 |
At least one 'Parameter' record was found in provision DB |
|
114 |
No 'Parameter' records were found in provision DB |
|
151 |
Serial number was found in XML file |
|
157 |
At least one standalone service was found |
|
158 |
No standalone services were found |
|
159 |
Matching standalone services with params.xml successfully done |
|
160 |
No data for the CPE found in provision DB |
|
161 |
Serial number was found in provision DB |
|
163 |
Matching services and default parameters successfully done |
|
164 |
Parameters were successfully set |
|
165 |
Successfully called FTRPCInvoke |
|
166 |
Serial number wasn’t found in provision DB |
|
168 |
Successfully called FTRPCInvoke |
|
169 |
At least one 'Standalone service' record was found in provision DB |
|
170 |
No 'Standalone service' records were found in provision DB |
|
171 |
Previous records for SN were deleted from provision DB |
|
172 |
Matching standalone services with objects.xml successfully done |
|
173 |
At least one 'Object' record was found in provision DB |
|
174 |
No 'Object' records were found in provision DB |
|
175 |
Matching objects with objects.xml successfully done |
|
176 |
Provision DB was updated successfully |
|
177 |
SN added to relevant record of Status DB table |
|
178 |
At least one 'Object related parameter' record was found in provision DB |
|
179 |
Matching object related parameters with objects.xml successfully done |
|
180 |
Successfully called FTAddObject with related parameters. CPE is offline |
|
181 |
No 'Object related parameter' records were found in provision DB |
|
182 |
No object.xml related data for the CPE found in provision DB |
|
183 |
Matching objects with its related default parameters from objects.xml successfully done |
|
184 |
The first object was selected for processing |
|
185 |
Random instance identified |
|
186 |
Serial number was found in production DB |
|
187 |
Successfully called FTAddObject with related parameters |
|
189 |
Object was created and related parameters were set successfully |
|
190 |
Specific instance identified |
|
191 |
Serial number wasn’t found in production DB |
|
192 |
Successfully called FTSetDeviceParameters |
|
194 |
Specific instance exists, related parameter wes set successfully |
|
195 |
Specific instance may not exist, failed to set related parameters |
|
196 |
Provisioning process was completed successfully |
Success, final |
197 |
Successfully called FTAddObject |
|
199 |
Object was created successfully |
|
201 |
Successfully called FTRemoveCPEProvisionData |
|
204 |
The next object was selected for processing |
|
205 |
No objects left to process |
|
206 |
Searching for the CPE in ACS DB |
|
211 |
The CPE is offline |
|
212 |
No matching service(s) found in objects.xml |
|
213 |
No matching service(s) found in params.xml |
|
214 |
At least one matching service was found in objects.xml |
|
215 |
Successfully called FTCPEStatus |
|
216 |
'Product class' and 'OUI' were obtained successfully |
|
217 |
Matching parameters with params.xml successfully done |
|
219 |
At least one matching service was found in params.xml |
|
221 |
The CPE is online |
|
231 |
Successfully called FTSetDeviceParameters |
|
246 |
Provisioning process was completed successfully |
Success, final |
247 |
Provisioning process was completed successfully |
Success, final |
248 |
Provisioning process was completed successfully |
Success, final |
251 |
MAC address was found in XML file |
|
261 |
Provisioning process was completed successfully |
Success, final |
266 |
MAC address was found in provision DB |
|
271 |
MAC address wasn’t found in provision DB |
|
276 |
Previous records for MAC were deleted from provision DB |
|
286 |
Matched SN and MAC address in production DB |
|
291 |
No matching SN for MAC address found in production DB |
|
293 |
Successfully called FTSetDeviceParameters |
|
295 |
Specific instance related parameters were set successfully |
|
305 |
Successfully called FTAddObject with related parameters |
|
313 |
Successfully called FTRPCInvoke |
|
314 |
Provisioning process was completed successfully |
Success, final |
319 |
No 'Parameter' records were handled |
|
320 |
At least one 'Object' record was handled |
|
321 |
At least one 'Parameter' record was handled |
|
322 |
No 'Object' records were handled |
|
440 |
Send data only from XML ignoring provision DB |
|
441 |
Send data from XML and provision DB |
|
442 |
At least one 'Info' record was found in XML |
|
443 |
No 'Info' records were found in XML |
|
450 |
Send data only from XML ignoring provision DB |
|
451 |
Send data from XML and provision DB |
|
452 |
At least one 'Standalone service' record was found in XML |
|
453 |
No 'Standalone service' records were found in XML |
|
460 |
Send data only from XML ignoring provision DB |
|
461 |
Send data from XML and provision DB |
|
462 |
At least one 'Object' record was found in XML |
|
463 |
No 'Object' records were found in XML |
|
470 |
Send data only from XML ignoring provision DB |
|
471 |
Send data from XML and provision DB |
|
472 |
At least one 'Object related parameter' record was found in XML |
|
473 |
No 'Object related parameter' records were found in XML |
|
480 |
Send data only from XML ignoring provision DB |
|
481 |
Send data from XML and provision DB |
|
482 |
At least one 'Standalone service' record was found in XML |
|
483 |
No 'Standalone service' records were found in XML |
|
490 |
Send data only from XML ignoring provision DB |
|
491 |
Send data from XML and provision DB |
|
492 |
At least one 'Parameter' record was found in XML |
|
493 |
No 'Parameter' records were found in XML |
|
600 |
Domain not set |
|
601 |
Successfully called FTSetCpeDomain |
|
700 |
Successfully called FTCreateDevice |
|
800 |
There is no sub-objects for current object |
|
801 |
Sub-object was selected for processing |
|
802 |
There is no sub-objects for current object |
|
803 |
Sub-object was selected for processing |
|
804 |
Successfully called FTGetDeviceParametersByTransID |
|
805 |
Successfully called FTGetDeviceParametersByTransID |
|
806 |
There is no sub-objects for current object |
|
807 |
Sub-object was selected for processing |
|
808 |
Successfully called FTGetDeviceParametersByTransID |
|
1080 |
Failed to call FTUpdateDeviceInfo |
Error, final |
1500 |
Neither SN nor MAC were found in XML file |
Error, final |
1590 |
Failed to retrieve default parameter name(s) for matching standalone service(s) from params.xml |
Error, final |
1630 |
Failed to match at least one service and its default parameter |
Error, final |
1650 |
Failed to call FTRPCInvoke |
Error, final |
1680 |
Failed to call FTRPCInvoke |
Error, final |
1700 |
Database exception occurred |
Error, final |
1720 |
Failed to retrieve object name(s) for matching standalone service(s) from objects.xml |
Error, final |
1750 |
Mismatched at least one of the objects with objects.xml |
Error, final |
1770 |
Failed to add SN to relevant record of Status DB table |
Error, final |
1790 |
Mismatched at least one of the object related parameters with objects.xml |
Error, final |
1830 |
Mismatched at least one of the objects with its related default parameters from objects.xml |
Error, final |
1840 |
Failed to select the first object for processing |
Error, final |
1850 |
Failed to call FTAddObject with related parameters |
Error, final |
1880 |
At least one task is still pending, timed out |
Error, final |
1890 |
At least one task was failed or rejected |
Error, final |
1900 |
Failed to call FTSetDeviceParameters |
Error, final |
1930 |
At least one task is still pending, timed out |
Error, final |
1970 |
Failed to call FTAddObject |
Error, final |
1980 |
At least one task is still pending, timed out |
Error, final |
1990 |
Failed to create the object, at least one task was failed or rejected |
Error, final |
2010 |
Failed to call FTRemoveCPEProvisionData |
Error, final |
2150 |
Failed to call FTCPEStatus |
Error, final |
2160 |
Failed to obtain 'Product class' and 'OUI' |
Error, final |
2171 |
Mismatched at least one of the parameters with params.xml |
Error, final |
2310 |
Failed to call FTSetDeviceParameters |
Error, final |
2350 |
At least one task is still pending, timed out |
Error, final |
2460 |
At least one task was failed or rejected |
Error, final |
2930 |
Failed to call FTSetDeviceParameters |
Error, final |
2940 |
At least one task is still pending, timed out |
Error, final |
2950 |
Failed to set related parameters for specific instance |
Error, final |
3070 |
Cannot proceed specific instance with reprovision = 2 |
Error, final |
3130 |
Failed to call FTRPCInvoke |
Error, final |
5000 |
Failed to discover CPE online/offline status |
Error, final |
5001 |
Failed to retrieve tasks status |
Error, final |
5007 |
Cannot process specific instance for an offline CPE |
Error, final |
5008 |
Failed to retrieve tasks status |
Error, final |
5009 |
Failed to retrieve tasks status |
Error, final |
5010 |
Failed to retrieve tasks status |
Error, final |
5012 |
Failed to retrieve tasks status |
Error, final |
6010 |
Failed to call FTSetCpeDomain |
Error, final |
7000 |
Failed to call FTCreateDevice. OUI and ProductClass are required |
Error, final |
8040 |
Failed to call FTGetDeviceParametersByTransID |
Error, final |
8050 |
Failed to call FTGetDeviceParametersByTransID |
Error, final |
8080 |
Failed to call FTGetDeviceParametersByTransID |
Error, final |
3. ACS Event Flow
Codes of the ACS Event Flow.
| Code | Description | Result |
|---|---|---|
101 |
No objects left to process |
|
102 |
At least one standalone service was found |
|
103 |
No standalone services were found |
|
104 |
Matching standalone services with params.xml successfully done |
|
105 |
At least one 'Info' record was found in provision DB |
|
106 |
No 'Info' records were found in provision DB |
|
107 |
Successfully called FTUpdateDeviceInfo |
|
109 |
At least one 'Parameter' record was found in provision DB |
|
111 |
'Product class' and 'OUI' were obtained successfully |
|
115 |
Matching parameters with params.xml successfully done |
|
116 |
Successfully called FTSetDeviceParameters |
|
117 |
No data for the CPE found in provision DB |
|
118 |
Matching services and default parameters successfully done |
|
119 |
Successfully called FTSetDeviceParameters |
|
120 |
At least one 'Standalone service' record was found in provision DB |
|
121 |
No 'Standalone service' records were found in provision DB |
|
122 |
Matching standalone services with objects.xml successfully done |
|
123 |
At least one 'Object' record was found in provision DB |
|
124 |
No 'Object' records were found in provision DB |
|
125 |
Matching objects with objects.xml successfully done |
|
127 |
At least one 'Object related parameter' record was found in provision DB |
|
128 |
No 'Object related parameter' records were found in provision DB |
|
129 |
No object.xml related data for the CPE found in provision DB |
|
130 |
Matching object related parameters with objects.xml successfully done |
|
133 |
Matching objects with its related default parameters from objects.xml successfully done |
|
134 |
The first object was selected for processing |
|
135 |
Random instance identified |
|
136 |
No data for the CPE found in provision DB |
|
137 |
Successfully called FTAddObject with related parameters |
|
139 |
Object was created and related parameters were set successfully |
|
140 |
Specific instance identified |
|
141 |
MAC address was found in provision DB |
|
142 |
Successfully called FTSetDeviceParameters |
|
143 |
SN added to relevant record of Status DB table |
|
145 |
Specific instance exists, related parameters were set successfully |
|
147 |
Specific instance may not exist, failed to set related parameters |
|
148 |
Successfully called FTAddObject |
|
152 |
Object was created successfully |
|
156 |
The next object was selected for processing |
|
162 |
Serial number was found in provision DB |
|
167 |
Serial number wasn’t found in provision DB |
|
199 |
Object was created successfully |
|
207 |
At least one matching service was found in objects.xml |
|
208 |
No matching service(s) found in objects.xml |
|
218 |
No 'Parameter' records were found in provision DB |
|
224 |
At least one matching service was found in params.xml |
|
225 |
No matching service(s) found in params.xml |
|
238 |
Parameters were successfully set |
|
239 |
Successfully called FTRPCInvoke |
|
246 |
Provisioning process was completed successfully |
Success, final |
300 |
Successfully called FTSetDeviceParameters |
|
302 |
Specific instance related parameters were set successfully |
|
308 |
Successfully called FTAddObject with related parameters |
|
316 |
Successfully called FTRPCInvoke |
|
323 |
At least one 'Object' record was handled |
|
324 |
No 'Object' records were handled |
|
341 |
New device event received |
|
602 |
Domain not set |
|
603 |
Successfully called FTSetCpeDomain |
|
900 |
There is no sub-objects for current object |
|
901 |
Sub-object was selected for processing |
|
902 |
There is no sub-objects for current object |
|
903 |
Sub-object was selected for processing |
|
904 |
Successfully called FTGetDeviceParametersByTransID |
|
905 |
Successfully called FTGetDeviceParametersByTransID |
|
906 |
There is no sub-objects for current object |
|
907 |
Successfully called FTGetDeviceParametersByTransID |
|
908 |
Sub-object was selected for processing |
|
1040 |
Failed to retrieve default parameter name(s) for matching standalone service(s) from params.xml |
Error, final |
1070 |
Failed to call FTUpdateDeviceInfo |
Error, final |
1110 |
Failed to obtain 'Product class' and 'OUI' |
Error, final |
1150 |
Mismatched at least one of the parameters with params.xml |
Error, final |
1160 |
Failed to call FTSetDeviceParameters |
Error, final |
1180 |
Failed to match at least one service and its default parameter |
Error, final |
1190 |
Failed to call FTSetDeviceParameters |
Error, final |
1220 |
Failed to retrieve object name(s) for matching standalone service(s) from objects.xml |
Error, final |
1250 |
Mismatched at least one of the objects with objects.xml |
Error, final |
1300 |
Mismatched at least one of the object related parameters with objects.xml |
Error, final |
1330 |
Mismatched at least one of the objects with its related default parameters from objects.xml |
Error, final |
1340 |
Failed to select the first object for processing |
Error, final |
1370 |
Failed to call FTAddObject with related parameters |
Error, final |
1380 |
At least one task is still pending, timed out |
Error, final |
1390 |
At least one task was failed or rejected |
Error, final |
1420 |
Failed to call FTSetDeviceParameters |
Error, final |
1440 |
At least one task is still pending, timed out |
Error, final |
1460 |
Provisioning process completed successfully |
Success, final |
1480 |
Failed to call FTAddObject |
Error, final |
1490 |
At least one task is still pending, timed out |
Error, final |
1520 |
Failed to create the object, at least one task was failed or rejected |
Error, final |
2370 |
At least one task is still pending, timed out |
Error, final |
2380 |
At least one task was failed or rejected |
Error, final |
2390 |
Failed to call FTRPCInvoke |
Error, final |
3000 |
Failed to call FTSetDeviceParameters |
Error, final |
3010 |
At least one task is still pending, timed out |
Error, final |
3020 |
Failed to set related parameters for specific instance |
Error, final |
3090 |
Cannot proceed specific instance with reprovision = 2 |
Error, final |
3160 |
Failed to call FTRPCInvoke |
Error, final |
5002 |
Failed to add SN to relevant record of Status DB table |
Error, final |
5003 |
Failed to retrieve tasks status |
Error, final |
5004 |
Failed to retrieve tasks status |
Error, final |
5005 |
Failed to retrieve tasks status |
Error, final |
5013 |
Failed to retrieve tasks status |
Error, final |
6030 |
Failed to call FTSetCpeDomain |
Error, final |
9040 |
Failed to call FTGetDeviceParametersByTransID |
Error, final |
9050 |
Failed to call FTGetDeviceParametersByTransID |
Error, final |
9070 |
Failed to call FTGetDeviceParametersByTransID |
Error, final |
4. Deactivate Service Flow
Codes of the Deactivate Service Flow.
| Code | Description | Result |
|---|---|---|
501 |
Serial number was found in XML file |
|
502 |
MAC address was found in XML file |
|
503 |
At least one service was found in XML |
|
504 |
At least one service was found in XML |
|
505 |
Serial number was found in provision DB |
|
506 |
MAC address was found in provision DB |
|
507 |
Matching service(s) record(s) for SN were deleted from provision DB |
|
508 |
SN was found in production DB |
|
509 |
SN and MAC match found in production DB |
|
510 |
Matching service(s) record(s) for MAC were deleted from provision DB |
|
511 |
SN wasn’t found in production DB |
|
512 |
SN and MAC match not found in production DB |
|
513 |
Service(s) deactivation process was completed successfully |
Success, final |
514 |
Service(s) deactivation process was completed successfully |
Success, final |
515 |
'Product class' and 'OUI' were obtained successfully |
|
516 |
Matching service(s) with params.xml successfully done |
|
517 |
Successfully called FTSetDeviceParameters |
|
518 |
The CPE is online |
|
519 |
The CPE is offline |
|
520 |
At least one related task is pending, waiting for its completion |
|
521 |
Parameters were successfully set |
|
522 |
Service(s) deactivation process was completed successfully |
Success, final |
523 |
Service(s) deactivation process was completed successfully |
Success, final |
524 |
'Product class' and 'OUI' were obtained successfully |
|
5100 |
SN or MAC wasn’t found in XML file |
Error, final |
5103 |
No service(s) found in XML |
Error, final |
5104 |
No service(s) found in XML |
Error, final |
5105 |
SN wasn’t found in provision DB |
Error, final |
5106 |
MAC address wasn’t found in provision DB |
Error, final |
5107 |
Failed to delete matching service(s) record(s) for SN from provision DB |
Error, final |
5110 |
Failed to delete matching service(s) record(s) for MAC from provision DB |
Error, final |
5111 |
Failed during FTFindCPEByWANMAC call |
Error, final |
5112 |
Failed during FTFindCPEByWANMAC call |
Error, final |
5115 |
Failed during FTGetDeviceInfo call |
Error, final |
5116 |
Failed to retrieve parameter name(s) for matching service(s) from params.xml |
Error, final |
5117 |
Failed during FTSetDeviceParameters call |
Error, final |
5118 |
Failed to retrieve tasks status |
Error, final |
5119 |
At least one task is still pending, timed out |
Error, final |
5121 |
At least one task was failed or rejected |
Error, final |
5. Replace CPE Flow
Codes of the Replace CPE Flow.
| Code | Description | Result |
|---|---|---|
400 |
FromCPE found in provision DB |
|
401 |
ToCPE found in provision DB |
|
402 |
ToCPE not found in provision DB |
|
403 |
Previous records for ToCPE were deleted from provision DB |
|
404 |
ToCPE was found in production DB |
|
405 |
ToCPE is online |
|
406 |
ToCPE wasn’t found in production DB |
|
407 |
Successfully cleared provision manager of ToCPE |
|
408 |
Data retrieval for FromCPE from provision DB successfully done |
|
409 |
Relevant customization section is found in Replace_CPE.xml |
|
410 |
Relevant customization section isn’t found in Replace_CPE.xml |
|
411 |
Successfully matched and replaced data from provision DB based on Replace_CPE.xml |
|
412 |
No provision DB data matches relevant customization section of Replace_CPE.xml |
|
413 |
Successfully formed a data package for ProvisioningForDevice flow execution |
|
415 |
ProvisioningForDevice flow executed successfully |
|
416 |
Previous records for FromCPE were deleted from provision DB |
|
417 |
FromCPE was found in production DB |
|
418 |
Successfully cleared provision manager of FromCPE |
|
419 |
Successfully cleared account information of FromCPE |
|
420 |
FromCPE is offline. Process completed successfully |
Success, final |
421 |
FromCPE is online |
|
422 |
Successfully called FTRPCInvoke to factory reset FromCPE |
|
424 |
FromCPE successfully restored to default configuration |
Success, final |
426 |
Matched SN and MAC address of ToCPE in production DB |
|
427 |
No matching SN for MAC address of ToCPE found in production DB |
|
428 |
Matched SN and MAC address of FromCPE in production DB |
|
429 |
No matching SN for MAC address of FromCPE found in production DB |
Success, final |
430 |
FromCPE was’t found in production DB |
Success, final |
431 |
Successfully cleared account information of ToCPE |
|
4000 |
FromCPE isn’t found in provision DB |
Error, final |
4001 |
Failed to access provision DB |
Error, final |
4010 |
ToCPE isn’t found in provision DB |
Error, final |
4030 |
Failed tp delete previous records for ToCPE from provision DB |
Error, final |
4040 |
Failed to locate ToCPE in production DB |
Error, final |
4050 |
ToCPE is present in production DB and offline |
Error, final |
4051 |
Failed to discover ToCPE online/offline status |
Error, final |
4070 |
Failed to cleared provision manager of ToCPE |
Error, final |
4080 |
Data retrieval for FromCPE from provision DB failed |
Error, final |
4130 |
Failed to form a data package for ProvisioningForDevice flow execution |
Error, final |
4150 |
Failed to execute ProvisioningForDevice flow |
Error, final |
4160 |
Failed to delete previous records for FromCPE from provision DB |
Error, final |
4180 |
Failed to clear provision manager of FromCPE |
Error, final |
4190 |
Failed to clear account information of FromCPE |
Error, final |
4220 |
Failed to call FTRPCInvoke to factory reset FromCPE |
Error, final |
4230 |
Failed to call FTGetTransactionStatus |
Error, final |
4231 |
At least one task is still pending, timed out |
Error, final |
4240 |
At least one task was failed or rejected |
Error, final |
4260 |
Failed to matched SN and MAC address of ToCPE in production DB |
Error, final |
4280 |
Failed to matched SN and MAC address of FromCPE in production DB |
Error, final |
4310 |
Failed to clear account information of ToCPE |
Error, final |
6. Codes Not Written by Any Flow
Status.java defines these codes.
No flow writes them.
The logs and the Get status tab never show these codes.
The Replace CPE diagram shows 423, 4110 and 4200.
No diagram shows the other codes.
| Code | Description |
|---|---|
138 |
At least one task is pending, waiting for its completion |
144 |
At least one task is pending, waiting for its completion |
149 |
At least one task is pending, waiting for its completion |
154 |
At least one task is pending, waiting for its completion |
188 |
At least one task is pending, waiting for its completion |
193 |
At least one task is pending, waiting for its completion |
198 |
At least one task is pending, waiting for its completion |
202 |
At least one task is pending, waiting for its completion |
235 |
At least one task is pending, waiting for its completion |
237 |
At least one task is pending, waiting for its completion |
294 |
At least one task is pending, waiting for its completion |
301 |
At least one task is pending, waiting for its completion |
414 |
ProvisioningForDevice flow execution completed |
423 |
At least one task is pending, waiting for its completion |
4110 |
Failed to match and replace data from provision DB based on Replace_CPE.xml |
4200 |
Failed to discover FromCPE online/offline status |