IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens IBM ®Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPPV6 (CORBA) Version 5.0 Reference Guide November 04,2011 SC22-5411-00

IBM® Tivoli® Netcool/OMNIbus Probe for Nokia-SiemensNetAct 3GPP V6 (CORBA)Version 5.0

Reference GuideNovember 04, 2011

SC22-5411-00

��

IBM® Tivoli® Netcool/OMNIbus Probe for Nokia-SiemensNetAct 3GPP V6 (CORBA)Version 5.0

Reference GuideNovember 04, 2011

SC22-5411-00

��

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

Edition notice

This edition (SC22-5411-00) applies to version 5.0 of IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct3GPP V6 (CORBA) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2011.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 forNokia-Siemens NetAct 3GPP V6(CORBA) . . . . . . . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 3Firewall considerations . . . . . . . . . . . 3Configuring the lookup table . . . . . . . . . 4Data acquisition . . . . . . . . . . . . . 4

Connecting to the CORBA interface. . . . . . 5Retrieving objects . . . . . . . . . . . . 5

Status checking . . . . . . . . . . . . 5Filtering notifications and alarms . . . . . . 6Command line interface . . . . . . . . . 8Peer-to-peer failover functionality . . . . . . 9Running multiple probes . . . . . . . . . 10

Properties and command line options . . . . . 10Elements . . . . . . . . . . . . . . . 15Error messages . . . . . . . . . . . . . 18ProbeWatch messages . . . . . . . . . . . 24Running the probe . . . . . . . . . . . . 26

Appendix. Notices and Trademarks . . 29Notices . . . . . . . . . . . . . . . . 29Trademarks . . . . . . . . . . . . . . 31

© Copyright IBM Corp. 2011 iii

iv IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): 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 Nokia-Siemens NetAct 3GPP V6(CORBA) documentation is provided in softcopy format only. To obtain the mostrecent version, visit the IBM® Tivoli® Information Center:

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

Table 1. Document modification history

Document version Publication date Comments

SC22-5411-00 November 04, 2011 First IBM publication.

Note: The Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) was previouslydocumented in the same reference guide as the Probe for Nokia-Siemens NetAct3GPP (CORBA). This reference guide documents the Probe for Nokia-SiemensNetAct 3GPP V6 (CORBA) only.

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

Operating system-dependent variables and paths

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

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

$OMNIHOME/probes

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

%OMNIHOME%\probes

For probes supported on UNIX, Linux, and Windows operating systems, probeguides use the standard UNIX conventions for specifying environment variablesand describing directory paths. When using the Windows command line with

© Copyright IBM Corp. 2011 v



these probes, replace the UNIX conventions used in the guide with Windowsconventions. If you are using the bash shell on a Windows system, you can use theUNIX conventions.

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

Operating system-specific directory names

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

$OMNIHOME/probes/arch

The following table lists the directory names used for each operating systemcurrently supported by Netcool/OMNIbus.

Table 2. Directory names for the arch variable

Operating system Directory name represented by arch

AIX® systems aix5

HP-UX PA-RISC-based systems hpux11

HP-UX Integrity-based systems hpux11hpia

Red Hat Linux and SUSE systems linux2x86

Linux for System z® linux2s390

Solaris systems solaris2

Windows systems win32

vi IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide

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

Nokia-Siemens NetAct is a networking and service management OperationsSupport System (OSS). It provides fault and performance management, serviceprovisioning, support for multiple wireless network technologies, and customermanagement interfaces. It operates across the radio-access and core subnetworks ofnext-generation wireless Internet networks.

The Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) collects alarms fromNokia-Siemens NetAct using a Common Object Request Broker Architecture(CORBA) 3rd Generation Partnership Project (3GPP) interface. The probe acquiresdata from Nokia-Siemens NetAct devices that support 3GPP version 6.2.0. IBMdoes not maintain a list of compatible Nokia-Siemens devices.

The probe complies with the following 3GPP standards:

Table 3. Supported 3GPP standards

3GPP TechnicalSpecification Version Object

32.111-3 6.2.0 Alarm Integration Reference Point (IRP)

32.303 6.3.0 Notification IRP

32.363 6.3.0 Entry Point IRP

This guide contains the following sections:v “Summary”v “Installing probes” on page 3v “Firewall considerations” on page 3v “Configuring the lookup table” on page 4v “Data acquisition” on page 4v “Properties and command line options” on page 10v “Elements” on page 15v “Error messages” on page 18v “ProbeWatch messages” on page 24v “Running the probe” on page 26

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.

Table 4. Summary

Probe target Nokia-Siemens NetAct 3GPP interface V6

Probe executable name nco_p_nokia_netact_3gpp_v6

© Copyright IBM Corp. 2011 1

Table 4. Summary (continued)

Probe installation package omnibus-arch-probe-nco-p-nokia-netact-3gpp-v6-version

Package version 5.0

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

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

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

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

Requirements One of the following versions of IBM TivoliNetcool/OMNIbus:

v V7.2.0 with Interim Fix 4 (7.2.0.7-IF0004) installed

