The severity level of the log record.
'critical' is the highest severity level, followed in
decreasing order by 'major', 'minor', 'warning', and
'normal', which is the lowest severity level. These
severity levels can be further qualified with an
indication that the 'health' of the system is effected
because of this event. In such a case, these events
are indicated with the '-health' suffix (
'critical-health', 'major-health', 'minor-health',
'warning-health', 'normal-health').
Additionally, a health effecting event can be normalized
by an associated event. For example, on the Network
Management Unit, or NMU, the radio PPP link going down is
normalized by the radio PPP going up, and vice versa.
When a health effecting event is subsequently normalized
(and have no further subsequent occurance), then the
log record indicates this qualification with the
'-NORMALIZED' suffix as below:
'normal-NORMALIZED',
'warning-NORMALIZED',
'minor-NORMALIZED',
'major-NORMALIZED',
'critical-NORMALIZED'.
'other' indicates a class of log record, rather than
a severity level. The severity level of 'other' is
considered less important than 'normal'. 'other'
primarily is used to indicate a 'Debug' type of log
record.
Some log events have configurable severity levels.
Others have predetermined (non-configurable) severity
levels. At the time this log record was added, or
as it replaced another record, the 'logSeverityFilter'
allowed this event to be logged.
The retrieval of any variable of the 'logRecTable' is
effected by the viewing variables, which provide sorting,
filtering and page controls. These variables are:
'logViewPageSize',
'logViewPageControl',
'logViewSeverityFilter',
'logViewMethod',
'logViewDirection',
'logViewAge'.
Parsed from file WESTERN-MULTIPLEX-MIB.mib
Module: WESTERN-MULTIPLEX-MIB
Vendor: Western Multiplex
Module: WESTERN-MULTIPLEX-MIB
[Automatically extracted from oidview.com]
logRecSeverity OBJECT-TYPE SYNTAX INTEGER { normal(1), warning(2), minor(3), major(4), critical(5), normal-health(6), warning-health(7), minor-health(8), major-health(9), critical-health(10), normal-NORMALIZED(11), warning-NORMALIZED(12), minor-NORMALIZED(13), major-NORMALIZED(14), critical-NORMALIZED(15), other(50) } ACCESS read-only STATUS mandatory DESCRIPTION "The severity level of the log record. 'critical' is the highest severity level, followed in decreasing order by 'major', 'minor', 'warning', and 'normal', which is the lowest severity level. These severity levels can be further qualified with an indication that the 'health' of the system is effected because of this event. In such a case, these events are indicated with the '-health' suffix ( 'critical-health', 'major-health', 'minor-health', 'warning-health', 'normal-health'). Additionally, a health effecting event can be normalized by an associated event. For example, on the Network Management Unit, or NMU, the radio PPP link going down is normalized by the radio PPP going up, and vice versa. When a health effecting event is subsequently normalized (and have no further subsequent occurance), then the log record indicates this qualification with the '-NORMALIZED' suffix as below: 'normal-NORMALIZED', 'warning-NORMALIZED', 'minor-NORMALIZED', 'major-NORMALIZED', 'critical-NORMALIZED'. 'other' indicates a class of log record, rather than a severity level. The severity level of 'other' is considered less important than 'normal'. 'other' primarily is used to indicate a 'Debug' type of log record. Some log events have configurable severity levels. Others have predetermined (non-configurable) severity levels. At the time this log record was added, or as it replaced another record, the 'logSeverityFilter' allowed this event to be logged. The retrieval of any variable of the 'logRecTable' is effected by the viewing variables, which provide sorting, filtering and page controls. These variables are: 'logViewPageSize', 'logViewPageControl', 'logViewSeverityFilter', 'logViewMethod', 'logViewDirection', 'logViewAge'." ::= { logRecEntry 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3727.20.10.4.40.1.1 | logRecIndexNumber | 0 | 0 | When a log record is created or replaced, the 'logIndexNumber' is incremented, then stored within the new log record's 'logRecInd… |
| 1.3.6.1.4.1.3727.20.10.4.40.1.3 | logRecEvent | 0 | 0 | The type of event recorded in the log record. See the product release note for detailed explanations of these events. The retrieva… |
| 1.3.6.1.4.1.3727.20.10.4.40.1.4 | logRecDescription | 0 | 0 | This variable contains a textual details of the system log record. Each log record contains : 1) a timestamp indicating when this … |