WESTERN-MULTIPLEX-MIB :: logTrapSeverityFilter

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsWESTERN-MULTIPLEX-MIBlogTrapSeverityFilter

logTrapSeverityFilter

Module: WESTERN-MULTIPLEX-MIB

OID (symbolic): WESTERN-MULTIPLEX-MIB::logTrapSeverityFilter

OID (numeric): 1.3.6.1.4.1.3727.20.10.4.30

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This persistent variable indicates the desired severity level or levels (and qualifiers) for the logging sub-system to generate a SNMP generic log trap, called 'logGenericTrap'. System events that are qualified as having an associated specific trap will NOT be allowed to generate a second generic trap ('logGenericTrap'), and are not considered filtered by this variable, because these events are defined by other specific traps.

This variable operates as a specific trap filter by restricting which system events cause the 'logGenericTrap' to be sent. If a trap is not sent due to this filter, then 'trapFilteredSpecific' is incremented.

The generation of the this trap is also controlled by 'logTrapHysteresis'.

The default value is 'none', which specifies that the 'logGenericTrap' will not be sent.

The log record contains the severity level in 'logRecSeverity'.

'critical' is the highest severity level, followed in decreasing order by 'major', 'minor', 'warning', and 'normal', which is the lowest severity level. These severity levels can be further qualified with an indication that the 'health' of the system is effected because of this event. In such a case, these events are indicated with the '-health' suffix ( 'critical-health', 'major-health', 'minor-health', 'warning-health', 'normal-health').

Specifying a severity level (or qualifier) with this variable indicates that ONLY log events of that level (or qualifier) or higher will be allowed to cause the associated generic trap to be sent (unless limited by the trap management controls, 'trapControl', 'trapMgrTable.trapMgrAddress', 'trapMgrTable.trapMgrControl', and 'trapSeverityFilter').

The '-health' qualifier restricts trap generation to those events that effect health. The 'all-non-health' restricts trap generation to events at any level that do not effect health. The absence of a '-health' or '-non-health' indicates that the health effecting qualifier is not considered, only the severity level.

For example, if this variable was set to 'major-health', only log events with a severity level of 'major' or higher ('critical') and qualified as effecting health will be allowed to generate the SNMP trap 'logGenericTrap'.

If this variable was set to 'warning', only log events with a severity level of 'warning' or higher will be allowed to generate the SNMP trap 'logGenericTrap'. (In this case, the health qualifier is NOT considered.)

The values 'all', 'all-health', and 'all-non-health' allow a broader range of log events to be specified. As implied by the names, 'all' will enable all events to generate traps, 'all-health' will allow any log records that effect health to generate traps, and 'all-non-health' will allow all log records that DO NOT effect health to generate traps.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3727.20.10.4.30
snmpwalk -v2c -c public <target> WESTERN-MULTIPLEX-MIB::logTrapSeverityFilter

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3727.20.10.4.30.1
snmpget -v2c -c public <target> WESTERN-MULTIPLEX-MIB::logTrapSeverityFilter.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.3727.20.10.4.30.1 i <value>

Start monitoring Western Multiplex (Proxim/BridgeWave) fixed-wireless microwave radio equipment (component-inventory/boot-history/event-log status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the WESTERN-MULTIPLEX-MIB::logTrapSeverityFilter OID value, configure state conditions and alerts, and monitor any Western Multiplex (Proxim/BridgeWave) fixed-wireless microwave radio equipment (component-inventory/boot-history/event-log status) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.3727western_multiplexWESTERN-MULTIPLEX-MIB
1.3.6.1.4.1.3727.20tsunami100_06WESTERN-MULTIPLEX-MIB
1.3.6.1.4.1.3727.20.10systemWESTERN-MULTIPLEX-MIB
1.3.6.1.4.1.3727.20.10.4logWESTERN-MULTIPLEX-MIB
1.3.6.1.4.1.3727.20.10.4.30logTrapSeverityFilterWESTERN-MULTIPLEX-MIB