Upgrading Offline Mediation Controller

7 Upgrading Offline Mediation Controller

This chapter describes how to upgrade to the latest release of Oracle Communications Offline Mediation Controller.

In this chapter, the Offline Mediation Controller 12.0 release running on your system is called the old release. The Offline Mediation Controller 15.0 release you are upgrading to is called the new release.

Topics in this chapter include:

About Upgrading Offline Mediation Controller

The upgrade process includes these tasks:

Ensure that the old release components are started.
Install and start the new release. See "Installing and Starting the New Release" for more information.
Export and import:

Note:

You cannot directly upgrade from the old release to the new release; instead you must export the configuration of the old release and import the configuration to the new release.
1. Export the configuration of the old release.
  
  See "Exporting a Configuration" for more information.
2. Import the configuration of the old release into the new release.
  
  See "Importing a Configuration" for more information.
View all node and node chain configurations in the new release Administration Client to verify that all nodes and node chain configurations of the old release are duplicated on the new release.

See "Verifying the New Release Configuration" for more information.
Switch operations from the old release to the new release.

See "Upgrading the Node Chains" for more information.
Configure and save any new features or settings that you require in the new release.
Keep or remove the software and node chain configurations of the old release.

Upgrade System Requirements

See "Software Requirements" and "Hardware Requirements" for more information on the software and hardware requirements to upgrade to Offline Mediation Controller 15.0.

After you complete the upgrade procedure and start using the Offline Mediation Controller 15.0 system, you can keep or remove the previous Offline Mediation Controller version and configured node chains.

Information Requirements

This section describes the information that you must provide during the upgrade process. You define some of these configuration values when you install and configure the new release.

Note:

Oracle recommends that you print the table and record the values for future reference.

The following information is required while upgrading from the old release to the new release:

Determine whether each system has the system resources to support the new release.
Determine the IP address, port number, and name of the old release Administration Server and its node managers. You can obtain this information from the Mediation Hosts screen in Administration Client.
Determine where you want to install the new release Administration Server, Node Manager, and Administration Client. Record the planned IP address, port number, and name of the new release Administration Server and its node managers.

You can either use the default ports for your new release installation or change them in the offline_mediation.conf file, which is used by the ProcessControl script. ProcessControl starts Administration Server, and Node Manager in the OMC_home directory on the appropriate ports when the system starts. See the discussion about managing the ProcessControl script in Offline Mediation Controller System Administrator's Guide for more information.

Determine how you want to map the old release Administration Server and Node Manager addresses, ports, and names to the new release Administration Server and Node Manager IP addresses, ports, and names. Table 7-1 lists the details to map the old release to a new release.

Table 7-1 Administration Server and Node Manager Map Table

Offline Mediation Controller Component	Old Release IP Address	Old Release Port Number	Old Release Assigned Name	New Release IP Address	New Release Port Number	New Release Assigned Name
Administration Server	-	-	NA	-	55105	NA
Node Manager	-	-	-	-	55109	-
Node Manager	-	-	-	-	-	-

Installing and Starting the New Release

To install and start the new release, follow these steps:

Note:

See "Installing Offline Mediation Controller" for more information on installing Offline Mediation Controller 15.0.

Install the new release Administration Server on at least one system that you want as part of the final system.
Install the new release Node Manager on each system that you want as part of the final system.
Install the new release Administration Client on a system that you want as part of the final system.
Start the new release Administration Server and Node Manager daemons. See "Starting Component Daemons" for more information.

Exporting a Configuration

To upgrade to the new release, you must capture the node configurations of the old release in an export file, and import that file after the installing the new release.

To export the old release host configurations:

Start the old release Administration Server and Node Manager daemons.
Start the old release Administration Client.
From the Admin menu, select Export Configuration.

