Upgrading from BAMS Release 2.68 to BAMS Release 3.10
Introduction
This appendix explains how to upgrade a redundant Cisco Billing and Measurements Server (BAMS) system from Release 2.68 to Release 3.10 software.
Note Before beginning this upgrade procedure, read the entire appendix to familiarize yourself with the prerequisites, major steps, and differences between the two releases.
Conversion utilities are provided in the Release 3.10 software that convert configuration and data files from Release 2.68 to Release 3.10 format. Releases before Release 2.68 are not supported. Node 1 of the Release 3.10 software is provisioned with the configuration information from the Release 2.68 system.
Note Ensure that your Release 2.68 software is up to Patch 7 before commencing this procedure.
Note BAMS Release 3.10 requires Solaris 8. You must install Solaris 8 after performing the backup and software uninstall (pkgrm) procedures explained below, but before installing BAMS 3.10. For information see "Installing the Sun Solaris 8 Operating System" section.
Upgrade Procedure
Use the following procedure to upgrade from BAMS Release 2.68 to BAMS Release 3.10:
Step 1 Log in as the BAMS user and stop the application for BAMS units 0 and 1:
Step 2 Perform the following for BAMS unit 0:
a. Use the change_mode utility to configure unit 0 as simplex. Do not change the measurement interval.
b. Using MML, modify the Poll table to rename files:
$
mml
mml> prov-sta::srcver=active,dstver=migration,confirm
mml> prov-ed:POLL:site-name="<site name>", action="R"
mml> prov-dply::
c. Export all MML parameters:
$
mml
mml> prov-exp:all:dirname=migration
mml> quit
This creates the file /opt/CiscoBAMS/files/mml/migration/all.mml.
Step 3 Back up data files and uninstall the application on BAMS unit 1:
a. To back up the data files, log in as the root user:
#
cd /opt/CiscoBAMS/data
# find . -print | xargs tar cvf /dev/rmt/0
# cd /opt/CiscoBAMS/CDR/archive
# find . -print | xargs tar cvf /dev/rmt/0
b. Remove the BAMS software on unit 1 using the pkgrm utility. Answer "yes" when asked to remove the data and archive directories.
c. Upgrade the operating system from Solaris 2.6 to Solaris 8 on unit 1.
d. Install BAMS Release 3.10 on unit 1.
e. Go to the Cisco Web site and download the latest patch for BAMS Release 3.10.
f. Install the patch.
g. Log in as the BAMS user.
h. Configure unit 1 as simplex using the change_mode utility.
i. Specify this unit as UNITNO=1 by modifying the file /opt/CiscoBAMS/bin/sym_defs.
j. Source the sym_defs file to update the environment variables:
$
. /opt/CiscoBAMS/bin/sym_defs
Step 4 Copy the MML batch file /opt/CiscoBAMS/files/mml/migration/all.mml from BAMS unit 0 to BAMS unit 1, /opt/CiscoBAMS/files/mml/all.phase2.mml. Convert this batch file from Release 2.68 to Release 3.10 format using the prov_2to3 utility provided in the Release 3.10 software:
$
cd /opt/CiscoBAMS/files/mml
$
prov_2to3 -i all.phase2.mml -D /opt/CiscoBAMS/contrib/BAMS3node1_top.mml -o
BAMS3node1.mml
Note The prov_2to3 command above should appear on one line.
Note Step 4 generates the file /opt/CiscoBAMS/files/mml/BAMS3node1.mml. Because of design changes in BAMS Release 3.10, this file contains most but not all of the MML commands you use to provision the processing tables from the Release 2.68 configuration. Here are the tables not carried over:
The System Parameters (SYSPARMS) table has been expanded and is now called NODEPARMS. The SYSPARMS entries from the Release 2.68 configuration are not carried over, and the default Release 3.10 values for NODEPARMS are in the file BAMS3node1.mml. Examine these values to make sure they are correct.
The TCA-TBL (thresholds) table has been significantly expanded in Release 3.10. The file BAMS3node1.mml must be manually edited if measurement parameters are to be provisioned in this migration procedure. Refer to the "TCA-TBL Tag ID" section.
The Skip CDE table of Release 2.68 has "5000" as a default entry. Because this CDE TAG can be processed in BAMS Release 3.10, this table entry is not carried over in this migration procedure.
Step 5 Once all necessary changes have been made to the file BAMS3node1.mml, configure BAMS unit 1 with the BAMS3node1.mml batch file:
$
cd /opt/CiscoBAMS/files/mml
$ mml -b BAMS3node1.mml
Step 6 Copy all files from the directory /opt/CiscoBAMS/data/output of BAMS unit 0 to BAMS unit 1, /opt/CiscoBAMS/data/s01/output. You must convert these files from the Release 2.68 to the Release 3.10 format using the cnv_outputdir.sh utility provided in the Release 3.10 software. Execute the following:
$
cd /opt/CiscoBAMS/data/s01/output
$ cnv_outputdir.sh
This script converts all Release 2.68 data files in the directory /opt/CiscoBAMS/data/s01/output to Release 3.10 format. Any files not converted are listed by this script and are stored in the /opt/CiscoBAMS/data/s01/output/unprocessed directory. Verify that this directory is empty. Any files that are left unprocessed in this directory should be forwarded to Cisco for further analysis. Files that were successfully converted are stored in the /opt/CiscoBAMS/data/s01/output/processed directory.
Step 7 Modify the Poll and Switch Information tables on BAMS unit 1:
Obtain the values for the SWITCHINFO fields from the file /opt/CiscoBAMS/files/ctb_cfg on BAMS unit 0:
$ cat /opt/CiscoBAMS/files/ctb_cfg
CTB -I$AUG_DIR_OUT -O$CTB_DIR_OUT -iaug_ct -obaf_ -s118 -x12345 -r118 -R67890
Here is the mapping between the ctb_cfg parameters and the Switch Information table:
ctb_cfg SWITCHINFO parameter
-s sensortype
-x sensorid
-r recoffctype
-R recoffcid
$
mml
mml>
set-node:1:
mml>
prov-sta::srcver=active,dstver=test,confirm
mml>
prov-ed:POLL:file-suffix1=".finished",file-suffix2=".finished"
mml>
prov-ed:SWITCHINFO:sensortype="sss",sensorid="xxxxx",recoffctype="rrr", recoffcid="RRRR"
mml> prov-dply::
The Poll tables on BAMS units 0 and 1 have now been configured so that BAMS unit 0 polls files from the MGC units and renames the files with a suffix of ".finished" after a successful poll. BAMS unit 1 then polls the "*.finished" files after they have already been polled and renamed by unit 0, and deletes these files after a successful poll. Both units process the same files, each in simplex mode.
Step 8 Use the MML chgno command to change the sequence number from "1" to "value_on_the_2.68_machine":
$
mml
mml> chgno::seqno1=x (where "x" is the CDR file number from the PGW)
Step 9 Set up the polling passwords:
$ setpollpwd -s 1
New value for 'userid1' []:
Enter password for 'password1':
password again -
New value for 'userid2' []:
Enter password for 'password2':
password again -
Step 10 Set the names for the BAMS units:
$ setbamunit
value for 'bam-name0' []:
value for 'login0' []:
Enter password for 'passwd0':
again password -
New value for 'bam-name1' []:
New value for 'login1' []:
Enter password for 'passwd1':
again password -
Step 11 Start both units with the start_system command. After several files have been polled and processed by BAMS unit 0, stop the application on BAMS unit 0 using the stop_system command.
Step 12 Allow enough time for BAMS unit 1 to poll and process all the files polled and processed by BAMS unit 0, and then stop the application on BAMS unit 1, using the stop_system command.
Step 13 Compare the output files on both units and verify that BAMS unit 1 is generating valid output files in the following directories:
/opt/CiscoBAMS/data/s01/BAF
/opt/CiscoBAMS/data/s01/ASCIIBAF
/opt/CiscoBAMS/data/s01/Measurements
/opt/CiscoBAMS/data/s01/ASCII
/opt/CiscoBAMS/data/s01/p001
Note The filenames are slightly different because unit 0 processed files with a .bin suffix, and unit 1 processed files with a .finished suffix from the MGC.
Compare the files in subdirectories BAF and ASCII directly with the files from unit 0. The files from the Measurements subdirectory will have some differences because of changes in how statistics are generated in Release 3.10.
The files in ASCIIBAF, EXTASCII, NICS, and P01 are new output types for Release 3.10.
In the ASCII output, one additional field has been added to the end (TAG 5000, Global Call id). You can use the skipcde parameter to no-write the GCI, but a comma placeholder there gives the record 48 fields.
In the measurement files, an extra field has been added to indicate whether a threshold crossing was exceeded for that interval.
If you find any problems, they must be fixed before proceeding further. Any differences would likely be due to provisioning errors.
If no problems are found, remove the following directories:
$ cd /opt/CiscoBAMS/data/s01/output
$ rm -rf processed unprocessed
These directories were created in step 6 and are no longer needed.
Step 14 If verification of the data is successful, upgrade unit 0 from Release 2.68 to Release 3.10 software:
a. To back up the data files on unit 0, log in as root on unit 0:
# cd /opt/CiscoBAMS/data
# find . -print | xargs tar cvf /dev/rmt/0
# cd /opt/CiscoBAMS/CDR/archive
# find . -print | xargs tar cvf /dev/rmt/0
b. Remove the BAMS software on unit 0 using the pkgrm utility. Answer "yes" when asked if you want to remove the data and archive directories.
c. Upgrade the operating system from Solaris 2.6 to Solaris 8 on unit 0.
d. Install BAMS software Release 3.10 on unit 0.
e. Go to the Cisco Web site and download the latest patch for the BAMS 3.10 release.
f. Install the patch.
g. Log in as the BAMS user.
h. Configure unit 0 as redundant using the change_mode utility.
i. Source the sym_defs file to update the environment variables:
$ . /opt/CiscoBAMS/bin/sym_defs
j. Execute the setbamunit utility and specify the host names and login information for units 0 and 1.
Step 15 Follow these steps for unit 1:
a. Using MML, modify the Poll table:
mml>
set-node:1:
mml> prov-sta::srcver=active,dstver=migration,confirm
mml> prov-ed:POLL:file-suffix1=".bin", file-suffix1=".bin"
mml> prov-dply::
b. Reconfigure BAMS unit 1 as redundant using the change_mode utility.
c. Execute the setbamunit utility on BAMS unit 1. Specify host names and login information for both BAMS units.
d. Copy the configuration information on unit 1 to unit 0 by executing the MML commands:
mml>
set-node:1:
mml> prov-sync::
Step 16 Use MML to start both BAMS units:
$
mml
mml:sys> sta-softw