Hum2co PDF

IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000
(CORBA)
Version 4.0
Reference Guide
August 22, 2014
SC23-6031-06

(CORBA)
Version 4.0
Reference Guide
August 22, 2014
SC23-6031-06
Notice
Before using this information and the product it supports, read the information in Notices and Trademarks, on page 25.
Edition notice
This edition (SC23-6031-06) 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-05.
Copyright IBM Corporation 2008, 2014.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this guide . . . . . . . . . . . v
Document control page . . . . . . . . . . . v
Conventions used in this guide . . . . . . . vii
IBM Tivoli Netcool/OMNIbus Probe for

Huawei M2000 (CORBA) . . . . . . . . 1
Summary . . . . . . . . . .
Installing probes . . . . . . . .
Firewall considerations . . . . . .
Data acquisition . . . . . . . .
Connecting to the CORBA interface.
Retrieving objects . . . . . . .
IRP Agent status . . . . . . .
Backoff strategy . . . . . . .
Timeout . . . . . . . . . .
Filtering notifications and alarms .
Copyright IBM Corp. 2008, 2014
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
2
3
4
4
5
5
5
5
6
Lookup table . . . . . . . .
Command Line Interface . . . .
Peer-to-peer failover functionality .
Encrypting passwords . . . . . .
Properties and command line options .
Elements . . . . . . . . . .
Parsing the AdditionalText element
Error messages . . . . . . . .
ProbeWatch messages . . . . . .
Running the probe . . . . . . .
Known issues. . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6
. 6
. 8
. 9
. 9
. 15
. 18
. 19
. 22
. 24
. 24
Appendix. Notices and Trademarks . . 25

Notices . . .
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 25
. 27
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 page

Use this information to track changes between versions of this guide.
The IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA)
documentation is provided in softcopy format only. To obtain the most recent
version, visit the IBM Tivoli Information Center:
http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/common/
kc_welcome-444.html?lang=en
Table 1. Document modification history
Document
version
Publication
date
SC23-6031-01
March 28, 2008 First IBM publication.
SC23-6031-02
October 31,
2010
Comments
Patch number updated in Summary on page 1.

The description of the device was updated in IBM Tivoli
Netcool/OMNIbus Probe for Huawei M2000 (CORBA),
on page 1.
The Internationalization support section was updated.
Section added to describe how to configure two probes to
run simultaneously, allowing the secondary one to start
sending events to the ObjectServer if the primary one
fails. See Peer-to-peer failover functionality on page 8.
Section added to describe how to run the probe. See
Running the probe on page 24.
SC23-6031-03
March 31, 2011
Installation section replaced by Installing probes on

page 2.
Firewall considerations on page 3 added.
Table 1. Document modification history (continued)

Document
version
Publication
date
Comments
SC23-6031-04
December 02,
2011
Information about operating system conventions added in

Conventions used in this guide on page vii.
Requirements updated in Summary on page 1.
Lookup table information added in Lookup table on
page 6.
FTP information updated in Connecting to the CORBA
interface on page 4.
The FtpUsername property was removed.
The following new properties were added in Properties
and command line options on page 9:
v ORBCharEncoding
v ORBLocalHost
v ORBWCharDefault
SC23-6031-05
April 06, 2012
Password encryption information updated in Encrypting

passwords on page 9.
The following new properties were added in Properties
and 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 is
explained in Parsing the AdditionalText element on
page 18.
A known issue with the userid_comment_alarm CLI
command was added in Known issues on page 24.
SC23-6031-06
vi
August 22,
2014
Supported device version and probe target information

updated in Summary on page 1.
Conventions used in this guide

All probe guides use standard conventions for operating system-dependent
environment variables and directory paths.
Operating system-dependent variables and paths

All probe guides use standard conventions for specifying environment variables
and describing directory paths, depending on what operating systems the probe is
supported on.
For probes supported on UNIX and Linux operating systems, probe guides use the
standard UNIX conventions such as $variable for environment variables and
forward slashes (/) in directory paths. For example:
$OMNIHOME/probes
For probes supported only on Windows operating systems, probe guides use the
standard Windows conventions such as %variable% for environment variables and
backward slashes (\) in directory paths. For example:
%OMNIHOME%\probes
For probes supported on UNIX, Linux, and Windows operating systems, probe
guides use the standard UNIX conventions for specifying environment variables
and describing directory paths. When using the Windows command line with
these probes, replace the UNIX conventions used in the guide with Windows
conventions. If you are using the bash shell on a Windows system, you can use the
UNIX conventions.
Note: The names of environment variables are not always the same in Windows
and UNIX environments. For example, %TEMP% in Windows environments is
equivalent to $TMPDIR in UNIX and Linux environments. Where such variables are
described 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 arch
directory under NCHOME or OMNIHOME, arch is a variable that represents your
operating system directory. For example:
$OMNIHOME/probes/arch
The following table lists the directory names used for each operating system
currently supported by Netcool/OMNIbus.
Table 2. Directory names for the arch variable
Directory name represented by arch
Operating system
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

Solaris systems
linux2s390
solaris2
About this guide
vii
Table 2. Directory names for the arch variable (continued)
viii
Operating system
Directory name represented by arch
Windows systems
win32

