This variable contains a textual details of
the system log record.
Each log record contains :
1) a timestamp indicating when this event last occurred;
2) a 32-bit location number that uniquely identifies the
location in the software;
3) a 32-bit error number which provides additional
information to further identify the event;
4) a counter indicating the number of times that this
event occurred (and was not filtered);
5) a timestamp indicating when this event first occurred,
and the 'logIndexNumber' of that first event;
6) a 'specTrap' indication flag marking whether the
event has a specific Trap associated with it (the
trap may or may not have been sent);
7) a 'NORMALIZED' indication flag marking whether this
event record had a subsequent associated event that
normalized the original health-related event. If the
record is marked for item 7, then it also contains a
timestamp of this cancelling event. 'NORMALIZED'
events revert to 'non-NORMALIZED' if the event occurs
again (without a subsequent normalization). (Item 7
only applies to events that effect the 'health' of
the system).
8) a 'Radio' indication flag marking whether the
event indicates a radio or nmu event.
Items 1, 2, and 3 are always included in this variable
as '[mm/dd hh:mm:ss] L:llllllll E:eeeeeeee',
where: 1) 'mm/dd' indicate the month/day with 'hh:mm:ss'
as 'hour:minute:second'; 2) 'llllllll' is a hexadecimal
location; and 3) 'eeeeeeee' is a hexadecimal error number.
Item 8 if present causes the string 'RADIO' to be
concatenated to the previous string.
Item 7 if present causes the string
'NORMALIZED:[mm/dd hh:mm:ss]' (the timestamp of the
normalizing event) to be concatenated to the previous
string.
Items 4 and 5 are also included, if this log record
has been marked with multiple occurences. In such a
case, the string 'T times 1st:[mm/dd hh:mm:ss](N)' is
concatenated to the previous string(s). 'T' is a decimal
count of the number of occurences, and the additional
timestamp indicates when the first occurence was added
to the system log. '(N)' is the 'logIndexNumber' of
this first occurance.
Item 6 if present causes the string 'specTrap' to be
concatenated to the previous string(s).
The log record contains additional information that is
contained in the other mib variables, namely,
'logRecIndexNumber', 'logRecSeverity', and 'logRecEvent'.
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]
logRecDescription OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS mandatory DESCRIPTION "This variable contains a textual details of the system log record. Each log record contains : 1) a timestamp indicating when this event last occurred; 2) a 32-bit location number that uniquely identifies the location in the software; 3) a 32-bit error number which provides additional information to further identify the event; 4) a counter indicating the number of times that this event occurred (and was not filtered); 5) a timestamp indicating when this event first occurred, and the 'logIndexNumber' of that first event; 6) a 'specTrap' indication flag marking whether the event has a specific Trap associated with it (the trap may or may not have been sent); 7) a 'NORMALIZED' indication flag marking whether this event record had a subsequent associated event that normalized the original health-related event. If the record is marked for item 7, then it also contains a timestamp of this cancelling event. 'NORMALIZED' events revert to 'non-NORMALIZED' if the event occurs again (without a subsequent normalization). (Item 7 only applies to events that effect the 'health' of the system). 8) a 'Radio' indication flag marking whether the event indicates a radio or nmu event. Items 1, 2, and 3 are always included in this variable as '[mm/dd hh:mm:ss] L:llllllll E:eeeeeeee', where: 1) 'mm/dd' indicate the month/day with 'hh:mm:ss' as 'hour:minute:second'; 2) 'llllllll' is a hexadecimal location; and 3) 'eeeeeeee' is a hexadecimal error number. Item 8 if present causes the string 'RADIO' to be concatenated to the previous string. Item 7 if present causes the string 'NORMALIZED:[mm/dd hh:mm:ss]' (the timestamp of the normalizing event) to be concatenated to the previous string. Items 4 and 5 are also included, if this log record has been marked with multiple occurences. In such a case, the string 'T times 1st:[mm/dd hh:mm:ss](N)' is concatenated to the previous string(s). 'T' is a decimal count of the number of occurences, and the additional timestamp indicates when the first occurence was added to the system log. '(N)' is the 'logIndexNumber' of this first occurance. Item 6 if present causes the string 'specTrap' to be concatenated to the previous string(s). The log record contains additional information that is contained in the other mib variables, namely, 'logRecIndexNumber', 'logRecSeverity', and 'logRecEvent'. 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 4 }
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.2 | logRecSeverity | 0 | 0 | The severity level of the log record. 'critical' is the highest severity level, followed in decreasing order by 'major', 'minor',… |
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… |