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
22 EMail: mundy@tislabs.com
23 phone: +1 301-947-7107
26 Co-editor: David Harrington
28 postal: 35 Industrial Way
30 Rochester NH 03866-5005
32 EMail: dbh@enterasys.com
33 phone: +1 603-337-2614
35 Co-editor: Jeffrey Case
37 postal: 3001 Kimberlin Heights Road
38 Knoxville, TN 37920-9716
41 phone: +1 423-573-1434
43 Co-editor: Randy Presuhn
45 postal: 2141 North First Street
48 EMail: randy_presuhn@bmc.com
49 phone: +1 408-546-1006
51 Co-editor: Bert Wijnen
56 EMail: bwijnen@lucent.com
57 phone: +31 348-680-485
59 DESCRIPTION "The MIB for Message Processing and Dispatching
61 Copyright (C) The Internet Society (2002). This
62 version of this MIB module is part of RFC 3412;
63 see the RFC itself for full legal notices.
65 REVISION "200210140000Z" -- 14 October 2002
66 DESCRIPTION "Updated addresses, published as RFC 3412."
67 REVISION "199905041636Z" -- 4 May 1999
68 DESCRIPTION "Updated addresses, published as RFC 2572."
73 REVISION "199709300000Z" -- 30 September 1997
74 DESCRIPTION "Original version, published as RFC 2272."
75 ::= { snmpModules 11 }
77 -- Administrative assignments ***************************************
79 snmpMPDAdmin OBJECT IDENTIFIER ::= { snmpMPDMIB 1 }
80 snmpMPDMIBObjects OBJECT IDENTIFIER ::= { snmpMPDMIB 2 }
81 snmpMPDMIBConformance OBJECT IDENTIFIER ::= { snmpMPDMIB 3 }
83 -- Statistics for SNMP Messages *************************************
85 snmpMPDStats OBJECT IDENTIFIER ::= { snmpMPDMIBObjects 1 }
87 snmpUnknownSecurityModels OBJECT-TYPE
91 DESCRIPTION "The total number of packets received by the SNMP
92 engine which were dropped because they referenced a
93 securityModel that was not known to or supported by
96 ::= { snmpMPDStats 1 }
98 snmpInvalidMsgs OBJECT-TYPE
102 DESCRIPTION "The total number of packets received by the SNMP
103 engine which were dropped because there were invalid
104 or inconsistent components in the SNMP message.
106 ::= { snmpMPDStats 2 }
108 snmpUnknownPDUHandlers OBJECT-TYPE
112 DESCRIPTION "The total number of packets received by the SNMP
113 engine which were dropped because the PDU contained
114 in the packet could not be passed to an application
115 responsible for handling the pduType, e.g. no SNMP
116 application had registered for the proper
117 combination of the contextEngineID and the pduType.
119 ::= { snmpMPDStats 3 }
124 -- Conformance information ******************************************
126 snmpMPDMIBCompliances OBJECT IDENTIFIER ::= {snmpMPDMIBConformance 1}
127 snmpMPDMIBGroups OBJECT IDENTIFIER ::= {snmpMPDMIBConformance 2}
129 -- Compliance statements
131 snmpMPDCompliance MODULE-COMPLIANCE
133 DESCRIPTION "The compliance statement for SNMP entities which
134 implement the SNMP-MPD-MIB.
136 MODULE -- this module
137 MANDATORY-GROUPS { snmpMPDGroup }
138 ::= { snmpMPDMIBCompliances 1 }
140 snmpMPDGroup OBJECT-GROUP
142 snmpUnknownSecurityModels,
144 snmpUnknownPDUHandlers
147 DESCRIPTION "A collection of objects providing for remote
148 monitoring of the SNMP Message Processing and
151 ::= { snmpMPDMIBGroups 1 }