IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumen ... · PDF fileperformance analysis of...

IBM® Tivoli® Netcool/OMNIbus Probe for ZTE M31NetNumen WCDMA and U31 Wireless (CORBA)Version 6.0

Reference GuideNovember 7, 2014

SC23-9571-04

��

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

Edition notice

This edition (SC23-9571-04) applies to version 6.0 of the IBM Tivoli Netcool/OMNIbus Probe for ZTE NetNumenM31 WCDMA (CORBA) and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC273-9571-03.

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

Contents

About this guide . . . . . . . . . . . vDocument Control Page . . . . . . . . . . vConventions used in this guide . . . . . . . . vi

IBM Tivoli Netcool/OMNIbus Probe forZTE M31 NetNumen WCDMA and U31Wireless (CORBA) . . . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 3Firewall considerations . . . . . . . . . . . 3Setting the target EMS . . . . . . . . . . . 4Data acquisition . . . . . . . . . . . . . 5

Connecting to the CORBA interface. . . . . . 5Retrieving alarms and notifications . . . . . . 6XML files . . . . . . . . . . . . . . 6Persistent subscriptions . . . . . . . . . . 7

Timeout . . . . . . . . . . . . . . . 7Backoff strategy . . . . . . . . . . . . 7Filtering notifications and alarms . . . . . . 7Lookup table . . . . . . . . . . . . . 9Command line interface . . . . . . . . . 9Peer-to-peer failover functionality . . . . . . 10

Properties and command line options. . . . . . 11Elements . . . . . . . . . . . . . . . 18Error messages . . . . . . . . . . . . . 20ProbeWatch messages . . . . . . . . . . . 25Running the probe . . . . . . . . . . . . 26

Appendix. Notices and Trademarks . . 27Notices . . . . . . . . . . . . . . . . 27Trademarks . . . . . . . . . . . . . . 29

© Copyright IBM Corp. 2008, 2014 iii

iv IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumen WCDMA and U31 Wireless: Reference Guide

About this guide

The following sections contain important information about using this guide.

Document Control PageUse this information to track changes between versions of this guide.

The IBM Tivoli Netcool/OMNIbus Probe for ZTE NetNumen M31 WCDMA(CORBA) documentation is provided in softcopy format only. To obtain the mostrecent version, visit the IBM® Tivoli® Knowledge Center:

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

Table 1. Document modification history

Document version Publication date Comments

SC23-9571-00 July 25, 2008 First IBM publication.

SC23-9571-01 February 25, 2011 Support added for RAN (LTE) and CN (LTE).

“Summary” on page 1 updated.

Description for FlushBufferInterval added.

Installation section replaced by “Installingprobes” on page 3.

“Firewall considerations” on page 3 added.

The following properties were added to“Properties and command line options” on page11:

v EncodingTo

v FileTransferIrpName

v InstanceID

v ORBDebug

v ORBDebugFileName

v ORBDebugFilePath

v TargetEMS

v ValidateXML

v XSDFile

v XSDFtpCommand

v XSDFtpPassword

© Copyright IBM Corp. 2008, 2014 v



Table 1. Document modification history (continued)

Document version Publication date Comments

SC23-9571-02 March 02, 2012 Information about operating system conventionsadded in “Conventions used in this guide.”

Requirements and multicultural supportinformation updated in “Summary” on page 1.

Information about connecting to the CORBAinterface was updated in “Connecting to theCORBA interface” on page 5.

The following properties were added in“Properties and command line options” on page11:

v ORBCharEncoding

v ORBLocalHost

v ORBWCharDefault

SC23-9571-03 July 06, 2012 Probe target information updated in“Summary” on page 1.

New information added to explain target EMSsettings in “Setting the target EMS” on page 4.

TargetEMS property updated in “Properties andcommand line options” on page 11.

Error messages updated in “Error messages” onpage 20.

ProbeWatch messages updated in “ProbeWatchmessages” on page 25.

SC23-9571-04 November 7, 2014 “Summary” on page 1 updated.

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

vi IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumen WCDMA and U31 Wireless: Reference Guide

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

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

Operating system-specific directory names

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

$OMNIHOME/probes/arch

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

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

Table 2. Directory names for the arch variable

Operating system Directory name represented by arch

AIX® systems aix5

HP-UX PA-RISC-based systems hpux11

HP-UX Integrity-based systems hpux11hpia

Red Hat Linux and SUSE systems linux2x86

Linux for System z® linux2s390

Solaris systems solaris2

Windows systems win32

OMNIHOME location

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

About this guide vii

viii IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumen WCDMA and U31 Wireless: Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumenWCDMA and U31 Wireless (CORBA)

ZTE NetNumen U31 element management system (EMS) is an integrated networkoperation and maintenance system that controls different interconnected networksand performs integrated network fault management, fault location, andperformance analysis of WCDMA, LTE, and GSM networks. It provides a uniformCORBA, northbound, fault management interface, and can be used to manage bothfixed and mobile network equipment.

ZTE NetNumen U31 replaces (amongst other systems) ZTE NetNumen M31 RAN(Radio Access Network) and ZTE NetNumen M31 CN (Core Network). In thisreference documentation, the ZTE U31, M31 RAN, and M31 CN are referred tocollectively as the ZTE EMS.

