Cisco Broadband Access Center Release Notes, 4.2.1

Available Languages

Download Options

  • PDF     (142.5 KB)
    View with Adobe Reader on a variety of devices
Updated:March 11, 2012

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Cisco Broadband Access Center Release Notes, 4.2.1

Table Of Contents

Cisco Broadband Access Center Release Notes, 4.2.1

Contents

Upgrading to Cisco BAC 4.2.1

Upgrade Tasks

Database Migration

Migration Procedure

Migration Tool

Caveats

Resolved Bugs

New Properties Added in Cisco BAC 4.2.1

Known Bugs

Related Documentation

Obtaining Documentation and Submitting a Service Request


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:
http://www.cisco.com/en/US/products/sw/netmgtsw/ps529/tsd_products_support_series_home.html

Contents

•Upgrading to Cisco BAC 4.2.1

•Caveats

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

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.

Upgrade Tasks

Table 1 describes the upgrade tasks.

Table 1 Upgrading to Cisco BAC 4.2.1

Version
RDU/DPE

Cisco BAC 2.7.1.x/4.0.1.x/4.1.0.x

To upgrade the RDU:

On Solaris:

Run install_bac_solaris.sh.

On Linux:

Run install_bac.sh.

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:

On Solaris:

Run install_bac_solaris.sh.

On Linux:

Run install_bac.sh.

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.

•Data <BPR_DATA>

•Database logs <BPR_DBLOG>

You can also use the default directories provided you have deleted the <BPR_DATA> and <BPR_DBLOG> directories.


Database Migration

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.

Migration Procedure

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.

Migration Tool

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.

Caveats

This section lists the customer-found problems that were either fixed in Cisco BAC 4.2.1 or are still open.

Resolved Bugs

Table 2 lists the bugs resolved in Cisco BAC 4.2.1 release.

Table 2 Resolved Bugs

Bug ID
Summary

CSCts64995

Uploading large .groovy file causes RDU to restart.

CSCtw48652

Files getting deleted even if it's referenced by a Cos.

CSCtt09096

Groovy Issue - Strings with $.

CSCtt38312

Uploading a Groovy script with a "-" in the filename crashes the RDU.

CSCtt97314

Groovy script upload time.

CSCtu08332

Default DOCSIS version (runCfgUtil.sh Groovy script parser).

CSCtu08613

Device not found issue.

CSCtu41898

Stackoverflow during groovy recursion.

CSCtu42917

API client messages falling behind.

CSCtw46710

Concurrent calls to GetAllClassesOfService causes java heap OOM in RDU.

CSCtw48653

ThreadDeath : add Diagnostics information for Shutting_down event change

CSCtw89758

ArrayIndexOutOfBoundsException seen in RDU defaults page

CSCtw94764

RDU defaults should not recompile the scripts if it's in enabled state.

CSCtx00190

When recompile is disabled, ext check does not happen while adding script.

CSCtx51980

OutOfMemoryError during TFTP file transfer with concurrent sessions.

CSCtx61775

TFTP empty local files fail to download.

CSCtx62011

Groovy performance improvements.

CSCtx62071

UpgradeProperties overwriting extension values and RADIUS configurations.

CSCtw79227

Secure packetcable provisioning defect on Linux.

CSCty15502

DPE restarted with NullPointerException while TFTP download.

CSCty37702

Database tool to collect BDB cache statistics.


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 3 New Properties Added in Cisco BAC 4.2.1

Bug ID
Description
Property change

CSCtw46710

Concurrent calls to GetAllClassesOfService causes java heap OOM in RDU.

By default, concurrent execution of GetAllClassesOfService is permitted, unless restricted. To restrict the concurrent execution of GetAllClassesOfService for a DeviceType, append the property /pace/batch/commands/duplicate/restrict in rdu.properties and change the value [true or false] accordingly.

File location: <BAC_HOME>/rdu/conf/rdu.properties

/pace/batch/commands/duplicate/restrict=true

ServerDefaultsKeys.PACE_DUP_REQ_RESTRICT

CSCtt97314

Groovy script upload time

A new property /server/scriptCompile is defined to control the groovy script compilation.

