SNMPv2 Management Information Base for the Internet Protocol using SMIv2
RFC 2011

Document Type RFC - Proposed Standard (November 1996; No errata)
Obsoleted by RFC 4293
Updates RFC 1213
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2011 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                              K. McCloghrie, Editor
Request for Comments: 2011                                 Cisco Systems
Updates: 1213                                              November 1996
Category: Standards Track

                   SNMPv2 Management Information Base
                 for the Internet Protocol using SMIv2

Status 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.

IESG Note:

   The IP, UDP, and TCP MIB modules currently support only IPv4.  These
   three modules use the IpAddress type defined as an OCTET STRING of
   length 4 to represent the IPv4 32-bit internet addresses.  (See RFC
   1902, SMI for SNMPv2.)  They do not support the new 128-bit IPv6
   internet addresses.

Table of Contents

   1. Introduction ...............................................    1
   2. Definitions ................................................    2
   2.1 The IP Group ..............................................    3
   2.2 The ICMP Group.............................................   11
   2.3 Conformance Information ...................................   16
   2.3.1 Compliance Statements ...................................   16
   2.3.2 Units of Conformance ....................................   16
   3. Acknowledgements ...........................................   18
   4. References .................................................   18
   5. Security Considerations ....................................   18
   6. Editor's Address ...........................................   18

1.  Introduction

   A management system contains: several (potentially many) nodes, each
   with a processing entity, termed an agent, which has access to
   management instrumentation; at least one management station; and, a
   management protocol, used to convey management information between
   the agents and management stations.  Operations of the protocol are
   carried out under an administrative framework which defines
   authentication, authorization, access control, and privacy policies.

McCloghrie                  Standards Track                     [Page 1]
RFC 2011                   SNMPv2 MIB for IP               November 1996

   Management stations execute management applications which monitor and
   control managed elements.  Managed elements are devices such as
   hosts, routers, terminal servers, etc., which are monitored and
   controlled via access to their management information.

   Management information is viewed as a collection of managed objects,
   residing in a virtual information store, termed the Management
   Information Base (MIB).  Collections of related objects are defined
   in MIB modules.  These modules are written using a subset of OSI's
   Abstract Syntax Notation One (ASN.1) [1], termed the Structure of
   Management Information (SMI) [2].

   This document is the MIB module which defines managed objects for
   managing implementations of the Internet Protocol (IP) [3] and its
   associated Internet Control Message Protocol (ICMP) [4].

   The managed objects in this MIB module were originally defined using
   the SNMPv1 framework as a part of MIB-II [5].  Since then, the
   managed objects related to managing routes in an IP internet were
   updated by RFC 1354 [6].  This document takes the remaining MIB-II
   objects for these protocols, and defines them using the SNMPv2
   framework.

2.  Definitions

IP-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Integer32,
    Counter32, IpAddress, mib-2        FROM SNMPv2-SMI
    PhysAddress                        FROM SNMPv2-TC
    MODULE-COMPLIANCE, OBJECT-GROUP    FROM SNMPv2-CONF;

ipMIB MODULE-IDENTITY
    LAST-UPDATED "9411010000Z"
    ORGANIZATION "IETF SNMPv2 Working Group"
    CONTACT-INFO
            "        Keith McCloghrie

             Postal: Cisco Systems, Inc.
                     170 West Tasman Drive
                     San Jose, CA  95134-1706
                     US

             Phone:  +1 408 526 5260
             Email:  kzm@cisco.com"

McCloghrie                  Standards Track                     [Page 2]
RFC 2011                   SNMPv2 MIB for IP               November 1996

    DESCRIPTION
            "The MIB module for managing IP and ICMP implementations,
            but excluding their management of IP routes."
    REVISION      "9103310000Z"
    DESCRIPTION
            "The initial revision of this MIB module was part of MIB-
            II."
    ::= { mib-2 48}

-- the IP group

ip       OBJECT IDENTIFIER ::= { mib-2 4 }

ipForwarding OBJECT-TYPE
    SYNTAX      INTEGER {
                    forwarding(1),    -- acting as a router
Show full document text