Probe for Nokia-Siemens Switch/Radio/@vantage … using the Windows command line with these probes, ... 2 Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5:

IBM® Tivoli® Netcool/OMNIbus Probe for Nokia-SiemensSwitch/Radio/@vantage Commander (CORBA) 3GPP V5.5Version 1.0

Reference GuideNovember 30, 2012

SC23-7668-03

��

IBM® Tivoli® Netcool/OMNIbus Probe for Nokia-SiemensSwitch/Radio/@vantage Commander (CORBA) 3GPP V5.5Version 1.0

Reference GuideNovember 30, 2012

SC23-7668-03

��

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

Edition notice

This edition (SC23-7668-03) applies to version 1.0 of the IBM Tivoli Netcool/OMNIbus Probe for Nokia-SiemensSwitch/Radio/@vantage Commander (CORBA) 3GPP V5.5 and to all subsequent releases and modifications untilotherwise indicated in new editions.

This edition replaces SC23-7668-02.

© Copyright IBM Corporation 2006, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this guide . . . . . . . . . . . vDocument control page . . . . . . . . . . . vConventions used in this guide . . . . . . . . vi

IBM Tivoli Netcool/OMNIbus Probe forNokia-Siemens Switch/Radio/@vantageCommander (CORBA) 3GPP V5.5 . . . . 1Summary . . . . . . . . . . . . . . . 2Installing probes . . . . . . . . . . . . . 2Setting environment variables . . . . . . . . 3Firewall considerations . . . . . . . . . . . 3Data acquisition . . . . . . . . . . . . . 4

Connecting to the CORBA interface. . . . . . 4Retrieving objects . . . . . . . . . . . . 5Filtering notifications and alarms . . . . . . 5

Lookup table . . . . . . . . . . . . . 6IRP Agent status . . . . . . . . . . . . 7Command line interface . . . . . . . . . 7Peer-to-peer failover functionality . . . . . . 8

Properties and command line options . . . . . . 9Elements . . . . . . . . . . . . . . . 12Error messages . . . . . . . . . . . . . 13ProbeWatch messages . . . . . . . . . . . 16Running the probe . . . . . . . . . . . . 17

Running multiple probes . . . . . . . . . 18

Appendix. Notices and Trademarks . . 19Notices . . . . . . . . . . . . . . . . 19Trademarks . . . . . . . . . . . . . . 21

© Copyright IBM Corp. 2006, 2012 iii

iv Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5: Reference Guide

About this guide

The following sections contain important information about using this guide.

Document control pageUse this information to track changes between versions of this guide.

The IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5 documentation is provided in softcopyformat only. To obtain the most recent version, visit the IBM® Tivoli® KnowledgeCenter:

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

Table 1. Document modification history

Documentversion Publication date Comments

SC23-7668-00 October 9, 2006 First IBM publication.

SC23-7668-01 October 31, 2010 “Summary” on page 2 updated.

SC23-7668-02 March 31, 2011 Installation section replaced by “Installing probes”on page 2.

“Firewall considerations” on page 3 added.

SC23-7668-03 November 30, 2012 Removed references to the Probe forNokia-Siemens Switch/Radio/@vantageCommander (CORBA) 3GPP V6.3.

Information about operating system conventionsadded in “Conventions used in this guide” onpage vi.

Multicultural support information added in“Summary” on page 2.

Note: The Probe for Nokia-Siemens Switch/Radio/@vantage Commander(CORBA) 3GPP V5.5 (nco_p_siemens_corba_v1) was previously documented in thesame reference guide as the Probe for Nokia-Siemens Switch/Radio/@vantageCommander (CORBA) 3GPP V6.3 (nco_p_siemens_corba_v2). This reference guidedocuments the Probe for Nokia-Siemens Switch/Radio/@vantage Commander(CORBA) 3GPP V5.5 only.

© Copyright IBM Corp. 2006, 2012 v



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

