Tivoli Netcool/Proviso Document Revision R2E2 Cisco IP Telephony 2.4.0.
Note Before using this information and the product it supports, read the information in Notices on page 95. © Copyright IBM Corp. 2010 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) . . . . . . . . . . . . . . .63 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 INSTANCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 INSTANCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1: Introduction This manual describes the IBM® Tivoli® Netcool®/Proviso® Cisco IP Telephony Technology Pack. Specifically, the manual describes the reports that display information about the devices and technologies that operate in the Cisco IP Telephony environment. Note: This technology pack supports the Cisco CallManager (CCM) environment and its new implementation, the Cisco Unified Communications Manager (CUCM) environment.
Chapter 1: Introduction • Appendix B, Template file (Tivoli Netcool/Proviso pre-v4.4.3 only) Explains the edits that must be made to the pack-specific UBA parameters delivered in the pack template file.
Chapter 2: Devices and Services This chapter discusses the following topics: Topic Page Overview 3 Summary of Device Technology 3 Sources of Collected Data 5 Prerequisites 8 Supported MIBs 9 Overview This chapter provides a summary of Cisco IP Telephony device technology that the Cisco IP Telephony Technology Pack is designed to support.
Chapter 2: Devices and Services Categories of Service Reporting The technology pack provides the following categories of service reporting: • Voice Quality Management — Latency, jitter, packet loss, network bandwidth, Class-Based QoS, and element availability. • Call Signaling Management — Call setup and termination metrics, based on data from Call Detail Records (CDRs). • Converged Network Infrastructure Management — Network and system devices in charge of the Service and Voice Data Packets Delivery.
Chapter 2: Devices and Services Sources of Collected Data The Tivoli Netcool/Proviso Cisco IP Telephony Technology Pack uses both SNMP and bulk data collection.
Chapter 2: Devices and Services The following figure illustrates the technology pack’s data collection architecture in a CCM environment: Port for SQL Access CallManager Publisher runs on a Microsoft SQL Server 2000 server. To collect SQL data from the CallManager Publisher, an SQL bridge must be set up on the machine where Tivoli Netcool/Proviso DataLoad resides. This bridge is provided as part of the Tivoli Netcool/Proviso Cisco IP Telephony Technology Pack.
Chapter 2: Devices and Services • With pre-4.4.3 Tivoli Netcool/Proviso versions, ensure that the dc.cfg file contains a URI for each CCM Publisher bulk adaptor, and that the URI matches the URI of the associated data source in the odbc.ini file.
Chapter 2: Devices and Services Prerequisites This section describes the prerequisites for the Tivoli Netcool/Proviso Cisco IP Telephony Technology Pack. SNMP Access The Tivoli Netcool/Proviso Cisco IP Telephony Technology Pack needs read access to SNMP agents of PSTN gateway, gatekeeper, and CallManager Server devices. Customers must provide a valid IP address and community name to access these devices. UDP Port number 161 needs to be open in the remote firewalls.
Chapter 2: Devices and Services In addition, the following enterprise parameters must be set: • LocalCDRPath — A directory for local CDR files written by Cisco CallManager. If this value is empty or invalid, the CDR files will not be moved. • PrimaryCDRUNCPath — A central collection point for CDR files. If this value is empty or invalid, the CDR files will not be moved. The installation procedure sets this parameter.
Chapter 2: Devices and Services The Cisco IP Telephony Technology Pack provides a file that interprets these bulk input files. See Bulk adaptor design files on page 11 for more information. Bulk input file name Cisco IP Telephony devices produce Comma-Separated Values (CSV) files that are named using the following syntax: DataType_ClusterName_Date_SerialNumber.csv where: • DataType specifies the type of data collected: cdr, cmr, cdrcmr, or perfmon.
Chapter 2: Devices and Services neCluster",0,"","",0,"",3,0,0,1,"6076",5362499,1273883641,541,2954,487,2849,6,96 ,144,"03d4df7b-78ff-460e-a0bb43ccee36cc5f","Phones","StandAloneCluster","SEP00155832DDD5","MLQK=3.2000;MLQKav =3.3000;MLQKmn=1.4000;MLQKmx=3.9000;ICR=0.8200;CCR=0.7600;ICRmx=0.
Chapter 2: Devices and Services NOTES 12 IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Chapter 3: Supported Reports and KPIs This chapter discusses the following topics: Topic Page Overview 13 Reporter sets 13 Reporter set tree 15 Reporter set contents 16 Key performance indicators 33 Overview The Cisco IP Telephony Technology Pack supplies a set of reports to display information about the devices and activity associated with the Cisco IP Telephony environment. The reports contain metrics that are generated by the formulas that this technology pack provides.
Chapter 3: Supported Reports and KPIs Table 1 shows a summary of the reports in each reporter set provided by the Cisco IP Telephony Technology Pack.
Chapter 3: Supported Reports and KPIs Reporter set tree The Cisco IP Telephony Technology Pack provides the following reporter sets, which are listed as they appear in the DataView Navigator tree structure: AP Cisco VOIP Pack Global Customer Reports Call Detail Record Cluster Extension K-Factor Codec Infrastructure CallManager Server PSTN Gateway Interface Device DSP Card Media Devices Gatekeeper Device Interface Perfmon IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Chapter 3: Supported Reports and KPIs Reporter set contents This section describes the contents of the reporter sets provided in the Cisco IP Telephony Technology Pack, including the key performance indicators (KPIs) for each report. Note: If any fields are omitted from the CDR or CMR data, the corresponding metric fields in the reports have dashes instead of zeroes.
Chapter 3: Supported Reports and KPIs • Cluster Total Hours of Traffic • ClusterNbPacketsSent • ClusterTotalCall Charts • TollBypass vs Normal Ougoing PSTN Calls • Company vs External Calls Cluster Quality Resource KPIs • ClusterNbPacketsLost • MLQK • ClusterLatency • ClusterJitter • Cluster Total Number of Normal Call Clearing • ClusterDropCall • ClusterSuccessfulCall • ClusterUnsuccessfulCall Charts • Successful vs Unsuccessful Calls • Drop calls vs Normal call clearing Cluster Call Distribution Resour
Chapter 3: Supported Reports and KPIs • ClusterInternationalCall • ClusterLocalCall • ClusterInternalCall • ClusterIncomingCall Charts • Incoming vs Outgoing Calls Ratio • Types of Calls Distribution Top 10 Cluster Call Completion KPIs • Cluster Percentage of Successful Calls (percent) • Cluster Percentage of Drop Calls (percent) • Cluster Percentage of Normal Call Clearing (percent) Cluster Quality Group KPIs • ClusterMOS • Cluster Percentage of Drop Calls (percent) • MLQK • ClusterLatency • ClusterJitt
Chapter 3: Supported Reports and KPIs Charts • TollBypass Calls Distribution Chart • Comapny Calls Percent Distribution Chart Top 10 Cluster Number of Calls KPIs • ClusterTotalCall • ClusterOnNetCall • ClusterIncomingCall • Cluster Total Number of Outgoing External Calls (Nb) • ClusterOffNetCall Top 10 Cluster Number of Errors KPIs • Cluster Percentage of Successful Calls (percent) • ClusterShortCall • Cluster Percentage of Packet Lost (percent) • Cluster Percentage of Drop Calls (percent) Cluster Voice
Chapter 3: Supported Reports and KPIs Cluster Utilization MLH Resource KPIs • ClusterTollBypassCall • ClusterNbPacketsLost • Cluster Total Number of Company Calls (Nb) • Cluster Total Hours of Traffic • ClusterNbPacketsReceived • ClusterSuccessfulCall • ClusterTotalCall • ClusterNbPacketsSent • ClusterUnsuccessfulCall Charts Cluster Erlang-B Group KPIs • Cluster Erlang • Cluster Total Hours of Traffic • ClusterBlocking • ClusterLines • ClusterErlangB Extension CDR Utilization Resource KPIs • Percentage o
Chapter 3: Supported Reports and KPIs • Percentage of Drop Calls (percent) CME(Bulk) VOIP Cisco • SuccessfulCall • Latency • MOS • Jitter • Percentage of Packet Lost (percent) CME(Bulk) VOIP Cisco • Percentage of Successful Calls (Nb) CME(Bulk) VOIP Cisco Charts • Drop Calls Distribution Chart • Percentage of Successful calls Distribution Chart CDR Call Distribution Resource KPIs • Local • Incoming • LongDistance • International • Total Number of Outgoing External Calls (Nb) • Internal Charts • Incoming v
Chapter 3: Supported Reports and KPIs CDR VoiceMail Usage Resource KPIs • VoicemailPackets • VoicemailCallDuration • VoiceMailCall • Total Number of VoiceMail Direct Calls (Nb) CME(Bulk) VOIP Cisco • ForwardToVoiceMail Charts • Direct vs Forward Calls ratio Top 10 CDR Call Completion KPIs • Percentage of Successful Calls (Nb) CME(Bulk) VOIP Cisco • Percentage of Drop Calls (percent) CME(Bulk) VOIP Cisco Top 10 CDR Call Duration KPIs • TollbypassCallDuration • CallDuration CDR Quality Group KPIs • Percen
Chapter 3: Supported Reports and KPIs • CallDuration • NbPacketsSent Charts • Company Calls Percent Distribution Chart • TollBypass Calls Distribution Chart CDR Call Distribution Group KPIs • Local • Incoming • LongDistance • International • Total Number of Outgoing External Calls (Nb) • Internal Charts • Incoming vs Outgoing Calls Ratio • Types of Calls Distribution K-Factor K-Factor Resource KPIs • MLQKmx • MLQKmn • MLQK • MLQKav • ICRmx • ICR • SCS • CS • CCR K-Factor Group KPIs • MLQKmn • MLQK • MLQ
Chapter 3: Supported Reports and KPIs • SCS • CS • CCR Charts • Mean Opinion Score Top 10 CDR K-Factor KPIs • CCR • ICR • CS • SCS • MLQK Codec Errors on Cluster by Codec KPIs • CauseTemporaryFailure • CauseNetworkOutOfOrder • CauseChannelUnacceptable • CauseUserBusy • CauseDestinationOutOfOrder • CauseNoRouteTransitNetwork • CauseUnassignedNumber • CauseNumberChanged • CauseNoChannelAvailable • CauseMisdialedTrunkPrefix • CauseNoRouteToDestination • CauseInvalidNumberFormat • CauseNoAnswerFromUser • Cau
Chapter 3: Supported Reports and KPIs Infrastructure CallManager Server CCM Server Quality Resource KPIs • CCM Rejected Devices (Nb) (Gauge) • CCM Physical Memory Utilization (percent) • CCM Registered Devices (Nb) (Gauge) • CCM CPU Utilization (percent) (avg last 5 mn) Charts • Managed Devices • CPU Utilization Distribution Chart CCM Sql Server Resource KPIs • CCM SQL Server number of locks • CCM SQL Server free buffers (Nb) • CCM SQL Server Cache Hit ratio (percent) • CCM SQL Server number active user c
Chapter 3: Supported Reports and KPIs Charts • CPU Utilization Distribution Chart • SQL Server Number of Locks Distribution Chart PSTN Gateway Interface Top 10 E1/T1 Utilization Resource KPIs • PSTN Gateway DS1 Active DS0 Channels (Nb) • Interface Bandwidth Utilization In (percent) • Interface Bandwidth Utilization Out (percent) • Interface Throughput In (kbps) • Interface Throughput Out (kbps) PSTN Gateway E1/T1Availability Resource KPIs • Interface Availability (percent) • Interface Packet Loss (percen
Chapter 3: Supported Reports and KPIs • SNMP Response Time (ms) (avg last hour) • PSTN Gateway Network Errors (percent) • PSTN Gateway Total Packets per Second Charts • Network Errors percentage • Number of Active DS0 Channels PSTN Gateway Availability Resource KPIs • PSTN Gateway ICMP Outbound Errors (percent) • PSTN Gateway ICMP Inbound Errors (percent) • SNMP Response Time (ms) (avg last hour) • SNMP Availability (percent) (avg last hour) Charts • SNMP Responce Time Distribution Chart • SNMP Availabili
Chapter 3: Supported Reports and KPIs Charts • Media Device Registration Distribution Chart Gatekeeper Device Gatekeeper Device Quality Resource Detail Chart KPIs • Gatekeeper Total Number of Concurrent Calls (Nb) (Gauge) • Gatekeeper Packet Errors (Nb) • Gatekeeper Total Number of Admission Requests (Nb) • Gatekeeper Buffer Utilization (percent) • Gatekeeper Total Number of Location Rejects (Nb) • Gatekeeper Total Number of Admission Rejects (Nb) • Gatekeeper Total Packets (Nb) • Gatekeeper Call Setup Qu
Chapter 3: Supported Reports and KPIs • Call Setup Quality Gatekeeper Availability Resource Detail Chart KPIs • Gatekeeper ICMP Inbound Errors (percent) • SNMP Unavailable (percent) (avg last hour) • SNMP Availability (percent) (avg last hour) • Gatekeeper ICMP Outbound Errors (percent) • SNMP Response Time (ms) (avg last hour) • SNMP Availability (percent) (avg last hour) Charts • SNMP Availability (percent) (avg last hour) • Outbound ICMP Errors (percent) • Availability vs Unavailable - SNMP • Inbound I
Chapter 3: Supported Reports and KPIs Gatekeeper Interface Availability Resource KPIs • Interface Availability (percent) • Inbound Loss (percent) • Outbound Loss (percent) Gatekeeper Interface Utilization Resource Detail Chart KPIs • Interface Bandwidth Utilization Out (percent) • Interface Bandwidth Utilization In (percent) • Interface Throughput Out (kbps) • Interface Throughput In (kbps) Charts • Inbound vs Outbound Utilization (avg) • AP.global.
Chapter 3: Supported Reports and KPIs • GatewayCallsActive • SIPCallsActive • H323CallsActive Perfmon Active Calls Group KPIs • CallsActive • CallsInProgress • HuntlistCallsInProgress • HuntlistCallsActive • SIPCallsInProgress • H323CallsInProgress • GatewayCallsActive • SIPCallsActive • H323CallsActive Perfmon Security Group KPIs • EncryptedCallsActive • AuthenticatedPartiallyRegisteredPhone • AuthenticatedCallsActive • CallsActive • AuthenticatedRegisteredPhones • EncryptedRegisteredPhones • EncryptedP
Chapter 3: Supported Reports and KPIs Perfmon PSTN Resource KPIs • T1SpansInService • T1ChannelsActive • FXSPortsInService • FXOPortsActive • BRIChannelsActive • FXSPortsActive • FXOPortsInService • BRISpansInService Perfmon PSTN Group KPIs • T1SpansInService • T1ChannelsActive • FXSPortsInService • FXOPortsActive • BRIChannelsActive • FXSPortsActive • FXOPortsInService • BRISpansInService Perfmon MOH Resource KPIs • MOHUnicastResourceActive • MOHTotalUnicastResources • MOHUnicastResourceAvailable • MOHM
Chapter 3: Supported Reports and KPIs Key performance indicators Table 2 lists all of the key performance indicators (KPIs) supported by the Cisco IP Telephony Technology Pack.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment CCM SQL Server number of locks blocking processes Total number of locks blocking other processes. CCM SQL Server number of pending rw Total number of reads and writes pending CCR Cumulative conceal ratio. Cumulative concealment ratio during a call represented as concealment time / speech time CS Conceal seconds.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment Cluster Percentage of Company Calls (percent) Ratio between Company calls and Total number of Calls Cluster Percentage of Drop Calls (percent) Ratio between DropCalls and Total number of Calls Cluster Percentage of Normal Call Clearing (percent) Ratio between Calls that have normal termination code and Total number of Calls. This metric is the opposite of the Percentage of Drop Calls metric.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment ClusterIncomingCall Identifies a call where caller is not an internal extension. An Incoming call is also: - An Inbound call - An Off-net call, coming from the PSTN ClusterInternalCall An Internal Call is a call between 2 internal extensions, managed by one or more CallManager Clusters, where the 2 Extension numbers (caller and callee) are short internal numbers.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment ClusterLocalCall Identifies a call where the caller is an internal extension and where the callee is a Local External PSTN number, according to the Numbering Plan (NANP or Other prefixes). A Local call is also:- An Outbound call - An Off-net call, routed towards the PSTN - Can be a TollBypassCall if a remote PSTN Gateway is involved in the Voice path Note: Internal extensions are managed through the UBA.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment ClusterShortCall Identifies a call successfully established, but with a call duration less than 1 second. In this case, the CallManager set the CallDuration value to 0 in the CDR table. A ShortCall call is also: - A Successful call - Any Inbound, Outbound, or other type of call described above. ClusterSuccessfulCall Identifies a call successfully established.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment ForwardToVoiceMail Identifies a call forwarded to another destination by the original callee. In this case, the destination is one of the VoiceMail extension number, defined in the VoiceMailExtensionRange variable from the UBA.xml adaptor configuration file.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment Inbound Loss (percent) Out of all inbound traffic received by this entity, the percentage of PDUs that: (a) contained defects which prevented them from being deliverable to a higher-layer protocol (bad checksums, bad length, etc.), (b) were discarded even though no errors are detected (i.e.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment Latency Designates value that is an estimate of the network latency, expressed in milliseconds. This value represents the average value of the difference between the NTP timestamp indicated by the RTP Control Protocol (RTCP) messages and theNTP timestamp of the receivers, measured when these messages are received.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment MOS Mean Opinion Score. This is an high level metric. Note: There is no algorithm for Mean Opinion Score calculations. This is a subjective metric from the end user point of view. In voice communications, particularly Internet telephony, the mean opinion score (MOS) provides a numerical measure of the quality of human speech at the destination end of the circuit.
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment PSTN Gateway ICMP Inbound Errors (percent) Percentage of inbound ICMP errors PSTN Gateway ICMP Outbound Errors (percent) Percentage of outbound SNMP errors PSTN Gateway Network Errors (percent) Percentage of network errors observed by a PSTN gateway PSTN Gateway Packet Discards Percentage of PSTN gateway packets discarded PSTN Gateway Total Number of Calls (Nb) Total number of calls for a PSTN device PSTN Gate
Chapter 3: Supported Reports and KPIs Table 2: Key performance indicators KPI Comment T1ChannelsActive Total number of T1 channels currently in use in the target device T1SpansInService Total number of T1 spans available in the target device TollBypassCall Identifies a call where the caller is an internal extension, managed by the CallManager and where the callee can be an internal extension or any external PSTN Number, with one or more following criteria: - Outbound call - Off-net call - The call i
Chapter 4: Configuring the technology pack This chapter explains how to configure the Cisco IP Telephony Technology Pack and consists of the following topics: Topic Page Overview 45 Before you begin 45 Configure the technology pack 46 Overview Tivoli Netcool/Proviso supports the following two types of technology packs, based on the type of data that they collect: • SNMP SNMP packs are MIB-based, and their configuration is relatively straightforward.
Chapter 4: Configuring the technology pack — An X Window server on the DataMart server. Note: (Tivoli Netcool/Proviso pre-v4.4.3) If there is no graphics card on the DataMart server, you can install the Xvfb virtual frame buffer package to provide X Window services, as described in the IBM Tivoli Netcool/Proviso Installation Guide. — Access to the SilverStream server. — Access to the DataChannel server. • Have completed the following tasks: — Reviewed the release notes for the current technology pack.
Chapter 4: Configuring the technology pack 1-c. Load the shell with the DataMart environment, by sourcing the dataMart.env file, as follows: . /opt/datamart/dataMart.env Note: After you load the DataMart environment into the shell, the PVMHOME variable is set to the DataMart home directory, /opt/datamart by default. These instructions assume that this variable has been set. 2. Copy technology-specific files from the DataMart server to the DataChannel server.
Chapter 4: Configuring the technology pack 3-a. Change your working directory to $PVMHOME/bin (/opt/datamart/bin, by default) on the DataMart server. 3-b. Invoke the DataMart GUI by entering the following command and pressing Enter: pvm 3-c. Click the Configuration tab, then click Request Editor to open the Request Editor. 3-d. Click the Collection tab. 3-e. Click Refresh. The predefined data collection requests are loaded into the Request Editor from the database. 3-f.
Chapter 4: Configuring the technology pack 5. CCM environment only: Configure the Data Direct SQL Server Bridge The Tivoli Netcool/Proviso Cisco IP Telephony Technology Pack collects data from SNMP devices and, through SQL for Call Detail Records, from each CCM database. The technology pack UBA is responsible for retrieving CCM data, using the Data Direct SQL server bridge to do so. This bridge is part of the UBA installation. No additional software is required.
Chapter 4: Configuring the technology pack Field Description [Data Source Name] The configuration of the specified data source. [ODBC] • [Data Source Name]: for example, [SANFRANCISCO] • Address: the remote IP address and TCP port of the CallManager Publisher Database (for example, 192.168.1.1,1433). To verify the remote connection configuration, establish the connection manually from a shell window: telnet xx.xx.xx.xx 1433 or telnet xx.xx.xx.xx 1370.
Chapter 4: Configuring the technology pack Field Description collect_cdr If true, ProvisoCUCM requests CDR and CMR data from the CUCM server. If false, ProvisoCUCM will not poll the CUCM server for CDR and CMR data. Example: collect_cdr=true collect_perfmon If true, ProvisoCUCM requests Perfmon data from the CUCM server. If false, ProvisoCUCM will not poll the CUCM server for Perfmon data. Example: collect_perfmon=true cucm.host The IP address of the CUCM server associated with this properties file.
Chapter 4: Configuring the technology pack Field Description ftp.user User ID required for login to the DataChannel host that issued the SOAP request. Example: ftp.user=provisouser grace_period The time, in milliseconds, to subtract from the polling start time. The polling start time is the time that the ProvisoCUCM instance begins polling the CUCM server for data. The grace period is intended to help you avoid missing data files that the CUCM has not yet written for the current time period.
Chapter 4: Configuring the technology pack Field Description resend_sent_files If true, the CUCM server will re-send files that it has already successfully sent. Since the CUCM can be configured to send data files to any host specified by CUCM Web administration configuration settings, this field must be set to true to ensure that data files are also sent to the DataChannel host that requested them.
Chapter 4: Configuring the technology pack These configuration files contain sample values. Edit either or both files to assign values appropriate for locations in your Cisco IP Telephony CCM or CUCM environment. The following table describes the global variables to define: Variable Description CUSTOMERNAME String specifying the customer’s identifier. This value allows automatic grouping and report navigation by customer.
Chapter 4: Configuring the technology pack Variable Description site A variable assigned to the JavaScript object Site. A Site object defines a set of properties specific for a site, business department, location, remote office, or group of people. You can define multiple Site objects. Objects are distinguished through the site name you pass to the object. Create a Site object as follows: site = new Site("MySite"); In the example, MySite is the site name.
Chapter 4: Configuring the technology pack 11. Run the initial SNMP inventory and initiate a discovery. An inventory collects data about the network resources that the technology pack monitors. After you install an SNMP technology pack, you must create an inventory profile using the Inventory Tool Wizard and then initiate a discovery by executing the inventory profile using the Inventory Tool.
Chapter 4: Configuring the technology pack 12-f. Open a second terminal emulator. 12-g. On the DataChannel server, change your working directory to the DATA_CHANNEL_HOME/conf directory (/opt/datachannel/conf, by default), by entering the following command: cd DATA_CHANNEL_HOME/conf 12-h. Make a backup copy of the dc.cfg file, by entering the following command: cp dc.cfg dc.cfg.ORIG 12-i. In a text editor, open the dc.cfg file for editing. 12-j.
Chapter 4: Configuring the technology pack 14-f. Use the following commands to restart each DataChannel visual process: cnsw logw amgrw cmgrw 14-g. Use the dccmd command to start all DataChannel applications: dccmd -action start all 14-h.
Chapter 4: Configuring the technology pack 15. Ensure that the bulk input files can be read. To verify that the UBA application can read the bulk input files, follow these steps: 15-a. Place a bulk input file at the source input location. — (Tivoli Netcool/Proviso v4.4.3 and later) The source input location for bulk input files is specified using the URI parameter from the pack XSD file, which you can view using the Topology Editor. — (Tivoli Netcool/Proviso pre-v4.4.
Chapter 4: Configuring the technology pack Success message Meaning PERF_INPUT_PROCESSING Processed records in seconds ( records/minute): records Specifies a Bulk Adaptor Design File completion message. A Bulk Adaptor Design File successfully completes when an informational message similar to this one displays in the log file. Success occurs when records equals 0. METRIC_STREAM_INFO Completed writing metric output: DATA_CHANNEL_HOME/UBA..
Chapter 4: Configuring the technology pack where: Syntax item Meaning bulk_ Identifies this as a bulk inventory profile for a UBA technology pack. N Specifies the collector number (for example, 100) the user specified when configuring this UBA Bulk Collector. You must use the Inventory Tool to run a bulk inventory profile. To run the bulk inventory profile for this technology pack, perform the following steps: 16-a.
Chapter 4: Configuring the technology pack 17-f. Click Close to exit the message box, or click Details to view a description of any errors. 17-g. Optional: You can also deploy reports on a regular basis by creating a cron entry that makes use of the inventory CLI command and the -reportGrouping option. This option instructs the inventory command to run the report grouping rules and update the deployed reports stored in the database.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) This appendix provides UNIX reference pages for each of the pack-specific UBA parameters supplied with the XSD file for the Cisco IP Telephony Technology Pack. The descriptions are the same as those that display in the Topology Editor Help. These reference pages are provided for convenience. Overview The following pages provide a reference for the UBA parameters that this technology pack provides.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) INSTANCES Description Group alias. Component UBA Value Default: VOIP_CISCO_IPT_PERFMON Attribute: Read-only Location: Advanced Properties tab Detail The DataChannel supports multiple instances of technology packs running in a single channel component.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) INSTANCES Description Group alias. Component UBA Value Default: VOIP_CISCO_IPT Attribute: Read-only Location: Advanced Properties tab Detail The DataChannel supports multiple instances of technology packs running in a single channel component. Therefore, there must be a way to guarantee that the DataChannel applications that handle inventory and metrics parse the correct design files and read the appropriate Bulk input files.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) INSTANCES Description Group alias. Component UBA Value Default: VOIP_CISCO_IPT Attribute: Read-only Location: Advanced Properties tab Detail The DataChannel supports multiple instances of technology packs running in a single channel component. Therefore, there must be a way to guarantee that the DataChannel applications that handle inventory and metrics parse the correct design files and read the appropriate Bulk input files.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.CCMINPUT.DELETEONACQUIRE Description Deletes CCM Bulk input files after acquisition. Component UBA Value Default: false Attribute: Writable Location: Advanced Properties tab Detail The CCMINPUT.DELETEONACQUIRE parameter specifies whether the Bulk input files should be preserved after the UBA acquires them. A related parameter - CCMINPUT.URI - specifies the location of the Bulk input files.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.CCMINPUT.URI Description CCM Bulk input files location. Component UBA Value Default: No default value Attribute: Read-only Location: Properties tab Detail The DataChannel applications that handle inventory and metrics must be directed to the location of the Bulk input files generated by the devices associated with the technology on which the application operates. The CCMINPUT.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.CDRINPUT.DELETEONACQUIRE Description Deletes CUCM Bulk input files after acquisition. Component UBA Value Default: false Attribute: Writable Location: Advanced Properties tab Detail The CDRINPUT.DELETEONACQUIRE parameter specifies whether the Bulk input files should be preserved after the UBA acquires them. A related parameter - CDRINPUT.URI - specifies the location of these Bulk input files.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.CDRINPUT.URI Description CUCM Bulk input files location. Component UBA Value Default: No default value Attribute: Read-only Location: Properties tab Detail The DataChannel applications that handle inventory and metrics must be directed to the location of the Bulk input files generated by the devices associated with the technology on which the application operates. The CDRINPUT.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.DESIGNFILE Description JavaScript file that controls UBA for CCM or CUCM metrics. Component UBA Value Default: CUCMAdaptor.js Attribute: Read-only Location: Properties tab Detail Netcool/Proviso technology packs control the behavior of the DataChannel UBA application through instructions contained in Bulk Adaptor design (JavaScript) files.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.DESIGNFILE Description JavaScript file that controls UBA for CCM or CUCM metrics. Component UBA Value Default: CCMAdaptor.js Attribute: Read-only Location: Properties tab Detail Netcool/Proviso technology packs control the behavior of the DataChannel UBA application through instructions contained in Bulk Adaptor design (JavaScript) files.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.INPUT_DIRECTORY Description Path to Bulk input files directory for CCM or CUCM metrics. Component UBA Value Default: sqldb:odbc*threaded/username=user&password=passwd&environment=EXAMPLE Attribute: Writable Location: Properties tab Detail The INPUT_DIRECTORY parameter specifies the path to the directory where the generated Bulk input files should be stored.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.INPUT_DIRECTORY Description Path to Bulk input files directory for CCM or CUCM metrics. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_DIRECTORY parameter specifies the path to the directory where the generated Bulk input files should be stored. Do not enter any subdirectories and the actual wildcards used to specify the Bulk input files to be acquired.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.INPUT_FTP_PASSWORD Description FTP or SFTP password for Bulk input files used in CCM or CUCM environments. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_FTP_PASSWORD parameter specifies the password that the server administrator assigned (using the ftp or sftp utility) to the FTP or SFTP user.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.INPUT_FTP_USERNAME Description FTP or SFTP username for Bulk input files used in CCM or CUCM environments. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_FTP_USERNAME parameter specifies the username that the server administrator assigned (using the ftp or sftp utility) to the FTP or SFTP user.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.INPUT_HOST Description Hostname for Bulk input files in CCM or CUCM environments. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_HOST parameter specifies the hostname of the server on which the Bulk input files reside. These are the files that the UBA parses. IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.INPUT_HOST Description Hostname for Bulk input files in CCM or CUCM environments. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_HOST parameter specifies the hostname of the server on which the Bulk input files reside. These are the files that the UBA parses. 78 IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.INPUT_USE_SECURE_FTP Description Acquire CCM or CUCM Bulk input files using secure FTP. Component UBA Value Default: false Attribute: Writable Location: Properties tab Detail The INPUT_USE_SECURE_FTP parameter specifies whether FTP (File Transfer Protocol) or SFTP (secure FTP) is used. To use FTP, specify the value false. Otherwise, to use SFTP, specify the value true. The default value is false.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT.INPUT_USE_SECURE_FTP Description Acquire CCM or CUCM Bulk input files using secure FTP. Component UBA Value Default: false Attribute: Writable Location: Properties tab Detail The INPUT_USE_SECURE_FTP parameter specifies whether FTP (File Transfer Protocol) or SFTP (secure FTP) is used. To use FTP, specify the value false. Otherwise, to use SFTP, specify the value true. The default value is false.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT_PERFMON.DESIGNFILE Description JavaScript file that controls UBA for CUCM Perfmon metrics. Component UBA Value Default: CUCMPerfmonAdaptor.js Attribute: Read-only Location: Properties tab Detail Netcool/Proviso technology packs control the behavior of the DataChannel UBA application through instructions contained in Bulk Adaptor design (JavaScript) files.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT_PERFMON.INPUT_DIRECTORY Description Path to Bulk input files directory for CUCM Perfmon metrics. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_DIRECTORY parameter specifies the path to the directory where the generated Bulk input files should be stored.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT_PERFMON.INPUT_FTP_PASSWORD Description FTP or SFTP password for Bulk input files used for collecting Perfmon metrics in CUCM environments. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_FTP_PASSWORD parameter specifies the password that the server administrator assigned (using the ftp or sftp utility) to the FTP or SFTP user.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT_PERFMON.INPUT_FTP_USERNAME Description FTP or SFTP username for Bulk input files used for collecting Perfmon metrics in CUCM environments. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_FTP_USERNAME parameter specifies the username that the server administrator assigned (using the ftp or sftp utility) to the FTP or SFTP user.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT_PERFMON.INPUT_HOST Description Hostname for Bulk input files containing Perfmon metrics in CUCM environments. Component UBA Value Default: No default value Attribute: Writable Location: Properties tab Detail The INPUT_HOST parameter specifies the hostname of the server on which the Bulk input files reside. These are the files that the UBA parses. IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT_PERFMON.INPUT_USE_SECURE_FTP Description Acquire CUCM Perfmon Bulk input files using secure FTP. Component UBA Value Default: false Attribute: Writable Location: Properties tab Detail The INPUT_USE_SECURE_FTP parameter specifies whether FTP (File Transfer Protocol) or SFTP (secure FTP) is used. To use FTP, specify the value false. Otherwise, to use SFTP, specify the value true. The default value is false.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT_PERFMON.PERFMON.DELETEONACQUIRE Description Deletes CUCM Perfmon Bulk input files after acquisition. Component UBA Value Default: false Attribute: Writable Location: Advanced Properties tab Detail The PERFMON.DELETEONACQUIRE parameter specifies whether the Bulk input files should be preserved after the UBA acquires them. A related parameter - PERFMON.URI - specifies the location of these Bulk input files.
Appendix A: UBA parameters (Tivoli Netcool/Proviso v4.4.3 and later) VOIP_CISCO_IPT_PERFMON.PERFMON.URI Description CUCM Perfmon Bulk input files location. Component UBA Value Default: No default value Attribute: Read-only Location: Properties tab Detail The DataChannel applications that handle inventory and metrics must be directed to the location of the Bulk input files generated by the devices associated with the technology on which the application operates. The PERFMON.
Appendix B: Template file (Tivoli Netcool/Proviso pre-v4.4.3 only) You should read this appendix after you open the voip_cisco_ipt_sample_dc.cfg template file for editing, as instructed in Chapter 4, Configuring the technology pack. This appendix describes the pack-specific UBA parameters that you need to add to the dc.cfg file, and explains how to tailor the values to your specific deployment. Template file name and location The voip_cisco_ipt_sample_dc.
Appendix B: Template file (Tivoli Netcool/Proviso pre-v4.4.3 only) The following table describes the values that you must provide for these UBA parameters. UBA Parameter Value Meaning Replace with the channel number that was configured for this technology pack. This channel number appears in the dc.cfg file. Replace with the UBA Bulk Collector number that was configured for this technology pack. This collector number appears in the dc.cfg file.
Appendix B: Template file (Tivoli Netcool/Proviso pre-v4.4.3 only) URI The DataChannel UBA application needs to know where to find the bulk input files that the supported device generates. Therefore, you must specify a Universal Resource Identifier (URI) for the location of the bulk input files. To define this location, the Cisco IP Telephony Technology Pack provides a URI parameter in its voip_cisco_ipt_sample_dc.cfg template file.
Appendix B: Template file (Tivoli Netcool/Proviso pre-v4.4.3 only) • The UBA technology pack requires the DataChannel UBA application to process metrics only. In this scenario, the UBA technology pack provides a metrics schema in its design file. In this case, DB_USERNAME must be set to PV_COLL. • The UBA technology pack requires the DataChannel UBA application to process both inventory and metrics. In this scenario, the UBA technology pack provides metrics and inventory schemas in its design file.
Appendix B: Template file (Tivoli Netcool/Proviso pre-v4.4.3 only) UBA.1.101.VOIP_CISCO_IPT.CCMINPUT.DELETEONACQUIRE=false UBA.1.101.METRIC_STREAM_TYPE=BOF UBA.1.101.DEBUG_WALKBACK_ON_ADAPTOR_ERROR=TRUE UBA.1.101.DUAL_LOGGING=true UBA.1.101.LOG_FILTER=FEWI 12345 UBA.1.101.SERVICE_INSTANCE=GLOBAL UBA.1.101.COLLECTOR_LIST=101 UBA.1.101.DB_USERNAME=PV_GUI UBA.1.101.DB_PASSWORD=AAAC UBA.1.101.INVENTORY_SUBELEMENT_FLUSH_THRESHOLD=10 IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Appendix B: Template file (Tivoli Netcool/Proviso pre-v4.4.3 only) NOTES 94 IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information about the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
Notices Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.
Notices Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other product and service names might be trademarks of IBM or other companies. © Copyright IBM Corp. 2010. US Government Users Restricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Notices 98 IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.
Additional Copyright Information The following copyright information is for software used by Tivoli Netcool/Proviso. Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3 This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
Additional Copyright information DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. Various copyrights apply to this package, listed in 3 separate parts below. Please make sure that you include all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time.
Additional Copyright information • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. • The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission.
Additional Copyright information This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
Additional Copyright information 3. Neither the names of Networks Associates Technology, Inc, Cambridge Broadband Ltd., Sparta, Inc., Cisco, Inc, Beijing University of Posts and Telecommunications, Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission.
Additional Copyright information for loss of data, loss of profit, or any other damage resulting directly or indirectly from the use of the software, even if the damage is caused by defects in the software. 3. You may use this software in any applications you build. 4. You may distribute this software provided that the software documentation and copyright notices are included and intact. 5.
IBM ®
