IBM® Tivoli® Netcool/OMNIbus Probe for Nokia-Siemens

NetAct 3GPP V4 (CORBA)

Version 10.0

Reference Guide
March 02, 2012



SC23-7667-06
IBM® Tivoli® Netcool/OMNIbus Probe for Nokia-Siemens
NetAct 3GPP V4 (CORBA)
Version 10.0

Reference Guide
March 02, 2012



SC23-7667-06
 Notice
Before using this information and the product it supports, read the information in “Notices and Trademarks,” on page 25.

Edition notice
This edition (SC23-7667-06) applies to version 10.0 of the IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens
NetAct 3GPP V4 (CORBA) and to all subsequent releases and modifications until otherwise indicated in new
editions.
This edition replaces SC23-7667-05.
© Copyright IBM Corporation 2007, 2012.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this guide . . . . . . . . . . . v Lookup table . . . . . . . . . . . . . 7
Document Control Page . . . . . . . . . . v Command line interface . . . . . . . . . 8
Conventions used in this guide . . . . . . . vii Peer-to-peer failover functionality . . . . . . 9
Properties and command line options . . . . . 10
IBM Tivoli Netcool/OMNIbus Probe for Elements . . . . . . . . . . . . . . . 12
Error messages . . . . . . . . . . . . . 14
Nokia-Siemens NetAct 3GPP V4 ProbeWatch messages . . . . . . . . . . . 19
(CORBA) . . . . . . . . . . . . . . 1 Running the probe . . . . . . . . . . . . 23
Summary . . . . . . . . . . . . . . . 2 Troubleshooting . . . . . . . . . . . . . 23
Installing probes . . . . . . . . . . . . . 2
Firewall considerations . . . . . . . . . . . 3 Appendix. Notices and Trademarks . . 25
Data acquisition . . . . . . . . . . . . . 4
Notices . . . . . . . . . . . . . . . . 25
Connecting to the CORBA interface. . . . . . 4
Trademarks . . . . . . . . . . . . . . 27
IRP Agent status . . . . . . . . . . . . 5
Filtering notifications and alarms . . . . . . 5

© Copyright IBM Corp. 2007, 2012 iii

iv IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (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 NetAct 3GPP V4

(CORBA) documentation is provided in softcopy format only. To obtain the most
recent version, visit the IBM® Tivoli® Knowledge Center:

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/common/
kc_welcome-444.html?lang=en
Table 1. Document modification history
Document Publication
version date Comments
SC23-6092-00 March 21, First IBM publication.
2007
SC23-7667-01 June 22, 2007 Probe version and patch number updated.

Information about running multiple instances of a probe

updated.

InstanceId property added.

Default property values updated.

SC23-7667-02 September Version number of the probe has been updated.
07, 2007

© Copyright IBM Corp. 2007, 2012 v

 Table 1. Document modification history (continued)
Document Publication
version date Comments
SC23-7667-03 June 30, 2008 Support to Nokia NetAct 3GPP v6 added.

Summary section updated.

Installation requirements section updated.

Environment variables section added.

Updating the rules file section updated.

Data acquisition section updated.

Format of the filters section added.

Peer-to-peer failover functionality section added.

Properties and command line options section updated.

The BeatInterval, Mode, NotificationIrpVersion,
PeerPort and PeerHostproperties removed.

Elements section updated. The CLEAR_SYSTEM_ID,

CLEAR_USER_ID, NV_ALARM_LIST_ALIGNMENT_REQUIREMENT,
NV_COMMENTS, NV_MANAGED_OBJECT_CLASS, NV_REASON,
NV_SECURITY_ALARM_DETECTOR, NV_SERVICE_PROVIDER,
NV_SERVICE_USER, and NV_VENDOR_SPECIFIC_ALARM_TYPE
elements added.

Error messages section updated.

ProbeWatch messages section updated.

SC23-7667-04 October 31, “Summary” on page 2 updated.
2010
Description for FlushBufferInterval added.
SC23-7667-05 March 31, Installation section replaced by “Installing probes” on
2011 page 2.

“Firewall considerations” on page 3 added.

SC23-7667-06 March 02, Reference information for the Probe for Nokia-Siemens
2012 NetAct 3GPP V6 (CORBA) was removed.

Information about operating system conventions added in

“Conventions used in this guide” on page vii.

Troubleshooting information added in “Troubleshooting”

on page 23.

Note: The Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA)

(nco_p_nokia_netact_3gpp) was previously documented in the same reference
guide as the Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA)
(nco_p_nokia_netact_3gpp_v6). This reference guide documents the Probe for
Nokia-Siemens NetAct 3GPP V4 (CORBA) only.

vi IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
Conventions used in this guide
All probe guides use standard conventions for operating system-dependent
environment variables and directory paths.

Operating system-dependent variables and paths

All probe guides use standard conventions for specifying environment variables
and describing directory paths, depending on what operating systems the probe is
supported on.

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

$OMNIHOME/probes

