ibm® tivoli® netcool/omnibus probe for alcatel-lucent ... · vi ibm ®tivoli netcool/omnibus...

IBM® Tivoli® Netcool/OMNIbus Probe for Alcatel-LucentNaviScore 9.1Version 1.0

Reference GuideApril 6, 2012

SC23-6026-02

��

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

Edition notice

This edition (SC23-6026-02) applies to version 1.0 of IBM Tivoli Netcool/OMNIbus Probe for Alcatel-LucentNaviScore 9.1 and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC23-6026-01.

© Copyright IBM Corporation 2006, 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 forAlcatel-Lucent NaviScore 9.1. . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Environment variables . . . . . . . . . . . 3Data acquisition . . . . . . . . . . . . . 3

Retrieving Alarms . . . . . . . . . . . 3Filtering Alarms . . . . . . . . . . . . 3

Status Checking . . . . . . . . . . . . 4ReadTimeout . . . . . . . . . . . . . 4Backoff strategy . . . . . . . . . . . . 4Peer-to-peer failover functionality . . . . . . 4

Properties and command line options . . . . . . 5Elements. . . . . . . . . . . . . . . . 8Error messages . . . . . . . . . . . . . 9ProbeWatch messages . . . . . . . . . . . 10

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

© Copyright IBM Corp. 2006, 2012 iii

||

||||

iv IBM® Tivoli® Netcool/OMNIbus Probe for Alcatel-Lucent NaviScore 9.1: 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 Alcatel-Lucent NaviScore 9.1documentation is provided in softcopy format only. To obtain the most recentversion, visit the IBM® Tivoli® Knowledge Center.

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/common/kc_welcome-444.html?lang=en

Table 1. Document modification history

Documentversion

Publicationdate

Comments

SC23-6026-01 April 30, 2009 First IBM publication.

SC23-6026-02 April 6, 2012 “Summary” on page 1 updated.

Descriptions for the following properties were added tothe“Properties and command line options” on page 5

v FlushBufferInterval

v OrbLocalPort

“Error messages” on page 9 updated.

“ProbeWatch messages” on page 10 updated.

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

© Copyright IBM Corp. 2006, 2012 v



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

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.

vi IBM® Tivoli® Netcool/OMNIbus Probe for Alcatel-Lucent NaviScore 9.1: Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for Alcatel-LucentNaviScore 9.1

The Alcatel-Lucent NaviScore is an element management software that provides acentralized service and network management system to control Alcatel-Lucent'smultiservice switching product functions. The Probe for Alcatel-Lucent NaviScore9.1 acquires data from the Alcatel-Lucent NaviScore 9.1 software using a CommonObject Request Broker Architecture (CORBA) interface.

This guide contains the following sections:v “Summary”v “Installing probes” on page 2v “Data acquisition” on page 3v “Properties and command line options” on page 5v “Elements” on page 8v “Error messages” on page 9

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 Alcatel-Lucent NaviScore9.1.

Table 3. Summary

Probe target Lucent NaviScore 9.1

Probe executable name nco_p_lucent_naviscore_tmf814

Product version 1.0

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

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

Requirements A currently supported version of IBM TivoliNetcool/OMNIbus.

Nonnative Probe Server: probe-nonnative-base

IBM Object Request Broker (IBM ORB, supplied withNetcool/OMNIbus)

Java™ Runtime Environment (JRE) 1.5

Connection method CORBA

Remote connectivity The Probe for Alcatel-Lucent NaviScore 9.1 can connectto a device on a remote host.

© Copyright IBM Corp. 2006, 2012 1

Table 3. Summary (continued)

Multicultural support Available

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 IPv6Note: The probe is supported on IPv6 when runningon IBM Tivoli Netcool/OMNIbus V7.3.0, 7.3.1 and7.4.0 on all UNIX and Linux operating systems.

Federal Information ProcessingStandards (FIPS)

