MIBs Depot

PMIPV6-MIB

Registered at
1.3.6.1.2.1.206
Last updated
2012-05-07 00:00
Organization
IETF NETLMM Working Group
Revisions
2012-05-07 00:00
Namespace
standard
Source file
PMIPV6-MIB
Digest
sha256:44586d4ad1c4543cb1f7235880bcf91bfd02ebdc204174eb9473f0de602d888a

Description

The MIB module for monitoring and controlling PMIPv6 entities. 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).

Contact

Glenn Mansfield Keeni Postal: Cyber Solutions, Inc. 6-6-3, Minami Yoshinari Aoba-ku, Sendai 989-3204, Japan. Tel: +81-22-303-4012 Fax: +81-22-303-4015 EMail: glenn@cysols.com Kazuhide Koide Postal: KDDI Corporation GARDEN AIR TOWER 3-10-10, Iidabashi Chiyoda-ku, Tokyo 102-8460, Japan. Tel: +81-3-6678-3378 EMail: ka-koide@kddi.com Sri Gundavelli Postal: Cisco 170 W.Tasman Drive, San Jose, CA 95134 USA Tel: +1-408-527-6109 EMail: sgundave@cisco.com Ryuji Wakikawa Postal: TOYOTA InfoTechnology Center, U.S.A., Inc. 465 Bernardo Avenue Mountain View, CA 94043 USA EMail: ryuji@us.toyota-itc.com Support Group EMail: netlmm@ietf.org

Imports

FromSymbols
INET-ADDRESS-MIBInetAddress, InetAddressPrefixLength, InetAddressType
IP-MIBIpv6AddressIfIdentifierTC
MOBILEIPV6-MIBmip6BindingCacheEntry, mip6MnBLEntry
PMIPV6-TC-MIBPmip6MnIdentifier, Pmip6MnIndex, Pmip6MnInterfaceATT, Pmip6MnLLIdentifier, Pmip6MnLLIndex, Pmip6TimeStamp64
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMICounter32, Gauge32, Integer32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso, mib-2
SNMPv2-TCDisplayString, PhysAddress, TEXTUAL-CONVENTION, TimeStamp, TruthValue

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

IANAifType-MIB
IF-MIB
INET-ADDRESS-MIB
IP-MIB
MOBILEIPV6-MIB
PMIPV6-MIB
PMIPV6-TC-MIB
SNMPv2-CONF
SNMPv2-MIB
SNMPv2-SMI
SNMPv2-TC

Objects

