Troubleshooting guide

6-5

Cisco Broadband Local Integrated Services Solution Troubleshooting Guide

OL-5169-01

Chapter 6 Troubleshooting MTAs

Troubleshooting EMTA Provisioning

Logs

The following log files contain information as listed:

• CNR logs name_dhcp_1_log and name_dns_1_log contain the most recent logging entries from

CNR. Look here for DHCP or DNS related problems.

• $BPR_HOME/kdc/logs/KDC.log shows all KDC interactions with MTAs, and KDC interactions

with the provisioning server (BACC DPE).

• $BPR_HOME/dpe.log (or view log from CLI, if using DPE appliance) shows the major steps related

to SNMPv3 interaction with MTA. See the BACC documentation for instructions on how to turn up

trace levels.

Ethereal, SnifferPro, or Other Packet Capture Tools

A packet capture tool is indispensable when troubleshooting the EMTAs. The Ethereal version, as

packaged by CableLabs, includes numerous packet decoders specific to PacketCable, including

Kerberos AS and AP packets.

If a failure is believed to be DHCP related, you will need to capture packets while filtering on packets

sourced from or destined to the CMTS cable interface IP address and the DHCP server IP address.

If a failure is believed to be related to any of the 25 steps occurring after DHCP, merely filter all packets

to/from the EMTA IP address. This gives a very concise, easy-to-follow trace of provisioning steps 5-25.

Troubleshooting Scenarios

The scenarios listed in Table 6-1 are possible failures involving embedded MTAs.

Ta b l e 6 - 1 Tr o b l e s h o o t i n g S c e n a r i o s

Problem Possible Causes Remedies

KDC will not start

a. KDC cert private does not

correspond to private key

b. KDC license expired or

missing

a. Ensure that you have matching certs and private

key

b. restore KDC license to $BPR_HOME/kdc