Примечания к выпуску для Cisco Cisco Broadband Access Center for Cable 4.1
5
Release Notes for Cisco Broadband Access Center 4.1.0.1
OL-24085-01
New and Changed Features
DCFG Support for Groovy Scripting
The Dynamic Configuration File Generation with Groovy scripting offers increased functionality over
template-based file generation. Templates are still supported for backward compatibility.
template-based file generation. Templates are still supported for backward compatibility.
To support dynamic configuration, the device discovered data are used at runtime by Groovy script
through exposed API's.
through exposed API's.
Groovy scripts are supported for all CableLabs standard devices and IP-modes supported by previous
versions of Cisco BAC (DOCSIS IPv4/IPv6, PacketCable and OpenCable IPv4/IPv6).
versions of Cisco BAC (DOCSIS IPv4/IPv6, PacketCable and OpenCable IPv4/IPv6).
The command line configuration file utility is updated to execute Groovy script. The command line
configuration file utility also supports the conversion from binary file to Groovy script and vice versa.
configuration file utility also supports the conversion from binary file to Groovy script and vice versa.
DPE Device Configuration Compression Support
In the previous release (Cisco BAC 4.0), the DPE supported compressed TFTP configurations, but the
configurations were compressed individually. In the Cisco BAC 4.1.0.1 release, the DHCP, TFTP and
SNMP configuration information are compressed using the delta compression technique as defined in
RFC 3284. This feature will enable the DPE to store more than two million device configurations.
configurations were compressed individually. In the Cisco BAC 4.1.0.1 release, the DHCP, TFTP and
SNMP configuration information are compressed using the delta compression technique as defined in
RFC 3284. This feature will enable the DPE to store more than two million device configurations.
GSLB Support
GSLB directs DNS requests to the best-performing GSLB website in a distributed internet environment.
In Cisco BAC 4.1.0.1, GSLB is used to implement the failover, the continuation of RDU service after
the failure of primary RDU. When the primary RDU fails, all the client requests will be routed to the
secondary RDU. In the previous releases (Cisco BAC 2.7 and 4.0), when the IP address of RDU FQDN
is changed, the clients (DPE, CNR_EP, API) should be restarted to reconnect with the secondary RDU
or RDU with the new IP address. In Cisco BAC 4.1.0.1, if the IP address of FQDN is changed and also
the primary RDU is down, FQDN will be resolved to the new IP address and all the client will be routed
to the secondary RDU.
In Cisco BAC 4.1.0.1, GSLB is used to implement the failover, the continuation of RDU service after
the failure of primary RDU. When the primary RDU fails, all the client requests will be routed to the
secondary RDU. In the previous releases (Cisco BAC 2.7 and 4.0), when the IP address of RDU FQDN
is changed, the clients (DPE, CNR_EP, API) should be restarted to reconnect with the secondary RDU
or RDU with the new IP address. In Cisco BAC 4.1.0.1, if the IP address of FQDN is changed and also
the primary RDU is down, FQDN will be resolved to the new IP address and all the client will be routed
to the secondary RDU.
Linux Support for DPE and CNR_EP
Cisco BAC 4.1.0.1 release includes support for the DPE and CNR extensions running on Red Hat
Enterprise Linux platform using x86 based hardware. This includes RPM based installations and mixed
platform provisioning group deployments. For example, CNR extensions can run on a Linux platform
and DPEs can either run on a Linux or Solaris platform. However, mixing the platform for a server type
is not recommended.
Enterprise Linux platform using x86 based hardware. This includes RPM based installations and mixed
platform provisioning group deployments. For example, CNR extensions can run on a Linux platform
and DPEs can either run on a Linux or Solaris platform. However, mixing the platform for a server type
is not recommended.
Non-root Solaris 10 Support
This feature allows non-root users to run Cisco BAC on a Solaris environment. The non-root user should
be assigned Solaris privileges before installing the product. The Cisco BAC 4.1.0.1 installer prompts for
user name and group name that are associated with the non-root user. The processes gets initiated with
the user name and the group name that where provided during the installation. Any other non-root user
who is in the same group provided during the installation will be able to run the product.
be assigned Solaris privileges before installing the product. The Cisco BAC 4.1.0.1 installer prompts for
user name and group name that are associated with the non-root user. The processes gets initiated with
the user name and the group name that where provided during the installation. Any other non-root user
who is in the same group provided during the installation will be able to run the product.