Troubleshooting guide

6-4
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 6 Troubleshooting MTAs
Troubleshooting EMTA Provisioning
Scope Selection Tag(s)
In most scenarios, the BACC will be involved in processing all DHCP requests from scopes which have
scope selection tags that match the selection criteria as specified in the DHCP criteria configuration tab
in the BACC GUI. Client Class can also be used to tie scopes to BACC processing. Make sure you make
this association before you attempt to provision devices.
MTA Configuration File
The MTA config file will most importantly contain the location of the CMS. Additionally, it must contain
an entry for Realm Org Name. This value must match that of the certificate chain in use.
Certain entries must be indexed by the realm name, as delivered to the MTA in Option 122. The realm
name used to index must match that delivered in Option 122. For example, if “DEF.COM” was the realm
name delivered in Option 122, MTA config file entries in the pktcMtaDevRealm table would be indexed
with a suffix made up of the ASCII-coded character values (in dot delimited decimal format when using
the Cisco Broadband Configurator) of the realm name, for example 68.69.70.46.67.79.77. There are
many free ASCII conversion pages available on the web to make this conversion easier.
Troubleshooting Tools
The 25 EMTA provisioning steps contained in PacketCable EMTA Provisioning Specification
(PKT-SP-PROV-I03-011221), are as shown in Figure 6-1.
Figure 6-1 Embedded-MTA Power-on Provisioning Flow