(CORBA)
Huawei M2000 provides operators with a centralized, mobile network operation
and maintenance (O&M) platform.
The device is used for the management of mobile network elements such as
WRAN, GBSS, SingleRAN, core network, LTE/EPC, NGN, STP, IMS, and other
transmission equipment at both the network element (NE) layer and the network
layer.
The IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA) collects
events from the Huawei M2000 management system using a 3rd Generation
Partnership Project (3GPP) Common Object Request Broker Architecture (CORBA)
interface.
Note: Huawei M2000 was renamed Huawei U2000 with version V200 R014.
This guide contains the following sections:
v Summary
v Installing probes on page 2
v
v
v
v
v
Firewall considerations on page 3

Data acquisition on page 4
Encrypting passwords on page 9
Properties and command line options on page 9
Elements on page 15
v
v
v
v
Error messages on page 19

ProbeWatch messages on page 22
Running the probe on page 24
Known issues on page 24
Summary
Each probe works in a different way to acquire event data from its source, and
therefore has specific features, default values, and changeable properties. Use this
summary information to learn about this probe.
The following table summarizes the probe.
Table 3. Summary
Probe target
Huawei iManager M2000 V200 R012

Huawei iManager M2000 V200 R013
Huawei iManager U2000 V200 R014
Probe executable name
nco_p_huawei_M2000_corba
Probe installation package
omnibus-arch-probe-nco-p-huawei-M2000-corba-version
Package version
4.0
Table 3. Summary (continued)

Probe supported on
For details of supported operating systems, see the

following Release Notice on the IBM Software Support
website:
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
For details of any additional software that this probe

requires, refer to the description.txt file that is
supplied in its download package.
Connection method
CORBA
Remote connectivity
The probe can connect to a remote device using the

CORBA interface.
Multicultural support
Available
For information about configuring multicultural
support, including language options, see the IBM Tivoli
Netcool/OMNIbus Installation and Deployment Guide.
Peer-to-peer failover functionality Available

IP environment
IPv4 and IPv6
Federal Information Processing

Standards (FIPS)
IBM Tivoli Netcool/OMNIbus V7.3.0, 7.3.1 and 7.4.0 use