The Probe for ZTE M31 NetNumen WCDMA and U31 Wireless (CORBA) collectsalarms from the ZTE EMS using a Common Object Request Broker Architecture(CORBA) 3rd Generation Partnership Project (3GPP) interface.

The probe is described in the following sections:v “Summary”v “Installing probes” on page 3v “Firewall considerations” on page 3v “Setting the target EMS” on page 4v “Data acquisition” on page 5v “Properties and command line options” on page 11v “Elements” on page 18v “Error messages” on page 20v “ProbeWatch messages” on page 25v “Running the probe” on page 26

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

The following table provides a summary of the Probe for ZTE NetNumen M31WCDMA (CORBA).

© Copyright IBM Corp. 2008, 2014 1

Table 3. Summary

Probe targets ZTE NetNumen M31-R (RAN and CN) V3.10

ZTE NetNumen M31 (CN) V12.11.30

ZTE NetNumen M31 (UMTS RAN) V12.10.032FP003 andV12.11.40B5

ZTE NetNumen M31 (LTE RAN) V12.10.040j

ZTE NetNumen U31 R06 V12.12.10 (which is another EMSR06)

ZTE NetNumen U31 R07 V12.12.20 and V12.11.40.P01.B7

Probe executable name nco_p_zte_corba_wcdma

Probe installation package omnibus-arch-probe-nco-p-zte-corba-wcdma-version

Package version 6.0

Probe supported on For details of supported operating systems, see thefollowing Release Notice on the IBM Software Supportwebsite:

http://www.ibm.com/support/docview.wss?uid=swg21599279

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

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

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

Connection method CORBA

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

Multicultural support Available

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

Peer-to-peer failoverfunctionality

Available

IP environment IPv4 and IPv6

Federal Information ProcessingStandards (FIPS)

IBM Tivoli Netcool/OMNIbus V7.3.0, 7.3.1, 7.4.0, and 8.1use the 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.

2 IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumen WCDMA and U31 Wireless: 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

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

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

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

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

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

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.

IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumen WCDMA and U31 Wireless (CORBA) 3

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

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

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

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

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

Setting the target EMSUse the TargetEMS property to specify which version of the ZTE EMS that you arerunning the probe against.

Different versions of the ZTE EMS use different CORBA interface definitionlanguage (IDL) files to specify the interfaces that CORBA objects present to theprobe. Some of the IDL files used are specific implementations by individualcommunications companies. The value specified by the TargetEMS property tellsthe probe which set of IDL files are being used when it is communicating with aparticular version of the ZTE EMS.

The following table lists the appropriate TargetEMS property setting for eachsupported ZTE EMS and its associated IDL files.

Table 4. Property settings for each supported ZTE EMS and IDL files

TargetEMS propertysetting Target ZTE EMS IDL files

RAN M31 UMTS RAN or LTERAN

Hong Kong CSL IDL

CN M31 CN Hong Kong CSL IDL

M31_CN_UNICOM M31 CN China Unicom IDL

M31_RAN_UNICOM M31 UMTS RAN China Unicom IDL

U31 U31 R06 (only for ChinaIDL)

U31 R07

Default universal IDL or ChinaUnicom IDL

U31_HKCSL U31 R07 Hong Kong CSL IDL


Data acquisitionThe probe gathers events from ZTE EMS using a 3GPP CORBA interface.

Data acquisition is further described in the following topics:v “Connecting to the CORBA interface”v “Retrieving alarms and notifications” on page 6v “XML files” on page 6v “Persistent subscriptions” on page 7v “Timeout” on page 7v “Backoff strategy” on page 7v “Filtering notifications and alarms” on page 7v “Lookup table” on page 9v “Command line interface” on page 9v “Peer-to-peer failover functionality” on page 10

Connecting to the CORBA interfaceThe probe acts as an Integration Reference Point (IRP) Manager and connects tothe ZTE EMS using a 3GPP CORBA interface. The probe connects to the interfaceusing Interoperable Object Reference (IOR) files.

Before it begins retrieving events from the ZTE EMS, the probe acquires theEntryPointIRP CORBA object. It gets this from the local IOR file specified by theEntryPointIrpFile property.

After it has acquired the EntryPointIRP object, the probe acquires the AlarmIRP andNotificationIRP objects. It needs the AlarmIRP object to perform resynchronizationand the NotificationIRP object to get real time alarms.

The probe uses the value specified by the AlarmIrpName property to locate theAlarmIRP object within the EntryPointIRP object. It uses the value specified by theNotificationIrpName property to locate the NotificationIRP object within theEntryPointIRP object.

Using FTP

If the Entry Point IRP file is on a remote system, the probe uses an FTP commandto retrieve it. To enable this, you must specify the following value for theEntryPointIrpFtpCommand property:

ftp://user:password@host/path

Where user and host are the user name and host name of the Entry Point IRPserver, password is specified by the FtpPassword property, and path is the location ofthe Entry Point IRP file as specified by the EntryPointIrpFile property.

