Normally, all events that pass the input filter criteria are
both logged and written out to the system console. This can be
a problem if the console is being used interactively, for
example to configure the system. Therefore, this object can be
set to 'false(2)' to disable printing of the events as they
occur to the display. Instead, the user can display the event
log using explicit commands.
Parsed from file xsys.mib.txt
Company: None
Module: XEDIA-SYSTEM-MIB
Normally, all events that pass the input filter criteria are
both logged and written out to the system console. This can be
a problem if the console is being used interactively, for
example to configure the system. Therefore, this object can be
set to 'false(2)' to disable printing of the events as they
occur to the display. Instead, the user can display the event
log using explicit commands.
Parsed from file XEDIA-SYSTEM-MIB.mib
Module: XEDIA-SYSTEM-MIB
Vendor: Xedia Corporation
Module: XEDIA-SYSTEM-MIB
[Automatically extracted from oidview.com]
xsysEventDisplay OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Normally, all events that pass the input filter criteria are both logged and written out to the system console. This can be a problem if the console is being used interactively, for example to configure the system. Therefore, this object can be set to 'false(2)' to disable printing of the events as they occur to the display. Instead, the user can display the event log using explicit commands." DEFVAL { true } ::= { xsysEvents 10 }
xsysEventDisplay OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Normally, all events that pass the input filter criteria are both logged and written out to the system console. This can be a problem if the console is being used interactively, for example to configure the system. Therefore, this object can be set to 'false(2)' to disable printing of the events as they occur to the display. Instead, the user can display the event log using explicit commands." DEFVAL { true } ::= { xsysEvents 10 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.838.3.1.1.4.10.0 | xsysEventDisplay | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.838.3.1.1.4.1 | xsysEventTable | 1 | 7 | A table of events in the order that they were generated. An event may or may not be added to this (conceptual) table based on whe… |
| 1.3.6.1.4.1.838.3.1.1.4.2 | xsysEventMaxTableSize | 1 | 1 | The maximum number of events in the event log table. When the number of events exceeds this value, newer events continue to be ad… |
| 1.3.6.1.4.1.838.3.1.1.4.3 | xsysEventInFilterLevel | 1 | 1 | The current event input filter level. The user can choose to not log events of the lower levels, but they cannot filter out warni… |
| 1.3.6.1.4.1.838.3.1.1.4.4 | xsysEventOutFilterLevel | 1 | 1 | The current event output filter level. The output filter effects which entries are returned when the table is dumped (e.g., via a… |
| 1.3.6.1.4.1.838.3.1.1.4.5 | xsysEventOutFilterDateTime | 1 | 1 | The current event output filter level based on date/time. Only events with xsysEventDateTime at or after this date are returned. … |
| 1.3.6.1.4.1.838.3.1.1.4.6 | xsysEventSubsystemFilterTable | 1 | 3 | A table of filter information by subsystem. |
| 1.3.6.1.4.1.838.3.1.1.4.7 | xsysEventIdFilterTable | 1 | 5 | A table of filter information for each subsystem/id combination. |
| 1.3.6.1.4.1.838.3.1.1.4.8 | xsysEventsClearAllControl | 1 | 1 | Setting this object to 'execute(2)' removes all entries from the xsysEventTable. When read, this object always returns the value … |
| 1.3.6.1.4.1.838.3.1.1.4.9 | xsysEventsAsTraps | 1 | 1 | This object is used to control whether Xedia system events are sent as SNMP traps. Generally, it is not appropriate to send all e… |
| 1.3.6.1.4.1.838.3.1.1.4.11 | xsysEventsAsSyslogMessages | 1 | 1 | This object is used to control whether system events are sent as UNIX syslog messages. Generally, it is not appropriate to send a… |
| 1.3.6.1.4.1.838.3.1.1.4.13 | xsysEventSyslogRemoteServer | 1 | 1 | PTS FIX THIS - NEEDS DESCRIPTION HERE The address(es) of the remote host where a syslogd syslog daemon is running and awaits mess… |
| 1.3.6.1.4.1.838.3.1.1.4.14 | xsysEventNvRamMaxTableSize | 1 | 1 | The maximum number of warning and fatal level events could be stored to non-volatile memory and are relogged into event log upon … |