Net Cool

7/22/2019 Net Cool

1/32

IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC(CORBA )

Version 9.0

Reference GuideNovember 4, 2011

SC23-7664-05

7/22/2019 Net Cool

2/32

7/22/2019 Net Cool

3/32

IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC(CORBA )

Version 9.0

Reference GuideNovember 4, 2011

SC23-7664-05

7/22/2019 Net Cool

4/32

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

Edition notice

This edition (SC23-7664-05) applies to version 9.0 of IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC andto all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC23-7664-04.

Copyright IBM Corporation 2007, 2011.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

7/22/2019 Net Cool

5/32

Contents

About this guide . . . . . . . . . . . vDocument control page . . . . . . . . . . . v

Conventions used in this guide . . . . . . . . v

IBM Tivoli Netcool/OMNIbus Probe forEricsson OSS-RC . . . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Firewall considerations . . . . . . . . . . . 3Configuring the probe . . . . . . . . . . . 4Data acquisition . . . . . . . . . . . . . 4

Configuring the probe for specific Ericsson devices 4Device connections through the CORBA interface 5

Retrieving objects . . . . . . . . . . . . 6Status checking . . . . . . . . . . . . 6

Filters for notifications and alarms . . . . . . 6Command line interface . . . . . . . . . 7Peer-to-peer failover functionality . . . . . . 8

Properties and command line options . . . . . . 9Elements . . . . . . . . . . . . . . . 13Error messages . . . . . . . . . . . . . 14ProbeWatch messages . . . . . . . . . . . 16

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

Copyright IBM Corp. 2007, 2011 iii

7/22/2019 Net Cool

6/32

iv IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC: Reference Guide

7/22/2019 Net Cool

7/32

About this guide

The following sections contain important information about using this guide.

Document control page

Use this information to track changes between versions of this guide.

The IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC documentation isprovided in softcopy format only. To obtain the most recent version, visit the IBMTivoli 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

SC23-6023-00 March 16, 2007 First IBM publication.

SC23-7664-00 June 20, 2007 Patch version and release updated.

Resynch property added.

SC23-7664-01 December 14,2007

Patch version and release updated.

Error messages added.

SC23-7664-02 January 15,2010

Summary on page 1updated.

Section added to discuss the properties that need to beconfigured to enable the probe to receive events. See

Configuring the probe for specific Ericsson devices onpage 4.

New properties added to the Properties and commandline options table. SeeProperties and command lineoptions on page 9.

Description for FlushBufferIntervaladded.

SC23-7664-03 March 31, 2011 Installation section replaced byInstalling probes onpage 2.

Firewall considerations on page 3added.

SC23-7664-04 July 1, 2011 Information about operating system conventions addedinConventions used in this guide.

Requirements updated inSummary on page 1.

SC23-7664-05 November 4,2011

Summary on page 1updated.

Conventions used in this guide

All probe guides use standard conventions for operating system-dependentenvironment variables and directory paths.

Copyright IBM Corp. 2007, 2011 v
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.namomnibus.doc/welcome_ptsm.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.namomnibus.doc/welcome_ptsm.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.namomnibus.doc/welcome_ptsm.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.tivoli.namomnibus.doc/welcome_ptsm.htm

7/22/2019 Net Cool

8/32

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 the

standard UNIX conventions such as$variablefor 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 and

backward 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 systemcurrently supported by Netcool/OMNIbus.

Table 2. Directory names for the arch variable

Operating system Directory name represented byarch

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 IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC: Reference Guide

7/22/2019 Net Cool

9/32

IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC

The Ericsson Operation and Support System Radio and Core (OSS-RC) is anelement manager for the Ericsson 3G core network. The Probe for Ericsson OSS-RC

connects to Ericsson OSS-RC versions 2.x, 3.x, 4.x, 5.x, 6.x, 7.x, 8.x, 10.x, and 11.x;RANOS; and CN-OSS using the standard CORBA interface.

The probe complies with the following 3GPP standards:

v TS 32.300 v4.1.1 Name Convention for Managed Objects (Release 4)

v TS 32.111-2 v3.2.0 Information Service (Release 99)

v TS 32.111-3 v3.2.0 Corba Solution Set (Release 99)

The following topics describe the probe and how it works:

v Summary

v Installing probes on page 2

v Firewall considerations on page 3v Configuring the probe on page 4

v Data acquisition on page 4

v Properties and command line options on page 9

v Elements on page 13

v Error messages on page 14

v ProbeWatch messages on page 16

Summary

Each probe works in a different way to acquire event data from its source, and

therefore has specific features, default values, and changeable properties. Use thissummary information to learn about this probe.

The following table summarizes the probe.

Table 3. Summary

Probe target Ericsson OSS-RC version 2.x, 3.x, 4.x, 5.x, 6.x, 7.x, 8.x,10.x, and 11.x;

Ericsson RANOS

Ericsson CNOSS

Probe executable name nco_p_ericsson_oss_rc

Package Version 9.0Probe supported on For details of supported operating systems, see the

following Release Notice on the IBM Software Supportwebsite:

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

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

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

Copyright IBM Corp. 2007, 2011 1
https://www-304.ibm.com/support/docview.wss?uid=swg21502793https://www-304.ibm.com/support/docview.wss?uid=swg21502793https://www-304.ibm.com/support/docview.wss?uid=swg21502793https://www-304.ibm.com/support/docview.wss?uid=swg21502793

7/22/2019 Net Cool

10/32

Table 3. Summary (continued)

Minimum requirements A currently supported version of IBM TivoliNetcool/OMNIbus.

Nonnative Probe Server: probe-nonnative-base-14

Command Port library: probe-command-port-3

Java Runtime Environment (JRE) 1.5

IBM Object Request Broker (IBM ORB, supplied withNetcool/OMNIbus)

Connection method CORBA

Remote connectivity The probe can connect to a remote device using aCORBA interface.

Licensing Electronic licensing was deprecated with the release of IBM 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(SC14-7604-00).

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

Federal Information ProcessingStandards (FIPS)

IBM Tivoli Netcool/OMNIbus V7.2.1, 7.3.0 and 7.3.1 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.htmFor details about configuringNetcool/OMNIbus for FIPS 140-2 mode, see IBM TivoliNetcool/OMNIbus Installation and Deployment Guide(SC14-7604).

Installing probes

All 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 PassportAdvantage 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 IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC: Reference Guide
http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htmhttp://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.htmlhttp://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htmhttp://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htm

7/22/2019 Net Cool

11/32

2. Installing the probe using the installation package.

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

Firewall considerations

When 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 mustdetermine 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, youmust determine the incoming port on which the probe will listen and to which

the target system will connect.3. If each host is secured with its own firewall, you must determine the following

four ports:

a. The outgoing port (or port range) for the probe.

b. The hostname and port of the target system.

c. The outgoing port on which the target system sends events if the probe isrunning 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 theORBLocalPortproperty. The default value for this property is 0, which means that

an available port is selected at random. If the probe is behind a firewall, the valueof the ORBLocalPortproperty 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.

IBM Tivoli Netcool/OMNIbus Probe for Ericsson OSS-RC 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.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_install_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_install_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_install_intro.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_install_intro.htmlhttp://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

7/22/2019 Net Cool

12/32

Configuring the probe

To configure the probe prior to running it, you must ensure the installationrequirements are met. You must also update the rules file using probe-specificinformation.

Updating the rules file

The probe is supplied with a lookup table (Corba_3gpp_V320.lookup). This file isinstalled in the following location: $OMNIHOME/probes/includes/

This file is referenced in the rules file by the following command:

include "../includes/Corba_3gpp_V320.lookup"

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.

Data acquisition

