All MIBs › MESSAGE-TRACKING-MIB › respNextHopMta
respNextHopMta
Module: MESSAGE-TRACKING-MIB
OID (symbolic): MESSAGE-TRACKING-MIB::respNextHopMta
OID (numeric): 1.3.6.1.3.73.2.1.4.1.5
Node type: OBJECT-TYPE
Type: DisplayString
Access: read-only
Description: Name of the MTA to which this message was sent. MADMAN-compliant
MTA's should be addressed in the form '(
What is respNextHopMta?
Identifies the MTA this message was forwarded to next, in the '(host-id::mtaName)' form for MADMAN-compliant MTAs, letting an admin continue tracing the message's path downstream.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.3.73.2.1.4.1.5 snmpwalk -v2c -c public <target> MESSAGE-TRACKING-MIB::respNextHopMta
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.3.73.2.1.4.1.5.1 snmpget -v2c -c public <target> MESSAGE-TRACKING-MIB::respNextHopMta.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::respNextHopMta 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.4 | msgTrackResponseTable | MESSAGE-TRACKING-MIB |
| 1.3.6.1.3.73.2.1.4.1 | msgTrackResponseEntry | MESSAGE-TRACKING-MIB |
| 1.3.6.1.3.73.2.1.4.1.5 | respNextHopMta | MESSAGE-TRACKING-MIB |