MIBs Depot

MOBILEIPV6-MIB

Registered at
1.3.6.1.2.1.133
Last updated
2006-02-01 00:00
Organization
IETF mip6 Working Group
Revisions
2006-02-01 00:00
Namespace
standard
Source file
MOBILEIPV6-MIB
Digest
sha256:9f4781dc4ff78b49641e242ba874b6b7606706bea1bef835a7baea6effc9713e

Description

The MIB module for monitoring Mobile-IPv6 entities. Copyright (C) The Internet Society 2006. This version of this MIB module is part of RFC 4295; see the RFC itself for full legal notices.

Contact

Glenn Mansfield Keeni Postal: Cyber Solutions Inc. 6-6-3, Minami Yoshinari Aoba-ku, Sendai, Japan 989-3204. Tel: +81-22-303-4012 Fax: +81-22-303-4015 E-mail: glenn@cysols.com Kenichi Nagami Postal: INTEC NetCore Inc. 1-3-3, Shin-suna Koto-ku, Tokyo, 135-0075 Japan Tel: +81-3-5665-5069 E-mail: nagami@inetcore.com Kazuhide Koide Postal: Tohoku University 2-1-1, Katahira Aoba-ku, Sendai, 980-8577 Japan Tel: +81-22-217-5454 E-mail: koide@shiratori.riec.tohoku.ac.jp Sri Gundavelli Postal: Cisco Systems 170 W.Tasman Drive, San Jose, CA 95134 USA Tel: +1-408-527-6109 E-mail: sgundave@cisco.com Support Group E-mail: mip6@ietf.org

Imports

FromSymbols
INET-ADDRESS-MIBInetAddress, InetAddressType
IP-MIBipv6InterfaceIfIndex
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMICounter32, Counter64, Gauge32, Integer32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso, mib-2
SNMPv2-TCDateAndTime, DisplayString, TEXTUAL-CONVENTION, TimeStamp, TruthValue

Imported by

2 module(s) in this corpus import this one.

Load order

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

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

Textual conventions

NameOIDSyntaxAccessStatus
Mip6BURequestRejectionCode
TEXTUAL-CONVENTION
The value of the status field in the Binding Acknowledgment message when the Binding Update was rejected.
current

Objects

