IBM Tivoli Netcool/OMNIbus Probe for HP OpenView … Probe for HP OpenView NNM 7 ... 2017 iii. iv IBM T ivoli ... IBM T ivoli Netcool/OMNIbus Probe for HP OpenV iew NNM 7

IBM® Tivoli® Netcool/OMNIbus Probe for HP OpenViewNNM 7Version 7.0

Reference GuideJuly 20, 2017

SC23-9111-05

IBM

IBM® Tivoli® Netcool/OMNIbus Probe for HP OpenViewNNM 7Version 7.0

Reference GuideJuly 20, 2017

SC23-9111-05

IBM

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

Edition notice

This edition (SC23-9111-05) applies to version 7.0 of IBM Tivoli Netcool/OMNIbus Probe for HP OpenView NNM 7and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC23-9111-04.

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

Contents

About this guide . . . . . . . . . . . vDocument control page . . . . . . . . . . . vConventions used in this guide . . . . . . . . vi

IBM Tivoli Netcool/OMNIbus Probe forHP OpenView NNM 7 . . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Configuring the probe . . . . . . . . . . . 3Running the probe . . . . . . . . . . . . 3Data acquisition . . . . . . . . . . . . . 4

Peer-to-peer failover functionality . . . . . . 5

Properties and command line options . . . . . . 6Elements. . . . . . . . . . . . . . . . 9

Static elements. . . . . . . . . . . . . 9Dynamic elements . . . . . . . . . . . 10

Error messages . . . . . . . . . . . . . 11ProbeWatch messages . . . . . . . . . . . 12Known issues. . . . . . . . . . . . . . 12Troubleshooting . . . . . . . . . . . . . 12

Appendix. Notices and Trademarks . . 13Notices . . . . . . . . . . . . . . . . 13Trademarks . . . . . . . . . . . . . . 15

© Copyright IBM Corp. 2006, 2017 iii

iv IBM Tivoli Netcool/OMNIbus Probe for HP OpenView NNM 7: Reference Guide

About this guide

The following sections contain important information about using this guide.

Document control pageUse this information to track changes between versions of this guide.

The IBM Tivoli Netcool/OMNIbus Probe for HP OpenView NNM 7 documentationis provided in softcopy format only. To obtain the most recent version, visit theIBM® Tivoli® Information Center:

http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSSHTQ/omnibus/probes/common/Probes.html

Table 1. Document modification history

Documentversion

Publicationdate

Comments

SC23-9111-01 December 31,2008

First IBM publication.

SC23-9111-02 January 31,2011

Installation section replaced by “Installing probes” onpage 2.

SC23-9111-03 July 15, 2011 The following topics were added:

v “About this guide”

v “Conventions used in this guide” on page vi

The following topics were updated:

v “Configuring the probe” on page 3

v “Data acquisition” on page 4

SC23-9111-04 August 26,2011

“Summary” on page 1 section updated.

“Configuring the probe” on page 3 section updated.

“Troubleshooting” on page 12 section added thedocument.

SC23-9111-05 July 20, 2017 “Known issues” on page 12 section added.

© Copyright IBM Corp. 2006, 2017 v



Conventions used in this guideAll probe guides use standard conventions for operating system-dependentenvironment variables and directory paths.

Operating system-dependent variables and paths

All probe guides use standard conventions for specifying environment variablesand describing directory paths, depending on what operating systems the probe issupported on.

For probes supported on UNIX and Linux operating systems, probe guides use thestandard UNIX conventions such as $variable for environment variables andforward slashes (/) in directory paths. For example:

$OMNIHOME/probes

For probes supported only on Windows operating systems, probe guides use thestandard Windows conventions such as %variable% for environment variables andbackward slashes (\) in directory paths. For example:

%OMNIHOME%\probes

For probes supported on UNIX, Linux, and Windows operating systems, probeguides use the standard UNIX conventions for specifying environment variablesand describing directory paths. When using the Windows command line withthese probes, replace the UNIX conventions used in the guide with Windowsconventions. If you are using the bash shell on a Windows system, you can use theUNIX conventions.

Note: The names of environment variables are not always the same in Windowsand UNIX environments. For example, %TEMP% in Windows environments isequivalent to $TMPDIR in UNIX and Linux environments. Where such variables aredescribed in the guide, both the UNIX and Windows conventions will be used.

Operating system-specific directory names

