Physical Topology MIB
RFC 2922

Document Type RFC - Informational (September 2000; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2922 (Informational)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         A. Bierman
Request for Comments: 2922                           Cisco Systems, Inc.
Category: Informational                                         K. Jones
                                                         Nortel Networks
                                                          September 2000

                         Physical Topology MIB

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects used for managing
   physical topology identification and discovery.

Table of Contents

   1 The SNMP Network Management Framework ............................2
   2 Overview .........................................................3
   2.1 Terms ..........................................................3
   2.2 Design Goals ...................................................5
   3 Topology Framework ...............................................6
   3.1 Devices and Topology Agents ....................................6
   3.2 Topology Mechanisms ............................................7
   3.3 Future Considerations ..........................................7
   4 Physical Topology MIB ............................................7
   4.1 Persistent Identifiers .........................................8
   4.2 Relationship to Entity MIB .....................................8
   4.3 Relationship to Interfaces MIB .................................9
   4.4 Relationship to RMON-2 MIB .....................................9
   4.5 Relationship to Bridge MIB .....................................9
   4.6 Relationship to Repeater MIB ...................................9
   4.7 MIB Structure .................................................10
   4.7.1 ptopoData Group .............................................10
   4.7.2 ptopoGeneral Group ..........................................10
   4.7.3 ptopoConfig Group ...........................................10
   4.8 Physical Topology MIB Definitions .............................10

Bierman & Jones              Informational                      [Page 1]
RFC 2922                 Physical Topology MIB            September 2000

   5 Intellectual Property ...........................................27
   6 Acknowledgements ................................................28
   7 References ......................................................28
   8 Security Considerations .........................................30
   9 Authors' Addresses ..............................................31
   10 Full Copyright Statement .......................................32

1.  The SNMP Network Management Framework

   The SNMP Management Framework presently consists of five major
   components:

        o   An overall architecture, described in RFC 2571 [RFC2571].

        o   Mechanisms for describing and naming objects and events for
            the purpose of management.  The first version of this
            Structure of Management Information (SMI) is called SMIv1
            and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC
            1212 [RFC1212] and RFC 1215 [RFC1215].  The second version,
            called SMIv2, is described in STD 58, RFC 2578 [RFC2578],
            STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].

        o   Message protocols for transferring management information.
            The first version of the SNMP message protocol is called
            SNMPv1 and described in STD 15, RFC 1157 [RFC1157].  A
            second version of the SNMP message protocol, which is not an
            Internet standards track protocol, is called SNMPv2c and
            described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906].  The
            third version of the message protocol is called SNMPv3 and
            described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC
            2574 [RFC2574].

        o   Protocol operations for accessing management information.
            The first set of protocol operations and associated PDU
            formats is described in STD 15, RFC 1157 [RFC1157].  A
            second set of protocol operations and associated PDU formats
            is described in RFC 1905 [RFC1905].

        o   A set of fundamental applications described in RFC 2573
            [RFC2573] and the view-based access control mechanism
            described in RFC 2575 [RFC2575].

   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [RFC2570].

   Managed objects are accessed via a virtual information store, termed
Show full document text