the FIPS 140-2 approved cryptographic provider: IBM
Crypto for C (ICC) certificate 384 for cryptography. This
certificate is listed on the NIST website at
http://csrc.nist.gov/groups/STM/cmvp/documents/
140-1/1401val2004.htm For details about configuring
Netcool/OMNIbus for FIPS 140-2 mode, see IBM Tivoli
Netcool/OMNIbus Installation and Deployment Guide.
Installing probes
All probes are installed in a similar way. The process involves downloading the
appropriate installation package for your operating system, installing the
appropriate files for the version of Netcool/OMNIbus that you are running, and
configuring 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 system
supported. For details about how to locate and download the installation
package for your operating system, visit the following page on the IBM Tivoli
Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/
probes/all_probes/wip/reference/install_download_intro.html
2. Installing the probe using the installation package.
The installation package contains the appropriate files for all supported
versions of Netcool/OMNIbus. For details about how to install the probe to
run with your version of Netcool/OMNIbus, visit the following page on the
IBM Tivoli Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/
probes/all_probes/wip/reference/install_install_intro.html
3. Configuring the probe.
This guide contains details of the essential configuration required to run this
probe. It combines topics that are common to all probes and topics that are
peculiar to this probe. For details about additional configuration that is
common to all probes, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway
Guide.
Firewall considerations
When using CORBA probes in conjunction with a firewall, the firewall must be
configured so that the probe can connect to the target system.
Most CORBA probes can act as both a server (listening for connections from the
target system) and a client (connecting to the port on the target system to which
the 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 must
determine 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 the
target system will connect.
3. If each host is secured with its own firewall, you must determine the following
four 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 the
ORBLocalPort property. The default value for this property is 0, which means that
an available port is selected at random. If the probe is behind a firewall, the value
of the ORBLocalPort property must be specified as a fixed port number.
CORBA probes that use EventManager or NotificationManager objects may use
different hosts and ports from those that use NamingService and EntryPoint
objects. If the probe is configured to get object references from a NamingService or
EntryPoint object, you must obtain the host and port information from the system
administrator of the target system. When you have this information, you can add
the appropriate firewall rules.
IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000 (CORBA)
Data acquisition
Each probe uses a different method to acquire data. Which method the probe uses
depends on the target system from which it receives data.
The probe gathers events from the Huawei M2000 system using a 3GPP CORBA
interface.
Data acquisition is described in the following topics:
v Connecting to the CORBA interface
v
v
v
v
v
v
v
v
Retrieving objects on page 5

IRP Agent status on page 5
Backoff strategy on page 5
Timeout on page 5
Filtering notifications and alarms on page 6
Lookup table on page 6
Command Line Interface on page 6
Peer-to-peer failover functionality on page 8
Connecting to the CORBA interface

The probe connects to the CORBA interface using Interoperable Object Reference
(IOR) files.
The probe gets the object reference of the AlarmIRPOperation and
NotificationIRPOperation objects from the IOR files specified by the AlarmIrpName
and NotificationIrpName properties. The AlarmIRPOperation and
NotificationIRPOperation 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 the
EntryPointIrpFile property.
If Entry Point IRP authentication is enabled on the IRP Agent, you must use the
Username and Password properties to specify the user name and password required
to log in to the Huawei M2000 system.
Note: If an encrypted password has been configured in the Huawei M2000 EMS
for the RAN Sharing feature, you will have to obtain the encrypted password
string from the EMS vendor, Huawei Technologies.
Using FTP
If the Entry Point IRP file is on a remote system, the probe uses a File Transfer
Protocol (FTP) command to retrieve the file. To acquire the Entry Point IOR file
over FTP, you must specify the following value for the EntryPointIrpFtpCommand
property:
ftp://username:password@EntryPointIorHost/
where username and EntryPointIorHost are the user name and host name of the
Entry Point IRP server. Use the FtpPassword property to specify the password.
Example FTP command:
ftp://trisha:password@server1.hursley.ibm.com
Example of an encrypted FtpPassword property value:
@44:AziJRb8nKabY//lhnhfrg41pCTN5iuCvh96Dcm97jC4=@
For more information about encrypting passwords, see Encrypting passwords on
page 9.
Retrieving objects
When the Resynch property is set to true, the probe initially receives a list of all
active alarms from the AlarmIRP object.
The probe then connects to the NotificationIRP object and uses the CORBA
notification push model to receive new alarms from the server as they are
generated. When the Resynch property is set to false, the probe receives only new
alarms.
IRP Agent status

The probe checks the status of the IRP Agent every 60 seconds.
You can use the Agentheartbeat property to change the frequency with which the
probe checks the status of the IRP Agent.
Backoff strategy
If the Retry property is set to true, and the probe fails to establish a connection or
loses an existing connection to the device, it reverts to a backoff strategy. The probe
tries 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 the
CORBA 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 place
until a successful login occurs.
Timeout
The probe has a timeout facility that allows it to disconnect from the system if
there has been no activity for a predefined amount of time.
You can use the Timeout property to specify how long the probe waits before
disconnecting. The default is 0, which instructs the probe to maintain the
connection indefinitely.
Filtering notifications and alarms

You can use filtering properties to specify how the probe filters events to receive
only preferred notifications and alarms.
The NotificationFilter and AlarmFilter properties allow you to specify what
notifications and alarms are sent to the probe. When you use these properties,
specify the actual token names. For example, the token h represents the element
NV_PERCEIVED_SEVERITY. To specify that the probe is only sent notifications with a
perceived severity of 3, set the NotificationFilter property to $h == 3.
You can specify more complex filters using AND, OR, and NOT operators. For
example, to specify that the probe receives notifications with a perceived severity
of 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 table
The probe is supplied with a lookup table that contains details of the various types
of alarms that the Huawei M2000 generates.
At installation, the Corba_3gpp_V630.lookup file supplied with the probe
installation 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 different
directory, replace .. with the absolute directory path to the lookup file. Do not
use the $OMNIHOME environment variable in this directory path.
Command Line Interface

The probe is supplied with a Command Line Interface (CLI). This interface enables
you to execute commands to acknowledge alarms or request a full
resynchronization of the 3GPP interface.
To use the CLI, you must use the CommandPort property to specify a port through
which commands will be sent. The default port is 6970. When you want to issue
commands, use Telnet to connect through this port. You can use the
CommandPortLimit property to limit the number of Telnet connections that the
probe can make at one time.
The following table describes the commands that you can use with the CLI.
Table 4. CLI commands
Command
Description
exit
Use these commands to close the connection.
quit
Table 4. CLI commands (continued)

Command
Description
help
Use this command to display online help about

the CLI.
resynch_all
Use this command to perform a full

resynchronization with the CORBA interface.
Before you can use this command, you must set
the Resynch property to true.
resynch_filter filter
Use this command to perform partial

resynchronization with the CORBA interface.
The filter parameter uses the same filter format as
the AlarmFilter property. For example:
> resynch_filter $h == 3
Before you can use this command, you must set
the Resynch property to true.
userid_acknowledge_alarm alarm_id
user_id
Use this command to acknowledge an alarm in

the CORBA interface by specifying the alarm ID
(NV_ALARM_ID) and the user ID of the user
acknowledging the alarm.
If you specify a value for the AckUserId property,
the user_id parameter is not required.
userid_unacknowledge_alarm alarm_id
user_id
Use this command to unacknowledge an alarm in

the CORBA interface by specifying the alarm ID
(NV_ALARM_ID) and the user ID of the user
acknowledging 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 by

specifying the alarm ID (NV_ALARM_ID) and the
user ID of the user acknowledging the alarm.
If you specify a value for the ClearUserId
property, the user_id parameter is not required.
userid_comment_alarm alarm_id user_id

comment_text
Use this command to add comments to an alarm

by specifying the alarm ID (NV_ALARM_ID), the
user ID of the user making the comment, and the
text of the comment.
If you specify a value for the CommentUserId
property, the user_id parameter is not required.
Note: There is a known issue with comments
longer than one word being logged as the user ID
in the log file. For details, see Known issues on
page 24.
version
Use this command to display the version of the

probe.
CLI scripts
Because the CLI uses Telnet connections, you can connect to the probe from
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 set up to
allow users to acknowledge selected events from the IBM Tivoli Netcool/OMNIbus
event list.
Peer-to-peer failover functionality

The probe supports failover configurations where two probes run simultaneously.
One probe acts as the master probe, sending events to the ObjectServer; the other
acts as the slave probe on standby. If the master probe fails, the slave probe
activates.
While the slave probe receives heartbeats from the master probe, it does not
forward events to the ObjectServer. If the master shuts down, the slave probe stops
receiving heartbeats from the master and any events it receives thereafter are
forwarded to the ObjectServer on behalf of the master probe. When the master is
running again, the slave continues to receive events, but no longer sends them to
the 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 and
slave 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 a
master probe:
Server
RulesFile
MessageLog
PeerHost
PeerPort
Mode
:
:
:
:
:
:
"NCOMS"
"master_rules_file"
"master_log_file"
"slave_hostname"
5555 # [communication port between master and slave probe]
"master"
The following example shows the peer-to-peer settings from the properties file of
the corresponding slave probe:
Server
RulesFile
MessageLog
PeerHost
PeerPort
Mode
:
:
:
:
:
:
"NCOMS"
"slave_rules_file"
"slave_log_file"
"master_hostname"
5555 # [communication port between master and slave probe]
"slave"
Encrypting passwords
You can encrypt the passwords specified by the Password and FtpPassword
properties using either the nco_g_crypt utility or the nco_aes_crypt utility
supplied with Netcool/OMNIbus.
If you encrypt the passwords using nco_aes_crypt, you must also specify values
for 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 set
the FtpPasswordAESEncrypted property to true.
For more information about encrypting property values, see the IBM Tivoli
Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).
Properties and command line options