Where Tivoli Netcool/OMNIbus files are identified as located within an archdirectory under NCHOME or OMNIHOME, arch is a variable that represents youroperating system directory. For example:

$OMNIHOME/probes/arch

The following table lists the directory names used for each operating system.

Note: This probe may not support all of the operating systems specified in thetable.

Table 2. Directory names for the arch variable

Operating system Directory name represented by arch

AIX® systems aix5

HP-UX Integrity-based systems hpux11hpia

vi IBM Tivoli Netcool/OMNIbus Probe for HP OpenView NNM 7: Reference Guide

Table 2. Directory names for the arch variable (continued)

Operating system Directory name represented by arch

Red Hat Linux and SUSE systems linux2x86

Linux for System z linux2s390

Solaris systems solaris2

Windows systems win32

OMNIHOME location

Probes and older versions of Tivoli Netcool/OMNIbus use the OMNIHOMEenvironment variable in many configuration files. Set the value of OMNIHOME asfollows:v On UNIX and Linux, set $OMNIHOME to $NCHOME/omnibus.v On Windows, set %OMNIHOME% to %NCHOME%\omnibus.

About this guide vii

viii IBM Tivoli Netcool/OMNIbus Probe for HP OpenView NNM 7: Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for HP OpenView NNM 7

HP OpenView Network Node Manager is a network management system.Network Node Manager (NNM) discovers network devices and provides a map toillustrate what the network actually looks like. Network Node Manager identifiesthe source of network problems and assists network managers in planning fornetwork growth and designing network changes.

This guide contains the following sections:v “Summary”v “Installing probes” on page 2v “Configuring the probe” on page 3v “Data acquisition” on page 4v “Properties and command line options” on page 6v “Elements” on page 9v “Error messages” on page 11v “ProbeWatch messages” on page 12v “Known issues” on page 12v “Troubleshooting” on page 12

SummaryEach probe works in a different way to acquire event data from its source, andtherefore has specific features, default values, and changeable properties. Use thissummary information to learn about this probe.

The following table provides a summary of the Probe for HP OpenView NNM 7.

Table 3. Summary

Probe target HP OpenView NNM versions 6.x and 7.x

Probe executable name nco_p_nnm6 (for NNM Version 6.x)

nco_p_nnm7 (for NNM Version 7.x)

Package version 7.0

Probe supported on For details of the operating systems on which the probeis supported, see the following Release Notice on theIBM Software Support website:

https://www-304.ibm.com/support/docview.wss?uid=swg21413075Note: If you are running the Probe for HP OpenViewNNM 7 on Red Hat Linux 4.0, you must set theExecCommand property to /opt/OV/bin/ovdumpevents -tl0. The last two characters are a lowercase L and a zero.

Properties file $OMNIHOME/probes/arch/nnm6.props (for NNM Version6.x)

$OMNIHOME/probes/arch/nnm7.props (for NNM Version7.x)

© Copyright IBM Corp. 2006, 2017 1

https://www-304.ibm.com/support/docview.wss?uid=swg21413075

https://www-304.ibm.com/support/docview.wss?uid=swg21413075

Table 3. Summary (continued)

Rules file $OMNIHOME/probes/arch/nnm6.rules (for NNM Version6.x)

$OMNIHOME/probes/arch/nnm7.rules (for NNM Version7.x)

Requirements A currently supported version of IBM TivoliNetcool/OMNIbus.

nonnative-base-2

Connection method API

Remote connectivity The probe can connect to a remote device. Details of theremote device are specified using the NNMhostnameproperty.

Multicultural Support For information about configuring multiculturalsupport, including language options, see the IBM TivoliNetcool/OMNIbus Installation and Deployment Guide.

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

Federal Information ProcessingStandards (FIPS)

IBM Tivoli Netcool/OMNIbus uses the FIPS 140-2approved cryptographic provider: IBM Crypto for C(ICC) certificate 384 for cryptography. This certificate islisted on the NIST website at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htm. For details about configuringNetcool/OMNIbus for FIPS 140-2 mode, see the IBMTivoli Netcool/OMNIbus Installation and Deployment Guide.

Installing probesAll probes are installed in a similar way. The process involves downloading theappropriate installation package for your operating system, installing theappropriate files for the version of Netcool/OMNIbus that you are running, andconfiguring the probe to suit your environment.

The installation process consists of the following steps:1. Downloading the installation package for the probe from the Passport

