Noksitnmsc PDF

8/9/2019 Noksitnmsc PDF

http://slidepdf.com/reader/full/noksitnmsc-pdf 1/28

IBM® Tivoli® Netcool/OMNIbus Probe for Nokia-SiemensTNMS (CORBA)

Version 3.0

Reference Guide March 02, 2012

SC27-4362-00





IBM® Tivoli® Netcool/OMNIbus Probe for Nokia-SiemensTNMS (CORBA)

Version 3.0

Reference Guide March 02, 2012

SC27-4362-00



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

Edition notice

This edition (SC27-4362-00) applies to version 3.0 of the IBM Tivoli Netcool/OMNIbus Probe for Nokia-SiemensTNMS (CORBA) and to all subsequent releases and modifications until otherwise indicated in new editions.

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

Conventions used in this guide . . . . . . . . v

IBM Tivoli Netcool/OMNIbus Probe forNokia-Siemens TNMS (CORBA) . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Firewall considerations . . . . . . . . . . . 3Data acquisition . . . . . . . . . . . . . 3

Retrieving Alarms . . . . . . . . . . . 4IRP Agent status . . . . . . . . . . . . 4Timeout . . . . . . . . . . . . . . . 4

Backoff strategy . . . . . . . . . . . . 4Filtering Alarms . . . . . . . . . . . . 4

Peer-to-peer failover functionality . . . . . . 5Properties and command line options . . . . . . 6Elements . . . . . . . . . . . . . . . 10Error messages . . . . . . . . . . . . . 11ProbeWatch messages . . . . . . . . . . . 12Running the probe . . . . . . . . . . . . 13

Running multiple probes . . . . . . . . . 13

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

© Copyright IBM Corp. 2012 iii



iv IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens TNMS (CORBA): Reference Guide



About this guide

The following sections contain important information about using this guide.

Document control page

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

The IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens TNMS (CORBA)documentation is provided in softcopy format only. To obtain the most recentversion, visit the IBM® Tivoli® Knowledge Center:

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

Table 1. Document modification history

Documentversion

Publicationdate

Comments

SC27-4362-00 March 02,2012

First IBM publication.

Conventions used in this guide

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

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

© Copyright IBM Corp. 2012 v







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 Nokia-Siemens TNMS (CORBA): Reference Guide



IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens TNMS(CORBA)

The Nokia-Siemens Telecommunication Network Management System (TNMS) is asub- network level management system that provides element management andnetwork management functions for telecommunications networks.

The Probe for Nokia-Siemens TNMS (CORBA) acquires data from Nokia-SiemensTNMS using a TMF814 V2 Common Object Request Broker Architecture (CORBA)interface.

This guide contains the following sections:

v “Summary”

v “Installing probes” on page 2

v “Firewall considerations” on page 3

v

“Data acquisition” on page 3v “Properties and command line options” on page 6

v “Elements” on page 10

v “Error messages” on page 11

v “ProbeWatch messages” on page 12

v “Running the probe” on page 13

Summary

Each 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 Nokia-Siemens TNMS(CORBA).

Table 3. Summary

Probe target Nokia-Siemens TNMS versions 10, 11, 12, and 13

Probe executable name nco_p_siemens_tnms_TMF814

Probe installation package omnibus-arch-probe-nco-p-siemens-tnms-TMF814-version

Package version 3.0

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

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

Connection method CORBA

Remote connectivity The probe can connect to a remote device using aCORBA interface.

Multicultural support Available

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

© Copyright IBM Corp. 2012 1



Table 3. Summary (continued)

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

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 for

cryptography. 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 probes

All 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, and

configuring the probe to suit your environment.

The installation process consists of the following steps:

1. Downloading the installation package for the probe from the PassportAdvantage 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 Nokia-Siemens TNMS (CORBA): Reference Guide

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














Firewall considerations

When using CORBA probes in conjunction with a firewall, the firewall must beconfigured so that the probe can connect to the target system.

Most CORBA probes can act as both a server (listening for connections from thetarget system) and a client (connecting to the port on the target system to which

the system writes events). If you are using the probe in conjunction with a firewall,you must add the appropriate firewall rules to enable this dual behavior.

There are three possible firewall protection scenarios, for which you mustdetermine port numbers before adding firewall rules:

1. If the host on which the probe is running is behind a firewall, you mustdetermine what remote host and port number the probe will connect to.

2. If the host on which the target system is running is behind a firewall, you mustdetermine the incoming port on which the probe will listen and to which thetarget system will connect.

3. If each host is secured with its own firewall, you must determine the followingfour ports:

a. The outgoing port (or port range) for the probe.

b. The hostname and port of the target system.

c. The outgoing port on which the target system sends events if the probe isrunning as a client.

d. The incoming port on which the probe listens for incoming events.

Note: Most, but not all, CORBA probes listen on the port specified by theORBLocalPort property. The default value for this property is 0, which means thatan available port is selected at random. If the probe is behind a firewall, the valueof the ORBLocalPort property must be specified as a fixed port number.

CORBA probes that use EventManager or NotificationManager objects may usedifferent hosts and ports from those that use NamingService and EntryPointobjects. If the probe is configured to get object references from a NamingService orEntryPoint object, you must obtain the host and port information from the systemadministrator of the target system. When you have this information, you can addthe appropriate firewall rules.

Data acquisition

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

The probe gathers events from Nokia-Siemens TNMS using a CORBA interface.

Data acquisition is described in the following topics:

v “Retrieving Alarms” on page 4

v “IRP Agent status” on page 4

v “Timeout” on page 4

v “Backoff strategy” on page 4

v “Filtering Alarms” on page 4

v “Peer-to-peer failover functionality” on page 5

IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens TNMS (CORBA) 3



Retrieving AlarmsIf the Resynch property is set to true, the probe initially receives a list of all activealarms from the AlarmIRP point.

The probe then connects to the NotificationIRP point and uses the CORBAnotification push model to receive new alarms. If the Resynch property is set to

false, the probe only receives new alarms.

IRP Agent statusThe probe checks the status of the IRP Agent every 60 seconds.

You can use the AgentHeartbeat property to change the frequency with which theprobe checks the status of the IRP Agent.

TimeoutThe probe has a timeout facility that allows it to disconnect from the system if there has been no activity for a predefined amount of time. You can specify howlong the probe waits before disconnecting using the Timeout property.

Backoff strategyIf the Retry property is set to true, and the probe fails to establish a connection orloses an existing connection to the device, the probe reverts to a backoff strategy.

The probe's backoff strategy is to try to reestablish a connection at successiveintervals of one second, two seconds, four seconds, eight seconds, and so on, up toa maximum of 4096 seconds. When the maximum retry interval is reached, theprobe shuts down, restarts, and tries to reconnect again. The backoff strategyremains in place until a successful login occurs.

Filtering Alarms

You can use filtering properties to limit the types of alarms that the probe retrievesfrom Nokia-Siemens TNMS.

The probe has six properties that enable you to filter alarms whose severity isCleared, Critical, Indeterminate, Major, Minor, or Warning. By default, the proberetrieves alarms of all severities.

Use one or more of the following properties to filter the alarms:

v ExcludeSeverityCleared

v ExcludeSeverityCritical

v ExcludeSeverityIndeterminate

v ExcludeSeverityMajor

v ExcludeSeverityMinor

v ExcludeSeverityWarning

For example, to exclude alarms of severity Indeterminate, set theExcludeSeverityIndeterminate property to true.




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

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

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

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

this probe. For more information about generic Netcool/OMNIbus properties andcommand line options, see the IBM Tivoli Netcool/OMNIbus Probe and GatewayGuide.

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 pings Nokia-SiemensTNMS to verify that it is running.

The default is 60.

EncodingStandard string -encodingstandard string Use this property to specify the

character encoding standard thatthe probe uses.

The default is ISO-8859-1 (this setsthe encoding standard to LatinAlphabet 1).

ExcludeSeverityCleared

string-excludecleared (This isequivalent toExcludeSeverityCleared

with a value of true.)

-noexcludecleared (This isequivalent toExcludeSeverityCleared

with a value of false.)

Use this property to specifywhether the probe excludes alarmsof severity Cleared from theretrieved events. This propertytakes the following values:

false: The probe does not excludealarms of severity Cleared.

true: The probe excludes alarmsof severity Cleared.

The default is false.

ExcludeSeverityCritical

