IBM Tivoli Netcool/OMNIbus Probe for Tandem SCP: … · Guide IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide ... the device automatically sends events to ... alarms. IBM Tivoli

IBM® Tivoli® Netcool/OMNIbus Probe for Tandem SCPVersion 4.0

Reference GuideJanuary 20, 2012

SC23-6384-03

��

IBM® Tivoli® Netcool/OMNIbus Probe for Tandem SCPVersion 4.0

Reference GuideJanuary 20, 2012

SC23-6384-03

��

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

Edition notice

This edition (SC23-6384-03) applies to version 4.0 of the IBM Tivoli Netcool/OMNIbus Probe for Tandem SCP andto all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC23-6384-02.

© Copyright IBM Corporation 2007, 2012.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 . . . . . . . . v

IBM Tivoli Netcool/OMNIbus Probe forTandem SCP. . . . . . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Configuring the hosts file . . . . . . . . . . 3Data acquisition . . . . . . . . . . . . . 3

Data stream capture . . . . . . . . . . . 4Logging invalid alarms . . . . . . . . . . 4

Read timeout . . . . . . . . . . . . . 4Inactivity . . . . . . . . . . . . . . 5Peer-to-peer failover functionality . . . . . . 5

Properties and command line options . . . . . . 5Elements. . . . . . . . . . . . . . . . 8Error messages . . . . . . . . . . . . . 9ProbeWatch messages . . . . . . . . . . . 12Running the probe . . . . . . . . . . . . 13

Appendix. Notices and Trademarks . . 15Notices . . . . . . . . . . . . . . . . 15Trademarks . . . . . . . . . . . . . . 17

© Copyright IBM Corp. 2007, 2012 iii

iv IBM Tivoli Netcool/OMNIbus Probe for Tandem SCP: 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 Tandem SCP documentation isprovided in softcopy format only. To obtain the most recent version, visit the IBM®

Tivoli® Information Center:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.namomnibus.doc/welcome_ptsm.htm

Table 1. Document modification history

Documentversion

Publicationdate

Comments

SC23-6384-00 March 21,2007

First IBM publication.

SC23-6384-01 December 31,2008

Summary table updated.

IPv6 support information added.FIPS information added.

Installation section added.

SC23-6384-02 March 31,2011

Installation section replaced by “Installing probes” onpage 2.

SC23-6384-03 January 20,2012

Information about operating system conventions addedin “Conventions used in this guide.”

Multicultural support information updated in“Summary” on page 1.

Descriptions of $SYSNAME and $SUBSYSNAME elementsupdated in “Elements” on page 8.

Information about running the probe added in “Runningthe probe” on page 13.

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:

© Copyright IBM Corp. 2007, 2012 v



$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 systemcurrently supported by Netcool/OMNIbus.

Table 2. Directory names for the arch variable

Operating system Directory name represented by arch

AIX® systems aix5

HP-UX PA-RISC-based systems hpux11

HP-UX Integrity-based systems hpux11hpia

Red Hat Linux and SUSE systems linux2x86

Linux for System z® linux2s390

Solaris systems solaris2

Windows systems win32

vi IBM Tivoli Netcool/OMNIbus Probe for Tandem SCP: Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for Tandem SCP

The Probe for Tandem SCP connects to Tandem SCP devices over TCP/IP andreceives alarms in the form of an ASCII data feed.

This guide contains the following sections:v “Summary”v “Installing probes” on page 2v “Configuring the hosts file” on page 3v “Data acquisition” on page 3v “Properties and command line options” on page 5v “Elements” on page 8v “Error messages” on page 9v “ProbeWatch messages” on page 12v “Running the probe” on page 13

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 Tandem SCP.

Table 3. Summary

Probe target Tandem SCP device

Probe executable name nco_p_tandem_scp

Probe installation package omnibus-arch-probe-nco-p-tandem-scp-version

Package version 4.0

Probe supported on For details of supported operating systems, see thefollowing Release Notice on the IBM Software Supportwebsite:

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

Note: The probe is supported on HP-UX PA-RISC 11.11.It is not supported on HP-UX PA-RISC 11.0.

Properties file $OMNIHOME/probes/arch/tandem_scp.props

Rules file $OMNIHOME/probes/arch/tandem_scp.rules

Additional files $OMNIHOME/probes/arch/tandem_scp.hosts

Requirements A currently supported version of IBM TivoliNetcool/OMNIbus.

Connection method TCP/IP

Remote connectivity Yes

© Copyright IBM Corp. 2007, 2012 1



Table 3. Summary (continued)

