|Oracle® Communications Service Broker Netra 6000 High Availability Manager Administrator's Guide
Part Number E20234-01
This chapter describes how to upgrade Oracle Communications Service Broker Netra 6000 High Availability Manager (HA Manager) software components.
You can upgrade software components using the Administration Console. You can update the following components:
This chapter explains how to upgrade deployment packages only.
For information about upgrading individual bundles, see "Managing Bundles in the Administration Console" in the "Managing Service Broker Domains" chapter in Oracle Communications Service Broker Configuration Guide.
Note:Instructions on whether to upgrade bundles individually or to upload a new Deployment Package are provided together with an upgrade patch.
To upgrade HA Manager components, the HA Manager implements Open Services Gateway initiative (OSGi) architecture. According to this architecture, the HA Manager software is modular, grouped into replaceable deployment packages.
Each deployment package contains one or more bundles that implement a certain functionality. You manage these bundles as a unit. For example, bundles that implement the Diameter SSU are grouped into a deployment package. This enables you to install Diameter SSU bundles together as a single unit.
Deploying a particular functionality might require you to install multiple deployment packages.
You can install and uninstall deployment packages using the Administration Console. See "Upgrading the HA Manager Software" for more information.
To add functionality, you upload the Oracle deployment package named Full Package. Full Package contains a complete set of bundles required for the new functionality.
Figure 11-1 shows how installing a Full Package with three new bundles is added to the existing deployment package of four bundles. Following the upgrade, HA Manager supports seven bundles, numbered from 1 to 7.
You can upgrade deployment packages in the following ways:
All bundles in an existing deployment package. See "About Upgrading Entire Deployment Packages" for more information.
Specific bundles in an existing deployment package. See "About Upgrading Specific Bundles in a Deployment Package" for more information.
New bundles to an existing deployment package. See "About Adding New Bundles to a Deployment Package" for more information.
To upgrade all bundles in an existing deployment package, you upload the Full Package that contains new versions of all bundles that the existing deployment package contains.
Figure 11-2 shows how installing a Full Package with three new bundle versions replaces the existing deployment package with earlier-version bundles of the same name. Following the upgrade, HA Manager supports upgraded versions of existing bundles.
To upgrade specific bundles in an existing deployment package, you upload the deployment package named Fix Package. Fix Package contains only the upgraded bundles. When you upload Fix Package, bundles not included in the Fix Package remain intact in the original deployment package.
Figure 11-3 shows how installing a Fix Package with new bundle versions replaces existing deployment package with earlier-version bundles of the same name. If the Fix Package does not contain a bundle with the same name as an existing bundle, the bundle remains intact in the deployment package. Following the upgrade, HA Manager supports upgraded versions of specific bundles.
To add new bundles to an existing deployment package, upload the Fix Package that contains only new bundles to be added to an existing deployment package.
Figure 11-4 shows how installing a Fix Package adds two new bundles to the three bundles in the existing deployment package. Following the upgrade, HA Manager supports five bundles in the deployment package compared to three before the upgrade.
The deployment package upgrade process works as follows, regardless of the upgrade type:
You upload a deployment package to HA Manager using the Administration Console.
HA Manager installs the deployment package on Signaling Servers or Processing Servers in the domain.
You restart each Signaling Server and Processing Server in the domain for the new deployment package to take effect.
Figure 11-5 shows the Managed Upgrade window, which you use to upgrade deployment packages.
The Managed Upgrade window consists of the following areas:
Packages List pane: Displays the Packages navigation tree which lists the installed packages.
Package Management pane: Displays the name and version of the bundle or package selected in the Packages List pane.
Uploading Packages area: Use this field to locate a package on a local drive and install the package on HA Manager.
You can manage HA Manager software upgrades by performing the following actions:
You can install new deployment packages and upgrade existing deployment packages by uploading packages to HA Manager using the System Administration Console. The procedure for installing Full Packages and Fix Packages is the same. After a package is installed, you restart the servers for the installation to take effect.
To install a deployment package:
On the System Administration Console toolbar, click Lock & Edit.
You can now make changes in HA Manager configuration settings.
On the toolbar, click Switch to Offline Mode and then click OK in the confirmation window.
Note:You can install deployment packages in offline mode only.
Click the Managed Upgrade tab.
The Upload File dialog box appears.
The File Upload dialog box appears.
Navigate to the directory that contains the deployment package you want to install and click Open.
A message confirming that the package was successfully uploaded appears.
In the Managed Upgrade window, click Install / Update to install the package that you uploaded.
HA Manager installs the deployment package on the servers.
Restart the Signaling Servers and Processing Servers for the uploaded deployment package to take effect.
See "Managing and Monitoring Hardware and Processes" for information about restarting servers.
Upgrading adds or updates packages based on the type of package you uploaded:
If you installed a Full Package, and a Deployment Package with the same name does not exist, the Deployment Package is installed as a new package.
If you installed a Full Package, and a Deployment Package with the same name already exists, all bundles of the existing package are replaced with the bundles from the uploaded Full Package.
If you installed a Fix Package, existing bundles are updated or new bundles are added to an existing package.
You can uninstall existing deployment packages using the Administration Console. After a package is uninstalled, you must restart servers for the new configuration to take effect.
To uninstall a deployment package:
On the Administration Console toolbar, click Lock & Edit.
You can now make changes to HA Manager configuration settings.
On the toolbar, click to Switch to Offline Mode and then click OK in the confirmation window.
Note:You can uninstall Deployment Packages in offline mode only.
In the Packages navigation tree, select a package to uninstall.
Note:You can use the Managed Upgrade window to uninstall packages only. You cannot uninstall individual bundles. For instructions on uninstalling individual bundles, see "Managing Bundles in the Administration Console" in the "Managing Service Broker Domains" chapter in Oracle Communications Service Broker Configuration Guide.
In the Package Management pane, click Uninstall.
The Uninstall Package progress bar appears. After HA Manager uninstalls the package from the Signaling Servers and Processing Servers the Packages tree is refreshed to display the updated list of packages.
Restart the Signaling Servers and Processing Servers for the new configuration to take effect.
See "Managing and Monitoring Hardware and Processes" for information about restarting servers.
If installation or uninstallation fails (for example, when a server on which HA Manager tries to install a deployment package is unavailable), HA Manager displays an error message in the Administration Console and restores the previous version of the deployment package.
You can upgrade the operating system on the Bootstrap Blades and the Worker Blades. To automate the upgrade process, Oracle provides upgrade patches that contain all files required for the upgrade:
Red Hat Package Manager (RPM) files, which contain package files required to upgrade the operating system
Upgrade script, which manages dependencies to ensure that the required files are installed
Installation notes, which provide detailed guidelines on how to install the upgrade patch
Note:During the upgrade process, the upgrade script merges existing RPM files with newer versions of these files. If you made any changes in the RPM files, the upgrade script might be unable to merge these files with their new versions. In this case, the script does the following:
For the new version of the RPM file, the script creates the file with the rpmnew extension
For the file modified by you, the script creates the file with the rpmsave extension
Although the upgrade script can automatically detect these cases, you need to manually resolve the conflicts. For more information, see the installation notes provided with the upgrade patch.
You can upgrade the operating system only on secondary Bootstrap Blades. (See "Primary and Secondary Bootstrap Blades" for more information about primary and secondary Bootstrap Blades. After you complete the upgrade, you can switch the Bootstrap Blade from secondary to primary.
To upgrade the operating system on the Bootstrap Blades:
In a Linux command-line interface, log in to the server on which the Bootstrap Blades are installed.
Check the current status of the Bootstrap Blades by entering the following command in the shell:
The following information is returned:
IP addresses of the Bootstrap Blades that the cluster contains
ID and status of each Bootstrap Blade
Services on the Bootstrap Blades and the state of these services. The Bootstrap Blade that contains a service with a state of Started is the primary Bootstrap Blade.
[root@bootstrap1 ~]# clustat Cluster Status for ocsba @ Tue Dec 28 07:56:28 2010 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ 192.168.1.1 1 Online, Local, rgmanager 192.168.1.2 2 Offline Service Name Owner (Last) State ------- ---- ----- ------ ----- service:ip 192.168.1.1 started
Make the primary Bootstrap Blade the secondary blade by entering the following command:
service rgmanager restart
The service parameter specifies the name of the service that runs on the primary Bootstrap Blade. For example:
ip rgmanager restart
The primary Bootstrap Blade is now in the secondary state.
Unpack and run the upgrade patch that you received from Oracle, as described in the upgrade patch documentation.
You can upgrade the operating system using the upgrade script that you received with the upgrade patch.
To upgrade the operating system on the Worker Blades:
Copy the RPM files that the upgrade package contains to the RPM repository at /var/ocsb/ramdisk/rpm.
Run the RAM disk upgrade script as described in the upgrade patch documentation.
The script rebuilds the RAM disk image based on the RPM files that you copied to /var/ocsb/ramdisk/rpm.
Enter your root and ocsb password when prompted.
The resulting RAM disk image is copied to the TFTP directory.
Reboot all Worker Blades as specified in the patch documentation.
The Worker Blades load the new RAM disk image from the TFTP directory.