-
null
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.
This chapter describes how to upgrade Broadband Access Center for Cable (BACC) 2.6.x versions to BAC 2.7.1.
Table 6-1 summarizes the upgrade tasks required for BAC components for different versions.
Note This release does not support the appliance DPE-590. You can, however, upgrade the DPE-590 to BAC 2.7, which is compatible with a BAC 2.7.1 RDU.
You should upgrade the components in the order specified below. Do not perform the upgrade in any other order as this may lead to unpredictable results.
5. Upgrading Network Registrar Extensions
To upgrade all BAC components, follow these procedures:
Step 1 Untar the upgrade file (271upgrade.tar) on the computer on which the BAC components reside.
For example:
tar -xvf 271upgrade.tar
The component upgrade scripts are extracted to the patch271/bin upgrade folder.
Step 2 To back up the RDU database files, run the backupDb.sh script in the BPR_HOME/rdu/bin directory.
For example:
# backupDb.sh /var/backup
where /var/backup identifies the database backup directory.
In this example, all backup database files are stored in a directory called /var/backup/rdu-backup-20070316-031028. The last subdirectory (rdu-backup-20070316-031028) is automatically created with a current time stamp.
Note The time-stamped subdirectory format is rdu-backup-yyyyMMdd-HHmmss. In this example, the subdirectory would be rdu-backup-20070316-031028, meaning that the directory contains a backup that was started at 3:10:28 a.m. on March 16, 2007.
Step 3 After backup, perform a database recovery.
For additional information on using the backupDb.sh tool and database recovery, see the Cisco Broadband Access Center Administrator Guide 2.7.1.
Step 4 Verify database integrity.
Note We recommend that you run the migration process on a staging (non-production) system, instead of on a live system during RDU downtime. We do not recommend verification of database integrity during live migration, because, if the database is large, verifying the database integrity will take a long time.
To verify the database, run the verifyDb.sh tool on a backup of the RDU database.
For example:
#/opt/CSCObpr/rdu/internal/db/bin/verifyDb.sh -dbdir /disk1/backup
Note To verify the database before migration, use the verifyDb.sh tool from the BAC installation corresponding to the version of the database.
If you find any errors in the database, contact the BAC deployment team. For more information on the verifyDb.sh tool, see the Cisco Broadband Access Center Administrator Guide 2.7.1.
To upgrade the RDU:
Step 1 Run the setup.bin file associated with a new installation of BAC. 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 as described in Migrating the RDU Database.
To upgrade the installed Solaris DPE from the 2.6.x and 2.7 versions to 2.7.1:
Step 1 From the upgrade folder, run:
./271-upgrade-dpe.sh
Output similar to the following appears.
BPR Located
BPR Home directory is /opt/CSCObpr
Current version is 2.6.2(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.1 Completed Successfully
Please start your BPR Agent to finish the upgrade Process
Step 2 You must manually restart the DPE agent to finish the upgrade process.
For example, from the command line, run:
# /etc/init.d/bprAgent start dpe
Step 3 To verify if the version information indicates BAC 2.7.1, enter:
# pkgparam CSCObpr VERSION
Note The previous version of the file bpr.jar is renamed bpr-2x.jar and resides in the
BPR_HOME/lib directory.
You may remotely patch your DPE devices, or if you have local access to these devices, you can fully reimage them. For the required reimaging procedure, refer to the DPE-2115 Recovery CD-ROM Release Notes that accompanied the DPE device.
Note This release does not support the appliance DPE-590. You can, however, upgrade the DPE-590 to BAC 2.7, which is compatible with the BAC 2.7.1 RDU.
To upgrade the DPE component to release 2.7.1:
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 filename.
Note When opening the FTP connection, you must enter the username admin and the login password chosen for the selected DPE.
Step 2 Once an FTP connection is established, change to the /incoming directory at the FTP prompt:
# cd incoming
This command locates the patch file so that the DPE can easily find it.
Step 3 Select the upgrade file corresponding to the BAC version currently running on your DPE and use the FTP facility to copy the file to the DPE.
|
|
---|---|
|
|
2.7 |
dpe-2115-27xto271-upgrade.bpr |
2.6.2.x |
dpe-2115- 262xto271-upgrade.bpr |
For example, use this command to copy the DPE-2115 upgrade file via FTP from BAC 2.6.2.x to BAC 2.7.1:
bin
put dpe-2115-262xto271-upgrade.bpr
Step 4 Log in to each DPE in the privilege mode, and run the upgrade command.
Step 5 When prompted to select the 2.7.1upgrade file, select and apply the file.
Once the upgrade is complete, the DPE reboots.
Step 6 Log in to each DPE in the privilege mode, and run the show version command. This command should identify the current software version running on the DPE as BAC 2.7.1.
Use this procedure to upgrade the Cisco Network Registrar extensions from BAC 2.6.x or 2.7 to BAC 2.7.1:
Step 1 Run the 271-upgrade-cnrep.sh script.
Step 2 Stop the Network Registrar Server Agent when prompted.
The upgrade script automatically copies the upgraded extension point files to the required directories. When complete, it prompts you to restart the Network Registrar Server Agent.
Step 3 To verify if the output information indicates BAC 2.7.1, enter:
# pkgparam CSCObpr VERSION
Step 4 Go to the BPR_HOME/lib directory. If the upgrade was successful, the directory content appears similar to the list of installed files 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 bpr-2x.jar and resides in the BPR_HOME/lib directory.
Step 5 To verify one more time if the installation upgrade was a success, go to the NR_HOME/extensions/dhcp/dex directory and verify if the following files appear:
-rwxr-xr-x 1 root bin 60904 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.so
Note The NR_HOME path defined in this step is the Network Registrar installation directory (the default directory is /opt/nwreg2), followed by the /regional or /local directory depending on the Network Registrar version that you have installed on your system.
Depending on the components installed, the directory content shown in this procedure may differ from the output featured above.
Note The BAC 2.7.1 KDC requires a new license. Before you start the BAC agent, ensure that the correct license and certificates are installed.
To upgrade the KDC from BAC 2.6.x or 2.7 to BAC 2.7.1:
Step 1 Run the 271-upgrade-KDC.sh script.
Step 2 Manually start the BAC agent to complete the upgrade process.
Step 3 To verify if the output information indicates BAC 2.7.1, enter:
# pkgparam CSCObpr VERSION
Step 4 Go to the BPR_HOME/kdc/internal/bin directory. If the upgrade was successful, the directory content appears similar to this output:
-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 Depending on the components installed, the directory content shown in this procedure may differ from that featured above.
The RDU database migration script lets you migrate your RDU database from BAC 2.6.x or 2.7 to BAC 2.7.1.
The migration script is automatically installed when you run the BAC 2.7.1 installation program (setup.bin). The installation program unpacks the migration script file, migrateDb.sh, into the BPR_HOME/migration directory. When using BAC 2.6.x or 2.7, you must run migrateDb.sh to migrate the RDU database to 2.7.1.
When migrating from BAC 2.6.x or 2.7, ensure that you:
•Use command-line parameters to specify the file system directory for temporary storage when running the migrateDb.sh script. This script resides in the BPR_HOME/migration directory.
•Allocate the available disk space to at least match the size of the old database files. For performance reasons, we recommend that you locate this temporary directory on a disk that differs from the one on which the database and the database log files are located.
To migrate your 2.6.x or 2.7 RDU database:
1. Run the migrateDb.sh script. For example:
# ./migrateDb.sh
2. After migrating the RDU database, ensure you complete the post-migration activities depending on your BAC version, as described in Post-Migration Activities.
Start the RDU using the bprAgent start rdu command and observe messages about successful initialization in the rdu.log file.
Table 6-2 describes the activities that you must complete after migrating your BAC 2.6.x or 2.7 database
Each time you migrate your database, information is recorded in a migration log file, which is stored in the BPR_DATA/rdu/logs directory. The migration.log file identifies the version of the database that is being migrated.