ibm prob with m2000pdf

Tivoli® Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA)Version 2.0.0

Reference GuideJanuary 31, 2011

SC23-6031-03

��

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

Edition notice

This edition applies to version 2.0.0 of IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA)(SC23-6031-03) and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC23-6031-02.

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

Contents

Document control page . . . . . . . . v

IBM Tivoli Netcool/OMNIbus Probe forHuawei M2000 (CORBA) . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 3Firewall considerations . . . . . . . . . . . 3Internationalization support . . . . . . . . . 4

Example multi-byte character set on Solaris . . . 5Example multi-byte configuration on Windows . . 5

Data acquisition . . . . . . . . . . . . . 5CORBA interface . . . . . . . . . . . . 6Status checking . . . . . . . . . . . . 6Backoff strategy . . . . . . . . . . . . 6

Timeout . . . . . . . . . . . . . . . 7Filtering notifications and alarms . . . . . . 7Command Line Interface . . . . . . . . . 7Peer-to-peer failover functionality . . . . . . 8

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

Appendix. Notices and Trademarks . . 21Notices . . . . . . . . . . . . . . . . 21Trademarks . . . . . . . . . . . . . . 23

© Copyright IBM Corp. 2006, 2011 iii

iv IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA): Reference Guide

Document control page

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

The IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA)documentation is provided in softcopy format only. To obtain the most recentversion, visit the IBM® Tivoli® Information Center:

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

Table 1. Document modification history

Document version Publication date Comments

01 March 28, 2008 First IBM publication.

02 October 31, 2010 Patch number updated in“Summary” on page 1.

The description of the devicewas updated in “IBM TivoliNetcool/OMNIbus Probe forHuawei M2000 (CORBA),”on page 1

The Internationalizationsupport section was updated.See “Internationalizationsupport” on page 4.

Section added to describehow to configure two probesto run simultaneously,allowing the secondary oneto start sending events to theObjectServer if the primaryone fails. See “Peer-to-peerfailover functionality” onpage 8.

Section added to describehow to run the probe. See“Running the probe” onpage 12.

03 January 31, 2011 Installation section replacedby “Installing probes” onpage 3.

“Firewall considerations” onpage 3 added.

© Copyright IBM Corp. 2006, 2011 v



vi IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA): Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000(CORBA)

Huawei M2000 is a wireless network management system that manages HuaweiWCDMA, CDMA2000, and GSM mobile communication networks.

The device is used for the operation and maintenance of subnets and can managethe access network, core network, and other networking products separately or ona unified basis. It manages Huawei mobile network equipment for broadband andnext generation networks, such as Msoftx3000 and BSC.

The IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA) collectsalarms from the Huawei M2000 (CORBA) management system using a 3rdGeneration Partnership Project Common Object Request Broker Architecture(CORBA) interface.

This guide contains the following sections:v “Summary”v “Installing probes” on page 3v “Firewall considerations” on page 3v “Internationalization support” on page 4v “Data acquisition” on page 5v “Properties and command line options” on page 9v “Running the probe” on page 12v “Elements” on page 12v “Error messages” on page 14v “ProbeWatch messages” on page 17

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 summarizes the probe.

Table 2. Summary

Probe target Huawei M2000 (CORBA) V200R800 and V2R9 for LTE.

Probe executable name nco_p_huawei_M2000_corba

Package Version 2.0

Probe supported on AIX®, HP-UX PA-RISC, Linux, Solaris, Windows

For details of the operating system versions on whichthis probe is supported, see the following page on theIBM Tivoli Netcool Information Center:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/Supported_Platforms.htm

© Copyright IBM Corp. 2006, 2011 1




Table 2. Summary (continued)

Properties file $OMNIHOME/probes/arch/huawei_M2000_corba.props (onUNIX and Linux operating systems)

%OMNIHOME%\probes\arch\huawei_M2000_corba.props (onWindows operating systems)

Rules file $OMNIHOME/probes/arch/huawei_M2000_corba.rules (onUNIX and Linux operating systems)

%OMNIHOME%\probes\arch\huawei_M2000_corba.rules (onWindows operating systems)

