SESSION-MIB :: tLock

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsSESSION-MIBtLock

tLock

Module: SESSION-MIB

OID (symbolic): SESSION-MIB::tLock

OID (numeric): 1.3.6.1.4.1.1038.201.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Number of minutes for which a write session is active on the equipment. When the value of this variable is 0, the equipment is not locked. When a SNMP manager (iONOSANMSupervisor and Operator) start a write session, tLock can be set to a value by the manager (up to 30 minutes, so it has time to configure the equipment). Each time an action is done under the equipment tLock is set again to its value. tLock is a decremental counter; when the value of tLock return to 0, the write session is ended and the equipment is unlocked. The SNMP manager can choose to unlock the equipment by setting the value of tLock to 0 before it reach this value itself.

What is tLock?

This value is the number of minutes for which a write session is actively locked on the equipment, decrementing over time; a value of 0 means the equipment is not locked. An admin managing exclusive write access uses this to see how much longer a current management session holds its lock, and can set it to 0 to manually unlock the equipment before the timer expires. For example, an SNMP manager starting a configuration session sets tLock to up to 30 minutes, and each subsequent action resets the countdown so the lock doesn't expire mid-task.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1038.201.1
snmpwalk -v2c -c public <target> SESSION-MIB::tLock

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1038.201.1.1
snmpget -v2c -c public <target> SESSION-MIB::tLock.1

Set instance 1 (SNMPv2c):

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

Start monitoring SAGEM/DR network device supporting SNMP/HTTP/CLI/vt100 management (concurrent management-session tracking) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SESSION-MIB::tLock OID value, configure state conditions and alerts, and monitor any SAGEM/DR network device supporting SNMP/HTTP/CLI/vt100 management (concurrent management-session tracking) from a single console.

How to Use in IPNetwork Monitor

Select an SAGEM/DR network device supporting SNMP/HTTP/CLI/vt100 management (concurrent management-session tracking) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tLock into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of minutes for which a write session is active on the equipment. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (7 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.1038sagemDrSAGEM-DR-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1038.201sessionSESSION-MIB
1.3.6.1.4.1.1038.201.1tLockSESSION-MIB