RFC 2677
Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)
Pages: 67
Proposed Standard
Proposed Standard
Part 1 of 3 – Pages 1 to 6
Network Working Group M. Greene Request for Comments: 2677 Contractor Category: Standards Track J. Cucchiara IronBridge Networks J. Luciani Bay Networks August 1999 Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP) 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 describes managed objects for the Next Hop Resolution Protocol (NHRP) as defined in RFC 2332.Table of Contents
1 Introduction ................................................. 2 2 The SNMP Management Framework ................................ 2 3 Structure of the MIB ......................................... 3 3.1 The NHRP General Group ..................................... 3 3.1.1 The NHRP Cache Table ..................................... 4 3.1.2 The NHRP Purge Request Table ............................. 4 3.2 The NHRP Client Group ...................................... 4 3.2.1 The NHRP Client Table .................................... 4 3.2.2 The NHRP Client Registration Table ....................... 5 3.2.3 The NHRP Client NHS Table ................................ 5 3.2.4 The NHRP Client Statistics Table ......................... 5 3.3 The NHRP Server Group ...................................... 5 3.3.1 The NHRP Server Table .................................... 5 3.3.2 The NHRP Server Cache Table .............................. 5 3.3.3 The NHRP Server NHC Table ................................ 6
3.3.4 The NHRP Server Statistics Table ......................... 6 4 NBMA Next Hop Resolution Protocol MIB Definitions ............ 6 5 IANA Considerations .......................................... 62 6 Security ..................................................... 62 7 Intellectual Property ........................................ 63 8 Acknowledgments .............................................. 63 9 References ................................................... 64 10 Authors' Addresses .......................................... 66 11 Full Copyright Statement .................................... 671. Introduction
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 for the Next Hop Resolution Protocol (NHRP) as defined in RFC 2332 [17]. 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 [21].2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [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 2578 [5], STD 58, RFC 2579 [6] and STD 58, 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 2572 [11] and RFC 2574 [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 2573 [14] and
the view-based access control mechanism described in RFC 2575
[15].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [16].
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.
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
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3. Structure of the MIB
The NHRP MIB contains three groups: the General Group, the Client
Group, and the Server Group.
3.1. The NHRP General Group
The General Group contains objects that apply to both clients and
servers -- in particular the nhrpNextIndex scalar object, the NHRP
Cache Table and the NHRP Purge Request Table.
The nhrpNextIndex scalar object is used to provide unique indices for
the nhprClientIndex in the nhrpClientTable and the nhrpServerIndex in
the nhrpServerTable. If used consistently, this object may prevent
conflicts when multiple managers attempt to create rows
simultaneously in the same table.
3.1.1. The NHRP Cache Table
The NHRP Cache Table represents the internetwork layer address to NBMA address cache that is maintained by both NHRP clients and NHRP servers. The NHRP Cache Table contains an ifIndex as part of the Index Clause. This ifIndex represents the use of a generic ifIndex, such that the value of this ifIndex SHOULD reflect a specific NBMA subnetwork related interface as determined by an implementation. For example, assuming that the NBMA subnetwork is ATM, then it is up to the implementors of this MIB to determine their own ATM interface layering (assuming compliance with the IF-MIB, RFC 2233 [18] and the ATM-MIB, RFC 2515 [19]). In other words, assuming that the NBMA subnetwork is ATM, the ifIndex in the NHRP Cache Table would represent the ifIndex containing or consisting of the VC (or shortcut) denoted by this Table entry. The indexing scheme for the NHRP Cache Table is very similar to the MPC Ingress Cache Table and the MPS Ingress Cache Table in the Multiprotocol Over ATM (MPOA) MIB [23]. This MIB and the MPOA MIB were designed to be complementary and non-overlapping. The MPOA MIB should also support this MIB. The MPOA MIB was designed prior to this MIB, and was designed by the LANE/MPOA Working Group in the ATM FORUM. The indexing scheme of the NHRP Cache Table (and the NHRP Server Cache Table) reflect the indexing scheme of the MPC Ingress Cache Table and the MPS Ingress Cache Table. Although, other indexing schemes could have been used for the NHRP Cache Table, a consistent indexing scheme between these tables was thought to be more advantageous from an implementation standpoint.3.1.2. The NHRP Purge Request Table
The NHRP Purge Request Table is a way to track Purge Request Information.3.2. The NHRP Client Group
The Client Group contains objects that only apply to NHRP clients (NHCs).3.2.1. The NHRP Client Table
The NHRP Client Table contains entries for NHRP Next Hop Clients (NHCs) associated with this agent. Each row in the table represents a single NHC. The RequestID used in Registration requests needs to be saved to non-volatile storage. Depending upon the implementation,
this may or may not impact how the StorageType is used. For a complete description of how the Registration RequestID is used, see Section 5.2.3 of [17].3.2.2. The NHRP Client Registration Table
The NHRP Client Registration Table contains information on registration requests which need to be maintained by the Clients. Each entry in this table represents a single registration request. Note: since the NHRP specification does not mandate a refresh algorithm, this table omits refresh information, however, this table does contain information for all the registration requests which need to be maintained by the NHRP Clients.3.2.3. The NHRP Client NHS Table
The NHRP Client NHS Table contains the NBMA subnetwork addresses of servers configured for use by the client. By default, the agent will add an entry to this table which corresponds to the client's default router.3.2.4. The NHRP Client Statistics Table
The NHRP Client Statistics Table contains NHRP statistics maintained by a client. These statistics include counters on requests and replies, as well as counters for errors which are encountered by the Clients.3.3. The NHRP Server Group
The Server Group contains objects that only apply to NHRP servers (NHSes).3.3.1. The NHRP Server Table
The NHRP Server Table contains entries for each server associated with this agent.3.3.2. The NHRP Server Cache Table
The NHRP Server Cache Table contains additional objects that a server keeps for each entry in its cache. This table extends the NHRP Cache Table defined in the General Group.
3.3.3. The NHRP Server NHC Table
This table contains information about all the Clients known to the Servers.3.3.4. The NHRP Server Statistics Table
The NHRP Server Statistics Table contains NHRP statistics maintained by a server. These statistics include counters on requests and replies, as well as counters for errors which are encountered by the Servers.
(page 6 continued on part 2)