SYSLOG-MSG-MIB
- Registered at
- 1.3.6.1.2.1.192
- Last updated
- 2009-08-13 08:00
- Organization
- IETF OPSAWG Working Group
- Revisions
- 2009-08-13 08:00
- Namespace
- standard
- Source file
SYSLOG-MSG-MIB- Digest
sha256:0a413f96a90eaa39139d23f71f271278ebfa384a3a13c688044523ddbc315c65
Description
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.
Contact
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Jacobs University Bremen Campus Ring 1 28757 Bremen Germany Alexander Clemm <alex@cisco.com> Cisco Systems 170 West Tasman Drive San Jose, CA 95134-1706 USA Anirban Karmakar <akarmaka@cisco.com> Cisco Systems India Pvt Ltd SEZ Unit, Cessna Business Park, Sarjapur Marathahalli ORR, Bangalore, Karnataka 560103 India
Imports
| From | Symbols |
|---|---|
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP |
| SNMPv2-SMI | MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso, mib-2 |
| SNMPv2-TC | DisplayString, TEXTUAL-CONVENTION, TruthValue |
| SYSLOG-TC-MIB | SyslogFacility, SyslogSeverity |
Imported by
Nothing in this corpus imports this module.
Load order
Every file a consumer needs in order to load this module, dependencies first.
SNMPv2-CONF SNMPv2-SMI SNMPv2-TC SYSLOG-MSG-MIB SYSLOG-TC-MIB
Textual conventions
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| SyslogParamValueString TEXTUAL-CONVENTION 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. | current | |||
| SyslogTimeStamp TEXTUAL-CONVENTION 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. | current |
Objects
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| syslogMsgNotifications OBJECT-IDENTITY | 1.3.6.1.2.1.192.0 | |||
| syslogMsgObjects OBJECT-IDENTITY | 1.3.6.1.2.1.192.1 | |||
| syslogMsgControl OBJECT-IDENTITY | 1.3.6.1.2.1.192.1.1 | |||
| syslogMsgTableMaxSize OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.1.1 | Unsigned32 | read-write | current |
| syslogMsgEnableNotifications OBJECT-TYPE Indicates whether syslogMsgNotification notifications are generated. The value of this object should be kept in nonvolatile memory. | 1.3.6.1.2.1.192.1.1.2 | TruthValue | read-write | current |
| syslogMsgTable OBJECT-TYPE A table containing recent SYSLOG messages. The size of the table is controlled by the syslogMsgTableMaxSize object. | 1.3.6.1.2.1.192.1.2 | not-accessible | current | |
| syslogMsgEntry OBJECT-TYPE An entry of the syslogMsgTable. | 1.3.6.1.2.1.192.1.2.1 | not-accessible | current | |
| syslogMsgIndex OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.2.1.1 | Unsigned32 (1..4294967295) | not-accessible | current |
| syslogMsgFacility OBJECT-TYPE The facility of the SYSLOG message. | 1.3.6.1.2.1.192.1.2.1.2 | SyslogFacility | read-only | current |
| syslogMsgSeverity OBJECT-TYPE The severity of the SYSLOG message | 1.3.6.1.2.1.192.1.2.1.3 | SyslogSeverity | read-only | current |
| syslogMsgVersion OBJECT-TYPE The version of the SYSLOG message. A value of 0 indicates that the version is unknown. | 1.3.6.1.2.1.192.1.2.1.4 | Unsigned32 (0..999) | read-only | current |
| syslogMsgTimeStamp OBJECT-TYPE The timestamp of the SYSLOG message. A zero-length string is returned if the timestamp is unknown. | 1.3.6.1.2.1.192.1.2.1.5 | SyslogTimeStamp | read-only | current |
| syslogMsgHostName OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.2.1.6 | DisplayString (SIZE(0..255)) | read-only | current |
| syslogMsgAppName OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.2.1.7 | DisplayString (SIZE(0..48)) | read-only | current |
| syslogMsgProcID OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.2.1.8 | DisplayString (SIZE(0..128)) | read-only | current |
| syslogMsgMsgID OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.2.1.9 | DisplayString (SIZE(0..32)) | read-only | current |
| syslogMsgSDParams OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.2.1.10 | Unsigned32 | read-only | current |
| syslogMsgMsg OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.2.1.11 | OCTET STRING | read-only | current |
| syslogMsgSDTable OBJECT-TYPE A table containing structured data elements of SYSLOG messages. | 1.3.6.1.2.1.192.1.3 | not-accessible | current | |
| syslogMsgSDEntry OBJECT-TYPE An entry of the syslogMsgSDTable. | 1.3.6.1.2.1.192.1.3.1 | not-accessible | current | |
| syslogMsgSDParamIndex OBJECT-TYPE 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. | 1.3.6.1.2.1.192.1.3.1.1 | Unsigned32 (1..4294967295) | not-accessible | current |
| syslogMsgSDID OBJECT-TYPE The name (SD-ID) of a structured data element. The SYSLOG protocol specification constrains this string to printable US-ASCII code points. | 1.3.6.1.2.1.192.1.3.1.2 | DisplayString (SIZE(1..32)) | not-accessible | current |
| syslogMsgSDParamName OBJECT-TYPE The name of a parameter of the structured data element. The SYSLOG protocol specification constrains this string to printable US-ASCII code points. | 1.3.6.1.2.1.192.1.3.1.3 | DisplayString (SIZE(1..32)) | not-accessible | current |
| syslogMsgSDParamValue OBJECT-TYPE The value of the parameter of a SYSLOG message identified by the index of this table. The value is stored in the unescaped format. | 1.3.6.1.2.1.192.1.3.1.4 | SyslogParamValueString | read-only | current |
| syslogMsgConformance OBJECT-IDENTITY | 1.3.6.1.2.1.192.2 | |||
| syslogMsgGroups OBJECT-IDENTITY | 1.3.6.1.2.1.192.2.1 | |||
| syslogMsgCompliances OBJECT-IDENTITY | 1.3.6.1.2.1.192.2.2 |
Notifications
| Name | OID | Status |
|---|---|---|
| syslogMsgNotification NOTIFICATION-TYPE 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. | 1.3.6.1.2.1.192.0.1 | current |
Conformance
| Name | OID | Status |
|---|---|---|
| syslogMsgNotificationGroup NOTIFICATION-GROUP The notifications emitted by this MIB module. | 1.3.6.1.2.1.192.2.1.1 | current |
| syslogMsgGroup OBJECT-GROUP A collection of objects representing a SYSLOG message, excluding structured data elements. | 1.3.6.1.2.1.192.2.1.2 | current |
| syslogMsgSDGroup OBJECT-GROUP A collection of objects representing the structured data elements of a SYSLOG message. | 1.3.6.1.2.1.192.2.1.3 | current |
| syslogMsgControlGroup OBJECT-GROUP A collection of control objects to control the size of the syslogMsgTable and to enable/disable notifications. | 1.3.6.1.2.1.192.2.1.4 | current |
| syslogMsgFullCompliance MODULE-COMPLIANCE The compliance statement for implementations of the SYSLOG-MSG-MIB. | 1.3.6.1.2.1.192.2.2.1 | current |
| syslogMsgReadOnlyCompliance MODULE-COMPLIANCE The compliance statement for implementations of the SYSLOG-MSG-MIB that do not support read-write access. | 1.3.6.1.2.1.192.2.2.2 | current |
| syslogMsgNotificationCompliance MODULE-COMPLIANCE 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. | 1.3.6.1.2.1.192.2.2.3 | current |