Tivoli Netcool Supports Guide to Q3 probes by Jim ... - IBM

Tivoli Netcool SupportsGuide to

Q3 probesby

Jim HutchinsDocument release: 2.0

Supports Guide to Q3 probes

Table of Contents1Introduction...................................................................................................................................3

1.1Product Status.............................................................................................................................31.2The Q3 transport layer.................................................................................................................31.3CMIP Transport Layer.................................................................................................................41.4Q3 probes....................................................................................................................................51.5Troubleshooting Q3 probes.........................................................................................................5

2Sun’s Solstice CMIP software.....................................................................................................6

2.1Overview......................................................................................................................................62.2Solstice CMIP Patches................................................................................................................62.3CMIP configuration......................................................................................................................72.3.1CMIP Configuration Tool..........................................................................................................72.3.2cmip.conf file.............................................................................................................................82.3.3manager.cfg file........................................................................................................................92.3.4IP Addresses............................................................................................................................9

3Probe Configuration...................................................................................................................10

3.1<q3>.df.cfg file...........................................................................................................................103.2<q3>.manager.cfg file................................................................................................................113.3Presentation Selector (PSEL)....................................................................................................123.4Properties configuration.............................................................................................................133.5The apTitle and aeQualifier values............................................................................................143.6Q3 Scripts..................................................................................................................................153.6.1Siemens Radio Commander..................................................................................................153.6.2Reading Q3 Scripts................................................................................................................163.6.3Q3 Start-up Script structure....................................................................................................173.6.4Classes...................................................................................................................................18

4Frequently Asked Questions.....................................................................................................19

5Understanding the rk6trace.......................................................................................................20

5.1Radio Commander Issue...........................................................................................................20

6Q3 Element Management Systems...........................................................................................21

6.1Nortel OMC-R............................................................................................................................21

7Command line interface.............................................................................................................22

7.1Securing the ConsolePort..........................................................................................................237.2Command-line authentication....................................................................................................247.2.1q3_crypt..................................................................................................................................247.3Common Development Framework...........................................................................................247.4Alarm Acknowledgement...........................................................................................................257.4.1Alcatel OMC-R Q3 EMS.........................................................................................................25

8CMIP Troubleshooting...............................................................................................................26

8.1CMIP.conf file............................................................................................................................268.2CMIP restart script.....................................................................................................................26

9Example Q3 Scripts....................................................................................................................27

9.1alcatel_omcr1353ra_b10.script.................................................................................................279.2alcatel_omcr1353ra_b62.script.................................................................................................279.3nortel_omcr_v14.script..............................................................................................................289.4siemens_rc_br70v31.script........................................................................................................289.5siemens_rc_br85v50.script........................................................................................................299.6siemens_rc_umr6.script............................................................................................................299.7siemens_sc_scr12.script...........................................................................................................30

IBM Copyright 2014 1

Supports Guide to Q3 probes10Q3 manager versions...............................................................................................................31

10.1Siemens Radio Commander...................................................................................................31



1 Introduction

1.1 Product Status

The Solstice CMIP 9.0 software is no longer supported by Oracle Sun microsystems which prevents customers from installing new instances of the Q3 probes. If a replacement Q3 probe is required, a Request For Enhancement should be raised, and your requirements discussed with your IBM Account team.

This documentation is provided for existing Q3 probe customers.

1.2 The Q3 transport layer

Q3 forms a part of the Open Systems Interconnection (OSI) communications standards.

OSI is a generic model for data communication. It splits the total set of tasks that need to be performed during such a communication into seven layers, where the services that one of the layers offers are built upon the services of the underlying layer.

The communication layers are:• Application (layer 7)• Presentation (layer 6)• Session (layer 5)• Transport (layer 4)• Network (layer 3)• Data Link (layer 2)• Physical (layer 1)

In the case of Q3, the application layer comprises the following service elements:1 Association Control Service Element (ACSE)2 Remote Operations Service Element (ROSE)3 Common Management Information Service Element (CMISE)4 Systems Management Application Service Element (SMASE)

All these service elements are combined into an application context.



1.3 CMIP Transport Layer

The diagram below illustrates the layers the probes messages travels through when communicating with the element management system.

Service elements DescriptionACSE Association Control Service Element for dealing with connection handling

ROSE Remote Operations Service Element for low level remote procedure call services

CMISE Common Management Information Service Element, which contains the actual management functionality

SMASE Systems Management Application Service Element


1

2

3

4

5

6

7

Physical connection

data link

network

Transport (TSEL)