IBM Tivoli Netcool/OMNIbus V7.3.0, 7.3.1, 7.4.0, and8.1 use the FIPS 140-2 approved cryptographicprovider: IBM Crypto for C (ICC) certificate 384 forcryptography. This certificate is listed on the NISTwebsite at http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htm For details aboutconfiguring Netcool/OMNIbus for FIPS 140-2 mode,see IBM Tivoli Netcool/OMNIbus Installation andDeployment 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.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.

2 IBM® Tivoli® Netcool/OMNIbus Probe for Alcatel-Lucent NaviScore 9.1: 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://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

Environment variablesYou must include the following path in the $PATH environment variable:

jre_directory/bin

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 Alcatel-Lucent NaviScore 9.1 gathers events from Alcatel-LucentNaviScore using a Common Object Request Broker Architecture (CORBA) interface.CORBA is an Object Management Group specification that provides a standardinterface definition between objects in a distributed environment; that is, it allowsapplications to communicate with one another regardless of where they are locatedor who has designed them.

Data acquisition is described in the following topics:v “Retrieving Alarms”v “Filtering Alarms”v “Status Checking” on page 4v “ReadTimeout” on page 4v “Backoff strategy” on page 4v “Peer-to-peer failover functionality” on page 4

Retrieving AlarmsThe probe connects to the CORBA interface and listens for existing alarms. Thenusing the CORBA notification push model the probe receives new alarms from theAlcatel-Lucent server as they are generated.

Filtering AlarmsYou can limit which types of alarms the probe retrieves using the followingfiltering properties:v ExcludeSeverityCleared

v ExcludeSeverityCritical

v ExcludeSeverityIndeterminate

v ExcludeSeverityMajor

v ExcludeSeverityMinor

v ExcludeSeverityWarning

These properties allow you to exclude those alarms whose severity is set tocleared, Critical, Indeterminate, Major, Minor, or Warning, respectively; forexample, to exclude alarms of severity Indeterminate, set theExcludeSeverityIndeterminate property to true.

Note: By default, the probe retrieves alarms of all severities.

IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent NaviScore 9.1 3

Status CheckingThe probe checks the status of the Alcatel-Lucent server every 60 seconds. You canchange this frequency if required using the Agentheartbeat property.

ReadTimeoutThe ReadTimeout property specifies how long the probe waits to read alarm databefore timing out. Each time the probe attempts to read an alarm, this is theallotted time that it waits to receive data. If nothing is received, the probe moveson to the next alarm.

Backoff strategyIf the Retry property is set to true, and the probe fails to establish a connection orloses an existing connection to the device, it reverts to a backoff strategy. The probetries to reestablish a connection after one second, two seconds, then four seconds,and so on, up to a maximum of 4096 seconds. Once the connection is made to theCORBA interface, the probe tries to log in to the device. If the probe fails to log in,it shuts down and tries to connect again. The backoff strategy remains in placeuntil a successful login occurs.

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.

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 : 5555 # [communication port between master and slave probe]Mode : "master"PidFile : "$OMNIHOME/var/opc_ua"

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"PidFile : "$OMNIHOME/var/opc_ua2"

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, (SC14-7530).

Table 4. Properties and command line options

Property name Command line option Description

AgentHeartBeat integer -agentheartbeat integer Use this property to specify thefrequency (in seconds) with whichthe probe checks that theAlcatel-Lucent server is stillrunning by sending a pingcommand.

The default is 60.

EncodingStandard string -encodingstandard string Use this property to specify thestandard used to encode anddecode multi-byte characters.

The default is ISO-8859-1.

ExcludeSeverity Clearedstring

-excludeseverity clearedstring

Use this property to specifywhether the probe excludes alarmsof severity Cleared from those thatit retrieves:

false: The probe does not excludealarms of severity Cleared

true: The probe excludes alarmsof severity Cleared.

The default is false.

ExcludeSeverity Criticalstring

-excludeseveritycriticalstring

Use this property to specifywhether the probe excludes alarmsof severity Critical from thosethat it retrieves:

false: The probe does not excludealarms of severity Critical.

true: The probe excludes alarmsof severity Critical.



Table 4. Properties and command line options (continued)


ExcludeSeverityIndeterminate string

-excludeseverityindeterminate string

Use this property to specifywhether the probe excludes alarmsof severity Indeterminate fromthose that it retrieves:

false: The probe does not excludealarms of severity Indeterminate.

true: The probe excludes alarmsof severity Indeterminate.


ExcludeSeverityMajorstring

-excludeseveritymajorstring

Use this property to specifywhether the probe excludes alarmsof severity Major from those that itretrieves:

false: The probe does not excludealarms of severity Major.

true: The probe excludes alarmsof severity Major.


ExcludeSeverityMinorstring

-excludeseverityminorstring

Use this property to specifywhether the probe excludes alarmsof severity Minor from those that itretrieves:

false: The probe does not excludealarms of severity Minor.

true: The probe excludes alarmsof severity Minor.


ExcludeSeverity Warningstring

-excludeseverity warningstring

Use this property to specifywhether the probe excludes alarmsof severity Warning from those thatit retrieves:

false: The probe does not excludealarms of severity Warning.

true: The probe excludes alarmsof severity Warning.


FlushBufferIntervalinteger

-flushbufferintervalinteger

Use this property to specify howoften (in seconds) the probeflushes all alerts in the buffer tothe ObjectServer.

The default is 0 (which instructsthe probe to never flush the alertsto the ObjectServer).




IORFile string -iorfile string Use this property to specify thepath of the Inter-operable ObjectReference (IOR) file.

The default is "".

NamingContextIORFilestring

-nsior string Use this property to specify thelocation of the IOR file thatcontains the root context of thenaming service.

The default is "".

NamingContextPath string -nspath string Use this property to specify thelocation of the interface objectwithin the naming service.

The default is "".

ORBInitialHost string -orbinitialhost string Use this property to specify thename of the naming service host.

The default is "".

ORBInitialPort integer -orbinitialport integer Use this property to specify theport number of the namingservice.

The default is 1570.

ORBLocalPort integer -orblocalport integer Local port to which the ORB tolistens.

The default is 0 (ORB selects anavailable port at random).

Password string -password string Use this property to specify thepassword required with theUsername property to log in to thesystem.

The default is "".

Resynch string -noresynch: This isequivalent to Resynchwith a value of false

-resynch: This equivalentto Resynch with a value oftrue.

Use this property to specifywhether the probe requests allactive alarms from the serverbefore acquiring new alarms:

false: The probe do not performthe resynchronization.

true: The probe performs theresynchronization.


ResynchBatchSize integer -resynchbatchsize integer Use this property to specify themaximum number of alarms thatthe probe retrieves in each batchof resynchronization alarms.

The default is 100.


||

||



Retry string -noretry: This isequivalent to Retry with avalue of false

-retry: This is equivalentto Retry with a value oftrue.

Use this property to specifywhether the probe attempts toreconnect to the system using abackoff strategy following areported error:

false: The probe shuts down anddoes not attempt to reconnect.

true: The probe attempts toreconnect to the system using thebackoff strategy.


Note: For details about thebackoff strategy, see “Backoffstrategy” on page 4.

Timeout integer -timeout integer Use this property to specify thetime (in seconds) that the probewaits to receive events beforedisconnecting from the namingservice and shutting down.

The default is 0 (probe nevertimes out).

Username string -username string Use this property to specify theusername of the account withwhich the probe logs on to theAlcatel-Lucent NaviScore 9.1interface.

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 for Alcatel-LucentNaviScore 9.1 generates. Not all the elements described are generated for eachevent; the elements that the probe generates depends upon the event type.

Table 5. Elements

Element name Element description

$additionalInfo This element displays additional informationabout the alarm.

$additionalText This element displays a brief description of theproblem being reported by the alarm.

$affectedTPList This element contains a list of termination pointsaffected by the problem being reported by thealarm.


