rfc1156.Management Information Base for Network Ma

NetworkWorkingGroupK.McCloghrieRequestForComments:1156HughesLANSystemsObsoletes:RFC1066M.RosePerformanceSystemsInternationalMay1990ManagementInformationBaseforNetworkManagementofTCP/IP-basedinternetsTableofContents1.StatusofthisMemo...................................12.IABPolicyStatement..................................23.Introduction..........................................24.Objects...............................................64.1ObjectGroups........................................64.2FormatofDefinitions................................75.ObjectDefinitions....................................85.1TheSystemGroup.....................................95.2TheInterfacesGroup.................................115.2.1TheInterfacesTable...............................115.3TheAddressTranslationGroup........................235.4TheIPGroup.........................................265.4.1TheIPAddressTable...............................345.4.2TheIPRoutingTable...............................365.5TheICMPGroup.......................................435.6TheTCPGroup........................................535.7TheUDPGroup........................................625.8TheEGPGroup........................................645.8.1TheEGPNeighborTable.............................656.Definitions...........................................687.Acknowledgements......................................898.References............................................909.SecurityConsiderations................................9110.Authors’Addresses....................................911.StatusofthisMemoThisRFCisare-releaseofRFC1066,withachangedStatusofthisMemo,IABPolicyStatement,andIntroductionsectionsplusafewminortypographicalcorrections.ThetechnicalcontentofthedocumentisunchangedfromRFC1066.ThismemoprovidestheinitialversionoftheManagementInformationBase(MIB)forusewithnetworkmanagementprotocolsinTCP/IP-basedinternetsintheshort-term.Inparticular,togetherwithitscompanionmemoswhichdescribethestructureofmanagementMcCloghrie&Rose[Page1]RFC1156MIBMay1990informationalongwiththeinitialnetworkmanagementprotocol,thesedocumentsprovideasimple,workablearchitectureandsystemformanagingTCP/IP-basedinternetsandinparticulartheInternet.ThismemospecifiesaStandardProtocolfortheInternetcommunity.TCP/IPimplementationsintheInternetwhicharenetworkmanageableareexpectedtoadoptandimplementthisspecification.TheInternetActivitiesBoardrecommendsthatallIPandTCPimplementationsbenetworkmanageable.ThisimpliesimplementationoftheInternetMIB(RFC-1156)andatleastoneofthetworecommendedmanagementprotocolsSNMP(RFC-1157)orCMOT(RFC-1095).Itshouldbenotedthat,atthistime,SNMPisafullInternetstandardandCMOTisadraftstandard.SeealsotheHostandGatewayRequirementsRFCsformorespecificinformationontheapplicabilityofthisstandard.PleaserefertothelatesteditionoftheIABOfficialProtocolStandardsRFCforcurrentinformationonthestateandstatusofstandardInternetprotocols.Distributionofthismemoisunlimited.2.IABPolicyStatementThisMIBspecificationisthefirsteditionofanevolvingdocumentdefiningvariablesneededformonitoringandcontrolofvariouscomponentsoftheInternet.NotallgroupsofdefinedvariablesaremandatoryforallInternetcomponents.Forexample,theEGPgroupismandatoryforgatewaysusingEGPbutnotforhostswhichshouldnotberunningEGP.Similarly,theTCPgroupismandatoryforhostsrunningTCPbutnotforgatewayswhicharen’trunningit.WhatISmandatory,however,isthatallvariablesofagroupbesupportedifanyelementofthegroupissupported.ItisexpectedthatadditionalMIBgroupsandvariableswillbedefinedovertimetoaccommodatethemonitoringandcontrolneedsofneworchangingcomponentsoftheInternet.Theresponsibleworkinggroup(s)willcontinuetorefinethisspecification.3.IntroductionAsreportedinRFC1052,IABRecommendationsfortheDevelopmentofInternetNetworkManagementStandards[1],theInternetActivitiesBoardhasdirectedtheInternetEngineeringTaskForce(IETF)tocreatetwonewworkinggroupsintheareaofnetworkmanagement.OnegroupwaschargedwiththefurtherspecificationanddefinitionofMcCloghrie&Rose[Page2]RFC1156MIBMay1990elementstobeincludedintheManagementInformationBase.TheotherwaschargedwithdefiningthemodificationstotheSimpleNetworkManagementProtocol(SNMP)toaccommodatetheshort-termneedsofthenetworkvendorandoperatorcommunities.Inthelong-term,theuseoftheOSInetworkmanagementframeworkwastobeexaminedusingtheISOCMIS/CMIP[2,3]frameworkasabasis.Twodocumentswereproducedtodefinethemanagementinformation:RFC1065,whichdefinedtheStructureofManagementInformation(SMI)[4],andRFC1066,whichdefinedtheManagementInformationBase(MIB)[5].BothofthesedocumentsweredesignedsoastobecompatiblewithboththeSNMPandtheOSInetworkmanagementframework.Thisstrategywasquitesuccessfulintheshort-term:Internet-basednetworkmanagementtechnologywasfielded,byboththeresearchandcommercialcommunities,withinafewmonths.Asaresultofthis,portionsoftheInternetcommunitybecamenetworkmanageableinatimelyfashion.AsreportedinRFC1109,ReportoftheSecondAdHocNetworkManagementReviewGroup[6],therequirementsoftheSNMPandtheOSInetworkmanagementframeworksweremoredifferentthanantic