Troubleshooting guide

6-7
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 6 Troubleshooting MTAs
Troubleshooting EMTA Provisioning
KDC reports success at step 9
(AS-Request/Reply), but MTA
never moves past step 9, and
continually reprovisions up to
that step
a. Telephony cert mismatch
between telephony root
loaded/enabled on MTA,
and that loaded on KDC
b. Corrupted telephony cert
chain (unlikely)
Note If other devices are
provisioning correctly,
b is not the cause of the
problem.
a. Check certs on MTA and KDC.
b. Ensure correct cert is loaded/enabled on MTA.
If no devices can be provisioned correctly, try
different certs on KDC.
Failure at AP Request/Reply
a. Clock skew error
b. Cannot resolve Prov Server
FQDN
c. no route from MTA to
provisioning server
a. Ensure that all BACC network elements are clock
synced via NTP
b. Make sure that the provisioning server (DPE) has
a correct DNS entry.
Ensure that dpe.properties provFQDNs entry has
correct FQDN and IP of provisioning server
(DPE)
c. correct routing problem
MTA never issues TFTP request
for config file
a. No route to TFTP server
(DPE in a BACC scenario)
a. correct routing problem
MTA never receives TFTP
config file
a. File not cached at DPE
b. Conflicting tftp-server
option included as part of
MTA scope policy in CNR
a. Wait until next provisioning attempt, at which
time file should be cached, or simply reset the
device
b. BACC will insert dpe address for tftp-server, one
can safely remove that option from the policy
MTA receives config file but
fails at step 25 (SNMP Inform to
provisioning server as seen in
DPE.log)
a. Config file has an internal
conflict, or a conflict with
Realm Org of telephony cert
chain, or a conflict with
Realm Name provided in
Option 122
a. Ensure that MTA config file is consistent.
MTA reports success at step 25,
but no RSIP is sent
a. MTA cannot resolve IP
address of CMS FQDN
given in MTA config file.
b. MTA cannot reach IP
addr(s) of CMS – no route
a. Ensure a DNS entry exists for the CMS
b. Resolve routing problem
Table 6-1 Trobleshooting Scenarios (continued)
Problem Possible Causes Remedies