All MIBs › NEMO-MIB
Organization: IETF MEXT Working Group
Last Updated: 2009-03-10
Category: IP and Core Protocols, Mobile IP
Description: Defines managed objects for monitoring and controlling Network Mobility (NEMO) functionality on Mobile IPv6 nodes.
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring NEMO-MIB with a free 30-day trial of IPNetwork Monitor.
What Is NEMO-MIB?
NEMO-MIB is the standard IETF MEXT Working Group MIB (RFC 5488) for NEMO (Network Mobility) Basic Support, monitoring Mobile Router-to-Home-Agent mobility state. Its objects cover general capabilities/status and a counter-discontinuity time, a Mobile Router binding-list table (mode, MR flag, home/care-of address prefix length, active egress interface, established home-tunnel interface), mobility message sent/received counts, prefix-registration mode, a Home Agent mobile-network-prefix table (sequence number, type, prefix/length, source), and a binding-cache table (MR flag, mode). As a configuration/status MIB it lets an administrator confirm whether a mobile router's NEMO tunnel to its home agent is established and watch mobility signaling volume. It is deployed on routers implementing IETF NEMO Basic Support (RFC 5488). Engineers can download the NEMO-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in NEMO-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Routers implementing IETF NEMO Basic Support (RFC 5488)
Monitoring Examples
An administrator checks nemoMrBLEstablishedHomeTunnelIfIndex to confirm a mobile router's NEMO tunnel to its home agent is up on an IETF NEMO-capable router.
What Can Be Monitored
- NEMO mobile router binding and tunnel status
This MIB depends on
Related MIBs
Imported Objects
From IF-MIB
| InterfaceIndex |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressPrefixLength | |
| InetAddressType |
From MOBILEIPV6-MIB
| mip6BindingCacheEntry | OBJECT-TYPE |
| mip6BindingHomeAddress | OBJECT-TYPE |
| mip6BindingHomeAddressType | OBJECT-TYPE |
| mip6MnBLCOA | OBJECT-TYPE |
| mip6MnBLCOAType | OBJECT-TYPE |
| mip6MnBLEntry | OBJECT-TYPE |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Gauge32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 | |
| mib-2 |
From SNMPv2-TC
| DateAndTime | |
| TEXTUAL-CONVENTION | |
| TimeStamp | |
| TruthValue |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| nemoMIB | 1.3.6.1.2.1.184 | Copyright (c) 2009 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, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5488; see the RFC itself for full legal notices. | ||
| nemoNotifications | 1.3.6.1.2.1.184.0 | |||
| NTF nemoHomeTunnelEstablished | 1.3.6.1.2.1.184.0.1 | This notification is sent by the mobile router every time the tunnel is established between the home agent and the mobile router. | ||
| NTF nemoHomeTunnelReleased | 1.3.6.1.2.1.184.0.2 | This notification is sent by the mobile router every time the tunnel is deleted between the home agent and the mobile router. | ||
| nemoObjects | 1.3.6.1.2.1.184.1 | |||
| nemoCore | 1.3.6.1.2.1.184.1.1 | |||
| nemoSystem | 1.3.6.1.2.1.184.1.1.1 | |||
| BIT nemoCapabilities | 1.3.6.1.2.1.184.1.1.1.1 | Bits | read-only | This object indicates the NEMO functions that are supported by this managed entity. Multiple NEMO functions may be supported by a single entity. |
| INT nemoStatus | 1.3.6.1.2.1.184.1.1.1.2 | INTEGER | read-write | This object indicates whether the NEMO function is enabled for the managed entity. If it is enabled, the agent discovery and registration functions will be operational. Changing the status from enabled(1) to disabled(2) will terminate the agent discovery and registration functions. On the other hand, changing the status from disabled(2) to enabled(1) will start the agent discovery and registration functions. The value of this object MUST remain unchanged across reboots of the managed entity. |
| nemoBindings | 1.3.6.1.2.1.184.1.1.2 | |||
| nemoBindingCacheTable | 1.3.6.1.2.1.184.1.1.2.1 | not-accessible | This table models the Binding Cache that includes NEMO-related information and that is maintained by the home agent. Entries in this table are not required to survive a reboot of the home agent. | |
| nemoBindingCacheEntry | 1.3.6.1.2.1.184.1.1.2.1.1 | not-accessible | An entry containing additional information related to NEMO-enabled entries in the Binding Cache table of the home agent. | |
| T/F nemoBindingMrFlag | 1.3.6.1.2.1.184.1.1.2.1.1.1 | TruthValue | read-only | true(1): indicates that the Binding Cache entry is from an entity acting as a mobile router. false(2): implies that the Binding Cache entry is from an entity acting as a mobile node. |
| INT nemoBindingMrMode | 1.3.6.1.2.1.184.1.1.2.1.1.2 | INTEGER | read-only | implicitMode(1): the Mobile Network Prefix Option is not included in the Binding Update by the mobile router. explicitMode(2): the mobile router included one or more Mobile Network Prefix Options in the Binding Update. |
| nemoConfiguration | 1.3.6.1.2.1.184.1.1.3 | |||
| nemoStats | 1.3.6.1.2.1.184.1.1.4 | |||
| TIM nemoCounterDiscontinuityTime | 1.3.6.1.2.1.184.1.1.4.1 | TimeStamp | read-only | The value of sysUpTime on the most recent occasion at which any one or more of this NEMO entity's counters, viz., counters with OID prefix 'nemoMrConf', 'nemoMrRegnCounters', 'nemoMrGlobalStats', or 'nemoHaGlobalStats', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. |
| nemoMr | 1.3.6.1.2.1.184.1.2 | |||
| nemoMrSystem | 1.3.6.1.2.1.184.1.2.1 | |||
| nemoMrEgressIfTable | 1.3.6.1.2.1.184.1.2.1.1 | not-accessible | A table representing the egress interfaces that will be used by the mobile router for roaming to foreign networks. Each entry in this table represents a configured egress interface. | |
| nemoMrEgressIfEntry | 1.3.6.1.2.1.184.1.2.1.1.1 | not-accessible | An entry in the egress interface table. It represents a single egress interface entry. | |
| NUM nemoMrEgressIfIndex | 1.3.6.1.2.1.184.1.2.1.1.1.1 | InterfaceIndex | not-accessible | The index of the interface on the mobile router. |
| U32 nemoMrEgressIfPriority | 1.3.6.1.2.1.184.1.2.1.1.1.2 | Unsigned32 | read-only | The priority configured to the egress interface. This value will be configured to a value between 0 and 255. |
| STR nemoMrEgressIfDescription | 1.3.6.1.2.1.184.1.2.1.1.1.3 | SnmpAdminString | read-only | A human-readable textual description of the egress interface on the mobile router. |
| G32 nemoMrEgressIfRoamHoldDownTime | 1.3.6.1.2.1.184.1.2.1.1.1.4 | Gauge32 | read-only | This object indicates the time for which the egress interface will be held down during roaming to avoid interface flapping. |
| nemoMrConf | 1.3.6.1.2.1.184.1.2.2 | |||
| C32 nemoMrDiscoveryRequests | 1.3.6.1.2.1.184.1.2.2.1 | Counter32 | read-only | Total number of Modified Dynamic Home Agent Address Discovery Requests, with Mobile Router Support Flag set, sent by the mobile router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrDiscoveryReplies | 1.3.6.1.2.1.184.1.2.2.2 | Counter32 | read-only | Total number of Modified Dynamic Home Agent Address Discovery Replies, with Mobile Router Support Flag set, received by the mobile router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrDiscoveryRepliesRouterFlagZero | 1.3.6.1.2.1.184.1.2.2.3 | Counter32 | read-only | Total number of Modified Dynamic Home Agent Address Discovery Replies, with Mobile Router Support Flag set to 0 although the flag in the corresponding request is set to 1. It implies that there is no home agent that supports mobile router functionality in the home network. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrMovedHome | 1.3.6.1.2.1.184.1.2.2.4 | Counter32 | read-only | Number of times the mobile router has detected movement from a foreign network to its home network. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrMovedOutofHome | 1.3.6.1.2.1.184.1.2.2.5 | Counter32 | read-only | Number of times the mobile router has detected movement to a foreign network from the home network, has acquired a care-of address, and has initiated the care-of address registration process. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrMovedFNtoFN | 1.3.6.1.2.1.184.1.2.2.6 | Counter32 | read-only | Number of times the mobile router has detected movement to/from a foreign network from/to another foreign network. Note that 'movement' implies movement in layer 3, i.e., the mobile router's care-of address changed, and it initiated the care-of address registration process. If there are multiple egress interfaces, this counter counts the total number of movements. The movement as a mobile node of the mobile entity is not counted. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrBetterIfDetected | 1.3.6.1.2.1.184.1.2.2.7 | Counter32 | read-only | Number of times the NEMO entity has found an egress interface with better priority. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| nemoMrRegistration | 1.3.6.1.2.1.184.1.2.3 | |||
| nemoMrBLTable | 1.3.6.1.2.1.184.1.2.3.1 | not-accessible | This table corresponds to the Binding Update List (BL) that includes NEMO-related information and that is maintained by the mobile router. The table holds a row for every binding that the mobile router has established or is trying to establish. Entries from the table are deleted as the lifetime of the binding expires. | |
| nemoMrBLEntry | 1.3.6.1.2.1.184.1.2.3.1.1 | not-accessible | An entry pertaining to NEMO-related information contained in a Binding Update sent by a NEMO-enabled mobile router to its home agent. | |
| INT nemoMrBLMode | 1.3.6.1.2.1.184.1.2.3.1.1.1 | INTEGER | read-only | implicitMode(1): the Mobile Network Prefix Option is not included in the Binding Update by the mobile router. explicitMode(2): the mobile router included one or more Mobile Network Prefix Options in the Binding Update. |
| T/F nemoMrBLMrFlag | 1.3.6.1.2.1.184.1.2.3.1.1.2 | TruthValue | read-only | true(1): the mobile router sent the Binding Update with Mobile Router Flag set. false(2): the mobile router did not send the Binding Update with Mobile Router Flag set. This implies that the mobile router is acting as a mobile node. |
| ADR nemoMrBLHomeAddressPrefixLength | 1.3.6.1.2.1.184.1.2.3.1.1.3 | InetAddressPrefixLength | read-only | The prefix length of the mobile router's home network. |
| ADR nemoMrBLCareofAddressPrefixLength | 1.3.6.1.2.1.184.1.2.3.1.1.4 | InetAddressPrefixLength | read-only | The prefix length of the care-of address of the mobile router. |
| NUM nemoMrBLActiveEgressIfIndex | 1.3.6.1.2.1.184.1.2.3.1.1.5 | InterfaceIndex | read-only | The interface index of the currently active egress interface. |
| NUM nemoMrBLEstablishedHomeTunnelIfIndex | 1.3.6.1.2.1.184.1.2.3.1.1.6 | InterfaceIndex | read-only | The interface index of the tunnel established between the mobile router and the home agent for NEMO traffic. |
| nemoMrRegnCounters | 1.3.6.1.2.1.184.1.2.3.2 | |||
| C32 nemoMrMobilityMessagesSent | 1.3.6.1.2.1.184.1.2.3.2.1 | Counter32 | read-only | The total number of mobility messages, i.e., IPv6 datagrams with Mobility Header, sent by the mobile node. This will include Binding Updates sent by a mobile router with the Mobile Router Flag set. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrMobilityMessagesRecd | 1.3.6.1.2.1.184.1.2.3.2.2 | Counter32 | read-only | The total number of mobility messages, i.e., IPv6 datagrams with Mobility Header, received by the mobile node. This will include Binding Acknowledgements with Mobile Router Flag set that are sent to a mobile router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| INT nemoMrPrefixRegMode | 1.3.6.1.2.1.184.1.2.3.3 | INTEGER | read-write | This object indicates the mode in which the mobile network prefixes will be registered with the home agent. implicitMode(1): the Mobile Network Prefix Option will not be included in the Binding Update by the mobile router. explicitMode(2): the mobile router will include one or more Mobile Network Prefix Options in the Binding Update. The value of this object MUST remain unchanged across reboots of the managed entity. |
| nemoMrGlobalStats | 1.3.6.1.2.1.184.1.2.4 | |||
| C32 nemoMrBindingAcksWONemoSupport | 1.3.6.1.2.1.184.1.2.4.1 | Counter32 | read-only | The total number of Binding Acknowledgements without NEMO support received by the mobile router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrBindingAcksRegTypeChangeDisallowed | 1.3.6.1.2.1.184.1.2.4.2 | Counter32 | read-only | The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Registration type change disallowed' (Code 139). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrBindingAcksOperationNotPermitted | 1.3.6.1.2.1.184.1.2.4.3 | Counter32 | read-only | The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Mobile Router Operation not permitted' (Code 140). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrBindingAcksInvalidPrefix | 1.3.6.1.2.1.184.1.2.4.4 | Counter32 | read-only | The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Invalid Prefix' (Code 141). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrBindingAcksNotAuthorizedForPrefix | 1.3.6.1.2.1.184.1.2.4.5 | Counter32 | read-only | The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Not Authorized for Prefix' (Code 142). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrBindingAcksForwardingSetupFailed | 1.3.6.1.2.1.184.1.2.4.6 | Counter32 | read-only | The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Forwarding Setup failed' (Code 143). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoMrBindingAcksOtherError | 1.3.6.1.2.1.184.1.2.4.7 | Counter32 | read-only | The total number of Binding Acknowledgements received by the mobile router (Mobile Router Flag is set) with status code other than: successfully processed --(Code 0 ) mobileRouterOperationNotPermitted (140) --(Code 140) invalidPrefix (141) --(Code 141) notAuthorizedForPrefix (142) --(Code 142) forwardingSetupFailed (143) --(Code 143) Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| nemoCn | 1.3.6.1.2.1.184.1.3 | |||
| nemoHa | 1.3.6.1.2.1.184.1.4 | |||
| nemoHaAdvertisement | 1.3.6.1.2.1.184.1.4.1 | |||
| nemoHaStats | 1.3.6.1.2.1.184.1.4.2 | |||
| nemoHaGlobalStats | 1.3.6.1.2.1.184.1.4.2.1 | |||
| C32 nemoHaBUAcksWONemoSupport | 1.3.6.1.2.1.184.1.4.2.1.1 | Counter32 | read-only | The total number of Binding Acknowledgements without NEMO support sent by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoHaBUAcksRegTypeChangeDisallowed | 1.3.6.1.2.1.184.1.4.2.1.2 | Counter32 | read-only | The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Registration type change disallowed' (Code 139). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoHaBUAcksOperationNotPermitted | 1.3.6.1.2.1.184.1.4.2.1.3 | Counter32 | read-only | The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Mobile Router Operation not permitted' (Code 140). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoHaBUAcksInvalidPrefix | 1.3.6.1.2.1.184.1.4.2.1.4 | Counter32 | read-only | The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Invalid Prefix' (Code 141). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoHaBUAcksNotAuthorizedForPrefix | 1.3.6.1.2.1.184.1.4.2.1.5 | Counter32 | read-only | The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Not Authorized for Prefix' (Code 142). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoHaBUAcksForwardingSetupFailed | 1.3.6.1.2.1.184.1.4.2.1.6 | Counter32 | read-only | The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Forwarding Setup failed' (Code 143). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| C32 nemoHaBUAcksOtherError | 1.3.6.1.2.1.184.1.4.2.1.7 | Counter32 | read-only | The total number of Binding Update requests from mobile routers (Mobile Router Flag is set) rejected by the home agent with status code other than: mobileRouterOperationNotPermitted (140) invalidPrefix (141) notAuthorizedForPrefix (142) forwardingSetupFailed (143) Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. |
| nemoHaCounterTable | 1.3.6.1.2.1.184.1.4.2.2 | not-accessible | A table containing registration statistics for all mobile routers registered with the home agent. | |
| nemoHaCounterEntry | 1.3.6.1.2.1.184.1.4.2.2.1 | not-accessible | Home agent registration statistics for a mobile router. Implementers need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. | |
| C32 nemoHaBURequestsAccepted | 1.3.6.1.2.1.184.1.4.2.2.1.1 | Counter32 | read-only | Total number of Binding Update requests from the mobile router accepted by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoHaCtrDiscontinuityTime. |
| C32 nemoHaBURequestsDenied | 1.3.6.1.2.1.184.1.4.2.2.1.2 | Counter32 | read-only | Total number of Binding Update requests from the mobile router rejected by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoHaCtrDiscontinuityTime. |
| DAT nemoHaBCEntryCreationTime | 1.3.6.1.2.1.184.1.4.2.2.1.3 | DateAndTime | read-only | The time when the current Binding Cache entry was created for the mobile router. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time. |
| DAT nemoHaBUAcceptedTime | 1.3.6.1.2.1.184.1.4.2.2.1.4 | DateAndTime | read-only | The time at which the last Binding Update was accepted by the home agent for this mobile router. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time. |
| DAT nemoHaBURejectionTime | 1.3.6.1.2.1.184.1.4.2.2.1.5 | DateAndTime | read-only | The time at which the last Binding Update was rejected by the home agent for this mobile router. If there have been no rejections, then this object will be inaccessible. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time. |
| NEM nemoHaRecentBURejectionCode | 1.3.6.1.2.1.184.1.4.2.2.1.6 | NemoBURequestRejectionCode | read-only | The Status code (>= 128) in the latest Binding Acknowledgment indicating a rejection, sent to this mobile router. If a Binding Update request is rejected and a Binding Acknowledgment is not sent to this mobile router, then this will be the value of the Status code that corresponds to the reason of the rejection. If there have been no Binding Update request rejections, then this object will be inaccessible. |
| TIM nemoHaCtrDiscontinuityTime | 1.3.6.1.2.1.184.1.4.2.2.1.7 | TimeStamp | read-only | The value of sysUpTime on the most recent occasion at which any one or more of the counters in this row, viz., instances of 'nemoHaBURequestsAccepted' and 'nemoHaBURequestsDenied', suffered a discontinuity. If no such discontinuity has occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. |
| nemoHaRegistration | 1.3.6.1.2.1.184.1.4.3 | |||
| nemoHaMobileNetworkPrefixTable | 1.3.6.1.2.1.184.1.4.3.1 | not-accessible | This table contains the mobile network prefixes that the home agent maintains for the mobile router. The mobile network prefixes in this table are registered by Binding Updates or are manually pre-configured. | |
| nemoHaMobileNetworkPrefixEntry | 1.3.6.1.2.1.184.1.4.3.1.1 | not-accessible | An entry for a mobile network prefix. The instances of the columnar objects in this entry pertain to an interface for a particular value of mip6BindingHomeAddressType, mip6BindingHomeAddress, and nemoHaMobileNetworkPrefixSeqNo. The nemoHaMobileNetworkPrefixSeqNo object is used to distinguish between multiple instances of the mobile network prefix in the same Binding Update for the same set of mip6BindingHomeAddressType and mip6BindingHomeAddress. There is no upper-bound on the maximum number of mobile network prefixes in a Binding Update but, for practical purposes, the upper bound of the value nemoHaMobileNetworkPrefixSeqNo is set to 1024. Implementers need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 112, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. | |
| U32 nemoHaMobileNetworkPrefixSeqNo | 1.3.6.1.2.1.184.1.4.3.1.1.1 | Unsigned32 | not-accessible | A Binding Update may have multiple mobile network prefixes. This object, along with mip6BindingHomeAddressType and mip6BindingHomeAddress, uniquely identifies a row containing a single mobile network prefix for a mobile router in this table. |
| IPt nemoHaMobileNetworkPrefixType | 1.3.6.1.2.1.184.1.4.3.1.1.2 | InetAddressType | read-only | The address type for the mobile network prefix that follows. |
| IP nemoHaMobileNetworkPrefix | 1.3.6.1.2.1.184.1.4.3.1.1.3 | InetAddress | read-only | A mobile network prefix related to the corresponding Binding Update. The type of the address represented by this object is specified by the corresponding nemoHaMobileNetworkPrefixType object. |
| U32 nemoHaMobileNetworkPrefixLength | 1.3.6.1.2.1.184.1.4.3.1.1.4 | Unsigned32 | read-only | The length of the prefix specified by the corresponding nemoHaMobileNetworkPrefix object. |
| INT nemoHaMobileNetworkPrefixSource | 1.3.6.1.2.1.184.1.4.3.1.1.5 | INTEGER | read-only | The information source of the mobile network prefix configured with the Binding Update. configured(1): indicates that the mobile network prefix has been manually pre-configured. bindingUpdate(2): indicates that the information is introduced to the home agent by the Mobile Network Prefix Option in the Binding Updates received by the home agent. |
| nemoConformance | 1.3.6.1.2.1.184.2 | |||
| nemoGroups | 1.3.6.1.2.1.184.2.1 | |||
| nemoSystemGroup | 1.3.6.1.2.1.184.2.1.1 | A collection of objects for basic NEMO monitoring. | ||
| nemoBindingCacheGroup | 1.3.6.1.2.1.184.2.1.2 | A collection of objects for monitoring the NEMO extensions of the Binding Cache. | ||
| nemoStatsGroup | 1.3.6.1.2.1.184.2.1.3 | A collection of objects for monitoring NEMO statistics. | ||
| nemoMrConfGroup | 1.3.6.1.2.1.184.2.1.4 | A collection of objects for monitoring the configuration-related information on the mobile router. | ||
| nemoMrRegistrationGroup | 1.3.6.1.2.1.184.2.1.5 | A collection of objects for monitoring the registration details and statistics for the mobile router. | ||
| nemoHaSystemGroup | 1.3.6.1.2.1.184.2.1.6 | A collection of objects for basic NEMO configuration monitoring at the home agent. | ||
| nemoHaStatsGroup | 1.3.6.1.2.1.184.2.1.7 | A collection of objects for monitoring NEMO registration-related statistics pertaining to the mobile routers registered with the home agent. | ||
| nemoHaGlobalStatsGroup | 1.3.6.1.2.1.184.2.1.8 | A collection of objects for monitoring basic NEMO advertisement and registration statistics on a home agent. | ||
| nemoNotificationGroup | 1.3.6.1.2.1.184.2.1.9 | A collection of notifications from a home agent or correspondent node to the manager about the tunnel status of the mobile router. | ||
| nemoCompliances | 1.3.6.1.2.1.184.2.2 | |||
| nemoCoreCompliance | 1.3.6.1.2.1.184.2.2.1 | The compliance statement for SNMP entities that implement the NEMO-MIB. | ||
| nemoCompliance2 | 1.3.6.1.2.1.184.2.2.2 | The compliance statement for SNMP entities that implement the NEMO-MIB and support monitoring of the Binding Cache. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- | ||
| nemoCoreReadOnlyCompliance | 1.3.6.1.2.1.184.2.2.3 | The compliance statement for SNMP entities that implement the NEMO-MIB without support for read-write (i.e., in read-only mode). | ||
| nemoReadOnlyCompliance2 | 1.3.6.1.2.1.184.2.2.4 | The compliance statement for SNMP entities that implement the NEMO-MIB without support for read-write (i.e., in read-only mode) and with support for monitoring of the Binding Cache. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- | ||
| nemoMrCompliance | 1.3.6.1.2.1.184.2.2.5 | The compliance statement for SNMP entities that implement the NEMO-MIB for monitoring configuration- related information, registration details, and statistics on a mobile router. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnBLNodeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnBLNodeAddress -- object. -- -- OBJECT mip6MnBLNodeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnBLNodeAddress -- object. | ||
| nemoMrReadOnlyCompliance2 | 1.3.6.1.2.1.184.2.2.6 | The compliance statement for SNMP entities that implement the NEMO-MIB without support for read- write (i.e., in read-only mode) and with support for monitoring of configuration-related information, registration details, and statistics on a mobile router. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnBLNodeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnBLNodeAddress -- object. -- -- OBJECT mip6MnBLNodeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnBLNodeAddress -- object. | ||
| nemoHaCoreCompliance | 1.3.6.1.2.1.184.2.2.7 | The compliance statement for SNMP entities that implement the NEMO-MIB for configuration monitoring at the home agent. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- | ||
| nemoHaCompliance2 | 1.3.6.1.2.1.184.2.2.8 | The compliance statement for SNMP entities that implement the NEMO-MIB with support for monitoring of the home agent functionality, specifically the home-agent-registration-related statistics. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- | ||
| nemoNotificationCompliance | 1.3.6.1.2.1.184.2.2.9 | The compliance statement for SNMP entities that implement the NEMO-MIB and support Notification from the home agent. |
RFC description
Supports Network Mobility (NEMO) IPv6 extensions for managing mobile network routes and binding cache.
Start monitoring Vendor-neutral IETF standard (router implementing NEMO Basic Support) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.