Broadband

Command Center
Troubleshooting Device
Provisioning

incognito.com
© 2013 Incognito Software Inc. All rights reserved.
Incognito is a registered trademark of Incognito Software Incorporated. Address Commander, Auto Configuration Server,
Broadband Command Center, Central Licensing Service, FastFlow BPM, Incognito Configuration File Manager Service,
Incognito Configuration File Manager Proxy Service, Incognito CWMP Service, Incognito DHCP Service, Incognito DNS
Service, Incognito Management Console, Incognito KDC Service, Incognito KDC Wrapper Service, Incognito Multimedia
Provisioning Service, Incognito TFTP Service, Incognito Web Management Console, Java Incognito Management Console,
Name Commander, Network Discovery Probe, Network Resource Commander, Service Activation Center, User Management
Service, and the Incognito Software logo are trademarks of Incognito Software Incorporated. All other trademarks are the
property of their respective owners.

No parts of this work may be reproduced in any form or by any means without the written permission of the publisher.
While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility
for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of
programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or
any other commercial damage caused or alleged to have been caused directly or indirectly by this document.

Incognito Software Inc., 375 Water Street, Suite 500, Vancouver, BC, Canada, V6B 5C6.
This product contains software developed by the Apache Software Foundation (http://www.apache.org/) and the OpenSSL
Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
TRADEMARKS:
CableLabs and DOCSIS are trademarks of Cable Television Laboratories, Inc.
CORBA is a registered trademark of Object Management Group, Inc. in the United States and/or other countries.

Debian is a registered trademark of Software in the Public Interest, Inc.

DRBD is a registered trademark of LINBIT® in Austria, the United States, and other countries.
Intel, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and other countries.
Linux is a registered trademark of Linus Torvalds.
Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.
Oracle, Java, MySQL, Open JDK, and SQL*Plus are trademarks or registered trademarks of Oracle and/or its affiliates.
PostgreSQL is a registered trademark of the PostgreSQL Global Development Group.
RabbitMQ is a registered trademark of VMware Inc. in the United States and/or other jurisdictions.
Red Hat and Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries.
SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries.

TAO and ACE are registered trademarks of Washington University.

UNIX and X Window System are registered trademarks of The Open Group.
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 1

Contents

1. Device Provisioning .................................................................................................................... 2

1.1. Introduction .......................................................................................................................... 2
2. Isolate Where in the Process the Failure Occurs ........................................................................ 3
2.1. Is the DHCP Service Receiving a DHCP:Discover? ........................................................... 3
2.2. Is the DHCP Service Sending Back an Offer?..................................................................... 4
2.3. Is the DHCP Service Receiving a DHCP:Request? ............................................................. 4
2.4. Is the DHCP Service Sending Back an ACK? ..................................................................... 5
2.5. CPE Fails to Come Online ................................................................................................... 5
3. Cable Modem Provisioning Issues.............................................................................................. 6
3.1. Is the Device Requesting a TFTP Download? ..................................................................... 6
3.2. Is the Download Failing? ..................................................................................................... 8
3.3. File Transfer Completes, but Device Fails to Come Online ................................................ 8
4. MTA Provisioning Issues ........................................................................................................... 9
4.1. CM Portion of eMTA Fails to Come Online ....................................................................... 9
4.2. Modem Portion of eMTA Online, but MTA Portion Fails .................................................. 9
4.3. MTA Completes, Sends PASS, but Fails to Contact CMS ............................................... 11
4.4. MTA Completes Provisioning, No Dial Tone when Off-Hook ......................................... 12
4.5. Euro Devices ...................................................................................................................... 12
5. DNS Troubleshooting ............................................................................................................... 13
5.1. DNS Slow to Resolve Queries ........................................................................................... 13
5.2. Provisioned Devices are not added to the DNS ................................................................. 13
5.3. Configuring DDNS on the DHCP and MP Services ......................................................... 14
6. Appendix A: Incognito Error Codes ........................................................................................ 15
6.1. DHCP Service API Error Codes ........................................................................................ 15
6.2. DNS Service API Error Codes ........................................................................................... 16
6.3. CFM Service API Error Codes .......................................................................................... 19
6.4. 6.3 TFTP Service API Error Codes ................................................................................... 19
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 2

1. Device Provisioning

1.1. Introduction

There are quite a number of different messages exchanged between a cable modem or MTA and
the BCC services during the provisioning process.

For all devices obtaining a lease via DHCP:

 At least 4 DHCP packets (DISCOVER, OFFER, REQUEST, ACK)

For cable modems:

 At least 3 TFTP packets (RRQ, DATA, ACK)

 Typically 2 TOD packets (request, response)

For MTAs:

 A number of DNS packets (resolve MPS, resolve Kerberos realm, resolve KDC)
 4 Kerberos packets with the KDC (if using secure provisioning flow)
 2 Kerberos packets with the MPS (if using secure provisioning flow)
 2 or more SNMP packets with the MPS (Enrollment Inform, Get, Set, Status Inform)

A failure can occur at any point in the provisioning sequence.

 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 3

2. Isolate Where in the Process the Failure Occurs

The first thing to do is to try and figure out where in the provisioning process the failure is
occurring.

 If many devices are affected, choose one to troubleshoot. It is likely the same problem
affecting all the devices, if you solve the problem for one device, you have likely solved
it for all. You must use Level 3 (debug) logging on the service, as this will show the
most information.
 If you are using a syslog service, see if the cable modem or MTA is reporting anything
useful in its syslog messages. The device might tell you what the problem is.
 Use a LAN sniffer to watch network traffic being exchanged with the device:
o For example, if the device is cycling, what packets are being sent before the
device stops and restarts the provisioning process?

2.1. Is the DHCP Service Receiving a DHCP:Discover?

If not:

 Is the CMTS showing the proper modem state i.e. the Discover has been sent to the
DHCP?
 Is the CMTS/relay-agent properly configured with the IP Address of the DHCP service
(IP Helper address), so it knows where to forward broadcasted Discovers?
 Can the CMTS/relay agent communicate properly with the DHCP service?
o Can you ping the address of the DHCP (IP Helper) from the CMTS?
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 4

2.2. Is the DHCP Service Sending Back an Offer?

If not:

 Check the level 3 log file to see how the service is processing the packet.
 Are any rules failing unexpectedly?
o ‘Is the Rule Criteria for those rules correct?
 ‘Non-local relay’ typically means a missing or incorrect Routing Element
entry connecting the GIADDR and the available rule ranges.
 ‘IP Limit reached’ means that IP Limiting has been enabled on a Rule or
Client Class provisioning this device.
 ‘No available IPs’ means the Rule is full. Check for available IPs in the
expected rule.

If so:

 Is the CMTS receiving the Offer?

 Is the CMTS broadcasting the Offer to the client?

2.3. Is the DHCP Service Receiving a DHCP:Request?

If not:

 Is the CMTS showing the proper modem state i.e. the Offer has been returned to the
client?
 If the CMTS is showing no signs of relaying the Offer, check the routing tables on both
the CMTS and DHCP service – there may be a routing issue.
o Can you ping the GIADDR (displayed in the incoming DHCP:Discover packet)
from the DHCP?
 Did the DHCP service send back values for all the options the device requested?
o In the case of a cable modem:
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 5

 The CTMS may simply drop the packet if DHCP Option 66:TFTP Server
Name is missing
 The modem may ignore the Offer if DHCP Option 7:Log Server is
missing (although the log server does not need to be configured and
listening)
 Some eMTA cable modems will not accept the lease Offer if neither 122.1
or 177.1 is included (the address of the DHCP service that the MTA will
accept a lease from).
o In the case of an MTA, the DHCP service must send:
 DHCP Option 122:3 Provisioning Server FQDN
 DHCP Option 122.6 or 177.6 (additional provisioning flow information)
 The device may ignore the Offer if DHCP Option 7:Log Server is missing
(although the log server does not need to be configured and listening)

2.4. Is the DHCP Service Sending Back an ACK?

If not:

 The DHCP service should give a reason as to why an ACK is not sent back.
 For renewals, we may not send back an ACK if:
o IP shuffling is enabled
o The service configuration was changed such that this device is now denied the IP
it had previously and is now trying to renew (“trying to renew someone else’s
lease”)

2.5. CPE Fails to Come Online

With CPEs (host devices), provisioning is much simpler, but there are still a number of things
that may cause a failure of the device to come online:

 Routing issues between the CMTS and DHCP

 CMTS misconfiguration
o Is the CMTS inserting the expected GIADDR in the CPE packets?
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 6

o Is the CMTS inserting the cable modem remote ID in the CPE packets (DHCP
option 82: Relay Agent Information)?
 Missing DHCP options (gateway [3], DNS services [6])
 The problem may actually be on the cable modem
o Is the modem blocked? (the Network Access value set to disabled)
o Is there a service flow created for default traffic in the DOCSIS configuration
file?
o Is IP spoofing prevention enabled? If so:
 Does the CPE have a Remote ID, or a mapping to a cable modem
configured on the DHCP service?
 Does the cable modem’s CPE table show the CPE IP address?
o Is IP limiting on?
 Does this CPE bring the number of devices behind that Remote ID over
the limit?
 Check to see if there are leases behind that Remote ID that are no longer
active (i.e., try pinging them). It could be that a device was taken offline
without sending a Release message to the DHCP service.
o MAX-CPEs, TLV18
 The value of TLV 18 may be too low. Check the value that is being sent
to the cable modem. Bear in mind that if using an eMTA, this counts for
one CPE.

3. Cable Modem Provisioning Issues

3.1. Is the Device Requesting a TFTP Download?

Both cable modems and MTAs should request a configuration file from a CFMProxy service.
Locate the lease object under Active IP Addresses for the rule the IP address was offered from,
and inspect the DHCP options sent to the cable modem. This will identify the CFMP service that
the download should be attempted from. Inspect debug level logs on that CFMP service. There
should be a record of a download attempt from that device’s IP address.
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 7

If not:

 There may be a routing issue that prevents the device from communicating with the
CFMP service.
o Check the DHCP Option 3:Gateway sent to the device.
o Check the routing table on the TFTP service.
o Can you traceroute to the client’s subnet from the server running the CFMP
service?
o Can you traceroute to the CFMP service from the device’s subnet?
o Check the Load Balanced Public Interface in the Multicast Integration container.
This is the IP the clients are attempting to reach.
 Is there a firewall between the clients and the CFMP service?
o Check that port 69 (UDP and TCP) are open to the clients
o Define the Client TFTP Transfer Ports under Protocol Services on the CFMP
service, and open these ports in the firewall. These ports are for the UDP protocol.
 Is the right interface (or all interfaces) bound under Configuration  Service
Configuration  Advanced Options  Protocol Interfaces?
 Are there any proxy servers between the client and the CFMP service, such as the CMTS
making a request to the CFMP service and then relaying it to the device?
o Certain installations, where a device proxies between the real client and the
CFMP service, change the source IP to the proxy's IP instead of the actual client's
IP. This causes dynamic DOCSIS file generation to fail the download stage, since
the client IP is included in the filename hash and must match the source IP of the
request.
 Enable the checkbox for Disable IP Verification for Dynamic DOCSISF
Files, located within the CFM service, Configuration  Service
Configuration  Dynamic Configuration File Generator. This parameter
disables the verification of the incoming source IP against the client
device IP embedded in the filename.
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 8

3.2. Is the Download Failing?

If the download is attempted, it will be logged at the debug level in the CFMP logs.

If the download fails:

 Is the file being downloaded a static (non-generated) file, and if so, does it exist in the
proper path on the local server?
 Is a DOCSIS TLV being included more times than it should be allowed?
o If so, set Ignore parameter count limit reached error under Dynamic
Configuration File Generator on the CFM service.
 Is there a CMTS record configured on DHCP for the GIADDR this device is using?
o Is the Shared Secret correct?
 Are there any mandatory DOCSIS TLVs missing?
 Are the CFM and CFMP services properly synchronized with the DHCP service?
o You may get errors such database lookup keys or DHCP ID not able to be found
in this case. If so, restart the CFM service to force a resynch of all databases.
 Are any definitions within the MTA configuration file missing?
 Any other lines that are tagged with [ERROR] or [WARN ] in the CFM or CFMP high
level logs?

3.3. File Transfer Completes, but Device Fails to Come Online

In such cases, there is likely a problem in the configuration file. If the device logs to a syslog
server, or has an internal log that can be viewed, these are helpful in determining the problem.

 Is the CMTS Message Integrity Check invalid?

o Be sure that the Shared Secret (authorization key) configured for the CMTS
Routing Element record on the DHCP service matches what is configured on the
CMTS.
 Some cable modem TLV configuration options missing or causing problems?
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 9

o If the downstream frequency is set in the configuration, is this a frequency that the
CMTS is configured to listen on?
o Review the high level CFM logs to see which DOCSIS File Settings are being
used to generate the file, and review the contents of these file settings.
o Is the Network Access set to disabled when it should not be?
o Configure the CFM service to write generated files to disk (using the option in
Dynamic Configuration File Generator Settings) and inspect the file with a
DOCSIS File Viewer utility.

4. MTA Provisioning Issues

4.1. CM Portion of eMTA Fails to Come Online

 The modem obtains a lease and downloads its configuration file, then repeats this process
every 10-20 seconds
o The Authorization Key entered in the CMTS Settings container of the DHCP
must match the <cable shared-secret "XXXXXXXX"> shown in the running-
config of the CMTS. The CMTS will show this modem in the ‘reject (m) state,
however it is difficult to catch it on the CMTS since the device is constantly
rebooting.
o The TLVs in the CM configuration file are incorrect (e.g. check that TLV 3 is
included and set to “Has Access”).
o There may be too many TLVs. Some devices have a limit.

4.2. Modem Portion of eMTA Online, but MTA Portion Fails

 Check the Address State in the General Information tab of the lease:
o If it is Offered; the DHCP options offered to the device are incomplete or
incorrect.
 For example option 122.1 (or 177.1). The IP address of the Primary DHCP
service for the MTA to obtain a lease from must be included in the CM
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 10

lease options. Optionally, 122.2 (or 177.2) may also be required – this is
the IP address of the Secondary DHCP service.
 If Primary DHCP IP address is 0.0.0.0 the MTA is effectively disabled
o If it is Active; Ping the modem IP address of the eMTA. If it does not respond
check the DHCP Options returned to the modem portion of the device.
 Check the DHCP Options assigned to the MTA by either finding the device by MAC
address in the Active IPv4 Addresses, or review the Lease tab under the rule that assigned
the MTA its lease. The following options should be present:
o Option 122.3 (or 177.3) – The provisioning server information entered as:
 A Fully Qualified Domain Name for PKTC devices
o Option 122.6 (or 177.6) – the provisioning service flow to be used. (122.6
requires the Kerberos Realm name if using SECURE flow)
o Option 6 – the IP address of a DNS service that will be able to resolve the FQDN
given in Option 122.3 (or 177.3)
o Option 7 – the Log Server is mandatory for some devices, even though the actual
IP listed does not need to be active.
 Check the DNS logs to insure the MTA is requesting and obtaining the correct IP address
for the MPS (DHCP Option 122:3)
 Check the MPS high level logs to insure the service is receiving an SNMP GET request
for configuration.
o If not, use a sniffer to verify that the GET is actually reaching the MPS server
 If yes, another service has bound port 162 before the MPS service started.
 Check the high level logs on the CFMP server to verify that the modem is requesting and
successfully downloading the correct file.
o The IP address of the CFMP service that is provided to the MTA (via SNMPSet)
is determined by the FQDN defined in the CFMP service’s Multicast
configuration. If a FQDN, there should be a DNS service provided to the MTA
(Option 6) that is able to resolve this to an IP address.
o Note that some MTAs will only work with an IP address in the Multicasting
FQDN field.
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 11

 Verify that there is a route between the CFMP server and the MTA (e.g. ‘tracert <MTA
ip address>’. It is possible for the MTA to find the CFMP service while the reverse route
is not properly configured. Add a static route to the CFMP server if necessary.
o Check the high level MPS logs for an SNMP PASS received from the MTA (note
this requires BASIC.2 or HYBRID.2 or SECURE). If the MTA has reported an
SNMP “PASS” to the MPS service the BCC provisioning is completed.
o Verify that SNMP filters or other MIB settings from the cable modem
configuration file are not blocking MTA DHCP traffic (and/or SNMP access)
from the provisioning service. Remove all TLV 11 objects, generate a new
modem configuration file and reboot the modem; then verify that the modem
comes online, SNMP access to it is supported, and the MTA DHCP traffic now
reaches the DHCP service
 The MPS must tell the device the FQDN of the TFTP service:
o Do the high level MPS logs show this correctly?
o Do the high level DNS logs show the query? If not:
 Is the correct DHCP Option 6: Name Server returned to the MTA?
 Try entering the FQDN as an IP address in the Multicasting container of
the CFMP Service. This is how the MPS learns where the CFMP is, and
some MTAs will not perform the PacketCable mandated DNS lookup
from FQDN to IP address.
o The MTA configuration must include the FQDN of the CMS.
o The CMS hostname must be resolved in the DNS returned as DHCP Option 6 to
the MTA.

4.3. MTA Completes, Sends PASS, but Fails to Contact CMS

Typically Incognito support ends at this point, since the provisioning of the devices is the
responsibility of BCC. However, these are a few things to consider:

 Ensure that the proper FQDN has been entered in the MTA configuration file
 Ensure that the FQDN of the CMS has been entered in the DNS, so that name resolves
properly and the MTA can find the IP address of the CMS
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 12

 Ensure that the CMTS knows a valid route to the CMS

 Ensure the ranging frequency and/or timing has been set correctly on the CMTS
 If the object pktcMtaDevCmsIpsecCtrl is included in the configuration file with the value
set to true (PKTC-MTA-MIB pktcMtaDevCmsIpsecCtrl[BX.SAT.DM] = 1), then an
IPSec tunnel MUST be established between the MTA and the CMS. This includes the
MTA sending a Kerberos AP request to the CMS, and the CMS replying with an AP
reply.
 Placing a sniffer between the MTA and the CMS can debug MTA to CMS
Communications. Verify that the MTA is sending RSIP (RestartInProgress) messages
(NCS signalling) to the CMS, and the CMS is responding.

4.4. MTA Completes Provisioning, No Dial Tone when Off-Hook

 MTA devices play a dial tone automatically; this does not require any communication
with the CMS. The MTA configuration file should have all the information the MTA
needs to produce a dial-tone. Therefore, check the configuration options sent to the MTA.
 Sometimes a phone line is simply 'dead' within the phone itself. Enable both lines on the
MTA through the configuration file and check both lines. The second line will use the
same configuration as the first line, except that it will be #10 (instead of #9).

4.5. Euro Devices

The trick is to deal with its 'native' mode, which is determined when it is ordered from Motorola.
Query for the firmware load and the value will end in one of the following suffix values:

 PC = packetcable
 SF = Single file
 NP = 'no packetcable'
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 13

The device MUST be brought up in its 'native' mode first, and then it can be reconfigured for the
mode you wish to run it in.

Incognito Services do not support SF (single file) in dynamic mode – Single File means use a
static file. If the "native" mode happens to be SF and if that means that eMTA will try to boot up
in SF mode, then a static file must be used and that static file should then have the necessary
upgrade information to switch the eMTA into either PC or NP modes.

5. DNS Troubleshooting

5.1. DNS Slow to Resolve Queries

 Cache may be disabled - This means that the service must send every non-local lookup
for referral, every time. Enable the cache and increase the size to 50,000 (if you have
1/4GB of RAM in the server). Then the first lookup of any record may be slow; however
if you repeat the same lookup it will be much faster as the service will not have to
perform additional queries across the network.

5.2. Provisioned Devices are not added to the DNS

In order for Dynamic DNS to work properly, such that provisioned devices are automatically
added to a domain on a DNS service, check the following on the DNS service:

 Under Service Configuration  Transfer, the box for Allow dynamic updating (DDNS)
should be checked and the box Incremental Transfer should be set to Incoming only.
 Each domain that is going to have records manipulated via Dynamic DNS should be
configured to allow DDNS updates from a particular source.
o Locate the primary domain under Domains and select it.
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 14

o Select the Notify & DDNS Sources tab. Add the IP Addresses of the servers that
will be sending DDNS updates to the Dynamic DNS Sources box – typically, this
will just be your DHCP servers (both primary and secondary).
o Click Apply.

5.3. Configuring DDNS on the DHCP and MP Services

Either the MPS or the DHCP Service may be configured to create FQDNs for MTA devices.
Note that configuring the MP Service to provide this feature will override the settings in DHCP
Rules and Client classes. The MPS will actually create a static Devices record for each device
which will have a network settings template attached with the configuration information to set up
the hostname, domain name, and DNS service to update. Normally, it is better to allow the
DHCP to handle this.

The DHCP Services requires at least the following options in the relevant Network Settings
Template:

 Option 12:Hostname – add at least 2 masks since each hostname must be unique
 Option 15:Domain Name – the domain to update
 The IP address of the DNS service to update (this is in the General tab of the template)

The MPS requires:

 The Service Configuration flag set to “Provision MTA FQDNs” service-wide.

 Each MTA added to the service must include a FQDN. Since the MPS overrides DHCP
in this evaluation process, excluding this entry will cause DDNS to fail.
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 15

6. Appendix A: Incognito Error Codes

6.1. DHCP Service API Error Codes

Error Code Description

2 The object (template, rule, lease, etc.) you are trying to access does not exist.
17 The object (template, rule, lease, etc.) you are trying to create/add already exists.
22 A parameter you entered is either out of range or invalid.
2100 Wrong service category.
2101 Wrong serial version.
2102 Wrong product version.
2103 Internal error.
2104 Demo copy has expired.
2105 License is ok.
2106 License is now under warning.
2107 License is now above warning level.
2108 Licensing library not initialized.
2109 Invalid key.
2110 Wrong product number.
2111 Serial number given does not match.
2112 Serial file not found.
2113 Option is valid
2114 Option is not valid.
2115 Bad option number.
29000 Modifications may not be made to a secondary server. You must make your
changes on the primary server.
29001 The API is no longer supported.
29002 All objects must have a name.
29003 Duplicate name: you already have an object with this name!
29006 Duplicate Hardware Mapping: a hardware mapping already exists for the
specified client.
29007 This action would create a relationship loop.
29008 You may not modify a Static Address that has an active lease associated with it.
29010 This modification would place this rule or static address outside of the IP Range
of its parent rule.
29011 LDAP update failed: the record has expired.
29012 Failed to connect to the LDAP service.
29013 Failed to initialize the LDAP session.
29014 Failed to add a record to the LDAP service.
29015 Failed to update a record on the LDAP service.
29016 Failed to delete a record from the LDAP service.
29017 Failed to clear all records from the LDAP service.
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 16

29018 LDAP update failed: maximum number of update retries exceeded.

29019 LDAP operation is DISABLED. Please enable LDAP operation first.
29020 Another LDAP operation is in progress. Please try again.
29021 Unable to initialize SNMP communications.
29022 Specified device is not a DOCSIS Cable Modem.
29023 Device refused SNMP communications.
29024 The object does not exist.
29025 This object already exists.
31800 The specified event trigger ID was invalid.
31801 The specified category ID was invalid.
31802 The specified target file is not an in-memory target file. All in-memory target files
must have a '.dll' extension (windows dynamic link library) or a '.so' extension
(unix shared object).
31803 The in-memory target file failed to load.
31804 An error occurred updating the event trigger database.
31805 An error occurred accessing the event trigger database.
31806 A trigger is already configured for the specified event.
31807 Access Denied.
31900 Access denied: the user's password must be reset
31901 Unsupported encryption method.
31902 Invalid password.
31903 The record could not be found in the database and may have been deleted.
31904 The login session could not be found and may have already expired, logged out or
been deleted
31905 Access denied: only account administrators and super users can perform this
operation
31906 Access denied: only super users can configure other super user accounts
31907 Access denied: the 'Administrator' account cannot be deleted or demoted from
super user access
31908 Access denied: the 'Administrator' account cannot have its login name modified
31909 That user already exists in the system.
31910 Access denied: only users given the service control attribute can perform this
function.

6.2. DNS Service API Error Codes

Error Code Description

29201 No configuration
29202 Access denied
29203 No permission
29204 Resource record not found
29205 Database not found
29206 Index not found
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 17

29207 Database open failed

29208 Database creation failed
29209 Invalid server name
29210 Invalid postmaster
29211 Domain does not exist
29212 File not created
29213 Resource record not added
29214 Resource record index not added
29215 Resource record not deleted
29216 Object is read only
29217 Zone not added
29218 Zone not updated
29219 Resource record not updated
29220 Import failed
29221 Key not found
29222 Database creation in progress
29223 Deletion failed
29224 Invalid
29225 Zone transfer failed
29226 Zone already exists
29227 Resource record already exists
29228 Zone alias already exists
29229 Delete DDNS RR failed
29230 Can't find zone alias
29231 Zone does not exist
29232 RR security not exist
29234 Maximum zones reached; limit must be increased
29236 Zone environment variable does not exist
29237 Zone environment variable already exists
29238 Database write error
29239 Database delete error
29240 Database read error
29241 No more entries
29242 RPC not implemented
29243 UID not found
29244 Zone already exists with that alias name
29245 Alias already exists with that zone name
29246 Invalid alias name
29247 Transfer refused
29248 Network error
29249 Cache entry not found
29250 Management information is in use
29251 Not all resource records are deleted
29252 Service is initializing; please retry later
29253 Service is terminating; please retry later
29254 Operation is in progress
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 18

29255 No audit entries found

29256 Invalid zone file
29257 $INCLUDE line not supported in the zone file
29258 Unsupported resource record type
29259 Invalid $ORIGIN line in the zone file
29260 $GENERATE line not supported in the zone file
29261 $ORIGIN line not specified in the zone file
29262 Zone transfer already in progress
29263 Invalid command
29264 Invalid parameter
29265 Invalid value
29266 Zone is not a primary
29267 Zone is not a secondary
29268 Zone transfer of the root cache is disallowed
29269 Zone is busy; please retry later
29270 Zone template cannot be found
29271 Not a zone template
29272 Asynchronous handle cannot be found
29273 More data is available
29274 No more data is available
29275 The object is protected from deletion
29276 The object is protected from renaming
29277 Can't convert because transfer in progress; retry later
29278 Invalid SOA record
29279 Open parenthesis \"(\" must not begin on a line
29280 Closing parenthesis \")\" not found
29281 Can't add the zone due to a license restriction; please contact vendor
29282 The function is no longer supported
29283 Can't add address resource record due to license restriction; please contact vendor
29284 CName records can't exist with other records of the same label
29285 Invalid domain name
29286 Invalid resource record data section
29287 No permission for reverse zone
29288 Disk error
29289 Need more data
29290 Too much data
29291 The cache entry already exists
29292 Invalid TTL
29293 Unsupported resource record class
29294 The resource record doesn't belong to the zone
29295 The zone name is too long; shorten the zone's records' labels/data or the zone’s
name
29296 The management information already exists
29297 The operation is not supported
29298 The sub-object cannot be found
29299 Can't add resource record due to a different TTL than its resource record set
 TM
Broadband Command Center 6.x Troubleshooting Device Provisioning 19

292300 The object is protected from conversion

6.3. CFM Service API Error Codes

6.4. 6.3 TFTP Service API Error Codes

Error Code Description

28300 Duplicate name: you already have an object with this name!
28301 Duplicate directory: you already have a directory with this name!
28302 Duplicate file: you already have a file with this name!
28303 Duplicate alias: you already have an alias with this name!
28304 Duplicate range: you already have a range with this name!
28305 File Group Uid Not Found
28306 File Info Not Found
28307 Address Range Not Found
28308 Directory Does Not Exist
28309 Make Dir Failed
28310 Remove Dir Failed
28311 The File Does Not Exist
28312 Add File Failed
28313 Delete File Failed
28314 No Blank Directory
28315 No Change Dir Name
28316 The DB Update Failed
28317 Modified Backup
28318 Newer Service
28319 File Name Used as Alias
28320 File Alias is the Default File
28321 File Group Delete Reschedule
28322 File Group No Default Delete
28323 Reserved Directory