tkelg-pdf

Tivoli® Netcool/OMNIbus Probe for Tekelec Eagle STP

Reference GuideDecember 31, 2008

Version 4.0.5903

SC23-7933-01

��

Tivoli® Netcool/OMNIbus Probe for Tekelec Eagle STP

Reference GuideDecember 31, 2008

Version 4.0.5903

SC23-7933-01

��

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

Edition notice

This edition applies to version 4.0.5903 of IBM Tivoli Netcool/OMNIbus Probe for Tekelec Eagle STP (SC23-7933-01)and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC23-7933-00.

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

Contents

Document control page . . . . . . . . v

IBM Tivoli Netcool/OMNIbus Probe forTekelec Eagle STP . . . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing the probe . . . . . . . . . . . . 2Internationalization support . . . . . . . . . 3

Example multi-byte character set on Solaris . . . 3Data acquisition . . . . . . . . . . . . . 3

Chat In and Chat Out Scripts . . . . . . . . 4Backoff Strategy . . . . . . . . . . . . 4Inactivity . . . . . . . . . . . . . . 4Data Stream Capture . . . . . . . . . . 4

Hosts file format . . . . . . . . . . . . 5Peer-to-peer failover functionality . . . . . . 6

Properties and command line options . . . . . . 7Escape Codes. . . . . . . . . . . . . 10

Elements . . . . . . . . . . . . . . . 11Static elements . . . . . . . . . . . . 11Dynamic elements . . . . . . . . . . . 11

Error messages . . . . . . . . . . . . . 12ProbeWatch messages . . . . . . . . . . . 12

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

© Copyright IBM Corp. 2006, 2008 iii

iv IBM Tivoli Netcool/OMNIbus Probe for Tekelec Eagle STP: Reference Guide

Document control page

Use this information to track changes between versions of this guide.

The IBM Tivoli Netcool/OMNIbus Probe for Tekelec Eagle STP 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.nam.doc/welcome_ptsm.htm

Table 1. Document modification history

Documentversion

Publicationdate

Comments

01 December 31,2008

Summary table updated.

IPv6 support information added.

FIPS information added.

Installation section added.

© Copyright IBM Corp. 2006, 2008 v



vi IBM Tivoli Netcool/OMNIbus Probe for Tekelec Eagle STP: Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for Tekelec Eagle STP

The Eagle STP product line is a carrier grade packet switch for Intelligent Networkcontrol configuration. The Probe for Tekelec Eagle STP is a multiheaded probe thatcan be attached to one or more STP devices using a TCP connection to a specific IPaddress and port.

This guide contains the following sections:v “Summary”v “Installing the probe” on page 2v “Data acquisition” on page 3v “Properties and command line options” on page 7v “Elements” on page 11v “Error messages” on page 12v “ProbeWatch messages” 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 Tekelec Eagle STP.

Table 2. Summary

Probe target Eagle STP

Probe executable name nco_p_eagle

Patch number 4.0

Probe supported on Solaris, HP-UX, AIX, and Linux

For details of the operating system versions on whichthis probe is supported, see the following page on theIBM Tivoli Netcool Information Center:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htm

Note: This probe is supported on HP-UX version 11.11,but not version 11.0.

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

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

© Copyright IBM Corp. 2006, 2008 1




Table 2. Summary (continued)

Requirements A currently supported version of IBM TivoliNetcool/OMNIbus

probe-compatibility-3.x (for IBM TivoliNetcool/OMNIbus version 3.6)

common-libnetcool-3_1 (for IBM TivoliNetcool/OMNIbus version 3.6)

common-libOpl-7_6 (for IBM Tivoli Netcool/OMNIbusversion 3.6)

Connection method TCP/IP

Remote connectivity The Probe for Tekelec Eagle STP can connect to a deviceon one or more remote hosts. Use the Host property todefine a single remote host. To connect to multiplehosts, create a file containing details of the remote hostsand identify the file using the HostsFile property.

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

Internationalization AvailableNote: The probe only supports internationalization onIBM Tivoli Netcool/OMNIbus V7.0, 7.1, 7.2, and 7.2.1.

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6Note: The probe is supported on IPv6 when runningon IBM Tivoli Netcool/OMNIbus V7.0, 7.1, 7.2 and 7.2.1on Solaris, and on IBM Tivoli Netcool/OMNIbus V7.2and 7.2.1 on all other UNIX plaftorms.

