Page: 1
blah
1HWFRRO,60
%DG6HUYLFH
$XWRPDWLRQ
Configuration
BUSINESS SOFTWARE SUPPORT LIMITED BAD SERVICE AUTOMATION CONFIGURATION
ISSUE 1.0 [20/04/00] Page 2 of
7DEOH RI &RQWHQWV
1. TABLE OF CONTENTS................................................................................................................................................. 2
2. INTRODUCTION............................................................................................................................................................ 3
3. CONFIGURATION......................................................................................................................................................... 4
3.1 NETCOOL/ISM RULES FILES........................................................................................................................................ 4
3.2 BADSERVICE AUTOMATION......................................................................................................................................... 5
3.3 GETSERVICESTATUS SCRIPT......................................................................................................................................... 6
BUSINESS SOFTWARE SUPPORT LIMITED BAD SERVICE AUTOMATION CONFIGURATION
ISSUE 1.0 [20/04/00] Page 3 of
,QWURGXFWLRQ
The SERVICE command is used in the Netcool/ISM rules files. By default its use is commented out.
The SERVICE command is used to define the status of a service before it is forwarded to the Object Server. The
status changes the color of the service status event when it is displayed in the event list and Service window.
The syntax of the SERVICE command is:
SERVICE (service_identifier, service_status)
Where
The service_identifier identifies the monitored service.
The service_status can be GOOD, BAD or MARGINAL;
BAD The service level agreement is not being met.
MARGINAL There are some problems with the service.
GOOD There are no problems with the service.
No Level Defined The status of the service is unknown.
BUSINESS SOFTWARE SUPPORT LIMITED BAD SERVICE AUTOMATION CONFIGURATION
ISSUE 1.0 [20/04/00] Page 4 of
&RQILJXUDWLRQ
1HWFRRO,60 5XOHV ILOHV
The Netcool/ISM rules files include a commented out service_name definition. By default this is very specific to
the host and type of service being monitored. In general it is not necessary to monitor all of these service
individually, but instead as a group. The simple way of doing this to set the service_name to the service, which is
of the form DNS, HTTP, FTP etc.
To implement these changes, edit each of the Netcool/ISM rules files and add the following line. The monitors will
need to be restarted for this change to take affect.
#$service_name = $service + " on " + $host + ":" + $port + " from " + $FQHostname
$service_name = $service
To do the same thing in a probes rules file, the following needs to be done;
$service_name = "PROBE_NAME"
if( match( @Manager, "ProbeWatch" ) )
{
switch(@Summary)
{
case "Running ...":
service($service_name, GOOD)
@Severity = 1
@AlertGroup = "probestat"
@Type = 2
case "Going Down ...":
service($service_name, MARGINAL)
@Severity = 5
@AlertGroup = "probestat"
@Type = 1
default:
service($service_name, MARGINAL)
@Severity = 1
}
@AlertKey = @Agent
@Summary = @Agent + " probe on " + @Node + ": " + @Summary
}
else
{
service($service_name, GOOD)
...}
BUSINESS SOFTWARE SUPPORT LIMITED BAD SERVICE AUTOMATION CONFIGURATION
ISSUE 1.0 [20/04/00] Page 5 of
%DG6HUYLFH $XWRPDWLRQ
The BadService automation is designed to monitor the status table in the service database. When a bad service is
reported the automation generates an alert in the status table in the alerts database. This provides the Netcool
operator with an event which they can then administer in the usual manner.
Trigger
select Name , LastBadAt, LastReportAt from service.status
where LastBadAt > (getdate - 300)
nand LastBadAt > LastGoodAt;
Action
insert into alerts.status values ('@Name BAD SERVICE',0,'','
','BAD SERVICE','','','',5,'@Name Bad Service reported',0,@LastBadAt,
@LastReportAt,0,0,0,10,0,0,'',0,10,0,0,'OBJECTSERVER',0,);
BUSINESS SOFTWARE SUPPORT LIMITED BAD SERVICE AUTOMATION CONFIGURATION
ISSUE 1.0 [20/04/00] Page 6 of
JHW6HUYLFH6WDWXV VFULSW
The getServiceStatus scripts was written as a command line interface into the status window provided by the
Netcool Event List Window.
#! /bin/sh
ARCH=solaris2
SERVER=OBJECTSERVER
USERNAME=read
PASSWORD=only
SYBASE=$OMNIHOME/platform/${ARCH}
export SYBASE COMMAND ARCH SERVER USERNAME PASSWORD
COMMAND="$OMNIHOME/bin/${ARCH}/isql -S$SERVER -U$USERNAME -P$PASSWORD -I$OMNIHOM
E/etc/interfaces.${ARCH} -w9999 -s :"
echo " Service Name Status"
echo " ------------ ------"
$COMMAND