tpmCurReportSize
TPM-MIB ·
.1.3.6.1.2.1.16.30.2.4
Object
The maximum number of completed transactions desired to be
retained in the tpmCurReportTable. If the agent doesn't have
enough resources to retain this many, it will retain as many
as possible. Regardless of this value, the agent must
attempt to keep records for all current transactions it is
monitoring.
The agent should consider this value to give a hint as to
how many transactions to save. This is not a hard limit,
just a hint to a maximum value of interest. If this value is
reduced by the management station, the agent can take note,
it may free some records, or it may do nothing.
The value of this object must persist across reboots.
Context
- MIB
- TPM-MIB
- OID
.1.3.6.1.2.1.16.30.2.4- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- tpmReports
- 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 'TPM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TPM-MIB::tpmCurReportSize.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TPM-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TPM-MIB::tpmCurReportSize'
Syntax
- Source
- SNMPv2-SMIUnsigned32
- Base type
Unsigned32
Values & Constraints
Type Constraints
range: 0..4294967295
Conformance
Member of