+ All Categories
Home > Documents > IBMTivoli Netcool Performance Manager 1.4 Wireline ... Install the 1.4.0.0-TIV-TNPM-IF0009 fix pack...

IBMTivoli Netcool Performance Manager 1.4 Wireline ... Install the 1.4.0.0-TIV-TNPM-IF0009 fix pack...

Date post: 12-May-2018
Category:
Upload: vantuyen
View: 214 times
Download: 1 times
Share this document with a friend
64
IBM Tivoli Netcool Performance Manager 1.4 Wireline Component Document Revision R2E3 Configuration Recommendations Guide
Transcript

IBM Tivoli Netcool Performance Manager 1.4Wireline ComponentDocument Revision R2E3

Configuration Recommendations Guide

���

NoteBefore using this information and the product it supports, read the information in “Notices” on page 55.

© Copyright IBM Corporation 2006, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Overview . . . . . . . . . 1

Chapter 2. Requirements . . . . . . . 3Plan your installation . . . . . . . . . . . 3Minimum requirements for installation . . . . . 5

Solaris hardware requirements . . . . . . . 5AIX hardware requirements . . . . . . . . 5Linux hardware requirements. . . . . . . . 5Oracle and DB2 deployment space requirements . 6Screen resolution . . . . . . . . . . . 10

Minimum requirements for a proof of conceptinstallation . . . . . . . . . . . . . . 10

Solaris hardware requirements (POC) . . . . . 11AIX hardware requirements (POC) . . . . . 11Linux hardware requirements (POC) . . . . . 11Screen resolution . . . . . . . . . . . 12

Supported operating systems and modules . . . . 12Solaris 10 for SPARC platforms . . . . . . . 12AIX platforms . . . . . . . . . . . . 15Linux platforms . . . . . . . . . . . . 20

Required user names . . . . . . . . . . . 26pvuser . . . . . . . . . . . . . . . 26oracle . . . . . . . . . . . . . . . 26db2 . . . . . . . . . . . . . . . . 27

Ancillary software requirements . . . . . . . 27FTP support . . . . . . . . . . . . . 27Open SSH and SFTP . . . . . . . . . . 27File compression. . . . . . . . . . . . 28

DataView load balancing . . . . . . . . . 29Databases . . . . . . . . . . . . . . 29Jazz for Service Management . . . . . . . 30Java Runtime Environment (JRE) . . . . . . 31Web browsers and settings for DataView reports 31X Emulation . . . . . . . . . . . . . 32Tivoli Netcool/OMNIbus Web GUI integration 32Microsoft Office Version . . . . . . . . . 33

Chapter 3. Architecture information . . 35ServerTime synchronization . . . . . . . . . 35Multiple SNMP DataLoad collectors . . . . . . 35DataChannel subchannels . . . . . . . . . 36DataChannel remote . . . . . . . . . . . 36

DataChannel "Standard" . . . . . . . . . 36Tivoli Netcool Performance Manager on Solaris10 . . . . . . . . . . . . . . . . 38Tivoli Netcool Performance Manager inventorydeployment . . . . . . . . . . . . . 39

Firewall configuration . . . . . . . . . . . 43DataChannel standard . . . . . . . . . . 44DataChannel "Remote Channel Option" . . . . 50SNMP inventory. . . . . . . . . . . . 51

Appendix. SNMP version support . . . 53

Notices . . . . . . . . . . . . . . 55

© Copyright IBM Corp. 2006, 2014 iii

iv IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Chapter 1. Overview

The Configuration Recommendations Guide describes all requirements of the IBMTivoli Netcool Performance Manager, Version 1.4 system.

IBM Tivoli Netcool Performance Manager, Version 1.4 consists of two maincomponents: a wireline component (formerly Tivoli® Netcool/Proviso) and awireless component (formerly Tivoli Netcool Performance Manager for Wireless).

This document lists the recommended configurations and the supported platformsand components for IBM Tivoli Netcool Performance Manager, Version 1.4.

© Copyright IBM Corp. 2006, 2014 1

2 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Chapter 2. Requirements

Details of all Tivoli Netcool Performance Manager requirements.

A complete set of requirements for Tivoli Netcool Performance Manager 1.4.

Plan your installationYou can choose to install a full installation of Tivoli Netcool Performance Manager1.4 in a stand-alone environment or in a distributed environment.

Pre-requisite software

Table 1. Pre-requisite software

Product Version

Operating system 64-bit only v Red Hat Enterprise Linux (RHEL) 6.x if you are doinga fresh install

Important: Install the 1.4.0.0-TIV-TNPM-IF0009 fixpack to resolve the library dependencies for RHELversions greater than 6.2.

v Red Hat Enterprise Linux (RHEL) 5.9 (Tikanga) forTivoli Netcool Performance Manager upgrade

v IBM AIX 6.1 or later

v Oracle Solaris 10 update 6

Note: For the required packages, see“Supported operating systems and modules” on page12.

© Copyright IBM Corp. 2006, 2014 3

Table 1. Pre-requisite software (continued)

Product Version

Databases:

v Oracle 11g support

v Support for 64-bit Oracle 11g (11.2.0.3)

v Enterprise Edition on Solaris (SPARC), Linux and AIX

v Oracle 11g Enterprise Edition must include thepartitioning option.

:

v IBM DB2 Enterprise Server Edition 10.1.0.1, Linux64-bit only

v IBM Data Server Client 10.1.0.1 64-bit only

Note: You must install the IBM Data Server Client(64-bit) in a distributed environment only. It is notrequired in a standalone environment. In a distributedenvironment, install the DB2 client software on eachserver where you plan to install a Tivoli NetcoolPerformance Manager component, with the exception ofwhere you installed the DB2 server.Note: Install DB2 Version 10.1 Fix Pack 3 to resolvesome issues that you may encounter in relation toadministering and performance of DB2. For moreinformation, see Release Summary. Ensure that youupgrade to DB2 10.1 Fix pack 3 only after completingthe installation of Tivoli Netcool Performance Manager.

Java v Java Runtime Environment (JRE) 1.6 or 1.7, 32-bit forall browsers

v IBM-JRE 1.6 SR14, 32-bit is required for DataView thatruns on Dashboard Application Services Hub

Note: IBM-JRE 1.6 SR14 32-bit is bundled with theTopology Editor.

Tivoli Common Reporting Tivoli Common Reporting 3.1.0.2Note: IBM Tivoli Common Reporting 3.1.0.1 base andthen apply the IBM Tivoli Common Reporting 3.1.0.2update available from Fix Central only. For moreinformation, seehttp://www-01.ibm.com/support/docview.wss?uid=swg24036990

Jazz for Service Management Jazz for Service Management 1.1.0.3Note: See Jazz for Service Management 1.1.0.3 at IBMKnowledge Center.

Web browsers v Internet Explorer 8.0 and 9.0

v Mozilla Firefox ESR 17 and 24

Note: Enable JavaScript and cookies

Note: Jazz for Service Management includes installation media for Jazz for ServiceManagement, IBM DB2, IBM WebSphere Application Server, and the Quick StartGuide. Jazz for Service Management has a number of integration services:Administration, Registry, IBM Tivoli Common Reporting, Security, and IBMDashboard Application Services Hub.

4 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Minimum requirements for installationThe minimum required host specifications for a Tivoli Netcool PerformanceManager deployment.

Solaris hardware requirements

Tivoli Netcool Performance Manager hardware requirements for the Solarisenvironment.

Tivoli Netcool Performance Manager has the following minimum hardwarerequirements for the Solaris environment.v 4 x SPARC64 VI (dual-core) 2.4GHz or 3 x SPARC64 VII (quad-core) 2.88GHz

processorv 16 GB Memoryv 2 x 146GB HDD

If deploying in a distributed environment, each server/zone requires:

1 x SPARC64 VI (dual-core) 2.4GHz or 1 x SPARC64 VII, (quad-core) 2.88GHzprocessor; 4 GB RAM; 146GB disk space.

AIX hardware requirements

Tivoli Netcool Performance Manager hardware requirements for the AIXenvironment.

Tivoli Netcool Performance Manager has the following minimum requirements forthe AIX environment:v 4 x POWER6 (Dual Core) 4.2 GHz, or 3 x POWER7 (Quad Core) 3.0 GHz

processor.v 16 GB Memoryv 2-x-146 GB HDD

If you are deploying in a distributed environment, each server/LPAR requires:v 1 x POWER6 (Dual Core) 4.2 GHz, orv 1 x POWER7 (Quad Core) 3.0 GHz processor;v 4-GB RAM; 146 GB disk space.

Other deployment configurations must be sized by IBM Professional Services.

Linux hardware requirements

Tivoli Netcool Performance Manager has a minimal deployment space requirementon Linux

Tivoli Netcool Performance Manager has the following minimum requirements forthe Linux environment:v 3 x Intel Xeon 5500/5600 series processors (quad-core), 2.4 GHz or greater.v 16 GB memory

Chapter 2. Requirements 5

v 2 x 300 GB HDD

If deploying in a distributed environment, each server/Virtual Machine requires:v 1 x Intel Xeon 5500/5600 series processor (quad-core) 2.4 GHzv 4 GB RAMv 300 GB disk space

Other deployment configurations should be sized by IBM® Professional Services.

Oracle and DB2 deployment space requirements

Tivoli Netcool Performance Manager has a minimal deployment space requirementfor Oracle servers.

When you install Oracle, the following host must confirm the previously statedhardware requirements for AIX, Solaris, and Linux. However, the database mayexperience problems if sufficient swap space is not provided.v The same amount of Swap as RAM must be present on the Oracle server host in

a distributed Tivoli Netcool Performance Manager system.v Twice as much Swap as RAM must be present on the Oracle server host for a

Tivoli Netcool Performance Manager proof of concept install.

Table 2. RAM Swap Space

RAM Swap Space

Between 1 GB and 2 GB 1.5 times the size of RAM

Between 2 GB and 16 GB Equal to the size of RAM

More than 16 GB 16 GB

Physical database design

A high-quality physical database design is an important factor in a successfuldatabase deployment. The choices and decisions that are made during physicaldatabase design have a long lasting effect and far reaching impact in terms ofoverall database health and day-to-day administrative overhead that is incurred ina data center. Understanding DB2 features and how it can be applied to meet thebusiness needs is crucial to come up with a high-quality physical database designthat can adapt to evolving business requirements over time.

A high-quality physical database design must consider the following items:v Business service level agreement (SLA)v I/O bandwidthv Performance objectives such as response time and throughputv Recovery timev Maintenance windowv Administrative overheadv Reliability, availability, and serviceability (RAS)v Data (lifecycle) management

6 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

As your business requirements change, you must reassess your physical databasedesign. This reassessment must include periodic revisions of the design. Ifnecessary, make configuration and data layout changes to meet your businessrequirements.v Minimize I/O traffic.v Balance design features that optimize query performance concurrently with

transaction performance and maintenance operations.v Improve the performance of administration tasks such as index creation or