Licensing Electronic licensing was deprecated with the release ofIBM Tivoli Netcool V7.2.0. All IBM Tivoli Netcool V7.2.0(and later) products use the IBM software licensingprocess.

Note: The probe requires one license for each host towhich it connects.

Multicultural support Available

For information about configuring multiculturalsupport, including language options, see the IBM TivoliNetcool/OMNIbus Installation and Deployment Guide(SC14-7604-00).

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

Federal Information ProcessingStandards (FIPS)

IBM Tivoli Netcool/OMNIbus V7.2.1, 7.3.0 and 7.3.1 usethe FIPS 140-2 approved cryptographic provider: IBMCrypto for C (ICC) certificate 384 for cryptography. Thiscertificate is listed on the NIST website athttp://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htm For details about configuringNetcool/OMNIbus for FIPS 140-2 mode, see IBM TivoliNetcool/OMNIbus Installation and Deployment Guide(SC14-7604).

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 TivoliInformation Center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/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 Information Center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_install_intro.html

3. Configuring the probe.

2 IBM Tivoli Netcool/OMNIbus Probe for Tandem SCP: Reference Guide

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

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

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.html



http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/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 IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).

Configuring the hosts fileThe probe can connect to multiple Tandem SCP devices. You must configure theconnection details for each device's host machine in the tandem_scp.hosts filesupplied with the probe.

When the probe starts up, it first checks the HostsFile property for the presence ofa hosts file. If you have not specified a hosts file, the probe then checks the Hostand Port properties for the host name and port details of a single Tandem SCPhost. If you have specified values for all three properties, the probe will use thedetails in the hosts file.

The format of a host entry in the hosts file is as follows:

host port : chi cho ft ia ri ra af ;

Each entry must end with a semicolon (;). Individual elements of an entry areseparated by one of the following white space characters: space (sp), tab (tab),carriage return (cr), or newline (nl). Blank lines are ignored.

The following table describes the available elements for a host entry.

Table 4. Hosts file elements

element Description

host This element specifies the host to which the probe connects.

port This element specifies the port to which the probe connects.

chi This element specifies the chatin string.

cho This element specifies the chatout string.

ft This element specifies the flush time value.

ia This element specifies the inactivity time.

ri This element specifies the reconnection interval.

ra This element specifies the number of reconnection attempts.

af This element specifies the active flag. You must set this element toTrue. Setting this to False deactivates the connection.

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 connects to Tandem SCP devices using a TCP/IP connection. When theconnection is made, the device automatically sends events to the probe.

IBM Tivoli Netcool/OMNIbus Probe for Tandem SCP 3

When the connection to the device is successful, the probe sends the ProbeWatchmessage specified by the Conn_Up property to the ObjectServer. If the connectionfails, the probe sends the ProbeWatch message specified by the Conn_Downproperty.

Data acquisition is further described in the following topics:v “Data stream capture”v “Logging invalid alarms”v “Read timeout”v “Inactivity” on page 5v “Peer-to-peer failover functionality” on page 5

Data stream captureThe probe can log the raw data stream sent from a device to a data stream capturefile. The raw data can be used for debugging purposes, to develop new featuresfor the probe, or to pass to other management systems that require the same data.

To enable data stream capture, use the StreamCaptureFile property to specify a filein which to store the data.

You can use the DateStreamCapture property to specify whether the probeappends the current date and time to the name of the data stream capture file.

Use the MaxStreamCapFileSize property to specify the maximum size (in bytes) ofthe data stream capture file.

The data stream capture function can generate large log files. To conserve diskspace, disable this function when you no longer require the data.

Logging invalid alarmsThe probe can log invalid alarms to a log file for later examination.

Use the InvalidAlarmLogging property to specify whether the probe logs invalidalarms. Specify a value of 1 to enable logging. The default is 0, which disableslogging.

Use the InvalidAlarmLogFile property to specify the name and location of theinvalid alarm log file and the MaxInvalidAlarmLogFileSize property to specify themaximum size of the log file in bytes. When the maximum log file size is reached,the probe creates a new file and appends the current date and time to the filename.

The probe flushes an event to the ObjectServer after five seconds, as specified bythe default value of the FlushTime property. If an event is flushed while it is beingparsed by the probe, the buffer is discarded and the incomplete alarm is logged asinvalid. If too many events are being flushed before completion, you might need toincrease the flush time interval.

Read timeoutUse the ReadTimeout property to specify the length of time for which the probetries to read an alarm before timing out.