Advantage Online website.Each probe has a single installation package for each operating systemsupported. For details about how to locate and download the installationpackage for your operating system, visit the following page on the IBM TivoliKnowledge Center:http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html

2. Installing the probe using the installation package.The installation package contains the appropriate files for all supportedversions of Netcool/OMNIbus. For details about how to install the probe torun with your version of Netcool/OMNIbus, visit the following page on theIBM Tivoli Knowledge Center:http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

3. Configuring the probe.

2 IBM Tivoli Netcool/OMNIbus Probe for HP OpenView NNM 7: Reference Guide

http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htm



http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

This guide contains details of the essential configuration required to run thisprobe. It combines topics that are common to all probes and topics that arepeculiar to this probe. For details about additional configuration that iscommon to all probes, see the IBM Tivoli Netcool/OMNIbus Probe and GatewayGuide.

Configuring the probeAfter installing the probe, you need to make various configuration settings to suityour environment.

The Probe for HP OpenView NNM requires that HP Network Node Manager isrunning to generate a real-time stream of events. There are different probes forversions 6.x and 7.x of Network Node Manager. Apart from using differentexecutables, they all operate in the same way.

Environment variables

Before using the Probe for HP OpenView NNM, you must include the followingpath in the $SHLIB_PATH environmental variable (for HP-UX 11) or the$LD_LIBRARY_PATH environmental variable (for Solaris):

/opt/OV/lib

Where /opt/OV is the location of your NNM installation.

The open view export server property also needs to be specified to connect withthe NNM host:

OVServer=<NNMhostname>

Running the probe from a different host

Version 6 and version 7 of the probe can run on a host remote from the systembeing managed. To do this, set the NNMhostname property to the name of the remotehost.

Note: The probe host requires an NNM6 or NNM7 installation, but it need not berunning. The probe and NNM server should be in the same network.

Running the probeProbes can be run in a variety of ways. The way you chose depends on a numberof factors, including your operating system, your environment, and the any highavailability considerations that you may have.

For details about how to run the probe, visit the following page on the IBM TivoliKnowledge Center:

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/concept/running_probe.html

IBM Tivoli Netcool/OMNIbus Probe for HP OpenView NNM 7 3



Data acquisitionEach probe uses a different method to acquire data. Which method the probe usesdepends on the target system from which it receives data.

The Probe for HP OpenView NNM acquires event data by connecting to a runningHP Network Node Manager system and capturing traps to form alerts. The proveacquires events directly from the trapd process and passes them to theObjectServer.

Note: If the trapd process is not running, the probe cannot run.

Connecting to HP OpenView NNM

The probe connects to an instance of the HP Network Node Manager (NNM) trapdprocess running on the host specified by the NNMhostname property. The hostspecified can be remote from the host on which the probe is running.

The probe makes an API connection to the Post Master Daemon (pmd) andsubscribes for information. The information it receives is available as an SNMPProtocol Data Unit (PDU). For details of the information available, see the SNMPDeveloper's Guide available from HP's OpenView website at the following address:

http://ovweb.external.hp.com/ovnsmdps/pdf/j1261-90072.pd

The probe cannot influence the format or the actual values that are sent by pmd.To view the information the probe is receiving, set the OVAPIDebug property to 3.This instructs the probe to send information to stdout.

Restarting the probe

If you need to restart the probe, you must end the native process(nco_p_nonnative) using a hangup signal (kill -HUP command); this ensures thatthe probe re-reads the rules file on startup.

IP status

You can specify that the probe generates an ipStatus element for the traps that itreceives. This element contains the status of the device from which the traporiginated. The value to which the probe sets this element is stored in the HPOpenView database. Possible statuses are:v Criticalv Disabledv Majorv Marginalv Normalv Not foundv Restrictedv Testingv Unknownv Unmanagedv Unsetv Warning


http://ovweb.external.hp.com/ovnsmdps/pdf/j1261-90072.pd

The status of the device can be used by the rules file as a criterion for discardingevents. For details of manipulating events using the rules file, see theNetcool/OMNIbus Administration Guide. To specify that the probe retrieves thestatus of the device and generates ipStatus elements, set the GetIPStatus propertyto 1.

Note: This functionality is only available if the NNM system and the probe areboth running on the same host.

Note: You must manually add the node names to the host file if the NNM serveris on a different network. This is because the IP address must be resolvable to nodename on the probe host, and as the value can be either node name or IP address inthe NNM database it should be specified.

OVsnmpEventOpen function