Session (SESS)

Presentation (PRES)

application

Q3 Probe Q3 ems

Q3 probe communicates with Q3 ems

Communication Path used


1.4 Q3 probes

The Q3 Probe was originally shipped as the nco_p_q3 probe, but is now divided into a series of element manager specific Q3 probes;

Element Manager Specific Probes

Binary Element managernco_p_alcatel_smc1360 Alcatel SMC 1360nco_p_alcatel_omcr1353ra_b10 Alcatel OMC-R b10nco_p_alcatel_omcr1353ra_b62 Alcatel OMC-R b62nco_p_siemens_rc_br70v31 Siemens Radio Commander br7.0nco_p_siemens_rc_br85v50 Siemens Radio Commander br8.5nco_p_siemens_rc_umr6 Siemens Radio Commander br9.0nco_p_siemens_sc_scr12 Siemens Switch Commandernco_p_motorola_omcr1620_v65 Motorola OMC-R 1620nco_p_nortel_omcr_v14 Nortel OMC-R v14

1.5 Troubleshooting Q3 probes

When dealing with q3 probes it is important to obtain the complete set of configuration and log files in order to debug the results;

Probe Configuration files

File Description

probe.manager.cfg Manager to agent configuration

probe.cdf.cfg Device rk6 configuration

probe.props Probes properties

probe.rules Probes rules file

probe.script Probes Q3 script file

Probe log files

Source Description

cmiptrace Debug information from the CMIP trace command

rk6trace Debug information from the rk6 trace command (rk6trace pres+)

probe.log Probes debug log file

FB.trace Device rk6 trace

FB.log Device rk6 logs



2 Sun’s Solstice CMIP software

2.1 Overview

The Solstice CMIP software is installed in /opt/SUNWconn and /etc/opt/SUNWconn.

RK6 Driver

Configuration directory /etc/opt/SUNWconn/rk6

Configuration file /etc/opt/SUNWconn/rk6/rk6d.conf

Default port 102

Boot script /etc/rc2.d/S*rk6

Daemon name rk6d

CMIP Stack

Configuration directory /etc/opt/SUNWconn/cmip

Configuration file /etc/opt/SUNWconn/cmip/cmip.conf

Boot script /etc/rc2.d/S*osimcs

Daemon name osimcsd

The latest Sun Solstice patches must be applied to ensure the system works correctly.

Stopping and starting the daemons:-/etc/rc2.d/S*osimcs stop/etc/rc2.d/S*rk6 stop/etc/rc2.d/S*rk6 start/etc/rc2.d/S*osimcs start

2.2 Solstice CMIP Patches

The latest list of patches can be found on the sunsolve.sun.com support site.

Patch-ID# 111619-07Synopsis: Solstice CMIP 9.0 patchBugId's fixed with this patch: 4971626 4967572 5013437 4935138 4961996 4821296 4862880 4855403 4862924 4487289 4828989 4780945 4697430 4711526 4736113 4657526 4636024 4664887 4456925 4487905 1180979 4530214 4479003 4616455 4616459 Changes incorporated in this version: 4971626 4967572 5013437Date: Apr/06/04


http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=111619&rev=07


2.3 CMIP configuration

2.3.1 CMIP Configuration Tool

The /opt/SUNWconn/sbin/cmiptool is used to configure the Solstice CMIP software. The default settings are generally used for single probe installations. Multiple probe installations require greater configuration.

CMIP Configuration Tool

[default settings]

Default XMP Address

Presentation Selector = rfc0 [x] Asc [ ] Hex

[ ] CONS(X.25)

[ ] CLNP (LLC)

[x] TCP/IP (RFC 1006)

Transport = A [x] Asc [ ] Hex

Network = c0a83447 [ ] Asc [x] Hex

Session = Prs [x] Asc [ ] Hex

Loopback [ ] On [x] Off

Timers

Inactivity (x 10s) = 12

Request (x 10s) = 5

Sizes

User Window = 5

Memory Pool = 200

Maximum number of

Outstanding Operations = 20

Confirmed Indications = 20

Confirmed Requests = 20

Common Transport Selector = A [x] Asc [ ] Hex

Host : localhost 192.168.20.20 (c0a81414)

[ ] OSI [x] RFC 1006



2.3.2 cmip.conf fileThe CMIP Configuration Tool writes to the file;

/etc/opt/SUNWconn/cmip/cmip.conf

Example file:-# This section sets the values of various MCS parametersSECTION CMIP_MCS_PARAMS

