- Preface
- Broadband Access Center Overview
- Broadband Access Center Architecture
- Configuration Workflows
- CPE Provisioning Overview
- Configuration Templates Management
- DOCSIS Configuration
- PacketCable Voice Configuration
- CableHome Configuration
- Managing Broadband Access Center
- Monitoring Broadband Access Center
- Understanding the Administrator User Interface
- Using the Administrator User Interface
- Configuring Broadband Access Center
- Support Tools and Advanced Concepts
- Database Management
- Troubleshooting Broadband Access Center
- Alert and Error Messages
- Option Support
- PacketCable DHCP Options to BAC Properties Mapping
- Provisioning API Use Cases
- FAQs on Provisioning Broadband Access Center
- Glossary
- Index
Mapping PacketCable DHCP Options to BAC Properties
This appendix identifies the mapping of BAC properties to the PacketCable DHCP options used for PacketCable provisioning and includes:
•
Option 122 and BAC Property Comparison
•Option 177 and BAC Property Comparison
The minimum required set of these properties is configured, during installation, in the BPR_HOME/cnr_ep/conf/cnr_ep.properties file. This file resides on the Cisco Network Registrar host. The set of properties defined in cnr_ep.properties is applied to all PacketCable voice technology devices in the provisioning group. Like other BAC properties, you can also set these properties on a device or a Class of Service. Setting them at the RDU, using either the administrator user interface or the application programming interface (API), overrides the corresponding values set in the cnr_ep.properties file.
Note See Using the KeyGen Tool, page 14-8, for information on changing these key configuration properties.
BAC supports both PacketCable DHCP Option 122 (as specified in RFC 3495 and 3594) and the deprecated PacketCable DHCP Option 177. BAC does not ignore DHCP requests when it cannot populate option 122 and/or 177 content. Whatever Option 122/177 content is available is populated and the decision to ignore the option is left to the eMTA.
When BAC receives a DHCP request asking for both options 122 and 177, BAC ignores the request for Option 177 and populates only Option 122 content.
There should be only one instance of each property in
BPR_HOME/cnr_ep/conf/cnr_ep.properties.
Option 122 and BAC Property Comparison
Table C-1 identifies the BAC properties as they apply to the definition of Option 122 in RFC 3495 and RFC 3594.
If any of
/ccc/kerb/auth/backoff/nomTimeout,
/ccc/kerb/auth/backoff/maxTimeout, or
/ccc/kerb/auth/backoff/maxRetries are defined, they must all be defined. Similarly, if any of
/ccc/kerb/app/backoff/nomTimeout,
/ccc/kerb/app/backoff/maxTimeout, or
/ccc/kerb/app/backoff/maxRetries are defined, they must all be defined.
Option 177 and BAC Property Comparison
In accordance with PacketCable compliance wave 26, Option 177 is deprecated, and Option 122 is now the preferred MTA provisioning option. For legacy devices that still support Option 177, Table C-2 identifies the BAC properties as they apply to the definition of Option 177.
Feedback