The Export Configuration dialog appears.
Do one of the following:
- If you want to export all the mediation hosts, select Export All Mediation Hosts.
- If you want to select the mediation hosts to export, select Selected Mediation Hosts, and then select the hosts whose configurations you want to export.
Click Browse and locate the directory in which you want to save the configuration files and click Select.
Do one of the following:
- To export a .nmx customization file that includes the exported .xml file, a .log file, an adminserver_ip_port.jar file, and a version information .xml file, click Export.
- To export only the .xml file, deselect Export Customization and click Export.
The node configurations are stored in the directory.

Importing a Customized Configuration

While importing, Offline Mediation Controller upgrades the node configurations, provides default values for new parameters, and maps nodes as necessary.

To import a customized configuration from the old release:

Start the new release Administration Server and Node Manager daemons. See "Starting Component Daemons" for more information.
Go to OMC_home/bin and run the following command:
```
./gui
```
The Welcome to Oracle Communications Offline Mediation Controller dialog appears.
Log on as the admin user.

Note:

You can create, modify, or delete users only as the administrator user.

The Oracle Communications Offline Mediation Controller Administration window appears.
From the Admin menu, select Import Customization.

The Import Customization dialog box appears.
Click Browse and select the desired .nmx export file.

The node managers display under the Old Node Manager column in the Node Manager mapping pane.
Select a Node Manager from the list and click Map.

The Map dialog box appears.
Enter Name, IP address or host name, and Port number for the new Node Manager.

For the Port number, use the Node Manager default of 55109 or the port number in Table 7-1.
Repeat step 6 and step 7 for the rest of the node managers in the list.
After mapping all node managers, click Import.

During the import customization process, the new release upgrades the nodes and provides default parameters for any new configuration options for the updated nodes.

After distribution is completed, restart Administration Server and all the Node Managers.

Importing a Configuration

While importing, Offline Mediation Controller upgrades the node configurations, provides default values for new parameters, and maps nodes as necessary.

To import a configuration:

Start the new release Administration Server and Node Manager daemons. See "Starting Component Daemons" for more information.
Go to OMC_home/bin and run the following command:
```
./gui
```
The Welcome to Oracle Communications Offline Mediation Controller dialog appears.
Log on as the admin user.

Note:

You can create, modify, or delete users only as the administrator user.

The Oracle Communications Offline Mediation Controller Administration window appears.
From the Admin menu, select Import Configuration.

The Import Configuration dialog box appears.
Click Browse and select the desired .xml export file.

The node managers display under the Old Node Manager column in the Node Manager mapping pane.
Select a Node Manager from the list and click Map.

The Map dialog box appears.
Enter Name, IP address or host name, and Port number for the new Node Manager.

For the Port number, use the Node Manager default of 55109 or the port number in Table 7-1.
Repeat Step 5 and Step 6 for the rest of the node managers in the list.
After mapping all node managers, click Import.

The new node managers are added and the corresponding nodes are created. Any errors are recorded in the upgrade log and displayed after the import.

During the import process, Offline Mediation Controller upgrades nodes and provides default parameters for any new configuration options for the updated nodes.

Verifying the New Release Configuration

When you finish exporting and importing, verify whether the nodes and node chain configurations with their current parameter settings are duplicated. Also, verify that you can start the nodes and node chains.

If any nodes were removed due to node obsolescence, you can upgrade the affected node chain configurations. For more information, see "Configuring New Features". Refer to the upgrade log file for the Node Destinations list and the Node ID Conversion Table to aid the verification procedure.

Upgrading the Node Chains

When you complete the export and import tasks, you must upgrade from the old release node chains to the new release.

To upgrade the node chains:

Configure the new release Collection Cartridge (CC) to look for incoming records in a directory different from the one in which the old release CC looks for records.
Configure the network devices to send records to the directory monitored by the new release CC.
Start all nodes in the new release node chain.
Verify data output from the new release node chain.
Stop the old release CC.
Verify the input directories of all nodes in the old release chains to ensure all files are processed.
Stop all nodes in the old release chain.

Upgrading the Wireless GGSN/SGSN Node Chain