The OVsnmpEventOpen function sends events from the NNM subsystem to the probe.The events that are sent are determined by the filter parameters that you canspecify using the NNMfilter property. The filter paramater comprises a list ofevents and a list of constraints. The origin of the events sent to the probe isspecified by one of the following event flow types:v RAW - All events received by the event subsystem, excluding those originating

from the ECS engine are sent to the probe.v COR{stream_name} - All events coming from the named event stream are sent to

the probe.v ALL - All events received by the event subsystem, including those originating

from the ECS engine are sent to the probe.

The list of events can be specified using wildcards and/or ranges. For full detailsof the syntax of the OVsnmpEventOpen function, see the SNMP Developer's Guideavailable from HP's OpenView website at the following address:

http://ovweb.external.hp.com/ovnsmdps/pdf/j1261-90072.pdf

Note: The {CORR} filter does not stop events from being sent to the probe if theyhave not been through the correlation engine.

Peer-to-peer failover functionalityThe probe supports failover configurations where two probes run simultaneously.One probe acts as the master probe, sending events to the ObjectServer; the otheracts as the slave probe on standby. If the master probe fails, the slave probeactivates.

While the slave probe receives heartbeats from the master probe, it does notforward events to the ObjectServer. If the master probe shuts down, the slaveprobe stops receiving heartbeats from the master and any events it receivesthereafter are forwarded to the ObjectServer on behalf of the master probe. Whenthe master probe is running again, the slave probe continues to receive events, butno longer sends them to the ObjectServer.


http://ovweb.external.hp.com/ovnsmdps/pdf/j1261-90072.pdf

Example property file settings for peer-to-peer failover

You set the peer-to-peer failover mode in the properties files of the master andslave probes. The settings differ for a master probe and slave probe.

Note: In the examples, make sure to use the full path for the property value. Inother words replace $OMNIHOME with the full path. For example:/opt/IBM/tivoli/netcool.

The following example shows the peer-to-peer settings from the properties file of amaster probe:Server : "NCOMS"RulesFile : "master_rules_file"MessageLog : "master_log_file"PeerHost : "slave_hostname"PeerPort : 6789 # [communication port between master and slave probe]Mode : "master"PidFile : "master_pid_file"

The following example shows the peer-to-peer settings from the properties file ofthe corresponding slave probe:Server : "NCOMS"RulesFile : "slave_rules_file"MessageLog : "slave_log_file"PeerHost : "master_hostname"PeerPort : 6789 # [communication port between master and slave probe]Mode : "slave"PidFile : "slave_pid_file"

Properties and command line optionsYou use properties to specify how the probe interacts with the device. You canoverride the default values by using the properties file or the command lineoptions.

The following table describes the properties and command line options specific tospecifythis probe. For information about default properties and command lineoptions, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, (SC23-6373).

Table 4. Properties and command line options

Property name Command line option Description

GetIpStatus integer -getipstatus integer Use this property to specifywhether the probe generates theipStatus element that contains thestatus of the device that generatedthe trap:

0: The probe does not generateipStatus elements.

1: The probe generates ipStatuselements.

The default is 0.

Note: This function is onlyavailable if the NNM and theprobe are running on the samemachine.


Table 4. Properties and command line options (continued)


Heartbeat integer -heartbeat integer Use this property to specify theinterval (in seconds) at which theprobe sends a ProbeWatchmessage to the ObjectServer.

The default is 60.

Note: Setting this property to 0disables the heartbeatingfunctionality.

Japanese integer -japanese integer Use this property to specifywhether the probe displays Kanjicharacters (Chinese charactersused in the Japanese writing) inraw token format:

0: The probe does not displayKanji characters in raw tokenformat.

1: The probe displays Kanjicharacters in raw token format.

The default is 0.

Note: If Kanji characters areexpected in the data stream, youmust set this property to 1.

NNMfilter string -nnmfilter string Use this property to specify thefilter parameters that are used bythe OVsnmpEventOpen functionto specify which events are sent tothe probe. For details about theOVsnmpEventOpen function, see“OVsnmpEventOpen function” onpage 5.

The default is {RAW}.*..

Note: The {CORR} filter does notstop events from being sent to theprobe if they have not beenthrough the correlation engine.

NNMhostname string -nnmhostname string Use this property to specify thename of the host on which theNNM system is running. This canbe a string or can be expressed indotted quad format.

The default is 127.0.0.1.

Note: This property applies toNNM6 and NNM7 only.


