Table Of Contents
Cisco Broadband Access Center Release Notes, 4.2.1
Revised: March 12, 2012, OL-26918-01
Cisco Broadband Access Center (Cisco BAC) 4.2.1 resolves some of the open defects in Cisco BAC 4.2. This release is supported on both Solaris 10 and Red Hat Enterprise Linux (RHEL) 5.
This document provides information on upgrade procedures from earlier versions of Cisco BAC to Cisco BAC 4.2.1 and the bug fixes being addressed in this release.
See the Cisco BAC 4.2 documentation for complete information about the product. You can access the Cisco BAC 4.2 product documentation at:
Upgrading to Cisco BAC 4.2.1
Cisco BAC 4.2.1 provides upgrades from the following earlier versions of Cisco BAC.
•Cisco BAC 2.7.1.x.
•Cisco BAC 4.0.1.x.
•Cisco BAC 4.1.0.x
•Cisco BAC 4.2
See Table 1 for upgrade task details.
Upgrade the Cisco BAC components in this order:
1. Upgrade the RDU and client APIs simultaneously.
2. In each provisioning group, upgrade the DPEs first, followed by the KDC, then the Network Registrar extensions.
Table 1 describes the upgrade tasks.
Table 1 Upgrading to Cisco BAC 4.2.1
Cisco BAC 2.7.1.x/4.0.1.x/4.1.0.x
To upgrade the RDU:
At the end, the installer prompts you to run the migration tool. (See Migration Tool.)
Cisco BAC 4.2
Note Migration of RDU database is not required.
To upgrade the RDU:
When upgrading to Cisco BAC 4.2.1, enter target location for these directories:
•Home <BPR_HOME>—This prompt is applicable only if you are upgrading from Cisco BAC 4.0.1.x to any later releases.
•Database logs <BPR_DBLOG>
You can also use the default directories provided you have deleted the <BPR_DATA> and <BPR_DBLOG> directories.
When Cisco BAC 4.2.1 is installed over the earlier versions, the installer detects if RDU database migration is necessary. At the end of installation, you are prompted to start the migration process. You have to run the migrateDb.sh shell script which is present in the <BPR_HOME>/migration directory.
The RDU database migration script allows you to migrate your RDU database from:
•Cisco BAC 2.7.1.x to Cisco BAC 4.2.1
•Cisco BAC 4.0.1.x to Cisco BAC 4.2.1
•Cisco BAC 4.1.0.x to Cisco BAC 4.2.1
There is no migration required if you are upgrading from Cisco BAC 4.2 to Cisco BAC 4.2.1 as all the new properties introduced in Cisco BAC 4.2.1 are automatically updated during the upgrade process.
However migration is required if you are upgrading from Cisco BAC 4.2 Solaris to Cisco BAC 4.2.1 Linux. See the Cisco BAC 2.7.1.x, 4.0.1.x, 4.1.0.x Solaris to Cisco BAC 4.2 Linux section of the Cisco Broadband Access Center Installation Guide, 4.2 for more details.
1. Back up the Cisco BAC 2.7.1.x/4.0.1.x/4.1.0.x database using the <BPR_HOME>/rdu/bin/backupDb.sh tool.
2. Execute <BPR_HOME>/rdu/bin/recoverDb.sh tool over the backed up database.
3. Upgrade the RDU from Cisco BAC 2.7.1.x/4.0.1.x/4.1.0.x to Cisco BAC 4.2.1 using the Cisco BAC 4.2.1 install script.
4. Execute migrateDb.sh tool to perform database migration.
5. Restore the database to Cisco BAC 4.2.1 active RDU database directories.
Note Before running the restoreDb.sh tool, you must stop the RDU server by running the /etc/init.d/bprAgent stop rdu command. Also, remember to back up the database, then remove all files from the rdu/db and the rdu/dblog directories.
6. Start the RDU.
Migration is not supported for the DPE cache. See the DPE Cache Backup and Restore Tool section of the Cisco Broadband Access Center Installation Guide, 4.2 for details on how to migrate the DPE database to Cisco BAC 4.2.1.
The Cisco BAC 4.2.1 migration tool facilitates database portability between platforms. You can also use this migration tool to migrate between different platforms like Cisco BAC 4.1.0.x Solaris to Cisco BAC 4.2.1 Linux.
See the Migrating the RDU Database section of the Cisco Broadband Access Center Installation Guide, 4.2 for details on how to migrate the RDU database to Cisco BAC 4.2.1.
Note For Solaris, use the <BPR_HOME>/migration/migrateDb.sh script. For Linux, run the Migration tool by untarring it from the BAC_421_MigrationTool.tar.gz package.
This section lists the customer-found problems that were either fixed in Cisco BAC 4.2.1 or are still open.
Table 2 lists the bugs resolved in Cisco BAC 4.2.1 release.
New Properties Added in Cisco BAC 4.2.1
Table 3 lists the properties that were added in Cisco BAC 4.2.1 release.
Table 4 lists major software known bugs in Cisco BAC 4.2.1. To find known problems in Cisco BAC, use the following URL:
To access Bug Toolkit you must log into Cisco.com. You can search for specific bugs or search for a range by product name. This tool enables you to query for keywords, severity, range, or version.
To get the list of known bugs of Cisco BAC 4.2, see the Known Problems section of the Release Notes for Cisco Broadband Access Center 4.2.
Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
See the Cisco BAC and Cisco Network Registrar Compatibility Matrix to know which Cisco BAC versions are compatible with a Cisco Network Registrar version.
See the following documents for more information about installing, configuring, and managing Cisco BAC 4.2.1.
See the following documents for information about Cisco Network Registrar.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
© 2012 Cisco Systems, Inc. All rights reserved.