v V7.2.1 with Interim Fix 3 (7.2.1.5-IF0003) installed

v V7.3.0

v V7.3.1

Nonnative Probe Server: probe-nonnative-base-14

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

Java Runtime Environment (JRE) 1.5

Connection method CORBA

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

Multicultural support Available

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

Peer-to-peer failoverfunctionality

Available

IP environment IPv4 and IPv6

Federal Information ProcessingStandards (FIPS)

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

2 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): 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

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

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

Advantage Online website.Each probe has a single installation package for each operating systemsupported. For details about how to locate and download the installationpackage for your operating system, visit the following page on the IBM TivoliInformation Center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.html

2. Installing the probe using the installation package.The installation package contains the appropriate files for all supportedversions of Netcool/OMNIbus. For details about how to install the probe torun with your version of Netcool/OMNIbus, visit the following page on theIBM Tivoli Information Center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_install_intro.html

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

Firewall considerationsWhen 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 whichthe 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 must

determine 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

must determine the incoming port on which the probe will listen and to whichthe target 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.

IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 3

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



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



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.

Configuring the lookup tableThe probe is supplied with a lookup table that contains details of the various typesof alarms that Nokia-Siemens NetAct generates. You might need to update therules file to include the path to the lookup table.

At installation, the Corba_3gpp_V620.lookup file supplied with the probeinstallation package is installed to the following location:

$OMNIHOME/probes/includes/

To reference the lookup table from the rules file, add the following line to the rulesfile:

include "$OMNIHOME/probes/includes/Corba_3gpp_V620.lookup"

The include command assumes that the probe is run from the standard$OMNIHOME/probes/ directory. If you are running the probe from a differentdirectory, use the absolute directory path to the lookup table. Do not use the$OMNIHOME environment variable in this directory path.

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 gathers alarms from Nokia-Siemens NetAct using a CORBA 3GPPinterface.

Data acquisition is described in the following topics:v “Connecting to the CORBA interface” on page 5v “Retrieving objects” on page 5v “Status checking” on page 5v “Filtering notifications and alarms” on page 6v “Command line interface” on page 8v “Peer-to-peer failover functionality” on page 9v “Running multiple probes” on page 10


Connecting to the CORBA interfaceThe probe acts as an Integration Reference Point (IRP) Manager and connects tothe Nokia-Siemens NetAct system using a CORBA 3GPP interface.

The AlarmIRP and NotificationIRP CORBA objects form a part of the IRP agent towhich the probe connects.

Depending on your operating environment, use one of the following connectionconfigurations:1. Option 1 - specify values for the following properties:

v NetActServerName - the name of the Nokia-Siemens NetAct server to whichthe probe connects to retrieve the Naming Context IOR file.

v NetActServerPort - the port on the Nokia-Siemens NetAct server throughwhich the probe connects to retrieve the Naming Context IOR file.

v NamingServiceIORRequest - specify the command that the probe uses toupload the CORBA Naming Service IOR.

v AlarmIrpName - specify the name used to resolve the Alarm IRP in theCORBA Naming Service.

v NotificationIrpName - specify the name used to resolve the Notification IRPin the CORBA Naming Service.

2. Option 2 - specify values for the following properties:v NamingServiceHost - specify the name of the host machine where the

CORBA Naming Service is running.v NamingServicePort - specify the port on which the CORBA Naming Service

listens.v AlarmIrpName - specify the name used to resolve the Alarm IRP in the

CORBA Naming Service.v NotificationIrpName - specify the name used to resolve the Notification IRP

in the CORBA Naming Service.3. Option 3 - specify values for the following properties:

v EntryPointIrpFile - specify the location of the file that contains the IOR ofthe EntryPoint IRP object.

v NotificationIrpName - specify the name used to resolve the Notification IRPin the CORBA Naming Service.

v AlarmIrpName - specify the name used to resolve the Alarm IRP in theCORBA Naming Service.

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

The probe then connects to the NotificationIRP server and uses the CORBAnotification push model to receive new alarms from the server as they aregenerated. If the Resynch property is set to false, the probe only receives newalarms.

Status checkingThis section contains information about the status checking method of the probe.

The probe checks the status of the IRP agent every 60 seconds. You can change thisfrequency if required using the Agentheartbeat property.


Filtering notifications and alarmsThis section contains information about how to enable the retrieval of notificationsand alarms from the target system.

The NotificationFilter and AlarmFilter properties allow you to specify thenotifications and alarms that the probe receives from the target device.

When you use these properties, you must use the actual token names. Forexample, the token h represents the element NV_PERCEIVED_SEVERITY. So to specifythat the probe is only sent notifications with a perceived severity of 3, set theNotificationFilter property to $h == 3.

You can specify more complex filters using AND, OR, and NOT statements. Forexample, to specify that the probe is sent notifications with a perceived severity of3 or 4, set the NotificationFilter property to the following value:

($h == 3) OR ($h == 4)

The following table lists the token/element mappings available for the AlarmFilterand NotificationFilter properties:

Table 5. Token/element mappings

Token Element

a NV_NOTIFICATION_ID

