rfc2573.SNMP Applications

NetworkWorkingGroupD.LeviRequestforComments:2573SNMPResearch,Inc.Obsoletes:2273P.MeyerCategory:StandardsTrackSecureComputingCorporationB.StewartCiscoSystemsApril1999SNMPApplicationsStatusofthisMemoThisdocumentspecifiesanInternetstandardstrackprotocolfortheInternetcommunity,andrequestsdiscussionandsuggestionsforimprovements.PleaserefertothecurrenteditionoftheInternetOfficialProtocolStandards(STD1)forthestandardizationstateandstatusofthisprotocol.Distributionofthismemoisunlimited.CopyrightNoticeCopyright(C)TheInternetSociety(1999).AllRightsReserved.AbstractThismemodescribesfivetypesofSNMPapplicationswhichmakeuseofanSNMPengineasdescribedin[RFC2571].ThetypesofapplicationdescribedareCommandGenerators,CommandResponders,NotificationOriginators,NotificationReceivers,andProxyForwarders.ThismemoalsodefinesMIBmodulesforspecifyingtargetsofmanagementoperations,fornotificationfiltering,andforproxyforwarding.TableOfContents1Overview.....................................................21.1CommandGeneratorApplications.............................31.2CommandResponderApplications.............................31.3NotificationOriginatorApplications.......................31.4NotificationReceiverApplications.........................31.5ProxyForwarderApplications...............................42ManagementTargets...........................................53ElementsOfProcedure........................................63.1CommandGeneratorApplications.............................63.2CommandResponderApplications.............................93.3NotificationOriginatorApplications.......................143.4NotificationReceiverApplications.........................17Levi,etal.StandardsTrack[Page1]RFC2573SNMPApplicationsApril19993.5ProxyForwarderApplications...............................193.5.1RequestForwarding.......................................203.5.1.1ProcessinganIncomingRequest.........................203.5.1.2ProcessinganIncomingResponse........................233.5.1.3ProcessinganIncomingInternal-ClassPDU..............243.5.2NotificationForwarding..................................254TheStructureoftheMIBModules.............................284.1TheManagementTargetMIBModule...........................284.1.1TagLists................................................294.1.2Definitions..............................................304.2TheNotificationMIBModule................................434.2.1Definitions..............................................434.3TheProxyMIBModule.......................................554.3.1Definitions..............................................555IdentificationofManagementTargetsinNotificationOriginators...............................................616NotificationFiltering.......................................627ManagementTargetTranslationinProxyForwarderApplica-tions.....................................................637.1ManagementTargetTranslationforRequestForwarding.......637.2ManagementTargetTranslationforNotificationForwarding...........................................................648IntellectualProperty........................................659Acknowledgments..............................................6610SecurityConsiderations.....................................6711References..................................................6712Editors’Addresses...........................................69A.TrapConfigurationExample..................................70B.FullCopyrightStatement....................................721.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,etal.StandardsTrack[Page2]RFC2573SNMPApplicationsApril1999NotethattherearenorestrictionsonwhichtypesofapplicationsmaybeassociatedwithaparticularSNMPengine.Forexample,asingleSNMPenginemay,infact,beassociatedwithbothcommandgeneratorandcommandresponderapplications.ThekeywordsMUST,MUSTNOT,REQUIRED,SHALL,SHALLNOT,SHOULD,SHOULDNOT,RECOMMENDED,MAY,andOPTIONALinthisdocumentaretobeinterpretedasdescribedin[RFC2119].1.1.CommandGeneratorApplicationsAcommandgeneratorapplicationinitiatesSNMPRead-Classand/orWrite-Classrequests,aswellasprocessingtheresponsetoarequestwhichitgenerated.1.2.CommandResponderApplicationsAcommandresponderapplicationreceivesSNMPRead-Classand/orWrite-ClassrequestsdestinedforthelocalsystemasindicatedbythefactthatthecontextEngineIDinthereceivedrequestisequaltothatofthelocalenginethroughwhichtherequestwasreceived.Thecommandresponderapplicationwillperformtheappropriateprotocoloperation,usingaccesscontrol,andwillgeneratearesponsemessagetobesenttotherequest’soriginator.1.3.NotificationOriginatorApplicationsAnotifi