NameOIDSyntaxAccessStatus
mip6Notifications
OBJECT-IDENTITY
1.3.6.1.2.1.133.0
mip6Objects
OBJECT-IDENTITY
1.3.6.1.2.1.133.1
mip6Core
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.1
mip6System
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.1.1
mip6Capabilities
OBJECT-TYPE
This object indicates the Mobile IPv6 functions that are supported by this managed entity. Multiple Mobile IPv6 functions may be supported by a single entity.
1.3.6.1.2.1.133.1.1.1.1Bits {mobileNode(0), homeAgent(1), correspondentNode(2)}read-onlycurrent
mip6Status
OBJECT-TYPE
This object indicates whether the Mobile IPv6 function is enabled for the managed entity. If it is enabled, the agent discovery and registration functions will be operational. Changing the status from enabled(1) to disabled(2) will terminate the agent discovery and registration functions. On the other hand, changing the status from disabled(2) to enabled(1) will start the agent discovery and registration functions. The value of this object SHOULD remain unchanged across reboots of the managed entity.
1.3.6.1.2.1.133.1.1.1.2INTEGER {enabled(1), disabled(2)}read-writecurrent
mip6Bindings
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.1.2
mip6BindingCacheTable
OBJECT-TYPE
This table models the Binding Cache on the managed entity. The cache is maintained by home agents and correspondent nodes. It contains both correspondent registration entries and home registration entries. Entries in this table are not required to survive a reboot of the managed entity.
1.3.6.1.2.1.133.1.1.2.1not-accessiblecurrent
mip6BindingCacheEntry
OBJECT-TYPE
This entry represents a conceptual row in the binding cache table. It represents a single Binding Update. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.1.2.1.1not-accessiblecurrent
mip6BindingHomeAddressType
OBJECT-TYPE
The InetAddressType of the mip6BindingHomeAddress that follows.
1.3.6.1.2.1.133.1.1.2.1.1.1InetAddressTypenot-accessiblecurrent
mip6BindingHomeAddress
OBJECT-TYPE
The home address of the mobile node corresponding to the Binding Cache entry. This field is used as the key for searching the mobile node's current care-of address in the Binding Cache. The type of the address represented by this object is specified by the corresponding mip6BindingHomeAddressType object.
1.3.6.1.2.1.133.1.1.2.1.1.2InetAddressnot-accessiblecurrent
mip6BindingCOAType
OBJECT-TYPE
The InetAddressType of the mip6BindingCOA that follows.
1.3.6.1.2.1.133.1.1.2.1.1.3InetAddressTyperead-onlycurrent
mip6BindingCOA
OBJECT-TYPE
The care-of address of the mobile node indicated by the home address field (mip6BindingHomeAddress) in this Binding Cache entry. The type of the address represented by this object is specified by the corresponding mip6BindingCOAType object.
1.3.6.1.2.1.133.1.1.2.1.1.4InetAddressread-onlycurrent
mip6BindingTimeRegistered
OBJECT-TYPE
The timestamp when this Binding Cache entry was created.
1.3.6.1.2.1.133.1.1.2.1.1.5DateAndTimeread-onlycurrent
mip6BindingTimeGranted
OBJECT-TYPE
The lifetime in seconds granted to the mobile node for this registration.
1.3.6.1.2.1.133.1.1.2.1.1.6Gauge32read-onlycurrent
mip6BindingTimeRemaining
OBJECT-TYPE
The lifetime in seconds remaining for this registration.
1.3.6.1.2.1.133.1.1.2.1.1.7Gauge32read-onlycurrent
mip6BindingHomeRegn
OBJECT-TYPE
This object indicates whether or not this Binding Cache entry is a home registration entry (applicable only on nodes that support home agent functionality).
1.3.6.1.2.1.133.1.1.2.1.1.8TruthValueread-onlycurrent
mip6BindingMaxSeq
OBJECT-TYPE
The maximum value of the Sequence Number field received in previous Binding Updates for this home address (mip6BindingHomeAddress).
1.3.6.1.2.1.133.1.1.2.1.1.9Unsigned32 (0..65536)read-onlycurrent
mip6BindingUsageTS
OBJECT-TYPE
The timestamp when this entry was last looked up.
1.3.6.1.2.1.133.1.1.2.1.1.10DateAndTimeread-onlycurrent
mip6BindingUsageCount
OBJECT-TYPE
The number of times this entry was looked up.
1.3.6.1.2.1.133.1.1.2.1.1.11Gauge32read-onlycurrent
mip6BindingAdminStatus
OBJECT-TYPE
This is an administrative object used to control the status of a binding cache entry. By default the value will be 'active'(1). A value of 'inactive'(2) will indicate that the validity of the entry is suspended. It does not exist in the binding cache for all practical purposes. The state can be changed from 'active' to 'inactive' by operator intervention. Causing the state to change to 'inactive' results in the entry being deleted from the cache. Attempts to change the status from 'inactive' to 'active' will be rejected.
1.3.6.1.2.1.133.1.1.2.1.1.12INTEGER {active(1), inactive(2)}read-writecurrent
mip6BindingHistoryTable
OBJECT-TYPE
A table containing a record of the bindings.
1.3.6.1.2.1.133.1.1.2.2not-accessiblecurrent
mip6BindingHistoryEntry
OBJECT-TYPE
The record of a binding. Implementors need to be aware that if the total number of octets in mip6BindingHstHomeAddress exceeds 112, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.1.2.2.1not-accessiblecurrent
mip6BindingHstHomeAddressType
OBJECT-TYPE
The InetAddressType of the mip6BindingHstHomeAddress that follows.
1.3.6.1.2.1.133.1.1.2.2.1.1InetAddressTypenot-accessiblecurrent
mip6BindingHstHomeAddress
OBJECT-TYPE
Mobile node's home address. The type of the address represented by this object is specified by the corresponding mip6BindingHstHomeAddressType object.
1.3.6.1.2.1.133.1.1.2.2.1.2InetAddressnot-accessiblecurrent
mip6BindingHstIndex
OBJECT-TYPE
The index to uniquely identify this record along with the mobile node's HomeAddress type and HomeAddress. It should be monotonically increasing. It may wrap after reaching its max value.
1.3.6.1.2.1.133.1.1.2.2.1.3Unsigned32 (1..4294967295)not-accessiblecurrent
mip6BindingHstCOAType
OBJECT-TYPE
The InetAddressType of the mip6BindingHstCOA that follows.
1.3.6.1.2.1.133.1.1.2.2.1.4InetAddressTyperead-onlycurrent
mip6BindingHstCOA
OBJECT-TYPE
Mobile node's care-of address. One mobile node can have multiple bindings with different care-of addresses. The type of the address represented by this object is specified by the corresponding mip6BindingHstCOAType object.
1.3.6.1.2.1.133.1.1.2.2.1.5InetAddressread-onlycurrent
mip6BindingHstTimeRegistered
OBJECT-TYPE
The timestamp when this Binding Cache entry was created.
1.3.6.1.2.1.133.1.1.2.2.1.6DateAndTimeread-onlycurrent
mip6BindingHstTimeExpired
OBJECT-TYPE
The timestamp when this Binding Cache entry expired.
1.3.6.1.2.1.133.1.1.2.2.1.7DateAndTimeread-onlycurrent
mip6BindingHstHomeRegn
OBJECT-TYPE
This object indicates whether or not this Binding Cache entry is a home registration entry (applicable only on nodes that support home agent functionality).
1.3.6.1.2.1.133.1.1.2.2.1.8TruthValueread-onlycurrent
mip6BindingHstUsageTS
OBJECT-TYPE
The timestamp when this entry was last looked up.
1.3.6.1.2.1.133.1.1.2.2.1.9DateAndTimeread-onlycurrent
mip6BindingHstUsageCount
OBJECT-TYPE
The number of times this entry was looked up.
1.3.6.1.2.1.133.1.1.2.2.1.10Gauge32read-onlycurrent
mip6Stats
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.1.3
mip6TotalTraffic
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.1.3.1
mip6InOctets
OBJECT-TYPE
The total number of octets in the MIPv6 datagrams received by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.1.1Counter32read-onlycurrent
mip6HCInOctets
OBJECT-TYPE
The total number of octets in the MIPv6 datagrams received by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. This object is a 64-bit version of mip6InOctets. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.1.2Counter64read-onlycurrent
mip6InPkts
OBJECT-TYPE
The number of MIPv6 datagrams received by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.1.3Counter32read-onlycurrent
mip6HCInPkts
OBJECT-TYPE
The number of MIPv6 datagrams received by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. This object is a 64-bit version of mip6InPkts. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.1.4Counter64read-onlycurrent
mip6OutOctets
OBJECT-TYPE
The total number of octets in the MIPv6 datagrams sent by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.1.5Counter32read-onlycurrent
mip6HCOutOctets
OBJECT-TYPE
The total number of octets in the MIPv6 datagrams sent by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. This object is a 64-bit version of mip6OutOctets. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.1.6Counter64read-onlycurrent
mip6OutPkts
OBJECT-TYPE
The number of MIPv6 datagrams sent by the MIPv6 entity. This will include the datagrams with Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.1.7Counter32read-onlycurrent
mip6HCOutPkts
OBJECT-TYPE
The number of MIPv6 datagrams sent by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. This object is a 64-bit version of mip6OutPkts. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.1.8Counter64read-onlycurrent
mip6CounterDiscontinuityTime
OBJECT-TYPE
The value of sysUpTime on the most recent occasion at which any one or more of this MIPv6 entities global counters, viz., counters with OID prefix 'mip6TotalTraffic' or 'mip6CnGlobalStats' or 'mip6HaGlobalStats' suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value.
1.3.6.1.2.1.133.1.1.3.1.9TimeStampread-onlycurrent
mip6NodeTrafficTable
OBJECT-TYPE
A table containing MIPv6 traffic counters per mobile node.
1.3.6.1.2.1.133.1.1.3.2not-accessiblecurrent
mip6NodeTrafficEntry
OBJECT-TYPE
The MIPv6 traffic statistics for a mobile node. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.1.3.2.1not-accessiblecurrent
mip6NodeInOctets
OBJECT-TYPE
The total number of octets in the MIPv6 datagrams received from the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the Home Address option in the Destination Option extension header (Next Header value = 60). It will also include the IPv6 datagrams that are reverse tunneled to a home agent from the mobile node's home address. 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 mip6NodeCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.2.1.1Counter32read-onlycurrent
mip6HCNodeInOctets
OBJECT-TYPE
The total number of octets in the MIPv6 datagrams received from the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the Home Address option in the Destination Option extension header (Next Header value = 60). It will also include the IPv6 datagrams that are reverse tunneled to a home agent from the mobile node's home address. This object is a 64-bit version of mip6NodeInOctets. 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 mip6NodeCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.2.1.2Counter64read-onlycurrent
mip6NodeInPkts
OBJECT-TYPE
The number of MIPv6 datagrams received from the mobile node by the MIPv6 entity. This will include the datagrams with the Mobility Header or the Home Address option in the Destination Option extension header (Next Header value = 60). It will also include the IPv6 datagrams that are reverse tunneled to a home agent from the mobile node's home address. 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 mip6NodeCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.2.1.3Counter32read-onlycurrent
mip6HCNodeInPkts
OBJECT-TYPE
The number of MIPv6 datagrams received from the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the Home Address option in the Destination Option extension header (Next Header value = 60). It will also include the IPv6 datagrams that are reverse tunneled to a home agent from the mobile node's home address. This object is a 64-bit version of mip6NodeInPkts. 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 mip6NodeCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.2.1.4Counter64read-onlycurrent
mip6NodeOutOctets
OBJECT-TYPE
The total number of octets in the MIPv6 datagrams sent to the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the type 2 Routing Header. It will also include the IPv6 datagrams that are tunneled by a home agent to the mobile node. 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 mip6NodeCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.2.1.5Counter32read-onlycurrent
mip6HCNodeOutOctets
OBJECT-TYPE
The total number of octets in the MIPv6 datagrams sent to the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the type 2 Routing Header. It will also include the IPv6 datagrams that are tunneled by a home agent to the mobile node. This object is a 64-bit version of mip6NodeOutOctets. 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 mip6NodeCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.2.1.6Counter64read-onlycurrent
mip6NodeOutPkts
OBJECT-TYPE
The number of MIPv6 datagrams sent to the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the type 2 Routing Header. It will also include the IPv6 datagrams that are tunneled by a home agent to the mobile node. 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 mip6NodeCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.2.1.7Counter32read-onlycurrent
mip6HCNodeOutPkts
OBJECT-TYPE
The number of MIPv6 datagrams sent to the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the type 2 Routing Header. It will also include the IPv6 datagrams that are tunneled by a home agent to the mobile node. This object is a 64-bit version of mip6NodeOutOctets. 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 mip6NodeCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.1.3.2.1.8Counter64read-onlycurrent
mip6NodeCtrDiscontinuityTime
OBJECT-TYPE
The value of sysUpTime on the most recent occasion at which any one or more of the counters in this row suffered a discontinuity. The relevant counters are the specific instances of any Counter32 or Counter64 objects in this row. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
1.3.6.1.2.1.133.1.1.3.2.1.9TimeStampread-onlycurrent
mip6Mn
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.2
mip6MnSystem
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.2.1
mip6MnHomeAddressTable
OBJECT-TYPE
A table containing registration status for all the home addresses pertaining to the mobile node.
1.3.6.1.2.1.133.1.2.1.1not-accessiblecurrent
mip6MnHomeAddressEntry
OBJECT-TYPE
The registration status for a home address. Implementors need to be aware that if the total number of octets in mip6MnHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.2.1.1.1not-accessiblecurrent
mip6MnHomeAddressType
OBJECT-TYPE
The InetAddressType of the mip6MnHomeAddress that follows.
1.3.6.1.2.1.133.1.2.1.1.1.1InetAddressTypenot-accessiblecurrent
mip6MnHomeAddress
OBJECT-TYPE
A unicast routable address assigned to the mobile node. This is used as the 'permanent address' of the mobile node in the sense that it remains unchanged regardless of the mobile node's current point of attachment. If mobile node doesn't have a home address assigned yet, then this object will take the default 'unspecified' value ::0. The type of the address represented by this object is specified by the corresponding mip6MnHomeAddressType object.
1.3.6.1.2.1.133.1.2.1.1.1.2InetAddressnot-accessiblecurrent
mip6MnHomeAddressState
OBJECT-TYPE
This object indicates the state of the mobile node: unknown -- The state of the mobile node cannot be determined. home -- mobile node is on the home network. registered -- mobile node is on a foreign network and is registered with the home agent. pending -- mobile node has sent registration request to the home agent and is waiting for the reply. isolated -- mobile node is isolated from network, i.e., it is not in its home network, it is not registered, and no registration ack is pending.
1.3.6.1.2.1.133.1.2.1.1.1.3INTEGER {unknown(1), home(2), registered(3), pending(4), isolated(5)}read-onlycurrent
mip6MnConf
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.2.2
mip6MnDiscoveryRequests
OBJECT-TYPE
Total number of ICMP Dynamic Home Agent Address Discovery Requests sent by the mobile node. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.2.1Counter32read-onlycurrent
mip6MnDiscoveryReplies
OBJECT-TYPE
Total number of ICMP Dynamic Home Agent Address Discovery Replies received by the mobile node. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.2.2Counter32read-onlycurrent
mip6MnDiscoveryTimeouts
OBJECT-TYPE
Total number of ICMP Dynamic Home Agent Address Discovery Requests that timed out. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.2.3Counter32read-onlycurrent
mip6MnPrefixSolicitationsSent
OBJECT-TYPE
Total number of ICMP Mobile Prefix Solicitations sent by the mobile node. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.2.4Counter32read-onlycurrent
mip6MnPrefixAdvsRecd
OBJECT-TYPE
Total number of ICMP Mobile Prefix Advertisements received by the mobile node. This will include the ICMP Mobile Prefix Advertisements that failed the validity checks. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.2.5Counter32read-onlycurrent
mip6MnPrefixAdvsIgnored
OBJECT-TYPE
Total number of Mobile Prefix Advertisements discarded by the validity check. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.2.6Counter32read-onlycurrent
mip6MnMovedToFN
OBJECT-TYPE
Number of times the mobile node has detected movement to a foreign network from another foreign network or from the home network, has reconstructed its care-of address and has initiated the care-of address registration process. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.2.7Counter32read-onlycurrent
mip6MnMovedToHN
OBJECT-TYPE
Number of times the mobile node has detected movement from a foreign network to its home network. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.2.8Counter32read-onlycurrent
mip6MnRegistration
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.2.3
mip6MnBLTable
OBJECT-TYPE
This table corresponds to the Binding Update List (BL) that is maintained by the mobile node. The list holds an item for every binding that the mobile node has established or is trying to establish. Both correspondent and home registrations are included in this table. Entries from the table are deleted as the lifetime of the binding expires.
1.3.6.1.2.1.133.1.2.3.1not-accessiblecurrent
mip6MnBLEntry
OBJECT-TYPE
Information about a Binding Update sent by the mobile node either to its home agent or to one of its correspondent nodes. Implementors need to be aware that if the total number of octets in mip6MnHomeAddress and mip6MnBLNodeAddress exceeds 111, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.2.3.1.1not-accessiblecurrent
mip6MnBLNodeAddressType
OBJECT-TYPE
The InetAddressType of the mip6MnBLNodeAddress that follows.
1.3.6.1.2.1.133.1.2.3.1.1.1InetAddressTypenot-accessiblecurrent
mip6MnBLNodeAddress
OBJECT-TYPE
The address of the agent as used in the destination address of the Binding Update. The agent may be a home agent or a correspondent node. The type of the address represented by this object is specified by the corresponding mip6MnBLNodeAddressType object.
1.3.6.1.2.1.133.1.2.3.1.1.2InetAddressnot-accessiblecurrent
mip6MnBLCOAType
OBJECT-TYPE
The InetAddressType of the mip6MnBLCOA that follows.
1.3.6.1.2.1.133.1.2.3.1.1.3InetAddressTyperead-onlycurrent
mip6MnBLCOA
OBJECT-TYPE
Care-of address that the mobile node intends to register in the Binding Update request. The type of the address represented by this object is specified by the corresponding mip6MnBLCOAType object.
1.3.6.1.2.1.133.1.2.3.1.1.4InetAddressread-onlycurrent
mip6MnBLLifeTimeRequested
OBJECT-TYPE
The lifetime requested by the mobile node (in seconds) in the Binding Update.
1.3.6.1.2.1.133.1.2.3.1.1.5Unsigned32read-onlycurrent
mip6MnBLLifeTimeGranted
OBJECT-TYPE
The lifetime granted to the mobile node for this binding. This field will be inaccessible if the Binding Update request has not been accepted. The lifetime remaining (lR) can be calculated using the current time (cT), mip6MnBLAcceptedTime (aT) and mip6MnBLLifeTimeGranted (lG) as follows: lR = lG - (cT - aT). When lR is zero, this entry will be deleted from the Binding Update List and consequently from this table.
1.3.6.1.2.1.133.1.2.3.1.1.6Unsigned32read-onlycurrent
mip6MnBLMaxSeq
OBJECT-TYPE
The maximum value of the Sequence Number field sent in previous Binding Updates to this destination.
1.3.6.1.2.1.133.1.2.3.1.1.7Unsigned32 (0..65536)read-onlycurrent
mip6MnBLTimeSent
OBJECT-TYPE
The time when the last (re-)transmission occurred.
1.3.6.1.2.1.133.1.2.3.1.1.8DateAndTimeread-onlycurrent
mip6MnBLAccepted
OBJECT-TYPE
true(1) if the mobile node has received a binding acknowledgment indicating that service has been accepted (status code 0 or 1); false(2) otherwise. false(2) implies that the registration is still pending.
1.3.6.1.2.1.133.1.2.3.1.1.9TruthValueread-onlycurrent
mip6MnBLAcceptedTime
OBJECT-TYPE
The time at which the mobile node receives a binding acknowledgment indicating that Binding Update has been accepted (status code 0 or 1); This object will be inaccessible if the Binding Update request is still pending.
1.3.6.1.2.1.133.1.2.3.1.1.10DateAndTimeread-onlycurrent
mip6MnBLRetransmissions
OBJECT-TYPE
The number of Binding Update retransmissions.
1.3.6.1.2.1.133.1.2.3.1.1.11Gauge32read-onlycurrent
mip6MnBLDontSendBUFlag
OBJECT-TYPE
true(1) indicates that future binding updates will not be sent to mip6MnBLNodeAddress. false(2) implies that binding updates will be sent to mip6MnBLNodeAddress. The mobile node sets this flag in the when it receives an ICMP Parameter Problem, Code 1, error message in response to a return routability message or Binding Update sent to mip6MnBLNodeAddress.
1.3.6.1.2.1.133.1.2.3.1.1.12TruthValueread-onlycurrent
mip6MnRegnCounters
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.2.3.2
mip6MnMobilityMessagesSent
OBJECT-TYPE
The total number of mobility messages, i.e., IPv6 datagrams with Mobility Header, sent by the mobile node. There are 3 types of mobility messages, viz., Home Test Init, Care-of Test Init, and Binding Updates, that are sent by mobile nodes. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.1Counter32read-onlycurrent
mip6MnMobilityMessagesRecd
OBJECT-TYPE
The total number of mobility messages, i.e., IPv6 datagrams with Mobility Header, received by the mobile node. There are 5 types of mobility messages, viz., Home Test, Care-of Test, Binding Acknowledgment, Binding Refresh Request, and Binding Error, that are sent to mobile nodes. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.2Counter32read-onlycurrent
mip6MnBUsToHA
OBJECT-TYPE
Total number of Binding Updates sent to the mobile node's home agent(s). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.3Counter32read-onlycurrent
mip6MnBUAcksFromHA
OBJECT-TYPE
Total number of valid binding acknowledgments received from the mobile node's home agent(s). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.4Counter32read-onlycurrent
mip6MnBUsToCN
OBJECT-TYPE
Total number of Binding Updates sent to correspondent nodes by the mobile node. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.5Counter32read-onlycurrent
mip6MnBUAcksFromCN
OBJECT-TYPE
Total number of valid Binding Update acks received from all the correspondent nodes. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.6Counter32read-onlycurrent
mip6MnBindingErrorsFromCN
OBJECT-TYPE
Total number of Binding Error messages received by mobile node from CN. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.7Counter32read-onlycurrent
mip6MnICMPErrorsRecd
OBJECT-TYPE
Total number of ICMP Error messages of type ICMP Parameter Problem, Code 1 or Code 2, received by the mobile node from a correspondent node in response to a return routability procedure, a Binding Update, or a packet with the Home Address option. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.8Counter32read-onlycurrent
mip6MnBRRequestsRecd
OBJECT-TYPE
The total number of Binding Refresh requests received by the mobile node from correspondent nodes. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.2.3.2.9Counter32read-onlycurrent
mip6Cn
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.3
mip6CnSystem
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.3.1
mip6CnStats
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.3.2
mip6CnGlobalStats
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.3.2.1
mip6CnHomeTestInitsRecd
OBJECT-TYPE
Total number of Home Test Init messages received. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.1Counter32read-onlycurrent
mip6CnHomeTestsSent
OBJECT-TYPE
Total number of Home Test messages sent. If a Home Test Init message is found to be valid, a Home Test message will be generated and sent. Otherwise the Home Test message is silently discarded. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.2Counter32read-onlycurrent
mip6CnCareOfTestInitsRecd
OBJECT-TYPE
Total number of Care-of Test Init messages received.
1.3.6.1.2.1.133.1.3.2.1.3Counter32read-onlycurrent
mip6CnCareOfTestsSent
OBJECT-TYPE
Total number of Care-of Test messages sent. If a Care-of Test Init message is found to be valid, a Care-of Test message will be generated and sent. Otherwise the Care-of Test message is silently discarded. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.4Counter32read-onlycurrent
mip6CnBUsRecd
OBJECT-TYPE
Total number of Binding Updates received by the correspondent node from mobile nodes. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.5Counter32read-onlycurrent
mip6CnBUAcksSent
OBJECT-TYPE
Total number of acknowledgments sent by the correspondent node for the Binding Updates received. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.6Counter32read-onlycurrent
mip6CnBRsSent
OBJECT-TYPE
Total number of Binding Refresh Request messages sent by the correspondent node. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.7Counter32read-onlycurrent
mip6CnBindingErrors
OBJECT-TYPE
Total number of Binding Error messages sent by the correspondent node to the mobile node. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.8Counter32read-onlycurrent
mip6CnBUsAccepted
OBJECT-TYPE
Total number of Binding Updates accepted by the correspondent node. If a Binding Acknowledgment message is sent for the Binding Update request, the Status code field in the message will have a value less than 128. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.9Counter32read-onlycurrent
mip6CnBUsRejected
OBJECT-TYPE
Total number of Binding Update requests rejected by the correspondent node. If a Binding Acknowledgment message has been sent for the Binding Update request, the Status code field in the message will have a value greater than or equal to 128. Otherwise the Binding Update request will be silently discarded. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.10Counter32read-onlycurrent
mip6CnReasonUnspecified
OBJECT-TYPE
Total number of Binding Update requests rejected by the correspondent node with status code in the Binding Acknowledgment message indicating 'reason unspecified' (Code 128). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.11Counter32read-onlycurrent
mip6CnInsufficientResource
OBJECT-TYPE
Total number of Binding Update requests rejected by the correspondent node with status code in the Binding Acknowledgment message indicating 'insufficient resources' (Code 130). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.12Counter32read-onlycurrent
mip6CnHomeRegnNotSupported
OBJECT-TYPE
Total number of Binding Update requests rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'home registration not supported' (Code 131). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.13Counter32read-onlycurrent
mip6CnSeqNumberOutOfWindow
OBJECT-TYPE
Total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'sequence number out of window' (Code 135). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.14Counter32read-onlycurrent
mip6CnExpiredHomeNonceIndex
OBJECT-TYPE
The total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'expired home nonce index' (Code 136). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.15Counter32read-onlycurrent
mip6CnExpiredCareOfNonceIndex
OBJECT-TYPE
The total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'expired care-of nonce index' (Code 137). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.16Counter32read-onlycurrent
mip6CnExpiredNonce
OBJECT-TYPE
The total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'expired nonces' (Code 138), i.e., the correspondent node no longer recognizes the Home Nonce Index value and the Care-of Nonce Index value. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.17Counter32read-onlycurrent
mip6CnRegTypeChangeDisallowed
OBJECT-TYPE
The total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'registration type change disallowed' (Code 139), i.e., a binding already exists for the given home address and the home registration flag has a different value than the Home Registration (H) bit in the Binding Update. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.1.18Counter32read-onlycurrent
mip6CnCounterTable
OBJECT-TYPE
A table containing each mobile .
1.3.6.1.2.1.133.1.3.2.2not-accessiblecurrent
mip6CnCounterEntry
OBJECT-TYPE
The set of correspondent node counters for a mobile node. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.3.2.2.1not-accessiblecurrent
mip6CnBURequestsAccepted
OBJECT-TYPE
Total number of Binding Update requests from the mobile node accepted by the correspondent node. If Binding Acknowledgment messages are sent, then the status code in the message will have a value less than 128. 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 mip6CnCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.2.1.1Counter32read-onlycurrent
mip6CnBURequestsRejected
OBJECT-TYPE
Total number of Binding Update requests from the mobile node that have been rejected by the correspondent node. This includes the Binding Update requests for which a Binding Acknowledgment message has been sent with status code value greater than or equal to 128 and the Binding Acknowledgment requests that have been silently discarded. 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 mip6CnCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.3.2.2.1.2Counter32read-onlycurrent
mip6CnBCEntryCreationTime
OBJECT-TYPE
The time when the current Binding Cache entry was created for the mobile node.
1.3.6.1.2.1.133.1.3.2.2.1.3DateAndTimeread-onlycurrent
mip6CnBUAcceptedTime
OBJECT-TYPE
The time at which the last Binding Update was accepted by the correspondent node and the corresponding Binding Cache entry was updated.
1.3.6.1.2.1.133.1.3.2.2.1.4DateAndTimeread-onlycurrent
mip6CnBURejectionTime
OBJECT-TYPE
The time at which the last Binding Update message was rejected by the correspondent node. If there have been no rejections, then this object will be inaccessible.
1.3.6.1.2.1.133.1.3.2.2.1.5DateAndTimeread-onlycurrent
mip6CnBURejectionCode
OBJECT-TYPE
If a Binding Acknowledgment is sent to the mobile node, this is the status code (> 128) that is returned in the Binding Acknowledgment. In case a Binding Acknowledgment is not sent to the mobile node, then this will be the value of the Status code that corresponds to the reason of the rejection. If there have been no rejections, then this object will be inaccessible.
1.3.6.1.2.1.133.1.3.2.2.1.6Mip6BURequestRejectionCoderead-onlycurrent
mip6CnCtrDiscontinuityTime
OBJECT-TYPE
The value of sysUpTime on the most recent occasion at which any one or more of counters in this row, viz., instances of 'mip6CnBURequestsAccepted' and 'mip6CnBURequestsRejected', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value.
1.3.6.1.2.1.133.1.3.2.2.1.7TimeStampread-onlycurrent
mip6Ha
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.4
mip6HaAdvertisement
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.4.1
mip6HaAdvsRecd
OBJECT-TYPE
Total number of valid Router Advertisements received with the Home Agent (H) bit set, on all the links on which it is serving as a Home Agent. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.1.1Counter32read-onlycurrent
mip6HaAdvsSent
OBJECT-TYPE
Total number of unsolicited multicast Router Advertisements sent with the Home Agent (H) bit set, on all the links on which the router is serving as a Home Agent. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.1.2Counter32read-onlycurrent
mip6HaConfTable
OBJECT-TYPE
A table containing configurable advertisement parameters for all interfaces on which the home agent service is advertised. It is RECOMMENDED that the last written values of the objects in the conceptual rows of this table will remain unchanged across reboots of the managed entity provided that the interfaces have not been renumbered after the reboot.
1.3.6.1.2.1.133.1.4.1.3not-accessiblecurrent
mip6HaConfEntry
OBJECT-TYPE
Advertisement parameters for an interface. The instances of the columnar objects in this entry pertain to the interface that is uniquely identified by the ipv6InterfaceIfIndex of the interface. The same ipv6InterfaceIfIndex object is used to uniquely identify instances of the columnar objects of this conceptual row.
1.3.6.1.2.1.133.1.4.1.3.1not-accessiblecurrent
mip6HaAdvPreference
OBJECT-TYPE
The preference value for the home agent to be used in the Router Advertisements. Higher value denotes greater preference.
1.3.6.1.2.1.133.1.4.1.3.1.1Integer32 (0..65536)read-writecurrent
mip6HaAdvLifetime
OBJECT-TYPE
The lifetime value for the home agent to be used in the Router Advertisements.
1.3.6.1.2.1.133.1.4.1.3.1.2Integer32 (1..65535)read-writecurrent
mip6HaPrefixAdv
OBJECT-TYPE
Indicates whether the home agent should support sending of the ICMP Mobile Prefix Advertisements. If it is disabled(2), the home agent will not send ICMP Mobile Prefix Advertisements to the mobile nodes. The state can be changed from enabled(1) to disabled(2) and vice versa by operator intervention. Causing the state to change from enabled(1) to disabled(2) will result in the home agent disabling the Prefix advertisement function. On the other hand, changing the status from disabled(2) to enabled(1) will start the prefix advertisement function.
1.3.6.1.2.1.133.1.4.1.3.1.3INTEGER {enabled(1), disabled(2)}read-writecurrent
mip6HaPrefixSolicitation
OBJECT-TYPE
Indicates whether the home agent should respond to ICMP Mobile Prefix Solicitation messages it receives from the mobile nodes. By default, the value will be set to enabled(1). If it is disabled(2), the home agent will not respond to any ICMP Mobile Prefix Solicitation messages. The state can be changed from enabled(1) to disabled(2), by operator intervention. Causing the state to change from enabled(1) to disabled(2) will result in the home agent not responding to any ICMP Mobile Prefix Solicitation messages it receives from the mobile nodes.
1.3.6.1.2.1.133.1.4.1.3.1.4INTEGER {enabled(1), disabled(2)}read-writecurrent
mip6HaMCastCtlMsgSupport
OBJECT-TYPE
Indicates whether the home agent should enable support for the processing of the multicast group membership control messages it receives from the mobile nodes. By default, the value will be set to enabled(1). If it is disabled(2), the home agent will not process any multicast group control messages it receives from the mobile nodes. The state can be changed from enabled(1) to disabled(2), by operator intervention. Causing the state to change from enabled(1) to disabled(2) will result in the home agent disabling the processing of the multicast group control messages it received from the mobile nodes.
1.3.6.1.2.1.133.1.4.1.3.1.5INTEGER {enabled(1), disabled(2)}read-writecurrent
mip6HaListTable
OBJECT-TYPE
This table models the Home Agents List that contains the list of all routers that are acting as home agents on each of the interfaces on which the home agent service is offered by this router.
1.3.6.1.2.1.133.1.4.1.4not-accessiblecurrent
mip6HaListEntry
OBJECT-TYPE
Information about a router that is offering home agent service. The instances of the columnar objects in this entry pertain to an interface for a particular value of mip6HaLinkLocalAddressType and mip6HaLinkLocalAddress. The interface is uniquely identified by its ipv6InterfaceIfIndex. The same ipv6InterfaceIfIndex object is used in conjunction with the mip6HaLinkLocalAddressType and mip6HaLinkLocalAddress to uniquely identify instances of the columnar objects of this row. Implementors need to be aware that if the total number of octets in mip6HaLinkLocalAddress exceeds 112, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.4.1.4.1not-accessiblecurrent
mip6HaLinkLocalAddressType
OBJECT-TYPE
The address type for the link-local address of the home agent that follows.
1.3.6.1.2.1.133.1.4.1.4.1.1InetAddressTypenot-accessiblecurrent
mip6HaLinkLocalAddress
OBJECT-TYPE
The link local address of the home agent. The type of the address represented by this object is specified by the corresponding mip6HaLinkLocalAddressType object.
1.3.6.1.2.1.133.1.4.1.4.1.2InetAddressnot-accessiblecurrent
mip6HaPreference
OBJECT-TYPE
The preference value of this home agent. Higher values indicate a more preferable home agent. The preference value is obtained from the preference field of the received Router Advertisement.
1.3.6.1.2.1.133.1.4.1.4.1.3Integer32read-onlycurrent
mip6HaRecvLifeTime
OBJECT-TYPE
The lifetime for this home agent.
1.3.6.1.2.1.133.1.4.1.4.1.4Gauge32read-onlycurrent
mip6HaRecvTimeStamp
OBJECT-TYPE
The time when the home agent advertisement was received.
1.3.6.1.2.1.133.1.4.1.4.1.5DateAndTimeread-onlycurrent
mip6HaGlAddrTable
OBJECT-TYPE
This table contains the global addresses of the home agents in the Home Agents List.
1.3.6.1.2.1.133.1.4.1.5not-accessiblecurrent
mip6HaGlAddrEntry
OBJECT-TYPE
A global address for a home agent in the Home Agents List. The instances of the columnar objects in this entry pertain to an interface for a particular value of mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress and mip6HaGaAddrSeqNo. The mip6HaGaAddrSeqNo object is used to distinguish between multiple instances of the home agent global addresses on the same interface for the same set of mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress, values. There is no upper-bound on the maximum number of global addresses on an interface but, for practical purposes, the upper-bound of the value mip6HaGaAddrSeqNo is set to 1024. The interface is uniquely identified by its ipv6InterfaceIfIndex. The same ipv6InterfaceIfIndex object is used in conjunction with the mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress, and mip6HaGaAddrSeqNo to uniquely identify instances of the columnar objects of this row. Implementors need to be aware that if the total number of octets in mip6HaLinkLocalAddress exceeds 111, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.4.1.5.1not-accessiblecurrent
mip6HaGaAddrSeqNo
OBJECT-TYPE
The index that along with ipv6InterfaceIfIndex, mip6HaLinkLocalAddressType, and mip6HaLinkLocalAddress uniquely identifies this row.
1.3.6.1.2.1.133.1.4.1.5.1.1Integer32 (1..1024)not-accessiblecurrent
mip6HaGaGlobalAddressType
OBJECT-TYPE
The address type for the global address of the home agent that follows.
1.3.6.1.2.1.133.1.4.1.5.1.2InetAddressTyperead-onlycurrent
mip6HaGaGlobalAddress
OBJECT-TYPE
A global address of the home agent. The type of the address represented by this object is specified by the corresponding mip6HaGaGlobalAddressType object.
1.3.6.1.2.1.133.1.4.1.5.1.3InetAddressread-onlycurrent
mip6HaStats
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.4.2
mip6HaGlobalStats
OBJECT-IDENTITY
1.3.6.1.2.1.133.1.4.2.1
mip6HaHomeTestInitsRecd
OBJECT-TYPE
Total number of Home Test Init messages received by the home agent. This will include Home Test Init messages that failed the validity checks. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.1Counter32read-onlycurrent
mip6HaHomeTestsSent
OBJECT-TYPE
Total number of Home Test messages sent by the home agent. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.2Counter32read-onlycurrent
mip6HaBUsRecd
OBJECT-TYPE
Total number of Binding Updates received by the home agent. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.3Counter32read-onlycurrent
mip6HaBUAcksSent
OBJECT-TYPE
Total number of Binding Acknowledgments sent by the home agent. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.4Counter32read-onlycurrent
mip6HaBRAdviceSent
OBJECT-TYPE
Total number of Binding Acknowledgments sent by the home agent with Binding Refresh Advice mobility option included. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.5Counter32read-onlycurrent
mip6HaBUsAccepted
OBJECT-TYPE
Total number of Binding Updates accepted by this HA. Binding Acknowledgment with status code of 0 or 1. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.6Counter32read-onlycurrent
mip6HaPrefDiscoverReqd
OBJECT-TYPE
The total number of Binding Acknowledgments sent by the home agent with status code indicating 'accepted but prefix discovery necessary' (Code 1). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.7Counter32read-onlycurrent
mip6HaReasonUnspecified
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'reason unspecified' (Code 128). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.8Counter32read-onlycurrent
mip6HaAdmProhibited
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'administratively prohibited' (Code 129). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.9Counter32read-onlycurrent
mip6HaInsufficientResource
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'insufficient resources' (Code 130). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.10Counter32read-onlycurrent
mip6HaHomeRegnNotSupported
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'home registration not supported' (Code 131). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.11Counter32read-onlycurrent
mip6HaNotHomeSubnet
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'not home subnet' (Code 132). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.12Counter32read-onlycurrent
mip6HaNotHomeAgentForThisMN
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'not home agent for this mobile node' (Code 133). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.13Counter32read-onlycurrent
mip6HaDupAddrDetectionFailed
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'Duplicate Address Detection failed' (Code 134). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.14Counter32read-onlycurrent
mip6HaSeqNumberOutOfWindow
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'sequence number out of window' (Code 135). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.15Counter32read-onlycurrent
mip6HaExpiredHomeNonceIndex
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'expired home nonce index' (Code 136). 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.16Counter32read-onlycurrent
mip6HaRegTypeChangeDisallowed
OBJECT-TYPE
Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'registration type change disallowed' (Code 139), i.e., a binding already exists for the given home address and the home registration flag has a different value than the Home Registration (H) bit in the Binding Update. 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 mip6CounterDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.1.17Counter32read-onlycurrent
mip6HaCounterTable
OBJECT-TYPE
A table containing registration statistics for all mobile nodes registered with the home agent.
1.3.6.1.2.1.133.1.4.2.2not-accessiblecurrent
mip6HaCounterEntry
OBJECT-TYPE
Home agent registration statistics for a mobile node. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
1.3.6.1.2.1.133.1.4.2.2.1not-accessiblecurrent
mip6HaBURequestsAccepted
OBJECT-TYPE
Total number of service requests for the mobile node accepted by the home agent. 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 mip6HaCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.2.1.1Counter32read-onlycurrent
mip6HaBURequestsDenied
OBJECT-TYPE
Total number of service requests for the mobile node rejected by the home agent. 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 mip6HaCtrDiscontinuityTime.
1.3.6.1.2.1.133.1.4.2.2.1.2Counter32read-onlycurrent
mip6HaBCEntryCreationTime
OBJECT-TYPE
The time when the current Binding Cache entry was created for the mobile node.
1.3.6.1.2.1.133.1.4.2.2.1.3DateAndTimeread-onlycurrent
mip6HaBUAcceptedTime
OBJECT-TYPE
The time at which the last Binding Update was accepted by the home agent for this mobile node.
1.3.6.1.2.1.133.1.4.2.2.1.4DateAndTimeread-onlycurrent
mip6HaBURejectionTime
OBJECT-TYPE
The time at which the last Binding Update was rejected by the home agent for this mobile node. If there have been no rejections, then this object will be inaccessible.
1.3.6.1.2.1.133.1.4.2.2.1.5DateAndTimeread-onlycurrent
mip6HaRecentBURejectionCode
OBJECT-TYPE
If a Binding Acknowledgment is sent to the mobile node, this is the status code (> 128) that is returned in the Binding Acknowledgment. In case a Binding Acknowledgment is not sent to the mobile node, then this will be the value of the status code that corresponds to the reason of the rejection. If there have been no rejections, then this object will be inaccessible.
1.3.6.1.2.1.133.1.4.2.2.1.6Mip6BURequestRejectionCoderead-onlycurrent
mip6HaCtrDiscontinuityTime
OBJECT-TYPE
The value of sysUpTime on the most recent occasion at which any one or more of counters in this row, viz., instances of 'mip6HaBURequestsAccepted' and 'mip6HaBURequestsRejected', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value.
1.3.6.1.2.1.133.1.4.2.2.1.7TimeStampread-onlycurrent
mip6Conformance
OBJECT-IDENTITY
1.3.6.1.2.1.133.2
mip6Groups
OBJECT-IDENTITY
1.3.6.1.2.1.133.2.1
mip6Compliances
OBJECT-IDENTITY
1.3.6.1.2.1.133.2.2