b NV_EVENT_TIME

c NV_SYSTEM_DN

d NV_MANAGED_OBJECT_CLASS

e NV_MANAGED_OBJECT_INSTANCE

f NV_ALARM_ID

ff NV_ALARM_LIST_ALIGNMENT_REQUIREMENT

g NV_PROBABLE_CAUSE

gg NV_SERVICE_USER

h NV_PERCEIVED_SEVERITY

hh NV_SERVICE_PROVIDER

i NV_SPECIFIC_PROBLEM

ii NV_SECURITY_ALARM_DETECTOR

j NV_ADDITIONAL_TEXT

jj NV_VENDOR_SPECIFIC_ALARM_TYPE

k NV_ACK_TIME

l NV_ACK_USER_ID

m NV_ACK_SYSTEM_ID

n NV_ACK_STATE

o NV_COMMENTS

p NV_BACKED_UP_STATUS

q NV_BACK_UP_OBJECT

r NV_THRESHOLD_INFO

s NV_TREND_INDICATION


Table 5. Token/element mappings (continued)

Token Element

t NV_STATE_CHANGE_DEFINITION

u NV_MONITORED_ATTRIBUTES

v NV_PROPOSED_REPAIR_ACTIONS

w NV_CORRELATED_NOTIFICATIONS

x NV_REASON

y CLEAR_USER_ID

z CLEAR_SYSTEM_ID

FiltersThis section describes the filters that help retrieve matching elements.

The probe retrieves elements by using a filter that associates an ObjectServer fieldwith its expected value. Filters take the following format:

<attribute_name> <attribute_comparison_operator> <attribute_value>

The following table lists the valid operators and attribute values for the availableObjectServer fields:

Table 6. Valid operators and attribute values

Name of the attribute Valid operators Valid attribute values

alarmType == COMMUNICATIONS_ALARM

ENVIRONMENTAL_ALARM

EQUIPMENT_ALARM

PROCESSING_ERROR_ALARM

QUALITY_OF_SERVICE_ALARM

managedObjectClass == The filtering of elements sent from thedevice can only be configured inNokia-Siemens NetAct. For details of thesyntax required for filtering object classes,refer to your CORBA documentation orcontact your system administrator.

Note: An attribute value of 0 retrieves anymatching alarms from both the 3GPPinterface and the Nokia-Siemens NetActsystem.

perceivedSeverity ==

<

<=

>

>=

CRITICAL

MAJOR

MINOR

WARNING

CLEARED


Valid filters

The following are examples of valid filters:1. (managedObjectClass == SubNetwork) OR (managedObjectClass ==

ManagedElement) OR (managedObjectClass == ManagedFunction) AND (NOTalarmType == PROCESSING_ERROR_ALARM)

2. (alarmType == ENVIRONMENTAL_ALARM) OR (perceivedSeverity <= MINOR)

3. (alarmType == ENVIRONMENTAL_ALARM) OR (NOT perceivedSeverity == WARNING)

Invalid filters

The following are examples of invalid filters that will not work:1. (perceivedSeverity == WARNING) OR (managedObjectInstance ==

SubNetwork=Nokia-1)

2. (alarmType == ENVIRONMENTAL_ALARM) AND (probableCause < 1000)

3. (alarmType < ENVIRONMENTAL_ALARM)

Command line interfaceThe probe has a command line interface (CLI) that you can use to issuecommands.

To use the CLI, use the CommandPort property to specify a port through whichcommands can be sent. Use Telnet to send commands to this port.

The following table lists the commands that you can use with the CLI:

Table 7. CLI commands

Command Description

acknowledge_alarm This command allows you to acknowledge analarm in the 3GPP interface.

Note: This command takes as a parameter theNV_ALARM_ID of the alarm being acknowledged.Only one alarm can be acknowledged at a time.

exit/quit This command closes the connection.

help This command displays online help about theCLI.

resynch_all This command allows you to perform a fullresynchonization with the 3GPP interface.

Note: Successful resynchronization requires thatthe Resynch property is set to true.

resynch_filter This command allows you to a perform partialresynchronization with the 3GPP interface.

Note: This command takes as a parameter a filterin the same format as the AlarmFilter property.For details, see “Filtering notifications andalarms” on page 6.

unacknowledge_alarm This command allows you to unacknowledge analarm in the 3GPP interface.

Note: This command is not currently supportedby Nokia-Siemens NetAct.


Table 7. CLI commands (continued)

Command Description

userid_acknowledge_alarm This command allows you to acknowledge analarm in the 3GPP interface by specifying theNV_ALARM_ID and NV_ACK_USER_ID parameters.These parameters are specified by theAckSystemId and AckUserId properties.

userid_clear_alarm userid This command allows you to clear an alarmcreated by a specific user ID.

userid_unacknowledge_alarm This command allows you to un-acknowledge analarm in the 3GPP interface by specifying theNV_ALARM_ID and NV_ACK_USER_ID parameters.

version This command displays the version of the probe.

