probe for huawei n2000

Tivoli® Netcool/OMNIbus Probe for Huawei N2000 (CORBA)Version 3.0.1

Reference GuideOctober 29, 2010

SC23-7870-03

��

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

Edition notice

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

This edition replaces SC23-7870-02.

© Copyright IBM Corporation 2006, 2010.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 N2000 (CORBA) . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Firewall considerations . . . . . . . . . . . 3Internationalization support . . . . . . . . . 4

Example multi-byte character set on Solaris . . . 4Data acquisition . . . . . . . . . . . . . 5

Running multiple probes . . . . . . . . . 5Retrieving alarms . . . . . . . . . . . . 6Status checking . . . . . . . . . . . . 6Timeout . . . . . . . . . . . . . . . 6

Backoff strategy . . . . . . . . . . . . 6Filtering alarms . . . . . . . . . . . . 6Event synchronization . . . . . . . . . . 7Peer-to-peer failover functionality . . . . . . 7

Command line interface . . . . . . . . . . 8Properties and command line options . . . . . . 9Running the probe . . . . . . . . . . . . 15Elements . . . . . . . . . . . . . . . 15Error messages . . . . . . . . . . . . . 16ProbeWatch messages . . . . . . . . . . . 17

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

© Copyright IBM Corp. 2006, 2010 iii

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

Document control page

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

The Probe for Huawei N2000 (CORBA) documentation is provided in softcopyformat only. To obtain the most recent version, visit the IBM® Tivoli® InformationCenter:

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

Table 1. Document modification history

Documentversion

Publicationdate

Comments

00 October 04,2007

First IBM publication.

01 November 14,2008

Patch number and version updated.

Event synchronization section added.

EventSynchronization property added.

Error messages section updated.

ProbeWatch messages section added.

02 April 30, 2009 Summary section updated.

Running multiple probes section added.

Command line interface topic added.

CommandPort and CommandPortLimit propertydescriptions added.

ORBLocalPort property description added.

© Copyright IBM Corp. 2006, 2010 v



Table 1. Document modification history (continued)

Documentversion

Publicationdate

Comments

03 October 29,2010

Patch number updated in “Summary” on page 1.

Section added to describe how to install the probe“Installing probes” on page 2.

The section on configuring the probe was removed as thisinformation is now covered in the new installationsection.

Internationalization support section updated with anexample for the Windows® operating system. See“Internationalization support” on page 4.

Section added to describe how to configure two probes torun simultaneously, allowing the secondary one to startsending events to the ObjectServer if the primary onefails. See “Peer-to-peer failover functionality” on page 7.

Section added to describe how to run the probe. See“Running the probe” on page 15.

Message descriptions were updated in “ProbeWatchmessages” on page 17.

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

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

The Huawei N2000 system is a sub-network-level management system thatprovides both element management and network management functionality fortelecommunications networks.

The IBM Tivoli Netcool/OMNIbus Probe for Huawei N2000 (CORBA) acquiresdata from the Huawei N2000 system using a Common Object Request BrokerArchitecture (CORBA) interface.

This guide contains the following sections:v “Summary”v “Installing probes” on page 2v “Data acquisition” on page 5v “Command line interface” on page 8v “Properties and command line options” on page 9v “Running the probe” on page 15v “Elements” on page 15v “Error messages” on page 16v “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 provides a summary of the Probe for Huawei N2000 (CORBA):

Table 2. Summary

Probe target Huawei N2000 on iMAP V200R003 or later

Probe executable name nco_p_huawei_N2000_corba

Patch number 4.0

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

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

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

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

© Copyright IBM Corp. 2006, 2010 1




Table 2. Summary (continued)

Requirements A currently supported version of IBM TivoliNetcool/OMNIbus.

JDK 1.5

probe-visibroker8-support-2

Connection method CORBA

Remote connectivity The Probe for Huawei N2000 (CORBA) can connect to aremote device using the CORBA interface.

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 Available

Note: The probe supports internationalization on IBMTivoli Netcool/OMNIbus V7.1.0, 7.2.0, 7.2.1, and 7.3.0.

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

Note: The probe is supported on IPv6 when running onIBM Tivoli Netcool/OMNIbus V7.1.0, 7.2.0, 7.2.1, and7.3.0 on Solaris, and on IBM Tivoli Netcool/OMNIbusV7.2.0, 7.2.1, and 7.3.0 on all other UNIX and Linuxoperating systems. The probe is supported on IPv6when running on IBM Tivoli Netcool/OMNIbus V7.2.1and 7.3.0 on Windows operating systems.