Table 5. Elements (continued)

Element name Element description

$emsTime This element displays the time at which thealarm was reported by the EMS.

$event_type This element displays the type of the alarm.

$isClearable This element indicates whether the alarm can becleared. Possible values are:

false

true

$layerRate This element displays the layer to which thealarm applies.

$nativeEMSName This element displays the name of the objectreporting the alarm as given in the EMS userinterface.

$nativeProbableCause This element displays the probable cause as givenin the EMS user interface.

$neTime This element displays the time at which the erroroccurred in the network element.

$notificationId This element displays a unique identifier of thealarm. This is derived from the serial number ofthe alarm as used by the EMS.

$objectName This element displays the name of the objectreporting the alarm.

$objectType This element displays the type of object reportingthe alarm.

$perceivedSeverity This element displays the perceived severity ofthe alarm.

$probableCause This element displays the probable cause of thealarm.

$probableCauseQualifier This element displays the qualifier used toclassify the alarm type.

$serviceAffecting This element indicates whether the alarm hasaffected the service.

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, (SC14-7530).


|

||

|||

Table 6. Error messages

Error Description Action

Failed to connect toNotification Service

The probe failed to connect tothe notification service. Eitherthe notification service wasnot running on the specifiedhost and port, or the IORspecified for the notificationservice was not correct.

Check that the notificationservice is running on thespecified host and port andthat the notification serviceIOR is correct.

Failed to connect tointerface object

The probe failed to connectwith the Alcatel-LucentNaviScore 9.1 interface.

Check that the Alcatel-Lucentserver is running correctlyand that the IOR files are upto date.

Check that the value specifiedfor the Username property iscorrect.

Failed to get EMS sessionobject

Failed to get EMS Managerreference

Either the ORBLocalPortproperty has been set but theport is occupied by anotherprocess, or the ORBLocalPortand Retry properties havebeen set but the probe'slistening port has not beenproperly released before theprobe attempts to reconnect tothe EMS server.

Check that the ORBLocalPortis set to a port that is notoccupied by other processes,or disable the Retry propertyand then set up the processcontrol to restart the probe

Failed to perform resynch The probe failed to get thealarm list or failed to iteratethrough resynch alarms.

Check that the connection tothe host is still active.

Failed to ping Lucentserver

The probe encountered aruntime exception whilepinging the Alcatel-Lucentserver.

Verify that the Alcatel-Lucentserver is running.

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, (SC14-7530).

Table 7. ProbeWatch messages

ProbeWatch message Description Triggers/causes

Attempting to performresynch

The synchronization of alarmshas started.

The probe started toresynchronize alarmscollected in the system duringthe timeout period.


||

|||

|||||||||

|||||

|||||

||||

|||

||

||

||||||||||

||||||

||||

||

||||||

||

|

||

|||

|||

||

|||

||||||||

Table 7. ProbeWatch messages (continued)

ProbeWatch message Description Triggers/causes

Connecting toNotification Service toget new alarms

The probe is trying to collectalarm data.

Either the probe is connectingto the Alcatel-Lucent systemto retrieve alarms or it isperforming an automaticresynchronization after beingdisconnected.

Initialising connectionto Lucent NavisCoresystem

The is trying to connect to theAlcatel-Lucent server.

The probe is running.

Pinging Lucent server The probe is sending aheartbeat message to theAlcatel-Lucent server.

The AgentHeartBeat propertyspecifies the frequency withwhich the probe verifies thatthe Alcatel-Lucent server isstill running.

Retry is false - will notreconnect

The probe has disconnectedfrom the Alcatel-Lucent serverand will not attempt toreconnect.

The Retry property is set tofalse.


|

|||

|||

||||||||

|||

|||

||||

|||||

||||||

||

||

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, 2012 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

��

Printed in USA

SC23-6026-02

ibm® tivoli® netcool/omnibus probe for alcatel-lucent ... · vi ibm ®tivoli netcool/omnibus...

Documents