Mobile IPv6 Management Information Base
Extracted elements (26)
All traffic counters are provided in both 32-bit (Counter32) and 64-bit (Counter64, prefixed 'HC') variants. The 64-bit versions prevent wrap-around on high-speed links where 32-bit counters would overflow too quickly for accurate monitoring.
The MIB is intentionally kept simple while meeting essential monitoring and control needs. Wherever possible, existing MIBs (IPSec MIB, Neighbor Discovery MIB, Tunnel MIB RFC 4087) are reused rather than duplicating management objects in the MOBILEIPV6-MIB.
For mip6BindingHistoryTable, if total octets in mip6BindingHstHomeAddress exceeds 112 (one fewer than the cache table limit of 113), OIDs will exceed 128 sub-identifiers and are inaccessible via SNMPv1, SNMPv2c, or SNMPv3.
If the total number of octets in mip6BindingHomeAddress exceeds 113, the OIDs of column instances in mip6BindingCacheTable will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
The MOBILEIPV6-MIB is designed to be implemented alongside the IPv6-capable IP-MIB (RFC 4293) and uses textual conventions from INET-ADDRESS-MIB (RFC 4001). These dependencies are assumed rather than optional.
The value of mip6Status SHOULD remain unchanged across reboots of the managed entity so that agent discovery and registration functions resume in the same enabled or disabled state after restart.
Correspondent node return routability counters include mip6CnHomeTestInitsRecd, mip6CnHomeTestsSent, mip6CnCareOfTestInitsRecd, and mip6CnCareOfTestsSent, tracking the four messages of the RR procedure per RFC 3775 Sections 9.4.1–9.4.4.
mip6BindingAdminStatus is a read-write object with values active(1) and inactive(2). Setting an entry to inactive suspends it and causes deletion from the cache; attempts to change the status from inactive back to active are rejected.
mip6BindingCacheTable models the Binding Cache maintained by home agents and correspondent nodes, indexed by mip6BindingHomeAddressType and mip6BindingHomeAddress. Entries are not required to survive a reboot of the managed entity.
mip6BindingHistoryTable records the history of Binding Cache entries after they expire, indexed by home address type, home address, and a monotonically increasing mip6BindingHstIndex (1..4294967295, may wrap). Its size is left to implementors.
Mip6BURequestRejectionCode is a textual convention mapping Binding Acknowledgment status codes 128–139 to named enumeration values such as reasonUnspecified, admProhibited, insufficientResource, duplicateAddressDetectionFailed, sequenceNumberOutOfWindow, expiredNonces, and registrationTypeChangeDisallowed.
mip6Capabilities is a read-only BITS object indicating which MIPv6 functions a managed entity supports: mobileNode (bit 0), homeAgent (bit 1), and correspondentNode (bit 2). Multiple functions may be indicated simultaneously.
mip6CnCounterTable provides per-mobile-node statistics at the correspondent node including BUs received, BU acks sent, and binding errors sent, indexed by the mobile node's home address.
mip6CounterDiscontinuityTime records the sysUpTime of the most recent occasion on which any global counter under mip6TotalTraffic, mip6CnGlobalStats, or mip6HaGlobalStats suffered a discontinuity; it is zero if no discontinuities have occurred since last re-initialization.
mip6HaConfTable provides per-interface configurable advertisement parameters for the home agent service: preference value, lifetime, whether to send Mobile Prefix Advertisements, whether to process Mobile Prefix Solicitations, and whether to process multicast group membership messages from mobile nodes.
mip6HaListTable lists all routers acting as home agents on each interface where the service is offered, including each home agent's global addresses via mip6HaGlAddrTable, to support management of the home agent list per RFC 3775 Section 10.1.
mip6MnBLDontSendBUFlag is set to true(1) when the mobile node receives an ICMP Parameter Problem Code 1 error in response to a return routability message or Binding Update sent to the peer, indicating that future BUs to that address should be suppressed.
mip6MnBLLifeTimeGranted enables calculation of remaining binding lifetime as lR = lG - (cT - aT), where lG is the granted lifetime, cT is current time, and aT is mip6MnBLAcceptedTime; when lR reaches zero the entry is deleted from the Binding Update List.
mip6MnBLTable models the mobile node's Binding Update List, including both correspondent and home registrations. Each entry records the node address, care-of address, lifetime requested and granted, sequence number, acceptance status, retransmission count, and a DontSendBU flag.
mip6MnHomeAddress takes the unspecified value ::0 when the mobile node has no home address assigned yet; it represents the permanent address used across all points of attachment.
MOBILEIPV6-MIB is assigned OID { mib-2 133 } and is organized into four major object groups: mip6Core (generic, common to all MIPv6 entities), mip6Mn (mobile node), mip6Cn (correspondent node), and mip6Ha (home agent), plus a mip6Notifications group for asynchronous events.
Traffic counters mip6InOctets/mip6InPkts and mip6OutOctets/mip6OutPkts (Counter32) together with 64-bit HC variants count all MIPv6 datagrams: those bearing a Mobility Header, the Home Address option (Next Header 60), the type 2 Routing Header, or tunneled/reverse-tunneled packets.
IANA assigned the MOBILEIPV6-MIB module the OID { mib-2 133 } under the mib-2 subtree. No new IANA registries are created; the assignment is recorded in the SMI Numbers registry.
Several MOBILEIPV6-MIB objects are read-write (e.g., mip6Status, mip6BindingAdminStatus, mip6HaConf objects), meaning unauthorized SNMP SET access could disable MIPv6 services or manipulate binding cache entries. The document recommends using SNMPv3 with authentication and privacy protocols to protect these objects.
The MIB exposes sensitive binding information including the mapping between a mobile node's home address and its current care-of address, which could be used to track the physical location of mobile nodes. Operators must apply appropriate SNMP access controls to read-only objects in the binding cache and history tables.
mip6MnHomeAddressState defines five states for the mobile node: unknown (indeterminate), home (on home network), registered (on foreign network, registered with HA), pending (BU sent, awaiting acknowledgment), and isolated (away from home, not registered, no ack pending).