How to prepare and upgrade an existing Tivoli Netcool Performance Manager 1.3.1 environment to Tivoli Netcool Performance Manager 1.3.2.
Shutting down the Tivoli Netcool Performance Manager components
The Tivoli Netcool Performance Manager components, except for the Database and Tivoli Integrated Portal, need to be shut down for the upgrade procedure.
There are a number of shutdown scenarios available:
v Shut down the DataChannel and DataMart components on all hosts now, leaving the DataLoad collectors running.
An overview of the strategy is as follows:
1. Shut down the DataChannel and DataMart components on all hosts now.
2. Follow all the instructions in this chapter up to the section, “Deploying the upgrade topology” on page 93
3. When deploying, deploy all components but DataLoad.
4. When this deployment is complete, shut down DataLoad, deploy the DataLoad component, and then restart all components.
This upgrade strategy reduces the period of no collections as the DataLoad collectors are only stopped while the installer deploys the upgraded DataLoad topology.
To use this strategy, perform all steps in this chapter, choosing “Deploy the upgrade topology for all components” on page 94 when you deploy your upgrade topology.
v Shut down the DataChannel and DataMart components on all hosts now, and deploy the upgrade topology in your environment to upgrade only one host at a time.
An overview of the strategy is as follows:
1. Shut down the DataChannel and DataMart components on all hosts now.
2. Follow all the instructions in this chapter up to the section, “Deploying the upgrade topology” on page 93
3. If a host is running a DataLoad collector, you only shut down that collector, then upgrade the Tivoli Netcool Performance Manager components on that host.
This upgrade strategy minimizes the period of no collections by only stopping one DataLoad collector at a time, leaving other collectors available for data collection.
To use this strategy, perform all steps in this chapter, choosing “Deploy the upgrade topology to minimize collections loss” on page 96 when you deploy your upgrade topology.
Note: Tivoli Integrated Portal must remain running. If Tivoli Integrated Portal is not running, the Tivoli Common Reporting upgrade and DataView upgrade will be successful, but the DataView migration step will fail.
Disabling the cron Jobs
You must disable the cron jobs on each DataChannel host in your environment by editing the crontab file.
About this task
To disable the cron jobs:
Procedure
1. On the DataChannel host, log in as the component user, such as pvuser.
2. Open the crontab file for editing by using the following command:
crontab -e
3. Comment out all jobs that start Tivoli Netcool Performance Manager components and any third-party tasks that work with Tivoli Netcool
Performance Manager tools by inserting a # character at the beginning of the job statement. For example:
Before:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * .
/opt/datachannel/dataChannel.env && /opt/datachannel/bin/cnsw > /dev/null 2>&1 After:
# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * .
/opt/datachannel/dataChannel.env && /opt/datachannel/bin/cnsw > /dev/null 2>&1 4. When you have made your edits, write and quit the file.
Note: While the current cron jobs must be manually commented out, these job statements are automatically updated when you have deployed your upgrade topology. This process is described in “Starting the cron jobs” on page 73.
Shutting down DataChannel
You must shut down the DataChannel components on each DataChannel host running in your environment.
About this task
To shut down DataChannel:
Note: The DataChannel CMGR, CNS, AMGR, and LOG visual processes must remain running until you have gathered the DataChannel parameters from your environment.
Procedure
1. On the DataChannel host, log in as the component user, such as pvuser.
2. Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default) using the following command:
$ cd /opt/datachannel/bin
3. Shut down the DataChannel FTE.
Before shutting down all DataChannel components, some DataChannel work queues must be emptied. To shut down the DataChannel FTE and empty the work queues:
$ ./dccmd stop –pattern FTE.*
4. Let all DataChannel components continue to process until the .../do directories for the FTE and CME components contain no files.
The .../do directories are located in the subdirectories of $DCHOME (typically, /opt/datachannel) that contain the DataChannel components – for example, FTE.1.1, CME.1.1.
5. Do one of the following:
a. If your environment does not run the DataLoad High Availability Manager (HAM), use the following dccmd command to stop the DataChannel
applications:
$ ./dccmd stop all
b. If your environment runs the DataLoad High Availability Manager (HAM), use the following dccmd commands to stop the DataChannel applications:
$ ./dccmd stop DLDR
$ ./dccmd stop LDR
$ ./dccmd stop CME
$ ./dccmd stop FTE
$ ./dccmd stop DISC
$ ./dccmd stop UBA (if required)
Note: For the DataLoad High Availability Manager, the HAM application must remain running until you have gathered the DataChannel parameters from your environment.
Shutting down DataMart
You must shut down DataMart on each DataMart host running in your environment.
About this task
To shut down DataMart:
Procedure
1. On the DataChannel host, log in as the component user, such as pvuser.
2. Set and export the DISPLAY variable.
3. Source the DataMart environment using the following command:
$ . /opt/datamart/dataMart.env
4. Change your working directory to the DataMart bin directory (/opt/datamart/bin by default) using the following command:
$ cd /opt/datamart/bin
5. Use the pismgr command to stop DataMart:
$ ./pismgr stop
6. Start the DataMart Status tool using the following command:
$ pvmstat
7. Remove any DataMart locks by selecting File > Remove locks.
Verifying Netcool/Proviso components are shut down
You must verify that the Netcool/Proviso components have been shut down in your environment.
About this task
To verify that Netcool/Proviso components have been shut down:
Procedure
1. On the Database host, log in as oracle.
2. Log into SqlPlus by entering the following command:
sqlplus “/as sysdba”
3. Submit the following query to the Database:
SELECT username,machine,program FROM v$session
ORDER BY username,machine,program;
On a system where all the clients have been shut down, you would expect to see output like the following:
USERNAME MACHINE PROGRAM PV_ADMIN Oak
sqlplus@oak (TNS V1-V3) .
. . USERNAME MACHINE PROGRAM PV_COLL Willow
pvmd@willow (TNS V1-V3)
The first item is the SQL query itself, while the second item is a DataLoad collector. This is expected if you chose to leave the DataLoad collectors running in order to minimize collections loss.
Installing and starting the Topology Editor
Only one instance of the Topology Editor can exist in the Tivoli Netcool Performance Manager environment. Using the launchpad, install the Topology Editor on the server you have chosen as the primary deployer.
You use the launchpad to install and start the topology editor on the primary deployer.
Note: Best practice on an upgrade scenario is to uninstall the older version of topology editor and install the newer version of topology editor.
Starting the Launchpad
The steps required to start the launchpad.
About this task
To start the launchpad:
Procedure
1. Log in as root.
2. Set and export the DISPLAY variable.
3. Set and export the BROWSER variable to point to your Web browser. For example:
On Solaris systems:
# BROWSER=/opt/mozilla/mozilla
# export BROWSER On AIX systems:
# BROWSER=/usr/mozilla/firefox/firefox
# export BROWSER On Linux systems:
# BROWSER=/usr/bin/firefox
# export BROWSER
Note: The BROWSER command cannot include any spaces around the equal sign.
4. Change directory to the directory where the launchpad resides.
On Solaris systems:
# cd <DIST_DIR>/proviso/SOLARIS On AIX systems:
# cd <DIST_DIR>/proviso/AIX On Linux systems:
# cd <DIST_DIR>/proviso/RHEL
<DIST_DIR>is the directory on the hard drive where you copied the contents of the Tivoli Netcool Performance Manager distribution.
5. Enter the following command to start the launchpad:
# ./launchpad.sh
Installing the Topology Editor
The steps required to install the Topology Editor.
About this task
Only one instance of the Topology Editor can exist in the Tivoli Netcool Performance Manager environment. Install the Topology Editor on the same system that will host database server.
You can install the Topology Editor from the launchpad or from the command line.
To install the Topology Editor:
Procedure
1. You can begin the Topology Editor installation procedure from the command line or from the launchpad. From the launchpad:
a. On the launchpad, click the Install Topology Editor option in the list of tasks.
b. On the Install Topology Editor page, click the Install Topology Editor link.
From the command line:
a. Log in as root.
b. Change directory to the directory that contains the Topology Editor installation script:
On Solaris systems:
# cd <DIST_DIR>/proviso/SOLARIS/Install/SOL10/topologyEditor/Disk1/InstData/VM On AIX systems:
# cd <DIST_DIR>/proviso/AIX/Install/topologyEditor/Disk1/InstData/VM On Linux systems:
# cd <DIST_DIR>/proviso/RHEL/Install/topologyEditor/Disk1/InstData/VM
<DIST_DIR>is the directory on the hard drive where you copied the contents of the Tivoli Netcool Performance Manager distribution.
c. Enter the following command:
# ./installer.bin
The installation wizard opens in a separate window, displaying a welcome page.
2. Click Next.
3. Review and accept the license agreement, then click Next.
4. Confirm the wizard is pointing to the correct directory. The default is
/opt/IBM/proviso. If you have previously installed the Topology Editor on this system, the installer does not prompt you for an installation directory and instead uses the directory where you last installed the application.
5. Click Next to continue.
6. Confirm the wizard is pointing to the correct base installation directory of the Oracle JDBC driver (/opt/oracle/product/11.0.2-client32/jdbc/libversion/
jdbc/lib), or click Choose to navigate to another directory.
7. Click Next to continue.
8. Review the installation information, then click Run.
9. When the installation is complete, click Done to close the wizard.
The installation wizard installs the Topology Editor and an instance of the deployer in the following directories:
Interface Directory
Topology Editor install_dir/topologyEditor
For example:
/opt/IBM/proviso/topologyEditor
Deployer install_dir/deployer
For example:
/opt/IBM/proviso/deployer
Results
The combination of the Topology Editor and the deployer is referred to as the primary deployer.
For more information, see the "Resuming a partially successful first-time installation" section of the Tivoli Netcool Performance Manager wireless Installation Guide.
Note: To uninstall the Topology Editor, follow the instructions in the "Uninstalling the Topology Editor" section of the Tivoli Netcool Performance Manager wireless Installation Guide. Do not delete the /opt/IBM directory. Doing so will cause problems when you try to reinstall the Topology Editor.
If the /opt/IBM directory is accidentally deleted, perform the following steps:
1. Change to the /var directory.
2. Rename the hidden file .com.zerog.registry.xml (for example, rename it to .com.zerog.registry.xml.backup).
3. Reinstall the Topology Editor.
4. Rename the backup file to the original name (.com.zerog.registry.xml).
Starting the Topology Editor
After you have installed the Topology Editor, you can invoke it from either the launchpad or from the command line.
Procedure
v To start the Topology Editor from the launchpad:
1. If the Install Topology Editor page is not already open, click the Install Topology Editor option in the list of tasks to open it.
2. On the Install Topology Editor page, click the Start Topology Editor link.
v To start the Topology Editor from the command line:
1. Log in as root.
2. Change directory to the directory in which you installed the Topology Editor.
For example:
# cd /opt/IBM/proviso/topologyEditor 3. Enter the following command:
# ./topologyEditor
Note: If your DISPLAY environment variable is not set, the Topology Editor will fail with a Java assertion message (core dump).
If you are running the Topology Editor for an AIX 6.1 or AIX 7.1 environment, use the command:
# ./topologyEditor -vm /opt/IBM/proviso/topologyEditor/jre/bin/java
Loading the upgrade topology into the Topology Editor
To load the upgrade topology.
Procedure
1. In the Topology Editor, select Topology > Open existing topology. The Open Topology windowis displayed.
2. For the topology source, select where it is being loaded from:
v local
If you select local, you will be required to click the Browse button and navigate to the desired topology file.
v From database
If you select From database, you will be required to verify that all of the fields for the database connection are filled in with the correct values:
– Database hostname — The name of the database host. The default value is localhost.
– Port — The port number used for communication with the database. The default value is 1521.
– Database user — The user name used to access the database. The default value is PV_INSTALL.
– Database Password — The password for the database user account. For example, PV.
– SID — The SID for the database. The default value is PV.
If desired, click Save as defaults to save these values for future incremental installations.
Note: If at any time you click cancel, memory is cleared and the topology is unchanged.
3. Click Next to change the topology.
4. Click Finish.
The upgrade topology is displayed in the Topology Editor.
5. Save the topology and close the topology.
6. Reopen the saved topology to edit it.
7. In the Topology Editor, make sure the MIGRATE_FROM_HOST property specifies the source DataView host, that is, the host containing the 1.3.1 DataView instance.
Note: For some environments, loading the upgrade topology into the Topology Editor can take several minutes.
8. Update the following properties:
v TIP_ADMIN_USER= tipadmin v Port= 16710
v TIP_ADMIN_PASSWORD= tipadmin
Preparing the upgrade topology for deployment
When the upgrade topology is initially loaded into the Topology Editor, it will contain several error and warning messages.
Errors are expected. This section describes how to resolve these issues and prepare the upgrade topology for deployment.
Perform the following tasks:
v Upgrade of existing Tivoli Integrated Portal.
v Determine which generated host definitions are valid, and decide which host definitions are extraneous and can be removed.
v Move Tivoli Netcool Performance Manager components from the extraneous hosts to the valid host definitions so that the upgrade topology matches what exists in your current Tivoli Netcool Performance Manager environment.
v Delete the extraneous host definitions.
v Review the host and Tivoli Netcool Performance Manager component properties so that they match the values that exist in your current Tivoli Netcool
Performance Manager environment.
v Verify that the upgrade topology matches your current Tivoli Netcool
Performance Manager install base before deploying the upgrade topology file.
Note: If you plan to make changes to your Tivoli Netcool Performance Manager environment, such as adding or removing hosts, components, or deploying an advanced configuration, you must upgrade your existing environment first.
Technology packs
In general, you do not need to perform any special actions for technology packs when upgrading your Tivoli Netcool Performance Manager environment. The installed packs will function at the new level of Tivoli Netcool Performance Manager without requiring any technology pack upgrade.
If you want to upgrade a technology pack after your Tivoli Netcool Performance Manager environment has been upgraded, or your environment has the
Alcatel-Lucent 5620 SAM or Cisco Netflow Technology Packs installed, see IBM Tivoli Netcool Performance Manager: Technology Pack Upgrade Guide for more information.
Note: If your pre-upgrade environment contains technology packs that include XSD files, DO NOT import the XSD files into the Topology Editor until AFTER you have finished upgrading your Tivoli Netcool Performance Manager environment.
Determining valid host definitions
In the Physical View, there can be several host definitions that appear for the same physical host, some of which may not be valid.
About this task
Extraneous host definitions can be generated when the upgrade topology is first created. You must determine which host definitions are valid and which host definitions are extraneous and can be renamed or later removed.
To determine which hosts are valid:
Procedure
1. In the Topology Editor, examine each host definition that appears in the Physical View. You must either rename delete any host definitions with the following characteristics (only delete a host after its Tivoli Netcool Performance Manager components have been removed):
v Host name is blank. For example:
Host <blank>
v Host name is fully qualified:
Host DOCSVR3.BBB.AAA.COM
Note: Fully-qualified host names are not supported by Tivoli Netcool Performance Manager .
2. If you determine that a host definition is valid and want to rename it, see
“Renaming host definitions” on page 91.
3. If you determine that a host definition is extraneous and want to later delete it, you must move the Tivoli Netcool Performance Manager components from the extraneous host to a valid host definition. For more information, see “Moving Tivoli Netcool Performance Manager components between host definitions.”
Moving Tivoli Netcool Performance Manager components between host definitions
Once you have determined which host definitions are valid in the Logical View, you must move Tivoli Netcool Performance Manager components from the extraneous hosts to the valid host definitions.
About this task
To move Tivoli Netcool Performance Manager components between hosts:
Procedure
1. In the Topology Editor, right-click on the Tivoli Netcool Performance Manager component in the Logical View that you want to move, then select the Change hostor Move menu option.
Note: The menu selection is “Change Host” or “Move” depending upon the component that is selected.
2. In the Available hosts field, select the name of the host where you intend the Tivoli Netcool Performance Manager component to reside from the scroll-down list.
3. Click Finish.
4. Repeat steps 1 - 3 until all Tivoli Netcool Performance Manager components have been moved from the extraneous host definitions to their intended target host definitions.
Deleting extraneous host definitions
When you have removed all of the Tivoli Netcool Performance Manager
components from an extraneous host definition, you can delete the host definition from the Physical View.
About this task
To delete host definitions:
Procedure
1. In the Topology Editor, right-click on the name of the host definition in the Physical View, then select the Remove menu option.
2. Repeat step 1 until all of the extraneous hosts have been removed from the Physical View.
Renaming host definitions
Renaming host definitions.
About this task
To rename a host definition:
Procedure
1. In the Topology Editor, right-click on the name of the host definition in the Physical View, then select the Rename menu option.
2. In the Host Name field, specify the new name of the host definition. This name must match the name of the physical host in your environment.
Note: Fully-qualified host names are not supported by Tivoli Netcool Performance Manager.
3. Click Finish.
Verifying host properties
You must verify the properties defined for each host in the Physical View so that they match the values that exist in your current Tivoli Netcool Performance
You must verify the properties defined for each host in the Physical View so that they match the values that exist in your current Tivoli Netcool Performance