Notifications

NameOIDStatus
mip6MnRegistered
NOTIFICATION-TYPE
This notification is sent by a home agent when a mobile node registers with the home agent for the first time. Notifications will not be sent for subsequent updates and/or refreshes. The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable.
1.3.6.1.2.1.133.0.1current
mip6MnDeRegistered
NOTIFICATION-TYPE
This notification is sent by a home agent every time a mobile node de-registers with the home agent by sending a Binding Update that requests the home agent to delete a binding. The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable.
1.3.6.1.2.1.133.0.2current
mip6MnCOAChanged
NOTIFICATION-TYPE
This notification is sent by a home agent every time a mobile node sends a Binding Update with a new care-of address (for an existing Binding Cache entry). Notifications will not be sent for subsequent updates and/or refreshes for the same Care-of address. The registration of a new care-of address may indicate that the mobile node has moved or that the primary care-of address of the mobile node has become deprecated. The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable.
1.3.6.1.2.1.133.0.3current
mip6MnBindingExpiredAtHA
NOTIFICATION-TYPE
This notification is sent by a home agent when a binding for the mobile node at the home agent expired (no timely Binding Updates were received). The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable.
1.3.6.1.2.1.133.0.4current
mip6MnBindingExpiredAtCN
NOTIFICATION-TYPE
This notification is sent by a correspondent node when a binding for the mobile node at the correspondent node expired (no timely Binding Updates were received). The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable.
1.3.6.1.2.1.133.0.5current