You use properties to specify how the probe interacts with the device. You can
override the default values by using the properties file or the command line
options.
The following table describes the properties and command line options specific to
this probe. For more information about generic Netcool/OMNIbus properties and
command line options, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway
Guide.
Table 5. Properties and command line options
Property name
Command line option
Description
AckUserId string
-ackuserid string
Use this property to specify the

user ID to use when
acknowledging and
unacknowledging alarms using the
CLI.
If you do not use the user_id
parameter when acknowledging or
unacknowledging an alarm using
the CLI, the probe will add the user
ID specified by this property to the
related log entry.
The default is " ".
Agentheartbeat integer
-agentheartbeat integer

frequency (in seconds) with which
the probe checks the status of the
IRP Agent.
The default is 60.
Table 5. Properties and command line options (continued)

Property name
Command line option
Description
AlarmFilter string
-alarmfilter string

filter that the Alarm IRP uses to
limit the alarms sent to the probe.
The default is " ".
For more information about
filtering alarms, see Filtering
notifications and alarms on page
6.
AlarmIrpName string
-alarmirpname string

name that the probe uses to resolve
the AlarmIRP point.
The default is AlarmIRP.
ClearUserId string
-clearuserid string

user ID to use when clearing
alarms using the CLI.
parameter when clearing an alarm
using the CLI, the probe will add
the user ID specified by this
property to the related log entry.
The default is " ".
CommandPort integer
-commandport integer

port to which users can connect to
the 3GPP interface using the CLI.
The default is 6970.
For more information about using
the CLI, see Command Line
Interface on page 6.
CommandPortLimit
integer
-commandportlimit integer

maximum number of Telnet
connections that can be made to the
probe.
The default is 10.
10

Property name
Command line option
Description
CommentUserId sring
-commentuserid string

user ID to use when adding
comments to alarms using the CLI.
parameter when commenting on an
alarm using the CLI, the probe will
add the user ID specified by this
property to the related log entry.
The default is " ".
Note: There is a known issue with
comments longer than one word
being logged as the user ID in the
probe log file, regardless of the
value of this property. For details,
see Known issues on page 24.
ConfigCryptoAlg sring
N/A

encryption method used to encrypt
property values in the properties
file. This is intended for use with
the Password and FtpPassword
properties.
The default is AES.
Use this property in conjunction
with the ConfigKeyFile property
and the nco_aes_crypt utility
encrypting passwords, see
Encrypting passwords on page 9.
ConfigKeyFile sring
N/A

location of the key file used to
decrypt property values.
The default is " ".
Use this property in conjunction
with the ConfigCryptoAlg property
and the nco_aes_crypt utility
encrypting passwords, see
Encrypting passwords on page 9.
11

Property name
Command line option
EncodingStandard sring -encodingstandard string
Description
encoding required to encode and
decode characters in events.
Specify a value of UTF8 for this
property to enable the probe to
receive events in languages that use
multibyte characters, such as
Chinese or Japanese.
The default is ISO-8859-1 (also
known as Latin-1).
EntryPointIrpFile
string
-entrypointirpfile string

location of the Entry Point IRP IOR
file.
The default is " ".
EntryPointIrpFtp
Command string
-entrypointirpftpcommand
string

FTP command used to retrieve the
Entry Point IRP IOR file.
The default is " ".
FlushBufferInterval
integer
-flushbufferinterval
integer
Use this property to specify how

often (in seconds) the probe flushes
all alerts in the buffer to the
ObjectServer.
The default is 0 (which instructs the
probe to never flush the alerts to
the ObjectServer).
FtpPassword string
-ftppassword string

password required to access the
Entry Point IRP IOR file over FTP.
The default is " ".
For information about encrypting
the FTP password, see Encrypting
passwords on page 9.
FtpPasswordAES
Encrypted string
-ftppasswordaesencrypted
string
Use this property to specify

whether the value of the
FtpPassword is encrypted using
AES encryption. This property
takes the following values:
true: The value of the FtpPassword
property is encrypted.
false: The value of the FtpPassword
property is not encrypted.
The default is false.
IrpVersion string
-Irpvesion string

version identifier required to get
the IRP outline.
The default is V1.2.0.
12

Property name
Command line option
Description
ManagerIdentifier
string
-manageridentifier string

