network management for netcool operations insight 1.4 … · network management for netcool...

1

Network Management for Netcool Operations Insight 1.4

Best Practices for deployment

Author: Rob Clark

January 2017

Contents Overview ....................................................................................................................................................... 3

Preparation ................................................................................................................................................... 3

Servers ...................................................................................................................................................... 3

DNS ........................................................................................................................................................ 3

Prerequisite Scanner Tool ..................................................................................................................... 4

Ulimit for open files .............................................................................................................................. 4

Special note if you are using root to install Network Manager core. ................................................... 4

Install media .............................................................................................................................................. 4

Repositories .......................................................................................................................................... 5

Installation paths ...................................................................................................................................... 6

Install Installation Manager on each server .............................................................................................. 7

Register the repositories in IM on each server ......................................................................................... 8

Important things to remember using Installation Manager ................................................................... 10

IBMIMShared directory ....................................................................................................................... 10

Rename install package default directories ........................................................................................ 11

Install the products on all servers ............................................................................................................... 12

Database ................................................................................................................................................. 12

Scenario A - Network Manager core + OMNIbus core............................................................................ 13

2

Scenario B - OMNIbus core server (separate server from Network Manager) ...................................... 13

Scenario B - Network Manager core (separate server from OMNIbus) ................................................. 14

GUI server ............................................................................................................................................... 14

WebGUI Data Source .......................................................................................................................... 14

Configuration panel for Network Manager GUI ................................................................................. 15

Post-install................................................................................................................................................... 15

Start/stop ................................................................................................................................................ 16

GUI ...................................................................................................................................................... 16

OMNIbus ............................................................................................................................................. 16

Network Manager ............................................................................................................................... 16

Reporting - TCR/Cognos ............................................................................................................................. 16

Preparation ............................................................................................................................................. 17

System ................................................................................................................................................. 17

Prerequisite Scanner ........................................................................................................................... 17

TCRCognos package ............................................................................................................................ 17

Remote Database ................................................................................................................................ 17

Install Reporting Services and Network Manager Reports ..................................................................... 17

Post-install............................................................................................................................................... 18

Workaround for error ......................................................................................................................... 18

Configure user/groups to use reports ................................................................................................ 18

References: ................................................................................................................................................. 19

3

Overview The NOI solution consists of several products and components which can be installed on a number of

different servers in many different combinations. There are also many choices to make along the way,

some critical, others to personal taste. The purpose of this document is to accelerate the initial

deployment of the Network Management for NOI by making best practice choices. This includes how to

get organized for a smooth deployment, and will conclude with everything running. After this, and

outside of the scope of this document, you can complete the customer specific deployment by installing

the other products that are needed, and implement any customizations required.

This guide covers the deployment of the

Database (DB2)

Event Management (Netcool/OMNIbus)

Network Manager

GUI (DASH, et al)

TCR/Cognos

Preparation No one likes to prepare - most of us like to dive in and only read something once we run into problems.

This document was written for those installing for the first time and are looking to get it all done today.

Most of it is in the preparation, the rest is easy.

Servers

Decide where you are going to install each product. For example, here are two common arrangements

that we will cover in this guide. These two scenarios also illustrate the subtle difference with OMNIbus

core and ITNM core collocated and when they are on separate servers.

A. Two server scenario

Server 1: DB2, GUI

Server 2: OMNIbus, ITNM

B. Four server scenario

Server 1: DB2

Server 2: GUI

Server 3: OMNIbus

Server 4: ITNM

DNS It is important that each server has consistent DNS resolution for the FQDNs and shortnames of the

other servers it will be communicating with, including the localhost 127.0.0.1 address. However, when

asked for the server address of the local machine, it is a good idea to always use the FQDN or shortname

rather than “localhost”. Make sure you can ping whatever name you use (FQDN or shortname).

4

Prerequisite Scanner Tool Begin with the standard preparation of each server with the operating system and the OS prerequisites

needed, making use of the Prerequisite Scanner Tool.

Use these two Technotes to get the latest Prerequisite Scanner Tool files for ITNM and OMNIbus and

