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'
Objects (39)
Showing 39 of 39 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.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
- SNMPv2-SMIrfc
- ENTERASYS-MIB-NAMESenterasys
- SNMPv2-TCrfc
- INET-ADDRESS-MIBrfc
- SNMPv2-CONFrfc
- SNMP-FRAMEWORK-MIBrfc
- 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)
Compliance Statements (5)
OID
.1.3.6.1.4.1.5624.1.2.14.4.2.1The compliance statement for devices that support sending
system messages to a syslog server.
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
| Object | Access | Syntax | Description |
|---|---|---|---|
| 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.2The compliance statement for devices that support sending
notifications upon specified syslog events.
notifications upon specified syslog events.
Required groups
| mandatory | etsysSyslogNotificationGroup |
OID
.1.3.6.1.4.1.5624.1.2.14.4.2.3The compliance statement for devices that support sending
system messages to a secure syslog file.
system messages to a secure syslog file.
Required groups
| mandatory | etsysSyslogSecureGroup |
OID
.1.3.6.1.4.1.5624.1.2.14.4.2.4The compliance statement for devices that support sending
system messages to a syslog server.
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
| Object | Access | Syntax | Description |
|---|---|---|---|
| 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.5The compliance statement for devices that support sending
system messages to a syslog server.
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
| Object | Access | Syntax | Description |
|---|---|---|---|
| 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)
| Name | OID | Description |
|---|---|---|
.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. |