IBM Tivoli Netcool/OMNIbus Probe for Huawei U2000 … IBM Tivoli Netcool/OMNIbus Probe for Huawei U2000 (CORBA): Reference Guide. ... you must add the appropriate firewall rules to

Netcool/OMNIbus Probe for Huawei U2000 (CORBA)Version 1.0.0

Reference GuideFebruary 25, 2011

SC14-7630-01

��

Netcool/OMNIbus Probe for Huawei U2000 (CORBA)Version 1.0.0

Reference GuideFebruary 25, 2011

SC14-7630-01

��

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

Edition notice

This edition applies to version 1.0.0 of IBM Tivoli Netcool/OMNIbus Probe for Huawei U2000 (CORBA)(SC14-7630-01) and to all subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC14-7630-00.

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

||

|

Contents

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

IBM Tivoli Netcool/OMNIbus Probe forHuawei U2000 (CORBA) . . . . . . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Configuring network resource names . . . . . . 3Firewall considerations . . . . . . . . . . . 3

Configuring firewall settings . . . . . . . . 4SSL-based connectivity . . . . . . . . . . . 4Data acquisition . . . . . . . . . . . . . 6

Event synchronization . . . . . . . . . . 6Server failover . . . . . . . . . . . . . 7Retrieving alarms . . . . . . . . . . . . 7

Filtering alarms . . . . . . . . . . . . 7Status checking . . . . . . . . . . . . 8Read timeout . . . . . . . . . . . . . 8Backoff strategy . . . . . . . . . . . . 8Command line interface . . . . . . . . . 8Peer-to-peer failover functionality . . . . . . 9Running multiple probes . . . . . . . . . 9

Properties and command line options . . . . . 10Elements . . . . . . . . . . . . . . . 17Error messages . . . . . . . . . . . . . 19ProbeWatch messages . . . . . . . . . . . 20

Appendix. Notices and Trademarks . . 23Notices . . . . . . . . . . . . . . . . 23Trademarks . . . . . . . . . . . . . . 25

© Copyright IBM Corp. 2006, 2011 iii

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

About this guide

The following sections contain important information about using this guide.

Document control pageUse this information to track changes between versions of this guide.