how to run it:

ITNM 4.2: http://www.ibm.com/support/docview.wss?uid=swg21970155

OMNIbus 8.1: http://www.ibm.com/support/docview.wss?uid=swg21472859

Ulimit for open files Particularly note the ulimit –n setting for the GUI server. Installation Manager itself also may need this

limit increased for the account you are using.

On Linux, you set it in /etc/security/limits.conf. Ensure the soft and hard limit is at least 8192 for the

user account that will be used to install and run the components. It is not enough to set it in the

command prompt window.

Special note if you are using root to install Network Manager core. The Storm component must be run using a non-root account. This is not an issue if you use a non-root

account for installing, since it will simply use that account automatically.

The root-install obliges you to create a separate non-root account for the Storm component (which

aggregates the stored polled data). By default, the installer will make some changes so that the Storm

processes will run with the non-root account. The installer will add root’s primary group at install time

to the non-root account by default. Do not change the default group name in the prompt without

understanding the consequences.

Note: If this does not sound acceptable, consider installing the whole solution using a single non-root

account – more secure and less hassle. Failing that you can use another group, but you will need to

change the group on many files and you still have to maintain passwords on two accounts. See the

documentation if you really need to do this.

Install media

There are many options for preparing the install media for installation. If you are in the business of

deployment, then take a look at the Package Utility to help organize the repositories.

Use these links to see the full list of part numbers depending on your license.

NOI 1.4: http://www-01.ibm.com/support/docview.wss?uid=swg24041694

NNM 9.3: http://www.ibm.com/support/docview.wss?uid=swg24041861

(The table below has the part numbers for the Linux install kits)

http://www.ibm.com/support/docview.wss?uid=swg21970155


http://www-01.ibm.com/support/docview.wss?uid=swg24041694


5

However, to use a simple approach to get going now, we need to understand some basic concepts.

Repositories The Installer uses install media which are located in repositories. A repository can be,

a) Set of files in a directory unpacked from a tar file

b) Set of files on a DVD

c) Set of files accessed via http from a remote server. For example, IBM’s Passport Advantage

(PPA).

d) Any of the above containing a combination of repositories merged into one (see the

Package Utility).

Each repository contains a special meta-data file that the IM installer uses and this is used to identity the

directory as a repository. This is named repository.config or disktag.inf.

You configure the IM installer by registering a list of repositories and it will then present you with a list

of all the components available for install. Very nice.

Best Practice: these repositories are very large, so installing directly from Passport Advantage, while

possible if you have an internet connection, will be slow. Better to download the tar files to a local

device, unpack them into their own subdirectories, and make these directories available via NFS to all

the servers.

The repositories made available by IBM will no doubt change over time in name and content. So the

important things to identify are the individual install packages you wish to install on each server.

Each Installation Manager, when it starts up, reads the repositories you configure it with. It then

presents all the Install Package names it finds in those repositories for you to select from for the server

you are working with.

Server Repository – (Linux part

number)

Install Packages

OMNIbus core

(8.1.0.10)

OMNIbus-v8.1.0.5-Core.linux64.zip

(CN8HFML)

Plus Fix Pack 10:

8.1.0-TIV-NCOMNIbus-Linux-FP0010

IBM Tivoli Netcool/OMNIbus

OMNIbus core NCOMNI_PROBE_FOR_SNMP.zip

(CN4FZEN)

Netcool/OMNIbus Probe nco-p-mttrapd

OMNIbus core NcKL_4.5.0.zip (CN8B6EN) Netcool/OMNIbus Knowledge Library

ITNM core

(4.2.0.2)

ITNP_IP_LIN.zip (CN931EN)

Plus Fix Pack 2:

Network Manager Core Components

6

4.2.0-TIV-ITNMIP-Linux-FP0002.zip Network Manager topology database

creation scripts

GUI

(WAS 8.5.5.9)

(JazzSM 1.1.3)

(DASH 3.1.3.0)

WAS_V8.5.5.9_FOR_JSM_FOR_LINUX_

ML.zip (CNC1ZML)