Operating system-dependent variables and paths

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

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

$OMNIHOME/probes

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

%OMNIHOME%\probes

For probes supported on UNIX, Linux, and Windows operating systems, probeguides use the standard UNIX conventions for specifying environment variablesand describing directory paths. When using the Windows command line withthese probes, replace the UNIX conventions used in the guide with Windowsconventions. If you are using the bash shell on a Windows system, you can use theUNIX conventions.

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

Operating system-specific directory names

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

$OMNIHOME/probes/arch

The following table lists the directory names used for each operating system.

Note: This probe may not support all of the operating systems specified in thetable.

Table 2. Directory names for the arch variable

Operating system Directory name represented by arch

AIX® systems aix5

HP-UX PA-RISC-based systems hpux11

HP-UX Integrity-based systems hpux11hpia

Red Hat Linux and SUSE systems linux2x86

vi Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5: Reference Guide

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 OMNIHOMEenvironment variable in many configuration files. Set the value of OMNIHOME asfollows:v On UNIX and Linux, set $OMNIHOME to $NCHOME/omnibus.v On Windows, set %OMNIHOME% to %NCHOME%\omnibus.

About this guide vii

viii Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5: Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for Nokia-SiemensSwitch/Radio/@vantage Commander (CORBA) 3GPP V5.5

The IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5 collects alarms from theNokia-Siemens Switch Commander, Radio Commander, and @vantage Commanderelement management systems (EMS).

The probe collects alarms from the Nokia-Siemens EMS using the Common ObjectRequest Broker Architecture (CORBA) 3rd Generation Partnership Project (3GPP)V5.5 interface.

The probe complies with the following 3GPP standards:

Table 3. Supported 3GPP standards

3GPP TechnicalSpecification Version Object

32.111-3 5.5.1 Alarm Integration Reference Point (IRP)

32.303 5.2.0 Notification IRP

32.623 5.2.0 Generic Network

This guide contains the following sections:v “Summary” on page 2v “Installing probes” on page 2v “Setting environment variables” on page 3v “Firewall considerations” on page 3v “Data acquisition” on page 4v “Properties and command line options” on page 9v “Elements” on page 12v “Error messages” on page 13v “ProbeWatch messages” on page 16v “Running the probe” on page 17

© Copyright IBM Corp. 2006, 2012 1

SummaryEach probe works in a different way to acquire event data from its source, andtherefore has specific features, default values, and changeable properties. Use thissummary information to learn about this probe.

The following table provides a summary of the probe.

Table 4. Summary

Probe target Nokia-Siemens CORBA 3GPP V5.5 interface

Probe executable name nco_p_siemens_corba_v1

Probe installation package omnibus-arch-probe-nco-p-siemens-corba-v1-version

Package version 1.0

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

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

Requirements For details of any additional software that this proberequires, refer to the description.txt file that issupplied in its download package.

Connection method CORBA

Multicultural support Available

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

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

Federal Information ProcessingStandards (FIPS)

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

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

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

Advantage Online website.Each probe has a single installation package for each operating systemsupported. For details about how to locate and download the installationpackage for your operating system, visit the following page on the IBM TivoliKnowledge Center:http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html

2. Installing the probe using the installation package.

2 Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5: Reference Guide

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

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

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html

The installation package contains the appropriate files for all supportedversions of Netcool/OMNIbus. For details about how to install the probe torun with your version of Netcool/OMNIbus, visit the following page on theIBM Tivoli Knowledge Center:http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

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

Setting environment variablesEnvironment variables are specific preset values that establish the probe's workingenvironment.

After installing the probe, you must include the following directory path as thefirst entry in the $PATH environment variable:

jre_directory/bin

where jre_directory is the location of your Java Runtime Environment (JRE) files.

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

Most CORBA probes can act as both a server (listening for connections from thetarget system) and a client (connecting to the port on the target system to whichthe system writes events). If you are using the probe in conjunction with a firewall,you must add the appropriate firewall rules to enable this dual behavior.