Table 4. Properties and command line options (continued)


NNMInactivityTimeoutinteger

-readtimeout integer Use this property to specify thetime (in seconds) the probe waitsto receive data from the NNMsystem before indicating in the logthat no events have been received,and shutting down.

The default is 0 (the probe nevertimes out).

NoNameResolution integer -nonameresolution(equivalent toNoNameResolution with avalue of 1)

Use this property to specifywhether the probe performs nameresolution on IP addresses:

0: The probe performs nameresolution.

1: The probe does not performname resolution.

The default is 0.

OVAPIDebug integer -ovapidebug integer Use this property to specify thelevel to which the probe sets theOpenView API debug.

The default is 0.

SeqNumFile string -seqnumfile string Use this property to specify thepath to the log file that the probeuses to record the number of timesplus one that it has been started.

The default is$OMNIHOME/var/num_run_seq.

SNMPMode integer -V1

-V2

Use this property to specify theflag that indicates whether theprobe receives traps from thenetwork node manage in V1 orV2c format:

0: The probe receives traps in V1format.

1: The probe receives traps in V2cformat.

The default is 0.


ElementsThe probe breaks event data down into tokens and parses them into elements.Elements are used to assign values to ObjectServer fields; the field values containthe event details in a form that the ObjectServer understands.

This section describes the elements generated by the Probe for HP OpenViewNNM.

Static and dynamic elements are described in the following topics:v “Static elements”v “Dynamic elements” on page 10

Static elementsThe probe generates the same set of static elements for each event it receives.

The following table describes the elements that the Probe for HP OpenView NNM7 generates. Not all the elements described are generated for each event; the staticelements that the probe generates depends upon the event type.

Table 5. Static elements

Element name Element description

$community This element contains the SNMP communitystring.

$enterprise This element contains the SNMP enterprisestring.

$Eventcount This element displays the number of event.

$generic-trap This element contains the SNMP generic trapinteger value. Applies only to traps in V1 format.

$IPAddress This element displays the IP address of thedevice.

$ipStatus This element indicates the management status ofthe device that originated the trap.

Note: The probe only generates the ipStatuselement if the GetIpStatus property is set to 1.

$Node This element identifies the node from which thetrap originated.

Note: If the NoNameResolution property is set to0, the probe resolves the host name and sets the$Node element to this value. If the host name isnot resolvable by the Domain Name Server, theprobe sets the $Node element to the IP address.

$notify This element displays SNMP notify value.Applies only to traps in V2 format.

$Sequence This element indicates the number of times theprobe has been run.

$SNMP_Version This element indicates which version of theSNMP software is monitoring the network.

$Source_Addr This element contains the IP address of the sourcehost.


Table 5. Static elements (continued)

Element name Element description

$specific-trap This element shows the SNMP specific trapinteger value. Applies only to traps in V1 format.

$uptime This element displays the amount of time (in100ths of a second) that the agent sending thetrap has been running.

$UUID This element shows the unique identifier for anECS event.

Dynamic elementsThe dynamic elements that the probe generates are entirely dependent on thedevices monitored.

The other dynamic elements that the probe generates are entirely dependent on thenetwork devices. Each varbind is mapped to elements called $1, $2, $3 and soforth. For each varbind, the object ID is placed in a corresponding element called$OID1, $OID2, $OID3, ...., $OIDn where n is the number of varbind elements present.

The probe also generates elements for each varbind elements named $raw(1),$raw(2), $raw(3) and so forth; these elements are raw string representations (priorto parsing) of the elements $1, $2, $3 and so forth.

Generic trap handling

The following table describes the handling of each generic trap type.

Table 6. Generic trap handling

Generic trap Handling

Generic trap-type 0 - Cold Start Summary field set to Cold Start.

AlertGroup field set to Generic.

Severity field set to 4.

Generic trap-type 1 - Warm Start Summary field set to Warm Start.



Generic trap-type 2 - Link Down Summary field set to Link Down.

AlertKey field set to the $1 varbind (ifIndex).



Identifier field set to Node name plus Agentplus generic-trap plus specific trap plusifIndex.


Table 6. Generic trap handling (continued)

Generic trap Handling

Generic trap-type 3 - Link Up Summary field set to Link Up.

AlertKey field set to the $1 varbind (ifIndex).



Identifier field set to Node name plus Agentplus generic-trap plus specific trap plusifIndex.