Federal Information ProtocolStandards (FIPS)

IBM Tivoli Netcool/OMNIbus V7.2.1 uses the FIPS140-2 approved cryptographic provider: IBM Crypto forC (ICC) certificate 384 for cryptography. This certificateis listed on the NIST web site at http://csrc.nist.gov/cryptval/140-1/1401val2004.htm For details aboutconfiguring Netcool/OMNIbus for FIPS 140-2 mode, seeIBM Tivoli Netcool/OMNIbus Installation and DeploymentGuide (SC23-6370).

Installing the probeAll probes follow a very similar installation procedure.

Installing the probe

To install the Probe for Tekelec Eagle STP, run the following command:$OMNIHOME/install/nco_patch -install patch

Where patch is the file name of the patch that you have downloaded.

2 IBM Tivoli Netcool/OMNIbus Probe for Tekelec Eagle STP: Reference Guide

http://csrc.nist.gov/cryptval/140-1/1401val2004.htm

http://csrc.nist.gov/cryptval/140-1/1401val2004.htm

Internationalization supportThe probe supports multibyte character sets. To view the character sets correctly,you must configure the locale settings on the host machine correctly. Eachmultibyte character set is configured slightly differently on each platform.

Example multi-byte character set on Solaris

The following steps describe how to configure Solaris to use the Japanese characterset:1. Install the necessary components for Japanese on to the host machine using the

Solaris CD.2. Set the LANG and LC_ALL environment variables to ja_JP PCK. This uses SJIS

encoding.

Note: You may have to set the LANG in the host machine’s default settings fileand reboot it to make the changes take effect.

3. Make sure that the file $OMNIHOME/platform/arch/locales/locales.dat hasthe following entry:locale = ja_JP PCK, japanese, sjis

where ja_JP PCK is the vendor locale, japanese is the Sybase language, andsjis is the Sybase character set.

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 Tekelec Eagle STP attaches to the STP using a TCP connection. It is amulti-headed probe that can connect to either a single device or multiple devices.

When the probe connects to a single device, it uses either a chat in script specifiedby the ChatinString property or a series of properties required for automatic login.

When the probe connects to multiple devices, it references a hosts file; this filecontains the same details necessary for a connection, but in a different format. Fordetails about this format, see “Hosts file format” on page 5. If you are usingmultiple hosts or ports, the probe rotates among the connections, processing oneevent from each. If the probe experiences a read timeout when doing its first readof any connection in each iteration, it moves directly to the next connection. If yousend a SIGUSR2 signal to the probe, the probe re-reads the hosts file withouthaving to be restarted.

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

Data acquisition is described in the following topics:v “Chat In and Chat Out Scripts” on page 4v “Backoff Strategy” on page 4v “Inactivity” on page 4v “Data Stream Capture” on page 4v “Peer-to-peer failover functionality” on page 6

IBM Tivoli Netcool/OMNIbus Probe for Tekelec Eagle STP 3

Chat In and Chat Out ScriptsChat in and chat out scripts control probe login and logout.

These scripts are on a single line in the expect-send format (for chat in scripts) orsend-expect format (for chat out scripts). You can specify chat in and chat outstrings using the ChatinString and ChatoutString properties. The format is:ChatinString : <expect> <send> <expect> <send> ...ChatoutString : <send> <expect> <send> <expect>

Note: The elements in the chat strings are separated by white space. In order tosend or expect a sequence that includes white space, surround the sequence withsingle quotes.

A typical chat in script might be:".*login.*:.*anu\r\n.*assword.*:.*anu\r\n"

The expect text can use any regular expression, while the send text can send anycharacters (including control characters) using the standard UNIX/C escapesequences described in “Escape Codes” on page 10.

Backoff StrategyBackoff strategy is used when the probe fails to establish a connection or loses anexisting connection to the device.

The probe tries to reestablish a connection after one second, two seconds, then fourseconds, and so on, up to a maximum of 4096 seconds. Once the connection ismade to the specified port, the probe tries to log in to the device. If the probe failsto log in, it shuts down and tries to connect again. The backoff strategy remains inplace until a successful login occurs.

