All MIBs › TIMETRA-DHCP-SERVER-MIB › tmnxDhcpSvrLeaseState
tmnxDhcpSvrLeaseState
Module: TIMETRA-DHCP-SERVER-MIB
OID (symbolic): TIMETRA-DHCP-SERVER-MIB::tmnxDhcpSvrLeaseState
OID (numeric): 1.3.6.1.4.1.6527.3.1.2.47.1.13.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The value of object tmnxDhcpSvrLeaseState indicates the state of this lease.
- 'offered (0)': The IP address was offered to the client. The client still has to acknowledge the offer by sending a DHCP request. - 'stable (1)': The IP address is now in use by the client. - 'forceRenewPending (2)': The IP address is in use by the client, but the server sends a DHCP FORCERENEW message to the client, because an option has changed in tmnxDhcpSvrPoolOptionTable or in tmnxDhcpSvrSubnetOptionTable or in the user database options for this client. - 'removePending (3)': The IP address is in use by the client, but it is no longer available in the IP address ranges configured in tmnxDhcpSvrSubnetRangesTable. The server sends a FORCERENEW message to the client. When the client sends a renewal DHCP request message, it will be rejected. - 'held (4)': The IP address has been used by the client but the lease has timed out. The lease is now in the hold list so that the client can get the exactly same IP address again upon the next request for a lease.
What is tmnxDhcpSvrLeaseState?
Reports the current state of this individual DHCP lease: offered (address handed out, awaiting client acknowledgment), stable (in active use), forceRenewPending (server is pushing a FORCERENEW because an applicable option changed), removePending (address no longer falls within a configured range and will be rejected on renewal), or held (expired but reserved so the same client can reclaim it). Operators read this per-lease state when investigating why a specific client isn't getting the address or options they expect.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.47.1.13.1.3 snmpwalk -v2c -c public <target> TIMETRA-DHCP-SERVER-MIB::tmnxDhcpSvrLeaseState
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.47.1.13.1.3.1 snmpget -v2c -c public <target> TIMETRA-DHCP-SERVER-MIB::tmnxDhcpSvrLeaseState.1
Start monitoring Alcatel-Lucent (Nokia) SR OS routers (DHCP server instance/lease-pool status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-DHCP-SERVER-MIB::tmnxDhcpSvrLeaseState OID value, configure state conditions and alerts, and monitor any Alcatel-Lucent (Nokia) SR OS routers (DHCP server instance/lease-pool status) 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.6527 | timetra | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3 | timetraProducts | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1 | tmnxSRMIB | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1.2 | tmnxSRObjs | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6527.3.1.2.47 | tmnxDhcpServer | TIMETRA-DHCP-SERVER-MIB |
| 1.3.6.1.4.1.6527.3.1.2.47.1 | tmnxDhcpServerObjs | TIMETRA-DHCP-SERVER-MIB |
| 1.3.6.1.4.1.6527.3.1.2.47.1.13 | tmnxDhcpSvrLeaseTable | TIMETRA-DHCP-SERVER-MIB |
| 1.3.6.1.4.1.6527.3.1.2.47.1.13.1 | tmnxDhcpSvrLeaseEntry | TIMETRA-DHCP-SERVER-MIB |
| 1.3.6.1.4.1.6527.3.1.2.47.1.13.1.3 | tmnxDhcpSvrLeaseState | TIMETRA-DHCP-SERVER-MIB |