IBM® Tivoli® Netcool/OMNIbus Probe for

Nokia-Siemens NetAct 3GPP V6 (CORBA)

5.0

Reference Guide
November 04, 2011

IBM

SC22-5411-00
 Note
Before using this information and the product it supports, read the information in Appendix A, “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 NetAct
3GPP V6 (CORBA) and to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2011.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
Contents

About this guide.................................................................................................... v

Document Control Page............................................................................................................................... v
Conventions used in this guide.................................................................................................................... v

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA)............................... 1

Summary...................................................................................................................................................... 1
Installing probes.......................................................................................................................................... 2
Firewall considerations................................................................................................................................3
Configuring the lookup table........................................................................................................................4
Data acquisition........................................................................................................................................... 4
Connecting to the CORBA interface....................................................................................................... 4
Retrieving objects................................................................................................................................... 5
Status checking...................................................................................................................................... 5
Filtering notifications and alarms...........................................................................................................5
Command line interface......................................................................................................................... 8
Peer-to-peer failover functionality.........................................................................................................9
Running multiple probes...................................................................................................................... 10
Properties and command line options...................................................................................................... 10
Elements.................................................................................................................................................... 15
Error messages.......................................................................................................................................... 18
ProbeWatch messages.............................................................................................................................. 24
Running the probe..................................................................................................................................... 27

Appendix A. Notices and Trademarks................................................................... 29

Notices....................................................................................................................................................... 29
Trademarks................................................................................................................................................ 30

iii
iv
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 V6 (CORBA) documentation is
provided in softcopy format only. To obtain the most recent version, visit the IBM Documentation site:
https://www.ibm.com/support/knowledgecenter/SSSHTQ_int/omnibus/probes/common/Probes.html

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 previously documented in the same
reference guide as the Probe for Nokia-Siemens NetAct 3GPP V4 (CORBA). This reference guide
documents the Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) only.

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:

© Copyright IBM Corp. 2011 v

 $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

Red Hat Linux® and SUSE systems linux2x86

Linux for System z linux2s390

Solaris systems solaris2

Windows systems win32

OMNIHOME location
Probes and older versions of Tivoli Netcool/OMNIbus use the OMNIHOME environment variable in many
configuration files. Set the value of OMNIHOME as follows:
• On UNIX and Linux, set $OMNIHOME to $NCHOME/omnibus.
• On Windows, set %OMNIHOME% to %NCHOME%\omnibus.