Note: Since the CLI uses Telnet connections, you can connect to the probe fromanywhere. This means that simple scripts can be set up to allow users toacknowledge selected events from the Netcool/OMNIbus event list. You can createdesktop tools that use Telnet to connect to the probe, send a command, and thenclose the connection.

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

While the slave probe receives heartbeats from the master probe, it does notforward events to the ObjectServer. If the master shuts down, the slave probe stopsreceiving heartbeats from the master and any events it receives thereafter areforwarded to the ObjectServer on behalf of the master probe. When the master isrunning again, the slave continues to receive events, but no longer sends them tothe ObjectServer.

Example property file settings for peer-to-peer failover

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

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

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


Running multiple probesYou can run multiple instances of the probe.

For each running instance, you must use the ORBLocalPort property to specify adifferent port to which the server listens.

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, thereceiving port of each probe must be added to the firewall rules. The direction ofthe connection is from 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.

The peer-to-peer settings of the master probe properties file should include thefollowing entries:PeerHost : "slave_hostname"PeerPort : 5555 # [communication port between master and slave probes]

The peer-to-peer settings of the slave probe properties file should include thefollowing entries:PeerHost : "master_hostname"PeerPort : 5555 # [communication port between master and slave probes]

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-7608).

Table 8. Properties and command line options

Property name Command line option Description

AckSystemId string -acksystemid string Use this property to specify theprocessing system on which theIRP Manager runs. This is used bythe acknowledge_alarm CLIfunction.

The default is "".

AckUserId string -ackuserid string Use this property to specify thename of the user acknowledgingthe alarm. This is used by theacknowledge_alarm CLI function.

The default is "".


Table 8. Properties and command line options (continued)


Agentheartbeat integer -agentheartbeat integer Use this property to specify thefrequency (in seconds) with whichthe probe checks the status of theIRP agent.

The default is 60.

AlarmFilter string -alarmfilter string Use this property to specify thefilter the Alarm IRP uses to limitthe alarms sent to the probe.

The default is "".

AlarmIrpName string -alarmirpname string Use this property to specify thename of the Alarm IRP Agent usedby the Naming Service.

The default is 32.111-3 V6.2.

Note: The value of this propertycan differ between NetAct systems.For example, it might take thefollowing format:NokiaNetact3gppv6AlarmIRP.

BeatInterval integer -beatinterval integer Use this property to specify theheartbeat interval for peer-to-peerfailover.

The default is 2.

ClearSystemId string -clearsystemid string Use this property to specify thesystem identifier that theuserid_clear_alarms CLIcommand clears.

The default is "".

ClearUserId string -clearuserid string Use this property to specify theuser clearing the alarms using theuserid_clear_alarms CLIcommand.

The default is "".

CommandPort integer -commandport integer Use this property to specify theport through which users canconnect to the 3GPP interface usingthe Command Line Interface (CLI)supplied with the probe. For detailsabout the CLI, see “Command lineinterface” on page 8.

The default is 6970.

CommandPortLimitinteger

-commandportlimit integer Use this property to specify themaximum number of Telnetconnections that can be made tothe probe.

The default is 10.




EntryPointIrpFilestring

-entrypointirpfile string Use this property to specify thelocation of the file that contains theIOR of the EntryPoint IRP object.

The default is "".

FlushBufferIntervalinteger

-flushbufferinterval integer Use this property to specify howoften (in seconds) the probe flushesall alerts in the buffer to theObjectServer.

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

InstanceId string -instanceid string Use this property to specify aunique identifier for the instance ofthe probe. This property allowsyou to run multiple instances ofthe probe on the same machine.

The default is "".

Mode string -mode string Use this property to specify therole of an instance of the probe in apeer-to-peer failover relationship.This property takes the followingvalues:

master: The instance is the masterprobe.

slave: The instance is the slaveprobe.

standard: There is no failoverrelationship.

The default is standard.

NamingServiceIORRequest string

-namingserviceiorrequeststring

Use this property to specify thecommand that the probe uses toupload the CORBA Naming ServiceIOR.

The default is GET /cgi-bin/get_nbif_ior.

NamingServiceHoststring

-namingservicehost string Use this property to specify thehost running the CORBA NamingService.

The default is localhost.

NamingServicePortinteger

-namingserviceport integer Use this property to specify theport on which the CORBA NamingService listens.





NetActServerNamestring

-netactservername string Use this property to specify thename of the Nokia-Siemens NetActserver to which the probe connectsto retrieve the Naming ContextIOR file.

The default is "".

NetActServerPortinteger

-netactserverport integer Use this property to specify theport on the Nokia-Siemens NetActserver through which the probeconnects to retrieve the NamingContext IOR file.


NotificationCategoriesstring

-notificationcategories string Use this property to specify thenotification categories that theprobe subscribes to.

The default is "" (the probesubscribes to all categories).

Note: To specify multiplecategories, separate them usingsemicolons, in the followingformat:

category1; category2; categoryn

For example, to subscribe to thealarms and heartbeat events, usethe following value:

ALARM IRP V1.0.0; CS IRP V1.0.0

NotificationFilterstring