You can also specify a reconnection interval using the ReconnectionIntervalproperty or -reconnectioninterval command line option. When this property isenabled, the probe reconnects at the specified time interval instead of using thebackoff strategy. If the connection is terminated by the remote host, the connectionis also closed by the probe on the host machine. The operating system is notallowed to close it.

InactivityThe Probe for Tekelec Eagle STP has a timeout facility that allows it to disconnectfrom the socket if it fails to receive the next alarm data within a predefinedamount of time. To specify how long the probe waits before disconnecting, use theInactivity property. After this length of time, the probe disconnects from theswitch, sends a ProbeWatch message 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.

Data Stream CaptureThe Probe for Tekelec Eagle STP can capture all raw data sent from a device.

The raw data is stored in a log file and can be used for debugging purposes, todevelop new features for the probe, or to pass to other management systems thatrequire the same data.


For each connection, the full data stream is stored in a file with the followingnaming convention:streamcapturefile_host_port

To enable stream capture, set the StreamCaptureFile property or-streamcapturefile command line option.

Where:v streamcapturefile is the value specified by the StreamCaptureFile property.v host is the name of the host to which the probe is connected.v port is the port on which the probe is listening for data

Stream capture 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.

Rotating Stream Capture Files

The Probe for Tekelec Eagle STP can rotate stream capture files; that is, write to astream capture file that is saved and archived periodically when a predefined filesize is reached.

To use this feature, set the maximum size for the stream capture file using theMaxStreamCapFileSize property and set the DateStreamCapture property to 1.When the DateStreamCapture property is set to 1, the probe creates a streamcapture file with the following naming convention:streamcapturefile_host_port_date_time

By appending the filename with a timestamp, the TSM avoids overwriting the oldstream capture file. The maximum file size specified by the MaxStreamCapFileSizeproperty acts as an upper limit for the stream capture file. If the TSM reads astream whose size exceeds the remaining allowable space in the current streamcapture file, it saves the current file and creates a new one, thus storing the wholestream in a single file.

If you do not specify a maximum size for the stream capture file, it growsindefinitely until the connection is closed. If the MaxStreamCapFileSize property isset and the DateStreamCapture property to 0, the TSM overwrites the streamcapture file for that connection each time the maximum file size is reached.

Hosts file formatThe probe needs a hosts file to connect to multiple hosts. The HostsFile propertyspecifies from which file the probe gets host information. The probe reads the hostsfile and attempts to connect and log in to each host.

If the HostsFile property is defined, the probe attempts to open the specified file.This file must contain the required connection information for the probe in thefollowing format:host port : chi, cho, ft, ia, ri, ra, af;


The following table describes the hosts file format.

Table 3. Hosts file format

Item Description

host This item specifies the host to which theprobe connects.

port This item specifies the port to which theprobe connects.

chi This item specifies the chat in string for thehost/port.

cho This item specifies the chat out string for thehost/port.

ft This item specifies the flush time value forthe host/port.

ia This item specifies the inactivity alarm forthe host/port.

ri This item specifies the reconnection interval.

ra This item specifies the reconnectionattempts.

af This item specifies the active flag. You mustset this to True. Setting this to Falsedeactivates the connection.

When you create a hosts file, note the following information:v In the hosts file, the end of each entry is indicated by a semicolon.v Whitespace and commas separate individual elements within a line.v Whitespace characters are sp and tab.v Comment lines are preceded #.v Blank lines are ignored.v You can force the probe reread the hosts file without restarting the probe by

issuing a USR1 signal. To do this, enter the command kill -USR1 pid, wherepid is the process identifier of the probe .

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 probes]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 probes]Mode : "slave"

Note: The properties file also contains all other properties required to configurethe probe.

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 information about default properties and command line options, seethe IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, (SC23-6373).

Table 4. Properties and command line options

Property name Command line option Description

ChatinString string -chatinstring string Use this property to specify thechat in script for connection to thehost system.

The default is ″″.

ChatoutString string -chatoutstring string Use this property to specify thechat out script for disconnectionfrom the host system.


DateStreamCaptureinteger

