probe for alcatel-lucent omc-r (corba) 3gpp v5.5: reference guide - ibm … · about this guide the...

IBM® Tivoli® Netcool/OMNIbus Probe for Alcatel-LucentOMC-R (CORBA) 3GPP V5.5Version 3.0

Reference GuideNovember 8, 2013

SC27-6214-00

��

NoteBefore using this information and the product it supports, read the information in “Notices and 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 IBM Corporation 1996, 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

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

IBM Tivoli Netcool/OMNIbus Probe forAlcatel-Lucent OMC-R (CORBA) . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Configuration . . . . . . . . . . . . . . 3

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

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

Connecting to the CORBA interface. . . . . . 6

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

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

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

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

© Copyright IBM Corp. 1996, 2013 iii

iv Probe for Alcatel-Lucent OMC-R (CORBA) 3GPP V5.5: Reference Guide

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 in softcopy format only. To obtain the most recentversion, please visit the IBM Tivoli Netcool Information Center:

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

Table 1. Document modification history

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

© Copyright IBM Corp. 1996, 2013 v



equivalent to $TMPDIR in UNIX and Linux environments. Where such variables aredescribed in the guide, both the UNIX and Windows conventions will be used.

Operating system-specific directory names

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

$OMNIHOME/probes/arch

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

Table 2. Directory names for the arch variable

Operating system Directory name represented by arch

AIX® systems aix5

HP-UX PA-RISC-based systems hpux11

HP-UX Integrity-based systems hpux11hpia

Red Hat Linux and SUSE systems linux2x86

Linux for System z® linux2s390

Solaris systems solaris2

Windows systems win32

vi Probe for Alcatel-Lucent OMC-R (CORBA) 3GPP V5.5: Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent OMC-R(CORBA)

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

The probe collects alarms from Alcatel-Lucent OMC-R 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”v “Installing probes” on page 2v “Configuration” on page 3v “Data acquisition” on page 6v “Properties and command line options” on page 9v “Elements” on page 12v “Error messages” on page 14v “ProbeWatch messages” on page 15v “Running the probe” on page 16

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 IBM Tivoli Netcool/OMNIbusProbe for Alcatel-Lucent OMC-R (CORBA).

The following table summarizes the probe.

Table 4. Summary

Probe target Alcatel-Lucent Evolium™ 1353 UMTS OMC-R 3GPPinterface V5.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 thefollowing Release Notice on the IBM Software Supportwebsite:

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 proberequires, refer to the description.txt file that issupplied in its download package.

Connection method CORBA

Remote connectivity Yes

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

Multicultural support Available

For information about configuring 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 ProtocolStandards (FIPS)

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

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

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

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

2. Installing the probe using the installation package.

2 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

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



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

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

ConfigurationTo configure the probe prior to running, you must ensure the probe installationcomplete; you must also update the rules file using probe-specific information andset the environment variables.

The following topics describe the configuration requirements for the probe.v “Configuring the lookup table”v “Setting environment variables”v “Firewall considerations” on page 4

Configuring the lookup tableThe probe is supplied with a lookup table that is referenced in the rules file of theprobe. If you change the directory location of the probe from the default, you mustupdate the command in the rules file to include the 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 followingcommand: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 thecommand in the rules file to include the full path of the lookup table.

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

Setting environment variablesYou must install the jre_directory/bin path in the $PATH environment variablewhere jre_directory is the installation directory of the Java™ RuntimeEnvironment (JRE).

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

IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent OMC-R (CORBA) 3

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



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 thatan available port is selected at random. If the probe is behind a firewall, the valueof the ORBLocalPort property must be specified as a fixed port number.

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

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

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.


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 connects to the Alcatel-Lucent OMC-R management system throughaCORBA interface.

It complies with the following 3GPP standards:v 32.111 V5.5.1 - Alarm IRPv 32.303 V5.2.0 - Notification IRPv 32.623 V5.2.0 - Generic Network

Data acquisition is described in the following topics:v “Connecting to the CORBA interface”v “Retrieving objects”v “Status checks” on page 7v “Filters for notifications and alarms” 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 Alcatel-Lucent OMC-R system using a CORBA 3GPP interface.

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

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