The probe connects to Ericsson OSS-RC through a Common Object Request BrokerArchitecture (CORBA) interface. CORBA is an Object Management Groupspecification that provides a standard interface definition between objects in adistributed environment; that is, it allows applications to communicate with oneanother regardless of where they are located or who has designed them.

On startup, the probe initializes an ORB and connects to the Ericsson ElementManager's Alarm IRP (OSS-RC, RANOS and CN-OSS) and Event IRP objects. Theprobe then resynchronizes with the Ericsson Element Manager and acquires thealarms/stateless events currently stored in the Ericsson Element Manager.

The probe then processes the acquired alarms/stateless events, setting most

attributes as tokens, and generates an AckAlarmID token. These tokens are sent tothe ObjectServer as events. Once the process is complete, the probe subscribes tothe online events, processes them, and then forwards them to the ObjectServer.

The probe checks the status of the IRP agent every 60 seconds. You can change thisfrequency if required using theAgentheartbeatproperty.

The following topics describe how the probe acquires data:

v Configuring the probe for specific Ericsson devices

v Device connections through the CORBA interface on page 5

v Retrieving objects on page 6

v Status checking on page 6

v Filters for notifications and alarms on page 6

v Command line interface on page 7

v Peer-to-peer failover functionality on page 8

Configuring the probe for specific Ericsson devicesThe Probe for Ericsson OSS-RC connects to the following Ericsson devices:

v Ericsson OSS-RC

v Ericsson RANOS.

v Ericsson CN-OSS.


7/22/2019 Net Cool

13/32

To enable the probe to receive events from the Ericsson device, you must specifythe following property values:

For Ericsson OSS-RC version 2.x

Set the Alarmirp property to com.ericsson.nms.fm.ALARM_IRP_CIRPAgent1 tospecify the appropriate alarm IRP object reference.

Set the Notificationirp property to com.ericsson.nms.fm.cif.service.NAConsumer tospecify the appropriate notification IRP object.

For Ericsson OSS-RC version 3.x and later

Set the Alarmirp property to com.ericsson.nms.fm_cirpagent.AlarmIRP to specifythe appropriate alarm IRP object reference.

Set the Notificationirp property to com.ericsson.nms.cif.service.NMSNAConsumerto specify the appropriate notification IRP object.

To locate the Naming Service, the probe can use either the NameServiceHost andNSPortproperties to identify the host name and port number of the NamingService, or the probe can use the IOR file specified by the NSIorfile property.

Therefore, the property settings depend on which method the probe will use tolocate the Naming Service. Either set the NameServiceHostproperty towhere the OSS-RC is running and set the NSPortproperty to 49254.

Or set the NSIorfile property to http://where the OSS-RC isrunning:80/ior/ExternalNameService.ior

For Ericsson RANOS

Set the Alarmirp property to com.ericsson.nms.umts.ranos.AlarmService_R1 tospecify the appropriate alarm IRP object reference.

Set the Notificationirp property to com.ericsson.umts.ranos.NotificationService_R1to specify the appropriate notification IRP object.

For Ericsson CN-OSS

Set the Alarmirp property to com.ericsson.nms.fm.ALARM_IRP_CIRPAgent1 tospecify the appropriate alarm IRP object reference.

Set the Notificationirp property tocom.ericsson.nms.fm.cif.service.NMSNAConsumer to specify the appropriate

notification IRP object.

Device connections through the CORBA interfaceThe probe uses the CORBA interface to retrieve alerts from Ericsson OSS-RC. Theprobe can use one of two methods to connect to the device: Interoperable ObjectReference (IOR ) files or the Naming Service.


7/22/2019 Net Cool

14/32

IOR files

If using IOR files, the probe retrieves the object reference of theAlarmIRPOperation from the IOR file that is specified by the AlarmirpFileproperty; the probe retrieves the object reference of the NotificationIRPOperationfrom the IOR file that is specified by the NotificationirpFileproperty. TheAlarmIRPOperation and NotificationIRPOperation servers form a part of the IRP