# Maximum number of confirmed requests # Value is an integer in the range [1..1024] MAX_CONFIRMED_REQS 20

# Maximum number of confirmed indications # Value is an integer in the range [1..1024] MAX_CONFIRMED_INDS 20

# Maximum number of outstanding operations # Value is an integer in the range [10..1024] MAX_OUTSTANDING_OPS 20

# Inactivity time after which a connection is released # automatically by the MCS # Amount is given in units of 10 seconds in the range [0..255] INACTIVITY_TIMER 120

# Time after which a connection is released when no reply # is obtained after a request emitted by a CMIS-user # Amount is given in units of 10 seconds in the range [0..255] REQUEST_TIMER 10

# User window size : maximum number of requests # for which no reply has been obtained in the range [1..20] USER_WND_SIZE 5

# Memory pool size : number of memory pool # allocated internally by the MCS. Range [100..10240] MEMORY_POOL_SIZE 1024

# Is loopback mode on ? # Value is either ON or OFF LOOPBACK OFF

# This section defines the default XMP addressSECTION DEFAULT_XMP_ADDRESS

# Subnetwork to be used # Value is one of CONS CLNP TCP-IP SUBNET TCP-IP

# Presentation selector to be used PRESENTATION_SEL rfc1

# This section defines the common transport selector# for all the MCS applicationsSECTION MCS_APPL_SEL

# Common session selector for all MCS applications SESSION_SEL Prs

# Common transport selector for all MCS applications TRANSPORT_SEL A



2.3.3 manager.cfg file

Address# Presentation Selector psel q3probe01# Session ssel Prs# Common Transport Selector tsel A# nsap 192.168.52.71 (probe server)# Host: nsap 0xc0a83447 end

2.3.4 IP Addresses

The CMIP configuration file references hexadecimal IP Addressed. Sun’s $OPENWIN/bin/calctool can translate the IP Address from decimal to hexadecimal, and vice versa, as required. As can the Windows Calculator.



3 Probe ConfigurationThe following notes are for all <q3> probes.

3.1 <q3>.df.cfg file

Location : $OMNIHOME/probes/solaris2/<q3>.cdf.cfg:

cdf

trace *

logToFile Y

logFile /opt/netcool/omnibus/log/<q3>_FB.log

logFileBak /opt/netcool/omnibus/log/<q3>_FB.log.bak

logFileSize 100000

traceFile /opt/netcool/omnibus/log/<q3>_FB.trc

traceFileBak /opt/netcool/omnibus/log/<q3>_FB.trc.bak

traceFileSize 100000

userTransactionPriority 64

taskStackSize 65536

consoleType NONE

end



3.2 <q3>.manager.cfg filecmisManagerinternalConfiguration metaDataFile /opt/netcool/Omnibus/probes/q3/<q3>.metadata.datend# Netcool Q3 ProbemanagerIdentity name netcool title apTitle 1.3.999.1.2001 aeQualifier 1 apInvokeId 0 aeInvokeId 0 end address psel src_probe01 ssel Prs tsel CMIP# nsap 192.168.52.63 (probe server) nsap 0xc0a8343f end #applicationContextName end# Siemens Radio CommanderagentIdentity name radio title apTitle 1.3.999.1.2000 aeQualifier 1 apInvokeId 0 aeInvokeId 0 end address psel nmc ssel Prs tsel CMIP # nsap 192.168.52.193 (radio commander) nsap 0xc0a834c1 endend# Controller (links manager to agent)agentController name agent managerIdentity netcool agentIdentity radio agentHandleFactory system agentSendControl timeout 60 endendend



3.3 Presentation Selector (PSEL)The presentation selector (PSEL) defines the unique identifier for the agent or manager. With single instance configurations the default value used by the CMIP tool is sufficient, but not recommended.

It is recommended that a unique PSEL is defined for each probe instance, with a numbered nomenclature in case more probes are installed in the future.

e.g.PSEL = radiocommander01PSEL = switchcommander01PSEL = switchcommander02

Currently multiple agent definitions are not fully supported in the manager.cfg file and multiple invocations of the q3 probe are required, with unique definitions for each agent and manager.

e.g.

For one instance of the probe;

psel probe01

ssel myses01

tsel CMIP

nsap 0xc0a834c1

For the next;

psel probe02

ssel myses02

tsel CMIP

nsap 0xc0a834c1

etc.



3.4 Properties configuration

Generic properties:-

# ScriptName : ""# KeepAlive : 0# CdfConfigFile : "<q3>.cdf.cfg"# MgrConfigFile : "<q3>.manager.cfg"

