Lucent Technologies Stinger, Administration Manual

Page: 92 / 374

3-10 Stinger® Administration Guide
Configuring logging, Syslog, and call logging services
Configuring system logging and Syslog services
index = 11
Configuring the Stinger unit Syslog facility
By configuring the Stinger unit to report events to a syslog host on the local IP
network, you can maintain a permanent log of events and send Call Detail Reporting
(CDR) reports to a host that can record and process them.
The host running a syslog daemon is typically a UNIX host, but it can also be a
Microsoft Windows system. If the log host is not on the same subnet as the Stinger
Parameter Specifies
log-type Type of log message saved— boot for boot log messages or run-
time for runtime log messages.
index Instance of a particular type of log entry (boot or runtime). This
value is incremented by 1 every time an instance of the type of
log occurs.
date
Date when the log was saved.
time Time when the log was saved.
level Level of the log message. Reported values can be one of the
following:
none —No log messages are saved or displayed.
emergency —Critical event has occurred; normal operation
is doubtful.
alert —Undesired event has occurred; normal operation
can probably continue.
critical —An interface is disabled or a security error has
occured.
error —Unexpected event has occured.
shelf
Shelf number on which the message was logged. Reported
values can be one of the following:
any-shelf —Special value used to specify any shelf.
shelf- n —Shelf number from 1 through 25.
slot
Slot number on which the message was logged. Reported
values are:
any-slot —Any slot.
slot- x —Slot number from 1 through 7 or 10 through 16.
first-control-module —The control module in slot 8.
second-control-module —The control module in slot 9.
trunk-module-1 —Trunk Module 1 pseudo slot.
trunk-module-2 —Trunk Module 2 pseudo slot.
control-module —The control module pseudo-slot. -STNGR
only
message
Log information. Text field, 255 characters