JAZZ_FOR_SM_1.1.3.0_FOR_LNX.zip

(CNC1PML)

IBM WebSphere Application Server

IBM WebSphere SDK Java Technology

Edition (mandatory, not optional as listed)

Jazz for Service Management extension for

IBM WebSphere

IBM Dashboard Application Services Hub

Security Services

Reporting Services

GUI

(TCR 3.1.3.0)

ITCR_3.1.3.0_FOR_LINUX.tar.gz

(CNC1TML)

Unpacks into a subdirectory called

TCRCognos. Let’s put in under /opt/IBM/

since it is not controlled by the netcool IM.

GUI

(WebGUI

8.1.0.8)

OMNIbus-v8.1.0.4-

WebGUI.Linux64.zip (CN8HGML)

Plus Fix Pack 8:

OMNIbus-v8.1.0-WebGUI-FP8-IM-

linux64-UpdatePack.zip

IBM Tivoli Netcool/OMNIbus Web GUI

Netcool Operations Insight Extensions for


GUI

(ITNM 4.2.0.2)

ITNP_IP_LIN.zip (as above CN931EN)

Plus Fix Pack 2

4.2.0-TIV-ITNMPIP-Linux-FP0002.zip

Network Manager GUI Components

Network Manager Reports

GUI

(ITNM 4.2.0.2)

NTWRK_HLTH_DSHBRD_V4.2_LNX.zip

(CN92JEN)

Plus Fix Pack 2:

4.2.0-TIV-NOIHD-Linux-FP0002.zip

(NOI only) Network Health Dashboard and

Event Analytics Integration

Database DB2_Svr_10.5.0.3_Linux_x86-64.tar.gz

(CIXV0ML)

DB2 v10.5 Enterprise Server Edition

Installation paths

Each install package will be installed in a default directory. This will not be what you want and it will

scatter the deployment and may even cause problems if the IM directories are nested.

7

Best Practice: We will use the root directory, /opt/IBM/netcool/, for all products on each server

for consistency. Easy to find the product directories later, but it has another useful benefit. It groups all

the NOI products with the IM used to install them. This makes it easy to clean with rm –rf if you want

to start again cleanly. Using rm –rf is easy and convenient if you need to remove all the products on a

server and start over. Otherwise, use IM to uninstall individual product components.

IMPORTANT! You will not be prompted, in GUI or console install mode, to change the default path

names. You must be vigilant to find the panel where you can change them, and then scroll down the list

to find and change all of the paths accordingly. If you forget, you can go back until you find it, unless it

has begun to install. In which case go back to the “rm –rf” above and start again – it will be easier!

Package Default - vary Best Practice

Installation

Manager

/root/IBM/InstallationMana

ger/eclipse

/opt/IBM/netcool/IM/Installa

tionManager/eclipse

IM Data /root/IBM/IBMIMData /opt/IBM/netcool/IM/IBMIMDat

a

IM Shared data /root/IBM/IBMIMShared /opt/IBM/netcool/IM/IBMIMSha

red

OMNIbus/ITNM /opt/IBM/tivoli/netcool /opt/IBM/netcool/core

OMNIbus Web

GUI

/opt/IBM/netcool_1 /opt/IBM/netcool/gui

ITNM GUI /opt/IBM/netcool/gui /opt/IBM/netcool/gui

WAS /root/IBM/WebSphere/AppSer

ver

/opt/IBM/netcool/WebSphere

JAZZSM /root/IBM/JazzSM /opt/IBM/netcool/JazzSM

NcKL /root/IBM/tivoli/NcKL /opt/IBM/netcool/NcKL

SNMP Probe /opt/IBM/tivoli/netcool /opt/IBM/netcool/core

TCR Cognos /opt/IBM/TCRCognos

Note: a non-root install will use the home directory instead of “/root” for the default path

Install Installation Manager on each server

Find and install the Installation Manager.

Find the install media (the repository) for the Installation Manager v1.8.4 in the top level directory of

the ITNM unzipped install media (ITNP_IP_LIN.zip). Confirm that by locating the files groupinst and

repository.config. Alternatively you can get it from Fix Central