Requirements A currently supported version of IBM TivoliNetcool/OMNIbus.

Java 1.5 (this is supplied with Netcool/OMNIbus).

probe-nonnative-base-10 (or later)

probe-visibroker-support (for VisiBroker 8.0)Note: The VisiBroker patch is not supplied with thisprobe; you can obtain the patch from the IBM PassportAdvantage Web site:

http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

Connection method CORBA

Remote connectivity Available

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

Internationalization AvailableNote: The probe supports internationalization on IBMTivoli Netcool/OMNIbus V7.2.0, 7.2.1, and 7.3.0.

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6Note: The probe is supported on IPv6 when running onIBM Tivoli Netcool/OMNIbus V7.2.0, 7.2.1, and 7.3.0 onall UNIX and Linux operating systems. The probe issupported on IPv6 when running on IBM TivoliNetcool/OMNIbus V7.2.1 and 7.3.0 on Windowsoperating systems.

Federal Information ProcessingStandards (FIPS)

IBM Tivoli Netcool/OMNIbus V7.2.1 and 7.3.0 use theFIPS 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(SC23-9680).

2 IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA): 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 TivoliInformation Center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.html

2. Installing the probe using the installation package.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 addition configuration that is commonto all probes, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide(SC23-9684).

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 whichthe target 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 Huawei M2000 (CORBA) 3

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



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



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.

Internationalization supportThe probe supports multibyte character sets (for example, Japanese) and charactersets that contain individual multibyte characters (for example German, French, andSpanish). To view the character sets correctly, you must configure the localesettings on the host machine correctly.

If you are using a language that contains multibyte characters, you must set theLANG environment variables to the name of your character set, and export theLC_ALL environment variable. For example, if you are using Japanese, set theseenvironment variables to ja_JP.UTF-8; if you are using German, set theseenvironment variables to de_DE.UTF-8. This will enable the probe to recognise themultibyte characters used by your character set when they occur in any networkevents.

The probe supports the following language locales:

Table 3. Supported language locales

Languages AIX HP-UX Solaris Linux

English (US) en_US en_US en_US en_US

SimplifiedChinese

zh_CN zh_CN zh_CN zh_CN

TraditionalChinese

zh_TW zh_TW.eucTW Zh_TW.big5 zh_TW.big5

Czech cs_CZ cs_CZ cs cs_CZ

French(standard)

fr_FR fr_FR fr fr_FR

German(standard)

de_DE de_DE de de_DE

Hungarian hu_HU hu_HU hu hu_HU

Italian (standard) it_IT it_IT it it_IT

Japanese ja_JP ja_JP ja ja_JP

Korean ko_KR ko_KR ko ko_KR

Polish pl_PL pl_PL pl pl_PL

Portuguese(Brazilian)

pt_BR pt_BR pt pt_BR


Table 3. Supported language locales (continued)

Languages AIX HP-UX Solaris Linux

Russian ru_RU ru_RU ru ru_RU

Spanish es_ES es_ES es es_ES

Example multi-byte character set on Solaris

The following steps describe how to configure Solaris to use the Japanese characterset:1. Install the necessary components for Japanese on to the host machine using the

Solaris CD.2. Set the LANG and LC_ALL environment variables to ja_JP PCK. This uses SJIS

encoding.

Note: You may have to set the LANG in the host machine's default settings fileand reboot it to make the changes take effect.

3. Make sure that the file $OMNIHOME/platform/arch/locales/locales.dat has thefollowing entry:locale = ja_JP PCK, japanese, sjis

Where ja_JP PCK is the vendor locale, japanese is the Sybase language, andsjis is the Sybase character set.

Example multi-byte configuration on Windows

The following steps describe how to configure Windows to use the Japanesecharacter set:1. Install the necessary language pack using the Control Panel.

Note: You must reboot the machine to make the character set available.2. Make sure the file %OMNIHOME%\locales\locales.dat, has the following element:

locale = jpn, japanese, sjis

Where jpn is the vendor locale, japanese is the Sybase language, and sjis isthe Sybase character set