name used to get all the IRP
references.
The default is " ".
Notification
Categories string
-notificationcategories
string

notification categories to which the
probe subscribes.
To specify multiple categories,
separate them using semicolons, in
the following format:
category1;category2;categoryn
For example:
ALARM IRP V1.0.0; CS IRP V1.0.0
The default is " " (the probe
subscribes to all available
notification categories).
NotificationFilter
string
-notificationfilter string

filter that the notification IRP uses
to limit the notifications sent to the
probe.
The default is " ".
NotificationIrpName
string
-notificationirpname string Use this property to specify the

name used to resolve the
Notification IRP.
The default is NotificationIRP.
ORBCharEncoding string
-orbcharencoding string

native character encoding set used
by the Object Request Broker (ORB)
for character data.
Specify a value of UTF8 for this
property to enable the probe to
receive events in languages that use
multibyte characters, such as
Chinese or Japanese.
The default is ISO-8859-1 (also
known as Latin-1).
ORBLocalHost string
-orblocalhost string

fully qualified domain name
(FQDN) or IP address of the
probe's host machine.
The default is " ".
13

Property name
Command line option
Description
ORBLocalPort integer
-orblocalport integer

local port to which the Object
Request Broker (ORB) listens.
The default is 0 (the ORB selects an
available port at random).
ORBWCharDefault string
-orbwchardefault string
Use this property to specify what

wide character (wchar) set the IBM
ORB uses when communicating
with other ORBs that do not
publish a wchar set.
The default is UTF16.
Password string
-password string

password required to log in to the
Huawei M2000 system.
The default is " ".
Note: If an encrypted password
has been configured in the Huawei
M2000 EMS for the RAN Sharing
feature, you will have to obtain the
encrypted password string from the
EMS vendor, Huawei Technologies.
Resynch string
-resynch (This is equivalent Use this property to specify

whether the probe attempts to
to Resynch with a value of
resynch to the 3GPP server
true.)
following a timeout. This property
-noresynch (This is
equivalent to Resynch with a
false: The probe does not attempt
value of false.)
to resynch to the system.
true: The probe attempts to
resynch to the system.
Retry string
-retry (This is equivalent to Use this property to specify

Retry with a value of true.) whether the probe attempts to
reconnect to the 3GPP interface
-noretry (This is equivalent following a timeout. This property
to Retry with a value of
false.)
false: The probe does not attempt
to reconnect to the system.
true: The probe attempts to
reconnect to the system using a
backoff strategy.
14

Property name
Command line option
Description
Timeout integer
-timeout integer

time (in seconds) that the probe
waits to receive events before
disconnecting from the notification
service and shutting down.
If the Retry property is set to true,
the probe will try to reconnect
using the standard backoff strategy.
The default is 0 (the probe does not
time out).
TimeTick integer
-timetick integer

duration (in minutes) of the
subscription to the target.
The default is -1 (this ensures that
the session remains open
indefinitely).
Note: A value of 15 releases
unused subscriptions and refreshes
the subscription.
Username string
-username string

user name required to log in to the
Huawei M2000 system.
The default is " ".
Elements
The probe breaks event data down into tokens and parses them into elements.
Elements are used to assign values to ObjectServer fields; the field values contain
the event details in a form that the ObjectServer understands.
The following table describes the elements that the probe generates. Not all the
elements described are generated for each event. The elements that the probe
generates depend on the event type.
Table 6. Elements
Element name
Element description
ADDITIONALTEXT_LINECOUNT
This element indicates the number of lines within

the AdditionalText element generated by the
3GPP interface..
CLEAR_SYSTEM_ID
This element indicates whether the system

identifier has been cleared.
CLEAR_USER_ID
This element indicates whether the user identifier

has been cleared.
15
Table 6. Elements (continued)

Element name
Element description
FullAdditionalText
This element contains all values contained in the

AdditionalText element generated by the 3GPP
interface.
This element is generated when one of the
following conditions is met:
v The NV_ADDITIONAL_TEXT element has not yet
been 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 the
parsed data.
FULL_NV_ADDITIONAL_TEXT
This element contains the raw values contained

in the 3GPP interface AdditionalText element.
This element will be generated whenever the
AdditionalText element is detected, and
regardless of whether it contains name-value
pairs or not.
NV_ACK_STATE
This element specifies the acknowledgement state

of the alarm.
NV_ACK_SYSTEM_ID
This element contains the system ID of the IRP

Manager processing the notification.
NV_ACK_TIME
This element specifies the time at which the user

acknowledged the alarm.
NV_ACK_USER_ID
This element identifies the last user who changed

the acknowledgement state.
NV_ADDITIONAL_TEXT
This element contains the raw values contained

in the 3GPP interface AdditionalText element
that are not name-value pairs. The
NV_ADDITIONAL_TEXT element is generated only
when there are undefined sub-elements in the
3GPP interface AdditionalText element.
For example, if the AdditionalText element
contains the string Testing purposes only
(which is not a name-value pair), this string will
be mapped to the NV_ADDITIONAL_TEXT element, as
shown in the probe's log file:
09/01/12 16:05:13: Debug: [Event Processor]
FULL_NV_ADDITIONAL_TEXT: Testing purposes
only
09/01/12 16:05:13: Debug: [Event Processor]
NV_ADDITIONAL_TEXT: Testing purposes only
16
NV_ADDITIONAL_TEXT_LINEnn
This element shows a single line within the