The probe tries to read each alarm for the length of time specified by theReadTimeout property. The default is 100 seconds. If no data is received withinthis time, the probe moves on to the next alarm.

InactivityThe probe has a timeout facility that allows it to disconnect from the socket if itfails to receive the next alarm data within a predefined amount of time. To specifyhow long the probe waits before disconnecting, use the Inactivity property. Afterthis length of time, the probe disconnects from the switch, sends a ProbeWatchmessage to the ObjectServer, and tries to reconnect.

You can also use the InactivityRetry property to specify the number of consecutiveinactivity intervals that the probe allows before disconnecting. If this property isset to 0, the probe disconnects after a single period of inactivity.

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 shuts down, the slave probe stopsreceiving heartbeats from the master and any events it receives thereafter areforwarded to the ObjectServer on behalf of the master probe. When the master isrunning again, the slave continues to receive events, but no longer sends them tothe ObjectServer.

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.

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 : 5555 # [communication port between master and slave probe]Mode : "master"

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 : 5555 # [communication port between master and slave probe]Mode : "slave"

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 tothis probe. For more information about generic Netcool/OMNIbus properties andcommand line options, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide(SC14-7608).

Table 5. Properties and command line options

Property name Command line option Description

Conn_Down string -conndown string Use this property to specify theProbeWatch message that theprobe sends to the ObjectServerwhen the connection to theTandem SCP device is lost.

The default is Connection down.

Conn_Up string -connup string Use this property to specify theProbeWatch message that theprobe sends to the ObjectServer toindicate a successful connection tothe Tandem SCP device.

The default is Connectionestablished.

DateStreamCaptureinteger

-datestreamcapture integer Use this property to specifywhether the probe appends thecurrent date and time to the nameof the data stream capture file.This property takes the followingvalues:

0: The probe does not append thedate and time to the file name.

1: The probe appends the date andtime to the file name.

The default is 0.

Note: Setting theDateStreamCapture property to 1prevents the data stream capturefile from being overwritten.

FlushTime integer -flushtime integer Use this property to specify thetime (in seconds) that the probewaits before flushing an event tothe ObjectServer.

The default is 5.

Host string -host string Use this property to specify thename of the host to which theprobe connects.

The default is localhost.

HostsFile string -hostsfile string Use this property to specify thelocation of the hosts file.

The default is "".


Table 5. Properties and command line options (continued)


Inactivity integer -inactivity integer Use this property to specify thetime (in seconds) that the probeallows a port to be inactive beforedisconnecting.

The default is 0.

InactivityRetry integer -inactivityretry integer Use this property to specify thenumber of consecutive periods ofinactivity that the probe allowsbefore attempting to reconnect tothe host.

The default is 0 (which disablesthis feature).

InvalidAlarmLogFilestring

-invalidlog string Use this property to specify thefile to which the probe logsinvalid alarms. The current dateand time is appended to the filename.

The default is $OMNIHOME/var/tandem_scp.invalid.

InvalidAlarmLogginginteger

-invalidlogging integer Use this property to specifywhether the probe logs invalidalarms. This property takes thefollowing values:

0: The probe does not log invalidalarms.

1: The probe logs invalid alarms.

The default is 0.

MaxEvents integer -maxevents integer Use this property to specify themaximum number of events thatthe probe attempts to readsimultaneously from a device.

The default is 1.

Note: When a large number ofevents is being generated by thedevice, you can increase thisnumber to increase eventthroughput.

MaxInvalidAlarmLogFileSize integer

-maxinvalidlog integer Use this property to specify themaximum size (in bytes) of theinvalid alarm log file. When thislimit is reached, the probe createsa new file and appends thecurrent date and time to the filename.

The default is 1048576.


Table 5. Properties and command line options (continued)


MaxStreamCapFileSizeinteger

-maxstreamcapfilesizeinteger

Use this property to specify themaximum size (in bytes) of thedata stream capture file. Whenthis limit is reached, the probecreates a new file.

The default is 0.

Note: If the probe reads a streamwhose size exceeds the remainingspace in the file, it creates a newfile in which to store the data.

Port integer -port integer Use this property to specify theport to which the probe connects.

The default is 23.

ReadTimeout integer -readtimeout integer Use this property to specify thetime (in seconds) for which theprobe tries to read an alarm beforetiming out.

The default is 100.

ReconnectionAttemptsinteger

-reconnectionattemptsinteger

Use this property to specify themaximum number of times thatthe probe attempts to reconnect tothe device.

The default is 0 (the probecontinuously attempts toreconnect).

ReconnectionIntervalinteger

-reconnectionintervalinteger

