Cisco Cisco Broadband Access Center for Cable 4.0
6
Release Notes for Cisco Broadband Access Center 4.0.1
OL-16643-01
New and Changed Features
•
Enhanced performance of the template parser (which DOCSIS, PacketCable, and CableHome
extensions use to provide dynamic configurations) to optimize generation of device configurations
based on templates. Additionally, you can compress all configurations that are generated, thus
decreasing overhead at the DPE to enhance server performance.
extensions use to provide dynamic configurations) to optimize generation of device configurations
based on templates. Additionally, you can compress all configurations that are generated, thus
decreasing overhead at the DPE to enhance server performance.
•
Enhanced multivendor support by enabling scoping of Option 43 and its suboptions. It also gives
you the option of using a single template to specify various TLV 43s from many vendors.
you the option of using a single template to specify various TLV 43s from many vendors.
Improved Management
This BAC release enables you to manage your network better by introducing support for:
•
Provisioning group properties on the property hierarchy—Enhances the flexibility that the BAC
property hierarchy provides by including the properties of a device’s provisioning group.
property hierarchy provides by including the properties of a device’s provisioning group.
•
Provisioning group capabilities—Allows you to control the device type support that must be enabled
for the provisioning groups in your deployment. In earlier BAC releases, each DPE in a provisioning
group registered what it was capable of supporting with the RDU at startup. This information was
combined with that of other DPEs in the provisioning group to determine the device types that the
group could support. Thus, the capabilities of a provisioning group were automatically enabled.
for the provisioning groups in your deployment. In earlier BAC releases, each DPE in a provisioning
group registered what it was capable of supporting with the RDU at startup. This information was
combined with that of other DPEs in the provisioning group to determine the device types that the
group could support. Thus, the capabilities of a provisioning group were automatically enabled.
In this release, however, you must manually enable the capabilities of a provisioning group from the
administrator user interface or the API. You can thus choose to enable only specific capabilities and
ignore others in keeping with your requirements.
administrator user interface or the API. You can thus choose to enable only specific capabilities and
ignore others in keeping with your requirements.
•
“Services” interface on the DPE command line—Provides flexibility in configuring the DPE to suit
your requirements. Using the “services” interface, you can choose to enable only certain services;
for example, you can enable the TFTP service for IPv4 transport, but not for IPv6 transport. All
services on the DPE are by default disabled.
your requirements. Using the “services” interface, you can choose to enable only certain services;
for example, you can enable the TFTP service for IPv4 transport, but not for IPv6 transport. All
services on the DPE are by default disabled.
Increased Security
This BAC release provides increased security via:
•
User-configurable IP addresses and ports to support:
–
Multipathing—Earlier BAC versions enable you to configure a DPE interface for provisioning
using the Solaris interface names. This BAC release enables you to configure the provisioning
interfaces using the IP addresses of the DPE interface, thus allowing one interface to back up
for another by switching its IP address in case of failure.
using the Solaris interface names. This BAC release enables you to configure the provisioning
interfaces using the IP addresses of the DPE interface, thus allowing one interface to back up
for another by switching its IP address in case of failure.
–
Multi-interface binding—When communicating with Network Registrar extension points,
previous BAC DPEs rely on the operating system to determine the interface for use, because the
extensions require the reply to come from the interface that the request was sent to. In this BAC
release, you can configure this interface, which by default is all IPv4 interfaces.
previous BAC DPEs rely on the operating system to determine the interface for use, because the
extensions require the reply to come from the interface that the request was sent to. In this BAC
release, you can configure this interface, which by default is all IPv4 interfaces.
–
Firewall compatibility—Earlier BAC releases rely on the operating system to determine the
source interface and the source port in communications between the DPE and the RDU. In this
BAC release, you can configure the source interface and the port, and thus segment management
traffic and create firewall rules.
source interface and the source port in communications between the DPE and the RDU. In this
BAC release, you can configure the source interface and the port, and thus segment management
traffic and create firewall rules.
•
CMTS MIC for DOCSIS 3.0—Supports DOCSIS 3.0 for the Extended CMTS MIC Configuration
Setting that configures how the CMTS checks the integrity of a message. By providing 3.0 support
for this setting, BAC uses advanced hashing techniques to detect unauthorized modification or
corruption of the cable modem configuration file.
Setting that configures how the CMTS checks the integrity of a message. By providing 3.0 support
for this setting, BAC uses advanced hashing techniques to detect unauthorized modification or
corruption of the cable modem configuration file.