Table Of Contents
Upgrade Procedure
Upgrading from Version 3.0 to Version 3.1
Upgrade Procedure
This module details the upgrade procedure for upgrading from a functional SCA BB 3.0 deployment to SCA BB 3.1.
This is a high level description of the procedure. The specific details are found in the corresponding user manuals.
The procedure describes a scenario where the Service Control deployment is required to continue functioning throughout the upgrade procedure with SCE platforms running SCA BB 3.0 and SCE platforms running SCA BB 3.1 are operating concurrently (using the same CM and SM servers).
This procedure is meant to minimize service downtime (for however long the upgrade process takes), bound to several limitations, as described in the preceding sections.
Upgrading from Version 3.0 to Version 3.1
SUMMARY STEPS
1. 
Upgrade the SM (or SM cluster) according to the procedure described in the SM user manual
2. Deploy or upgrade the CM to 3.1
3. Upgrade the SCE platform software (SCOS and application PQI).
4. Remove the second CM running the former version (if one was used) once the upgrade of all SCE platforms is complete.
DETAILED STEPS
Step 1 Upgrade the SM (or SM cluster) according to the procedure described in the SM user manual
a. Uninstall the SCA BB application and the SM LEGs' PQIs
b. Run the SM upgrade script.
c. Install the SCA BB application and the SM LEGs' PQIs.
d. Configure the SCE cascade to the SM as described in the Cisco SCMS Subscriber Manager User Guide .
This step is required because in version 3.1, the SM is aware of SCE cascade topologies and must be configured accordingly. Immediately after the upgrade, all SCEs are configured to the SM as standalone SCEs. You must configure the SCEs manually after the upgrade of an SCE pair.
e. Configure the cascade SCEs as a cascade pair in the SM configuration.
This causes the SM to treat the standby SCE that will be upgraded to 3.1.0 in the correct way and not send subscriber updates to it.
The SM will not update an SCE that is identified as standby even if it is configured as 'standalone' in the SM.
f. Only after the SM is configured correctly can you update the SCEs.
Step 2 Deploy or upgrade the CM to 3.1
•In the case of deployment of an additional CM and database for the transition phase ( two CM databases in total, regardless of whether or not the configuration is bundled), collection will work for all SCE platforms (both the older version and 3.1). Regarding non-bundled databases , there may be several ways to implement this; it is recommended to consult a DB specialist if you are using a non-bundled database.
–Each CM collects RDRs from a single version, to a distinct database (either bundled or non-bundled) and CSV repository.
Step 3 Upgrade the SCE platform software (SCOS and application PQI).
This also applies in the case of an SCE platform cluster. See the SCE Installation Guide and the Software Configuration Guide for more details.
The SCE platform upgrade procedure involves the following high-level steps:
•Retrieve the service configuration (PQB)—Use a 3.0 SCA BB Console.
•Update the service configuration to 3.1—Open the old service configuration in the Service Configuration Editor in the new Console, and make any necessary adjustments to the old service configuration. These changes are described in the SCA BB 3.1 Release Notes . Alternatively, create a new service configuration using the 3.1 Service Configuration Editor.
•Use the 3.1 Network Navigator GUI to install SCOS 3.1—Install PQI 3.1 on the SCE platform and then install the latest protocol pack on top of SCA BB 3.1.
•Apply the service configuration to the SCE platform.
–Each SCE platform remains functional from a traffic control perspective from the completion of the SM upgrade until it is upgraded, and then again after the upgrade. On High Availability configurations, no service downtime is expected as the SCE upgrade is performed when the SCE is in standby mode.
–Make sure the upgraded SCE platform RDRs are directed to the CM running version 3.1. Service downtime (from a collection perspective) depends on the CM configuration that you have implemented (single or dual during the upgrade).
For a cascade SCE pair:
•Verify that the SM was already upgraded to 3.1.
•Upgrade the standby SCE as described above.
•Force a fail-over.
•Upgrade the new standby SCE (the formerly active SCE) as describe above.
At this stage, the entire solution is upgrade and fully operational.
Step 4 Remove the second CM running the former version (if one was used) once the upgrade of all SCE platforms is complete.
