The Tivoli Netcool Performance Manager IBM Tivoli Monitoring agents do not contain alarm definitions.
Alarm definitions can be added to the agents as the customer sees fit. For details on how to configure situation for agents on IBM Tivoli Monitoring with action to generate alarm, refer to Manage Situation and Take Action sections in IBM Tivoli Monitoring documentation.
Tivoli Netcool Performance Manager provides a portable package that enables the generation of internal Tivoli Netcool Performance Manager alarms from the
command line on a non Tivoli Netcool Performance Manager core server. The most suitable method of handling alarms depends on the existing application
infrastructure:
v Customer already has IBM Tivoli Monitoring and Netcool/OMNIbus
v Customer has Netcool/OMNIbus and other non-IBM IT monitoring solutions v Customer does not have Netcool/OMNIbus or IBM Tivoli Monitoring v Customer has IBM Tivoli Monitoring but other non-IBM Fault Management
solution
Existing application infrastructure
The existing application structure.
Customer already has IBM Tivoli Monitoring and Netcool/OMNIbus
In this case, the Tivoli Netcool Performance Manager agents can be integrated into the customer's existing IBM Tivoli Monitoring Infrastructure. It is possible that the customer already has IBM Tivoli Monitoring / Netcool/OMNIbus integration configured.
Customer has Netcool/OMNIbus and other non-IBM IT monitoring solutions
In this case, a single-server IBM Tivoli Monitoring solution would be deployed to monitor the Tivoli Netcool Performance Manager servers only.
The alarms that are generated by this IBM Tivoli Monitoring deployment can be directly integrated into the customer's Netcool/OMNIbus system through the existing Tivoli EIF probe.
Customer does not have Netcool/OMNIbus or IBM Tivoli Monitoring
In this case, a single-server IBM Tivoli Monitoring solution would again be deployed to monitor the Tivoli Netcool Performance Manager servers.
Tivoli Netcool Performance Manager internal alarms can be generated using the alarm package. The standard Tivoli Netcool Performance Manager alarm export functions can be used to forward these alarms to external systems, for example through email or SNMP.
Customer has IBM Tivoli Monitoring but other non-IBM Fault Management solution
In this case, the custom Tivoli Netcool Performance Manager agents can be integrated into the customer's existing IBM Tivoli Monitoring infrastructure.
The customer already has IBM Tivoli Monitoring integration that is configured with an external non-IBM fault management system.
Generating the alarm package
Instructions on how to generate the package.
Procedure
1. Run the following as user virtuo:
$WMCROOT/admin/common/install/scripts/create_alarmgenerator_package -wmcr $WMCROOT The package that is created is /appl/virtuo/admin/itm/pkg/
tnpmw_alarm_generator.tar.
2. Copy the generated package to the server where alarm is required. The alarm is generated from the agents.
Note: The package includes the password that is provided in the database configuration. If this password is not encoded, then the plain text password is readable on the target server.
3. Extract the archive on the target server. The following folders are created:
v bin - contains the alarm_generator file
v conf- contains the file vtdb.properties that can be configured for database connection information.
v lib - contains the necessary .jar files.
4. To generate an alarm from the target server, run the following command:
<package_loc>/bin/alarm_generator -g <notification_id>
Table 3. Alarm generator parameters Parameter
CLI
format PL-SQL format Description Default notification_id Integer INTEGER Alarm notification Id. None.
Table 3. Alarm generator parameters (continued) Parameter
CLI
format PL-SQL format Description Default
ev_source String VARCHAR2(255) Event/Alarm source. None.
ev_type String VARCHAR2(255) Event type, see Event types . None.
monitored_attribute String NUMBER Attribute value that triggered the alarm, for example 51.3.
None.
managed_object_class String VARCHAR2(255) Entity name, for example cell. None.
managed_object_
instance
String VARCHAR2(255) Entity instance name/local key, for example 12345.
None.
alarm_predicate String VARCHAR2(255) Alarm predicate. None.
probable_cause String VARCHAR2(255) Probable alarm cause, see Probable causes .
None.
specific_problem String VARCHAR2(255) Specific alarm problem. None.
additional_text String VARCHAR2(255) Any additional text. None.
trend_indication String VARCHAR2(255) 'more severe' (raised) or 'less Severe' (cleared), see Trend Indications .
None.
report_id Integer NUMBER Associated report Id, which is given as alarmapi_admin -r.
None.
alarm_severity String VARCHAR2(255) Alarm severity, see Severity . None.
event_time String:
yyyy MMdd HHmm ss.
DATE Optional. Alarm time. When the alarm reflects a past event, it must be set to the event time.
If not provided, it is assumed to be the current time.
Current time.
Note: IBM Tivoli Monitoring actions can be configured to call the script to generate internal Tivoli Netcool Performance Manager alarms. You can type the full path of the alarm_generator script with the required parameters mentioned in step 4 at the system command in the action screen.
Note: The alarm spool daemon asd sap process must be running to raise alarms in Tivoli Netcool Performance Manager. The daemon is started and stopped, as user virtuo with the commands sap start asd and sap stop asd.
Note: The script requires JavaTM Runtime Environment (JRE) version 1.6.0.
The PATH set in the environment must use the 1.6.0 version of Java.
Parameter values - lists
A number of parameters have defined values, including:
v Event types v Probable causes v Trend Indications v Severity
Event types
It is possible that the Tivoli Netcool Performance Manager accepts non-standard values, but alarms with non-standard values cannot be forwarded to SNMP recipients, such as Tivoli Netcool OMNIbus.
The following table lists all the possible values for event types.
Table 4. Event type Event type
Lists all the possible values for probable_cause.
Table 5. Probable Causes
Probable cause Probable cause
adapterError lossOfRedundancy
Table 5. Probable Causes (continued)
Probable cause Probable cause
congestion payloadTypeMismatch
Table 5. Probable Causes (continued)
Probable cause Probable cause
framingError softwareErrorX733
List of all the possible values for trend_indication.
Table 6. Trend Indication Trend Indication More Severe Less Severe No Change
Severity
List of all the possible values for alarm_severity.
Table 7. Severity values Severity
Cleared Indeterminate Critical Major Minor Warning
Chapter 7. Tivoli Netcool Performance Manager agent metrics and IBM Tivoli Monitoring navigation layout
This section describes the metrics that are collected for each Tivoli Netcool Performance Manager agent, the log files used, and the default IBM Tivoli Monitoring navigation layout.
This section describes:
v Loader metrics and navigation layout
v Application server metrics and navigation layout v Gateway server metrics and navigation layout
Loader metrics and navigation layout
This section details the loader metrics and navigation layout.
Loader agent log files
The list of loader agent log files.
The default log file directory on the Tivoli Netcool Performance Manager loader logs is $WMCROOT/logs/loader.
The IBM Tivoli Monitoring agent for Tivoli Netcool Performance Manager loaders has the following attributes:
v Loader Name
v Technology Pack Name v Technology Pack Version v Reporting Start Time v Reporting End Time v Reporting Duration v Interval Start Time v Interval End Time v Interval Duration
v File Processing Start Time v File Processing End Time v File Processing Duration v Number of LIF files processed v Total Size of LIF files processed
v Number of LIF files successfully processed v Percentage LIF files successfully processed v Number of LIF files unsuccessfully processed v Percentage LIF files unsuccessfully processed
v Minimum Latency - the time between Interval End Time and File Processing Start Time
v Maximum Latency - the time between Interval End Time and File Processing End Time
v Late - "Yes" if Maximum Latency is greater than Interval Duration. "No"
otherwise.
Default IBM Tivoli Monitoring navigation layout
Default IBM Tivoli Monitoring navigation layout.
An example default navigation layout is as follows:
Enterprise UNIX Systems
<<Hostname>>
Tivoli Netcool Performance Manager Loaders
<<Instance Name, e.g. technology pack>>
File Processing
To configure IBM Tivoli Monitoring workspaces, refer to the IBM Tivoli Monitoring product documentation.
Default Loader workspace
The default workspace for the Tivoli Netcool Performance Manager application Loaders item in the IBM Tivoli Monitoring Navigator contains four frames in addition to the default Navigator frame.
The structure is as follows:
v Stacking bar chart displays the loader file processing, aggregated for all technology packs on the system:
– LIF files successfully processed – LIF files unsuccessfully processed
v Bar chart showing maximum data latency, aggregated for all tech packs on the system:
– File Processing Latency
v Table showing main loader file processing attributes:
– Loader Name
– Technology Pack Name – Technology Pack Version – Reporting Start Time – Interval Start Time – File Processing Start Time
– Number of LIF Files Successfully Processed – Percentage of LIF Files Successfully Processed – Number of LIF Files Unsuccessfully Processed – Percentage of LIF Files Unsuccessfully Processed v Table showing loader data latency attributes:
– Loader Name – Tech Pack Name – Tech Pack Version – Interval Start Time – File Processing Duration – Minimum Latency – Maximum Latency – Late
The corresponding cell within the file processing and latency tables is red for the following conditions:
v Table showing main loader file processing attributes:
– Number of LIF Files Successfully Processed = 0 – Number of LIF Files Unsuccessfully Processed > 1 v Table showing loader data latency attributes:
– Late is set to 'Yes'
Default technology pack workspace
The default workspace for a technology pack that is selected beneath a loader contains four frames in addition to the default Navigator frame.
The structure is as follows:
v Bar chart displays:
– Total number of LIF files processed – LIF files successfully processed – LIF files unsuccessfully processed v Bar chart displays:
– File Processing Latency
v Table showing loader file processing attributes:
– Loader Name
– Technology Pack Name – Technology Pack Version – Reporting Start Time – Interval Start Time – File Processing Start Time
– Number of LIF files Successfully Processed – Percentage of LIF Files Successfully Processed – Number of LIF files unsuccessfully processed – Percentage of LIF Files Unsuccessfully Processed v Table showing loader data latency attributes:
– Loader Name
– Technology Pack Name – Technology Pack Version – Interval Start Time – File Processing Duration – Minimum Latency – Maximum Latency – Late
The corresponding cell within the file processing and latency tables is red for the following conditions:
v Table showing main loader file processing attributes:
– Number of LIF Files Successfully Processed = 0 – Number of LIF Files Unsuccessfully Processed > 1 v Table showing loader data latency attributes:
– Late is set to 'Yes'
Application server metrics and navigation layout
This section describes the application server metrics and navigation layout.
Application server agent log files
The list of application server agent log files.
The default log file directory on the Tivoli Netcool Performance Manager application server is $WMCROOT/logs/itm.
It contains the following logs:
Table 8. Application server log files
Log Description
Usage
Usage information:
v Time interval
v Maximum number of user sessions v Number of active users
v Number of scheduled reports run v Number of ad hoc reports run
Table 8. Application server log files (continued)
Log Description
Reports
For each report run, the following is logged:
v Report Id v Report Name v Report Folder
v Report Type - ad hoc or scheduled.
v User - user that ran or scheduled the report.
v Roles - the user's roles.
v Groups - the user's groups.
v Start Time - either the scheduled start time or the time a user ran an Immediate report
v Actual Start Time - the time the report was started by the system. This can be different on a busy system.
v Actual End Time - the end time.
v Preparation Time - the length of time from the actual start time to just before the Reap query.
v Resolution Time - the length of time the Reap query takes
v Execution Time - the length of time the final report calculation takes.
v Number of Entities - the number of entities that are returned by the Reap query, not necessarily the same as the number in the final report.
v Number of KPIs - the number of KPIs requested.
v Number of Rows - the number of rows that are returned by the report, including roll ups.
v Time Interval Raw data coverage
Raw data coverage information:
v Timestamp v Vendor v Technology v KPI
v Rollup Node Name v Percent complete
Table 8. Application server log files (continued)
Log Description
Busy hour execution
Busy hour execution information:
v Busy Hour Name v Start Time v End Time v Duration
v Type (Daily, Weekly, Monthly) v Result
v Number of rows Busy hour completion
Busy hour completion information:
v Timestamp (Date / Time) v Total number of Busy Hours v Number of Busy Hours complete v % Busy Hours complete
Summary execution
v Type (Hourly, Weekly, Monthly) v Result
v Number of rows Summary completion
Summary completion information:
v Timestamp (Date / Time) v Total number of Summaries v Number of Summaries complete v % Summaries complete
Default IBM Tivoli Monitoring navigation layout
An example of the default navigation layout is as follows:
Enterprise UNIX Systems
<<Hostname>>
Tivoli Netcool Performance Manager Application Server Usage
Reports Coverage
To configure IBM Tivoli Monitoring workspaces, refer to your IBM Tivoli Monitoring product documentation.
The default workspace that opens when the Tivoli Netcool Performance Manager application item is selected in the IBM Tivoli Monitoring Navigator contains four frames in addition to the default Navigator frame, as follows:
v Bar chart that displays the report execution metrics (top 10)
v Bar chart that displays the vendor raw data coverage (aggregated) v Table that displays the user session information
– Time Interval
– Maximum number of user sessions – Number of active users
– Number of scheduled reports run – Number of ad hoc reports run
v Table that displays the data coverage attributes (row per node) – Timestamp
– Vendor Technology – KPI
– Rollup Node Name – Percent complete
Usage
The default workspace for Usage contains one frame in addition to the default Navigator frame.
The structure is as follows:
v Table displays usage attributes:
– Time Interval
– Maximum number of user sessions – Number of active users
– Number of scheduled reports run – Number of ad-hoc reports run
The corresponding cell within the data coverage table is red for the following condition:
Table displays main data coverage attributes -v % Complete < 95
Reports
The default workspace for Reports contains five frames in addition to the default Navigator frame.
The structure is as follows:
v Bar chart that displays the ad hoc report attributes (top 10) v Bar chart that displays the scheduled report attributes (top 10) v Bar chart that displays the average report execution times v Table that displays the user session attributes
v Table that displays the report execution attributes
Coverage
The default workspace for Coverage contains three frames in addition to the default Navigator frame.
The structure is as follows:
v Bar chart displays the vendor raw data coverage metrics
– Timestamp (Date / Time) – Total number of Busy Hours – Number of Busy Hours complete – % Busy Hours complete
v Table displays the summary percent completion:
– Timestamp (Date / Time) – Total number of Busy Hours – Number of Busy Hours complete – % Busy Hours complete
v Table displays the busy hour data coverage metrics:
– Busy Hour Name – Start Time – End Time – Duration
– Type (Daily, Weekly, Monthly) – Result
– Number of rows
v Table displays the summary data coverage metrics:
– Summary Name – Start Time – End Time – Duration
– Type (Daily, Weekly, Monthly) – Result
– Number of rows
Using IBM Tivoli Monitoring threshold definitions, cells within the busy hour execution table are red for the following conditions:
v Number of rows = 0 AND Result != 'Completed'
Using IBM Tivoli Monitoring threshold definitions, cells within the summary execution table are red for the following conditions:
v Number of rows = 0 AND Result == 'failed'
Gateway server metrics and navigation layout
This section describes the gateway server metrics and navigation layout.
Gateway agent log files
The location of gateway agent log files and the list of available attributes.
The default log file directory on the Tivoli Netcool Performance Manager gateways logs is $WMCROOT/logs/itm.
The IBM Tivoli Monitoring agent for Tivoli Netcool Performance Manager gateways logs the following attributes:
v Gateway
v Transfer IN/OUT
v Parser
Gateway
The information that is logged for the gateway.
The following information is logged for the gateway:
v Vendor subsystem (for example, nokia-utran) v Vendor Release (for example, 6.0)
v Gateway PID
v Gateway Stages including the duration for:
– TRANSFER-IN – PARSER
– TRANSFER-OUT
v Period of Execution (crontab) v Execution Start Time
v Execution End Time
v Status: Normal Exit or Aborted/Killed
Transfer IN/OUT
The information that is logged for the Transfer parts of the gateway.
The following information is logged for the Transfer parts of the gateway:
v Vendor subsystem (for example, nokia-utran) v Vendor Release (for example, 6.0)
v Gateway PID v Transfer Rule Name v Transfer Type: IN or OUT
v Transfer Protocol (FTP, SCP, RCP, CP) v Transfer Host (IP)
v Transfer Start Time v Transfer End Time
v Number of files transferred v Total Size of files transferred v Maximum file size
Tivoli Netcool Performance Manager gateways agents can be configured to log per-file information. If configured, the following per-file information is logged:
v In File Name v In File Size
v In file name Time Stamp (if available from source) v File Processing Start Time
v File Processing End Time v Out File Name
v Out File Size
Parser
The information logged for the parser part of the gateway.
v Vendor SubSystem (e.g. nokia-utran) v Vendor Release (e.g. 6.0)
v Gateway PID v Engine Rule Name v Engine Start Time v Engine End Time
v Number of input files processed v Total Size of input files processed v Number of PIF files produced v Total Size of PIF files produced v Number of LIF files produced v Total Size of LIF files produced
Tivoli Netcool Performance Manager gateways agents can be configured to log per-file information. If configured, the following per-file information is logged:
v Input File Name v Input File Size
v Input Filename Time Stamp (if available from source) v File Processing Start Time
v File Processing End Time
v Out File Name(s) : PIFs and LIFs v Out File(s) Size
Default IBM Tivoli Monitoring navigation layout
An example of the default navigation layout is as follows:
Enterprise UNIX Systems
<<Hostname>>
Tivoli Netcool Performance Manager Gateways
<<Instance Name, e.g. vendor subsystem>>
Gateway Parser Transfer
To configure IBM Tivoli Monitoring workspaces, refer to your IBM Tivoli Monitoring product documentation.
Default Gateways workspace
The default workspace for the Tivoli Netcool Performance Manager application Gateways item in the IBM Tivoli Monitoring Navigator contains three frames in addition to the default Navigator frame.
The structure is as follows:
v Stacked bar chart that displays the gateway phase durations, aggregated for all vendor subsystems on the system:
– Transfer IN – Parser – Transfer OUT
v Table that displays the main file transfer attributes (for all gateways, all vendor subsystems):
– Vendor subsystem Name – Vendor Release
– Transfer Rule Name – Transfer Type (IN/OUT) – Transfer Start Time – Transfer End Time
– Number of Files Transferred
v Table that displays the main PIF and LIF file processing attributes (for all gateways, all vendor subsystems):
– Vendor subsystem Name – Vendor Release
– Engine Rule Name – Engine Start Time – Engine End Time
– Number of PIF Files Produced – Number of LIF Files Produced
The corresponding cell within the attributes table is red for the following conditions:
v Number of Files Transferred IN = 0 v Number of Files Transferred OUT = 0 v Number of LIF Files Produced = 0
Individual instance
The default workspace for an individual Gateways instance contains three frames in addition to the default Navigator frame.
The structure is as follows:
v Line chart that displays the following:
– # Files Transferred IN – # LIF Files Generated
v Table that displays transfer attributes (for all gateways that are monitored by that agent):
– Vendor subsystem Name – Vendor Release
– Transfer Rule Name – Transfer Type (IN/OUT) – Transfer Start Time
– Transfer Rule Name – Transfer Type (IN/OUT) – Transfer Start Time