There are three possible firewall protection scenarios, for which you mustdetermine port numbers before adding firewall rules:1. If the host on which the probe is running is behind a firewall, you must

determine what remote host and port number the probe will connect to.2. If the host on which the target system is running is behind a firewall, you must

determine the incoming port on which the probe will listen and to which thetarget system will connect.

3. If each host is secured with its own firewall, you must determine the followingfour ports:a. The outgoing port (or port range) for the probe.b. The hostname and port of the target system.c. The outgoing port on which the target system sends events if the probe 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 theORBLocalPort property. The default value for this property is 0, which means that

IBM Tivoli Netcool/OMNIbus Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5 3

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

an available port is selected at random. If the probe is behind a firewall, the valueof the ORBLocalPort property must be specified as a fixed port number.

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

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

The probe gathers alarms from the Nokia-Siemens EMS using the CORBA 3GPPinterface.

Data acquisition is further described in the following topics:v “Connecting to the CORBA interface”v “Retrieving objects” on page 5v “Filtering notifications and alarms” on page 5v “Lookup table” on page 6v “IRP Agent status” on page 7v “Command line interface” on page 7v “Peer-to-peer failover functionality” on page 8

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

The AlarmIRPOperation and NotificationIRPOperation points form a part of theIRP Agent to which the probe connects.

The probe uses one of the following methods to make a connection:v Interoperable Object Reference (IOR) filesv Naming Service

Using IOR files

The probe gets the object references of the AlarmIrpName and NotificationIrpNameobjects from the IOR files specified by the AlarmIrpFile and NotificationIrpFileproperties.

Using a Naming Service

If the AlarmIrpFile and NotificationIrpFile properties are not specified, theprobe gets the object references of the AlarmIRPOperation andNotificationIRPOperation points from the Naming Service.

The probe uses the values of the NamingServiceHost and NamingServicePortproperties to locate the Naming Service.


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

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

Filtering notifications and alarmsYou can specify the notifications and alarms that the probe receives from the targetdevice using the NotificationFilter and AlarmFilter properties.

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

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

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

Specifying specific managed elements

To ensure that the probe is only sent notifications for a specific managed element,specify a value of Managed_Node_Name~$f for the NotificationFilter property,where Managed_Node_Name is the name of the managed object and $f representsthe element NV_MANAGED_OBJECT_INSTANCE.

For example, if you require a set of alarms that return a value ofSubNetwork=ONRM_RootMo, SubNetwork=SNMP, ManagedElement=SP1 for theNV_MANAGED_OBJECT_INSTANCE element, specify the following value for theNotificationFilter property:

SP1'~$'f

Note: When specifying values for the NotificationFilter property, you mustreplace spaces with the tilde character (~). For string comparisons, the firstargument is considered to be contained in the second argument, which is why $f ispositioned after the literal.

Token/element mappings

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

Table 5. Token/element mappings

Token Element

a NV_NOTIFICATION_ID

b NV_CORRELATED_NOTIFICATIONS

c NV_EVENT_TIME

d NV_SYSTEM_DN


Table 5. Token/element mappings (continued)

Token Element

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

t NV_STATE_CHANGE_DEFINITION

u NV_MONITORED_ATTRIBUTES

v NV_PROPOSED_REPAIR_ACTIONS

w NV_REASON

Lookup tableThe probe is supplied with a lookup table that contains details of the various typesof alarms that the Nokia-Siemens EMS generates.

At installation, the Corba_3gpp_ V551.lookup file supplied with the probeinstallation 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_ V551.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 differentdirectory, replace “..” with the absolute directory path to the lookup table. Do notuse the $OMNIHOME environment variable in this directory path.


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

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

Command line interfaceThe probe is supplied with a command line interface (CLI). This interface enablesyou to execute commands to acknowledge alarms or request a fullresynchronization in the CORBA interface.

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

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