Example customised properties:-

Name : "<q3>"Server : "NCOMS"MessageLevel : "debug"MessageLog : "/opt/netcool/omnibus/log/<q3>.log"ScriptName : "/opt/netcool/omnibus/probes/solaris2/q3/<q3>.script"CdfConfigFile : "/opt/netcool/omnibus/probes/solaris2/q3/<q3>.cdf.cfg"MgrConfigFile : "/opt/netcool/omnibus/probes/solaris2/q3/<q3>.manager.cfg"RulesFile : "/opt/netcool/omnibus/probes/solaris2/q3/<q3>.rules"

# Probe re-runs the last command in the <q3>.script every KeepAlive seconds

KeepAlive : 60

#EOF



3.5 The apTitle and aeQualifier values

AE title is normally constructed from AP title + AE qualifier.

i.e.

If AE title is { 1 3 9999 3 } then AP title is { 1 3 9999 } and AE qualifier is { 3 }.

The <q3> probes <q3>.manager.cfg file would therefore be:-

managerIdentity name netcool title apTitle 1.3.9999 aeQualifier 3 # apInvokeId 0 # aeInvokeId 0 end address psel netcool ssel Prs tsel CMIP nsap 0x0a790719 end end

For the Siemens Radio Commander ;

AETitle = ApTitle

e.g.

AETitle = ApTitle = 1 3 9999

NOTE: apInvokeId and aeInvokeId are generally not used.



3.6 Q3 ScriptsIBM Support does not provide detailed support for Q3 scripts.

3.6.1 Siemens Radio CommanderThe values used in the example script (OBR / Plmn / 1 / "1") are defined in the configuration of Q3 Element Management System, in this case the Siemens Radio Commander.

# Object definitionObjectNaming global

CreateRef instance

Class x721:eventForwardingDiscriminator

Instance d3100:networkId = pString: "OBR" / \

d3100:networkId = pString: "Plmn" / \

d3100:managedElementId = numericName: 1 / \

x721:discriminatorId = number: 0

# Recreate the Event Forward Descriptor (EFD) [AE Title]DELETE

CREATE x721:discriminatorConstruct = and: {} / \

x721:destination = { 1 3 9999 3} / \

x721:administrativeState = unlocked

# Reset (uncomment if required)#SET x721:administrativeState = locked

#SET x721:discriminatorConstruct = and: {}

#SET x721:administrativeState = unlocked

# KeepAlive commandClass x721:eventForwardingDiscriminator




x721:discriminatorId = number: 0

GET x721:administrativeState



3.6.2 Reading Q3 Scripts

# Create Instance

ObjectNaming global

CreateRef instance

Class x721:eventForwardingDiscriminator




x721:discriminatorId = string: "example"

The sequence of data types of an 'Instance' is:

d3100:networkId =

d3100:networkId =

d3100:managedElementId =

x721:discriminatorId =

All the values to be used depend on the element manager and can only be derived from the element manager's configuration.

DELETE CREATE x721:discriminatorConstruct = and: {} / \ x721:destination = { 1 3 9999 1 2000 } / \

AE Title = 1 3 9999 1 2000

Every object is identified by its 'Managed Object Instance' (MOI) which is referred to as 'Instance' within the Q3 script. This MOI is a path from a single root object to the referred object.

nid d3100:networkIdmelid 3100:managedElementId discid x721:discriminatorId

nid=”OBR60”/nid=”Plmn”/melid=1/discid=”example”

- nid=”OBR60“ - nid=”OBR60”/nid=”Plmn” - nid=”OBR60”/nid=”Plmn”/melid=1 - nid=”OBR60”/nid=”Plmn”/melid=1/discid=”example”

fid OMCB:sbsOmcFunctionIdaaiid OMCB:sbsActiveAlarmInfoId

nid=”OBR60”/nid=”Plmn”/melid=1/fid=1/aaiid=1



3.6.3 Q3 Start-up Script structure

The example below is for the Alcatel OMC-R Q3 EMS:

# Create EFDObjectNaming globalClass x721:eventForwardingDiscriminatorInstance d3100:managedElementId = numericName: 1 / \ x721:discriminatorId = number: 0DELETECREATE x721:discriminatorConstruct = and: {} / \ x721:destination = {1 3 6 1 4 1 3396 2 1 1} / \ x721:administrativeState = unlocked# Start of Synchronisation# 100 / 1 – Resync Class anoi051019:CoreManagedElementInstance d3100:networkId = numericName: 100 / \ d3100:managedElementId = 1EventSource syncProbeWatch START SYNCHRONIZATIONACTION anoi051019:retrieveCurrentAlarmsDataEventSource live# 101 / 1 – Resync Class anoi051019:CoreManagedElementInstance d3100:networkId = numericName: 101 / \ d3100:managedElementId = 1EventSource syncACTION anoi051019:retrieveCurrentAlarmsDataEventSource live# End of Synchronisation commandsProbeWatch END SYNCHRONIZATIONEventSource live# Active alarm commands# None reqired# Keep Alive command – Last CommandGET x721:administrativeState#EOF

The start-up script performs the following actions:1. Creates the EFD2. Performs synchronisation3. Sets the KeepAlive command

The Q3 EMS administrator and EMS Vendor support teams should be contacted to provided specific details on writing Q3 scriptsas they require knowledge of the specific EMS and the vendors implementation of Q3.



With the Alcatel OMC-R Q3 EMS ANOI [Alcatel Network Object Instance] commands can be used, for example:ACTION anoi051019:retrieveCurrentAlarmsDatathese can be applied to ANOI classes, for example:Class anoi051019:anoiCoreManagedElementProvided the EMS is configured to understand these manufacturer.

The available network instances can be derived from the probes log file and $ MOInstance token:e.g. $MOInstance -> dn:{ networkId=numericName:101,managedElementId=numericName:1 }Which can allow EMS specific synchronisation Q3 scripts to be created, that request all elements so far reported to the ObjectServer, to be resynchronised.

Probe specific commands:• The EventSource command is used to define the $eventsource token which can be used in rules file processing.• The ProbeWatch command is used to register the Synchronisation timings with the object server.

3.6.4 Classes

Whether the prefix anoi051019, x721, or d3100 is used depends on the object being addressed in the MIB. These prefixes referto various documents that define the object classes or attribute names.

For example:The Alcatel interface document "anoi_051019.mib" defines a class "anoiPlmnNetwork".The description of this class states that it has an attribute named "networkId " whose details are specified in the ITU standard document M.3100. The probe can therefore refer to the attribute as d3100:networkId. As defined in the "anoi_051019.mib" document.Other Alcatel OMCR probes use "anoi" instead.

Valid class can be given as:Class anoi051019:anoiCoreManagedElementORClass 1.3.12.2.1006.53.1.3.0.3.13

Whilst it is important to be aware of class restrictions, for example:The ACTION retrieveCurrentAlarmsData" is only supported by the classes

• anoi051019:anoiManagedElement• anoi051019:anoiCoreManagedElement• anoi051019:anoiGPRSManagedElement



4 Frequently Asked Questions

Is Solstice CMIP a point-to-point protocol? Yes, CMIP is Point-to-Point. A TCP connection must be established. Both servers can establish the connection and are allowed to disconnect at will. Disconnection can be based on connection activity at the CMIP level. Solstice CMIP supports multiple connections to multiple peer systems from single or multiple applications.

Multiple probes can be run on the same server, provided their file names are separated and they are configured uniquely.

How can Solstice CMIP be configured for multiple element managers?

Multiple applications must be defined uniquely, so that they can be identified correctly. The OSI protocol stack uses the selectors NSAP, Transport, Session, Presentation as well as the Application Title (AP Title + AE qualifier). The Solstice CMIP stack fixes NSAP, Transport and Session Selector. The rest of the address is assigned by the <q3> probe. The Q3 probes must ensure thatthey use unique values for each element manager when they are installed on the same probe server.

From the probe's point of view, there are two aspects of configuration

1) outgoing connections are defined by the probe and probe servers CMIP configuration

2) incoming connections are defined on the Q3 Element Management System

These configurations are defined in the <q3>.manager.cfg file which contains the agentIdentitity (ems) and managerIdentity (probe) definitions.



5 Understanding the rk6trace

5.1 Radio Commander Issue

grep -i call rk6trace.log

Radio Commander: Unknown permission problem (check parameters/configuration)

23.23 TP Calling TSAP-ID = 0x4001

23.23 TP Called TSAP-ID = 0x434d4950 <CMIP>

23.23 SES Calling session selector = 0x01

23.23 SES Called session selector = 0x507273 <Prs>

23.23 PRES Calling-presentation-selector = 01 <.>

23.23 PRES Called-presentation-selector = <dflt>

23.23 ACSE Called-AP-title

23.23 ACSE Called-AE-qualifier

