All MIBs › TIMETRA-DHCP-SERVER-MIB › tmnxDhcpsFoOperMaxClientLeadTime
tmnxDhcpsFoOperMaxClientLeadTime
Module: TIMETRA-DHCP-SERVER-MIB
OID (symbolic): TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsFoOperMaxClientLeadTime
OID (numeric): 1.3.6.1.4.1.6527.3.1.2.47.1.18.2.1.4
Node type: OBJECT-TYPE
Type: Unsigned32
Access: read-only
Description: The value of the object tmnxDhcpsFoOperMaxClientLeadTime indicates the actual maximum client lead time.
The value of the object tmnxDhcpsFoOperMaxClientLeadTime is initialized to the value of the object tmnxDhcpsFoMaxClientLeadTime.
Every time the value of the object tmnxDhcpsFoMaxClientLeadTime is set, the value of the object tmnxDhcpsFoOperMaxClientLeadTime is modified accordingly.
When the value of the object tmnxDhcpsFoState becomes equal to 'normal', the actual maximum client lead time becomes equal to the maximum of the values of the objects tmnxDhcpsFoOperMaxClientLeadTime on this system and on the failover peer.
When the value of the object tmnxDhcpsFoAdminState becomes equal to 'outOfService', the value of the object tmnxDhcpsFoOperMaxClientLeadTime is reset to the value of the object tmnxDhcpsFoMaxClientLeadTime.
What is tmnxDhcpsFoOperMaxClientLeadTime?
Reports the actual operating MCLT value in effect, initialized from and updated whenever tmnxDhcpsFoMaxClientLeadTime is set, and re-synchronized to the larger of the two peers' values once the failover state reaches 'normal'; it resets back to the configured value when the facility goes out of service. Operators read this to see the real negotiated MCLT rather than just the locally configured intention.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.47.1.18.2.1.4 snmpwalk -v2c -c public <target> TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsFoOperMaxClientLeadTime
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.47.1.18.2.1.4.1 snmpget -v2c -c public <target> TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsFoOperMaxClientLeadTime.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::tmnxDhcpsFoOperMaxClientLeadTime 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.18 | tmnxDhcpsFailoverObjs | TIMETRA-DHCP-SERVER-MIB |
| 1.3.6.1.4.1.6527.3.1.2.47.1.18.2 | tmnxDhcpsFoTable | TIMETRA-DHCP-SERVER-MIB |
| 1.3.6.1.4.1.6527.3.1.2.47.1.18.2.1 | tmnxDhcpsFoEntry | TIMETRA-DHCP-SERVER-MIB |
| 1.3.6.1.4.1.6527.3.1.2.47.1.18.2.1.4 | tmnxDhcpsFoOperMaxClientLeadTime | TIMETRA-DHCP-SERVER-MIB |