OID reference

snmpSyslogDeviceCompliance

1.3.6.1.4.1.89.82.1.4.2.1

Description

The compliance statement for devices that support sending system messages to a syslog collector.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.89.82.1.4.2 (snmpSyslogDeviceCompliances)
Node code: 1
Node name: snmpSyslogDeviceCompliance
Numeric OID: 1.3.6.1.4.1.89.82.1.4.2.1
URN notation: urn:oid:1.3.6.1.4.1.89.82.1.4.2.1

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 89 82 1 4 2 1}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rnd(89) rlSyslog(82) snmpSyslogDeviceMIB(1) snmpSyslogDeviceConformance(4) snmpSyslogDeviceCompliances(2) snmpSyslogDeviceCompliance(1)}

OID-IRI notation

/1/3/6/1/4/1/89/82/1/4/2/1
/ISO/Identified-Organization/6/1/4/1/89/82/1/4/2/1
/ISO/3/6/1/4/1/89/82/1/4/2/1

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/identified-organization/dod/internet/private/enterprises/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/identified-organization/dod/internet/private/ldap-enterprise/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/identified-organization/dod/internet/private/vendor-objects/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/org/dod/internet/private/enterprise/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/org/dod/internet/private/enterprises/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/org/dod/internet/private/ldap-enterprise/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/org/dod/internet/private/vendor-objects/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/iso-identified-organization/dod/internet/private/enterprise/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/iso-identified-organization/dod/internet/private/enterprises/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/iso-identified-organization/dod/internet/private/vendor-objects/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/iso-organization/dod/internet/private/enterprise/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/iso-organization/dod/internet/private/enterprises/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/iso-organization/dod/internet/private/ldap-enterprise/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance
/iso/iso-organization/dod/internet/private/vendor-objects/rnd/rlSyslog/snmpSyslogDeviceMIB/snmpSyslogDeviceConformance/snmpSyslogDeviceCompliances/snmpSyslogDeviceCompliance

Product context

Documented MIB packages

The NETGEAR catalogue lists MIB files containing this definition with these product and release labels:

MS510TX: 6.7.0.52
MS510TXPP: 6.7.0.52

These are catalogue release labels, not necessarily MIB revisions. A MIB definition does not establish that a device implements it or permits access.

Published definition

The displayed source records contain one distinct definition. Compare its source records.