Note: Encrypt the password using the nco_g_crypt utility supplied withNetcool/OMNIbus and use the encrypted string as the value of the FtpPasswordproperty. For more information about encrypting passwords, see the IBM TivoliNetcool/OMNIbus Administration Guide (SC14-7605).


Retrieving alarms and notificationsIf 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.

XML filesIf the number of alarms in the ZTE EMS exceeds a maximum number (asconfigured in the EMS), the EMS puts all the active alarm data into an XML file.The probe then parses the XML file to retrieve the alarm data.

If the probe is running against ZTE NetNumen M31 CN, you can make the probevalidate the XML file against an XML schema document (XSD) before processingthe alarm data. If the probe is running against ZTE NetNumen M31 RAN, theprobe parses the XML file without validating it first.

The properties related to XML validation can only be used when the value of theTargetEMS property is CN.

To enable XML validation, specify a value of true for the ValidateXML propertyand specify the location of the XML schema using the XSDFile property.

Using FTP

If the XML schema file is on a remote system, the probe can retrieve it over FTP.To enable this, you must specify the following value for the XSDFtpCommandproperty:

ftp://user:password@host/

Where user and host are the user name and host name of the server where theschema is located, and password is specified by the XSDFtpPassword property.

Note: Encrypt the password using the nco_g_crypt utility supplied withNetcool/OMNIbus and use the encrypted string as the value of theXSDFtpPassword property. For more information about encrypting passwords, seethe IBM Tivoli Netcool/OMNIbus Administration Guide (SC14-7605).


Persistent subscriptionsThe probe can maintain a subscription to the ZTE EMS across sessions.

To maintain a subscription across sessions, specify a value of true for thePersistentSubscription property.

If this property is set to false, the probe creates a new subscription to the ZTE EMSeach time it makes a connection.

TimeoutThe probe has a timeout facility that allows it to disconnect from the system ifthere has been no activity for a predefined amount of time.

You can use the Timeout property to specify how long the probe waits beforedisconnecting. The default is 0, which instructs the probe to maintain theconnection indefinitely.

Backoff strategyIf the Retry property is set to true, and the probe fails to establish a connection orloses an existing connection to the device, the probe reverts to a backoff strategy.

The probe's backoff strategy is to try to reestablish a connection at successiveintervals of one second, two seconds, four seconds, eight seconds, and so on, up toa maximum of 4096 seconds. When the maximum retry interval is reached, theprobe stops trying to reconnect and will not try again until it is restarted.

Filtering notifications and alarmsYou can use the NotificationFilter and AlarmFilter properties to limit thealarms and notifications that the probe acquires from the ZTE EMS.

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

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

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

You can use e and h as notification filter or alarm filter properties.

If the probe is acquiring events from ZTE LTE RAN, you can use c, d, e, f, g,h, l, m, n, s, y, z, jj, b, kk, a, k, ll, u, mm for alarm filtering, and c, d,e, b.time, h for notification filtering.

If the probe is acquiring events from ZTE LTE CN, you can use c, d, e, f, g ,h,k.time, l, m, n, s, y, z, b.time for alarm filtering, and c, d, e, b.time fornotification filtering.

Note: To filter for b.time or b, the values must be in corba time and not real time.


The following table lists the token mappings that can be used with theAlarmFilter and NotificationFilter properties:

Table 5. Token mappings

Element Token

NV_NOTIFICATION_ID a

NV_EVENT_TIME b

NV_SYSTEM_DN c

NV_MANAGED_OBJECT_CLASS d

NV_MANAGED_OBJECT_INSTANCE e

NV_ALARM_ID f

NV_PROBABLE_CAUSE g

NV_PERCEIVED_SEVERITY h

NV_SPECIFIC_PROBLEM i

NV_ADDITIONAL_TEXT j

NV_ACK_TIME k

NV_ACK_USER_ID l

NV_ACK_SYSTEM_ID m

NV_ACK_STATE n

NV_COMMENTS 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_CORRELATED_NOTIFICATIONS w

NV_REASON x

CLEAR_USER_ID y

CLEAR_SYSTEM_ID z

NV_ALARM_LIST_ALIGNMENT_REQUIREMENT ff

NV_SERVICE_USER gg

NV_SERVICE_PROVIDER hh

NV_SECURITY_ALARM_DETECTOR ii

NV_VENDOR_SPECIFIC_ALARM_TYPE jj

NV_ALARM_RAISED_TIME kk

NV_ALARM_CLEARED_TIME ll

NV_ALARM_CHANGED_TIME mm

NV_NOTIFICATION_CATEGORY_SET zz

AI_VS_PERCEIVED_SEVERITY ai_ps

AI_VS_ALARM_TYPE ai_at

AI_VS_OTHER ai_vs_other


Lookup tableThe probe is supplied with a lookup table that contains details of the various typesof alarms that ZTE EMS generates. You might need to update the rules file toinclude the path to the lookup table.

At installation, the Corba_zte_wcdma.lookup file supplied with the probeinstallation package is installed to the following location:

$OMNIHOME/probes/includes/

The following line in the rules file references the lookup file:

include "../includes/Corba_zte_wcdma.lookup"