agent. TheEventirp and EventirpFile properties can be used to retrieve statelessevents from the Ericsson OSS-RC system. Set the Eventirp to property tocom.ericsson.nms.fm_cirpagent.EventIRP to specify the Event IRP Object Reference.Set the EventirpFile property to specify the path to the Event IRP Object Referencefile.

Naming Service

If the AlarmirpFile and NotificationirpFileproperties are not specified, the proberetrieves the object references of the AlarmIRPOperation andNotificationIRPOperation servers from the Naming Service. To locate the NamingService, the probe either uses the NameServiceHostand NSPortproperties toidentify the host name and port number of the Naming Service, or uses the IORfile specified by the NSIorfile property.

The Naming Service uses the values that are specified by the Alarmirp andNotificationirpproperties to retrieve the object references to the IRP objects.

Retrieving objectsThe probe initially receives a list of all active alarms from the AlarmIRPOperationserver. The probe connects to the Event IRP object of the Ericsson ElementManager and retrieves the stateless events. The probe then connects to theNotificationIRPOperation server and uses the CORBA notification push model toreceive new alarms from the server as they are generated.

Status checkingThe probe checks the status of the IRP agent every 60 seconds. You can change thisfrequency if required using theAgentheartbeatproperty.

Filters for notifications and alarmsThe NotificationFilterand 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 NotificationFilterproperty to $h = = 3.

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

To specify that the probe is only sent notifications for a specific managed element,set the NotificationFilterproperty to Managed_Node_Name~$f where $frepresents the element NV_MANAGED_OBJECT_INSTANCE andManaged_Node_Name is the name of the managed object.


7/22/2019 Net Cool

15/32

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 NotificationFilterproperty toSP1'~$'f.

Note: The tilde character (~) is required because spaces cannot be entered in thisproperty. For string comparisons, the first argument is considered to be contained

in the second argument; which is why $f is listed second to the literal.

The following table displays the token mappings for use with the AlarmFilterandNotificationFilterproperties.

Table 4. Token mappings

Element Token

NV_NOTIFICATION_ID a

NV_CORRELATED_NOTIFICATIONS b

NV_EVENT_TIME c

NV_SYSTEM_DN d

NV_MANAGED_OBJECT_CLASS eNV_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

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

Command line interfaceThe probe has a Command Line Interface (CLI) that you can use to performcommands, for example, to acknowledge alarms or to request a fullresynchronization of the CORBA interface.

To use the CLI, you must use the CommandPort property in the properties file tospecify a port through which commands are sent. When you want to performcommands, Telnet to this port. The following table describes the commands thatyou can use with the CLI.


7/22/2019 Net Cool

16/32

Table 5. CLI commands

Command Description

acknowledge_alarm Use this command to acknowledge an alarm inthe 3GPP interface.Note: This command takes as a parameter theNV_ALARM_ID of the alarm beingacknowledged. Only one alarm can beacknowledged at a time. This command also usesthe values specified by the AckSystemId andAckUserIdproperties in the properties file.

get_event_list Use this command to display a list of events fromEvent IRP.

get_event_list_filter Use this command to perform a get_event_listusing this filter.

help Use this command to display online help aboutthe CLI.

resynch_all Use this command to perform a fullresynchonization with the 3GPP interface.

resynch_filter Use this command to perform partialresynchronization with the 3GPP interface.Note: This command takes as a parameter a filterin the same format as the AlarmFilterproperty.

unacknowledge_alarm Use this command to unacknowledge an alarm inthe 3GPP interface.

userid_acknowledge_alarm Use this command to acknowledge an alarm inthe 3GPP interface by specifying theNV_ALARM_ID of the alarm beingacknowledged and the NV_ACK_USER_ID . Theformat of the alarm is: ID userID.

userid_unacknowledge_alarm Use this command to unacknowledge an alarm inthe 3GPP interface by specifying the

NV_ALARM_ID of the alarm beingacknowledged and the NV_ACK_USER_ID.

version Use this command to display the version of theprobe.