23.23 ACSE Calling-AP-title

23.23 ACSE Calling-AE-qualifier

23.23 SES Refuse reason code = Rejection by called SS-user

Switch Commander: Unknown permission problem (check parameters/configuration)

42.08 TP Calling TSAP-ID = 0x434d4950 <CMIP>

42.08 TP Called TSAP-ID = 0x38313431 <8141>

42.10 TP Calling TSAP-ID = 0x434d4950 <CMIP>

42.10 TP Called TSAP-ID = 0x38313431 <8141>

42.10 SES Calling session selector = 0x507273 <Prs>

42.10 SES Called session selector = 0x3031 <01>

42.10 PRES 81 07 Calling-presentation-selector = <netcool>

42.10 PRES 82 02 Called-presentation-selector = <01>

42.10 ACSE a2 0b Called-AP-title

42.10 ACSE a3 03 Called-AE-qualifier

42.10 ACSE a6 0b Calling-AP-title

42.10 ACSE a7 03 Calling-AE-qualifier

42.13 SES Refuse reason code = Rejection by called SS-user



6 Q3 Element Management Systems

6.1 Nortel OMC-R

The omc_configure.cfg file defines the manager and agents on the Nortel OMC-R ems.

The remote CMIP device (the probe server) is defined as;

1.2.826.1.1336.6.6 1 NMA Prs CMIP c0a8780a

The element manager is defined as;

BEGIN_PREFERENTIAL_ACTIVE_MEDIATION_DEVICE

1.2.250.1.16.1.3.21.30 1024

END_PREFERENTIAL_ACTIVE_MEDIATION_DEVICE



7 Command line interfaceThe Q3 EMS administrator can create Q3 scripts with the correct parameters and syntax that can be used against the EMS via the probes command line interface.

For example, a resynchronisation script [resync.script] can be created and used.

From the probes command-line interface, connected to using telnet, issue the command:

Include /opt/IBM/tivoli/netcool/omnibus/probes/solaris2/resync.script

The syntax of the resync.script would be of the format given below:

Class SCR12:sssActiveAlarmList Instance d3100:managedElementId = numericName: 1 / \ SCR12:sssSwitchCommanderId = number: 0 / \ SCR12:sssActiveAlarmListId = number: 0 ACTION SCR12:sssReportActiveAlarms = { \ alignmentRequestNumber 0, \ networkEntities { \ localDistinguishedName: { \ { { \ namingAttributeId { 0 0 11 1100 0 1 11 }, \ namingAttributeValue numericName: 1 \ } } \ } \ } \ }

The probe property file configured the command-line interface, for example: ConsolePort : 9009AuthInfo : "probeuser:jsFrqujJ5NXs2"

With access to the command-line interface accessed using telnet as;telenet probe_server 9009

Auth probeuser netcool



7.1 Securing the ConsolePortWhen the ConsolePort is set to '0' the console port feature is inactive.There is another console port set in the <probe>.cdf.cfg file which is defined by the socketConsolePort.Setting this to NONE disables the CDF console port.

The username and password used in the AuthInfo property is not tied to UNIX or object server authentication. The password is unencrypted by the probe on start-up, and the unencrypted password is used for issuing authentication.There are no repeated failure checks, or port access prevention configured into the probe. Therefore it is recommended that the console ports are disabled in a secure environment.

Where console port access is required, within a secure environment, the socketConsolePort should be disabled, and the AuthInfo property set. A unique username should be chosen, and the password set to a long random character string to prevent guessing, and decryption of the probe property. One of the Netcool/OMNIbus crypt tools could be used to confuse any possible attack.e.g.nco_g_crypt myrandomstringtextEBFHBHAEBIEMGGFOGOCBBNBJCABFCNFAFIGH$OMNIHOME/probes/q3_crypt EBFHBHAEBIEMGGFOGOCBBNBJCABFCNFAFIGHyb1gRpRlXmYvU

Use a non-root port for ConsolePort:e.g.AuthInfo 'myrandom-non-unixuser:yb1gRpRlXmYvU'ConsolePort : 9900

Access to the ConsolePort could be performed local to the probe only, using a trigger in a local collection object server or via nco_pad, preventing snooping of the ConsolePort. The use of an operating system firewall could also be used to prevent unauthorised access.



7.2 Command-line authentication

The Q3 probe command-line authentication syntax is: Auth <username> <unencryptedPassword>

Where the username and unencryptedPassword are the same settings used in the probes AuthInfo property, with the unencryptedPassword string being encrypted using q3_crypt. The

