IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent 5620 ...€¦ · Establishing a secure connection between the ... For probes supported only on Windows operating systems, ... HP-UX

IBM® Tivoli® Netcool/OMNIbus Probe for Alcatel-Lucent5620 SAM JMSVersion 3.0

Reference GuideJune 12, 2014

SC22-5460-03

��

IBM® Tivoli® Netcool/OMNIbus Probe for Alcatel-Lucent5620 SAM JMSVersion 3.0

Reference GuideJune 12, 2014

SC22-5460-03

��

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

Edition notice

This edition (SC22-5460-03) applies to version 3.0 Tivoli Netcool/OMNIbus Probe for Alcatel 5620 SAM v10 and toall subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC22-5460-02.

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

Contents

About this guide . . . . . . . . . . . vDocument Control Page . . . . . . . . . . vConventions used in this guide . . . . . . . . v

IBM Tivoli Netcool/OMNIbus Probe forAlcatel-Lucent 5620 SAM v10 JMS . . . 1Summary . . . . . . . . . . . . . . . 1Installing probes . . . . . . . . . . . . . 2Configuring the probe . . . . . . . . . . . 3

Obtaining the probe-nonnative patch . . . . . 3Configuring Java . . . . . . . . . . . . 3Migrating from a previous version of the SAMprobe . . . . . . . . . . . . . . . . 4Jar files . . . . . . . . . . . . . . . 5Configuring lookup tables . . . . . . . . . 6Configuring advanced correlation . . . . . . 7Establishing a secure connection between theprobe and Alcatel-Lucent SAM-O . . . . . . 10Configuring SSL connections . . . . . . . 10Displaying unicode and non-unicode characters 12

Running the probe . . . . . . . . . . . . 13Data acquisition . . . . . . . . . . . . . 13

Connectivity and firewall considerations. . . . 14Resynchronization . . . . . . . . . . . 14Using durable subscriptions . . . . . . . . 15Subscribing to JMS topics. . . . . . . . . 15Subscribing to the 5620-SAM-topic-xml-filteredtopic. . . . . . . . . . . . . . . . 16Filtering events . . . . . . . . . . . . 17

JMS acknowlegement modes . . . . . . . 18Peer-to-peer failover functionality . . . . . . 19Command line interface . . . . . . . . . 20

Properties and command line options . . . . . 21Properties and command line options provided bythe probe framework version 3.0 . . . . . . . 26Elements . . . . . . . . . . . . . . . 28

Common elements . . . . . . . . . . . 28Alarm event elements . . . . . . . . . . 29Attribute value change event elements . . . . 30State change event elements . . . . . . . . 31Alarm status change event elements . . . . . 31Object deletion event elements . . . . . . . 32Relationship change event elements . . . . . 32Elements generated for object creation events . . 32Client session event elements . . . . . . . 35File available event elements . . . . . . . 36Database activity event elements . . . . . . 36Database connection state change event elements 36Database error event elements . . . . . . . 37Database proxy state change event elements . . 37

Error messages . . . . . . . . . . . . . 37ProbeWatch messages . . . . . . . . . . . 38Troubleshooting . . . . . . . . . . . . . 39

Appendix. Notices and Trademarks . . 41Notices . . . . . . . . . . . . . . . . 41Trademarks . . . . . . . . . . . . . . 43

© Copyright IBM Corp. 2012, 2014 iii

iv IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent 5620 SAM JMS: 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 Alcatel-Lucent 5620 SAM v10documentation is provided in softcopy format only. To obtain the most recentversion, visit the IBM® Tivoli® Netcool® Knowledge Center:

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/common/kc_welcome-444.html?lang=en

Table 1. Document modification history

Documentversion

Publicationdate

Comments

SC22-5460-00 July 6, 2012 First IBM publication.

SC22-5460-01 September 30,2012

Information clarified about which versions ofAlcatel-Lucent 5620 SAM are supported by the probe.

SC22-5460-02 July 5, 2013 Support added for Alcatel-Lucent 5620 SAM v11.

The following topics were added: “Displaying unicodeand non-unicode characters” on page 12 and“Configuring advanced correlation” on page 7.

The following topic were updated: “Jar files” on page 5,“Configuring lookup tables” on page 6, and “ConfiguringSSL connections” on page 10.

SC22-5460-03 June 12, 2014 Support added for Alcatel-Lucent 5620 SAM v12.

“Establishing a secure connection between the probe andAlcatel-Lucent SAM-O” on page 10 added.

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

Operating system-dependent variables and paths

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

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

$OMNIHOME/probes

© Copyright IBM Corp. 2012, 2014 v



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

vi IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent 5620 SAM JMS: Reference Guide

IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent 5620SAM v10 JMS

The Alcatel-Lucent 5620 Service Aware Manager (SAM) is a network managementsystem that is used to manage network nodes. Distributed Alcatel-Lucent 5620SAM elements are monitored by the Alcatel-Lucent 5620 SAM database using GUIand network management components through a Java-based application. TheProbe for Alcatel-Lucent 5620 SAM v10 acquires data from Alcatel-Lucent 5620SAM using a Java™ Messaging System (JMS).

The Probe for Alcatel-Lucent 5620 SAM v10 supports all revisions of SAM V9.0,V10.0, V11.0, and V12.0.

This guide contains the following sections:v “Summary”v “Installing probes” on page 2v “Configuring the probe” on page 3v “Data acquisition” on page 13v “Properties and command line options” on page 21v “Elements” on page 28v “Error messages” on page 37v “ProbeWatch messages” on page 38v “Troubleshooting” on page 39

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

The following table provides a summary of the Probe for Alcatel-Lucent 5620 SAMv10.

Table 3. Summary

Probe target All revisions of Alcatel-Lucent 5620 Service AwareManager (SAM) V9.0, V10.0, V11.0, and V12.0.

Probe executable names nco_p_alcatel_5620_sam_v10

nco_p_alcatel_5620_sam_v10.bat (for Alcatel-Lucent5620 SAM on Windows OS)

Probe installation packages omnibus-arch-probe-nco-p-alcatel-5620-sam-v10-3_0

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

http://www-01.ibm.com/support/docview.wss?uid=swg21641822

Properties files $OMNIHOME/probes/arch/alcatel_5620_sam_v10.props

Rules files $OMNIHOME/probes/arch/alcatel_5620_sam_v10.rules

© Copyright IBM Corp. 2012, 2014 1



Table 3. Summary (continued)

Requirements For details of any additional software that this proberequires, refer to the description.txt file that issupplied in its download package.

Connection method Java Messaging System (JMS) and HTTP(s) Port(optional)

Remote connectivity The Probe for Alcatel-Lucent 5620 SAM v10 can connectto a remote device. Details of the remote device arespecified using the Host, EJBPort, and HTTPPortproperties in the properties file.

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 or IPv6

Note: The probe is supported on IPv6 when running onIBM Tivoli Netcool/OMNIbus V7.3.0, 7.3.1 and 7.4.0.

Federal Information ProcessingStandards (FIPS)

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

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

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

Advantage Online website.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 TivoliKnowledge 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 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 Knowledge Center:http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

3. Configuring the probe.

2 IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent 5620 SAM JMS: Reference Guide

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

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

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html

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

Configuring the probeAfter installing the probe, you need to make various configuration settings to suityour environment.

This section contains topics on the Alcatel-Lucent 5620 SAM configurationrequirements:v “Obtaining the probe-nonnative patch”v “Configuring Java”v “Migrating from a previous version of the SAM probe” on page 4v “Jar files” on page 5v “Configuring lookup tables” on page 6v “Displaying unicode and non-unicode characters” on page 12v “Configuring advanced correlation” on page 7

Obtaining the probe-nonnative patchIf you are running a pre 7.3 version of Netcool/OMNIbus, you must alsodownload the probe-nonnative patch

To obtain the probe-nonnative-base patch:1. Access the Passport Advantage® website:

http://www-306.ibm.com/software/howtobuy/passportadvantage/2. Select Software Downloads.3. Perform a text search on nonnative.4. Select Expand All to see all search results.5. Select the patch that corresponds to your hardware platform.

Configuring JavaThe certification test between IBM and Alcatel-Lucent SAM v10 has been carriedout using Oracle Sun JRE 1.6 patch 32. You should use Oracle Sun JRE 1.6 patch 32or later with this probe. For Alcatel-Lucent SAM v11, you should use Java/JRE 7.

You should configure your JAVA_HOME path to the Oracle Sun JRE path beforerunning the probe, especially if you are running probe-nonnative version 14 andabove.

On on UNIX and Linux operating systems, run the following command:

export JAVA_HOME=/usr/bin/jre6/jre

On Windows operating systems:

set JAVA_HOME=C:\\Java\\Jre6\\jre

Note: Oracle Sun JRE is required due to a limitation on the Alcatel-Lucent clientmodule that the probe uses for SSL connections.

IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent 5620 SAM v10 JMS 3

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

Migrating from a previous version of the SAM probeIf you previously had installed a probe for a previous version of SAM, you willneed to migrate some of the properties.

The following table indicates which properties have been deprecated, whatproperties in the new version of the probe replace those deprecated, and providesmigration instructions for each deprecated property. For details about configuringeach of the properties listed, see “Properties and command line options providedby the probe framework version 3.0” on page 26.

Table 4. Properties deprecated and their replacements

Deprecated property usedby the probe for SAM v9or earlier

Replacement propertyused by the Probe forAclatel-Lucent 5620 SAMv10

Migration instructions

AliveTimeout Inactivity Migrate the AliveTimeoutproperty value to the Inactivityproperty.

ReconnectionAttempts Retry Set the Retry property to specifywhether the probe attempts toreconnect to the target system,instead of specifying how manyreconnection attempts the probemakes using theReconnectionAttempts property.

ReconnectionInterval RetryMaxTime

RetryConstantWait

Set the RetryMaxTime andRetryConstantWait properties todefine how the probe retries aconnection, instead of specifyingthe length of the reconnectioninterval using theReconnectionInterval property.

XMLretrieve Resync Set the Resync property to specifywhether the probe requests activealarms, instead of using theXMLretrieve property.

NbEventsStoreRecovery N/A This property is not supported bythe Probe for Alcatel-Lucent 5620SAM v10.

SizeBlockRead ResyncBatchSize Set the ResyncBatchSize propertyto the maximum number ofalarms retrieved in each batch ofresynchronization alarms, insteadof using the the SizeBlockReadproperty.


Jar filesAs a part of the configuration process, you must copy the samOss.jar file to thejava folder in your Netcool/OMNIbus installation and include its path in your$CLASSPATH environment variable.

The samOss.jar file forms a part of the Alcatel-Lucent server installation and mustbe copied to the following location:

$OMNIHOME/probes/java (on UNIX and Linux operating systems)

%OMNIHOME%\probes\win32 (on Windows operating systems)

You must also include the path to the jar file in the $CLASSPATH environmentvariable.

Note: The xercesImpl.jar file was required by version 1.0 of the Probe forAlcatel-Lucent 5620 SAM v10. It is not required with version 2.0 (or later versions)of the probe.

Configuring the SAMJARHOME environment variable

If you want to use a path other than the default path mentioned in the previoussection for the SAM jar file, you must configure the SAMJARHOME environmentvariable accordingly.

To set the SAMJARHOME environment variable on UNIX or Linux operating systems,run the following command:

export SAMJARHOME=<directory_path>

For example:

export SAMJARHOME=/opt/5620sam/jar

To set the SAMJARHOME environment variable on Windows operating systems, runthe following command:

set SAMJARHOME=<directory_path>

For example:

set SAMJARHOME=C:\\5620sam\\jar

Location of the jar files

If you use default installation, you can find the jar file in the following location ofthe Alcatel SAM server:

/opt/5620sam/server/nms/integration/SAM_O/samOss.jar


Configuring lookup tablesThe probe is supplied with a lookup table that contains details of the various typesof alarms that Alcatel-Lucent 5620 SAM generates. You may need to update therules file to include the path to the lookup table in your installation.

Following lookup file accompanies the Probe for Alcatel-Lucent 5620 SAM v10:

alcatel_5620_sam_v10.lookup

This file is installed in the following location:

$OMNIHOME/probes/includes

The lookup file contains details of the alarm names and probable causes generatedby Alcatel-Lucent 5620 SAM v10.0 and v11.0. The following table shows howalarms defined in the ProbableCause_t table have changed from v10.0 to v11.0.

Table 5. Alarm names in 5620 SAM v10 and v11

Alcatel-Lucent 5620 SAM v10.0 Alcatel-Lucent 5620 SAM v11.0

degradedSignalM3100 degradedSignal

framingErrorM3100 framingError

externalDeviceProblem externalIfDeviceProblem

multiplexerProblemM3100 multiplexerProblem

processorProblemM3100 processorProblem

receiverFailureM3100 receiverFailure

transmitterFailureM3100 transmitterFailure

pumpFailureM3100 pumpFailure

rectifierLowVoltage rectifierLowFVoltage

iceBuild iceBuildUp

storageCapacityProblemM3100 storageCapacityProblem

ABISTOBISInterfaceFailure ABISTOBTSInterfaceFailure

The following table shows how alarms defined in the AlarmType_t table havechanged from v11.0 to v12.0.

Table 6. Alarm names in 5620 SAM v11 and v12

Alcatel-Lucent 5620 SAM v11.0 Alcatel-Lucent 5620 SAM v12.0

DeploymentFailure deploymentFailure

The path to the lookup file is included in the rules file. If you are not running theprobe from $OMNIHOME/probes, you must change this path accordingly.

Note: You cannot use $OMNIHOME in the paths to the lookup files; you must use thefull path in the rules file.


Configuring advanced correlationIn addition to automated deduplication and generic-clear event correlation, thisprobe also supports alarm pre-classification. Pre-classification allows you toidentify and flag within the probe rules file the causal relevance of each event type.This feature enables you to overcome many of the shortcomings of Root CauseAnalysis (RCA) systems by more efficiently and accurately determining the rootcause of a failure from the events processed.

Advanced correlation is implemented by building a lookup table referenced by theprobe rules file to determine the causal relevance of a received event before it isforwarded to the Netcool/OMNIbus ObjectServer.

Details about the causal relevance of each event type are stored in thealcatel_5620_sam-preclass.snmptrap.lookup file. You can modify this file to addto or change the causal relevance details.

The entry for each event type uses the following format:

{ "Event_Id","Causal_relevance" }

For example: {"alcatel-5620-sam-LinkDown","0"},

The causal relevance of each event type is defined using one of the of followingpredefined integer values:

0 – Unknown

1 – Root Cause

2 – Symptom

3 – Singularity

4 – Information

To determine the causal relevance assigned to an entry, use the followingguidelines:

UnknownIf the condition represented by an event cannot be classified as a rootcause, symptom, singularity, or informational event, it is Unknown.

Root CauseA condition that is known not to be caused by any other detectablecondition.

SymptomA condition that is known to always be caused by another detectablecondition. Generally these are events that indicate degraded conditions orfailures of higher level entities or processes.

SingularityIf an event represents a degraded condition or failure that is known to notbe able to be a root cause, and cannot be caused by another condition, it isa singularity.

InformationIf an event provides information about a system that does not represent a


degraded condition or failure, or it indicates the clearing, or resolution, ofpreviously occurring fault related condition, it is an informational event.

To use the alarm pre-classification feature provided with this probe, you mustperform the tasks described in the following topics:v “Configuring the ObjectServer to support intra-device correlations”v “Manually adding conversions to the ObjectServer” on page 9

Configuring the ObjectServer to support intra-device correlations

You must perform this task as an IBM Tivoli Netcool/OMNIbus V7.x user withISQLWrite permissions.