Option 1- specify values for the following properties:v AlarmIrpFile - specify the full path to the file containing the IOR of the

AlarmIRP object.v NotificationIrpFile - specify the full path to the file containing the IOR of the

NotificationIRP object.

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

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

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

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

the CORBA Naming Service.

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.

Status checksThe probe checks the status of the IRP agent every 60 seconds. You can change thisfrequency if required using the AgentHeartbeat property.

Filters for notifications and alarmsThe NotificationFilter and AlarmFilter properties allow you to specify whatnotifications and alarms are sent to the probe. When you use these properties, youmust use the actual token names.

For example, the token h represents the element NV_PERCEIVED_SEVERITY. So,to specify that the probe is 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, tospecify that the probe is sent notifications with a perceived severity of 3 or 4, youmust set the NotificationFilter property to $h = = 3 or $h = = 4.

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

For example, if the set of alarms that you require return anNV_MANAGED_OBJECT_INSTANCE of SubNetwork=ONRM_RootMo,SubNetwork=SNMP, ManagedElement=SP1, set the NotificationFilter propertyto SP1'~$'f.

Note: The tilde character (~) is required because spaces cannot be entered in thisproperty. For string comparisons, the first argument is considered to be containedin the second argument; which is why $f is listed second to the literal.

The following table displays the token mappings for use with the AlarmFilter andNotificationFilter properties.

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


Table 6. Token mappings (continued)

Element Token

NV_ACK_USER_ID l

NV_ACK_TIME m

NV_ACK_SYSTEM_ID n

NV_ACK_STATE o

NV_BACKED_UP_STATUS p

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 the master probe, sending events to the ObjectServer; the otheracts as the slave probe on standby. If the master probe fails, the slave probeactivates.

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

Example property file settings for peer-to-peer failover

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

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

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


Properties and command line optionsThe 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

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 uses to limit thealarms 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 -alarmirpname string Use this property to specify the nameof the Alarm IRP Agent used by theNaming Service.

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

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 concurrent Telnetconnections that the probe can makeusing the command port.

The default is 10.

FlushBufferIntervalinteger

-flushbufferintervalinteger

Use this property to specify how often(in seconds) the probe flushes all alertsin the buffer to the ObjectServer.

The default is 0 (which instructs theprobe to never flush the alerts to theObjectServer).

NamingServiceHoststring

-namingservicehoststring

Use this property to specify the hostrunning the CORBA Naming Service.

The default is localhost.


Table 7. Properties and command line options (continued)


NamingServicePortinteger

-namingserviceportinteger

Use this property to specify the port onwhich the CORBA Naming Servicelistens.

The default is 5001.

NotificationFilterstring

-notificationfilterstring

Use this property to specify the filterthat the notification IRP uses to limitthe 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 used bythe Naming Service.

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

ORBCharEncoding string -orbcharencoding string Use this property to specify the nativecharacter encoding set used by theObject Request Broker (ORB) forcharacter data.

The default is UTF8.

This property can also take the valueISO8859_1.

ORBLocalHostName string -orblocalhostnamestring

Use this property to specify the localhost name used by the server-side ORBto place the server's host name into theIOR of a remote object.

The default is "".

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

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

The default is UTF16.

This property can also take the valueUCS2.




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.

ResyncPeriod integer -resyncperiod integer Use this property to specify thenumber seconds prior to the currenttime to set the NV_EVENT_TIME in theAlarmFilter.

The default is "".

Note: The probe ignores this propertyif a time filter is already specified inthe AlarmFilter.

ResyncTimeOperatorstring

-resynctimeoperatorstring

Use this property to specify theassignment operator for building thetime filter.

The default is >


TimeFilterFormat string -timefilterformatstring

Use this property to specify the formatof the time filter format required by theNV_EVENT_TIME filter.

The default is "".


Retry string -retry (equivalent toRetry with a value oftrue)

-noretry(equivalent toRetry with a value offalse)

Use this property to specify whetherthe probe attempts to reconnect to thesystem following a timeout:

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

true: The probe attempts to reconnectto the system.

The default is false.




