Proxy Mobile IPv6 Management Information Base
Extracted elements (25)
pmip6LmaMaxDelayBeforeNewBCEAssign (default 1500 ms) has an explicit dependency on the PBU retransmission algorithm: retransmissions must complete before this window expires, otherwise a lost de-registration from a previous MAG may cause the LMA to needlessly create a new mobility session and allocate new prefixes.
The PMIPV6-MIB extends MOBILEIPV6-MIB (RFC 4295) rather than defining all objects independently, using AUGMENTS on existing binding cache and binding update list entries. This keeps the MIB as simple as possible while leveraging existing Mobile IPv6 management infrastructure.
If the total number of octets in pmip6MagProxyCOA or pmip6LmaLMAA exceeds 113, or pmip6MagHomeNetworkPrefix / pmip6LmaHomeNetworkPrefix exceeds 111, the resulting OIDs will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
For access technologies where there is no link-layer address, pmip6FixedMagLinkLayerAddressOnAllAccessLinks MUST be initialized with all zeroes.
pmip6LmaMaxDelayBeforeNewBCEAssign specifies the time (default 1500 ms) the LMA MUST wait for a de-registration from an existing session before creating a new mobility session; this value has a dependency on the PBU retransmission algorithm timing.
pmip6LmaMinDelayBeforeBCEDelete specifies the time (default 10000 ms) the LMA MUST wait before deleting a Binding Cache entry upon receiving a PBU with lifetime 0; if a valid PBU with lifetime > 0 arrives during this interval the BCE must be updated instead.
pmip6LmaTimestampValidityWindow specifies the maximum allowed clock difference (default 300 ms) between a received PBU timestamp and LMA local time; the variable must be adjusted to suit deployment needs.
pmip6MagBLTimeRecentlyAccepted and pmip6BindingTimeRecentlyAccepted MUST be initialized with all zeroes when the Timestamp option is not present in the Proxy Binding Update (i.e., when the sequence-number-based scheme is in use).
pmip6MagProxyCOAState SHOULD be reported as activated when the MAG is up but has no attached mobile node, indicating readiness to establish a tunnel.
The value of pmip6MagStatus and pmip6LmaStatus MUST remain unchanged across reboots of the managed entity, ensuring that the MAG or LMA function restarts in the same enabled/disabled state after a reboot.
pmip6BindingCacheTable augments the mip6BindingCacheEntry from MOBILEIPV6-MIB and models the LMA Binding Cache, adding PMIPv6-specific fields: PBU flag, MN index, MN link-layer index, MAG link-local address, tunnel interface identifier, access technology type, and most-recently-accepted timestamp.
pmip6Capabilities is a read-only BITS object indicating which PMIPv6 functions the managed entity supports: mobilityAccessGateway(0) and/or localMobilityAnchor(1), allowing a single device to report support for both roles simultaneously.
pmip6LmaLMAATable models LMA Addresses (LMAAs) configured on the LMA, each with address type, address, and state (unknown/activated/tunneled). Each LMAA serves as a transport endpoint for the LMA–MAG bidirectional tunnel.
pmip6MagBLTable augments mip6MnBLEntry and models the MAG Binding Update List with PMIPv6-specific fields: proxy registration flag, MN and MN-LL indices, MAG link-local address on access link, MAG interface identifier toward MN, tunnel interface identifier, access technology type, and most-recently-accepted timestamp.
pmip6MagMnProfileTable contains the policy profile of each mobile node attached to the MAG, including MN identifier and the LMA address (global address used as the Proxy Binding Update destination and tunnel transport endpoint).
pmip6MagProxyCOATable models the Proxy Care-of Addresses configured on MAG egress interfaces, each entry containing the address type, address, and state (unknown/activated/tunneled). These addresses are transport endpoints of the MAG–LMA tunnel.
Pmip6MnIdentifier is an OCTET STRING of 0–255 octets representing the stable identity of a mobile node in the PMIPv6 domain; examples include NAI and opaque application-specific identifiers (RFC 4283 Section 3).
Pmip6MnInterfaceATT is an integer enumeration of access technology types: reserved(0), logicalNetworkInterface(1), pointToPointInterface(2), ethernet(3), wirelessLan(4), wimax(5), 3GPP GERAN/UTRAN/E-UTRAN (6–8), 3GPP2 eHRPD/HRPD/1xRTT/UMB (9–12).
PMIPV6-MIB defines managed objects for monitoring and controlling PMIPv6 entities (MAG and LMA functions). It is assigned OID mib-2 206 and extends MOBILEIPV6-MIB (RFC 4295), requiring the latter to always be co-implemented.
PMIPV6-TC-MIB defines textual conventions for Proxy Mobile IPv6 management information, including Pmip6TimeStamp64, Pmip6MnIdentifier, Pmip6MnLLIdentifier, Pmip6MnIndex, Pmip6MnLLIndex, and Pmip6MnInterfaceATT. It is assigned OID mib-2 205 and is intended to be imported by PMIPv6-related MIB modules.
The pmip6BindingRegCounters group defines 17 Counter32 objects tracking PMIPv6 binding events at the LMA: rejected PBUs (codes 152–162), initial registrations, lifetime extensions (same MAG and after handoff), de-registrations, binding acknowledgements, and a discontinuity timestamp (pmip6CounterDiscontinuityTime).
IANA assigned OID mib-2 205 to the PMIPV6-TC-MIB module (Proxy Mobile IPv6 Textual Conventions MIB) and OID mib-2 206 to the PMIPV6-MIB module under the mib-2 subtree.
The PMIPV6-MIB contains read-write objects (e.g., pmip6MagStatus, pmip6LmaStatus, pmip6LmaMinDelayBeforeBCEDelete, pmip6MobileNodeGeneratedTimestampInUse) that can affect PMIPv6 entity behavior; unauthorized write access could disrupt mobility sessions or allow replay attacks via timestamp manipulation. SNMPv3 with authentication and privacy is recommended.
Both pmip6MagProxyCOAState and pmip6LmaLMAAState share three states: unknown (state cannot be determined), activated (address ready to establish a tunnel, e.g., MAG is up but has no attached mobile node), and tunneled (bidirectional tunnel is established).
Pmip6TimeStamp64 is an 8-octet fixed-point timestamp. The first 48 bits hold integer seconds since January 1, 1970 00:00 UTC; the remaining 16 bits hold 1/65536 fractions of a second. Display hint is '6d:2d'.