From a command prompt, run the extracted advcorr.sql script using one of thefollowing platform-dependent, case-sensitive commands.

UNIX and Linux operating systems

On UNIX and Linux operating systems, run the following command:

$OMNIHOME/bin/nco_sql -server objectserver_name -user username -passwordpassword < path_to_file/advcorr.sql

where:

$OMNIHOME is your installation location of Tivoli Netcool/OMNIbus V7.x

objectserver_name is the name assigned to your ObjectServer

username and password are your ObjectServer login details

path_to_file is the path to the advcorr.sql file

Windows operating systems

On Windows operating systems, run the following command:

%NCHOME%\bin\redist\isql.exe -S objectserver_name -U username -P password-i path_to_file\advcorr.sql

where:

%NCHOME% is your installation location of IBM Tivoli Netcool/OMNIbus V7.x

objectserver_name is the name assigned to your ObjectServer

username and password are your ObjectServer login details

path_to_file is the path to the advcorr.sql file

Messages generated

As part of the configuration, the script attempts to drop intra-device correlationtables (and associated triggers) which might have been created during a previousinstallation. As this is a first-time installation, no such tables or triggers exist, and


an error listing is generated on completion. These messages are harmless and canbe ignored. Sample output is shown below:ERROR=Object not found on line 102 of statement'--#############################################################################...', at or near 'AdvCorr_SetCauseType'ERROR=Object not found on line 1 of statement 'drop triggerAdvCorr_LPC_RC;...',at or near 'AdvCorr_LPC_RC'ERROR=Object not found on line 1 of statement 'drop triggerAdvCorr_LPC_Sym;...', at or near 'AdvCorr_LPC_Sym'ERROR=Object not found on line 4 of statement '-- Drop tables in case theyalready exist from a previous installation...', at or near'AdvCorrLpcSymCand'ERROR=Object not found on line 1 of statement 'drop tablealerts.AdvCorrLpcRcCand;...', at or near 'AdvCorrLpcRcCand'(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)

(0 rows affected)(0 rows affected)(0 rows affected)(0 rows affected)

Objects created in the ObjectServer

The advcorr.sql script creates the following objects in the ObjectServer to aid indetermining the causal relevance of events:v Intra-device correlation (AdvCorr) tables within the alerts databasev Supplementary automations implemented as an AdvCorr trigger group and

three related triggersv Additional columns in the alerts.status table

Manually adding conversions to the ObjectServer

Conversions are required to support the two columns (AdvCorrCauseType andCauseType) that were added to the alerts.status table as a result of theObjectServer configuration (see “Configuring the ObjectServer to supportintra-device correlations” on page 8). These conversions translate Type integervalues (0 - 4) into descriptive causal relevance text for display within the event list.

Note: These conversions are automatically created from Netcool/OMNIbusKnowledge Library version 3.8 onwards.

To add the required conversions, use the following steps:1. From the Tivoli Netcool/OMNIbus Administrator window, click the Visual

dropdown list, and then click the Conversions icon.2. Right click alert.status and click Add Conversion to access the Conversion

Details window.


3. Select AdvCorrCauseType from the Column dropdown list, and then create thefollowing entries within the Value and Conversion fields, clicking OK to saveeach set of entries:

Table 7. Value and conversion mapping

Value Conversion

0 Unknown

1 Root cause

2 Symptom

3 Singularity

4 Information

4. Repeat steps 2 and 3 to set up the same conversions for the CauseType column,substituting CauseType as the Column field entry in step 3.On completion, the Conversions window appears.

5. Enable the pre-class rules by uncommenting the following lines found in thealcatel_5620_sam_v10.rules file:include "../includes/alcatel_5620_sam-preclass.include.snmptrap.rules"include "../includes/AdvCorr36.include.compat.rules"

Note: Without the configuration described in this topic, the probe will only use thedefault rules file configuration and will ignore the alarm pre-classificationprocessing.

Establishing a secure connection between the probe andAlcatel-Lucent SAM-O

To establish a secure communication between the probe and the Alcatel-LucentSAM-O interface, you should use an SSL connection with HTTPS. Such aconnection significantly reduces the vulnerabilities of hijacked sessions andpasswords.

Configuring SSL connectionsIf the Alcatel-Lucent 5620 SAM server is using a Secure Socket Layer (SSL)connection to encrypt data exchanged over JMS and HTTP, you will need toconfigure the truststore for the HTTPS connection on the Netcool/OMNIbus probeserver.

Importing a certificate file into the truststore

To import a certificate file into the truststore, use the following steps:1. Either obtain the Alcatel EMS security certificate from the certificate authority

(CA) or, if you have the appropriate user access, export the Alcatel EMSkeystore into a certificate on the Alcatel EMS server. Refer to the note below fordetails of where to find instructions about obtaining certificate files and how togenerate a keystore file.To export the Alcatel EMS keystore file from the Alcatel EMS server into acertificate, use the following command:

./keytool -export -alias alias_name -keystore keystore_file -storepasspassword -file certificate_file


Where:alias_name is the keystore alias specified during Alcatel EMS keystoregeneration, for example: SAM10.keystore_file is the path to and name of the Alcatel EMS keystore file, forexample: /opt/samserver.keystore .password is the Alcatel EMS keystore password, for example: the password ofsamserver.keystore.certificate_file is the path to and name of the certificate file to be created,for example: /opt/samcert.

2. On the Netcool/OMNIbus probe server, you need to import the Alcatel EMScertificate either into an existing truststore or into a new truststore.To import the Alcatel EMS certificate into an existing truststore, you need topoint an alias to a key entry as the certificate reply. The alias must be the sameas that specified during Alcatel EMS server keystore file generation, forexample:

./keytool -import -trustcacerts -alias alias_name -file certificate_file-keystore truststore_file -storepass password

To import the Alcatel EMS certificate into a new truststore, make sure that thealias that you specify does not already existing in your truststore, for example:

./keytool -import -trustcacerts -alias new_alias_name -filecertificate_file -keystore truststore_file -storepass password

In the preceding examples:alias_name is the keystore alias specified during Alcatel EMS keystoregeneration, for example: SAM10.new_alias_name is the keystore alias of a new keystore, for example: samprobe.certificate_file is the path to and name of the certificate file created earlier,for example: /opt/samcert.truststore_file is the path to and name of the truststore file that will containthe imported certificate, for example: /opt/samserver.truststorepassword is the Alcatel EMS keystore password, for example: the password ofsamserver.truststore.

3. Verify that the certificate has been imported into the keystore using thefollowing command:

./keytool -list -v -keystore truststore_file

Where:truststore_file is the path to and name of the truststore file generated, forexample: /opt/alusam.trustStore.

Note: For more details about configuring SSL security for the 5620 SAM server(including instructions about obtaining certificate files), refer to the Alcatel 5620SAM Installation and Upgrade Guide.

Configuring the probe

To configure the probe to connect to the SAM server using an SSL connection, usethe following steps:


1. Set the probe's UseSSL property to true and configure the probe's HTTPPortproperty to use the default Alcatel EMS HTTPS port, 8443.

2. Specify values for the following probe properties:v TrustStore: Specify the path of the probe's Java keystore that you created in

the steps for importing the certificate, for example: /opt/alusam.trustStore.v TrustStorePassword: Specify the password that you set for the Java keystore.

Example SSL configuration property settings

The following example shows SSL configuration settings from the properties file ofan example Probe for Alcatel-Lucent 5620 SAM v10:Host : "198.162.20.21"HTTPPort : 8443UseSSL : "true"TrustStore : "/opt/alusam.trustStore"TrustStorePassword : "newpassword"

Displaying unicode and non-unicode charactersThe probe can support multibyte characters and so can display both unicode andnon-unicode characters.

Before using the probe to process data that contains multibyte characters, performthe following steps:1. Ensure that the 5620 SAM server is configured to send data to the probe in

UTF-8 format.The probe can only support multibyte characters if the incoming data has beenconfigured in correct UTF-8 format. Consult your 5620 SAM serverdocumentation for details about how to configure the server to send data inUTF-8 format.