Note: You must reboot the machine to be able to use the probe as a service in therequired locale.

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

The Probe for Huawei M2000 (CORBA) gathers events from the Huawei M2000(CORBA) system using a Common Object Request Broker Architecture (CORBA)interface. CORBA is an Object Management Group specification that provides astandard interface definition between objects in a distributed environment; that is,it allows applications to communicate with one another regardless of where theyare located or who has designed them.

The probe complies with the following 3GPP standards:v 32.111 V5.5.1 - Alarm IRP


v 32.303 V5.2.0 - Notification IRPv 32.623 V5.2.0 - Generic Network

Data acquisition is described in the following topics:v “CORBA interface”v “Status checking”v “Backoff strategy”v “Timeout” on page 7v “Filtering notifications and alarms” on page 7v “Command Line Interface” on page 7v “Peer-to-peer failover functionality” on page 8

CORBA interfaceThe probe connects to the CORBA interface using Interoperable Object Reference(IOR) files.

The following topics provide the information required to use these methods.

IOR filesIf you use IOR files, the probe gets the object reference of the AlarmIRPOperationand NotificationIRPOperation objects from the IOR files specified by theAlarmIrpName and NotificationIrpName properties, respectively. TheAlarmIRPOperation and NotificationIRPOperation servers form a part of theIntegrations Reference Point (IRP) agent.

To get the IOR files, the probe retrieves the Entry Point IRP file specified by theEntryPointIrpFile property. If the Entry Point IRP file is accessible on a remotesystem, the probe uses the FTP command to retrieve the file. You can specify theFTP command that the probe sends using the EntryPointIrpFtpCommandproperty, and the related username and password using the FtpUsername andFtpPassword properties, respectively.

Retrieving objects

When the Resynch property is set to true, the probe initially receives a list of allactive alarms from the AlarmIRP server. The probe then connects to theNotificationIRP server and uses the CORBA notification push model to receive newalarms from the server as they are generated. When the Resynch property is set tofalse, the probe receives only new alarms.

Status checking

The probe checks the status of the IRP agent every 60 seconds. You can change thisfrequency using the Agentheartbeat property.

Backoff strategyIf the Retry property is set to true, and the probe fails to establish a connection orloses an existing connection to the device, it reverts to a backoff strategy. The probetries to reestablish a connection after one second, two seconds, then four seconds,and so on, up to a maximum of 4096 seconds. Once the connection is made to theCORBA interface, the probe tries to log in to the device. If the probe fails to log in,it shuts down and tries to connect again. The backoff strategy remains in placeuntil a successful login occurs.


Timeout

The Probe for Huawei M2000 (CORBA)has a timeout facility that allows it todisconnect from the system if there is no activity for a predefined amount of time.You can specify how long the probe waits before disconnecting using the Timeoutproperty.

Filtering notifications and alarmsUsing the properties file you can specify how the probe filters events to receiveonly the preferred notifications and alarms.

The NotificationFilter and AlarmFilter properties allow you to specify whatnotifications and alarms are sent to the probe. When you use these properties,specify the actual token names. For example, the token h represents the elementNV_PERCEIVED_SEVERITY. So, to specify that the probe is only sent notifications witha perceived severity of 3, set the NotificationFilter property to $h == 3.

You can specify more complex filters using and and or statements. For example, tospecify that the probe receives notifications with a perceived severity of 3 or 4, setthe NotificationFilter property to $h == 3 or $h == 4.

You can use type_name, domain_name, event_name, e, and h as notification filterproperties.

Command Line InterfaceThe Probe for Huawei M2000 (CORBA) has a Command Line Interface (CLI). Thisinterface allows you to execute commands using the probe (for example, toacknowledge alarms or to request a full resynchronization of the 3GPP interface).

To use the CLI, set the CommandPort property in the properties file to the numberof the port to use for sending commands. To execute commands, telnet them tothis port.

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

Table 4. CLI commands

Command Description

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

exit

quit

Use these commands to close the connection.

help Use this command to display online help aboutthe CLI.

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


