Table Of Contents
Release Notes for Cisco Broadband Access Center 2.7.1
Enforcing Attribute Requirements for Configuration Generation
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Broadband Access Center 2.7.1
June 21, 2007
These release notes describe new software features and fixes to software issues in Cisco Broadband Access Center, Release 2.7.1.
Contents
•Obtaining Documentation, Obtaining Support, and Security Guidelines
Introduction
Cisco Broadband Access Center, referred to as BAC throughout this document, automates the tasks of provisioning and managing customer premises equipment (CPE) in a broadband service-provider network. The application provides a simple and easy way to deploy high-speed data, voice technology, and home networking devices.
BAC can be scaled to suit networks of virtually any size, even those deploying millions of devices. It also offers high availability, made possible by its distributed architecture with centralized management.
System Components
The BAC product comprises:
•The Regional Distribution Unit (RDU), which is the primary server in a BAC deployment. Through its extensible architecture, the RDU supports the addition of new technologies and services.
•The Device Provisioning Engine (DPE), which handles all device interactions with the RDU. The DPE server is available as:
–A software DPE that is installed on a Solaris SPARC computer.
–A rack-mountable DPE-2115 appliance with the BAC software already installed on it.
•Cisco Network Registrar extension points, which are the link between BAC and Network Registrar. Network Registrar provides BAC with the DHCP and Domain Name System (DNS) functionality.
•The Key Distribution Center (KDC), which is a Kerberos server that authenticates PacketCable Media Terminal Adapters (MTAs).
•An administrator user interface from which you can monitor and manage BAC.
•A sample user interface, which you can use to demonstrate BAC power and flexibility.
•A Java provisioning application programming interface (API), which you use to integrate BAC into an existing operations support-system environment.
Before Installing BAC 2.7.1
Review the following critical information before you begin to install BAC 2.7.1.
System Requirements
To successfully install BAC software on your system, you must meet these requirements:
•Operating System—You must have Solaris 8 or 9 running on your system.
•Network Registrar—You must have Network Registrar version 5.5.12 or later installed on the servers on which you are installing BAC extensions.
Note Cisco recommends that you install Network Registrar version 6.2.3.2 or later. Running BAC with a version earlier than 6.0.3 restricts you from using certain features available in this
2.7.1 release.
•Administrator User Interface—At a minimum, you must have Microsoft Internet Explorer 6.0 (Service Pack 2) or Netscape 4.7.
•API client
–Ensure that you install Java 1.5 to support the API client in release 2.7.1. API clients in versions earlier than 2.7.1, however, support JRE versions earlier than 1.5.
–Ensure that the files bpr.jar and bacbase.jar are available in the classpath.
For detailed information on system requirements, refer to the Installation and Setup Guide for Cisco Broadband Access Center, 2.7.1.
Licensing Requirements
You must have a valid license key to successfully provision devices that use BAC. These licenses are specific to:
•The following BAC components:
–DPE
–KDC, if you configure your network to support voice technology.
•Each technology that you provision.
Note If you have not yet received your licenses, contact your Cisco representative.
Installation Notes
Review the following notes before installing BAC 2.7.1.
•Ensure that your systems meets the requirements described in System Requirements.
•Ensure that you download and install the recommended patches from the Sun Microsystems
support site.•Obtain a valid BAC license key for each technology that you provision. This includes the DPE and the KDC components. If you have not yet received your licenses, contact your Cisco representative.
•Verify the file-system block size of the directory in which you intend to install the BAC database and database transaction log files. For optimum performance and reliability of the BAC database, configure the file system or systems that contain the database files and database log files with an 8-KB or greater block size.
•Ensure that the file system in which you place database files is configured to support files larger
than 2 GB.For complete information on installation procedures, refer to the Installation and Setup Guide for Cisco Broadband Access Center, 2.7.1.
Upgrade Notes
Review the following notes before upgrading to BAC 2.7.1 from a previous release.
•If you are upgrading from a BAC release earlier than Broadband Access Center for Cable (BACC) 2.6.2.x, you must first upgrade your system to BACC 2.6.2. You cannot upgrade directly to 2.7.1 from a version preceding 2.6.2.
•This release does not support the DPE-590 appliance. You can, however, upgrade the DPE-590 to BACC 2.7, which is compatible with a BAC 2.7.1 RDU.
•Before upgrading the new BAC version, you must back up the database files by running the backupDb.sh tool. For detailed information, refer to the Cisco Broadband Access Center Administrator Guide, 2.7.1.
•If you are upgrading from:
–BAC 2.7.x, you do not need to migrate the RDU database.
–BAC 2.6.2.x, you must migrate the RDU database. You can use the RDU database migration script to migrate your RDU database from BACC 2.6.2.x to BAC 2.7.1.
•You must upgrade to BAC 2.7.1 in the order specified below. Performing the upgrade in any other order results in errors during provisioning.
First complete the preliminary upgrade procedure, then upgrade the components in this order:
a. RDU
b. Solaris DPE
c. Hardware DPE
d. Network Registrar extensions
e. KDC
For complete information on upgrading, refer to the Cisco Broadband Access Center Installation Guide, 2.7.1.
New Features
This section briefly describes new or modified features found in the BAC 2.7.1 release.
Logging of Batch Operations
In this release, the RDU has been enhanced to record additional messages when logging of informational messages is enabled. These messages expose batch-processing operations that were previously not logged. Messages related to batch processing have been enhanced to contain information on elapsed time and rate to provide an indicator of RDU load and performance.
Enforcing Attribute Requirements for Configuration Generation
In the release, BAC extensions installed on Network Registrar have been enhanced to send requests to the RDU for device configuration only if the request meets the values required by the RDU. If the request does not specify the required value, Network Registrar extensions reject devices from triggering a request for configuration generation.
This feature supports a property containing a list of Network Registrar DHCP option names that must
be present in the DHCP Discover to allow BAC extensions to send a request to the RDU for a
device configuration.IP Lease Reservation
Although this feature was supported in previous BAC releases, in this release, this feature is supported only when Network Registrar, version 6.1.2.3 or later, is in use with the Regional CCM feature that is deployed.
The Lease Reservation feature in BAC 2.7.1 works only in scenarios involving a single Network Registrar DHCP server with no failover configured. This feature is not supported in cases involving failover DHCP servers.
Automated Migration
The BAC 2.7.1 release supports the automatic migration of the RDU datastore from BACC 2.6.2.x
and 2.7.Caveats
For information on the complete list of BAC bugs, see the BAC271_BugList.html file in the docs/ subdirectory of the BAC CD-ROM or at the BAC software download site on Cisco.com.
Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl.
You must have a valid Cisco Connection Online (CCO) account to access the software bug toolkit.
•Table 1—Describes the major bugs fixed in this release.
•Table 2—Describes the open bugs in this release.
Fixed Bugs in BAC 2.7.1
Table 1 lists major software issues fixed in this release of BAC.
Open Bugs in BAC 2.7.1
Table 2 lists major open issues in this release of BAC.
Related Documentation
These related guides support this release of the BAC product:
•Cisco Broadband Access Center Administrator Guide, 2.7.1
•Installation and Setup Guide for Cisco Broadband Access Center, 2.7.1
•Cisco Broadband Access Center DPE CLI Reference, 2.7.1
•To support the DPE-2115:
–DPE-2115 Recovery CD-ROM Release Notes
–Installation and Setup Guide for the Cisco 1102 VLAN Policy Server
http://www.cisco.com/en/US/products/sw/secursw/ps2136/
products_installation_and_configuration_guide_book09186a00801f0d02.html
Caution Refer to the Cisco VLAN Policy Server guide only for port and connector identification, and to perform hardware installation. Do not attempt to perform any of the configuration instructions found in the VLAN Policy Server guide.
•Release Notes for Cisco Network Registrar 6.2.3
•Cisco Network Registrar User's Guide, 6.2.1
•Cisco Network Registrar CLI Reference, 6.2.1
•DOCSIS 2.0 Specification SP-RFIv2.0-I03-021218
•PacketCable MTA Device Provisioning Specification PKT-SP-PROV1.5-I02-050128
•CableHome CH-SP-CH1.0-I05-030801
Notices
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
© 2007 Cisco Systems, Inc. All rights reserved.