2. Check that the probe server has UTF-8 support enabled and that the correctlocale is set; for example, set the locale to Chinese.On Windows operating systems, use the following steps:a. Access the Region and Language section of the Control Panel.b. Select the Formats tab.c. Select Format > Chinese (Simplified, PRC)

d. Select the Administrative tab.e. Select Change system locale

f. Select Current system locale > Chinese (Simplified, PRC)

g. Click OK.h. Click OK.On UNIX and Linux operating systems, set the system locale using the LANGand LC_ALL environment variables:export LANG=zh_CN.utf8export LC_ALL=zh_CN.utf8

3. Restart the ObjectServer.4. Configure the ObjectServer to enable the insertion of UTF-8 encoded data. See

the Netcool/OMNIbus Installation and Deployment Guide.5. If you are running the probe on a Windows operating system, you must use

the -utf8enabled command-line option each time you start the probe.


Note: Netcool/OMNIbus can only receive multibyte characters from the NetworkElement (NE) custom properties using the additionalText field sent in the alarm.The custom text field also supports multibyte characters. However, this is anattribute of the alarm policy, which is not sent in the alarm. UTF-8 encoding isused for all fields in Alcatel-Lucent 5620 SAM server, but multibyte charactersupport only applies to these few selected attributes. This is because the NE doesnot support multibyte characters.

Running the probeTo start the probe on UNIX or Linux operating systems, use the followingcommand: $OMNIHOME/probes/nco_p_alcatel_5620_sam_v10

To start the probe on a Windows operating systems, use the following command:%OMNIHOME%\probes\win32\nco_p_alcatel_5620_sam_v10.bat

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

The Probe for Alcatel-Lucent 5620 SAM v10 acquires current alarms and downtimealarms (if there is a loss of connection) by connecting to the HTTP port on theAlcatel-Lucent 5620 SAM server. The probe can also obtain alarms as they aregenerated by subscribing to the Java Messaging Service (JMS) running on theAlcatel-Lucent 5620 SAM server.

The probe obtains data from Alcatel-Lucent 5620 SAM as follows:1. The probe connects to the machine on which the Alcatel-Lucent 5620 SAM

server is running specified by the Host property.2. If the Resynch property is set to 1, the probe connects to the HTTPPort, logs onto

the SAM server using the values specified for the SAMServerUserName andSAMServerPassword properties, and sends a HTTP request to perform aresynchronization.The SAM server sends all currently active alarms.

3. The probe then connects to the EJBPort and subscribes to the JMS topicspecified by the JmsTopic property to receive new events as they are generated.

Note: You can specify filter criteria that the probe sends with the request usingthe JmsFilter property.The SAM server sends all events that meet the filter criteria to the probe.

4. The probe extracts event information using a SAX parser and sends it to theObjectServer.

5. If the probe received a TerminateClientSession alarm from the SAM server, theprobe ends the JMS session and shuts down.

Data acquisition is described in the following topics:v “Connectivity and firewall considerations” on page 14v “Resynchronization” on page 14v “Using durable subscriptions” on page 15v “Subscribing to JMS topics” on page 15v “Subscribing to the 5620-SAM-topic-xml-filtered topic” on page 16v “Filtering events” on page 17


v “JMS acknowlegement modes” on page 18v “Peer-to-peer failover functionality” on page 19v “Command line interface” on page 20v “Alcatel-Lucent SAM server redundancy” on page 20

Connectivity and firewall considerationsTo connect to the Alcatel-Lucent 5620 SAM server, the probe uses the EJBPort andHTTPPort properties.

The EJBPort property specifies the EJB port to which the probe connects. Thedefault value for this property is 1099. The HTTPPort property specifies the HTTPport to which the probe connects. The default value for this property is 8080.

For connectivity within a firewall, the Alcatel-Lucent 5620 SAM also uses the JMSport. The JMS service details are specified within the Alcatel-Lucent 5620 SAMserver. The JMS service can only be altered from the Alcatel-Lucent 5620 SAMserver configuration. The default value for the JMS port is 8093.

ResynchronizationOn startup, you can instruct the to probe connect to an HTTP port of theAlcatel-Lucent SAM server, and send a SOAP/XML request to resynchronize allactive alarms.

Using the Resynch property, the probe can resynchronize alarms generated whilethe network elements managed by the SAM server are either inService (active) orinMaintenance (in the maintenance stage or inactive). The SAM server generatesinService alarms when the associated network elements are active, and generatesinMaintenance alarms when they are inactive.

To resynchronize only the active network elements and to receive only theinService alarms, set the XMLretrieveUseInService property to 1. If you havespecified a value for the RecoveryFile property, the server only sends alarms thathave been generated since the timestamp indicated in the recovery file.

If you set the ResynchInterval property to a value greater than 1, the probeperiodically resynchronizing with the SAM server.

If you set the Optimize property to 1, the probe optimizes performance by notwriting the resynchronized events received from the HTTP request and the JMSevents to the log file.


Using durable subscriptionsThe probe can make a durable or a non-durable subscription with a JMS topic.

In durable subscription to a topic, an active subscriber specified by the probereceives messages that were published on the topic while the subscriber wasinactive. When the durable subscription is enabled, the JMS stores messagespublished on the specified topic while the subscriber is not active or disconnectedfrom the JMS.

In a non-durable subscription to a topic, the subscriber only receives messages thatare published on that topic while the subscriber is active. The JMS drops othermessages that are sent while the subscriber is inactive.

Enabling durable subscriptions

You can specify the identifier of the subscriber in the PersistentJmsId property,and enable a durable subscription using the Durable property. When the probereconnects with the same subscriber value, the JMS sends the stored events.

In durable subscription mode, if you stop the probe manually using Ctrl - C andthe StoreEvent property is set to 0 the JMS session becomes inactive. However,when the probe is stopped unexpectedly the durable JMS session remains active(or if the StoreEvent property is set to 1). For example, if the probe is stopped dueto a system crash, the JMS session remains active. This helps the probe receivealarms generated when it was inactive.

Note: Make sure that the same JMS ID value specified using the PersistentJmsIDproperty is part of the JmsFilter property value.

Disabling durable subscriptions

To disable the durable subscription mode, set the value for the Durable property tofalse. If the value specified for this property is false, the probe makes anon-durable subscription with the JMS topic and receives active alarms.

Note: The JMS removes the stored messages once the probe receives newmessages, when the stored messages expire, or when the durable subscription isdeleted.

Subscribing to JMS topicsThe probe can subscribe to a JMS topic and receive events in XML format.

The following table describes the topics to which the probe can subscribe using theJmsTopic property.

Table 8. JMS topics

JMS topic Description

5620-SAM-topic-xml-fault Subscribes to fault events in XML format.

5620-SAM-topic-xml-file Subscribes to findToFile events in XML format.

5620-SAM-topic-xml-general Subscribes to general events (such as object creationand deletion) in XML format.

5620-SAM-topic-xml-stats Subscribes to events related to statistics collection.


Table 8. JMS topics (continued)

JMS topic Description

5620-SAM-topic-xml-filtered Subscribes to all events using advanced filtering tolimit the number of JMS messages that are sent.

Subscribing to the 5620-SAM-topic-xml-filtered topicThe Probe for Alcatel 5620 SAM JMS can subscribe to the 5620-SAM-topic-xml-filtered topic. This topic supports the advanced JMS message filter which allowsyou to base event message selection on the content of the event message body.

To subscribe to the 5620-SAM-topic-xml-filtered topic, set the JmsTopic property to5620-SAM-topic-xml-filtered. The probe will receive events of type EventVesseland XMLFilterChange. You can limit the messages that the SAM sever sends to theprobe by specifying an XML filter using the AdvancedFilterConfigFile property.

You can dynamically modify the XML message filter when the probe is running byissuing a registerNotification command from the CLI, or you can specify analternative XML filter by issuing a registerNotificationFile command. Fordetails of these commands, see “Command line interface” on page 20.