NameOIDSyntaxAccessStatus
pmip6Notifications
OBJECT-IDENTITY
1.3.6.1.2.1.206.0
pmip6Objects
OBJECT-IDENTITY
1.3.6.1.2.1.206.1
pmip6Core
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.1
pmip6System
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.1.1
pmip6Capabilities
OBJECT-TYPE
This object indicates the PMIPv6 functions that are supported by this managed entity. Multiple Proxy Mobile IPv6 functions may be supported by a single entity. mobilityAccessGateway(0) indicates the availability of the mobility access gateway function. localMobilityAnchor(1) indicates the availability of the local mobility anchor function.
1.3.6.1.2.1.206.1.1.1.1Bits {mobilityAccessGateway(0), localMobilityAnchor(1)}read-onlycurrent
pmip6Bindings
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.1.2
pmip6BindingCacheTable
OBJECT-TYPE
This table models the Binding Cache on the local mobility anchor. Entries from the table are deleted as the lifetime of the binding expires. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.206.1.1.2.1not-accessiblecurrent
pmip6BindingCacheEntry
OBJECT-TYPE
An entry containing additional information contained in the Binding Cache table of the local mobility anchor.
1.3.6.1.2.1.206.1.1.2.1.1not-accessiblecurrent
pmip6BindingPBUFlag
OBJECT-TYPE
true(1) indicates that the local mobility anchor accepted the binding update with Proxy Registration Flag from a mobile access gateway. false(0) implies that the binding cache is from a mobile node. In this case, the remaining objects will not be accessible.
1.3.6.1.2.1.206.1.1.2.1.1.1TruthValueread-onlycurrent
pmip6BindingMnIndex
OBJECT-TYPE
An index to the identifier of the registered mobile node.
1.3.6.1.2.1.206.1.1.2.1.1.2Pmip6MnIndexread-onlycurrent
pmip6BindingMnLLIndex
OBJECT-TYPE
The index to the link-layer identifier of the mobile node's connected interface on the access link.
1.3.6.1.2.1.206.1.1.2.1.1.3Pmip6MnLLIndexread-onlycurrent
pmip6BindingMagLinkLocalAddressType
OBJECT-TYPE
The InetAddressType of the pmip6BindingMagLinkLocalAddress that follows.
1.3.6.1.2.1.206.1.1.2.1.1.4InetAddressTyperead-onlycurrent
pmip6BindingMagLinkLocalAddress
OBJECT-TYPE
The link-local address of the mobile access gateway on the point-to-point link shared with the mobile node. This is generated by the local mobility anchor after accepting the initial Proxy Binding Update message. This is the address that is present in the Link-local Address option of the corresponding Proxy Binding Acknowledgement message.
1.3.6.1.2.1.206.1.1.2.1.1.5InetAddressread-onlycurrent
pmip6BindingTunnelIfIdentifier
OBJECT-TYPE
The tunnel interface identifier (tunnel-if-id) of the bidirectional tunnel between the local mobility anchor and the mobile access gateway where the mobile node is currently anchored. This is internal to the local mobility anchor. The tunnel interface identifier is acquired during the tunnel creation.
1.3.6.1.2.1.206.1.1.2.1.1.6Ipv6AddressIfIdentifierTCread-onlycurrent
pmip6BindingMnInterfaceATT
OBJECT-TYPE
The access technology type by which the mobile node is currently attached. This is obtained from the Access Technology Type option, present in the Proxy Binding Update message.
1.3.6.1.2.1.206.1.1.2.1.1.7Pmip6MnInterfaceATTread-onlycurrent
pmip6BindingTimeRecentlyAccepted
OBJECT-TYPE
The 64-bit timestamp value of the most recently accepted Proxy Binding Update message sent for this mobile node. This is the time of day on the local mobility anchor, when the message was received. If the Timestamp option is not present in the Proxy Binding Update message (i.e., when the sequence number based scheme is in use), the value MUST be initialized with all zeroes.
1.3.6.1.2.1.206.1.1.2.1.1.8Pmip6TimeStamp64read-onlycurrent
pmip6Conf
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.1.3
pmip6MobileNodeGeneratedTimestampInUse
OBJECT-TYPE
This flag indicates whether or not the MN-generated timestamp mechanism is in use in that Proxy Mobile IPv6 domain. true(1) indicates that the local mobility anchors and mobile access gateways in that Proxy Mobile IPv6 domain apply the MN-generated timestamp considerations. false(0) indicates that the MN-generated timestamp mechanism is not in use in that Proxy Mobile IPv6 domain. The default value for this flag is 'false'.
1.3.6.1.2.1.206.1.1.3.1TruthValueread-writecurrent
pmip6FixedMagLinkLocalAddressOnAllAccessLinksType
OBJECT-TYPE
The InetAddressType of the pmip6FixedMagLinkLocalAddressOnAllAccessLinks that follows.
1.3.6.1.2.1.206.1.1.3.2InetAddressTyperead-writecurrent
pmip6Stats
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.1.4
pmip6BindingRegCounters
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.1.4.1
pmip6MissingMnIdentifierOption
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Missing mobile node identifier option' (Code 160). Discontinuities in the value of this counter can occur at re-initialization of the mobile router, and at other times as indicated by the value of pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.1Counter32read-onlycurrent
pmip6MagNotAuthorizedForProxyReg
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Not authorized to send Proxy Binding Updates' (Code 154). Discontinuities in the value of this counter can occur at re-initialization of the mobile router, and at other times as indicated by the value of pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.2Counter32read-onlycurrent
pmip6NotLMAForThisMobileNode
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Not local mobility anchor for this mobile node' (Code 153). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.3Counter32read-onlycurrent
pmip6ProxyRegNotEnabled
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Proxy Registration not enabled' (Code 152). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.4Counter32read-onlycurrent
pmip6MissingHomeNetworkPrefixOption
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Missing home network prefix option' (Code 158). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.5Counter32read-onlycurrent
pmip6MissingHandOffIndicatorOption
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Missing handoff indicator option' (Code 161). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.6Counter32read-onlycurrent
pmip6MissingAccessTechTypeOption
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Missing access technology type option' (Code 162). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.7Counter32read-onlycurrent
pmip6NotAuthorizedForHomeNetworkPrefix
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Mobile node not authorized for one or more of the requesting home network prefixes' (Code 155). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.8Counter32read-onlycurrent
pmip6TimestampMismatch
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Invalid timestamp value (the clocks are out of sync)' (Code 156). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.9Counter32read-onlycurrent
pmip6TimestampLowerThanPrevAccepted
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'The timestamp value is lower than the previously accepted value' (Code 157). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.10Counter32read-onlycurrent
pmip6BcePbuPrefixSetDoNotMatch
OBJECT-TYPE
Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'All the home network prefixes listed in the Binding Cache entry do not match all the prefixes in the received Proxy Binding Update' (Code 159). 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.11Counter32read-onlycurrent
pmip6InitialBindingRegistrations
OBJECT-TYPE
Total number of Proxy Binding Update messages that newly creates the Binding Cache entry. 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.12Counter32read-onlycurrent
pmip6BindingLifeTimeExtensionNoHandOff
OBJECT-TYPE
Total number of Proxy Binding Update messages for extending the binding lifetime, received from the same mobile access gateway that last updated the binding. 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.13Counter32read-onlycurrent
pmip6BindingLifeTimeExtensionAfterHandOff
OBJECT-TYPE
Total number of Proxy Binding Update messages for extending the binding lifetime, received from a new mobile access gateway where the mobile node's mobility session is handed off. 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.14Counter32read-onlycurrent
pmip6BindingDeRegistrations
OBJECT-TYPE
Total number of Proxy Binding Update messages with the lifetime value of zero. 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.15Counter32read-onlycurrent
pmip6BindingBindingAcks
OBJECT-TYPE
Total number of Proxy Binding Acknowledgement messages. 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 pmip6CounterDiscontinuityTime.
1.3.6.1.2.1.206.1.1.4.1.16Counter32read-onlycurrent
pmip6CounterDiscontinuityTime
OBJECT-TYPE
The value of sysUpTime on the most recent occasion at which any one or more of this PMIPv6 entity's global counters, viz., counters with OID prefix 'pmip6BindingRegCounters' 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.
1.3.6.1.2.1.206.1.1.4.1.17TimeStampread-onlycurrent
pmip6Mag
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.2
pmip6MagSystem
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.2.1
pmip6MagStatus
OBJECT-TYPE
This object indicates whether the PMIPv6 mobile access gateway function is enabled for the managed entity. Changing the status from enabled(1) to disabled(2) will terminate the PMIPv6 mobile access gateway function. On the other hand, changing the status from disabled(2) to enabled(1) will start the PMIPv6 mobile access gateway function. The value of this object MUST remain unchanged across reboots of the managed entity.
1.3.6.1.2.1.206.1.2.1.1INTEGER {enabled(1), disabled(2)}read-writecurrent
pmip6MagProxyCOATable
OBJECT-TYPE
This table models the Proxy Care-of Addresses configured on the egress interfaces of the mobile access gateway. This address is the transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.206.1.2.1.2not-accessiblecurrent
pmip6MagProxyCOAEntry
OBJECT-TYPE
This entry represents a conceptual row in the Proxy-CoA table. It represents a Proxy Care-of Address on the mobile access gateway. Implementers need to be aware that if the total number of octets in pmip6MagProxyCOA 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.
1.3.6.1.2.1.206.1.2.1.2.1not-accessiblecurrent
pmip6MagProxyCOAType
OBJECT-TYPE
The InetAddressType of the pmip6MagProxyCOA that follows.
1.3.6.1.2.1.206.1.2.1.2.1.1InetAddressTypenot-accessiblecurrent
pmip6MagProxyCOA
OBJECT-TYPE
The Proxy-CoA configured on the egress interface of the mobile access gateway. The type of the address represented by this object is specified by the corresponding pmip6MagProxyCOAType object.
1.3.6.1.2.1.206.1.2.1.2.1.2InetAddressnot-accessiblecurrent
pmip6MagProxyCOAState
OBJECT-TYPE
This object indicates the state of the Proxy-CoA: unknown -- The state of the Proxy-CoA cannot be determined. activated -- The Proxy-CoA is ready to establish a tunnel. This state SHOULD be indicated when the MAG is up but has no mobile node. tunneled -- Bidirectional tunnel is established using the Proxy-CoA.
1.3.6.1.2.1.206.1.2.1.2.1.3INTEGER {unknown(1), activated(2), tunneled(3)}read-onlycurrent
pmip6MagConf
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.2.2
pmip6MagEnableMagLocalRouting
OBJECT-TYPE
This flag indicates whether or not the mobile access gateway is allowed to enable local routing of the traffic exchanged between a visiting mobile node and a correspondent node that is locally connected to one of the interfaces of the mobile access gateway. The correspondent node can be another visiting mobile node as well, or a local fixed node. true(1) indicates that the mobile access gateway routes the traffic locally. false(0) indicates that the mobile access gateway reverse tunnels all the traffic to the mobile node's local mobility anchor. The default value for this flag is 'false'.
1.3.6.1.2.1.206.1.2.2.1TruthValueread-writecurrent
pmip6MagMnIdentifierTable
OBJECT-TYPE
A table containing the identifiers of mobile nodes attached to the MAG. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.206.1.2.2.2not-accessiblecurrent
pmip6MagMnIdentifierEntry
OBJECT-TYPE
An entry in the mobile node identifier table.
1.3.6.1.2.1.206.1.2.2.2.1not-accessiblecurrent
pmip6MagMnIdentifier
OBJECT-TYPE
The identity of a mobile node in the Proxy Mobile IPv6 domain.
1.3.6.1.2.1.206.1.2.2.2.1.1Pmip6MnIdentifierread-onlycurrent
pmip6MagMnLLIdentifierTable
OBJECT-TYPE
A table containing the link-layer identifiers of the interfaces of the mobile nodes attached to the MAG. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.206.1.2.2.3not-accessiblecurrent
pmip6MagMnLLIdentifierEntry
OBJECT-TYPE
An entry in the mobile node link-layer identifier table.
1.3.6.1.2.1.206.1.2.2.3.1not-accessiblecurrent
pmip6MagMnLLIdentifier
OBJECT-TYPE
The link-layer identifier of the mobile node's connected interface on the access link.
1.3.6.1.2.1.206.1.2.2.3.1.1Pmip6MnLLIdentifierread-onlycurrent
pmip6MagHomeNetworkPrefixTable
OBJECT-TYPE
A table representing the home network prefixes assigned to the connected interfaces of mobile nodes attached to the MAG.
1.3.6.1.2.1.206.1.2.2.4not-accessiblecurrent
pmip6MagHomeNetworkPrefixEntry
OBJECT-TYPE
An entry in the home network prefixes table. Implementers need to be aware that if the total number of octets in pmip6MagHomeNetworkPrefix exceeds 111, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.206.1.2.2.4.1not-accessiblecurrent
pmip6MagHomeNetworkPrefixType
OBJECT-TYPE
The InetAddressType of the pmip6MagHomeNetworkPrefix that follows.
1.3.6.1.2.1.206.1.2.2.4.1.1InetAddressTypenot-accessiblecurrent
pmip6MagHomeNetworkPrefix
OBJECT-TYPE
The mobile network prefix that is delegated to the mobile node. The type of the address represented by this object is specified by the corresponding pmip6MagHomeNetworkPrefixType object.
1.3.6.1.2.1.206.1.2.2.4.1.2InetAddressnot-accessiblecurrent
pmip6MagHomeNetworkPrefixLength
OBJECT-TYPE
The prefix length of the home network prefix.
1.3.6.1.2.1.206.1.2.2.4.1.3InetAddressPrefixLengthread-onlycurrent
pmip6MagHomeNetworkPrefixLifeTime
OBJECT-TYPE
The lifetime parameter (in seconds) that will be advertised in Router Advertisements by the MAG for this home network prefix.
1.3.6.1.2.1.206.1.2.2.4.1.4Unsigned32read-onlycurrent
pmip6MagRegistration
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.2.3
pmip6MagBLTable
OBJECT-TYPE
This table corresponds to the Binding Update List (BL) that includes PMIPv6-related information and is maintained by the mobile access gateway. Entries from the table are deleted as the lifetime of the binding expires.
1.3.6.1.2.1.206.1.2.3.1not-accessiblecurrent
pmip6MagBLEntry
OBJECT-TYPE
An entry containing additional information from a Binding Update sent by the mobile access gateway to the local mobility anchor.
1.3.6.1.2.1.206.1.2.3.1.1not-accessiblecurrent
pmip6MagBLFlag
OBJECT-TYPE
true(1) indicates that the mobile access gateway sent the Proxy Binding Update with Proxy Registration Flag that indicates to the local mobility anchor that the registration is the Proxy Binding Update and is from a mobile access gateway. false(0) implies that the mobile access gateway is behaving as a simple mobile node.
1.3.6.1.2.1.206.1.2.3.1.1.1TruthValueread-onlycurrent
pmip6MagBLMnIndex
OBJECT-TYPE
The index to the identifier of the attached mobile node in the pmip6MagMnIdentifierTable.
1.3.6.1.2.1.206.1.2.3.1.1.2Pmip6MnIndexread-onlycurrent
pmip6MagBLMnLLIndex
OBJECT-TYPE
The index to the link-layer identifier of the mobile node's connected interface in the pmip6MagMnLLIdentifierTable.
1.3.6.1.2.1.206.1.2.3.1.1.3Pmip6MnLLIndexread-onlycurrent
pmip6MagBLMagLinkLocalAddressType
OBJECT-TYPE
The InetAddressType of the pmip6MagBLMagLinkLocalAddress that follows.
1.3.6.1.2.1.206.1.2.3.1.1.4InetAddressTyperead-onlycurrent
pmip6MagBLMagLinkLocalAddress
OBJECT-TYPE
The link-local address of the mobile access gateway on the access link shared with the mobile node. This is the address that is present in the Link-local Address option of the corresponding Proxy Binding Update message.
1.3.6.1.2.1.206.1.2.3.1.1.5InetAddressread-onlycurrent
pmip6MagBLMagIfIdentifierToMn
OBJECT-TYPE
The interface identifier (if-id) of the point-to-point link between the mobile node and the mobile access gateway. This is internal to the mobile access gateway and is used to associate the Proxy Mobile IPv6 tunnel to the access link where the mobile node is attached.
1.3.6.1.2.1.206.1.2.3.1.1.6Ipv6AddressIfIdentifierTCread-onlycurrent
pmip6MagBLTunnelIfIdentifier
OBJECT-TYPE
The tunnel interface identifier (tunnel-if-id) of the bidirectional tunnel between the mobile node's local mobility anchor and the mobile access gateway. This is internal to the mobile access gateway. The tunnel interface identifier is acquired during the tunnel creation.
1.3.6.1.2.1.206.1.2.3.1.1.7Ipv6AddressIfIdentifierTCread-onlycurrent
pmip6MagBLMnInterfaceATT
OBJECT-TYPE
The type of the access technology by which the mobile node is currently attached to the mobile access gateway.
1.3.6.1.2.1.206.1.2.3.1.1.8Pmip6MnInterfaceATTread-onlycurrent
pmip6MagBLTimeRecentlyAccepted
OBJECT-TYPE
The 64-bit timestamp value of the most recently accepted Proxy Binding Update message sent for this mobile node. This is the time of day on the mobile access gateway, when the Proxy Binding Acknowledgement message with the Status field set to 0 was received. If the Timestamp option is not present in the Proxy Binding Update message (i.e., when the sequence-number-based scheme is in use), the value MUST be initialized with all zeroes.
1.3.6.1.2.1.206.1.2.3.1.1.9Pmip6TimeStamp64read-onlycurrent
pmip6MagMnProfileTable
OBJECT-TYPE
This table corresponds to the mobile node's policy profile that includes the essential operational parameters that are required by the network entities for managing the mobile node's mobility service. It contains policy profiles of mobile nodes that are connected to the mobile access gateway. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.206.1.2.3.2not-accessiblecurrent
pmip6MagMnProfileEntry
OBJECT-TYPE
An entry containing information about the mobile node's policy profile.
1.3.6.1.2.1.206.1.2.3.2.1not-accessiblecurrent
pmip6MagProfMnIndex
OBJECT-TYPE
The index for a mobile node in the Proxy Mobile IPv6 domain.
1.3.6.1.2.1.206.1.2.3.2.1.1Pmip6MnIndexnot-accessiblecurrent
pmip6MagProfMnIdentifier
OBJECT-TYPE
The identity of a mobile node in the Proxy Mobile IPv6 domain.
1.3.6.1.2.1.206.1.2.3.2.1.2Pmip6MnIdentifierread-onlycurrent
pmip6MagProfMnLocalMobilityAnchorAddressType
OBJECT-TYPE
The InetAddressType of the pmip6MagMnLocalMobilityAnchorAddress that follows.
1.3.6.1.2.1.206.1.2.3.2.1.3InetAddressTyperead-onlycurrent
pmip6MagProfMnLocalMobilityAnchorAddress
OBJECT-TYPE
The global address that is configured on the interface of the local mobility anchor and is the transport endpoint of the bidirectional tunnel established between the local mobility anchor and the mobile access gateway. This is the address to which the mobile access gateway sends the Proxy Binding Update messages.
1.3.6.1.2.1.206.1.2.3.2.1.4InetAddressread-onlycurrent
pmip6Lma
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.3
pmip6LmaSystem
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.3.1
pmip6LmaStatus
OBJECT-TYPE
This object indicates whether the PMIPv6 local mobility anchor function is enabled for the managed entity. Changing the status from enabled(1) to disabled(2) will terminate the PMIPv6 local mobility anchor function. On the other hand, changing the status from disabled(2) to enabled(1) will start the PMIPv6 local mobility anchor function. The value of this object MUST remain unchanged across reboots of the managed entity.
1.3.6.1.2.1.206.1.3.1.1INTEGER {enabled(1), disabled(2)}read-writecurrent
pmip6LmaLMAATable
OBJECT-TYPE
This table models the LMA Addresses configured on the local mobility anchor. Each LMA Address acts as a transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway and is the transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.206.1.3.1.2not-accessiblecurrent
pmip6LmaLMAAEntry
OBJECT-TYPE
This entry represents a conceptual row in the LMAA table. It represents each LMAA on the local mobility anchor. Implementers need to be aware that if the total number of octets in pmip6LmaLMAA 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.
1.3.6.1.2.1.206.1.3.1.2.1not-accessiblecurrent
pmip6LmaLMAAType
OBJECT-TYPE
The InetAddressType of the pmip6LmaLMAA that follows.
1.3.6.1.2.1.206.1.3.1.2.1.1InetAddressTypenot-accessiblecurrent
pmip6LmaLMAA
OBJECT-TYPE
The LMAA configured on the local mobility anchor. The type of the address represented by this object is specified by the corresponding pmip6LmaLMAAType object.
1.3.6.1.2.1.206.1.3.1.2.1.2InetAddressnot-accessiblecurrent
pmip6LmaLMAAState
OBJECT-TYPE
This object indicates the state of the LMAA: unknown -- The state of the LMAA cannot be determined. activated -- The LMAA is ready to establish a tunnel. tunneled -- The LMAA is used to set up the bidirectional tunnel.
1.3.6.1.2.1.206.1.3.1.2.1.3INTEGER {unknown(1), activated(2), tunneled(3)}read-onlycurrent
pmip6LmaConf
OBJECT-IDENTITY
1.3.6.1.2.1.206.1.3.2
pmip6LmaMinDelayBeforeBCEDelete
OBJECT-TYPE
This variable specifies the length of time in milliseconds the local mobility anchor MUST wait before it deletes a Binding Cache entry of a mobile node, upon receiving a Proxy Binding Update message from a mobile access gateway with a lifetime value of 0. During this wait time, if the local mobility anchor receives a Proxy Binding Update for the same mobility binding, with a lifetime value greater than 0, then it must update the Binding Cache entry with the accepted binding values. By the end of this wait time, if the local mobility anchor did not receive any valid Proxy Binding Update message for that mobility binding, it MUST delete the Binding Cache entry. This delay essentially ensures that a mobile node's Binding Cache entry is not deleted too quickly and allows some time for the new mobile access gateway to complete the signaling for the mobile node. The default value for this variable is 10000 milliseconds.
1.3.6.1.2.1.206.1.3.2.1Integer32 (1..65535)read-writecurrent
pmip6LmaMaxDelayBeforeNewBCEAssign
OBJECT-TYPE
This variable specifies the length of time in milliseconds the local mobility anchor MUST wait for the de-registration message for an existing mobility session before it decides to create a new mobility session. The default value for this variable is 1500 milliseconds. Note that there is a dependency between this value and the values used in the retransmission algorithm for Proxy Binding Updates. The retransmissions need to happen before MaxDelayBeforeNewBCEAssign runs out, as otherwise there are situations where a de-registration from a previous mobile access gateway may be lost, and the local mobility anchor creates, needlessly, a new mobility session and new prefixes for the mobile node. However, this affects situations where there is no information from the lower layers about the type of a handoff or other parameters that can be used for identifying the mobility session.
1.3.6.1.2.1.206.1.3.2.2Integer32 (1..65535)read-writecurrent
pmip6LmaTimestampValidityWindow
OBJECT-TYPE
This variable specifies the maximum length of time difference in milliseconds between the timestamp in the received Proxy Binding Update message and the current time of day on the local mobility anchor that is allowed by the local mobility anchor for the received message to be considered valid. The default value for this variable is 300 milliseconds. This variable must be adjusted to suit the deployments.
1.3.6.1.2.1.206.1.3.2.3Integer32 (1..65535)read-writecurrent
pmip6LmaMnIdentifierTable
OBJECT-TYPE
A table containing the identifiers of mobile nodes served by the LMA. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.206.1.3.2.4not-accessiblecurrent
pmip6LmaMnIdentifierEntry
OBJECT-TYPE
An entry in the mobile node identifier table.
1.3.6.1.2.1.206.1.3.2.4.1not-accessiblecurrent
pmip6LmaMnIdentifier
OBJECT-TYPE
The identity of a mobile node in the Proxy Mobile IPv6 domain.
1.3.6.1.2.1.206.1.3.2.4.1.1Pmip6MnIdentifierread-onlycurrent
pmip6LmaMnLLIdentifierTable
OBJECT-TYPE
A table containing the link-layer identifiers of the interfaces of the mobile nodes served by the LMA. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.206.1.3.2.5not-accessiblecurrent
pmip6LmaMnLLIdentifierEntry
OBJECT-TYPE
An entry in the mobile node link-layer identifier table.
1.3.6.1.2.1.206.1.3.2.5.1not-accessiblecurrent
pmip6LmaMnLLIdentifier
OBJECT-TYPE
The link-layer identifier of the mobile node's connected interface on the access link.
1.3.6.1.2.1.206.1.3.2.5.1.1Pmip6MnLLIdentifierread-onlycurrent
pmip6LmaHomeNetworkPrefixTable
OBJECT-TYPE
A table representing the home network prefixes assigned to the connected interfaces of all the mobile nodes anchored at the LMA.
1.3.6.1.2.1.206.1.3.2.6not-accessiblecurrent
pmip6LmaHomeNetworkPrefixEntry
OBJECT-TYPE
An entry in the home network prefixes table. Implementers need to be aware that if the total number of octets in pmip6LmaHomeNetworkPrefix exceeds 111 then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.206.1.3.2.6.1not-accessiblecurrent
pmip6LmaHomeNetworkPrefixType
OBJECT-TYPE
The InetAddressType of the pmip6LmaHomeNetworkPrefix that follows.
1.3.6.1.2.1.206.1.3.2.6.1.1InetAddressTypenot-accessiblecurrent
pmip6LmaHomeNetworkPrefix
OBJECT-TYPE
The mobile network prefix that is delegated to the mobile node. The type of the address represented by this object is specified by the corresponding pmip6LmaHomeNetworkPrefixType object.
1.3.6.1.2.1.206.1.3.2.6.1.2InetAddressnot-accessiblecurrent
pmip6LmaHomeNetworkPrefixLength
OBJECT-TYPE
The prefix length of the home network prefix.
1.3.6.1.2.1.206.1.3.2.6.1.3InetAddressPrefixLengthread-onlycurrent
pmip6LmaHomeNetworkPrefixLifeTime
OBJECT-TYPE
The lifetime (in seconds) granted to the mobile node for this registration.
1.3.6.1.2.1.206.1.3.2.6.1.4Gauge32read-writecurrent
pmip6Conformance
OBJECT-IDENTITY
1.3.6.1.2.1.206.2
pmip6Groups
OBJECT-IDENTITY
1.3.6.1.2.1.206.2.1
pmip6Compliances
OBJECT-IDENTITY
1.3.6.1.2.1.206.2.2