Note: The include command assumes that the probe is run from the standard$OMNIHOME/probes/ directory. If you are running the probe from a differentdirectory, replace “..” with the absolute directory path to the lookup file. Do notuse the $OMNIHOME environment variable in this directory path.

Command line interfaceThe probe is supplied with a Command Line Interface (CLI). This interface allowsyou to execute commands using the probe to acknowledge alarms or request a fullresynchronization.

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.

Note: If there is a firewall between the probe and the ZTE EMS, keep thefollowing ports open: TCP 21115, TCP 21126, and TCP 21111.

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

Table 6. CLI commands

Command Description

exit/quit Use this command to close the connection.

help Use this command to display online help aboutthe CLI.

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

Resynchronization using the command line isonly possible when the Resynch property is set totrue.

resynch_filter filter Use this command to perform partialresynchronization with the 3GPP interface.

This command uses the filter specified by theAlarmFilter property as a parameter.


Table 6. CLI commands (continued)

Command Description

userid_acknowledge_alarm alarm_iduser_id

Use this command to acknowledge an alarm inthe 3GPP interface by specifying the NV_ALARM_IDidentifier of the alarm and the user identifier ofthe user acknowledging the alarm.

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

userid_unacknowledge_alarm alarm_iduser_id

Use this command to unacknowledge an alarm inthe 3GPP interface by specifying the NV_ALARM_IDidentifier of the alarm and the user identifier ofthe user acknowledging the alarm.

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

userid_clear_alarm alarm_id user_id Use this command to clear an alarm byspecifying the NV_ALARM_ID identifier of the alarmand the user identifier of the user acknowledgingthe alarm.

Before using this command, you must specify avalue for the ClearSystemId property.

userid_comment_alarm alarm_id user_idcommentText

Use this command to add comments to an alarmby specifying the NV_ALARM_ID identifier of thealarm, the user identifier of the user making thecomment, and the text of the comment.

Before using this command, you must specify avalue for the CommentSystemId property.

version Use this command to display the version of theprobe.

CLI scripts

Because the CLI uses Telnet connections, you can connect to the probe fromanywhere by creating a desktop tool to open a Telnet connection, send a command,and then close the connection. This means that simple scripts can be set up toallow users to acknowledge selected events from the IBM Tivoli Netcool/OMNIbusevent list.

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

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


Example property file settings for peer-to-peer failover

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

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

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

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

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

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

Table 7. Properties and command line options

Property name Command line option Description

AckSystemId string -acksystemid string Use this property to specify thesystem identifier to use whenacknowledging alarms using theCLI.

The default is Default.

Note: You must provide thesystem ID of the processingsystem instead of the default nullvalue.


Table 7. Properties and command line options (continued)


Agentheartbeat integer -agentheartbeat integer Use this property to specify thefrequency (in seconds) with whichthe probe checks the status of theZTE EMS server.

The default is 300.

AlarmFilter string -alarmfilter string Use this property to specify thefilter that the Alarm IRP uses tolimit the alarms sent to the probe.

The default is "".

AlarmIrpName string -alarmirpname string Use this property to specify thename of the Alarm IRP Agent thatthe probe uses to resolve theAlarmIRP point in the NamingService.

The default is ALARM IRP V1.0.0.

ClearSystemId string -clearsystemid string Use this property to specify thesystem identifier to use whenclearing alarms using the CLI.


CommandPort integer -commandport integer Use this property to specify theport through which you can useTelnet to send commands usingthe CLI.

The default is 6970.

CommandPortLimit integer -commandportlimit integer Use this property to specify themaximum number of Telnetconnections that the probe canmake.

The default is 10.

CommentSystemId string -commentsystemid string Use this property to specify thesystem identifier to use whenadding comments to an alarmusing the CLI.


EncodingTo string -encodingto string Use this property to specify theencoding standard used by theprobe.

The default is ISO-8859-1.

Note: When connecting to a ZTEEMS running in Chinese mode,specify the following value for thisproperty: GB18030.

EntryPointIrpFile string -entrypointirpfile string Use this property to specify thelocation of the EntryPoint IRP file.

The default is "" .




EntryPointIrpFtpCommand string

-entrypointirpftpcommandstring

Use this property to specify thecomplete FTP command that theprobe uses to access a remoteEntry Point IRP file.

The default is "".

FileTransferIrpNamestring

-filetransferirpnamestring

Use this property to specify thename that the probe uses toresolve the FileTransferIRP pointin the Naming Service.

The default is FILETRANSFER IRPV1.0.0.

Note: The default value is for usewith ZTE NetNumen M31 CN.Use the following value for ZTENetNumen M31 RAN:

FileTransfer IRP V1.0

FlushBufferIntervalinteger

-flushbufferintervalinteger

Use this property to specify howoften (in seconds) the probeflushes all alerts in the buffer tothe ObjectServer.

The default is 0 (which instructsthe probe to never flush the alertsto the ObjectServer).

FtpPassword string -ftppassword string Use this property to specify theFTP password that the probe usesto access the Entry Point IRP fileover FTP.

The default is "".

Note: Encrypt the password usingthe nco_g_crypt utility suppliedwith Netcool/OMNIbus.