The default AdvancedFilterConfigFile contains the following XML code:<filter-Set><filter>

<and><equal class="jmsEvent" name="MTOSI_NTType" value="NT_ALARM" /><not>

<equal class="jmsEvent" name="MTOSI_NTType"value="NT_ATTRIBUTE_VALUE_CHANGE" /></not>

</and></filter></filter-Set><extraTags><tag name="ALA_category" /><tag name="eventName" /><tag name="MTOSI_osTime" /><tag name="MTOSI_objectType" /><tag name="MTOSI_perceivedSeverity" eventName="ObjectCreation" /><tag name="ALA_alarmType" eventName="ObjectCreation" /><tag name="ALA_clientId" /></extraTags>

When the probe subscribes to the 5620-SAM-topic-xml-filtered topic, by default, theevent vessel does not contain the JMS header properties of the individual events.You must use the AdvancedFilterConfigFile property to specify the JMS headerproperties (for example, MTOSI_osTime, eventName, and so on).

For information about how to configure complex filter for advanced filteringpurpose, refer to the Alcatel-Lucent SAM documentation.

Note: The Probe for Alcatel 5620 SAM v10 only supports XML filters that have90,000 characters or fewer. If the XML filter specified by theAdvancedFilterConfigFile property contains more that 90,000 characters, the probewrites the following warning message to the probe log file:

Probe only support AdvancedFilterConfigFile: ...


Filtering eventsYou can specify how the JMS filters the events sent to the probe by using theJmsFilter property. This property allows you to specify a filter that uses the JMSproperties associated with the event.

You can filter events using any of the JMS properties. For example, the followingfilter is based on fault messages with a severity class of Warning:ALA_category in (\’FAULT\’) and MTOSI_perceivedSeverity in (\’Warning\’)

By default, the JMS filters events sent to the probe using the following filter:ALA_category not in (\’STATISTICS\’, \’ACCOUNTING\’)

Note: The JMS filter must contain ALA_clientId in (’persistent_jms_id’, ’’)where persistent_jms_id is the value set for the PersistentJmsId property. If youchange the value of the PersistentJmsId property, you must also change the thisvalue in the JMS filter accordingly.

The following table describes all JMS properties that are available for use in filters.For each property, the table lists the possible values that the property can take.

Table 9. JMS properties

Property Values Description

MTOSI_NTType ALA_OTHER

NT_OBJECTCREATION

NT_OBJECTDELETION

NT_ATTRIBUTE_VALUE_ CHANGE

NT_STATE_CHANGE

NT_ALARM

NT_HEARTBEAT

ALA_ RELATIONSHIPCHANGE

Use this property to specify thetype of notification that you wantthe filter to send to the probe.

MTOSI_osTime Time in milliseconds Use this property to specify thetime when the event was createdon the server. The filter sends thistime of the event creation to theprobe.

MTOSI_objectName Object name Use this property to specify theobject name for the event thatyou want the filter to send to theprobe.

MTOSI_objectType Object type Use this property to specify theobject type for the event that youwant the filter to send to theprobe.


Table 9. JMS properties (continued)

Property Values Description

ALA_category SERVICE

EQUIPMENT

ACCOUNTING

GENERAL

FAULT

STATISTICS

DATABASE

SOFTWARE

Use this property to specify thecategory of the event that youwant the filter to send to theprobe.

ALA_allomorphic Allomorphic class for theobject type

Use this property to specify theallomorphic class for the objecttype that you want the filter tosend to the probe.

ALA_topic JMS topic Use this property to specify theJMS topic for the message thatyou want the filter to send to theprobe.

ALA_clientId Specific client ID Use this property to specify theclient ID that you want the filterto send to the probe.

JMS acknowlegement modesWithin the SAM server, the probe acts as a JMS client and supports either of thetwo acknowledgement modes: DUPS_OK_ACKNOWLEDGE orAUTO_ACKNOWLEDGE. You can set the JMSAcknowledgeMode property to a modein which the probe should run as a JMS client.

If the JMS is running in DUPS_OK_ACKNOWLEDGE mode, the probe allows theJMS provider to send a message more than once to the same destination. Thismode can be chosen when the performance and throughput of the probe decreaseto avoid duplicate messages.

If the JMS is running in AUTO_ACKNOWLEDGE mode, the probe automaticallyacknowledges a received message, and waits for a broker acknowledgement of themessage.


Peer-to-peer failover functionalityThe Probe for Alcatel-Lucent 5620 SAM v10 supports failover configurations wheretwo probes run simultaneously. One probe acts as the master probe, sending eventsto the ObjectServer; the other acts as the slave probe on standby. If the masterprobe fails, the slave probe activates.

While the slave probe receives heartbeats from the master probe, it will notforward events to the ObjectServer. If the master shuts down, the slave probe willstop receiving heartbeats from the master and any events it receives thereafter willbe forwarded to the ObjectServer on behalf of the master probe. When the masteris running again, the slave will continue to receive events, but will no longer sendthem to the ObjectServer.

Note: Peer-to-peer functionality does not work if you specify the same value forthe JmsFilter property for both the master probe and the slave probe files. Youmust create two queues that both use the JMS filter that you want to use, andspecify one queue in the master probe properties file and specify the other queuein the slave probe properties file. You must also specify different values for thePersistentJmsID property on the master and slave properties.

Example property file settings for peer-to-peer failoverThe following settings show the peer-to-peer settings from the properties file of anexample master probe:Server : "NCOMS"RulesFile : "master_rules_file"MessageLog : "master_log_file"PeerHost : "slave_hostname"PeerPort : 5555 # [communication port between master and slave probes]Mode : "master"JmsFilter: ALA_clientId in (’netcool@[email protected]’, ’’) and ALA_category not in(’STATISTICS’, ’ACCOUNTING’)PersistentJmsId : netcool@[email protected]

The following settings show the peer-to-peer settings from the properties file of thecorresponding slave probe:Server : "NCOMS"RulesFile : "slave_rules_file"MessageLog : "slave_log_file"PeerHost : "master_hostname"PeerPort : 5555 # [communication port between master and slave probes]Mode : "slave"JmsFilter: ALA_clientId in (’netcool@[email protected]’, ’’) and ALA_category not in(’STATISTICS’, ’ACCOUNTING’)PersistentJmsId : netcool@[email protected]

Note: The properties files also contain all other properties required to configurethe probe.


Alcatel-Lucent SAM server redundancyTwo Alcatel-Lucent SAM servers can run in a redundancy pair (that is, one runs asthe primary server and the other as a backup server). This affects the way that youconfigure the probe.

If you are using two Alcatel-Lucent SAM servers in a redundancy pair, you willneed to run two instances of the Probe for Alcatel-Lucent 5620 SAM v10. Oneinstance of the probe connects to the primary server and the other to the backupserver. The settings in the properties file for the two probe instances should beidentical except for the host name.

Command line interfaceThe probe is supplied with a Command Line Interface (CLI) that enables you toissue commands to the probe.

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.

Use the CommandPortLimit property to specify how many CLI connections can beopen at the same time.

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

Table 10. CLI commands

Command Description

registerNotification Use this command to register the advanced JMSfilter XML file specified by theAdvancedFilterConfigFile property .

registerNotificationFileXML_config_file_path

Use this command to register an alternative JMSfilter XML file.

resync Use this command to perform aresynchronization using the parameters specifiedby the following properties in the properties file:

v XMLretreiveUseInService

v SAMServerUserName

v SAMServerPassword

exit/quit Use this command to close the connection.

help Use this command to display online help aboutthe CLI.

name Use this command to display the name of theprobe.

shutdown Use this command to shutdown the probe.

version Use this command to print 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 Netcool/OMNIbus Event List.


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

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

Table 11. Properties and command line options

Property name Command lineoption

Description

AdvancedFilterConfigFilestring

-advancedfilterconfigfile string