Table 6. CLI commands

Command Description

acknowledge_alarm alarm_id Use this command to acknowledge an alarm inthe CORBA interface by specifying the identifier(NV_ALARM_ID) of the alarm.

Before you can use this command, you mustspecify a value for the AckSystemId property.

userid_acknowledge_alarm alarm_iduser_id

Use this command to unacknowledge an alarm inthe CORBA interface by specifying the identifier(NV_ALARM_ID) of the alarm and the user identifier(NV_ACK_USER_ID) of the user acknowledging thealarm.


If you specify a value for the AckUserId property,the user_id parameter is not required.

unacknowledge_alarm alarm_id Use this command to unacknowledge an alarm inthe CORBA interface by specifying the identifier(NV_ALARM_ID) of the alarm.


userid_unacknowledge_alarm alarm_iduser_id

Use this command to unacknowledge an alarm inthe CORBA interface by specifying the identifier(NV_ALARM_ID) of the alarm and the user identifier(NV_ACK_USER_ID) of the user acknowledging thealarm.


If you specify a value for the AckUserId property,the user_id parameter is not required.

resynch_all Use this command to perform a fullresynchronization with the CORBA interface.


Table 6. CLI commands (continued)

Command Description

resynch_filter filter Use this command to perform a partialresynchronization with the CORBA interface.

The filter parameter uses the same filter format asthe AlarmFilter property.

help This command displays online help about theCLI.

exit/quit This command closes the connection.

version This command displays the version of the probe.

CLI scripts

Because the CLI uses Telnet connections, you can connect to the probe fromanywhere 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 toallow users to acknowledge selected events from the IBM Tivoli Netcool/OMNIbusevent list.

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

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

Example property file settings for peer-to-peer failover

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

Note: In the examples, make sure to use the full path for the property value. Inother words replace $OMNIHOME with the full path. For example:/opt/IBM/tivoli/netcool.

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

The following example shows the peer-to-peer settings from the properties file ofthe corresponding slave probe:


Server : "NCOMS"RulesFile : "slave_rules_file"MessageLog : "slave_log_file"PeerHost : "master_hostname"PeerPort : 5555 # [communication port between master and slave probe]Mode : "slave"PidFile : "$OMNIHOME/var/opc_ua2"

Properties and command line optionsYou use properties to specify how the probe interacts with the device. You canoverride the default values by using the properties file or the command lineoptions.

The following table describes the properties and command line options specific tothis probe. For more information about generic Netcool/OMNIbus properties andcommand line options, see the IBM Tivoli Netcool/OMNIbus Probe and GatewayGuide.

Table 7. Properties and command line options

Property Name Command Line Option Description

AckSystemId string -acksystemid string Use this property to specify the systemidentifier to use when acknowledgingand unacknowledging alarms using theCLI.

The default is "".

AckUserId string -ackuserid string Use this property to specify the user IDto use when acknowledging andunacknowledging alarms using theCLI.

The default is "".

Agentheartbeat integer -agentheartbeat integer Use this property to specify thefrequency (in seconds) with which theprobe checks the status of the IRPAgent.

The default is 60.

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

The default is "".

AlarmIrpFile string -alarmirpfile string Use this property to specify thelocation of the file that contains theIOR of the AlarmIRP object.

The default is "".

AlarmIrpName string -alarmirpiorfilenamestring

Use this property to specify the nameof the Alarm IRP Agent.

The default is 1.SubNetwork/1.Management Node/1.IrpAgent/A0.AlarmIRP/Object.


Table 7. Properties and command line options (continued)


CommandPort integer -commandport string Use this property to specify the portthrough which you will sendcommands using the CLI.

The default is 6970.

CommandPortLimitinteger

-commandportlimitinteger

Use this property to specify themaximum number of Telnetconnections that the probe can makeusing the command port.

The default is 10.

