All MIBs › MESSAGE-TRACKING-MIB › reqFailureReason
reqFailureReason
Module: MESSAGE-TRACKING-MIB
OID (symbolic): MESSAGE-TRACKING-MIB::reqFailureReason
OID (numeric): 1.3.6.1.3.73.2.1.3.1.22
Node type: OBJECT-TYPE
Type: DisplayString
Access: read-only
Description: A textual description of why a message tracking request failed. This variable may be set by an agent when the reqResponseStatus is set to either 'failedInvalidQuery(4)', or 'failedError(5)'.
What is reqFailureReason?
A text explanation the agent fills in when reqResponseStatus comes back as failedInvalidQuery(4) or failedError(5), telling the admin why their tracking query didn't run.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.3.73.2.1.3.1.22 snmpwalk -v2c -c public <target> MESSAGE-TRACKING-MIB::reqFailureReason
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.3.73.2.1.3.1.22.1 snmpget -v2c -c public <target> MESSAGE-TRACKING-MIB::reqFailureReason.1
Start monitoring Vendor-neutral IETF standard (messaging gateway/MTA, message tracking) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MESSAGE-TRACKING-MIB::reqFailureReason OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard (messaging gateway/MTA, message tracking) from a single console.
OID Breakdown
Upper-level ancestors (5 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.3 | experimental | APERTUS-NPG-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.3.73.2 | msgTracking | MESSAGE-TRACKING-MIB |
| 1.3.6.1.3.73.2.1 | mta_message_track | MESSAGE-TRACKING-MIB |
| 1.3.6.1.3.73.2.1.3 | msgTrackRequestTable | MESSAGE-TRACKING-MIB |
| 1.3.6.1.3.73.2.1.3.1 | msgTrackRequestEntry | MESSAGE-TRACKING-MIB |
| 1.3.6.1.3.73.2.1.3.1.22 | reqFailureReason | MESSAGE-TRACKING-MIB |