Note: Because the CLI is based upon Telnet connections, you can connect to theprobe from anywhere. This means that simple scripts can be set up to allow usersto acknowledge selected events from the event list by creating desktop tools toTelnet to the probe, send a command, and then close the connection.

Peer-to-peer failover functionality

The probe supports failover configurations where two probes run simultaneously.One probe acts as the master probe, sending events to the ObjectServer; the 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.


7/22/2019 Net Cool

17/32

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 options

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

Table 6. Properties and command line options

Property name Command line option Description

AckSystemIdstring -acksystemid string Use this property to specify theprocessing system on which the IRPManager runs. This is used by theacknowledge_alarm CLI function.

The default is "".

AckUserIdstring -ackuserid string Use this property to specify the nameof the user acknowledging the alarm.This is used by the acknowledge_alarmCLI function.

The default is "".

Agentheartbeatinteger -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 -alarmfilterstring Use this property to specify the filterthe alarm IRP uses to limit the alarmssent to the probe.

The default is "".


7/22/2019 Net Cool

18/32

Table 6. Properties and command line options (continued)


Alarmirpstring -alarmirpstring Use this property to specify the alarmIRP object reference.

The default iscom.ericsson.nms.fm_cirpagent.

AlarmIRP.Note: The value required for thisproperty is version-specific. SeeConfiguring the probe for specificEricsson devices on page 4

AlarmirpFilestring -alarmirpfilestring Use this property to specify the path tothe Alarm IRP object reference.

The default is "".

CommandPortinteger -commandport integer Use this property to specify the port towhich users can Telnet to communicatewith the 3GPP interface using theCommand Line Interface (CLI)

supplied with the probe.

The default is 6790.

CommandPortLimitinteger

-commandportlimitinteger

Use this property to specify themaximum number of Telnetconnections that can be made to theprobe.

The default is 10.

DiscardBlankAddTextstring

-discardblankaddtextstring

Use this property to specify whetherthe probe discards blank additional lineelements.

The default is true.

EventFilterstring -eventfilter string Use this property to specify the filterused by the EventIrp.

The default is "".

Eventirpstring -eventirpstring Use this property to specify the EventIRP Object Reference.

The default is "".

EventirpFilestring -eventirpfilestring Use this property to specify the fullpath to the Event IRP Ior file.

The default is "".

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


7/22/2019 Net Cool

19/32



GetEventListstring -geteventlist string Use this property to specify whetherevents are received from Event IRP.

The default is false: Events are notreceived from Event IRP.

GetEventListOnStartstring

-geteventlistonstartstring

Use this property to specify whetherevents are received from Event IRPduring startup.

The default is false: Events are notreceived from Event IRP duringstartup.

GetFMError Messagesstring

-getfmerror messagesstring

Use this property to specify whetherthe probe subscribes to FaultManagement Error Messages.

The default is false.

NameServiceHoststring -nameservicehost string Use this property to specify the host onwhich the naming service is running.

The default is "".

NotificationFilterstring -notificationfilter string Use this property to specify the filterthe notification IRP uses to limit thenotifications sent to the probe.

The default is "".

Notificationirpstring -notificationirpstring Use this property to specify theNotification IRP object.

The default iscom.ericsson.nms.cif.service.

NMSNAConsumer.Note: The value required for thisproperty is version-specific. SeeConfiguring the probe for specificEricsson devices on page 4.

NotificationirpFilestring

-notificationirpfilestring Use this property to specify the path ofthe notification IRP IOR file.

The default is "".

NSIorfilestring -nsiorfilestring Use this property to specify theNaming Service object reference file.

The default is "".

NSPortinteger -nsport integer Use this property to specify the port onwhich the Naming Service is running.

The default is 0.

ORBCharEncodingstring

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

The default is UTF8.


7/22/2019 Net Cool

20/32



ORBLocalHostNamestring

-orblocalhostnamestring Use this property to specify the host towhich the ORB connects.

The default is "".