-notificationfilter string Use this property to specify thefilter that the Notification IRP usesto limit the notifications sent to theprobe.

The default is "".

NotificationIrpNamestring

-notificationirpname string Use this property to specify thename of the Notification IRP Agentused by the Naming Service.

The default is 32.303 V6.1.

Note: The value of this propertycan differ between NetAct systems.For example, it might take thefollowing format:NokiaNetact3gppv6NotificationIRP.




ORBCharEncodingstring

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

The default is UTF8.

This property can also take thevalue ISO8859_1.

ORBLocalHostNamestring

-orblocalhostname string Use this property to specify thelocal host name used by theserver-side ORB to place theserver's host name into the IOR ofa remote object.

The default is "".

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

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

ORBWCharDefaultstring

-orbwchardefault string Use this property to specify whatwide character (wchar) set the IBMORB uses when communicatingwith other ORBs that do notpublish a wchar set.

The default is UTF16.

This property can also take thevalue UCS2.

PeerHost string -peerhost string Use this property to specify thehost to which the probe fails overin a peer-to-peer failoverconfiguration.

The default is localhost.

PeerPort integer -peerport integer Use this property to specify theport through which the master andslave probes communicate in apeer-to-peer failover configuration.





Resynch string -resynch (This is equivalentto Resynch with a value oftrue.)

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

Use this property to specifywhether the probe requests allactive alarms from theNokia-Siemens NetAct systembefore connecting to thenotification service for new alarms.This property takes the followingvalues:

false: The probe does not performresynchronization.

true: The probe performsresynchronization at startup.

The default is false.

Retry string -retry string Use this property to specifywhether the probe attempts toreconnect to the Nokia-SiemensNetAct system following a timeout.This property takes the followingvalues:

false: The probe does not attemptto reconnect to the system

true: The probe attempts toreconnect to the system

The default is false.

TimeTick integer -timetick integer Use this property to specify thelifetime (in minutes) of theNotification IRP session on the3GPP server.

The default is 0 (there is no timelimit for the session).

Timeout integer -timeout integer Use this property to specify thetime period (in seconds) that theprobe waits for the next alarmbefore disconnecting.

The default is 0 (which instructsthe probe to never disconnect).

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

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


Table 9. Elements

Element name Element description

AttributeValue(element_name) This element contains the value of anelement being monitored. This element isgenerated dynamically and its content isdependent on the IRP agent.

Note: The element_name part of thiselement can be the name of any of theother elements in this table.

AttributeValueChange(element_name) This element indicates how the value ofthe element being monitored haschanged.

Note: The element_name part of thiselement can be the name of any of theother elements in this table.

CLEAR_SYSTEM_ID This element indicates whether thesystem identifier has been cleared.

CLEAR_USER_ID This element indicates whether the useridentifier has been cleared.

DOMAIN_NAME This element contains the name of thedomain where the notification wasgenerated.

EVENT_NAME This element contains the extended eventtype for this IRP.

EVENT_TYPE This element contains the event type ofthe notification.

NV_ACK_STATE This element indicates theacknowledgement state of the alarm.

NV_ACK_SYSTEM_ID This element contains the system ID ofthe IRP Manager processing thenotification.

NV_ACK_TIME This element contains the time at whichthe user acknowledged the alarm.

NV_ACK_USER_ID This element identifies the last user whochanged the acknowledgement state.

NV_ADDITIONAL_TEXT This element provides information aboutthe network element that generated thealarm.

NV_ALARM_ID This element contains the identificationinformation about the alarm as it appearsin the alarm list.

NV_ALARM_LIST_ALIGNMENT_ REQUIREMENT This element indicates whether the alarmlist requires alignment.

NV_BACK_UP_OBJECT This element contains the DistinguishedName (DN) of the backup object.

NV_BACKED_UP_STATUS This element identifies whether the objecthas been backed up.

NV_COMMENTS This element contains the comment aboutthe alarm.


Table 9. Elements (continued)

Element name Element description

NV_CORRELATED_NOTIFICATIONS_notif_ID_Set This element contains the set ofnotifications to which this notification isconsidered to be correlated. This elementis generated dynamically and its contentis dependent on the IRP agent.

NV_CORRELATED_NOTIFICATIONS_ SOURCE This element contains the source of thenotification set.

NV_EVENT_TIME This element contains the time at whichthe event occurred.

NV_MANAGED_OBJECT_CLASS This element shows the managed objectclass of the network resource.

NV_MANAGED_OBJECT_INSTANCE This element contains the managed objectinstance of the network resource.

NV_MONITORED_ATTRIBUTE This element contains the managed objectattribute of the network resource.

NV_NOTIFICATION_ID This element contains identificationinformation for the notification.

NV_PERCEIVED_SEVERITY This element indicates the relative level ofurgency of the alarm.

NV_PROBABLE_CAUSE This element provides further informationabout the probable cause of the alarm.

NV_PROPOSED_REPAIR_ACTIONS This element contains the proposed repairactions for the notification.

NV_REASON This element contains the reason thattriggered the proposed repair action.