Timeout integer -timeout integer Use this property to specify the time(in seconds) the probe waits to receiveevents before disconnecting from thenotification service and shutting down.

The default is 0 (the probe never timesout).

TimeTick integer -timetick integer Use this property to specify the length(in minutes) of the notification IRPsession lifetime; this is used bythe3GPP 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 elementbeing monitored. This element is generateddynamically and its content is dependent on theIRP agent.Note: The element_name part of this element andthe next element can be the name of any of theother elements in this table.

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

$domain_name This element shows the domain name fromwhich the notification originated.

$EVENT_NAME This element shows the name of the event.

$EVENT_TYPE This element identifies the event type of thenotification.

$NV_ACK_STATE This element indicates the acknowledgement stateof the alarm.

$NV_ACK_SYSTEM_ID This element shows the system ID of the IRPManager processing 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 haschanged the acknowledgement state.

$NV_ADDITIONAL_TEXT This element contains the information about thenetwork element from which the alarmoriginated.

$NV_ALARM_ID This element identification information of thealarm as it appears in the alarm list.

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


Table 8. Static elements (continued)

Element Name Element Description

$NV_BACKED_UP_STATUS This element identifies whether the object hasbeen 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 identifies the source of thenotification set.

$NV_EVENT_TIME This element shows the time when the eventoccurred.

$NV_MANAGED_OBJECT_INSTANCE This element identifies 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 perceived severity ofthe alarm.

$NV_PROBABLE_CAUSE This element provides further information aboutthe probable 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 aboutthe problem to which the notification relates.

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

$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 messagesThe 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

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

CORBA Exception stack trace tostderr

CORBA.OBJECT_NOT_EXIST exceptionraised. NotificationIRP is down!

CORBA.TRANSIENT exception raised.NotificationIRP is down!

Failed to narrow NotificationIRPreference

Failed to narrow Security IRPinterface

InvalidParameter Exception

login: Failed to get IRP object

login: Unknown exception occurred

NetcoolIRPManager: Failed toretrieve AlarmIRP object fromsecurity interface

NetcoolIRPManager: Failed toretrieve NotificationIRP objectfrom security interface

OperationNotSupported Exception

There is a problem withthe CORBA interface.

Refer to your CORBAdocumentation.

Communication failure - lostconnection to NoticiationIRP

Failed to get subscription status

Failed to ping notificationservice

The probe lost itsconnection to the server.

Check that theAlcatel-Lucent OMC-R3GPP server is runningcorrectly. Check theconnection to theAlcatel-Lucent OMC-R3GPP server.

Failed to attach to notificationcategories

Failed to iterate through resynchalarms

Failed to perform resynch

There was a problemwith theresynchronizationprocess.

Check that Alcatel-LucentOMC-R 3GPP server isrunning correctly. Checkthat you have specifiedthe resynchronizationparameters correctly.


Table 9. Error messages (continued)

Error message Description Action

NetcoolIRPManager: Error whenparsing event

NetcoolIRPManager: Failed to sendevent

The probe cannot parsethe alarm; this isprobably because thealarm is not in a formatthat the probe canunderstand.

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

NetcoolIRPManager: Failed to findIOR file filename

The file specified doesnot exist.

Check that the IRPmanager has been set upcorrectly.

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 NotificationIRP

Failed to connect toNotificationIRP: Shuttingdown

Failed to Connect: Either,the server is not running,the IOR is out of date, orprobe cannot reach remoteServer

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.

START SYNCHRONIZATION The synchronization ofalarms has started.

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


Table 10. ProbeWatch Messages (continued)

ProbeWatch message Description Triggers or causes

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 details about how to configure these properties, see “Connecting to theCORBA 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 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 documentin other 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. 1996, 2013 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 wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

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

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

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

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

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

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

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

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

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


COPYRIGHT LICENSE:

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

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

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

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

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

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

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

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

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in theUnited States, other countries, or both.

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

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

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

Appendix. Notices and Trademarks 21

��

Printed in USA

SC27-6214-00

probe for alcatel-lucent omc-r (corba) 3gpp v5.5: reference guide - ibm … · about this guide the...

Documents