ORBLocalPortinteger -orblocalport integer Use this property to specify the portnumber for the ORB to listen on.

The default is 0.

ORBWCharDefaultstring

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

Resynchstring -resynch string Use this property to specify whetherthe probe performs a resynchronizationat startup. The possible values are:

false - probe does not perform aresynchronization

true - probe performs aresynchronization


Retrystring -retrystring Use this property to specify whetherthe probe attempts to reconnect to thesystem following a timeout. Thepossible values are:

false: The probe does not attempt toreconnect to the system

true: The probe attempts to reconnectto the system


Timeout integer -timeoutinteger Use this property to specify the time(in seconds) that the probe allows theport to be silent before disconnecting.

The default is 0 (probe neverdisconnects).

TimeTickinteger -timetickinteger Use this property to specify the time(in minutes) that Ericsson OSS-RC

sessions are kept open.The default is 15.


7/22/2019 Net Cool

21/32

Elements

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

The following table describes the elements that the probe generates:

Table 7. Elements

Element name Element description

ATTRIBUTE_VALUE(element_name) This element specifies the value of an elementthat is being monitored. This element isgenerated dynamically and its content isdependent on the IRPAgent.Note: Theelement_name part of this elementand the next element can be the name of any ofthe other elements in this table.

ATTRIBUTE_VALUE_CHANGE (element_name) This element specifies the managed objectattributes whose value changes are beingmonitored.

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

EVENT_NAME This element specifies the extended event typefor this IRP.

EVENT_TYPE This element specifies the event type of thenotification.

NV_ACK_STATE This element specifies the acknowledgementstate of the alarm.

NV_ACK_SYSTEM_ID This element specifies the system ID of the IRPManager processing the notification.

NV_ACK_TIME This element specifies the time at which the

user acknowledged the alarm.

NV_ACK_USER_ID This element specifies the last user who haschanged the acknowledgement state.

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

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

NV_BACK_UP_OBJECT This element specifies the distinguished Name(DN) of the backup object.

NV_BACKED_UP_STATUS This element specifies whether the object hasbeen backed up.

NV_CORRELATED_NOTIFICATIONS_notif_ID_Set

This element specifies the set of notifications towhich this notification is considered to becorrelated. This element is generateddynamically and its content is dependent onthe IRPAgent.

NV_CORRELATED_NOTIFICATIONS_ SOURCE This element specifies the source of thenotification set.


7/22/2019 Net Cool

22/32

Table 7. Elements (continued)

Element name Element description

NV_EVENT_TIME This element specifies the time at which theevent occurred.

NV_MANAGED_OBJECT_INSTANCE This element specifies the managed objectinstance of the network resource.

NV_NOTIFICATION_ID This element specifies the identificationinformation of the notification.

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

NV_PROBABLE_CAUSE This element specifies further informationabout the probable cause of the alarm.

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

NV_SPECIFIC_PROBLEM This element specifies further informationabout the problem to which the notificationrelates.

NV_SYSTEM_DN This element specifies the distinguished name(DN) used to identify the system.

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

NV_TREND_INDICATION This element specifies how an observedcondition has changed.

RESYNC_EVENT This element specifies whether the event wasobtained by running the resynchronizationfunction getalarm_list(). Possible values are:

v false: The event was obtained after the probesubscribed to the notification service forreal-time alarms

v

true: The event was obtained by running theresynchronization function

Error messages

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


7/22/2019 Net Cool

23/32

Table 8. Error messages

Error Description Action

Command Port Erroroccurred

Command Port Failedto get CommandPortLimitproperty - using IOR

Command Port Failedto get property CommandPort

Command Port Failedto open listening socket,shutting down Thread!

Command Port Failedto send probewatch message

Command Port hostFailed to closecommand socket

Command Port hostFailed to get socket IO

Command Port hostFailed to read command

Command Port Threadshutting down due to error!

NetcoolIRPManager: Failed toacknowledge_alarms()

NetcoolIRPManager: Failed toUnacknowledge_alarms()