NamingServiceHoststring

-namingservicehoststring

Use this property to specify the nameof the host where the Naming Serviceis available.

The default is localhost.

NamingServiceIorFilestring

-namingserviceiorfilestring

Use this property to specify thelocation of the file that contains theIOR of the Naming Service.

The default is "".

NamingServicePortstring

-namingserviceportstring

Use this property to specify the port onwhich the Naming Service listens.

The default is 5001.

NotificationCategoriesstring

-notificationcategories string

Use this property to specify thenotification categories to which theprobe subscribes.

To specify multiple categories, separatethem using semicolons in the followingformat:

category1;category2;categoryn

The default is "" (the probe subscribesto all available notification categories).

NotificationFilterstring

-notificationfilterstring

Use this property to specify the filterthat the Notification IRP point uses tolimit the notifications sent to the probe.

The default is "".

NotificationIrpFilestring

-notificationirpfilestring

Use this property to specify thelocation of the file that contains theIOR of the NotificationIRP object.

The default is "".

NotificationIrpNamestring

-notificationirpnamestring

Use this property to specify the nameof the Notification IRP Agent.

The default is 1.SubNetwork/1.Management Node/1.IrpAgent/N0.NotificationIRP/ Object.


Table 7. Properties and command line options (continued)


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

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

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

-resynch (This isequivalent to Resynchwith a value of true.)

Use this property to specify whetherthe probe attempts to resynchronizeexisting alarms before retrieving newalarms. This property takes thefollowing values:

false : The probe does not attempt toresynchronize the alarms.

true : The probe attempts toresynchronize the alarms.

The default is false.

Retry string -noretry (This isequivalent to Retrywith a value of false)

-retry (This isequivalent to Retrywith a value of true)

Use this property to specify whether ornot the probe attempts to reconnect tothe CORBA interface following atimeout. This property takes thefollowing values:

false : The probe does not attempt toreconnect to the CORBA interface.

true : The probe attempts to reconnectto the CORBA interface.

The default is false.

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

The default is 0 (the probe never timesout).

TimeTick integer -timetick integer Use this property to specify theduration (in minutes) of thesubscription to the target.

The default is -1 (this ensures that thesession remains open indefinitely).


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

The following table describes the elements generated by the probe.

Table 8. Elements

Element Name Element Description

AttributeValue(element_name) This element contains the value of an elementbeing monitored. This element is generateddynamically and its content is dependent on theIRP agent.

The element_name part of this element can be thename of any of the other elements in this table.

AttributeValueChange(element_name) This element indicates how the value of theelement being monitored has changed.

The element_name part of this element can be thename of any of the other elements in this table.

DOMAIN_NAME This element indicates the domain name fromwhich the notification originated.

EVENT_NAME This element indicates the extended event typefor this IRP.

EVENT_TYPE This element indicates the event type of thenotification.

NV_ACK_STATE This element indicates the acknowledgement stateof the alarm.

NV_ACK_SYSTEM_ID This element indicates the System ID of the IRPManager processing the notification.

NV_ACK_TIME This element indicates the time at which the useracknowledged the alarm.

NV_ACK_USER_ID This element identifies the last user who changedthe acknowledgement state.

NV_ADDITIONAL_TEXT This element indicates information about thenetwork element from which the alarmoriginated.

NV_ALARM_ID This element contains the identificationinformation of the alarm as it appears in thealarm list.

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

NV_BACKED_UP_STATUS This element indicates whether or not the objecthas been backed up.

NV_CORRELATED_NOTIFICATIONS_notif_ID_Set

This element contains the set of notifications towhich this notification is considered to becorrelated. This element is generated dynamicallyand its content is dependent on the IRP agent.

NV_CORRELATED_NOTIFICATIONS_SOURCE This element indicates the source of thenotification set.


Table 8. Elements (continued)

Element Name Element Description

