ENTERASYS-SYSLOG-CLIENT-MIB

        This MIB module defines a portion of the SNMP enterprise
MIBs under the Enterasys enterprise OID pertaining to the
configuration of the generation of Syslog compatible
diagnostic messages for Extreme products.
    
Source file
ENTERASYS-SYSLOG-CLIENT-MIB
Last revised
Identity
etsysSyslogClientMIB
Base OID
1.3.6.1.4.1.5624.1.2.14
Imported Objects
ENTERASYS-MIB-NAMES etsysModules
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Gauge32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus TEXTUAL-CONVENTION (no object page) TimeStamp
Net-SNMP examples using the enterasys MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'ENTERASYS-SYSLOG-CLIENT-MIB' -M '/opt/observium/mibs/enterasys:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ENTERASYS-SYSLOG-CLIENT-MIB::etsysSyslogClientMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ENTERASYS-SYSLOG-CLIENT-MIB' -M '/opt/observium/mibs/enterasys:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ENTERASYS-SYSLOG-CLIENT-MIB::etsysSyslogClientMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (39)
.1.3.6.1.4.1.5624.1.2.14
.1.3.6.1.4.1.5624.1.2.14.1
.1.3.6.1.4.1.5624.1.2.14.1.1
.1.3.6.1.4.1.5624.1.2.14.1.2
.1.3.6.1.4.1.5624.1.2.14.1.3
Bits
.1.3.6.1.4.1.5624.1.2.14.1.4
.1.3.6.1.4.1.5624.1.2.14.1.5
.1.3.6.1.4.1.5624.1.2.14.2
Unsigned32
.1.3.6.1.4.1.5624.1.2.14.2.1
.1.3.6.1.4.1.5624.1.2.14.2.2
Unsigned32
.1.3.6.1.4.1.5624.1.2.14.2.3
.1.3.6.1.4.1.5624.1.2.14.2.4
.1.3.6.1.4.1.5624.1.2.14.2.4.1
Unsigned32
.1.3.6.1.4.1.5624.1.2.14.2.4.1.1
OctetString
.1.3.6.1.4.1.5624.1.2.14.2.4.1.10
OctetString
.1.3.6.1.4.1.5624.1.2.14.2.4.1.2
.1.3.6.1.4.1.5624.1.2.14.2.4.1.3
.1.3.6.1.4.1.5624.1.2.14.2.4.1.4
.1.3.6.1.4.1.5624.1.2.14.2.4.1.5
.1.3.6.1.4.1.5624.1.2.14.2.4.1.6
.1.3.6.1.4.1.5624.1.2.14.2.4.1.7
.1.3.6.1.4.1.5624.1.2.14.2.4.1.8
.1.3.6.1.4.1.5624.1.2.14.2.4.1.9
.1.3.6.1.4.1.5624.1.2.14.2.5
.1.3.6.1.4.1.5624.1.2.14.2.6
.1.3.6.1.4.1.5624.1.2.14.2.7
Enumeration
.1.3.6.1.4.1.5624.1.2.14.2.8
.1.3.6.1.4.1.5624.1.2.14.3
.1.3.6.1.4.1.5624.1.2.14.3.1
.1.3.6.1.4.1.5624.1.2.14.3.1.1
.1.3.6.1.4.1.5624.1.2.14.3.1.1.1
OctetString
.1.3.6.1.4.1.5624.1.2.14.3.1.1.2
OctetString
.1.3.6.1.4.1.5624.1.2.14.3.1.1.3
.1.3.6.1.4.1.5624.1.2.14.3.1.1.4
Bits
.1.3.6.1.4.1.5624.1.2.14.3.1.1.5
.1.3.6.1.4.1.5624.1.2.14.4
.1.3.6.1.4.1.5624.1.2.14.4.1
.1.3.6.1.4.1.5624.1.2.14.4.2
.1.3.6.1.4.1.5624.1.2.14.5
Dependencies (6) 6 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. ENTERASYS-MIB-NAMESenterasys
  3. SNMPv2-TCrfc
  4. INET-ADDRESS-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMP-FRAMEWORK-MIBrfc
  7. ENTERASYS-SYSLOG-CLIENT-MIBenterasysselected
Type Definitions (3)
Enumeration
local0(16)
local1(17)
local2(18)
local3(19)
local4(20)
local5(21)
local6(22)
local7(23)
Enumeration
emergency(1)
alert(2)
critical(3)
error(4)
warning(5)
notice(6)
info(7)
debug(8)
Unsigned32 range: 0..65535
Conformance Groups (8)
A collection of objects providing syslog message
statistics.
.1.3.6.1.4.1.5624.1.2.14.4.1.1
A collection of objects providing descriptions of
syslog servers for sending system messages to.
.1.3.6.1.4.1.5624.1.2.14.4.1.2
A collection of objects providing a mechanism to
control the severity level of the messages individual
application may generate.
.1.3.6.1.4.1.5624.1.2.14.4.1.3
A collection of objects providing default values for
the syslog servers that can optionally be overridden
on a per server basis with etsysSyslogServerFacility,
etsysSyslogServerSeverity, or etsysSyslogServerUdpPort.
.1.3.6.1.4.1.5624.1.2.14.4.1.4
A collection of supported notifications regarding syslog
events.
.1.3.6.1.4.1.5624.1.2.14.4.1.5
A collection of objects providing statistics and information
for syslog events that are associated with a secure file.
.1.3.6.1.4.1.5624.1.2.14.4.1.6
A collection of objects providing descriptions of
syslog servers for sending system messages to.
.1.3.6.1.4.1.5624.1.2.14.4.1.7
A collection of objects providing descriptions of
syslog servers for sending system messages to.
.1.3.6.1.4.1.5624.1.2.14.4.1.8
Compliance Statements (5)

OID .1.3.6.1.4.1.5624.1.2.14.4.2.1
The compliance statement for devices that support sending
system messages to a syslog server.
Required groups
mandatory etsysSyslogClientGroup
mandatory etsysSyslogServerGroup
mandatory etsysSyslogServerDefaultsGroup
optional etsysSyslogApplicationGroup The etsysSyslogApplication group is mandatory only for
agents which support configuring the severity level of
the messages that individual applications may generate.
Object refinements
ObjectAccessSyntaxDescription
etsysSyslogClientControl readonly
Write access is not required for implementations that
do not support configuring BOTH console AND persistent
logging. Implementations may choose to support only
a subset of the client controls. Sets which attempt
to modify unsupported controls should fail.
etsysSyslogServerUdpPort readonly
Write access is not required for implementations that
do not support configuring the UDP port number on a
per server basis.
etsysSyslogServerFacility readonly
Write access is not required for implementations that
do not support configuring the syslog facility on a
per server basis.
etsysSyslogServerSeverity readonly
Write access is not required for implementations that
do not support configuring the message severity level
on a per server basis.
etsysSyslogServerDefaultUdpPort readonly
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.
etsysSyslogServerDefaultFacility readonly
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.
etsysSyslogServerDefaultSeverity readonly
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.
etsysSyslogApplicationAllowedServers readonly
Write access is not required for implementations that
do not support configuring the syslog facility at all,
or do not support specification of allowable servers
per application.

OID .1.3.6.1.4.1.5624.1.2.14.4.2.2
The compliance statement for devices that support sending
notifications upon specified syslog events.
Required groups

OID .1.3.6.1.4.1.5624.1.2.14.4.2.3
The compliance statement for devices that support sending
system messages to a secure syslog file.
Required groups

OID .1.3.6.1.4.1.5624.1.2.14.4.2.4
The compliance statement for devices that support sending
system messages to a syslog server.
Required groups
mandatory etsysSyslogClientGroup
mandatory etsysSyslogServerGroup2
mandatory etsysSyslogServerDefaultsGroup
optional etsysSyslogApplicationGroup The etsysSyslogApplication group is mandatory only for
agents which support configuring the severity level of
the messages that individual applications may generate.
Object refinements
ObjectAccessSyntaxDescription
etsysSyslogClientControl readonly
Write access is not required for implementations that
do not support configuring BOTH console AND persistent
logging. Implementations may choose to support only
a subset of the client controls. Sets which attempt
to modify unsupported controls should fail.
etsysSyslogServerUdpPort readonly
Write access is not required for implementations that
do not support configuring the UDP port number on a
per server basis.
etsysSyslogServerFacility readonly
Write access is not required for implementations that
do not support configuring the syslog facility on a
per server basis.
etsysSyslogServerSeverity readonly
Write access is not required for implementations that
do not support configuring the message severity level
on a per server basis.
etsysSyslogServerDefaultUdpPort readonly
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.
etsysSyslogServerDefaultFacility readonly
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.
etsysSyslogServerDefaultSeverity readonly
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.
etsysSyslogApplicationAllowedServers readonly
Write access is not required for implementations that
do not support configuring the syslog facility at all,
or do not support specification of allowable servers
per application.

OID .1.3.6.1.4.1.5624.1.2.14.4.2.5
The compliance statement for devices that support sending
system messages to a syslog server.
Required groups
mandatory etsysSyslogClientGroup
mandatory etsysSyslogServerGroup3
mandatory etsysSyslogServerDefaultsGroup
optional etsysSyslogApplicationGroup The etsysSyslogApplication group is mandatory only for
agents which support configuring the severity level of
the messages that individual applications may generate.
Object refinements
ObjectAccessSyntaxDescription
etsysSyslogClientControl readonly
Write access is not required for implementations that
do not support configuring BOTH console AND persistent
logging. Implementations may choose to support only
a subset of the client controls. Sets which attempt
to modify unsupported controls should fail.
etsysSyslogServerUdpPort readonly
Write access is not required for implementations that
do not support configuring the UDP port number on a
per server basis.
etsysSyslogServerFacility readonly
Write access is not required for implementations that
do not support configuring the syslog facility on a
per server basis.
etsysSyslogServerSeverity readonly
Write access is not required for implementations that
do not support configuring the message severity level
on a per server basis.
etsysSyslogServerDefaultUdpPort readonly
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.
etsysSyslogServerDefaultFacility readonly
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.
etsysSyslogServerDefaultSeverity readonly
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.
etsysSyslogApplicationAllowedServers readonly
Write access is not required for implementations that
do not support configuring the syslog facility at all,
or do not support specification of allowable servers
per application.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.5624.1.2.14.5.1
Syslog security log archive notification. The device will send
this notification when the secure syslog file should be
archived offline.
.1.3.6.1.4.1.5624.1.2.14.5.2
Syslog secure messages dropped notification. The device will
send this notification when messages that are required to be
sent to the secure syslog file are dropped, failing to record
those events.