For probes supported only on Windows operating systems, probe guides use the
standard 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, probe
guides use the standard UNIX conventions for specifying environment variables
and describing directory paths. When using the Windows command line with
these probes, replace the UNIX conventions used in the guide with Windows
conventions. If you are using the bash shell on a Windows system, you can use the
UNIX conventions.

Note: The names of environment variables are not always the same in Windows
and UNIX environments. For example, %TEMP% in Windows environments is
equivalent to $TMPDIR in UNIX and Linux environments. Where such variables are
described 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 arch

directory under NCHOME or OMNIHOME, arch is a variable that represents your
operating 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 the
table.
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

About this guide vii

 Table 2. Directory names for the arch variable (continued)
Operating system Directory name represented by arch
®
Linux for System z linux2s390
Solaris systems solaris2
Windows systems win32

OMNIHOME location

Probes and older versions of Tivoli Netcool/OMNIbus use the OMNIHOME

environment variable in many configuration files. Set the value of OMNIHOME as
follows:
v On UNIX and Linux, set $OMNIHOME to $NCHOME/omnibus.
v On Windows, set %OMNIHOME% to %NCHOME%\omnibus.

viii IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct
3GPP V4 (CORBA)
Nokia-Siemens NetAct is a networking and service management Operations
Support System (OSS). It provides fault and performance management, service
provisioning, support for multiple wireless network technologies, and customer
management interfaces. It operates across the radio-access and core subnetworks of
next-generation wireless Internet networks.

The Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA) collects alarms from
Nokia-Siemens NetAct using a Common Object Request Broker Architecture
(CORBA) 3rd Generation Partnership Project (3GPP) interface. The probe acquires
data from Nokia-Siemens NetAct devices that support 3GPP version 4.3.0. IBM
does not maintain a list of compatible Nokia-Siemens devices.

The probe complies with the following 3GPP standards:

Table 3. Supported 3GPP standards
3GPP Technical
Specification Version Object
32.111-3 4.1.0 Alarm Integration Reference Point (IRP)
32.303 4.0.0 Notification IRP

This guide contains the following sections:

v “Summary” on page 2
v “Installing probes” on page 2
v “Firewall considerations” on page 3
v “Data acquisition” on page 4
v “Properties and command line options” on page 10
v “Elements” on page 12
v “Error messages” on page 14
v “ProbeWatch messages” on page 19
v “Running the probe” on page 23
v “Troubleshooting” on page 23

© Copyright IBM Corp. 2007, 2012 1

Summary
Each probe works in a different way to acquire event data from its source, and
therefore has specific features, default values, and changeable properties. Use this
summary 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 V4
Probe executable names nco_p_nokia_netact_3gpp
Probe installation package omnibus-arch-probe-nco-p-nokia-netact-3gpp-version
Package version 10.0
Properties files $OMNIHOME/probes/arch/nokia_netact_3gpp.props
Rules files $OMNIHOME/probes/arch/nokia_netact_3gpp.rules
Connection method CORBA
Multicultural support Available

For information about configuring multicultural support,

including language options, see the IBM Tivoli
Netcool/OMNIbus Installation and Deployment Guide.
Peer-to-peer failover Available
functionality
IP environment IPv4 and IPv6
Federal Information IBM Tivoli Netcool/OMNIbus V7.3.0, 7.3.1, 7.4.0, and 8.1
Processing Standards (FIPS) use the FIPS 140-2 approved cryptographic provider: IBM
Crypto for C (ICC) certificate 384 for cryptography. This
certificate is listed on the NIST website at
http://csrc.nist.gov/groups/STM/cmvp/documents/140-
1/1401val2004.htm For details about configuring
Netcool/OMNIbus for FIPS 140-2 mode, see IBM Tivoli
Netcool/OMNIbus Installation and Deployment Guide.

Installing probes
All probes are installed in a similar way. The process involves downloading the
appropriate installation package for your operating system, installing the
appropriate 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 Passport
Advantage Online website.
Each probe has a single installation package for each operating system
supported. For details about how to locate and download the installation
package for your operating system, visit the following page on the IBM Tivoli
Knowledge 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.

2 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
 The installation package contains the appropriate files for all supported
versions of Netcool/OMNIbus. For details about how to install the probe to
run with your version of Netcool/OMNIbus, visit the following page on the
IBM 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 this
probe. It combines topics that are common to all probes and topics that are
peculiar to this probe. For details about additional configuration that is
common to all probes, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway
Guide.

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