e.g.q3_crypt unencryptedPasswordjsFrqujJ5NXs2

AuthInfo : "probeuser:jsFrqujJ5NXs2"

commandline syntax:telnet probe-host command-portAuth probeuser unencryptedPassword

It is recommended that the q3_crypt tool is run a number of times until an alphanumeric string returned as the encryptedPassword for use in the probes property to prevent special character problems.

7.2.1 q3_crypt

The q3_crypt tool creates a random string based on the command-line string:

#!/usr/bin/perl -w

if (scalar(@ARGV) != 1) { die "usage: q3_crypt password\n";}

my @charset = ('.', '/', 0..9, 'A'..'Z', 'a'..'z');my $seed = join('', $charset[rand 64], $charset[rand 64]);

print crypt($ARGV[0], $seed), "\n";#EOF

7.3 Common Development FrameworkThe probe.cdf.cfg file is used to configure the probes side of the CMIP integration. The socketConsolePort defines a Console Port socket that listens for commands.This feature should be disabled in secure environments, and not used in all other environments.The socketConsolePort is not secured using a username and password.The default value is 3000. To disable the port use a value of NONE.



7.4 Alarm AcknowledgementGeneral syntax:

AcknowledgeAlarmInfo ::= SEQUENCE {managedObjectClass ObjectClass,managedObjectInstance ObjectInstance,eventType EventTypeId,probableCause ProbableCause,specificProblems [1] SpecificProblems OPTIONAL,perceivedSeverity PerceivedSeverity,additionalInformation [10] AdditionalInformation OPTIONAL}

7.4.1 Alcatel OMC-R Q3 EMS

Acknowledge all alarms:ACTION anoi051019:acknowledgeAlarms={}



8 CMIP Troubleshooting

8.1 CMIP.conf file

Altering the properties of the CMIP stack should be performed on the advice of Sun Microsystems Support. The following examples are for reference purposes only.

Filename : /etc/opt/SUNWconn/cmip/cmip.conf

Memory issues Increase the memory to the maximum allowable.

MEMORY_POOL_SIZE 10240

Timeout issues Increase the timeout to 20 minutes (120*10 seconds).

INACTIVITY_TIMER 120

8.2 CMIP restart script

#! /bin/shLM_LICENSE_FILE=/etc/opt/licenses/licenses_combinedexport LM_LICENSE_FILE/etc/init.d/osimcs stop/etc/init.d/rk6 stop/etc/init.d/rk6 start/etc/init.d/osimcs start



9 Example Q3 ScriptsThe following q3 scripts are provided with the Q3 probes.

9.1 alcatel_omcr1353ra_b10.scriptObjectNaming global

Class x721:eventForwardingDiscriminatorInstance d3100:managedElementId = numericName: 1 / \ x721:discriminatorId = number: 0CREATE x721:discriminatorConstruct = and: {} / \ x721:destination = {1 3 6 1 4 1 3396 2 1 1} / \ x721:administrativeState = unlocked


9.2 alcatel_omcr1353ra_b62.script

ObjectNaming global

Class x721:eventForwardingDiscriminatorInstance d3100:networkId = pString: "mynet" / \ d3100:managedElementId = pString: "mySystem" / \ x721:discriminatorId = number: 0DELETECREATE x721:discriminatorConstruct = and: {} / \ x721:destination = {1 3 6 1 4 1 3396 2 1 1} / \ x721:administrativeState = unlocked

Class ANOI:anoiCoreManagedElementInstance d3100:networkId = pString: "mynet" / \ d3100:managedElementId = pString: "mySystem"

ACTION ANOI:retrieveCurrentAlarmsData

#Class x721:eventForwardingDiscriminator#Instance d3100:managedElementId = numericName: 1 / \# x721:discriminatorId = number: 0#GET x721:administrativeState

Instance d3100:networkId = pString: "mynet" / \ d3100:managedElementId = pString: "mySystem" / \ x721:discriminatorId = number: 0




9.3 nortel_omcr_v14.script

ObjectNaming globalCreateRef superiorinstance

Class x721:eventForwardingDiscriminatorInstance CfGDMO:md = 1CREATE x721:discriminatorConstruct = and: {} / \ x721:destination = {1 3 6 1 4 1 3396 2 1 1} / \ x721:administrativeState = unlocked

Class CfGDMO:mdACTION CfGDMO:nortelUserAlarmGetAlarmListAction

#Instance ???#GET x721:administrativeState

9.4 siemens_rc_br70v31.script

