All MIBs › CXEventManager-MIB › cxEvmLogFileEvLogFilter
cxEvmLogFileEvLogFilter
Module: CXEventManager-MIB
OID (symbolic): CXEventManager-MIB::cxEvmLogFileEvLogFilter
OID (numeric): 1.3.6.1.4.1.495.2.1.5.17.8.1.6
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
Description: This field consists of 2 hexadecimal octets. The value represents a bit field used to determines which events are to be filtered out according to their event type. Each bit in this object is mapped to a specific event type. Turning a bit off (0) causes the associated events to be filtered out. Setting a bit to 1 will allow the event manager process to log the event message received.
- bit 0: error type (0: filter out, 1:log event) - bit 1: warning type (0: filter out, 1:log event) - bit 2: status type (0: filter out, 1:log event) - bit 3: trace type (0: filter out, 1:log event) - bit 4: user1 type (0: filter out, 1:log event) - bit 5: user2 type (0: filter out, 1:log event) - bit 6: user3 type (0: filter out, 1:log event) - bit 7: user4 type (0: filter out, 1:log event) - bit 8: user5 type (0: filter out, 1:log event) - bit 9: user6 type (0: filter out, 1:log event) - bit 10: user7 type (0: filter out, 1:log event) - bit 11: user8 type (0: filter out, 1:log event) - bit 12: user9 type (0: filter out, 1:log event) - bit 13: user10 type (0: filter out, 1:log event) - bit 14: user11 type (0: filter out, 1:log event) - bit 15: user12 type (0: filter out, 1:log event)
Range of Values: 0000 to ffff (hexadecimal)
Default Value: 0000
What is cxEvmLogFileEvLogFilter?
This 2-byte hexadecimal bitmask, defaulting to 0000, controls which event types are logged to this file, with bits mapped to error, warning, status, trace, and twelve user-defined event types; clearing a bit filters that event type out, while setting it to 1 allows the event manager to log matching events. Admins configure this to narrow a log file to just the event categories they care about, such as errors and warnings only. For example, setting only bits 0 and 1 (hex 0003) restricts logging to error-type and warning-type events.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.495.2.1.5.17.8.1.6 snmpwalk -v2c -c public <target> CXEventManager-MIB::cxEvmLogFileEvLogFilter
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.495.2.1.5.17.8.1.6.1 snmpget -v2c -c public <target> CXEventManager-MIB::cxEvmLogFileEvLogFilter.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.495.2.1.5.17.8.1.6.1 s <value>
Start monitoring CX Memotec communications gateway/multiplexer (event logging) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CXEventManager-MIB::cxEvmLogFileEvLogFilter OID value, configure state conditions and alerts, and monitor any CX Memotec communications gateway/multiplexer (event logging) from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.495 | memotec | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2 | memotecProducts | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2.1 | cxProduct | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2.1.5 | cxSystem | CXProduct-SMI |
| 1.3.6.1.4.1.495.2.1.5.17 | cxEventManager | CXProduct-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.495.2.1.5.17.8 | cxEvmLogFileTable | CXEventManager-MIB |
| 1.3.6.1.4.1.495.2.1.5.17.8.1 | cxEvmLogFileEntry | CXEventManager-MIB |
| 1.3.6.1.4.1.495.2.1.5.17.8.1.6 | cxEvmLogFileEvLogFilter | CXEventManager-MIB |