PMIPV6-MIB
File:
PMIPV6-MIB.mib (89341 bytes)
Imported modules
Imported symbols
Defined Types
| Pmip6MagProxyCOAEntry |
|
| SEQUENCE |
|
|
|
| |
pmip6MagProxyCOAType |
InetAddressType |
|
| |
pmip6MagProxyCOA |
InetAddress |
|
| |
pmip6MagProxyCOAState |
INTEGER |
|
| Pmip6MagHomeNetworkPrefixEntry |
|
| SEQUENCE |
|
|
|
| |
pmip6MagHomeNetworkPrefixType |
InetAddressType |
|
| |
pmip6MagHomeNetworkPrefix |
InetAddress |
|
| |
pmip6MagHomeNetworkPrefixLength |
InetAddressPrefixLength |
|
| |
pmip6MagHomeNetworkPrefixLifeTime |
Unsigned32 |
|
| Pmip6MagBLEntry |
|
| SEQUENCE |
|
|
|
| |
pmip6MagBLFlag |
TruthValue |
|
| |
pmip6MagBLMnIndex |
Pmip6MnIndex |
|
| |
pmip6MagBLMnLLIndex |
Pmip6MnLLIndex |
|
| |
pmip6MagBLMagLinkLocalAddressType |
InetAddressType |
|
| |
pmip6MagBLMagLinkLocalAddress |
InetAddress |
|
| |
pmip6MagBLMagIfIdentifierToMn |
Ipv6AddressIfIdentifierTC |
|
| |
pmip6MagBLTunnelIfIdentifier |
Ipv6AddressIfIdentifierTC |
|
| |
pmip6MagBLMnInterfaceATT |
Pmip6MnInterfaceATT |
|
| |
pmip6MagBLTimeRecentlyAccepted |
Pmip6TimeStamp64 |
|
| Pmip6MagMnProfileEntry |
|
| SEQUENCE |
|
|
|
| |
pmip6MagProfMnIndex |
Pmip6MnIndex |
|
| |
pmip6MagProfMnIdentifier |
Pmip6MnIdentifier |
|
| |
pmip6MagProfMnLocalMobilityAnchorAddressType |
InetAddressType |
|
| |
pmip6MagProfMnLocalMobilityAnchorAddress |
InetAddress |
|
| Pmip6BindingCacheEntry |
|
| SEQUENCE |
|
|
|
| |
pmip6BindingPBUFlag |
TruthValue |
|
| |
pmip6BindingMnIndex |
Pmip6MnIndex |
|
| |
pmip6BindingMnLLIndex |
Pmip6MnLLIndex |
|
| |
pmip6BindingMagLinkLocalAddressType |
InetAddressType |
|
| |
pmip6BindingMagLinkLocalAddress |
InetAddress |
|
| |
pmip6BindingTunnelIfIdentifier |
Ipv6AddressIfIdentifierTC |
|
| |
pmip6BindingMnInterfaceATT |
Pmip6MnInterfaceATT |
|
| |
pmip6BindingTimeRecentlyAccepted |
Pmip6TimeStamp64 |
|
| Pmip6LmaLMAAEntry |
|
| SEQUENCE |
|
|
|
| |
pmip6LmaLMAAType |
InetAddressType |
|
| |
pmip6LmaLMAA |
InetAddress |
|
| |
pmip6LmaLMAAState |
INTEGER |
|
| Pmip6LmaHomeNetworkPrefixEntry |
|
| SEQUENCE |
|
|
|
| |
pmip6LmaHomeNetworkPrefixType |
InetAddressType |
|
| |
pmip6LmaHomeNetworkPrefix |
InetAddress |
|
| |
pmip6LmaHomeNetworkPrefixLength |
InetAddressPrefixLength |
|
| |
pmip6LmaHomeNetworkPrefixLifeTime |
Gauge32 |
|
Defined Values
| pmip6MIB |
1.3.6.1.2.1.206 |
| 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).
|
| MODULE-IDENTITY |
|
|
|
| pmip6Core |
1.3.6.1.2.1.206.1.1 |
| OBJECT IDENTIFIER |
|
|
|
| pmip6Mag |
1.3.6.1.2.1.206.1.2 |
| OBJECT IDENTIFIER |
|
|
|
| pmip6Lma |
1.3.6.1.2.1.206.1.3 |
| OBJECT IDENTIFIER |
|
|
|
| pmip6Conf |
1.3.6.1.2.1.206.1.1.3 |
| OBJECT IDENTIFIER |
|
|
|
| pmip6Stats |
1.3.6.1.2.1.206.1.1.4 |
| OBJECT IDENTIFIER |
|
|
|
| pmip6Capabilities |
1.3.6.1.2.1.206.1.1.1.1 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
BITS |
mobilityAccessGateway(0), localMobilityAnchor(1) |
|
| pmip6MobileNodeGeneratedTimestampInUse |
1.3.6.1.2.1.206.1.1.3.1 |
| 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'.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| pmip6FixedMagLinkLocalAddressOnAllAccessLinks |
1.3.6.1.2.1.206.1.1.3.3 |
| 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. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| pmip6FixedMagLinkLayerAddressOnAllAccessLinks |
1.3.6.1.2.1.206.1.1.3.4 |
| 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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
PhysAddress |
|
|
| pmip6MagStatus |
1.3.6.1.2.1.206.1.2.1.1 |
| 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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enabled(1), disabled(2) |
|
| pmip6MagProxyCOATable |
1.3.6.1.2.1.206.1.2.1.2 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6MagProxyCOAEntry |
|
| pmip6MagProxyCOAEntry |
1.3.6.1.2.1.206.1.2.1.2.1 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MagProxyCOAEntry |
|
|
| pmip6MagProxyCOA |
1.3.6.1.2.1.206.1.2.1.2.1.2 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| pmip6MagProxyCOAState |
1.3.6.1.2.1.206.1.2.1.2.1.3 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), activated(2), tunneled(3) |
|
| pmip6MagEnableMagLocalRouting |
1.3.6.1.2.1.206.1.2.2.1 |
| 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'.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| pmip6MagMnIdentifierTable |
1.3.6.1.2.1.206.1.2.2.2 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6MagMnIdentifierEntry |
|
| pmip6MagMnIdentifierEntry |
1.3.6.1.2.1.206.1.2.2.2.1 |
| An entry in the mobile node identifier table.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MagMnIdentifierEntry |
|
|
| pmip6MagMnLLIdentifierTable |
1.3.6.1.2.1.206.1.2.2.3 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6MagMnLLIdentifierEntry |
|
| pmip6MagMnLLIdentifierEntry |
1.3.6.1.2.1.206.1.2.2.3.1 |
| An entry in the mobile node link-layer identifier
table.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MagMnLLIdentifierEntry |
|
|
| pmip6MagHomeNetworkPrefixEntry |
1.3.6.1.2.1.206.1.2.2.4.1 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MagHomeNetworkPrefixEntry |
|
|
| pmip6MagHomeNetworkPrefix |
1.3.6.1.2.1.206.1.2.2.4.1.2 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| pmip6MagHomeNetworkPrefixLifeTime |
1.3.6.1.2.1.206.1.2.2.4.1.4 |
| The lifetime parameter (in seconds) that will be
advertised in Router Advertisements by the MAG for
this home network prefix.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| pmip6MagBLTable |
1.3.6.1.2.1.206.1.2.3.1 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6MagBLEntry |
|
| pmip6MagBLEntry |
1.3.6.1.2.1.206.1.2.3.1.1 |
| An entry containing additional information from
a Binding Update sent by the mobile access gateway
to the local mobility anchor.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MagBLEntry |
|
|
| pmip6MagBLFlag |
1.3.6.1.2.1.206.1.2.3.1.1.1 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| pmip6MagBLMnIndex |
1.3.6.1.2.1.206.1.2.3.1.1.2 |
| The index to the identifier of the attached mobile
node in the pmip6MagMnIdentifierTable.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MnIndex |
|
|
| pmip6MagBLMnLLIndex |
1.3.6.1.2.1.206.1.2.3.1.1.3 |
| The index to the link-layer identifier of the mobile
node's connected interface in the
pmip6MagMnLLIdentifierTable.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MnLLIndex |
|
|
| pmip6MagBLMagLinkLocalAddress |
1.3.6.1.2.1.206.1.2.3.1.1.5 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| pmip6MagBLMagIfIdentifierToMn |
1.3.6.1.2.1.206.1.2.3.1.1.6 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Ipv6AddressIfIdentifierTC |
|
|
| pmip6MagBLTunnelIfIdentifier |
1.3.6.1.2.1.206.1.2.3.1.1.7 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Ipv6AddressIfIdentifierTC |
|
|
| pmip6MagBLMnInterfaceATT |
1.3.6.1.2.1.206.1.2.3.1.1.8 |
| The type of the access technology by which the mobile
node is currently attached to the mobile access gateway.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MnInterfaceATT |
|
|
| pmip6MagBLTimeRecentlyAccepted |
1.3.6.1.2.1.206.1.2.3.1.1.9 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Pmip6TimeStamp64 |
|
|
| pmip6MagMnProfileTable |
1.3.6.1.2.1.206.1.2.3.2 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6MagMnProfileEntry |
|
| pmip6MagMnProfileEntry |
1.3.6.1.2.1.206.1.2.3.2.1 |
| An entry containing information about the
mobile node's policy profile.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MagMnProfileEntry |
|
|
| pmip6MagProfMnIndex |
1.3.6.1.2.1.206.1.2.3.2.1.1 |
| The index for a mobile node in the Proxy Mobile IPv6
domain.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MnIndex |
|
|
| pmip6MagProfMnLocalMobilityAnchorAddress |
1.3.6.1.2.1.206.1.2.3.2.1.4 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| pmip6BindingCacheTable |
1.3.6.1.2.1.206.1.1.2.1 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6BindingCacheEntry |
|
| pmip6BindingCacheEntry |
1.3.6.1.2.1.206.1.1.2.1.1 |
| An entry containing additional information contained
in the Binding Cache table of the local mobility anchor.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6BindingCacheEntry |
|
|
| pmip6BindingPBUFlag |
1.3.6.1.2.1.206.1.1.2.1.1.1 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| pmip6BindingMnIndex |
1.3.6.1.2.1.206.1.1.2.1.1.2 |
| An index to the identifier of the registered mobile
node.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MnIndex |
|
|
| pmip6BindingMnLLIndex |
1.3.6.1.2.1.206.1.1.2.1.1.3 |
| The index to the link-layer identifier of the mobile
node's connected interface on the access link.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MnLLIndex |
|
|
| pmip6BindingMagLinkLocalAddress |
1.3.6.1.2.1.206.1.1.2.1.1.5 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| pmip6BindingTunnelIfIdentifier |
1.3.6.1.2.1.206.1.1.2.1.1.6 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Ipv6AddressIfIdentifierTC |
|
|
| pmip6BindingMnInterfaceATT |
1.3.6.1.2.1.206.1.1.2.1.1.7 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Pmip6MnInterfaceATT |
|
|
| pmip6BindingTimeRecentlyAccepted |
1.3.6.1.2.1.206.1.1.2.1.1.8 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Pmip6TimeStamp64 |
|
|
| pmip6MissingMnIdentifierOption |
1.3.6.1.2.1.206.1.1.4.1.1 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6MagNotAuthorizedForProxyReg |
1.3.6.1.2.1.206.1.1.4.1.2 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6NotLMAForThisMobileNode |
1.3.6.1.2.1.206.1.1.4.1.3 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6ProxyRegNotEnabled |
1.3.6.1.2.1.206.1.1.4.1.4 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6MissingHomeNetworkPrefixOption |
1.3.6.1.2.1.206.1.1.4.1.5 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6MissingHandOffIndicatorOption |
1.3.6.1.2.1.206.1.1.4.1.6 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6MissingAccessTechTypeOption |
1.3.6.1.2.1.206.1.1.4.1.7 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6NotAuthorizedForHomeNetworkPrefix |
1.3.6.1.2.1.206.1.1.4.1.8 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6TimestampMismatch |
1.3.6.1.2.1.206.1.1.4.1.9 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6TimestampLowerThanPrevAccepted |
1.3.6.1.2.1.206.1.1.4.1.10 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6BcePbuPrefixSetDoNotMatch |
1.3.6.1.2.1.206.1.1.4.1.11 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6InitialBindingRegistrations |
1.3.6.1.2.1.206.1.1.4.1.12 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6BindingLifeTimeExtensionNoHandOff |
1.3.6.1.2.1.206.1.1.4.1.13 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6BindingLifeTimeExtensionAfterHandOff |
1.3.6.1.2.1.206.1.1.4.1.14 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6BindingDeRegistrations |
1.3.6.1.2.1.206.1.1.4.1.15 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6BindingBindingAcks |
1.3.6.1.2.1.206.1.1.4.1.16 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| pmip6CounterDiscontinuityTime |
1.3.6.1.2.1.206.1.1.4.1.17 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TimeStamp |
|
|
| pmip6LmaStatus |
1.3.6.1.2.1.206.1.3.1.1 |
| 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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enabled(1), disabled(2) |
|
| pmip6LmaLMAATable |
1.3.6.1.2.1.206.1.3.1.2 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6LmaLMAAEntry |
|
| pmip6LmaLMAAEntry |
1.3.6.1.2.1.206.1.3.1.2.1 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6LmaLMAAEntry |
|
|
| pmip6LmaLMAAType |
1.3.6.1.2.1.206.1.3.1.2.1.1 |
| The InetAddressType of the pmip6LmaLMAA
that follows.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InetAddressType |
|
|
| pmip6LmaLMAA |
1.3.6.1.2.1.206.1.3.1.2.1.2 |
| The LMAA configured on the local mobility anchor.
The type of the address represented by this object
is specified by the corresponding
pmip6LmaLMAAType object.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| pmip6LmaLMAAState |
1.3.6.1.2.1.206.1.3.1.2.1.3 |
| 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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), activated(2), tunneled(3) |
|
| pmip6LmaMinDelayBeforeBCEDelete |
1.3.6.1.2.1.206.1.3.2.1 |
| 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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
1..65535 |
|
| pmip6LmaMaxDelayBeforeNewBCEAssign |
1.3.6.1.2.1.206.1.3.2.2 |
| 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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
1..65535 |
|
| pmip6LmaTimestampValidityWindow |
1.3.6.1.2.1.206.1.3.2.3 |
| 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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
1..65535 |
|
| pmip6LmaMnIdentifierTable |
1.3.6.1.2.1.206.1.3.2.4 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6LmaMnIdentifierEntry |
|
| pmip6LmaMnIdentifierEntry |
1.3.6.1.2.1.206.1.3.2.4.1 |
| An entry in the mobile node identifier table.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6LmaMnIdentifierEntry |
|
|
| pmip6LmaMnLLIdentifierTable |
1.3.6.1.2.1.206.1.3.2.5 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Pmip6LmaMnLLIdentifierEntry |
|
| pmip6LmaMnLLIdentifierEntry |
1.3.6.1.2.1.206.1.3.2.5.1 |
| An entry in the mobile node link-layer identifier
table.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6LmaMnLLIdentifierEntry |
|
|
| pmip6LmaHomeNetworkPrefixEntry |
1.3.6.1.2.1.206.1.3.2.6.1 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Pmip6LmaHomeNetworkPrefixEntry |
|
|
| pmip6LmaHomeNetworkPrefix |
1.3.6.1.2.1.206.1.3.2.6.1.2 |
| 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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| pmip6MagHomeTunnelEstablished |
1.3.6.1.2.1.206.0.1 |
| 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.
|
| Status: current |
Access: read-write |
| NOTIFICATION-TYPE |
|
|
|
| pmip6MagHomeTunnelReleased |
1.3.6.1.2.1.206.0.2 |
| 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.
|
| Status: current |
Access: read-write |
| NOTIFICATION-TYPE |
|
|
|
| pmip6LmaHomeTunnelEstablished |
1.3.6.1.2.1.206.0.3 |
| 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.
|
| Status: current |
Access: read-write |
| NOTIFICATION-TYPE |
|
|
|
| pmip6LmaHomeTunnelReleased |
1.3.6.1.2.1.206.0.4 |
| 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.
|
| Status: current |
Access: read-write |
| NOTIFICATION-TYPE |
|
|
|
| pmip6SystemGroup |
1.3.6.1.2.1.206.2.1.1 |
| A collection of objects for basic PMIPv6
monitoring. |
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| pmip6BindingCacheGroup |
1.3.6.1.2.1.206.2.1.2 |
| A collection of objects for monitoring the
PMIPv6 extensions of the Binding Cache. |
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| pmip6StatsGroup |
1.3.6.1.2.1.206.2.1.3 |
| A collection of objects for basic PMIPv6
statistics monitoring.
|
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| pmip6MagSystemGroup |
1.3.6.1.2.1.206.2.1.4 |
| A collection of objects for monitoring the
PMIPv6-system-related objects on a mobile router. |
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| pmip6MagConfigurationGroup |
1.3.6.1.2.1.206.2.1.5 |
| A collection of objects for monitoring the
configuration-related objects on a mobile access
gateway.
|
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| pmip6MagRegistrationGroup |
1.3.6.1.2.1.206.2.1.6 |
| A collection of objects for monitoring the
registration-related objects on a mobile access
gateway.
|
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| pmip6LmaSystemGroup |
1.3.6.1.2.1.206.2.1.7 |
| A collection of objects for monitoring the
system-related objects on an LMA. |
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| pmip6LmaConfigurationGroup |
1.3.6.1.2.1.206.2.1.8 |
| A collection of objects for Monitoring the
configuration-related objects on an LMA. |
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| pmip6MagNotificationGroup |
1.3.6.1.2.1.206.2.1.9 |
| A collection of notifications from a home agent
or correspondent node to the Manager about the
tunnel status of the mobile router.
|
| Status: current |
Access: read-write |
| NOTIFICATION-GROUP |
|
|
|
| pmip6LmaNotificationGroup |
1.3.6.1.2.1.206.2.1.10 |
| A collection of notifications from a home agent
or correspondent node to the Manager about the
tunnel status of the mobile router.
|
| Status: current |
Access: read-write |
| NOTIFICATION-GROUP |
|
|
|
| pmip6CoreCompliance |
1.3.6.1.2.1.206.2.2.1 |
| 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.
--
|
| Status: current |
Access: read-write |
| MODULE-COMPLIANCE |
|
|
|
| pmip6Compliance2 |
1.3.6.1.2.1.206.2.2.2 |
| The compliance statement for SNMP entities
that implement the PMIPV6-MIB.
|
| Status: current |
Access: read-write |
| MODULE-COMPLIANCE |
|
|
|
| pmip6CoreReadOnlyCompliance |
1.3.6.1.2.1.206.2.2.3 |
| The compliance statement for SNMP entities
that implement the PMIPV6-MIB without support
for read-write (i.e., in read-only mode).
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6ReadOnlyCompliance2 |
1.3.6.1.2.1.206.2.2.4 |
| The compliance statement for SNMP entities
that implement the PMIPV6-MIB without support
for read-write (i.e., in read-only mode).
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6MagCoreCompliance |
1.3.6.1.2.1.206.2.2.5 |
| 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.
--
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6MagCompliance2 |
1.3.6.1.2.1.206.2.2.6 |
| 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.
--
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6MagCoreReadOnlyCompliance |
1.3.6.1.2.1.206.2.2.7 |
| 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.
--
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6MagReadOnlyCompliance2 |
1.3.6.1.2.1.206.2.2.8 |
| 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.
--
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6LmaCoreCompliance |
1.3.6.1.2.1.206.2.2.9 |
| 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.
--
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6LmaCompliance2 |
1.3.6.1.2.1.206.2.2.10 |
| 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.
--
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6LmaReadOnlyCompliance |
1.3.6.1.2.1.206.2.2.11 |
| 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.
--
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6LmaReadOnlyCompliance2 |
1.3.6.1.2.1.206.2.2.12 |
| 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.
--
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6MagNotificationCompliance |
1.3.6.1.2.1.206.2.2.13 |
| The compliance statement for SNMP entities that
implement the PMIPV6-MIB and support notification
from the mobile access gateway.
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| pmip6LmaNotificationCompliance |
1.3.6.1.2.1.206.2.2.14 |
| The compliance statement for SNMP entities that
implement the PMIPV6-MIB and support notification
from the LMA.
|
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|