Table 4. CLI commands (continued)

Command Description

resynch_filter <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 AlarmFilter property.

unacknowledge_alarm <alarm_id> Use this command to unacknowledge thespecified alarm identifier in the 3GPP interface.

userid_acknowledge_alarm <alarm_id><user_id>

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.

userid_unacknowledge_alarm<alarm_id> <user_id>

Use this command to unacknowledge an alarm inthe 3GPP interface by specifying theNV_ALARM_ID of the alarm beingacknowledged and the NV_ACK_USER_ID.

userid_clear_alarm <alarm_id><user_id>

Use this command to clear an alarm byspecifying the NV_ALARM_ID of the alarmbeing cleared and the NV_ACK_USER_ID.

userid_comment_alarm <alarm_id><user_id> <comment_text>

Use this command to add comments to an alarmby specifying the NV_ALARM_ID of the alarmbeing commented using the user specified by theCommentUserId property.

version Use this command to display the version of theprobe.

Note: As the CLI is based on Telnet connections, you can connect to the probefrom anywhere by creating desktop tools to open a Telnet connection, send acommand, and then close the connection. This means that simple scripts can be setup to allow users to acknowledge selected events from the IBM TivoliNetcool/OMNIbus event 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.

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"

Note: The properties file also contains all other properties required to configurethe probe.

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

Table 5. Properties and command line options

Property name Command line option Description

AckUserId string -ackuserid string Use this property to specify thename of the user acknowledging analarm. This is used by theacknowledge_alarm CLI function.

The default is "".

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

The default is 60.

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 that the probe uses to resolvethe AlarmIRP point.

The default is AlarmIRP.

ClearUserId string -clearuserid string Use this property to specify thename of the user clearing an alarm.

The default is "".


Table 5. Properties and command line options (continued)


CommandPort integer -commandport integer Use this property to specify theport that users can provide to telnetto communicate with the 3GPPinterface using the Command LineInterface (CLI). For details aboutthe CLI, see “Command LineInterface” on page 7.

The default is 6970.

CommandPortLimitinteger

-commandportlimit integer Use this property to specify themaximum number of telnetconnections that can be made to theprobe.

The default is 10.

CommentUserId sring -commentuserid string Use this property to specify thename of the user commenting onan alarm. This is used by theuserid_comment_alarm CLIfunction.

The default is "".

EncodingStandardsring

-encodingstandard string Use this property to specify theencoding required to parse Chinesecharacters.

The default is ISO-8859-1.

EntryPointIrpFile string -entrypointirpfile string Use this property to specify thepath to the Entry Point IRP IORfile.

The default is "".

EntryPointIrpFtpCommand string

-entrypointirpftpcommandstring

Use this property to specify theFTP command to retrieve the EntryPoint IRP IOR file.

The default is "".

FlushBufferIntervalinteger

-flushbufferinterval integer Use this property to specify howoften (in seconds) the probe flushesall alerts in the buffer to theObjectServer.

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

FtpPassword string -ftppassword string Use this property to specify thepassword required to access theEntry Point IRP IOR file throughFTP.

The default is "".




FtpUsername string -ftpusername string Use this property to specify theusername required to access theEntry Point IRP IOR file throughFTP.

The default is "".

IrpVersion string -Irpvesion string Use this property to specify theversion identifier required to getthe IRP outline.

The default is V1.2.0.

ManagerIdentifierstring

-manageridentifier string Use this property to specify thename used to get all the IRPreferences.

The default is "".

NotificationCategoriesstring

-notificationcategories string Use this property to specify thecategories of notifications to whichthe probe will subscribe.

The default is "" (this instructs theprobe to subscribe to all thenotification categories).

NotificationFilter string -notificationfilter string Use this property to specify thefilter that the notification IRP usesto limit the notifications sent to theprobe.

The default is "".

NotificationIrpNamestring

-notificationirpname string Use this property to specify thename used to resolve theNotification IRP.

The default is NotificationIRP.

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

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

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

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

Use this property to specifywhether the probe attempts toresynch to the 3GPP serverfollowing a timeout. This propertytakes the following values:

false: The probe does not attemptto resynch to the system.

true: The probe attempts to resynchto the system.

The default is false.




Retry string -retry (This is equivalent toRetry with a value of true.)

-noretry (This is equivalentto Retry with a value offalse.)

Use this property to specifywhether the probe attempts toreconnect to the 3GPP interfacefollowing a timeout. This propertytakes the following values:

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

true: The probe attempts toreconnect to the system.

The default is false.

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

The default is 0 (this ensures thatthe probe never times out).

TimeTick integer -timetick integer Use this property to specify thelength (in seconds) of thenotification IRP session lifetime.This is used by the 3GPP interface.

The default is -1 (this ensures thatthe session never times out).

Note: A value of 15 releases theunused subscriptions and refreshesthe subscriptions.

Running the probeHow you run the probe depends on whether you are running a UNIX or Windowsoperating system.

To start the probe on UNIX or Linux operating systems, use the followingcommand:$OMNIHOME/bin/nco_p_huawei_M2000_corba

To start the probe from a Windows command prompt, use the following command:%OMNIHOME%\bin\nco_p_huawei_M2000_corba

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 for Huawei M2000(CORBA) generates. Not all the elements described are generated for each event;the elements that the probe generates depend upon the event type.


Table 6. Elements

Element name Element description

ADDITIONALTEXT_LINECOUNT This element indicates the number of lines withinthe AdditionalText element.

CLEAR_SYSTEM_ID This element indicates whether the systemidentifier has been cleared.

CLEAR_USER_ID This element indicates whether the user identifierhas been cleared.

FULL_ADDITIONAL_TEXT This element contains all values within theAdditionalText element generated by the 3GPPinterface.

NV_ACK_STATE This element specifies the acknowledgement stateof the alarm.

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

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

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

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

NV_ADDITIONAL_TEXT_LINEXX This element shows a single line within theAdditionalText element; xx indicates the linenumber.

NV_ALARM_CHANGED_TIME This element contains the date at which the statusof the alarm was changed. The date is displayedin the format mm/dd/yy.

NV_ALARM_CLEARED_TIME This element contains the date at which the alarmwas cleared. The date is displayed in the formatmm/dd/yy.

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

NV_ALARM_LIST_ALIGNMENT_REQUIREMENT This element indicates whether the alarm listrequires alignment.

NV_ALARM_RAISED_TIME This element contains the date at which the alarmwas raised. The date is displayed in the formatmm/dd/yy.

NV_COMMENTS This element contains comments about thealarms.

NV_COMMENTS_TIME This element contains the date at which thecomment was raised. The date is displayed in theformat mm/dd/yy.

NV_COMMENTS_USER_ID This element contains the name of the user whoraised the comment.

NV_COMMENTS_SYSTEM_ID This element contains the name of the systemused to raise the comment.

NV_COMMENTS_TEXT This element contains the comment text.


Table 6. Elements (continued)

Element name Element description

NV_EVENT_TIME This element contains the time at which the eventoccurred.

NV_MANAGED_OBJECT_CLASS This element identifies the managed object classof the network resource.

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

NV_MONITORED_ATTRIBUTES This element contains the managed objectattributes of the network resource.

NV_NOTIFICATION_ID This element contains the identificationinformation of the notification.

NV_PERCEIVED_SEVERITY This element contains the perceived severity ofthe alarm.

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

NV_PROPOSED_REPAIR_ACTIONS This element specifies the proposed repair actionsassociated with the notification.

NV_REASON This element specifies the reason that triggeredthe proposed repair action.

NV_SECURITY_ALARM_DETECTOR This element identifies the security alarm detectorfor the device.

NV_SERVICE_PROVIDER This element contains the name of the serviceprovider.

NV_SERVICE_USER This element contains the name of the user whouses the service.

NV_SPECIFIC_PROBLEMS This element provides further information aboutthe problem to which the notification relates.

NV_STATE_CHANGE_DEFINITION This element provides information about the statechange.

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

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

