ibmthe alcatel-lucent omc-r (operation and maintenance center-radio operation and maintenance...

IBM® Tivoli® Netcool/OMNIbus Probe forAlcatel-Lucent OMC-R (CORBA) 3GPP V5.5Version 3.0

Reference GuideNovember 8, 2013

IBM

SC27-6214-00

Note

Before using this information and the product it supports, read the information in Appendix A, “Noticesand Trademarks,” on page 19.

Edition notice

This edition (SC27-6214-00) applies to version 3.0 of IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent OMC-R(CORBA) and to all subsequent releases and modifications until otherwise indicated in new editions.

This is the first publication of this guide.© Copyright International Business Machines Corporation 1996, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

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

Chapter 1. Probe for Alcatel-Lucent OMC-R (CORBA).............................................. 1Summary...................................................................................................................................................... 1Installing probes.......................................................................................................................................... 2Configuration................................................................................................................................................3

Configuring the lookup table.................................................................................................................. 3Setting environment variables............................................................................................................... 3Firewall considerations.......................................................................................................................... 3

Command line interface...............................................................................................................................4Data acquisition........................................................................................................................................... 6

Connecting to the CORBA interface....................................................................................................... 6Retrieving objects................................................................................................................................... 6Status checks..........................................................................................................................................7Filters for notifications and alarms........................................................................................................ 7Peer-to-peer failover functionality.........................................................................................................8

Properties and command line options........................................................................................................ 8Elements.................................................................................................................................................... 12Error messages.......................................................................................................................................... 14ProbeWatch messages.............................................................................................................................. 15Running the probe..................................................................................................................................... 16

Running multiple probes......................................................................................................................16

Appendix A. Notices and Trademarks................................................................... 19Notices....................................................................................................................................................... 19Trademarks................................................................................................................................................ 20

iii

About this guide

The following sections contain important information about using this guide.

Document control pageThe IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent OMC-R (CORBA) documentation is provided insoftcopy format only. To obtain the most recent version, please visit the IBM Tivoli Netcool KnowledgeCenter:

https://www.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/common/Probes.html

Table 1. Document modification history

Documentversion

Publicationdate

Comments

SC27-6214-00 November 8,2013

First IBM publication.

Conventions used in this guideAll probe guides use standard conventions for operating system-dependent environment variables anddirectory paths.

Operating system-dependent variables and paths

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

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

$OMNIHOME/probes

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

© Copyright IBM Corp. 1996, 2013 v

https://www.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/common/Probes.html

Operating system-specific directory names

Where Tivoli Netcool/OMNIbus files are identified as located within an arch directory under NCHOME orOMNIHOME, arch is a variable that represents your operating system directory. For example:

$OMNIHOME/probes/arch

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

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

Table 2. Directory names for the arch variable

Operating system Directory name represented by arch

AIX® systems aix5

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 manyconfiguration 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 Alcatel-Lucent OMC-R (CORBA) 3GPP V5.5: Reference Guide

Chapter 1. Probe for Alcatel-Lucent OMC-R (CORBA)

The Alcatel-Lucent OMC-R (Operation and Maintenance Center-Radio Operation and Maintenance Center-Radio) system manages radio devices.

The probe collects alarms from Alcatel-Lucent OMC-R using the Common Object Request BrokerArchitecture (CORBA) 3rd Generation Partnership Project (3GPP) V5.5 interface.

The probe complies with the following 3GPP standards:

Table 3. Supported 3GPP standards

3GPP Technical Specification 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:

• “Summary” on page 1• “Installing probes” on page 2• “Configuration” on page 3• “Data acquisition” on page 6• “Properties and command line options” on page 8• “Elements” on page 12• “Error messages” on page 14• “ProbeWatch messages” on page 15• “Running the probe” on page 16

SummaryEach probe works in a different way to acquire event data from its source, and therefore has specificfeatures, default values, and changeable properties. Use this summary information to learn about thisprobe.

The following table provides a summary of the IBM Tivoli Netcool/OMNIbus Probe for Alcatel-LucentOMC-R.

The following table summarizes the probe.

Table 4. Summary

Probe target Alcatel-Lucent Evolium™ 1353 UMTS OMC-R 3GPP interfaceV5.5

Probe executable name nco_p_alcatel_omcr_3gpp

Patch number 3.0

© Copyright IBM Corp. 1996, 2013 1

Table 4. Summary (continued)

Probe supported on For details of supported operating systems, see the followingRelease Notice on the IBM Software Support website:

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

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

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

Requirements For details of any additional software that this probe requires,refer to the description.txt file that is supplied in itsdownload package.

Connection method CORBA

Remote connectivity Yes

Multicultural support Not Available

For information about configuring multicultural support,including language options, see the IBM Tivoli Netcool/OMNIbusInstallation and Deployment Guide.

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

Federal Information ProtocolStandards (FIPS)

IBM Tivoli Netcool/OMNIbus uses the FIPS 140-2 approvedcryptographic provider: IBM Crypto for C (ICC) certificate 384 forcryptography. This certificate is listed on the NIST website athttp://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 probesAll probes are installed in a similar way. The process involves downloading the appropriate installationpackage for your operating system, installing the appropriate files for the version of Netcool/OMNIbusthat you are running, and configuring the probe to suit your environment.

The installation process consists of the following steps:

1. Downloading the installation package for the probe from the Passport Advantage Online website.

Each probe has a single installation package for each operating system supported. For details abouthow to locate and download the installation package for your operating system, visit the following pageon the IBM Tivoli Knowledge Center:

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

2. Installing the probe using the installation package.

2 IBM® Tivoli® Netcool/OMNIbus Probe for Alcatel-Lucent OMC-R (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



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 thefollowing page on the IBM Tivoli Knowledge Center:

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

3. Configuring the probe.

This guide contains details of the essential configuration required to run this probe. It combines topicsthat are common to all probes and topics that are peculiar to this probe. For details about additionalconfiguration that is common to all probes, see the IBM Tivoli Netcool/OMNIbus Probe and GatewayGuide.

ConfigurationTo configure the probe prior to running, you must ensure the probe installation complete; you must alsoupdate the rules file using probe-specific information and set the environment variables.

The following topics describe the configuration requirements for the probe.

• “Configuring the lookup table” on page 3• “Setting environment variables” on page 3• “Firewall considerations” on page 3

Configuring the lookup tableThe probe is supplied with a lookup table that is referenced in the rules file of the probe. If you change thedirectory location of the probe from the default, you must update the command in the rules file to includethe full path of the lookup table

The lookup table (Corba_3gpp_V551.lookup) is installed in the following location:

$OMNIHOME/probes/includes/

This file is referenced in the rules file supplied with the probe by the following command:

include "../includes/Corba_3gpp_V551.lookup"

The command assumes that the probe is run from the following location:

$OMNIHOME/probes/

If you are running the probe from a different location, you must change the command in the rules file toinclude the full path of the lookup table.

Note: $OMNIHOME cannot be used in the paths to the lookup files; you must enter the full path to the IBMTivoli Netcool/OMNIbus installation directory.

Setting environment variablesYou must install the jre_directory/bin path in the $PATH environment variable wherejre_directory is the installation directory of the Java Runtime Environment (JRE).

This must be the first path set in the $PATH environment variable.

Firewall considerationsWhen using CORBA probes in conjunction with a firewall, the firewall must be configured so that the probecan connect to the target system.

Most CORBA probes can act as both a server (listening for connections from the target system) and aclient (connecting to the port on the target system to which the system writes events). If you are using the

Probe for Alcatel-Lucent OMC-R (CORBA) 3



probe in conjunction with a firewall, you must add the appropriate firewall rules to enable this dualbehavior.

There are three possible firewall protection scenarios, for which you must determine port numbers beforeadding firewall rules:

1. If the host on which the probe is running is behind a firewall, you must determine what remote hostand 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 incomingport 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. Thedefault value for this property is 0, which means that an available port is selected at random. If the probeis 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 portsfrom those that use NamingService and EntryPoint objects. If the probe is configured to get objectreferences from a NamingService or EntryPoint object, you must obtain the host and port informationfrom the system administrator of the target system. When you have this information, you can add theappropriate firewall rules.

Command line interfaceThe probe is supplied with a command line interface (CLI). This interface enables you to executecommands to acknowledge alarms or request a full resynchronization in the CORBA interface.

To use the CLI, you must use the CommandPort property to specify a port through which commands willbe sent. The default port is 6970. When you want to issue commands, use Telnet to connect through thisport. You can use the CommandPortLimit 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 5. CLI commands

Command Description

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

Before you can use this command, you must specify avalue for the AckSystemId property.


Table 5. CLI commands (continued)

Command Description

userid_acknowledge_alarm alarm_iduser_id

Use this command to acknowledge an alarm in theCORBA 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, theuser_id parameter is not required.

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


userid_unacknowledge_alarm alarm_iduser_id

Use this command to unacknowledge an alarm in theCORBA 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, theuser_id parameter is not required.

resynch_all Use this command to perform a full resynchronizationwith the CORBA interface.

resynch_filter filter Use this command to perform a partial resynchronizationwith the CORBA interface.

The filter parameter uses the same filter format as theAlarmFilter property.

help This command displays online help about the CLI.

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 from anywhere by creating adesktop tool to open a Telnet connection, send a command, and then close the connection. This meansthat simple scripts can be set up to allow users to acknowledge selected events from the IBM TivoliNetcool/OMNIbus event list.


Data acquisitionEach probe uses a different method to acquire data. Which method the probe uses depends on the targetsystem from which it receives data.

The probe connects to the Alcatel-Lucent OMC-R management system through aCORBA interface.

It complies with the following 3GPP standards:

• 32.111 V5.5.1 - Alarm IRP• 32.303 V5.2.0 - Notification IRP• 32.623 V5.2.0 - Generic Network

Data acquisition is described in the following topics:

• “Connecting to the CORBA interface” on page 6• “Retrieving objects” on page 6• “Status checks” on page 7• “Filters for notifications and alarms” on page 7• “Peer-to-peer failover functionality” on page 8

Connecting to the CORBA interfaceThe probe acts as an Integration Reference Point (IRP) Manager and connects to the Alcatel-Lucent OMC-R system using a CORBA 3GPP interface.

The AlarmIRP and NotificationIRP CORBA objects form a part of the IRP agent to which the probeconnects.

Depending on your operating environment, use one of the following connection configurations:

Option 1- specify values for the following properties:

• AlarmIrpFile - specify the full path to the file containing the IOR of the AlarmIRP object.• NotificationIrpFile - specify the full path to the file containing the IOR of the NotificationIRP

object.

Option 2 - specify values for the following properties:

• NamingServiceHost - specify the name of the host machine where the CORBA Naming Service isrunning.

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

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

The probe then connects to the NotificationIRP point and uses the CORBA notification push model toreceive new alarms. If the Resynch property is set to false, the probe only receives new alarms.


Status checksThe probe checks the status of the IRP agent every 60 seconds. You can change this frequency if requiredusing the AgentHeartbeat property.

Filters for notifications and alarmsThe NotificationFilter and AlarmFilter properties allow you to specify what notifications and alarms aresent to the probe. 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 probeis sent only notifications with a perceived severity of 3, you must set the NotificationFilter property to $h= = 3.

You can specify more complex filters using AND and OR statements. For example, to specify that theprobe is sent notifications with a perceived severity of 3 or 4, you must set the NotificationFilter propertyto $h = = 3 or $h = = 4.

To specify that the probe is only sent notifications for a specific managed element, set theNotificationFilter property to Managed_Node_Name~$f where $f represents the elementNV_MANAGED_OBJECT_INSTANCE and Managed_Node_Name is the name of the managed object.

For example, if the set of alarms that you require return an NV_MANAGED_OBJECT_INSTANCE ofSubNetwork=ONRM_RootMo, SubNetwork=SNMP, ManagedElement=SP1, set the NotificationFilterproperty to SP1'~$'f.

Note: The tilde character (~) is required because spaces cannot be entered in this property. For stringcomparisons, the first argument is considered to be contained in the second argument; which is why $f islisted second to the literal.

The following table displays the token mappings for use with the AlarmFilter and NotificationFilterproperties.

Table 6. Token mappings

Element Token

NV_NOTIFICATION_ID a

NV_CORRELATED_NOTIFICATIONS b

NV_EVENT_TIME c

NV_SYSTEM_DN d

NV_MANAGED_OBJECT_CLASS e

NV_MANAGED_OBJECT_INSTANCE f

NV_PROBABLE_CAUSE g

NV_PERCEIVED_SEVERITY h

NV_SPECIFIC_PROBLEM i

NV_ADDITIONAL_TEXT j

NV_ALARM_ID k

NV_ACK_USER_ID l

NV_ACK_TIME m

NV_ACK_SYSTEM_ID n

NV_ACK_STATE o

NV_BACKED_UP_STATUS p


Table 6. Token mappings (continued)

Element Token

NV_BACK_UP_OBJECT q

NV_THRESHOLD_INFO r

NV_TREND_INDICATION s

NV_STATE_CHANGE_DEFINITION t

NV_MONITORED_ATTRIBUTES u

NV_PROPOSED_REPAIR_ACTIONS v

NV_REASON w

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

While the slave probe receives heartbeats from the master probe, it does not forward events to theObjectServer. If the master probe shuts down, the slave probe stops receiving heartbeats from the masterand 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 sendsthem 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 settingsdiffer 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 slaveprobe:

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"

Properties and command line optionsThe following table describes the properties and command line options specific to this probe. For moreinformation about generic Netcool/OMNIbus properties and command line options, see the IBM TivoliNetcool/OMNIbus Probe and Gateway Guide.


Table 7. Properties and command line options

Property name Command line option Description

AgentHeartbeat integer -agentheartbeat integer Use this property to specify the frequency (inseconds) with which the probe checks thestatus of the IRP agent.

The default is 60.

AlarmFilter string -alarmfilter string Use this property to specify the filter that thealarm IRP uses to limit the alarms sent to theprobe.

The default is "".

AlarmIrpFile string -alarmirpfile string Use this property to specify the location ofthe file that contains the IOR of theAlarmIRP object.

The default is "".

AlarmIrpName string -alarmirpname string Use this property to specify the name of theAlarm IRP Agent used by the Naming Service.

The default is OMC/3GPP/EntryPoint/DC=ALCATEL\.COM,SubNetwork=1,ManagementNode=01,IRPAgent=1/32\.111 V5\.5/iRPReference.

CommandPort integer -commandport string Use this property to specify the port throughwhich you will send commands using the CLI.

The default is 6970.

CommandPortLimitinteger

-commandportlimit integer Use this property to specify the maximumnumber of concurrent Telnet connections thatthe probe can make using the command port.

The default is 10.

FlushBufferIntervalinteger

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

The default is 0 (which instructs the probe tonever flush the alerts to the ObjectServer).

NamingServiceHost string -namingservicehost string Use this property to specify the host runningthe CORBA Naming Service.

The default is localhost.

NamingServicePortinteger

-namingserviceport integer Use this property to specify the port on whichthe CORBA Naming Service listens.

The default is 5001.


Table 7. Properties and command line options (continued)


NotificationFilter string -notificationfilter string Use this property to specify the filter that thenotification IRP uses to limit the notificationssent to the probe.

The default is "".

NotificationIrpFile string -notificationirpfile string Use this property to specify the location ofthe file that contains the IOR of theNotificationIRP object.

The default is "".

NotificationIrpNamestring

-notificationirpname string Use this property to specify the name of theNotification IRP Agent used by the NamingService.

The default is OMC/3GPP/EntryPoint/DC=ALCATEL\.COM,SubNetwork=1,ManagementNode=01,IRPAgent=1/32\.303 V5\.2/iRPReference.

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

The default is UTF8.

This property can also take the valueISO8859_1.

ORBLocalHostName string -orblocalhostname string Use this property to specify the local hostname used by the server-side ORB to placethe server's host name into the IOR of aremote object.

The default is "".

ORBLocalPort integer -orblocalport integer Use this property to specify the local port towhich the ORB listens.

The default is 0 (the ORB selects an availableport at random).

ORBWCharDefault string -orbwchardefault string Use this property to specify what widecharacter (wchar) set the IBM ORB useswhen communicating with other ORBs that donot publish a wchar set.

The default is UTF16.

This property can also take the value UCS2.




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

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

Use this property to specify whether theprobe attempts to resynchronize existingalarms before retrieving new alarms. Thisproperty takes the following values:

false : The probe does not attempt toresynchronize the alarms.

true : The probe attempts to resynchronizethe alarms.

The default is false.

ResyncPeriod integer -resyncperiod integer Use this property to specify the numberseconds prior to the current time to set theNV_EVENT_TIME in the AlarmFilter.

The default is "".

Note: The probe ignores this property if atime filter is already specified in theAlarmFilter.

ResyncTimeOperatorstring

-resynctimeoperator string Use this property to specify the assignmentoperator for building the time filter.

The default is >


TimeFilterFormat string -timefilterformat string Use this property to specify the format of thetime filter format required by theNV_EVENT_TIME filter.

The default is "".


Retry string -retry (equivalent to Retrywith a value of true)

-noretry(equivalent toRetry with a value of false)

Use this property to specify whether theprobe attempts to reconnect to the systemfollowing a timeout:

false: The probe does not attempt toreconnect to the system.

true: The probe attempts to reconnect to thesystem.

The default is false.




Timeout integer -timeout integer Use this property to specify the time (inseconds) the probe waits to receive eventsbefore disconnecting from the notificationservice and shutting down.

The default is 0 (the probe never times out).

TimeTick integer -timetick integer Use this property to specify the length (inminutes) of the notification IRP sessionlifetime; this is used by the3GPP server.

The default is -1.

ElementsThe following table describes the static elements that the probe generates:

Table 8. Static elements

Element Name Element Description

$AttributeValue(element_name) This element contains the value of an element beingmonitored. This element is generated dynamically and itscontent is dependent on the IRP agent.

Note: The element_name part of this element and thenext element can be the name of any of the otherelements in this table.

$AttributeValueChange(element_name)

This element indicates how the value of the elementbeing monitored has changed.

$domain_name This element shows the domain name from which thenotification originated.

$EVENT_NAME This element shows the name of the event.

$EVENT_TYPE This element identifies the event type of the notification.

$NV_ACK_STATE This element indicates the acknowledgement state ofthe alarm.

$NV_ACK_SYSTEM_ID This element shows the system ID of the IRP Managerprocessing the notification.

$NV_ACK_TIME This element shows the time when the useracknowledged the alarm.

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


Table 8. Static elements (continued)

Element Name Element Description

$NV_ADDITIONAL_TEXT This element contains the information about the networkelement from which the alarm originated.

$NV_ALARM_ID This element identification information of the alarm as itappears in the alarm list.

$NV_BACK_UP_OBJECT This element shows the Distinguished Name (DN) of thebackup object.

$NV_BACKED_UP_STATUS This element identifies whether the object has beenbacked up.

$NV_CORRELATED_NOTIFICATIONS_notif_ID_Set

This element contains the set of notifications to whichthis notification is considered to be correlated. Thiselement is generated dynamically and its content isdependent on the IRP agent.

$NV_CORRELATED_NOTIFICATIONS_SOURCE

This element identifies the source of the notification set.

$NV_EVENT_TIME This element shows the time when the event occurred.

$NV_MANAGED_OBJECT_INSTANCE This element identifies the managed object instance ofthe network resource.

$NV_NOTIFICATION_ID This element contains the identification information ofthe notification.

$NV_PERCEIVED_SEVERITY This element indicates the perceived severity of thealarm.

$NV_PROBABLE_CAUSE This element provides further information about theprobable cause of the alarm.

$NV_PROPOSED_REPAIR_ACTIONS This element contains the proposed repair actionsassociated with the notification.

$NV_SPECIFIC_PROBLEM This element provides further information about theproblem to which the notification relates.

$NV_SYSTEM_DN This element shows the DN used to identify the system.

$NV_THRESHOLD_INFO This element provides information about a threshold thathas been crossed.

$NV_TREND_INDICATION This element indicates how an observed condition haschanged.


Error messagesThe following table describes the error messages specific to this probe. For information about genericNetcool/OMNIbus error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 9. Error messages

Error message Description Action

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

CORBA Exception stack trace tostderr

CORBA.OBJECT_NOT_EXISTexception raised.NotificationIRP is down!

CORBA.TRANSIENT exceptionraised. NotificationIRP isdown!

Failed to narrowNotificationIRP reference

Failed to narrow Security IRPinterface

InvalidParameter Exception

login: Failed to get IRP object

login: Unknown exceptionoccurred

NetcoolIRPManager: Failed toretrieve AlarmIRP object fromsecurity interface

NetcoolIRPManager: Failed toretrieve NotificationIRP objectfrom security interface

OperationNotSupported Exception

There is a problem with theCORBA interface.

Refer to your CORBAdocumentation.

Communication failure - lostconnection to NoticiationIRP

Failed to get subscriptionstatus

Failed to ping notificationservice

The probe lost its connectionto the server.

Check that the Alcatel-Lucent OMC-R 3GPP server isrunning correctly. Check theconnection to the Alcatel-Lucent OMC-R 3GPP server.


Table 9. Error messages (continued)

Error message Description Action

Failed to attach tonotification categories

Failed to iterate throughresynch alarms

Failed to perform resynch

There was a problem withthe resynchronizationprocess.

Check that Alcatel-LucentOMC-R 3GPP server isrunning correctly. Check thatyou have specified theresynchronizationparameters correctly.

NetcoolIRPManager: Error whenparsing event

NetcoolIRPManager: Failed tosend event

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

Check that Alcatel-LucentOMC-R 3GPP server isrunning correctly.

NetcoolIRPManager: Failed tofind IOR file filename

The file specified does notexist.

Check that the IRP managerhas been set up correctly.

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

The following table describes the ProbeWatch messages that the probe generates. For information aboutgeneric Netcool/OMNIbus ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe andGateway Guide.

Table 10. ProbeWatch Messages

ProbeWatch message Description Triggers or causes

Communication failure -lost connection toNoticiationIRP

CORBA.TRANSIENTException: Lostconnection toNotificationIRP

CORBA.OBJECT_NOT_EXISTException: Lostconnection toNotificationIRP

Failed to connect toNotificationIRP: Shuttingdown

Failed to Connect:Either, the server is notrunning, the IOR is outof date, or probe cannotreach remote Server

The communication with thenotification IRP server has failed.

The probe lost its connection tothe notification IRP server.


Table 10. ProbeWatch Messages (continued)

ProbeWatch message Description Triggers or causes

END SYNCHRONIZATION The synchronization of alarmshas stopped.

The probe has resynched all theavailable alarms in the server.

Failed to find IOR filealarmirp_ior_file

The specified alarm IRP file doesnot exist.

The IRP manager has been set upincorrectly.

Failed to find IOR filenotificationirp_ior_file

The specified notification IRP filedoes not exist.

The IRP manager has been set upincorrectly.

START SYNCHRONIZATION The synchronization of alarmshas started.

The probe started toresynchronize alarms collected inthe system during the timeoutperiod.

Will listen for commandson port numberlistening_port

The probe will listen forcommands on the specified portnumber.

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

Running the probeBefore 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 valuesfor the some of the following properties before running the probe:

• AlarmIrpFile• AlarmIrpName• NamingServiceHost• NamingServicePort• NotificationIrpFile• NotificationIrpName

For details about how to configure these properties, see “Connecting to the CORBA interface” on page 6.

Starting the probe

Use the following command to start the probe:

$OMNIHOME/probes/nco_p_alcatel_omcr_3gpp

Shutting down the probe

To stop an instance of the probe, issue a stop signal to the process associated with that 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 using the ORBLocalPortproperty.


Running multiple probes in a failover configuration

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

Where you are running this configuration in conjunction with a firewall, add the receiving port of eachprobe to the firewall rules. The direction of the connection is from the target system to the master or slaveprobe.

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]


Appendix A. Notices and TrademarksThis appendix contains the following sections:

• Notices• 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 in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply that onlythat IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property right may be used instead. However, it is theuser'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 licenseinquiries, 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 IBM Intellectual PropertyDepartment 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 other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress 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 periodicallymade 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 thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe 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 withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

© Copyright IBM Corp. 1996, 2013 19

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 material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, orany equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurements may have been estimatedthrough extrapolation. Actual results may vary. Users of this document should verify the applicable datafor their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

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

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

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

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

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms.

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

TrademarksIBM, the IBM logo, ibm.com, AIX, Tivoli, zSeries, and Netcool are trademarks of International BusinessMachines Corporation in the United States, other countries, or both.


Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-based trademarks are eitherregistered trademarks or trademarks of Adobe Systems Incorporated in the United States, othercountries, or both.

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

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

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, othercountries, 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.

Other company, product, or service names may be trademarks or service marks of others.

Notices and Trademarks 21

IBM®

SC27-6214-00

ibmthe alcatel-lucent omc-r (operation and maintenance center-radio operation and maintenance...

Documents