⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2466.txt

📁 著名的RFC文档,其中有一些文档是已经翻译成中文的的.
💻 TXT
📖 第 1 页 / 共 2 页
字号:
Network Working Group                                        D. HaskinRequest for Comments: 2466                                   S. OnishiCategory: Standards Track                           Bay Networks, Inc.                                                         December 1998             Management Information Base for IP Version 6:                              ICMPv6 GroupStatus of this Memo   This document specifies an Internet standards track protocol for the   Internet community, and requests discussion and suggestions for   improvements.  Please refer to the current edition of the "Internet   Official Protocol Standards" (STD 1) for the standardization state   and status of this protocol.  Distribution of this memo is unlimited.Copyright Notice   Copyright (C) The Internet Society (1998).  All Rights Reserved.Abstract   This document is one in the series of documents that define various   MIB object groups for IPv6.  Specifically, the ICMPv6 group is   defined in this document.   This memo defines a portion of the Management Information Base (MIB)   for use with network management protocols in the IPv6-based   internets.   This document specifies a MIB module in a manner that is both   compliant to the SNMPv2 SMI, and semantically identical to the peer   SNMPv1 definitions.Table of Contents   1.  The SNMPv2 Network Management Framework .............    2   1.1   Object Definitions ................................    2   2.  Overview ............................................    2   3.  The ICMPv6 Group ....................................    3   4.  Acknowledgments ....................................    14   5.  References ..........................................   14   6.  Security Considerations .............................   15   7.  Authors' Addresses...................................   15   8.  Full Copyright Statement.............................   16Haskin & Onishi             Standards Track                     [Page 1]RFC 2466                 IPv6 MIB: ICMPv6 Group            December 19981.  The SNMPv2 Network Management Framework   The SNMPv2 Network Management Framework presently consists of three   major components.  They are:   o the SMI, described in RFC 1902 [1] - the mechanisms used for     describing and naming objects for the purpose of management.   o the MIB-II, described in RFC 1213/STD 17 [3] - the core set of     managed objects for the Internet suite of protocols.   o RFC 1157/STD 15 [4] and RFC 1905 [5] which define two versions of the     protocol used for network access to managed objects.   The Framework permits new objects to be defined for the purpose of   experimentation and evaluation.1.1.  Object Definitions   Managed 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)   defined in the SMI.  In particular, each object type is named by an   OBJECT IDENTIFIER, an administratively assigned name.  The object type   together with an object instance serves to uniquely identify a   specific instantiation of the object.  For human convenience, we often   use a textual string, termed the descriptor, to refer to the object   type.2.  Overview   This document is the one in the series of documents that define   various MIB object groups for IPv6. These groups are the basic unit of   conformance: if the semantics of a group is applicable to an   implementation, then it must implement all objects in that group.  For   example, an implementation must implement the TCP group if and only if   it implements the TCP over IPv6 protocol.  At minimum, implementations   must implement the IPv6 General group [9] as well as the ICMPv6 group   defined in this document.   This document defines the ICMPv6 group of the IPv6 MIB.Haskin & Onishi             Standards Track                     [Page 2]RFC 2466                 IPv6 MIB: ICMPv6 Group            December 19983.  The ICMPv6 Group    IPV6-ICMP-MIB DEFINITIONS ::= BEGIN    IMPORTS        MODULE-IDENTITY, OBJECT-TYPE,        Counter32, mib-2                 FROM SNMPv2-SMI        MODULE-COMPLIANCE, OBJECT-GROUP  FROM SNMPv2-CONF        ipv6IfEntry                      FROM IPV6-MIB;    ipv6IcmpMIB MODULE-IDENTITY        LAST-UPDATED "9801082155Z"        ORGANIZATION "IETF IPv6 Working Group"        CONTACT-INFO          "           Dimitry Haskin              Postal: Bay Networks, Inc.                      660 Techology Park Drive.                      Billerica, MA  01821                      US                 Tel: +1-978-916-8124              E-mail: dhaskin@baynetworks.com                      Steve Onishi              Postal: Bay Networks, Inc.                      3 Federal Street                      Billerica, MA 01821                      US                 Tel: +1-978-916-3816              E-mail: sonishi@baynetworks.com"        DESCRIPTION          "The MIB module for entities implementing           the ICMPv6."        ::= { mib-2 56 }    -- the ICMPv6 group    ipv6IcmpMIBObjects OBJECT IDENTIFIER ::= { ipv6IcmpMIB  1 }    -- Per-interface ICMPv6 statistics table    ipv6IfIcmpTable OBJECT-TYPE        SYNTAX     SEQUENCE OF Ipv6IfIcmpEntry        MAX-ACCESS not-accessibleHaskin & Onishi             Standards Track                     [Page 3]RFC 2466                 IPv6 MIB: ICMPv6 Group            December 1998        STATUS     current        DESCRIPTION         "IPv6 ICMP statistics. This table contains statistics         of ICMPv6 messages that are received and sourced by         the entity."        ::= { ipv6IcmpMIBObjects 1 }    ipv6IfIcmpEntry OBJECT-TYPE        SYNTAX     Ipv6IfIcmpEntry        MAX-ACCESS not-accessible        STATUS     current        DESCRIPTION         "An ICMPv6 statistics entry containing         objects at a particular IPv6 interface.         Note that a receiving interface is         the interface to which a given ICMPv6 message         is addressed which may not be necessarily         the input interface for the message.         Similarly,  the sending interface is         the interface that sources a given         ICMP message which is usually but not         necessarily the output interface for the message."        AUGMENTS { ipv6IfEntry }        ::= { ipv6IfIcmpTable 1 }    Ipv6IfIcmpEntry ::= SEQUENCE {            ipv6IfIcmpInMsgs                  Counter32      ,            ipv6IfIcmpInErrors                  Counter32      ,            ipv6IfIcmpInDestUnreachs                  Counter32      ,            ipv6IfIcmpInAdminProhibs                  Counter32      ,            ipv6IfIcmpInTimeExcds                  Counter32      ,            ipv6IfIcmpInParmProblems                  Counter32      ,            ipv6IfIcmpInPktTooBigs                  Counter32      ,            ipv6IfIcmpInEchos                  Counter32      ,            ipv6IfIcmpInEchoReplies                  Counter32      ,            ipv6IfIcmpInRouterSolicits                  Counter32      ,Haskin & Onishi             Standards Track                     [Page 4]RFC 2466                 IPv6 MIB: ICMPv6 Group            December 1998            ipv6IfIcmpInRouterAdvertisements                  Counter32      ,            ipv6IfIcmpInNeighborSolicits                  Counter32      ,            ipv6IfIcmpInNeighborAdvertisements                  Counter32      ,            ipv6IfIcmpInRedirects                  Counter32      ,            ipv6IfIcmpInGroupMembQueries                  Counter32      ,            ipv6IfIcmpInGroupMembResponses                  Counter32      ,            ipv6IfIcmpInGroupMembReductions                  Counter32      ,            ipv6IfIcmpOutMsgs                  Counter32      ,            ipv6IfIcmpOutErrors                  Counter32      ,            ipv6IfIcmpOutDestUnreachs                  Counter32      ,            ipv6IfIcmpOutAdminProhibs                  Counter32      ,            ipv6IfIcmpOutTimeExcds                  Counter32      ,            ipv6IfIcmpOutParmProblems                  Counter32      ,            ipv6IfIcmpOutPktTooBigs                  Counter32      ,            ipv6IfIcmpOutEchos                  Counter32      ,            ipv6IfIcmpOutEchoReplies                  Counter32      ,            ipv6IfIcmpOutRouterSolicits                  Counter32      ,            ipv6IfIcmpOutRouterAdvertisements                  Counter32      ,            ipv6IfIcmpOutNeighborSolicits                  Counter32      ,            ipv6IfIcmpOutNeighborAdvertisements                  Counter32      ,            ipv6IfIcmpOutRedirects                  Counter32      ,            ipv6IfIcmpOutGroupMembQueries                  Counter32      ,            ipv6IfIcmpOutGroupMembResponses                  Counter32      ,            ipv6IfIcmpOutGroupMembReductions                  Counter32Haskin & Onishi             Standards Track                     [Page 5]RFC 2466                 IPv6 MIB: ICMPv6 Group            December 1998        }    ipv6IfIcmpInMsgs OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The total number of ICMP messages received         by the interface which includes all those         counted by ipv6IfIcmpInErrors. Note that this         interface is the interface to which the         ICMP messages were addressed which may not be         necessarily the input interface for the messages."        ::= { ipv6IfIcmpEntry 1 }    ipv6IfIcmpInErrors OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP messages which the interface         received but determined as having ICMP-specific         errors (bad ICMP checksums, bad length, etc.)."        ::= { ipv6IfIcmpEntry 2 }    ipv6IfIcmpInDestUnreachs OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Destination Unreachable         messages received by the interface."        ::= { ipv6IfIcmpEntry 3 }    ipv6IfIcmpInAdminProhibs OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP destination         unreachable/communication administratively         prohibited messages received by the interface."        ::= { ipv6IfIcmpEntry 4 }    ipv6IfIcmpInTimeExcds OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     currentHaskin & Onishi             Standards Track                     [Page 6]RFC 2466                 IPv6 MIB: ICMPv6 Group            December 1998        DESCRIPTION         "The number of ICMP Time Exceeded messages          received by the interface."        ::= { ipv6IfIcmpEntry 5 }    ipv6IfIcmpInParmProblems OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Parameter Problem messages          received by the interface."        ::= { ipv6IfIcmpEntry 6 }    ipv6IfIcmpInPktTooBigs OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Packet Too Big messages         received by the interface."        ::= { ipv6IfIcmpEntry 7 }    ipv6IfIcmpInEchos OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Echo (request) messages          received by the interface."        ::= { ipv6IfIcmpEntry 8 }    ipv6IfIcmpInEchoReplies OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Echo Reply messages received         by the interface."        ::= { ipv6IfIcmpEntry 9 }    ipv6IfIcmpInRouterSolicits OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Router Solicit messages          received by the interface."Haskin & Onishi             Standards Track                     [Page 7]RFC 2466                 IPv6 MIB: ICMPv6 Group            December 1998        ::= { ipv6IfIcmpEntry 10 }    ipv6IfIcmpInRouterAdvertisements OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Router Advertisement messages         received by the interface."        ::= { ipv6IfIcmpEntry 11 }    ipv6IfIcmpInNeighborSolicits OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Neighbor Solicit messages          received by the interface."        ::= { ipv6IfIcmpEntry 12 }    ipv6IfIcmpInNeighborAdvertisements OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMP Neighbor Advertisement         messages received by the interface."        ::= { ipv6IfIcmpEntry 13 }    ipv6IfIcmpInRedirects OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of Redirect messages received         by the interface."        ::= { ipv6IfIcmpEntry 14 }    ipv6IfIcmpInGroupMembQueries OBJECT-TYPE        SYNTAX     Counter32        MAX-ACCESS read-only        STATUS     current        DESCRIPTION         "The number of ICMPv6 Group Membership Query         messages received by the interface."        ::= { ipv6IfIcmpEntry 15}    ipv6IfIcmpInGroupMembResponses OBJECT-TYPEHaskin & Onishi             Standards Track                     [Page 8]

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -