Definitions of Managed Objects for APPN/HPR in IP Networks
RFC 2584

Document Type RFC - Proposed Standard (May 1999; 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 2584 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                B. Clouston, Ed.
Request for Comments: 2584                              Cisco Systems
Category: Standards Track                               B. Moore, Ed.
                                                      IBM Corporation
                                                             May 1999

                     Definitions of Managed Objects
                      for APPN/HPR in IP Networks

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.

Copyright Notice

   Copyright (C) The Internet Society (1999).  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 defines objects for monitoring and controlling HPR
   (High Performance Routing) network devices which have the capability
   to communicate in IP (Internet Protocol) networks. This memo
   identifies managed objects for the HPR in IP network communications.

Table of Contents

   1.     Introduction  ...........................................  2
   2.     The SNMP Network Management Framework  ..................  2
   3.     Overview  ...............................................  3
   3.1      HPR/IP Values for Objects in the APPN MIB .............  3
   3.2      APPN/HPR in IP Networks MIB structure .................  4
   3.2.1      hprIpMonitoringGroup ................................  5
   3.2.2      hprIpConfigurationGroup .............................  5
   4.     Definitions  ............................................  6
   5.     Security Considerations  ................................ 16
   6.     Intellectual Property  .................................. 17
   7.     Acknowledgments  ........................................ 18
   8.     References  ............................................. 18
   9.     Authors' Addresses  ..................................... 20
   10.    Full Copyright Statement  ............................... 21

Clouston & Moore            Standards Track                     [Page 1]
RFC 2584              APPN/HPR in IP Networks MIB               May 1999

1.  Introduction

   This document is a product of the SNA NAU Services MIB Working Group.
   It defines a MIB module for managing devices with HPR in IP networks
   capabilities.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [17].

2.  The SNMP Network Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o    An overall architecture, described in RFC 2271 [1].

   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 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
        second version, called SMIv2, is described in STD 58, RFC 2478
        [5], RFC 2579 [6] and RFC 2580 [7].

   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 [8]. A second version of the SNMP
        message protocol, which is not an Internet standards track
        protocol, is called SNMPv2c and described in RFC 1901 [9] and
        RFC 1906 [10]. The third version of the message protocol is
        called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and
        RFC 2274 [12].

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

   o    A set of fundamental applications described in RFC 2273 [14] and
        the view-based access control mechanism described in RFC 2275
        [15].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

Clouston & Moore            Standards Track                     [Page 2]
RFC 2584              APPN/HPR in IP Networks MIB               May 1999

   This memo specifies a MIB module that is compliant to the SMIv2. A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations. The resulting translated MIB must be semantically
Show full document text