MESSAGE-TRACKING-MIB: View SNMP OID List / Download MIB
VENDOR: INTERNET-STANDARD
| Home | MIB: MESSAGE-TRACKING-MIB | |||
|---|---|---|---|---|
| Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
| Object Name | OID | Type | Access | Info |
| msgTracking | 1.3.6.1.3.73.2 | |||
| mta_message_track | 1.3.6.1.3.73.2.1 |
The MIB module describing message tracking |
||
| mtaInformationTable | 1.3.6.1.3.73.2.1.1 | no-access |
The table holding information about the MTA being queried. A table is used because there may be multiple MTAs at a single host. |
|
| 1.3.6.1.3.73.2.1.1.1 | no-access |
One entry in the table holding information about the MTA being queried |
||
| mtaIndex | 1.3.6.1.3.73.2.1.1.1.1 | integer | read-only |
The integer index into this table. |
| mtaName | 1.3.6.1.3.73.2.1.1.1.2 | displaystring | read-only |
The name of the MTA described in this row of the table. |
| mtaMessagingType | 1.3.6.1.3.73.2.1.1.1.3 | displaystring | read-only |
Common name of the messaging system of this MTA (e.g. X.400, SMTP). |
| mtaStartTimeforRecordedInformation | 1.3.6.1.3.73.2.1.1.1.4 | dateandtime | read-only |
The date/time of the oldest message tracking information available from this MTA. |
| mtaAlternativeAgent | 1.3.6.1.3.73.2.1.1.1.5 | displaystring | read-only |
The name (or address) of another agent that may have message tracking information concerning this MTA. |
| msgTrackNextRequestIndex | 1.3.6.1.3.73.2.1.2 | counter32 | read-only |
The index that may be used by a manager (requestor) on a 'set-request' PDU to create a new conceptual row in the msgTrackRequestTable table (and thereby issue a message tracking query). |
| msgTrackRequestTable | 1.3.6.1.3.73.2.1.3 | no-access |
The table holding all active message tracking requests. |
|
| 1.3.6.1.3.73.2.1.3.1 | no-access |
The entry associated with each request for message information. |
||
| reqEntryIndex | 1.3.6.1.3.73.2.1.3.1.1 | integer | read-only |
The integer index into the msgTrackRequestTable table. |
| reqRowStatus | 1.3.6.1.3.73.2.1.3.1.2 | integer | read-write |
The status of the conceptual row. These are mapped to the same values as the RowStatus textual conversion in SNMPv2 and carry the same semantics with one exception: the exception is that when a manager (requestor) sets the value to destroy(6), this also has the added semantics of deleting all conceptual rows in the msgTrackResponseTable table whose respEntryIndex matches the reqEntryIndex of this conceptual row. Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6. |
| reqResponseStatus | 1.3.6.1.3.73.2.1.3.1.3 | integer | read-only |
Indicates the status of this query and its responses in the msgTrackResponseTable. Values are: unknown - The status of this query is not known. inProgress - The agent(responder) is still processing the request. failedNoMatches - The query has been processed and has produced no matches. failedInvalidQuery - The query could not be processed due to invalid or missing data in the original query. FailedError - The query could not be processed due to an error in the agent(responder). successUnderqualified - The query was successfully processed, but the query was found to be underqualified. That is, more reponses were found than were specified in reqMaxResponses. reqMaxResponses entries were returned in the msgTrackResponseTable. success - The query succeeded, returning from 1 to reqMaxResponse entries in the msgTrackResponseTable. Enumeration: 'success': 7, 'unknown': 1, 'failedError': 5, 'failedNoMatches': 3, 'inProgress': 2, 'successUnderqualified': 6, 'failedInvalidQuery': 4. |
| reqMaxResponses | 1.3.6.1.3.73.2.1.3.1.4 | integer | read-write |
Specifies the largest number of responses to be returned in the msgTrackResponseTable on an underspecified query (i.e. the maximum value of respMsgIndex in the msgTrackResponseTable conceptual row whose respEntryIndex matches the reqEntryIndex of this conceptual row). |
| reqUniqueMsgId | 1.3.6.1.3.73.2.1.3.1.5 | displaystring | read-write |
Specifies a unique message id used internally by the MTA for identification of a message. This form of the message id may or may not be identical to the inbound and/or outbound forms of the message id. If specified, this may be the only search criteria required. If the entire unique message id is not specified, prefix matching is assumed. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqInboundMsgId | 1.3.6.1.3.73.2.1.3.1.6 | displaystring | read-write |
Specifies a unique message id as received by the MTA for identification of a message. This form of the message id may or may not be identical to the internal and/or outbound forms of the message id. If specified, this may be the only search criteria required. If the entire inbound message id is not specified, prefix matching is assumed. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqOutboundMsgId | 1.3.6.1.3.73.2.1.3.1.7 | displaystring | read-write |
Specifies a unique message id as transmitted by the MTA for identification of a message. This form of the message id may or may not be identical to the internal and/or inbound forms of the message id. If specified, this may be the only search criteria required. If the entire outbound message id is not specified, prefix matching is assumed. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqInboundOriginator | 1.3.6.1.3.73.2.1.3.1.8 | displaystring | read-write |
Identifies the originator of the message in its received form, expressed in string format. The style and format of this identifier varies according to a specific messaging technology. As a result of potentially disparate messaging technologies, this identifier is only guaranteed to be the name known to the end-user on the first MTA in the delivery sequence. If reqOriginatorNameForm is set to 'x.400(2)' or 'smtp(3)', the supplied attributes will be considered in the match. Any attributes not supplied will be wildcarded. If reqOriginatorNameForm is set to 'freeForm(1)', this value is assumed to be a substring of the originator name. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqOutboundOriginator | 1.3.6.1.3.73.2.1.3.1.9 | displaystring | read-write |
Identifies the originator of the message in its transmitted form, expressed in string format. The style and format of this identifier varies according to a specific messaging technology. As a result of potentially disparate messaging technologies this identifier is only guaranteed to be the name known to the end-user on the last MTA in the delivery sequence. If reqOriginatorNameForm is set to 'x.400(2)' or 'smtp(3)', the supplied attributes will be considered in the match. Any attributes not supplied will be wildcarded. If reqOriginatorNameForm is set to 'freeForm(1)', this value is assumed to be a substring of the originator name. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqOriginatorNameForm | 1.3.6.1.3.73.2.1.3.1.10 | nameform | read-write |
Identifies the name form of originator strings supplied in the reqInboundOriginator and/or reqOutboundOriginator values. This value is used by the agent to perform name form dependant parsing of these values. If neither of these strings are supplied, this name form value is irrelevant to the query. A value of 'any(1)' implies that no special parsing should be performed on the originator names supplied. |
| reqInboundRecipient | 1.3.6.1.3.73.2.1.3.1.11 | displaystring | read-write |
Identifies one of the recipients (the one to be tracked) of the message in its received form, expressed in string format. The style and format of this identifier varies according to a specific messaging technology. As a result of potentially disparate messaging technologies, this identifier is only guaranteed to be the name an end-user knows the recipient by on the first MTA in the delivery sequence. If reqRecipientNameForm is set to 'x.400(2)' or 'smtp(3)', the supplied attributes will be considered in the match. Any attributes not supplied will be wildcarded. If reqRecipientNameForm is set to 'freeForm(1)', this value is assumed to be a substring of the recipient name. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqOutboundRecipient | 1.3.6.1.3.73.2.1.3.1.12 | displaystring | read-write |
Identifies one of the recipients (the one to be tracked) of the message in its transmitted form, expressed in string format. The style and format of this identifier varies according to a specific messaging technology. As a result of potentially disparate messaging technologies, this identifier is only guaranteed to be the name an end-user knows the recipient by on the last MTA in the delivery sequence. If reqRecipientNameForm is set to 'x.400(2)' or 'smtp(3)', the supplied attributes will be considered in the match. Any attributes not supplied will be wildcarded. If reqRecipientNameForm is set to 'freeForm(1)', this value is assumed to be a substring of the recipient name. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqRecipientNameForm | 1.3.6.1.3.73.2.1.3.1.13 | nameform | read-write |
Identifies the name form of recipient strings supplied in the reqInboundRecipient and/or reqOutboundRecipient values. This value is used by the agent to perform name form dependant parsing of these values. If neither of these strings are supplied, this name form value is irrelevant to the query. A value of 'any(1)' implies that no special parsing should be performed on the recipient names supplied. |
| reqSubject | 1.3.6.1.3.73.2.1.3.1.14 | displaystring | read-write |
Identifies a substring of the text of the 'Subject' attribute of the message. Since some messaging technologies make it difficult for an MTA to preserve this data, it may not be supported by all agents. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqMinMsgSize | 1.3.6.1.3.73.2.1.3.1.15 | integer | read-write |
Specifies the minimum size of a message to be tracked (content, excluding envelope), expressed in kilo-octets. Set both reqMinMsgSize and reqMaxMsgSize to zero if message size is irrelevant to the query. |
| reqMaxMsgSize | 1.3.6.1.3.73.2.1.3.1.16 | integer | read-write |
Specifies the maximum size of a message to be tracked (content, excluding envelope), expressed in kilo-octets. Set both reqMinMsgSize and reqMaxMsgSize to zero if message size is irrelevant to the query. |
| reqEarliestArrivalTime | 1.3.6.1.3.73.2.1.3.1.17 | dateandtime | read-write |
Specifies the earliest arrival time, at this MTA, for a message to be tracked. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqLatestArrivalTime | 1.3.6.1.3.73.2.1.3.1.18 | dateandtime | read-write |
Specifies the latest arrival time, at this MTA, for a message to be tracked. Set to an empty (zero length) string if unknown or irrelevant to query. |
| reqDispositionStatus | 1.3.6.1.3.73.2.1.3.1.19 | dispositionstatus | read-write |
Specifies the disposition status of the message for a particular recipient. Set to 'unknown(1)' if unknown or irrelevant to the query. |
| reqMsgType | 1.3.6.1.3.73.2.1.3.1.20 | msgtype | read-write |
The type of message to be tracked. Set to 'any(1)' if message type is unknown or irrelevant to the query. |
| reqCollapseRecipients | 1.3.6.1.3.73.2.1.3.1.21 | integer | read-write |
If a value of 'true(2)' is specified, a single msgTrackResponseEntry will be created for each matching message regardless of the number of recipients. If not specified or set to 'false(1)', a msgTrackResponseEntry will be created for each matching message and/or recipient. This variable may be used in the case of a distribution list or a message with a large number of recipients. Enumeration: 'true': 2, 'false': 1. |
| reqFailureReason | 1.3.6.1.3.73.2.1.3.1.22 | displaystring | read-only |
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)'. |
| msgTrackResponseTable | 1.3.6.1.3.73.2.1.4 | no-access |
The table holding the response to all active message tracking requests. |
|
| 1.3.6.1.3.73.2.1.4.1 | no-access |
The entry associated with each response to a request for message information. |
||
| respEntryIndex | 1.3.6.1.3.73.2.1.4.1.1 | integer | read-only |
The primary integer index into the msgTrackResponseTable table. It matches the value of reqEntryIndex for the original request. |
| respMsgIndex | 1.3.6.1.3.73.2.1.4.1.2 | integer | read-only |
The secondary integer index into the msgTrackResponseTable table. For each value of respEntryIndex in the table, there may be multiple conceptual rows indexed by respMsgIndex, each denoting a possible response to the tracking query. The maximum number of entries should have an upper bound of the value of reqMaxResponses in the conceptual row of msgTrackRequestTable that represents the original query request. |
| respDispositionStatus | 1.3.6.1.3.73.2.1.4.1.3 | dispositionstatus | read-only |
Indicates the disposition of this message by this MTA for this recipient. |
| rspDispositionTime | 1.3.6.1.3.73.2.1.4.1.4 | dateandtime | read-only |
Time at which this MTA disposed of this message for this recipient. |
| respNextHopMta | 1.3.6.1.3.73.2.1.4.1.5 | displaystring | read-only |
Name of the MTA to which this message was sent. MADMAN-compliant MTA's should be addressed in the form '( |
| respPrevHopMta | 1.3.6.1.3.73.2.1.4.1.6 | displaystring | read-only |
Name of the MTA from which this message was received. MADMAN- compliant MTA's should be addressed in the form '( |
| respNonDeliveryReason | 1.3.6.1.3.73.2.1.4.1.7 | displaystring | read-only |
A textual representation representing the reason for non-delivery to this recipient. No attempt is made to normalize these non-delivered reasons across systems, since this indicates a terminal condition. |
| respMsgArrivalTime | 1.3.6.1.3.73.2.1.4.1.8 | dateandtime | read-only |
Represents the time at which this message for this recipient arrived at this MTA. |
| respMsgSize | 1.3.6.1.3.73.2.1.4.1.9 | integer | read-only |
Size of the message in kilo-octets. |
| respMsgPriority | 1.3.6.1.3.73.2.1.4.1.10 | displaystring | read-only |
Textual representation of the priority of the message. No attempt is made to normalize these values across disparate messaging technologies. |
| respUniqueMsgId | 1.3.6.1.3.73.2.1.4.1.11 | displaystring | read-only |
The unique message identifier that the MTA assigned internally to the message. |
| respInboundMsgId | 1.3.6.1.3.73.2.1.4.1.12 | displaystring | read-only |
The unique message identifier that the 'previous hop' MTA assigned to the message. If the 'previous' MTA uses a different messaging technology or identifier scheme, this identifier serves to correlate the message from MTA to MTA. If the 'previous' MTA uses the same technology, this value is generally superfluous. If this is the first MTA in the delivery sequence, or if the previous message id is unknown, this variable is null- valued. |
| respOutboundMsgId | 1.3.6.1.3.73.2.1.4.1.13 | displaystring | read-only |
The unique message identifier that the 'next hop' MTA assigned to the message. If the 'next' MTA uses a different messaging technology or identifier scheme, this identifier serves to correlate the message from MTA to MTA. If the 'next' MTA uses the same technology, this value is generally superfluous. If this is the last MTA in the delivery sequence, or if the next hop message id is unknown, this variable is null-valued. |
| respInboundOriginator | 1.3.6.1.3.73.2.1.4.1.14 | displaystring | read-only |
Textual representation identifying the originator of the message as it was received from the 'previous hop' MTA. The style of this variable varies according to a specific messaging technology. |
| respOutboundOriginator | 1.3.6.1.3.73.2.1.4.1.15 | displaystring | read-only |
Textual representation identifying the originator of the message as it was (or will be) presented to the 'next hop' MTA. The style of this variable varies according to a specific messaging technology. |
| respInboundRecipient | 1.3.6.1.3.73.2.1.4.1.16 | displaystring | read-only |
Textual representation identifying the recipient of the message as it was received from the 'previous hop' MTA. The style of this variable varies according to a specific messaging technology.. |
| respOutboundRecipient | 1.3.6.1.3.73.2.1.4.1.17 | displaystring | read-only |
Textual representation identifying the recipient of the message as it was (or will be) presented to the 'next hop' MTA. The style of this variable varies according to a specific messaging technology. |
| respSupplementalInformation | 1.3.6.1.3.73.2.1.4.1.18 | displaystring | read-only |
Contains information provided by the agent to the manager that may be of use in identifying or tracking this message. No formal structure for this information is specified. Knowledge of the contents of this field is by bilateral agreement. |
| respSubject | 1.3.6.1.3.73.2.1.4.1.19 | displaystring | read-only |
The full text of the subject of the tracked message |
| respMsgType | 1.3.6.1.3.73.2.1.4.1.20 | msgtype | read-only |
The type of the tracked message |
| messageTrackingConformance | 1.3.6.1.3.73.2.1.5 | |||
| messageTrackingGroups | 1.3.6.1.3.73.2.1.5.1 | |||
| msgIdGroup | 1.3.6.1.3.73.2.1.5.1.1 |
A collection of objects for tracking messages where the messageId is known with responses containing basic message information. |
||
| basicGroup | 1.3.6.1.3.73.2.1.5.1.2 |
A collection of objects for tracking messages where the messageId is not known with responses containing basic message information. |
||
| enhancedGroup | 1.3.6.1.3.73.2.1.5.1.3 |
A collection of objects for tracking messages where the messageId is not known with responses containing enhanced message information as well as enhanced query capabilities. |
||
| gatewayGroup | 1.3.6.1.3.73.2.1.5.1.4 |
A collection of object for tracking messages that have passed through a gateway mta. |
||
| messageTrackingCompliances | 1.3.6.1.3.73.2.1.5.2 | |||
| limitedCompliance | 1.3.6.1.3.73.2.1.5.2.1 |
The basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking requiring the knowledge of a message Id. |
||
| basicCompliance | 1.3.6.1.3.73.2.1.5.2.2 |
The basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking without requiring the knowledge of a message Id. |
||
| enhancedCompliance | 1.3.6.1.3.73.2.1.5.2.3 |
The basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking without requiring the knowledge of a message Id and allowing an enhanced level of query capabilities. |
||
| gatewayCompliance | 1.3.6.1.3.73.2.1.5.2.4 |
The basic levels of compliance for SNMPv2 entities that implement this MIB for message tracking across mta's that perform a gateway function. |
||