NV_THRESHOLD_INFO__ATTRIBUTE_ID This element provides identification informationabout a threshold object attribute.

NV_THRESHOLD_OBSERVED_VALUE This element provides the observed value of thethreshold that has been crossed.

NV_THRESHOLD_HIGH This element contains the maximum limit of thethreshold value.

NV_THRESHOLD_LOW This element contains the minimum limit of thethreshold value.

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

Table 7. Error Messages

Error message Description Action

Failed to pingnotification service

Failed to getsubscription status

The probe has connectionproblems with theNotificationIRP point.

Check that the 3GPP server isrunning correctly. Check theconnection to the 3GPP server.

NetcoolIRPManager: Failedto acknowledge_alarms

The probe has failed toacknowledge the alarms.

Check that theNV_ALARM_ID specified bythe CLI is correct.

NetcoolIRPManager: Failedto clear alarms

The probe has failed to clearthe alarms.


NetcoolIRPManager: Failedto unacknowledge_alarms

The probe has failed tounacknowledge the alarms.


[Command Port] Failed toget property CommandPort

[Command Port] Threadshutting down due toerror!

[Command Port] Failed toopen listening socket,shutting down Thread!

[Command Port] Erroroccured

[Command Port] hostnameFailed to get socket IO

[Command Port] hostnameFailed to read command

[Command Port] hostnameFailed to close commandsocket

A problem occurred when theuser attempted to connect tothe command port, or whenthe user sent a command.

Check that the value of theCommandPort property iscorrect, and that thenco_p_nonnative process isrunning. Check theconnection between the probeand the command prompt.

[Command Port] Failed toget CommandPortLimitproperty - using 10

The probe could not retrievethe value of theCommandPortLimit property.It is set to 10 by default,therefore this does not affectthe behavior of the probe.

Check the value ofCommandPortLimit property.

Cannot initialize the Orb Problem during initializationof the ORB.

Ensure your CLASSPATHcontains the path to theVisibroker jar files. The pathis set in the $PATHenvironment variable.


Table 7. Error Messages (continued)


Communication failure -lost connection toNoticiationIRP:

CORBA.TRANSIENT exceptionraised. NotificationIRPis down!

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

RBA Exception stack traceto stderr

Failed to Connect

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

Cannot proceed. Shuttingdown!

There are no responses fromthe NotificationIRP point.

Check that the Huawei M2000server is running correctly.

Failed to find IOR file The probe has failed to getthe IOR file.

Check that theEntryPointIrpFile property iscorrectly set in the propertiesfile.

Failed to narrow EntryPoint IRP interface

Failed to narrow the objectreference to the Entry PointIrpAgent object.

Check that theEntryPointIrpFile property iscorrectly set in the propertiesfile.

Failed to perform resynch

Failed to iterate throughresynch alarms

The probe failed to get thealarm list, or failed to performresynchronization of alarms.

Check that the Huawei M2000server is running correctly.Check that the Resynchproperty is set correctly.

FtpPassword is incorrectlength (ensure it hasbeen encrypted usingnco_g_crypt)

There is a problem with theencrypted password.

Check the value of theFtpPassword property in theproperties file.

NetcoolIRPManager: ERRORwhen parsing anotification event

NetcoolIRPManager: StackTrace to stderr:

Failed to parse eventcompletely

A problem occurred whileparsing a received alarm. Theprobe may not have parsedthe event completely.

Check that the HuaweiM2000server is runningcorrectly.

NetcoolIRPManager: Failedto send event

The probe could not forwardthe Event to the ObjectServer.

Check that the ObjectServer isrunning.

OperationNotSupportedException

There is a problem with theCORBA interface.

Refer to your CORBAdocumentation.


Table 7. Error Messages (continued)


NetcoolIRPManager: Failedto retrieve AlarmIRPobject from entry pointinterface

NetcoolIRPManager: Failedto retrieveNotificationIRP objectfrom entry pointinterface

Problem while trying toconnect to the IRP points

Login: Failed to get IRPreferences - invalidparameter Parameters used- Subscription ID: sub_idSubscription Filtersubs_filter SubscriptionState: subscription_stateTime Tick: time_tick

