📄 gated.rf
字号:
.\" $Id: gated.rf,v 1.4 1998/09/15 16:48:24 wfs Exp $.\" experimental.rf - your comments here.\" replace TITLE, DATE, AUTHOR, ADDRESS, E-MAIL.\" xx, yy, MMM, XXX.\".\" ------------------------------------------------------------------------.\" .\" Copyright (c) 1996, 1997 The Regents of the University of Michigan.\" All Rights Reserved.\" .\" Royalty-free licenses to redistribute GateD Release.\" 3 in whole or in part may be obtained by writing to:.\" .\" Merit GateDaemon Project.\" 4251 Plymouth Road, Suite C.\" Ann Arbor, MI 48105.\" .\" THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER.\" EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE REGENTS OF THE.\" UNIVERSITY OF MICHIGAN AND MERIT DO NOT WARRANT THAT THE.\" FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET LICENSEE'S REQUIREMENTS OR.\" THAT OPERATION WILL BE UNINTERRUPTED OR ERROR FREE. The Regents of the.\" University of Michigan and Merit shall not be liable for.\" any special, indirect, incidental or consequential damages with respect.\" to any claim by Licensee or any third party arising from use of the.\" software. GateDaemon was originated and developed through release 3.0.\" by Cornell University and its collaborators..\" .\" Please forward bug fixes, enhancements and questions to the.\" gated mailing list: gated-people@gated.merit.edu..\" .\" ------------------------------------------------------------------------.\" .\" Copyright (c) 1990,1991,1992,1993,1994,1995 by Cornell University..\" All rights reserved..\" .\" THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY.\" EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT.\" LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY.\" AND FITNESS FOR A PARTICULAR PURPOSE..\" .\" GateD is based on Kirton's EGP, UC Berkeley's routing.\" daemon (routed), and DCN's HELLO routing Protocol..\" Development of GateD has been supported in part by the.\" National Science Foundation..\" .\" ------------------------------------------------------------------------.\" .\" Portions of this software may fall under the following.\" copyrights:.\" .\" Copyright (c) 1988 Regents of the University of California..\" All rights reserved..\" .\" Redistribution and use in source and binary forms are.\" permitted provided that the above copyright notice and.\" this paragraph are duplicated in all such forms and that.\" any documentation, advertising materials, and other.\" materials related to such distribution and use.\" acknowledge that the software was developed by the.\" University of California, Berkeley. The name of the.\" University may not be used to endorse or promote.\" products derived from this software without specific.\" prior written permission. THIS SOFTWARE IS PROVIDED.\" ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,.\" INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE..\".ie \nh \{\.ll 66 .po 2 \}.el \{\.ll 62 .pl 58.nr sf R.nr fm 0 \}.he 'Internet Draft'Gated MIB'%%TODAY%%'.fo 'Jeffrey C. Honig''[Page %]'.de $0.(x t\\$2 \\$1.)x...lp.na.nh.ceGated MIB.sp 1.ce%%TODAY%%.sp 2.ceJeffrey C. Honig.sp 1.ce 4Information Technologies/Network ResourcesCornell University143 Caldwell HallIthaca, NY 14853-2602.sp 1.cejch@nr-tech.cit.cornell.edu.sp 5.sh 1 "Status of this Memo".lpThis draft document will be submitted to the RFC editor as anexperimental extension to the SNMP MIB.Distribution of this memo is unlimited.Please send comments to the author..sh 1 "Abstract".lpThis memo defines an enterprise portion of the ManagementInformation Base (MIB) for use with network management protocols inTCP/IP-based internets.In particular,it defines objects for managing Gated..lpThis memo does not specify a standard for the Internet community..bp.sh 1 "The Network Management Framework".lpThe Internet-standard Network Management Framework consists of threecomponents.They are:.in +.25i.lpRFC 1155 which defines the SMI, the mechanisms used for describing and namingobjects for the purpose of management.RFC 1212 defines a more concise description mechanism, which is whollyconsistent with the SMI..lpRFC 1156 which defines MIB-I,the core set of managed objects for the Internet suite of protocols.RFC 1213 defines MIB-II,an evolution of MIB-I based on implementation experience and new operationalrequirements..lpRFC 1157 which defines the SNMP,the protocol used for network access to managed objects..in -.25i.lpThe Framework permits new objects to be defined for the purpose ofexperimentation and evaluation..bp.sh 1 "Objects".lpManaged objects are accessed via a virtual information store,termed the Management Information Base or MIB.Objects in the MIB are defined using the subset of Abstract Syntax Notation One(ASN.1) [7] defined in the SMI.In particular,each object has a name, a syntax, and an encoding.The name is an object identifier,an administratively assigned name,which specifies an object type.The object type together with an object instance serves to uniquely identifya specific instantiation of the object.For human convenience,we often use a textual string,termed the OBJECT DESCRIPTOR,to also refer to the object type..lpThe syntax of an object type defines the abstract data structurecorresponding to that object type.The ASN.1 language is used for this purpose.However, the SMI [3] purposely restricts the ASN.1constructs which may be used.These restrictions are explicitly made for simplicity..lpThe encoding of an object type is simply how that object type is representedusing the object type's syntax.Implicitly tied to the notion of an object type's syntax and encoding is howthe object type is represented when being transmitted on the network..lpThe SMI specifies the use of the basic encoding rules of ASN.1 [8],subject to the additional requirements imposed by the SNMP..sh 2 "Format of Definitions".lpSection 6 contains contains the specification of all object types containedin this MIB module.The object types are defined using the conventions defined in the SMI,as amended by the extensions specified in [9,10]..bp.sh 1 "Overview".lp.\".\" IF YOU WISH TO DEFINE ANY EXPOSITORY Syntax TYPES IN THIS MIB,.\" THEN UNCOMMENT THE FOLLOWING SECTION AND FILL IN THE APPROPRIATE .\" DEFINITONS IN SECTION 6..\".\" .sh 2 "Textual Conventions".\" .lp.\" Several new data types are introduced as a textual convention.\" in this MIB document..\" These textual conventions enhance the.\" readability of the specification and can ease comparison with .\" other specifications if appropriate..\" It should be noted that the introduction of the.\" these textual conventions has no effect on either the.\" syntax nor the semantics of any managed objects..\" The use of these is merely an artifact of the explanatory method used..\" Objects defined in terms of one of these methods are always.\" encoded by means of the rules that define the primitive type..\" Hence, no changes to the SMI or the SNMP are necessary to.\" accommodate these textual conventions which are adopted merely.\" for the convenience of readers and writers in pursuit of the.\" elusive goal of clear, concise, and unambiguous MIB documents..\" .lp.\" The new data types are: Nnn, Ooo, Ppp..sh 2 "Structure of MIB".lpINCLUDE TEXT HERE DESCRIBING OVERALL STRUCTURE OF MIB DEFINTIONS..bp.sh 1 "Definitions".sp.nfGATED-MIB DEFINITIONS ::= BEGINIMPORTS enterprises FROM RFC1155\-SMI OBJECT-TYPE FROM RFC-oooo TRAP-TYPE FROM RFC-tttt;-- This MIB module uses the extended OBJECT-TYPE macro as-- defined in [9], and the TRAP-TYPE macro as defined in [10]-- Titlegated OBJECT IDENTIFIER ::= { enterprises 51 }.\" .\" IF YOU ARE DEFINING ANY NEW EXPOSITORY Syntax TYPES, INCLUDE.\" THEM HERE, E.G.,.\" .\" Nnn ::= OCTET STRING (SIZE (4)).\" .\" -- This data type is used for ....\" --.so gatedAgents.rf.so gatedGeneral.rf.so gatedInet.rf.so gatedConfig.rfEND.fi.bp.sh 1 "Acknowledgements".lpThis document was produced by Jeffrey C. Honig:.sp.in +.5i.nf.fi.in -.5i.lpIn addition,the comments of the following individuals are also acknowledged:.sp.in +.5i.nf.fi.in -.5i.bp.sh 1 "References".ip [1]V.\0Cerf,IAB Recommendations for the Development of Internet NetworkManagement Standards.Internet Working Group Request for Comments 1052.Network Information Center, SRI International, Menlo Park, California,(April, 1988)..ip [2]V.\0Cerf,Report of the Second Ad Hoc Network Management Review Group,Internet Working Group Request for Comments 1109.Network Information Center, SRI International, Menlo Park, California,(August, 1989)..ip [3]M.T.\0Rose and K.\0McCloghrie,Structure and Identification of Management Information forTCP/IP\-based internets,Internet Working Group Request for Comments 1155.Network Information Center, SRI International, Menlo Park, California,(May, 1990)..ip [4]K.\0McCloghrie and M.T.\0Rose,Management Information Base for Network Management of TCP/IP-basedinternets,Internet Working Group Request for Comments 1156.Network Information Center, SRI International, Menlo Park, California,(May, 1990)..ip [5]J.D.\0Case, M.S.\0Fedor, M.L.\0Schoffstall, and J.R.\0Davin,Simple Network Management Protocol,Internet Working Group Request for Comments 1157.Network Information Center, SRI International, Menlo Park, California,(May, 1990)..ip [6]M.T.\0Rose (editor),Management Information Base for Network Management of TCP/IP-basedinternets,Internet Working Group Request for Comments 1158.Network Information Center, SRI International, Menlo Park, California,(May, 1990)..ip [7]Information processing systems \(em Open Systems Interconnection \(emSpecification of Abstract Syntax Notation One (ASN.1), InternationalOrganization for Standardization.International Standard 8824,(December, 1987)..ip [8]Information processing systems \(em Open Systems Interconnection \(emSpecification of Basic Encoding Rules for Abstract NotationOne (ASN.1),International Organization for Standardization.International Standard 8825,(December, 1987)..ip [9]M.T.\0Rose, K.\0McCloghrie (editors),Towards Concise MIB Definitions,Internet Draft,Internet Engineering Task Force,(September, 1990)..ip [10]M.T.\0Rose (editor),A Convention for Defining Traps for use with the SNMP,Internet Draft,Internet Engineering Task Force,(September, 1990)..bp.lpTable of Contents.sp 2.xp t.\".\" ------------------------------------------------------------------------.\" .\" Copyright (c) 1996, 1997 The Regents of the University of Michigan.\" All Rights Reserved.\" .\" Royalty-free licenses to redistribute GateD Release.\" 3 in whole or in part may be obtained by writing to:.\" .\" Merit GateDaemon Project.\" 4251 Plymouth Road, Suite C.\" Ann Arbor, MI 48105.\" .\" THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER.\" EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE REGENTS OF THE.\" UNIVERSITY OF MICHIGAN AND MERIT DO NOT WARRANT THAT THE.\" FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET LICENSEE'S REQUIREMENTS OR.\" THAT OPERATION WILL BE UNINTERRUPTED OR ERROR FREE. The Regents of the.\" University of Michigan and Merit shall not be liable for.\" any special, indirect, incidental or consequential damages with respect.\" to any claim by Licensee or any third party arising from use of the.\" software. GateDaemon was originated and developed through release 3.0.\" by Cornell University and its collaborators..\" .\" Please forward bug fixes, enhancements and questions to the.\" gated mailing list: gated-people@gated.merit.edu..\" .\" ------------------------------------------------------------------------.\" .\" Copyright (c) 1990,1991,1992,1993,1994,1995 by Cornell University..\" All rights reserved..\" .\" THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY.\" EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT.\" LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY.\" AND FITNESS FOR A PARTICULAR PURPOSE..\" .\" GateD is based on Kirton's EGP, UC Berkeley's routing.\" daemon (routed), and DCN's HELLO routing Protocol..\" Development of GateD has been supported in part by the.\" National Science Foundation..\" .\" ------------------------------------------------------------------------.\" .\" Portions of this software may fall under the following.\" copyrights:.\" .\" Copyright (c) 1988 Regents of the University of California..\" All rights reserved..\" .\" Redistribution and use in source and binary forms are.\" permitted provided that the above copyright notice and.\" this paragraph are duplicated in all such forms and that.\" any documentation, advertising materials, and other.\" materials related to such distribution and use.\" acknowledge that the software was developed by the.\" University of California, Berkeley. The name of the.\" University may not be used to endorse or promote.\" products derived from this software without specific.\" prior written permission. THIS SOFTWARE IS PROVIDED.\" ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,.\" INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE..\"
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -