ipIfStatsTableLastChange
IP-MIB ·
.1.3.6.1.2.1.4.31.2
Object
The value of sysUpTime on the most recent occasion at which
a row in the ipIfStatsTable was added or deleted.
If new objects are added to the ipIfStatsTable that require
the ipIfStatsTableLastChange to be updated when they are
modified, they must specify that requirement in their
description clause.
Context
- MIB
- IP-MIB
- OID
.1.3.6.1.2.1.4.31.2- Type
- scalar
- Access
- readonly
- Status
- current
- Parent
- ipTrafficStats
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'IP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'IP-MIB::ipIfStatsTableLastChange.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'IP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IP-MIB::ipIfStatsTableLastChange'
Syntax
- Source
- SNMPv2-TCTimeStamp
- Base type
Unsigned32- Based on
- SNMPv2-SMITimeTicks
Type Description
The value of the sysUpTime object at which a specific
occurrence happened. The specific occurrence must be
defined in the description of any object defined using this
type.
If sysUpTime is reset to zero as a result of a re-
initialization of the network management (sub)system, then
the values of all TimeStamp objects are also reset.
However, after approximately 497 days without a re-
initialization, the sysUpTime object will reach 2^^32-1 and
then increment around to zero; in this case, existing values
of TimeStamp objects do not change. This can lead to
ambiguities in the value of TimeStamp objects.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of