TIMETRA-LLDP-MIB :: tmnxLldpStatsRxPortAgeouts

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › TIMETRA-LLDP-MIB › tmnxLldpStatsRxPortAgeouts

tmnxLldpStatsRxPortAgeouts

Module: TIMETRA-LLDP-MIB

OID (symbolic): TIMETRA-LLDP-MIB::tmnxLldpStatsRxPortAgeouts

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.59.2.2.1.7

Node type: OBJECT-TYPE

Type: ZeroBasedCounter32

Access: read-only

Description: The counter that represents the number of age-outs that occurred on a given port. An age-out is the number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in tmnxLldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired.

This counter is similar to lldpStatsRemTablesAgeouts, except that the counter is on a per port basis. This enables NMS to poll tables associated with the tmnxLldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems on the indicated port only.

This counter should be set to zero during agent initialization and its value should not be saved in non-volatile storage. When a port's admin status changes from 'disabled' to 'rxOnly', 'txOnly' or 'txAndRx', the counter associated with the same port should reset to 0. The agent should also flush all remote system information associated with the same port.

This counter should be incremented only once when the complete set of information is invalidated (aged out) from all related tables on a particular port. Partial ageing is not allowed, and thus, should not change the value of this counter.

What is tmnxLldpStatsRxPortAgeouts?

A count of times a complete set of remote-neighbor information on this port aged out because its advertised timeliness interval expired; a rising count tells an admin that a neighbor is dropping off and reappearing rather than staying continuously visible.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.59.2.2.1.7
snmpwalk -v2c -c public <target> TIMETRA-LLDP-MIB::tmnxLldpStatsRxPortAgeouts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.59.2.2.1.7.1
snmpget -v2c -c public <target> TIMETRA-LLDP-MIB::tmnxLldpStatsRxPortAgeouts.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> tmnxLldpStatsRxPortAgeouts.1

Start monitoring Nokia/Alcatel-Lucent 7750 SR router (SROS) (LLDP per-port config/neighbor-discovery status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-LLDP-MIB::tmnxLldpStatsRxPortAgeouts OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7750 SR router (SROS) (LLDP per-port config/neighbor-discovery status) from a single console.

OID Breakdown

Upper-level ancestors (10 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.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.59tmnxLldpObjectsTIMETRA-LLDP-MIB
1.3.6.1.4.1.6527.3.1.2.59.2tmnxLldpStatisticsTIMETRA-LLDP-MIB
1.3.6.1.4.1.6527.3.1.2.59.2.2tmnxLldpStatsRxPortTableTIMETRA-LLDP-MIB
1.3.6.1.4.1.6527.3.1.2.59.2.2.1tmnxLldpStatsRxPortEntryTIMETRA-LLDP-MIB
1.3.6.1.4.1.6527.3.1.2.59.2.2.1.7tmnxLldpStatsRxPortAgeoutsTIMETRA-LLDP-MIB