InstanceId string -instanceid string Use this property to specify aunique identifier for an instance ofthe probe. This property allowsyou to run multiple instances ofthe probe on the same machine.

The default is default.

ManagerIdentifier string -manageridentifier string Use this property to specify thename of the Manager Identifierthat receives all the IRPs.

The default is Netcool.




NotificationCategoriesstring

-notificationcategoriesstring

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

To specify multiple categories,separate them using semicolons, inthe following format:

category1;category2;categoryn

For example, use the followingvalue to subscribe to alarms andheartbeat events:

ALARM IRP V1.0.0; CS IRP V1.0.0

The default is "" (the probesubscribes to all availablenotification categories).

NotificationFilter string -notificationfilter string Use this property to specify thefilter that the Notification IRP usesto limit the notifications sent tothe probe.

This property uses the ExtendedTrader Constraint Language(Extended TCL) syntax defined inthe OMG Notification Servicespecification.

The default is "".

NotificationIrpNamestring

-notificationirpnamestring

Use this property to specify thename that the probe uses toresolve the Notification IRP pointin the Naming Service.

The default is NOTIFICATION IRPV1.0.0.

ORBCharEncoding string -orbcharencoding string Use this property to specify thenative character encoding set usedby the Object Request Broker(ORB) for character data. Thisproperty takes the followingvalues:

v ISO8859_1

v UTF8

The default is ISO8859_1.

Note: If the value of this propertydoes not match the characterencoding set used by the targetsystem, the probe might not beable to perform resynchronizationor get new notifications.




ORBDebug string -orbdebug string Use this property to specifywhether the probe includes ORBmessages in the debug file. Thisproperty takes the followingvalues:

false: The probe does not includeORB messages in the debug file.

true: The probe includes ORBmessages in the debug file.

The default is false.

ORBDebugFileName string -orbdebugfilename string Use this property to specify thename of the ORB debug file.

The default is orb.debug.

ORBDebugFilePath string -orbdebugfilepath string Use this property to specify thelocation of the ORB debug file.

The default is ${OMNIHOME}/log/.

ORBLocalHost string -orblocalhost string Use this property to specify thelocal host used by the server-sideORB to place the server's hostname into the IOR of a remoteobject.

The default is "".

ORBLocalPort integer -orblocalport integer Use this property to specify thelocal port to which the ObjectRequest Broker (ORB) listens.

The default is 0 (the ORB selectsan available port at random).

ORBWCharDefault string -orbwchardefault string Use this property to specify whatwide character (wchar) set theIBM ORB uses whencommunicating with other ORBsthat do not publish a wchar set.This property takes the followingvalues:

v UTF16

v UCS2

The default is UTF16.




PersistentSubscriptionstring

-persistentsub (This isequivalent toPersistentSubscriptionwith a value of true.)

-nopersistentsub (This isequivalent toPersistentSubscriptionwith a value of false.)

Use this property to specifywhether the probe maintains apersistent subscription to the ZTEEMS across sessions. This propertytakes the following values:

true: The probe maintains apersistent subscription to the EMS.

false: The probe does notmaintain a persistent subscriptionto the EMS.


Resynch string -resynch (This isequivalent to Resynch witha value of true.)

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

Use this property to specifywhether the probe requests allexisting active alarms from theZTE EMS before connecting to thenotification service for newalarms. This property takes thefollowing values:

false: The probe does not performresynchronization.

true: The probe performsresynchronization.


Retry string -retry (This is equivalentto Retry with a value oftrue.)

-noretry (This isequivalent to Retry with avalue of false.)

Use this property to specifywhether the probe attempts toreconnect to the ZTE EMS afterlosing the connection. Thisproperty takes the followingvalues:

false: The probe does not attemptto reconnect to the EMS.

true: The probe attempts toreconnect to the EMS.


TargetEMS string -targetems string Use this property to specify thetarget EMS to which the probewill connect to get alerts. Thisproperty takes the followingvalues:

v RAN

v CN

v M31_CN_UNICOM

v M31_RAN_UNICOM

v U31

v U31_HKCSL

The default is RAN.




Timeout integer -timeout integer Use this property to specify thetime period (in seconds) that theprobe waits for the next alarmbefore disconnecting.

The default is 0 (which instructsthe probe to maintain theconnection indefinitely).

TimeTick integer -timetick integer Use this property to specify thelifetime (in minutes) of theNotification IRP session on the3GPP server.

The value of this property mustmatch or exceed the default timetick setting on the ZTE EMSsystem.

The default is 0 (the sessionremains open indefinitely).

ValidateXML string -validatexml (This isequivalent to ValidateXMLwith a value of true.)

-novalidatexml (This isequivalent to ValidateXMLwith a value of false.)

Use this property to specifywhether the probe validates XMLalarm data files received from ZTENetNumen M31 CN. Thisproperty takes the followingvalues:

false: The probe does not validatethe XML file.

true: The probe validates the XMLfile.


XSDFile string -xsdfile string Use this property to specify thelocation of the XML schema file(XSD) used to validate the XMLalarm data file.

The default is "".

XSDFtpCommand string -xsdftpcommand string Use this property to specify thecomplete FTP command that theprobe uses to access the XSD file.