Failed to get either theAlarmIRP or the NotificationIRP object.

Check that theAlarmirpName andNotificationirpNameproperties are correctly set inthe properties file.

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

Table 8. ProbeWatch messages

ProbeWatch messages Description Triggers/causes

Communication failure -lost connection toNoticiationIRP

CORBA.TRANSIENT Exception:Lost connection toNotificationIRP

CORBA.OBJECT_NOT_EXISTException: Lost connectionto NotificationIRP

Failed to connect toNotificationIRP: Shuttingdown

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

Communication with thenotification IRP server hasfailed.

The probe lost its connectionto the notification IRP server.


Table 8. ProbeWatch messages (continued)


END SYNCHRONIZATION The resynchronization ofalarms has stopped.

The probe hasresynchronized all theavailable alarms in theserver.

Failed to find IOR filealarmirp_ior_file

The specified alarm IRP filedoes not exist.

The IRP manager has beenset up incorrectly.

Failed to find IOR filenotificationirp_ior_file

The specified notification IRPfile does not exist.

The IRP manager has beenset up incorrectly.

Failed to get IRP Outline(GetIRPOutline exceptioncaught when callingget_IRP_outline)

Unexpected fatal errorwhen getting IRP referencefrom Entry Point IRP

Unexpected fatal errorwhile getting IRP Outline

The probe could not get theIRP object.

There is a problem with theCORBA interface.

Failed to get IRPreference (GetIRPReferenceexception caught whencalling get_IRP_reference)

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

The probe could not get theIRP version.

An incorrect reference isspecified in the IRP file.

Failed to get subscriptonstatus

The probe lost its connectionto the server.

The 3GPP server is either notrunning correctly or theconnection to the 3GPPserver is lost.

Failed to listen forcommands on port numberlistening_port

A problem occurred whiletrying to listen forcommands.

If this message occurs whenthe probe tries to initializethe connection, then there isinsufficient memory tocomplete the operation.

If this message occurs aftersome events had beenparsed, then either there wasa connection failure or thespecified port is already inuse.

Failed to log in tointerface(InvalidParameterexception caught whencalling get_IRP_outline)

Unexpected fatal error,failed to connect

The probe failed to login tothe server.

The specified user name andpassword are incorrect.


Table 8. ProbeWatch messages (continued)


Failed to log in to theSecurity IRP - incorrectusername/password

The probe failed to login tothe Security IRP.

The password entered doesnot match the user name.

Invalid IRPVersion(InvalidIRPVersionexception caught whencalling get_IRP_outline)

The specified IRP version isincorrect.

An incorrect IRP name isspecified in the propertiesfile.

NetcoolIRPManager: Failedto find IOR file ior_file

The specified IOR file doesnot exist.

The IRP Manager has beenset up incorrectly.

PermissionDenied(PermissionDeniedexception caught whencalling get_IRP_outline)

Permission to login to theserver is denied.

The probe does not have theappropriate permissions setto login to the server.

probe cannot reach remoteServer

The probe failed to login tothe server.

The 3GPP server is either notrunning correctly or theconnection to the 3GPPserver is lost.

START SYNCHRONIZATION The resynchronization ofalarms has started.

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

Will listen for commandson port numberlistening_port

The probe is now listeningfor commands on thespecified port number.

The probe has successfullycreated the specifiedcommand port in theproperties file.


Appendix. Notices and Trademarks

This appendix contains the following sections:v Noticesv Trademarks

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

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

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

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

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

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

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

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

© Copyright IBM Corp. 2006, 2011 21

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

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

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

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

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

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

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

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

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

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

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

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


COPYRIGHT LICENSE:

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

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

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

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

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

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

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

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

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

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

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

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

Appendix. Notices and Trademarks 23

��

Printed in USA

SC23-6031-03

ibm prob with m2000pdf

Documents

omnihome probes arch huawei m2000 corba

invalidparameter exception caught

unexpected fatal error

command line options

peer failover functionality

linux operating systems

windows operating systems

copyright ibm corp