Cisco Cisco Broadband Access Center for Cable 4.0 Release Notes
8
Release Notes for Cisco Broadband Access Center 4.0.1
OL-16643-01
Additional Notes for BAC 4.0.1
•
Automatic migration of the DPE cache.
•
Compatibility of the 4.0.1 RDU and DPE with earlier versions of Solaris DPEs and Network
Registrar servers, respectively, for gradual online migration.
Registrar servers, respectively, for gradual online migration.
Licensing Using Cisco Standard
This BAC release enhances licensing to provide flexible options, greater reliability and security, and ease
of use. While earlier BAC versions used a proprietary model of licensing, this release incorporates
support for FlexLM, a Cisco license management system.
of use. While earlier BAC versions used a proprietary model of licensing, this release incorporates
support for FlexLM, a Cisco license management system.
In previous BAC releases, you were licensed for the technologies that provisioned the devices in your
network. In this release, you are licensed to provision a specific number of services for any device type.
Each service translates to three IP addresses that are provisioned in the system.
network. In this release, you are licensed to provision a specific number of services for any device type.
Each service translates to three IP addresses that are provisioned in the system.
See also
.
Additional Notes for BAC 4.0.1
The following changes also apply to BAC 4.0.1:
Processing DHCP Option 177 Requests
BAC now properly handles incoming requests from legacy devices that support DHCP option 177, which
was deprecated and replaced by option 122 (cable-labs-client-configuration; see
was deprecated and replaced by option 122 (cable-labs-client-configuration; see
).
A BAC 4.0 DHCP extension that received a PacketCable eMTA DHCPDISCOVER packet containing
option 177 would drop the packet. The workaround was not to install BAC 4.0 in deployments of legacy
MTAs supporting DHCP option 177 (CSCso61910). BAC 4.0.1 now correctly provisions legacy devices
that use Option 177.
option 177 would drop the packet. The workaround was not to install BAC 4.0 in deployments of legacy
MTAs supporting DHCP option 177 (CSCso61910). BAC 4.0.1 now correctly provisions legacy devices
that use Option 177.
Provisioning Promiscuous Mode MTA Devices
A promiscuous MTA device is allowed to boot and be configured without being preregistered in BAC
and whose provisioning is based on policies assigned to its relay agent.
and whose provisioning is based on policies assigned to its relay agent.
Promiscuous mode is allowed in BASIC.1and BASIC.2 workflows only; it is not applicable to SECURE
workflows. See:
workflows. See:
•
).
In BAC 4.0, MTA devices did not provision correctly in the promiscuous mode, even with the
PacketCable Promiscuous Mode enabled and the PacketCable Promiscuous Class of Service set at the
system level (CSCsq40930). The DOCSIS configuration would be correct, but the DHCPOFFER sent to
the MTA would be missing the fully qualified domain name (FQDN), hence the MTA could not be
provisioned.
PacketCable Promiscuous Mode enabled and the PacketCable Promiscuous Class of Service set at the
system level (CSCsq40930). The DOCSIS configuration would be correct, but the DHCPOFFER sent to
the MTA would be missing the fully qualified domain name (FQDN), hence the MTA could not be
provisioned.