NV_EVENT_TIME This element indicates the time at which theevent occurred.

NV_MANAGED_OBJECT_INSTANCE This element indicates the Managed Objectinstance of the network resource.

NV_NOTIFICATION_ID This element contains the identificationinformation of the notification.

NV_PERCEIVED_SEVERITY This element indicates the relative level ofurgency for operator attention.

NV_PROBABLE_CAUSE This element provides further information aboutthe probable cause of the alarm.

NV_PROPOSED_REPAIR_ACTIONS This element indicates the proposed repairactions associated with the notification.

NV_SPECIFIC_PROBLEM This element contains further information aboutthe problem to which the notification relates.

NV_SYSTEM_DN This element indicates the Distinguished Name(DN) used to identify the system.

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

NV_TREND_INDICATION This element indicates how an observedcondition has changed.

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

The following table describes the error messages specific to this probe. Forinformation about generic Netcool/OMNIbus error messages, see the IBM TivoliNetcool/OMNIbus Probe and Gateway Guide.


Table 9. Error messages

Error message Description Action

Command_Port Erroroccurred

Command_Port Failed toget CommandPortLimitproperty - using 10

Command_Port Failed toget property CommandPort

Command_Port Failed toopen listening socket,shutting down Thread!

Command_Port Failed tosend probewatch message!

Command_Port host Failedto close command socket

Command_Port host Failedto get socket IO

Command_Port host Failedto read command

Command_Port Threadshutting down due toerror!

NetcoolIRPManager: Failedto acknowledge_alarms()

NetcoolIRPManager: Failedto Unacknowledge_alarms()

There was a problem with thecommand port functionality.

Check that you have specifiedthe command port correctly.Check the connection betweenthe probe and the commandport.

BAD_PARAM Exception i.eone or more of the in/outparameter is null

There is a problem with theCORBA interface.

Refer to your CORBAdocumentation.

InvalidParameterException

NetcoolIRPManager:Exception occurred. Stacktrace to stderr

OperationNotSupportedException

Unexpected CORBAException

There is a problem with theCORBA interface.

Refer to your CORBAdocumentation.


Table 9. Error messages (continued)

Error message Description Action

COMMUNICATION FAILUREException i.e Server isdead

GetSubscriptionStatusException

NetcoolIRPManager:BothNameServiceHost andNSPort property needs tobe set

NetcoolIRPManager:'Alarmirp' property needsto be set

NetcoolIRPManager:'Notificationirp'property needs to be set

NetcoolIRPManager: Failedto perform resynch

The probe cannot connect tothe server.

Check that the Nokia-SiemensEMS server is runningcorrectly. Check that you havespecified the parameterscorrectly in the properties file.

Error to parse eventcompletely

Failed to parse eventcompletely

Name is null, cannotcreate Element

NetcoolIRPManager:Category Value NOTsupported: DiscardingAlarm

NetcoolIRPManager: Errorwhen parsing event

NetcoolIRPManager: Failedto send event

The probe cannot parse thealarm. This is probablybecause the alarm is not in aformat that the probe canunderstand.

Check that the Nokia-SiemensEMS server is runningcorrectly.

Failed to get timeoutproperty value,defaulting to 0

The Timeout property has notbeen set.

Check the value for theTimeout property and, ifnecessary, change it.

NetcoolIRPManager: StackTrace to stderr:

This message is generated bythe Netcool IRP Manager.

This message is intended foruse when debugging.


ProbeWatch messagesDuring normal operations, the probe generates ProbeWatch messages and sendsthem to the ObjectServer. These messages tell the ObjectServer how the probe isrunning.

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

Table 10. ProbeWatch Messages

ProbeWatch message Description Triggers or causes

Communication failure -lost connection toNoticiationIRPCORBA.TRANSIENT Exception:Lost connection toNotificationIRP

