All MIBs › TPM-MIB › tpmTransMetricDirConfig
tpmTransMetricDirConfig
Module: TPM-MIB
OID (symbolic): TPM-MIB::tpmTransMetricDirConfig
OID (numeric): 1.3.6.1.2.1.16.30.1.5.1.5
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: This object describes and configures the probe's support for this performance metric in relationship to the specified transaction and application. The agent
creates entries in this table for all metric and transaction combinations that it can generate. Because the probe will only populate this table with supported entries, and the table cannot have entries added, the notSupported(1) setting is only used to signify that other configuration parameters are causing the agent currently not to support the generation and collection of this metric for the specified protocol and application. Also, the status of this object will not change to notSupported(1) due to a change to supportedOff(2) in the tpmMetricDir table.
If the value of this object is notSupported(1), the probe will not perform computations for this performance metric and transaction combination and will not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports computations for this performance metric and protocol and is configured to perform the computations for this performance metric and protocol combination for the application for all interfaces. If the value of this object is supportedOff(2), the probe supports computations for this performance metric for the specified protocol, but is configured not to perform the computations for this performance metric and protocol for the application for any interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall cause the deletion of all entries in the tpmReportGroup tables, for all appropriate studies configured in the tpmAggrReportCntrlTable.
The value of this object must persist across reboots.
What is tpmTransMetricDirConfig?
This controls whether the probe actively collects this specific metric/transaction/application combination: notSupported(1) means the probe currently cannot generate it and the value can't be changed, supportedOff(2) means the probe is capable but not configured to collect it (and doing so deletes any related report entries), and supportedOn(3) means it's actively being collected on all interfaces.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.16.30.1.5.1.5 snmpwalk -v2c -c public <target> TPM-MIB::tpmTransMetricDirConfig
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.16.30.1.5.1.5.1 snmpget -v2c -c public <target> TPM-MIB::tpmTransMetricDirConfig.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.16.30.1.5.1.5.1 i <value>
Start monitoring vendor-neutral, standards-based MIB, RMON2-capable network probe/switch for APM (transaction/latency performance-metric status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TPM-MIB::tpmTransMetricDirConfig OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, RMON2-capable network probe/switch for APM (transaction/latency performance-metric status) from a single console.
OID Breakdown
Upper-level ancestors (7 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.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.16 | rmon | LBHUB-BOOM-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.16.30 | tpmMIB | TPM-MIB |
| 1.3.6.1.2.1.16.30.1 | tpmCapabilities | TPM-MIB |
| 1.3.6.1.2.1.16.30.1.5 | tpmTransMetricDirTable | TPM-MIB |
| 1.3.6.1.2.1.16.30.1.5.1 | tpmTransMetricDirEntry | TPM-MIB |
| 1.3.6.1.2.1.16.30.1.5.1.5 | tpmTransMetricDirConfig | TPM-MIB |