The IBM Tivoli Netcool/OMNIbus Probe for Huawei U2000 (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.namomnibus.doc/welcome_ptsm.htm

Table 1. Document modification history

Documentversion

Publicationdate

Comments

00 October 29,2010

First IBM publication.

01 February 25,2011

Summary

02 July 6, 2012 Summary

Conventions used in this guideAll probe guides use standard conventions for operating system-dependentenvironment variables and directory paths.

Operating system-dependent variables and paths

All probe guides use standard conventions for specifying environment variablesand describing directory paths, depending on what operating systems the probe issupported on.

For probes supported on UNIX and Linux operating systems, probe guides use thestandard UNIX conventions such as $variable for environment variables andforward slashes (/) in directory paths. For example:

$OMNIHOME/probes

For probes supported only on Windows operating systems, probe guides use thestandard Windows conventions such as %variable% for environment variables andbackward slashes (\) in directory paths. For example:

%OMNIHOME%\probes

For probes supported on UNIX, Linux, and Windows operating systems, probeguides use the standard UNIX conventions for specifying environment variablesand describing directory paths. When using the Windows command line with

© Copyright IBM Corp. 2006, 2011 v



these probes, replace the UNIX conventions used in the guide with Windowsconventions. If you are using the bash shell on a Windows system, you can use theUNIX conventions.

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

Operating system-specific directory names

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

$OMNIHOME/probes/arch

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

Table 2. Directory names for the arch variable

Operating system Directory name represented by arch

AIX® systems aix5

HP-UX PA-RISC-based systems hpux11

HP-UX Integrity-based systems hpux11hpia

Red Hat Linux and SUSE systems linux2x86

Linux for System z® linux2s390

Solaris systems solaris2

Windows systems win32

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

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

The Huawei U2000 is a unified network management system that provides elementmanagement and network management functions for telecommunicationsnetworks.

The Probe for Huawei U2000 (CORBA) acquires data from the Huawei U2000element management system (EMS) 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.

This guide contains the following sections:v “Summary”v “Installing probes” on page 2v “Configuring network resource names” on page 3v “Firewall considerations” on page 3v “SSL-based connectivity” on page 4v “Data acquisition” on page 6v “Properties and command line options” on page 10v “Elements” on page 17v “Error messages” on page 19v “ProbeWatch messages” on page 20

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

The following table provides a summary of the IBM Tivoli Netcool/OMNIbusProbe for Huawei U2000 (CORBA).

Table 3. Summary

Probe target Huawei U2000 (CORBA) on iMAP V300R001C01 (orlater)

Probe executable name nco_p_huawei_T2000_corba

Package version 1.0

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

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

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

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

© Copyright IBM Corp. 2006, 2011 1

|



Table 3. Summary (continued)

Requirements A currently supported version of IBM TivoliNetcool/OMNIbus.

JDK 1.5

probe-nonnative-base-7 (or later)

probe-visibroker8-support-2 (or later)

If you are running IBM Tivoli Netcool/OMNIbusV7.1.0, you must have Interim Fix 8 (7.1.0.11-IF0008)installed.



Connection method CORBA

Remote connectivity The probe can connect to a remote device using theCORBA 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 AvailableNote: The probe supports internationalization on IBMTivoli Netcool/OMNIbus V7.3.0, 7.3.1 or 7.4.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.3.0, 7.3.1 and 7.4.0 onall UNIX and Linux operating systems.

Federal Information ProcessingStandards (FIPS)

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

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

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

Advantage Online website.

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

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 additional configuration that iscommon to all probes, see the IBM Tivoli Netcool/OMNIbus Probe and GatewayGuide.

Configuring network resource namesAfter installing the probe, you might need to change the names of any networkresources that report alarms.

The probe breaks event data down into tokens and parses them into elements.These elements are then used to assign values to ObjectServer fields.

The element $nativeEMSName contains the name of the network resource reportingan alarm, as displayed in the EMS user interface. If brackets are passed to the$nativeEMSName element as part of a resource name, the node field in the event listwill not be filled. Therefore, any network resource that reports alarms must beconfigured so that its name does not contain brackets.

Firewall considerationsWhen using CORBA probes in conjunction with a firewall, the firewall must beconfigured so that the probe can connect to the target system.

Most CORBA probes can act as both a server (listening for connections from thetarget system) and a client (connecting to the port on the target system to whichthe system writes events). If you are using the probe in conjunction with a firewall,you must add the appropriate firewall rules to enable this dual behavior.

There are three possible firewall protection scenarios, for which you mustdetermine port numbers before adding firewall rules:1. If the host on which the probe is running is behind a firewall, you must

determine what remote host and port number the probe will connect to.2. If the host on which the target system is running is behind a firewall, you must

determine the incoming port on which the probe will listen and to which thetarget system will connect.

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



3. If each host is secured with its own firewall, you must determine the followingfour ports:a. The outgoing port (or port range) for the probe.b. The hostname and port of the target system.c. The outgoing port on which the target system sends events if the probe is

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

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

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

Configuring firewall settingsThe Probe for Huawei U2000 (CORBA) can be used in conjunction with a firewall.

If a firewall exists between the probe and the target system, you must configurethe following firewall ports to enable data flow:v The Naming Service port number.

The port for this service is on the target system. You must also specify this porton the probe side of the firewall, using the ORBInitialPort property. The defaultvalue of the ORBInitialPort property is 1570.

v The notification service port number.The port for this service is on the target system. This port number is usuallyrandom but can be set to a fixed value by the administrator of the target system.No firewall configuration is required on the probe side.

v The CORBA Agent (ORB at target system or inter-ORB bridge) port number.The port number is specified both on the target system and on the probe side ofthe firewall. On the probe side, use the OrbLocaLPort property to specify thisvalue, which must be greater than 0. The port number on the target system canbe obtained from either the Naming Service or the Interoperable ObjectReference file (specified by the IORFile property).

When using the probe over Secure Sockets Layer (SSL) connections, you mustconfigure the same ports listed above.

SSL-based connectivityThe Probe for Huawei U2000 (CORBA) supports Secure Sockets Layer (SSL)connections between the probe and the EMS server. SSL connections provideadditional security when the probe retrieves alarms from the EMS.

To enable SSL connections, you must obtain the required SSL certificates and theTrusted Authority certificate from the EMS vendor, Huawei Technologies. Thecertificates must be added to a local Java keystore so that they can be referencedby the ClientCertificate and TrustStore properties.


Prerequisites

To create the keystore, you must have the following software installed:v The OpenSSL toolkit.

This is available from http://www.openssl.org/.v The IBM KeyMan utility.

This is available from http://www.alphaworks.ibm.com/tech/keyman/download.

You must also obtain the client and server certificates, client_ca.cer andserver_ca.cer, and the server key pair, server_key.pem, from HuaweiTechnologies.

Note: The certificate and key pair files used here are the default files used by theHuawei U2000 EMS. If you replace these files, you must create a keystorecontaining the new files.

Creating the SSL keystore

To create a Java keystore, follow these steps:1. Convert the server certificate to PKCS12 format using the following OpenSSL

toolkit command:openssl pkcs12 -export -inkey server_key.pem -in server_ca.cer -outserver_ca.pkcs12

2. Create the keystore using the KeyMan utility:a. Start the KeyMan utility.b. Click Create New and select the Keystore token option.c. Click File > Import and choose the server_ca.pkcs12 file that you created

in step 1.This imports the keyEntry into the keystore.

d. Click File > Import and choose the server_ca.cer certificate.This imports the server certificate into the keystore.

e. Click File > Import and choose the client_ca.cer certificate.This imports the client certificate into the keystore.

f. Click File > Save and enter a password and name for the keystore, forexample trusted_keystore.jks.

Enabling SSL connections

To enable SSL-based connections between the probe and the EMS server, followthese steps:1. Set the EnableSSL property to true.

When the EnableSSL property is set to true, the following properties areenabled:v ClientCertificate

v ClientCertificatePassword

v TrustStore

v TrustStorePassword

v EnabledProtocols

v SecurityProtocol


http://www.openssl.org/

http://www.alphaworks.ibm.com/tech/keyman/download

http://www.alphaworks.ibm.com/tech/keyman/download

2. Use both the ClientCertificate property and the TrustStore property tospecify the location of the keystore file trusted_keystore.jks.

3. Use both the ClientCertificatePassword property and the TrustStorePasswordproperty to specify a password for the keystore.

4. Encrypt the keystore file password using the nco_g_crypt utility.

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 U2000 (CORBA) gathers events from the EMS using aCORBA interface.

This section contains the following topics:v “Event synchronization”v “Server failover” on page 7v “Retrieving alarms” on page 7v “Filtering alarms” on page 7v “Status checking” on page 8v “Read timeout” on page 8v “Backoff strategy” on page 8v “Command line interface” on page 8v “Peer-to-peer failover functionality” on page 9v “Running multiple probes” on page 9

Event synchronizationThe probe supports event synchronization between the EMS server and theObjectServer.

When the probe reconnects and requests a full resynchronization, the EMS doesnot send any cleared alarms. The ObjectServer will still show those alarms in itsevent list.

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_U2000.sh file, located in the $OMNIHOME/probes/directory:Server="NCOMS" (Object Server Name)User="root" (User name of Object Server)Password="" (Password)


Server failoverIf events are not received within a specified time period, the probe can switchbetween the CORBA Naming Services of a primary EMS server and a secondaryEMS server.

The ServerSwitchingTime property specifies the amount of time the probe waits toreceive events before disconnecting from the primary EMS server and switching tothe secondary EMS server. The probe will continue to switch between the primaryand secondary server until a connection is made to one of them.

Note: To enable the server failover function, the following conditions must be met:1. The EnableFailover property must be set to true to enable the values specified

in the following properties:v ServerSwitchingTime

v SecondaryIORFile

v SecondaryNamingContextIORFile

v SecondaryORBInitialHost

v SecondaryORBInitialPort

2. The Retry property must be set to true.If the Retry property is set to false, the probe will not be in continuousreconnect mode and will not failover to the secondary EMS server.

3. The value of the ServerSwitchingTime property must not exceed 4096 seconds.This is the default value of the backoff strategy time that, if exceeded, willcause the probe to disconnect from the CORBA interface.

Retrieving alarmsThe probe initially receives a list of all active alarms from the AlarmIRP server. Theprobe then connects to the NotificationIRP server and uses the CORBA notificationpush model to receive new alarms from the server as they are generated.

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

The filtering properties allow you to exclude resynchronization alarms according totheir severity. They cannot be used to filter new notification alarms.

For example, to exclude alarms of severity Indeterminate, set theExcludeSeverityIndeterminate property to true.

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

The Filtering properties table shows the filtering properties that are available.

Table 4. Filtering properties

Property Alarm Severity

ExcludeSeverityCleared Cleared

ExcludeSeverityCritical Critical

ExcludeSeverityIndeterminate Indeterminate

ExcludeSeverityMajor Major

ExcludeSeverityMinor Minor


Table 4. Filtering properties (continued)

Property Alarm Severity

ExcludeSeverityWarning Warning

Status checkingThe probe checks that the EMS server is running by sending a ping commandevery 60 seconds. You can change this frequency using the AgentHeartbeatproperty.

Read timeoutThe ReadTimeout property specifies how long the probe waits to read alarm databefore timing out. Each time the probe attempts to read an alarm, this is theallotted time that it waits to receive data. If nothing is received, the probe moveson to the next alarm.

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.

Command line interfaceThe Probe for Huawei U2000 (CORBA) is supplied with a Command Line Interface(CLI) that allows you to execute commands using the probe.

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

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

Table 5. CLI commands

Command Description

exit/quit Use this command to close the connection.

help Use this command to display online help aboutthe CLI.

resynch_alarm Use this command to perform a full or partialresynchronization of the alarms. A full or partialresynchronization will depend on the value of theExcludeSeverity properties (Cleared, Critical,Indeterminate, Major, Minor, Warning) specified inthe properties file.

version Use this command to display the version of theprobe and the CLI.

Note: As the CLI is based on Telnet connections, you can connect to the probefrom anywhere by creating a desktop tool to open a Telnet connection, send a


command, and then close the connection. This means that simple scripts can be 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"

Running multiple probesYou can run multiple instances of the probe.

For each running instance, specify a different port to which the server listens usingthe ORBLocalPort property.

Running multiple probes in a failover configuration

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

Where you are running this configuration in conjunction with a firewall, add thereceiving port of each probe to the firewall rules. The direction of the connection isfrom the target system to the master or slave probe.

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


Include the following peer-to-peer settings in the master's probe properties file:PeerHost : "slave_hostname"PeerPort : 5555 # [communication port between master and slave probes]

Include the following peer-to-peer settings in the slave's probe properties file:PeerHost : "master_hostname"PeerPort : 5555 # [communication port between master and slave probes]

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 EMS serveris still running.

The default is 60.

ClientCertificate string -clientcertificate string Use this property to specify thelocation of the keystore file thatcontains the client certificate forSSL.

The default is "".

ClientCertificatePassword string

-clientcertificatepassword string

Use this property to specify thepassword required to access thecertificate specified by theClientCertificate property.

The default is "".

Note: You must encrypt thispassword using the nco_g_cryptutility with Netcool/OMNIbus.

CommandPort integer -commandport integer Use this property to specify theport to which users can connectusing Telnet and run commands.

The default is 6970.

CommandPortLimit integer -commandportlimit integer Use this property to specify themaximum number of commandport sessions.

The default is 10.


Table 6. Properties and command line options (continued)


EnableFailover string -noenablefailover (Thisis equivalent toEnableFailover with avalue of false.)

-enablefailover (This isequivalent toEnableFailover with avalue of true.)

Use this property to specifywhether the server failoverfunction between the probe andthe primary and secondary EMSservers is enabled or disabled.This property takes the followingvalues:

false: The server failover functionbetween the probe and the EMSservers is disabled.

true: The server failover functionbetween the probe and the EMSservers is enabled.

The default is false.

EnabledProtocols string -enabledprotocols string Use this property to specify thelist of comma-separated valuesthat indicate the enabledprotocols, for example SSLv2,SSLv3, and so on.

The default is SSLv2.

EnableSSL string -noenablessl (This isequivalent to EnableSSLwith a value of false.)

-enablessl (This isequivalent to EnableSSLwith a value of true.)

Use this property to specifywhether SSL connectivity betweenthe probe and the EMS server isenabled or disabled. This propertytakes the following values:

false: SSL connectivity betweenthe probe and the EMS server isdisabled.

true: SSL connectivity between theprobe and the EMS server isenabled.


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 while the probe was notrunning. This property takes thefollowing values:

false: The probe does notsynchronize with the EMS onstartup.

true: The probe synchronizes withthe EMS on startup.


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

ExcludeSeverityClearedstring

-excludecleared (This isequivalent toExcludeSeverityClearedwith a value of true.)

-noexcludecleared (This isequivalent toExcludeSeverityClearedwith a value of false.)

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 alarmsof severity Cleared.


ExcludeSeverityCriticalstring

-excludecritical (This isequivalent toExcludeCritical with avalue of true.)

-noexcludecritical (Thisis equivalent toExcludeCritical with avalue of false.)

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 alarmsof severity Critical.





ExcludeSeverityIndeterminate string

-excludeindeterm (This isequivalent toExcludeSeverityIndeterminate with avalue of true.)

-noexcludeindeterm (Thisis equivalent toExcludeSeverityIndeterminate with avalue of false.)

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 alarmsof severity Indeterminate.


ExcludeSeverityMajorstring

-excludemajor (This isequivalent toExcludeSeverityMajorwith a value of true.)

-noexcludemajor (This isequivalent toExcludeSeverityMajorwith a value of false.)

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 alarmsof severity Major.


ExcludeSeverityMinorstring

-excludeminor (This isequivalent toExcludeSeverityMinorwith a value of true.)

-noexcludeminor (This isequivalent toExcludeSeverityMinorwith a value of false.)

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 alarmsof severity Minor.


ExcludeSeverityWarningstring

-excludewarning (This isequivalent toExcludeSeverityWarningwith a value of true.)

-noexcludewarning (This isequivalent toExcludeSeverityWarningwith a value of false.)

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 alarmsof severity Warning.





FlushBufferIntervalinteger

-flushbufferintervalstring

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 thelocation of the Inter-operableObject Reference (IOR) file for theinterface objectEmsSessionFactory_I on the EMS.

The default is "".

NamingContextIORFilestring

-nsior string If the values of either theORBInitialHost or theORBInitialPort properties are notspecified, use this property tospecify the location of the IOR filethat contains the root context ofthe Naming 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\\/U2000.EmsInstance/2\\.0.Version/Huawei\\/U2000.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


ORBLocalPort integer -orbinitialport 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 required with theUsername property to log in to thesystem.

The default is "".




PersistenceFile string -persistencefile string Use this property to specify thelocation of the IOR file for thenotification service.

The default is "".

PersistentNotificationstring

-nopersist (This isequivalent toPersistentNotificationwith a value of false.)

-persist (This isequivalent toPersistentNotificationwith a value of true.)

Use this property to specifywhether the probe reuses the sameIOR for the notification service onreconnection. This property takesthe following values:

false: The probe does not use thesame IOR for reconnection.

true: The probe uses the sameIOR for reconnection.


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

-resynch (This isequivalent to Resynch witha 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 performresynchronization.


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




SecondaryIORFile string -seciorfile string Use this property to specify thelocation of the IOR file of thesecondary EMS server.

The default is "".

SecondaryNamingContextIORFile string

-secnsior string Use this property to specify thelocation of the IOR file for the rootcontext of the Naming Service ofthe secondary EMS server.

The default is "".

SecondaryORBInitialHoststring

-secorbinitialhost string Use this property to specify theNaming Service host name of thesecondary EMS server.

The default is "".

SecondaryORBInitialPortstring

-secorbinitialport string Use this property to specify theNaming Service port number ofthe secondary EMS server.

The default is 1570 .

SecurityProtocol string -securityprotocol string Use this property to specify thesecurity protocol. This propertytakes the following values:

SSL

SSLv2

SSLv3

TLS

TLSv1

The default is TLSv1.

ServerSwitchingTimeinteger

-serverswtime integer Use this property to specify thetime (in seconds) that the probewaits to receive events beforedisconnecting from the CORBANaming Service of the primaryEMS server and switching to theCORBA Naming Service of thesecondary EMS server.


Note: The probe will continue toswitch between the primary andsecondary server, in the specifiedtime, until a connection is made toeither server.




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 (the probe nevertimes out).

TrustStore string -truststore string Use this property to specify thepath to the keystore file containingthe trusted authority certificate.

The default is "".

TrustStorePassword string -truststorepasswordstring

Use this property to specify thepassword required to access thekeystore file containing the trustedauthority certificate.

The default is "".

Note: You must encrypt thispassword using the nco_g_cryptutility within Netcool/OMNIbus.

Username string -username string Use this property to specify theuser name of the account withwhich the probe logs in to theEMS interface.

The default is "".

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 tables describe the elements that the Probe for Huawei U2000(CORBA) generates. Not all the elements described are generated for each event.The elements that the probe generates depend 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 displays the list of terminationpoints affected by the problem being reported.

$emsTime This element indicates the time at which thealarm was reported by the EMS.

$event_type This element indicates the type of the alarm.


Table 7. Elements (continued)


$isClearable This element indicates whether the alarm can becleared. The possible values are:

false

true

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

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

Note: Object names must not contain brackets. Ifbrackets are passed to the $nativeEMSNameelement as part of an object name, the node fieldin the event list will not be filled.

$nativeProbableCause This element indicates the probable cause asgiven in the EMS user interface.

$neTime This elements indicates the time at which theerror occurred in the network element.

$notificationId This element contains the unique identifier of thealarm. This is derived from the serial number ofthe alarm as used by the EMS.

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

$objectType This element indicates the type of objectreporting the alarm.

$perceivedSeverity This element indicates the perceived severity ofthe alarm.

$probableCause This element contains the probable cause of thealarm.

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

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

Table 8. Elements specific to NT_PROTECTION_SWITCH alarms


$protectedTP This element identifies the protected terminationpoint when the switch occurs.

$ProtectionType This element indicates the type of protection.

$switchAwayFromTP This element identifies the source terminationpoint from where the switch is being made.

$switchReason This element indicates the reason why the switchhas been made.

$switchToTP This element identifies the destinationtermination point where the switch is beingmade.


Table 9. Elements specific to NT_TCA alarms


$granularity This element contains the details of the thresholdthat has been crossed.

$pmParameterName This element contains the pmParameter that hascrossed the threshold.

$pmLocation This element indicates the pmLocation where thethreshold has been crossed.

$thresholdType This element indicates whether a threshold wasset for the log report.

$unit This element contains the faulty program unit.

$value This element contains the threshold 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-6373).

Table 10. 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 call amethod on the Huawei 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 10. 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 the NamingContextPathproperty.

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.

There is a possibilitythat the Persistent Eventfeature has not beeninitiated on the ORB, oris not available on thisORB implementation.Please check with yourORB provider on how to dothis

Persistence has not beenenabled for this ObjectRequest Broker (ORB), or it isnot available for thisimplementation of the ORB.

Check that the PersistentEvent feature has beeninitiated on the ORB.

Failed to run eventsynchronization

The EventSynch_U2000.shscript did not run properly.

Verify that theEventSynch_U2000.sh fileexists in the $OMNIHOME/probesdirectory and that thepermissions have been setcorrectly.

Check the value of the server,user, and password fields inthe EventSynch_U2000.sh file.

Failed to get EMS sessionobject :

org.omg.CORBA.OBJ_ADAPTER:

java.net.BindException:Address already in use

Either the ORBLocalPortproperty has been set but theport is occupied by anotherprocess, or the ORBLocalPortand Retry properties havebeen set but the probe'slistening port has not beenproperly released before theprobe attempts to reconnect tothe EMS server.

Check that the ORBLocalPortis set to a port that is notoccupied by other processes,or disable the Retry propertyand then set up the processcontrol to restart the probe.

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 11. ProbeWatch messages

ProbeWatch message Description Triggers/causes

ClientSession event lossoccurred.

Events were lost between theEMS and the ObjectServer.

Events are being lost and theEMS is not able to providerelevant notifications.

ClientSession event losscleared.

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.

Performing Resynch.... The probe is performingresynchronization.

The probe has startedresynchronization.

Will listen for commandson port number 6970.

The probe will listen forcommands on the specifiedport number.

The probe has successfullycreated the specifiedcommand port in theproperties file.

Failed to listen forcommands on port number6970.

A problem occurred whiletrying to listen for commandson the specified port number.

There was a probleminitializing the connectionbecause of insufficientmemory or, if this messagewas sent after some eventswere parsed, there was alicense failure, a connectionfailure, or the port is alreadyin use.



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 23

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. inthe United States, other countries, or both.

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

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

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

Appendix. Notices and Trademarks 25


��

Printed in USA

SC14-7630-01

Documents

IBM Tivoli Netcool/OMNIbus Probe for Huawei U2000 … IBM Tivoli Netcool/OMNIbus Probe for Huawei U2000 (CORBA): Reference Guide. ... you must add the appropriate firewall rules to