backup and recovery processing.v Reduce the time database administrators spend in regular maintenance tasks.v Minimize backup and recovery elapsed time.v Reassess overall database design as business requirements change.

Use the following design best practices for RAS:v Design your business infrastructure with a solid sizing and capacity planning for

current and future needs as the business grows.v Identify and eliminate single point of failures (SPOF) in the business

infrastructure.v Implement redundancy in your infrastructure such as networks and mirrored

disks.v Implement high availability and disaster recovery solutions in all layers of

business infrastructure such as, database, application, and middleware.v For DB2 databases:

– Use separate high performing disks for data, transaction logs, and archivedlogs.

– Use mirrored logs for redundancy.– Create a backup and restore plan for backing up databases, table paces, and

transactional logs.

For more information about DB2 product configurations and best practices, seehttps://ibm.biz/Bdx2ew.

Disk and memory requirements

Ensure that an appropriate amount of disk space is available for your DB2environment, and allocate memory accordingly.

Disk requirements

The disk space that is required for your product depends on the type ofinstallation you choose and the type of file system you have. The DB2 Setupwizard provides dynamic size estimates based on the components that are selectedduring a typical, compact, or custom installation.

Remember to include disk space for required databases, software, andcommunication products. Ensure that the file system is not mounted withconcurrent I/O (CIO) option.

On Linux and UNIX operating systems, 2 GB of free space in the /tmp directory isrecommended, and at least 512 MB of free space in the directory is required.

Chapter 2. Requirements 7

Note: On Linux and UNIX operating systems, you must install your DB2 productin an empty directory. If the directory that you have specified as the install pathcontains subdirectories or files, your DB2 installation might fail.

Memory requirements

Memory requirements are affected by the size and complexity of your databasesystem, the extent of database activity, and the number of clients accessing yoursystem. At a minimum, a DB2 database system requires 256 MB of RAM. For asystem running just a DB2 product and the DB2 GUI tools, a minimum of 512 MBof RAM is required. However, 1 GB of RAM is recommended for improvedperformance. These requirements do not include any additional memoryrequirements for other software that is running on your system. For IBM dataserver client support, these memory requirements are for a base of five concurrentclient connections. For every additional five client connections, an extra 16 MB ofRAM is required.

For DB2 server products, the self-tuning memory manager (STMM) simplifies thetask of memory configuration by automatically setting values for several memoryconfiguration parameters. When enabled, the memory tuner dynamicallydistributes available memory resources among several memory consumersincluding sort, the package cache, the lock list, and buffer pools.

Paging space requirements

DB2 requires paging, also called swap to be enabled. This configuration is requiredto support various functions in DB2, which monitor or depend on knowledge ofswap/paging space utilization. The actual amount of swap/paging space that isrequired varies across systems and is not solely based on memory utilization byapplication software.

A reasonable minimum swap/paging space configuration for most systems is25-50% of RAM. These higher requirements are due to virtual memorypre-allocated per database instance, and retained virtual memory in the case ofSTMM tuning multiple databases. More swap/paging space might be wanted toprovision for unanticipated memory overcommitment on a system.

For more information about Prerequisites for a DB2 database server installation (Linuxand UNIX), see http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.qb.server.doc/doc/c0059823.html

Some DB2 configuration parameters settings

When a DB2 database instance or a database is created, a correspondingconfiguration file is created with default parameter values. You can modify theseparameter values to improve performance and other characteristics of the instanceor database. It is recommended that the two parameters; instance_memory anddatabase_memory are set to the default values in Tivoli Netcool PerformanceManager 1.4.

The disk space and memory that is allocated by the database manager that isbased on default values of the parameters might be sufficient to meet your needs.In some situations, however, you might not be able to achieve maximumperformance by using these default values.

8 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Each transaction processing environment is unique in one or more aspects. Thesedifferences can have a profound impact on the performance of the databasemanager when using the default configuration. For this reason, you might berequired to tune your configuration for your environment.

Configuration files contain parameters that define values such as the resourcesallocated to the DB2 database products and to individual databases, and thediagnostic level. There are two types of configuration files:

The database manager configuration file for each DB2 instance

The database manager configuration file is created when a DB2 instance iscreated. The parameters that it contains affect system resources at theinstance level, independent of any one database that is part of thatinstance. Values for many of these parameters can be changed from thesystem default values to improve performance or increase capacity,depending on your system's configuration.

Database manager configuration parameters are stored in a file nameddb2systm. This file is created when the instance of the database manager iscreated. In Linux and UNIX environments, this file can be found in thesqllib subdirectory for the instance of the database manager.

The database configuration file for each individual database

A database configuration file is created when a database is created, and islocated where that database exists. There is one configuration file perdatabase. Its parameters specify, among other things, the amount ofresource to be allocated to that database. Values for many of theparameters can be changed to improve performance or increase capacity.Different changes might be required, depending on the type of activity in aspecific database.

All database configuration parameters are stored in a file namedSQLDBCONF. These files cannot be directly edited, and can be changed orviewed via a supplied API or by a tool, which calls that API.

To change the database manager configuration parameters, use UPDATEDATABASE MANAGER CONFIGURATION command. Database configurationparameters can be changed by using UPDATE DATABASE CONFIGURATIONcommand.

Attention: If you edit db2systm, SQLDBCON, or SQLDBCONF by using amethod other than those provided by the database manager, you mightmake the database unusable. Do not change these files by using methodsother than those documented and supported by the database manager.

instance_memoryThe instance_memory is the database manager instance memoryconfiguration parameter. This parameter specifies the maximum amount ofmemory that can be allocated for a database partition if you are using DB2database products with memory usage restrictions or if you set it to aspecific value. In Tivoli Netcool Performance Manager 1.4, set thisparameter to AUTOMATIC. This setting allows instance memory to grow asneeded.

database_memoryThe database_memory is configuration parameter specifies the size of thedatabase memory set. The database memory size counts towards anyinstance memory limit in effect. The setting must be large enough to

Chapter 2. Requirements 9

accommodate the following configurable memory pools: bufferpools, thedatabase heap, the locklist, the utility heap, the package cache, the catalogcache, the shared sort heap, and an additional minimum overflow area of5%. In Tivoli Netcool Performance Manager 1.4, set this parameter toAUTOMATIC. The initial database memory size is calculated based on theunderlying configuration requirements.

logprimaryNumber of primary log files configuration parameter.

This parameter allows you to specify the number of primary log files to bepreallocated. The primary log files establish a fixed amount of storage thatis allocated to the recovery log files.

logsecond

Number of secondary log files configuration parameter.

This parameter specifies the number of secondary log files that are createdand used for recovery log files. The secondary log files are created only asneeded.

Following database configuration parameter values are set in the DB2 database forIBM Tivoli Netcool Performance Manager 1.4.

Log file size (4 KB) (LOGFILSIZ) = 8192This parameter defines the size of each primary and secondary log file. Thesize of these log files limits the number of log records that can be writtento them before they become full and a new log file is required.v Number of primary log files (LOGPRIMARY) = 50v Number of secondary log files (LOGSECOND) = -1

For more information about these and other parameters, see http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.admin.config.doc/doc/c0004555.html?cp=SSEPGG_10.1.0%2F2-2-4

Screen resolutionRecommended screen resolution details.

A screen resolution of 1024 x 768 pixels or higher is recommended when runningthe deployer.

Minimum requirements for a proof of concept installationTivoli Netcool Performance Manager has minimum required host specifications forProof of Concept (POC) deployments.

Note: The minimum requirements do not account for additional functionality suchas WebGUI, Cognos and MDE, each have additional memory and CPU impacts.

10 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Solaris hardware requirements (POC)

The minimum system requirements for a proof of concept install on Solaris.v 2 x SPARC64 VI (dual-core) 2.4GHz or 2 x SPARC64 VII (quad-core) 2.88GHz

processor.v 8GB Memoryv 1 x 146 GB HDD

To support:v SNMP data only.v All Tivoli Netcool Performance Manager components deployed on a single

server.v Number of resources supported up to 20,000.v 3 SNMP Technology Packs based on MIB II, Cisco Device and IPSLA.v 15 minute pollingv Number of DataView users limited to less than three.

AIX hardware requirements (POC)

The minimum system requirements for a proof of concept install on AIX.v 2 x Power6 (Dual Core) 4.2GHz, or 2 x Power7 (Quad Core) 3.0GHz processorv 8 GB Memoryv 1 x 146 GB HDD

To support:v SNMP data only.v All Tivoli Netcool Performance Manager components deployed on a single

server.v Number of resources supported up to 20,000.v 3 SNMP Technology Packs based on MIB-II, Cisco Device and IPSLA.v 15 minute pollingv Number of DataView users limited to less than three.

Note: Additional features such as WebGUI and Mass Data Extraction (MDE) arenot accounted for in this spec. They will have additional memory and CPUimpacts.

Linux hardware requirements (POC)

The minimum system requirements for a proof of concept install on Linux.v 2 x Intel Xeon 5500/5600 series processors (quad-core), 2.4 GHz or greaterv 8 GB memoryv 1 x 300 GB HDD

To support:v SNMP data only

Chapter 2. Requirements 11

v All Tivoli Netcool Performance Manager components deployed on a singleserver

v Number of resources supported up to 20,000v 3 SNMP Technology Packs based on MIB-II, Cisco Device and IPSLAv 15 minute pollingv Number of DataView users limited to less than three

Screen resolutionRecommended screen resolution details.

A screen resolution of 1024 x 768 pixels or higher is recommended when runningthe deployer.

Supported operating systems and modulesThe supported operating systems, modules, and third-party applications for IBMTivoli Netcool Performance Manager, Version 1.4.

The following sections list the supported operating systems, modules, andthird-party applications for IBM Tivoli Netcool Performance Manager, Version 1.4.

All subcomponents of the Tivoli Netcool Performance Manager - WirelineComponent can be installed on a mix of AIX, Linux, and Solaris operating systems;that is, the operating systems on which the DataChannel, DataView, DataLoad andDataMart subcomponents are installed do not have to be of the same type. Thesupported versions of AIX, Linux and Solaris operating systems are discussed inthis document.

For more information, see the Release notes - IBM Tivoli Netcool Performance Manager,Version 1.4 , which contains the version numbers for each Tivoli NetcoolPerformance Manager module in Version 1.4.

Attention: DB2 is supported on Linux only. Whereas, Oracle is supported onSolaris, AIX, and Linux systems.

Important: DataView can be installed on the server which has Jazz for ServiceManagement 1.1.0.3 installed. Jazz for Service Management 1.1.0.3 is supportedonly on AIX and Linux. Thus, in Tivoli Netcool Performance Manager 1.4,DataView can be installed on AIX or Linux platform only.

Solaris 10 for SPARC platforms

Supported Solaris systems.

Operating systems and kernelSupported operating system and kernel version.

Solaris 10 update 6 (released in October 2008).

Update level can be checked from /etc/release file.