Use this property to specify thetime interval (in seconds) betweensuccessive reconnection attempts.

The default is 0.

StreamCaptureFile string -streamcapturefile string Use this property to specify thefile the probes uses to store theinput stream log.

The default is "".

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.

The following table describes the elements that the probe generates. Not all theelements described are generated for each event. The elements that the probegenerates depend on the event type.


Table 6. Elements

Element name Element description

$Alarm_Id This element contains the unique identifier of thealarm.

$Date This element contains date of the event in theformat yy-mm-dd.

$HeaderText This element contains the header text of theevent.

$linen This element contains a single line of the eventmessage, where n is the line number.

$NumOfLines This element contains the total number of lines inthe event message.

$SUBSYSNAME This element contains the subsystem identifier.

For example: TANDEM.TN32SERV.D40.

$SYSNAME This element contains the name of the systemgenerating the alarm.

For example: \INDY.$C10.

$Time This element contains the time at which the eventoccurred.

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 Netcool/OMNIbus error messages, see the IBM TivoliNetcool/OMNIbus Probe and Gateway Guide (SC14-7604).

Table 7. Error messages

Error Description Action

Buffer size exceeded.Registering read error.Discarding line:linenumber

The event read by the probeis larger than the value of theMaxEvents property. Thiscaused the probe to discardthe specified line.

Make more memory available.

ConvertEscapes: Errorallocating memory foroctal code

The probe was unable toallocate memory for thebuffer that contains the eventbeing read. This caused theprobe to stop.


CreateAndSet failed forhost

The probe is unable to createan element.

Refer to your support contractfor details about contactingIBM Support.

Discarding invalid databetween alarms

Discarding line:linenumber

A line from the alert audit fileis not in the correct format.

Check that the probe isrunning correctly.


Table 7. Error messages (continued)


Disconnect fromObjectServer failed:hostname

The probe failed to disconnectproperly from theObjectServer.

Check that the ObjectServer isrunning correctly.

Error initialisinginternal probe list

Error initialising list

This is an internal probe error. Rerun the probe. If that doesnot solve the problem, refer toyour support contract fordetails about contacting IBMSupport.

Error reading host filehostfilename

The probe could not open thehosts file for reading.

Check the permissions for thehosts file and directories, andamend if necessary.

Expect timed out afternumber seconds

The probe was unable toconnect to the remote host.

Check the remote host isavailable.

Expect: Error allocatingmemory for buffer

Unable to allocate memory forthe buffer that contains theevent being read. This causedthe probe to terminate.


Failed to allocate memory The probe failed to allocateinternal storage.


Failed to compile regularexpression

A regular expression isincorrectly formed in the rulesfile.

Check the rules file for theregular expression and correctthe entry.

Failed to create and set:$Host-> element

The probe is unable to createan element for the host.


Failed to create and set:$Port-> element

The probe is unable to createan element for the port.


Failed to disconnect fromhost: hostname port

The probe failed to disconnectproperly from the device.

Check that the device and theObjectServer are runningcorrectly.

Failed to parse firstline of event

The probe failed to parse theincoming data. The incomingdata may be corrupt.

Check that the device isrunning properly.

Failed to parse textblock

The probe was unable toparse the data specified.

This is an internal error. Referto your support contract fordetails of contacting IBMSupport.

Failed to read fromsocket - disconnecting

The probe had successfullylogged into the target host,but something interrupted theconnection.

Check that the target host isworking correctly.

Failed to retrieve valuefor property propertyname

The probe failed to retrieve avalue for a required property.

Check that the properties filecontains the required propertyand that it has been specifiedin the appropriate format.

Failed to rolloverInvalidAlarmLogFile

The probe was unable to openanother alarm log file to writeto.

Check that there is sufficientdisk space and that thepermissions are correct.




Failed to send alert

Failed to send commandstring

The probe was unable to sendan alert to the ObjectServer.

Check that the ObjectServer isavailable.

Failed to send messageProbeWatch message

Failed to send ProbeWatchmessage: message

The probe was unable to sendthe specified ProbeWatchmessage to the ObjectServer.


Failed to send string The probe failed to send themessage specified to thedevice.

Check that the connection tothe host is still active.

Feature has expired:featurename

The license for the featurespecified has expired.

Update the license for thefeature using the NetcoolLicense Server.

File error: filename notfound

File error: ReadHostFile

File error:ReReadHostFile

filename: file not found

The probe could not find thefile specified.

Check that the host file existsand that the permissions arecorrect.

First line is invalid(not enough tokens):invalid_line