NV_SECURITY_ALARM_DETECTOR This element contains the identifier of thedetector of the security alarm.

NV_SERVICE_PROVIDER This element contains the name of theservice provider.

NV_SERVICE_USER This element contains further informationabout the problem that the notificationrelates to.

NV_SPECIFIC_PROBLEM This element contains further informationabout the problem that the notificationrelates to.

NV_STATE_CHANGE_DEFINITION This element contains information aboutthe status change of the alarm.

NV_SYSTEM_DN This element contains the distinguishedname (DN) used to identify the system.

NV_THRESHOLD_INFO This element contains information about athreshold that has been crossed.

NV_TREND_INDICATION This element indicates how an observedcondition has changed.

NV_VENDOR_SPECIFIC_ALARM_TYPE This element contains the alarm typespecific to the vendor.


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-7608).

Table 10. Error messages

Error Description Action

A problem while connecting toAlarmIRP orNotificationIRPBAD_PARAM Exceptioni.e one or more of the in/outparameter is null: +e

Cannot proceed. Shutting down!

CORBA.OBJECT_NOT_ EXIST exceptionraised.

NotificationIRP is down!

InvalidParameter Exception

NetcoolIRPManager: Exceptionoccurred. Stack trace to stderr

OperationNotSupported Exception

Unexpected CORBA Exception

The probe could notconnect to AlarmIRP orNotificationIRP pointsdue to a problem withthe CORBA interface.

Check that theNokia-Siemens NetActserver is runningcorrectly.

Refer to your CORBAdocumentation.

Cannot initialize the Orb: " + e: The probe encountereda problem duringinitialization of theObject Request Broker(ORB).

Ensure that the$CLASSPATH environmentvariable contains thepath to the IBM ORB.jar files.


Table 10. Error messages (continued)


Command_Port Error occurred

Command_Port Failed to getCommandPortLimit property - using10

Command_Port Failed to get propertyCommandPort

Command_Port Failed to sendprobewatch message!

Command_Port host Failed to closecommand socket

Command_Port host Failed to getsocket IO

Command_Port host Failed to readcommand

Command_Port Thread shutting downdue to error!

NetcoolIRPManager: Failed toacknowledge_alarms()

NetcoolIRPManager: Failed toUnacknowledge_ alarms()

The probe encountereda problem with thecommand port CLIfunction.

Check that you havespecified the commandport correctly.

Check the connectionbetween the probe andthe command port.

Command_Port Thread shutting downdue to error!

The probe encountereda problem with thecommand port CLIfunction.

Check that theCommandPort propertyhas the correct value.

Check that thenco_p_nonnative processis running correctly.

Command_Port Failed to openlistening socket, shutting downThread!

The probe could notopen a listening socketon the command portspecified.

Specify a different portin the CommandPortproperty.

COMMUNICATION FAILURE Exception i.eServer is dead

GetSubscriptionStatus Exception

The probe could notconnect to theNokia-Siemens NetActserver.


Error to parse event completely

Failed to parse event completely

Name is null, cannot create Element

NetcoolIRPManager: Category ValueNOT supported: Discarding Alarm

NetcoolIRPManager: Error whenparsing event

The probe cannot parsethe alarm. This isprobably because thealarm is in a formatthat the probe cannotunderstand.





Failed to get timeout propertyvalue, defaulting to 0

The probe could notget the timeout value,and is not going totime out.

Check the value of theTimeout property iscorrect. Change thevalue if necessary.

Failed to connect to the NamingContext: " + e:

The probe could notconnect to theNamingContext.

Check that theNamingServiceHost andNamingServicePortproperties have thecorrect values.

Failed to resolve theNotificationIRP object: " + e:

The probe could notresolve theNotificationIRP objectas the object is notregistered in theNamingService.

Check that theNotificationIrpNameproperty has the correctvalue.

Name is null, cannot create Element The probe could notcreate the matchingelement for anunknown field found inan alarm. Parsing of theremaining known fieldscontinues.

Check whether thedefault fields of theObjectServer aremodified.

NetcoolIRPManager: Failed to sendevent

The probe could notsend the parsed eventto the ObjectServer.

Check whether theObjectServer is runningcorrectly.

NetcoolIRPManager: Failed toretrieve AlarmIRP object fromsecurity interface

NetcoolIRPManager: Failed toretrieve NotificationIRP objectfrom security interface

login: Failed to get IRP object:+ex

login: Unknown exception occured+ex

The probe could notget either the AlarmIRPor the NotificationIRPobject. (ex in the errormessage specifies therelated Java exception.)

Check that theAlarmIrpName andNotificationIrpNameproperties have thecorrect values.

NetcoolIRPManager: Failed to findIOR file filename

The probe could notlocate the IRP Manageras the filename does notexist.

Check that the IRPManager is set upcorrectly.

NetcoolIRPManager: Failed toperform resynch

Failed to perform resynch

Failed to iterate through resynchalarms

The probe could notresynchronize thealarms.

Check thatNokia-Siemens NetActserver is runningcorrectly.

Check that the Resynchproperty has the correctvalue.

NetcoolIRPManager: Stack Trace tostderr:

The probe could notconnect to AlarmIRP orNotificationIRP pointsdue to a problem withthe CORBA interface.

Use this message fromthe Netcool® IRPManager whiledebugging.




NetcoolIRPManager: Notificationirpproperty needs to be set

NetcoolIRPManager: BothNameServiceHost and NSPort propertyneeds to be set

NetcoolIRPManager: Alarmirpproperty needs to be set

The probe could notfind one or moreproperties required toconnect to theNokia-Siemens NetActserver.

Check that theproperties given in theerror message have thecorrect values.

Failed to connect to the NamingContext : + e

The probe cannotconnect to theNamingContext.

Check thattheNamingServiceHostand NamingServicePortproperties have thecorrect values.

Failed to resolve the AlarmIRPobject : + e

The AlarmIRP object isnot registered in theNaming Service withthe AlarmIrpNameprovided in theproperties file.

Check thatAlarmIrpName propertyhas the correct value.

Failed to resolve theNotificationIRP object : + e

The NotificationIRPobject is not registeredin the Naming Servicewith theNotificationIrpNameprovided in theproperties file.

Check that theNotificationIrpNameproperty has the correctvalue.

NetcoolIRPManager: Failed toretrieve AlarmIRP object fromsecurity interface

NetcoolIRPManager: Failed toretrieve NotificationIRP objectfrom security interface

Failed to narrow Security IRPinterface :" +ex'

Problem while trying to connect tothe IRP points : "+e

login: Failed to get IRP object : "+ex

login: Unknown exception occured "+ex

Failed to get either theAlarmIRP orNotificationIRP object.There is a problem withthe CORBA interface.

Refer to your CORBAdocumentation.

NetcoolIRPManager: Failed to findIOR file '" +ior_file+ "'

The probe could notlocate the IRP Manageras the filename does notexist.

Check that the IRPManager has been setup correctly.




Failed to perform resynch

Failed to ping notification service

There is a problem withthe resynchronizationprocess.

Check thatNokia-Siemens NetActserver is runningcorrectly. Check that youhave specified theresynchronizationparameters correctly.

"Communication failure - lostconnection to NoticiationIRP: " +e

“CORBA.TRANSIENT exception raised.NotificationIRP is down!"

"CORBA.OBJECT_NOT_EXIST exceptionraised. NotificationIRP is down!"

"BAD_PARAM Exception i.e one ormore of the in/out parameter isnull: " +e

"CORBA Exception stack trace tostderr: " +e

"Failed to Connect : " +e"

Either, the server is not running,the IOR is out of date, or probecannot reach remote Server!"

"Failed to Connect : " +e"

Cannot proceed. Shutting down!"

The probe could notconnect to theNotificationIRP pointin the Nokia-SiemensNetAct system.

Check whether theNokia-SiemensNetActserver is stillrunning.

Failed to iterate through resynchalarms

The probe failed to getthe alarm list or failedto performresynchronization ofalarms.


Check that the Resynchproperty is set correctly.

NetcoolIRPManager: Failed toacknowledge_alarms() : +e

NetcoolIRPManager: Failed toUnacknowledge_alarms() : +e

The probe could notacknowledge thealarms.



NetcoolIRPManager: ERROR whenparsing a notification event

NetcoolIRPManager: Stack Trace tostderr: + e

The probe has aproblem duringinitialization of theORB.

Ensure that the$CLASSPATH environmentvariable contains thepath to the IBM ORB.jar files.

NetcoolIRPManager: Failed to sendevent : +e

The probe could notforward the event tothe ObjectServer.

Check that theObjectServer is stillrunning.




Name is null, cannot create Element The probe could notfind one of theexpected element forthe event.

Check the log file thatstores the alarms for thesyntax error. If the probeis run in debug mode,the alarm is printed inthe log file created bythe probe. Also checkthat the alarm is in thecorrect format.

Note: This inability ofthe probe to createelement does not affectthe parsing of the rest ofthe fields.

[Command Port] Failed to getCommandPortLimit property - using10

The probe could notretrieve the value of theCommandPortLimitproperty.

Check that theCommandPortLimitproperty has the correctvalue.

Note: As the defaultvalue is set to 10, thiserror does not affect thebehavior of the probe.

[Command Port] Failed to getproperty 'CommandPort

[Command Port] Failed to openlistening socket, shutting downThread!

[Command Port] Thread shutting downdue to error!

The probe has failed tounacknowledge thealarms.

Check that theNV_ALARM_IDspecified by the CLI iscorrect.

[Command Port] Error occured :+e A problem occurredwhile the userattempted to connect tothe CommandPort, orwhile the user sent acommand.

Check that theCommandPortLimitproperty has the correctvalue.

[Command Port] host Failed to getsocket IO : "+e

There was a problemwith command portfunctionality.



[Command Port] host Failed to readcommand : "+e

[Command Port] host Failed to closecommand socket : +e

The probe found thatthere is a problem withcommand portfunctionality.




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

Table 11. ProbeWatch messages

ProbeWatch message Description Triggers or causes

