Network Mobility (NEMO) Management Information Base
Extracted elements (26)
The NEMO MIB augments the existing MOBILEIPV6-MIB tables (via AUGMENTS) rather than redefining them, because a mobile router may also function as a mobile node. This avoids duplication and allows a single entity to be managed through both MIBs simultaneously.
The nemoHaMobileNetworkPrefixSeqNo index (1..1024) was introduced to distinguish multiple mobile network prefixes within the same Binding Update for the same home address, since a single BU may carry arbitrarily many Mobile Network Prefix Options.
NEMO-MIB tables that use mip6BindingHomeAddress as an index object can produce OIDs with more than 128 sub-identifiers if the address exceeds 112 (or 113) octets, making those rows inaccessible via SNMPv1, SNMPv2c, or SNMPv3.
The NEMO MIB depends on MOBILEIPV6-MIB (RFC 4295) via AUGMENTS on mip6MnBLEntry and mip6BindingCacheEntry, and requires the IF-MIB ifTable. Compliance statements mandate support for global IPv6 addresses (InetAddressType ipv6(2), InetAddress SIZE(16)) for all home address index objects.
Deployment of SNMPv3 with full cryptographic mechanisms (authentication and privacy) is RECOMMENDED; deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Implementers SHOULD consider the SNMPv3 security framework per RFC 3410 section 8.
Implementations MUST return all 11 bytes of the DateAndTime textual convention for nemoHaBCEntryCreationTime, nemoHaBUAcceptedTime, and nemoHaBURejectionTime so that a manager can retrieve the UTC offset.
Implementations supporting both mobile node and NEMO functionality SHOULD implement managed objects from both MOBILEIPV6-MIB (RFC 4295) and NEMO-MIB.
The value of nemoMrPrefixRegMode MUST remain unchanged across reboots of the managed entity, ensuring the prefix registration mode is consistently applied.
The value of nemoStatus MUST remain unchanged across reboots of the managed entity, preserving the enabled/disabled state of NEMO functionality.
nemoBindingCacheTable augments mip6BindingCacheEntry with two NEMO fields: nemoBindingMrFlag (TruthValue indicating MR vs. MN) and nemoBindingMrMode (implicit/explicit prefix registration mode). Entries are not required to survive a home agent reboot.
NemoBURequestRejectionCode is a textual convention encoding NEMO-specific Binding Acknowledgment rejection status codes: mobileRouterOperationNotPermitted(140), invalidPrefix(141), notAuthorizedForPrefix(142), and forwardingSetupFailed(143).
nemoCapabilities (nemoSystem 1) is a read-only BITS object indicating which NEMO functions are supported: mobileRouter(0) and homeAgentSupport(1). Multiple functions may be supported simultaneously.
nemoCounterDiscontinuityTime (TimeStamp) records the sysUpTime of the most recent counter discontinuity across nemoMrConf, nemoMrRegnCounters, nemoMrGlobalStats, and nemoHaGlobalStats counter groups. A zero value indicates no discontinuity since last re-initialization.
nemoHaCounterTable provides per-mobile-router registration statistics at the home agent, including nemoHaBURequestsAccepted, nemoHaBURequestsDenied, nemoHaBCEntryCreationTime, nemoHaBUAcceptedTime, nemoHaBURejectionTime, and nemoHaRecentBURejectionCode.
nemoHaMobileNetworkPrefixSource indicates how each mobile network prefix was introduced: configured(1) for manually pre-configured prefixes, or bindingUpdate(2) for prefixes learned via the Mobile Network Prefix Option in received Binding Updates.
nemoHaMobileNetworkPrefixTable maintains per-MR mobile network prefixes at the home agent, indexed by { mip6BindingHomeAddressType, mip6BindingHomeAddress, nemoHaMobileNetworkPrefixSeqNo }. The sequence number (1..1024) distinguishes multiple prefixes in the same Binding Update.
nemoMrBLMode indicates whether the mobile router uses implicitMode(1) (no Mobile Network Prefix Option in BU) or explicitMode(2) (one or more Mobile Network Prefix Options included in BU) for a given binding.
nemoMrBLTable augments mip6MnBLEntry from MOBILEIPV6-MIB with NEMO-specific fields: nemoMrBLMode (implicit/explicit), nemoMrBLMrFlag, nemoMrBLHomeAddressPrefixLength, nemoMrBLCareofAddressPrefixLength, nemoMrBLActiveEgressIfIndex, and nemoMrBLEstablishedHomeTunnelIfIndex.
nemoMrEgressIfTable models configured egress interfaces on the mobile router, with fields for priority (0..255), textual description, and roam hold-down time (in seconds) to avoid interface flapping during roaming.
nemoMrPrefixRegMode (read-write) configures the global mode for registering mobile network prefixes with the home agent: implicitMode(1) or explicitMode(2). This setting persists across reboots.
nemoStatus (nemoSystem 2) is a read-write INTEGER { enabled(1), disabled(2) } controlling whether agent discovery and registration functions are operational. Changing from enabled to disabled terminates these functions; disabled to enabled starts them.
The NEMO MIB is organized into four primary groups: nemoCore (common objects), nemoHa (home agent service), nemoMr (mobile router service), and nemoNotifications (asynchronous event notifications). These are rooted under nemoObjects { nemoMIB 1 }.
Two SNMP notifications are defined: nemoHomeTunnelEstablished and nemoHomeTunnelReleased, sent by the mobile router whenever a home tunnel is established or deleted. Both carry egress interface index, tunnel interface index, CoA type/address, and prefix lengths.
IANA assigned OID arc mib-2 (184) for the nemoMIB module. The nemoMIB MODULE-IDENTITY is rooted at { mib-2 184 }.
The read-write objects nemoStatus and nemoMrPrefixRegMode are sensitive: unauthorized SET operations could disable NEMO functionality or disrupt mobile network prefix registration, disrupting dependent communications.
The readable objects nemoHaMobileNetworkPrefixType, nemoHaMobileNetworkPrefix, and nemoHaMobileNetworkPrefixLength reveal mobile router topology and are considered sensitive; GET and NOTIFY access should be controlled and values encrypted in transit.