The default is "".

XSDFtpPassword string -xsdftppassword string Use this property to specify thepassword required to access theXSD file over FTP.

The default is "".

Note: Encrypt the password usingthe nco_g_crypt utility suppliedwith Netcool/OMNIbus.


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

The following table describes the elements that the probe generates. Not all theelements described are generated for each event. The elements that the probegenerates depends on the event type.

Table 8. Elements

Element name Element description

AI_VS_ALARM_TYPE This element identifies the alarm typespecific to the vendor.

AI_VS_OTHER This element contains all the other detailsspecific to the vendor.

AI_VS_OTHER_ALARM_LOCATION_n This element provides the topologicaldetails specific to the vendor.

AI_VS_OTHER_ALARM_SEQUENCE_ID This element contains the sequencenumber of the alert.

AI_VS_OTHER_SERVER_ID This element indicates the other serverspecific to the vendor.

AI_VS_OTHER_SYSTEM_TYPE This element shows the type of vendorsystem that generated the alarm.

AI_VS_OTHER_TOPOLOGICAL_ID This element provides the othertopological number specific to the vendor.

AI_VS_PERCEIVED_SEVERITY This vendor specific element indicates therelative level of urgency for operatorattention.

CLEAR_SYSTEM_ID This element identifies the system thatcleared the alarm.

CLEAR_USER_ID This element identifies the user thatcleared the alarm.

NV_ACK_STATE This element shows the acknowledgementstate of the alarm.

NV_ACK_SYSTEM_ID This element shows the system ID of theIRP Manager processing the notification.

NV_ACK_TIME This element shows the time at which theuser acknowledged the alarm.

NV_ACK_USER_ID This element identifies the last user whochanged the acknowledgement state.

NV_ADDITIONAL_TEXT This element provides information aboutthe network element from which the alarmoriginated.

NV_ALARM_CHANGED_TIME This element contains the time when thealarm is changed.

NV_ALARM_CLEARED_TIME This element contains the time when thealarm is cleared.

NV_ALARM_ID This element shows the identificationinformation of the alarm as it appears inthe alarm list.


Table 8. Elements (continued)


NV_ALARM_LIST_ALIGNMENT_REQUIREMENT This element indicates whether the alarmlist requires alignment.

NV_ALARM_RAISED_TIME This element indicates the time when thealarm is raised.

NV_BACK_UP_OBJECT This element shows the DistinguishedName (DN) of the backup object.

NV_BACKED_UP_STATUS This element identifies whether the objecthas been backed up.

NV_COMMENTS This element shows the comments aboutthe alarms.

NV_COMMENTS_SYSTEM_ID This element indicates the system used toraise comments.

NV_COMMENTS_TEXT This element contains the text of thecomment.

NV_COMMENTS_TIME This element mentions the time when thecomment is raised.

NV_COMMENTS_USER_ID This element identifies the user that raisedthe comment.

NV_CORRELATED_NOTIFICATIONS This element shows the correlatednotifications.

NV_CORRELATED_NOTIFICATIONS_notif_ID_Set This element shows the set of notificationsto which this notification is considered tobe correlated. This element is generateddynamically and its content is dependenton the IRP agent.

NV_CORRELATED_NOTIFICATIONS_SOURCE This element shows the source of thenotification set.

NV_EVENT_TIME This element shows the time at which theevent occurred.

NV_MANAGED_OBJECT_CLASS This element shows the managed objectclass of the network resource.

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

NV_MONITORED_ATTRIBUTE This element shows the monitoredattribute of the network resource.

NV_NOTIFICATION_ID This element shows the identificationinformation of the notification.

NV_NOTIFICATION_CATEGORY_SET This element shows the category setinformation of the notification.

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

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

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

NV_REASON This element shows the reason thattriggered the proposed repair action.


Table 8. Elements (continued)


NV_SECURITY_ALARM_DETECTOR This element shows the identifier of thedetector of the security alarm.

NV_SERVICE_PROVIDER This element shows the name of theservice provider.

NV_SERVICE_USER This element provides further informationabout the problem to which thenotification relates.

NV_SPECIFIC_PROBLEM This element provides further informationabout the problem to which thenotification relates.

NV_STATE_CHANGE_DEFINITION This element provides further informationabout the status change of the alarm.

NV_SYSTEM_DN This element provides further informationabout the distinguished name (DN) usedto identify the system.

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

NV_TREND_INDICATION This element indicates how an observedcondition has changed.

NV_VENDOR_SPECIFIC_ALARM_TYPE This element shows the alarm type specificto the vendor.

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

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

Table 9. Error messages

Error Description Action

Parser: ERROR whenparsing an eventexception

An event from the ZTE EMScould not be parsed. Some ofthe event elements mighthave been discarded.

Check the exception part of themessage for more informationabout the cause of the error. Ifyou cannot identify the causeof the error, contact IBMSoftware Support or the ZTEEMS administration team.

Parser: Stack Trace tostderr: exception

The probe encountered severeparser issues.

Probe cannot handle data sentfrom EMS and will providemore information by loggingstack trace.

Parser: Failed to sendevent: exception

