As per Relevance of the word indicate, we have this rfc below:
Network Working Group M.
Request for Comments: 2677
Category: Standards Track J.
IronBridge
J.
Bay
August 1999
Definitions of Managed Objects
the NBMA Next Hop Resolution Protocol (NHRP
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
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
Resolution Protocol (NHRP) as defined in RFC 2332.
Table of
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
Greene, et al. Standards Track [Page 1]
RFC 2677 NHRP MIB August 1999
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 .................................... 67
1.
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
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
document are to be interpreted as described in RFC 2119 [21].
2. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
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.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9] and
1906 [10]. The third version of the message protocol is
SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
Greene, et al. Standards Track [Page 2]
RFC 2677 NHRP MIB August 1999
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [16].
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
3. Structure of the
The NHRP MIB contains three groups: the General Group, the
Group, and the Server Group
3.1. The NHRP General
The General Group contains objects that apply to both clients
servers -- in particular the nhrpNextIndex scalar object, the
Cache Table and the NHRP Purge Request Table
The nhrpNextIndex scalar object is used to provide unique indices
the nhprClientIndex in the nhrpClientTable and the nhrpServerIndex
the nhrpServerTable. If used consistently, this object may
conflicts when multiple managers attempt to create
simultaneously in the same table
Greene, et al. Standards Track [Page 3]
RFC 2677 NHRP MIB August 1999
3.1.1. The NHRP Cache
The NHRP Cache Table represents the internetwork layer address
NBMA address cache that is maintained by both NHRP clients and
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
value of this ifIndex SHOULD reflect a specific NBMA
related interface as determined by an implementation. For example
assuming that the NBMA subnetwork is ATM, then it is up to
implementors of this MIB to determine their own ATM
layering (assuming compliance with the IF-MIB, RFC 2233 [18] and
ATM-MIB, RFC 2515 [19]). In other words, assuming that the
subnetwork is ATM, the ifIndex in the NHRP Cache Table
represent the ifIndex containing or consisting of the VC (
shortcut) denoted by this Table entry
The indexing scheme for the NHRP Cache Table is very similar to
MPC Ingress Cache Table and the MPS Ingress Cache Table in
Multiprotocol Over ATM (MPOA) MIB [23]. This MIB and the MPOA
were designed to be complementary and non-overlapping. The MPOA
should also support this MIB. The MPOA MIB was designed prior
this MIB, and was designed by the LANE/MPOA Working Group in the
FORUM. The indexing scheme of the NHRP Cache Table (and the
Server Cache Table) reflect the indexing scheme of the MPC
Cache Table and the MPS Ingress Cache Table. Although,
indexing schemes could have been used for the NHRP Cache Table,
consistent indexing scheme between these tables was thought to
more advantageous from an implementation standpoint
3.1.2. The NHRP Purge Request
The NHRP Purge Request Table is a way to track Purge
Information
3.2. The NHRP Client
The Client Group contains objects that only apply to NHRP
(NHCs).
3.2.1. The NHRP Client
The NHRP Client Table contains entries for NHRP Next Hop
(NHCs) associated with this agent. Each row in the table
a single NHC. The RequestID used in Registration requests needs
be saved to non-volatile storage. Depending upon the implementation
Greene, et al. Standards Track [Page 4]
RFC 2677 NHRP MIB August 1999
this may or may not impact how the StorageType is used. For
complete description of how the Registration RequestID is used,
Section 5.2.3 of [17].
3.2.2. The NHRP Client Registration
The NHRP Client Registration Table contains information
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
algorithm, this table omits refresh information, however, this
does contain information for all the registration requests which
to be maintained by the NHRP Clients
3.2.3. The NHRP Client NHS
The NHRP Client NHS Table contains the NBMA subnetwork addresses
servers configured for use by the client. By default, the agent
add an entry to this table which corresponds to the client's
router
3.2.4. The NHRP Client Statistics
The NHRP Client Statistics Table contains NHRP statistics
by a client. These statistics include counters on requests
replies, as well as counters for errors which are encountered by
Clients
3.3. The NHRP Server
The Server Group contains objects that only apply to NHRP
(NHSes).
3.3.1. The NHRP Server
The NHRP Server Table contains entries for each server
with this agent
3.3.2. The NHRP Server Cache
The NHRP Server Cache Table contains additional objects that a
keeps for each entry in its cache. This table extends the NHRP
Table defined in the General Group
Greene, et al. Standards Track [Page 5]
RFC 2677 NHRP MIB August 1999
3.3.3. The NHRP Server NHC
This table contains information about all the Clients known to
Servers
3.3.4. The NHRP Server Statistics
The NHRP Server Statistics Table contains NHRP statistics
by a server. These statistics include counters on requests
replies, as well as counters for errors which are encountered by
Servers
4. NBMA Next Hop Resolution Protocol MIB
NHRP-MIB DEFINITIONS ::=
OBJECT-TYPE, MODULE-IDENTITY, mib-2, Integer32,
Counter32, Unsigned32
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType
FROM SNMPv2-
FROM IF-
FROM IANA-ADDRESS-FAMILY-NUMBERS-
;
nhrpMIB MODULE-
LAST-UPDATED "9908260000Z" -- August 26, 1999
ORGANIZATION "Internetworking Over NBMA (ion) Working Group
CONTACT-
"Maria Greene (maria@xedia.com
Joan Cucchiara (joan@ironbridgenetworks.com
IronBridge
James V. Luciani (luciani@baynetworks.com
Bay Networks
Greene, et al. Standards Track [Page 6]
RFC 2677 NHRP MIB August 1999
"This MIB contains managed object definitions for the
Hop Resolution Procol, NHRP, as defined in RFC 2332 [17]."
-- revision
REVISION "9908260000Z" -- August 26, 1999
DESCRIPTION "Initial version, published as RFC 2677."
::= { mib-2 71 }
--****************************************************************
-- NHRP Textual
--****************************************************************
NhrpGenAddr ::= TEXTUAL-
STATUS
"The value of an internetwork layer or NBMA address."
SYNTAX OCTET STRING (SIZE (0..64))
nhrpObjects OBJECT IDENTIFIER ::= { nhrpMIB 1 }
--****************************************************************
-- NHRP General (Client and Server)
--****************************************************************
nhrpGeneralObjects OBJECT IDENTIFIER ::= { nhrpObjects 1 }
--
-- The following scalar is to be used
-- provided indices for
-- nhrpClientTable, and/or the nhrpServerTable
--
nhrpNextIndex OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS
"This scalar is used for creating rows in
nhrpClientTable and the nhrpServerTable
The value of this variable is a currently unused
for nhrpClientIndex and nhrpServerIndex
Greene, et al. Standards Track [Page 7]
RFC 2677 NHRP MIB August 1999
The value returned when reading this variable must
unique for the NHC's and NHS's indices associated
this row. Subsequent attempts to read this
must return different values
NOTE: this object exists in the General Group
it is to be used in establishing rows in
nhrpClientTable and the nhrpServerTable. In other words
the value retrieved from this object could become
value of nhrpClientIndex and nhprServerIndex
In the situation of an agent re-initialization the
of this object must be saved in non-volatile storage
This variable will return the special value 0 if no
rows can be created."
::= { nhrpGeneralObjects 1 }
--
-- The NHRP Cache
--
nhrpCacheTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains mappings between internetwork
addresses and NBMA subnetwork layer addresses."
::= { nhrpGeneralObjects 2 }
nhrpCacheEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A cached mapping between an internetwork layer
and an NBMA address. Entries can be created by
network administrator using the
column, or they may be added dynamically based
protocol operation (including NHRP, SCSP, and others
such as ATMARP).
When created based by NHRP protocol
this entry is largely based on contents contained
the Client Information Entry (CIE).
Greene, et al. Standards Track [Page 8]
RFC 2677 NHRP MIB August 1999
Zero or more Client Information Entries (CIEs) may
included in the NHRP Packet. For a complete
of the CIE, refer to Section 5.2.0.1
RFC 2332 [17]."
INDEX {
nhrpCacheInternetworkAddrType
nhrpCacheInternetworkAddr
ifIndex
}
::= { nhrpCacheTable 1 }
NhrpCacheEntry ::= SEQUENCE {
nhrpCacheInternetworkAddrType AddressFamilyNumbers
nhrpCacheInternetworkAddr NhrpGenAddr
nhrpCacheIndex Unsigned32,
nhrpCachePrefixLength Integer32,
nhrpCacheNextHopInternetworkAddr NhrpGenAddr
nhrpCacheNbmaAddrType AddressFamilyNumbers
nhrpCacheNbmaAddr NhrpGenAddr
nhrpCacheNbmaSubaddr NhrpGenAddr
nhrpCacheType INTEGER
nhrpCacheState INTEGER
nhrpCacheHoldingTimeValid TruthValue
nhrpCacheHoldingTime Unsigned32,
nhrpCacheNegotiatedMtu Integer32,
nhrpCachePreference Integer32,
nhrpCacheStorageType StorageType
nhrpCacheRowStatus
}
nhrpCacheInternetworkAddrType OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The internetwork layer address type of this Next
Resolution Cache entry. The value of this object
how to interpret the values of
and nhrpCacheNextHopInternetworkAddr."
::= { nhrpCacheEntry 1 }
nhrpCacheInternetworkAddr OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
Greene, et al. Standards Track [Page 9]
RFC 2677 NHRP MIB August 1999
"The value of the internetwork address of
destination."
::= { nhrpCacheEntry 2 }
nhrpCacheIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"An identifier for this entry that has
significance within the scope of the
Group. This identifier is used here
uniquely identify this row, and also
in the 'nhrpPurgeTable' for the value
the 'nhrpPurgeCacheIdentifier'."
::= { nhrpCacheEntry 3 }
nhrpCachePrefixLength OBJECT-
SYNTAX Integer32 (0..255)
MAX-ACCESS read-
STATUS
"The number of bits that define the internetwork
prefix associated with the nhrpCacheInternetworkAddr."
::= { nhrpCacheEntry 4 }
nhrpCacheNextHopInternetworkAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the internetwork address of the next hop."
::= { nhrpCacheEntry 5 }
nhrpCacheNbmaAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The NBMA address type. The value of
object indicates how to
the values of nhrpCacheNbmaAddr
nhrpCacheNbmaSubaddr."
::= { nhrpCacheEntry 6 }
Greene, et al. Standards Track [Page 10]
RFC 2677 NHRP MIB August 1999
nhrpCacheNbmaAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the NBMA subnetwork address of the
hop."
::= { nhrpCacheEntry 7 }
nhrpCacheNbmaSubaddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the NBMA subaddress of the next hop.
there is no subaddress concept for the NBMA
family, this value will be a zero-length OCTET STRING."
::= { nhrpCacheEntry 8 }
nhrpCacheType OBJECT-
SYNTAX INTEGER {
other(1),
register(2),
resolveAuthoritative(3),
resoveNonauthoritative(4),
transit(5),
administrativelyAdded(6),
atmarp(7),
scsp(8)
}
MAX-ACCESS read-
STATUS
"An indication of how this cache
was created. The values are
'other(1)' The entry was added by
other means
'register(2)' In a server, added based on
client registration
'resolveAuthoritative(3)' In a client, added based
receiving an
NHRP Resolution Reply
Greene, et al. Standards Track [Page 11]
RFC 2677 NHRP MIB August 1999
'resolveNonauthoritative(4)' In a client, added based
receiving a
NHRP Resolution Reply
'transit(5)' In a transit server, added
examining a forwarded
packet
'administrativelyAdded(6)' In a client or server
manually added by
administrator.
StorageType of this entry
reflected
'nhrpCacheStorageType'.
'atmarp(7)' The entry was added due to
ATMARP
'scsp(8)' The entry was added due
SCSP
When the entry is under creation using
nhrpCacheRowStatus column, the only value that can
specified by the administrator is 'administrativelyAdded'.
Attempting to set any other value will cause
'inconsistentValue' error
The value cannot be modified once the entry is active."
::= { nhrpCacheEntry 9 }
nhrpCacheState OBJECT-
SYNTAX INTEGER {
incomplete(1),
ackReply(2),
nakReply(3)
}
MAX-ACCESS read-
STATUS
"An indication of the state of this entry. The values are
'incomplete(1)' The client has sent a NHRP
Request but has not yet received
NHRP Resolution Reply
Greene, et al. Standards Track [Page 12]
RFC 2677 NHRP MIB August 1999
'ackReply(2)' For a client or server, this is
cached valid mapping
'nakReply(3)' For a client or server, this is
cached NAK mapping."
::= { nhrpCacheEntry 10 }
nhrpCacheHoldingTimeValid OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"True(1) is returned if the value
'nhrpCacheType' is
'administrativelyAdded'. Since
value of 'nhrpCacheType' was
configured by a user, the value
'nhrpCacheHoldingTime'
considered valid. In other words, the value
'nhrpCacheHoldingTime'
the Holding Time for the cache Entry
If 'nhrpCacheType has been configured by
user, (i.e. the value of 'nhrpCacheType'
'administrativelyAdded') then false(2) will be returned
This indicates that the value
'nhrpCacheHoldingTime' is undefined because this
could possibly be backed up in nonvolatile storage."
::= { nhrpCacheEntry 11 }
nhrpCacheHoldingTime OBJECT-
SYNTAX Unsigned32(0..65535)
UNITS "seconds
MAX-ACCESS read-
STATUS
"If the value of 'nhrpCacheHoldingTimeValid
true(1) then this object represents the
of seconds that the cache entry will remain in
table. When this value reaches 0 (zero) the row
be deleted
If the value of 'nhrpCacheHoldingTimeValid
false(2) then this object is undefined."
::= { nhrpCacheEntry 12 }
Greene, et al. Standards Track [Page 13]
RFC 2677 NHRP MIB August 1999
nhrpCacheNegotiatedMtu OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The maximum transmission unit (MTU) that was
or registered for this entity. In other words, this is
actual MTU being used."
::= { nhrpCacheEntry 13 }
nhrpCachePreference OBJECT-
SYNTAX Integer32 (0..255)
MAX-ACCESS read-
STATUS
"An object which reflects the Preference value of
Client Information Entry (CIE).
Zero or more Client Information Entries (CIEs) may
included in the NHRP Packet. One of the fields in
CIE is the Preference. For a complete description
the CIE, refer to Section 5.2.0.1 of RFC 2332 [17]."
"Section 5.2.0.1 Mandatory Part Format, RFC 2332 [17]."
::= { nhrpCacheEntry 14 }
nhrpCacheStorageType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This value only has meaning when the 'nhrpCacheType
has the value of 'administrativelyAdded'.
When the row is created due to
'administrativelyAdded', this object reflects
this row is kept in volatile
and lost upon reboot or if this row is backed up
non-volatile or permanent storage
If the value of 'nhrpCacheType' has a value
is not 'administrativelyAdded, then the value of
object is 'other(1)'."
DEFVAL { nonVolatile }
::= { nhrpCacheEntry 15 }
Greene, et al. Standards Track [Page 14]
RFC 2677 NHRP MIB August 1999
nhrpCacheRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An object that allows entries in this table to
created and deleted using the RowStatus convention."
::= { nhrpCacheEntry 16 }
--
-- The NHRP Purge Request
--
nhrpPurgeReqTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table will track Purge Request Information."
::= { nhrpGeneralObjects 3 }
nhrpPurgeReqEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information regarding a Purge Request."
INDEX { nhrpPurgeIndex }
::= { nhrpPurgeReqTable 1 }
NhrpPurgeReqEntry ::= SEQUENCE {
nhrpPurgeIndex Unsigned32,
nhrpPurgeCacheIdentifier Unsigned32,
nhrpPurgePrefixLength Integer32,
nhrpPurgeRequestID Unsigned32,
nhrpPurgeReplyExpected TruthValue
nhrpPurgeRowStatus
}
nhrpPurgeIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"An index for this entry that has local
within the scope of this table."
::= { nhrpPurgeReqEntry 1 }
Greene, et al. Standards Track [Page 15]
RFC 2677 NHRP MIB August 1999
nhrpPurgeCacheIdentifier OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-
STATUS
"This object identifies which row
'nhrpCacheTable' is being purged. This
should have the same value as the 'nhrpCacheIndex
in the 'nhrpCacheTable'."
::= { nhrpPurgeReqEntry 2 }
nhrpPurgePrefixLength OBJECT-
SYNTAX Integer32 (0..255)
MAX-ACCESS read-
STATUS
"In the case of NHRP Purge Requests, this specifies
equivalence class of addresses which match the
'Prefix Length' bit positions of the Client
Address specified in the Client Information Entry (CIE)."
::= { nhrpPurgeReqEntry 3 }
nhrpPurgeRequestID OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS
"The Request ID used in the purge request."
::= { nhrpPurgeReqEntry 4 }
nhrpPurgeReplyExpected OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An indication of whether this Purge Request has
'N' Bit cleared (off)."
::= { nhrpPurgeReqEntry 5 }
nhrpPurgeRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An object that allows entries in this table to
created and deleted using the RowStatus convention."
::= { nhrpPurgeReqEntry 6 }
Greene, et al. Standards Track [Page 16]
RFC 2677 NHRP MIB August 1999
--****************************************************************
-- NHRP Client
--****************************************************************
nhrpClientObjects OBJECT IDENTIFIER ::= { nhrpObjects 2 }
--
-- The NHRP Client
--
nhrpClientTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Information about NHRP clients (NHCs) managed by
agent."
::= { nhrpClientObjects 1 }
nhrpClientEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a single NHC."
INDEX { nhrpClientIndex }
::= { nhrpClientTable 1 }
NhrpClientEntry ::= SEQUENCE {
nhrpClientIndex Unsigned32,
nhrpClientInternetworkAddrType AddressFamilyNumbers
nhrpClientInternetworkAddr NhrpGenAddr
nhrpClientNbmaAddrType AddressFamilyNumbers
nhrpClientNbmaAddr NhrpGenAddr
nhrpClientNbmaSubaddr NhrpGenAddr
nhrpClientInitialRequestTimeout Integer32,
nhrpClientRegistrationRequestRetries Integer32,
nhrpClientResolutionRequestRetries Integer32,
nhrpClientPurgeRequestRetries Integer32,
nhrpClientDefaultMtu Unsigned32,
nhrpClientHoldTime Unsigned32,
nhrpClientRequestID Unsigned32,
nhrpClientStorageType StorageType
nhrpClientRowStatus
}
Greene, et al. Standards Track [Page 17]
RFC 2677 NHRP MIB August 1999
nhrpClientIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"An identifier for the NHRP client that is unique
the scope of this agent. The 'nhrpNextIndex'
should be consulted (read), prior to creating a row
this table, and the value returned from
'nhrpNextIndex' should be used as this object's value."
::= { nhrpClientEntry 1 }
nhrpClientInternetworkAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the internetwork layer address of
client. This object indicates how the value
nhrpClientInternetworkAddr is to be interpreted."
::= { nhrpClientEntry 2 }
nhrpClientInternetworkAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the internetwork layer address of
client."
::= { nhrpClientEntry 3 }
nhrpClientNbmaAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the NBMA subnetwork address of this client
This object indicates how the values
nhrpClientNbmaAddr and nhrpClientNbmaSubaddr are to
interpreted."
::= { nhrpClientEntry 4 }
nhrpClientNbmaAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Greene, et al. Standards Track [Page 18]
RFC 2677 NHRP MIB August 1999
"The NBMA subnetwork address of this client."
::= { nhrpClientEntry 5 }
nhrpClientNbmaSubaddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The NBMA subaddress of this client. For NBMA
families without a subaddress concept, this will be
zero-length OCTET STRING."
::= { nhrpClientEntry 6 }
nhrpClientInitialRequestTimeout OBJECT-
SYNTAX Integer32 (1..900)
UNITS "seconds
MAX-ACCESS read-
STATUS
"The number of seconds that the client will wait
timing out an NHRP initial request. This object only
meaning for the initial timeout period."
DEFVAL { 10 }
::= { nhrpClientEntry 7 }
nhrpClientRegistrationRequestRetries OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The number of times the client will retry
registration request before failure. A value
0 means don't retry. A value of 65535
retry forever."
DEFVAL { 3 }
::= { nhrpClientEntry 8 }
nhrpClientResolutionRequestRetries OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The number of times the client will retry the
request before failure. A value of 0 means don't retry
A value of 65535 means retry forever."
DEFVAL { 3 }
::= { nhrpClientEntry 9 }
Greene, et al. Standards Track [Page 19]
RFC 2677 NHRP MIB August 1999
nhrpClientPurgeRequestRetries OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The number of times the client will retry a purge
before failure. A value of 0 means don't retry. A value
65535 means retry forever."
DEFVAL { 3 }
::= { nhrpClientEntry 10 }
nhrpClientDefaultMtu OBJECT-
SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-
STATUS
"The default maximum transmission unit (MTU) of
LIS/LAG which this client should use. This
will be initialized by the agent to the default
of the LIS/LAG (which is 9180) unless a different
value is specified during creation of this Client."
"RFC 2225 [25], Classical IP and ARP over ATM, Section 7,
DEFAULT VALUE FOR IP MTU OVER ATM AAL5."
DEFVAL { 9180 }
::= { nhrpClientEntry 11 }
nhrpClientHoldTime OBJECT-
SYNTAX Unsigned32(0..65535)
UNITS "seconds
MAX-ACCESS read-
STATUS
"The hold time the client will register."
DEFVAL { 900 }
::= { nhrpClientEntry 12 }
nhrpClientRequestID OBJECT-
SYNTAX Unsigned32
MAX-ACCESS read-
STATUS
"The Request ID used to register this client with
server. According to Section 5.2.3 of the
Specification, RFC 2332 [17], the Request ID
be kept in non-volatile storage, so that if an
crashes and re-initializes, it will use a
Greene, et al. Standards Track [Page 20]
RFC 2677 NHRP MIB August 1999
Request ID during the registration
when reregistering with the same NHS."
"Section 5.2.3 NHRP Registration Request, RFC 2332 [17]."
::= { nhrpClientEntry 13 }
nhrpClientStorageType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object defines whether this row is kept
volatile storage and lost upon a Client crash
reboot situation, or if this row is backed up
nonvolatile or permanent storage."
DEFVAL { nonVolatile }
::= { nhrpClientEntry 14 }
nhrpClientRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An object that allows entries in this table to
created and deleted using the RowStatus convention."
::= { nhrpClientEntry 15 }
--
-- The NHRP Client Registration
--
nhrpClientRegistrationTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table of Registration Request Information
needs to be maintained by the NHCs (clients)."
"Section 5.2.3 NHRP Registration Request, RFC 2332 [17]."
::= { nhrpClientObjects 2 }
nhrpClientRegistrationEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
Greene, et al. Standards Track [Page 21]
RFC 2677 NHRP MIB August 1999
"An NHC needs to maintain registration request
between the NHC and the NHS. An entry in this
represents information for a single registration request."
INDEX { nhrpClientIndex
}
::= { nhrpClientRegistrationTable 1 }
NhrpClientRegistrationEntry ::= SEQUENCE {
nhrpClientRegIndex Unsigned32,
nhrpClientRegUniqueness INTEGER
nhrpClientRegState INTEGER
nhrpClientRegRowStatus
}
nhrpClientRegIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"An identifier for this entry such that
identifies a specific Registration Request
the NHC represented by the nhrpClientIndex."
::= { nhrpClientRegistrationEntry 1 }
nhrpClientRegUniqueness OBJECT-
SYNTAX INTEGER {
requestUnique(1),
requestNotUnique(2)
}
MAX-ACCESS read-
STATUS
"The Uniqueness indicator for this Registration Request
If this object has the value of requestUnique(1),
the Uniqueness bit is set in the the NHRP
Request represented by this row. The value
be changed once the row is created."
::= { nhrpClientRegistrationEntry 2 }
nhrpClientRegState OBJECT-
SYNTAX INTEGER {
other(1),
registering(2),
ackRegisterReply(3),
nakRegisterReply(4)
Greene, et al. Standards Track [Page 22]
RFC 2677 NHRP MIB August 1999
}
MAX-ACCESS read-
STATUS
"The registration state of this client. The values are
'other(1)' The state of the
request is not one
'registering',
'ackRegisterReply'
'nakRegisterReply'.
'registering(2)' A registration request
been issued and a
reply is expected
'ackRegisterReply(3)' A positive registration
has been received
'nakRegisterReply(4)' The client has received
negative
reply (NAK)."
::= { nhrpClientRegistrationEntry 3 }
nhrpClientRegRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An object that allows entries in this table to
created and deleted using the RowStatus convention."
::= { nhrpClientRegistrationEntry 4 }
--
-- The NHRP Client->Server
--
nhrpClientNhsTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table of NHSes that are available for use by this
(client). By default, the agent will add an entry to
table that corresponds to the client's default router."
::= { nhrpClientObjects 3 }
Greene, et al. Standards Track [Page 23]
RFC 2677 NHRP MIB August 1999
nhrpClientNhsEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An NHS that may be used by an NHC."
INDEX { nhrpClientIndex, nhrpClientNhsIndex }
::= { nhrpClientNhsTable 1 }
NhrpClientNhsEntry ::= SEQUENCE {
nhrpClientNhsIndex Unsigned32,
nhrpClientNhsInternetworkAddrType AddressFamilyNumbers
nhrpClientNhsInternetworkAddr NhrpGenAddr
nhrpClientNhsNbmaAddrType AddressFamilyNumbers
nhrpClientNhsNbmaAddr NhrpGenAddr
nhrpClientNhsNbmaSubaddr NhrpGenAddr
nhrpClientNhsInUse TruthValue
nhrpClientNhsRowStatus
}
nhrpClientNhsIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"An identifier for an NHS available to an NHC."
::= { nhrpClientNhsEntry 1 }
nhrpClientNhsInternetworkAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the internetwork layer address of
NHRP server represented in this entry. This
indicates how the value
nhrpClientNhsInternetworkAddr is to be interpreted."
::= { nhrpClientNhsEntry 2 }
nhrpClientNhsInternetworkAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the destination internetwork
address of the NHRP server represented by
Greene, et al. Standards Track [Page 24]
RFC 2677 NHRP MIB August 1999
entry. If this value is not known, this will
a zero-length OCTET STRING."
::= { nhrpClientNhsEntry 3 }
nhrpClientNhsNbmaAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the NBMA subnetwork address of the
Server represented by this entry. This object
how the values of nhrpClientNhsNbmaAddr
nhrpClientNhsNbmaSubaddr are to be interpreted."
::= { nhrpClientNhsEntry 4 }
nhrpClientNhsNbmaAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The NBMA subnetwork address of the NHS. The type
the address is indicated by the corresponding value
nhrpClientNhsNbmaAddrType."
::= { nhrpClientNhsEntry 5 }
nhrpClientNhsNbmaSubaddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The NBMA subaddress of the NHS. For NMBA
families that do not have the concept of subaddress
this will be a zero-length OCTET STRING."
::= { nhrpClientNhsEntry 6 }
nhrpClientNhsInUse OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An indication of whether this NHS is in use by the NHC."
::= { nhrpClientNhsEntry 7 }
nhrpClientNhsRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Greene, et al. Standards Track [Page 25]
RFC 2677 NHRP MIB August 1999
"An object that allows entries in this table to
created and deleted using the RowStatus convention."
::= { nhrpClientNhsEntry 8 }
--
-- The NHRP Client
--
nhrpClientStatTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains statistics collected by
clients."
::= { nhrpClientObjects 4 }
nhrpClientStatEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Statistics collected by a NHRP client."
INDEX { nhrpClientIndex }
::= { nhrpClientStatTable 1 }
NhrpClientStatEntry ::= SEQUENCE {
nhrpClientStatTxResolveReq Counter32,
nhrpClientStatRxResolveReplyAck Counter32,
nhrpClientStatRxResolveReplyNakProhibited Counter32,
nhrpClientStatRxResolveReplyNakInsufResources Counter32,
nhrpClientStatRxResolveReplyNakNoBinding Counter32,
nhrpClientStatRxResolveReplyNakNotUnique Counter32,
nhrpClientStatTxRegisterReq Counter32,
nhrpClientStatRxRegisterAck Counter32,
nhrpClientStatRxRegisterNakProhibited Counter32,
nhrpClientStatRxRegisterNakInsufResources Counter32,
nhrpClientStatRxRegisterNakAlreadyReg Counter32,
nhrpClientStatRxPurgeReq Counter32,
nhrpClientStatTxPurgeReq Counter32,
nhrpClientStatRxPurgeReply Counter32,
nhrpClientStatTxPurgeReply Counter32,
nhrpClientStatTxErrorIndication Counter32,
nhrpClientStatRxErrUnrecognizedExtension Counter32,
nhrpClientStatRxErrLoopDetected Counter32,
Greene, et al. Standards Track [Page 26]
RFC 2677 NHRP MIB August 1999
nhrpClientStatRxErrProtoAddrUnreachable Counter32,
nhrpClientStatRxErrProtoError Counter32,
nhrpClientStatRxErrSduSizeExceeded Counter32,
nhrpClientStatRxErrInvalidExtension Counter32,
nhrpClientStatRxErrAuthenticationFailure Counter32,
nhrpClientStatRxErrHopCountExceeded Counter32,
nhrpClientStatDiscontinuityTime
}
nhrpClientStatTxResolveReq OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Resolution Requests
by this client
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 1 }
nhrpClientStatRxResolveReplyAck OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of positively acknowledged NHRP
Replies received by this client
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 2 }
nhrpClientStatRxResolveReplyNakProhibited OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Resolution Replies
by this client that contained the code
'Administratively Prohibited'.
Greene, et al. Standards Track [Page 27]
RFC 2677 NHRP MIB August 1999
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 3 }
nhrpClientStatRxResolveReplyNakInsufResources OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Resolution Replies
by this client that contained the code
'Insufficient Resources'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 4 }
nhrpClientStatRxResolveReplyNakNoBinding OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Resolution Replies
by this client that contained the code
'No Internetworking Layer Address to NBMA
Binding Exists'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 5 }
nhrpClientStatRxResolveReplyNakNotUnique OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
Greene, et al. Standards Track [Page 28]
RFC 2677 NHRP MIB August 1999
"The number of NAKed NHRP Resolution Replies
by this client that contained the code
'Binding Exists But Is Not Unique'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 6 }
nhrpClientStatTxRegisterReq OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Registration Requests
by this client
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 7 }
nhrpClientStatRxRegisterAck OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of positively acknowledged NHRP
Replies received by this client
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 8 }
nhrpClientStatRxRegisterNakProhibited OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
Greene, et al. Standards Track [Page 29]
RFC 2677 NHRP MIB August 1999
"The number of NAKed NHRP Registration Replies
by this client that contained the code
'Administratively Prohibited'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 9 }
nhrpClientStatRxRegisterNakInsufResources OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Registration Replies
by this client that contained the code
'Insufficient Resources'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 10 }
nhrpClientStatRxRegisterNakAlreadyReg OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Registration Replies
by this client that contained the code indicating '
Internetworking Layer Address Already Registered'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 11 }
nhrpClientStatRxPurgeReq OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
Greene, et al. Standards Track [Page 30]
RFC 2677 NHRP MIB August 1999
"The number of NHRP Purge Requests received by
client
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 12 }
nhrpClientStatTxPurgeReq OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Purge Requests transmitted by
client
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 13 }
nhrpClientStatRxPurgeReply OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Purge Replies received by
client
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 14 }
nhrpClientStatTxPurgeReply OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Purge Replies transmitted by
client
Greene, et al. Standards Track [Page 31]
RFC 2677 NHRP MIB August 1999
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
::= { nhrpClientStatEntry 15 }
nhrpClientStatTxErrorIndication OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Error Indication packets
by this client
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 16 }
nhrpClientStatRxErrUnrecognizedExtension OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Error Indication packets
by this client with the error
'Unrecognized Extension'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 17 }
nhrpClientStatRxErrLoopDetected OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
Greene, et al. Standards Track [Page 32]
RFC 2677 NHRP MIB August 1999
"The number of NHRP Error Indication packets
by this client with the error code 'NHRP Loop Detected'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 18 }
nhrpClientStatRxErrProtoAddrUnreachable OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Error Indication packets
by this client with the error code 'Protocol
Unreachable'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 19 }
nhrpClientStatRxErrProtoError OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Error Indication packets
by this client with the error code 'Protocol Error'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 20 }
Greene, et al. Standards Track [Page 33]
RFC 2677 NHRP MIB August 1999
nhrpClientStatRxErrSduSizeExceeded OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Error Indication packets
by this client with the error code 'NHRP SDU
Exceeded'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 21 }
nhrpClientStatRxErrInvalidExtension OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Error Indication packets
by this client with the error code 'Invalid Extension'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 22 }
nhrpClientStatRxErrAuthenticationFailure OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Error Indication packets
by this client with the error code '
Failure'.
Greene, et al. Standards Track [Page 34]
RFC 2677 NHRP MIB August 1999
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 23 }
nhrpClientStatRxErrHopCountExceeded OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Error Indication packets
by this client with the error code 'Hop Count Exceeded'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Client re-initialization and
other times as indicated by the value
nhrpClientStatDiscontinuityTime."
"Section 5.2.7 NHRP Error Indication, RFC 2332 [17]."
::= { nhrpClientStatEntry 24 }
nhrpClientStatDiscontinuityTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime on the most recent occasion
which any one or more of this Client's
suffered a discontinuity. If no such
have occurred since the last re-initialization of
local management subsystem or the NHRP
re-initialization associated with this entry,
this object contains a zero value."
"RFC 2233 [18]."
::= { nhrpClientStatEntry 25 }
Greene, et al. Standards Track [Page 35]
RFC 2677 NHRP MIB August 1999
--****************************************************************
-- NHRP Server
--****************************************************************
nhrpServerObjects OBJECT IDENTIFIER ::= { nhrpObjects 3 }
--
-- The NHRP Next Hop Server
--
nhrpServerTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains information for a set of
associated with this agent."
::= { nhrpServerObjects 1 }
nhrpServerEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a single NHS."
INDEX { nhrpServerIndex }
::= { nhrpServerTable 1 }
NhrpServerEntry ::= SEQUENCE {
nhrpServerIndex Unsigned32,
nhrpServerInternetworkAddrType AddressFamilyNumbers
nhrpServerInternetworkAddr NhrpGenAddr
nhrpServerNbmaAddrType AddressFamilyNumbers
nhrpServerNbmaAddr NhrpGenAddr
nhrpServerNbmaSubaddr NhrpGenAddr
nhrpServerStorageType StorageType
nhrpServerRowStatus
}
nhrpServerIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"An identifier for the server that is unique within
scope of this agent."
::= { nhrpServerEntry 1 }
Greene, et al. Standards Track [Page 36]
RFC 2677 NHRP MIB August 1999
nhrpServerInternetworkAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the internetwork layer address of
server. This object is used to interpret the value
nhrpServerInternetworkAddr."
::= { nhrpServerEntry 2 }
nhrpServerInternetworkAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the internetwork layer address of
server."
::= { nhrpServerEntry 3 }
nhrpServerNbmaAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the NBMA subnetwork address of this server
This object is used to interpret the value
nhrpServerNbmaAddr."
::= { nhrpServerEntry 4 }
nhrpServerNbmaAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the NBMA subnetwork address of
server."
::= { nhrpServerEntry 5 }
nhrpServerNbmaSubaddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the NBMA subaddress of this server
For NBMA address families without a
concept, this will be a zero-length OCTET STRING."
::= { nhrpServerEntry 6 }
Greene, et al. Standards Track [Page 37]
RFC 2677 NHRP MIB August 1999
nhrpServerStorageType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object defines whether this row is kept
volatile storage and lost upon a Server crash
reboot situation, or if this row is backed up
nonvolatile or permanent storage."
DEFVAL { nonVolatile }
::= { nhrpServerEntry 7 }
nhrpServerRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An object that allows entries in this table to
created and deleted using the RowStatus convention."
::= { nhrpServerEntry 8 }
--
-- The Server Cache
--
nhrpServerCacheTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table extends the nhrpCacheTable
NHSes. If the nhrpCacheTable has a row added due
an NHS or based on information regarding an NHS
a row is also added in this table
The rows in this table will be created when rows
the nhrpCacheTable are created. However, there
be rows created in the nhrpCacheTable which do
have corresponding rows in this table. For example
if the nhrpCacheTable has a row added due to a
Hop Client which is co-resident on the same
as the NHS, a row will not be added to this table."
::= { nhrpServerObjects 2 }
nhrpServerCacheEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
Greene, et al. Standards Track [Page 38]
RFC 2677 NHRP MIB August 1999
"Additional information kept by a NHS for a
Next Hop Resolution Cache entry."
INDEX {
nhrpCacheInternetworkAddrType
nhrpCacheInternetworkAddr
ifIndex
}
::= { nhrpServerCacheTable 1 }
NhrpServerCacheEntry ::= SEQUENCE {
nhrpServerCacheAuthoritative TruthValue
nhrpServerCacheUniqueness
}
nhrpServerCacheAuthoritative OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An indication of whether this cache entry
authoritative, which means the entry was added
of a direct registration request with this server
by Server Cache Synchronization Protocol (SCSP)
an authoritative source."
::= { nhrpServerCacheEntry 1 }
nhrpServerCacheUniqueness OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Uniqueness indicator for this
entry used in duplicate address detection. This
cannot be changed after the entry is active."
::= { nhrpServerCacheEntry 2 }
--
-- The NHRP Server->Client
--
nhrpServerNhcTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
Greene, et al. Standards Track [Page 39]
RFC 2677 NHRP MIB August 1999
"A table of NHCs that are available for use by this
(Server)."
"Section 4 Configuration (Next Hop Servers),
RFC 2332 [17]."
::= { nhrpServerObjects 3 }
nhrpServerNhcEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An NHC that may be used by an NHS."
INDEX { nhrpServerIndex, nhrpServerNhcIndex }
::= { nhrpServerNhcTable 1 }
NhrpServerNhcEntry ::= SEQUENCE {
nhrpServerNhcIndex Unsigned32,
nhrpServerNhcPrefixLength Integer32,
nhrpServerNhcInternetworkAddrType AddressFamilyNumbers
nhrpServerNhcInternetworkAddr NhrpGenAddr
nhrpServerNhcNbmaAddrType AddressFamilyNumbers
nhrpServerNhcNbmaAddr NhrpGenAddr
nhrpServerNhcNbmaSubaddr NhrpGenAddr
nhrpServerNhcInUse TruthValue
nhrpServerNhcRowStatus
}
nhrpServerNhcIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"An identifier for an NHC available to an NHS."
::= { nhrpServerNhcEntry 1 }
nhrpServerNhcPrefixLength OBJECT-
SYNTAX Integer32 (0..255)
MAX-ACCESS read-
STATUS
"The number of bits that define the
layer prefix associated with
nhrpServerNhcInternetworkAddr."
::= { nhrpServerNhcEntry 2 }
Greene, et al. Standards Track [Page 40]
RFC 2677 NHRP MIB August 1999
nhrpServerNhcInternetworkAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the internetwork layer address of
NHRP Client represented in this entry. This
indicates how the value of
is to be interpreted."
::= { nhrpServerNhcEntry 3 }
nhrpServerNhcInternetworkAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the internetwork layer address
the NHRP Client represented by this entry. If
value is not known, this will be a zero-
OCTET STRING."
::= { nhrpServerNhcEntry 4 }
nhrpServerNhcNbmaAddrType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the NBMA subnetwork address of the
Client represented by this entry. This object
how the values of nhrpServerNhcNbmaAddr
nhrpServerNhcNbmaSubaddr are to be interpreted."
::= { nhrpServerNhcEntry 5 }
nhrpServerNhcNbmaAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The NBMA subnetwork address of the NHC. The type of
address is indicated by the corresponding value
nhrpServerNbmaAddrType."
::= { nhrpServerNhcEntry 6 }
nhrpServerNhcNbmaSubaddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Greene, et al. Standards Track [Page 41]
RFC 2677 NHRP MIB August 1999
"The NBMA subaddress of the NHC. For NMBA address
that do not have the concept of subaddress, this
be a zero-length OCTET STRING."
::= { nhrpServerNhcEntry 7 }
nhrpServerNhcInUse OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An indication of whether this NHC is in use by the NHS."
::= { nhrpServerNhcEntry 8 }
nhrpServerNhcRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An object that allows entries in this table to
created and deleted using the RowStatus convention."
::= { nhrpServerNhcEntry 9 }
--
-- The Next Hop Server Statistics
--
nhrpServerStatTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Statistics collected by Next Hop Servers."
::= { nhrpServerObjects 4 }
nhrpServerStatEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Statistics for a particular NHS. The statistics
broken into received (Rx), transmitted (Tx
and forwarded (Fw). Forwarded (Fw) would be
by a transit NHS."
INDEX { nhrpServerIndex }
::= { nhrpServerStatTable 1 }
Greene, et al. Standards Track [Page 42]
RFC 2677 NHRP MIB August 1999
NhrpServerStatEntry ::= SEQUENCE {
nhrpServerStatRxResolveReq Counter32,
nhrpServerStatTxResolveReplyAck Counter32,
nhrpServerStatTxResolveReplyNakProhibited Counter32,
nhrpServerStatTxResolveReplyNakInsufResources Counter32,
nhrpServerStatTxResolveReplyNakNoBinding Counter32,
nhrpServerStatTxResolveReplyNakNotUnique Counter32,
nhrpServerStatRxRegisterReq Counter32,
nhrpServerStatTxRegisterAck Counter32,
nhrpServerStatTxRegisterNakProhibited Counter32,
nhrpServerStatTxRegisterNakInsufResources Counter32,
nhrpServerStatTxRegisterNakAlreadyReg Counter32,
nhrpServerStatRxPurgeReq Counter32,
nhrpServerStatTxPurgeReq Counter32,
nhrpServerStatRxPurgeReply Counter32,
nhrpServerStatTxPurgeReply Counter32,
-- Error
nhrpServerStatRxErrUnrecognizedExtension Counter32,
nhrpServerStatRxErrLoopDetected Counter32,
nhrpServerStatRxErrProtoAddrUnreachable Counter32,
nhrpServerStatRxErrProtoError Counter32,
nhrpServerStatRxErrSduSizeExceeded Counter32,
nhrpServerStatRxErrInvalidExtension Counter32,
nhrpServerStatRxErrInvalidResReplyReceived Counter32,
nhrpServerStatRxErrAuthenticationFailure Counter32,
nhrpServerStatRxErrHopCountExceeded Counter32,
nhrpServerStatTxErrUnrecognizedExtension Counter32,
nhrpServerStatTxErrLoopDetected Counter32,
nhrpServerStatTxErrProtoAddrUnreachable Counter32,
nhrpServerStatTxErrProtoError Counter32,
nhrpServerStatTxErrSduSizeExceeded Counter32,
nhrpServerStatTxErrInvalidExtension Counter32,
nhrpServerStatTxErrAuthenticationFailure Counter32,
nhrpServerStatTxErrHopCountExceeded Counter32,
-- Transit NHS
nhrpServerStatFwResolveReq Counter32,
nhrpServerStatFwResolveReply Counter32,
nhrpServerStatFwRegisterReq Counter32,
nhrpServerStatFwRegisterReply Counter32,
nhrpServerStatFwPurgeReq Counter32,
nhrpServerStatFwPurgeReply Counter32,
nhrpServerStatFwErrorIndication Counter32,
nhrpServerStatDiscontinuityTime
Greene, et al. Standards Track [Page 43]
RFC 2677 NHRP MIB August 1999
}
nhrpServerStatRxResolveReq OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Resolution Requests received by
server
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 1 }
nhrpServerStatTxResolveReplyAck OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of positively acknowledged
Resolution Replies transmitted by this server
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 2 }
nhrpServerStatTxResolveReplyNakProhibited OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Resolution
transmitted by this server with the
'Administratively Prohibited'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 3 }
Greene, et al. Standards Track [Page 44]
RFC 2677 NHRP MIB August 1999
nhrpServerStatTxResolveReplyNakInsufResources OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Resolution
transmitted by this server with the
'Insufficient Resources'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 4 }
nhrpServerStatTxResolveReplyNakNoBinding OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Resolution
transmitted by this server with the
'No Internetworking Layer Address to
Address Binding Exists'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 5 }
nhrpServerStatTxResolveReplyNakNotUnique OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Resolution
transmitted by this server with the
'Binding Exists But Is Not Unique'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 6 }
Greene, et al. Standards Track [Page 45]
RFC 2677 NHRP MIB August 1999
nhrpServerStatRxRegisterReq OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NHRP Registration Requests
by this server
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 7 }
nhrpServerStatTxRegisterAck OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of positively acknowledged NHRP
Replies transmitted by this server
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 8 }
nhrpServerStatTxRegisterNakProhibited OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of NAKed NHRP Registration
transmitted by this server with the
'Administratively Prohibited'.
Discontinuities in the value of this counter can
at re-initialization of the management system,
NHRP Server re-initialization and
other times as indicated by the value
nhrpServerStatDiscontinuityTime."
::= { nhrpServerStatEntry 9 }
Greene, et al. Standards Track [Page 46]
RFC 2677 NHRP MIB August 1999
nhrpServerStatTxRegisterNakInsufResources OBJECT-
SYNTAX Counter32
MAX-ACCESS