Use this property to specify the pathof an advanced JMS filter XML file.The SAM server uses this file todetermine which events to send tothe probe when the JmsTopicproperty is set to5620-SAM-topic-xml-filtered. Fordetails about how to dynamicallychanging the advanced JMS filterwhile the probes is running, see“Subscribing to the5620-SAM-topic-xml-filtered topic”on page 16.

On UNIX and Linux operatingsystems, the default is$OMNIHOME/var/registerNotification.txt.

On Windows operating systems, thedefault is %OMNIHOME%\\var\\registerNotification.txt.

CertificateStore string -certificatestorestring

Use this property to specify the pathof the certificate store file.

The default is "".

CertificateStorePasswordstring

-certificatestorepassword string

Use this property to specify thepassword required to access thecertificate store file.

The default is "".

CertificateStoreType string -certificatestoretype string

Use this property to specify thecertificate type obtained from thecertificate store.

The default is JKS.

CommandPort integer -commandport integer Use this property to specify a portthrough which you can sendcommands to the probe using theprobe's CLI.

The default is 6970.


Table 11. Properties and command line options (continued)


Description

CommandPortLimit integer -commandportlimitinteger

Use this property to specify themaximum number of CLIconnections that you can have openat one time.

The default is 10.

Durable string -durable string Use this property to specify that theprobe makes a durable subscriptionto the JMS.

false: JMS subscription is notdurable.

true: JMS subscription is durable.

The default is true.

EJBPort integer -ejbport integer Use this property to specify the EJBport to which the probe connects.


FlushBufferInterval integer -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 deactivate the flush bufferfunctionality).

Host string -host string Use this property to specify the IPaddress of the host machine onwhich the Alcatel-Lucent 5620 SAMserver is running.

The default is localhost.

HTTPPort integer -httpport integer Use this property to specify theHTTP port to which the probeconnects.


JMSAcknowledgeMode string -jmsacknowledge modestring

Use this property to specify theacknowledgement mode in whichthe probe runs. This property takesthe following values:

AUTO_ACKNOWLEDGE: The probe runs inautomatic acknowledgement(AUTO_ACKNOWLEDGE) mode.

DUPS_OK_ACKNOWLEDGE: The proberuns in deduplication allowed(DUPS_OK_ACKNOWLEDGE)mode.

The default is DUPS_OK_ACKNOWLEDGE.




Description

JmsFilter string -jmsfilter string Use this property to specify the filterthe probe uses to limit the eventsreceived from Alcatel-Lucent 5620SAM. For details of the format inwhich to specify this filter, see“Filtering events” on page 17.

The default value is ALA_clientId in('[email protected]', '') andALA_category not in('STATISTICS', 'ACCOUNTING').

JmsTopic string -jmstopic string Use this property to specify the XMLtopic that the probe uses to subscribeto events within the JMS. For detailsabout valid values for this property,see Table 8 on page 15.

The default is 5620-SAM-topic-xml.

Optimize integer -optimize integer Use this property to specify whetherthe probe optimizes performance:

0: The probe does not optimizeperformance.

1: The probe optimizes performanceby writing neither events receivedfrom the HTTP request nor JMSevents to the log file.

The default is 1.

ParseSaxDebug integer -parsesaxdebuginteger

Use this property to specify thewhether the probe outputs extradebug information from the SAXParser.

The default is 0.

Note: Use this option for debugpurposes only.

PersistentJmsId string -persistentjmsidstring

Use this property to specify the ID ofthe JMS subscription.

The default is [email protected].




Description

RecoveryFile string -recoveryfile string Use this property to specify thename of the recovery file in whichthe probe stores the timestamp of thelast keepAlive event read beforedisconnecting from theAlcatel-Lucent 5620 SAM server. Theprobe uses this when reconnecting tothe server.

On UNIX and Linux operatingsystems, the default is$OMNIHOME/var/AlcatelSamRecovery.

On Windows operating systems, thedefault is %OMNIHOME%\\var\\AlcatelSamRecovery.

This recovery file does not exist bydefault. You must create this filemanually when this property isspecified for the first time.Note: You should backup or removethe recovery file when switching to anew machine or upgrading to anewer version of the probe. Failureto do so may result in successiveresynchronizations but with missingevents.

SAMServerPassword string -samserverpasswordstring

Use this property to specify thepassword required with theSAMServerUserName property to log into the JMS.

The default is "".

SAMServerUserName string -samserverusernamestring

Use this property to specify the username with which the probe logs into the JMS.

The default is "".

StoreEvents integer -storeevents integer Use this property to specify whetheror not Alcatel SAM continues tostore events after the probe has beenstopped by a CTRL-C command. Thisproperty takes the following values:

0: Alcatel SAM does not store eventsafter a CTRL-C stop.

1: Alcatel SAM stores events after aCTRL-C stop.

The default is 1.

TrustStore string -truststore string Use this property to specify the filepath of the truststore file.

The default is "".




Description

TrustStorePassword string -truststorepasswordstring

Use this property to specify thepassword required to access thetruststore file containing the trustedcertificates.

The default is "".

UseSSL string -usessl string Use this property to enable SSLauthentication when connecting tothe SAM server. This property takesthe following values:

false: SSL is not used whenconnecting to the SAM server.

true: SSL is used when connecting tothe SAM server.

The default is false.

Note: If UseSSL is set to true, theHTTPPort property must beconfigured to use the Alcatel SAMHTTPS port. The default AlcatelSAM HTTPS port is 8443. You mustalso configure the followingproperties for the Probe forAlcatel-Lucent 5620 SAM v10:

v CertificateStoreType

v CertificateStore

v CertificateStorePassword

v TrustStore

v TrustStorePassword

XMLFile string -xmlfile string Use this property to specify the XMLfile that the probe reads to check theSAX parser.

The default is "".


XMLFileRead integer -xmlread integer Use this property to specify whetherthe probe reads an XML file to checkthe SAX parser. This property takesthe following values:

0: The probe does not read an XMLfile.

1: The probe reads the XML filespecified by the XMLFile property.

The default is 0.





Description

XMLretrieveUseInServiceinteger

-xmlretrieveuseinservice integer

Use this property to specify whetherthe probe receives alarms from thenodes that are in either inService orinMaintenance mode. This propertytakes the following values:

0: The probe receives alarms from allthe nodes.

1: The probe receives alarms onlyfrom the nodes that are in theinService mode.

The default is 0.

Properties and command line options provided by the probeframework version 3.0

All probes can be configured by a combination of generic properties and propertiesspecific to the probe.

The following table describes the properties and command line options that areprovided by the probe framework version 3.0.

Table 12. Properties and command line options

Property name Command line option Description

AgentHeartBeat integer -agentheartbeat integer Use this property to specify thefrequency (in seconds) with whichthe probe checks the status of thehost server.

The default is 60.

CommandPort integer -commandport integer Use this property to specify theprobe port through which userscan Telnet to send commands tothe host server.


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

The default is 10.

Inactivity integer -inactivity integer Use this property to specify thelength of time (in seconds) thatthe probe allows the port to beinactive before disconnecting.

The default is 0 (which instructsthe probe to not disconnect duringperiods of inactivity).




MaxEventQueueSize integer -maxeventqueuesizeinteger

Use this property to specify themaximum number of events thatcan be queued between the nonnative process and theObjectServer.


Note: You can increase thisnumber to increase the eventthroughput when a large numberof events is generated.

Resync string -noresync (This isequivalent to Resync witha value of false.)

-resync (This is equivalentto Resync with a value oftrue.)

Use this property to specifywhether the probe requests allactive alarms from the host serveron startup. This property takes thefollowing values:

false: The probe does not requestresynchronization on startup.

true: The probe requestsresynchronization on startup.

The default is true.

ResyncBatchSize integer -resyncbatchsize integer Use this property to specify themaximum number of alarmsretrieved in each batch ofresynchronization alarms.

The default is 100.

ResyncInterval integer -resyncinterval integer Use this property to specify theinterval (in seconds) at which theprobe makes successiveresynchronization requests.