snmpSyslogDeviceCompliance MODULE-COMPLIANCE
    STATUS  current
    DESCRIPTION
        "The compliance statement for devices that support sending
         system messages to a syslog collector."
    MODULE -- this module
    MANDATORY-GROUPS {
        snmpSyslogDeviceGroup,
        snmpSyslogCollectorGroup,
        snmpSyslogCollectorDefaultsGroup
    }

    GROUP       snmpSyslogApplicationGroup
    DESCRIPTION
        "The snmpSyslogApplication group is mandatory only for
         agents which support configuring the severity level of
         the messages that individual applications may generate."

    OBJECT      snmpSyslogCollectorUdpPort
    MIN-ACCESS  read-only
    DESCRIPTION
        "Write access is not required for implementations that
         do not support configuring the UDP port number on a
         per collector basis."

    OBJECT      snmpSyslogCollectorFacility
    MIN-ACCESS  read-only
    DESCRIPTION
        "Write access is not required for implementations that
         do not support configuring the syslog facility on a
         per collector basis."

    OBJECT      snmpSyslogCollectorSeverity
    MIN-ACCESS  read-only
    DESCRIPTION
        "Write access is not required for implementations that
         do not support configuring the message severity level
         on a per collector basis."

    OBJECT      snmpSyslogCollectorDefaultUdpPort
    MIN-ACCESS  read-only
    DESCRIPTION
        "Write access is not required for implementations that
         do not support configuring the UDP port number at all,
         or do not want to support a configurable default.
         Hopefully, it is only the later."

    OBJECT      snmpSyslogCollectorDefaultFacility
    MIN-ACCESS  read-only
    DESCRIPTION
        "Write access is not required for implementations that
         do not support configuring the syslog facility at all,
         or do not want to support a configurable default.
         Hopefully, it is only the later."
    OBJECT      snmpSyslogCollectorDefaultSeverity
    MIN-ACCESS  read-only
    DESCRIPTION
        "Write access is not required for implementations that
         do not support configuring the syslog facility at all,
         or do not want to support a configurable default.
         Hopefully, it is only the later."

    ::= { snmpSyslogDeviceCompliances 1 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The compliance statement for devices that support sending system messages to a syslog collector.

Sources for this description

NETGEAR official product and EOL MIB downloads

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1NETGEAR official product and EOL MIB downloads1 record · 1 source

Description 1

snmpSyslogDeviceCompliance · currentNETGEAR official product and EOL MIB downloads1 source

Status in source: current.

Names: snmpSyslogDeviceCompliance

Technical details

{
  "smi_kind": "MODULE-COMPLIANCE",
  "definition": [
    "snmpSyslogDeviceCompliance",
    "MODULE-COMPLIANCE",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The compliance statement for devices that support sending system messages to a syslog collector.\"",
    "MODULE",
    "MANDATORY-GROUPS",
    "{",
    "snmpSyslogDeviceGroup",
    ",",
    "snmpSyslogCollectorGroup",
    ",",
    "snmpSyslogCollectorDefaultsGroup",
    "}",
    "GROUP",
    "snmpSyslogApplicationGroup",
    "DESCRIPTION",
    "\"The snmpSyslogApplication group is mandatory only for agents which support configuring the severity level of the messages that individual applications may generate.\"",
    "OBJECT",
    "snmpSyslogCollectorUdpPort",
    "MIN-ACCESS",
    "read-only",
    "DESCRIPTION",
    "\"Write access is not required for implementations that do not support configuring the UDP port number on a per collector basis.\"",
    "OBJECT",
    "snmpSyslogCollectorFacility",
    "MIN-ACCESS",
    "read-only",
    "DESCRIPTION",
    "\"Write access is not required for implementations that do not support configuring the syslog facility on a per collector basis.\"",
    "OBJECT",
    "snmpSyslogCollectorSeverity",
    "MIN-ACCESS",
    "read-only",
    "DESCRIPTION",
    "\"Write access is not required for implementations that do not support configuring the message severity level on a per collector basis.\"",
    "OBJECT",
    "snmpSyslogCollectorDefaultUdpPort",
    "MIN-ACCESS",
    "read-only",
    "DESCRIPTION",
    "\"Write access is not required for implementations that do not support configuring the UDP port number at all, or do not want to support a configurable default. Hopefully, it is only the later.\"",
    "OBJECT",
    "snmpSyslogCollectorDefaultFacility",
    "MIN-ACCESS",
    "read-only",
    "DESCRIPTION",
    "\"Write access is not required for implementations that do not support configuring the syslog facility at all, or do not want to support a configurable default. Hopefully, it is only the later.\"",
    "OBJECT",
    "snmpSyslogCollectorDefaultSeverity",
    "MIN-ACCESS",
    "read-only",
    "DESCRIPTION",
    "\"Write access is not required for implementations that do not support configuring the syslog facility at all, or do not want to support a configurable default. Hopefully, it is only the later.\"",
    "::=",
    "{",
    "snmpSyslogDeviceCompliances",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The compliance statement for devices that support sending system messages to a syslog collector."
    ],
    null,
    [
      "ComplianceModules",
      [
        [
          null,
          [
            "snmpSyslogDeviceGroup",
            "snmpSyslogCollectorGroup",
            "snmpSyslogCollectorDefaultsGroup",
            "snmpSyslogApplicationGroup"
          ]
        ]
      ]
    ]
  ]
}

NETGEAR official product and EOL MIB downloads · Publisher's source file: Source package: MS510TX_TXPP_MIBS_V6.7.0.43.zip
Module: DRAFT-IETF-SYSLOG-DEVICE-MIB

See published definition above
Module imports
```
{'SNMPv2-TC': ['RowStatus', 'TEXTUAL-CONVENTION', 'TimeStamp'], 'RADLAN-MIB': ['rlSyslog'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32', 'Gauge32', 'snmpModules'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
```
· Download draft-ietf-syslog-device-mib.mib
Related source files and packages:
Show more related files and packages
Same file in MIB-6.5.1.22.zip.
Same file in XS728T_XS748T_mib_files.zip.
Same file in XS728T_XS748T_MIB_V6.5.1.59.zip.
Same file in XS728T_XS748T_MIB_V6.5.1.42.zip.

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.89)

Nethaniel Rina