Generic trap-type 4 - Authentication By default, Authentication traps are notdiscarded.

Generic trap-type 5 - EGP NeighborLoss

Summary field set to EGP Neighbor Loss.



Error messagesError messages provide information about problems that occur while running theprobe. You can use the information that they contain to resolve such problems.

The following table describes the error messages specific to this probe. Forinformation about generic error messages, see the IBM Tivoli Netcool/OMNIbusProbe and Gateway Guide, (SC23-6373).

Table 7. Error messages

Error Description Action

Could not get thesequence number: Err codenumber

The probe could not retrievethe sequence number and sosets it to 0.

Check that you have specifieda log file using theSeqNumFile property and thatthe permissions on the file areset correctly.

OVerror - Connection totrapd died

The connection to HPOpenView NNM has ended.

This is due to a known limitin HP OpenView. See “Knownissues” on page 12.

OVerror - No response -request timed out

A timeout occurred withoutreceiving a response.

Check that the trapd processis running correctly.

OVerror - Unable toinitialize SNMPov_session - trapdprobably died

The connection to HPOpenView NNM could not beinitiated.

Check the status of the trapdprocess; restart the process ifnecessary.

Warning:NonnativeProtocolCapabilities: Expected 2,got 0

Warning: Upgradenco_p_nonnative:Continuing anyway

The message refers tofunctionality not required orused by this probe.

No action is required.


ProbeWatch messagesDuring normal operations, the probe generates ProbeWatch messages and sendsthem to the ObjectServer. These messages tell the ObjectServer how the probe isrunning.

The following table describes the raw ProbeWatch error messages that the probegenerates. For information about generic ProbeWatch messages, see the IBM TivoliNetcool/OMNIbus Probe and Gateway Guide, (SC23-6373).

Table 8. ProbeWatch messages

ProbeWatch message Description Triggers/causes

Heartbeat Message This is the regular heartbeatmessage that the probe sendsto the ObjectServer.

The probe sends this messageto the ObjectServer with afrequency specified by theHeartbeat property.

Known issuesHP OpenView disconnects from the probe

If HP OpenView disconnects from the probe, you may see the following messagewritten to the probe's error log:

OVerror - connection to trapd died

If so, this is due to a known limit set within HP OpenView.

The Probe for HP OpenView NNM7 connects to the HP OpenView PMD processand subscribes to receive NNM events from the PMD process. HP OpenViewmaintains an internal queue of between 0-8192 events (the actual size of the queueis set by the parameter: qnum). If there is a situation (for example, an event storm)during which the probe cannot receive events at the rate at which the PMD processis attempting to send them, PMD stores these events in the internal queue until theprobe is ready to receive them. When the number of events in the internal queuereaches the maximum set by qnum, HP OpenView disconnects from the probe.

The default value set for qnum is 4096 events. If you find that HP OpenViewdisconnects from the probe, try increasing the value set for qnum to 8192.

TroubleshootingVarious issues arise as users work with the probe. Troubleshooting information isprovided to help you diagnose and resolve such issues.

The probe disconnects when reading large SAF files

This problem occurs when the probe is run as a service on a machine other thanthat on which HP OpenView is installed. If you are running the probe as a service,the probe and HP OpenView must be installed on the same machine.


Appendix. Notices and Trademarks

This appendix contains the following sections:v Noticesv Trademarks

NoticesThis 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 grant youany license to these patents. You can send license inquiries, in writing, to:

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

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

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, 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 orimplied warranties in certain transactions, therefore, this statement may not applyto 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.

© Copyright IBM Corp. 2006, 2017 13

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.

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 CorporationSoftware Interoperability Coordinator, Department 49XA3605 Highway 52 NRochester, MN 55901U.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 information 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 measurements 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 toIBM, 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.

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 softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, ibm.com, AIX, Tivoli, zSeries, and Netcool are trademarks ofInternational Business Machines Corporation in the United States, other countries,or both.

Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-basedtrademarks are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States, other countries, or both.

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporationin the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in theUnited States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

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

Other company, product, or service names may be trademarks or service marks ofothers.

Appendix. Notices and Trademarks 15


IBM®

Printed in USA

SC23-9111-05

Documents

IBM Tivoli Netcool/OMNIbus Probe for HP OpenView … Probe for HP OpenView NNM 7 ... 2017 iii. iv IBM T ivoli ... IBM T ivoli Netcool/OMNIbus Probe for HP OpenV iew NNM 7