Notifications

NameOIDStatus
pmip6MagHomeTunnelEstablished
NOTIFICATION-TYPE
This notification is sent by the Proxy Mobile IPv6 entities every time the tunnel is established between the local mobility anchor and mobile access gateway.
1.3.6.1.2.1.206.0.1current
pmip6MagHomeTunnelReleased
NOTIFICATION-TYPE
This notification is sent by the Proxy Mobile IPv6 entities every time the tunnel between the local mobility anchor and mobile access gateway is released.
1.3.6.1.2.1.206.0.2current
pmip6LmaHomeTunnelEstablished
NOTIFICATION-TYPE
This notification is sent by the Proxy Mobile IPv6 entities every time the tunnel is established between the local mobility anchor and mobile access gateway.
1.3.6.1.2.1.206.0.3current
pmip6LmaHomeTunnelReleased
NOTIFICATION-TYPE
This notification is sent by the Proxy Mobile IPv6 entities every time the tunnel between the local mobility anchor and mobile access gateway is released.
1.3.6.1.2.1.206.0.4current

Conformance

NameOIDStatus
pmip6SystemGroup
OBJECT-GROUP
A collection of objects for basic PMIPv6 monitoring.
1.3.6.1.2.1.206.2.1.1current
pmip6BindingCacheGroup
OBJECT-GROUP
A collection of objects for monitoring the PMIPv6 extensions of the Binding Cache.
1.3.6.1.2.1.206.2.1.2current
pmip6StatsGroup
OBJECT-GROUP
A collection of objects for basic PMIPv6 statistics monitoring.
1.3.6.1.2.1.206.2.1.3current
pmip6MagSystemGroup
OBJECT-GROUP
A collection of objects for monitoring the PMIPv6-system-related objects on a mobile router.
1.3.6.1.2.1.206.2.1.4current
pmip6MagConfigurationGroup
OBJECT-GROUP
A collection of objects for monitoring the configuration-related objects on a mobile access gateway.
1.3.6.1.2.1.206.2.1.5current
pmip6MagRegistrationGroup
OBJECT-GROUP
A collection of objects for monitoring the registration-related objects on a mobile access gateway.
1.3.6.1.2.1.206.2.1.6current
pmip6LmaSystemGroup
OBJECT-GROUP
A collection of objects for monitoring the system-related objects on an LMA.
1.3.6.1.2.1.206.2.1.7current
pmip6LmaConfigurationGroup
OBJECT-GROUP
A collection of objects for Monitoring the configuration-related objects on an LMA.
1.3.6.1.2.1.206.2.1.8current
pmip6MagNotificationGroup
NOTIFICATION-GROUP
A collection of notifications from a home agent or correspondent node to the Manager about the tunnel status of the mobile router.
1.3.6.1.2.1.206.2.1.9current
pmip6LmaNotificationGroup
NOTIFICATION-GROUP
A collection of notifications from a home agent or correspondent node to the Manager about the tunnel status of the mobile router.
1.3.6.1.2.1.206.2.1.10current
pmip6CoreCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB. 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 pmip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the pmip6BindingHomeAddress -- object. --
1.3.6.1.2.1.206.2.2.1current
pmip6Compliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB.
1.3.6.1.2.1.206.2.2.2current
pmip6CoreReadOnlyCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode).
1.3.6.1.2.1.206.2.2.3current
pmip6ReadOnlyCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode).
1.3.6.1.2.1.206.2.2.4current
pmip6MagCoreCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB. 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 pmip6MagProxyCOAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOAType -- object. -- -- OBJECT pmip6MagProxyCOA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOA -- object. --
1.3.6.1.2.1.206.2.2.5current
pmip6MagCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB for monitoring configuration- related information, registration details, and statistics on a mobile access gateway. 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 pmip6MagProxyCOAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOA -- object. -- -- OBJECT pmip6MagProxyCOA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOAType -- object. -- -- OBJECT pmip6MagHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. -- -- OBJECT pmip6MagHomeNetworkPrefix -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. --
1.3.6.1.2.1.206.2.2.6current
pmip6MagCoreReadOnlyCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode). 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 pmip6MagProxyCOAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOA -- object. -- -- OBJECT pmip6MagProxyCOA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOAType -- object. -- -- OBJECT pmip6MagHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. --
1.3.6.1.2.1.206.2.2.7current
pmip6MagReadOnlyCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read- write (i.e., in read-only mode) and with support for monitoring configuration-related information, registration details, and statistics on a mobile access gateway. 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 pmip6MagProxyCOAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOA -- object. -- -- OBJECT pmip6MagProxyCOA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOAType -- object. -- -- OBJECT pmip6MagHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. -- -- OBJECT pmip6MagHomeNetworkPrefix -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. --
1.3.6.1.2.1.206.2.2.8current
pmip6LmaCoreCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB. 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 pmip6LmaLMAAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaLMAA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. --
1.3.6.1.2.1.206.2.2.9current
pmip6LmaCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB for monitoring configuration- related information, registration details, and statistics on a mobile access gateway. 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 pmip6LmaLMAAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaLMAA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6LmaHomeNetworkPrefix object. -- -- OBJECT pmip6LmaHomeNetworkPrefix -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6LmaHomeNetworkPrefix object. --
1.3.6.1.2.1.206.2.2.10current
pmip6LmaReadOnlyCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB. 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 pmip6LmaLMAAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaLMAA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. --
1.3.6.1.2.1.206.2.2.11current
pmip6LmaReadOnlyCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode) and for monitoring configuration-related information, registration details, and statistics on a mobile access gateway. 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 pmip6LmaLMAAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaLMAA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6LmaHomeNetworkPrefix object. -- -- OBJECT pmip6LmaHomeNetworkPrefix -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6LmaHomeNetworkPrefix object. --
1.3.6.1.2.1.206.2.2.12current
pmip6MagNotificationCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB and support notification from the mobile access gateway.
1.3.6.1.2.1.206.2.2.13current
pmip6LmaNotificationCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the PMIPV6-MIB and support notification from the LMA.
1.3.6.1.2.1.206.2.2.14current