Applying a kernel patch or a Solaris patch bundle is not the equivalent toinstalling the specific Solaris 10 "update 6" image. Oracle 11gR2 RDBMS software is

12 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

only certified for a base install image of Solaris 10 update 6 or greater. For moreinformation, see Document 971464.1, FAQ - 11gR2 requires Solaris 10 update 6 +.

Kernel Parameters

Solaris 10 uses the resource control facility to implement the System V IPC.However, Oracle recommends that you set both resource control and /etc/system/parameters. Operating system parameters that are not replaced by resourcecontrols continue to affect performance and security on Solaris 10 systems.Parameter Replaced by Resource Control Minimum Valuenoexec_user_stack NA (can be set in /etc/system only) 1semsys:seminfo_semmni project.max-sem-ids 100semsys:seminfo_semmsl process.max-sem-nsems 256shmsys:shminfo_shmmax project.max-shm-memory 4294967295shmsys:shminfo_shmmni project.max-shm-ids 100

Note: project.max-shm-memory represent the maximum shared memory availablefor a project, so the value for this parameter must be greater than sum of all SGAsize.

Refer to the following document for checking/setting kernel parameter values byusing resource control: Note 429191.1 Kernel setup for Solaris 10 using project files.v The 'umask' setting for the oracle user must be 022.v Hostname command must return the fully qualified hostname as either %

hostname or % hostname.domainname.

For more information, see the following:v NOTE:429191.1 - Kernel setup for Solaris 10 using project files.v NOTE:971464.1 - FAQ - 11gR2 requires Solaris 10 update 6 or greater

Refer to "Verifying UDP and TCP Kernel Parameters" in the 11g Solaris InstallGuide. Part Number E17163-01 for other recommended kernel parameters.http://download.oracle.com/docs/cd/E11882_01/install.112/e17163/pre_install.htm#BABEJIGD

Solaris 10 requirementsRequired packages and patches for the Solaris 10 system.

Tivoli Netcool Performance Manager requires at a minimum the End Userdistribution of Solaris 10.

Required packages:

Required packages for the Solaris 10 system.

Before installing the Oracle server, ensure the following Solaris packages areinstalled on your system:v SUNWarcv SUNWbtoolv SUNWcslv SUNWheav SUNWi15csv SUNWi1cs

Chapter 2. Requirements 13

v SUNWi1ofv SUNWlibCv SUNWlibmv SUNWlibmsv SUNWsprotv SUNWtoov SUNWxwfnt

To verify that the required Solaris packages are installed:1. Enter the following command at the shell prompt:

# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprotSUNWtoo SUNWuiu8

The following output confirms that the specified Solaris packages are installedcorrectly:

system SUNWarc Archive Librariessystem SUNWbtool CCS tools bundled with SunOSsystem SUNWhea SunOS Header Filessystem SUNWlibm Forte Developer Bundled libmsystem SUNWlibms Forte Developer Bundled shared libmsystem SUNWsprot Solaris Bundled toolssystem SUNWtoo Programming Tools...

2. If these packages are not on your system, see the Solaris Installation Guide forinstructions on installing supplementary package software.

Required patches:

Required patches for the Solaris 10 system.

To determine the patch level on your system, enter the following command:uname -v

Note: All Tivoli Netcool Performance Manager modules are tested to run on anEnd User distribution of Solaris 10.

The following list of minimum Solaris patches is required:v For all Installations :

– 120753-06: SunOS 5.10: Microtasking libraries (libmtsk) patch– 139574-03: SunOS 5.10: file crle ldd stings elfdump patch– 141444-09– 141414-02

To determine whether an operating system patch is installed, enter a commandsimilar to the following:1. Enter the command:

/usr/sbin/patchadd -p | grep patch_number(without version number)

For example, to determine if any version of the 120753-06 patch is installed, usethe following command:/usr/sbin/patchadd -p | grep 120753

14 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Solaris 10 virtualized containersIf you are using Solaris 10 virtualized containers, you must create containers with"whole root" partitions.

If you are using Solaris 10 virtualized containers, you must create containers with"whole root" partitions. Tivoli Netcool Performance Manager does not work incontainers with "sparse root" partitions.

Note: The Tivoli Netcool Performance Manager Self Monitoring Pack and SSMpacks do not report data correctly in virtualized environments, due tocompatibility issues of the underlying SSM agents in these configurations. TheMIB-II pack can also have difficulties discovering resources in virtualized serverenvironments.

DataMartDataMart requirements if you are using Solaris 10.

Configure the default language of Solaris to English.

IBM Java Runtime Environment (JRE) 1.6.

DataLoadDataLoad requirements if you are using Solaris 10.

Configure the default language of Solaris to English.

DataChannelDataChannel requirements if you are using Solaris 10.

Configure the default language of Solaris to English.

The DataChannel components require X libraries to be installed. The graphicaltools in DataChannel also require a running X server, which can be on a differenthost.

Technology packsTechnology pack requirements if you are using Solaris 10.

Installation of technology packs on Solaris 10 requires JRE 1.6 (32-bit). The correctversion is installed with the Topology Editor in the following default location:

/opt/IBM/proviso/topologyEditor/jre/bin

AIX platforms

Supported AIX systems.

Tivoli Netcool Performance Manager can be installed and operated in a virtualizedAIX environment.

Note: Tivoli Netcool Performance Manager on AIX does not support connection toa Solaris-based Oracle database.

Note: The Tivoli Netcool Performance Manager Self Monitoring Pack and SSMpacks do not report data correctly in virtualized environments, due to

Chapter 2. Requirements 15

compatibility issues of the underlying SSM agents in these configurations. The MIBII pack can also have difficulties discovering resources in virtualized serverenvironments.

Operating system

Supported operating system and kernel version.

