1 SNMP-MPD-MIB DEFINITIONS ::= BEGIN
4 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
5 MODULE-IDENTITY, OBJECT-TYPE,
6 snmpModules, Counter32 FROM SNMPv2-SMI;
8 snmpMPDMIB MODULE-IDENTITY
9 LAST-UPDATED "200210140000Z"
10 ORGANIZATION "SNMPv3 Working Group"
11 CONTACT-INFO "WG-EMail: snmpv3@lists.tislabs.com
12 Subscribe: snmpv3-request@lists.tislabs.com
15 Network Associates Laboratories
16 postal: 15204 Omega Drive, Suite 300
17 Rockville, MD 20850-4601
20 EMail: mundy@tislabs.com
21 phone: +1 301-947-7107
24 Co-editor: David Harrington
26 postal: 35 Industrial Way
28 Rochester NH 03866-5005
30 EMail: dbh@enterasys.com
31 phone: +1 603-337-2614
33 Co-editor: Jeffrey Case
35 postal: 3001 Kimberlin Heights Road
36 Knoxville, TN 37920-9716
39 phone: +1 423-573-1434
41 Co-editor: Randy Presuhn
43 postal: 2141 North First Street
46 EMail: randy_presuhn@bmc.com
47 phone: +1 408-546-1006
49 Co-editor: Bert Wijnen
54 EMail: bwijnen@lucent.com
55 phone: +31 348-680-485
57 DESCRIPTION "The MIB for Message Processing and Dispatching
59 Copyright (C) The Internet Society (2002). This
60 version of this MIB module is part of RFC 3412;
61 see the RFC itself for full legal notices.
63 REVISION "200210140000Z" -- 14 October 2002
64 DESCRIPTION "Updated addresses, published as RFC 3412."
65 REVISION "199905041636Z" -- 4 May 1999
66 DESCRIPTION "Updated addresses, published as RFC 2572."
68 REVISION "199709300000Z" -- 30 September 1997
69 DESCRIPTION "Original version, published as RFC 2272."
70 ::= { snmpModules 11 }
72 -- Administrative assignments ***************************************
74 snmpMPDAdmin OBJECT IDENTIFIER ::= { snmpMPDMIB 1 }
75 snmpMPDMIBObjects OBJECT IDENTIFIER ::= { snmpMPDMIB 2 }
76 snmpMPDMIBConformance OBJECT IDENTIFIER ::= { snmpMPDMIB 3 }
78 -- Statistics for SNMP Messages *************************************
80 snmpMPDStats OBJECT IDENTIFIER ::= { snmpMPDMIBObjects 1 }
82 snmpUnknownSecurityModels OBJECT-TYPE
86 DESCRIPTION "The total number of packets received by the SNMP
87 engine which were dropped because they referenced a
88 securityModel that was not known to or supported by
91 ::= { snmpMPDStats 1 }
93 snmpInvalidMsgs OBJECT-TYPE
97 DESCRIPTION "The total number of packets received by the SNMP
98 engine which were dropped because there were invalid
99 or inconsistent components in the SNMP message.
101 ::= { snmpMPDStats 2 }
103 snmpUnknownPDUHandlers OBJECT-TYPE
107 DESCRIPTION "The total number of packets received by the SNMP
108 engine which were dropped because the PDU contained
109 in the packet could not be passed to an application
110 responsible for handling the pduType, e.g. no SNMP
111 application had registered for the proper
112 combination of the contextEngineID and the pduType.
114 ::= { snmpMPDStats 3 }
116 -- Conformance information ******************************************
118 snmpMPDMIBCompliances OBJECT IDENTIFIER ::= {snmpMPDMIBConformance 1}
119 snmpMPDMIBGroups OBJECT IDENTIFIER ::= {snmpMPDMIBConformance 2}
121 -- Compliance statements
123 snmpMPDCompliance MODULE-COMPLIANCE
125 DESCRIPTION "The compliance statement for SNMP entities which
126 implement the SNMP-MPD-MIB.
128 MODULE -- this module
129 MANDATORY-GROUPS { snmpMPDGroup }
130 ::= { snmpMPDMIBCompliances 1 }
132 snmpMPDGroup OBJECT-GROUP
134 snmpUnknownSecurityModels,
136 snmpUnknownPDUHandlers
139 DESCRIPTION "A collection of objects providing for remote
140 monitoring of the SNMP Message Processing and
143 ::= { snmpMPDMIBGroups 1 }