By default, script compilation mode is enabled and if enabled, the scripts will get compiled and cached during file addition. The replaceFile and deleteFile commands will clear the compiled class cache. The addFile and replaceFile commands will compile the script in order to detect compile-time issues immediately.

If the mode is disabled then no compilation or recompilation of groovy scripts occurs during script addition, deletion, or replacement. The respective and dependent scripts will get compiled only at run time and appropriate error messages will be thrown, in case the compilation fails.

A Scripts recompile radio button is added to the Configuration >Defaults > RDU Defaults page to control this behavior.

/server/scriptCompile

(ServerDefaultsKeys.DYNAMIC_FILE_AUTOMATIC_COMPILE_ENABLE)


Known Bugs

Table 4 lists major software known bugs in Cisco BAC 4.2.1. To find known problems in Cisco BAC, use the following URL:

http://tools.cisco.com/Support/BugToolKit

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.

Table 4 Known Bugs

Bug ID
Description
Workaround

CSCtx94934

Jar files added are not shown under "Extension Point JAR File Search Order" field in the RDU Defaults page, if the field is manually edited in 4.1.0.3.

Manually add the uploaded Jar file name under "Extension Point JAR File Search Order" in the RDU Defaults page.

CSCtx99988

Bulk addition of Groovy scripts fail with PermGen space error.

Modify <BPR_HOME>/rdu/internal/bin/runRDU.sh file to include "-XX:MaxPermSize=128M" in order to increase the default PermGen value to 128MB so as to support approximately 1500 groovy scripts of size 40k.

CSCty47874

Cisco BAC version displayed while migration is 4.2 instead of 4.2.1.

This has no impact on Migration. Incorrect message is shown in the log/console.

CSCty33176

DPE with removed ipv6 interface causes port is already used statement

You have to remove the bad IP address configured in the DPE to overcome this issue. The DPE interface IPv4/v6 address should be the same as the one configured on the server. If you change the system IPv4/v6 address, you should also change the DPE interface IPv4/v6 address from DPE CLI mode.

CSCty13181

KDC license deleted after upgrade from BAC 4.2.

Backup the KDC license located in <BPR_HOME>/kdc before upgrade and replace it after upgrade.


Related Documentation

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.

Table 5 Cisco BAC Related Documentation

Document Title
Available Location

Installation and Setup Guide for Cisco Broadband Access Center 4.2

•PDF file on the product CD-ROM.

•On Cisco.com:
http://www.cisco.com/en/US/products/sw/netmgtsw/
ps529/prod_installation_guides_list.html

Cisco Broadband Access Center DPE CLI Reference 4.2

•PDF file on the product CD-ROM.

•On Cisco.com:
http://www.cisco.com/en/US/products/sw/netmgtsw/
ps529/prod_command_reference_list.html

Administrator Guide for Cisco Broadband Access Center 4.2

•PDF file on the product CD-ROM.

•On Cisco.com:
http://www.cisco.com/en/US/products/sw/netmgtsw/
ps529/prod_maintenance_guides_list.html

Release Notes for Cisco Broadband Access Center 4.2

•PDF file on the product CD-ROM.

•On Cisco.com:
http://www.cisco.com/en/US/products/sw/netmgtsw/
ps529/prod_release_notes_list.html


See the following documents for information about Cisco Network Registrar.

Table 6 Cisco Network Registrar Related Documentation

Document Title
Available Location

User Guide for Cisco Network Registrar 7.2

•PDF file on the product CD-ROM.

•On Cisco.com:
http://www.cisco.com/en/US/products/sw/
netmgtsw/ps1982/products_user_guide_list.html

Installation Guide for Cisco Network Registrar 7.2

•PDF file on the product CD-ROM.

•On Cisco.com:
http://www.cisco.com/en/US/products/sw/
netmgtsw/ps1982/prod_installation_guides_list.html

CLI Reference Guide for Cisco Network Registrar 7.2

•PDF file on the product CD-ROM.

•On Cisco.com:
http://www.cisco.com/en/US/products/sw/
netmgtsw/ps1982/prod_command_reference_list.html

Release Notes for Cisco Network Registrar 7.2

•PDF file on the product CD-ROM.

•On Cisco.com:
http://www.cisco.com/en/US/products/sw/
netmgtsw/ps1982/prod_release_notes_list.html


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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco