ActiveXperts Network Monitor 2019##AdminFavorites

MIME-MHS by vendor RFC

MIME-MHS file content

The SNMP protocol is used to for conveying information and commands between agents and managing entities. SNMP uses the User Datagram Protocol (UDP) as the transport protocol for passing data between managers and agents. The reasons for using UDP for SNMP are, firstly it has low overheads in comparison to TCP, which uses a 3-way hand shake for connection. Secondly, in congested networks, SNMP over TCP is a bad idea because TCP in order to maintain reliability will flood the network with retransmissions.

Management information (MIB) is represented as a collection of managed objects. These objects together form a virtual information base called MIB. An agent may implement many MIBs, but all agents must implement a particular MIB called MIB-II [16]. This standard defines variables for things such as interface statistics (interface speeds, MTU, octets sent, octets received, etc.) as well as various other things pertaining to the system itself (system location, system contact, etc.). The main goal of MIB-II is to provide general TCP/IP management information.

Use ActiveXperts Network Monitor 2019 to import vendor-specific MIB files, inclusing MIME-MHS.


Vendor: RFC
Mib: MIME-MHS  [download]  [view objects]
Tool: ActiveXperts Network Monitor 2019 [download]    (ships with advanced SNMP/MIB tools)
-- WinAgents MIB Extraction Wizard
-- Extracted from rfc1495.txt 16.03.2005 20:20:18

MIME-MHS DEFINITIONS ::= BEGIN


mail OBJECT IDENTIFIER ::= { internet 7 }

mime-mhs OBJECT IDENTIFIER ::= { mail 1 }

mime-mhs-headings OBJECT IDENTIFIER ::= { mime-mhs 1 }

id-hex-partial-message OBJECT IDENTIFIER ::=
        { mime-mhs-headings 1 }

id-hex-multipart-message OBJECT IDENTIFIER ::=
        { mime-mhs-headings 2 }


mime-mhs-bodies OBJECT IDENTIFIER ::= { mime-mhs 2 }


END