rfc3413.Simple Network Management Protocol (SNMP)

NetworkWorkingGroupD.LeviRequestforComments:3413NortelNetworksSTD:62P.MeyerObsoletes:2573SecureComputingCorporationCategory:StandardsTrackB.StewartRetiredDecember2002SimpleNetworkManagementProtocol(SNMP)ApplicationsStatusofthisMemoThisdocumentspecifiesanInternetstandardstrackprotocolfortheInternetcommunity,andrequestsdiscussionandsuggestionsforimprovements.PleaserefertothecurrenteditionoftheInternetOfficialProtocolStandards(STD1)forthestandardizationstateandstatusofthisprotocol.Distributionofthismemoisunlimited.AbstractThisdocumentdescribesfivetypesofSimpleNetworkManagementProtocol(SNMP)applicationswhichmakeuseofanSNMPengineasdescribedinSTD62,RFC3411.ThetypesofapplicationdescribedareCommandGenerators,CommandResponders,NotificationOriginators,NotificationReceivers,andProxyForwarders.ThisdocumentalsodefinesManagementInformationBase(MIB)modulesforspecifyingtargetsofmanagementoperations,fornotificationfiltering,andforproxyforwarding.ThisdocumentobsoletesRFC2573.TableofContents1Overview...............................................21.1CommandGeneratorApplications.........................31.2CommandResponderApplications.........................31.3NotificationOriginatorApplications...................31.4NotificationReceiverApplications.....................31.5ProxyForwarderApplications...........................42ManagementTargets.....................................53ElementsOfProcedure..................................63.1CommandGeneratorApplications.........................63.2CommandResponderApplications.........................93.3NotificationOriginatorApplications...................143.4NotificationReceiverApplications.....................173.5ProxyForwarderApplications...........................193.5.1RequestForwarding.....................................21Levi,et.al.StandardsTrack[Page1]RFC3413SNMPApplicationsDecember20023.5.1.1ProcessinganIncomingRequest.........................213.5.1.2ProcessinganIncomingResponse........................243.5.1.3ProcessinganIncomingInternal-ClassPDU..............253.5.2NotificationForwarding................................264TheStructureoftheMIBModules.......................294.1TheManagementTargetMIBModule.......................294.1.1TagLists.....................,........................294.1.2Definitions..................,.........................304.2TheNotificationMIBModule............................444.2.1Definitions............................................444.3TheProxyMIBModule...................................564.3.1Definitions............................................575IdentificationofManagementTargetsinNotificationOriginators...............................636NotificationFiltering.................................647ManagementTargetTranslationinProxyForwarderApplications...........................657.1ManagementTargetTranslationforRequestForwarding.....................................657.2ManagementTargetTranslationforNotificationForwarding................................668IntellectualProperty..................................679Acknowledgments........................................6710SecurityConsiderations................................6911References.............................................69A.TrapConfigurationExample.............................71Editors’Addresses.....................................73FullCopyrightStatement...............................741.OverviewThisdocumentdescribesfivetypesofSNMPapplications:-ApplicationswhichinitiateSNMPRead-Class,and/orWrite-Classrequests,called’commandgenerators.’-ApplicationswhichrespondtoSNMPRead-Class,and/orWrite-Classrequests,called’commandresponders.’-ApplicationswhichgenerateSNMPNotification-ClassPDUs,called’notificationoriginators.’-ApplicationswhichreceiveSNMPNotification-ClassPDUs,called’notificationreceivers.’-ApplicationswhichforwardSNMPmessages,called’proxyforwarders.’Levi,et.al.StandardsTrack[Page2]RFC3413SNMPApplicationsDecember2002NotethattherearenorestrictionsonwhichtypesofapplicationsmaybeassociatedwithaparticularSNMPengine.Forexample,asingleSNMPenginemay,infact,beassociatedwithbothcommandgeneratorandcommandresponderapplications.ThekeywordsMUST,MUSTNOT,REQUIRED,SHALL,SHALLNOT,SHOULD,SHOULDNOT,RECOMMENDED,MAY,andOPTIONALinthisdocumentaretobeinterpretedasdescribedin[RFC2119].1.1.CommandGeneratorApplicationsAcommandgeneratorapplicationinitiatesSNMPRead-Classand/orWrite-Classrequests,andprocessesresponsestorequestswhichitgenerated.1.2.CommandResponderApplicationsAcommandresponderapplicationreceivesSNMPRead-Classand/orWrite-ClassrequestsdestinedforthelocalsystemasindicatedbythefactthatthecontextEngineIDinthereceivedrequestisequaltothatofthelocalenginethroughwhichtherequestwasreceived.Thecommandresponderapplicationwillperformtheappropriateprotocoloperation,usingaccesscontrol,andwillgeneratearesponsemessagetobesenttotherequest’soriginator.1.3.NotificationOriginatorApplicationsAnotificationoriginatorapplicationconceptuallymonitorsasystemforparticulareventsorconditions,andgeneratesNotification-