Communication failure -lost connection toNoticiationIRP

Failed to getsubscripton status

CORBA TIMEOUT Exceptionwhile trying to getsubscription status fromNotificationIRP

Failed to connect toNotificationIRP:ae.reason Shutting down

Failed to Connect:Either, the server isnot running, the IOR isout of date, or probecannot reach remoteServer

CORBA.OBJECT _NOT_EXISTException: Lostconnection toNotificationIRP

CORBA.TRANSIENTException: Lostconnection toNotificationIRP

The probe has failed to getthe subscription status fromthe Notification IRP.

The notification service is notavailable.

Connection toNotificationIRP serverhas been established

The probe has successfullyestablished a connection tothe Notification IRP.

The probe has successfullysubscribed to the Notificationservice.

Detaching subscription The probe is disconnectingfrom the Notification IRP.

Either the probe has notreceived any events for thespecified timeout period, theprobe is shutting down, or theprobe has received a stopsignal.

END SYNCHRONIZATION The probe is closing thesynchronization process.

The probe has finishedreceiving alarms from thealarm list.


Table 11. ProbeWatch messages (continued)


Failed to get IRPOutline (GetIRPOutlineexception caught whencalling get_IRP_outline)

Failed to get IRPreference(GetIRPReferenceexception caught whencallingget_IRP_reference)

Failed to get IRPreferences - invalidparameter(InvalidParameterexception caught whencallingget_IRP_reference)

The probe could not get eitherthe AlarmIRP or theNotification IRP object.

The AlarmirpName orNotificationirpNameproperties have incorrectvalues.

Failed to listen forcommands on port numberlistening_port

The probe could not open thesocket specified by the port tolisten for commands.

The specified port is in use foranother process.

Failed to log in tointerface(InvalidParameterexception caught whencallingget_IRP_outline)s

The probe could not login tothe Nokia NetAct 3GPPserver.

The Nokia-Siemens NetActserver is not running correctly.

There is a connection errorwith the Nokia-SiemensNetAct server.

The IOR is out of date.

The probe does not haveappropriate permissionsrequired to log in to theNokia-Siemens NetAct server.

Going Down The probe is shutting down. The probe has started shuttingdown the connection.

Inactivity: No eventsreceived for timeoutseconds

The probe has exceeded thetime out period already set.

The probe did not receiveevents for the specified period.

Invalid IRPVersion(InvalidIRPVersionexception caught whencallingget_IRP_outline))

The probe could not get theNotification IRP object due toinvalid IRP version.

Incorrect value set for theNotificationIrpVersionproperty.

NetcoolIRPManager:Failed to find IOR filealarmirp_ior_file

The probe has failed to getthe IOR file specified.

The AlarmirpFile property inthe properties file has anincorrect value.

NetcoolIRPManager:Failed to find IOR fileior_file g

The probe could not find theIOR file specified.

The AlarmirpFile orNotificationirpFile propertieshave incorrect values.

NetcoolIRPManager:Failed to find IOR filenotificationirp_ior_file

The probe has failed to getthe IOR file.

The NotificationirpFileproperty has an incorrectvalue.


Table 11. ProbeWatch messages (continued)


PermissionDenied(PermissionDeniedexception caught whencallingget_IRP_outline)s

The probe could not login tothe Nokia-Siemens NetActserver.

The probe does not haveappropriate permissionsrequired to log in to theNokia-Siemens NetAct server.

Running The probe is successfullyrunning.

The probe has startedfunctioning.

START SYNCHRONIZATION The probe is synchronizingthe events.

The probe has startedreceiving alarms from thealarm list.

SYNCHRONIZATION FAILED The probe could not get newalarms.

The probe failed to get thealarm list, or failed to performresynchronization of alarms.

Unable to get events The probe could not getevents from Nokia-SiemensNetAct.

The probe has failed to getevents.

Unexpected fatal errorwhen connecting tointerface

Unexpected fatal errorwhen getting IRPreference from EntryPoint IRP

Unexpected fatal errorwhile getting IRPOutline

Unexpected fatal error,failed to connect

The probe has received a fatalerror message from theGIF/FM process.

The error message containsinformation about the cause ofthe fatal error.

Will listen for commandson port numberlistening_port

The probe is listening forcommands on the portspecified.

The port specified is ready toreceive commands.

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

Depending on which method you use to connect to the CORBA 3GPP interface,you must specify values for the properties described in “Connecting to the CORBAinterface” on page 5.

Use the following command to start the probe:

$OMNIHOME/probes/nco_p_nokia_netact_3gpp_v6

Running multiple probes

You can run multiple instances of the probe on the same machine. For eachrunning instance, use the ORBLocalport property to specify a different port to


which the server listens. You must also specify a unique identifier for the probeinstance using the InstanceId property.

Shutting down the probe

To stop an instance of the probe, issue a stop signal to the process associated withthat probe instance.



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. 2011 29

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 31


��

Printed in USA

SC22-5411-00

Documents

IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens IBM ®Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPPV6 (CORBA) Version 5.0 Reference Guide November 04,2011 SC22-5411-00