IBM Tivoli Netcool Performance Manager, Version 1.4 supports:v AIX 6.1 TL 04 SP1 ("6100-04-01), 64-bit kernelv AIX 7.1 TL 0 SP3 ("7100-00-03"), 64-bit kernel

To verify your AIX release level:

As root, enter the following command at the shell prompt:# oslevel -r

This command returns a string that represents the maintenance level for your AIXsystem.

For AIX 6.1: If the operating system version is lower than AIX 6.1 TechnologyLevel 4 SP 1, then upgrade your operating system to this or a later level.

For AIX 7.1: If the operating system version is lower than AIX 7.1 TechnologyLevel 0 plus SP 3, then upgrade your operating system to this or a later level. AIXmaintenance packages are available from the following Web site:http://www-933.ibm.com/support/fixcentral/

Required files and fixes

Files and fixes required by Oracle and Tivoli Netcool Performance Manager for theAIX system.

AIX 6.1

The following operating system filesets are required for AIX 6.1:v bos.adt.basev bos.adt.libv bos.adt.libmv bos.perf.libperfstat 6.1.2.1 or laterv bos.perf.perfstatv bos.perf.proctoolsv xlC.aix61.rte:10.1.0.0 or laterv gpfs.base 3.2.1.8 or later

If you are using the minimum operating system TL level for AIX 6L listed above,then install all AIX 6L 6.1 Authorized Problem Analysis Reports (APARs) for AIX6.1 TL 02 SP1, and the following AIX fixes:v IZ41855v IZ51456v IZ52319

16 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

These 6.1 fixes are already present in the following TL levels:v AIX 6.1 TL-02 SP-04 and laterv AIX 6.1 TL-03 SP-02 and laterv AIX 6.1 TL-04

The following AIX fixes are required also:v IZ97457v IZ89165

Note: See Oracle Metalink Note:1264074.1 and Note:1379753.1 for other AIX 6.1patches that may be required

AIX 7.1

The following operating system filesets are required for AIX 7.1:v bos.adt.basev bos.adt.libv bos.adt.libmv bos.perf.libperfstatv bos.perf.perfstatv bos.perf.proctoolsv xlC.aix61.rte:10.1.0.0 or laterv xlC.rte:10.1.0.0 or later

If you are using the minimum operating system TL level for AIX 7.1 listed above,then install all AIX 7L 7.1 Authorized Problem Analysis Reports (APARs) for AIX7.1 TL 0 SP1, and the following AIX fixes:v IZ87216v IZ87564v IZ89165v IZ97035

Note: See Oracle Metalink Note:1264074.1 and Note:1379753.1 for other AIX 7.1patches that may be required.

Determining installed filesets

To determine if the required filesets are installed and committed, enter a commandsimilar to the following:# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.perfstat \bos.perf.libperfstat bos.perf.proctools

To determine the supported kernel mode, enter a command similar to thefollowing:# getconf KERNEL_BITMODE

Determining installed APAR fixes

To determine if an APAR is installed, enter a command similar to the following:# /usr/sbin/instfix -i -k "IZ42940 IZ49516 IZ52331 IZ41855 IZ52319"

Chapter 2. Requirements 17

If an APAR is not installed, then download it from the following Web site andinstall it: http://www-933.ibm.com/support/fixcentral/

Set resource limitsThe default user process limits are not adequate and must be reset.

On AIX systems, the default user process limits are not adequate for Tivoli NetcoolPerformance Manager. For detailed information on setting the correct user processlimits, see set Resource Limits in the Installing Tivoli Netcool Performance Manager -Wireline Component.

DataMart

DataMart requirements if you are using AIX.

Java Runtime Environment (JRE) 1.6 or higher (for the Database Informationmodule).

DataLoad

DataLoad requirements if you are using AIX.

No special requirements.

DataChannel

DataChannel requirements if you are using AIX.

The following DataChannel components require X libraries to be installed:v Bulk Collectorv CMEv DLDRv FTEv FED (also requires that an X Server is running)v LDRv The showVersion utility.

Technology packs

Technology pack requirements if you are using AIX.

Installation of technology packs on AIX 6.1 requires JRE 1.6 (32-bit). The correctversion is installed with the Topology Editor in the following default location:

/opt/IBM/proviso/topologyEditor/jre/bin

Viewing the documentation on AIX systems

Viewing the documentation requires that you can run Adobe Acrobat Reader.

To run on AIX systems, Adobe Acrobat Reader requires GIMP Toolkit (GTK+)Version 2.2.2 or higher. You can download the toolkit from the following URL:

http://www-03.ibm.com/servers/aix/products/aixos/linux/download.html

18 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

In addition, you must install all the dependent packages for GTK+. You can installGTK+ and its dependent packages either before or after installing Acrobat Reader.

At the time of publication, the latest version of GTK+ is gtk2-2.8.3-9, and thelatest versions of the dependent packages are as follows:v libpng-1.2.8-5

v libtiff-3.6.1-4

v libjpeg-6b-6

v gettext-0.10.40-6

v glib2-2.8.1-3

v atk-1.10.3-2

v freetype2-2.1.7-5

v xrender-0.8.4-7

v expat-1.95.7-4

v fontconfig-2.2.2-5

v xft-2.1.6-5

v cairo-1.0.2-6

v pango-1.10.0-2

v xcursor-1.0.2-3

v gtk2-2.8.3-9

To fulfill dependency requirements, you must install these Red Hat PackageManagers (RPMs) in the order specified.

Installing an RPM:1. To install an RPM use the following syntax:

rpm -i rpm_filename

2. To see a list of the RPMs that have been installed, enter the followingcommand:rpm -qa

Acrobat Reader and LDAP:

By default, AIX systems do not have LDAP installed.

By default, AIX systems do not have LDAP installed. If the AIX system does nothave LDAP installed and you run Acrobat Reader, a warning message is displayed.Click OK to have Acrobat Reader proceed normally.

To remove the error message, delete or rename /opt/acrobat/Reader/rs6000aix/plug_ins/PPKLite.api, where /opt/acrobat is the installation path.

Chapter 2. Requirements 19

Linux platforms

Supported Linux Systems

IBM Tivoli Netcool Performance Manager, Version 1.4 can be installed andoperated in an environment that is using VMware partitions. Here are the detailsthe Linux environment prerequisites for Tivoli Netcool Performance Manager.

Operating systemSupported operating system and kernel versions.

Table 3. Tivoli Netcool Performance Manager supports the following Linux systems.

v Linux hosts running 64-bit Red HatEnterprise Linux Version 6.x with Oracle11g (for fresh install).

v RHEL 5.9 (for upgrade option only).

v Linux hosts running 64-bit Red HatEnterprise Linux Version 6.x with DB2Version 10.1.0.1

To check the version of your operatingsystem, enter:

# cat /etc/redhat-release

This command must return the outputsimilar to:

Red Hat Enterprise Linux Serverrelease 6.x

To check the version of your operatingsystem, enter:

# cat /etc/redhat-release

This command must return the outputsimilar to:

Red Hat Enterprise Linux Serverrelease 6.x

To verify the processor type, run thefollowing command:

uname -p

To verify the processor type, run thefollowing command:

uname -p

To verify the machine type, run thefollowing command:

uname -m

To verify the machine type, run thefollowing command:

uname -m

To verify the hardware platform, run thefollowing command:

uname -i

To verify the hardware platform, run thefollowing command:

uname -i

All results should contain the output:

x86_64

All results should contain the output:

x86_64

Database

Database requirements if you are using Linux.

It is recommended that you consult Metalink Note 880989.1, Requirements ForInstalling Oracle11g On RHEL5, which has a full list of Oracle requirements forRHEL6. Oracle keeps this list up to date.

Note: See Note 225710.1 for supported kernels and Note 265262.1 for "Things toknow about Linux." https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=265262.1

20 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Required packages for Oracle on Red Hat Enterprise Linux 6.x

Required packages if you are using Linux.

The following is a list of packages for Red Hat Enterprise Linux 6.x:v binutils-2.20.51.0.2-5.11.el6 (x86_64)

v compat-libcap1-1.10-1 (x86_64)

v compat-libstdc++-33-3.2.3-69.el6 (i686) - both architectures are required.v compat-libstdc++-33-3.2.3-69.el6 (x86_64) - both architectures are required.v glibc-2.12-1.7.el6 (i686) - both architectures are required.v glibc-2.12-1.7.el6 (x86_64) - both architectures are required.v glibc-common-2.5-24 (x86_64)

v ksh-*.el6 (x86_64) - any version of ksh is acceptable.v libaio-0.3.107-10.el6 (i686) - both architectures are required.v libaio-0.3.107-10.el6 (x86_64) - both architectures are required.v libgcc-4.4.4-13.el6 (i686) - both architectures are required.v libgcc-4.4.4-13.el6 (x86_64)

v libstdc++-4.4.4-13.el6 (i686)

v libstdc++-4.4.4-13.el6 (x86_64)

v libXext-* (i686) - any version.v libX11-* (i686)

v libxcb-* (i686)

v libXau-* (i686)

v make-3.81-19.el6 (x86_64)

v libXtst-1.0.99.2-3.el6.i686

Note: These are minimum required versions. Also, for some architectures both ofthe i386 and x86_64 package versions must be verified.

For example, both the i386 and the x86_64 architectures for glibc-2.5-24 must beinstalled.

Also required are:v elfutils-libelf-devel-0.125-3.el5.x86_64.rpm

which in turn requires the following:– elfutils-libelf-devel and– elfutils-libelf-devel-static

One depends upon the other.Therefore, they must be installed together, in one (1)rpm -ivh command asfollows:rpm -ivh elfutils-libelf-devel-0.125-3.el5.x86_64.rpm elfutils-libelf-devel-static-0.125-3.el5.x86_64.rpm

v glibc-headers-2.5-24.x86_64.rpm

which in turn requires the following:– kernel-headers-2.6.18-92.el5.x86_64.rpm

Chapter 2. Requirements 21

– glibc-devel-2.12-1.7.el6 (i686).rpm - both architectures are required.– glibc-devel-2.12-1.7.el6 (x86_64).rpm- both architectures are required.

v gcc-4.4.4-13.el6 (x86_64.rpm)

which in turn requires the following:– libgomp-4.1.2-42.el5.x86_64.rpm

– libstdc++-devel-4.4.4-13.el6 (x86_64).rpm

– libstdc++-devel-4.4.4-13.el6 (i686).rpm

– gcc-c++-4.4.4-13.el6 (x86_64).rpm

– libaio-devel-0.3.107-10.el6 (i686).rpm - both architectures are required.– libaio-devel-0.3.107-10.el6 (x86_64).rpm - both architectures are required.– sysstat-9.0.4-11.el6 (x86_64).rpm

– unixODBC-2.2.11-7.1.x86_64.rpm - both architectures are required.– unixODBC-2.2.11-7.1.i386.rpm - both architectures are required.– unixODBC-devel-2.2.11-7.1.x86_64.rpm - both architectures are required.– ODBC-devel-2.2.11-7.1.i386.rpm - both architectures are required.

The following packages are required and checked for by the check_os.iniapplication:v libXp-1.0.0-i386

v libXp-1.0.0-x86_64

v libXpm-3.5.5-x86_64

v libstdc++-devel-4.1.1-x86_64

v glibc-devel-2.5-i386

v glibc-devel-2.5-x86_64

v gcc-c++-4.1.2-x86_64

v openmotif-2.3.3-4.el6.i686

v openmotif-2.3.1-i386

v openmotif-2.3.1-x86_64

v gtk2.i686 2.18.9-6.el6

v cairo-1.8.8-3.1.el6.i686

v atk-1.28.0-2.el6.i686

v openssl098e-0.9.8e-17.el6.i686

Required packages for IBM DB2 on Red Hat Enterprise Linux 6.x

Required packages if you are using Linux.

The following list shows the package requirements for Red Hat Enterprise Linuxdistributions:v libpam.so.0 (32-bit) is required for DB2 database servers to run 32-bit non-SQL

routines.v libaio.so.1 is required for DB2 database servers that are using asynchronous

I/O.v libstdc++.so.6 is required for DB2 database servers and clients.

22 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Table 4. Package requirements for Red Hat Enterprise Linux

Package name Description

libaio Contains the asynchronous library that isrequired for DB2 database servers.

compat-libstdc++ Contains libstdc++.so.6 (not required forLinux on POWER)

The following tables list the package requirements for Red Hat Enterprise Linuxdistributions for DB2 partitioned database servers.v The ksh93 Korn shell is required for RHEL5 systems. The pdksh Korn Shell

package is required for all other DB2 database systems.v A remote shell utility is required for partitioned database systems. DB2 database

systems support the following remote shell utilities:– rsh– ssh

By default, DB2 database systems use rsh when you run commands onremote DB2 nodes, for example, when you start a remote DB2 databasepartition. To use the DB2 database system default, the rsh-server packagemust be installed (see following table). More information about rsh and ssh isavailable in the DB2 Information Center.If you choose to use the rsh remote shell utility, inetd (or xinetd) must beinstalled and running as well. If you choose to use the ssh remote shell utility,you must set the DB2RSHCMD communication variable immediately after theDB2 installation is complete. If this registry variable is not set, rsh is used.

v The nfs-utils Network file system support package is required for partitioneddatabase systems.

All required packages must be installed and configured before you continue withthe DB2 database system setup. For general Linux information, see your Linuxdistribution documentation.

Table 5. Package requirements for Red Hat Enterprise Linux

Directory Package name Description

/System Environment/Shell pdksh or ksh93 Korn Shell.

/Applications/Internet openssh This package contains a setof client programs, whichallow users to runcommands on a remotecomputer via a Secure Shell.This package is not requiredif you use the defaultconfiguration of DB2database systems with rsh.

/System Environment/Daemons

openssh-server This package contains a setof server programs, whichallow users to runcommands from a remotecomputer via a Secure Shell.This package is not requiredif you use the defaultconfiguration of DB2database systems with rsh.

Chapter 2. Requirements 23

Table 5. Package requirements for Red Hat Enterprise Linux (continued)

Directory Package name Description

/System Environment/Daemons

rsh-server This package contains a setof programs, which allowusers to run commands on aremote computer. Requiredfor partitioned databaseenvironments. This packageis not required if youconfigure DB2 databasesystems to use ssh.

/System Environment/Daemons

nfs-utils Network File System supportpackage. It allows access tolocal files from remotecomputers.

Extra packages that are required:v binutils-2.17.50.0.6-6.el5 (x86_64)v compat-libstdc++-33-3.2.3-61 (x86_64)v compat-libstdc++-33-3.2.3-61 (i386)v elfutils-libelf-0.125-3.el5 (x86_64)v glibc-2.5-24 (x86_64)v glibc-2.5-24 (i686) - both architectures are required.v glibc-common-2.5-24 (x86_64)v ksh-20060214-1.7 (x86_64)v libaio-0.3.106-3.2 (x86_64)v libaio-0.3.106-3.2 (i386)v libgcc-4.1.2-42.el5 (i386)v libgcc-4.1.2-42.el5 (x86_64)v libstdc++-4.1.2-42.el5 (i386)v make-3.81-3.el5 (x86_64)

Note: These are minimum required versions. Also, for some architectures both ofthe i386 and x86_ 64 package versions must be verified. For example, both the i386and the x86_64 architectures for glibc-2.5-24 must be installed.v elfutils-libelf-devel-0.125-3.el5.x86_64.rpm

Requires the following interdependent packages:– elfutils-libelf-devel– elfutils-libelf-devel-static

Note: Since these packages are interdependent, they must be installedtogether by using the following command:rpm -ivh elfutils-libelf-devel-0.125-3.el5.x86_64.rpmelfutils-libelf-devel-static-0.125-3.el5

v glibc-headers-2.5-24.x86_64.rpmRequires the following packages:– kernel-headers-2.6.18-92.el5.x86_64.rpm– glibc-devel-2.5-24.x86_64.rpm– glibc-devel-2.5-24.i386.rpm

24 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

v gcc-4.1.2-42.el5.x86_64.rpmRequires the following packages:– libgomp-4.1.2-42.el5.x86_64.rpm– libstdc++-devel-4.1.2-42.el5.x86_64.rpm– gcc-c++-4.1.2-42.el5.x86_64.rpm– libaio-devel-0.3.106-3.2.x86_64.rpm– libaio-devel-0.3.106-3.2.i386.rpm– sysstat-7.0.2-1.el5.x86_64.rpm– unixODBC-2.2.11-7.1.x86_64.rpm– unixODBC-2.2.11-7.1.i386.rpm– unixODBC-devel-2.2.11-7.1.x86_64.rpm– unixODBC-devel-2.2.11-7.1.i386.rpm

v The following packages are required and checked for by the check_os.iniapplication:– libXp-1.0.0-i386– libXp-1.0.0-x86_64– libXpm-3.5.5-x86_64– libstdc++-devel-4.1.1-x86_6– glibc-devel-2.5-i386– glibc-devel-2.5-x86_64– gcc-c++-4.1.2-x86_64– openmotif-2.3.1-i386– openmotif-2.3.1-x86_64

Run the db2prereqcheck command to check if your system meets the prerequisitesfor the installation of a specific version of DB2 for Linux, UNIX, and Windows. Forexample, run the following commands:./db2prereqcheck -v 10.1.0.1 -s

DBT3533I The db2prereqcheck utility has confirmed that all installation prerequisiteswere met for DB2 database "server " "". Version: "10.1.0.1"DBT3533I The db2prereqcheck utility has confirmed that all installation prerequisiteswere met for DB2 database "server " "with DB2 pureScale feature ". Version: "10.1.0.1"

DataMart

DataMart requirements if you are using Linux.

Java Runtime Environment (JRE) 1.6 or higher (for the Database Informationmodule).

DataLoad

DataLoad requirements if you are using Linux.

No special requirements.

Chapter 2. Requirements 25

DataChannel

DataChannel requirements if you are using Linux.

No special requirements.

Required user namesThere are two user names that must be created when installing Tivoli NetcoolPerformance Manager.

Two specific user names are required on any server hosting Tivoli NetcoolPerformance Manager components, they are:

pvuserA dedicated Tivoli Netcool Performance Manager Unix user.

oracle A dedicated Oracle user.

db2 A dedicated DB2 user.

pvuserThe pvuser user name.

The Tivoli Netcool Performance Manager UNIX user pvuser must be added to eachserver hosting a Tivoli Netcool Performance Manager component. The TivoliNetcool Performance Manager UNIX user, which is referred to as pvuserthroughout the documentation, can be named by using any string as required byyour organizations naming standards.

oracle

The oracle user name.

The Oracle user oracle is added to each server hosting a Tivoli NetcoolPerformance Manager component. This user is added when installing either Oracleclient or server. The default username used is oracle; however, this Oracleusername can be named using any string as required by your organizationsnaming standards.

Note: Should you choose a non-default Oracle username, you must use the samename across all instances of Oracle Client and Server throughout your TivoliNetcool Performance Manager system.

26 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

db2

The db2 user name.

The DB2 user db2 is added to each server hosting a Tivoli Netcool PerformanceManager component. This user is added when installing either DB2 client orserver. The default username used is db2; however, this DB2 username can benamed using any string as required by your organizations naming standards.

Note: If you want to select a non-default DB2 username, you must use the samename across all instances of DB2 client and server throughout your Tivoli NetcoolPerformance Manager system.

Ancillary software requirementsExtra and third-party software requirements.

The following sections outline the extra software packages required by TivoliNetcool Performance Manager.

FTP supportTivoli Netcool Performance Manager requires FTP support.

The FTP (File Transfer Protocol) version used to transfer files between TivoliNetcool Performance Manager components is delivered with Solaris 10.

AIX also uses FTP to transfer files between Tivoli Netcool Performance Managercomponents.

Tivoli Netcool Performance Manager supports the following file transport protocolsbetween Tivoli Netcool Performance Manager components and third-partyequipment (for example, EMS):v FTP Solaris 10v Microsoft

®

Internet Information Services (IIS) FTP server

Open SSH and SFTPTivoli Netcool Performance Manager requires OpenSSH and SFTP support.

Tivoli Netcool Performance Manager supports encrypted Secure File Transfer(SFTP) and FTP to move data files from DataLoad to DataChannel, or fromDataChannel Remote to the DataChannel Loader.

Tivoli Netcool Performance Manager SFTP is compatible only with OpenSSHserver and client version 3.1p1 and above. OpenSSH is freely downloadable anddistributable (http://www.openssh.org). OpenSSH is supported on Solaris, AIX,and Linux. Other SSH versions such as F-Secure, the SSH bundled in Solaris 10and the SSH bundled with AIX is not compatible.

If you use the SFTP capability, you must obtain, install, generate keys for, maintain,and support OpenSSH and any packages required by OpenSSH.

See Tivoli Netcool Performance Manager Technical Note: DataChannel Secure File TransferInstallation for more information about installing and configuring OpenSSH.

Chapter 2. Requirements 27

AIX requirements

AIX requirements in order to use OpenSSH and SFTP.

The following table lists additional prerequisites that must be installed on an AIXsystem, and where these packages can be found:

Table 6. Additional Prerequisites

Package Location

openssl-0.9.7g-1.aix5.1.ppc.rpm https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=aixtbx

openssh-4.1p1_53.tar.Z https://sourceforge.net/projects/openssh-aix/

bos.adt.libm AIX installation CD.

Solaris requirements

Solaris requirements in order to use OpenSSH and SFTP.

The following are additional prerequisites that must be installed on an Solarissystems:v openssh- SSH client (openssh-4.5p1-sol-sparc-local.gz or higher).v zlib - zlib compression and decompression library (zlib-1.2.3-sol9-sparc-

local.gz or higher).

Linux requirements

Linux requirements in order to use OpenSSH and SFTP.

OpenSSH is required for VSFTP to work with Tivoli Netcool Performance Manager.OpenSSH is installed by default on any RHEL system.

By default, FTP is not enabled on Linux systems. You must enable FTP on yourLinux host to carry out the installation of Tivoli Netcool Performance Manager.

To enable FTP on your Linux host, run the following command as root:

/etc/init.d/vsftpd start

File compressionFile compression support.

Archives delivered as part of the IBM Tivoli Netcool Performance Managerdistribution are created by using GNU Tar. This program must be used for thedecompression of archives.

28 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

DataView load balancingLoad balancing support.

IBM Tivoli Netcool Performance Manager supports the use of an external loadbalancer to optimize the use of available DataView instances.

The load balancer must support the following basic features:v Basic IP-based load balancingv Sticky sessions based on incoming IPv Up/down status based on checking for a listening port

The following is the link to the CSS Basic Configuration Guide: http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v7.20/configuration/basic/guide/bsccfggd.html

DatabasesTivoli Netcool Performance Manager 1.4 supports both the databases, Oracle andIBM DB2.

Oracle support

Oracle server support and hidden Oracle parameters.

License recommendations

When purchasing a license from Oracle, IBM recommends a Processor licenserather than a Named User Plus license.

Oracle defines a Named User in such a way that it includes not only actual humanusers, but also non-human-operated devices. In other words, you would require aNamed User Plus license for every resource that Tivoli Netcool PerformanceManager polls, which would be very expensive.

http://www.oracle.com .

Oracle server support

Oracle 11g Enterprise Edition for Solaris (SPARC) and Linux AIX are 64-bitonly. Oracle 11g Enterprise Edition must include the partitioning option.The database no longer provides 32-bit libraries, therefore you must installthe Oracle client on every host of the Tivoli Netcool Performance Manager.

Note: Tivoli Netcool Performance Manager must be installed and run as astandalone database. It must not be placed on a server that already has adatabase as the installation program will likely to interfere. The co-hostingof Tivoli Netcool Performance Manager also affects performance inunknown ways. If a co-host is required then the Customer should seek outProfessional Services for support.

Hidden Oracle parameters

This section lists all of the Oracle '_', or hidden parameters, used by TivoliNetcool Performance Manager:v _partition_view_enabled = TRUEv _unnest_subquery = FALSE

Chapter 2. Requirements 29

v _gby_hash_aggregation_enabled = FALSE

DB2 servers and IBM Data Server clients

DB2 server and client support.

DB2 server support

IBM DB2 Enterprise Server Edition 10.1.0.1, Linux 64-bit only.

Note: Tivoli Netcool Performance Manager must be installed and run as astandalone database. It must not be placed on a server that already has adatabase as the installation program will likely to interfere. The co-hostingof Tivoli Netcool Performance Manager also affects performance inunknown ways. If a co-host is required then the Customer must seek IBMProfessional Services for support.

DB2 client support

IBM Data Server Client 10.1.0.1 Linux 64-bit only.

Note: Tivoli Netcool Performance Manager must be installed and run as astandalone database. It must not be placed on a server that already has adatabase as the installation program will likely to interfere. The co-hostingof Tivoli Netcool Performance Manager also affects performance inunknown ways. If a co-host is required then the Customer must seek IBMProfessional Services for support.

For more information about DB2 servers, see http://www.ibm.com/software/data/db2/.

Jazz for Service ManagementDashboard Application Services Hub is replacing the Tivoli Integrated Portal.

Jazz for Service Management contains the following components:v Administration Servicesv Dashboard Application Services Hubv Security Servicesv Registry Servicesv Administration Services UIv Reporting Services environmentv Tivoli Common Reporting

Note: The supported Tivoli Common Reporting is 3.1.0.2

30 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Java Runtime Environment (JRE)Required Java support.

Java Runtime Environment (JRE) 1.6 (32-bit) is required for all servers hostingTivoli Netcool Performance Manager components.

Web browsers and settings for DataView reportsSupported browsers.

The following browsers are required to support the Web client and provide accessto DataView reports:

Important: No other browser types are supported.

Table 7. Windows Clients

Windows Vista Windows 7

v Microsoft Internet Explorer 8.0, 9.0

v Mozilla Firefox ESR 17 and 24

v Microsoft Internet Explorer 8.0, 9.0

v Mozilla Firefox ESR 17 and 24

Note: When using Windows Internet Explorer, IBM recommends that you haveavailable at least 1GB of memory

Table 8. UNIX Clients

AIX RHEL 6 Solaris 10

v Mozilla Firefox ESR 17 and24

v Mozilla Firefox ESR 17 and24

v Mozilla Firefox ESR 17 and24

The following are required browser settings:v Enable JavaScriptv Enable cookies

Browser requirements for the LaunchpadWeb browser requirements for the Launchpad.

The new Launchpad has been tested on the following browsers:

:v Mozilla Firefox

:v Mozilla Firefox

:v Mozilla Firefox

For information about downloading and installing these browsers, see thefollowing web sites:v http://www.mozilla.org/v http://www-03.ibm.com/systems/p/os/aix/browsers/index.html

Chapter 2. Requirements 31

Note: You must be a registered user to use this site.

Screen resolutionRecommended screen resolution details.

A screen resolution of 1152 x 864 pixels or higher is recommended for the displayof DataView reports. Some reports may experience rendering issues at lowerresolutions.

Report Studio - CognosReport Studio support.

Report Studio is only supported by Microsoft Internet Explorer.

X EmulationRemote desktop support.

For DataMart GUI access, Tivoli Netcool Performance Manager supports thefollowing:v Native X Terminalsv Exceed V 6.x

The following libraries are required in order for Exceed to work with Eclipse:v libgtk 2.10.1v libgib 2.12.1v libfreetype 2.1.10v libatk 1.12.1v libcairo 1.2.6v libxft 2.1.6v libpango 1.14.0v Real VNC server 4.0

Tivoli Netcool/OMNIbus Web GUI integrationTivoli Netcool/OMNIbus Web GUI, Version 8.1 support.

The IBM Tivoli Netcool/OMNIbus Web GUI Integration Guide for Wireline describeshow to integrate IBM Tivoli Netcool® /OMNIbus Web GUI and Jazz™ for ServiceManagement 1.1.0.3 with the wireline component of Tivoli Netcool PerformanceManager.

Tivoli Netcool Performance Manager 1.4 supports:

Jazz for Service Management 1.1.0.3 and Tivoli Netcool/OMNIbus Web GUI 8.1.

The web browsers supported by Tivoli Netcool/OMNIbus Web GUI and TivoliNetcool Performance Manager are listed in the following table.

Table 9. Web clients browsers supported by Tivoli Netcool/OMNIbus Web GUI

Browser Version Operating system

Internet Explorer 8.09.0

Windows 7

32 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Table 9. Web clients browsers supported by Tivoli Netcool/OMNIbus Web GUI (continued)

Browser Version Operating system

Mozilla Firefox Mozilla Firefox ESR 17and 24 Windows 7

Red HatEnterprise Linux (RHEL) 6.x

Note: When you are using Internet Explorer, IBM recommends that you have atleast 1 GB of memory available.

Microsoft Office VersionMicrosoft Office support.

The Tivoli Netcool Performance Manager DataView Scheduled Report optiongenerates files compatible with Microsoft Office Word 2002 or higher.

Chapter 2. Requirements 33

34 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Chapter 3. Architecture information

Supported architecture configurations.

The following sections provide information on the supported architectureconfigurations.

ServerTime synchronizationSever synchronization requirements.

Tivoli Netcool Performance Manager requires that the clocks on all Solaris serversrunning Tivoli Netcool Performance Manager modules be synchronized. IBMrecommends using NTP (or equivalent) to keep all Tivoli Netcool PerformanceManager synchronized to within 500 milliseconds.

Multiple SNMP DataLoad collectorsYou can install multiple SNMP DataLoad collectors on the same host

In Tivoli Netcool Performance Manager 1.4 you can have multiple collectors perhost. This helps in reducing the server resources required. In certain customer sitesthey have up to 40 SNMP collectors that required 40 hosts (any of which could bevirtual hosts). In the current scenario multiple collectors are allowed on a singlehost, which reduces the number of servers (physical or virtualized) but does notchange the disk or CPU requirements. However, each multiple collector that isadded requires 4 GB RAM for efficient functioning

This makes the solution cost-effective with minimum changes to the topology toaccommodate this for service providers with their current network and also forservice providers with growing networks.

CPU improvements came in the form of faster cores but now come as multiplecores. This change in computer hardware architecture drives changes in how TivoliNetcool Performance Manager scales. Tivoli Netcool Performance Manager used toscale by adding "commodity hardware" so we did not frequently encounter thescenario where it was not necessary to put multiple SNMP DataLoad collectors ona single box but now the "commodity hardware" is frequently a 4-16 core machine.So this change will add value to Tivoli Netcool Performance Manager scalability.

This scenario results in:v Reduction in number of operating system instancesv Reduction in related licensing, support and maintenance costsv Ease in handling the upgrade process

© Copyright IBM Corp. 2006, 2014 35

DataChannel subchannelsSubchannel support.

Datachannel limit is increased from 8 to 16 in Tivoli Netcool Performance Manager1.4. Tivoli Netcool Performance Manager supports up to 40 subchannels perdatabase channel.

DataChannel remoteSupported DataChannel deployment types.

Tivoli Netcool Performance Manager supports two deployment types forDataChannel:v DataChannel Standard, usually deployed on the central site. This requires the

standard DataChannel module.v DataChannel Remote Channel option, where the Sub-Channel component (also

called CME) is split from the rest of the central DataChannel and deployed onthe remote DataLoad server (usually on a remote site, behind a fire-wall).

This option is primarily intended for Managed Network Service Providers whoneed to place the DataChannel component at an end-user site, co-located with thedata collector. The benefits of the DataChannel Remote option are:v Allows Managed Network Service Providers to better align costs with revenues

as they scale their systems to support more end customers.v Improves distributed Fault managementv Closer to alarm receiver and correlationv Threshold detection resistant to disconnectionv Reduces hardware costsv Leverages available CPU if remote DataLoad under loaded (unused CPU can be

used by DataChannel remote - CME)

Please refer to “SNMP version support,” on page 53 for more information aboutthis option.

The following sections describe both deployment types in more detail.

DataChannel "Standard"Standard DataChannel installation.

DataChannel "Standard", usually deployed on the central site. This requires thestandard DataChannel module.

DataChannel Standard Installation

36 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

For firewall configuration recommendations, see “Firewall configuration” on page43.

DataChannel "Remote Channel Option"DataChannel remote installation.

In this mode, Tivoli Netcool Performance Manager allows the CME to be installedon a remote system away from the rest of the DataChannel components (such ascustomer premise equipment).

The DataChannel Remote system is composed of the following elements and obeysthe stated execution order:1. Collector2. File Transfer Engine3. Complex Metric Engine

All DataChannel Remote elements must be installed on the same server and filesystem.

Multiple DataChannel Remote systems can plug into the DataChannel system,which is composed of the following elements and obeys the following order ofexecution:

Loader Staging, which inovlves either of the following:v Daily Loader: interacts with the Database Serverv Hourly Loader: interacts with the Database Server

Chapter 3. Architecture information 37

Tivoli Netcool Performance Manager on Solaris 10Options when deploying Tivoli Netcool Performance Manager on Solaris.

This section describes some basic scenarios for introducing Tivoli NetcoolPerformance Manager into the Solaris 10 operating environment, and options fordeploying Tivoli Netcool Performance Manager modules within Solaris 10containers. It is not an attempt to describe all possible deployment options.

Multiple SNMP collectors are supported on the same Solaris 10 server, as long aseach collector is isolated in a separate Solaris 10 container.

Note: Do not install more than one DataLoad SNMP collector in any given Solaris10 container. Installing two or more collectors in a container will causeperformance to degrade due to those collectors competing for CPU resources.

With the one exception noted above, all deployments of Tivoli NetcoolPerformance Manager modules within Solaris 10 containers are possible - forexample:v All modules can be installed within a single container on the same Solaris 10

server.v Each module can be installed in a separate container on separate Solaris 10

servers.v Any combination of module deployments in between the above deployments is

also possible (with the exception of the SNMP collector restriction noted above).

Note: In configuring Solaris containers for each Tivoli Netcool PerformanceManager component, follow the limitations for server CPU, disk, and memorydocumented for those components.

New installs on Solaris 10A scenario illustrating a possible deployment of Tivoli Netcool PerformanceManager.

In this scenario, a customer is installing Tivoli Netcool Performance Manager attheir site for the first time, and chooses to do so on a Solaris 10 server. Thefollowing illustration shows a possible deployment of Tivoli Netcool PerformanceManager modules - DataLoad (DL), DataChannel (DC), DataView (DV), DataMart(DM), and Database (DB) - on a single Solaris 10 server:

38 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Tivoli Netcool Performance Manager inventory deploymentTivoli Netcool Performance Manager supports an architecture for the Inventoryprocess.

Tivoli Netcool Performance Manager supports an architecture for the Inventoryprocess, which is especially evident at the SNMP Discovery level. The SNMPDiscovery portion of inventory collection is implemented as a permanentlyrunning process (a daemon).

The new Inventory architecture provides several benefits:v The logic for defining Element uniqueness rules, as well as Element "correlation"

(when the same network Element is discovered several times from several of itsinterfaces) is now exposed (in the file inventory_elements.txt). This enablesyou to adapt the rules for Elements that do not support the expected MIBvariables (the one Tivoli Netcool Performance Manager uses to implement theuniqueness and correlation rules).

v The Inventory GUI supports several features, typically implemented with hookscripts. The new architecture makes the hook scripts simpler and moremaintainable.

v Log messages issued by the Discovery process now comply with the centralizedLOG mechanism (that is, support has been added for logging to syslog).

The following sections explain the supported Inventory deployments (BULK andSNMP) and help you making deployment choices related to the SNMP Discoveryserver.

Tivoli Netcool Performance Manager Inventory is made up of Discovery,Synchronization, and Grouping phases.

Chapter 3. Architecture information 39

Content of the SNMP inventory componentRequirements of the SNMP Inventory Component.

The SNMP Inventory component is made up of the following:v Inventory CLI and Inventory GUI (profile management, as in 3.x)v 4.0 SNMP Discovery serverv Hook scripts

The SNMP Inventory component is installed by the DataMart installation - exceptthe new 4.0 SNMP Discovery server, which is part of the DataChannel installation.

The SNMP Inventory component (especially the SNMP Discovery process) isusually unique for the entire Tivoli Netcool Performance Manager system, and canserve multiple SNMP Collectors.

However, if several SNMP Inventory components must be installed, they cannot beinstalled on the same machine. In this case, you must install the entire DataMartcomponent on each machine.

For performance reasons. This configuration is unlikely given the low impact ofthe Inventory process on the overall system.

Content of the BULK inventory componentRequirements of the BULK Inventory Component.

The BULK Inventory process is made up of:v Inventory CLI and Inventory GUI (profile management, as in 3.x)v Cron'ed CLI pollinvv Cron'ed CLI pollprofilev Hook scripts

The BULK Inventory component is installed by the DataMart installation.

As will be explained in the following deployment scenarios, there cannot beconnectivity issues between Bulk Collector and BULK Inventory. Therefore, IBMrecommends the following approach:v Bulk Collector and BULK Inventory should never be separated by a WAN

and/or firewall, NAT, or any component that may hinder the connection.

Note: These configurations (WAN, Firewall, or NAT) are not supported.v For a critical use of the Bulk collector (for example, expected service levels,

billing, and so on), IBM recommends that you install a Bulk Inventory on thesame machine. In this case, you must run the DataMart installation as manytimes as there are Bulk collectors.

v For a standard use of the Bulk collector, IBM recommends that you install aunique Bulk Inventory on the DataMart machine. In this case, there should be avery reliable connection between the Bulk Inventory and the Database, andbetween the Bulk Inventory and the Bulk Collector (LAN).

DataChannel Central and Bulk Collector centralDeployment configurations.

The deployment shown in the following figure is characterized by:

40 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

v DataChannel deployed centrally (Standard)v BULK deployed centrally for critical usage

DataChannel Central and Bulk Collector Central (Critical)

The deployment shown in the following figure is characterized by:v DataChannel deployed centrally (Standard)v BULK deployed centrally for standard usage

DataChannel Central and Bulk Collector Central (Standard)

DataChannel Remote and Bulk Collector remoteDeployment configurations.

DataChannel Remote and Bulk Collector Remote

Chapter 3. Architecture information 41

When DataChannel Remote is deployed (remotely), in order to process data flowgenerated by a bulk collector, the same machine needs to support:v Remote Sub-channelv Remote Bulk Collectorv Remote Bulk Inventory

DataChannel Central and Bulk Collector remoteDeployment configurations.

The deployment shown in the following figure is characterized by:v DataChannel deployed centrally (Standard)v BULK deployed remotely

DataChannel Central and Bulk Collector Remote

Tivoli Netcool Performance Manager does not support Bulk Inventory processesbeing on the other side of the firewall or though a WAN, compared to BulkCollector, as shown in the following figure:

Figure 6: Unsupported Firewall Configuration

DataChannel Central, SNMP Collector remote, and SNMPinventory centralDeployment configurations.

The deployment shown in the following figure is characterized by:v DataChannel deployed centrally (Standard)

42 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

v SNMP collector deployed remotelyv SNMP Inventory deployed centrally

DataChannel Central, SNMP Collector Remote, and SNMP Inventory Central

DataChannel and SNMP Collector remote, and SNMP inventorycentralDeployment configurations.

This deployment is characterized by:v DataChannel deployed remotelyv SNMP collector deployed remotelyv SNMP Inventory deployed centrally

Figure 8: DataChannel and SNMP Collector Remote, and SNMP Inventory Central

Related informationLinks to further information.v For more information on collectors and inventory deployments, see the

"Configuring the Discovery Server" section in the Installing Tivoli NetcoolPerformance Manager - Wireline Component

v For firewall recommendation related to the SNMP Discovery Server, see “SNMPinventory” on page 51.

Firewall configurationFirewall Configuration.

The following sections explain firewall configurations.

Chapter 3. Architecture information 43

DataChannel standardFirewall support for a DataChannel standard configuration.

This section explains Tivoli Netcool Performance Manager firewall support, andthe protocols to open through them. The direction of the connection opening isshown by the following arrows.

Note: Modules are also centrally managed, so the management protocols also needto open through the firewalls.

As shown in the following figure, aside from file transfer and databaseconnectivity, management protocols need to pass through the firewalls. DataMart,using the internal 3002 protocol, manages SNMP Collectors. The ChannelManagement modules, through CORBA, manage the Bulk Collectors and theDataChannel modules. Additionally, these modules log through UDP to a remotelogger.

Note: You can use a different port other than port 3002.

Protocols Through Firewalls - DataChannel Standard

Channel management overviewChannel management module communication.

The Channel Management modules communicate between machines supportingthe DataChannels, and these modules are the components that need static ports.The set of management modules for all DataChannels includes a Channel Manager,a Channel Name Server, a Log Server, and one Application Manager for eachmachine supporting the DataChannels, Bulk Collectors, and the Discovery server.For restrictive firewalls, the protocols used by these components need to be setstatically and the firewalls must be configured to allow these protocols through.

The Topology Editor can be used to statically set many of these ports.

Important: The Topology Editor can set the CORBA port for the managementcomponents (except the log server, which does not use CORBA), but not for theregular components (CMEs and FTEs, for example). Normally, the CORBA portsfor regular components are dynamic, because they communicate only with theAMGR, which is on the same machine and not affected by firewalls.

Configuring a static portConfiguring static ports by using the Topology Editor.

44 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

About this task

When you upgrade from an existing installation or installing for the first time, youcan configure the static ports by using the Topology Editor.

Note: If you have an installation configuration file, you can use it when you runthe Topology Editor. Or, you can re-enter all relevant information and save theinstallation configuration file and use it for the next time you upgrade.

To configure static ports, follow these steps:

Procedure1. Determine which ports you can set statically. For more information,

see.“Choosing static ports” on page 46. Open these ports in the appropriatefirewalls.

2. Set the ports for the following protocols in the Topology Editor:v Log Server portv IOR Server portv Name service portv Channel Manager CORBA portv For each host: the Application Manager CORBA portv For each Sub-Channel component: the trap port

Note: There are other protocols that you must open in the firewall that is notconfigured here.

3. Install the DataChannel. Save the installer configuration file.4. For each Bulk Collector that is running in DISCOVERY_MODE==noinventory,

manually edit the topology and add 3002_SERVICE_PORT for each Collector. Forexample, BCOL.2.36.3002_SERVICE_PORT=4003

5. Restart the channel management and the channels.DataView and DataMart also need ports that are opened in the firewallsee,“Standard Deployment of DataChannel” on page 46. See the DataView andDataMart documentation for information about configuring ports, if necessary.

What to do next

For information on assigning static ports to some DataChannel components, seeAssigning static port to some DataChannel components on remote server

Assigning static port to some DataChannel components onremote serverWhen the FTE and CME components are on remote DataChannel server, a staticport must be configured. Then, the FTE is able to communicate with PBL from thelocal DataChannel.

Each component listens for inbound CORBA communications. By default, arandom port is selected and the port gets registered in the CNS shortly afterstartup. You can override the default port by using the following configurationsetting:PBL.CORBA_PORT = <port_number>

For example: PBL.CORBA_PORT = 9007

Chapter 3. Architecture information 45

Note: This configured port must be allowed to access through the firewall.

Choosing static portsChoosing Static Ports.

About this task

You need to choose which ports to use. Ask your Network Administrator for theseports or choose the ports yourself, based on “Standard Deployment ofDataChannel.” Some ports used by Tivoli Netcool Performance Manager arestandard ports, like FTP. Other ports you need to choose. You can use the sameport on different machines. For example, you can assign the same port to allApplication Managers.

There are several places you can look to see if a given port is already in use. Firstchoose the range, then check to see if it is in use.

When selecting ports, follow these guidelines:v Choose your ports from the range 1024 to 32767. The other ranges are reserved

(or sometimes used) for other applications. Ports 1 to 1023 are reserved portsand ports 32768 to 65535 are ephemeral ports.

v Check the file /etc/services on each machine and see if any of these ports arebeing used by a different application

v As a fail-safe, run netstat -a to see if this port is in use by other applications.Make sure the DataChannels and Channel Management are not running whenyou check.

Active and Passive FTP (Alcatel-Lucent 5620 SAM technologypack only)Alcatel-Lucent 5620 SAM Technology Pack support.

The Alcatel-Lucent 5620 SAM Technology Pack supports both active and passiveFTP through the firewall.

Use the following guidelines when specifying passive or active data transfer modein URI (Universal Resource Identifier) specifications:v By default, the Alcatel-Lucent 5620 SAM uses active connections (traditional FTP

mode). You can, however, explicitly specify active data transfer mode byappending ;mode=active to the end of the FTP (File Transfer Protocol) URI(Universal Resource Identifier) as in the following example:

ftp://loginname:password@hostname//full/path/to/resource;mode=active

v To use passive data transfer mode, you must explicitly specify passive mode byappending ;mode=passive to the end of the FTP URL as in ther followingexample:

ftp://loginname:password@hostname//full/path/to/resource;mode=passive

For information on recommended ports, see the following URL:http://slacksite.com/other/ftp.html

Standard Deployment of DataChannel:

Describes the standard deployment of Datachannel.

The following table lists the module-to-protocol mappings for the standarddeployment of DataChannel.

46 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Note the following:v The cells marked with an "X" identify the modules that are communicating with

one another.v FM represents the TRAP receiver of the Fault Management external station. This

is not a Tivoli Netcool Performance Manager module.

Module-to-Protocol Mapping For DataChannel Standard Deployment

Dev DL DC DM DB DV WEB FM Module/ Pair ProtocolPort Type /

Port # Dir. Property Setting in Topology Editor

X X SNMP Device- SNMPDataLoad

SNMP forcollection

Static UDP 161 � �

X X Bulk Device -Bulk DataLoad

FTP or TFTPor otherprotocol

Devicedependent

X X SNMPDataLoad -DataChannel

FTP forcollection

Static,non-configurableTCP 20, 21 orsFTP/TCP 22

X X SNMPDataLoad -DataChannel

ChannelManageraccess toSNMP Coll.For Real Time

Static,configurableTCP 3002

� For each SNMP Collector:PVM_SNMP_COLL_SSDPORT=3002PVM_SSDPORT=3002 (These areentered using SERVICE_PORT in theTopology Editor: DataChannel >Admin Components > ChannelManager and DataChannel > AdminComponents > CORBA NamingServer Host)

X X Bulk DataLoad- DataChannel

FTP metriccollection OrSFTP

Static,non-configurableTCP 20, 21SFTP 22

� See the Technical Note TivoliNetcool Performance ManagerDataChannel Secure File TransferInstallation in the file tech note -sftp.pdf on the CD.

X X LOG UDP Static,configurableUDP 25000

� DC configuration:GLOBAL.LOG_PORT

X X CNS foracquiring thename service

Static,configurableTCP 45107

� DC configuration:GLOBAL.ORB_NAMESERVICE_PORT

X X Channel NameService ORB

Static,configurableTCP 9005

� DC configuration:CNS.CORBA_PORT

X X ChannelManager ORB

Static,configurableTCP 9001

� DC configuration:CMGR.CORBA_PORT

X X ApplicationManager ORB

Static,configurableTCP 9002

� DC configuration:AMGR.<hostname>. CORBA_PORT(AMGR.<hostname> is a property istaken from the location chosen forthe Disk Usage Server host.)

X X Trapd service Static,configurableTCP 162

� DC configuration:CME.x.y.TRAPD_PORT

X X SNMPDataLoad -DataMart

AutomaticDiscovery

Static,configurableTCP 3002

� On each SNMP Collector:PVM_SNMP_COLL_ SSDPORT=3002PVM_SSDPORT=3002 (These areentered using SERVICE_PORT in theTopology Editor: DataChannel >Admin Components > ChannelManager and DataChannel > AdminComponents > CORBA NamingServer Host)

X X TCP forconfigurationreload trigger

Static,configurableTCP 3002

X X Bulk DataLoad-DataMart

FTP inventoryOr SFTP

Static,non-configurableTCP 20, 21SFTP 22

� � See the Technical Note TivoliNetcool Performance ManagerDataChannel Secure File TransferInstallation in the file tech note -sftp.pdf on the CD.

X X TCP forconfigurationreload trigger

Static,configurableTCP 3002

� DC configuration:BCOL.x.x.3002_SERVICE_PORT

Chapter 3. Architecture information 47

Dev DL DC DM DB DV WEB FM Module/ Pair ProtocolPort Type /

Port # Dir. Property Setting in Topology Editor

X X SNMPDataLoad -database

NET 8 reloads Static,configurableTCP 1521

� listener.ora on Oracle server:

LISTENER =(DESCRIPTION_LIST=(DESCRIPTION =(ADDRESS =(PROTOCOL =IPC)(KEY =EXTPROC)))(DESCRIPTION =(ADDRESS =(PROTOCOL =TCP)(HOST =pl2dbs1)(PORT = 1521))))tnsnames.ora on Oracleserver and all clients:PV =(DESCRIPTION =(ADDRESS_LIST =(ADDRESS =(PROTOCOL =TCP)(HOST =pl2dbs1)(PORT = 1521)))(CONNECT_DATA =(SERVICE_NAME =PV.world)))

X X Bulk DataLoad- database

NET 8 reloads Static,configurableTCP 1521

X X DataChannel -database

NET 8 reloads Static,configurableTCP 1521

X X Database -DataView

NET 8 forqueries

Static,configurableTCP 1521

X X Channel NameService ORB

Static,ConfigurableTCP 9005

� DC configuration:CNS.CORBA_PORT

X X ChannelManager ORBfor NearReal-Time andReal Timeaccess.

Static,configurableTCP 9001

� DC configuration:CMGR.CORBA_PORT

The following sections describe additional device-specific protocol mappings,including:v “Alcatel 5620 NM mappings”v “Alcatel-Lucent 5620 SAM mappings” on page 49v “Cisco CWM mappings” on page 49v “Nortel CS2000 mappings” on page 49v “Radcom Probe” on page 50

Alcatel 5620 NM mappings:

Alcatel 5620 NM Mappings.

The following table lists the module-to-protocol mappings for integrating with theAlcatel 5620 NM.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 46, if a firewall sits betweenTivoli Netcool Performance Manager and the Alcatel 5620 NM servers.

Module-to-Protocol Mappings for Integrating with Alcatel 5620 NM

5620 NM DL DC DM DB DV WEB Module Pair Protocol Port Type /Port #

Direction

X X 5620 -DataLoadQCIF

CORBAconnection to5620 NMevent bus

Static,configurable8248

48 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

X X 5620 -DataLoadBulk LoadBalancer(BLB)

FTP and FTPData forbinarytransferduringremoteinstallation

Static, non-configurableTCP 20, 21

Alcatel-Lucent 5620 SAM mappings:

Alcatel-Lucent 5620 SAM Mappings.

The following table lists the module to protocol mappings for integrating with theAlcatel-Lucent 5620 SAM.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 46, if a firewall sits betweenTivoli Netcool Performance Manager and the Alcatel-Lucent 5620 SAM servers.

Module-to-Protocol Mappings for Integrating with Alcatel-Lucent 5620 SAM

5620 SAM DL DC DM DB DV WEB Module Pair Protocol Port Type /Port #

Direction

X X 5620 -DataLoadSAMIF

SOAP/XMLJMS

Static,configurable8080 Staticconfigurable1099

� �

X X 5620 -DataLoadBulk LoadBalancer(BLB)

FTP and FTPData forbinarytransferduringremoteinstallation

Static, non-configurableTCP 20, 21

Cisco CWM mappings:

Cisco CWM Mappings.

The following table lists the module-to-protocol mappings for integrating with theCisco CWM.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 46, if a firewall sits betweenTivoli Netcool Performance Manager and the Cisco CWM servers.

Module-to-Protocol Mappings for Integrating with the Cisco CWM

CWM DL DC DM DB DV WEB Module Pair Protocol Port Type /Port #

Direction

X X CWM -DataLoadBulk

Issue GETsand SETs tothe CWMReceiveInventoryevent TRAPs

Static UDP161 StaticUDP 162

� �

X X CWM -DataLoadBulk

Connectionto Informixfor gettingdata files

Static,configurableTCP 8000

Nortel CS2000 mappings:

Nortel CS2000 Mappings.

Chapter 3. Architecture information 49

The following table lists module-to-protocol mappings for integrating with theNortel CS2000.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 46, if a firewall sits betweenTivoli Netcool Performance Manager and the Nortel CS2000 servers.

Module-to-Protocol Mappings for Integrating with the Nortel CS2000

CS2K DL DC DM DB DV WEB Module Pair Protocol Port Type /Port #

Direction

X X CS2K -DataLoadBulk

FTP transferbetweenDataLoadand NortelEMS.

Static,configurableTCP 8000

Radcom Probe:

Radcom Probe.

The following table lists the module-to-protocol mappings for integrating with theRadcom Probe.

Note: These ports are to be configured in addition to the ones described in“Standard Deployment of DataChannel” on page 46, if a firewall sits betweenTivoli Netcool Performance Manager and the Radcom Probe servers.

Module-to-Protocol Mappings for Integrating with the Radcom Probe

RadcomProbe

DL DC DM DB DV WEB Module Pair Protocol Port Type / Port # Direction

X X Radcom Probe -DataLoad Bulk

Bulk SQL betweenDataLoad andRadcom QManagerOracle DB.

Oracle SQL*Netdefault TCP 1521

DataChannel "Remote Channel Option"Additional ports to open for the DataChannel "Remote Channel Option."

This section describes the additional ports to open for the DataChannel "RemoteChannel Option."

DataChannel "Remote Channel Option" Deployment

The following table lists the module to protocol for the DataChannel remoteoption. For more information, see “SNMP version support,” on page 53.

50 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Module to Protocol Mappings for DataChannel Remote Option (Outside Firewall)

Dev DCR DCL DM DB DV WEB FM Module Pair Protocol Port Type /Port #

Direction Config Setting

X X DC Remote(DCR) - DCLoader (DCL)

FTP metriccollection OrSFTP

Static, NonConfigurableTCP 20, 21SFTP 22

� � See document "Tivoli NetcoolPerformance Manager DataChannelSecure File Transfer Installation-Technical Note " in file "tech note -sftp.pdf" from the CD

X X LOG UDP Static,ConfigurableUDP 25000

� DC config GLOBAL.LOG_PORT

X X CNS foracquiring thename service

Static,ConfigurableTCP 45107

� DC config:GLOBAL.ORB_NAMESERVICE_PORT

X X Channel NameService ORB

Static,ConfigurableTCP 9005

� DC config: CNS.CORBA_PORT

X X ChannelManager ORB

Static,ConfigurableTCP 9001

� DC config: CMGR.CORBA_PORT

X X ApplicationManager ORB

Static,ConfigurableTCP 9002

� DC config:AMGR.<hostname>.CORBA_PORT(AMGR.<hostname> is a property istaken from the location chosen forthe Disk Usage Server host.)

X X Trapd service Static,ConfigurableUDP 162

� DC config: CME.x.y.TRAPD_PORT

X X CME ORB forNear RealTime

StaticConfigurationTCP 9006

� DC config: CME.x.y.CORBA_PORT

X X DC Remote(DCR) -database (DB)

NET 8 forqueries

Static,ConfigurableTCP 1521

� listener.ora and tnsnames.ora onOracle server. Port 1521 is supposedto be already configured by standardports settings - see table above.

v DCR represents the Remote server supporting DataLoad and the Sub-Channelcomponent of DataChannel.

v DCL represents the other modules of the DataChannel (Loader), deployedLocally.

v Fault Management external station - This is not a Tivoli Netcool PerformanceManager module.

v There is no default line created in the configuration file by the installer, but willbe leveraged if configured.

SNMP inventoryThis section highlights the various protocol exchanged between Tivoli NetcoolPerformance Manager components. It can be used to figure out the relevantfirewall configuration depending on where the various components reside (SNMPDiscovery process, DataChannel).

As described previously, in most cases the SNMP Discovery process is deployed onthe DataMart server and does not require you to open specific ports throughfirewalls. In very specific cases, the SNMP Discovery process needs to be deployedremotely, and requires you to open additional firewall ports.

“SNMP inventory” shows the protocols through firewalls deployment.

The following figure shows the most common deployment for Protocols ThroughFirewalls - Central SNMP Discovery Process.

Chapter 3. Architecture information 51

In Module-to-Protocol Mappings for the Tivoli Netcool Performance Manager SNMPDiscovery Process:v DISC is the SNMP Discovery process, deployed on the DataLoad server.v FM represents the Fault Management external station. This is not a Tivoli

Netcool Performance Manager module.

Module-to-Protocol Mappings for the Tivoli Netcool Performance Manager SNMPDiscovery Process

Dev DL DC DISC DM DB DV WEB FM Module Pair Protocol Port Type /Port #

Dir. Property Setting in Topology Editor

X X Discoveryserver -database

NET 8reloads

Static,configurableTCP 1521

� Listener.ora on server side,tnsnames.ora on client side.

X X SNMPDataLoad -Discoveryserver

Disc server,fordiscoveryformulaexecutions

Static,non-configurableTCP 3002

X X DataChannel(CME notinvolved) -Discoveryserver

LOG UDP Static,configurableUDP 25000

� DC configuration: GLOBAL.LOG_PORT

X X CNS foracquiringthe nameservice

Static,configurableTCP 45107

� DC configuration:GLOBAL.ORB_NAMESERVICE_PORT

X X Disc server'sAMGRtalking totheDataChannel

ChannelNameService ORB

Static,configurableTCP 9005

� DC configuration: CNS.CORBA_PORT

X X ChannelManagerORB

Static,configurableTCP 9001

� DC configuration:CMGR.CORBA_PORT

X X ApplicationManagerORB

Static,configurableTCP 9002

� DC configuration: AMGR.<hostname>. CORBA_PORT

X X Discoveryserver -DataMartinventory

Discoveryserver ORB

Dynamic,configurable

� DC configuration: DISC.<hostname>.1. CORBA_PORT (isinherited from the DataMart hostCORBA_PORT property.)

X X DataChannel(CME notinvolved) -DataMartinventory

CNS foracquiringthe nameservice

Static,configurableTCP 45107

� DC configuration:GLOBAL.ORB_NAMESERVICE_PORT

Note: For most deployments, where the Discovery server is on the central site,these ports do not have to be opened, except the one described in the second rowof

“SNMP inventory” on page 51

(if DataLoad is behind the firewall).

See Professional Services for more information.

52 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Appendix. SNMP version support

Tivoli Netcool Performance Manager can automatically detect the SNMP versionsupported by each element on the network, between SNMP Versions 1, 2c, and 3.

Tivoli Netcool Performance Manager supports the following PDU sets for thefollowing SNMP versions:v SNMP Version 1 - Get/GetNext/Setv SNMP Version 2c - Get/GetNext/GetBulk/Setv SNMP Version 3 - Get / GetNext / GetBulk / Set, only MD5 authentication (no

SHA-1 authentication, no DES encryption)

© Copyright IBM Corp. 2006, 2014 53

54 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law :

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

© Copyright IBM Corp. 2006, 2014 55

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment to

56 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Notices 57

Java and all Java-based trademarks and logos are trademarks orregistered trademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

58 IBM Tivoli Netcool Performance Manager: Configuration Recommendations Guide

����

Printed in USA


Recommended