AdditionalText element, where nn is the line
number.
NV_ALARM_CHANGED_TIME
This element contains the date at which the status

of the alarm was changed. The date is displayed
in the format mm/dd/yy.
NV_ALARM_CLEARED_TIME
This element contains the date at which the alarm

was cleared. The date is displayed in the format
mm/dd/yy.

Element name
Element description
NV_ALARM_ID
This element contains the identification

information of the alarm as it appears in the
alarm list.
NV_ALARM_LIST_ALIGNMENT_REQUIREMENT
This element indicates whether the alarm list

requires alignment.
NV_ALARM_RAISED_TIME
This element contains the date at which the alarm

was raised. The date is displayed in the format
mm/dd/yy.
NV_COMMENTS
This element contains comments about the

alarms.
NV_COMMENTS_TIME
This element contains the date at which the

comment was raised. The date is displayed in the
format mm/dd/yy.
NV_COMMENTS_USER_ID
This element contains the name of the user who

raised the comment.
NV_COMMENTS_SYSTEM_ID
This element contains the name of the system

used to raise the comment.
NV_COMMENTS_TEXT
This element contains the comment text.
NV_EVENT_TIME
This element contains the time at which the event

occurred.
NV_MANAGED_OBJECT_CLASS
This element identifies the managed object class

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

instance of the network resource.
NV_MONITORED_ATTRIBUTES
This element contains the managed object

attributes of the network resource.
NV_NOTIFICATION_ID
This element contains the identification

information of the notification.
NV_PERCEIVED_SEVERITY
This element contains the perceived severity of

the alarm.
NV_PROBABLE_CAUSE
This element provides further information about

the probable cause of the alarm.
NV_PROPOSED_REPAIR_ACTIONS
This element specifies the proposed repair actions

associated with the notification.
NV_REASON
This element specifies the reason that triggered

the proposed repair action.
NV_SECURITY_ALARM_DETECTOR
This element identifies the security alarm detector

for the device.
NV_SERVICE_PROVIDER
This element contains the name of the service

provider.
NV_SERVICE_USER
This element contains the name of the user who

uses the service.
NV_SPECIFIC_PROBLEMS
This element provides further information about

the problem to which the notification relates.
NV_STATE_CHANGE_DEFINITION
This element provides information about the state

change.
NV_SYSTEM_DN
This element specifies the distinguished name

(DN) used to identify the system.
17

Element name
Element description
NV_THRESHOLD_INFO
This element provides information about a

threshold that has been crossed.
NV_THRESHOLD_INFO__ATTRIBUTE_ID
This element provides identification information

about a threshold object attribute.
NV_THRESHOLD_OBSERVED_VALUE
This element provides the observed value of the

threshold that has been crossed.
NV_THRESHOLD_HIGH
This element contains the maximum limit of the

threshold value.
NV_THRESHOLD_LOW
This element contains the minimum limit of the

threshold value.
Parsing the AdditionalText element

Version 4.0 of the probe introduced a new element, FULL_NV_ADDITIONAL_TEXT, to
tokenize parts of the 3GPP interface AdditionalText element.
The Huawei M2000 system appends any data that is not in a name-value pair
format to the AdditionalText element. Earlier versions of the probe tokenized this
unformatted data as an element name without a corresponding value, so this data
could not be parsed by the rules file. The new element FULL_NV_ADDITIONAL_TEXT
enables the probe to tokenize the contents of the AdditionalText element.
Example tokenization
This example shows the contents of an AdditionalText element parsed by the
probe 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: Alarm
parameter=0,1,172.18.154.59,10601| appendInfo: | ALARM 63023 Cleared Major CG 59
Software System
Alarm name = No GSN Response
Alarm raised time = 2011-07-25 02:33:49 DST
Location info = igwb1: Alarm parameter=0,1,172.18.154.59,10601
Cleared type = Cleared
Cleared 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: Alarm
parameter=0,1,172.18.154.59,10601| appendInfo: | ALARM 63023 Cleared Major CG 59
Software System
Alarm raised time = 2011-07-25 02:33:49 DST
Cleared time = 2011-07-25 02:34:23 DST
NeType: CG
NeLocation:
vendor:
neName: CG_22
18
alarmName: No GSN Response

alarmLocation: igwb1: Alarm
parameter=0,1,172.18.154.59,10601
appendInfo:
ALARM 63023 Cleared Major CG 59
Software System
Alarm raised time = 2011-07-25 02: 33:49 DST
Cleared time = 2011-07-25 02:34:23 DST
Error messages
Error messages provide information about problems that occur while running the
probe. You can use the information that they contain to resolve such problems.
The following table describes the error messages specific to this probe. For
information about generic Netcool/OMNIbus error messages, see the IBM Tivoli
Netcool/OMNIbus Probe and Gateway Guide.
Table 7. Error Messages
Error message
Description
Action
Failed to ping
notification service
The probe has connection

problems with the
NotificationIRP point.
Check that the 3GPP server is

running correctly. Check the
connection to the 3GPP server.
Failed to get
subscription status
NetcoolIRPManager: Failed The probe has failed to
to acknowledge_alarms
acknowledge the alarms.
Check that the

NV_ALARM_ID specified by
the CLI is correct.
NetcoolIRPManager: Failed The probe has failed to clear

to clear alarms
the alarms.
Check that the

the CLI is correct.
NetcoolIRPManager: Failed The probe has failed to