CORBA.OBJECT_NOT_EXISTException: Lost connectionto NotificationIRPFailedto connect toNotificationIRP: Shuttingdown Failed to Connect:Either, the server is notrunning, the IOR is out ofdate, or probe cannotreach remote Server

The communication with thenotification IRP server hasfailed.

The probe lost its connectionto the notification IRP server.

END SYNCHRONIZATION The synchronization ofalarms has stopped.

The probe has resynched allthe available alarms in theserver.

Failed to find IOR filealarmirp_ior_file

The specified alarm IRP filedoes not exist.

The IRP manager has beenset up incorrectly.

Failed to find IOR filenotificationirp_ior_file

The specified notification IRPfile does not exist.

The IRP manager has beenset up incorrectly.

Failed to get IRP Outline(GetIRPOutline exceptioncaught when callingget_IRP_outline)

The probe could not get thesupported IRP outline usingEntry Point IRP.

Incorrect value set for theAlarmIrpName orNotificationIrpNameproperties.

Failed to get IRPreference (GetIRPReferenceexception caught whencalling get_IRP_reference)

Failed to get IRPreferences - invalidparameter(InvalidParameterexception caught whencalling get_IRP_reference)

The probe could not get theIRP references using EntryPoint IRP.

Failed to get the IRP Outline.


Table 10. ProbeWatch Messages (continued)

ProbeWatch message Description Triggers or causes

Failed to listen forcommands on port numberlistening_port

A problem occurred whiletrying to listen forcommands.

Either there was a probleminitializing the connectiondue to insufficient memoryor (if this message was sentafter some events had beenparsed) there was aconnection failure.

Invalid IRPVersion(InvalidIRPVersionexception caught whencalling get_IRP_outline)

The specified IRP version isincorrect.

An incorrect IRP name isspecified in the propertiesfile.

START SYNCHRONIZATION The synchronization ofalarms has started.

The probe started toresynchronize alarmscollected in the systemduring the timeout period.

Will listen for commandson port numberlistening_port

The probe will listen forcommands on the specifiedport number.

The probe has successfullycreated the CLI server on thespecified command portspecified in the propertiesfile.

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

Depending on which method you use to connect to the CORBA 3GPP interface,you must specify values for the some of the following properties before runningthe probe:v AlarmIrpFile

v AlarmIrpName

v NamingServiceHost

v NamingServicePort

v NotificationIrpFile

v NotificationIrpName

For more information about these properties, see “Connecting to the CORBAinterface” on page 4.

Starting the probe

Use the following command to start the probe:

$OMNIHOME/probes/nco_p_siemens_corba_v1

Shutting down the probe

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


Running multiple probesYou can run multiple instances of the probe.

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

Running multiple probes in a failover configuration

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

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

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

Include the following peer-to-peer settings in the master's probe properties file:PeerHost : "slave_hostname"PeerPort : 5555 # [communication port between master and slave probes]

Include the following peer-to-peer settings in the slave's probe properties file:PeerHost : "master_hostname"PeerPort : 5555 # [communication port between master and slave probes]


Appendix. Notices and Trademarks

This appendix contains the following sections:v Noticesv Trademarks

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

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

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

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

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

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

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

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

© Copyright IBM Corp. 2006, 2012 19

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who want to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationSoftware Interoperability Coordinator, Department 49XA3605 Highway 52 NRochester, MN 55901U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

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

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

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

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


COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, ibm.com, AIX, Tivoli, zSeries, and Netcool are trademarks ofInternational Business Machines Corporation in the United States, other countries,or both.

Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-basedtrademarks are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States, other countries, or both.

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporationin the United States, other countries, or both.

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

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

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

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

Appendix. Notices and Trademarks 21


��

Printed in USA

SC23-7668-03

Documents

Probe for Nokia-Siemens Switch/Radio/@vantage … using the Windows command line with these probes, ... 2 Probe for Nokia-Siemens Switch/Radio/@vantage Commander (CORBA) 3GPP V5.5: