draft-ietf-manet-nhdp-mib-03.txt   draft-ietf-manet-nhdp-mib-04.txt 
Internet Engineering Task Force U. Herberg Internet Engineering Task Force U. Herberg
Internet-Draft LIX, Ecole Polytechnique Internet-Draft LIX, Ecole Polytechnique
Intended status: Standards Track R. Cole Intended status: Standards Track R. Cole
Expires: September 9, 2010 Johns Hopkins University Expires: January 9, 2011 US Army CERDEC
I. Chakeres I. Chakeres
CenGen CenGen
March 8, 2010 July 8, 2010
Definition of Managed Objects for the Neighborhood Discovery Protocol Definition of Managed Objects for the Neighborhood Discovery Protocol
draft-ietf-manet-nhdp-mib-03 draft-ietf-manet-nhdp-mib-04
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the In particular, it describes objects for configuring parameters of the
Neighborhood Discovery Protocol (NHDP) process on a router. The NHDP Neighborhood Discovery Protocol (NHDP) process on a router. The MIB
MIB also reports state information, performance information and defined in this memo, denoted NHDP-MIB, also reports state,
notifications. This additional state and performance information is performance information and notifications. This additional state and
useful to management stations troubleshooting neighbor discovery performance information is useful to troubleshoot problems and
problems. performance issues during neighbor discovery.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on January 9, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 9, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
skipping to change at page 2, line 15 skipping to change at page 2, line 9
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
5.1. The Configuration Group . . . . . . . . . . . . . . . . . 4 5.1. The Configuration Group . . . . . . . . . . . . . . . . . 4
5.1.1. Interface Parameters . . . . . . . . . . . . . . . . . 4 5.2. The State Group . . . . . . . . . . . . . . . . . . . . . 5
5.1.2. Router Parameters . . . . . . . . . . . . . . . . . . 6 5.3. The Performance Group . . . . . . . . . . . . . . . . . . 5
5.2. The State Group . . . . . . . . . . . . . . . . . . . . . 6 5.4. Notifications . . . . . . . . . . . . . . . . . . . . . . 15
5.3. The Performance Group . . . . . . . . . . . . . . . . . . 7 5.4.1. Introduction . . . . . . . . . . . . . . . . . . . . . 15
5.4. Notifications . . . . . . . . . . . . . . . . . . . . . . 17 5.4.2. Notification Generation . . . . . . . . . . . . . . . 15
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 18 5.4.3. Limiting Frequency of Notifications . . . . . . . . . 15
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 18 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 16
6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 18 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 16
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.2. Relationship to Routing Protocol MIBs relying on the
8. Security Considerations . . . . . . . . . . . . . . . . . . . 61 NHDP-MIB . . . . . . . . . . . . . . . . . . . . . . . . . 16
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 6.3. Relationship to the REPORT-MIB . . . . . . . . . . . . . . 17
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 63 6.4. MIB modules required for IMPORTS . . . . . . . . . . . . . 17
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 17
11.1. Normative References . . . . . . . . . . . . . . . . . . . 64 8. Security Considerations . . . . . . . . . . . . . . . . . . . 58
11.2. Informative References . . . . . . . . . . . . . . . . . . 64 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 65 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 60
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 66 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 67 11.1. Normative References . . . . . . . . . . . . . . . . . . . 60
11.2. Informative References . . . . . . . . . . . . . . . . . . 61
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 61
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 63
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 65
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring aspects of the In particular, it describes objects for configuring parameters of the
Neighborhood Discovery Protocol (NHDP) [NHDP] process on a router. Neighborhood Discovery Protocol [NHDP] process on a router. The MIB
The NHDP MIB also reports state information, performance information defined in this memo, denoted NHDP-MIB, also reports state,
and notifications. This additional state and performance information performance information and notifications. This additional state and
is useful to management stations troubleshooting neighbor discovery performance information is useful to troubleshoot problems and
problems. performance issues during neighbor discovery.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to Section 7 of
RFC 3410 [RFC3410]. [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2578], [RFC2579] and [RFC2580].
[RFC2580].
3. Conventions 3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
4. Overview 4. Overview
The NHDP protocol allows a router in a Mobile Ad-Hoc Network (MANET) [NHDP] allows a router in a Mobile Ad Hoc Network (MANET) to discover
to discover and track topological information of routers up to two and track topological information of routers up to two hops away by
hops away by virtue of exchanging HELLO messages. This information virtue of exchanging HELLO messages. This information is useful for
is useful for routers running various routing and multicast flooding routers running various routing and multicast flooding protocols
protocols developed within the IETF MANET Working Group. developed within the IETF MANET Working Group.
4.1. Terms 4.1. Terms
The following definitions apply throughout this document: The following definitions apply throughout this document:
o Configuration Objects - switches, tables, objects which are o Configuration Objects - switches, tables, objects which are
initialized to default settings or set through the management initialized to default settings or set through the management
interface defined by this MIB. interface defined by this MIB.
o State Objects - automatically generated values which define the o State Objects - automatically generated values which define the
current operating state of the NHDP protocol process in the current operating state of the NHDP protocol process in the
router. router.
o Performance Objects - automatically generated values which help an o Performance Objects - automatically generated values which help an
administrator or automated tool to assess the performance of the administrator or automated tool to assess the performance of the
NHDP protocol process on the router and the overall discovery NHDP protocol process on the router and the overall discovery
performance within the NHDP domain. performance within the MANET.
o Notification Objects - define triggers and associated notification o Notification Objects - define triggers and associated notification
messages allowing for asynchronous tracking of pre-defined events messages allowing for asynchronous tracking of pre-defined events
on the managed device. on the managed router.
5. Structure of the MIB Module 5. Structure of the MIB Module
This section presents the structure of the NHDP MIB module. The MIB This section presents the structure of the NHDP-MIB module. The MIB
is arranged into the following structure: is arranged into the following structure:
o nhdpObjects - defining objects within this MIB. The objects are o nhdpObjects - defining objects within this MIB. The objects are
arranged into the following groups: arranged into the following groups:
* Configuration Group - defining objects related to the * Configuration Group - defining objects related to the
configuration of the NHDP instance on the device. configuration of the NHDP instance on the router.
* State Group - defining objects which reflect the current state * State Group - defining objects which reflect the current state
of the NHDP instance running on the device. of the NHDP instance running on the router.
* Performance Group - defining objects which are useful to a * Performance Group - defining objects which are useful to a
management station when characterizing the performance of NHDP management station when characterizing the performance of NHDP
on the device and in the MANET. on the router and in the MANET.
o nhdpNotifications - objects defining NHDP MIB notifications. o nhdpNotifications - objects defining NHDP-MIB notifications.
o nhdpConformance - defining the minimal and maximal conformance o nhdpConformance - defining the minimal and maximal conformance
requirements for implementations of this MIB. requirements for implementations of this MIB.
5.1. The Configuration Group 5.1. The Configuration Group
The device is configured with a set of controls. The list of The NHDP router is configured with a set of controls. The
configuration controls for the NHDP-MIB (found in [NHDP]), are authoritative list of configuration controls within the NHDP-MIB are
discussed in the following subsections. For all of the configuration found within the MIB module itself. Generally, an attempt was made
parameters, the same constraints apply as specified in [NHDP]. The in developing the NHDP-MIB module to support all configuration
default values of these parameters are defined in [NHDP] objects defined in [NHDP]. For all of the configuration parameters,
the same constraints and default values of these parameters as
5.1.1. Interface Parameters defined in [NHDP] are followed.
The Interface Parameters include:
5.1.1.1. Message Intervals
o HELLO_INTERVAL - is the maximum time between the transmission of
two successive HELLO messages on this MANET interface.
o HELLO_MIN_INTERVAL - is the minimum interval between transmission
of two successive HELLO messages, on this MANET interface.
o REFRESH_INTERVAL - is the maximum interval between advertisements,
in a HELLO message on this MANET interface, of each 1-hop
neighbor.
5.1.1.2. Information Validity Times
Parameters related to the Information Validity Times include:
o L_HOLD_TIME - is the period of advertisement, on this MANET
interface, of former 1-hop neighbor network addresses as lost in
HELLO messages, allowing recipients of these HELLO messages to
accelerate removal of this information from their Link Sets.
o H_HOLD_TIME - is used as the Value in the VALIDITY_TIME Message
TLV included in all HELLO messages on this MANET interface. It is
then used by each router receiving such a HELLO message to
indicate the validity of the information taken from that HELLO
message and recorded in the receiving router's Information Bases.
5.1.1.3. Link Quality
Parameters related to the Link Quality include:
o HYST_ACCEPT - is the link quality threshold at or above which a
link becomes usable, if it was not already so.
o HYST_REJECT - is the link quality threshold below which a link
becomes unusable, if it was not already so.
o INITIAL_QUALITY - is the initial quality of a newly identified
link.
o INITIAL_PENDING - if true, then a newly identified link is
considered pending, and is not usable until the link quality has
reached or exceeded the HYST_ACCEPT threshold.
5.1.1.4. Jitter
If jitter, as defined in [RFC5148], is used then these parameters are
as follows:
o HP_MAXJITTER - represents the value of MAXJITTER used in [RFC5148]
for periodically generated HELLO messages on this MANET interface.
o HT_MAXJITTER - represents the value of MAXJITTER used in [RFC5148]
for externally triggered HELLO messages on this MANET interface.
5.1.2. Router Parameters
The following Router Parameters apply:
5.1.2.1. Information Validity Time
o N_HOLD_TIME - is used as the period during which former 1-hop
neighbor network addresses are advertised as lost in HELLO
messages, allowing recipients of these HELLO messages to
accelerate removal of this information from their 2-Hop Sets.
o I_HOLD_TIME - is the period for which a recently used local
interface network address is recorded.
5.2. The State Group 5.2. The State Group
The State Subtree reports current state information, including The State Group reports current state information of a router running
neighbor tables. These are separately discussed below. [NHDP]. The NHDP-MIB State Group tables were designed to contain the
complete set of state information defined within the information
The Local Information Base (LIB), contains the network addresses of bases in [NHDP].
the interfaces (MANET and non-MANET) of this router. The contents of
this Information Base are not changed by signaling. The LIB contains
two tables:
o The "Local Interface Set", which records its local interfaces. It
consists of Local Interface Tuples, one per interface. Note that
the information from this set is contained in the
nhdpInterfaceTable, which is defined by this MIB document.
Therefore, the Local Interface Set is not defined as an object in
this MIB.
o The "Removed Interface Address Set", which records network
addresses which were recently used as local interface network
addresses. It consists of Removed Interface Address Tuples, one
per network address.
The Interface Information Based (IIB), recording information
regarding links to this MANET interface and symmetric 2-hop neighbors
which can be reached through such links. The IIB contains two
tables:
o A "Link Set", which records information about current and recently
lost links between this interface and MANET interfaces of 1-hop
neighbors. The Link Set consists of Link Tuples, each of which
contains information about a single link.
o A "Two-Hop Set", which records the existence of bidirectional
links between symmetric 1-hop neighbors of this MANET interface
and other routers (symmetric 2-hop neighbors). The 2-Hop Set
consists of 2-Hop Tuples, each of which records an interface
address of a symmetric 2-hop neighbor, and all interface addresses
of the corresponding symmetric 1-hop neighbor.
The Neighbor Information Base (NIB), records information regarding
current and recently lost 1-hop neighbors of this router. The NIB
contains two tables:
o A "Neighbor Set", which records all network addresses of each
1-hop neighbor. It consists of Neighbor Tuples, each representing
a single 1-hop neighbor
o A "Lost Neighbor Set", which records network addresses of routers Two constructs, i.e., TEXTUAL CONVENTIONs, are defined in support of
which recently were symmetric 1-hop neighbors, but which are now the tables in the State Group. These are NeighborIfIndex and
advertised as lost. It consists of Lost Neighbor Tuples, each NeighborRouterId. These are locally (to the NHDP router) defined,
representing a single such network address unique identifiers. They are used to define indexes to the
appropriate State Group tables and to correlate table entries to
interface address, interfaces and routers within the MANET.
NeighborIfIndex is a unique identifier of discovered NHDP interfaces
on all routers within the MANET. NeighborRouterId is a unique
identifier of discovered NHDP routers within the MANET.
5.3. The Performance Group 5.3. The Performance Group
The Performance Group reports values relevant to system performance. The Performance Group reports values relevant to system performance.
This section lists objects for NHDP performance monitoring, some of This section lists objects for NHDP performance monitoring, some of
which explicitly appear in the NHDP-MIB and others which are which explicitly appear in the NHDP-MIB and others which are
obtainable through a combination of base objects from this MIB and obtainable through a combination of base objects from this MIB and
reports available through the REPORT-MIB [REPORT]. Throughout this reports available through the REPORT-MIB [REPORT]. Throughout this
section those objects will be pointed out that are intended as base section, those objects will be pointed out that are intended as base
objects which will be explicitly defined within this MIB and those objects, which will be explicitly defined within this MIB, and those
objects which are derived through a combination of the base objects objects which are derived through a combination of the base objects
and capabilities afforded by the REPORT-MIB. and capabilities afforded by the REPORT-MIB.
The objects described in the following can be useful for determining The objects described in the following can be useful for determining
certain properties of the NHDP instance. Notably unstable neighbors certain properties of the NHDP instance. Notably unstable neighbors
or 2-hop neighbors and frequent changes of sets can have a negative or 2-hop neighbors and frequent changes of sets can have a negative
influence on the performance of NHDP. The following objects allow influence on the performance of NHDP. The following objects allow
management applications to acquire information related to the management applications to acquire information related to the
stability and performance of NHDP: stability and performance of NHDP:
The following objects return some of the statistics related to HELLO The following objects return statistics related to HELLO messages:
messages:
o Total number of sent HELLO messages on an interface o Total number of sent HELLO messages on an interface
This is a Base Object. This is a Base Object.
Object name: nhdpIfHelloMessageXmits Object name: nhdpIfHelloMessageXmits
Object type: Counter32 Object type: Counter32
o Total number of received HELLO messages on an interface o Total number of received HELLO messages on an interface
skipping to change at page 8, line 40 skipping to change at page 6, line 29
Object type: Counter32 Object type: Counter32
o Total number of sent triggered HELLO messages on an interface o Total number of sent triggered HELLO messages on an interface
This is a Base Object. This is a Base Object.
Object name: nhdpIfHelloMessageTriggeredXmits Object name: nhdpIfHelloMessageTriggeredXmits
Object type: Counter32 Object type: Counter32
o Acquire history of HELLO message scheduling instance for the given o Acquire history of HELLO message scheduling instances for a given
time duration on an interface time duration on an interface
It is desirable to develop the history of the exact timestamps It is desirable to develop the history of the exact timestamps
of each HELLO message that has been sent as well as the type of of each HELLO message that has been sent as well as the type of
the message (triggered or periodical). The list of events the message (triggered or periodical). The list of events
starts at the given point of time t0 and ends at the given time starts at the given point of time t0 and ends at the given time
t1. t1.
This is a Derived Object to be pulled from the REPORT-MIB. It This is a Derived Object to be pulled from the REPORT-MIB. It
is derived from, e.g., the nhdpIfHelloMessagePeriodicXmits Base is derived from, e.g., the nhdpIfHelloMessagePeriodicXmits Base
Object from the NHDP-MIB along with the capabilities derived Object from the NHDP-MIB along with the capabilities derived
from the reportHistoryGroup from the REPORT-MIB. from the reportHistoryGroup from the REPORT-MIB.
Object type: SEQUENCE OF (TimeStamp, nhdpMessageType) Object type: SEQUENCE OF (TimeStamp, nhdpMessageType)
o Histogram of the intervals between HELLO messages on an interface o Histogram of the intervals between HELLO messages on an interface
It is desirable to track the values (in a 2-dimensional array) It is desirable to track the values (in a 2-dimensional array)
that represent a histogram of intervals between HELLO messages, that represent a histogram of intervals between HELLO messages,
separated by periodic and triggered HELLOs. The histogram separated by periodic and triggered HELLOs. The histogram
would display the distribution of intervals between two displays the distribution of intervals between two consecutive
consecutive HELLOs of the same type (triggered or periodical) HELLOs of the same type (triggered or periodical) using a given
using a given bin size. It includes all HELLOs that have been bin size. It includes all HELLOs that have been sent after the
sent after the given time t0 and before the given time t1. given time t0 and before the given time t1.
This is a Derived Object to be pulled from the REPORT-MIB. It This is a Derived Object to be pulled from the REPORT-MIB. It
can be derived from, e.g., the nhdpIfHelloMessagePeriodicXmits can be derived from, e.g., the nhdpIfHelloMessagePeriodicXmits
Base Object from the NHDP-MIB along with the capabilities Base Object from the NHDP-MIB along with the capabilities
derived from the reportHistoryGroup from the REPORT-MIB. The derived from the reportHistoryGroup from the REPORT-MIB. The
network management application could convert this information network management application could convert this information
into the desired histogram. into the desired histogram.
Object type: SEQUENCE OF (nhdpMessageType, TimeTicks, Object type: SEQUENCE OF (nhdpMessageType, TimeTicks,
Unsigned32) Unsigned32)
o Changes of the frequency of the message scheduling on an interface o Changes of the frequency of the message scheduling on an interface
This object will divide the given time interval from t0 to t1 This object will divide the given time interval from t0 to t1
into a given number of equal parts. It then creates a into a given number of equal parts. It then creates a
histogram for each part and calculate the distances (using the histogram for each part and calculates the distances (e.g.
Bhattacharyya distance) between each two adjacent histograms in using the Bhattacharyya distance) between each two adjacent
time. A higher value between two histograms means more histograms in time. A higher value between two histograms
difference between the histograms. For instance, that could means more difference between the histograms. For instance,
happen if suddenly many triggered HELLO messages are sent, this is representative of an event that suddenly sends many
whereas before there have been only very few such triggered triggered HELLO messages, whereas before only very few such
messages. triggered messages have been transmitted.
This is a Derived Object to be pulled from the REPORT-MIB, as This is a Derived Object to be pulled from the REPORT-MIB, as
previously discussed, albeit this is a bit more complex with previously discussed, albeit this is a bit more complex with
respect to the management application. respect to the management application.
Object type: SEQUENCE OF (nhdpMessageType, TimeStamp, Float32) Object type: SEQUENCE OF (nhdpMessageType, TimeStamp, Float32)
o Average number of sent HELLO messages per second between the given o Average number of sent HELLO messages per second between the given
time t0 and t1 on an interface time t0 and t1 on an interface
skipping to change at page 11, line 5 skipping to change at page 8, line 43
Object type: Float32 Object type: Float32
o Average size in octets of received HELLO messages between the o Average size in octets of received HELLO messages between the
given time t0 and t1 on an interface given time t0 and t1 on an interface
This is a Derived Object to be pulled from the REPORT-MIB. See This is a Derived Object to be pulled from the REPORT-MIB. See
previous discussion. previous discussion.
Object type: Float32 Object type: Float32
o Total accumulated number of advertized symmetric neighbors in o Total accumulated number of advertised symmetric neighbors in
HELLOs on that interface. HELLOs on that interface.
This is a Base Object. This is a Base Object.
Object name: Object name:
nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount
Object type: Counter32 Object type: Counter32
o Total accumulated number of advertized heard neighbors in HELLOs o Total accumulated number of advertised heard neighbors in HELLOs
on that interface on that interface
This is a Base Object. This is a Base Object.
Object name: Object name:
nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount
Object type: Counter32 Object type: Counter32
o Total accumulated number of advertized lost neighbors in HELLOs on o Total accumulated number of advertised lost neighbors in HELLOs on
that interface that interface
This is a Base Object. This is a Base Object.
Object name: nhdpIfHelloMessageXmitAccumulatedLostNeighborCount Object name: nhdpIfHelloMessageXmitAccumulatedLostNeighborCount
Object type: Counter32 Object type: Counter32
o Number of expected packets from a given neighbor based on the o Number of expected packets from a given neighbor based on the
packet sequence number on an interface packet sequence number on an interface
skipping to change at page 12, line 51 skipping to change at page 10, line 43
previously discussed Base Object. The network management previously discussed Base Object. The network management
application would develop the histograms based upon lists application would develop the histograms based upon lists
obtained from the REPORT-MIB. obtained from the REPORT-MIB.
Object type: SEQUENCE OF (TimeTicks, Unsigned32) Object type: SEQUENCE OF (TimeTicks, Unsigned32)
o Changes of the frequency of the Neighbor Set changes o Changes of the frequency of the Neighbor Set changes
This object will divide the given time interval from t0 to t1 This object will divide the given time interval from t0 to t1
into a given number of equal parts. It then creates a into a given number of equal parts. It then creates a
histogram for each part and calculate the distances (using the histogram for each part and calculates the distances (e.g.
Bhattacharyya distance) between each two adjacent histograms in using the Bhattacharyya distance) between each two adjacent
time. A higher value between two histograms means more histograms in time. A higher value between two histograms
difference between the histograms. means more difference between the histograms.
This is a Derived Object to be pulled from the This is a Derived Object to be pulled from the
reportHistoryGroup from the REPORT-MIB. It is derived from the reportHistoryGroup from the REPORT-MIB. It is derived from the
previously discussed Base Object. The network management previously discussed Base Object. The network management
application could then compute the desired metrics. application could then compute the desired metrics.
Object type: SEQUENCE OF (TimeStamp, Float32) Object type: SEQUENCE OF (TimeStamp, Float32)
The next objects examine the uptime of a given neighbor: The next objects examine the uptime of a given neighbor:
skipping to change at page 14, line 22 skipping to change at page 12, line 12
histogram includes all changes that have been made after the histogram includes all changes that have been made after the
given time t0 and before the given time t1. given time t0 and before the given time t1.
This is a Derived Object to be pulled from the This is a Derived Object to be pulled from the
reportHistoryGroup of the REPORT-MIB. It is derived from, e.g. reportHistoryGroup of the REPORT-MIB. It is derived from, e.g.
the nhdpDiscNeighborNibNeighborSetChanges Base Object defined the nhdpDiscNeighborNibNeighborSetChanges Base Object defined
in this MIB. This object sits in the in this MIB. This object sits in the
nhdpDiscNeighborSetPerfTable which is indexed by the nhdpDiscNeighborSetPerfTable which is indexed by the
nhdpDiscNeighborSetRouterId. nhdpDiscNeighborSetRouterId.
Object name: nhdpNeighborStatusHistogram
Object type: SEQUENCE OF (TimeTicks, Unsigned32) Object type: SEQUENCE OF (TimeTicks, Unsigned32)
The following objects examine the stability of a neighbor. A The following objects examine the stability of a neighbor. A
neighbor is said to be unstable if it "flaps" frequently between neighbor is said to be unstable if it "flaps" frequently between
several links. It is said to be stable if the set of Link Tuples several links. It is said to be stable if the set of Link Tuples
that correspond to the given neighbor is stationary. that correspond to the given neighbor is stationary.
o Count the changes of the interface over which a given neighbor can o Count the changes of the interface over which a given neighbor can
be reached. be reached.
skipping to change at page 15, line 12 skipping to change at page 12, line 49
given link moves from the Link Set of one interface to another given link moves from the Link Set of one interface to another
interface. interface.
This is a Derived Object to be pulled from the This is a Derived Object to be pulled from the
reportHistoryGroup of the REPORT-MIB. It is derived from, reportHistoryGroup of the REPORT-MIB. It is derived from,
e.g., the nhdpDiscNeighborNibNeighborSetReachableLinkChanges e.g., the nhdpDiscNeighborNibNeighborSetReachableLinkChanges
Base Object. The network management could develop the desired Base Object. The network management could develop the desired
histogram based upon the information retrieved from the REPORT- histogram based upon the information retrieved from the REPORT-
MIB. MIB.
Object name: nhdpNeighborIfChangeHistory
Object type: SEQUENCE OF (TimeStamp) Object type: SEQUENCE OF (TimeStamp)
o Histogram of the intervals between a change of the interface over o Histogram of the intervals between a change of the interface over
which a given neighbor is reachable which a given neighbor is reachable
Returns the values that represent a histogram of intervals Returns the values that represent a histogram of intervals
between a change of the interface over which a given neighbor between a change of the interface over which a given neighbor
is reachable after the given time t0 and before the given time is reachable after the given time t0 and before the given time
t1. t1.
This is a Derived Object to be pulled from the This is a Derived Object to be pulled from the
reportHistoryGroup from the REPORT-MIB. It is derived from the reportHistoryGroup from the REPORT-MIB. It is derived from the
previously discussed Base Object. The network management previously discussed Base Object,
application would develop the histograms based upon lists nhdpDiscNeighborNibNeighborSetChanges counter. The network
obtained from the REPORT-MIB. management application would develop the histograms based upon
lists obtained from the REPORT-MIB.
Object name: nhdpNeighborIfChangeHistogram
Object type: SEQUENCE OF ( TimeTicks, Unsigned32)) Object type: SEQUENCE OF (TimeTicks, Unsigned32)
The following objects inspect the stability of a given 2-hop The following objects inspect the stability of a given 2-hop
neighbor: neighbor:
o Count the changes of the N2_neighbor_iface_addr_list of a given o Count the changes of the N2_neighbor_iface_addr_list of a given
2-hop neighbor 2-hop neighbor
This object returns the count of the times the 2-hop neighbor This object returns the count of the times the 2-hop neighbor
changes its N2_neighbor_iface_addr_list, i.e. the neighbor over changes its N2_neighbor_iface_addr_list, i.e. the neighbor over
which it is reachable. which it is reachable.
This is a Base Object. This is a Base Object.
Object name: nhdpIib2HopSetPerfChanges Object name: nhdpIib2HopSetPerfChanges
Object type: Counter32 Object type: Counter32
o Acquire history of changes of the N2_neighbor_iface_addr_list of a o Acquire history of changes of the N2_neighbor_iface_addr_list of a
given 2-hop neighbor (Note: Not sure what the Base Object is for given 2-hop neighbor
this set and not clear how to capture in the REPORT-MIB.)
This object returns the history of the exact timestamps of each This object returns the history of the exact timestamps of each
time the 2-hop neighbor changes its time the 2-hop neighbor changes its
N2_neighbor_iface_addr_list, i.e. the neighbor over which it is N2_neighbor_iface_addr_list, i.e. the neighbor over which it is
reachable. reachable.
This is a Derived Object to be pulled from the This is a Derived Object to be pulled from the
reportHistoryGroup of the REPORT-MIB. It is derived from the reportHistoryGroup of the REPORT-MIB. It is derived from the
previously discussed Base Object. previously discussed Base Object, nhdpIib2HopSetPerfChanges
counter.
Object name: nhdpN2ReachabilityChangeHistory
Object type: SEQUENCE OF (TimeStamp) Object type: SEQUENCE OF (TimeStamp)
o Histogram of the intervals between a change of a 2-hop neighbor's o Histogram of the intervals between a change of a 2-hop neighbor's
N2_neighbor_iface_addr_list N2_neighbor_iface_addr_list
Returns the values that represent a histogram of intervals Returns the values that represent a histogram of intervals
between a change of the 2-hop neighbor's between a change of the 2-hop neighbor's
N2_neighbor_iface_addr_list after the given time t0 and before N2_neighbor_iface_addr_list after the given time t0 and before
the given time t1. the given time t1.
This is a Derived Object to be pulled from the This is a Derived Object to be pulled from the
reportHistoryGroup from the REPORT-MIB. It is derived from the reportHistoryGroup from the REPORT-MIB. It is derived from the
previously discussed Base Object. The network management previously discussed Base Object, nhdpIib2HopSetPerfChanges
application would develop the histograms based upon lists counter. The network management application would develop the
obtained from the REPORT-MIB. histograms based upon lists obtained from the REPORT-MIB.
Object name: nhdpN2ReachabilityChangeHistogram
Object type: SEQUENCE OF (TimeTicks, Unsigned32) Object type: SEQUENCE OF (TimeTicks, Unsigned32)
The next objects examine the uptime of a given 2-hop neighbor: The next objects examine the uptime of a given 2-hop neighbor:
o 2-hop Neighbor uptime o 2-hop Neighbor uptime
Returns the number of milliseconds since the 2-Hop Tuple Returns the number of milliseconds since the 2-Hop Tuple
corresponding to the given 2-hop neighbor IP address exists. corresponding to the given 2-hop neighbor IP address exists.
skipping to change at page 17, line 4 skipping to change at page 14, line 38
corresponding to the given 2-hop neighbor IP address exists. corresponding to the given 2-hop neighbor IP address exists.
This is a Base Object. This is a Base Object.
Object name: nhdpIib2HopSetPerfUpTime Object name: nhdpIib2HopSetPerfUpTime
Object type: Unsigned32 Object type: Unsigned32
o Acquire history of change of onlink status of a given 2-hop o Acquire history of change of onlink status of a given 2-hop
neighbor neighbor
This object returns the history of the exact timestamps of each This object returns the history of the exact timestamps of each
time the 2-hop neighbor becomes onlink or offlink. A 2-hop time the 2-hop neighbor becomes onlink or offlink. A 2-hop
neighbor is said to become "onlink" if a new 2-hop Tuple is neighbor is said to become "onlink" if a new 2-hop Tuple is
created that corresponds to the given 2-hop neighbor. It created that corresponds to the given 2-hop neighbor. It
becomes "offlink" if such a tuple has been deleted. becomes "offlink" if such a tuple has been deleted.
This is a Derived Object to be pulled from the This is a Derived Object to be pulled from the
reportHistoryGroup of the REPORT-MIB. It is derived from the reportHistoryGroup of the REPORT-MIB. It is derived from the
previously discussed Base Object. previously discussed Base Object, nhdpIib2HopSetPerfChanges
counter.
Object name: nhdpN2StatusHistory
Object type: SEQUENCE OF (TimeStamp) Object type: SEQUENCE OF (TimeStamp)
o Histogram of the intervals between a change of the onlink status o Histogram of the intervals between a change of the onlink status
of a given 2-hop neighbor of a given 2-hop neighbor
Returns the values that represent a histogram of intervals Returns the values that represent a histogram of intervals
between a change of the onlink status of a given 2-hop between a change of the onlink status of a given 2-hop
neighbor. The histogram includes all changes that have been neighbor. The histogram includes all changes that have been
made after the given time t0 and before the given time t1. made after the given time t0 and before the given time t1.
This is a Derived Object to be pulled from the This is a Derived Object to be pulled from the
reportHistoryGroup from the REPORT-MIB. It is derived from the reportHistoryGroup from the REPORT-MIB. It is derived from the
previously discussed Base Object. The network management previously discussed Base Object, nhdpIib2HopSetPerfChanges
application would develop the histograms based upon lists counter. The network management application would develop the
obtained from the REPORT-MIB. histograms based upon lists obtained from the REPORT-MIB.
Object name: nhdpN2StatusHistogram
Object type: SEQUENCE OF (TimeTicks, Unsigned32) Object type: SEQUENCE OF (TimeTicks, Unsigned32)
5.4. Notifications 5.4. Notifications
The Notifications subtree contains the list of notifications This section describes the use of notifications, and mechanisms to
supported within the NHDP MIB and their intended purpose or utility. enhance the ability to manage NHDP networks.
The following notifications are specified:
o nhdpNbrStateChange is a notification sent each time the status of 5.4.1. Introduction
a neighbor has changed. Possible status values are down,
asymmetric, and symmetric.
o nhdp2hopNbrStateChange is a notification sent each time the status Notifications can be emitted by an NHDP router as a reaction a to
of a neighbor has changed. Possible status values are down and specific event. This allows a network manager to efficiently
up. determine the source of problems or significant changes of
configuration or topology, instead of polling a possibly large number
of NHDP routers.
o nhdpIfRxBadMessage is a notification sent each time an incoming 5.4.2. Notification Generation
HELLO message has not been succesfully parsed on an interface.
o nhdpIfStateChange is a notification sent each time the status of When an exception event occurs, the application notifies the local
an interface of the designated router has changed (i.e. an IP agent, which sends a notification to the appropriate SNMP management
address has been added or removed to the interface, or the stations. The message includes the notification type and may include
interface has changed its status from up to down or vice versa). a list of notification-specific variables. Section 7 contains,
amongst others, the notification definitions, which includes the
variable lists. At least one IP address of the NHDP router that
originates the notification is included in the variable list so that
the network manager may determine the source of the notification.
5.4.3. Limiting Frequency of Notifications
To limit the frequency of notifications, the following additional
mechanisms are suggested, similar to those in [RFC4750]:
5.4.3.1. Ignoring Initial Activity
The majority of critical events occur when NHDP is enabled on a
router, at which time the symmetric neighbors and two-hop neighbors
of the NHDP router are discovered. During this initial period, a
potential flood of notifications is unnecessary since the events are
expected. To avoid unnecessary notifications, a router should not
originate expected notifications until a certain time interval has
elapsed, which is to be predefined by the network manager.
5.4.3.2. Throttling Traps
The mechanism for throttling the notifications is the same as in
[RFC4750] (i.e. the amount of transmitted notifications per time is
bounded).
Appropriate values for the window time and upper bound are to be
selected by the network manager and depend on the deployment of the
MANET.
5.4.3.3. One Notification per Event
Similar to the according mechanism in [RFC4750], only one
notification is sent per event.
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
This section specifies the relationship of the MIB modules contained This section specifies the relationship of the MIB modules contained
in this document to other standards, particularly to standards in this document to other standards, particularly to standards
containing other MIB modules. Definitions imported from other MIB containing other MIB modules. Definitions imported from other MIB
modules and other MIB modules that SHOULD be implemented in modules and other MIB modules that SHOULD be implemented in
conjunction with the MIB module contained within this document are conjunction with the MIB module contained within this document are
identified in this section. identified in this section.
6.1. Relationship to the SNMPv2-MIB 6.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The NHDP-MIB does not entity and certain other system-wide data. The NHDP-MIB does not
duplicate those objects. duplicate those objects.
6.2. MIB modules required for IMPORTS 6.2. Relationship to Routing Protocol MIBs relying on the NHDP-MIB
The following NHDP MIB module IMPORTS objects from SNMPv2-SMI [NHDP] allows routing protocols to rely on the neighborhood
information that is discovered by means of HELLO message exchange.
In order to allow for troubleshoot, fault isolate, and manage such
routing protocols through a routing protocol MIB, it may be desired
to align the State Group tables of the NHDP-MIB and the routing
protocol MIB. This is accomplished through the definition of two
TEXTUAL-CONVENTIONS in the NHDP-MIB: the NeighborInterfaceId and the
NeighborRouterId. These object types are used to develop indexes
into common NHDP-MIB and routing protocol State Group tables. These
objects are locally significant but should be locally common to the
NHDP-MIB and the routing protocol MIB implemented on a common
networked router. This will allow for improved cross referencing of
information across the two MIBs.
6.3. Relationship to the REPORT-MIB
This document describes several Performance Management metrics for
the management of NHDP network routers. However, not all of these
metrics are explicitly defined solely within the context of this
NHDP-MIB. Some of these metrics are obtained through joint
interaction between this MIB and the REPORT-MIB [REPORT]. This NHDP-
MIB defines the minimum necessary objects (often of type COUNTER)
which form the underlying basis for more sophisticated Performance
Management reporting available in conjunction with the REPORT-MIB.
See Section 5.3 for a discussion of the performance metrics for NHDP
management.
6.4. MIB modules required for IMPORTS
The following NHDP-MIB module IMPORTS objects from SNMPv2-SMI
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB
[RFC2863], INET-ADDRESS-MIB [RFC4001], and SMIng [RFC3781]. [RFC2863], INET-ADDRESS-MIB [RFC4001], and SMIng [RFC3781].
7. Definitions 7. Definitions
NHDP-MIB DEFINITIONS ::= BEGIN This section contains the MIB module defined by the specification.
NHDP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Float32 Float32
FROM SMIng --[RFC3781] FROM SMIng --[RFC3781]
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Unsigned32, mib-2 Counter32, Integer32, Unsigned32, mib-2
FROM SNMPv2-SMI --[RFC2578] FROM SNMPv2-SMI --[RFC2578]
TEXTUAL-CONVENTION, StorageType, TimeStamp, TEXTUAL-CONVENTION, StorageType, TimeStamp,
TruthValue, RowStatus TruthValue, RowStatus
FROM SNMPv2-TC --[RFC2579] FROM SNMPv2-TC --[RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF --[STD58] FROM SNMPv2-CONF --[STD58]
InetAddressType, InetAddress, InetAddressType, InetAddress,
InetAddressPrefixLength InetAddressPrefixLength
FROM INET-ADDRESS-MIB --[RFC4001] FROM INET-ADDRESS-MIB --[RFC4001]
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB --[RFC2863] FROM IF-MIB --[RFC2863]
; ;
nhdpMIB MODULE-IDENTITY nhdpMIB MODULE-IDENTITY
LAST-UPDATED "201003081000Z" -- March 08,2010 LAST-UPDATED "201007071000Z" -- July 07,2010
ORGANIZATION "IETF MANET working group" ORGANIZATION "IETF MANET working group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com WG Chairs: ian.chakeres@gmail.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Ulrich Herberg Editors: Ulrich Herberg
Ecole Polytechnique Ecole Polytechnique
LIX LIX
91128 Palaiseau Cedex 91128 Palaiseau Cedex
France France
+33 1 69 33 41 26
ulrich@herberg.name ulrich@herberg.name
http://www.herberg.name/ http://www.herberg.name/
Robert G. Cole Robert G. Cole
Johns Hopkins University US Army CERDEC
Department of Computer Science Space and Terrestrial Communications
3400 North Charles Street 328 Hopkins Road
NEB Room 213 Bldg 245, Room 16
Baltimore, MD 21218 Aberdeen Proving Ground, MD 21005
USA USA
+1 443 910-4420 +1 410 278-6779
rgcole01@comcast.net robert.g.cole@us.army.mil
http://www.cs.jhu.edu/~rgcole/ http://www.cs.jhu.edu/~rgcole/
Ian D Chakeres Ian D Chakeres
CenGen CenGen
9250 Bendix Road North 9250 Bendix Road North
Columbia, Maryland 21045 Columbia, Maryland 21045
USA USA
ian.chakeres@gmail.com ian.chakeres@gmail.com
http://www.ianchak.com/" http://www.ianchak.com/"
DESCRIPTION DESCRIPTION
"This NHDP MIB module is applicable to devices "This NHDP-MIB module is applicable to routers
implementing the Neighborhood Discovery Protocol implementing the Neighborhood Discovery Protocol
defined in [XXX]. defined in [RFC XXXX].
Copyright (C) The IETF Trust (2009). This version Copyright (C) The IETF Trust (2009). This version
of this MIB module is part of RFC xxxx; see the RFC of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices." itself for full legal notices."
-- revision -- revision
REVISION "201007071000Z" -- July 07, 2010
DESCRIPTION
"The seventh version of this MIB module,
published as draft-ietf-manet-nhdp-mib-04.txt.
Cleaned up and condensed the textual material
in the earlier sections of this draft. Checked
consistency with NHDP draft, i.e.,
draft-ietf-manet-nhdp-12.txt."
REVISION "201003081000Z" -- March 08, 2010 REVISION "201003081000Z" -- March 08, 2010
DESCRIPTION DESCRIPTION
"The sixth version of this MIB module, "The sixth version of this MIB module,
published as draft-ietf-manet-nhdp-mib-03.txt. published as draft-ietf-manet-nhdp-mib-03.txt.
Added the local nhdpIfIndex to the Added the local nhdpIfIndex to the
nhdpIibLinkSetTable." nhdpIibLinkSetTable."
REVISION "200911091000Z" -- November 09, 2009 REVISION "200911091000Z" -- November 09, 2009
DESCRIPTION DESCRIPTION
"The fifth version of this MIB module, "The fifth version of this MIB module,
published as draft-ietf-manet-nhdp-mib-02.txt. published as draft-ietf-manet-nhdp-mib-02.txt.
skipping to change at page 21, line 32 skipping to change at page 20, line 38
NHDP neighbor interface. NHDP neighbor interface.
All objects of type NeighborIfIndex are assigned by the agent All objects of type NeighborIfIndex are assigned by the agent
out of a common number space. In other words, NeighborIfIndex out of a common number space. In other words, NeighborIfIndex
values assigned to entries in one table must not overlap with values assigned to entries in one table must not overlap with
NeighborIfIndex values assigned to entries in another NeighborIfIndex values assigned to entries in another
table. table.
The NeighborIfIndex defines a discovered interface of a 1-hop The NeighborIfIndex defines a discovered interface of a 1-hop
or 2-hop neighbor of the local router. The agent identifies a or 2-hop neighbor of the local router. The agent identifies a
unique neighbor interface through the reciept of an address unique neighbor interface through the receipt of an address
list advertised through an NHDP HELLO message. list advertised through an NHDP HELLO message.
The value for each discovered neighbor interface must remain The value for each discovered neighbor interface must remain
constant at least from one re-initialization of the entity's constant at least from one re-initialization of the entity's
network management system to the next re-initialization, except network management system to the next re-initialization, except
that if an application is deleted and re-created. that if an application is deleted and re-created.
The specific value is meaningful only within a given SNMP The specific value is meaningful only within a given SNMP
entity. An NeighborIfIndex value must not be re-used until the entity. An NeighborIfIndex value must not be re-used until the
next agent restart." next agent restart."
skipping to change at page 22, line 10 skipping to change at page 21, line 16
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A locally arbitrary unique identifier associated with an "A locally arbitrary unique identifier associated with an
NHDP discovered peer router. NHDP discovered peer router.
All objects of type NeighborRouterId are assigned by the agent All objects of type NeighborRouterId are assigned by the agent
out of a common number space. out of a common number space.
The NeighborRouterId defines a discovered NHDP peer of The NeighborRouterId defines a discovered NHDP peer of
the local router. The agent identifies a the local router. The agent identifies a
unique neighbor through the reciept of an address unique neighbor interface through the receipt of an address
list advertised through an NHDP HELLO message and the list advertised through an NHDP HELLO message.
associated .....
The value for each discovered neighbor ID must remain The value for each discovered neighbor ID must remain
constant at least from one re-initialization of the entity's constant at least from one re-initialization of the entity's
network management system to the next re-initialization, except network management system to the next re-initialization, except
that if an application is deleted and re-created. that if an application is deleted and re-created.
The specific value is meaningful only within a given SNMP The specific value is meaningful only within a given SNMP
entity. An NeighborRouterId value must not be re-used until the entity. An NeighborRouterId value must not be re-used until the
next agent restart." next agent restart."
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
-- --
-- nhdpObjects -- nhdpObjects
-- --
-- 1) Configuration Objects Group
-- 2) State Objects Group
-- 3) Performance Objects Group
-- --
-- nhdpConfigurationObjGrp -- nhdpConfigurationObjGrp
-- --
-- Contains the NHDP objects which configure specific options -- Contains the NHDP objects which configure specific options
-- which determine the overall performance and operation of the -- which determine the overall performance and operation of the
-- discovery protocol. -- discovery protocol.
nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 } nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 }
skipping to change at page 22, line 42 skipping to change at page 22, line 4
-- --
-- nhdpConfigurationObjGrp -- nhdpConfigurationObjGrp
-- --
-- Contains the NHDP objects which configure specific options -- Contains the NHDP objects which configure specific options
-- which determine the overall performance and operation of the -- which determine the overall performance and operation of the
-- discovery protocol. -- discovery protocol.
nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 } nhdpConfigurationObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 1 }
nhdpInterfaceTable OBJECT-TYPE nhdpInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpInterfaceEntry SYNTAX SEQUENCE OF NhdpInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NHDP Interface Table describes the "nhdpInterfaceTable describes the
configuration of the interfaces of this NHDP device. configuration of the interfaces of this NHDP router.
The ifIndex is from the interfaces group The ifIndex is from the interfaces group
defined in the Interfaces Group MIB. defined in the Interfaces Group MIB.
The object 'nhdpIfStatus' provides the functionality nhdpIfStatus provides the functionality
expected by the NHDP in the Local Interface Base (LIB) expected by the NHDP in the Local Interface Base (LIB)
Local Interface Set Table. Hence, the Local Interface Local Interface Set Table. Hence, the Local Interface
Set Table will not be defined below." Set Table will not be defined below.
The objects in this table are persistent and when
written the entity SHOULD save the change to
non-volatile storage."
REFERENCE REFERENCE
"RFC 2863 - The Interfaces Group MIB, McCloghrie, "RFC 2863 - The Interfaces Group MIB, McCloghrie,
K., and F. Kastenholtz, June 2000." K., and F. Kastenholtz, June 2000."
::= { nhdpConfigurationObjGrp 1 } ::= { nhdpConfigurationObjGrp 1 }
nhdpInterfaceEntry OBJECT-TYPE nhdpInterfaceEntry OBJECT-TYPE
SYNTAX NhdpInterfaceEntry SYNTAX NhdpInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NHDP interface entry describes one NHDP "nhdpInterfaceEntry describes one NHDP
local interface configuration as indexed by local interface configuration as indexed by
its ifIndex as defined in the Standard MIB II its ifIndex as defined in the Standard MIB II
Interface Table (RFC2863)." Interface Table (RFC2863)."
INDEX { nhdpIfIndex } INDEX { nhdpIfIndex }
::= { nhdpInterfaceTable 1 } ::= { nhdpInterfaceTable 1 }
NhdpInterfaceEntry ::= NhdpInterfaceEntry ::=
SEQUENCE { SEQUENCE {
nhdpIfIndex nhdpIfIndex
InterfaceIndexOrZero, InterfaceIndexOrZero,
skipping to change at page 23, line 48 skipping to change at page 23, line 8
Unsigned32, Unsigned32,
nhdpHelloMinInterval nhdpHelloMinInterval
Unsigned32, Unsigned32,
nhdpRefreshInterval nhdpRefreshInterval
Unsigned32, Unsigned32,
nhdpLHoldTime nhdpLHoldTime
Unsigned32, Unsigned32,
nhdpHHoldTime nhdpHHoldTime
Unsigned32, Unsigned32,
nhdpHystAcceptQuality nhdpHystAcceptQuality
Unsigned32, Float32,
nhdpHystRejectQuality nhdpHystRejectQuality
Unsigned32, Float32,
nhdpInitialQuality nhdpInitialQuality
Unsigned32, Float32,
nhdpInitialPending nhdpInitialPending
TruthValue, TruthValue,
nhdpHpMaxJitter nhdpHpMaxJitter
Unsigned32, Unsigned32,
nhdpHtMaxJitter nhdpHtMaxJitter
Unsigned32, Unsigned32,
nhdpIfRowStatus nhdpIfRowStatus
RowStatus RowStatus
} }
skipping to change at page 24, line 28 skipping to change at page 23, line 36
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex for this interface." "The ifIndex for this interface."
::= { nhdpInterfaceEntry 1 } ::= { nhdpInterfaceEntry 1 }
nhdpIfStatus OBJECT-TYPE nhdpIfStatus OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhpdIfStatus indicates whether this interface is "nhpdIfStatus indicates whether this interface is
a MANET interface. A value of true(1) indicates a MANET interface. A value of true(1) indicates
that the interface is a MANET interface. A value of that the interface is a MANET interface. A value of
false(2) indicates that the interface is not a MANET false(2) indicates that the interface is not a MANET
interface. This corresponds to the I_manet parameter interface. This corresponds to the I_manet parameter
in the Local Interface Set, which is omitted in this MIB in the Local Interface Set, which is omitted in this MIB
due to the redundancy with the nhdpInterfaceTable." due to the redundancy with the nhdpInterfaceTable."
DEFVAL { 2 } DEFVAL { 2 }
::= { nhdpInterfaceEntry 2 } ::= { nhdpInterfaceEntry 2 }
-- --
-- Interface Parameters - Message Intervals -- Interface Parameters - Message Intervals
-- --
nhdpHelloInterval OBJECT-TYPE nhdpHelloInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhpdHelloInterval is the maximum time "nhpdHelloInterval corresponds to
between the transmission of two successive HELLO_INTERVAL of NHDP.
HELLO messages on this MANET interface.
The following constraints apply to this The following constraint applies to this
parameter: parameter:
nhpdHelloInterval >= 0 nhpdHelloInterval > = nhdpHelloMinInterval"
nhpdHelloInterval >= nhdpHelloMinInterval"
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 2000 } DEFVAL { 2000 }
::= { nhdpInterfaceEntry 3 } ::= { nhdpInterfaceEntry 3 }
nhdpHelloMinInterval OBJECT-TYPE nhdpHelloMinInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhpdHelloMinInterval is the minimum interval "nhpdHelloMinInterval corresponds to
between transmission of two successive HELLO HELLO_MIN_INTERVAL of NHDP."
messages, on this MANET interface.
The following constraints apply to this
parameter:
nhdpHelloMinInterval >= 0"
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 500 } DEFVAL { 500 }
::= { nhdpInterfaceEntry 4 } ::= { nhdpInterfaceEntry 4 }
nhdpRefreshInterval OBJECT-TYPE nhdpRefreshInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhpdRefreshInterval is the maximum interval "nhpdRefreshInterval corresponds to
between advertisements, in a HELLO message on this REFRESH_INTERVAL of NHDP.
MANET interface, of each 1-hop neighbor network
address and its status.
The following constraint applies to this The following constraint applies to this
parameter: parameter:
nhdpRefreshInterval >= nhdpHelloInterval" nhdpRefreshInterval > = nhdpHelloInterval"
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 2000 } DEFVAL { 2000 }
::= { nhdpInterfaceEntry 5 } ::= { nhdpInterfaceEntry 5 }
-- --
-- Interface Parameters - Information Validity times -- Interface Parameters - Information Validity times
-- --
nhdpLHoldTime OBJECT-TYPE nhdpLHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpLHoldTime is used to define the time "nhdpLHoldTime corresponds to
for which a recently used and replaced L_HOLD_TIME of NHDP."
originator address is used to recognize
the router's own messages.
The following constraint applies to this
parameter:
nhdpLHoldTime >= 0"
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 6000 } DEFVAL { 6000 }
::= { nhdpInterfaceEntry 6 } ::= { nhdpInterfaceEntry 6 }
nhdpHHoldTime OBJECT-TYPE nhdpHHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpHHoldTime is used to define the time "nhdpHHoldTime corresponds to
for which a recently used and replaced H_HOLD_TIME of NHDP."
originator address is used to recognize
the router's own messages.
The following constraint applies to this
parameter:
nhdpHHoldTime >= 0"
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 6000 } DEFVAL { 6000 }
::= { nhdpInterfaceEntry 7 } ::= { nhdpInterfaceEntry 7 }
-- --
-- Interface Parameters - Link Quality -- Interface Parameters - Link Quality
-- (is optional and settings define operation) -- (is optional and settings define operation)
-- --
-- Note: Can we set a Float32 value here ranging
-- from 0.0 to 1.0?
nhdpHystAcceptQuality OBJECT-TYPE nhdpHystAcceptQuality OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Float32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpHystAcceptQuality is the "nhdpHystAcceptQuality corresponds to
link quality threshold at or above HYST_ACCEPT of NHDP.
which a link becomes usable,
if it was not already so.
The following constraint applies to this The following constraint applies to this
parameter: parameter:
0 < = nhdpHystRejectQuality 0 < = nhdpHystRejectQuality
< = nhdpHystAcceptQuality < = 255" < = nhdpHystAcceptQuality < = 1.0"
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 255 } -- DEFVAL { 1.0 }
::= { nhdpInterfaceEntry 8 } ::= { nhdpInterfaceEntry 8 }
nhdpHystRejectQuality OBJECT-TYPE nhdpHystRejectQuality OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Float32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpHystRejectQuality is the "nhdpHystRejectQuality corresponds to
link quality threshold below which HYST_REJECT of NHDP.
a link becomes unusable, if it
was not already so.
The following constraint applies to this The following constraint applies to this
parameter: parameter:
0 < = nhdpHystRejectQuality 0 < = nhdpHystRejectQuality
< = nhdpHystAcceptQuality < = 255" < = nhdpHystAcceptQuality < = 1.0"
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 0 } -- DEFVAL { 0.0 }
::= { nhdpInterfaceEntry 9 } ::= { nhdpInterfaceEntry 9 }
nhdpInitialQuality OBJECT-TYPE nhdpInitialQuality OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Float32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpInitialQuality is the "nhdpInitialQuality corresponds to
initial quality of a newly INITIAL_QUALITY of NHDP.
identified link.
The following constraint applies to this The following constraint applies to this
parameter: parameter:
0 < = nhdpInitialQuality < = 255" 0 < = nhdpInitialQuality < = 1.0"
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 255 } -- DEFVAL { 1.0 }
::= { nhdpInterfaceEntry 10 } ::= { nhdpInterfaceEntry 10 }
-- Note: Probably wnat to move this following object
-- `nhdpInitialPending' to the State Objects Group.
nhdpInitialPending OBJECT-TYPE nhdpInitialPending OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpInitialPending is defined as "nhdpInitialPending corresponds to
follows: INITIAL_PENDING of NHDP."
If true, then a newly identified link
is considered pending, and is not
usable until the link quality has
reached or exceeded the
nhdpHystAccept threshold."
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 2 } DEFVAL { 2 } -- i.e. false
::= { nhdpInterfaceEntry 11 } ::= { nhdpInterfaceEntry 11 }
-- --
-- Interface Parameters - Jitter -- Interface Parameters - Jitter
-- --
nhdpHpMaxJitter OBJECT-TYPE nhdpHpMaxJitter OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpHpMaxJitter represents the "nhdpHpMaxJitter corresponds to
value of MAXJITTER used in [4] for HP_MAXJITTER of NHDP."
periodically generated HELLO messages
on this MANET interface."
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 500 } DEFVAL { 500 }
::= { nhdpInterfaceEntry 12 } ::= { nhdpInterfaceEntry 12 }
nhdpHtMaxJitter OBJECT-TYPE nhdpHtMaxJitter OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpHtMaxJitter represents the "nhdpHtMaxJitter corresponds to
value of MAXJITTER used in [4] for HT_MAXJITTER of NHDP."
externally triggered HELLO messages
on this MANET interface."
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 500 } DEFVAL { 500 }
::= { nhdpInterfaceEntry 13 } ::= { nhdpInterfaceEntry 13 }
nhdpIfRowStatus OBJECT-TYPE nhdpIfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 30, line 13 skipping to change at page 28, line 30
this object has no effect on whether other this object has no effect on whether other
objects in this conceptual row can be objects in this conceptual row can be
modified." modified."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpInterfaceEntry 14 } ::= { nhdpInterfaceEntry 14 }
-- --
-- Router Parameters - Information Validity Time -- Router Parameters - Information Validity Time
-- --
nhdpNHoldTime OBJECT-TYPE nhdpNHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpHHoldTime is used as the period "nhdpNHoldTime corresponds to
during which former 1-hop neighbor N_HOLD_TIME of NHDP.
addresses are advertised as lost in
HELLO messages, allowing recipients of
these HELLO messages to accelerate removal
of information from their 2-Hop Sets.
N_HOLD_TIME can be set to zero if
accelerated information removal is not
required.
The following constraint applies to this This object is persistent and when written
parameter: the entity SHOULD save the change to
nhdpHHoldTime >= 0" non-volatile storage."
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 6000 } DEFVAL { 6000 }
::= { nhdpConfigurationObjGrp 2 } ::= { nhdpConfigurationObjGrp 2 }
nhdpIHoldTime OBJECT-TYPE nhdpIHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIHoldTime is the period "nhdpIHoldTime corresponds to
for which a recently used local I_HOLD_TIME of NHDP.
interface address is recorded.
The following constraint applies to this This object is persistent and when written
parameter: the entity SHOULD save the change to
nhdpIHoldTime >= 0 " non-volatile storage."
REFERENCE REFERENCE
"The NHDP draft. "The NHDP draft.
Section 5 on Protocol Parameters and Section 5 on Protocol Parameters and
Constraints." Constraints."
DEFVAL { 6000 } DEFVAL { 6000 }
::= { nhdpConfigurationObjGrp 3 } ::= { nhdpConfigurationObjGrp 3 }
-- --
-- nhdpStateObjGrp -- nhdpStateObjGrp
-- --
-- Contains information describing the current state of the NHDP -- Contains information describing the current state of the NHDP
-- process. -- process.
nhdpStateObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 2 } nhdpStateObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 2 }
-- Before building the NHDP Information Bases, we define -- Two new constructs have been defined in this MIB for
-- two new constructs for indexing into the following -- indexing into the following
-- tables and indexing into other tables in other MIBs. -- tables and indexing into other tables in other MIBs.
-- The NeighborIfIndex defines a unique (to the local router) -- The NeighborIfIndex defines a unique (to the local router)
-- index referencing a discovered interface on another -- index referencing a discovered interface on another
-- router within the NHDP MANET. The NeighborRouterId defines a -- router within the MANET. The NeighborRouterId defines a
-- unique (to the local router) index referencing a discovered -- unique (to the local router) index referencing a discovered
-- router within the NHDP MANET. -- router within the MANET.
-- Note: This table is indexed by an IpAddr associated with -- Note: This table is indexed by an IpAddr associated with
-- NeighborIfIndex. Multiple addresses can be associated -- NeighborIfIndex. Multiple addresses can be associated
-- with a given NeighborIfIndex. Each NeighborIfIndex is -- with a given NeighborIfIndex. Each NeighborIfIndex is
-- associated with a NeighborRouterId. Throughout this MIB, -- associated with a NeighborRouterId. Throughout this MIB,
-- the NeighborIfIndex and the NeighborRouterId are used -- the NeighborIfIndex and the NeighborRouterId are used
-- to define the set of IpAddrs related to the interface -- to define the set of IpAddrs related to the interface
-- in discussion. -- in discussion.
nhdpDiscIfSetTable OBJECT-TYPE nhdpDiscIfSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpDiscIfSetEntry SYNTAX SEQUENCE OF NhdpDiscIfSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's set of discovered interfaces on "A router's set of discovered interfaces on
neighboring routers." neighboring routers."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpStateObjGrp 1 } ::= { nhdpStateObjGrp 1 }
-- Note: need to describe how to age out
-- the entries in this table?
nhdpDiscIfSetEntry OBJECT-TYPE nhdpDiscIfSetEntry OBJECT-TYPE
SYNTAX NhdpDiscIfSetEntry SYNTAX NhdpDiscIfSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entries include the nhdpDiscRouterId of "The entries include the nhdpDiscRouterId of
the discovered router, the nhdpDiscIfIndex the discovered router, the nhdpDiscIfIndex
of the discovered interface and the of the discovered interface and the
current set of addresses associated current set of addresses associated
with this neighbor interface. The with this neighbor interface. The
nhdpDiscIfIndex has to uniquely identify nhdpDiscIfIndex has to uniquely identify
the remote interface address sets. It the remote interface address sets. It
need not be unique across the MANET. does not need to be unique across the MANET.
It must be unique within this router." It must be unique within this router."
REFERENCE REFERENCE
"This NHDP-MIB draft." "This NHDP-MIB draft."
INDEX { nhdpDiscIfSetIpAddr } INDEX { nhdpDiscIfSetIpAddr }
::= { nhdpDiscIfSetTable 1 } ::= { nhdpDiscIfSetTable 1 }
NhdpDiscIfSetEntry ::= NhdpDiscIfSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpDiscIfSetRouterId nhdpDiscIfSetRouterId
NeighborRouterId, NeighborRouterId,
skipping to change at page 34, line 19 skipping to change at page 32, line 19
before being compared to the value in the before being compared to the value in the
nhdpDiscIfSetAddr field. If the resulting nhdpDiscIfSetAddr field. If the resulting
address block is contained in a block in this address block is contained in a block in this
table, then a match should be returned." table, then a match should be returned."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpDiscIfSetEntry 5 } ::= { nhdpDiscIfSetEntry 5 }
-- An NHDP router's Local Information Base (LIB) -- An NHDP router's Local Information Base (LIB)
-- Local IF Set Table -- Note: Local IF Set Table is not specified in this
-- Entry (foreach IF): (IfAddrList, -- MIB because the table would be redundant with
-- PrefixMask, -- information in nhdpInterfaceTable.
-- Manet_indication)
--
-- Note: This table is redundant with information in
-- the nhdpInterfaceTable above. Hence it is not present here.
-- Removed Interface Addr Set Table -- Removed Interface Addr Set Table
-- Entry (foreach Addr): (IfAddrRemoved, -- Entry (foreach Addr): (IfAddrRemoved,
-- ExpirationTime) -- ExpirationTime)
nhdpLibRemovedIfAddrSetTable OBJECT-TYPE nhdpLibRemovedIfAddrSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpLibRemovedIfAddrSetEntry SYNTAX SEQUENCE OF NhdpLibRemovedIfAddrSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 35, line 17 skipping to change at page 33, line 13
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's Removed Interface Address Set consists "A router's Removed Interface Address Set consists
of Removed Interface Address Tuples, one per network of Removed Interface Address Tuples, one per network
address: address:
(IR_local_iface_addr, IR_time) (IR_local_iface_addr, IR_time)
The association between these addrs and The association between these addrs and
the router's Interface is found in the the router's Interface is found in the
Standard MIB II's IP addr table Standard MIB II's IP address table
(RFC1213)." (RFC1213)."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
INDEX { nhdpLibRemovedIfAddrSetIpAddr } INDEX { nhdpLibRemovedIfAddrSetIpAddr }
::= { nhdpLibRemovedIfAddrSetTable 1 } ::= { nhdpLibRemovedIfAddrSetTable 1 }
NhdpLibRemovedIfAddrSetEntry ::= NhdpLibRemovedIfAddrSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpLibRemovedIfAddrSetIpAddrType nhdpLibRemovedIfAddrSetIpAddrType
InetAddressType, InetAddressType,
nhdpLibRemovedIfAddrSetIpAddr nhdpLibRemovedIfAddrSetIpAddr
InetAddress, InetAddress,
nhdpLibRemovedIfAddrSetIpAddrPrefixLen nhdpLibRemovedIfAddrSetIpAddrPrefixLen
InetAddressPrefixLength, InetAddressPrefixLength,
nhdpLibRemovedIfAddrSetIfIndex nhdpLibRemovedIfAddrSetIfIndex
InterfaceIndexOrZero, InterfaceIndexOrZero,
nhdpLibRemovedIfAddrSetIrTime nhdpLibRemovedIfAddrSetIrTime
Unsigned32 TimeStamp
} }
nhdpLibRemovedIfAddrSetIpAddrType OBJECT-TYPE nhdpLibRemovedIfAddrSetIpAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the nhdpLibRemovedIfAddrSetIpAddr "The type of the nhdpLibRemovedIfAddrSetIpAddr
in the InetAddress MIB [RFC 4001]." in the InetAddress MIB [RFC 4001]."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpLibRemovedIfAddrSetEntry 1 } ::= { nhdpLibRemovedIfAddrSetEntry 1 }
nhdpLibRemovedIfAddrSetIpAddr OBJECT-TYPE nhdpLibRemovedIfAddrSetIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpLibRemovedIfAddrSetAddr is a "nhdpLibRemovedIfAddrSetAddr is a
recently used address of an interface of recently used address of an interface of
this router." this router."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpLibRemovedIfAddrSetEntry 2 } ::= { nhdpLibRemovedIfAddrSetEntry 2 }
nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of leading one bits that form the "Indicates the number of leading one bits that form the
mask to be logical-ANDed with the address mask to be logical-ANDed with the address
to determine the network address to which to determine the network address to which
this interface is attached. this interface is attached."
"
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpLibRemovedIfAddrSetEntry 3 } ::= { nhdpLibRemovedIfAddrSetEntry 3 }
-- Note: need to identify a time type for the
-- nhdpRemoveAddrSetIrTime.
nhdpLibRemovedIfAddrSetIfIndex OBJECT-TYPE nhdpLibRemovedIfAddrSetIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the local IfIndex from which this "Specifies the local IfIndex from which this
Ip addr was recently removed." IP address was recently removed."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpLibRemovedIfAddrSetEntry 4 } ::= { nhdpLibRemovedIfAddrSetEntry 4 }
nhdpLibRemovedIfAddrSetIrTime OBJECT-TYPE nhdpLibRemovedIfAddrSetIrTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies when this Tuple expires and MUST be removed "Specifies when this Tuple expires and MUST be removed
from this table." from this table."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpLibRemovedIfAddrSetEntry 5 } ::= { nhdpLibRemovedIfAddrSetEntry 5 }
-- Interface Information Base (IIB) -- Interface Information Base (IIB)
skipping to change at page 37, line 43 skipping to change at page 35, line 39
SYNTAX NhdpIibLinkSetEntry SYNTAX NhdpIibLinkSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Link Set consists of Link Tuples, each "A Link Set consists of Link Tuples, each
representing a single link indexed by the representing a single link indexed by the
local and remote interface pair: local and remote interface pair:
(L_neighbor_iface_addr_list, L_HEARD_time, (L_neighbor_iface_addr_list, L_HEARD_time,
L_SYM_time, L_quality, L_pending, L_SYM_time, L_quality, L_pending,
L_lost, L_time)." L_lost, L_time).
Note that L_quality is not included in the
entries below, because updates may be
required too frequently."
REFERENCE REFERENCE
"This NHDP-MIB draft." "This NHDP-MIB draft."
INDEX { nhdpIfIndex, INDEX { nhdpIfIndex,
nhdpIibLinkSet1HopIfIndex } nhdpIibLinkSet1HopIfIndex }
::= { nhdpIibLinkSetTable 1 } ::= { nhdpIibLinkSetTable 1 }
NhdpIibLinkSetEntry ::= NhdpIibLinkSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpIibLinkSet1HopIfIndex nhdpIibLinkSet1HopIfIndex
NeighborIfIndex, NeighborIfIndex,
nhdpIibLinkSetIfIndex nhdpIibLinkSetIfIndex
InterfaceIndexOrZero, InterfaceIndexOrZero,
nhdpIibLinkSetLHeardTime nhdpIibLinkSetLHeardTime
Unsigned32, TimeStamp,
nhdpIibLinkSetLSymTime nhdpIibLinkSetLSymTime
Unsigned32, TimeStamp,
nhdpIibLinkSetLQuality
Unsigned32,
nhdpIibLinkSetLPending nhdpIibLinkSetLPending
TruthValue, TruthValue,
nhdpIibLinkSetLLost nhdpIibLinkSetLLost
TruthValue, TruthValue,
nhdpIibLinkSetLTime nhdpIibLinkSetLTime
Unsigned32 TimeStamp
} }
nhdpIibLinkSet1HopIfIndex OBJECT-TYPE nhdpIibLinkSet1HopIfIndex OBJECT-TYPE
SYNTAX NeighborIfIndex SYNTAX NeighborIfIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIibLinkSet1HopIfIndex is "nhdpIibLinkSet1HopIfIndex is
the value of the NeighborIfIndex (from the value of the NeighborIfIndex (from
table nhdpDiscIfSetTable above). This nhdpDiscIfSetTable). This
object is repeated here to support object is repeated here to support
table walks to view the set of neighbors table walks to view the set of neighbors
of this router." of this router."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIibLinkSetEntry 1 } ::= { nhdpIibLinkSetEntry 1 }
nhdpIibLinkSetIfIndex OBJECT-TYPE nhdpIibLinkSetIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIibLinkSetIfIndex is "nhdpIibLinkSetIfIndex is
is the local router's interface is the local router's interface
index associated with the symmetric index associated with the symmetric
link to this entries neighbor link to this entries neighbor
interface. interface.
The IP addr set associated with this The set of IP addresses associated with
neighbor's interface is found in the this neighbor's interface is found in
'nhdpDiscIfSetTable' above." nhdpDiscIfSetTable."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIibLinkSetEntry 2 } ::= { nhdpIibLinkSetEntry 2 }
nhdpIibLinkSetLHeardTime OBJECT-TYPE nhdpIibLinkSetLHeardTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIibLinkSetLHeardTime is "nhdpIibLinkSetLHeardTime corresponds
the time until which the MANET to L_HEARD_time of NHDP."
interface of the 1-hop neighbor
would be considered heard if not
considering link quality."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIibLinkSetEntry 3 } ::= { nhdpIibLinkSetEntry 3 }
nhdpIibLinkSetLSymTime OBJECT-TYPE nhdpIibLinkSetLSymTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIibLinkSetLSymTime is the "nhdpIibLinkSetLSymTime corresponds
time until which the link to the to L_SYM_time of NHDP."
1-hop neighbor would be considered
symmetric if not considering link
quality."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIibLinkSetEntry 4 } ::= { nhdpIibLinkSetEntry 4 }
-- (Note: Is this wise to include in a MIB? What is the
-- frequency of updates or what are the requirements on
-- the frequency of updates to this parameter?)
nhdpIibLinkSetLQuality OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The nhdpIibLinkSetLQuality is a
dimensionless number between 0
(inclusive) and 1 (inclusive)
describing the quality of a link;
a greater value of L_quality
indicating a higher quality link."
REFERENCE
"The NHDP draft."
::= { nhdpIibLinkSetEntry 5 }
nhdpIibLinkSetLPending OBJECT-TYPE nhdpIibLinkSetLPending OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIibLinkSetLPending is a "nhdpIibLinkSetLPending corresponds
boolean flag, describing if a to L_pending of NHDP"
link is considered pending (i.e.,
a candidate, but not yet
established, link)."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIibLinkSetEntry 6 } ::= { nhdpIibLinkSetEntry 5 }
nhdpIibLinkSetLLost OBJECT-TYPE nhdpIibLinkSetLLost OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIibLinkSetLLost is a "nhdpIibLinkSetLLost corresponds
boolean flag, describing if a to L_lost of NHDP"
link is considered lost due
to link quality."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIibLinkSetEntry 7 } ::= { nhdpIibLinkSetEntry 6 }
-- Note: need to locate a time type for this object
nhdpIibLinkSetLTime OBJECT-TYPE nhdpIibLinkSetLTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIibLinkSetLTime specifies "nhdpIibLinkSetLTime specifies
when this Tuple expires and MUST when this Tuple expires and MUST
be removed. be removed."
"
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIibLinkSetEntry 8 } ::= { nhdpIibLinkSetEntry 7 }
-- --
-- IIB 2-Hop Set -- IIB 2-Hop Set
-- Entry (foreach IF on a 2-H neighbor): -- Entry (foreach IF on a 2-H neighbor):
-- (1NeighIfAddrList, -- (1NeighIfAddrList,
-- 2NeighIfAddr, -- 2NeighIfAddr,
-- ExpireTime) -- ExpireTime)
--
nhdpIib2HopSetTable OBJECT-TYPE nhdpIib2HopSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpIib2HopSetEntry SYNTAX SEQUENCE OF NhdpIib2HopSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A 2-Hop Set of an interface records network "A 2-Hop Set of an interface records network
addresses of symmetric 2-hop neighbors, and addresses of symmetric 2-hop neighbors, and
the symmetric links to symmetric 1-hop neighbors the symmetric links to symmetric 1-hop neighbors
through which these symmetric 2-hop neighbors through which these symmetric 2-hop neighbors
can be reached. It consists of 2-Hop Tuples, can be reached. It consists of 2-Hop Tuples,
skipping to change at page 41, line 34 skipping to change at page 38, line 44
N2_2hop_addr, N2_time)." N2_2hop_addr, N2_time)."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpStateObjGrp 4 } ::= { nhdpStateObjGrp 4 }
nhdpIib2HopSetEntry OBJECT-TYPE nhdpIib2HopSetEntry OBJECT-TYPE
SYNTAX NhdpIib2HopSetEntry SYNTAX NhdpIib2HopSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entries include the 2 hop neighbor addrs, "The entries include the 2-hop neighbor addresses,
which act as the table index, and associated which act as the table index, and associated
1 hop symmetric link addr set, designated through 1-hop symmetric link address set, designated
the nhdpDiscIfIndex, and an expiration time." through nhdpDiscIfIndex, and an expiration time."
REFERENCE REFERENCE
"This NHDP-MIB draft." "This NHDP-MIB draft."
INDEX { nhdpIib2HopSetIpAddress } INDEX { nhdpIib2HopSetIpAddress }
::= { nhdpIib2HopSetTable 1 } ::= { nhdpIib2HopSetTable 1 }
NhdpIib2HopSetEntry ::= NhdpIib2HopSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpIib2HopSetIpAddressType nhdpIib2HopSetIpAddressType
InetAddressType, InetAddressType,
nhdpIib2HopSetIpAddress nhdpIib2HopSetIpAddress
InetAddress, InetAddress,
nhdpIib2HopSet1HopIfIndex nhdpIib2HopSet1HopIfIndex
NeighborIfIndex, NeighborIfIndex,
nhdpIib2HopSetN2Time nhdpIib2HopSetN2Time
Unsigned32 TimeStamp
} }
nhdpIib2HopSetIpAddressType OBJECT-TYPE nhdpIib2HopSetIpAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the nhdpIib2HopSetIpAddress "The type of the nhdpIib2HopSetIpAddress
in the InetAddress MIB [RFC 4001]." in the InetAddress MIB [RFC 4001]."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIib2HopSetEntry 1 } ::= { nhdpIib2HopSetEntry 1 }
nhdpIib2HopSetIpAddress OBJECT-TYPE nhdpIib2HopSetIpAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIib2HopSetIpAddr is an "nhdpIib2HopSetIpAddr corresponds
address of an interface of a symmetric to N2_2hop_addr of NHDP."
2-hop neighbor which has a symmetric
link (using any MANET interface) to
the indicated symmetric 1-hop neighbor."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIib2HopSetEntry 2 } ::= { nhdpIib2HopSetEntry 2 }
nhdpIib2HopSet1HopIfIndex OBJECT-TYPE nhdpIib2HopSet1HopIfIndex OBJECT-TYPE
SYNTAX NeighborIfIndex SYNTAX NeighborIfIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIib2HopSet1HopIfIndex is "nhdpIib2HopSet1HopIfIndex is
NeighborIfIndex of the one hop NeighborIfIndex of the one hop
neighbor which communicated the ipAddress neighbor which communicated the ipAddress
of the 2 hop neighbor in this row entry." of the 2-hop neighbor in this row entry."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIib2HopSetEntry 3 } ::= { nhdpIib2HopSetEntry 3 }
-- Note: need to get a time type for this object.
nhdpIib2HopSetN2Time OBJECT-TYPE nhdpIib2HopSetN2Time OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpIib2HopSetN2Time specifies "nhdpIib2HopSetN2Time specifies
when this column entry expires and when this column entry expires and
MUST be removed." MUST be removed."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpIib2HopSetEntry 4 } ::= { nhdpIib2HopSetEntry 4 }
-- --
-- Neighbor Information Base (NIB) -- Neighbor Information Base (NIB)
-- --
-- Each router maintains a Neighbor Information Base -- Each router maintains a Neighbor Information Base
-- that records information about addresses of -- that records information about addresses of
-- current and recently symmetric 1-hop neighbors. -- current and recently symmetric 1-hop neighbors.
--
-- All addresses MUST have an associated prefix
-- length. Prefix lengths are indicated in HELLO
-- messages as specified in [1]; if an address
-- has no specified prefix length, then its prefix
-- length is equal to the address length. Two
-- addresses are considered equal if and only
-- if their associated prefix lengths are also equal.
-- NIB Neighbor Set -- NIB Neighbor Set
-- Entry (foreach 1-H Neighbor): -- Entry (foreach 1-H Neighbor):
-- (AllIfAddrListOfIhNeighbor, -- (AllIfAddrListOfIhNeighbor,
-- SymmetricIndicator) -- SymmetricIndicator)
-- The NIB Neighbor Set Table is small because -- The NIB Neighbor Set Table is small because
-- most of the corresponding information is found -- most of the corresponding information is found
-- in the nhdpDiscoveredIfTable above. -- in the nhdpDiscoveredIfTable above.
--
nhdpNibNeighborSetTable OBJECT-TYPE nhdpNibNeighborSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpNibNeighborSetEntry SYNTAX SEQUENCE OF NhdpNibNeighborSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's Neighbor Set records all network "A router's Neighbor Set records all network
addresses of each 1-hop neighbor." addresses of each 1-hop neighbor."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpStateObjGrp 5 } ::= { nhdpStateObjGrp 5 }
skipping to change at page 44, line 30 skipping to change at page 41, line 32
NeighborRouterId, NeighborRouterId,
nhdpNibNeighborSetNSymmetric nhdpNibNeighborSetNSymmetric
TruthValue TruthValue
} }
nhdpNibNeighborSetRouterId OBJECT-TYPE nhdpNibNeighborSetRouterId OBJECT-TYPE
SYNTAX NeighborRouterId SYNTAX NeighborRouterId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpNibNeighborSetRouterId is "nhdpNibNeighborSetRouterId is
the NeighborRouterId of a one hop the NeighborRouterId of a one hop
neighbor to this router. It must also neighbor to this router. It must also
exist in the 'nhdpDiscIfSetTable' exist in nhdpDiscIfSetTable,
allowing the manager to determine allowing the manager to determine
the set of Ip addr's associated the set of IP addresses associated
with the NeighborRouterId in this row." with NeighborRouterId in this row."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpNibNeighborSetEntry 1 } ::= { nhdpNibNeighborSetEntry 1 }
nhdpNibNeighborSetNSymmetric OBJECT-TYPE nhdpNibNeighborSetNSymmetric OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpNibNeighborNSymmetric is "nhdpNibNeighborNSymmetric corresponds
a boolean flag, describing if this to N_symmetric of NHDP."
is a symmetric 1-hop neighbor."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpNibNeighborSetEntry 2 } ::= { nhdpNibNeighborSetEntry 2 }
-- Lost Neighbor Set -- Lost Neighbor Set
-- Entry ( foreach IF foreach 1-H Neighbor): (IfAddr, -- Entry ( foreach IF foreach 1-H Neighbor): (IfAddr,
-- ExpireTime) -- ExpireTime)
--
nhdpNibLostNeighborSetTable OBJECT-TYPE nhdpNibLostNeighborSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpNibLostNeighborSetEntry SYNTAX SEQUENCE OF NhdpNibLostNeighborSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's Lost Neighbor Set records network "A router's Lost Neighbor Set records network
addresses of routers which recently were addresses of routers which recently were
symmetric 1-hop neighbors, but which are now symmetric 1-hop neighbors, but which are now
advertised as lost." advertised as lost."
REFERENCE REFERENCE
skipping to change at page 45, line 42 skipping to change at page 42, line 44
REFERENCE REFERENCE
"This NHDP-MIB draft." "This NHDP-MIB draft."
INDEX { nhdpNibLostNeighborSetRouterId } INDEX { nhdpNibLostNeighborSetRouterId }
::= { nhdpNibLostNeighborSetTable 1 } ::= { nhdpNibLostNeighborSetTable 1 }
NhdpNibLostNeighborSetEntry ::= NhdpNibLostNeighborSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpNibLostNeighborSetRouterId nhdpNibLostNeighborSetRouterId
NeighborRouterId, NeighborRouterId,
nhdpNibLostNeighborSetNLTime nhdpNibLostNeighborSetNLTime
Unsigned32 TimeStamp
} }
nhdpNibLostNeighborSetRouterId OBJECT-TYPE nhdpNibLostNeighborSetRouterId OBJECT-TYPE
SYNTAX NeighborRouterId SYNTAX NeighborRouterId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpNibLostNeighborSetRouterId is "nhdpNibLostNeighborSetRouterId is
the NeighborRouterId of a one hop the NeighborRouterId of a one hop
neighbor to this router which was neighbor to this router which was
recently lost. It must also recently lost. It must also
exist in the 'nhdpDiscIfSetTable' exist in nhdpDiscIfSetTable,
allowing the manager to determine allowing the manager to determine
the set of Ip addr's associated the set of IP addresses associated
with the NeighborRouterId in this row." with NeighborRouterId in this row."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpNibLostNeighborSetEntry 1 } ::= { nhdpNibLostNeighborSetEntry 1 }
-- Note: need to fime time type for this object
nhdpNibLostNeighborSetNLTime OBJECT-TYPE nhdpNibLostNeighborSetNLTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpNibLostNeighborSetNLTime "nhdpNibLostNeighborSetNLTime
specifies when this Tuple expires specifies when this Tuple expires
and MUST be removed." and MUST be removed."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpNibLostNeighborSetEntry 2 } ::= { nhdpNibLostNeighborSetEntry 2 }
-- --
-- nhdpPerformanceObjGrp -- nhdpPerformanceObjGrp
-- --
-- Contains objects which help to characterize the performance of -- Contains objects which help to characterize the performance of
-- the NHDP process, typically counters. -- the NHDP process, typically counters.
--
nhdpPerformanceObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 3 } nhdpPerformanceObjGrp OBJECT IDENTIFIER ::= { nhdpObjects 3 }
-- --
-- Objects per local interface -- Objects per local interface
-- --
nhdpInterfacePerfTable OBJECT-TYPE nhdpInterfacePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpInterfacePerfEntry SYNTAX SEQUENCE OF NhdpInterfacePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 49, line 13 skipping to change at page 46, line 16
DESCRIPTION DESCRIPTION
"A counter is incremented each time a periodic "A counter is incremented each time a periodic
HELLO message has been sent." HELLO message has been sent."
::= { nhdpInterfacePerfEntry 7 } ::= { nhdpInterfacePerfEntry 7 }
nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount OBJECT-TYPE nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter is incremented by the number of advertized "A counter is incremented by the number of advertised
symmetric neighbors in a HELLO each time a HELLO symmetric neighbors in a HELLO each time a HELLO
message has been sent." message has been sent."
::= { nhdpInterfacePerfEntry 8 } ::= { nhdpInterfacePerfEntry 8 }
nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount OBJECT-TYPE nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter is incremented by the number of advertized "A counter is incremented by the number of advertised
heard neighbors in a HELLO each time a HELLO heard neighbors in a HELLO each time a HELLO
message has been sent." message has been sent."
::= { nhdpInterfacePerfEntry 9 } ::= { nhdpInterfacePerfEntry 9 }
nhdpIfHelloMessageXmitAccumulatedLostNeighborCount OBJECT-TYPE nhdpIfHelloMessageXmitAccumulatedLostNeighborCount OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter is incremented by the number of advertized "A counter is incremented by the number of advertised
lost neighbors in a HELLO each time a HELLO lost neighbors in a HELLO each time a HELLO
message has been sent." message has been sent."
::= { nhdpInterfacePerfEntry 10 } ::= { nhdpInterfacePerfEntry 10 }
-- --
-- Objects per discovered neighbor interface -- Objects per discovered neighbor interface
-- --
nhdpDiscIfSetPerfTable OBJECT-TYPE nhdpDiscIfSetPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpDiscIfSetPerfEntry SYNTAX SEQUENCE OF NhdpDiscIfSetPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's set of performance properties for "A router's set of performance properties for
each discovered interface of a neighbor." each discovered interface of a neighbor."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpPerformanceObjGrp 2 } ::= { nhdpPerformanceObjGrp 2 }
skipping to change at page 50, line 48 skipping to change at page 47, line 50
REFERENCE REFERENCE
"This NHDP-MIB draft." "This NHDP-MIB draft."
::= { nhdpDiscIfSetPerfEntry 1 } ::= { nhdpDiscIfSetPerfEntry 1 }
nhdpDiscIfRecvdPackets OBJECT-TYPE nhdpDiscIfRecvdPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter increments each "This counter increments each
time this device receives a packet from that interface time this router receives a packet from that interface
of the neighbor." of the neighbor."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpDiscIfSetPerfEntry 2 } ::= { nhdpDiscIfSetPerfEntry 2 }
nhdpDiscIfExpectedPackets OBJECT-TYPE nhdpDiscIfExpectedPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter increments by the number "This counter increments by the number
of missed packets from this neighbor based of missed packets from this neighbor based
on the packet sequence number each time this on the packet sequence number each time this
device receives a packet from that interface router receives a packet from that interface
of the neighbor." of the neighbor."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpDiscIfSetPerfEntry 3 } ::= { nhdpDiscIfSetPerfEntry 3 }
-- --
-- Objects concerning the neighbor set -- Objects concerning the neighbor set
-- --
nhdpNibNeighborSetChanges OBJECT-TYPE nhdpNibNeighborSetChanges OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter increments each time the Neighbor Set changes. "This counter increments each time the Neighbor Set changes.
A change occurs whenever a new Neighbor Tuple has been A change occurs whenever a new Neighbor Tuple has been
added, a Neighbor Tuple has been removed or any entry of added, a Neighbor Tuple has been removed or any entry of
a Neighbor Tuple has been modified." a Neighbor Tuple has been modified."
::= { nhdpPerformanceObjGrp 3 } ::= { nhdpPerformanceObjGrp 3 }
skipping to change at page 52, line 46 skipping to change at page 49, line 46
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NHDP router ID (locally created) "The NHDP router ID (locally created)
of a neigboring router. Used for cross of a neigboring router. Used for cross
indexing into other NHDP tables and other indexing into other NHDP tables and other
MIBs." MIBs."
REFERENCE REFERENCE
"This NHDP-MIB draft." "This NHDP-MIB draft."
::= { nhdpDiscNeighborSetPerfEntry 1 } ::= { nhdpDiscNeighborSetPerfEntry 1 }
-- (Note: Can we point this to changes in a state grp
-- table below?)
nhdpDiscNeighborNibNeighborSetChanges OBJECT-TYPE nhdpDiscNeighborNibNeighborSetChanges OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter increments each time the neighbor becomes "This counter increments each time the neighbor becomes
onlink or offlink. A neighbor is said to become onlink or offlink. A neighbor is said to become
'onlink' if a new Neighbor Tuple is created that 'onlink' if a new nhdpNibNeighborSetEntry is created
corresponds to the given neighbor. It becomes 'offlink' for a particular nhdpNibNeighborSetRouterId. It becomes
if such a tuple has been deleted." 'offlink' if the entry for that neighbor has been deleted."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpDiscNeighborSetPerfEntry 2 } ::= { nhdpDiscNeighborSetPerfEntry 2 }
-- (Note: Can we point this to the time since an entry in a
-- table below has changed?)
nhdpDiscNeighborNibNeighborSetUpTime OBJECT-TYPE nhdpDiscNeighborNibNeighborSetUpTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object returns the time in milliseconds since "This object returns the time in milliseconds since
the neighbor becomes onlink or offlink. A neighbor is the neighbor becomes onlink or offlink. A neighbor is
said to become 'onlink' if a new Neighbor Tuple is created that said to become 'onlink' if a new nhdpNibNeighborSetEntry
corresponds to the given neighbor. It becomes 'offlink' if is created for a particular nhdpNibNeighborSetRouterId.
such a tuple has been deleted. It becomes 'offlink' if the entry for that neighbor
has been deleted.
Positive values indicate that the neighbor is currently Positive values indicate that the neighbor is currently
'onlink' and indicates the duration of the current 'onlink' 'onlink' and indicates the duration of the current 'onlink'
period. Negative values indicate that the neighbor is period. Negative values indicate that the neighbor is
currently 'offlink' and the magnitude indicates the currently 'offlink' and the magnitude indicates the
duration of the current 'offlink' period." duration of the current 'offlink' period."
REFERENCE REFERENCE
"This NHDP-MIB draft." "This NHDP-MIB draft."
::= { nhdpDiscNeighborSetPerfEntry 3 } ::= { nhdpDiscNeighborSetPerfEntry 3 }
skipping to change at page 54, line 4 skipping to change at page 50, line 46
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter increments each "This counter increments each
time the neighbor changes the interface over which it is time the neighbor changes the interface over which it is
reachable. That means that the corresponding Link Tuple of the reachable. That means that the corresponding Link Tuple of the
given link moves from the Link Set of one interface to another given link moves from the Link Set of one interface to another
interface." interface."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpDiscNeighborSetPerfEntry 4 } ::= { nhdpDiscNeighborSetPerfEntry 4 }
-- --
-- Objects per discovered 2-hop neighbor -- Objects per discovered 2-hop neighbor
-- --
nhdpIib2HopSetPerfTable OBJECT-TYPE
nhdpIib2HopSetPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpIib2HopSetPerfEntry SYNTAX SEQUENCE OF NhdpIib2HopSetPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains performance objects per "This table contains performance objects per
discovered 2-hop neighbor." discovered 2-hop neighbor."
REFERENCE REFERENCE
"The NHDP draft." "The NHDP draft."
::= { nhdpPerformanceObjGrp 5 } ::= { nhdpPerformanceObjGrp 5 }
skipping to change at page 55, line 37 skipping to change at page 52, line 34
corresponding to the given 2-hop neighbor IP address exists corresponding to the given 2-hop neighbor IP address exists
in the nhdpIib2HopSetTable." in the nhdpIib2HopSetTable."
REFERENCE REFERENCE
"This NHDP-MIB draft." "This NHDP-MIB draft."
::= { nhdpIib2HopSetPerfEntry 3 } ::= { nhdpIib2HopSetPerfEntry 3 }
-- --
-- nhdpNotifications -- nhdpNotifications
-- --
nhdpNotificationsGrp OBJECT IDENTIFIER ::= { nhdpObjects 4 } nhdpNotificationsControl OBJECT IDENTIFIER ::= { nhdpNotifications 1 }
nhdpNotificationsControl OBJECT IDENTIFIER ::= { nhdpObjects 5 } nhdpNotificationsObjects OBJECT IDENTIFIER ::= { nhdpNotifications 2 }
nhdpNotificationsStates OBJECT IDENTIFIER ::= { nhdpObjects 6 } nhdpNotificationsStates OBJECT IDENTIFIER ::= { nhdpNotifications 3 }
-- nhdpNotificationsControl
nhdpSetNotification OBJECT-TYPE nhdpSetNotification OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(4)) SYNTAX OCTET STRING (SIZE(4))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A 4-octet string serving as a bit map for "A 4-octet string serving as a bit map for
the notification events defined by the NHDP the notification events defined by the NHDP
notifications. This NHDP notifications where notifications. This object is used to enable
and disable specific NHDP notifications where
a 1 in the bit field represents enabled. The a 1 in the bit field represents enabled. The
right-most bit (leastsignificant) represents right-most bit (leastsignificant) represents
notification 0. notification 0.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage.
"
::= { nhdpNotificationsControl 1 } ::= { nhdpNotificationsControl 1 }
nhdpMessageSrc OBJECT-TYPE nhdpPacketSrc OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of an inbound message that "The IP address of an inbound packet that
cannot be identified by a neighbor instance. When cannot be identified by a neighbor instance. When
the last value of a notification using this object is the last value of a notification using this object is
needed, but no notifications of that type have been sent, needed, but no notifications of that type have been sent,
this value pertaining to this object should this value pertaining to this object should
be returned as 0.0.0.0 or :: respectively." be returned as 0.0.0.0 or :: respectively."
::= { nhdpNotificationsControl 2 } ::= { nhdpNotificationsControl 2 }
-- Notifications -- nhdpNotificationsObjects
-- Note: does this work when the neighbor goes down?
-- (there is no nhdpNibNeighborSetRouterId any more...)
nhdpNbrStateChange NOTIFICATION-TYPE nhdpNbrStateChange NOTIFICATION-TYPE
OBJECTS { nhdpDiscIfSetRouterId, -- The originator OBJECTS { nhdpDiscIfSetRouterId, -- The originator of
-- of the notification -- the notification.
nhdpNbrState -- The new state nhdpNbrState -- The new state
}
STATUS current
DESCRIPTION
"nhdpNbrStateChange is a notification sent when a
significant number of neighbors change their status
(i.e. down, asymmetric, or symmetric) in a short
time. The network administrator should select
appropriate values for 'significant number of
neighbors' and 'short time'."
::= { nhdpNotificationsObjects 1 }
nhdp2hopNbrStateChange NOTIFICATION-TYPE
OBJECTS { nhdpIib2HopSetIpAddress, -- The originator
-- of the notification
nhdp2hopNbrState -- The new state
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An nhdpNbrStateChange notification signifies that "nhdp2hopNbrStateChange is a notification sent
there has been a change in the state of a when a significant number of 2-hop neighbors
NHDP neighbor." change their status (i.e. up or down) in a short
::= { nhdpNotificationsGrp 1 } time. The network administrator should select
appropriate values for 'significant number of
neighbors' and 'short time'."
::= { nhdpNotificationsObjects 2 }
nhdpIfRxBadPacket NOTIFICATION-TYPE
OBJECTS { nhdpDiscIfSetRouterId, -- The originator of
-- the notification
nhdpDiscIfSetIndex, -- The interface on which the
-- packet has been received
nhdpPacketSrc -- The source IP address of the packet
}
STATUS current
DESCRIPTION
"nhdpIfRxBadPacket is a notification sent when a
significant number of incoming packets have not
been succesfully parsed in a short time. The
etwork administrator should select appropriate
values for 'significant number of neighbors'
and 'short time'."
::= { nhdpNotificationsObjects 3 }
nhdpIfStateChange NOTIFICATION-TYPE
OBJECTS { nhdpIfIndex, -- The local interface
nhdpIfState -- The new state
}
STATUS current
DESCRIPTION
"nhdpIfStateChange is a notification sent when
the status of an interface of this router has
changed (i.e. an IP address has been added or
removed to the interface, or the interface has
changed its status from up to down or vice versa)."
::= { nhdpNotificationsObjects 4 }
-- nhdpNotificationStates
nhdpNbrState OBJECT-TYPE nhdpNbrState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
down (0), down (0),
asymmetric (1), asymmetric (1),
symmetric(2) symmetric(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"NHDP neighbor states." "NHDP neighbor states."
DEFVAL { down } DEFVAL { down }
::= { nhdpNotificationsStates 1 } ::= { nhdpNotificationsStates 1 }
nhdp2hopNbrStateChange NOTIFICATION-TYPE
OBJECTS { nhdpIib2HopSetIpAddress, -- The originator
-- of the notification
nhdp2hopNbrState -- The new state
}
STATUS current
DESCRIPTION
"An nhdp2hopNbrStateChange notification signifies that
there has been a change in the state of a 2-hop
neighbor. This notification should be
generated when the 2-hop neighbor state goes
down or up."
::= { nhdpNotificationsGrp 2 }
nhdp2hopNbrState OBJECT-TYPE nhdp2hopNbrState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
down (0), down (0),
up (1) up (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"NHDP 2hop neighbor states." "NHDP 2hop neighbor states."
DEFVAL { down } DEFVAL { down }
::= { nhdpNotificationsStates 2 } ::= { nhdpNotificationsStates 2 }
nhdpIfRxBadMessage NOTIFICATION-TYPE
OBJECTS { nhdpDiscIfSetRouterId, -- The originator of
-- the notification
nhdpDiscIfSetIndex, -- The interface on which the
-- message has been received
nhdpMessageSrc -- The source IP address
}
STATUS current
DESCRIPTION
"An nhdpIfRxBadMessage notification signifies that a
HELLO message has been received on an
interface that cannot be parsed."
::= { nhdpNotificationsGrp 3 }
nhdpIfStateChange NOTIFICATION-TYPE
OBJECTS { nhdpIfIndex, -- The local interface
nhdpIfState -- The new state
}
STATUS current
DESCRIPTION
"An nhdpIfStateChange notification signifies that there
has been a change in the state of an NHDP
interface. This notification should be generated
when the interface goes up or down, or when
the list of addresses of that interface
changes."
::= { nhdpNotificationsGrp 4 }
nhdpIfState OBJECT-TYPE nhdpIfState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
down (0), down (0),
up (1), up (1),
addresschange(2) -- If a new address has been addresschange(2) -- If a new address has been
-- added or an address has -- added or an address has
-- been removed -- been removed
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"NHDP interface states." "NHDP interface states."
DEFVAL { down } DEFVAL { down }
::= { nhdpNotificationsStates 3 } ::= { nhdpNotificationsStates 3 }
-- --
-- nhdpConformance information -- nhdpConformance information
-- --
nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 } nhdpCompliances OBJECT IDENTIFIER ::= { nhdpConformance 1 }
nhdpMIBGroups OBJECT IDENTIFIER ::= { nhdpConformance 2 } nhdpMIBGroups OBJECT IDENTIFIER ::= { nhdpConformance 2 }
-- Compliance Statements -- Compliance Statements
nhdpBasicCompliance MODULE-COMPLIANCE nhdpBasicCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The basic implementation requirements for "The basic implementation requirements for
managed network entities that implement managed network entities that implement
NHDP." NHDP."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { nhdpConfigurationGroup } MANDATORY-GROUPS { nhdpConfigurationGroup }
skipping to change at page 60, line 27 skipping to change at page 57, line 30
nhdpDiscIfSetIndex, nhdpDiscIfSetIndex,
nhdpDiscIfSetIpAddrType, nhdpDiscIfSetIpAddrType,
nhdpDiscIfSetIpAddrPrefixLen, nhdpDiscIfSetIpAddrPrefixLen,
nhdpLibRemovedIfAddrSetIpAddrType, nhdpLibRemovedIfAddrSetIpAddrType,
nhdpLibRemovedIfAddrSetIpAddrPrefixLen, nhdpLibRemovedIfAddrSetIpAddrPrefixLen,
nhdpLibRemovedIfAddrSetIfIndex, nhdpLibRemovedIfAddrSetIfIndex,
nhdpLibRemovedIfAddrSetIrTime, nhdpLibRemovedIfAddrSetIrTime,
nhdpIibLinkSetIfIndex, nhdpIibLinkSetIfIndex,
nhdpIibLinkSetLHeardTime, nhdpIibLinkSetLHeardTime,
nhdpIibLinkSetLSymTime, nhdpIibLinkSetLSymTime,
nhdpIibLinkSetLQuality,
nhdpIibLinkSetLPending, nhdpIibLinkSetLPending,
nhdpIibLinkSetLLost, nhdpIibLinkSetLLost,
nhdpIibLinkSetLTime, nhdpIibLinkSetLTime,
nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddressType,
nhdpIib2HopSet1HopIfIndex, nhdpIib2HopSet1HopIfIndex,
nhdpIib2HopSetN2Time, nhdpIib2HopSetN2Time,
nhdpNibNeighborSetNSymmetric, nhdpNibNeighborSetNSymmetric,
nhdpNibLostNeighborSetNLTime nhdpNibLostNeighborSetNLTime
} }
STATUS current STATUS current
skipping to change at page 61, line 25 skipping to change at page 58, line 27
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of NHDP performance objects implemented "Set of NHDP performance objects implemented
in this module." in this module."
::= { nhdpMIBGroups 4 } ::= { nhdpMIBGroups 4 }
nhdpNotificationGroup NOTIFICATION-GROUP nhdpNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
nhdpNbrStateChange, nhdpNbrStateChange,
nhdp2hopNbrStateChange, nhdp2hopNbrStateChange,
nhdpIfRxBadMessage, nhdpIfRxBadPacket,
nhdpIfStateChange nhdpIfStateChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of NHDP notification objects implemented "Set of NHDP notification objects implemented
in this module." in this module."
::= { nhdpMIBGroups 5 } ::= { nhdpMIBGroups 5 }
END END
8. Security Considerations 8. Security Considerations
This MIB defines objects for the configuration, monitoring and This MIB defines objects for the configuration, monitoring and
notification of the Neighborhood Discovery Protocol (NHDP) [NHDP]. notification of the Neighborhood Discovery Protocol [NHDP]. NHDP
NHDP allows routers to acquire topological information up to two hops allows routers to acquire topological information up to two hops away
away by virtue of exchanging HELLO messages. The information by virtue of exchanging HELLO messages. The information acquired by
acquired by NHDP is used by other protocols, such as OLSRv2 [OLSRv2] NHDP may be used by routing protocols. The neighborhood information,
and SMF [SMF], and possibly other protocols. The neighborhood exchanged between routers using NHDP, serves these routing protocols
information, exchanged between routers using NHDP, serves these as a baseline for calculating paths to all destinations in the MANET,
routing protocols as a baseline for calculating paths to all relay set selection for network-wide transmissions etc.
destinations in the MANET, relay set selection for network-wide
transmissions etc.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o Specifically sensitive objects -
o nhdpIfStatus - this writable object turns on or off the NHDP o nhdpIfStatus - this writable object turns on or off the NHDP
process for the specified interface. If disabled, higher level process for the specified interface. If disabled, higher level
protocol functions, e.g., routing, would fail causing network-wide protocol functions, e.g., routing, would fail causing network-wide
disruptions. disruptions.
o nhdpHelloInterval, nhdpHelloMinInterval, and nhdpRefreshInterval - o nhdpHelloInterval, nhdpHelloMinInterval, and nhdpRefreshInterval -
these writable objects control the rate at which HELLO messages these writable objects control the rate at which HELLO messages
are sent on a wireless interface. If set at too high a rate, this are sent on a wireless interface. If set at too high a rate, this
could represent a form of DOS attack by overloading interface could represent a form of DOS attack by overloading interface
resources. resources.
o nhdpHystAcceptQuality, nhdpHystRejectQuality, nhdpInitialQuality, o nhdpHystAcceptQuality, nhdpHystRejectQuality, nhdpInitialQuality,
nhdpInitialPending - these writable objects affect the perceived nhdpInitialPending - these writable objects affect the perceived
quality of the HNDP links and hence the overall stability of the quality of the HNDP links and hence the overall stability of the
network. If improperly set, these settings could result in network. If improperly set, these settings could result in
network-wide disruptions. network-wide disruptions.
o The writable tables -
o nhdpInterfaceTable - this table contains writable objects that o nhdpInterfaceTable - this table contains writable objects that
affect the overall performance and stability of the NHDP process. affect the overall performance and stability of the NHDP process.
Failure of the NHDP process would result in network-wide failure. Failure of the NHDP process would result in network-wide failure.
Particularly sensitive objects from this table are discussed in Particularly sensitive objects from this table are discussed in
the previous list items. This is the only table in the NHDP-MIB the previous list items. This is the only table in the NHDP-MIB
with writable objects. with writable objects.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o nhdpDiscIfSetTable - The contains information on discovered o nhdpDiscIfSetTable - The contains information on discovered
neighbors, specifically their IP address in the neighbors,specifically their IP address in the nhdpDiscIfSetIpAddr
nhdpDiscIfSetIpAddr object. This information provides an object. This information provides an adversary broad information
adversary broad information on the members of the MANET, located on the members of the MANET, located within this single table.
within this single table. This information can be use to expedite This information can be use to expedite attacks on the other
attacks on the other members of the MANET without having to go members of the MANET without having to go through a laborious
through a laborious discovery process on their own. This object discovery process on their own. This object is the index into the
is the index into the table, and has a MAX-ACCESS of 'not- table, and has a MAX-ACCESS of 'not-accessible'. However, this
accessible'. However this information can be exposed using SNMP information can be exposed using SNMP operations.
operations.
MANET technology is often deployed to support communications of MANET technology is often deployed to support communications of
emergency services or military tactical applications. In these emergency services or military tactical applications. In these
applications, it is imperative to maintain the proper operation of applications, it is imperative to maintain the proper operation of
the communications network and to protect sensitive information the communications network and to protect sensitive information
related to its operation. Therefore, when implementing these related to its operation. Therefore, when implementing these
capabilities, the full use of SNMPv3 cryptographic machanisms for capabilities, the full use of SNMPv3 cryptographic mechanisms for
authentication and privacy is RECOMMENDED. authentication and privacy is RECOMMENDED.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB module. MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
skipping to change at page 63, line 40 skipping to change at page 60, line 34
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. IANA Considerations 9. IANA Considerations
This memo includes no request to IANA. This memo does not include any request to IANA.
10. Contributors 10. Contributors
This MIB document uses the template authored by D. Harrington which This MIB document uses the template authored by D. Harrington which
is based on contributions from the MIB Doctors, especially Juergen is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002. RFC 3418, December 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 64, line 28 skipping to change at page 61, line 20
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[NHDP] Clausen, T., Dearlove, C., and J. Dean, "The MANET [NHDP] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc
Neighborhood Discovery Protocol (NHDP)", Network (MANET) Neighborhood Discovery Protocol (NHDP)",
draft-ietf-manet-nhdp-11 (work in progress), October 2009. draft-ietf-manet-nhdp-12 (work in progress), March 2010.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
11.2. Informative References 11.2. Informative References
[REPORT] Cole, R., Macker, J., and A. Morton, "Definition of [REPORT] Cole, R., Macker, J., and A. Morton, "Definition of
Managed Objects for Performance Reporting", Managed Objects for Performance Reporting",
draft-cole-manet-report-mib-02 (work in progress), draft-ietf-manet-report-mib-00 (work in progress),
March 2010. July 2010.
[RFC5148] Clausen, T., Dearlove, C., and B. Adamson, "Jitter
Considerations in Mobile Ad Hoc Networks (MANETs)",
RFC 5148, February 2008.
[OLSRv2] Clausen, T., Dearlove, C., and P. Philippe, "The Optimized
Link State Routing Protocol version 2", work in
progress draft-ietf-manet-olsrv2-10.txt, September 2009.
[SMF] Macker, J., "Simplified Multicast Forwarding", work in [RFC4750] Joyal, D., Galecki, P., Giacalone, S., Coltun, R., and F.
progress draft-ietf-manet-smf-09.txt, July 2009. Baker, "OSPF Version 2 Management Information Base",
RFC 4750, December 2006.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC3781] Strauss, F. and J. Schoenwaelder, "Next Generation [RFC3781] Strauss, F. and J. Schoenwaelder, "Next Generation
Structure of Management Information (SMIng) Mappings to Structure of Management Information (SMIng) Mappings to
the Simple Network Management Protocol (SNMP)", RFC 3781, the Simple Network Management Protocol (SNMP)", RFC 3781,
May 2004. May 2004.
Appendix A. Change Log Appendix A. Change Log
Here we list the changes made to the various drafts of this MIB. Here we list the changes made to the various drafts of this MIB.
We list here the changes made on the draft-ietf-manet-nhdp-mib-03
draft to generate draft-ietf-manet-nhdp-mib-04.
1. Cleaned up and condensed text in the front material to this
draft. Specifically, shortened the Configuration and State Group
sections, defering to the MIB as definitive. Left the
Performance Group discussion primarily intact due to its
discussion of base and derived performance objects and statistics
and their value to management and operations of NHDP.
2. Added information identifying objects requiring non-volatile
storage within the DESCRIPTION clause of the objects within the
NHDP-MIB.
3. Updated to to NHDP draft version 12.
4. Changed type of several objects in the MIB (for timers, and
floating point values).
5. Removed link-quality object for performance reasons.
6. Fixed many small editorial issues.
7. Removed references to SMF- and OLSRv2-MIB.
We list here the changes made on the draft-ietf-manet-nhdp-mib-02 We list here the changes made on the draft-ietf-manet-nhdp-mib-02
draft to generate the draft-ietf-manet-nhdp-mib-03 draft. draft to generate the draft-ietf-manet-nhdp-mib-03 draft.
1. Cleaned up text in the Performance Group section defining the 1. Cleaned up text in the Performance Group section defining the
base versus the derived (from the REPORT-MIB) objects. base versus the derived (from the REPORT-MIB) objects.
2. Added the local nhdpIfIndex to the nhdpIibLinkSetTable. A duplex 2. Added the local nhdpIfIndex to the nhdpIibLinkSetTable. A duplex
of interface indecies is required to define a wireless link. of interface indecies is required to define a wireless link.
3. Added text to the Security Considerations section. 3. Added text to the Security Considerations section.
skipping to change at page 66, line 43 skipping to change at page 64, line 5
7. Aligned the NHDP-MIB and the OLSRv2-MIB configuration tables and 7. Aligned the NHDP-MIB and the OLSRv2-MIB configuration tables and
indexing. indexing.
Appendix B. Open Issues Appendix B. Open Issues
This section contains the set of open issues related to the This section contains the set of open issues related to the
development and design of the NHDP-MIB. This section will not be development and design of the NHDP-MIB. This section will not be
present in the final version of the MIB and will be removed once all present in the final version of the MIB and will be removed once all
the open issues have been resolved. the open issues have been resolved.
1. How to handle dynamic parameters within NHDP? Should we expose 1. Assure that once can set Float32 values to variables. If so, is
setting, min and max values? it possible to set upper and lower bounds (e.g. (0.0..1.0),
similar to Unsigned32)?
2. Identify all objects requiring non-volatile storage in their 2. Are DEFVALs required for NHDP parameters? How to specify
DESCRIPTION clauses. Float32 DEFVAL?
3. Incorporate parameter relationship conditions into their 3. Check out the definitions of the Notification Group and their
DESCRIPTION clauses. relationship within the subtree of the NHDP-MIB. Should we
specify thresholds for neighbor change Notifications? How do we
specify these?
4. Also, specify specific SNMP response to the snmp set request, 4. Need to check out the structure of the Notification Group and
i.e., 'generic error', 'bad value', etc. also its location within the NHDP-MIB (should be the zeroth
group).
5. Clean up all of the 'Note:' statements within the body of the 5. How to handle dynamic parameters within NHDP? Should we expose
MIB. setting, min and max values?
6. Work on the relationship to other MIBs, IF-MIB, REPORT-MIB, 6. Incorporate parameter relationship conditions into their
OLSRv2-MIB. DESCRIPTION clauses.
7. Cleanup all the [TODOs] from the MIB template. 7. Also, specify specific SNMP response to the snmp set request,
i.e., 'generic error', 'bad value', etc.
8. Clean up all of the 'Note:' statements within the body of the
MIB.
9. Work on the relationship to other MIBs, IF-MIB, REPORT-MIB.
10. Cleanup all the [TODOs] from the MIB template.
Appendix C. Appendix C.
*************************************************************** ***************************************************************
* Note to the RFC Editor (to be removed prior to publication) * * Note to the RFC Editor (to be removed prior to publication) *
* * * *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses * * 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be * * of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. * * assigned by the RFC Editor. *
* * * *
skipping to change at page 67, line 42 skipping to change at page 65, line 31
Ulrich Herberg Ulrich Herberg
LIX, Ecole Polytechnique LIX, Ecole Polytechnique
Palaiseau Cedex, 91128 Palaiseau Cedex, 91128
France France
EMail: ulrich@herberg.name EMail: ulrich@herberg.name
URI: http://www.herberg.name/ URI: http://www.herberg.name/
Robert G. Cole Robert G. Cole
Johns Hopkins University US Army CERDEC
3400 North Charles Street, NEB Room 213 328 Hopkins Road, Bldg 245
Baltimore, Maryland 21218 Aberdeen Proving Ground, Maryland 21005
USA USA
Phone: +1 443 910 4420 Phone: +1 410 278 6779
EMail: rgcole01@comcast.net EMail: robert.g.cole@us.army.mil
URI: http://www.cs.jhu.edu/~rgcole/ URI: http://www.cs.jhu.edu/~rgcole/
Ian D Chakeres Ian D Chakeres
CenGen CenGen
9250 Bendix Road North 9250 Bendix Road North
Columbia, Maryland 560093 Columbia, Maryland 560093
USA USA
EMail: ian.chakeres@gmail.com EMail: ian.chakeres@gmail.com
URI: http://www.ianchak.com/ URI: http://www.ianchak.com/
 End of changes. 224 change blocks. 
657 lines changed or deleted 536 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/