to unacknowledge_alarms
unacknowledge the alarms.
Check that the

the CLI is correct.
19
Table 7. Error Messages (continued)

Error message
Description
Action
[Command Port] Failed to

get property CommandPort
A problem occurred when the

user attempted to connect to
the command port, or when
the user sent a command.
Check that the value of the

CommandPort property is
correct, and that the
nco_p_nonnative process is
running. Check the
connection between the probe
and the command prompt.
The probe could not retrieve

the value of the
CommandPortLimit property. It
is set to 10 by default,
therefore this does not affect
the behavior of the probe.
Check the value of

CommandPortLimit property.
[Command Port] Thread

shutting down due to
error!
open listening socket,
shutting down Thread!
[Command Port] Error
occured
[Command Port] hostname
Failed to get socket IO
Failed to read command
Failed to close command
socket
get CommandPortLimit
property - using 10
Cannot initialize the Orb There was a problem during

initialization of the ORB.
Ensure that the $CLASSPATH

environment variable contains
the path to the IBM ORB .jar
files.
There are no responses from

the NotificationIRP point.
Check that the Huawei M2000

server is running correctly.
Communication failure lost connection to

NoticiationIRP:
CORBA.TRANSIENT exception
raised. NotificationIRP
is down!
BAD_PARAM Exception i.e
one or more of the in/out
parameter is null
RBA Exception stack trace
to stderr
Failed to Connect
Either, the server is not
running, the IOR is out
of date, or probe cannot
reach remote Server
Cannot proceed. Shutting
down!
20
Table 7. Error Messages (continued)

Error message
Description
Action
Failed to find IOR file
The probe has failed to get

the IOR file.
Check that the

EntryPointIrpFile property is
correctly set in the properties
file.
Failed to narrow Entry

Point IRP interface
Failed to narrow the object

reference to the Entry Point
IrpAgent object.
Check that the

EntryPointIrpFile property is
correctly set in the properties
file.
Failed to perform resynch The probe failed to get the

alarm list, or failed to perform
Failed to iterate through resynchronization of alarms.
resynch alarms
Check that the Huawei M2000

server is running correctly.
Check that the Resynch
property is set correctly.
FtpPassword is incorrect
length (ensure it has
been encrypted using
nco_g_crypt)
There is a problem with the

encrypted password.
Check the value of the

FtpPassword property in the
properties file.
NetcoolIRPManager: ERROR
when parsing a
notification event
A problem occurred while

parsing a received alarm. The
probe may not have parsed
the event completely.
Check that the Huawei

M2000server is running
correctly.
NetcoolIRPManager: Stack
Trace to stderr:
Failed to parse event
completely
NetcoolIRPManager: Failed The probe could not forward
to send event
the Event to the ObjectServer.
OperationNotSupported
Exception

CORBA interface.
NetcoolIRPManager: Failed Failed to get either the

AlarmIRP or the Notification
to retrieve AlarmIRP
IRP object.
object from entry point
interface
Check that the ObjectServer is

running.
Refer to your CORBA
documentation.
Check that the AlarmirpName
and NotificationirpName
properties are correctly set in
the properties file.
NetcoolIRPManager: Failed
to retrieve
NotificationIRP object
from entry point
interface
Problem while trying to
connect to the IRP points
Login: Failed to get IRP
references - invalid
parameter Parameters used
- Subscription ID: sub_id
Subscription Filter
subs_filter Subscription
State: subscription_state
Time Tick: time_tick
21
ProbeWatch messages
During normal operations, the probe generates ProbeWatch messages and sends
them to the ObjectServer. These messages tell the ObjectServer how the probe is
running.
The following table describes the ProbeWatch messages that the probe generates.
For information about generic Netcool/OMNIbus ProbeWatch messages, see the
IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.
Table 8. ProbeWatch messages
ProbeWatch messages
Description
Triggers/causes
Communication failure lost connection to

NoticiationIRP
Communication with the

notification IRP server has
failed.
The probe lost its connection

to the notification IRP server.
END SYNCHRONIZATION
The resynchronization of
alarms has stopped.
The probe has

resynchronized all the
available alarms in the
server.

alarmirp_ior_file
The specified alarm IRP file

does not exist.
The IRP manager has been

set up incorrectly.

notificationirp_ior_file
The specified notification IRP The IRP manager has been

file does not exist.
set up incorrectly.
Failed to get IRP Outline

(GetIRPOutline exception
caught when calling
get_IRP_outline)
The probe could not get the

IRP object.
CORBA.TRANSIENT Exception:
Lost connection to
NotificationIRP
CORBA.OBJECT_NOT_EXIST
Exception: Lost connection
to NotificationIRP
Failed to connect to
NotificationIRP: Shutting
down
Failed to Connect: Either,
the server is not running,
the IOR is out of date, or
probe cannot reach remote
Server
Unexpected fatal error

when getting IRP reference
from Entry Point IRP
Unexpected fatal error
while getting IRP Outline
22

CORBA interface.
Table 8. ProbeWatch messages (continued)

ProbeWatch messages
Description
Triggers/causes
Failed to get IRP

reference (GetIRPReference
exception caught when
calling get_IRP_reference)
The probe could not get the

IRP version.
An incorrect reference is
specified in the IRP file.
Failed to get subscripton

status
The probe lost its connection

to the server.
The 3GPP server is either not

running correctly or the
connection to the 3GPP
server is lost.
Failed to listen for

