MOBILEIPV6-MIB

File: MOBILEIPV6-MIB.mib (160469 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SNMPv2-CONF
INET-ADDRESS-MIB IP-MIB

Imported symbols

MODULE-IDENTITY mib-2 Unsigned32
Integer32 Counter32 Gauge32
Counter64 OBJECT-TYPE NOTIFICATION-TYPE
TEXTUAL-CONVENTION TruthValue DateAndTime
TimeStamp MODULE-COMPLIANCE OBJECT-GROUP
NOTIFICATION-GROUP InetAddressType InetAddress
ipv6InterfaceIfIndex

Defined Types

Mip6BURequestRejectionCode  
TEXTUAL-CONVENTION    
  current INTEGER reasonUnspecified(1), admProhibited(2), insufficientResource(3), homeRegistrationNotSupported(4), notHomeSubnet(5), notHomeAgentForThisMobileNode(6), duplicateAddressDetectionFailed(7), sequenceNumberOutOfWindow(8), expiredHomeNonceIndex(9), expiredCareofNonceIndex(10), expiredNonces(11), registrationTypeChangeDisallowed(12)

Mip6BindingCacheEntry  
SEQUENCE    
  mip6BindingHomeAddressType InetAddressType
  mip6BindingHomeAddress InetAddress
  mip6BindingCOAType InetAddressType
  mip6BindingCOA InetAddress
  mip6BindingTimeRegistered DateAndTime
  mip6BindingTimeGranted Gauge32
  mip6BindingTimeRemaining Gauge32
  mip6BindingHomeRegn TruthValue
  mip6BindingMaxSeq Unsigned32
  mip6BindingUsageTS DateAndTime
  mip6BindingUsageCount Gauge32
  mip6BindingAdminStatus INTEGER

Mip6BindingHistoryEntry  
SEQUENCE    
  mip6BindingHstHomeAddressType InetAddressType
  mip6BindingHstHomeAddress InetAddress
  mip6BindingHstIndex Unsigned32
  mip6BindingHstCOAType InetAddressType
  mip6BindingHstCOA InetAddress
  mip6BindingHstTimeRegistered DateAndTime
  mip6BindingHstTimeExpired DateAndTime
  mip6BindingHstHomeRegn TruthValue
  mip6BindingHstUsageTS DateAndTime
  mip6BindingHstUsageCount Gauge32

Mip6NodeTrafficEntry  
SEQUENCE    
  mip6NodeInOctets Counter32
  mip6HCNodeInOctets Counter64
  mip6NodeInPkts Counter32
  mip6HCNodeInPkts Counter64
  mip6NodeOutOctets Counter32
  mip6HCNodeOutOctets Counter64
  mip6NodeOutPkts Counter32
  mip6HCNodeOutPkts Counter64
  mip6NodeCtrDiscontinuityTime TimeStamp

Mip6MnHomeAddressEntry  
SEQUENCE    
  mip6MnHomeAddressType InetAddressType
  mip6MnHomeAddress InetAddress
  mip6MnHomeAddressState INTEGER

Mip6MnBLEntry  
SEQUENCE    
  mip6MnBLNodeAddressType InetAddressType
  mip6MnBLNodeAddress InetAddress
  mip6MnBLCOAType InetAddressType
  mip6MnBLCOA InetAddress
  mip6MnBLLifeTimeRequested Unsigned32
  mip6MnBLLifeTimeGranted Unsigned32
  mip6MnBLMaxSeq Unsigned32
  mip6MnBLTimeSent DateAndTime
  mip6MnBLAccepted TruthValue
  mip6MnBLAcceptedTime DateAndTime
  mip6MnBLRetransmissions Gauge32
  mip6MnBLDontSendBUFlag TruthValue

Mip6CnCounterEntry  
SEQUENCE    
  mip6CnBURequestsAccepted Counter32
  mip6CnBURequestsRejected Counter32
  mip6CnBCEntryCreationTime DateAndTime
  mip6CnBUAcceptedTime DateAndTime
  mip6CnBURejectionTime DateAndTime
  mip6CnBURejectionCode Mip6BURequestRejectionCode
  mip6CnCtrDiscontinuityTime TimeStamp

Mip6HaConfEntry  
SEQUENCE    
  mip6HaAdvPreference Integer32
  mip6HaAdvLifetime Integer32
  mip6HaPrefixAdv INTEGER
  mip6HaPrefixSolicitation INTEGER
  mip6HaMCastCtlMsgSupport INTEGER

Mip6HaCounterEntry  
SEQUENCE    
  mip6HaBURequestsAccepted Counter32
  mip6HaBURequestsDenied Counter32
  mip6HaBCEntryCreationTime DateAndTime
  mip6HaBUAcceptedTime DateAndTime
  mip6HaBURejectionTime DateAndTime
  mip6HaRecentBURejectionCode Mip6BURequestRejectionCode
  mip6HaCtrDiscontinuityTime TimeStamp

Mip6HaListEntry  
SEQUENCE    
  mip6HaLinkLocalAddressType InetAddressType
  mip6HaLinkLocalAddress InetAddress
  mip6HaPreference Integer32
  mip6HaRecvLifeTime Gauge32
  mip6HaRecvTimeStamp DateAndTime

Mip6HaGlAddrEntry  
SEQUENCE    
  mip6HaGaAddrSeqNo Integer32
  mip6HaGaGlobalAddressType InetAddressType
  mip6HaGaGlobalAddress InetAddress

Defined Values

mip6MIB 1.3.6.1.2.1.133
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.
MODULE-IDENTITY    

mip6Notifications 1.3.6.1.2.1.133.0
OBJECT IDENTIFIER    

mip6Objects 1.3.6.1.2.1.133.1
OBJECT IDENTIFIER    

mip6Conformance 1.3.6.1.2.1.133.2
OBJECT IDENTIFIER    

mip6Core 1.3.6.1.2.1.133.1.1
OBJECT IDENTIFIER    

mip6Mn 1.3.6.1.2.1.133.1.2
OBJECT IDENTIFIER    

mip6Cn 1.3.6.1.2.1.133.1.3
OBJECT IDENTIFIER    

mip6Ha 1.3.6.1.2.1.133.1.4
OBJECT IDENTIFIER    

mip6System 1.3.6.1.2.1.133.1.1.1
OBJECT IDENTIFIER    

mip6Bindings 1.3.6.1.2.1.133.1.1.2
OBJECT IDENTIFIER    

mip6Stats 1.3.6.1.2.1.133.1.1.3
OBJECT IDENTIFIER    

mip6MnSystem 1.3.6.1.2.1.133.1.2.1
OBJECT IDENTIFIER    

mip6MnConf 1.3.6.1.2.1.133.1.2.2
OBJECT IDENTIFIER    

mip6MnRegistration 1.3.6.1.2.1.133.1.2.3
OBJECT IDENTIFIER    

mip6CnSystem 1.3.6.1.2.1.133.1.3.1
OBJECT IDENTIFIER    

mip6CnStats 1.3.6.1.2.1.133.1.3.2
OBJECT IDENTIFIER    

mip6HaAdvertisement 1.3.6.1.2.1.133.1.4.1
OBJECT IDENTIFIER    

mip6HaStats 1.3.6.1.2.1.133.1.4.2
OBJECT IDENTIFIER    

mip6Capabilities 1.3.6.1.2.1.133.1.1.1.1
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.
OBJECT-TYPE    
  BITS mobileNode(0), homeAgent(1), correspondentNode(2)  

mip6Status 1.3.6.1.2.1.133.1.1.1.2
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.
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

mip6BindingCacheTable 1.3.6.1.2.1.133.1.1.2.1
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.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6BindingCacheEntry

mip6BindingCacheEntry 1.3.6.1.2.1.133.1.1.2.1.1
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.
OBJECT-TYPE    
  Mip6BindingCacheEntry  

mip6BindingHomeAddressType 1.3.6.1.2.1.133.1.1.2.1.1.1
The InetAddressType of the mip6BindingHomeAddress that follows.
OBJECT-TYPE    
  InetAddressType  

mip6BindingHomeAddress 1.3.6.1.2.1.133.1.1.2.1.1.2
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.
OBJECT-TYPE    
  InetAddress  

mip6BindingCOAType 1.3.6.1.2.1.133.1.1.2.1.1.3
The InetAddressType of the mip6BindingCOA that follows.
OBJECT-TYPE    
  InetAddressType  

mip6BindingCOA 1.3.6.1.2.1.133.1.1.2.1.1.4
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.
OBJECT-TYPE    
  InetAddress  

mip6BindingTimeRegistered 1.3.6.1.2.1.133.1.1.2.1.1.5
The timestamp when this Binding Cache entry was created.
OBJECT-TYPE    
  DateAndTime  

mip6BindingTimeGranted 1.3.6.1.2.1.133.1.1.2.1.1.6
The lifetime in seconds granted to the mobile node for this registration.
OBJECT-TYPE    
  Gauge32  

mip6BindingTimeRemaining 1.3.6.1.2.1.133.1.1.2.1.1.7
The lifetime in seconds remaining for this registration.
OBJECT-TYPE    
  Gauge32  

mip6BindingHomeRegn 1.3.6.1.2.1.133.1.1.2.1.1.8
This object indicates whether or not this Binding Cache entry is a home registration entry (applicable only on nodes that support home agent functionality).
OBJECT-TYPE    
  TruthValue  

mip6BindingMaxSeq 1.3.6.1.2.1.133.1.1.2.1.1.9
The maximum value of the Sequence Number field received in previous Binding Updates for this home address (mip6BindingHomeAddress).
OBJECT-TYPE    
  Unsigned32 0..65536  

mip6BindingUsageTS 1.3.6.1.2.1.133.1.1.2.1.1.10
The timestamp when this entry was last looked up.
OBJECT-TYPE    
  DateAndTime  

mip6BindingUsageCount 1.3.6.1.2.1.133.1.1.2.1.1.11
The number of times this entry was looked up.
OBJECT-TYPE    
  Gauge32  

mip6BindingAdminStatus 1.3.6.1.2.1.133.1.1.2.1.1.12
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.
OBJECT-TYPE    
  INTEGER active(1), inactive(2)  

mip6BindingHistoryTable 1.3.6.1.2.1.133.1.1.2.2
A table containing a record of the bindings.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6BindingHistoryEntry

mip6BindingHistoryEntry 1.3.6.1.2.1.133.1.1.2.2.1
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.
OBJECT-TYPE    
  Mip6BindingHistoryEntry  

mip6BindingHstHomeAddressType 1.3.6.1.2.1.133.1.1.2.2.1.1
The InetAddressType of the mip6BindingHstHomeAddress that follows.
OBJECT-TYPE    
  InetAddressType  

mip6BindingHstHomeAddress 1.3.6.1.2.1.133.1.1.2.2.1.2
Mobile node's home address. The type of the address represented by this object is specified by the corresponding mip6BindingHstHomeAddressType object.
OBJECT-TYPE    
  InetAddress  

mip6BindingHstIndex 1.3.6.1.2.1.133.1.1.2.2.1.3
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.
OBJECT-TYPE    
  Unsigned32 1..4294967295  

mip6BindingHstCOAType 1.3.6.1.2.1.133.1.1.2.2.1.4
The InetAddressType of the mip6BindingHstCOA that follows.
OBJECT-TYPE    
  InetAddressType  

mip6BindingHstCOA 1.3.6.1.2.1.133.1.1.2.2.1.5
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.
OBJECT-TYPE    
  InetAddress  

mip6BindingHstTimeRegistered 1.3.6.1.2.1.133.1.1.2.2.1.6
The timestamp when this Binding Cache entry was created.
OBJECT-TYPE    
  DateAndTime  

mip6BindingHstTimeExpired 1.3.6.1.2.1.133.1.1.2.2.1.7
The timestamp when this Binding Cache entry expired.
OBJECT-TYPE    
  DateAndTime  

mip6BindingHstHomeRegn 1.3.6.1.2.1.133.1.1.2.2.1.8
This object indicates whether or not this Binding Cache entry is a home registration entry (applicable only on nodes that support home agent functionality).
OBJECT-TYPE    
  TruthValue  

mip6BindingHstUsageTS 1.3.6.1.2.1.133.1.1.2.2.1.9
The timestamp when this entry was last looked up.
OBJECT-TYPE    
  DateAndTime  

mip6BindingHstUsageCount 1.3.6.1.2.1.133.1.1.2.2.1.10
The number of times this entry was looked up.
OBJECT-TYPE    
  Gauge32  

mip6TotalTraffic 1.3.6.1.2.1.133.1.1.3.1
OBJECT IDENTIFIER    

mip6InOctets 1.3.6.1.2.1.133.1.1.3.1.1
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.
OBJECT-TYPE    
  Counter32  

mip6HCInOctets 1.3.6.1.2.1.133.1.1.3.1.2
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.
OBJECT-TYPE    
  Counter64  

mip6InPkts 1.3.6.1.2.1.133.1.1.3.1.3
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.
OBJECT-TYPE    
  Counter32  

mip6HCInPkts 1.3.6.1.2.1.133.1.1.3.1.4
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.
OBJECT-TYPE    
  Counter64  

mip6OutOctets 1.3.6.1.2.1.133.1.1.3.1.5
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.
OBJECT-TYPE    
  Counter32  

mip6HCOutOctets 1.3.6.1.2.1.133.1.1.3.1.6
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.
OBJECT-TYPE    
  Counter64  

mip6OutPkts 1.3.6.1.2.1.133.1.1.3.1.7
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.
OBJECT-TYPE    
  Counter32  

mip6HCOutPkts 1.3.6.1.2.1.133.1.1.3.1.8
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.
OBJECT-TYPE    
  Counter64  

mip6CounterDiscontinuityTime 1.3.6.1.2.1.133.1.1.3.1.9
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.
OBJECT-TYPE    
  TimeStamp  

mip6NodeTrafficTable 1.3.6.1.2.1.133.1.1.3.2
A table containing MIPv6 traffic counters per mobile node.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6NodeTrafficEntry

mip6NodeTrafficEntry 1.3.6.1.2.1.133.1.1.3.2.1
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.
OBJECT-TYPE    
  Mip6NodeTrafficEntry  

mip6NodeInOctets 1.3.6.1.2.1.133.1.1.3.2.1.1
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.
OBJECT-TYPE    
  Counter32  

mip6HCNodeInOctets 1.3.6.1.2.1.133.1.1.3.2.1.2
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.
OBJECT-TYPE    
  Counter64  

mip6NodeInPkts 1.3.6.1.2.1.133.1.1.3.2.1.3
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.
OBJECT-TYPE    
  Counter32  

mip6HCNodeInPkts 1.3.6.1.2.1.133.1.1.3.2.1.4
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.
OBJECT-TYPE    
  Counter64  

mip6NodeOutOctets 1.3.6.1.2.1.133.1.1.3.2.1.5
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.
OBJECT-TYPE    
  Counter32  

mip6HCNodeOutOctets 1.3.6.1.2.1.133.1.1.3.2.1.6
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.
OBJECT-TYPE    
  Counter64  

mip6NodeOutPkts 1.3.6.1.2.1.133.1.1.3.2.1.7
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.
OBJECT-TYPE    
  Counter32  

mip6HCNodeOutPkts 1.3.6.1.2.1.133.1.1.3.2.1.8
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.
OBJECT-TYPE    
  Counter64  

mip6NodeCtrDiscontinuityTime 1.3.6.1.2.1.133.1.1.3.2.1.9
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.
OBJECT-TYPE    
  TimeStamp  

mip6MnHomeAddressTable 1.3.6.1.2.1.133.1.2.1.1
A table containing registration status for all the home addresses pertaining to the mobile node.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6MnHomeAddressEntry

mip6MnHomeAddressEntry 1.3.6.1.2.1.133.1.2.1.1.1
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.
OBJECT-TYPE    
  Mip6MnHomeAddressEntry  

mip6MnHomeAddressType 1.3.6.1.2.1.133.1.2.1.1.1.1
The InetAddressType of the mip6MnHomeAddress that follows.
OBJECT-TYPE    
  InetAddressType  

mip6MnHomeAddress 1.3.6.1.2.1.133.1.2.1.1.1.2
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.
OBJECT-TYPE    
  InetAddress  

mip6MnHomeAddressState 1.3.6.1.2.1.133.1.2.1.1.1.3
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.
OBJECT-TYPE    
  INTEGER unknown(1), home(2), registered(3), pending(4), isolated(5)  

mip6MnDiscoveryRequests 1.3.6.1.2.1.133.1.2.2.1
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.
OBJECT-TYPE    
  Counter32  

mip6MnDiscoveryReplies 1.3.6.1.2.1.133.1.2.2.2
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.
OBJECT-TYPE    
  Counter32  

mip6MnDiscoveryTimeouts 1.3.6.1.2.1.133.1.2.2.3
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.
OBJECT-TYPE    
  Counter32  

mip6MnPrefixSolicitationsSent 1.3.6.1.2.1.133.1.2.2.4
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.
OBJECT-TYPE    
  Counter32  

mip6MnPrefixAdvsRecd 1.3.6.1.2.1.133.1.2.2.5
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.
OBJECT-TYPE    
  Counter32  

mip6MnPrefixAdvsIgnored 1.3.6.1.2.1.133.1.2.2.6
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.
OBJECT-TYPE    
  Counter32  

mip6MnMovedToFN 1.3.6.1.2.1.133.1.2.2.7
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.
OBJECT-TYPE    
  Counter32  

mip6MnMovedToHN 1.3.6.1.2.1.133.1.2.2.8
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.
OBJECT-TYPE    
  Counter32  

mip6MnBLTable 1.3.6.1.2.1.133.1.2.3.1
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.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6MnBLEntry

mip6MnBLEntry 1.3.6.1.2.1.133.1.2.3.1.1
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.
OBJECT-TYPE    
  Mip6MnBLEntry  

mip6MnBLNodeAddressType 1.3.6.1.2.1.133.1.2.3.1.1.1
The InetAddressType of the mip6MnBLNodeAddress that follows.
OBJECT-TYPE    
  InetAddressType  

mip6MnBLNodeAddress 1.3.6.1.2.1.133.1.2.3.1.1.2
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.
OBJECT-TYPE    
  InetAddress  

mip6MnBLCOAType 1.3.6.1.2.1.133.1.2.3.1.1.3
The InetAddressType of the mip6MnBLCOA that follows.
OBJECT-TYPE    
  InetAddressType  

mip6MnBLCOA 1.3.6.1.2.1.133.1.2.3.1.1.4
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.
OBJECT-TYPE    
  InetAddress  

mip6MnBLLifeTimeRequested 1.3.6.1.2.1.133.1.2.3.1.1.5
The lifetime requested by the mobile node (in seconds) in the Binding Update.
OBJECT-TYPE    
  Unsigned32  

mip6MnBLLifeTimeGranted 1.3.6.1.2.1.133.1.2.3.1.1.6
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.
OBJECT-TYPE    
  Unsigned32  

mip6MnBLMaxSeq 1.3.6.1.2.1.133.1.2.3.1.1.7
The maximum value of the Sequence Number field sent in previous Binding Updates to this destination.
OBJECT-TYPE    
  Unsigned32 0..65536  

mip6MnBLTimeSent 1.3.6.1.2.1.133.1.2.3.1.1.8
The time when the last (re-)transmission occurred.
OBJECT-TYPE    
  DateAndTime  

mip6MnBLAccepted 1.3.6.1.2.1.133.1.2.3.1.1.9
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.
OBJECT-TYPE    
  TruthValue  

mip6MnBLAcceptedTime 1.3.6.1.2.1.133.1.2.3.1.1.10
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.
OBJECT-TYPE    
  DateAndTime  

mip6MnBLRetransmissions 1.3.6.1.2.1.133.1.2.3.1.1.11
The number of Binding Update retransmissions.
OBJECT-TYPE    
  Gauge32  

mip6MnBLDontSendBUFlag 1.3.6.1.2.1.133.1.2.3.1.1.12
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.
OBJECT-TYPE    
  TruthValue  

mip6MnRegnCounters 1.3.6.1.2.1.133.1.2.3.2
OBJECT IDENTIFIER    

mip6MnMobilityMessagesSent 1.3.6.1.2.1.133.1.2.3.2.1
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.
OBJECT-TYPE    
  Counter32  

mip6MnMobilityMessagesRecd 1.3.6.1.2.1.133.1.2.3.2.2
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.
OBJECT-TYPE    
  Counter32  

mip6MnBUsToHA 1.3.6.1.2.1.133.1.2.3.2.3
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.
OBJECT-TYPE    
  Counter32  

mip6MnBUAcksFromHA 1.3.6.1.2.1.133.1.2.3.2.4
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.
OBJECT-TYPE    
  Counter32  

mip6MnBUsToCN 1.3.6.1.2.1.133.1.2.3.2.5
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.
OBJECT-TYPE    
  Counter32  

mip6MnBUAcksFromCN 1.3.6.1.2.1.133.1.2.3.2.6
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.
OBJECT-TYPE    
  Counter32  

mip6MnBindingErrorsFromCN 1.3.6.1.2.1.133.1.2.3.2.7
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.
OBJECT-TYPE    
  Counter32  

mip6MnICMPErrorsRecd 1.3.6.1.2.1.133.1.2.3.2.8
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.
OBJECT-TYPE    
  Counter32  

mip6MnBRRequestsRecd 1.3.6.1.2.1.133.1.2.3.2.9
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.
OBJECT-TYPE    
  Counter32  

mip6CnGlobalStats 1.3.6.1.2.1.133.1.3.2.1
OBJECT IDENTIFIER    

mip6CnHomeTestInitsRecd 1.3.6.1.2.1.133.1.3.2.1.1
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.
OBJECT-TYPE    
  Counter32  

mip6CnHomeTestsSent 1.3.6.1.2.1.133.1.3.2.1.2
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.
OBJECT-TYPE    
  Counter32  

mip6CnCareOfTestInitsRecd 1.3.6.1.2.1.133.1.3.2.1.3
Total number of Care-of Test Init messages received.
OBJECT-TYPE    
  Counter32  

mip6CnCareOfTestsSent 1.3.6.1.2.1.133.1.3.2.1.4
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.
OBJECT-TYPE    
  Counter32  

mip6CnBUsRecd 1.3.6.1.2.1.133.1.3.2.1.5
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.
OBJECT-TYPE    
  Counter32  

mip6CnBUAcksSent 1.3.6.1.2.1.133.1.3.2.1.6
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.
OBJECT-TYPE    
  Counter32  

mip6CnBRsSent 1.3.6.1.2.1.133.1.3.2.1.7
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.
OBJECT-TYPE    
  Counter32  

mip6CnBindingErrors 1.3.6.1.2.1.133.1.3.2.1.8
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.
OBJECT-TYPE    
  Counter32  

mip6CnBUsAccepted 1.3.6.1.2.1.133.1.3.2.1.9
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.
OBJECT-TYPE    
  Counter32  

mip6CnBUsRejected 1.3.6.1.2.1.133.1.3.2.1.10
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.
OBJECT-TYPE    
  Counter32  

mip6CnReasonUnspecified 1.3.6.1.2.1.133.1.3.2.1.11
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.
OBJECT-TYPE    
  Counter32  

mip6CnInsufficientResource 1.3.6.1.2.1.133.1.3.2.1.12
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.
OBJECT-TYPE    
  Counter32  

mip6CnHomeRegnNotSupported 1.3.6.1.2.1.133.1.3.2.1.13
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.
OBJECT-TYPE    
  Counter32  

mip6CnSeqNumberOutOfWindow 1.3.6.1.2.1.133.1.3.2.1.14
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.
OBJECT-TYPE    
  Counter32  

mip6CnExpiredHomeNonceIndex 1.3.6.1.2.1.133.1.3.2.1.15
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.
OBJECT-TYPE    
  Counter32  

mip6CnExpiredCareOfNonceIndex 1.3.6.1.2.1.133.1.3.2.1.16
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.
OBJECT-TYPE    
  Counter32  

mip6CnExpiredNonce 1.3.6.1.2.1.133.1.3.2.1.17
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.
OBJECT-TYPE    
  Counter32  

mip6CnRegTypeChangeDisallowed 1.3.6.1.2.1.133.1.3.2.1.18
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.
OBJECT-TYPE    
  Counter32  

mip6CnCounterTable 1.3.6.1.2.1.133.1.3.2.2
A table containing each mobile .
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6CnCounterEntry

mip6CnCounterEntry 1.3.6.1.2.1.133.1.3.2.2.1
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.
OBJECT-TYPE    
  Mip6CnCounterEntry  

mip6CnBURequestsAccepted 1.3.6.1.2.1.133.1.3.2.2.1.1
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.
OBJECT-TYPE    
  Counter32  

mip6CnBURequestsRejected 1.3.6.1.2.1.133.1.3.2.2.1.2
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.
OBJECT-TYPE    
  Counter32  

mip6CnBCEntryCreationTime 1.3.6.1.2.1.133.1.3.2.2.1.3
The time when the current Binding Cache entry was created for the mobile node.
OBJECT-TYPE    
  DateAndTime  

mip6CnBUAcceptedTime 1.3.6.1.2.1.133.1.3.2.2.1.4
The time at which the last Binding Update was accepted by the correspondent node and the corresponding Binding Cache entry was updated.
OBJECT-TYPE    
  DateAndTime  

mip6CnBURejectionTime 1.3.6.1.2.1.133.1.3.2.2.1.5
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.
OBJECT-TYPE    
  DateAndTime  

mip6CnBURejectionCode 1.3.6.1.2.1.133.1.3.2.2.1.6
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.
OBJECT-TYPE    
  Mip6BURequestRejectionCode  

mip6CnCtrDiscontinuityTime 1.3.6.1.2.1.133.1.3.2.2.1.7
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.
OBJECT-TYPE    
  TimeStamp  

mip6HaAdvsRecd 1.3.6.1.2.1.133.1.4.1.1
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.
OBJECT-TYPE    
  Counter32  

mip6HaAdvsSent 1.3.6.1.2.1.133.1.4.1.2
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.
OBJECT-TYPE    
  Counter32  

mip6HaConfTable 1.3.6.1.2.1.133.1.4.1.3
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.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6HaConfEntry

mip6HaConfEntry 1.3.6.1.2.1.133.1.4.1.3.1
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.
OBJECT-TYPE    
  Mip6HaConfEntry  

mip6HaAdvPreference 1.3.6.1.2.1.133.1.4.1.3.1.1
The preference value for the home agent to be used in the Router Advertisements. Higher value denotes greater preference.
OBJECT-TYPE    
  Integer32 0..65536  

mip6HaAdvLifetime 1.3.6.1.2.1.133.1.4.1.3.1.2
The lifetime value for the home agent to be used in the Router Advertisements.
OBJECT-TYPE    
  Integer32 1..65535  

mip6HaPrefixAdv 1.3.6.1.2.1.133.1.4.1.3.1.3
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.
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

mip6HaPrefixSolicitation 1.3.6.1.2.1.133.1.4.1.3.1.4
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.
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

mip6HaMCastCtlMsgSupport 1.3.6.1.2.1.133.1.4.1.3.1.5
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.
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

mip6HaGlobalStats 1.3.6.1.2.1.133.1.4.2.1
OBJECT IDENTIFIER    

mip6HaHomeTestInitsRecd 1.3.6.1.2.1.133.1.4.2.1.1
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.
OBJECT-TYPE    
  Counter32  

mip6HaHomeTestsSent 1.3.6.1.2.1.133.1.4.2.1.2
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.
OBJECT-TYPE    
  Counter32  

mip6HaBUsRecd 1.3.6.1.2.1.133.1.4.2.1.3
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.
OBJECT-TYPE    
  Counter32  

mip6HaBUAcksSent 1.3.6.1.2.1.133.1.4.2.1.4
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.
OBJECT-TYPE    
  Counter32  

mip6HaBRAdviceSent 1.3.6.1.2.1.133.1.4.2.1.5
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.
OBJECT-TYPE    
  Counter32  

mip6HaBUsAccepted 1.3.6.1.2.1.133.1.4.2.1.6
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.
OBJECT-TYPE    
  Counter32  

mip6HaPrefDiscoverReqd 1.3.6.1.2.1.133.1.4.2.1.7
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.
OBJECT-TYPE    
  Counter32  

mip6HaReasonUnspecified 1.3.6.1.2.1.133.1.4.2.1.8
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.
OBJECT-TYPE    
  Counter32  

mip6HaAdmProhibited 1.3.6.1.2.1.133.1.4.2.1.9
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.
OBJECT-TYPE    
  Counter32  

mip6HaInsufficientResource 1.3.6.1.2.1.133.1.4.2.1.10
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.
OBJECT-TYPE    
  Counter32  

mip6HaHomeRegnNotSupported 1.3.6.1.2.1.133.1.4.2.1.11
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.
OBJECT-TYPE    
  Counter32  

mip6HaNotHomeSubnet 1.3.6.1.2.1.133.1.4.2.1.12
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.
OBJECT-TYPE    
  Counter32  

mip6HaNotHomeAgentForThisMN 1.3.6.1.2.1.133.1.4.2.1.13
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.
OBJECT-TYPE    
  Counter32  

mip6HaDupAddrDetectionFailed 1.3.6.1.2.1.133.1.4.2.1.14
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.
OBJECT-TYPE    
  Counter32  

mip6HaSeqNumberOutOfWindow 1.3.6.1.2.1.133.1.4.2.1.15
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.
OBJECT-TYPE    
  Counter32  

mip6HaExpiredHomeNonceIndex 1.3.6.1.2.1.133.1.4.2.1.16
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.
OBJECT-TYPE    
  Counter32  

mip6HaRegTypeChangeDisallowed 1.3.6.1.2.1.133.1.4.2.1.17
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.
OBJECT-TYPE    
  Counter32  

mip6HaCounterTable 1.3.6.1.2.1.133.1.4.2.2
A table containing registration statistics for all mobile nodes registered with the home agent.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6HaCounterEntry

mip6HaCounterEntry 1.3.6.1.2.1.133.1.4.2.2.1
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.
OBJECT-TYPE    
  Mip6HaCounterEntry  

mip6HaBURequestsAccepted 1.3.6.1.2.1.133.1.4.2.2.1.1
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.
OBJECT-TYPE    
  Counter32  

mip6HaBURequestsDenied 1.3.6.1.2.1.133.1.4.2.2.1.2
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.
OBJECT-TYPE    
  Counter32  

mip6HaBCEntryCreationTime 1.3.6.1.2.1.133.1.4.2.2.1.3
The time when the current Binding Cache entry was created for the mobile node.
OBJECT-TYPE    
  DateAndTime  

mip6HaBUAcceptedTime 1.3.6.1.2.1.133.1.4.2.2.1.4
The time at which the last Binding Update was accepted by the home agent for this mobile node.
OBJECT-TYPE    
  DateAndTime  

mip6HaBURejectionTime 1.3.6.1.2.1.133.1.4.2.2.1.5
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.
OBJECT-TYPE    
  DateAndTime  

mip6HaRecentBURejectionCode 1.3.6.1.2.1.133.1.4.2.2.1.6
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.
OBJECT-TYPE    
  Mip6BURequestRejectionCode  

mip6HaCtrDiscontinuityTime 1.3.6.1.2.1.133.1.4.2.2.1.7
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.
OBJECT-TYPE    
  TimeStamp  

mip6HaListTable 1.3.6.1.2.1.133.1.4.1.4
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.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6HaListEntry

mip6HaListEntry 1.3.6.1.2.1.133.1.4.1.4.1
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.
OBJECT-TYPE    
  Mip6HaListEntry  

mip6HaLinkLocalAddressType 1.3.6.1.2.1.133.1.4.1.4.1.1
The address type for the link-local address of the home agent that follows.
OBJECT-TYPE    
  InetAddressType  

mip6HaLinkLocalAddress 1.3.6.1.2.1.133.1.4.1.4.1.2
The link local address of the home agent. The type of the address represented by this object is specified by the corresponding mip6HaLinkLocalAddressType object.
OBJECT-TYPE    
  InetAddress  

mip6HaPreference 1.3.6.1.2.1.133.1.4.1.4.1.3
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.
OBJECT-TYPE    
  Integer32  

mip6HaRecvLifeTime 1.3.6.1.2.1.133.1.4.1.4.1.4
The lifetime for this home agent.
OBJECT-TYPE    
  Gauge32  

mip6HaRecvTimeStamp 1.3.6.1.2.1.133.1.4.1.4.1.5
The time when the home agent advertisement was received.
OBJECT-TYPE    
  DateAndTime  

mip6HaGlAddrTable 1.3.6.1.2.1.133.1.4.1.5
This table contains the global addresses of the home agents in the Home Agents List.
OBJECT-TYPE    
  SEQUENCE OF  
    Mip6HaGlAddrEntry

mip6HaGlAddrEntry 1.3.6.1.2.1.133.1.4.1.5.1
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.
OBJECT-TYPE    
  Mip6HaGlAddrEntry  

mip6HaGaAddrSeqNo 1.3.6.1.2.1.133.1.4.1.5.1.1
The index that along with ipv6InterfaceIfIndex, mip6HaLinkLocalAddressType, and mip6HaLinkLocalAddress uniquely identifies this row.
OBJECT-TYPE    
  Integer32 1..1024  

mip6HaGaGlobalAddressType 1.3.6.1.2.1.133.1.4.1.5.1.2
The address type for the global address of the home agent that follows.
OBJECT-TYPE    
  InetAddressType  

mip6HaGaGlobalAddress 1.3.6.1.2.1.133.1.4.1.5.1.3
A global address of the home agent. The type of the address represented by this object is specified by the corresponding mip6HaGaGlobalAddressType object.
OBJECT-TYPE    
  InetAddress  

mip6MnRegistered 1.3.6.1.2.1.133.0.1
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.
NOTIFICATION-TYPE    

mip6MnDeRegistered 1.3.6.1.2.1.133.0.2
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.
NOTIFICATION-TYPE    

mip6MnCOAChanged 1.3.6.1.2.1.133.0.3
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.
NOTIFICATION-TYPE    

mip6MnBindingExpiredAtHA 1.3.6.1.2.1.133.0.4
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.
NOTIFICATION-TYPE    

mip6MnBindingExpiredAtCN 1.3.6.1.2.1.133.0.5
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.
NOTIFICATION-TYPE    

mip6Groups 1.3.6.1.2.1.133.2.1
OBJECT IDENTIFIER    

mip6Compliances 1.3.6.1.2.1.133.2.2
OBJECT IDENTIFIER    

mip6SystemGroup 1.3.6.1.2.1.133.2.1.1
A collection of objects for basic MIPv6 monitoring.
OBJECT-GROUP    

mip6BindingCacheGroup 1.3.6.1.2.1.133.2.1.2
A collection of objects for monitoring the Binding Cache.
OBJECT-GROUP    

mip6BindingHstGroup 1.3.6.1.2.1.133.2.1.3
A collection of objects for monitoring the Binding History. This can be used to monitor the movement of the mobile node.
OBJECT-GROUP    

mip6TotalTrafficGroup 1.3.6.1.2.1.133.2.1.4
A collection of objects for monitoring the total MIPv6 traffic.
OBJECT-GROUP    

mip6NodeTrafficGroup 1.3.6.1.2.1.133.2.1.5
A collection of objects for monitoring the MIPv6 traffic due to a mobile node.
OBJECT-GROUP    

mip6MnSystemGroup 1.3.6.1.2.1.133.2.1.6
A collection of objects for basic monitoring of the mobile node.
OBJECT-GROUP    

mip6MnConfGroup 1.3.6.1.2.1.133.2.1.7
A collection of objects for monitoring the advertisement-related info on the mobile node.
OBJECT-GROUP    

mip6MnRegistrationGroup 1.3.6.1.2.1.133.2.1.8
A collection of objects for monitoring the registration statistics for the mobile node.
OBJECT-GROUP    

mip6CnStatsGroup 1.3.6.1.2.1.133.2.1.9
A collection of objects for monitoring the control messages and corresponding statistics for each mobile node communicating with the correspondent node.
OBJECT-GROUP    

mip6HaSystemGroup 1.3.6.1.2.1.133.2.1.10
A collection of objects for monitoring the advertisement-related parameters and statistics for the home agent.
OBJECT-GROUP    

mip6HaListGroup 1.3.6.1.2.1.133.2.1.11
A collection of objects for monitoring the Home Agent List on the home agent.
OBJECT-GROUP    

mip6HaStatsGroup 1.3.6.1.2.1.133.2.1.12
A collection of objects for monitoring registration-related statistics on the home agent.
OBJECT-GROUP    

mip6CnGlobalStatsGroup 1.3.6.1.2.1.133.2.1.13
A collection of objects for monitoring advertisement and registration statistics on a correspondent node.
OBJECT-GROUP    

mip6HaGlobalStatsGroup 1.3.6.1.2.1.133.2.1.14
A collection of objects for monitoring advertisement and registration statistics on a home agent.
OBJECT-GROUP    

mip6BindingCacheCtlGroup 1.3.6.1.2.1.133.2.1.15
A collection of objects for controlling the Binding Cache.
OBJECT-GROUP    

mip6NotificationGroup 1.3.6.1.2.1.133.2.1.16
A collection of notifications from a home agent or correspondent node to the Manager about the status of a mobile node.
NOTIFICATION-GROUP    

mip6CoreCompliance 1.3.6.1.2.1.133.2.2.1
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB.
MODULE-COMPLIANCE    

mip6Compliance2 1.3.6.1.2.1.133.2.2.2
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. --
MODULE-COMPLIANCE    

mip6Compliance3 1.3.6.1.2.1.133.2.2.3
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. --
MODULE-COMPLIANCE    

mip6CoreReadOnlyCompliance 1.3.6.1.2.1.133.2.2.4
Write access is not required.
MODULE-COMPLIANCE    

mip6ReadOnlyCompliance2 1.3.6.1.2.1.133.2.2.5
Write access is not required.
MODULE-COMPLIANCE    

mip6ReadOnlyCompliance3 1.3.6.1.2.1.133.2.2.6
Write access is not required.
MODULE-COMPLIANCE    

mip6MnCoreCompliance 1.3.6.1.2.1.133.2.2.7
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. --
MODULE-COMPLIANCE    

mip6MnCompliance2 1.3.6.1.2.1.133.2.2.8
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. --
MODULE-COMPLIANCE    

mip6CnCoreCompliance 1.3.6.1.2.1.133.2.2.9
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic correspondent node functionality.
MODULE-COMPLIANCE    

mip6CnCompliance 1.3.6.1.2.1.133.2.2.10
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.
MODULE-COMPLIANCE    

mip6HaCoreCompliance 1.3.6.1.2.1.133.2.2.11
The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic home agent functionality.
MODULE-COMPLIANCE    

mip6HaCompliance2 1.3.6.1.2.1.133.2.2.12
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. --
MODULE-COMPLIANCE    

mip6HaCompliance3 1.3.6.1.2.1.133.2.2.13
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. --
MODULE-COMPLIANCE    

mip6HaCoreReadOnlyCompliance 1.3.6.1.2.1.133.2.2.14
Write access is not required.
MODULE-COMPLIANCE    

mip6HaReadOnlyCompliance2 1.3.6.1.2.1.133.2.2.15
Write access is not required.
MODULE-COMPLIANCE    

mip6HaReadOnlyCompliance3 1.3.6.1.2.1.133.2.2.16
Write access is not required.
MODULE-COMPLIANCE    

mip6NotificationCompliance 1.3.6.1.2.1.133.2.2.17
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.
MODULE-COMPLIANCE