Most CORBA probes can act as both a server (listening for connections from the
target 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 must
determine 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 which the
target system will connect.
3. If each host is secured with its own firewall, you must determine the following
four 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 is
running 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 the
ORBLocalPort property. The default value for this property is 0, which means that
an available port is selected at random. If the probe is behind a firewall, the value
of the ORBLocalPort property must be specified as a fixed port number.

CORBA probes that use EventManager or NotificationManager objects may use

different hosts and ports from those that use NamingService and EntryPoint
objects. If the probe is configured to get object references from a NamingService or
EntryPoint object, you must obtain the host and port information from the system
administrator of the target system. When you have this information, you can add
the appropriate firewall rules.

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

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

The probe gathers alarms from Nokia-Siemens NetAct using a CORBA 3GPP
interface.

Data acquisition is described in the following topics:

v “Connecting to the CORBA interface”
v “IRP Agent status” on page 5
v “Filtering notifications and alarms” on page 5
v “Lookup table” on page 7
v “Command line interface” on page 8
v “Peer-to-peer failover functionality” on page 9

Connecting to the CORBA interface

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

The AlarmIRPOperation and NotificationIRPOperation points form a part of the

IRP Agent to which the probe connects.

The probe uses one of the following methods to make a connection:

v Interoperable Object Reference (IOR) files
v Naming Service

Using IOR files

When using IOR files, the probe gets the object reference of the AlarmIrpName and
NotificationIrpName objects from the Interoperable Object Reference (IOR) files
specified in the AlarmIrpFile and NotificationIrpFile properties.

Set the AlarmIrpName property to the name used to resolve the Alarm IRP in the
Naming Service and set the NotificationIrpName property to the name used to
resolve the Notification IRP in the Naming Service.

Using a Naming Service

If the AlarmIrpFile and NotificationIrpFile properties are not specified, the

probe gets the object references of the AlarmIRPOperation and
NotificationIRPOperation points from the Naming Service.

The probe gets the Naming Service IOR file from the server specified by the
NetActServerName property (using the port specified by the NetActServerPort
property and the command specified by the NamingServiceIorRequest property).

The Naming Service uses the values specified by the AlarmIrpName and
NotificationIrpName properties to resolve the Alarm IRP and Notification IRP
points.

4 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
IRP Agent status
The probe checks the status of the IRP Agent every 60 seconds.

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

Filtering notifications and alarms

This topic contains information about how to enable the retrieval of notifications
and alarms from the target system.

The NotificationFilter and AlarmFilter properties allow you to specify the

notifications and alarms that the probe receives from the target device.

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

You can specify more complex filters using AND, OR, and NOT statements. For
example, to specify that the probe is sent notifications with a perceived severity of
3 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 AlarmFilter
and NotificationFilter properties:
Table 5. Token/element mappings
Token Element
a NV_NOTIFICATION_ID
b NV_CORRELATED_NOTIFICATIONS
c NV_EVENT_TIME
d NV_SYSTEM_DN
e NV_MANAGED_OBJECT_CLASS
f NV_MANAGED_OBJECT_INSTANCE
g NV_PROBABLE_CAUSE
h NV_PERCEIVED_SEVERITY
i NV_SPECIFIC_PROBLEM
j NV_ADDITIONAL_TEXT
k NV_ALARM_ID
l NV_ACK_USER_ID
m NV_ACK_TIME
n NV_ACK_SYSTEM_ID
o NV_ACK_STATE
p NV_BACKED_UP_STATUS
q NV_BACK_UP_OBJECT
r NV_THRESHOLD_INFO
s NV_TREND_INDICATION

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

 Table 5. Token/element mappings (continued)
Token Element
t NV_STATE_CHANGE_DEFINITION
u NV_MONITORED_ATTRIBUTES
v NV_PROPOSED_REPAIR_ACTIONS
w NV_REASON

Filters are described in detail in the following topic:

v “Filters”

Filters
The probe retrieves elements by using a filter that associates an ObjectServer field
with 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 available
ObjectServer 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 the
device can only be configured in
Nokia-Siemens NetAct. For details of the
syntax required for filtering object classes,
refer to your CORBA documentation or
contact your system administrator.

Note: An attribute value of 0 retrieves any

matching alarms from both the 3GPP
interface and the Nokia-Siemens NetAct
system.
perceivedSeverity == CRITICAL

< MAJOR

<= MINOR

> WARNING

>= CLEARED

6 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
 Valid filters

The following are examples of valid filters:

1. (managedObjectClass == SubNetwork) OR (managedObjectClass ==
ManagedElement) OR (managedObjectClass == ManagedFunction) AND (NOT
alarmType == 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)

Lookup table
The probe is supplied with a lookup table that contains details of the various types
of alarms that Nokia-Siemens NetAct generates.

At installation, the Corba_3gpp_V430.lookup file supplied with the probe

installation package is installed to the following location:

$OMNIHOME/probes/includes/

The following line in the rules file references the lookup file:

include "../includes/Corba_3gpp_V430.lookup"

Note: The include command assumes that the probe is run from the standard
$OMNIHOME/probes/ directory. If you are running the probe from a different
directory, replace “..” with the absolute directory path to the lookup file. Do not
use the $OMNIHOME environment variable in this directory path.

In this section of the rules file, you must also specify which version of
Nokia-Siemens Operations Support System (OSS) the probe is running against:
v For OSS4, specify $Version = "OSS4"
v For OSS3 and all previous versions, specify $Version = "OSS3"

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

 Command line interface
The probe is supplied with a Command Line Interface (CLI). This interface enables
you to execute commands to acknowledge and unacknowledge alarms.

To use the CLI, you must use the CommandPort property to specify a port through
which commands will be sent. The default port is 6970. When you want to issue
commands, use Telnet to connect through this port. You can use the
CommandPortLimit property to limit the number of Telnet connections that the
probe can make at one time.

The following table lists the commands that you can use with the CLI:
Table 7. CLI commands
Command Description
acknowledge_alarm alarm_id This command allows you to acknowledge an
alarm in the 3GPP interface.

This command takes the NV_ALARM_ID identifier as

a parameter. Only one alarm can be
acknowledged at a time.

Before using this command, you must specify a

value for the AckSystemId property.
exit/quit This command closes the connection.
help This command displays online help about the
CLI.
unacknowledge_alarm This command allows you to unacknowledge an
alarm in the 3GPP interface.

Note: This command is not currently supported

by Nokia-Siemens NetAct.
userid_acknowledge_alarm alarm_id Use this command to acknowledge an alarm in
user_id the CORBA interface by specifying the alarm ID
(NV_ALARM_ID) and the user ID (NV_ACK_USER_ID)
of the user acknowledging the alarm.

Before using this command, you must specify a

value for the AckSystemId and AckUserId
properties.
userid_unacknowledge_alarm alarm_id Use this command to unacknowledge an alarm in
user_id the CORBA interface by specifying the alarm ID
(NV_ALARM_ID) and the user ID (NV_ACK_USER_ID)
of the user acknowledging the alarm.

Before using this command, you must specify a

value for the AckSystemId and AckUserId
properties.
version This command displays the version of the probe.

CLI scripts

Because the CLI uses Telnet connections, you can connect to the probe from
anywhere by creating a desktop tool to open a Telnet connection, send a command,
and then close the connection. This means that simple scripts can be set up to
allow users to acknowledge selected events from the IBM Tivoli Netcool/OMNIbus

8 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
 event list.

Peer-to-peer failover functionality

The probe supports failover configurations where two probes run simultaneously.
One probe acts as the master probe, sending events to the ObjectServer; the other
acts as the slave probe on standby. If the master probe fails, the slave probe
activates.

While the slave probe receives heartbeats from the master probe, it does not
forward events to the ObjectServer. If the master shuts down, the slave probe stops
receiving heartbeats from the master and any events it receives thereafter are
forwarded to the ObjectServer on behalf of the master probe. When the master is
running again, the slave continues to receive events, but no longer sends them to
the 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 and
slave 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 a
master 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"

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

Properties and command line options
You use properties to specify how the probe interacts with the device. You can
override the default values by using the properties file or the command line
options.

The following table describes the properties and command line options specific to
this probe. For more information about generic Netcool/OMNIbus properties and
command line options, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway
Guide.
Table 8. Properties and command line options
Property name Command line option Description
AckSystemId string -acksystemid string Use this property to specify the
system identifier to use when
acknowledging alarms using the
CLI.

The default is "".

AckUserId string -ackuserid string Use this property to specify the
user identifier to use when
acknowledging alarms using the
CLI.

The default is "".

Agentheartbeat integer -agentheartbeat integer Use this property to specify the
frequency (in seconds) with which
the probe checks the status of the
IRP agent.

The default is 60.

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

The default is Active|.

AlarmIrpFile string -alarmirpfile string Use this property to specify the
path to the Alarm IRP object
reference.

The default is /opt/nokianetact/

data/ 3gpp/ior/3gppaia.ior.
AlarmIrpName string -alarmirpname string Use this property to specify the
name of the Alarm IRP Agent used
by the Naming Service.

The default is AlarmIRP.

CommandPort integer -commandport integer Use this property to specify the
port through which users can
connect to the 3GPP interface using
the Command Line Interface (CLI)
supplied with the probe.

The default is 6970.

For more information about the

CLI, see “Command line interface”
on page 8.

10 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
Table 8. Properties and command line options (continued)
Property name Command line option Description
CommandPortLimit -commandportlimit integer Use this property to specify the
integer maximum number of Telnet
connections that can be made to
the probe.

The default is 10.

FlushBufferInterval -flushbufferinterval integer Use this property to specify how
integer often (in seconds) the probe flushes
all alerts in the buffer to the
ObjectServer.

The default is 0 (which instructs

the probe to never flush the alerts
to the ObjectServer).
InstanceId string -instanceid string Use this property to specify a
unique identifier for the instance of
the probe. This property allows
you to run multiple instances of
the probe on the same machine.

The default is "".

NamingServiceIOR -namingserviceiorrequest Use this property to specify the
Request string string command that the probe uses to
get the Naming Service from the
Nokia-Siemens NetAct server.

The default is GET /cgi-bin

/get_nbif_ior.
NetActServerName -netactservername string Use this property to specify the
string name of the Nokia-Siemens NetAct
server to which the probe connects.

The default is "".

NetActServerPort -netactserverport integer Use this property to specify the
integer port of the Nokia-Siemens NetAct
server through which the probe
retrieves the IOR for the Naming
Service.

The default is 10115.

NotificationFilter -notificationfilter string Use this property to specify the
string filter that the Notification IRP uses
to limit the notifications sent to the
probe.

The default is "".

NotificationIrpFile -notificationirpfile string Use this property to specify the
string path of the Notification IRP IOR
file.

The default is /opt/nokianetact/

data/ 3gpp/ior/3gppnia.ior.

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

 Table 8. Properties and command line options (continued)
Property name Command line option Description
NotificationIrpName -notificationirpname string Use this property to specify the
string name of the Notification IRP Agent
used by the Naming Service.

The default is NotificationIRP/

FMNotifIRP.
ORBLocalPort integer -orblocalport integer Use this property to specify the
local port to which the Object
Request Broker (ORB) listens.

The default is 0 (the ORB selects an

available port at random).
Retry string -retry string Use this property to specify
whether the probe attempts to
reconnect to the Nokia-Siemens
NetAct system following a timeout.
This property takes the following
values:

false: The probe does not attempt

to reconnect to the system

true: The probe attempts to

reconnect to the system

The default is false.

Timeout integer -timeout integer Use this property to specify the
time period (in seconds) that the
probe waits for the next alarm
before disconnecting.

The default is 0 (which instructs

the probe to never disconnect).

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 contain
the event details in a form that the ObjectServer understands.

The following table describes the elements that the Probe for Nokia-Siemens
NetAct 3GPP V4 (CORBA) generates. Not all the elements described are generated
for each event; the elements that the probe generates depends upon the event type.
Table 9. Elements
Element name Element description
AttributeValue(element_name) This element contains the value of an
element being monitored. This element is
generated dynamically and its content is
dependent on the IRP agent.

Note: The element_name part of this

element can be the name of any of the
other elements in this table.

12 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
Table 9. Elements (continued)
Element name Element description
AttributeValueChange(element_name) This element indicates how the value of
the element being monitored has
changed.

Note: The element_name part of this

element can be the name of any of the
other elements in this table.
DOMAIN_NAME This element contains the name of the
domain where the notification was
generated.
EVENT_NAME This element contains the extended event
type for this IRP.
EVENT_TYPE This element contains the event type of
the notification.
NV_ACK_STATE This element indicates the
acknowledgement state of the alarm.
NV_ACK_SYSTEM_ID This element contains the system ID of
the IRP Manager processing the
notification.
NV_ACK_TIME This element contains the time at which
the user acknowledged the alarm.
NV_ACK_USER_ID This element identifies the last user who
changed the acknowledgement state.
NV_ADDITIONAL_TEXT This element provides information about
the network element that generated the
alarm.
NV_ALARM_ID This element contains the identification
information about the alarm as it appears
in the alarm list.
NV_BACK_UP_OBJECT This element contains the Distinguished
Name (DN) of the backup object.
NV_BACKED_UP_STATUS This element identifies whether the object
has been backed up.
NV_CORRELATED_NOTIFICATIONS_notif_ID_Set This element contains the set of
notifications to which this notification is
considered to be correlated. This element
is generated dynamically and its content
is dependent on the IRP agent.
NV_CORRELATED_NOTIFICATIONS_ SOURCE This element contains the source of the
notification set.
NV_MANAGED_OBJECT_INSTANCE This element contains the managed object
instance of the network resource.
NV_MONITORED_ATTRIBUTE This element contains the managed object
attribute of the network resource.
NV_NOTIFICATION_ID This element contains identification
information for the notification.
NV_PERCEIVED_SEVERITY This element indicates the relative level of
urgency of the alarm.
NV_PROBABLE_CAUSE This element provides further information
about the probable cause of the alarm.

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

 Table 9. Elements (continued)
Element name Element description
NV_PROPOSED_REPAIR_ACTIONS This element contains the proposed repair
actions for the notification.
NV_REASON This element contains the reason that
triggered the proposed repair action.
NV_SERVICE_PROVIDER This element contains the name of the
service provider.
NV_SPECIFIC_PROBLEM This element contains further information
about the problem that the notification
relates to.
NV_STATE_CHANGE_DEFINITION This element contains information about
the status change of the alarm.
NV_SYSTEM_DN This element contains the distinguished
name (DN) used to identify the system.
NV_THRESHOLD_INFO This element contains information about a
threshold that has been crossed.
NV_TREND_INDICATION This element indicates how an observed
condition has changed.

Error messages
Error messages provide information about problems that occur while running the
probe. You can use the information that they contain to resolve such problems.

The following table describes the error messages specific to this probe. For
information about generic Netcool/OMNIbus error messages, see the IBM Tivoli
Netcool/OMNIbus Probe and Gateway Guide.
Table 10. Error messages
Error Description Action
A problem while connecting to The probe could not Check that the
AlarmIRP or connect to AlarmIRP or Nokia-Siemens NetAct
NotificationIRPBAD_PARAM Exception NotificationIRP points server is running
i.e one or more of the in/out due to a problem with correctly.
parameter is null: +e the CORBA interface.
Refer to your CORBA
Cannot proceed. Shutting down! documentation.

CORBA.OBJECT_NOT_ EXIST exception

raised.

NotificationIRP is down!

InvalidParameter Exception

NetcoolIRPManager: Exception
occurred. Stack trace to stderr

OperationNotSupported Exception

Unexpected CORBA Exception

14 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
Table 10. Error messages (continued)
Error Description Action
Cannot initialize the Orb: " + e: The probe encountered Ensure that the
a problem during $CLASSPATH environment
initialization of the variable contains the
Object Request Broker path to the IBM ORB
(ORB). .jar files.
Command_Port Error occurred The probe encountered Check that you have
a problem with the specified the command
Command_Port Failed to get command port CLI port correctly.
CommandPortLimit property - using function.
10 Check the connection
between the probe and
Command_Port Failed to get property the command port.
CommandPort

Command_Port Failed to send

probewatch message!

Command_Port host Failed to close

command socket

Command_Port host Failed to get

socket IO

Command_Port host Failed to read

command

Command_Port Thread shutting down

due to error!

NetcoolIRPManager: Failed to
acknowledge_alarms()

NetcoolIRPManager: Failed to
Unacknowledge_ alarms()
Command_Port Thread shutting down The probe encountered Check that the
due to error! a problem with the CommandPort property
command port CLI has the correct value.
function.
Check that the
nco_p_nonnative process
is running correctly.
Command_Port Failed to open The probe could not Specify a different port
listening socket, shutting down open a listening socket in the CommandPort
Thread! on the command port property.
specified.
COMMUNICATION FAILURE Exception i.e The probe could not Check that the
Server is dead connect to the Nokia-Siemens NetAct
Nokia-Siemens NetAct server is running
GetSubscriptionStatus Exception server. correctly.

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

 Table 10. Error messages (continued)
Error Description Action
Error to parse event completely The probe cannot parse Check that the
the alarm. This is Nokia-Siemens NetAct
Failed to parse event completely probably because the server is running
alarm is in a format correctly.
Name is null, cannot create Element that the probe cannot
understand.
NetcoolIRPManager: Category Value
NOT supported: Discarding Alarm

NetcoolIRPManager: Error when

parsing event
Failed to get timeout property The probe could not Check the value of the
value, defaulting to 0 get the timeout value, Timeout property is
and is not going to correct. Change the
time out. value if necessary.
Failed to resolve the The probe could not Check that the
NotificationIRP object: " + e: resolve the NotificationIrpName
NotificationIRP object property has the correct
as the object is not value.
registered in the
NamingService.
Name is null, cannot create Element The probe could not Check whether the
create the matching default fields of the
element for an ObjectServer are
unknown field found in modified.
an alarm. Parsing of the
remaining known fields
continues.
NetcoolIRPManager: Failed to send The probe could not Check whether the
event send the parsed event ObjectServer is running
to the ObjectServer. correctly.
NetcoolIRPManager: Failed to The probe could not Check that the
retrieve AlarmIRP object from get either the AlarmIRP AlarmIrpName and
security interface or the NotificationIRP NotificationIrpName
object. (ex in the error properties have the
NetcoolIRPManager: Failed to message specifies the correct values.
retrieve NotificationIRP object related Java™
from security interface exception.)

login: Failed to get IRP object:

+ex

login: Unknown exception occured

+ex
NetcoolIRPManager: Failed to find The probe could not Check that the IRP
IOR file filename locate the IRP Manager Manager is set up
as the filename does not correctly.
exist.
NetcoolIRPManager: Stack Trace to The probe could not Use this message from
stderr: connect to AlarmIRP or the Netcool® IRP
NotificationIRP points Manager while
due to a problem with debugging.
the CORBA interface.

16 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
Table 10. Error messages (continued)
Error Description Action
NetcoolIRPManager: Notificationirp The probe could not Check that the
property needs to be set find one or more properties given in the
properties required to error message have the
NetcoolIRPManager: Both connect to the correct values.
NameServiceHost and NSPort property Nokia-Siemens NetAct
needs to be set server.
NetcoolIRPManager: Alarmirp
property needs to be set
Failed to resolve the AlarmIRP The AlarmIRP object is Check that AlarmIrpName
object : + e not registered in the property has the correct
Naming Service with value.
the AlarmIrpName
provided in the
properties file.
Failed to resolve the The NotificationIRP Check that the
NotificationIRP object : + e object is not registered NotificationIrpName
in the Naming Service property has the correct
with the value.
NotificationIrpName
provided in the
properties file.
NetcoolIRPManager: Failed to Failed to get either the Refer to your CORBA
retrieve AlarmIRP object from AlarmIRP or documentation.
security interface NotificationIRP object.
There is a problem with
NetcoolIRPManager: Failed to the CORBA interface.
retrieve NotificationIRP object
from security interface

Failed to narrow Security IRP

interface :" +ex'

Problem while trying to connect to

the IRP points : "+e

login: Failed to get IRP object : "

+ex

login: Unknown exception occured "

+ex
NetcoolIRPManager: Failed to find The probe could not Check that the IRP
IOR file '" +ior_file+ "' locate the IRP Manager Manager has been set
as the filename does not up correctly.
exist.
Failed to perform resynch There is a problem with Check that
the resynchronization Nokia-Siemens NetAct
Failed to ping notification service process. server is running
correctly. Check that you
have specified the
resynchronization
parameters correctly.

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

 Table 10. Error messages (continued)
Error Description Action
"Communication failure - lost The probe could not Check whether the
connection to NoticiationIRP: " +e connect to the Nokia-Siemens NetAct
NotificationIRP point server is still running.
“CORBA.TRANSIENT exception raised. in the Nokia-Siemens
NotificationIRP is down!" NetAct system.

"CORBA.OBJECT_NOT_EXIST exception
raised. NotificationIRP is down!"

"BAD_PARAM Exception i.e one or

more of the in/out parameter is
null: " +e

"CORBA Exception stack trace to

stderr: " +e

"Failed to Connect : " +e"

Either, the server is not running,

the IOR is out of date, or probe
cannot reach remote Server!"

"Failed to Connect : " +e"

Cannot proceed. Shutting down!"

NetcoolIRPManager: Failed to The probe could not Check that you have
acknowledge_alarms() : +e acknowledge the specified the command
alarms. port correctly.
NetcoolIRPManager: Failed to
Unacknowledge_alarms() : +e Check the connection
between the probe and
the command port.
NetcoolIRPManager: ERROR when The probe has a Ensure that the
parsing a notification event problem during $CLASSPATH environment
initialization of the variable contains the
NetcoolIRPManager: Stack Trace to ORB. path to the IBM ORB
stderr: + e .jar files.
NetcoolIRPManager: Failed to send The probe could not Check that the
event : +e forward the event to ObjectServer is still
the ObjectServer. running.
Name is null, cannot create Element The probe could not Check the log file that
find one of the stores the alarms for the
expected element for syntax error. If the probe
the event. is run in debug mode,
the alarm is printed in
the log file created by
the probe. Also check
that the alarm is in the
correct format.

Note: This inability of

the probe to create
element does not affect
the parsing of the rest of
the fields.

18 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
 Table 10. Error messages (continued)
Error Description Action
[Command Port] Failed to get The probe could not Check that the
CommandPortLimit property - using retrieve the value of the CommandPortLimit
10 CommandPortLimit property has the correct
property. value.

Note: As the default

value is set to 10, this
error does not affect the
behavior of the probe.
[Command Port] Failed to get The probe has failed to Check that the
property 'CommandPort unacknowledge the NV_ALARM_ID specified by
alarms. the CLI is correct.
[Command Port] Failed to open
listening socket, shutting down
Thread!

[Command Port] Thread shutting down

due to error!
[Command Port] Error occured :+e A problem occurred Check that the
while the user CommandPortLimit
attempted to connect to property has the correct
the CommandPort, or value.
while the user sent a
command.
[Command Port] host Failed to get There was a problem Check that you have
socket IO : "+e with command port specified the command
functionality. port correctly.

Check the connection

between the probe and
the command port.
[Command Port] host Failed to read The probe found that Check that you have
command : "+e there is a problem with specified the command
command port port correctly.
[Command Port] host Failed to close functionality.
command socket : +e Check the connection
between the probe and
the command port.

ProbeWatch messages
During normal operations, the probe generates ProbeWatch messages and sends
them to the ObjectServer. These messages tell the ObjectServer how the probe is
running.

The following table describes the ProbeWatch messages that the probe generates.
For information about generic Netcool/OMNIbus ProbeWatch messages, see the
IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

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

 Table 11. ProbeWatch messages
ProbeWatch message Description Triggers or causes
Communication failure - The probe has failed to get The notification service is not
lost connection to the subscription status from available.
NoticiationIRP the Notification IRP.

Failed to get
subscripton status

CORBA TIMEOUT Exception

while trying to get
subscription status from
NotificationIRP

Failed to connect to
NotificationIRP:
ae.reason Shutting down

Failed to Connect:
Either, the server is
not running, the IOR is
out of date, or probe
cannot reach remote
Server

CORBA.OBJECT _NOT_EXIST
Exception: Lost
connection to
NotificationIRP

CORBA.TRANSIENT
Exception: Lost
connection to
NotificationIRP
Connection to The probe has successfully The probe has successfully
NotificationIRP server established a connection to subscribed to the Notification
has been established the Notification IRP. service.
Detaching subscription The probe is disconnecting Either the probe has not
from the Notification IRP. received any events for the
specified timeout period, the
probe is shutting down, or the
probe has received a stop
signal.
END SYNCHRONIZATION The probe is closing the The probe has finished
synchronization process. receiving alarms from the
alarm list.

20 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
Table 11. ProbeWatch messages (continued)
ProbeWatch message Description Triggers or causes
Failed to get IRP The probe could not get either The AlarmirpName or
Outline (GetIRPOutline the AlarmIRP or the NotificationirpName
exception caught when Notification IRP object. properties have incorrect
calling get_IRP_outline) values.

Failed to get IRP

reference
(GetIRPReference
exception caught when
calling
get_IRP_reference)

Failed to get IRP

references - invalid
parameter
(InvalidParameter
exception caught when
calling
get_IRP_reference)
Failed to listen for The probe could not open the The specified port is in use for
commands on port number socket specified by the port to another process.
listening_port listen for commands.
Failed to log in to The probe could not login to The Nokia-Siemens NetAct
interface the Nokia NetAct 3GPP server is not running correctly.
(InvalidParameter server.
exception caught when There is a connection error
calling with the Nokia-Siemens
get_IRP_outline)s NetAct server.

The IOR is out of date.

The probe does not have

appropriate permissions
required to log in to the
Nokia-Siemens NetAct server.
Going Down The probe is shutting down. The probe has started shutting
down the connection.
Inactivity: No events The probe has exceeded the The probe did not receive
received for timeout time out period already set. events for the specified period.
seconds
Invalid IRPVersion The probe could not get the Incorrect value set for the
(InvalidIRPVersion Notification IRP object due to NotificationIrpVersion
exception caught when invalid IRP version. property.
calling
get_IRP_outline))
NetcoolIRPManager: The probe has failed to get The AlarmirpFile property in
Failed to find IOR file the IOR file specified. the properties file has an
alarmirp_ior_file incorrect value.
NetcoolIRPManager: The probe could not find the The AlarmirpFile or
Failed to find IOR file IOR file specified. NotificationirpFile
ior_file g properties have incorrect
values.

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

 Table 11. ProbeWatch messages (continued)