commands on port number
listening_port
A problem occurred while

trying to listen for
commands.
If this message occurs when

the probe tries to initialize
the connection, then there is
insufficient memory to
complete the operation.
Failed to get IRP

references - invalid
parameter
(InvalidParameter
calling get_IRP_reference)
If this message occurs after

some events had been
parsed, then either there was
a connection failure or the
specified port is already in
use.
The probe failed to login to
the server.
The specified user name and

password are incorrect.
Failed to log in to the

Security IRP - incorrect
username/password

the Security IRP.
The password entered does

not match the user name.
Invalid IRPVersion
(InvalidIRPVersion
calling get_IRP_outline)
The specified IRP version is

incorrect.
An incorrect IRP name is

specified in the properties
file.
NetcoolIRPManager: Failed
to find IOR file ior_file
The specified IOR file does

not exist.
The IRP Manager has been

set up incorrectly.
PermissionDenied
(PermissionDenied
Permission to login to the

server is denied.
The probe does not have the

appropriate permissions set
to login to the server.
probe cannot reach remote

Server

the server.
The 3GPP server is either not

running correctly or the
connection to the 3GPP
server is lost.
Failed to log in to
interface
(InvalidParameter
Unexpected fatal error,
failed to connect
23
Table 8. ProbeWatch messages (continued)

ProbeWatch messages
Description
Triggers/causes
START SYNCHRONIZATION
The resynchronization of
alarms has started.
The probe started to

resynchronize the alarms
collected in the system
during the timeout period.
Will listen for commands

on port number
listening_port
The probe is now listening

for commands on the
specified port number.
The probe has successfully

created the specified
command port in the
properties file.
Running the probe

You run the probe from the command line.
To start the probe, use the following command:
$OMNIHOME/probes/nco_p_huawei_M2000_corba
Known issues
At the time of release, a known issue was reported that you should be aware of
when running the probe.
Alarm comments logged as user ID

The userid_comment_alarm CLI command enables you to add comments to an
alarm by specifying the alarm ID (NV_ALARM_ID), the user ID of the user making the
comment, and the text of the comment. It is also possible to use this command
without specifying the user ID, in which case the user ID specified by the
CommentUserId 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 the
comment that you add contains more than one word, the entire comment string is
logged in the probe's log file in place of the user ID. This happens regardless of the
value specified by the CommentUserId property.
The following example demonstrates how the CLI successfully completes a
userid_comment_alarm command where only the alarm ID and the comment string
are entered:
> userid_comment_alarm 2042480408 testing purposes only
Completed userid_comment_alarm
In this case, the related entry in the probe's log file contains the comment string
testing purposes only in place of the user ID.
24
Appendix. Notices and Trademarks

This appendix contains the following sections:
v Notices
v Trademarks
Notices
This 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 in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
25
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product 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 it
believes appropriate without incurring any obligation to you.
Licensees of this program who want to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
U.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 material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
26
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work, must
include 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 rights
reserved.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, ibm.com, AIX, Tivoli, zSeries, and Netcool are trademarks of
International Business Machines Corporation in the United States, other countries,
or both.
Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-based
trademarks are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States, other countries, or both.
Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation
in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in
the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Appendix. Notices and Trademarks
27
28

Printed in USA
SC23-6031-06

Hum2co PDF

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hum2co PDF

Uploaded by

Copyright:

Available Formats

IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000

IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000

IBM Tivoli Netcool/OMNIbus Probe for

Copyright IBM Corp. 2008, 2014

Appendix. Notices and Trademarks . . 25

About this guide

Document control page

March 28, 2008 First IBM publication.

Patch number updated in Summary on page 1.

March 31, 2011

Installation section replaced by Installing probes on

Copyright IBM Corp. 2008, 2014

Table 1. Document modification history (continued)

Information about operating system conventions added in

April 06, 2012

Password encryption information updated in Encrypting

Supported device version and probe target information

Conventions used in this guide

Operating system-dependent variables and paths

Operating system-specific directory names

HP-UX PA-RISC-based systems

HP-UX Integrity-based systems

Red Hat Linux and SUSE systems

Linux for System z

Table 2. Directory names for the arch variable (continued)

Directory name represented by arch

IBM Tivoli Netcool/OMNIbus Probe for Huawei M2000

Firewall considerations on page 3

Error messages on page 19

Huawei iManager M2000 V200 R012

Probe executable name

Probe installation package

Copyright IBM Corp. 2008, 2014

Table 3. Summary (continued)

For details of supported operating systems, see the

For details of any additional software that this probe

The probe can connect to a remote device using the

Peer-to-peer failover functionality Available

IPv4 and IPv6

Federal Information Processing

IBM Tivoli Netcool/OMNIbus V7.3.0, 7.3.1 and 7.4.0 use

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

Retrieving objects on page 5

Connecting to the CORBA interface

IRP Agent status

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

Filtering notifications and alarms

Command Line Interface

Use these commands to close the connection.

Table 4. CLI commands (continued)

Use this command to display online help about

Use this command to perform a full

Use this command to perform partial

Use this command to acknowledge an alarm in

Use this command to unacknowledge an alarm in

userid_clear_alarm alarm_id user_id

Use this command to clear an alarm by

userid_comment_alarm alarm_id user_id

Use this command to add comments to an alarm

Use this command to display the version of the

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

Peer-to-peer failover functionality

Example property file settings for peer-to-peer failover

Properties and command line options