Logging and event file

This configuration file holds the options for controlling the event handler, trace handling and alert suppression.

Filename:	LogEvent.cfg
Designated Editor:	ss7view (program)

Trace logging

The trace logging options define what information is written to the SS7-Trace file. In normal operation, the trace-to-text file is disabled, but can be enabled with the following options:

Trace = [<trace options>]

where the <trace options> are:

Info: Useful information relating to the passage of the program, such as activities in the internal state table.
Action: Typically logs information relating to entry to other functions.
Message: Logs detailed information about messages sent and received.
Subsystem: Details AIX system requests, for example creating shared memory.
Screen: Indicates that the log information should be sent to standard out and not to the trace file. This is only useful if SS7SigLib is being run from the command line.
Table: Details the outbound call allocation tables.
Function: Enables function and line reporting in the D7 Enablement package. This option does not affect the trace logging — SS7 Trace is not created or updated.

An example of the trace options would be:

Trace = Info Subsystem Function

Error options

Error=[<error options>]

where the error options are:

Screen: Indicates that the error information is to be sent to standard out as well as to the error file and Blueworx Voice Response. This is useful only if SS7SigLib is being run from the command line.

Event options

The following lines are used to control the event-capturing facility:

EventTrigger = <list>
EventTrigCmd = <valid shell command>
EventSize = <size>

EventTrigger=<list>

This defines which error events cause the current contents of the Event buffer to be written to disk file. Each item in the list consist of the following :

where WVRerror is the error number as passed to Blueworx Voice Response, in the range 30000-30199. The special error of ANY can be used to refer to any error events within the valid range. The <times> is the number of occurrences after which no further captures are generated. The <times> and the colon (:) can be omitted, in which case event files will continue to be issued.

An example would be EventTrigger = ANY: 3, 30000:4, 30020:2. This matches any error three times, error 30000 four times, and finally error 30020 twice. Note that if the first error detected by the system is 30020, this is handled under the ANY error as it is first in the list.

When an error trigger is detected, the EventTrigCmd is processed. This calls ss7view to copy the shared memory into disk file.

EventTrigCmd = <valid shell command>

This describes the command you should run when an event trigger has been detected. Typically this would call the ss7view command to copy the event shared memory to disk file. However, other commands can be substituted.

Note that the command is run in the background relative to SS7_D7 custom server, so does not delay the real-time execution. However, there is no monitoring of the program and over-triggering or badly chosen commands could result in the system running out of CPU and processing slots.

The command can utilize two substitutions to describe the event with the use of the %d parameter. The first %d is replaced with the Error number that triggered this capture and the second is replaced with the issue number.

An example would be:

EventTrigCmd 	= "ss7view –event R Events/Event-%d-%d"

This example shows the ss7view being run to copy the event-shared memory in raw mode into the file Events/Event-%d-%d. The first %d will be substituted with the error number that triggered this execution and the second %d is an incrementing issue number for this error.

EventSize = <size>

The default value for size is 300000. This defines the size of the shared memory block used to capture the events. The value refers to the number of events captured before wrapping around

AlertSupress=[*(<AlertNumber>,| <Alertnumber>-<Alertnumber>,)]

This option defines a number of alerts which are to be suppressed when an attempt is made to send to the Blueworx Voice Response reporting mechanism. The condition is still recorded in the SS7_D7 custom server error file.

The list of Alerts to suppress can be given as a list of single numbers or as ranges separated by commas. This suppress option works only for Alert in the range 30000-30499. An example would be: AlertSupress=30021, 30030-30035

Statistical Information

Stats = Off/Interval <interval> Buffer <buffer>

This controls the statistical collection option. <interval> defines how many seconds between collecting samples and <buffer> defines how many samples to remember.