Before using this information and the product it supports, read the information in Appendix A. "Notices" on page 25.
This edition applies to 1.0.3744 of Netcool/OMNIbus Probe for Nortel CNM (SC23-6398-02) and to all subsequent releases
and modifications until otherwise indicated in new editions.
Netcool/OMNIbus Probe for Nortel CNM Reference Guideiv
docscontrol.fm December 22, 2007
Document control page
The Netcool/OMNIbus Probe for Nortel CNM documentation is provided in softcopy
format only. To obtain the most recent version, visit the IBM Tivoli Netcool Information
Center:
Netcool/OMNIbus Probe for Nortel CNM Reference Guidevi
Nortel CNM.fm December 22, 2007
Probe for Nortel CNM
Nortel CNM (CDMA Network manager) is a networking and service management system
that provides a real-time view of the service provisioning, order managment, fault and
performance management for an enterprise customer’s network. This system supports
multiple wireless network technologies, and customer management interfaces for the
creation, delivery, and playback of multimedia over GSM and CDMA2000 wireless
networks.
The Probe for Nortel CNM collects alarms from Nortel CNM system using a 3GPP2 CORBA
(Common Object Request Broker Architecture) interface for CDMA2000 networks.
This guide contains the following sections:
•Summary
•Supported platforms
•Basic configuration
•Data acquisition
•Peer-to-Peer failover functionality
•Internationalization support
•Properties and command line options
•Elements
•Error messages
•ProbeWatch messages
Probe for Nortel CNM1
Summary
Table 2 provides a summary of the Probe for Nortel CNM.
RequirementsA currently supported version of Tivoli Netcool/OMNIbus.
JDK 1.5
probe-compatibility-3.x (for Tivoli Netcool/
OMNIbus 3.6)
probe-nonnative-base
probe-nonnative-java
nco_p_commandport-0
probe-visibroker-support
Note: The Visibroker patch is not available on the support
site; to obtain this patch, you must contact IBM
Technical Support.
Connection methodCORBA
Remote connectivityYes
LicensingElectronic licensing is no longer implemented in Tivoli
Netcool/OMNIbus products. All Tivoli products now use
the IBM Tivoli software licensing process.
InternationalizationAvailable
Peer-to-peer failover functionalityAvailable
IP environmentIPv4 and IPv6
Note: The probe only supports the IPv6 environment on
Tivoli Netcool/OMNIbus v7.x running on Solaris.
Netcool/OMNIbus Probe for Nortel CNM Reference Guide2
Supported platforms
For details of the versions of HP-UX and Solaris on which this probe is supported, see the
following page on the IBM Tivoli Netcool Information Center:
This section describes the basic configuration requirements for the Probe for Nortel CNM.
Installation requirements
Before running the probe, you must install the JDK 1.5 runtime libraries and the following
IBM Tivoli Netcool/OMNIbus patches in the following order:
1.probe-compatibility-3.x
2.probe-nonnative-base
3.probe-nonnative-java
4.nco_p_commandport-0
5.probe-visibroker-support
Note: These patches (except the VisiBroker patch) are available from the IBM Support
Site. To obtain the VisiBroker patch, you must contact IBM Support.
Updating the rules file
The Probe for Nortel CNM is supplied with a lookup table (Corba_3gpp2_
R6C1.lookup). This file is installed in the following location:
$OMNIHOME/probes/includes/
This file is referenced in the rules file by the following command:
include "/opt/netcool/probes/includes/Corba_3gpp2_R6C1.lookup"
If the Tivoli Netcool/OMNIbus installation directory is different from /opt/netcool/,
you must update the rules file include statement accordingly.
Note: $OMNIHOME cannot be used in the paths to the lookup files; you must enter the full
path to the Tivoli Netcool/OMNIbus installation directory.
Probe for Nortel CNM3
Data acquisition
The Probe for Nortel CNM gathers events from the Nortel CNM 3GPP servers using a
Common Object Request Broker Architecture (CORBA) interface. CORBA is an Object
Management Group specification that provides a standard interface definition between
objects in a distributed environment; that is, it allows applications to communicate with one
another regardless of where they are located or who has designed them.
Connecting to the CORBA interface
The Probe for Nortel CNM acts as an Integration Reference Point (IRP) Manager. The
AlarmIRPOperation and NotificationIRPOperation points form a part of the IRP agent to
which the probe connects through a CORBA interface.
The probe uses the Using Interoperable Object Reference (IOR) files for this connection:
Using IOR files
To connect to the CORBA interface, the probe uses the SecurityIRPAgent Interoperable
Object Reference (IOR) file. If the IOR file is on a remote machine, specify the FTP command
that the probe must use to access it using the SecurityIrpFtpCommand property. If the
IOR file is on a local machine, specify its location using the NortelSecurityIrpFile
property.
Connecting to a remote system
The probe uses secure mode to connect to the remote machine where the IOR file is
available.
To access the IOR file on the remote machine, perform the following steps:
1.Set up the required OpenSSL environment in both the probe server and target system.
2.Create your own PKI key. Remember the password that you specify while creating the
PKI key.
3.Change the access permissions of the PKI key for the SSH to access.
4.Edit the download_ior.sh script so that the IOR_FILE_NAME script variable points
to the same value as the NortelSecurityIrpFile property.
5.Replace the <remote machine name>:<remote path to nortel ior file>
text in the download_ior.sh script with the location and name of the remote
machine.
6.Replace the <password> text in the add-passwd script with the password you
specified while creating the PKI key.
7.Run the probe.
Netcool/OMNIbus Probe for Nortel CNM Reference Guide4
The FTP command is run in the user’s home directory. For FTP users other than root, you
must change the default path specified by the NortelSecurityIrpFile property to
enable the probe to locate the security IRP file; for example, if the FTP user is norteluser,
the home directory for this user will be /home/norteluser. In this case, you must change
the default path specified by the NortelSecurityIrpFile property to:
The probe checks the status of the IRP agent every 60 seconds. You can change this
frequency if required using the Agentheartbeat property.
Retrieving objects
If the Resynch property is set to true, the probe initially receives a list of all active alarms
from the AlarmIRP server. The probe then connects to the NotificationIRP server and uses
the CORBA notification push model to receive new alarms from the server as they are
generated. If the Resynch property is set to false, the probe only receives new alarms.
The probe initially receives a list of all active alarms from the AlarmIRP server. The probe
then connects to the NotificationIRP server and uses the CORBA notification push model
to receive new alarms from the server as they are generated.
Running multiple probes
You can run multiple instances of the Probe for Nortel CNM. For each instance running,
you must specify a different port to which the server listens using the ORBLocalport
property.
Shutting down the probe
To stop an instance of the probe, you must issue a stop signal to the process associated with
that probe instance.
Timeout
The Probe for Nortel CNM has a timeout facility that al lows it to di sconne ct from the sys tem
if there is no activity for a predefined amount of time. You can specify how long the probe
waits before disconnecting using the Timeout property.
Probe for Nortel CNM5
Loading...
+ 23 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.