Conformance

NameOIDStatus
mip6SystemGroup
OBJECT-GROUP
A collection of objects for basic MIPv6 monitoring.
1.3.6.1.2.1.133.2.1.1current
mip6BindingCacheGroup
OBJECT-GROUP
A collection of objects for monitoring the Binding Cache.
1.3.6.1.2.1.133.2.1.2current
mip6BindingHstGroup
OBJECT-GROUP
A collection of objects for monitoring the Binding History. This can be used to monitor the movement of the mobile node.
1.3.6.1.2.1.133.2.1.3current
mip6TotalTrafficGroup
OBJECT-GROUP
A collection of objects for monitoring the total MIPv6 traffic.
1.3.6.1.2.1.133.2.1.4current
mip6NodeTrafficGroup
OBJECT-GROUP
A collection of objects for monitoring the MIPv6 traffic due to a mobile node.
1.3.6.1.2.1.133.2.1.5current
mip6MnSystemGroup
OBJECT-GROUP
A collection of objects for basic monitoring of the mobile node.
1.3.6.1.2.1.133.2.1.6current
mip6MnConfGroup
OBJECT-GROUP
A collection of objects for monitoring the advertisement-related info on the mobile node.
1.3.6.1.2.1.133.2.1.7current
mip6MnRegistrationGroup
OBJECT-GROUP
A collection of objects for monitoring the registration statistics for the mobile node.
1.3.6.1.2.1.133.2.1.8current
mip6CnStatsGroup
OBJECT-GROUP
A collection of objects for monitoring the control messages and corresponding statistics for each mobile node communicating with the correspondent node.
1.3.6.1.2.1.133.2.1.9current
mip6HaSystemGroup
OBJECT-GROUP
A collection of objects for monitoring the advertisement-related parameters and statistics for the home agent.
1.3.6.1.2.1.133.2.1.10current
mip6HaListGroup
OBJECT-GROUP
A collection of objects for monitoring the Home Agent List on the home agent.
1.3.6.1.2.1.133.2.1.11current
mip6HaStatsGroup
OBJECT-GROUP
A collection of objects for monitoring registration-related statistics on the home agent.
1.3.6.1.2.1.133.2.1.12current
mip6CnGlobalStatsGroup
OBJECT-GROUP
A collection of objects for monitoring advertisement and registration statistics on a correspondent node.
1.3.6.1.2.1.133.2.1.13current
mip6HaGlobalStatsGroup
OBJECT-GROUP
A collection of objects for monitoring advertisement and registration statistics on a home agent.
1.3.6.1.2.1.133.2.1.14current
mip6BindingCacheCtlGroup
OBJECT-GROUP
A collection of objects for controlling the Binding Cache.
1.3.6.1.2.1.133.2.1.15current
mip6NotificationGroup
NOTIFICATION-GROUP
A collection of notifications from a home agent or correspondent node to the Manager about the status of a mobile node.
1.3.6.1.2.1.133.2.1.16current
mip6CoreCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB.
1.3.6.1.2.1.133.2.2.1current
mip6Compliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the Binding Cache and the Total Traffic. 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. --
1.3.6.1.2.1.133.2.2.2current
mip6Compliance3
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the Binding Cache, the Binding History, the total traffic, and the mobile node-wide traffic. 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHstHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. -- -- OBJECT mip6BindingHstHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. --
1.3.6.1.2.1.133.2.2.3current
mip6CoreReadOnlyCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode).
1.3.6.1.2.1.133.2.2.4current
mip6ReadOnlyCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the Binding Cache and Total Traffic. 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. --
1.3.6.1.2.1.133.2.2.5current
mip6ReadOnlyCompliance3
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the Binding Cache, the Binding History, the total traffic, and the mobile node-wide traffic. 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHstHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. -- -- OBJECT mip6BindingHstHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. --
1.3.6.1.2.1.133.2.2.6current
mip6MnCoreCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic mobile node functionality. 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 mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. --
1.3.6.1.2.1.133.2.2.7current
mip6MnCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the mobile node functionality specifically the Discovery- and Registration-related statistics, 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 mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnBLNodeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnBLNodeAddress -- object. -- -- OBJECT mip6MnBLNodeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnBLNodeAddress -- object. --
1.3.6.1.2.1.133.2.2.8current
mip6CnCoreCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic correspondent node functionality.
1.3.6.1.2.1.133.2.2.9current
mip6CnCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic correspondent node functionality. 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object.
1.3.6.1.2.1.133.2.2.10current
mip6HaCoreCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic home agent functionality.
1.3.6.1.2.1.133.2.2.11current
mip6HaCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics, 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType -- SYNTAX InetAddressType { ipv6z(4) } -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- -- OBJECT mip6HaLinkLocalAddress -- SYNTAX InetAddress (SIZE(20)) -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. --
1.3.6.1.2.1.133.2.2.12current
mip6HaCompliance3
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring and control of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics, 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType -- SYNTAX InetAddressType { ipv6z(4) } -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- -- OBJECT mip6HaLinkLocalAddress -- SYNTAX InetAddress (SIZE(20)) -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. --
1.3.6.1.2.1.133.2.2.13current
mip6HaCoreReadOnlyCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the basic home agent functionality.
1.3.6.1.2.1.133.2.2.14current
mip6HaReadOnlyCompliance2
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics. 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType -- SYNTAX InetAddressType { ipv6z(4) } -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- -- OBJECT mip6HaLinkLocalAddress -- SYNTAX InetAddress (SIZE(20)) -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. --
1.3.6.1.2.1.133.2.2.15current
mip6HaReadOnlyCompliance3
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring and control of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics, 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType -- SYNTAX InetAddressType { ipv6z(4) } -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- -- OBJECT mip6HaLinkLocalAddress -- SYNTAX InetAddress (SIZE(20)) -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. --
1.3.6.1.2.1.133.2.2.16current
mip6NotificationCompliance
MODULE-COMPLIANCE
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support Notification from home agent or correspondent node to management stations about the mobile node status. 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 mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object.
1.3.6.1.2.1.133.2.2.17current