Installation Guide for Cisco Broadband Access Center Release 2.7

Upgrading Broadband Access Center for Cable

This chapter describes how to upgrade a BACC 2.5.0.2 or higher installation to BACC 2.7. If you have a BACC release preceding BACC 2.5.0.2, you must first upgrade your system to BACC 2.5.0.2 and then complete this upgrade procedure.

Table 6-1 summarizes the order of upgrade and migration tasks required for BACC components for different versions.

The BACC upgrade procedure requires that the components be updated in the exact order described below. Performing the upgrade in any other order may result in errors during provisioning:

•Before You Begin

•Upgrading the RDU

•Upgrading the Solaris DPE

•Upgrading Hardware DPEs

•Upgrading Network Registrar Extensions

•Upgrading the KDC

Before You Begin

The following procedure is required before upgrading all components except the RDU.

Step 1 Untar the upgrade file(27upgrade.tar) onto the computer where the BACC components reside. For example:

tar -xvf 27upgrade.tar 

The component upgrade scripts are extracted to the patch27/bin upgrade folder.

Step 2 Run the backupDb.sh script to back up the RDU database files. See the Cisco Broadband Access Center for Cable Administrator's Guide for additional information.

Upgrading the RDU

To upgrade the RDU:

Step 1 Run the setup.bin file normally associated with a new installation of BACC. The setup.bin file automatically detects the previous installation.

Step 2 When the installation program prompts you to perform the database migration procedure, run the migration script using the migrateDb.sh script as described in Migrating the RDU Database.

Upgrading the Solaris DPE

Complete these steps to upgrade the installed Solaris DPE component from release 2.6.x to release 2.7:

Step 1 Run this script from the upgrade folder:

./27-upgrade-dpe.sh 

Step 2 You must manually restart the agent to finish the upgrade process.

An output similar to this displays.

BPR Located

BPR Home directory is /opt/CSCObpr

Current version is 2.6.(x)

DPE Component Installed

Stopping the BPR Agent

BPR Agent is stopped.

BPR Agent stopped

Copying the Upgrade Files

Upgrading Package Information

Upgrade for BPR 2.7 Completed Successfully

Please start your BPR Agent to finish the upgrade Process 

Step 3 Run this command to verify that the output indicates it is BACC release 2.7:

# pkgparam CSCObpr VERSION  

The version information returned should be 2.7.

Note The previous version of the file bpr.jar is renamed as bpr-2x.jar and is located in the <BACC_HOME>/lib directory.

Step 4 Check the list of installed files. An output similar to this is displayed.

drwxr-xr-x 4 root smmsp 512 May 26 11:22 electric 
-rw-r--r-- 1 root smmsp 11730913 May 26 11:22 bpr.jar 
-rwxr-xr-x 1 root smmsp 116848 May 26 11:22 libosstatus.so 
-rwxr-xr-x 1 root smmsp 465392 May 26 11:22 libnative.so 
-rwxr-xr-x 1 root smmsp 827344 May 26 11:22 libInformManager.so 
-rwxr-xr-x 1 root smmsp 1983836 May 26 11:22 libbprextensions.so 
-rw-r--r-- 1 root smmsp 30790 May 26 11:23 pkcerts.jar 
-rwxr-xr-x 1 root smmsp 938940 May 26 11:23 libdb_java-4.1.so 
-rwxr-xr-x 1 root smmsp 840988 May 26 11:23 libdb-4.1.so 
-rwxr-xr-x 1 root smmsp 187162 May 26 11:23 sun_parser.jar 
-rwxr-xr-x 1 root smmsp 28404 May 26 11:23 sun_jaxp.jar 
-rwxr-xr-x 1 root smmsp 33428 May 26 11:23 sleepycat.jar 
-rw-r--r-- 1 root smmsp 936631 May 26 11:23 bcprov.jar 
-rwxr-xr-x 1 root smmsp 832960 May 26 11:23 libgcc_s.so.1 
-rwxr-xr-x 1 root smmsp 62624 May 26 11:23 TelnetD.jar 
-rwxr-xr-x 1 root smmsp 8661944 May 26 11:23 libstdc++.so.5 
-rw-r--r-- 1 root smmsp 285176 May 26 11:23 libscp_java01.so 
-rw-r--r-- 1 root smmsp 849020 May 26 11:23 libscp01.so 
-rw-r--r-- 1 root smmsp 185208 May 26 11:23 libmlog.so 
-rw-r--r-- 1 root smmsp 529820 May 26 11:23 libcnrschema.so 
-rw-r--r-- 1 root smmsp 2847640 May 26 11:23 libaic.so 
-rw-r--r-- 1 root smmsp 217572 May 26 11:23 dnsjava-1.5.1.jar 
-rwxr-xr-x 1 root smmsp 29411 May 26 11:23 comm.jar 
-rwxr-xr-x 1 root smmsp 384820 May 26 11:23 cnrsdk.jar 
-rwxr-xr-x 1 root smmsp 131919 May 26 11:23 xmlParserAPIs.jar 
-rwxr-xr-x 1 root smmsp 1728861 May 26 11:23 xercesImpl.jar 
-rwxr-xr-x 1 root smmsp 2370312 May 26 11:23 libssl.so.0.9.7 
-rwxr-xr-x 1 root smmsp 2328048 May 26 11:23 libnetsnmp.so.5 
drwxr-xr-x 2 root smmsp 512 May 26 11:23 SnmpAgent 
-rwxr-xr-x 1 root smmsp 14475552 May 26 11:23 libcrypto.so.0.9.7 
-rwxr-xr-x 1 root smmsp 28404 May 26 11:23 jaxp.jar 
-rwxr-xr-x 1 root smmsp 187162 May 26 11:23 crimson.jar 
-rwxr-xr-x 1 root smmsp 1107051 May 26 11:23 AdventNetSnmp.jar 
-rwxr-xr-x 1 root smmsp 801714 May 26 11:23 xalan.jar 
-rwx------ 1 root smmsp 167588 May 26 11:23 libnativeCrypto.so 
-rw-r--r-- 1 root smmsp 515746 May 26 11:23 adminui.war 
-rw-r--r-- 1 root smmsp 84311 May 26 11:23 sampleui.war

