RFC 6475
Proxy Mobile IPv6 Management Information Base
5.2. The Proxy Mobile IPv6 MIB
PMIPV6-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, mib-2, Integer32, Counter32, Gauge32, Unsigned32, OBJECT-TYPE, NOTIFICATION-TYPE FROM SNMPv2-SMI -- RFC 2578 PhysAddress, TimeStamp, TruthValue FROM SNMPv2-TC -- RFC 2579 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC 2580 InetAddressType, InetAddress, InetAddressPrefixLength FROM INET-ADDRESS-MIB -- RFC 4001 Ipv6AddressIfIdentifierTC FROM IP-MIB -- RFC 4293 mip6MnBLEntry, mip6BindingCacheEntry FROM MOBILEIPV6-MIB -- RFC 4295 Pmip6TimeStamp64, Pmip6MnIdentifier, Pmip6MnLLIdentifier, Pmip6MnIndex, Pmip6MnLLIndex, Pmip6MnInterfaceATT FROM PMIPV6-TC-MIB -- RFC 6475 ; pmip6MIB MODULE-IDENTITY LAST-UPDATED "201205070000Z" -- 7th May, 2012 ORGANIZATION "IETF NETLMM Working Group" CONTACT-INFO " 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"
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).
"
REVISION "201205070000Z" -- 7th May 2012
DESCRIPTION "Initial version, published as RFC 6475."
::= { mib-2 206 }
-- The PMIPv6 MIB has the following 5 primary groups
pmip6Notifications OBJECT IDENTIFIER ::= { pmip6MIB 0 }
pmip6Objects OBJECT IDENTIFIER ::= { pmip6MIB 1 }
pmip6Conformance OBJECT IDENTIFIER ::= { pmip6MIB 2 }
pmip6Core OBJECT IDENTIFIER ::= { pmip6Objects 1 }
pmip6Mag OBJECT IDENTIFIER ::= { pmip6Objects 2 }
pmip6Lma OBJECT IDENTIFIER ::= { pmip6Objects 3 }
-- The sub groups
pmip6System OBJECT IDENTIFIER ::= { pmip6Core 1 }
pmip6Bindings OBJECT IDENTIFIER ::= { pmip6Core 2 }
pmip6Conf OBJECT IDENTIFIER ::= { pmip6Core 3 }
pmip6Stats OBJECT IDENTIFIER ::= { pmip6Core 4 }
pmip6MagSystem OBJECT IDENTIFIER ::= { pmip6Mag 1 }
pmip6MagConf OBJECT IDENTIFIER ::= { pmip6Mag 2 }
pmip6MagRegistration OBJECT IDENTIFIER ::= { pmip6Mag 3 }
pmip6LmaSystem OBJECT IDENTIFIER ::= { pmip6Lma 1 }
pmip6LmaConf OBJECT IDENTIFIER ::= { pmip6Lma 2 }
-- The pmip6Stats group has the following sub groups
pmip6BindingRegCounters OBJECT IDENTIFIER ::= { pmip6Stats 1 }
--
--
-- pmip6System group
--
--
pmip6Capabilities OBJECT-TYPE
SYNTAX BITS {
mobilityAccessGateway (0),
localMobilityAnchor (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 6275: Sections 3.2, 4.1"
::= { pmip6System 1 }
pmip6MobileNodeGeneratedTimestampInUse OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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'.
"
REFERENCE
"RFC 5213: Sections 5.5, 9.3"
DEFVAL { false }
::= { pmip6Conf 1 }
pmip6FixedMagLinkLocalAddressOnAllAccessLinksType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The InetAddressType of the
pmip6FixedMagLinkLocalAddressOnAllAccessLinks
that follows.
"
::= { pmip6Conf 2 }
pmip6FixedMagLinkLocalAddressOnAllAccessLinks OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This 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."
REFERENCE
"RFC 5213: Sections 2.2, 6.8, 6.9.1.1, 6.9.3, 9.3"
::= { pmip6Conf 3 }
pmip6FixedMagLinkLayerAddressOnAllAccessLinks OBJECT-TYPE
SYNTAX PhysAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This 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.
"
REFERENCE
"RFC 5213: Sections 6.9.3, 9.3"
::= { pmip6Conf 4 }
pmip6MagStatus OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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.
"
DEFVAL { disabled }
::= { pmip6MagSystem 1 }
pmip6MagProxyCOATable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagProxyCOAEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.10"
::= { pmip6MagSystem 2 }
pmip6MagProxyCOAEntry OBJECT-TYPE
SYNTAX Pmip6MagProxyCOAEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
INDEX { pmip6MagProxyCOAType, pmip6MagProxyCOA }
::= { pmip6MagProxyCOATable 1 }
Pmip6MagProxyCOAEntry ::=
SEQUENCE {
pmip6MagProxyCOAType InetAddressType,
pmip6MagProxyCOA InetAddress,
pmip6MagProxyCOAState INTEGER
}
pmip6MagProxyCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the pmip6MagProxyCOA
that follows.
"
::= { pmip6MagProxyCOAEntry 1 }
pmip6MagProxyCOA OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.10"
::= { pmip6MagProxyCOAEntry 2 }
pmip6MagProxyCOAState OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
activated(2),
tunneled(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
::= { pmip6MagProxyCOAEntry 3 }
pmip6MagEnableMagLocalRouting OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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'.
"
REFERENCE
"RFC 5213: Section 9.2" DEFVAL { false }
::= { pmip6MagConf 1 }
pmip6MagMnIdentifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagMnIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1"
::= { pmip6MagConf 2 }
pmip6MagMnIdentifierEntry OBJECT-TYPE
SYNTAX Pmip6MagMnIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the mobile node identifier table.
"
INDEX { pmip6MagBLMnIndex
}
::= { pmip6MagMnIdentifierTable 1 }
Pmip6MagMnIdentifierEntry ::=
SEQUENCE {
pmip6MagMnIdentifier Pmip6MnIdentifier
}
pmip6MagMnIdentifier OBJECT-TYPE
SYNTAX Pmip6MnIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identity of a mobile node in the Proxy Mobile IPv6
domain.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1"
::= { pmip6MagMnIdentifierEntry 1 }
pmip6MagMnLLIdentifierTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagMnLLIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1"
::= { pmip6MagConf 3 }
pmip6MagMnLLIdentifierEntry OBJECT-TYPE
SYNTAX Pmip6MagMnLLIdentifierEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the mobile node link-layer identifier
table.
"
INDEX { pmip6MagBLMnIndex, pmip6MagBLMnLLIndex
}
::= { pmip6MagMnLLIdentifierTable 1 }
Pmip6MagMnLLIdentifierEntry ::=
SEQUENCE {
pmip6MagMnLLIdentifier Pmip6MnLLIdentifier
}
pmip6MagMnLLIdentifier OBJECT-TYPE
SYNTAX Pmip6MnLLIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The link-layer identifier of the mobile node's
connected interface on the access link.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1"
::= { pmip6MagMnLLIdentifierEntry 1 }
pmip6MagHomeNetworkPrefixTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagHomeNetworkPrefixEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table representing the home network prefixes
assigned to the connected interfaces of mobile nodes
attached to the MAG.
"
REFERENCE
"RFC 5213: Sections 2, 6.1, 6.2"
::= { pmip6MagConf 4 }
pmip6MagHomeNetworkPrefixEntry OBJECT-TYPE
SYNTAX Pmip6MagHomeNetworkPrefixEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
INDEX { pmip6MagBLMnIndex, pmip6MagBLMnLLIndex,
pmip6MagHomeNetworkPrefixType,
pmip6MagHomeNetworkPrefix }
::= { pmip6MagHomeNetworkPrefixTable 1 }
Pmip6MagHomeNetworkPrefixEntry ::=
SEQUENCE {
pmip6MagHomeNetworkPrefixType InetAddressType,
pmip6MagHomeNetworkPrefix InetAddress,
pmip6MagHomeNetworkPrefixLength InetAddressPrefixLength,
pmip6MagHomeNetworkPrefixLifeTime Unsigned32
}
pmip6MagHomeNetworkPrefixType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the pmip6MagHomeNetworkPrefix
that follows.
"
::= { pmip6MagHomeNetworkPrefixEntry 1 }
pmip6MagHomeNetworkPrefix OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Section 2"
::= { pmip6MagHomeNetworkPrefixEntry 2 }
pmip6MagHomeNetworkPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The prefix length of the home network prefix.
"
::= { pmip6MagHomeNetworkPrefixEntry 3 }
pmip6MagHomeNetworkPrefixLifeTime OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime parameter (in seconds) that will be
advertised in Router Advertisements by the MAG for
this home network prefix.
"
REFERENCE
"RFC 5213: Sections 6.2, 6.7"
::= { pmip6MagHomeNetworkPrefixEntry 4 }
pmip6MagBLTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 6275: Sections 4.5, 11.1
RFC 5213: Section 6.1"
::= { pmip6MagRegistration 1 }
pmip6MagBLEntry OBJECT-TYPE
SYNTAX Pmip6MagBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing additional information from
a Binding Update sent by the mobile access gateway
to the local mobility anchor.
"
AUGMENTS {mip6MnBLEntry}
::= { pmip6MagBLTable 1 }
Pmip6MagBLEntry ::= SEQUENCE {
pmip6MagBLFlag TruthValue,
pmip6MagBLMnIndex Pmip6MnIndex,
pmip6MagBLMnLLIndex Pmip6MnLLIndex,
pmip6MagBLMagLinkLocalAddressType InetAddressType,
pmip6MagBLMagLinkLocalAddress InetAddress,
pmip6MagBLMagIfIdentifierToMn Ipv6AddressIfIdentifierTC,
pmip6MagBLTunnelIfIdentifier Ipv6AddressIfIdentifierTC,
pmip6MagBLMnInterfaceATT Pmip6MnInterfaceATT,
pmip6MagBLTimeRecentlyAccepted Pmip6TimeStamp64
}
pmip6MagBLFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Section 8.1"
::= { pmip6MagBLEntry 1 }
pmip6MagBLMnIndex OBJECT-TYPE
SYNTAX Pmip6MnIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index to the identifier of the attached mobile
node in the pmip6MagMnIdentifierTable.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1, 8.1"
::= { pmip6MagBLEntry 2 }
pmip6MagBLMnLLIndex OBJECT-TYPE
SYNTAX Pmip6MnLLIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index to the link-layer identifier of the mobile
node's connected interface in the
pmip6MagMnLLIdentifierTable.
"
REFERENCE
"RFC 5213: Sections 2.2, 6.1, 8.1"
::= { pmip6MagBLEntry 3 }
pmip6MagBLMagLinkLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the pmip6MagBLMagLinkLocalAddress
that follows.
"
::= { pmip6MagBLEntry 4 }
pmip6MagBLMagLinkLocalAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3963: Sections 4.1, 5.1"
::= { pmip6MagBLEntry 5 }
pmip6MagBLMagIfIdentifierToMn OBJECT-TYPE
SYNTAX Ipv6AddressIfIdentifierTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 6.1, 8.1"
::= { pmip6MagBLEntry 6 }
pmip6MagBLTunnelIfIdentifier OBJECT-TYPE
SYNTAX Ipv6AddressIfIdentifierTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 6.1, 8.1"
::= { pmip6MagBLEntry 7 }
pmip6MagBLMnInterfaceATT OBJECT-TYPE
SYNTAX Pmip6MnInterfaceATT
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the access technology by which the mobile
node is currently attached to the mobile access gateway.
"
REFERENCE
"RFC 5213: Sections 6.9.1.1, 6.9.1.5, 8.1"
::= { pmip6MagBLEntry 8 }
pmip6MagBLTimeRecentlyAccepted OBJECT-TYPE
SYNTAX Pmip6TimeStamp64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.1, 8.1"
::= { pmip6MagBLEntry 9 }
pmip6MagMnProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6MagMnProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Section 6.2"
::= { pmip6MagRegistration 2 }
pmip6MagMnProfileEntry OBJECT-TYPE
SYNTAX Pmip6MagMnProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing information about the
mobile node's policy profile.
"
INDEX { pmip6MagProfMnIndex }
::= { pmip6MagMnProfileTable 1 }
Pmip6MagMnProfileEntry ::=
SEQUENCE {
pmip6MagProfMnIndex Pmip6MnIndex,
pmip6MagProfMnIdentifier Pmip6MnIdentifier,
pmip6MagProfMnLocalMobilityAnchorAddressType
InetAddressType,
pmip6MagProfMnLocalMobilityAnchorAddress InetAddress
}
pmip6MagProfMnIndex OBJECT-TYPE
SYNTAX Pmip6MnIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index for a mobile node in the Proxy Mobile IPv6
domain.
"
::= { pmip6MagMnProfileEntry 1 }
pmip6MagProfMnIdentifier OBJECT-TYPE
SYNTAX Pmip6MnIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The identity of a mobile node in the Proxy Mobile IPv6
domain.
"
REFERENCE
"RFC 5213: Section 2.2"
::= { pmip6MagMnProfileEntry 2 }
pmip6MagProfMnLocalMobilityAnchorAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the
pmip6MagMnLocalMobilityAnchorAddress that follows.
"
::= { pmip6MagMnProfileEntry 3 }
pmip6MagProfMnLocalMobilityAnchorAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Section 2.2"
::= { pmip6MagMnProfileEntry 4 }
pmip6BindingCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF Pmip6BindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 6275: Sections 4.5, 9.1, 10.1
RFC 5213: Section 5.1"
::= { pmip6Bindings 1 }
pmip6BindingCacheEntry OBJECT-TYPE
SYNTAX Pmip6BindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing additional information contained
in the Binding Cache table of the local mobility anchor.
"
AUGMENTS {mip6BindingCacheEntry}
::= { pmip6BindingCacheTable 1 }
Pmip6BindingCacheEntry ::= SEQUENCE {
pmip6BindingPBUFlag TruthValue,
pmip6BindingMnIndex Pmip6MnIndex,
pmip6BindingMnLLIndex Pmip6MnLLIndex,
pmip6BindingMagLinkLocalAddressType InetAddressType,
pmip6BindingMagLinkLocalAddress InetAddress,
pmip6BindingTunnelIfIdentifier Ipv6AddressIfIdentifierTC,
pmip6BindingMnInterfaceATT
Pmip6MnInterfaceATT,
pmip6BindingTimeRecentlyAccepted Pmip6TimeStamp64
}
pmip6BindingPBUFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.1, 8.1"
::= { pmip6BindingCacheEntry 1 }
pmip6BindingMnIndex OBJECT-TYPE
SYNTAX Pmip6MnIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An index to the identifier of the registered mobile
node.
"
REFERENCE
"RFC 5213: Sections 2.2, 5.1, 8.1
RFC 4283: Section 3"
::= { pmip6BindingCacheEntry 2 }
pmip6BindingMnLLIndex OBJECT-TYPE
SYNTAX Pmip6MnLLIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index to the link-layer identifier of the mobile
node's connected interface on the access link.
"
REFERENCE
"RFC 5213: Sections 2.2, 5.1, 8.1"
::= { pmip6BindingCacheEntry 3 }
pmip6BindingMagLinkLocalAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the
pmip6BindingMagLinkLocalAddress that follows.
"
::= { pmip6BindingCacheEntry 4 }
pmip6BindingMagLinkLocalAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.1, 6.9.1.2, 8.2"
::= { pmip6BindingCacheEntry 5 }
pmip6BindingTunnelIfIdentifier OBJECT-TYPE
SYNTAX Ipv6AddressIfIdentifierTC
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.1, 8.1"
::= { pmip6BindingCacheEntry 6 }
pmip6BindingMnInterfaceATT OBJECT-TYPE
SYNTAX Pmip6MnInterfaceATT
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.1, 8.1"
::= { pmip6BindingCacheEntry 7 }
pmip6BindingTimeRecentlyAccepted OBJECT-TYPE
SYNTAX Pmip6TimeStamp64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.1, 8.1"
::= { pmip6BindingCacheEntry 8 }
---
---
--- pmip6Stats group
---
---
--
-- pmip6Stats:pmip6BindingRegCounters
--
pmip6MissingMnIdentifierOption OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 1 }
pmip6MagNotAuthorizedForProxyReg OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 2 }
pmip6NotLMAForThisMobileNode OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 3 }
pmip6ProxyRegNotEnabled OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.3.1, 6.9.1.2, 8.9"
::= { pmip6BindingRegCounters 4 }
pmip6MissingHomeNetworkPrefixOption OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 5 }
pmip6MissingHandOffIndicatorOption OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 6 }
pmip6MissingAccessTechTypeOption OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.3.1, 8.9"
::= { pmip6BindingRegCounters 7 }
pmip6NotAuthorizedForHomeNetworkPrefix OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.3.2, 6.9.1.2, 8.9"
::= { pmip6BindingRegCounters 8 }
pmip6TimestampMismatch OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 5213: Sections 5.5, 6.9.1.2, 8.9"
::= { pmip6BindingRegCounters 9 }
(next page on part 3)