Federal Information ProtocolStandards (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).

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:

2 IBM Tivoli Netcool/OMNIbus Probe for Huawei N2000 (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

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.c. The outgoing port on which the target system sends events if the probe is

running as a client.d. The incoming port on which the probe listens for incoming events.

Note: Most, but not all, CORBA probes listen on the port specified by theORBLocalPort property. The default value for this property is 0, which means thatan available port is selected at random. If the probe is behind a firewall, the valueof the ORBLocalPort property must be specified as a fixed port number.

CORBA probes that use EventManager or NotificationManager objects may usedifferent hosts and ports from those that use NamingService and EntryPointobjects. If the probe is configured to get object references from a NamingService or

IBM Tivoli Netcool/OMNIbus Probe for Huawei N2000 (CORBA) 3




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



EntryPoint 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

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

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.

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 IBM Tivoli Netcool/OMNIbus Probe for Huawei N2000 (CORBA) gathersevents from the Huawei N2000 using a Common Object Request BrokerArchitecture (CORBA) interface. CORBA is an Object Management Groupspecification that provides a standard interface definition between objects in adistributed environment; that is, it allows applications to communicate with oneanother regardless of where they are located or who has designed them.

Data acquisition is described in the following topics:v “Retrieving alarms” on page 6v “Status checking” on page 6v “Timeout” on page 6v “Backoff strategy” on page 6v “Filtering alarms” on page 6v “Event synchronization” on page 7v “Peer-to-peer failover functionality” on page 7

Running multiple probesYou can run multiple instances of the probe.

For each running instance, you must use the ORBLocalPort property to specify adifferent port to which the server listens.

Running multiple probes in a failover configuration

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

Where you are running this configuration in conjunction with a firewall, thereceiving port of each probe must be added to the firewall rules. The direction ofthe connection is from the target system to the master or slave probe.

You set the peer-to-peer failover mode in the properties files of the master andslave probes.

The peer-to-peer settings of the master probe properties file should include thefollowing:


PeerHost : "slave_hostname"PeerPort : 5555 # [communication port between master and slave probes]

The peer-to-peer settings of the slave probe properties file should include thefollowing:PeerHost : "master_hostname"PeerPort : 5555 # [communication port between master and slave probes]

Retrieving alarmsThe probe can retrieve alarms either by calling the pullNewAlarms() method or byusing the CORBA notification service.

You can specify which method the probe uses by setting theUseNotificationService property in the properties file. To instruct the probe to usethe notification service, set the UseNotificationService property to true. To instructthe probe to use the pullNewAlarms() method, set the UseNotificationServiceproperty to false and use the PullInterval property to specify the frequency withwhich it calls the method. Use the AlarmBatchSize property to specify how manyalarms the probe retrieves each time the method is called.

Tip: IBM Tivoli Netcool/OMNIbus recommends that you use the pullNewAlarms()method to retrieve data.

Status checkingThe probe checks that the Huawei N2000 server is running by sending a pingcommand every 60 seconds.

You can use the Agentheartbeat property to change the ping frequency.

TimeoutThe Probe for Huawei N2000 (CORBA) has a timeout facility that allows it todisconnect from the system if there has been no activity for a predefined amountof time.

You can use the Timeout property to specify how long the probe waits beforedisconnecting from the system.

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.

Filtering alarmsYou can limit the types of alarms the probe retrieves using the filtering properties.

The filtering properties allow you to exclude alarms according to their severity. Forexample, to exclude alarms of severity Indeterminate, set theExcludeSeverityIndeterminate property to true.

The following filtering properties are available:


Table 4. Filtering properties

Property Alarm Severity

ExcludeSeverityCleared Cleared

ExcludeSeverityCritical Critical

ExcludeSeverityIndeterminate Indeterminate

ExcludeSeverityMajor Major

ExcludeSeverityMinor Minor

ExcludeSeverityWarning Warning

Note: By default, the probe retrieves alarms of all severities.

Event synchronizationThe probe supports event synchronization between the Huawei N2000 ElementManagement System (EMS) and the ObjectServer.

When the probe restarts and requests a full resynchronization, the EMS does notsend any cleared alarms. The ObjectServer will still show those alarms in its eventlist.

To synchronize the ObjectServer with the EMS so that the ObjectServer shows onlyuncleared events, set the Resynch and EventSynchronization properties to true.After the resynchronization is complete, the events that did not come from theEMS through resynchronization (those that have been cleared) will be removedfrom the ObjectServer.

Note: Event synchronization only works for resynchronization events. It does notaffect any new notification alarms. The ObjectServer will continue to receive allnotifications sent by the EMS, without regard to the state of the alarms.

Before running the probe for event synchronization, change the followingproperties in the EventSynch_N2000.sh file, located in the $OMNIHOME/probes/directory:Server="NCOMS" (Object Server Name)User="root" (User name of Object Server)Password="" (Password)

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.

Command line interfaceThe probe has a command line interface (CLI) that you can use to performcommands using the probe, for example, to acknowledge or clear alarms in theCORBA interface.

To use the CLI, you must use the CommandPort property in the properties file tospecify a port through which commands will be sent. When you want to performcommands, use Telnet to connect through this port.

Note: The probe can only use Telnet to connect to destination systems that haveenabled the Telnet option.

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

Table 5. CLI commands

Command Description

acknowledge_alarm Use this command to acknowledge one or morealarms in the CORBA interface.

Note: This command takes as a parameter thenotification IDs of the alarms beingacknowledged. The syntax for the command isacknowledge_alarm Notification_Id1,Notification_Id2, and so on.


Table 5. CLI commands (continued)

Command Description

clear_alarm Use this command to clear one or more alarms inthe CORBA interface.

Note: This command takes as a parameter thenotification IDs of the alarms being cleared. Thesyntax for the command is clear_alarmNotification_Id1, Notification_Id2, and so on.

help Use this command to display online help aboutthe CLI.

quit Use this command to close the connection to theprobe.

version Use this command to display the version of theprobe.

Note: Because the CLI is based upon Telnet connections, you can connect to theprobe from anywhere. This means that simple scripts can be set up to allow usersto acknowledge selected events from the Netcool/OMNIbus event list.

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 information about default properties and command line options, seethe IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, (SC23-6373).

Table 6. Properties and command line options

Property name Command line option Description

AgentHeartBeat integer -agentheartbeat integer Use this property to specify thefrequency (in seconds) at whichthe probe sends a ping commandto check whether the Huaweiserver is still running.

The default is 60.

AlarmBatchSize integer -alarmbatchsize integer Use this property to specify themaximum number of real-timealarms that the probe retrieveswhen using the pullNewAlarms()method.

The default is 100.


Table 6. Properties and command line options (continued)


CommandPort integer -commandport integer Use this property to specify theport through which users can useTelnet to communicate with theCORBA interface. Users cancommunicate with the CORBAinterface using the Command LineInterface (CLI) supplied with theprobe. For details about the CLI,see “Command line interface” onpage 8.

The default is 6970.

CommandPortLimitinteger

-commandportlimit integer Use this property to specify themaximum number of Telnetconnections that can be made tothe probe.

The default is 10.

EncodingStandard string -encodingstandard string Use this property to specify thestandard used to encode anddecode multi-byte characters.

The default is ISO-8859-1.

EventSynchronizationstring

-noeventsynch (This isequivalent toEventSynchronizationwith a value of false.)

-eventsynch (This isequivalent toEventSynchronizationwith a value of true.)

Use this property to synchronizethe ObjectServer with the EMS.This removes the alarms from theObjectServer that were cleared inthe EMS during the probeshutdown.

The default is false.

Note: If you set this property totrue, you must also set theResynch property to true.

ExcludeSeverityClearedstring

-excludeseverityclearedstring

Use this property to specifywhether the probe excludes alarmsof severity Cleared from those thatit retrieves. This property takesthe following values:

false: The probe does not excludealarms of severity Cleared.

true: The probe excludes alarms ofseverity Cleared.





ExcludeSeverityCriticalstring

-excludeseveritycriticalstring

Use this property to specifywhether the probe excludes alarmsof severity Critical from thosethat it retrieves. This propertytakes the following values:

false: The probe does not excludealarms of severity Critical.

true: The probe excludes alarms ofseverity Critical.


ExcludeSeverityIndeterminate string

-excludeseverityindeterminate string

Use this property to specifywhether the probe excludes alarmsof severity Indeterminate fromthose that it retrieves. Thisproperty takes the followingvalues:

false: The probe does not excludealarms of severity Indeterminate.

true: The probe excludes alarms ofseverity Indeterminate.


ExcludeSeverityMajorstring

-excludeseveritymajorstring

Use this property to specifywhether the probe excludes alarmsof severity Major from those that itretrieves. This property takes thefollowing values:

false: The probe does not excludealarms of severity Major.

true: The probe excludes alarms ofseverity Major.


ExcludeSeverityMinorstring

-excludeseverityminorstring

Use this property to specifywhether the probe excludes alarmsof severity Minor from those that itretrieves. This property takes thefollowing values:

false: The probe does not excludealarms of severity Minor.

true: The probe excludes alarms ofseverity Minor.





ExcludeSeverityWarningstring

-excludeseveritywarningstring

Use this property to specifywhether the probe excludes alarmsof severity Warning from those thatit retrieves. This property takesthe following values:

false: The probe does not excludealarms of severity Warning.

true: The probe excludes alarms ofseverity Warning.


FlushBufferIntervalinteger

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

The default is 0 (which instructsthe probe to never flush alerts tothe ObjectServer).

IORFile string -iorfile string Use this property to specify thepath of the inter-operable objectreference (IOR) file.

The default is "".

NamingContextIORFilestring

-nsior string Use this property to specify thelocation of the IOR file thatcontains the root context of theNaming Service.

The default is "".

NamingContextPath string -nspath string Use this property to specify thelocation of the interface objectwithin the Naming Service.

The default isTMF_MTNM.Class/HUAWEI.Vendor/Huawei\\/N2000.EmsInstance/2\\ .1.Version/Huawei\\/N2000.EmsSessionFactory_I.

ORBInitialHost string -orbinitialhost string Use this property to specify thename of the Naming Service host.

The default is "".

ORBInitialPort integer -orbinitialport integer Use this property to specify theport number of the NamingService.

The default is 1570.




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

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

Password string -password string Use this property to specify thepassword that is required with theUsername property to log in tothe system.

The default is "".

PullInterval integer -pullinterval integer Use this property to specify thefrequency (in seconds) with whichthe probe uses thepullNewAlarms() method to getalarms from Huawei N2000.

The default is 10.

Note: The probe only uses thisproperty if theUseNotificationService propertyis set to false.

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

-resynch (This isequivalent to Resynchwith a value of true.)

Use this property to specifywhether the probe requests allactive alarms from the serverbefore acquiring new alarms. Thisproperty takes the followingvalues:

false: The probe does not performresynchronization.

true: The probe performsresynchronization.


ResynchBatchSize integer -resynchbatchsize integer Use this property to specify themaximum number of alarms thatthe probe retrieves in each batchof resynchronization alarms.

The default is 100.




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

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

Use this property to specifywhether the probe attempts toreconnect to the system using abackoff strategy following areported error. This property takesthe following values:

false: The probe shuts down anddoes not attempt to reconnect.

true: The probe attempts toreconnect to the system using thebackoff strategy.


Note: For details about thebackoff strategy, see “Backoffstrategy” on page 6.

Timeout integer -timeout integer Use this property to specify thetime (in seconds) that the probewaits to receive events beforedisconnecting from the CORBANaming Service and shuttingdown.

The default is 0 (probe nevertimes out).

UseNotificationServiceinteger

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

-usenotifservice (This isequivalent to Retry with avalue of true.)

Use this property to specifywhether the probe uses theCORBA notification service or thepullNewAlarms() method to getalarms from Huawei N2000. Thisproperty takes the followingvalues:

false: The probe uses thepullNewAlarms() method to getalarms.

true: The probe uses the CORBAnotification service to get alarms.


Note: If you set this property tofalse, you must use thePullInterval property to specifythe frequency with which theprobe calls the pullNewAlarms()method.

Username string -username string Use this property to specify theuser name of the account that theprobe uses to log in to the HuaweiN2000 interface.

The default is "".


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_N2000_corba

To start the probe from a Windows command prompt, use the following command:%OMNIHOME%\bin\nco_p_huawei_N2000_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 N2000(CORBA) generates. Not all the elements described are generated for each event;the elements that the probe generates depends upon the event type.

Table 7. Elements

Element name Element description

$additionalInfo This element contains additional informationabout the alarm.

$additionalText This element contains a brief description of theproblem being reported by the alarm.

$affectedTPList This element contains the list of terminationpoints affected by the problem being reported bythe alarm.

$emsTime This element contains the time when the alarmwas reported by the EMS.

$event_type This element contains the type of the alarm.

$isClearable This element indicates whether the alarm can becleared. This element can take the followingvalues:

false

true

$layerRate This element indicates the layer to which thealarm applies.

$nativeEMSName This element contains the name of the objectreporting the alarm as given in the EMS userinterface.

$nativeProbableCause This element contains the probable cause as givenin the EMS user interface.

$neTime This element contains the time at which the erroroccurred in the network element.

$notificationId This element contains a unique identifier for thealarm. This identifier is derived from the serialnumber of the alarm as used by the EMS.


Table 7. Elements (continued)

Element name Element description

$objectType This element contains the type of object reportingthe alarm.

$objectName This element contains the name of the objectreporting the alarm.

$perceivedSeverity This element contains the perceived severity ofthe alarm.

$probableCause This element contains the probable cause of thealarm.

$probableCauseQualifier This element indicates the qualifier used toclassify the alarm type.

$serviceAffecting This element indicates whether the alarm hasaffected the service.

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

Table 8. Error messages

Error Description Action

Failed to connect toNaming Service

The CORBA service is notrunning on the expectedHost/Port/IOR

The probe failed to connect tothe Naming Service. Eitherthe Naming Service was notrunning on the specified hostand port, or the IOR specifiedfor the Naming Service wasnot correct.

Check that the NamingService is running on thespecified host and port andthat the Naming Service IORis correct.

Failed to get interfaceversion information

Failed to ping Huaweiserver

The probe failed to getinterface version informationbecause it failed to pingHuawei server.

Check that the Huawei serveris running correctly and thatthe IOR files are up to date.

Failed to get objectreference from IOR file

Failed to get object fromIOR file

Failed to find file,please check file exists!

Failed to convert IOR toobject

Please check that theinterface is running andthe probe is using up todate IOR files

The probe failed to get theobject reference from the IORfile. Either the IOR filerequested was not found or itdid not contain a valid IORfile.

Check that the IOR file existsand that it is a valid IOR file.


Table 8. Error messages (continued)

Error Description Action

Failed to narrow objectreference

Failed to narrow managerreference

The probe failed to narrowthe object reference to theinterface object.

This is a CORBA related errorand is probably related to theCORBA installation.

Failed to resolve NamingContext

Exception raised whenlocating server

The probe failed to resolvethe naming context path tofind the server object. Eitherthe naming context path wasinvalid or did not exist.

Check theNamingContextPath property.

Name is null, cannotcreate element

Cannot parsetypevalue_type : name

Failed to parse alarm

The probe failed to parse thealarm.

Check that the alarmconforms to theStructuredEvent format.

Failed to run eventsynchronization

The EventSynch_T2000.shscript did not run properly.

Check the availability of theEventSynch_T2000.sh file inthe $OMNIHOME/probesdirectory.

Check that the values set forthe server, user and passwordin the EventSynch_T2000.shfile are correct.

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

Table 9. ProbeWatch messages

ProbeWatch message Description Triggers/causes

ClientSession event lossoccurred

There is a loss of eventsbetween the EMS and theObjectServer.

Events generated by EMShave failed to reach theObjectServer.

ClientSession event losscleared

A loss of events between theEMS and ObjectServer iscleared

Events are no longer beinglost and the EMS is nowcapable of providing relevantnotifications.

Failed to generate andprocess Probewatch eventfor the event loss beingcleared

The specified notification IRPfile does not exist.

The IRP manager is not set upcorrectly.

Will listen for commandson port number 6970

The probe is listening forcommands on the specifiedport.

The specified port is ready toreceive commands.


Table 9. ProbeWatch messages (continued)

ProbeWatch message Description Triggers/causes

Failed to listen forcommands on port number6970

The probe is not able to listento commands from thespecified port.

If this message occurred whenthe probe was trying toinitialize the connection, thereis insufficient memory tocomplete the operation.

If the message occurred aftersome event had been parsed,it will be because of one thefollowing reasons:

License failure.

Connection failure.

The port is already in use.

Performing Resynch.... The probe is performingresynchronization.

The probe has startedresynchronization.

Resynch Completed.... The probe found that theresynchronization is complete.

The probe has finishedresynchronization.


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, 2010 19

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

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

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

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

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

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

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

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

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

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

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

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


COPYRIGHT LICENSE:

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

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

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

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

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

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

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

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

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

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

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

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

Appendix. Notices and Trademarks 21

��

Printed in USA

SC23-7870-03

probe for huawei n2000

Documents

summary section

multiple probes section

ibm tivoli informationcenter

error messages section

probewatch messages

ibm publication

huawei n2000 corbaversion

copyright ibm corporation