The probe could not forwardthe Event to the ObjectServer.

Check that the ObjectServer isrunning.


Table 9. Error messages (continued)


Parser: Exception raisedin XML handling:exception

The probe encountered aproblem while parsing theXML file.

Verify that the followingproperties are correctlyspecified: XSDFile,XSDFtpCommand, andXSDFtpPassword.

Parser: Failed to findXSD file 'xsd_file'

The probe could not retrievethe XSD file.


Parser: XML Validationfailed

The probe could not validatethe XML configuration.

Verify that the XSD file beingused is up to date with anyEMS changes.


Will not parse the XML The probe encountered aproblem while parsing theXML file.


Parser: Not validatingthe incoming XML as thetarget EMS is:TargetEMS_value

The probe is not validatingthe XML file.

The probe will only validatethe XML file when the valuespecified by the TargetEMSproperty is CN.

Error setting up SAXParser to read ResynchXML file exception

The probe cannot set up theSAX Parser.

Ensure that the $CLASSPATHenvironment variable iscorrectly specified.


Parser: Failed to parseXML file exception

The probe encountered aproblem while parsing theXML file.

Check the exception part of themessage for more informationabout the cause of this error.


SaxZTEParser:Exception :exception

The SAX parser encounteredan exception.

Review the additional errormessages and ProbeWatchmessages for moreinformation.

SaxZTEParser: Failed tosend event : exception

The probe could not send anevent to the ObjectServer.

Verify the connection to theObjectServer and that theObjectServer is runningcorrectly.




SAX Exception, XMLValidation failed.Perhaps the XML isinvalid exception

The probe could not validatethe XML configuration.


Error collecting anduncompressing XML filefrom target

The probe failed to retrievethe XML file.


Probe unable to receiveResynchronization events

The probe cannot receiveresynchronization events.

Verify that the target EMS isrunning correctly.

Verify that the Resynchproperty is correctly specified.

Resynch events in XMLfile cannot be passed toObjectServer

The probe could not forwardan event to the ObjectServer.

Verify that the ObjectServer isrunning.

Error fetching Resynchproperty

The probe could not retrievethe value specified by theResynch property.


Failed to perform resynch The probe failed to get thealarm list, or failed to iteratethrough resynchronizationalarms.

Verify the connection to thetarget EMS and that the targetEMS is running correctly.

Login: Failed to find IORfile 'iorFilePath'

The probe failed to get theIOR file from the given FTPlocation.

Verify that theEntryPointIrpFile,EntryPointIrpFtpCommand andFtpPassword properties arecorrectly specified.

Login: FtpPassword isincorrect length (ensureit has been encryptedusing nco_g_crypt)

The probe found that there isa problem with the encryptedpassword.

Verify that the FtpPasswordproperty is correctly specified.

Failed to find IOR fileexception

The probe failed to find theIOR file that storessubscription information forthe previous session with theZTE EMS.

Verify that the$OMNIHOME/var/TargetEMSInstanceId_NetcoolIRPManager.ior fileexists and is readable.

Name is null, cannotcreate Element

The probe cannot get a namevalue for an event sent by theZTE EMS, so the probe cannotprocess the event.

Check the log for related errormessages with moreinformation.

No fault management fileis identified in filelisting from EMS

The probe failed to locate inthe ZTE EMS the XML filethat contains the current listof all active alarms.

Verify that an XML file forfault management wasrecently generated properly inthe ZTE EMS.

Exception encountered.Listing available filesexception

The probe is unable to list thefiles on the target EMS thatcontain resynchronizationdata.

Check that the EMS hascreated a file of event data.




Delete: no such file ordirectory: filename

The probe could not find thefile or directory specified fordeletion.

Check that you have specifiedthe correct file or directory.

Delete: write protected:filename

The probe failed to overwritea file or directory.

Check the permissions on thefile or directory.

Delete: deletion failed:filename

The probe failed to delete thenamed file or directory.

Check the permissions on thefile or directory.

PersistentSusbscriptionproperty incorrectly set- assuming false

An invalid value wasspecified for thePersistentSubscriptionproperty.

Verify that the value of thePersistentSubscriptionproperty. is either true orfalse. No other values arepermitted.

Failed to unsubscribefrom EMS exception

The probe failed tounsubscribe from ZTE EMSwhen shutting down. Thesubscription is still active inthe ZTE EMS and this mightcause problems in the EMS.


Error sending probewatch The probe failed to send aProbeWatch message to theObjectServer.


Error sending probe watchmessage on failedconnection

The probe failed to get theAlarm IRP object that matchesthe value of the AlarmIRPproperty.


Refer to your CORBAdocumentation for moreinformation.

Error sending probe watchmessage on failed resynch

The probe failed to completea resynchronization and couldnot send the relatedProbeWatch message.



Error sending probe watchmessage on startingsynchronization

The probe encountered anerror while sending thestarting synchronizationProbeWatch message.


Error sending probe watchmessage on successfullycompleted resynch

The probe encountered anerror while sending thecompleted resynchronizationProbeWatch message.


Error sending probe watchmessage on failure to getsubscription status

The probe cannot retrieve thesubscription status and cannotsend the related ProbeWatch.


