CLAB-ANI-DEV-MIB :: aniDevSysLoggingLevelCtrl

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CLAB-ANI-DEV-MIB › aniDevSysLoggingLevelCtrl

aniDevSysLoggingLevelCtrl

Module: CLAB-ANI-DEV-MIB

OID (symbolic): CLAB-ANI-DEV-MIB::aniDevSysLoggingLevelCtrl

OID (numeric): 1.3.6.1.4.1.4491.4.7.1.2.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The current logging priority level for system messages. Setting a level sets all levels from the level specified to the highest severity level except for �off�. The level �all� indicates all levels. The log levels are derived from the log4j class.

all(1) The all level has the lowest possible rank and is intended to turn on all logging.

trace(2) The trace level designates finer-grained informational events than the DEBUG (see log4j class for further definition).

debug(3) The debug level designates fine-grained informational events that are most useful to debug an application.

info(4) The info level designates informational messages that highlight the progress of the application at coarse-grained level.

warn(5) The warn level designates potentially harmful situations.

error(6) The error level designates error events that might still allow the application to continue running.

fatal(7) The fatal level designates very severe error events that will presumably lead the application to abort.

off(8) The off has the highest possible rank and is intended to turn off logging.

What is aniDevSysLoggingLevelCtrl?

This INTEGER object sets the device's current system logging severity threshold (from all(1) down through fatal(7), plus off(8)), following log4j-style semantics where setting a level enables that level and all more-severe levels. An administrator raises or lowers it to control how verbose system event logging is during normal operation versus active troubleshooting. For example, setting this to debug(3) during a field investigation captures much more detail than the warn(5) level typically used in normal production operation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4491.4.7.1.2.3
snmpwalk -v2c -c public <target> CLAB-ANI-DEV-MIB::aniDevSysLoggingLevelCtrl

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4491.4.7.1.2.3.1
snmpget -v2c -c public <target> CLAB-ANI-DEV-MIB::aniDevSysLoggingLevelCtrl.1

Set instance 1 (SNMPv2c):

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

Start monitoring DOCSIS cable gateway/sRouter devices with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CLAB-ANI-DEV-MIB::aniDevSysLoggingLevelCtrl OID value, configure state conditions and alerts, and monitor any DOCSIS cable gateway/sRouter devices from a single console.

OID Breakdown

Upper-level ancestors (8 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
1.3.6.1.4.1.4491cableLabsCLAB-DEF-MIB
1.3.6.1.4.1.4491.4clabCommonMibsCLAB-DEF-MIB
Numeric OIDNameModule
1.3.6.1.4.1.4491.4.7clabAniDevMibCLAB-ANI-DEV-MIB
1.3.6.1.4.1.4491.4.7.1clabAniDevObjectsCLAB-ANI-DEV-MIB
1.3.6.1.4.1.4491.4.7.1.2clabAniDevSysLoggingObjectsCLAB-ANI-DEV-MIB
1.3.6.1.4.1.4491.4.7.1.2.3aniDevSysLoggingLevelCtrlCLAB-ANI-DEV-MIB