string-excludecritical (This isequivalent toExcludeSeverityCritical


-noexcludecritical (Thisis equivalent toExcludeSeverityCritical


Use this property to specifywhether the probe excludes alarmsof severity Critical from theretrieved events. This propertytakes the following values:

false: The probe does not excludealarms of severity Critical.

true: The probe excludes alarmsof severity Critical.





Table 4. Properties and command line options (continued)


ExcludeSeverity

Indeterminate string-excludeindeterm (This isequivalent toExcludeSeverity

Indeterminate with avalue of true.)

-noexcludeindeterm (Thisis equivalent toExcludeSeverity

Indeterminate with avalue of false.)

Use this property to specifywhether the probe excludes alarmsof severity Indeterminate from theretrieved events. This propertytakes the following values:

false: The probe does not excludealarms of severity Indeterminate.

true: The probe excludes alarmsof severity Indeterminate.


ExcludeSeverityMajor

string-excludemajor (This isequivalent toExcludeSeverityMajor


-noexcludemajor (This is

equivalent toExcludeSeverityMajor


Use this property to specifywhether the probe excludes alarmsof severity Major from theretrieved events. This propertytakes the following values:

false: The probe does not excludealarms of severity Major.

true: The probe excludes alarmsof severity Major.


ExcludeSeverityMinor

string-excludeminor (This isequivalent toExcludeSeverityMinor


-noexcludeminor (This isequivalent to

ExcludeSeverityMinorwith a value of false.)

Use this property to specifywhether the probe excludes alarmsof severity Minor from theretrieved events. This propertytakes the following values:

false: The probe does not exclude

alarms of severity Minor.

true: The probe excludes alarmsof severity Minor.


ExcludeSeverityWarning

string-excludewarning (This isequivalent toExcludeSeverityWarning


-noexcludewarning (This isequivalent toExcludeSeverityWarning


Use this property to specifywhether the probe excludes alarmsof severity Warning from theretrieved events. This propertytakes the following values:

false: The probe does not excludealarms of severity Warning.

true: The probe excludes alarmsof severity Warning.


IORFile string -iorfile string Use this property to specify thelocation of the InteroperableObject Reference (IOR) file.

The default is "".






NamingContextIORFile

string-nsior string Use this property to specify the

location 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 object inthe Naming Service.

The default is "".

ORBCharEncoding string -orbcharencoding string Use this property to specify thenative character encoding set used by the Object Request Broker(ORB) for character data.

The default is UTF8.

ORBInitialHost string -orbinitialhost string Use this property to specify the

name of the Naming Service host.

The default is "".

ORBInitialPort integer -orbinitialport integer Use this property to specify theport number on the NamingService host to which the probeconnects.

The default is 1570.

ORBLocalHost string -orblocalhost string Use this property to specify tospecify the local host name used by the server-side ORB to placethe server's host name into the

IOR of a remote object.

The default is "".

ORBLocalPort integer -orblocalport integer Use this property to specify thelocal port to which the ORBlistens.

The default is 0 (the ORB selectsan available port at random).

ORBWCharDefault string -orbwchardefault integer Use this property to specify whatwide character (wchar) set theIBM ORB uses whencommunicating with other ORBs

that do not publish a wchar set.The default is UTF16.

Password string -password string Use this property to specify thepassword required to log in to theNokia-Siemens TNMS system.

The default is "".






Resynch string -noresynch (This isequivalent to Resynch witha value of false.)

-resynch (This is

equivalent to Resynch witha value of true.)

Use this property to specifywhether the probe performs aresynchronization before acquiringnew alarms from Nokia-SiemensTNMS. This property takes thefollowing values:

false: The probe does not performa resynchronization.

true: The probe performs aresynchronization.


ResynchBatchSize integer -resynchbatchsize integer Use this property to specify themaximum number of alarms thatthe probe retrieves in eachresynchronization batch.

The default is 100.

Retry string -noretry (This isequivalent to Retry with avalue of false.)

-retry (This is equivalentto Retry with a value of true.)

Use this property to specifywhether the probe attempts toreconnect to the CORBA interfacefollowing an error. This propertytakes the following values:

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

true: The probe attempts toreconnect.


Timeout integer -timeout integer Use this property to specify thetime (in seconds) that the probewaits to receive events before itdisconnects from the CORBAinterface and shuts down.

The default is 0 (the probe waitsindefinitely).

Username string -username string Use this property to specify theusername required to log in to theNokia-Siemens TNMS system.

The default is "".




Elements

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

elements described are generated for each event. The elements that the probegenerates depend on the event type.

Table 5. Elements

Element name Element description

$additionalInfo This element contains additional informationabout the alarm.

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

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

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

$event_type This element contains the type of the alarm.Possible values are:

v communicationsAlarm

v environmentalAlarm

v equipmentAlarm

v processingErrorAlarm

v qualityofServiceAlarm

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

v false

v true

$layerRate This element contains the name of the objectreporting the alarm as given in the EMS userinterface.

$nativeEMSName This element contains the name of the alarm asgiven in the EMS user interface.

$nativeProbableCause This element contains the probable cause of thealarm as given in the EMS user interface.

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

$notificationId This element contains the unique identifier of thealarm. This is derived from the serial number of

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




Table 5. Elements (continued)

Element name Element description

$perceivedSeverity This element displays the perceived severity of the alarm. Possible values are:

v 0: PS_INDETERMINATE

v 1: PS_CRITICAL

v 2: PS_MAJOR

v 3: PS_MINOR

v 4: PS_WARNING

v 5: PS_CLEARED

$probableCause This element contains the probable cause of thealarm.

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

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

Error messages

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

Table 6. Error messages

Error Description Action

Failed to connect to

Naming Service

The CORBA service is notrunning on the expectedHost/Port/IOR

The probe failed to connect to

the naming service. Either thenaming service was notrunning on the specified hostand port, or the IOR specifiedfor the naming service wasnot correct.

Check that the naming service

is running on the specifiedhost and port and that thenaming service IOR is correct.

Failed to get interfaceversion information

Failed to ping Siemensserver

The probe failed to call amethod on the SiemensTNMS server.

Check that the SiemensTNMS server is runningcorrectly and that the IORfiles are up to date.




Table 6. Error messages (continued)

Error Description Action

Failed to get objectreference from IOR file

Failed to get object fromIOR file

Failed to find file,please check file exists!

Failed to convert IOR toobject

Please check that theinterface is running andthe probe is using up todate IOR files

The probe failed to get theobject reference from the IORfile. Either the IOR filerequested was not found or itdid not contain a valid IORfile.

Check that the IOR file existsand that it is a valid IOR file.

Failed to narrow objectreference

Failed to narrow managerreference

The probe failed to narrowthe object reference to theinterface object.

This is a CORBA related errorand is probably related to theCORBA installation.

Failed to resolve NamingContext

Exception raised whenlocating server

The probe failed to resolvethe naming context path tofind the server object. Eitherthe naming context path wasinvalid or did not exist.

Check the NamingContextPathproperty.

Name is null, cannotcreate element

Cannot parsetypevalue_type : name

Failed to parse alarm

The probe failed to parse thealarm.

Check that the alarmconforms to theStructuredEvent format.

ProbeWatch messages

During 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 messages that the probe generates.For information about generic Netcool/OMNIbus ProbeWatch messages, see theIBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 7. ProbeWatch messages

ProbeWatch message Description Triggers/causes

Performing Resynch ... Resynchronization is inprogress.

The probe has startedresynchronization.

Starting the resynch ofalarm list

The probe is synchronizingthe alarms.

The probe has startedreceiving alarms from thealarm list.

Finished the resynch ofalarm list

The probe is finishedsynchronizing the alarms.

The probe has finishedreceiving alarms from thealarm list.




Table 7. ProbeWatch messages (continued)

ProbeWatch message Description Triggers/causes

Resynch Completed ... The probe successfullycompleted resynchronization.

The probe has finishedresynchronization.

Running the probeYou run the probe from the command line.

Before you run the probe, use the IORFile property to specify the full directorypath to the IOR file.

To start the probe, use the following command:

$OMNIHOME/probes/nco_p_siemens_tnms_TMF814

Running multiple probesYou can run multiple instances of the probe.

For each running instance, specify a different port to which the server listens usingthe ORBLocalPort property.

Running multiple probes in a failover configuration

If you have implemented a peer-to-peer failover configuration, both the masterprobe and the slave probe have their own Object Request Broker (ORB) local port.

Where you are running this configuration in conjunction with a firewall, add thereceiving port of each probe to the firewall rules. The direction of the connection isfrom the target system to the master or slave probe.

You set the peer-to-peer failover mode in the properties files of the master andslave probes.

Include the following peer-to-peer settings in the master's probe properties file:

PeerHost : "slave_hostname"PeerPort : 5555 # [communication port between master and slave probes]

Include the following peer-to-peer settings in the slave's probe properties file:

PeerHost : " master_hostname"PeerPort : 5555 # [communication port between master and slave probes]







Appendix. Notices and Trademarks

This appendix contains the following sections:

v Notices

v Trademarks

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right may

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

WARRANTIES 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. 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 it believes 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 agreement

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

estimated 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 of those products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy of performance, 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 operating

platform for which the sample programs are written. These examples have not been 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.

Trademarks

IBM, the IBM logo, ibm.com, AIX, Tivoli, zSeries, and Netcool are trademarks of International 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 Corporation

in the United States, other countries, or both.

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

Java™ and all Java-based trademarks are trademarks of Sun Microsystems, Inc. inthe United States, other countries, or both.

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

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

Appendix. Notices and Trademarks 17








Printed in USA

SC27-4362-00

Documents

Noksitnmsc PDF