8

Install the Installation Manager using the groupinst command. There are other options here and you

can research them later. Other options for the curious:

https://www.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/

omnibus/wip/install/reference/omn_ins_im_install_overview.html

Run this command to install the IM in one step, using the console mode and setting up the best practice

directories:

./groupinstc -dL /opt/IBM/netcool/IM/IBMIMData -acceptLicense -

installationDirectory

/opt/IBM/netcool/IM/InstallationManager/eclipse

Register the repositories in IM on each server

Assuming you have NFS-mounted the central repository directory on each server, then launch IM and

register the repositories.

Include the repositories for any Fix Pack updates that apply when installing the full product - they will be

automatically applied so that you do not have to follow the initial installation with a separate update.

Or if you choose, use IM to apply the Fix Pack afterwards using the Update button instead of the Install

button.

Note: IM supports several installation modes – GUI, Console, Silent, and HTTP. However, not all

products support all modes. So we will assume you have X/vnc setup, or equivalent, and will use the

GUI mode. A later section covers the console mode option and how you can install WAS/JAZZSM/DASH

using Silent mode, since they do not support console mode at time of writing.

1. Start the IM GUI by running:

/opt/IBM/netcool/IM/InstallationManager/eclipse/IBMIM

2. Select File->Preferences…->Repositories

https://www.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/install/reference/omn_ins_im_install_overview.html

https://www.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/install/reference/omn_ins_im_install_overview.html

9

3. Add Repository…

10

If the repositories are on the disk or DVD, then Browse to find the repository.config or

diskTag.inf file inside the repository you want to add.

Note: if the top level directory contains both repository.config and groupinst then that is

the IM install media – look for a subdirectory that contains the actual repository.

If the repository is available via HTTP, then type the URL.

For Passport Advantage, select File->Preferences->Passport Advantage. You will need your IBM ID and

password.

Press OK to verify access to the repository. There is also a Test Connections button you can use to check

all added repositories later.

Important things to remember using Installation Manager

IBMIMShared directory

The first installation with IM that you do on a server will set the path for the IBMIMShared directory.

This is an important IM related directory that should be a peer to the other IM directories. You will be

given the opportunity to change it on the first install. It can not be changed after that. Using our best

practice install root, make sure you set it to,

/opt/IBM/netcool/IM/IBMIMShared

11

Rename install package default directories You will not be prompted to change the default directories, but you will have the opportunity on the

following panel. It is easy to forget, and even easier to miss any directories below the scroll line.

12

You are now ready to begin installing the products.

Install the products on all servers With the preparation done, you can now install each server in turn. The order is important as some

components will not let you proceed without access to its dependencies.

Database

Install DB2 10.5 using its db2setup command. The installer will create an instance with the default

name, db2inst1, and the user account db2inst1 that will own that instance.

After installing the DB2 server, you must create a database in the instance you created during the install.

Locate the file db2_creation_scripts.tar.gz in the Network Manager repository you

downloaded.

Unpack it, and copy the file create_db2_database.sh to the DB2 server.

13

Run this file using the instance owner (db2inst1) to create the NCIM database:

./create_db2_database.sh NCIM <user> <password>

For full details, see Setting up a topology database,

www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_usedb2oror

acleforncim.html

Scenario A - Network Manager core + OMNIbus core

Install Network Manager core components, using either IM GUI mode or Console mode, by selecting

the Network Manager and OMNIbus packages,




Netcool/OMNIbus Knowledge Library

Make sure you change the install directories to:

/opt/IBM/netcool/core

/opt/IBM/netcool/NcKL

In this co-located scenario, the installer will create the ObjectServer for OMNIbus in order to configure it

for Network Manager, and set up nco_pa for OMNIbus process control.

Both Network Manager and OMNIbus core will be installed under /opt/IBM/netcool/core.

Scenario B - OMNIbus core server (separate server from Network Manager)

Install OMNIbus core components, using either IM GUI mode or Console mode, by selecting the

packages,



Netcool/OMNIbus Knowledge Library


/opt/IBM/netcool/core