ProbeWatch message Description Triggers or causes
NetcoolIRPManager: The probe has failed to get The NotificationirpFile
Failed to find IOR file the IOR file. property has an incorrect
notificationirp_ior_ value.
file
PermissionDenied The probe could not login to The probe does not have
(PermissionDenied the Nokia-Siemens NetAct appropriate permissions
exception caught when server. required to log in to the
calling Nokia-Siemens NetAct server.
get_IRP_outline)s
Running The probe is successfully The probe has started
running. functioning.
START SYNCHRONIZATION The probe is synchronizing The probe has started
the events. receiving alarms from the
alarm list.
SYNCHRONIZATION FAILED The probe could not get new The probe failed to get the
alarms. alarm list, or failed to perform
resynchronization of alarms.
Unable to get events The probe could not get The probe has failed to get
events from Nokia-Siemens events.
NetAct.
Unexpected fatal error The probe has received a fatal The error message contains
when connecting to error message from the information about the cause of
interface GIF/FM process. the fatal error.

Unexpected fatal error

when getting IRP
reference from Entry
Point IRP

Unexpected fatal error

while getting IRP
Outline

Unexpected fatal error,

failed to connect
Will listen for commands The probe is listening for The port specified is ready to
on port number commands on the port receive commands.
listening_port specified.