-datestreamcapture integer Use this property to specifywhether the probe appends a dateand time to the stream capturefilename. Possible values are:

0 No

1 Yes

Setting this property to 1 preventsthe stream capture file from beingoverwritten.

The default is 0.


Table 4. Properties and command line options (continued)


ExpectTimeout integer -expecttimeout integer Use this property to specify thetime in seconds the probe allowsfor a response to the expect partof the chat in/out script.

The default is 20.

FlushTime integer -flushtime integer Use this property to specify thetime in seconds the probe waitsbefore flushing the event to theObjectServer.

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 thefile that the probe uses to connectto multiple hosts.


Inactivity integer -inactivity integer Use this property to specify thetime (in seconds) the probe allowsa port to be inactive beforesending an Inactivity ProbeWatchmessage to the ObjectServer.

The default is 0 (no message issent).

InactivityRetry integer -inactivityretry integer Use this property to specify thenumber of consecutive periods ofinactivity the probe allows beforeattempting to reconnect to thehost.

The default is 0 (the feature isdisabled).

InvalidAlarmLogFilestring

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

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




InvalidAlarmLogginginteger

-invalidlogging integer Use this property to specify thewhether the probe logs invalidalarms. Possible values are:

0: The probe does not log invalidalarms.

1: The probe logs invalid alarms.

The default is 0.

MaxEvents integer integer Use this property to specify themaximum number of events theprobe attempts to readsimultaneously from a givensource.

You can increase this number toincrease the event throughputwhen a large number of events isgenerated.

The default is 1.

MaxInvalidAlarmLogFileSize integer

-maxinvalidlog integer Use this property to specify themaximum size in bytes for theinvalid alarm file. When this limitis reached, the probe creates a newfile with a new date and time.

If the probe reads a stream whosesize exceeds the remainingallowable space in the file, itcreates a new one, thus storing thewhole stream in a single file.

The default is 1048576.

MaxStreamCapFileSizeinteger

-maxstreamcapfilesizeinteger

Use this property to specify themaximum size in bytes of thestream capture file. When thislimit is reached, the probe createsa new file.

The default is 0.

Port integer -commandline 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 thelength of time in the millisecondsthat the probe waits when readingfrom or writing to the devicebefore timing out.

The default is 100.




ReconnectionAttemptsinteger

-reconnectionattemptsinteger

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

The default is 0 (the.probe makesunlimited attempts to reconnect tothe socket)

ReconnectionIntervalinteger

integer Use this property to specify thetime in seconds betweensuccessive reconnection attempts.

The default is 0 (the probe usesthe standard backoff strategy).

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


Escape CodesSome properties support C-style escape codes.

You can use C-style escape codes in the following properties:v ChatinStringv ChatoutString

This allows you to easily define whether or not to send escape code sequencesafter commands. For example, the following ChatinString sends a carriage returncharacter (\r) after the username and password:ChatinString : ".*: user\r .*: passwd\r .*:"

The following character sequences are recognized.

Table 5.

Escape code Character

\b Backspace

\f Form-feed

\n New-line

\r Carriage return

\t Tab

\\ Backslash

\’ Single quote

\″ Double quote

Note: The escape sequences for backslash, single quote, and double quote shouldbe double-escaped. For example, to send a backslash character (\) use \\\\.


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.

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

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 Tekelec Eagle STPgenerates. Not all the elements described are generated for each event; the staticelements that the probe generates depends upon the event type.

Table 6. Static elements

Element name Element description

$Host This element contains the name of the host.

$Port This element identifies the port from which thealarm originated.

$Date . This element contains the date of the alarm.

$Time This element contains the time of the alarm.

$TimeZone This element contains the three letter timezonecode.

$SRN This element contains the system release number.

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

The following table describes the elements that the Probe for Tekelec Eagle STPgenerates. Not all the elements described are generated for each event; thedynamic elements that the probe generates depends upon the event type.

Table 7. Dynamic elements

Element name Element description

$AlarmLevel This element indicates the severity of alarm.

$MSN This element contains the message sequencenumber.

$MRN This element contains the message referencenumber.

$Message This element contains the event message.

$Report This element specifies whether the alarm appliesto a report.

$TextLineNN This element contains the event-specificmessage(s).


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 8. Error messages

