CLARENT-MIB :: gkLogFileMaxNumFiles

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCLARENT-MIBgkLogFileMaxNumFiles

gkLogFileMaxNumFiles

Module: CLARENT-MIB

OID (symbolic): CLARENT-MIB::gkLogFileMaxNumFiles

OID (numeric): 1.3.6.1.4.1.2858.100.20.2.13

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Maximum number of log files Clarent Gatekeeper creates before overwriting existing logs

What is gkLogFileMaxNumFiles?

This read-write integer caps how many rolled-over log files the Clarent Gatekeeper keeps before it starts overwriting the oldest ones. It works together with gkLogFileRolloverSize to bound total log storage consumed on the gatekeeper. For example, setting gkLogFileMaxNumFiles to 20 retains the last 20 rotated logs before the oldest is recycled.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2858.100.20.2.13
snmpwalk -v2c -c public <target> CLARENT-MIB::gkLogFileMaxNumFiles

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2858.100.20.2.13.1
snmpget -v2c -c public <target> CLARENT-MIB::gkLogFileMaxNumFiles.1

Set instance 1 (SNMPv2c):

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

Start monitoring Clarent VoIP gateway (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CLARENT-MIB::gkLogFileMaxNumFiles OID value, configure state conditions and alerts, and monitor any Clarent VoIP gateway (legacy) 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.2858clarentCLARENT-MIB
1.3.6.1.4.1.2858.100mgtCLARENT-MIB
1.3.6.1.4.1.2858.100.20cGatekeeperCLARENT-MIB
1.3.6.1.4.1.2858.100.20.2cGkConfigCLARENT-MIB
1.3.6.1.4.1.2858.100.20.2.13gkLogFileMaxNumFilesCLARENT-MIB