/opt/IBM/netcool/NcKL

After OMNIbus is installed, create the ObjectServer NCO_AGG_P. You can do this easily by running the

script,

/opt/IBM/netcool/core/omnibus/bin/nco_icw –gui|-console

14

You can take the defaults to create an aggregation ObjectServer if there is no need to create a multi-

tiered architecture for the ObjectServers, or collection or presentation objectservers.

Scenario B - Network Manager core (separate server from OMNIbus)

Make sure that the OMNIbus ObjectServer is running before you install Network Manager.

Install Network Manager core component, using either IM GUI mode or Console mode, by selecting the

Network Manager package,


GUI server

The WAS, JazzSM, and DASH components can only be installed using IM GUI mode or Silent mode with a

response file.

Select the following packages to install the GUI,

IBM WebSphere Application Server

IBM WebSphere SDK Java Technology Edition

Jazz for Service Management extension for IBM WebSphere

IBM Dashboard Application Services Hub


Network Manager GUI Components

Network Health Dashboard and Event Analytics Integration


/opt/IBM/netcool/WebSphere

/opt/IBM/netcool/JazzSM

/opt/IBM/netcool/gui

WebGUI Data Source It is important to understand a bit about the WebGUI Data Source since this is used by Network

Manager. If this is not set correctly, the status colors in Network Views will be missing along with the

events in the event viewer on the Network Health Dashboard and the Network Health pages.

You can configure one or more data sources for the WebGUI. Each one is matched to one or more

ObjectServer ports. Network Manager GUI must be configured with a data source. This is set on the

Network Manager core server in the file, /opt/IBM/netcool/core/etc/precision/ModelNcimDb.<domain>.cfg

By default it is set to the ObjectServer name created by the NM core installation, NCO_AGG_P.

If WebGUI has been already been configured with a data source, or you wish to use a different one, then

you must edit ModelNcimDb.<domain>.cfg afterwards.

15

Configuration panel for Network Manager GUI This panel asks you for the ObjectServer connection parameters for the GUI. It will use this information

to configure WebGUI with the Network Manager settings for right click menus, filters, and views.

The check box is important – always check it unless the WebGUI SME has already set a data source. By

default it will be checked for you if WebGUI has not yet been configured with a data source.

If set, it will create a data source, using the name of the ObjectServer, in WebGUI. Be aware that this

will replace any others already configured – much to the dismay of the WebGUI SME.

If not set, it will not change WebGUI’s data source, but you will need to find this name and edit the file

on the core server, ModelNcimDb.<domain>.cfg. The WebGUI data source can be found in, /opt/IBM/netcool/gui/omnibus_webgui/etc/datasources/ncwDataSourceDefinitions.xml

Post-install Once you have completed the installations above, each component is ready to start, if not already

running.

16

[…add link to post install section in docs… remind key ones]

Start/stop

GUI /opt/IBM/netcool/JazzSM/profile/bin/startServer server1

/opt/IBM/netcool/JazzSM/profile/bin/stopServer –username smadmin –

password <pw> server1

OMNIbus Assuming NCO_PA is set up,

/opt/IBM/netcool/core/omnibus/bin/nco_pad –name NCO_PA –authenticate

PAM

/opt/IBM/netcool/core/omnibus/bin/nco_pa_shutdown -server nco_pa -user

root -password <pw> -option STOP

Network Manager Source the environment as usual, and then use the start/stop/status tools. Note that these tools only

control the Network Manager core processes: ncp processes and Storm.

Source the environment for Network Manager core,

. /opt/IBM/netcool/core/env.sh

itnm_start [ncp|storm]

itnm_status [ncp|storm]

itnm_stop [ncp|storm]

This is a good time to take a snapshot if working with VM servers.

Reporting - TCR/Cognos A quick overview first.

The Cognos code is in a separate package that you simply unpack, there is no installer required.

You will need either a local DB2 server or a remote one. If the DB2 server is remote, you must

set up and configure the database before installing TCR.

Use IM to install JazzSM’s Reporting Services and Network Manager Reports

Post-install, use the GUI Cognos administration to:

o grant authority to the DASH users who need report access

o set the datasource isolation level to “uncommitted”

17

Preparation

System Ensure there is 17GB of diskspace available for the install of TCR.

Set the following system settings if the current settings are lower. On Linux, edit the file,

/etc/security/limits.conf, and set both hard and soft entries for the account used to install and run the

GUI.

Open file limit 32768 (nofile)

Max number of processes 256000 (nproc)

Stack size 2048 (stack)

Prerequisite Scanner

Run the Prereq Scanner convenience script TCR.sh that comes with the Prerequisite Scanner.

http://www.ibm.com/support/knowledgecenter/SS2RKB_1.2.0.17/com.ibm.ips.doc/ips_install_prs.html

TCRCognos package

Unpack the package ITCR_3.1.2.1_FOR_LINUX.tar.gz into /opt/IBM. It will create the

subdirectory TCRCognos and put all the files underneath.

Remote Database Typically you would use the existing DB2 server for the TCR Content Store database. If a DB2 database is

on the same server where you are installing TCR, then there is nothing more to do. The installer will

create and setup the database.

If the DB2 database is on a remote server, then you must run a couple of scripts to create and set up

the Content Store database. Then during the Reporting Services install, simply select the option for

“Existing database”.

The two scripts are located in /opt/IBM/TCRCognos/ContentStoreDatabase. Copy them to the remote

DB2 server and follow these steps:

a) Run the script to generate the tcr_create_db2_cs.sql, using the default database name, tcrdb, and

the database instance owner: ./TCR_generate_content_store_db2_definition.sh tcrdb, db2inst1

b) Apply the generated SQL script, by running the command, db2 -vtf ./tcr_create_db2_cs.sql

Install Reporting Services and Network Manager Reports

Run the Installation Manager and select the Reporting Services from the JazzSM repository, and the

Network Manager Reports from the ITNM repository.

It will ask if you want to create a database or use an existing one. Only select ‘create’ if DB2 is local,

otherwise select the existing tcrdb database you just created on the remote database server

Enter the credentials when prompted for,

http://www.ibm.com/support/knowledgecenter/SS2RKB_1.2.0.17/com.ibm.ips.doc/ips_install_prs.html

18

WAS smadmin account password

itnmadmin account password

NCIM database credentials

Post-install

Before running the reports there are two actions that may be necessary for the smadmin account to

successfully launch the Cognos GUI Administration application.

Workaround for error On launching the Administration application (Step 3 below) you might get this error:

PF-VAL-6171 Error retrieving metadata for the target fragment.

To circumvent the problem, rename or remove the following jar file:

/opt/IBM/netcool/JazzSM/reporting/lib/birt-runtime-

2_2_2/ReportEngine/lib/BirtAdapterB.jar

Restart DASH:

/opt/IBM/netcool/JazzSM/profile/bin/stopServer.sh server1 -username smadmin

/opt/IBM/netcool/JazzSM/profile/bin/startServer.sh server1


Configure user/groups to use reports You must also configure Cognos for the users/groups you wish to see the reports.

For best results, use Firefox web browser and follow these steps.

1. Log into JazzSM portal (ex: smadmin user)

2. Click on Reporting->Common Reporting

3. Click on Launch->Administration

4. Click on Security tab

5. Click on Cognos directory

6. Select Authors and then go to set properties

7. Click on Members tab

8. Click on Add link

9. Click on VMMProvider

10. Click on Search link

11. Search for new users/groups and add them into Selected entries

12. Again click on Directory

13. Click on Cognos

14. Select "All authenticated users" group and add into Selected entries

15. Click Ok


19

16. Log out from JazzSM portal and re-login with new user

17. Open Reporting->Common Reporting

( http://www.ibm.com/support/docview.wss?uid=swg21963430 )

References: http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_insta

llingreports.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/tcr_c_install_

prereqs.html


http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installingreports.html

http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installingreports.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/tcr_c_install_prereqs.html

http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/install/tcr_c_install_prereqs.html

network management for netcool operations insight 1.4 … · network management for netcool...

Documents