vi IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6
(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 V6 (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 6.2.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 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:

• “Summary” on page 1
• “Installing probes” on page 2
• “Firewall considerations” on page 3
• “Configuring the lookup table” on page 4
• “Data acquisition” on page 4
• “Properties and command line options” on page 10
• “Elements” on page 15
• “Error messages” on page 18
• “ProbeWatch messages” on page 24
• “Running the probe” on page 27

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 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 which this probe
is supported, see the following page on the IBM Tivoli Netcool
Knowledge 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 Tivoli Netcool/OMNIbus:

• V7.2.0 with Interim Fix 4 (7.2.0.7-IF0004) installed
• V7.2.1 with Interim Fix 3 (7.2.1.5-IF0003) installed
• V7.3.0
• V7.3.1
Nonnative Probe Server: probe-nonnative-base-14
IBM Object Request Broker (IBM ORB, supplied with Netcool/
OMNIbus)
Java™ Runtime Environment (JRE) 1.5

Connection method CORBA

Multicultural support Available

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

Federal Information Processing IBM Tivoli Netcool/OMNIbus uses the FIPS 140-2 approved
Standards (FIPS) 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 the 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.

2 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
 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 IBM
Documentation:
https://www.ibm.com/support/knowledgecenter/SSSHTQ_int/omnibus/probes/all_probes/wip/
reference/install_download_intro.html
2. Installing the probe using the installation package.
The installation package contains the appropriate files for all 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 in IBM Documentation:
https://www.ibm.com/support/knowledgecenter/SSSHTQ_int/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.

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 3

Configuring the lookup table
The probe is supplied with a lookup table that contains details of the various types of alarms that Nokia-
Siemens NetAct generates. You might need to update the rules file to include the path to the lookup table.
At installation, the Corba_3gpp_V620.lookup file supplied with the probe installation 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 rules file:
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 different directory, use the absolute directory path to the
lookup table. Do not use the $OMNIHOME environment variable in this directory path.

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:
• “Connecting to the CORBA interface” on page 4
• “Retrieving objects” on page 5
• “Status checking” on page 5
• “Filtering notifications and alarms” on page 5
• “Command line interface” on page 8
• “Peer-to-peer failover functionality” on page 9
• “Running multiple probes” on page 10

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 AlarmIRP and NotificationIRP CORBA objects form a part of the IRP agent to which the probe
connects.
Depending on your operating environment, use one of the following connection configurations:
1. Option 1 - specify values for the following properties:
• NetActServerName - the name of the Nokia-Siemens NetAct server to which the probe connects to
retrieve the Naming Context IOR file.
• NetActServerPort - the port on the Nokia-Siemens NetAct server through which the probe
connects to retrieve the Naming Context IOR file.
• NamingServiceIORRequest - specify the command that the probe uses to upload the CORBA
Naming Service IOR.
• AlarmIrpName - specify the name used to resolve the Alarm IRP in the CORBA Naming Service.
• NotificationIrpName - specify the name used to resolve the Notification IRP in the CORBA
Naming Service.
2. Option 2 - specify values for the following properties:
• NamingServiceHost - specify the name of the host machine where the CORBA Naming Service is
running.

4 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
 • NamingServicePort - specify the port on which the CORBA Naming Service listens.
• AlarmIrpName - specify the name used to resolve the Alarm IRP in the CORBA Naming Service.
• NotificationIrpName - specify the name used to resolve the Notification IRP in the CORBA
Naming Service.
3. Option 3 - specify values for the following properties:
• EntryPointIrpFile - specify the location of the file that contains the IOR of the EntryPoint IRP
object.
• NotificationIrpName - specify the name used to resolve the Notification IRP in the CORBA
Naming Service.
• AlarmIrpName - specify the name used to resolve the Alarm IRP in the CORBA Naming Service.

Retrieving objects
If the Resynch property is set to true, the probe initially receives a list of all active alarms from the
AlarmIRP server.
The probe then connects to the NotificationIRP server and uses the CORBA notification push model to
receive new alarms from the server as they are generated. If the Resynch property is set to false, the
probe only receives new alarms.

Status checking
This 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 this frequency if required
using the Agentheartbeat property.

Filtering notifications and alarms

This section 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_EVENT_TIME

c NV_SYSTEM_DN

d NV_MANAGED_OBJECT_CLASS

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 5

 Table 5. Token/element mappings (continued)

Token Element

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

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

6 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Table 5. Token/element mappings (continued)

Token Element

z CLEAR_SYSTEM_ID

Filters
This section describes the filters that help retrieve matching elements.
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

Valid filters
The following filters 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)

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 7

 Invalid filters
The following filters 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 interface

The probe has a command line interface (CLI) that you can use to issue commands.
To use the CLI, use the CommandPort property to specify a port through which commands 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 an alarm in

the 3GPP interface.
Note: This command takes as a parameter the
NV_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 the CLI.

resynch_all This command allows you to perform a full

resynchonization with the 3GPP interface.
Note: Successful resynchronization requires that the
Resynch property is set to true.

resynch_filter This command allows you to a perform partial

resynchronization with the 3GPP interface.
Note: This command takes as a parameter a filter in the
same format as the AlarmFilter property. For details,
see “Filtering notifications and alarms” on page 5.

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 This command allows you to acknowledge an alarm in

the 3GPP interface by specifying the NV_ALARM_ID and
NV_ACK_USER_ID parameters. These parameters are
specified by the AckSystemId and AckUserId
properties.

userid_clear_alarm userid This command allows you to clear an alarm created by a

specific user ID.

8 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
 Table 7. CLI commands (continued)

Command Description

userid_unacknowledge_alarm This command allows you to un-acknowledge an alarm in

the 3GPP interface by specifying the NV_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 from anywhere. This means
that simple scripts can be set up to allow users to acknowledge selected events from the Netcool/
OMNIbus event list. You can create desktop tools that use Telnet to connect to the probe, send a
command, and then close the connection.

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 probe 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 probe is running again, the slave probe 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 : 6789 # [communication port between master and slave probe]
Mode : "master"
PidFile : "master_pid_file"

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 : 6789 # [communication port between master and slave probe]
Mode : "slave"
PidFile : "slave_pid_file"

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 9

Running multiple probes
You can run multiple instances of the probe.
For each running instance, specify a different port to which the server listens using the ORBLocalPort
property.

Running multiple probes in a failover configuration

If you have implemented a peer-to-peer failover configuration, both the master probe and the slave probe
have their own Object Request Broker (ORB) local port.
Where you are running this configuration in conjunction with a firewall, add the receiving port of each
probe to the firewall rules. The direction of the 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 and slave probes.
Include the following peer-to-peer settings in the master's probe properties file:

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

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

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

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
information about default properties and command line options, see the 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 the

processing system on which the IRP
Manager runs. This is used by the
acknowledge_alarm CLI function.
The default is "".

AckUserId string -ackuserid string Use this property to specify the name of
the user acknowledging the alarm. This
is used by the acknowledge_alarm CLI
function.
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.

10 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Table 8. Properties and command line options (continued)

Property name Command line option Description

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

AlarmIrpName string -alarmirpname string Use this property to specify the name of
the Alarm IRP Agent used by the Naming
Service.
The default is 32.111-3 V6.2.
Note: The value of this property can
differ between NetAct systems. For
example, it might take the following
format:
NokiaNetact3gppv6AlarmIRP.

BeatInterval integer -beatinterval integer Use this property to specify the

heartbeat interval for peer-to-peer
failover.
The default is 2.

ClearSystemId string -clearsystemid string Use this property to specify the system
identifier that the
userid_clear_alarms CLI command
clears.
The default is "".

ClearUserId string -clearuserid string Use this property to specify the user
clearing the alarms using the
userid_clear_alarms CLI command.
The default is "".

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.
For details about the CLI, see “Command
line interface” on page 8.
The default is 6970.

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.

EntryPointIrpFile -entrypointirpfile string Use this property to specify the location

string of the file that contains the IOR of the
EntryPoint IRP object.
The default is "".

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 11

 Table 8. Properties and command line options (continued)

Property name Command line option Description

FlushBufferInterval -flushbufferinterval Use this property to specify how often (in

integer integer 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 "".

Mode string -mode string Use this property to specify the role of an
instance of the probe in a peer-to-peer
failover relationship. This property takes
the following values:
master: The instance is the master
probe.
slave: The instance is the slave probe.
standard: There is no failover
relationship.
The default is standard.

NamingServiceIOR -namingserviceiorrequest Use this property to specify the

Request string string command that the probe uses to upload
the CORBA Naming Service IOR.
The default is GET /cgi-bin /
get_nbif_ior.

NamingServiceHost -namingservicehost string Use this property to specify the host

string running the CORBA Naming Service.
The default is localhost.

NamingServicePort -namingserviceport integer Use this property to specify the port on

integer which the CORBA Naming Service
listens.
The default is 5001.

NetActServerName -netactservername string Use this property to specify the name of

string the Nokia-Siemens NetAct server to
which the probe connects to retrieve the
Naming Context IOR file.
The default is "".

12 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Table 8. Properties and command line options (continued)

Property name Command line option Description

NetActServerPort -netactserverport integer Use this property to specify the port on

integer the Nokia-Siemens NetAct server
through which the probe connects to
retrieve the Naming Context IOR file.
The default is 10115.

Notification -notificationcategories Use this property to specify the

Categories string string notification categories that the probe
subscribes to.
The default is "" (the probe subscribes
to all categories).
Note: To specify multiple categories,
separate them using semicolons, in the
following format:
category1; category2;
categoryn
For example, to subscribe to the alarms
and heartbeat events, use the following
value:
ALARM IRP V1.0.0; CS IRP
V1.0.0

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

NotificationIrpName -notificationirpname string Use this property to specify the name of

string the Notification IRP Agent used by the
Naming Service.
The default is 32.303 V6.1.
Note: The value of this property can
differ between NetAct systems. For
example, it might take the following
format:
NokiaNetact3gppv6NotificationI
RP

ORBCharEncoding string -orbcharencoding string Use this property to specify the native
character encoding set used by the
Object Request Broker (ORB) for
character data.
The default is UTF8.
This property can also take the value
ISO8859_1.

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 13

 Table 8. Properties and command line options (continued)

Property name Command line option Description

ORBLocalHostName -orblocalhostname string Use this property to specify the local

string host name used by the server-side ORB
to place the server's host name into the
IOR of a remote object.
The default is "".

ORBLocalPort integer -orblocalport integer Use this property to specify the local port
to which the ORB listens.
The default is 0 (the ORB selects an
available port at random).

ORBWCharDefault string -orbwchardefault string Use this property to specify what wide
character (wchar) set the IBM ORB uses
when communicating with other ORBs
that do not publish a wchar set.
The default is UTF16.
This property can also take the value
UCS2.

PeerHost string -peerhost string Use this property to specify the host to
which the probe fails over in a peer-to-
peer failover configuration.
The default is localhost.

PeerPort integer -peerport integer Use this property to specify the port
through which the master and slave
probes communicate in a peer-to-peer
failover configuration.
The default is 9999.

Resynch string -resynch (This is equivalent to Use this property to specify whether the
Resynch with a value of true.) probe requests all active alarms from the
Nokia-Siemens NetAct system before
-noresynch (This is equivalent
connecting to the notification service for
to Resynch with a value of
new alarms. This property takes the
false.)
following values:
false: The probe does not perform
resynchronization.
true: The probe performs
resynchronization at startup.
The default is false.

14 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
 Table 8. Properties and command line options (continued)

Property name Command line option Description

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.

TimeTick integer -timetick integer Use this property to specify the lifetime
(in minutes) of the Notification IRP
session on the 3GPP server.
The default is 0 (there is no time limit for
the session).

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 generates. Not all the elements described are
generated for each event. The elements that the probe generates depend on 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.

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.

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 15

 Table 9. Elements (continued)

Element name Element description

CLEAR_SYSTEM_ID This element indicates whether the system

identifier has been cleared.

CLEAR_USER_ID This element indicates whether the user

identifier has been cleared.

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_ALARM_LIST_ALIGNMENT_ REQUIREMENT This element indicates whether the alarm list

requires alignment.

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_COMMENTS This element contains the comment about the

alarm.

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.

16 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Table 9. Elements (continued)

Element name Element description

NV_CORRELATED_NOTIFICATIONS_ SOURCE This element contains the source of the

notification set.

NV_EVENT_TIME This element contains the time at which the

event occurred.

NV_MANAGED_OBJECT_CLASS This element shows the managed object class

of the network resource.

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.

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_SECURITY_ALARM_DETECTOR This element contains the identifier of the

detector of the security alarm.

NV_SERVICE_PROVIDER This element contains the name of the service

provider.

NV_SERVICE_USER This element contains further information about

the problem that the notification relates to.

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.

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 17

 Table 9. Elements (continued)

Element name Element description

NV_TREND_INDICATION This element indicates how an observed

condition has changed.

NV_VENDOR_SPECIFIC_ALARM_TYPE This element contains the alarm type specific to

the vendor.

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

Table 10. Error messages

Error Description Action

A problem while connecting to The probe could not Check that the Nokia-
AlarmIRP or connect to AlarmIRP or Siemens NetAct server is
NotificationIRPBAD_PARAM Exception NotificationIRP points running correctly.
i.e one or more of the in/out due to a problem with the
Refer to your CORBA
parameter is null: +e CORBA interface.
documentation.
Cannot proceed. Shutting down!
CORBA.OBJECT_NOT_ EXIST exception
raised.
NotificationIRP is down!
InvalidParameter Exception
NetcoolIRPManager: Exception
occurred. Stack trace to stderr
OperationNotSupported Exception
Unexpected CORBA Exception

Cannot initialize the Orb: " + e: The probe encountered a Ensure that the
problem during $CLASSPATH environment
initialization of the Object variable contains the path
Request Broker (ORB). to the IBM ORB .jar files.

18 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Table 10. Error messages (continued)

Error Description Action

Command_Port Error occurred The probe encountered a Check that you have
problem with the specified the command port
Command_Port Failed to get
command port CLI correctly.
CommandPortLimit property - using
function.
10 Check the connection
between the probe and the
Command_Port Failed to get
command port.
property 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 a Check that the
due to error! problem with the CommandPort property has
command port CLI the correct value.
function.
Check that the
nco_p_nonnative
process is running correctly.

Command_Port Failed to open The probe could not open Specify a different port in
listening socket, shutting down a listening socket on the the CommandPort property.
Thread! command port specified.

COMMUNICATION FAILURE Exception The probe could not Check that the Nokia-
i.e Server is dead connect to the Nokia- Siemens NetAct server is
Siemens NetAct server. running correctly.
GetSubscriptionStatus Exception

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

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 19

 Table 10. Error messages (continued)

Error Description Action

Failed to get timeout property The probe could not get Check the value of the
value, defaulting to 0 the timeout value, and is Timeout property is
not going to time out. correct. Change the value if
necessary.

Failed to connect to the Naming The probe could not Check that the
Context: " + e: connect to the NamingServiceHost and
NamingContext. NamingServicePort
properties have the correct
values.

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 The probe could not create Check whether the default
Element the matching element for fields of the ObjectServer
an unknown field found in are modified.
an alarm. Parsing of the
remaining known fields
continues.

NetcoolIRPManager: Failed to send The probe could not send Check whether the
event the parsed event to the ObjectServer is running
ObjectServer. correctly.

NetcoolIRPManager: Failed to The probe could not get Check that the
retrieve AlarmIRP object from either the AlarmIRP or AlarmIrpName and
security interface the NotificationIRP NotificationIrpName
object. (ex in the error properties have the correct
NetcoolIRPManager: Failed to
message specifies the values.
retrieve NotificationIRP object
related Java exception.)
from security interface
login: Failed to get IRP object:
+ex
login: Unknown exception occured
+ex

NetcoolIRPManager: Failed to find The probe could not locate Check that the IRP Manager
IOR file filename the IRP Manager as the is set up correctly.
filename does not exist.

NetcoolIRPManager: Failed to The probe could not Check that Nokia-Siemens

perform resynch resynchronize the alarms. NetAct server is running
correctly.
Failed to perform resynch
Check that the Resynch
Failed to iterate through resynch
property has the correct
alarms
value.

20 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Table 10. Error messages (continued)

Error Description Action

NetcoolIRPManager: Stack Trace to The probe could not Use this message from the
stderr: connect to AlarmIRP or Netcool® IRP Manager while
NotificationIRP points debugging.
due to a problem with the
CORBA interface.

NetcoolIRPManager: Notificationirp The probe could not find Check that the properties
property needs to be set one or more properties given in the error message
required to connect to the have the correct values.
NetcoolIRPManager: Both
Nokia-Siemens NetAct
NameServiceHost and NSPort
server.
property needs to be set
NetcoolIRPManager: Alarmirp
property needs to be set

Failed to connect to the Naming The probe cannot connect Check that
Context : + e to the NamingContext. theNamingServiceHost
and NamingServicePort
properties have the correct
values.

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 the value.
AlarmIrpName provided
in the properties file.

Failed to resolve the The NotificationIRP Check that the

NotificationIRP object : + e object is not registered in NotificationIrpName
the Naming Service with property has the correct
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
NetcoolIRPManager: Failed to
with 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

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 21

 Table 10. Error messages (continued)

Error Description Action

NetcoolIRPManager: Failed to find The probe could not locate Check that the IRP Manager
IOR file '" +ior_file+ "' the IRP Manager as the has been set up correctly.
filename does not exist.

Failed to perform resynch There is a problem with Check that Nokia-Siemens

the resynchronization NetAct server is running
Failed to ping notification
process. correctly. Check that you
service
have specified the
resynchronization
parameters correctly.

"Communication failure - lost The probe could not Check whether the Nokia-
connection to NoticiationIRP: " +e connect to the Siemens NetActserver is
NotificationIRP point 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!"

Failed to iterate through resynch The probe failed to get the Check that the Nokia-
alarms alarm list or failed to Siemens NetAct server is
perform resynchronization running correctly.
of alarms.
Check that the Resynch
property is set correctly.

NetcoolIRPManager: Failed to The probe could not Check that you have
acknowledge_alarms() : +e acknowledge the alarms. specified the command 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 problem Ensure that the
parsing a notification event during initialization of the $CLASSPATH environment
ORB. variable contains the path
NetcoolIRPManager: Stack Trace to
to the IBM ORB .jar files.
stderr: + e

22 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Table 10. Error messages (continued)

Error Description Action

NetcoolIRPManager: Failed to send The probe could not Check that the ObjectServer
event : +e forward the event to the is still running.
ObjectServer.

Name is null, cannot create The probe could not find Check the log file that
Element one of the expected stores the alarms for the
element for the event. syntax error. If the probe 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.

[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 while Check that the
the user attempted to CommandPortLimit
connect to the property has the correct
CommandPort, or while value.
the user sent a command.

[Command Port] host Failed to get There was a problem with Check that you have
socket IO : "+e command port specified the command port
functionality. correctly.
Check the connection
between the probe and the
command port.

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 23

 Table 10. Error messages (continued)

Error Description Action

[Command Port] host Failed to read The probe found that there Check that you have
command : "+e is a problem with specified the command port
command port correctly.
[Command Port] host Failed to
functionality.
close 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 raw ProbeWatch error messages that the probe generates. For
information about generic error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide
(SC14-7608).

Table 11. ProbeWatch messages

ProbeWatch message Description Triggers or causes

Communication failure The probe has failed to get the The notification service is not
- lost connection to subscription status from the available.
NoticiationIRP 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

24 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Table 11. ProbeWatch messages (continued)

ProbeWatch message Description Triggers or causes

Connection to The probe has successfully The probe has successfully

NotificationIRP server established a connection to the subscribed to the Notification
has been established Notification IRP. service.

Detaching subscription The probe is disconnecting from Either the probe has not received
the Notification IRP. 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 receiving
synchronization process. alarms from the alarm list.

Failed to get IRP The probe could not get either the The AlarmirpName or
Outline (GetIRPOutline AlarmIRP or the Notification IRP NotificationirpName
exception caught when object. properties have incorrect values.
calling
get_IRP_outline)
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 socket specified by the port to another process.
number listening_port listen for commands.

Failed to log in to The probe could not login to the The Nokia-Siemens NetAct server
interface Nokia NetAct 3GPP server. is not running correctly.
(InvalidParameter
There is a connection error with the
exception caught when
Nokia-Siemens NetAct server.
calling
get_IRP_outline)s 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.

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 25

 Table 11. ProbeWatch messages (continued)

ProbeWatch message Description Triggers or causes

Inactivity: No events The probe has exceeded the time The probe did not receive events
received for timeout out period already set. 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 property.
exception caught when invalid IRP version.
calling
get_IRP_outline))

NetcoolIRPManager: The probe has failed to get the The AlarmirpFile property in the
Failed to find IOR IOR file specified. properties file has an incorrect
file alarmirp_ior_file value.

NetcoolIRPManager: The probe could not find the IOR The AlarmirpFile or
Failed to find IOR file specified. NotificationirpFile
file ior_file g properties have incorrect values.

NetcoolIRPManager: The probe has failed to get the The NotificationirpFile

Failed to find IOR IOR file. property has an incorrect value.
file
notificationirp_ior_
file

PermissionDenied The probe could not login to the The probe does not have
(PermissionDenied Nokia-Siemens NetAct server. appropriate permissions required
exception caught when to log in to the Nokia-Siemens
calling NetAct server.
get_IRP_outline)s

Running The probe is successfully running. The probe has started functioning.

START SYNCHRONIZATION The probe is synchronizing the The probe has started receiving
events. alarms from the alarm list.

SYNCHRONIZATION FAILED The probe could not get new The probe failed to get the alarm
alarms. list, or failed to perform
resynchronization of alarms.

Unable to get events The probe could not get events The probe has failed to get events.
from Nokia-Siemens NetAct.

26 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
 Table 11. ProbeWatch messages (continued)

ProbeWatch message Description Triggers or causes

Unexpected fatal error The probe has received a fatal The error message contains
when connecting to error message from the GIF/FM information about the cause of the
interface process. 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 The probe is listening for The port specified is ready to
commands on port commands on the port specified. receive commands.
number listening_port

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 properties described in “Connecting to the CORBA interface” on page 4.
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 each running instance, use the
ORBLocalport property to specify a different port to which the server listens. You must also specify a
unique identifier for the probe instance 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.

Chapter 1. Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA) 27

28 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
Appendix A. Notices and Trademarks
This appendix contains the following sections:
• Notices
• 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.
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

© Copyright IBM Corp. 2011 29

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

30 IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens NetAct 3GPP V6 (CORBA): Reference Guide
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 A. Notices and Trademarks 31

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

SC22-5411-00