SYSLOG-MSG-MIB
File:
SYSLOG-MSG-MIB.mib (21083 bytes)
Imported modules
Imported symbols
Defined Types
SyslogTimeStamp |
|
A date-time specification. This type is similar to the
DateAndTime type defined in the SNMPv2-TC, except the
subsecond granulation is microseconds instead of
deciseconds and a zero-length string can be used
to indicate a missing value.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8-10 microseconds* 0..999999
8 11 direction from UTC '+' / '-'
9 12 hours from UTC* 0..13
10 13 minutes from UTC 0..59
* Notes:
- the value of year is in network-byte order
- the value of microseconds is in network-byte order
- daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone
information (fields 11-13) is not present. |
TEXTUAL-CONVENTION |
|
|
|
|
OCTET STRING |
Size(0|10|13) |
|
SyslogParamValueString |
|
The value of a SYSLOG SD-PARAM is represented using the
ISO/IEC IS 10646-1 character set, encoded as an octet string
using the UTF-8 transformation format described in RFC 3629.
Since additional code points are added by amendments to the
10646 standard from time to time, implementations must be
prepared to encounter any code point from 0x00000000 to
0x7fffffff. Byte sequences that do not correspond to the
valid UTF-8 encoding of a code point or that are outside this
range are prohibited. Similarly, overlong UTF-8 sequences
are prohibited.
UTF-8 may require multiple bytes to represent a single
character / code point; thus, the length of this object in
octets may be different from the number of characters
encoded. Similarly, size constraints refer to the number of
encoded octets, not the number of characters represented by
an encoding. |
TEXTUAL-CONVENTION |
|
|
|
|
OCTET STRING |
|
|
SyslogMsgEntry |
|
SEQUENCE |
|
|
|
|
syslogMsgIndex |
Unsigned32 |
|
|
syslogMsgFacility |
SyslogFacility |
|
|
syslogMsgSeverity |
SyslogSeverity |
|
|
syslogMsgVersion |
Unsigned32 |
|
|
syslogMsgTimeStamp |
SyslogTimeStamp |
|
|
syslogMsgHostName |
DisplayString |
|
|
syslogMsgAppName |
DisplayString |
|
|
syslogMsgProcID |
DisplayString |
|
|
syslogMsgMsgID |
DisplayString |
|
|
syslogMsgSDParams |
Unsigned32 |
|
|
syslogMsgMsg |
OCTET STRING |
|
SyslogMsgSDEntry |
|
SEQUENCE |
|
|
|
|
syslogMsgSDParamIndex |
Unsigned32 |
|
|
syslogMsgSDID |
DisplayString |
|
|
syslogMsgSDParamName |
DisplayString |
|
|
syslogMsgSDParamValue |
SyslogParamValueString |
|
Defined Values
syslogMsgMib |
1.3.6.1.2.1.192 |
This MIB module represents SYSLOG messages as SNMP objects.
Copyright (c) 2009 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC 5676; see
the RFC itself for full legal notices. |
MODULE-IDENTITY |
|
|
|
syslogMsgTableMaxSize |
1.3.6.1.2.1.192.1.1.1 |
The maximum number of SYSLOG messages that may be held in
syslogMsgTable. A particular setting does not guarantee that
there is sufficient memory available for the maximum number
of table entries indicated by this object. A value of 0 means
no fixed limit.
If an application reduces the limit while there are SYSLOG
messages in the syslogMsgTable, the SYSLOG messages that are
in the syslogMsgTable for the longest time MUST be discarded
to bring the table down to the new limit.
The value of this object should be kept in nonvolatile
memory. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Unsigned32 |
|
|
syslogMsgEnableNotifications |
1.3.6.1.2.1.192.1.1.2 |
Indicates whether syslogMsgNotification notifications are
generated.
The value of this object should be kept in nonvolatile
memory. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
syslogMsgTable |
1.3.6.1.2.1.192.1.2 |
A table containing recent SYSLOG messages. The size of the
table is controlled by the syslogMsgTableMaxSize object. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
SyslogMsgEntry |
|
syslogMsgEntry |
1.3.6.1.2.1.192.1.2.1 |
An entry of the syslogMsgTable. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SyslogMsgEntry |
|
|
syslogMsgIndex |
1.3.6.1.2.1.192.1.2.1.1 |
A monotonically increasing number used to identify entries in
the syslogMsgTable. When syslogMsgIndex reaches the maximum
value (4294967295), the value wraps back to 1.
Applications periodically polling the syslogMsgTable for new
entries should take into account that a complete rollover of
syslogMsgIndex will happen if more than 4294967294 messages
are received during a poll interval. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
Unsigned32 |
1..4294967295 |
|
syslogMsgVersion |
1.3.6.1.2.1.192.1.2.1.4 |
The version of the SYSLOG message. A value of 0 indicates
that the version is unknown. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Unsigned32 |
0..999 |
|
syslogMsgTimeStamp |
1.3.6.1.2.1.192.1.2.1.5 |
The timestamp of the SYSLOG message. A zero-length
string is returned if the timestamp is unknown. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
SyslogTimeStamp |
|
|
syslogMsgHostName |
1.3.6.1.2.1.192.1.2.1.6 |
The hostname and the (optional) domain name of the SYSLOG
message. A zero-length string indicates an unknown hostname.
The SYSLOG protocol specification constrains this string to
printable US-ASCII code points. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..255) |
|
syslogMsgAppName |
1.3.6.1.2.1.192.1.2.1.7 |
The app-name of the SYSLOG message. A zero-length string
indicates an unknown app-name. The SYSLOG protocol
specification constrains this string to printable US-ASCII
code points. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..48) |
|
syslogMsgProcID |
1.3.6.1.2.1.192.1.2.1.8 |
The procid of the SYSLOG message. A zero-length string
indicates an unknown procid. The SYSLOG protocol
specification constrains this string to printable
US-ASCII code points. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..128) |
|
syslogMsgMsgID |
1.3.6.1.2.1.192.1.2.1.9 |
The msgid of the SYSLOG message. A zero-length string
indicates an unknown msgid. The SYSLOG protocol specification
constrains this string to printable US-ASCII code points. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(0..32) |
|
syslogMsgSDParams |
1.3.6.1.2.1.192.1.2.1.10 |
The total number of structured data element parameters
carried in the SYSLOG message. This number effectively
indicates the number of entries in the syslogMsgSDTable.
It can be used, for example, by a notification receiver
to determine whether a notification carried all
structured data element parameters of a SYSLOG message. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Unsigned32 |
|
|
syslogMsgMsg |
1.3.6.1.2.1.192.1.2.1.11 |
The message part of the SYSLOG message. The syntax does not
impose a size restriction. Implementations of this MIB module
may truncate the message part of the SYSLOG message such that
it fits into the size constraints imposed by the implementation
environment. Such truncations can also happen elsewhere in the
SYSLOG forwarding chain.
If the first octets contain the value 'EFBBBF'h, then the rest
of the message is a UTF-8 string. Since SYSLOG messages may be
truncated at arbitrary octet boundaries during forwarding, the
message may contain invalid UTF-8 encodings at the end. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
OCTET STRING |
|
|
syslogMsgSDTable |
1.3.6.1.2.1.192.1.3 |
A table containing structured data elements of SYSLOG
messages. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SEQUENCE OF |
|
|
|
|
SyslogMsgSDEntry |
|
syslogMsgSDEntry |
1.3.6.1.2.1.192.1.3.1 |
An entry of the syslogMsgSDTable. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
SyslogMsgSDEntry |
|
|
syslogMsgSDParamIndex |
1.3.6.1.2.1.192.1.3.1.1 |
This object indexes the structured data element parameters
contained in a SYSLOG message. The first structured data
element parameter has the index value 1, and subsequent
parameters are indexed by incrementing the index of the
previous parameter. The index increases across structured
data element boundaries so that the value reflects the
position of a structured data element parameter in a
SYSLOG message. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
Unsigned32 |
1..4294967295 |
|
syslogMsgSDID |
1.3.6.1.2.1.192.1.3.1.2 |
The name (SD-ID) of a structured data element. The SYSLOG
protocol specification constrains this string to printable
US-ASCII code points. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(1..32) |
|
syslogMsgSDParamName |
1.3.6.1.2.1.192.1.3.1.3 |
The name of a parameter of the structured data element. The
SYSLOG protocol specification constrains this string to
printable US-ASCII code points. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
DisplayString |
Size(1..32) |
|
syslogMsgSDParamValue |
1.3.6.1.2.1.192.1.3.1.4 |
The value of the parameter of a SYSLOG message identified by
the index of this table. The value is stored in the unescaped
format. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
SyslogParamValueString |
|
|
syslogMsgNotification |
1.3.6.1.2.1.192.0.1 |
The syslogMsgNotification is generated when a new SYSLOG
message is received and the value of
syslogMsgGenerateNotifications is true.
Implementations may add syslogMsgSDParamValue objects as long
as the resulting notification fits into the size constraints
imposed by the implementation environment and the notification
message size constraints imposed by maxMessageSize [RFC3412]
and SNMP transport mappings. |
Status: current |
Access: read-only |
NOTIFICATION-TYPE |
|
|
|
syslogMsgFullCompliance |
1.3.6.1.2.1.192.2.2.1 |
The compliance statement for implementations of the
SYSLOG-MSG-MIB. |
Status: current |
Access: read-only |
MODULE-COMPLIANCE |
|
|
|
syslogMsgReadOnlyCompliance |
1.3.6.1.2.1.192.2.2.2 |
The compliance statement for implementations of the
SYSLOG-MSG-MIB that do not support read-write access. |
Status: current |
Access: read-only |
MODULE-COMPLIANCE |
|
|
|
syslogMsgNotificationCompliance |
1.3.6.1.2.1.192.2.2.3 |
The compliance statement for implementations of the
SYSLOG-MSG-MIB that do only generate notifications and do not
provide a table to allow read access to SYSLOG message
details. |
Status: current |
Access: accessible-for-notify |
MODULE-COMPLIANCE |
|
|
|
syslogMsgNotificationGroup |
1.3.6.1.2.1.192.2.1.1 |
The notifications emitted by this MIB module. |
Status: current |
Access: accessible-for-notify |
NOTIFICATION-GROUP |
|
|
|
syslogMsgGroup |
1.3.6.1.2.1.192.2.1.2 |
A collection of objects representing a SYSLOG message,
excluding structured data elements. |
Status: current |
Access: accessible-for-notify |
OBJECT-GROUP |
|
|
|
syslogMsgSDGroup |
1.3.6.1.2.1.192.2.1.3 |
A collection of objects representing the structured data
elements of a SYSLOG message. |
Status: current |
Access: accessible-for-notify |
OBJECT-GROUP |
|
|
|
syslogMsgControlGroup |
1.3.6.1.2.1.192.2.1.4 |
A collection of control objects to control the size of the
syslogMsgTable and to enable/disable notifications. |
Status: current |
Access: accessible-for-notify |
OBJECT-GROUP |
|
|
|