A problem occurred withthe command portfunctionality.

Check that you havespecified the commandport correctly.

Check the connection

between the probe and thecommand port.

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

InvalidParameter Exception

NetcoolIRPManager: Exception

occurred.Stack trace to stderr

OperationNotSupportedException

Unexpected CORBA Exception

There is a problem with thecommand portfunctionality.

Refer to your CORBAdocumentation.

COMMUNICATION FAILUREException i.e Server is dead

GetSubscriptionStatusException

NetcoolIRPManager:BothNameServiceHost and NSPortproperty needs to be set

NetcoolIRPManager:Alarmirpproperty needs to be set

NetcoolIRPManager:Notificationirpproperty needs to be set

NetcoolIRPManager: Failedto perform resynch

The probe cannot connectto the server.

Check that the EricssonOSS-RC server is runningcorrectly.

Check that you havespecified the parameterscorrectly in the propertiesfile.


7/22/2019 Net Cool

24/32

Table 8. Error messages (continued)

Error Description Action

Error Failed to parse eventcompletely

Name is null, cannot createElement

NetcoolIRPManager: CategoryValue NOT supported:Discarding Alarm

NetcoolIRPManager: Error whenparsing event

NetcoolIRPManager: Failed tosend event

The probe cannot parse thealarm; this is probably

because the alarm is not ina format that the probe canunderstand.

Check that the EricssonOSS-RC server is runningcorrectly.

Failed to get properties The probe is unable toopen the properties file.

Check the properties file orthe command line andensure the parameter ispointing to the correctdestination.

Failed to get timeout

property value, defaultingto 0

This is message generated

by the IRP Manager.

This message is intended

for use when debugging.

NetcoolIRPManager: StackTrace to stderr:

TheTimeoutproperty hasnot been set.

Check the value for theTimeout property; changethis value if necessary.

ProbeWatch messages

During 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 raw probe Watch error messages that the probegenerates. For information about generic error messages, see the IBM TivoliNetcool/OMNIbus Probe and Gateway Guide, (SC14-7608).

Table 9. ProbeWatch messages

ProbeWatch message Description Triggers or causes

Will listen for commandson port numbercommand_port value

The probe is listening forcommands on the specifiedport.

The specified port is ready toreceive commands.

[Command Port] Failed tosend probewatch message

The probe was unable tosend the alert, command, orProbeWatch messagespecified to the ObjectServer.

The ObjectServer is notavailable, or there is aproblem witht the connectionwith the ObjectServer.

Failed to listen forcommands on port numbercommand_port value : +e.toString()

The probe could not openthe socket specified by theport to listen for commands.

The specified port is in usefor another process.

START SYNCHRONIZATION The probe is synchronizingthe events.

The probe has startedreceiving alarms from thealarm list.


7/22/2019 Net Cool

25/32

Table 9. ProbeWatch messages (continued)

ProbeWatch message Description Triggers or causes

SYNCHRONIZATION ERROR - +e.toString()

The probe could not get newalarms.

The probe failed to get thealarm list, or failed toperform resynchronization ofalarms.

END SYNCHRONIZATION The probe is closing thesynchronization process.

The probe has finishedreceiving alarms from thealarm list.


7/22/2019 Net Cool

26/32


7/22/2019 Net Cool

27/32

Appendix. Notices and Trademarks

This appendix contains the following sections:

v Notices

v Trademarks

Notices

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

IBM may not offer the products, services, or features discussed in this 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 may

be 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 IMPLIED

WARRANTIES 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. 2007, 2011 19

7/22/2019 Net Cool

28/32

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 agreement

between 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 been

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


7/22/2019 Net Cool

29/32

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 operating

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

Trademarks

IBM, 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 Corporation

in 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

7/22/2019 Net Cool

30/32


7/22/2019 Net Cool

31/32

7/22/2019 Net Cool

32/32

Printed in USA

SC23-7664-05

Documents

Net Cool