ObjectNaming globalCreateRef instanceClass x721:eventForwardingDiscriminatorInstance TS32_624:subNetworkId = 1 / \ TS32_624:managementNodeId = 1 / \ x721:discriminatorId = number: 1

DELETECREATE x721:discriminatorConstruct = and: {} / \ x721:destination = {1 3 6 1 4 1 3396 2 1 1} / \ x721:administrativeState = unlocked

Class SBS3:sbsAlarmControlInstance TS32_624:subNetworkId = 1 / \ TS32_624:managementNodeId = 1 / \ TS32_111:alarmControlId = 1

ACTION TS32_111:getAlarmList = { \ alarmAckState allActiveAlarms, \ destination {1 3 6 1 4 1 3396 2 1 1}, / \ filter and: {} \ }

#Class x721:eventForwardingDiscriminator#Instance TS32_624:subNetworkId = 1 / \# TS32_624:managementNodeId = 1 / \# x721:discriminatorId = number: 1#GET x721:administrativeState

ObjectNaming globalClass SBS3:sbsMobileNetworkInstance TS32_624:subNetworkId = 1SET SBS3:sbsAssocTimeOutCounter = 1



9.5 siemens_rc_br85v50.script



Class SBS3:sbsAlarmControl-0-2Instance TS32_624:subNetworkId = 1 / \ TS32_624:managementNodeId = 1 / \ TS32_111:alarmControlId = 1


9.6 siemens_rc_umr6.script



Class SBS3:sbsAlarmControlInstance TS32_624:subNetworkId = 1 / \ TS32_624:managementNodeId = 1 / \ TS32_111:alarmControlId = 1


#Class x721:eventForwardingDiscriminator#Instance TS32_624:subNetworkId = 1 / \# TS32_624:managementNodeId = 1 / \# x721:discriminatorId = number: 1#GET x721:administrativeState

ObjectNaming globalClass SBS3:sbsMobileNetworkInstance TS32_624:subNetworkId = 1SET SBS3:sbsAssocTimeOutCounter = 1



9.7 siemens_sc_scr12.script

# Note: Real SCR12 needs a local nameObjectNaming localCreateRef instanceClass x721:eventForwardingDiscriminatorInstance d3100:managedElementId = numericName: 1 / \ x721:discriminatorId = number: 0DELETECREATE x721:discriminatorConstruct = and: {} / \ x721:destination = {1 3 6 1 4 1 3396 2 1 1} / \ x721:administrativeState = unlocked

Class SCR12:sssActiveAlarmListInstance d3100:managedElementId = numericName: 1 / \ SCR12:sssSwitchCommanderId = number: 0 / \ SCR12:sssActiveAlarmListId = number: 0

ACTION SCR12:sssReportActiveAlarms = { \ alignmentRequestNumber 0, \ networkEntities { \ localDistinguishedName: { \ { { \ namingAttributeId { 0 0 13 3100 0 7 28 }, \ namingAttributeValue numericName: 1 \ } } \ } \ } \ }

#Class x721:eventForwardingDiscriminator#Instance d3100:managedElementId = numericName: 1 / \# x721:discriminatorId = number: 0#GET x721:administrativeState



10Q3 manager versions

Probe Binary Supported Q3 system

nco_p_alcatel_omcr1353ra_b10 Alcatel OMC-R RA B9, B10

nco_p_alcatel_omcr1353ra_b62 Alcatel OMC-R RA B62

nco_p_motorola_omcr1620_v65 Motorola OMC-R 1620 version 65

nco_p_nortel_omcr_v14 Nortel OMCR version 14

nco_p_siemens_rc_br70v31 RadioCommander BR70 v31

nco_p_siemens_rc_br85v50 RadioCommander BR85 v50

nco_p_nco_p_siemens_rc_umr6 RadioCommander UMR 4,5,6,7

nco_p_siemens_sc_scr12 Siemens SwitchCommander SCR12

10.1Siemens Radio Commander

The Siemens Radio Commander manages network elements as follows: Base Station Controller (BSC), Base Transceiver Station (BTS), Transcoding and Rate Adaptation Unit (TRAU), as well as Radio Network Controller (RNC) and NodeB.

The supported Radio Commander versions are shown below:

• RC8.0 - BR8 / UMR4• RC8.5 - BR8 / UMR5• RC9.0 - BR9 / UMR6• RC9.5 – UMR6.5• RC10.0 - BR10 / UMR7


Documents

Tivoli Netcool Supports Guide to Q3 probes by Jim ... - IBM