All MIBs › CENTILLION-SYSTEM-EVENT-LOG-MIB › sysEvtLogPreFilterEntityMap
sysEvtLogPreFilterEntityMap
Module: CENTILLION-SYSTEM-EVENT-LOG-MIB
OID (symbolic): CENTILLION-SYSTEM-EVENT-LOG-MIB::sysEvtLogPreFilterEntityMap
OID (numeric): 1.3.6.1.4.1.930.2.1.5.2
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
Description: The bit array that contains the bit map of all possible entities for event logging pre-filter control. There are total of 64 entities. Each entity represented by one bit. A bit with a value of 1 means that the corresponding Entity is enabled for event logging, 0 when the event logging is disabled for the corresponding entity.
The following show the bit position and associated entity. Bit 0 - SNMP_ENT_ATM_PORT Bit 1 - SNMP_ENT_BOOTP Bit 2 - SNMP_ENT_CLC Bit 3 - SNMP_ENT_CLI Bit 4 - SNMP_ENT_CONFIG Bit 5 - SNMP_ENT_ETHERNET Bit 6 - SNMP_ENT_FDB Bit 7 - SNMP_ENT_HW Bit 8 - SNMP_ENT_IISP Bit 9 - SNMP_ENT_ILMI Bit 10 - SNMP_ENT_IP Bit 11 - SNMP_ENT_LANE Bit 12 - SNMP_ENT_LEC Bit 13 - SNMP_ENT_MCP Bit 14 - SNMP_ENT_SIGNL Bit 15 - SNMP_ENT_SNMP Bit 16 - SNMP_ENT_STP Bit 17 - SNMP_ENT_TELNET Bit 18 - SNMP_ENT_TFTP Bit 19 - SNMP_ENT_TOKENRING Bit 20 - SNMP_ENT_VPORT Bit 21 - SNMP_ENT_MPOA
When a new entity is created, a new bit position should also be defined. The order of bit is defined as bit 0-7 in the lowest oder of byte (first byte), bit 8-15 in the second lowest order of byte(second bye), and so on. The lower number of bit is the least significant bit within the byte.
What is sysEvtLogPreFilterEntityMap?
This is an 8-byte bitmap, one bit per internal logging entity out of 64 possible entities (such as SNMP_ENT_ATM_PORT, SNMP_ENT_BOOTP, SNMP_ENT_CLC, and others), where a 1 bit enables event logging for that entity and a 0 bit disables it. An admin sets specific bits here to reduce event log noise by turning off logging entirely for subsystems that aren't currently being investigated, rather than filtering purely by severity. For example, clearing the bit for SNMP_ENT_BOOTP would silence all BOOTP-related log entries entirely, even critical ones, while leaving every other entity's logging behavior untouched.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.930.2.1.5.2 snmpwalk -v2c -c public <target> CENTILLION-SYSTEM-EVENT-LOG-MIB::sysEvtLogPreFilterEntityMap
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.930.2.1.5.2.1 snmpget -v2c -c public <target> CENTILLION-SYSTEM-EVENT-LOG-MIB::sysEvtLogPreFilterEntityMap.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.930.2.1.5.2.1 s <value>
Start monitoring Nortel/Bay Networks Centillion ATM switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CENTILLION-SYSTEM-EVENT-LOG-MIB::sysEvtLogPreFilterEntityMap OID value, configure state conditions and alerts, and monitor any Nortel/Bay Networks Centillion ATM switches from a single console.
OID Breakdown
Upper-level ancestors (10 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.930 | centillion | CENTILLION-ROOT-MIB |
| 1.3.6.1.4.1.930.2 | proprietary | CENTILLION-ROOT-MIB |
| 1.3.6.1.4.1.930.2.1 | cnSystem | CENTILLION-ROOT-MIB |
| 1.3.6.1.4.1.930.2.1.5 | sysEvtLogMgmt | CENTILLION-ROOT-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.930.2.1.5.2 | sysEvtLogPreFilterEntityMap | CENTILLION-SYSTEM-EVENT-LOG-MIB |