Error sending endasynchronous resynchprobe watch message

The probe failed to send anasynchronousresynchronization ProbeWatchmessage.





Error sending startasynchronous resynchprobe watch message

The probe failed to send anasynchronousresynchronizationProbeWatch.


NetcoolIRPManager: Failedto get subscriptionstatus exception

The probe cannot get thesubscription status from thenotification service.


NetcoolIRPManager: Failedto Connect: exception

NetcoolIRPManager:Either, the server is notrunning, the IOR is outof date, or probe cannotreach remote Server!

The Notification IRP pointfrom the target EMS is nolonger responding.

The notification service is notavailable. Verify theconnection to the target EMSand that the target EMS isrunning correctly.

NetcoolIRPManager: Detachexception when handlingold subscriptionexception

The probe failed to detachfrom a previous subscriptionto the ZTE EMS beforecreating a new subscription.


NetcoolIRPManager: Failedto get alarm listexception

The probe failed to retrievethe current list of activealarms from the ZTE EMS.The alarm list may not besynchronized between theObjectServer and the ZTEEMS.


NetcoolIRPManager: Failedto iterate throughresynch alarms exception

The probe encountered aproblem while parsing thealarms retrieved during aresynchronization.



NetcoolIRPManager: Failedto acknowledge alarm(s)exception

The probe failed toacknowledge an alarm in theZTE EMS using the commandport.

Verify that the command portcommands were properlyentered using the commandline interface.

NetcoolIRPManager: Failedto unacknowledge alarm(s)exception

The probe failed tounacknowledge an alarm inthe ZTE EMS using thecommand port.


NetcoolIRPManager: Failedto comment alarm(s)exception

The probe failed to add acomment to an alarm in theZTE EMS using the commandport.


IO exception when readingIOR file: exception

The probe failed to read theIOR file that storessubscription information forthe previous session with theZTE EMS.

Verify that the$OMNIHOME/var/TargetEMSInstanceId_NetcoolIRPManager.ior fileexists and is readable.

IO exception whilereading old subscriptionid file= subFileNameexception

The probe failed to read thefile that stores subscriptioninformation for the previoussession with the ZTE EMS.

Verify that the subFileNamefile exists and is readable.




Cannot initialize the Orb: exception

The probe found a problemduring initialization of theORB.

Ensure that the $CLASSPATHenvironment variable containsthe path to the IBM ORB .jarfiles.

Failed to pingnotification service

The probe is not able to pingthe notification service.


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 Trigger or cause

Detaching subscription The probe is disconnectingfrom the target EMS.

The probe is restarting.

Login: Failed to find IORfile 'iorFilePath'

The probe could not find theEntry Point IOR file on thelocal host.

Verify that theEntryPointIrpFile propertyis correctly specified and thatthe iorFilePath file isavailable.

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

The probe failed to connectto the Notification IRP on theZTE EMS due to a CORBAOBJECT_NOT_EXIST exception.

Verify that the NotificationIRP service is up andrunning on the ZTE EMS.

Parser: Failed to find XSDfile 'xsd_file'

The probe could not find thenamed XSD file.

The values specified for thefollowing properties mightbe incorrect: XSDFile,XSDFtpCommand,XSDFtpPassword.

START SYNCHRONIZATION The probe is synchronizingthe events.

The probe has startedreceiving alarms from thealarm list.

END SYNCHRONIZATION The probe is ending thesynchronization process.

The probe has finishedreceiving alarms from thealarm list.

START ASYNCHRONOUS RESYNCH The probe is starting anasynchronousresynchronization.

The probe has startedreceiving alarms from thealarm list.

END ASYNCHRONOUS RESYNCH The probe has completed anasynchronousresynchronization.

This probe has received thealarms from the alarm list.


Table 10. ProbeWatch messages (continued)

ProbeWatch message Description Trigger or cause

SYNCHRONIZATION ENDEDUNSUCCESSFULLY. SEE PROBEERROR LOG

The probe failed to retrievethe current list of all activealarms from the ZTE EMS.

Check the probe log file formore information about thiserror.

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

Before you run the probe, you must specify values for the following properties:v AlarmIrpName

v EntryPointIrpFile

v FileTransferIrpName

v NotificationIrpName

v TargetEMS

If the Entry Point IRP file is on a remote system, you must also specify values forthe following FTP properties:v EntryPointIrpFtpCommand

v FtpPassword

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

To start the probe, use the following command:

$OMNIHOME/probes/nco_p_zte_corba_wcdma


Appendix. Notices and Trademarks

This appendix contains the following sections:v Noticesv Trademarks

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

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

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

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

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

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

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

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

© Copyright IBM Corp. 2008, 2014 27

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

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

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

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

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

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

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

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

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

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

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

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


COPYRIGHT LICENSE:

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

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

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

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

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

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

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

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

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

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

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

Appendix. Notices and Trademarks 29

��

Printed in USA

SC23-9571-04

IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumen ... · PDF fileperformance analysis of...

Documents

Transcript of IBM Tivoli Netcool/OMNIbus Probe for ZTE M31 NetNumen ... · PDF fileperformance analysis of...