First line from the alert auditfile is not in the correctformat.

Check that the probe isrunning correctly.

Have lost all connections- going down

The probe has lost itsconnection to the socket andis stopping.

Check that the device isrunning correctly.

Hostfile entry is notvalid: linenumber

A line in the hosts file wasformatted incorrectly.

Check the hosts file.

Invalid port number forhost: port

The port number specifieddoes not exist on the host.

Check the value specified forPort in the properties file.

License heartbeat failed The probe could not processthe response from the hostduring an expect. This couldbe caused by a problem withthe target which caused theconnection to time out, or theresponse from the targetcould have been corrupted.

If the probe is configured toreconnect, it will try again toestablish the connection.

Only managed to writenumber out of numbercharacters

The probe was unable towrite to the alarm log file.

Check that there is sufficientdisk space and that thepermissions are correct.

OplPropGetValue() failed:propertyname

The probe failed to retrieve avalue for a required property.

Check that the properties filecontains the required propertyand that it has been specifiedin the appropriate format.

Read error during expect The probe could not processthe response from the host.

Check that the device isrunning currently.




SendCommand: Errorallocating memory forcommand

Unable to allocate memory forbuffer that contains the eventbeing read. This caused theprobe to terminate.


SessionProcess failedinternal error code

The probe was unable toprocess the alert against therules file.


Too many tokens inhostfile entry

A line in the hosts file wasformatted incorrectly. Thereare too many entries on theline.

Check the hosts file.

Unable to compile regexpfor string

A regular expression isincorrectly formed in the rulesfile.

Check the rules file for theregular expression and correctthe entry.

Unable to extract $MSNfrom event

Extract() is unable to extract$MSN element from the alarmdata.

Check the rules file andcorrect the problem.

Unable to get events The probe was unable to getany events from the system.

Check that the system isrunning correctly.

Unable to open file:filename - filename

The probe could not open thefile specified.

Check that the permissionsare set correctly on the filespecified.

Unable to sendHeartbeatString

The probe could not send aheartbeat string to the device.

Check that the connection tothe host is still active.

Unable to write to filefilename

The probe could not write tothe file specified.

Check the permissions on thefile specified.

Unknown system error! An unknown error occurredwhile the probe was receivingthe data.


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 ProbeWatch error messages that the probegenerates. For information about generic Netcool/OMNIbus ProbeWatch messages,see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).

Table 8. ProbeWatch messages

ProbeWatch message Description Triggers/causes

Discarding owing totimeout prior toheaderline

The probe is discarding theevent without reading theheader line.

The probe has exceeded thetime specified by theReadTimeout property toread the event.

Disconnected from systemdue to shutdown signal

The probe has disconnectedfrom the host.

A shutdown signal was sentto the probe.


Table 8. ProbeWatch messages (continued)

ProbeWatch message Description Triggers/causes

Failed to get events A problem occurred whilereceiving events.

Either there was a probleminitializing the connection dueto insufficient memory or (ifthis message was sent aftersome events had been parsed)there was a license or aconnection failure.

Failed to send ProbeWatchmessage: message

The probe was unable to sendthe alert, command, orProbeWatch message specifiedto the ObjectServer.


Flushtime exceeded whilebuffering event, flushingevent

The probe has flushed theevent to the ObjectServerbefore the event is completelyread into the buffer.

The probe has exceeded thetime specified by theFlushTime property.

Going Down The probe is shutting down. The probe is shutting downafter performing theshutdown routine.

Have lost all connections- going down

The probe is shutting downbecause all of its connectionshave been deactivated.

The number of times that theprobe has attempted toreconnect to the device hasexceeded the numberspecified by theReconnectionAttemptsproperty for each connection.

License failure - goingdown

The license server could notbe reached.

Either the license has expired,the license server has gonedown, or the connection tothe license server has beenlost.

Running The probe is runningnormally.

The probe has just beenstarted.

Running the probeBefore running the probe for the first time, you must specify a minimum set ofproperties.

If you want to use the probe with a single Tandem SCP device, you must specifythe host name and port of the device using the Host and Port properties.

If you want to use the probe with multiple Tandem SCP devices, you must specifythe location of a hosts file using the HostsFile property.

To start the probe, use the following command:

$OMNIHOME/probes/nco_p_tandem_scp



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. 2007, 2012 15

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 want 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 17


��

Printed in USA

SC23-6384-03

Documents

IBM Tivoli Netcool/OMNIbus Probe for Tandem SCP: … · Guide IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide ... the device automatically sends events to ... alarms. IBM Tivoli