Error Description Action

CreateAndSet failed fortoken_number

The processing of an alertfailed.

Check the connection to theSTP system.

ConvertEscapes: Errorallocating memory foroctal code

ConvertEscapes: Errorallocating memory fortemp buffer

Expect: Error allocatingmemory for buffer

LogInOut: Errorallocating memory fortoken

Unable to allocate memoryfor processing buffer

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

Make more memory available.

Expect timed out The probe was unable toconnect to the remote host.

Check that the remote host isavailable.

Failed to open connectionto host port

The probe was unable tocreate a connection to the hoston the specified port. .

Check the physical connectionto the host system.

SendAlert failed The probe was unable to sendan alert to the ObjectServer.

Check the ObjectServer isavailable.

SessionProcess failed The probe was unable toprocess the alert against therules file.

Contact IBM SoftwareSupport.

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 9. ProbeWatch messages

ProbeWatch message Description Triggers/causes

Connection attempted ...(host,port)

The probe is trying toestablish a connection to thehost.

The probe is trying toestablish a connection to thehost.

Connection failed ...(host,port)

The probe has failed toestablish a connection to thehost.

General connection failuredue either to an incorrectsetting of the Host or Portproperty, or the host refusinga connection request from theprobe.

Connection lost ...(host,port)

The probe has lost theconnection to the host.

The device has dropped theconnection to the probe.

Connection succeeded ...(host,port)

The probe has successfullyestablished a connection tothe host.

The probe has successfullyestablished a connection tothe host.

Discarding on readfailure buffer

The probe discarded apartially read event from itsbuffer following a readfailure.

The probe is unable tocomplete reading an eventdue to a problem with theconnection to the device; forexample, the device hasdropped the connection to theprobe.

Discarding on timeoutbuffer

The probe discarded apartially read event from itsbuffer following a readtimeout.

While reading a line of theevent, the probe could notfind the end-of-lineterminator within the periodspecified by the ReadTimeoutproperty. This is due to aslow or busy network, or tothe ReadTimeout propertybeing set too low.

Disconnected from systemdue to shutdown signal

The probe has disconnectedfrom the host.

A shutdown signal was sentto the probe.

Disconnecting from systemdue to Inactivity alarm... (host,port)

The probe has disconnectedfrom the device.

The device was silent for theperiod specified by theInactivity property. If youwant the probe to time outless frequently, increase thisvalue.

Disconnection attempted... (host,port)

The probe is attempting todisconnect from the host.

The probe is shutting downor has lost the connection.

Disconnection failed ...(host,port)

The probe has failed todisconnect cleanly from thehost.

There has been a corruptionof the memory locationstoring the connection details.

Disconnection succeeded... (host,port)

The probe has disconnectedfrom the host.

The probe has shut down orlost the connection.

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.


Table 9. ProbeWatch messages (continued)

ProbeWatch message Description Triggers/causes

Failed to get license ...(host,port)

The probe is unable to obtaina license for the connection tothe host.

Either the license server isdown or there are insufficientlicenses in the server.

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 attemptedreconnection for each of itsconnections has exceeded thatspecified by theReconnectionAttemptsproperty.

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.

Login attempted ...(host,port)

The probe is trying to log into the host.

The probe is trying to log into the host.

Login failed ...(host,port)

The probe has failed to log into the host.

The probe has encountered aproblem while logging in.Check that the ChatinStringproperty is specified correctly.

Login succeeded ...(host,port)

The probe has logged in tothe host.

The probe has logged in tothe host.

Logout attempted ...(host,port)

The probe is trying to log outfrom the host.

The probe has received acommand to shut down.

Logout failed ...(host,port)

The probe has failed to logout from the host.

The probe has encountered aproblem while logging out.Check that the ChatoutStringproperty is specified correctly.

Logout succeeded ...(host,port)

The probe has logged outfrom the host.

The probe has logged outfrom the host.

Running ... The probe is runningnormally.

The probe has just beenstarted.


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, 2008 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 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 17


��

Printed in USA

SC23-7933-01

Date post:	01-Dec-2014
Category:	Documents
Upload:	ashish-mishra
View:	117 times
Download:	3 times

tkelg-pdf

Documents