Note The actual directory contents displayed in this procedure may differ, from those shown above, depending on the components installed on the computer.

Upgrading Hardware DPEs

You may remotely patch your DPE devices, or if you have local access to these devices, you can fully reimage them. Refer to the recovery CD-ROM release notes that accompanied the DPE device for the required reimaging procedure.

Complete these steps to upgrade the DPE component to release 2.7:

Caution If the hardware DPE is rebooted or powered off while a patch is being applied, the device is left in an unknown state and must be completely reimaged. Refer to either the DPE-590 or DPE-2115 Recovery CD-ROM Release Notes that accompany the DPE device, for reimaging instructions.

Step 1 Open an FTP connection to each DPE to be patched and upload the patch bundle to the DPE. See step 3 for the appropriate DPE file name.

Note When opening the FTP connection, you must enter the username admin and the login password chosen for the selected DPE.

Step 2 After an FTP connection is established, change directory to `incoming' using this command at the FTP prompt:

cd incoming 

This will locate the patch file so that the DPE can easily find it.

Step 3 Select the upgrade file corresponding to the BACC version currently running on your DPE and FTP it to the DPE.

For example, you use this command to FTP the DPE-590 upgrade file from BACC 2.6.x to BACC 2.7:

bin

put dpe-590-26xto27-upgrade.bpr 

Step 4 Log into each DPE, in the enable mode, and run the upgrade command. You are prompted to select the 2.7 upgrade file and apply it. After the upgrade is finished, the DPE will reboot.

Step 5 Log into each DPE, in the enable mode, and run the show version command. This should identify the current version running on the DPE as BACC 2.7.

Upgrading Network Registrar Extensions

Use this procedure to upgrade the Network Registrar extensions from BACC 2.5.0.2, or 2.6.x to BACC 2.7:

Step 1 Run the 27-upgrade-cnrep.sh script.

Step 2 Stop the Network Registrar Server Agent when prompted.

The upgrade script automatically copies the upgraded extension point files into the required directories. When complete, it prompts you to restart the Network Registrar Server Agent.

Step 3 Run this command to verify that the output indicates it is BACC release 2.7:

# pkgparam CSCObpr VERSION  

The version information returned should be 2.7.

Step 4 Go to the /opt/CSCObpr/lib directory. Provided that the upgrade was successful, the directory content should appear similar to the list for the Solaris DPE upgrade with the addition of the libbprextensions-2x.so file.

Note The previous version of the file bpr.jar is renamed as bpr-2x.jar and is located in the <BACC_HOME>/lib directory.

Step 5 If a second check is required to verify upgrade success, go to the $CNR_HOME/extensions/dhcp/dex directory and verify that these files appear:

-rwxr-xr-x 

1 root 

bin 6

0904 

Oct 29 2003 

libdexextension.so

-rwxr-xr-x 

1 root 

other 

1530628 

Jul 22 12:43

libbprextensions-2x.so

-rwxr-xr-x 

1 root 

other 

1560748 

Aug 11 12:49

 libbprextensions.s

Note The actual directory contents displayed in this procedure may differ, from those shown above, depending on the components installed on the computer.

Upgrading the KDC

Note BACC 2.7 KDC requires a new license. Please ensure that the correct license and certificates are installed before you start the BACC agent.

Use this procedure to upgrade the KDC from BACC 2.5.0.2 or 2.6.x to BACC 2.7:

Step 1 Run the 27-upgrade-KDC.sh script.

Step 2 Manually start the BACC agent to complete the upgrade process.

Step 3 Run this command to verify that the output indicates it is BACC release 2.7:

# pkgparam CSCObpr VERSION  

The version information returned should be 2.7.

Step 4 Go to the /opt/CSCObpr/kdc/internal/bin directory. Provided that the upgrade was successful, this directory content should appear similar to this:

-r-x------ 

1 root 

smmsp 

1388 

May 26 11:23 

shutdownKDC.sh

-r-x------ 

1 root 

smmsp 

535

May 26 11:23 

runKDC.sh

-rwxr-xr-x 

1 root 

smmsp 

1023548 

May 26 11:23 

kdc

Note The actual directory content that is displayed may differ, from that shown above, depending on the components installed on the computer.

Migrating the RDU Database

The Regional Distribution Unit (RDU) database migration script lets you migrate your RDU database from BACC 2.5.0.2 into BACC 2.7.

The migration script is automatically installed, and unpacked, whenever the BACC 2.7 installation program (setup.bin) is run. The installation program unpacks the migration script file into the <BACC_HOME>/migration directory. You run the RDU database migration script using the migrateDb.sh script. This script migrates the BACC 2.5.0.2 or BACC 2.6.x database to BACC 2.7.

Note Prior to installing the new BACC version you must run the backupDb.sh script to back up the database files. See the Cisco Broadband Access Center for Cable Administrator's Guide for additional information.

After the migration is completed, run the verifyDb.sh script to check database consistency. Verification is an optional step and may be skipped if shorter downtime for migration is critical.

Each time a migration is performed, information is recorded in a migration log file, which is stored in <BACC_DATA>/rdu/logs directory. The migration.log file identifies which version of the database is being migrated.

Start the RDU using "bprAgent start rdu" command and observe messages about successful initialization in the rdu.log file.

Caution The RDU should not be started while migration is in progress; any attempt to restart the RDU results in a series of error messages being written into the rdu.log file. These messages will indicate that database migration is needed before the RDU can be restarted.

Migrating from BACC 2.5.0.2

When migrating from release 2.5.0.2, you must use command line parameters to specify the file system directory for temporary storage when running the migrateDb.sh script. This script is located in the <BACC_HOME>/migration directory.

When running this script, use this syntax:

./migrateDb.sh temp_dir

Where temp_dir identifies the temporary directory.

When performing this migration, you must allow for the available disk space required for temporary storage. The available disk space must be at least the same as the size of the old database files. However, for performance reasons, Cisco recommends that you locate this directory on a different disk from the database and the database log files.

Internally, the migration process from BACC 2.5.0.2 is a two-step process. The first step, migration from BACC 2.5.0.2 to BACC 2.6 generates a migration25to26.log file. The second part, from BACC 2.6 to 2.7 generates a migration26to27.log file.

•If migration is interrupted during the first part, from BACC 2.5.0.2 to BACC 2.6, migration restarts from where it left off, and the same migration log continues to be used.

•If migration is interrupted during the second part, from BACC 2.6 to 2.7, migration restarts from the beginning. The old migration log is renamed with a suffix with the timestamp and a new migration log is created.

If migration is interrupted during the first part, and a clean restart of migration from BACC 2.5.0.2 is required, you must:

Step 1 Delete all files from the temporary directory.

Step 2 Rerun the database migration script.

Step 3 Start the RDU to initialize the database.

Step 4 Run the verifyDb.sh script to verify database consistency (optional).

Step 5 Restart the RDU after migration is complete and the database verified.

Migrating from BACC 2.6

When migrating 2.6.x, no command line parameter is needed.

Use this syntax:

./migrateDb.sh

Migrating from BACC 2.6 generates a migration26to27.log file.

Interrupting the migration from BACC 2.6.x to BACC 2.7 restarts the migration from the beginning. The old migration log is renamed with a suffix with the timestamp and a new migration log is created.