To upgrade the GGSN/SGSN node chain from the old release to the new release, complete the following procedure.

Note:

The upgrade occurs between two separate systems so there is no connectivity between the node chains. PDP sessions that are open during the upgrade may contain partial and duplicate records since the Enhancement Processor (EP) and the Aggregation Processor (AP) cannot process these records.

To upgrade the old release GGSN/SGSN node chain:

Stop the old release GGSN/SGSN CC, Session Sequencing EP and Session Aggregation AP.
Start all nodes in the new release node chain, except the Distribution Cartridge (DC).
Open the node configuration window for the old release GGSN/SGSN CC and on the GSM3GPP tab, change the Receive Port number to 3396 and the Send Port number to 1225.
Open the node configuration window for the old release Session Sequencing EP and on the Sequencing tab change the Expiry Interval to 2 minutes.
Open the node configuration window for the old release Session Aggregation AP and on the Aggregator tab, change the Flush Time to 300 seconds (5 minutes).
Open the node configuration window for the old release DC and on the File Output tab, change the Output Push Time Unit to minutes and the Output Push Time Period to 5.
Start the old release GGSN/SGSN CC, Session Sequencing EP and Session Aggregation AP to clear the chain and wait twenty minutes to ensure the old release chain processes and outputs all data.
Verify the input directories of all nodes in the old release chain to ensure all files are processed and then stop the chain.
Start the new release DC.
Verify data output from the new release node chain.

Troubleshooting Import Errors

The import process uses a best effort approach where any successfully created node managers and nodes remain intact, even if errors occur during the import.

If an import has errors or terminates abnormally, examine the following files:

Console session history
Import log

You can find the import log file in the log directory of the installation directory. For example:
```
OMC_home/log/import_DateTime.log
```

The import log file resides on the same system as Administration Client.

If needed, call Oracle Global Support and supply information from the console session history or the upgrade log file.

Switching to a New LDAP Installation

If you are switching from an existing to a new LDAP installation, you must perform the following procedure after completing the installation and upgrade steps.

To change LDAP versions

On the host system running LDAP, locate the old slapd process in the installation directory.

The following list shows the default installation directories.
- 5.0.1: NetworkMediation501
- 6.0: ocomc
Run the following command using the appropriate installation directory:
```
# ps -eaf | grep slapd
```
The following information is displayed:
```
   root 2821   1 0 10:11:37 ?   0:00 /
Install_Directory/ldap/libexec/slapd -f /
Install_Directory/...
```
Where Install_Directory is the directory where you have installed the LDAP server.
Run the following command to kill the old LDAP process:
```
# kill 2821
```

Run the following command to populate directory script:

OMC_home# /ocomc/ldap/data/populateDir

Where OMC_home is the directory in which you installed Offline Mediation Controller.

The following information is displayed:

Starting slapd on TCP/IP port 389...
/OMC_home/ldap/libexec/slapd -f 
/OMC_home/ldap/etc/slapd.conf -p 389
Waiting 5 seconds for slapd to start...
Populating the directory...
Verifying entries...
Directory populated successfully.

Run the following command to verify that slapd is running:
```
# ps -eaf | grep slapd
```
The following information is displayed:
```
   root 4529   1 0 11:04:02 ?   0:00 /OMC_home/ldap/libexec/slapd -f /OMC_Home/ldap/etc/slapd.conf 
```
You can now log on using the new LDAP installation. The default login user ID and password is admin.

Data from the old LDAP system is not transferred into the new LDAP system. You must re-create users and passwords for the new LDAP system.
When you are satisfied with the new LDAP installation, modify the host system startup scripts so the former LDAP server does not startup upon reboot using the following command:
```
# rm /etc/rc2.d/S81slapd
```

Configuring New Features

After upgrading from the old release to the new release, you must configure any features that are new to Offline Mediation Controller 15.0. For a list of new features, see Offline Mediation Controller 15.0 Release Notes.