Corba Huawei

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

Reference GuideApril 06, 2012

SC23-6031-05

��

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

Edition notice

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

This edition replaces SC23-6031-04.

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

Contents

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

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

Connecting to the CORBA interface. . . . . . 4Retrieving objects . . . . . . . . . . . . 5IRP Agent status . . . . . . . . . . . . 5Backoff strategy . . . . . . . . . . . . 5Timeout . . . . . . . . . . . . . . . 5Filtering notifications and alarms . . . . . . 6

Lookup table . . . . . . . . . . . . . 6Command Line Interface . . . . . . . . . 6Peer-to-peer failover functionality . . . . . . 8

Encrypting passwords . . . . . . . . . . . 8Properties and command line options . . . . . . 9Elements . . . . . . . . . . . . . . . 15

Parsing the AdditionalText element . . . . . 17Error messages . . . . . . . . . . . . . 18ProbeWatch messages . . . . . . . . . . . 21Running the probe . . . . . . . . . . . . 23Known issues. . . . . . . . . . . . . . 23

Appendix. Notices and Trademarks . . 25Notices . . . . . . . . . . . . . . . . 25Trademarks . . . . . . . . . . . . . . 27

© Copyright IBM Corp. 2008, 2012 iii

iv IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (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 M2000 (CORBA)documentation is provided in softcopy format only. To obtain the most recentversion, visit the IBM® Tivoli® Information Center:

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

Table 1. Document modification history

Documentversion

Publicationdate Comments

SC23-6031-01 March 28, 2008 First IBM publication.

SC23-6031-02 October 31,2010

Patch number updated in “Summary” on page 1.

The description of the device was updated in “IBM TivoliNetcool/OMNIbus Probe for Huawei M2000 (CORBA),”on page 1.

The Internationalization support section was updated.

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

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

SC23-6031-03 March 31, 2011 Installation section replaced by “Installing probes” onpage 3.

“Firewall considerations” on page 3 added.

© Copyright IBM Corp. 2008, 2012 v



Table 1. Document modification history (continued)

Documentversion

Publicationdate Comments

SC23-6031-04 December 02,2011

Information about operating system conventions added in“Conventions used in this guide.”

Requirements updated in “Summary” on page 1.

Lookup table information added in “Lookup table” onpage 6.

FTP information updated in “Connecting to the CORBAinterface” on page 4.

The FtpUsername property was removed.

The following new properties were added in “Propertiesand command line options” on page 9:

v ORBCharEncoding

v ORBLocalHost

v ORBWCharDefault

SC23-6031-05 April 06, 2012 Password encryption information updated in “Encryptingpasswords” on page 8.

The following new properties were added in “Propertiesand command line options” on page 9:

v ConfigCryptoAlg

v ConfigKeyFile

v FtpPasswordAESEncrypted

v Password

v Username

A new element, FULL_NV_ADDITIONAL_TEXT, was added in“Elements” on page 15.

The function of the FULL_NV_ADDITIONAL_TEXT element isexplained in “Parsing the AdditionalText element” onpage 17.

A known issue with the userid_comment_alarm CLIcommand was added in “Known issues” on page 23.

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:

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

$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 withthese probes, replace the UNIX conventions used in the guide with Windowsconventions. If you are using the bash shell on a Windows system, you can use theUNIX conventions.

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

Operating system-specific directory names

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

$OMNIHOME/probes/arch

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

Table 2. Directory names for the arch variable

Operating system Directory name represented 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

About this guide vii

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

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

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

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

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

The probe complies with the following 3GPP standards:

Table 3. Supported 3GPP standards

3GPP TechnicalSpecification Version Object

32.111 5.5.1 Alarm Integration Reference Point (IRP)

32.303 5.2.0 Notification IRP

32.623 5.2.0 Generic network resources IRP

This guide contains the following sections:v “Summary”v “Installing probes” on page 3v “Firewall considerations” on page 3v “Data acquisition” on page 4v “Encrypting passwords” on page 8v “Properties and command line options” on page 9v “Elements” on page 15v “Error messages” on page 18v “ProbeWatch messages” on page 21v “Running the probe” on page 23v “Known issues” on page 23

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

The following table summarizes the probe.

© Copyright IBM Corp. 2008, 2012 1

Table 4. Summary

Probe target Huawei iManager M2000 V200 R010, V200 R011, V200R012, V200 R013

Probe executable name nco_p_huawei_M2000_corba

Probe installation package omnibus-arch-probe-nco-p-huawei-M2000-corba-version

Package version 4.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=swg21579706

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

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

Requirements One of the following versions of IBM TivoliNetcool/OMNIbus:

v V7.2.0 with Interim Fix 4 (7.2.0.7-IF0004)

v V7.2.1 with Interim Fix 3 (7.2.1.5-IF0003)

v V7.3.0

v V7.3.1

Nonnative Probe Server: probe-nonnative-base-14

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

Java™ Runtime Environment (JRE) 1.5

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.

Multicultural support Available

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

Peer-to-peer failover functionality Available

IP environment IPv4 and IPv6

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.

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



http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htm

http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2004.htm

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

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

Advantage Online website.Each probe has a single installation package for each operating systemsupported. For details about how to locate and download the installationpackage for your operating system, visit the following page on the IBM TivoliInformation Center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_download_intro.html

2. Installing the probe using the installation package.The installation package contains the appropriate files for all supportedversions of Netcool/OMNIbus. For details about how to install the probe torun with your version of Netcool/OMNIbus, visit the following page on theIBM Tivoli Information Center:http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_OMNIbus.doc/probes/install/wip/out-html/reference/install_install_intro.html

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

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

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

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

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

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

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

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

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



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



c. The outgoing port on which the target system sends events if the probe isrunning as a client.

d. The incoming port on which the probe listens for incoming events.

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

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

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 gathers events from the Huawei M2000 system using a 3GPP CORBAinterface.

Data acquisition is described in the following topics:v “Connecting to the CORBA interface”v “Retrieving objects” on page 5v “IRP Agent status” on page 5v “Backoff strategy” on page 5v “Timeout” on page 5v “Filtering notifications and alarms” on page 6v “Lookup table” on page 6v “Command Line Interface” on page 6v “Peer-to-peer failover functionality” on page 8

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

The probe gets the object reference of the AlarmIRPOperation andNotificationIRPOperation objects from the IOR files specified by the AlarmIrpNameand NotificationIrpName properties. The AlarmIRPOperation andNotificationIRPOperation objects form a part of the Integration Reference Point(IRP) Agent.

To get the IOR files, the probe retrieves the Entry Point IRP file specified by theEntryPointIrpFile property.

If Entry Point IRP authentication is enabled on the IRP Agent, you must use theUsername and Password properties to specify the user name and password requiredto log in to the Huawei M2000 system.


Note: If an encrypted password has been configured in the Huawei M2000 EMSfor the RAN Sharing feature, you will have to obtain the encrypted passwordstring from the EMS vendor, Huawei Technologies.

Using FTP

If the Entry Point IRP file is on a remote system, the probe uses a File TransferProtocol (FTP) command to retrieve the file. To acquire the Entry Point IOR fileover FTP, you must specify the following value for the EntryPointIrpFtpCommandproperty:

ftp://username:password@EntryPointIorHost/

where username and EntryPointIorHost are the user name and host name of theEntry Point IRP server. Use the FtpPassword property to specify the password.

Example FTP command:

ftp://trisha:[email protected]

Example of an encrypted FtpPassword property value:

@44:AziJRb8nKabY//lhnhfrg41pCTN5iuCvh96Dcm97jC4=@

For more information about encrypting passwords, see “Encrypting passwords” onpage 8.

Retrieving objectsWhen the Resynch property is set to true, the probe initially receives a list of allactive alarms from the AlarmIRP object.

The probe then connects to the NotificationIRP object and uses the CORBAnotification push model to receive new alarms from the server as they aregenerated. When the Resynch property is set to false, the probe receives only newalarms.

IRP Agent statusThe probe checks the status of the IRP Agent every 60 seconds.

You can use the Agentheartbeat property to change the frequency with which theprobe checks the status of the IRP Agent.

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.

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


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

Filtering notifications and alarmsYou can use filtering properties to specify how the probe filters events to receiveonly preferred notifications and alarms.

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

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

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

You can use the e and h tokens as notification filter properties.

Lookup tableThe probe is supplied with a lookup table that contains details of the various typesof alarms that the Huawei M2000 generates.

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

$OMNIHOME/probes/includes/

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

include "../includes/Corba_3gpp_V630.lookup"

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

Command Line InterfaceThe probe is supplied with a Command Line Interface (CLI). This interface enablesyou to execute commands to acknowledge alarms or request a fullresynchronization of the 3GPP interface.

To use the CLI, you must use the CommandPort property to specify a port throughwhich commands will be sent. The default port is 6970. When you want to issuecommands, use Telnet to connect through this port. You can use theCommandPortLimit property to limit the number of Telnet connections that theprobe can make at one time.

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


Table 5. CLI commands

Command Description

exit

quit

Use these commands to close the connection.

help Use this command to display online help aboutthe CLI.

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

Before you can use this command, you must setthe Resynch property to true.

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

The filter parameter uses the same filter format asthe AlarmFilter property. For example:

> resynch_filter $h == 3

Before you can use this command, you must setthe Resynch property to true.

userid_acknowledge_alarm alarm_iduser_id

Use this command to acknowledge an alarm inthe CORBA interface by specifying the alarm ID(NV_ALARM_ID) and the user ID of the useracknowledging the alarm.

If you specify a value for the AckUserId property,the user_id parameter is not required.

userid_unacknowledge_alarm alarm_iduser_id

Use this command to unacknowledge an alarm inthe CORBA interface by specifying the alarm ID(NV_ALARM_ID) and the user ID of the useracknowledging the alarm.

If you specify a value for the AckUserId property,the user_id parameter is not required.

userid_clear_alarm alarm_id user_id Use this command to clear an alarm byspecifying the alarm ID (NV_ALARM_ID) and theuser ID of the user acknowledging the alarm.

If you specify a value for the ClearUserIdproperty, the user_id parameter is not required.

userid_comment_alarm alarm_id user_idcomment_text

Use this command to add comments to an alarmby specifying the alarm ID (NV_ALARM_ID), theuser ID of the user making the comment, and thetext of the comment.

If you specify a value for the CommentUserIdproperty, the user_id parameter is not required.

Note: There is a known issue with commentslonger than one word being logged as the user IDin the log file. For details, see “Known issues” onpage 23.

version Use this command to display the version of theprobe.


CLI scripts

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

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

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

Example property file settings for peer-to-peer failover

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

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"

Encrypting passwordsYou can encrypt the passwords specified by the Password and FtpPasswordproperties using either the nco_g_crypt utility or the nco_aes_crypt utilitysupplied with Netcool/OMNIbus.

If you encrypt the passwords using nco_aes_crypt, you must also specify valuesfor the ConfigCryptoAlg and ConfigKeyFile properties. For example:ConfigCryptoAlg: ’AES_FIPS’ConfigKeyFile: ’$NCHOME/omnibus/etc/keyfile’

If you encrypt the FTP password using the nco_aes_crypt utility, you must also setthe FtpPasswordAESEncrypted property to true.


For more information about encrypting property values, see the IBM TivoliNetcool/OMNIbus Probe and Gateway Guide (SC14-7608).

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

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

Table 6. Properties and command line options

Property name Command line option Description

AckUserId string -ackuserid string Use this property to specify theuser ID to use whenacknowledging andunacknowledging alarms using theCLI.

If you do not use the user_idparameter when acknowledging orunacknowledging an alarm usingthe CLI, the probe will add the userID specified by this property to therelated log entry.

The default is " ".

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

The default is 60.

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

The default is " ".

For more information aboutfiltering alarms, see “Filteringnotifications and alarms” on page6.

AlarmIrpName string -alarmirpname string Use this property to specify thename that the probe uses to resolvethe AlarmIRP point.

The default is AlarmIRP.


Table 6. Properties and command line options (continued)


ClearUserId string -clearuserid string Use this property to specify theuser ID to use when clearingalarms using the CLI.

If you do not use the user_idparameter when clearing an alarmusing the CLI, the probe will addthe user ID specified by thisproperty to the related log entry.

The default is " ".

CommandPort integer -commandport integer Use this property to specify theport to which users can connect tothe 3GPP interface using the CLI.

The default is 6970.

For more information about usingthe CLI, see “Command LineInterface” on page 6.

CommandPortLimitinteger

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

The default is 10.

CommentUserId sring -commentuserid string Use this property to specify theuser ID to use when addingcomments to alarms using the CLI.

If you do not use the user_idparameter when commenting on analarm using the CLI, the probe willadd the user ID specified by thisproperty to the related log entry.

The default is " ".

Note: There is a known issue withcomments longer than one wordbeing logged as the user ID in theprobe log file, regardless of thevalue of this property. For details,see “Known issues” on page 23.




ConfigCryptoAlg sring N/A Use this property to specify theencryption method used to encryptproperty values in the propertiesfile. This is intended for use withthe Password and FtpPasswordproperties.

The default is AES.

Use this property in conjunctionwith the ConfigKeyFile propertyand the nco_aes_crypt utilitysupplied with Netcool/OMNIbus.

For more information aboutencrypting passwords, see“Encrypting passwords” on page 8.

ConfigKeyFile sring N/A Use this property to specify thelocation of the key file used todecrypt property values.

The default is " ".

Use this property in conjunctionwith the ConfigCryptoAlg propertyand the nco_aes_crypt utilitysupplied with Netcool/OMNIbus.

For more information aboutencrypting passwords, see“Encrypting passwords” on page 8.

EncodingStandard sring -encodingstandard string Use this property to specify theencoding required to encode anddecode characters in events.

Specify a value of UTF8 for thisproperty to enable the probe toreceive events in languages that usemultibyte characters, such asChinese or Japanese.

The default is ISO-8859-1 (alsoknown as Latin-1).

EntryPointIrpFilestring

-entrypointirpfile string Use this property to specify thelocation of the Entry Point IRP IORfile.

The default is " ".

EntryPointIrpFtpCommand string

-entrypointirpftpcommandstring

Use this property to specify theFTP command used to retrieve theEntry Point IRP IOR file.

The default is " ".




FlushBufferIntervalinteger

-flushbufferintervalinteger

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

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

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

The default is " ".

For information about encryptingthe FTP password, see “Encryptingpasswords” on page 8.

FtpPasswordAESEncrypted string

-ftppasswordaesencryptedstring

Use this property to specifywhether the value of theFtpPassword is encrypted usingAES encryption. This propertytakes the following values:

true: The value of the FtpPasswordproperty is encrypted.

false: The value of the FtpPasswordproperty is not encrypted.

The default is false.

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

The default is V1.2.0.

ManagerIdentifierstring

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

The default is " ".

NotificationCategories string

-notificationcategoriesstring

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

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

category1;category2;categoryn

For example:

ALARM IRP V1.0.0; CS IRP V1.0.0

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




NotificationFilterstring

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

The default is " ".

NotificationIrpNamestring

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

The default is NotificationIRP.

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

Specify a value of UTF8 for thisproperty to enable the probe toreceive events in languages that usemultibyte characters, such asChinese or Japanese.

The default is ISO-8859-1 (alsoknown as Latin-1).

ORBLocalHost string -orblocalhost string Use this property to specify thefully qualified domain name(FQDN) or IP address of theprobe's host machine.

The default is " ".

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

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

ORBWCharDefault string -orbwchardefault string Use this property to specify whatwide character (wchar) set the IBMORB uses when communicatingwith other ORBs that do notpublish a wchar set.

The default is UTF16.

Password string -password string Use this property to specify thepassword required to log in to theHuawei M2000 system.

The default is " ".

Note: If an encrypted passwordhas been configured in the HuaweiM2000 EMS for the RAN Sharingfeature, you will have to obtain theencrypted password string from theEMS vendor, Huawei Technologies.




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

-noresynch (This isequivalent to Resynch with avalue of false.)

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

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

true: The probe attempts toresynch to the system.


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

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

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

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

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


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

If the Retry property is set to true,the probe will try to reconnectusing the standard backoff strategy.

The default is 0 (the probe does nottime out).

TimeTick integer -timetick integer Use this property to specify theduration (in minutes) of thesubscription to the target.

The default is -1 (this ensures thatthe session remains openindefinitely).

Note: A value of 15 releasesunused subscriptions and refreshesthe subscription.

Username string -username string Use this property to specify theuser name required to log in to theHuawei M2000 system.

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 table describes the elements that the probe generates. Not all theelements described are generated for each event. The elements that the probegenerates depend on the event type.

Table 7. Elements

Element name Element description

ADDITIONALTEXT_LINECOUNT This element indicates the number of lines withinthe AdditionalText element generated by the3GPP interface..

CLEAR_SYSTEM_ID This element indicates whether the systemidentifier has been cleared.

CLEAR_USER_ID This element indicates whether the user identifierhas been cleared.

FullAdditionalText This element contains all values contained in theAdditionalText element generated by the 3GPPinterface.

This element is generated when one of thefollowing conditions is met:

v The NV_ADDITIONAL_TEXT element has not yetbeen created.

v The data received is in the default 3GPP format(data type org.omg.CORBA.TCKind._tk_string).

v The keyword AdditionalText is detected in theparsed data.

FULL_NV_ADDITIONAL_TEXT This element contains the raw values containedin the 3GPP interface AdditionalText element.This element will be generated whenever theAdditionalText element is detected, andregardless of whether it contains name-valuepairs or not.

NV_ACK_STATE This element specifies the acknowledgement stateof the alarm.

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

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

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


Table 7. Elements (continued)


NV_ADDITIONAL_TEXT This element contains the raw values containedin the 3GPP interface AdditionalText elementthat are not name-value pairs. TheNV_ADDITIONAL_TEXT element is generated onlywhen there are undefined sub-elements in the3GPP interface AdditionalText element.

For example, if the AdditionalText elementcontains the string “Testing purposes only”(which is not a name-value pair), this string willbe mapped to the NV_ADDITIONAL_TEXT element, asshown in the probe's log file:

09/01/12 16:05:13: Debug: [Event Processor]FULL_NV_ADDITIONAL_TEXT: Testing purposesonly09/01/12 16:05:13: Debug: [Event Processor]NV_ADDITIONAL_TEXT: Testing purposes only

NV_ADDITIONAL_TEXT_LINEnn This element shows a single line within theAdditionalText element, where nn is the linenumber.

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

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

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

NV_ALARM_LIST_ALIGNMENT_REQUIREMENT This element indicates whether the alarm listrequires alignment.

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

NV_COMMENTS This element contains comments about thealarms.

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

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

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

NV_COMMENTS_TEXT This element contains the comment text.

NV_EVENT_TIME This element contains the time at which the eventoccurred.

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

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


Table 7. Elements (continued)


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

NV_NOTIFICATION_ID This element contains the identificationinformation of the notification.

NV_PERCEIVED_SEVERITY This element contains the perceived severity ofthe alarm.

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

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

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

NV_SECURITY_ALARM_DETECTOR This element identifies the security alarm detectorfor the device.

NV_SERVICE_PROVIDER This element contains the name of the serviceprovider.

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

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

NV_STATE_CHANGE_DEFINITION This element provides information about the statechange.

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

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

NV_THRESHOLD_INFO__ATTRIBUTE_ID This element provides identification informationabout a threshold object attribute.

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

NV_THRESHOLD_HIGH This element contains the maximum limit of thethreshold value.

NV_THRESHOLD_LOW This element contains the minimum limit of thethreshold value.

Parsing the AdditionalText elementVersion 4.0 of the probe introduced a new element, FULL_NV_ADDITIONAL_TEXT, totokenize parts of the 3GPP interface AdditionalText element.

The Huawei M2000 system appends any data that is not in a name-value pairformat to the AdditionalText element. Earlier versions of the probe tokenized thisunformatted data as an element name without a corresponding value, so this datacould not be parsed by the rules file. The new element FULL_NV_ADDITIONAL_TEXTenables the probe to tokenize the contents of the AdditionalText element.


Example tokenization

This example shows the contents of an AdditionalText element parsed by theprobe to create a FULL_NV_ADDITIONAL_TEXT token.

The AdditionalText element received by the probe:AdditionalText: ’NeType: CG| NeLocation: | vendor: | neName: CG_22|alarmName: No GSN Response| alarmLocation: igwb1: Alarmparameter=0,1,172.18.154.59,10601| appendInfo: | ALARM 63023 Cleared Major CG 59Software SystemAlarm name = No GSN ResponseAlarm raised time = 2011-07-25 02:33:49 DSTLocation info = igwb1: Alarm parameter=0,1,172.18.154.59,10601Cleared type = ClearedCleared time = 2011-07-25 02:34:23 DST’

The FULL_NV_ADDITIONAL_TEXT token created by the probe:FULL_NV_ADDITIONAL_TEXT: NeType: CG| NeLocation: | vendor: | neName: CG_22|alarmName: No GSN Response| alarmLocation: igwb1: Alarmparameter=0,1,172.18.154.59,10601| appendInfo: | ALARM 63023 Cleared Major CG 59Software SystemAlarm name = No GSN ResponseAlarm raised time = 2011-07-25 02:33:49 DSTLocation info = igwb1: Alarm parameter=0,1,172.18.154.59,10601Cleared type = ClearedCleared time = 2011-07-25 02:34:23 DST

NeType: CG

NeLocation:

vendor:

neName: CG_22

alarmName: No GSN Response

alarmLocation: igwb1: Alarmparameter=0,1,172.18.154.59,10601

appendInfo:

ALARM 63023 Cleared Major CG 59Software SystemAlarm name = No GSN ResponseAlarm raised time = 2011-07-25 02: 33:49 DSTLocation info = igwb1: Alarm parameter=0,1,172.18.154.59,10601Cleared type = ClearedCleared time = 2011-07-25 02:34:23 DST

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

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


Table 8. Error Messages

Error message Description Action

Failed to pingnotification service

Failed to getsubscription status

The probe has connectionproblems with theNotificationIRP point.

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

NetcoolIRPManager: Failedto acknowledge_alarms

The probe has failed toacknowledge the alarms.

Check that theNV_ALARM_ID specified bythe CLI is correct.

NetcoolIRPManager: Failedto clear alarms

The probe has failed to clearthe alarms.


NetcoolIRPManager: Failedto unacknowledge_alarms

The probe has failed tounacknowledge the alarms.


[Command Port] Failed toget property CommandPort

[Command Port] Threadshutting down due toerror!

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

[Command Port] Erroroccured

[Command Port] hostnameFailed to get socket IO

[Command Port] hostnameFailed to read command

[Command Port] hostnameFailed to close commandsocket

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

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

[Command Port] Failed toget CommandPortLimitproperty - using 10

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

Check the value ofCommandPortLimit property.

Cannot initialize the Orb There was a problem duringinitialization of the ORB.

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


Table 8. Error Messages (continued)


Communication failure -lost connection toNoticiationIRP:

CORBA.TRANSIENT exceptionraised. NotificationIRPis down!

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

RBA Exception stack traceto stderr

Failed to Connect

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

Cannot proceed. Shuttingdown!

There are no responses fromthe NotificationIRP point.

Check that the Huawei M2000server is running correctly.

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

Check that theEntryPointIrpFile property iscorrectly set in the propertiesfile.

Failed to narrow EntryPoint IRP interface

Failed to narrow the objectreference to the Entry PointIrpAgent object.

Check that theEntryPointIrpFile property iscorrectly set in the propertiesfile.

Failed to perform resynch

Failed to iterate throughresynch alarms

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

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

FtpPassword is incorrectlength (ensure it hasbeen encrypted usingnco_g_crypt)

There is a problem with theencrypted password.

Check the value of theFtpPassword property in theproperties file.

NetcoolIRPManager: ERRORwhen parsing anotification event

NetcoolIRPManager: StackTrace to stderr:

Failed to parse eventcompletely

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

Check that the HuaweiM2000server is runningcorrectly.

NetcoolIRPManager: Failedto send event

The probe could not forwardthe Event to the ObjectServer.

Check that the ObjectServer isrunning.

OperationNotSupportedException

There is a problem with theCORBA interface.

Refer to your CORBAdocumentation.


Table 8. Error Messages (continued)


NetcoolIRPManager: Failedto retrieve AlarmIRPobject from entry pointinterface

NetcoolIRPManager: Failedto retrieveNotificationIRP objectfrom entry pointinterface

Problem while trying toconnect to the IRP points

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

Failed to get either theAlarmIRP or the NotificationIRP object.

Check that the AlarmirpNameand NotificationirpNameproperties are correctly set inthe properties file.

ProbeWatch messagesDuring normal operations, the probe generates ProbeWatch messages and sendsthem to the ObjectServer. These messages tell the ObjectServer how the probe isrunning.

The following table describes the ProbeWatch messages that the probe generates.For information about generic Netcool/OMNIbus ProbeWatch messages, see theIBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 9. ProbeWatch messages

ProbeWatch messages Description Triggers/causes

Communication failure -lost connection toNoticiationIRP

CORBA.TRANSIENT Exception:Lost connection toNotificationIRP

CORBA.OBJECT_NOT_EXISTException: Lost connectionto NotificationIRP

Failed to connect toNotificationIRP: Shuttingdown

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

Communication with thenotification IRP server hasfailed.

The probe lost its connectionto the notification IRP server.


Table 9. ProbeWatch messages (continued)


END SYNCHRONIZATION The resynchronization ofalarms has stopped.

The probe hasresynchronized all theavailable alarms in theserver.

Failed to find IOR filealarmirp_ior_file

The specified alarm IRP filedoes not exist.

The IRP manager has beenset up incorrectly.

Failed to find IOR filenotificationirp_ior_file

The specified notification IRPfile does not exist.

The IRP manager has beenset up incorrectly.

Failed to get IRP Outline(GetIRPOutline exceptioncaught when callingget_IRP_outline)

Unexpected fatal errorwhen getting IRP referencefrom Entry Point IRP

Unexpected fatal errorwhile getting IRP Outline

The probe could not get theIRP object.

There is a problem with theCORBA interface.

Failed to get IRPreference (GetIRPReferenceexception caught whencalling get_IRP_reference)

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

The probe could not get theIRP version.

An incorrect reference isspecified in the IRP file.

Failed to get subscriptonstatus

The probe lost its connectionto the server.

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

Failed to listen forcommands on port numberlistening_port

A problem occurred whiletrying to listen forcommands.

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

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

Failed to log in tointerface(InvalidParameterexception caught whencalling get_IRP_outline)

Unexpected fatal error,failed to connect

The probe failed to login tothe server.

The specified user name andpassword are incorrect.


Table 9. ProbeWatch messages (continued)


Failed to log in to theSecurity IRP - incorrectusername/password

The probe failed to login tothe Security IRP.

The password entered doesnot match the user name.

Invalid IRPVersion(InvalidIRPVersionexception caught whencalling get_IRP_outline)

The specified IRP version isincorrect.

An incorrect IRP name isspecified in the propertiesfile.

NetcoolIRPManager: Failedto find IOR file ior_file

The specified IOR file doesnot exist.

The IRP Manager has beenset up incorrectly.

PermissionDenied(PermissionDeniedexception caught whencalling get_IRP_outline)

Permission to login to theserver is denied.

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

probe cannot reach remoteServer

The probe failed to login tothe server.

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

START SYNCHRONIZATION The resynchronization ofalarms has started.

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

Will listen for commandson port numberlistening_port

The probe is now listeningfor commands on thespecified port number.

The probe has successfullycreated the specifiedcommand port in theproperties file.

Running the probeYou run the probe from the command line.

To start the probe, use the following command:

$OMNIHOME/probes/nco_p_huawei_M2000_corba

Known issuesAt the time of release, a known issue was reported that you should be aware ofwhen running the probe.

Alarm comments logged as user ID

The userid_comment_alarm CLI command enables you to add comments to analarm by specifying the alarm ID (NV_ALARM_ID), the user ID of the user making thecomment, and the text of the comment. It is also possible to use this commandwithout specifying the user ID, in which case the user ID specified by theCommentUserId property is added to the related entry in the probe's log file.

However, when you use the command without specifying a user ID, and thecomment that you add contains more than one word, the entire comment string islogged in the probe's log file in place of the user ID. This happens regardless of thevalue specified by the CommentUserId property.


The following example demonstrates how the CLI successfully completes auserid_comment_alarm command where only the alarm ID and the comment stringare entered:> userid_comment_alarm 2042480408 testing purposes onlyCompleted userid_comment_alarm

In this case, the related entry in the probe's log file contains the comment stringtesting purposes only in place of the user ID.


Appendix. Notices and Trademarks

This appendix contains the following sections:v Noticesv Trademarks

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

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

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

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

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

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

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

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

© Copyright IBM Corp. 2008, 2012 25

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

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

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

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

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

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

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

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

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

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

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

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


COPYRIGHT LICENSE:

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

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

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

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

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

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

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

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

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. 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.

Appendix. Notices and Trademarks 27

��

Printed in USA

SC23-6031-05

Corba Huawei

Documents

Transcript of Corba Huawei