NHDP-MIB: View SNMP OID List / Download MIB

This NHDP-MIB module is applicable to routers implementing the Neighborhood Discovery Protocol defined in RFC 6130. Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 6779; see the RFC itself for full legal notices.

nhdpNbrStateChange is a notification sent when more than nhdpNbrStateChangeThreshold neighbors change their status (i.e., 'down(0)', 'asymmetric(1)', or 'symmetric(2)') within a time window of nhdpNbrStateChangeWindow.

nhdp2HopNbrStateChange is a notification sent when more than nhdp2HopNbrStateChangeThreshold 2-hop neighbors change their status (i.e., 'down(0)' or 'up(1)') within a time window of nhdp2HopNbrStateChangeWindow.

nhdpIfStateChange is a notification sent when nhdpIfStatus has changed on this interface.

A threshold value for the nhdpNbrStateChange object. If the number of occurrences exceeds this threshold within the previous nhdpNbrStateChangeWindow, then the nhdpNbrStateChange notification is to be sent. It is recommended that the value of this threshold be set to at least 10 and higher in dense topologies with frequent expected topology changes.

A time window for the nhdpNbrStateChange object. If the number of occurrences exceeds the nhdpNbrStateChangeThreshold within the previous nhdpNbrStateChangeWindow, then the nhdpNbrStateChange notification is to be sent. It is recommended that the value for this window be set to at least 5 times the nhdpHelloInterval. This object represents the time in hundredths of a second.

A threshold value for the nhdp2HopNbrStateChange object. If the number of occurrences exceeds this threshold within the previous nhdp2HopNbrStateChangeWindow, then the nhdp2HopNbrStateChange notification is to be sent. It is recommended that the value of this threshold be set to at least 10 and higher when topologies are expected to be highly dynamic.

A time window for the nhdp2HopNbrStateChange object. If the number of occurrences exceeds the nhdp2HopNbrStateChangeThreshold within the previous nhdp2HopNbrStateChangeWindow, then the nhdp2HopNbrStateChange notification is to be sent. It is recommended that the value for this window be set to at least 5 times nhdpHelloInterval. This object represents the time in hundredths of a second.

NHDP neighbor states. In NHDP, it is not necessary to remove Protocol Tuples from Protocol Sets at the exact time indicated, only to behave as if the Protocol Tuples were removed at that time. This case is indicated here as 'down(0)', all other cases being indicated as 'asymmetric(1)' or 'symmetric(2)'. If 'down(0)', the direct neighbor is also added to the nhdpNibLostNeighborSetTable. Enumeration: 'down': 0, 'asymmetric': 1, 'symmetric': 2.

NHDP 2-hop neighbor states. In NHDP, it is not necessary to remove Protocol Tuples from Protocol Sets at the exact time indicated, only to behave as if the Protocol Tuples were removed at that time. This case is indicated here as 'down(0)'; otherwise, it is 'up(1)'. Enumeration: 'down': 0, 'up': 1.

The nhdpInterfaceTable describes the configuration of the interfaces of this router that are intended to use MANET control protocols. As such, this table 'sparse augments' the ifTable specifically when NHDP is to be configured to operate over this interface. The interface is identified by the ifIndex from the interfaces group defined in the Interfaces Group MIB module. A conceptual row in this table exists if and only if either a manager has explicitly created the row or there is an interface on the managed device that supports and runs NHDP. The manager can create a row by setting rowStatus to 'createAndGo' or 'createAndWait'. Row objects having associated DEFVAL clauses are automatically defined by the agent with these values during row creation, unless the manager explicitly defines these object values during the row creation. If the corresponding entry with ifIndex value is deleted from the Interface Table, then the entry in this table is automatically deleted, NHDP is disabled on this interface, and all configuration and state information related to this interface is to be removed from memory.

The nhdpInterfaceEntry describes one NHDP local interface configuration as indexed by its ifIndex as defined in the Standard MIB II Interface Table (RFC 2863). The objects in this table are persistent, and when written, the device SHOULD save the change to non-volatile storage. For further information on the storage behavior for these objects, refer to the description for the nhdpIfRowStatus object.

This value MUST correspond to an ifIndex referring to a valid entry in the Interfaces Table.

The textual name of the interface. The value of this object SHOULD be the name of the interface as assigned by the local device. This can be a text-name, such as 'le0' or a simple port number, such as '1', depending on the interface-naming syntax of the device. If there is no local name or this object is otherwise not applicable, then this object contains a zero-length string.

nhdpIfStatus indicates whether this interface is currently running NHDP. A value of 'true(1)' indicates that NHDP is running on this interface. A value of 'false(2)' indicates that NHDP is not currently running on this interface. This corresponds to the I_manet parameter in the Local Interface Set of NHDP.

nhdpHelloInterval corresponds to HELLO_INTERVAL of NHDP and represents the maximum time between the transmission of two successive HELLO messages on this MANET interface. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o nhdpHelloInterval > 0 o nhdpHelloInterval >= nhdpHelloMinInterval

nhdpHelloMinInterval corresponds to HELLO_MIN_INTERVAL of NHDP and represents the minimum interval between transmission of two successive HELLO messages on this MANET interface. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o nhdpHelloMinInterval <= nhdpHelloInterval

nhdpRefreshInterval corresponds to REFRESH_INTERVAL of NHDP and represents the maximum interval between advertisements of each 1-hop neighbor network address and its status. Each advertisement is in a HELLO message on this MANET interface. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o nhdpRefreshInterval >= nhdpHelloInterval

nhdpLHoldTime corresponds to L_HOLD_TIME of NHDP and represents 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. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that it should be assigned a value significantly greater than the refresh interval held by nhdpRefreshInterval.

nhdpHHoldTime corresponds to H_HOLD_TIME of NHDP and 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. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that it should be assigned a value significantly greater than the refresh interval held by nhdpRefreshInterval and must be representable as described in RFC 5497.

nhdpHystAcceptQuality corresponds to HYST_ACCEPT of NHDP and represents the link quality threshold at or above which a link becomes usable, if it was not already so. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o 0 <= nhdpHystRejectQuality <= nhdpHystAcceptQuality <= 1.0 The default value for this object is 1.0. According to RFC 6340: Since these textual conventions are defined in terms of the OCTET STRING type, the SMI's mechanisms for formally setting range constraints are not available. MIB designers using these textual conventions will need to use DESCRIPTION clauses to spell out any applicable range constraints beyond those implied by the underlying IEEE types. Therefore, this object does not have a DEFVAL clause.

nhdpHystRejectQuality corresponds to HYST_REJECT of NHDP and represents the link quality threshold below which a link becomes unusable, if it was not already so. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o 0 <= nhdpHystRejectQuality <= nhdpHystAcceptQuality <= 1.0 The default value for this object is 0.0. According to RFC 6340: Since these textual conventions are defined in terms of the OCTET STRING type, the SMI's mechanisms for formally setting range constraints are not available. MIB designers using these textual conventions will need to use DESCRIPTION clauses to spell out any applicable range constraints beyond those implied by the underlying IEEE types. Therefore, this object does not have a DEFVAL clause.

nhdpInitialQuality corresponds to INITIAL_QUALITY of NHDP and represents the initial quality of a newly identified link. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o 0 <= nhdpInitialQuality <= 1.0 The default value for this object is 1.0. According to RFC 6340: Since these textual conventions are defined in terms of the OCTET STRING type, the SMI's mechanisms for formally setting range constraints are not available. MIB designers using these textual conventions will need to use DESCRIPTION clauses to spell out any applicable range constraints beyond those implied by the underlying IEEE types. Therefore, this object does not have a DEFVAL clause.

nhdpInitialPending corresponds to INITIAL_PENDING of NHDP. If the value of this object is 'true(1)', then a newly identified link is considered pending and is not usable until the link quality has reached or exceeded the nhdpHystAcceptQuality threshold. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o If nhdpInitialQuality >= nhdpHystAcceptQuality, then nhdpInitialPending := false(2). o If nhdpInitialQuality < nhdpHystRejectQuality, then nhdpInitialPending := true(1).

nhdpHpMaxJitter corresponds to HP_MAXJITTER of NHDP and represents the value of MAXJITTER used in RFC 5148 for periodically generated HELLO messages on this MANET interface. Guidance for setting this object may be found in Section 5 of RFC 5148, which indicates that: o nhdpHpMaxJitter <= nhdpHelloInterval / 2 o nhdpHpMaxJitter should not be greater than nhdpHelloInterval / 4 o If nhdpMinHelloInterval > 0, then nhdpHpMaxJitter <= nhdpHelloMinInterval; and nhdpHpMaxJitter should not be greater than nhdpHelloMinInterval / 2

nhdpHtMaxJitter corresponds to HT_MAXJITTER of NHDP and represents the value of MAXJITTER used in RFC 5148 for externally triggered HELLO messages on this MANET interface. Guidance for setting this object may be found in Section 5 of RFC 5148, which indicates that: o nhdpHtMaxJitter <= nhdpHelloInterval / 2 o nhdpHtMaxJitter should not be greater than nhdpHelloInterval / 4 o If nhdpMinHelloInterval > 0, then nhdpHtMaxJitter <= nhdpHelloMinInterval; and nhdpHtMaxJitter should not be greater than nhdpHelloMinInterval / 2

This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified. An entry may not exist in the 'active(1)' state unless all objects in the entry have a defined appropriate value. For objects with DEFVAL clauses, the management station does not need to specify the value of this object in order for the row to transit to the 'active(1)' state; the default value for this object is used. For objects that do not have DEFVAL clauses, then the network manager MUST specify the value of this object prior to this row transitioning to the 'active(1)' state. When this object transitions to 'active(1)', all objects in this row SHOULD be written to non-volatile (stable) storage. Read-create objects in this row MAY be modified. When an object in a row with nhdpIfRowStatus of 'active(1)' is changed, then the updated value MUST be reflected in NHDP, and this new object value MUST be written to non-volatile storage. If the value of this object is not equal to 'active(1)', all associated entries in the nhdpLibLocalIfSetTable, nhdpInterfaceStateTable, nhdpIibLinkSetTable, and nhdpInterfacePerfTable MUST be deleted.

nhdpNHoldTime corresponds to N_HOLD_TIME of NHDP and 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. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.

nhdpIHoldTime corresponds to I_HOLD_TIME of NHDP and represents the period for which a recently used local interface network address is recorded. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.

A router's Local Interface Set records all network addresses that are defined as local MANET interface network addresses. As such, this table 'sparse augments' the nhdpInterfaceTable when network addresses are being defined for the interfaces existing within the nhdpInterfaceTable. The local interface is defined by the nhdpIfIndex. The Local Interface Set consists of Local Interface Address Tuples per MANET interface and their prefix lengths (in order to determine the network addresses related to the interface). A conceptual row in this table exists if and only if a manager has explicitly created the row. The manager can create a row by setting rowStatus to 'createAndGo' or 'createAndWait'. Further guidance on the addition or removal of local addresses and network addresses is found in Section 9 of RFC 6130.

A router's Local Interface Set consists of Configured Interface Address Tuples for each network interface. The objects in this table are persistent, and when written, the device SHOULD save the change to non-volatile storage. For further information on the storage behavior for these objects, refer to the description for the nhdpLibLocalIfSetRowStatus object.

The index for this table. Necessary because multiple addresses may be associated with a given nhdpIfIndex.

Specifies the local nhdpIfIndex for which this IP address was added.

The type of the nhdpLibLocalIfSetIpAddr in the InetAddress MIB (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.

nhdpLibLocalIfSetIpAddr is an address of an interface of this router. This object is interpreted according to the setting of nhdpLibLocalIfSetIpAddrType.

Indicates the number of leading one bits that form the mask. The mask is logically ANDed to the nhdpLibLocalIfSetIpAddr to determine the address prefix. A row match is true if the address used as an index falls within the network address range defined by the address prefix.

This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified. An entry may not exist in the 'active(1)' state unless all read-create objects in the entry have a defined appropriate value. As no objects in this table have DEFVAL clauses, the management station MUST specify the values of all read-create objects prior to this row transitioning to the 'active(1)' state. When this object transitions to 'active(1)', all objects in this row SHOULD be written to non-volatile (stable) storage. Read-create objects in this row MAY be modified. When an object in a row with nhdpIfRowStatus of 'active(1)' is changed, then the updated value MUST be reflected in NHDP, and this new object value MUST be written to non-volatile storage.

A router's Removed Interface Address Set records network addresses that were recently used as local interface network addresses. If a router's interface network addresses are immutable, then the Removed Interface Address Set is always empty and may be omitted. It consists of Removed Interface Address Tuples, one per network address.

A router's Removed Interface Address Set consists of Removed Interface Address Tuples, one per network address: (IR_local_iface_addr, IR_time) The association between these addresses and the router's Interface is found in the Standard MIB II's IP address table (RFC 1213).

The index for this table. Necessary because multiple addresses may be associated with a given nhdpIfIndex.

The type of the nhdpLibRemovedIfAddrSetIpAddr in the InetAddress MIB (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.

nhdpLibRemovedIfAddrSetIpAddr is a recently used address of an interface of this router.

Indicates the number of leading one bits that form the mask. The mask is logically ANDed to the nhdpLibRemovedIfAddrSetIpAddr to determine the address prefix. A row match is true if the address used as an index falls within the network address range defined by the address prefix.

Specifies the local IfIndex from which this IP address was recently removed.

nhdpLibRemovedIfAddrSetIRTime specifies the value of sysUptime when this entry should expire and be removed from the nhdpLibRemovedIfAddrSetTable.

The value of sysUpTime at the time the current NHDP process was initialized.

nhdpInterfaceStateTable lists state information related to specific interfaces of this router. The value of nhdpIfIndex is an ifIndex from the interfaces group defined in the Interfaces Group MIB. The objects in this table are persistent, and when written, the entity SHOULD save the change to non-volatile storage.

nhdpInterfaceStateEntry describes one NHDP local interface state as indexed by its nhdpIfIndex.

The value of the sysUpTime when NHDP was last initialized on this MANET interface.

A router's set of discovered interfaces on neighboring routers.

The entries include the nhdpDiscRouterIndex of the discovered router, the nhdpDiscIfIndex of the discovered interface, and the current set of addresses associated with this neighbor interface. The nhdpDiscIfIndex uniquely identifies the remote interface address sets through this table. It does not need to be unique across the MANET but MUST be locally unique within this router.

The index for this table. Necessary because multiple addresses may be associated with a given nhdpDiscIfIndex.

The NHDP interface index (locally created) of a neighbor's interface. Used for cross- indexing into other NHDP tables and other MIB modules.

The NHDP neighbor index (locally created) of a neighboring router. Used for cross- indexing into other NHDP tables and other MIB modules.

The type of the nhdpDiscIfSetIpAddr in the InetAddress MIB (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.

The nhdpDiscIfSetIpAddr is a recently used address of a neighbor of this router.

Indicates the number of leading one bits that form the mask. The mask is logically ANDed to the nhdpDiscIfSetIpAddr to determine the address prefix. A row match is true if the address used as an index falls within the network address range defined by the address prefix.

A Link Set of an interface records all links from other routers that are, or recently were, 1-hop neighbors.

A Link Set consists of Link Tuples, each representing a single link indexed by the local and remote interface pair: (L_neighbor_iface_addr_list, L_HEARD_time, L_SYM_time, L_quality, L_pending, L_lost, L_time). The local interface is indexed via the nhdpIfIndex. The 1-hop interface is indexed via the nhdpDiscIfIndex. There SHOULD be an entry in this table for each local interface and associated 1-hop neighbor reachable on this local interface. Note that L_quality is not included in the entries below, because updates may be required too frequently.

nhdpIibLinkSetLHeardTime corresponds to L_HEARD_time of NHDP and represents the time up to which the MANET interface of the 1-hop neighbor would be considered heard if not considering link quality.

nhdpIibLinkSetLSymTime corresponds to L_SYM_time of NHDP and represents the time up to which the link to the 1-hop neighbor would be considered symmetric if not considering link quality.

nhdpIibLinkSetLPending corresponds to L_pending of NHDP and is a boolean flag, describing if a link is considered pending (i.e., a candidate, but not yet established, link).

nhdpIibLinkSetLLost corresponds to L_lost of NHDP and is a boolean flag, describing if a link is considered lost due to low link quality.

nhdpIibLinkSetLTime specifies the value of sysUptime when this entry should expire and be removed from the nhdpIibLinkSetTable.

A 2-Hop Set of an interface records network addresses of symmetric 2-hop neighbors and the symmetric links to symmetric 1-hop neighbors through which these symmetric 2-hop neighbors can be reached. It consists of 2-Hop Tuples.

nhdpIib2HopSetTable consists of 2-Hop Tuples, each representing a single network address of a symmetric 2-hop neighbor and a single MANET interface of a symmetric 1-hop neighbor. (N2_neighbor_iface_addr_list, N2_2hop_addr, N2_time). The entries include the 2-hop neighbor addresses, which act as the table index, and associated 1-hop symmetric link address set, designated through nhdpDiscIfIndex, and an expiration time. The nhdpIfIndex in the INDEX is the interface index of the local interface through which these 2-hop addresses are accessible. The nhdpDiscIfIndex in the INDEX represents the 1-hop neighbor interface through which these 2-hop addresses are reachable.

The type of the nhdpIib2HopSetIpAddress in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.

nhdpIib2HopSetIpAddr corresponds to N2_2hop_addr of NHDP and is a network address of a symmetric 2-hop neighbor that has a symmetric link (using any MANET interface) to the indicated symmetric 1-hop neighbor.

Indicates the number of leading one bits that form the mask. The mask is logically ANDed to the nhdpIib2HopSetIpAddress to determine the address prefix. A row match is true if the address used as an index falls within the network address range defined by the address prefix.

nhdpIib2HopSet1HopIfIndex is nhdpDiscIfIndex of the 1-hop neighbor that communicated the ipAddress of the 2-hop neighbor in this row entry.

nhdpIib2HopSetN2Time specifies the value of sysUptime when this entry should expire and be removed from the nhdpIib2HopSetTable.

A router's Neighbor Set records all network addresses of each 1-hop neighbor.

A router's Neighbor Set consists of Neighbor Tuples, each representing a single 1-hop neighbor: (N_neighbor_addr_list, N_symmetric)

nhdpNibNeighborNSymmetric corresponds to N_symmetric of NHDP and is a boolean flag, describing if this is a symmetric 1-hop neighbor.

A router's Lost Neighbor Set records network addresses of routers that were recently symmetric 1-hop neighbors but are now advertised as lost.

A router's Lost Neighbor Set consists of Lost Neighbor Tuples, each representing a single such network address: (NL_neighbor_addr, NL_time)

nhdpNibLostNeighborSetNLTime specifies the value of sysUptime when this entry should expire and be removed from the nhdpNibLostNeighborSetTable.

This table summarizes performance objects that are measured per local NHDP interface.

A single entry contains performance counters for a local NHDP interface.

A counter is incremented each time a HELLO message has been transmitted on that interface.

A counter is incremented each time a HELLO message has been received on that interface.

A counter is incremented by the number of octets in a HELLO message each time a HELLO message has been sent.

A counter is incremented by the number of octets in a HELLO message each time a HELLO message has been received.

A counter is incremented each time a triggered HELLO message has been sent.

A counter is incremented each time a periodic HELLO message has been sent.

A counter is incremented by the number of advertised symmetric neighbors in a HELLO each time a HELLO message has been sent.

A counter is incremented by the number of advertised heard neighbors in a HELLO each time a HELLO message has been sent.

A counter is incremented by the number of advertised lost neighbors in a HELLO each time a HELLO message has been sent.

A router's set of performance properties for each discovered interface of a neighbor.

There is an entry for each discovered interface of a neighbor.

This counter increments each time this router receives a packet from that interface of the neighbor.

This counter increments by the number of missed packets from this neighbor based on the packet sequence number each time this router receives a packet from that interface of the neighbor.

This counter increments each time the Neighbor Set changes. A change occurs whenever a new Neighbor Tuple has been added, a Neighbor Tuple has been removed, or any entry of a Neighbor Tuple has been modified.

A router's set of discovered neighbors and their properties.

The entries include the nhdpDiscRouterIndex of the discovered router as well as performance objects related to changes of the Neighbor Set.

This object returns the number of changes to the given Neighbor Tuple.

This object returns the sysUpTime when the neighbor becomes 'nbrup'. A neighbor is said to become 'nbrup' if a new nhdpNibNeighborSetEntry is created for a particular nhdpNibNeighborSetRouterIndex. It becomes 'nbrdown' if the entry for that neighbor has been deleted.

This object counts each time the neighbor changes the interface(s) over which it is reachable. A change in the set of Link Tuples corresponding to the appropriate Neighbor Tuple is registered, i.e., a corresponding Link Tuple is added or removed from the set of all corresponding Link Tuples.

This table contains performance objects per discovered 2-hop neighbor.

The entries contain performance objects per discovered 2-hop neighbor.

This object counts 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 2-hop neighbor's addresses.

This object returns the sysUpTime when the 2-Hop Tuple corresponding to the given 2-hop neighbor IP address was registered in the nhdpIib2HopSetTable.

The basic implementation requirements for managed network entities that implement NHDP.

The full implementation requirements for managed network entities that implement NHDP.

Set of NHDP configuration objects implemented in this module.

Set of NHDP state objects implemented in this module.

Set of NHDP performance objects implemented in this module.

Set of NHDP notification objects implemented in this module.

Set of NHDP notifications implemented in this module.