draft-ietf-manet-nhdp-mib-09.txt   draft-ietf-manet-nhdp-mib-10.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: January 29, 2012 US Army CERDEC Expires: March 9, 2012 US Army CERDEC
I. Chakeres I. Chakeres
CenGen CenGen
July 28, 2011 September 6, 2011
Definition of Managed Objects for the Neighborhood Discovery Protocol Definition of Managed Objects for the Neighborhood Discovery Protocol
draft-ietf-manet-nhdp-mib-09 draft-ietf-manet-nhdp-mib-10
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 parameters of the In particular, it describes objects for configuring parameters of the
Neighborhood Discovery Protocol (NHDP) process on a router. The MIB Neighborhood Discovery Protocol (NHDP) process on a router. The MIB
defined in this memo, denoted NHDP-MIB, also reports state, defined in this memo, denoted NHDP-MIB, also reports state,
performance information and notifications. This additional state and performance information and notifications. This additional state and
performance information is useful to troubleshoot problems and performance information is useful to troubleshoot problems and
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. 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."
This Internet-Draft will expire on January 29, 2012. This Internet-Draft will expire on March 9, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 2, line 28 skipping to change at page 2, line 28
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 4 5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 4
5.1.1. Introduction . . . . . . . . . . . . . . . . . . . . . 4 5.1.1. Introduction . . . . . . . . . . . . . . . . . . . . . 4
5.1.2. Notification Generation . . . . . . . . . . . . . . . 5 5.1.2. Notification Generation . . . . . . . . . . . . . . . 5
5.1.3. Limiting Frequency of Notifications . . . . . . . . . 5 5.1.3. Limiting Frequency of Notifications . . . . . . . . . 5
5.2. The Configuration Group . . . . . . . . . . . . . . . . . 5 5.2. The Configuration Group . . . . . . . . . . . . . . . . . 5
5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 6 5.3. The State Group . . . . . . . . . . . . . . . . . . . . . 6
5.4. The Performance Group . . . . . . . . . . . . . . . . . . 6 5.4. The Performance Group . . . . . . . . . . . . . . . . . . 6
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 15 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 15
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 15 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 15
6.2. Relationship to Routing Protocol MIBs relying on the 6.2. Relationship to Routing Protocol MIBs Relying on the
NHDP-MIB . . . . . . . . . . . . . . . . . . . . . . . . . 16 NHDP-MIB . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3. Relationship to the REPORT-MIB . . . . . . . . . . . . . . 16 6.3. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 16
6.4. MIB modules required for IMPORTS . . . . . . . . . . . . . 16
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 16
8. Security Considerations . . . . . . . . . . . . . . . . . . . 63 8. Security Considerations . . . . . . . . . . . . . . . . . . . 63
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 65 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 65
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 65
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65
12.1. Normative References . . . . . . . . . . . . . . . . . . . 65 12.1. Normative References . . . . . . . . . . . . . . . . . . . 65
12.2. Informative References . . . . . . . . . . . . . . . . . . 66 12.2. Informative References . . . . . . . . . . . . . . . . . . 66
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 66
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)
skipping to change at page 6, line 42 skipping to change at page 6, line 42
topology. These constructs are used to define indexes to the topology. These constructs are used to define indexes to the
appropriate State Group tables and to correlate table entries to appropriate State Group tables and to correlate table entries to
address sets, virtual neighbor interfaces and virtual neighbors address sets, virtual neighbor interfaces and virtual neighbors
within the MANET. within the MANET.
5.4. The Performance Group 5.4. 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 are explicitly defined in the NHDP-MIB and others which can be which are explicitly defined in the NHDP-MIB and others which can be
estimated through a combination of base objects from this MIB and estimated through a combination of base objects from this MIB.
reports available through the REPORT-MIB [REPORT]. Throughout this Throughout this section, those objects will be pointed out that are
section, those objects will be pointed out that are intended as base intended as base objects which are explicitly defined within this MIB
objects which are explicitly defined within this MIB and those and those objects which can be estimated.
objects which are estimated through a combination of the base objects
and capabilities offered by the REPORT-MIB.
Unstable neighbors or 2-hop neighbors and frequent changes of sets Unstable neighbors or 2-hop neighbors and frequent changes of sets
can have a negative influence on the performance of NHDP. The can have a negative influence on the performance of NHDP. The
following objects allow management applications to acquire following objects allow management applications to acquire
information related to the stability and performance of NHDP: information related to the stability and performance of NHDP:
The following objects return statistics related to HELLO messages: The following objects return statistics related to HELLO messages:
o Total number of sent HELLO messages on an interface o Total number of sent HELLO messages on an interface
skipping to change at page 8, line 5 skipping to change at page 7, line 48
o Acquire history of HELLO message scheduling instances for a 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 estimated from the REPORT-MIB. It is This is a Derived Object estimated from the NHDP-MIB. It is
derived from, e.g., the nhdpIfHelloMessagePeriodicXmits Base derived from, e.g., the nhdpIfHelloMessagePeriodicXmits Base
Object from the NHDP-MIB along with the capabilities derived Object from the NHDP-MIB.
from the reportHistoryGroup from the REPORT-MIB.
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.
The histogram would display the distribution of intervals The histogram would display the distribution of intervals
between two consecutive HELLOs using a given bin size. It between two consecutive HELLOs using a given bin size. It
includes all HELLOs that have been sent after the given time t0 includes all HELLOs that have been sent after the given time t0
and before the given time t1. and before the given time t1.
This is a Derived Object to be estimated from the REPORT-MIB. This is a Derived Object to be estimated from objects within
It can be estimated from, e.g., the the NHDP-MIB. It can be estimated from, e.g., the
nhdpIfHelloMessagePeriodicXmits Base Object from the NHDP-MIB nhdpIfHelloMessagePeriodicXmits Base Object from the NHDP-MIB.
along with the capabilities derived from the REPORT-MIB. The The network management application could convert this
network management application could convert this information information into the desired histogram.
into the desired histogram.
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 calculates the distances (e.g. histogram for each part and calculates the distances (e.g.
using the Bhattacharyya distance) between each two adjacent using the Bhattacharyya distance) between each two adjacent
histograms in time. A higher value between two histograms histograms in time. A higher value between two histograms
means more difference between the histograms. For instance, means more difference between the histograms. For instance,
this is representative of an event that suddenly sends many this is representative of an event that suddenly sends many
triggered HELLO messages, whereas before there have been only triggered HELLO messages, whereas before there have been only
very few such triggered messages. very few such triggered messages.
This is a Derived Object estimated from the REPORT-MIB, as This is a Derived Object estimated from objects within the
previously discussed, albeit this is a bit more complex with NHDP-MIB, as previously discussed, albeit this is a bit more
respect to the management application. complex with respect to the management application.
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
This is a Derived Object estimated from the reportSampledGroup This is a Derived Object estimated from, e.g., the
from the REPORT-MIB. It is derived from, e.g., the
nhdpIfHelloMessageXmits Base Object. nhdpIfHelloMessageXmits Base Object.
o Average number of received HELLO messages per second on an o Average number of received HELLO messages per second on an
interface between the given time t0 and t1 interface between the given time t0 and t1
This is a Derived Object estimated from the REPORT-MIB. See
the previous discussion. This is a Derived Object estimated from the NHDP-MIB. See the
previous discussion.
o Total accumulated size in octets of sent HELLO messages on an o Total accumulated size in octets of sent HELLO messages on an
interface interface
This is a Base Object. This is a Base Object.
Object name: nhdpIfHelloMessageXmitAccumulatedSize Object name: nhdpIfHelloMessageXmitAccumulatedSize
Object type: Counter64 Object type: Counter64
o Total accumulated size in octets of received HELLO messages on an o Total accumulated size in octets of received HELLO messages on an
interface interface
This is a Base Object. This is a Base Object.
skipping to change at page 9, line 28 skipping to change at page 9, line 22
This is a Base Object. This is a Base Object.
Object name: nhdpIfHelloMessageRecvdAccumulatedSize Object name: nhdpIfHelloMessageRecvdAccumulatedSize
Object type: Counter64 Object type: Counter64
o Average size in octets of sent HELLO messages between the given o Average size in octets of sent HELLO messages between the given
time t0 and t1 on an interface time t0 and t1 on an interface
This is a Derived Object estimated from the reportSampledGroup This is a Derived Object estimated from, e.g., the
from the REPORT-MIB. It is derived from, e.g., the
nhdpIfHelloMessageRecvdAccumulatedSize Base Object from this nhdpIfHelloMessageRecvdAccumulatedSize Base Object from this
NHDP-MIB. NHDP-MIB.
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 estimated from the REPORT-MIB. See This is a Derived Object estimated from the NHDP-MIB. See
previous discussion. previous discussion.
o Total accumulated number of advertised 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
skipping to change at page 11, line 16 skipping to change at page 11, line 10
Object name: nhdpNibNeighborSetChanges Object name: nhdpNibNeighborSetChanges
Object type: Counter32 Object type: Counter32
o Acquire history of Neighbor Set changes o Acquire history of Neighbor Set changes
This object returns the history of the exact timestamps of each This object returns the history of the exact timestamps of each
time the Neighbor Set has been changed. time the Neighbor Set has been changed.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from the NHDP-MIB. It is
derived from the previously discussed Base Object. derived from the previously discussed Base Object.
o Histogram of the intervals between Neighbor Set changes o Histogram of the intervals between Neighbor Set changes
Returns the values (in a 2-dimensional array) that represent a Returns the values (in a 2-dimensional array) that represent a
histogram of intervals between Neighbor Set changes. histogram of intervals between Neighbor Set changes.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from the previously
derived from the previously discussed Base Object. The network discussed Base Object.
management application would develop the histograms based upon
lists obtained from the REPORT-MIB.
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 calculates the distances (e.g. histogram for each part and calculates the distances (e.g.
using the Bhattacharyya distance) between each two adjacent using the Bhattacharyya distance) between each two adjacent
histograms in time. A higher value between two histograms histograms in time. A higher value between two histograms
means more difference between the histograms. means more difference between the histograms.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from the previously
derived from the previously discussed Base Object. The network discussed Base Object.
management application could then compute the desired metrics.
The next objects examine the uptime of a given neighbor (as listed in The next objects examine the uptime of a given neighbor (as listed in
the Neighbor Set): the Neighbor Set):
o Number of changes of a Neighbor Tuple o Number of changes of a Neighbor Tuple
Returns the number of changes to the given Neighbor Tuple. Returns the number of changes to the given Neighbor Tuple.
This is a Base Object. This is a Base Object.
skipping to change at page 12, line 32 skipping to change at page 12, line 23
This object returns the history of the exact timestamps of each This object returns the history of the exact timestamps of each
time the neighbor (as listed in the Neighbor Set) becomes time the neighbor (as listed in the Neighbor Set) becomes
'nbrup' or 'nbrdown'. A neighbor is said to become 'nbrup' if 'nbrup' or 'nbrdown'. A neighbor is said to become 'nbrup' if
a new Neighbor Tuple is created that corresponds to the given a new Neighbor Tuple is created that corresponds to the given
neighbor. It becomes 'nbrdown' if such a Neighbor Tuple has neighbor. It becomes 'nbrdown' if such a Neighbor Tuple has
been deleted. The existence of a Lost Neighbor Tuple for that been deleted. The existence of a Lost Neighbor Tuple for that
previous neighbor does not mean that the neighbor is still previous neighbor does not mean that the neighbor is still
'nbrup'. 'nbrup'.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from, e.g., the
derived from, e.g., the nhdpDiscNeighborNibNeighborSetChanges nhdpDiscNeighborNibNeighborSetChanges Base Object defined in
Base Object defined in this MIB. this MIB.
o Histogram of the intervals between a change of the 'nbrup' status o Histogram of the intervals between a change of the 'nbrup' status
of a given neighbor of a given neighbor
Returns the values that represent a histogram of intervals Returns the values that represent a histogram of intervals
between a change of the 'nbrup' status of a given neighbor. between a change of the 'nbrup' status of a given neighbor.
The 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. the given time t0 and before the given time t1.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from, e.g. the
derived from, e.g. the nhdpDiscNeighborNibNeighborSetChanges nhdpDiscNeighborNibNeighborSetChanges Base Object defined in
Base Object defined in this MIB. This object sits in the this MIB. This object sits in the nhdpDiscNeighborSetPerfTable
nhdpDiscNeighborSetPerfTable which is indexed by the which is indexed by the nhdpDiscRouterIndex.
nhdpDiscRouterIndex.
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(s) over which a given neighbor o Count the changes of the interface(s) over which a given neighbor
(as listed in the Neighbor Set) can be reached (as listed in the Neighbor Set) can be reached
This object counts each time the neighbor changes the This object counts each time the neighbor changes the
skipping to change at page 13, line 31 skipping to change at page 13, line 21
o Acquire history of changes of the interface(s) over which a given o Acquire history of changes of the interface(s) over which a given
neighbor can be reached neighbor can be reached
This object returns the history of the exact timestamps of each This object returns the history of the exact timestamps of each
time the neighbor changes the interface(s) over which it is time the neighbor changes the interface(s) over which it is
reachable. That means that there is a change in the set of reachable. That means that there is a change in the set of
corresponding Link Tuples of for that Neighbor Tuple, i.e. a corresponding Link Tuples of for that Neighbor Tuple, i.e. a
corresponding Link Tuple is added or removed from the set of corresponding Link Tuple is added or removed from the set of
all corresponding Link Tuples. all corresponding Link Tuples.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from, e.g., the
derived from, e.g., the
nhdpDiscNeighborNibNeighborSetReachableLinkChanges Base Object. nhdpDiscNeighborNibNeighborSetReachableLinkChanges Base Object.
The network management could develop the desired histogram
based upon the information retrieved from the REPORT-MIB.
o Histogram of the intervals between a change of the interface(s) o Histogram of the intervals between a change of the interface(s)
over which a given neighbor is reachable over 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 estimated from the REPORT-MIB. It is This is a Derived Object estimated from the previously
derived from the previously discussed Base Object, discussed Base Object, nhdpDiscNeighborNibNeighborSetChanges
nhdpDiscNeighborNibNeighborSetChanges counter. The network counter.
management application would develop the histograms based upon
lists obtained from the REPORT-MIB.
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 union of all N2_neighbor_iface_addr_list o Count the changes of the union of all N2_neighbor_iface_addr_list
of 2-hop Tuples with an N2_2hop_addr equal to one of the given of 2-hop Tuples with an N2_2hop_addr equal to one of the given
2-hop neighbor's addresses 2-hop neighbor's addresses
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 the neighbor(s) over which it is reachable. changes the neighbor(s) over which it is reachable.
skipping to change at page 14, line 16 skipping to change at page 14, line 4
o Count the changes of the union of all N2_neighbor_iface_addr_list o Count the changes of the union of all N2_neighbor_iface_addr_list
of 2-hop Tuples with an N2_2hop_addr equal to one of the given of 2-hop Tuples with an N2_2hop_addr equal to one of the given
2-hop neighbor's addresses 2-hop neighbor's addresses
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 the neighbor(s) over which it is reachable. changes the neighbor(s) over 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 given 2-hop 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 changes the neighbor(s) over which it time the 2-hop neighbor changes the neighbor(s) over which it
is reachable. is reachable.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from the previously
derived from the previously discussed Base Object, discussed Base Object, nhdpIib2HopSetPerfChanges counter.
nhdpIib2HopSetPerfChanges counter.
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 neighbor(s) over which the 2-hop between a change of the neighbor(s) over which the 2-hop
neighbor is reachable after the given time t0 and before the neighbor is reachable after the given time t0 and before the
given time t1. given time t1.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from the previously
derived from the previously discussed Base Object, discussed Base Object, nhdpIib2HopSetPerfChanges counter.
nhdpIib2HopSetPerfChanges counter. The network management
application would develop the histograms based upon lists
obtained from the REPORT-MIB.
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 hundredths of a second since the any Returns the number of hundredths of a second since the any
2-Hop Tuple with a N2_2hop_addr of the given 2-hop neighbor IP 2-Hop Tuple with a N2_2hop_addr of the given 2-hop neighbor IP
address was registered. address was registered.
This is a Base Object. This is a Base Object.
skipping to change at page 15, line 21 skipping to change at page 15, line 5
o Acquire history of change of 'nbrup' status of a given 2-hop o Acquire history of change of 'nbrup' 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 'nbrup' or 'nbrdown'. A 2-hop time the 2-hop neighbor becomes 'nbrup' or 'nbrdown'. A 2-hop
neighbor becomes 'nbrup' when the first 2-hop Tuple with neighbor becomes 'nbrup' when the first 2-hop Tuple with
N2_2hop_addr of the given 2-hop neighbor is created. It N2_2hop_addr of the given 2-hop neighbor is created. It
becomes 'nbrdown' when the last 2-hop Tuple with N2_2hop_addr becomes 'nbrdown' when the last 2-hop Tuple with N2_2hop_addr
of the given 2-hop neighbor has been deleted. of the given 2-hop neighbor has been deleted.
This is a Derived Object estimated from the REPORT-MIB. It is This is a Derived Object estimated from the previously
derived from the previously discussed Base Object, discussed Base Object, nhdpIib2HopSetPerfChanges counter.
nhdpIib2HopSetPerfChanges counter.
o Histogram of the intervals between a change of the 'nbrup' status o Histogram of the intervals between a change of the 'nbrup' 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 'nbrup' status of a given 2-hop between a change of the 'nbrup' 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 estimated from the REPORT-MIB. It is This is a Derived Object estimated from the previously
derived from the previously discussed Base Object, discussed Base Object, nhdpIib2HopSetPerfChanges counter.
nhdpIib2HopSetPerfChanges counter. The network management
application would develop the histograms based upon lists
obtained from the REPORT-MIB.
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. Relationship to Routing Protocol MIBs relying on the NHDP-MIB 6.2. Relationship to Routing Protocol MIBs Relying on the NHDP-MIB
[RFC6130] allows routing protocols to rely on the neighborhood [RFC6130] allows routing protocols to rely on the neighborhood
information that is discovered by means of HELLO message exchange. information that is discovered by means of HELLO message exchange.
In order to allow for troubleshooting, fault isolation, and In order to allow for troubleshooting, fault isolation, and
management of such routing protocols through a routing protocol MIB, management of such routing protocols through a routing protocol MIB,
it may be desired to align the State Group tables of the NHDP-MIB and it may be desired to align the State Group tables of the NHDP-MIB and
the routing protocol MIB. This is accomplished through the the routing protocol MIB. This is accomplished through the
definition of two TEXTUAL-CONVENTIONS in the NHDP-MIB: the definition of two TEXTUAL-CONVENTIONS in the NHDP-MIB: the
NeighborIfIndex and the NeighborRouterIndex. These object types are NeighborIfIndex and the NeighborRouterIndex. These object types are
used to develop indexes into common NHDP-MIB and routing protocol used to develop indexes into common NHDP-MIB and routing protocol
State Group tables. These objects are locally significant but should State Group tables. These objects are locally significant but should
be locally common to the NHDP-MIB and the routing protocol MIB be locally common to the NHDP-MIB and the routing protocol MIB
implemented on a common networked router. This will allow for implemented on a common networked router. This will allow for
improved cross referencing of information across the two MIBs. improved cross referencing of information across the two MIBs.
6.3. Relationship to the REPORT-MIB 6.3. MIB Modules Required for IMPORTS
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.4 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 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 FLOAT-TC-MIB [FLOATTC]. [RFC2863], INET-ADDRESS-MIB [RFC4001], and FLOAT-TC-MIB [RFC6340].
7. Definitions 7. Definitions
This section contains the MIB module defined by the specification. This section contains the MIB module defined by the specification.
NHDP-MIB DEFINITIONS ::= BEGIN NHDP-MIB DEFINITIONS ::= BEGIN
-- This MIB module defines objects for the management of the -- This MIB module defines objects for the management of the
-- NHDP [RFC6130] - The Neighborhood Discovery Protocol, -- NHDP [RFC6130] - The Neighborhood Discovery Protocol,
-- Clausen, T., Dearlove, C. and J. Dean, January 2011. -- Clausen, T., Dearlove, C. and J. Dean, January 2011.
skipping to change at page 17, line 27 skipping to change at page 16, line 43
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]
Float32TC Float32TC
FROM FLOAT-TC-MIB --[RFCXXXX] FROM FLOAT-TC-MIB --[RFC6340]
; ;
nhdpMIB MODULE-IDENTITY nhdpMIB MODULE-IDENTITY
LAST-UPDATED "201107281000Z" -- July 28, 2011 LAST-UPDATED "201109061000Z" -- September 6, 2011
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
skipping to change at page 18, line 24 skipping to change at page 17, line 39
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 routers "This NHDP-MIB module is applicable to routers
implementing the Neighborhood Discovery Protocol implementing the Neighborhood Discovery Protocol
defined in [RFC6130]. defined in [RFC6130].
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 RFCXXXX; see the RFC
itself for full legal notices." itself for full legal notices."
-- revision -- revision
REVISION "201109061000Z" -- September 6, 2011
DESCRIPTION
"The thirteenth version of this MIB module,
published as draft-ietf-manet-nhdp-mib-10.txt.
Removed references to the REPORT-MIB.
Added references to RFC 6340 for the
Float32TC Textual Convention.
"
REVISION "201107281000Z" -- July 28, 2011 REVISION "201107281000Z" -- July 28, 2011
DESCRIPTION DESCRIPTION
"The twelth version of this MIB module, "The twelth version of this MIB module,
published as draft-ietf-manet-nhdp-mib-09.txt. published as draft-ietf-manet-nhdp-mib-09.txt.
" "
REVISION "201107081000Z" -- July 8, 2011 REVISION "201107081000Z" -- July 8, 2011
DESCRIPTION DESCRIPTION
"The eleventh version of this MIB module, "The eleventh version of this MIB module,
published as draft-ietf-manet-nhdp-mib-08.txt. published as draft-ietf-manet-nhdp-mib-08.txt.
Clarified the use of the NeighborIfIndex and Clarified the use of the NeighborIfIndex and
skipping to change at page 21, line 23 skipping to change at page 20, line 47
entity." entity."
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
NeighborRouterIndex ::= TEXTUAL-CONVENTION NeighborRouterIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary, locally unique identifier associated with a "An arbitrary, locally unique identifier associated with a
virtual discovered neighbor (one or two hop). Due to the virtual discovered neighbor (one or two hop). Due to the
nature of the NHDP protocol, the local router may identify nature of the NHDP protocol, the local router may identify
multiple virtual neighbors which in fact are on and multiple virtual neighbors which in fact are one and
the same. Two hop neighbors with more than one advertised the same. Two hop neighbors with more than one advertised
address will exhibit this behavior. As the address will exhibit this behavior. As the
local router's knowledge of its neighbors' topology local router's knowledge of its neighbors' topology
increases, the local router will be able to associate increases, the local router will be able to associate
multiple virtual neighbor indexes into a single virtual multiple virtual neighbor indexes into a single virtual
neighbor index chosen from the set of aggregated indexes, neighbor index chosen from the set of aggregated indexes,
it must update all tables in this MIB indexed by these it must update all tables in this MIB indexed by these
indexes, and it can reuse the freed indexes following the indexes, and it can reuse the freed indexes following the
next agent re-initialization. next agent re-initialization.
skipping to change at page 30, line 6 skipping to change at page 29, line 30
-- Entry (foreach local interface): (IfNetAddrs, Is_manet) -- Entry (foreach local interface): (IfNetAddrs, Is_manet)
nhdpLibLocalIfSetTable OBJECT-TYPE nhdpLibLocalIfSetTable OBJECT-TYPE
SYNTAX SEQUENCE OF NhdpLibLocalIfSetEntry SYNTAX SEQUENCE OF NhdpLibLocalIfSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A router's Local Interface Set records all "A router's Local Interface Set records all
network addresses which are defined as local network addresses which are defined as local
interface network addresses. The local interface interface network addresses. The local interface
is defined by the nhdpLibLocalIfSetIfIndex. is defined by the nhdpIfIndex.
It consists of Local Interface Address Tuples It consists of Local Interface Address Tuples
per network interface and their prefix lengths (in per network interface and their prefix lengths (in
order to determine the network addresses related to order to determine the network addresses related to
the interface) and an indication of whether the the interface) and an indication of whether the
interface is a MANET interface or not. interface is a MANET interface or not.
Further guidance on the addition or removal of Further guidance on the addition or removal of
local addresses and network addresses is found local addresses and network addresses is found
in Section 9 of [RFC6130]." in Section 9 of [RFC6130]."
skipping to change at page 33, line 13 skipping to change at page 32, line 40
nhdpLibRemovedIfAddrSetIpAddrPrefixLen nhdpLibRemovedIfAddrSetIpAddrPrefixLen
InetAddressPrefixLength, InetAddressPrefixLength,
nhdpLibRemovedIfAddrSetIfIndex nhdpLibRemovedIfAddrSetIfIndex
InterfaceIndexOrZero, InterfaceIndexOrZero,
nhdpLibRemovedIfAddrSetIrTime nhdpLibRemovedIfAddrSetIrTime
TimeStamp TimeStamp
} }
nhdpLibRemovedIfAddrSetIpAddrType OBJECT-TYPE nhdpLibRemovedIfAddrSetIpAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the nhdpLibRemovedIfAddrSetIpAddr "The type of the nhdpLibRemovedIfAddrSetIpAddr
in the InetAddress MIB [RFC4001]." in the InetAddress MIB [RFC4001]."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
::= { nhdpLibRemovedIfAddrSetEntry 1 } ::= { nhdpLibRemovedIfAddrSetEntry 1 }
nhdpLibRemovedIfAddrSetIpAddr OBJECT-TYPE nhdpLibRemovedIfAddrSetIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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
"[RFC6130]." "[RFC6130]."
::= { nhdpLibRemovedIfAddrSetEntry 2 } ::= { nhdpLibRemovedIfAddrSetEntry 2 }
nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE nhdpLibRemovedIfAddrSetIpAddrPrefixLen OBJECT-TYPE
skipping to change at page 37, line 15 skipping to change at page 36, line 36
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 uniquely identifies nhdpDiscIfIndex uniquely identifies
the remote interface address sets the remote interface address sets
through this table. It does not need through this table. It does not need
to be unique across the MANET, but must to be unique across the MANET, but must
be locally unique within this router." be locally unique within this router."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
INDEX { nhdpDiscRouterIndex, INDEX { nhdpDiscIfSetIndex }
nhdpDiscIfIndex }
::= { nhdpDiscIfSetTable 1 } ::= { nhdpDiscIfSetTable 1 }
NhdpDiscIfSetEntry ::= NhdpDiscIfSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpDiscRouterIndex nhdpDiscIfSetIndex
NeighborRouterIndex, Integer32,
nhdpDiscIfIndex nhdpDiscIfIndex
NeighborIfIndex, NeighborIfIndex,
nhdpDiscRouterIndex
NeighborRouterIndex,
nhdpDiscIfSetIpAddrType nhdpDiscIfSetIpAddrType
InetAddressType, InetAddressType,
nhdpDiscIfSetIpAddr nhdpDiscIfSetIpAddr
InetAddress, InetAddress,
nhdpDiscIfSetIpAddrPrefixLen nhdpDiscIfSetIpAddrPrefixLen
InetAddressPrefixLength InetAddressPrefixLength
} }
nhdpDiscRouterIndex OBJECT-TYPE nhdpDiscIfSetIndex OBJECT-TYPE
SYNTAX NeighborRouterIndex SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NHDP neighbor index (locally created) "The index for this table. Necessary
of a neighboring router. Used for cross because multiple addresses may be associated
indexing into other NHDP tables and other with a given nhdpDiscIfIndex."
MIBs."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
::= { nhdpDiscIfSetEntry 1 } ::= { nhdpDiscIfSetEntry 1 }
nhdpDiscIfIndex OBJECT-TYPE nhdpDiscIfIndex OBJECT-TYPE
SYNTAX NeighborIfIndex SYNTAX NeighborIfIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NHDP interface index (locally created) "The NHDP interface index (locally created)
of a neighbor's interface. Used for cross of a neighbor's interface. Used for cross
indexing into other NHDP tables and other indexing into other NHDP tables and other
MIBs." MIBs."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
::= { nhdpDiscIfSetEntry 2 } ::= { nhdpDiscIfSetEntry 2 }
nhdpDiscRouterIndex OBJECT-TYPE
SYNTAX NeighborRouterIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NHDP neighbor index (locally created)
of a neighboring router. Used for cross
indexing into other NHDP tables and other
MIBs."
REFERENCE
"[RFC6130]."
::= { nhdpDiscIfSetEntry 3 }
nhdpDiscIfSetIpAddrType OBJECT-TYPE nhdpDiscIfSetIpAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the nhdpDiscIfSetIpAddr "The type of the nhdpDiscIfSetIpAddr
in the InetAddress MIB [RFC4001]." in the InetAddress MIB [RFC4001]."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
::= { nhdpDiscIfSetEntry 3 } ::= { nhdpDiscIfSetEntry 4 }
nhdpDiscIfSetIpAddr OBJECT-TYPE nhdpDiscIfSetIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The nhdpDiscIfSetIpAddr is a "The nhdpDiscIfSetIpAddr is a
recently used address of a neighbor recently used address of a neighbor
of this router." of this router."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
::= { nhdpDiscIfSetEntry 4 } ::= { nhdpDiscIfSetEntry 5 }
nhdpDiscIfSetIpAddrPrefixLen OBJECT-TYPE nhdpDiscIfSetIpAddrPrefixLen 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 "Indicates the number of leading one bits that
form the mask. The mask is logically-ANDed form the mask. The mask is logically-ANDed
to the nhdpDiscIfSetIpAddr to determine to the nhdpDiscIfSetIpAddr to determine
the address prefix. A row match is true the address prefix. A row match is true
if the address used as an index falls within if the address used as an index falls within
the network address range defined by the the network address range defined by the
address prefix." address prefix."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
::= { nhdpDiscIfSetEntry 5 } ::= { nhdpDiscIfSetEntry 6 }
-- Interface Information Base (IIB) -- Interface Information Base (IIB)
-- --
-- NHDP Interface Information Base (IIB) -- NHDP Interface Information Base (IIB)
-- --
-- IIB Link Set -- IIB Link Set
-- Entry (foreach discovered link to a -- Entry (foreach discovered link to a
-- 1-H neighbor): (NeighborIfAddrList, -- 1-H neighbor): (NeighborIfAddrList,
-- HeardTime, -- HeardTime,
-- SymTime, -- SymTime,
-- Quality, -- Quality,
skipping to change at page 42, line 15 skipping to change at page 41, line 49
::= { nhdpStateObjGrp 5 } ::= { nhdpStateObjGrp 5 }
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 addresses, "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 address set, designated 1-hop symmetric link address set, designated
through nhdpDiscIfIndex, and an expiration time." through nhdpDiscIfIndex, and an expiration time.
The nhdpIfIndex in the INDEX is
interface index of the local interface
through which these 2-hop addresses are
accessible."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
INDEX { nhdpIib2HopSetIpAddressType, INDEX { nhdpIfIndex,
nhdpIib2HopSetIpAddressType,
nhdpIib2HopSetIpAddress } nhdpIib2HopSetIpAddress }
::= { nhdpIib2HopSetTable 1 } ::= { nhdpIib2HopSetTable 1 }
NhdpIib2HopSetEntry ::= NhdpIib2HopSetEntry ::=
SEQUENCE { SEQUENCE {
nhdpIib2HopSetIpAddressType nhdpIib2HopSetIpAddressType
InetAddressType, InetAddressType,
nhdpIib2HopSetIpAddress nhdpIib2HopSetIpAddress
InetAddress, InetAddress,
nhdpIib2HopSetIpAddrPrefixLen nhdpIib2HopSetIpAddrPrefixLen
skipping to change at page 43, line 31 skipping to change at page 43, line 24
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
::= { nhdpIib2HopSetEntry 3 } ::= { nhdpIib2HopSetEntry 3 }
nhdpIib2HopSet1HopIfIndex OBJECT-TYPE nhdpIib2HopSet1HopIfIndex OBJECT-TYPE
SYNTAX NeighborIfIndex SYNTAX NeighborIfIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"nhdpIib2HopSet1HopIfIndex is "nhdpIib2HopSet1HopIfIndex is
nhdpDiscIfIndex of the one hop nhdpDiscIfIndex of the 1-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
"[RFC6130]." "[RFC6130]."
::= { nhdpIib2HopSetEntry 4 } ::= { nhdpIib2HopSetEntry 4 }
nhdpIib2HopSetN2Time OBJECT-TYPE nhdpIib2HopSetN2Time OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 44, line 11 skipping to change at page 44, line 6
::= { nhdpIib2HopSetEntry 5 } ::= { nhdpIib2HopSetEntry 5 }
-- --
-- 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.
-- NIB Neighbor Set -- NIB Neighbor Set
-- Entry (foreach discovered 1-Hop neighbor: -- Entry (foreach discovered 1-hop neighbor:
-- N_neighbor_addr_list, N_symmetric) -- N_neighbor_addr_list, N_symmetric)
-- 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
skipping to change at page 53, line 35 skipping to change at page 53, line 27
nhdpIib2HopSetPerfUpTime nhdpIib2HopSetPerfUpTime
TimeTicks TimeTicks
} }
nhdpIib2HopSetPerfChanges OBJECT-TYPE nhdpIib2HopSetPerfChanges OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the changes of the union of all "This object counts the changes of the union of all
N2_neighbor_iface_addr_list of 2-hop Tuples with an N2_neighbor_iface_addr_list of 2-Hop Tuples with an
N2_2hop_addr equal to one of the given 2-hop N2_2hop_addr equal to one of the given 2-hop
neighbor's addresses." neighbor's addresses."
REFERENCE REFERENCE
"[RFC6130]." "[RFC6130]."
::= { nhdpIib2HopSetPerfEntry 1 } ::= { nhdpIib2HopSetPerfEntry 1 }
nhdpIib2HopSetPerfUpTime OBJECT-TYPE nhdpIib2HopSetPerfUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 58, line 35 skipping to change at page 58, line 28
::= { nhdpNotificationsStates 1 } ::= { nhdpNotificationsStates 1 }
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 2-hop neighbor states."
DEFVAL { down } DEFVAL { down }
::= { nhdpNotificationsStates 2 } ::= { nhdpNotificationsStates 2 }
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
skipping to change at page 61, line 4 skipping to change at page 60, line 41
nhdpInitialPending, nhdpInitialPending,
nhdpHpMaxJitter, nhdpHpMaxJitter,
nhdpHtMaxJitter, nhdpHtMaxJitter,
nhdpNHoldTime, nhdpNHoldTime,
nhdpIHoldTime, nhdpIHoldTime,
nhdpIfRowStatus, nhdpIfRowStatus,
nhdpLibLocalIfSetIpAddrType, nhdpLibLocalIfSetIpAddrType,
nhdpLibLocalIfSetIpAddr, nhdpLibLocalIfSetIpAddr,
nhdpLibLocalIfSetIpAddrPrefixLen, nhdpLibLocalIfSetIpAddrPrefixLen,
nhdpLibLocalIfSetIsManet, nhdpLibLocalIfSetIsManet,
nhdpLibRemovedIfAddrSetIpAddrType,
nhdpLibRemovedIfAddrSetIpAddr,
nhdpLibRemovedIfAddrSetIpAddrPrefixLen, nhdpLibRemovedIfAddrSetIpAddrPrefixLen,
nhdpLibRemovedIfAddrSetIfIndex, nhdpLibRemovedIfAddrSetIfIndex,
nhdpLibRemovedIfAddrSetIrTime nhdpLibRemovedIfAddrSetIrTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of NHDP configuration objects implemented "Set of NHDP configuration objects implemented
in this module." in this module."
::= { nhdpMIBGroups 2 } ::= { nhdpMIBGroups 2 }
skipping to change at page 65, line 32 skipping to change at page 65, line 24
11. Acknowledgements 11. Acknowledgements
The authors wish to thank Thomas Clausen and Justin Dean for their The authors wish to thank Thomas Clausen and Justin Dean for their
detailed reviews and insightful comments to this document. detailed reviews and insightful comments to this document.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
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.
[RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Network (MANET) Neighborhood Discovery Protocol (NHDP)", MIB", RFC 2863, June 2000.
RFC 6130, April 2011.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
[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.
[FLOATTC] Presuhn, R., "Textual Conventions for the Representation [RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc
of Floating-Point Numbers", work in Network (MANET) Neighborhood Discovery Protocol (NHDP)",
progress draft-ietf-opsawg-mibs-floats-02.txt, June 2011. RFC 6130, April 2011.
[RFC6340] Presuhn, R., "Textual Conventions for the Representation
of Floating-Point Numbers", RFC 6340, August 2011.
12.2. Informative References 12.2. Informative References
[REPORT] Cole, R., Macker, J., and A. Morton, "Definition of [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Managed Objects for Performance Reporting", "Introduction and Applicability Statements for Internet-
draft-ietf-manet-report-mib-01 (work in progress), Standard Management Framework", RFC 3410, December 2002.
February 2011.
[RFC4750] Joyal, D., Galecki, P., Giacalone, S., Coltun, R., and F. [RFC4750] Joyal, D., Galecki, P., Giacalone, S., Coltun, R., and F.
Baker, "OSPF Version 2 Management Information Base", Baker, "OSPF Version 2 Management Information Base",
RFC 4750, December 2006. RFC 4750, December 2006.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
Appendix A. Appendix A.
*************************************************************** ***************************************************************
* 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 * * 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. *
* * * *
* 2) The reference to RFCXXX2 throughout this document point *
* to the current draft-ietf-manet-nhdp-mib-xx.txt. This *
* need to be replaced with the XXX RFC number. *
* *
*************************************************************** ***************************************************************
Authors' Addresses Authors' Addresses
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
 End of changes. 65 change blocks. 
146 lines changed or deleted 129 lines changed or added

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