PMIPV6-MIB
AI MIB Summary
The PMIPV6-MIB module provides the management interface for monitoring and controlling Proxy Mobile IPv6 (PMIPv6) entities, specifically tracking Local Mobility Anchor (LMA) and Mobile Access Gateway (MAG) session states, binding cache entries, and associated traffic counters. It enables network administrators to verify PMIPv6 tunnel establishment, monitor handover events, and diagnose mobility management failures within IPv6 mobile networks.
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).
Main OID:
pmip6MIB.1.3.6.1.2.1.206
136
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
136 total| Object Name |
|---|
pmip6MIBThe 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). MODULE-IDENTITY .1.3.6.1.2.1.206 |
pmip6Notifications OBJECT IDENTIFIER .1.3.6.1.2.1.206.0 |
pmip6MagHomeTunnelEstablishedThis notification is sent by the Proxy Mobile IPv6 entities every time the tunnel is established between the local mobility anchor and mobile access gateway. NOTIFICATION-TYPE .1.3.6.1.2.1.206.0.1 |
pmip6MagHomeTunnelReleasedThis notification is sent by the Proxy Mobile IPv6 entities every time the tunnel between the local mobility anchor and mobile access gateway is released. NOTIFICATION-TYPE .1.3.6.1.2.1.206.0.2 |
pmip6LmaHomeTunnelEstablishedThis notification is sent by the Proxy Mobile IPv6 entities every time the tunnel is established between the local mobility anchor and mobile access gateway. NOTIFICATION-TYPE .1.3.6.1.2.1.206.0.3 |
pmip6LmaHomeTunnelReleasedThis notification is sent by the Proxy Mobile IPv6 entities every time the tunnel between the local mobility anchor and mobile access gateway is released. NOTIFICATION-TYPE .1.3.6.1.2.1.206.0.4 |
pmip6Objects OBJECT IDENTIFIER .1.3.6.1.2.1.206.1 |
pmip6Core OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.1 |
pmip6System OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.1.1 |
pmip6CapabilitiesThis 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.ro Bits .1.3.6.1.2.1.206.1.1.1.1 |
pmip6Bindings OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.1.2 |
pmip6BindingCacheTableThis 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. SEQUENCE OF Pmip6BindingCacheEntry .1.3.6.1.2.1.206.1.1.2.1 |
pmip6BindingCacheEntryAn entry containing additional information contained in the Binding Cache table of the local mobility anchor. Pmip6BindingCacheEntry .1.3.6.1.2.1.206.1.1.2.1.1 |
pmip6BindingPBUFlagtrue(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.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.206.1.1.2.1.1.1 |
pmip6BindingMnIndexAn index to the identifier of the registered mobile node.ro Pmip6MnIndex (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.1.2.1.1.2 |
pmip6BindingMnLLIndexThe index to the link-layer identifier of the mobile node's connected interface on the access link.ro Pmip6MnLLIndex (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.1.2.1.1.3 |
pmip6BindingMagLinkLocalAddressTypeThe InetAddressType of the pmip6BindingMagLinkLocalAddress that follows.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.1.2.1.1.4 |
pmip6BindingMagLinkLocalAddressThe 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.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.1.2.1.1.5 |
pmip6BindingTunnelIfIdentifierThe 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.ro Ipv6AddressIfIdentifierTC (IP-MIB) .1.3.6.1.2.1.206.1.1.2.1.1.6 |
pmip6BindingMnInterfaceATTThe 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.ro Pmip6MnInterfaceATT (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.1.2.1.1.7 |
pmip6BindingTimeRecentlyAcceptedThe 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.ro Pmip6TimeStamp64 (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.1.2.1.1.8 |
pmip6Conf OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.1.3 |
pmip6MobileNodeGeneratedTimestampInUseThis 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'.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.206.1.1.3.1 |
pmip6FixedMagLinkLocalAddressOnAllAccessLinksTypeThe InetAddressType of the pmip6FixedMagLinkLocalAddressOnAllAccessLinks that follows.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.1.3.2 |
pmip6FixedMagLinkLocalAddressOnAllAccessLinksThis variable indicates the link-local address value that all the mobile access gateways should use on any of the access links shared with any of the mobile nodes in that Proxy Mobile IPv6 domain. If this variable is initialized with all zeroes, it implies that the use of fixed link-local address mode is not enabled for that Proxy Mobile IPv6 domain.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.1.3.3 |
pmip6FixedMagLinkLayerAddressOnAllAccessLinksThis variable indicates the link-layer address value that all the mobile access gateways should use on any of the access links shared with any of the mobile nodes in that Proxy Mobile IPv6 domain. For access technologies where there is no link-layer address, this variable MUST be initialized with all zeroes.rw PhysAddress (SNMPv2-TC) .1.3.6.1.2.1.206.1.1.3.4 |
pmip6Stats OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.1.4 |
pmip6BindingRegCounters OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.1.4.1 |
pmip6MissingMnIdentifierOptionTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.1 |
pmip6MagNotAuthorizedForProxyRegTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.2 |
pmip6NotLMAForThisMobileNodeTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.3 |
pmip6ProxyRegNotEnabledTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.4 |
pmip6MissingHomeNetworkPrefixOptionTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.5 |
pmip6MissingHandOffIndicatorOptionTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.6 |
pmip6MissingAccessTechTypeOptionTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.7 |
pmip6NotAuthorizedForHomeNetworkPrefixTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.8 |
pmip6TimestampMismatchTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.9 |
pmip6TimestampLowerThanPrevAcceptedTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.10 |
pmip6BcePbuPrefixSetDoNotMatchTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.11 |
pmip6InitialBindingRegistrationsTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.12 |
pmip6BindingLifeTimeExtensionNoHandOffTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.13 |
pmip6BindingLifeTimeExtensionAfterHandOffTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.14 |
pmip6BindingDeRegistrationsTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.15 |
pmip6BindingBindingAcksTotal 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.ro Counter32 .1.3.6.1.2.1.206.1.1.4.1.16 |
pmip6CounterDiscontinuityTimeThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.206.1.1.4.1.17 |
pmip6Mag OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.2 |
pmip6MagSystem OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.2.1 |
pmip6MagStatusThis 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.rw Enumeration .1.3.6.1.2.1.206.1.2.1.1 |
pmip6MagProxyCOATableThis 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. SEQUENCE OF Pmip6MagProxyCOAEntry .1.3.6.1.2.1.206.1.2.1.2 |
pmip6MagProxyCOAEntryThis 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. Pmip6MagProxyCOAEntry .1.3.6.1.2.1.206.1.2.1.2.1 |
pmip6MagProxyCOATypeThe InetAddressType of the pmip6MagProxyCOA that follows. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.1.2.1.1 |
pmip6MagProxyCOAThe 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. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.1.2.1.2 |
pmip6MagProxyCOAStateThis 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.ro Enumeration .1.3.6.1.2.1.206.1.2.1.2.1.3 |
pmip6MagConf OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.2.2 |
pmip6MagEnableMagLocalRoutingThis 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'.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.206.1.2.2.1 |
pmip6MagMnIdentifierTableA 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. SEQUENCE OF Pmip6MagMnIdentifierEntry .1.3.6.1.2.1.206.1.2.2.2 |
pmip6MagMnIdentifierEntryAn entry in the mobile node identifier table. Pmip6MagMnIdentifierEntry .1.3.6.1.2.1.206.1.2.2.2.1 |
pmip6MagMnIdentifierThe identity of a mobile node in the Proxy Mobile IPv6 domain.ro Pmip6MnIdentifier (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.2.2.2.1.1 |
pmip6MagMnLLIdentifierTableA 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. SEQUENCE OF Pmip6MagMnLLIdentifierEntry .1.3.6.1.2.1.206.1.2.2.3 |
pmip6MagMnLLIdentifierEntryAn entry in the mobile node link-layer identifier table. Pmip6MagMnLLIdentifierEntry .1.3.6.1.2.1.206.1.2.2.3.1 |
pmip6MagMnLLIdentifierThe link-layer identifier of the mobile node's connected interface on the access link.ro Pmip6MnLLIdentifier (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.2.2.3.1.1 |
pmip6MagHomeNetworkPrefixTableA table representing the home network prefixes assigned to the connected interfaces of mobile nodes attached to the MAG. SEQUENCE OF Pmip6MagHomeNetworkPrefixEntry .1.3.6.1.2.1.206.1.2.2.4 |
pmip6MagHomeNetworkPrefixEntryAn 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. Pmip6MagHomeNetworkPrefixEntry .1.3.6.1.2.1.206.1.2.2.4.1 |
pmip6MagHomeNetworkPrefixTypeThe InetAddressType of the pmip6MagHomeNetworkPrefix that follows. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.2.4.1.1 |
pmip6MagHomeNetworkPrefixThe 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. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.2.4.1.2 |
pmip6MagHomeNetworkPrefixLengthThe prefix length of the home network prefix.ro InetAddressPrefixLength (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.2.4.1.3 |
pmip6MagHomeNetworkPrefixLifeTimeThe lifetime parameter (in seconds) that will be advertised in Router Advertisements by the MAG for this home network prefix.ro Unsigned32 UNITS "seconds" .1.3.6.1.2.1.206.1.2.2.4.1.4 |
pmip6MagRegistration OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.2.3 |
pmip6MagBLTableThis 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. SEQUENCE OF Pmip6MagBLEntry .1.3.6.1.2.1.206.1.2.3.1 |
pmip6MagBLEntryAn entry containing additional information from a Binding Update sent by the mobile access gateway to the local mobility anchor. Pmip6MagBLEntry .1.3.6.1.2.1.206.1.2.3.1.1 |
pmip6MagBLFlagtrue(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.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.206.1.2.3.1.1.1 |
pmip6MagBLMnIndexThe index to the identifier of the attached mobile node in the pmip6MagMnIdentifierTable.ro Pmip6MnIndex (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.2.3.1.1.2 |
pmip6MagBLMnLLIndexThe index to the link-layer identifier of the mobile node's connected interface in the pmip6MagMnLLIdentifierTable.ro Pmip6MnLLIndex (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.2.3.1.1.3 |
pmip6MagBLMagLinkLocalAddressTypeThe InetAddressType of the pmip6MagBLMagLinkLocalAddress that follows.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.3.1.1.4 |
pmip6MagBLMagLinkLocalAddressThe 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.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.3.1.1.5 |
pmip6MagBLMagIfIdentifierToMnThe 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.ro Ipv6AddressIfIdentifierTC (IP-MIB) .1.3.6.1.2.1.206.1.2.3.1.1.6 |
pmip6MagBLTunnelIfIdentifierThe 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.ro Ipv6AddressIfIdentifierTC (IP-MIB) .1.3.6.1.2.1.206.1.2.3.1.1.7 |
pmip6MagBLMnInterfaceATTThe type of the access technology by which the mobile node is currently attached to the mobile access gateway.ro Pmip6MnInterfaceATT (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.2.3.1.1.8 |
pmip6MagBLTimeRecentlyAcceptedThe 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.ro Pmip6TimeStamp64 (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.2.3.1.1.9 |
pmip6MagMnProfileTableThis 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. SEQUENCE OF Pmip6MagMnProfileEntry .1.3.6.1.2.1.206.1.2.3.2 |
pmip6MagMnProfileEntryAn entry containing information about the mobile node's policy profile. Pmip6MagMnProfileEntry .1.3.6.1.2.1.206.1.2.3.2.1 |
pmip6MagProfMnIndexThe index for a mobile node in the Proxy Mobile IPv6 domain. Pmip6MnIndex (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.2.3.2.1.1 |
pmip6MagProfMnIdentifierThe identity of a mobile node in the Proxy Mobile IPv6 domain.ro Pmip6MnIdentifier (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.2.3.2.1.2 |
pmip6MagProfMnLocalMobilityAnchorAddressTypeThe InetAddressType of the pmip6MagMnLocalMobilityAnchorAddress that follows.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.3.2.1.3 |
pmip6MagProfMnLocalMobilityAnchorAddressThe 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.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.2.3.2.1.4 |
pmip6Lma OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.3 |
pmip6LmaSystem OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.3.1 |
pmip6LmaStatusThis 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.rw Enumeration .1.3.6.1.2.1.206.1.3.1.1 |
pmip6LmaLMAATableThis 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. SEQUENCE OF Pmip6LmaLMAAEntry .1.3.6.1.2.1.206.1.3.1.2 |
pmip6LmaLMAAEntryThis 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. Pmip6LmaLMAAEntry .1.3.6.1.2.1.206.1.3.1.2.1 |
pmip6LmaLMAATypeThe InetAddressType of the pmip6LmaLMAA that follows. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.3.1.2.1.1 |
pmip6LmaLMAAThe LMAA configured on the local mobility anchor. The type of the address represented by this object is specified by the corresponding pmip6LmaLMAAType object. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.3.1.2.1.2 |
pmip6LmaLMAAStateThis 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.ro Enumeration .1.3.6.1.2.1.206.1.3.1.2.1.3 |
pmip6LmaConf OBJECT IDENTIFIER .1.3.6.1.2.1.206.1.3.2 |
pmip6LmaMinDelayBeforeBCEDeleteThis 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.rw Integer32 .1.3.6.1.2.1.206.1.3.2.1 |
pmip6LmaMaxDelayBeforeNewBCEAssignThis 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.rw Integer32 .1.3.6.1.2.1.206.1.3.2.2 |
pmip6LmaTimestampValidityWindowThis 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.rw Integer32 .1.3.6.1.2.1.206.1.3.2.3 |
pmip6LmaMnIdentifierTableA 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. SEQUENCE OF Pmip6LmaMnIdentifierEntry .1.3.6.1.2.1.206.1.3.2.4 |
pmip6LmaMnIdentifierEntryAn entry in the mobile node identifier table. Pmip6LmaMnIdentifierEntry .1.3.6.1.2.1.206.1.3.2.4.1 |
pmip6LmaMnIdentifierThe identity of a mobile node in the Proxy Mobile IPv6 domain.ro Pmip6MnIdentifier (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.3.2.4.1.1 |
pmip6LmaMnLLIdentifierTableA 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. SEQUENCE OF Pmip6LmaMnLLIdentifierEntry .1.3.6.1.2.1.206.1.3.2.5 |
pmip6LmaMnLLIdentifierEntryAn entry in the mobile node link-layer identifier table. Pmip6LmaMnLLIdentifierEntry .1.3.6.1.2.1.206.1.3.2.5.1 |
pmip6LmaMnLLIdentifierThe link-layer identifier of the mobile node's connected interface on the access link.ro Pmip6MnLLIdentifier (PMIPV6-TC-MIB) .1.3.6.1.2.1.206.1.3.2.5.1.1 |
pmip6LmaHomeNetworkPrefixTableA table representing the home network prefixes assigned to the connected interfaces of all the mobile nodes anchored at the LMA. SEQUENCE OF Pmip6LmaHomeNetworkPrefixEntry .1.3.6.1.2.1.206.1.3.2.6 |
pmip6LmaHomeNetworkPrefixEntryAn 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. Pmip6LmaHomeNetworkPrefixEntry .1.3.6.1.2.1.206.1.3.2.6.1 |
pmip6LmaHomeNetworkPrefixTypeThe InetAddressType of the pmip6LmaHomeNetworkPrefix that follows. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.3.2.6.1.1 |
pmip6LmaHomeNetworkPrefixThe 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. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.3.2.6.1.2 |
pmip6LmaHomeNetworkPrefixLengthThe prefix length of the home network prefix.ro InetAddressPrefixLength (INET-ADDRESS-MIB) .1.3.6.1.2.1.206.1.3.2.6.1.3 |
pmip6LmaHomeNetworkPrefixLifeTimeThe lifetime (in seconds) granted to the mobile node for this registration.rw Gauge32 UNITS "seconds" .1.3.6.1.2.1.206.1.3.2.6.1.4 |
pmip6Conformance OBJECT IDENTIFIER .1.3.6.1.2.1.206.2 |
pmip6Groups OBJECT IDENTIFIER .1.3.6.1.2.1.206.2.1 |
pmip6SystemGroupA collection of objects for basic PMIPv6 monitoring. Unknown .1.3.6.1.2.1.206.2.1.1 |
pmip6BindingCacheGroupA collection of objects for monitoring the PMIPv6 extensions of the Binding Cache. Unknown .1.3.6.1.2.1.206.2.1.2 |
pmip6StatsGroupA collection of objects for basic PMIPv6 statistics monitoring. Unknown .1.3.6.1.2.1.206.2.1.3 |
pmip6MagSystemGroupA collection of objects for monitoring the PMIPv6-system-related objects on a mobile router. Unknown .1.3.6.1.2.1.206.2.1.4 |
pmip6MagConfigurationGroupA collection of objects for monitoring the configuration-related objects on a mobile access gateway. Unknown .1.3.6.1.2.1.206.2.1.5 |
pmip6MagRegistrationGroupA collection of objects for monitoring the registration-related objects on a mobile access gateway. Unknown .1.3.6.1.2.1.206.2.1.6 |
pmip6LmaSystemGroupA collection of objects for monitoring the system-related objects on an LMA. Unknown .1.3.6.1.2.1.206.2.1.7 |
pmip6LmaConfigurationGroupA collection of objects for Monitoring the configuration-related objects on an LMA. Unknown .1.3.6.1.2.1.206.2.1.8 |
pmip6MagNotificationGroupA collection of notifications from a home agent or correspondent node to the Manager about the tunnel status of the mobile router. Unknown .1.3.6.1.2.1.206.2.1.9 |
pmip6LmaNotificationGroupA collection of notifications from a home agent or correspondent node to the Manager about the tunnel status of the mobile router. Unknown .1.3.6.1.2.1.206.2.1.10 |
pmip6Compliances OBJECT IDENTIFIER .1.3.6.1.2.1.206.2.2 |
pmip6CoreComplianceThe 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. -- Unknown .1.3.6.1.2.1.206.2.2.1 |
pmip6Compliance2The compliance statement for SNMP entities that implement the PMIPV6-MIB. Unknown .1.3.6.1.2.1.206.2.2.2 |
pmip6CoreReadOnlyComplianceThe compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode). Unknown .1.3.6.1.2.1.206.2.2.3 |
pmip6ReadOnlyCompliance2The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode). Unknown .1.3.6.1.2.1.206.2.2.4 |
pmip6MagCoreComplianceThe 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. -- Unknown .1.3.6.1.2.1.206.2.2.5 |
pmip6MagCompliance2The 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. -- Unknown .1.3.6.1.2.1.206.2.2.6 |
pmip6MagCoreReadOnlyComplianceThe 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. -- Unknown .1.3.6.1.2.1.206.2.2.7 |
pmip6MagReadOnlyCompliance2The 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. -- Unknown .1.3.6.1.2.1.206.2.2.8 |
pmip6LmaCoreComplianceThe 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. -- Unknown .1.3.6.1.2.1.206.2.2.9 |
pmip6LmaCompliance2The 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. -- Unknown .1.3.6.1.2.1.206.2.2.10 |
pmip6LmaReadOnlyComplianceThe 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. -- Unknown .1.3.6.1.2.1.206.2.2.11 |
pmip6LmaReadOnlyCompliance2The 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. -- Unknown .1.3.6.1.2.1.206.2.2.12 |
pmip6MagNotificationComplianceThe compliance statement for SNMP entities that implement the PMIPV6-MIB and support notification from the mobile access gateway. Unknown .1.3.6.1.2.1.206.2.2.13 |
pmip6LmaNotificationComplianceThe compliance statement for SNMP entities that implement the PMIPV6-MIB and support notification from the LMA. Unknown .1.3.6.1.2.1.206.2.2.14 |