The default is 0 (which instructsthe probe to not make successiveresynchronization requests).

Retry string -retry string Use this property to specifywhether the probe attempts toreconnect to the target systemfollowing a timeout. This propertytakes the following values:

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

true: The probe attempts toreconnect to the system.

The default is false.




RetryConstantWait integer -retryconstantwaitinteger

Use this property to specify thelength of time (in seconds) thatthe probe waits betweensuccessive connection attempts tothe target system.

The default is 0 (which instructsthe probe to use an exponentiallyincreasing period betweensuccessive connection attempts, forexample, the probe will wait for 1second, then 2 seconds, then 4seconds, and so forth).

RetryMaxTime integer -retrymaxtime integer Use this property to specify themaximum length of time (inseconds) that the probe makesreconnection attempts to the targetsystem. If you set this property to0, the probe makes reconnectionattempts indefinitely.


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.

This section describes the elements that the Probe for Alcatel-Lucent 5620 SAM v10generates. The elements that are generated depend on whether you are runningAlcatel-Lucent 5620 SAM version v9.0, v10.0, v11.0, and v12.0.

Common elementsThe probe generates a common set of elements for each event that it receives.

The following table describes the elements that are generated for all events.

Table 13. Common elements

Element name Element description

$ALA_allomorphic This element contains the allomorphic class of theobject.

$ALA_category This element shows the category of the message, forexample, FAULT.

$ALA_clientId This element contains the client identifier for themessage.

$correlationId This element contains the correlation identifier forthe related messages.

$eventName This element shows the type of event, for example,an attribute value change.

$MTOSI_NTType This element shows the notification type of themessage, for example, NT_ALARM.


Table 13. Common elements (continued)


$MTOSI_objectName This element contains the object full nameassociated with the event.

$MTOSI_objectType This element indicates the object type for themessage, for example, fm.AlarmObject.

$MTOSI_osTime This element shows the time that the message wascreated.

Alarm event elementsThe probe generates a standard set of elements for each alarm event that itreceives.

The following table describes the elements that are generated for alarm eventelements.

Table 14. Alarm event elements


$ALA_alarmType This element indicates the alarm type.

$ALA_OLC This element indicates the OLC state of the objectassociated to the event. A value of zero (0) indicatesno state for the object.

$ALA_application This element shows the tag associated with theapplication.

$ALA_span This element contains the span of control ID list.

$ALA_isCorr This element shows the isCorrelated flag. A valueof true indicates that the alarm is correlated at thecreation time to another alarm.

$MTOSI_aliasNameList This element indicates the alias for the alarm name.

$MTOSI_perceivedSeverity This element indicates the severity of the alarm.

$MTOSI_probableCause This element identifies the probable cause of thealarm.

$MTOSI_serviceAffecting This element contains the identifies whether thealarm is service affecting.


Attribute value change event elementsAn attribute value change alarm indicates changes occurred to a particularproblem alarm that the probe received earlier. Based on the indicated changes, theprobe generates a standard set of elements for each attribute value change eventthat it receives.

The probe performs the following if the attribute value change alarm indicates thatthe severity field is updated with a value other than cleared in Attribute4:v deduplicates the problem alarm.v updates severity of the problem alarm with the latest value.v increments the count of the problem alarm by 1.

The probe performs the following if the attribute value change alarm indicates thatthe severity field is updated with a cleared value in Attribute4:v makes the attribute value change alarm as a new resolution alarm in the event

list. This action is performed as per the Netcool/OMNIbus generic clearstandards.

v clears both the problem alarm and the resolution alarm.

It is possible that the probe may receive another attribute value change alarmbefore the problem alarm get cleared. If this new attribute value change alarmindicates that the severity field is updated with a value other than cleared inAttribute4, then the probe performs the following:v deduplicates the problem alarm.v updates severity of the problem alarm with the latest value.v increments the count of the problem alarm by 1.

It is The probe performs the following if the attribute value change alarm indicatesthat attributes other than the severity field are updated in Attribute4:v deduplicates the problem alarm.v keeps the severity field with its current value.v increments the count of the problem alarm by 1.

The following table describes the elements that are generated for attribute valuechange events.

Table 15. Attribute value change event elements


$avc_n This element shows the attribute changed and itsassociated value.

$objectFullName This element contains the name of the object whoseattributes changed.


State change event elementsThe probe generates a standard set of elements for each state change event that itreceives.

The following table describes the elements that are generated for state changeevent elements.

Table 16. State change event elements


$maxAlarmCount This element shows the maximum alarm count.

$state This element indicates the state that changed.

$sysPrimaryIp This element shows the primary IP address of thesystem.

$sysStandbyIp This element shows the standby IP address of thesystem.

$sysStartTime This element shows the time that the system startedup.

Alarm status change event elementsThe probe generates a standard set of elements for each alarm status change eventthat it receives.

The following table describes the elements that are generated for alarm statuschange event elements.

Table 17. Alarm status change event elements


$Attributen This element contains the attribute changed and itsassociated value.

$objectFullName This element shows the name of the object whosealarm status has changed.

$olcState This element indicates whether the alarm isgenerated when the node is in inService orinMaintenance mode.

$spanObjectPointer This element identifies the span of object pointer.

$correlatingAlarm This element indicates whether the alarm has acorrelating alarm.

$isImplicitlyCleared This element indicates whether the alarm isimplicitly cleared.

$numberOfCorrelatedAlarms This element shows the number of alarms correlatedto the alarm.


Object deletion event elementsThe probe generates a single element for each database proxy state change eventthat it receives.

The following table describes the element that is generated for object deletionevent elements.

Table 18. Object deletion event elements


$objectFullName This element shows the name of the object deleted.

Relationship change event elementsThe probe generates a standard set of elements for each relationship change eventthat it receives.

The following table describes the elements that are generated for relationshipchange event elements.

Table 19. Relation change event elements


$changeType This element shows the type of change.

$fromObjectClass This element contains the class of the original object.

$fromObjectName This element identifies the name of the originalobject.

$objectFullName This element identifies the name of the object with achanged relationship.

$toObjectClass This element contains the class of the new object.

$toObjectName This element shows the name of the new object.

Elements generated for object creation eventsThe probe generates a standard set of elements for each object creation event that itreceives.

The following table describes the elements generated when alarm informationobjects are created.

Table 20. Elements for object creation events


$acknowledgedBy This element contains the name of the operator thatacknowledged the alarm.

$additionalText This element contains the additional descriptiveinformation about the alarm.

$affectedObjectClassIndex This element indicates the identifier of the managedobject class.

$affectedObjectClassName This element contains the name of the managedobject class to which the object with the alarmbelongs.

$affectedObjectDisplayedName This element contains the text version name of thealarm’s affected object.


Table 20. Elements for object creation events (continued)


$affectedObjectFullName This element contains the fully distinguished nameof the object against which the alarm was raised.

$affectedObjectInstanceIndex This element indicates the identifier of the managedobject instance.

$alarmClassTag This element shows the object class against whichthe alarm was raised.

$alarmName This element contains the alarm name.

$alarmType This element shows the vendor-specific and X.733standards for the type of the alarm.

$firstTimeDetected This element shows the date and time the alarmwas first raised.

$highestSeverity This element identifies the highest severity value ofthe alarm since it was generated.

$isAcknowledged This element indicates whether the alarm iscurrently acknowledged by an operator.

$isServiceAffecting This element indicates whether an alarm hasaffected a customer’s service.

$lastTimeAcknowledged This element shows the date and time at which thealarm was acknowledged.

$lastTimeCleared This element shows the date and time at which thealarm was cleared.

$lastTimeDeEscalated This element shows the date and time at which thealarm was de-escalated.

$lastTimeDemoted This element shows the date and time at which thealarm was demoted.

$lastTimeDetected This element shows the date and time the alarmwas most recently observed.

$lastTimeEscalated This element shows the date and time at which thealarm was escalated.

$lastTimePromoted This element shows the date and time at which thealarm was promoted.