22 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
Running the probe
Before running the probe for the first time, you must specify a minimum set of
properties.

Depending on which method you use to connect to the CORBA 3GPP interface,
you must specify values for the some of the following properties before running
the probe:
v AlarmIrpFile
v NetActServerName
v NotificationIrpFile
For more information about these properties, see “Connecting to the CORBA
interface” on page 4.

Use the following command to start the probe:

$OMNIHOME/probes/nco_p_nokia_netact_3gpp

Running multiple probes

You can run multiple instances of the probe on the same machine. For each
instance, specify a different port to which the server listens using the ORBLocalport
property and specify a unique instance identifier using the InstanceId property.

Shutting down the probe

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

Troubleshooting
Various issues arise as users work with the probe. This troubleshooting information
is provided to help you diagnose and resolve such issues.

IOR FileNotFound exception in the log file

The probe is running properly but the following error message appears in the log
file:

Error: Failed to retrieve old probe-IOR: java.io.FileNotFoundException:

/tmp/NetcoolIRPManager.ior (No such file or directory)

This issue arises because the IOR file is not available in the expected location the
first time the probe looks for it, but it is detected subsequently.

For example, if you specify a value of Nokia_Netact_R4_3 for the InstanceId

property, the probe will look for the following file in the /tmp directory on startup:

Nokia_Netact_R4_3_NetcoolIRPManager.ior

This file will not be available in this location the first time that you run the probe,
so the probe throws the error described above. The probe then continues to
connect to the Nokia-Siemens NetAct server and subsequently creates the IOR file
in the /tmp directory. The next time that the probe is started, it will detect the IOR
file in this directory.
IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA) 23
24 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
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 in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, 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 the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

© Copyright IBM Corp. 2007, 2012 25

 Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product 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 purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
U.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 material
available 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 controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should 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 the
suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

26 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA): Reference Guide
 COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs 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 or
imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must
include 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 rights
reserved.

If you are viewing this information softcopy, the photographs and color
illustrations 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-based
trademarks are either registered trademarks or trademarks of Adobe Systems
Incorporated 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. in the
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 other
countries.

Appendix. Notices and Trademarks 27

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


Printed in USA

SC23-7667-06