$lastTimeSeverityChanged This element shows the date and time at which thealarm was cleared.

$nodeId This element contains the IP address of the routerthat issued the alarm and contains the affectedobject.

$nodeName This element contains the text version name of therouter that issued the alarm and contains theaffected object.

$numberOfOccurrences This element indicates the number of times thealarm has been raised.

$numberOfOccurrencesSinceAck This element indicates the number of times thealarm has been raised since it was acknowledged.

$numberOfOccurrencesSinceClear This element indicates the number of times thealarm has been raised since it was cleared.




$operatorAssignedUrgency This element indicates the urgency setting of thealarm as determined by the user-configured valueset for the alarm. The possible values are:

0: Unspecified

1: Indeterminate

2: Minor

3: Major

4: Critical

$originalSeverity This element shows the severity of the alarm whenit was first raised.

$previousSeverity This element shows the severity value of the alarmprevious to the current value.

$probableCause This element shows the vendor-specific and X.733standards for the probable cause of the alarm.

$relatedObject This element contains the list of fully distinguishednames that point to other objects that are alsoaffected by a particular alarm.

$specificProblem This element indicates the specific problem that thealarm is reporting. It is generated when the nodereports vendor specific information in thespecificProblem field. The probe populates thiselement by referring to thealcatel_5620_sam_v10.lookup table supplied withthe probe. For details about configuring the lookuptable, see “Configuring lookup tables” on page 6.

Note: This element is only available on SAM v12(or later versions).

$severity This element shows the vendor-specific, TMN, andX.733 standards for severity of the alarm. Thepossible values are:

0: Unspecified

1: Cleared

2: Indeterminate

3: Info

4: Condition

5: Warning

6: Minor

7: Major

8: Critical

$urgencyAssignedBy This element contains the name of the operator thatlast modified the urgency of the alarm.




$wasAcknowledged This element indicates whether the alarm has everbeen acknowledged by an operator.

Customizing the rules file to populate the $specificProblemelementThe $specificProblem element is available for SAM v12 and above for certaintypes of alarms, for example NobeB alarms. To populate the $specificProblemelement you need to customize the probe rules file.

The probe rules file contains the following lines that define the specifcProblemelement:#specificProblem is only available starting SAM v12 and above; and applicablefor certain alarm type only (eg: NodeB alarm)

if (exists($specificProblem)){$SpecificProblem_T = lookup($specificProblem, SpecificProblem_t)

## Remove hash below to map specific problem with object server field## @X733SpecificProb = $SpecificProblem_T

}

To make the $specificProblem element available, uncomment the following line byremoving the hash symbols:

@X733SpecificProb = $SpecificProblem_T

This will map $SpecificProblem to the @X733SpecificProb field.

Alternatively, you can create a new field in the ObjectServer using NetcoolAdministrator and map $SpecificProblem_T with a new field (for example@NewField).

@NewField = $SpecificProblem_T

Client session event elementsThe probe generates a single element for each client session event that it receives.

The following table describe the element that is generated for client session eventelements.

Table 21. Client session event elements


$clientId This element shows the identifier of the client in thissession.


File available event elementsThe probe generates a standard set of elements for file available event that itreceives.

The following table describes the elements that are generated for file availableevent elements.

Table 22. File available event elements


$fileName This element contains the name of the file required.

$requestId This element shows the identifier of the request.

Database activity event elementsThe probe generates a single element for each database activity event that itreceives.

The following table describes the element that is generated for database activityevent elements.

Table 23. Database activity event elements


$state This element shows the state associated with thedatabase activity.

Database connection state change event elementsThe probe generates a single element for each database connection state changeevent that it receives.

The following table describes the element that is generated for database connectionstate change event elements.

Table 24. Database connection state change event elements


$state This element indicates the state of the databaseconnection.


Database error event elementsThe probe generates a standard set of elements for each database error event that itreceives.

The following table describes the elements that are generated for database errorevent elements.

Table 25. Database error event elements


$error This element shows the description of the error.

$state This element identifies the database error state.

Database proxy state change event elementsThe probe generates a single element for each database proxy state change eventthat it receives.

The following table describes the element that is generated for database proxy statechange event elements.

Table 26. Database proxy state change event elements


$state This element indicates the state of the databaseproxy.

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 27. Error messages

Error Description Action

Error from parser inreading input xml

There was a problem readinga line of XML from theAlcatel-Lucent 5620 SAMSever.

Check that the server isrunning correctly.

Error in parsing There was a error generatedby the SAX Parser.

Check that the SAX Parser isrunning correctly.

Failed to connect to theObjectManager

The probe cannot find theObjectManager reference inthe naming host.

Check that the ObjectManageris correctly registered with thedefined Naming Service.

Failed to create a URLconnection Object

The probe failed to create oropen an HTTP connection tothe Alcatel-Lucent 5620 SAMService.

Check that the server isrunning. Check the connectionto the host machine on whichthe server is running.

Failed to get properties The probe could not accessthe properties file.

Check the location of andpermissions set for theproperties file.


Table 27. Error messages (continued)

Error Description Action

Failed to make HTTPconnection to host

The probe was unable toconnect to the port specifiedby the HTTPPort property.

Check that you have specifiedthe correct port in theproperties file.

JNDI API lookup failed The probe failed to create atopicConnectionFactoryobject with which to connectto the JMS.

Contact IBM Software Support.

Unsuccessful attempt toto create default tokens

Unsuccessful attempt toset element_name element

The probe failed to create atoken from the alarm. Thisindicates a parsing error.

Contact IBM Software Support.

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

ProbeWatch message Description Triggers/causes

Could not find JNDIcontext topic topic_name

There was an error when theprobe attempted to connect tothe SAM server.

The JMS did not start properlyon the SAM server.

Failed to establish HTTPconnection

The probe has failed toestablish an HTTP connectionto the SAM server.

The probe failed to connect tothe port specified by theHTTPPort.

Going Down The probe is shutting down. The probe is shutting downafter performing the shutdownroutine.

JNDI API lookup failed There was an error when theprobe attempted to connect tothe SAM server.

The JMS did not start properlyon the SAM server.

No keepAlive event fornumber seconds

The probe has not receivedany events from the JMS forthe period specified by theAliveTimeout property.

The probe has stoppedreceiving events from the JMS.

Running ... The probe is runningnormally.

The probe has just been startedup.


TroubleshootingVarious issues arise as users work with the probe. Troubleshooting information isprovided to help you diagnose and resolve such issues.

Probe is missing some events and how to resolve it?

Part of the value set for the JmsFilter property includes the value set for thePersistentJmsId property. So, the probe will not work properly if the JmsFilterproperty is not updated after changing the value of the PersistentJmsId property.When the probe encounters this issue, the following debug message appears in thelogfile:

Debug: SAM: Sleeping until receiving the Sam server’s data?

To resolve this problem, set the JMS filter and the JMS ID to the same IP addressor host name, and not to a combination of local host and IP or host name.

Event count in Event List does not tally with that of the Alcatel5620 SAM v10/v11 events

This is because the deduplication trigger that is available for Netcool/OMNIbusv7.3.0 onwards will not process correctly events whose Identifier value is the sameas the value set for the LastOccurrence fields.

To resolve this issue, remove the following code from the Netcool/OMNIbusdeduplication trigger:if( %user.app_name = ’PROBE’ )thenif( (old.LastOccurrence > new.LastOccurrence) or

((old.ProbeSubSecondId >= new.ProbeSubSecondId) and(old.LastOccurrence = new.LastOccurrence) ) )

thencancel;end if;end if;

For further information about deduplication trigger issues, see the followingTechnote http://www-01.ibm.com/support/docview.wss?uid=swg21469238.




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. 2012, 2014 41

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 43


��

Printed in USA

SC22-5460-03

Documents

IBM Tivoli Netcool/OMNIbus Probe for Alcatel-Lucent 5620 ...€¦ · Establishing a secure connection between the ... For probes supported only on Windows operating systems, ... HP-UX