[RFCs/IDs] [Plain Text] [From draft-ietf-mip6-mipv6-mib]
PROPOSED STANDARD
Errata
Network Working Group G. Keeni
Request for Comments: 4295 Cyber Solutions Inc.
Category: Standards Track K. Koide
Tohoku University
K. Nagami
INTEC NetCore Inc.
S. Gundavelli
Cisco Systems Inc.
April 2006
Mobile IPv6 Management Information Base
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This memo defines a portion of the Management Information Base (MIB),
the Mobile-IPv6 MIB, for use with network management protocols in the
Internet community. In particular, the Mobile-IPv6 MIB will be used
to monitor and control the mobile node, home agent, and correspondent
node functions of a Mobile IPv6 (MIPv6) entity.
Table of Contents
1. The Internet-Standard Management Framework ......................2
2. Overview ........................................................2
2.1. The Mobile IPv6 Protocol Entities ..........................2
2.2. Terminology ................................................3
3. Mobile IPv6 Monitoring and Control Requirements .................3
4. MIB Design ......................................................4
5. The Mobile-IPv6 MIB .............................................6
6. Security Considerations .......................................104
7. IANA Considerations ...........................................106
8. References ....................................................106
8.1. Normative References .....................................106
8.2. Informative References ...................................107
9. Acknowledgements ..............................................107
Keeni, et al. Standards Track [Page 1]
RFC 4295 MOBILEIPV6-MIB April 2006
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
2. Overview
2.1. The Mobile IPv6 Protocol Entities
Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol that allows nodes
to remain reachable while moving around in the IPv6 Internet. An
entity that implements the MIPv6 protocol is a MIPv6 entity. There
are three types of entities envisaged by the MIPv6 protocol.
mobile node (MN): A node that can change its point of attachment
from one link to another, while still being reachable via its home
address.
correspondent node (CN): A peer node with which a mobile node is
communicating. The correspondent node may be either mobile or
stationary. (Note that a correspondent node does not necessarily
require MIPv6 support.)
home agent (HA): A router on a mobile node's home link with which
the mobile node has registered its current care-of address. While
the mobile node is away from home, the home agent intercepts
packets on the home link destined to the mobile node's home
address, encapsulates them, and routes them to the mobile node's
registered care-of address.
This document defines a set of managed objects (MOs) that can be used
to monitor and control MIPv6 entities.
Keeni, et al. Standards Track [Page 2]
RFC 4295 MOBILEIPV6-MIB April 2006
2.2. Terminology
The terminology used in this document is consistent with the
definitions used in Mobile IPv6 protocol specification [RFC3775].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14, RFC 2119 [RFC2119].
3. Mobile IPv6 Monitoring and Control Requirements
For managing a MIPv6 entity it is necessary to monitor
the following:
o capabilities of MIPv6 entities
o traffic due to MIPv6
o binding-related statistics (at home agent, correspondent
node, and mobile node)
o binding details (at home agent and correspondent node)
o history of Binding Updates (at home agent, correspondent
node, and mobile node)
The MIPv6 protocol document stipulates that several MIPv6-related
parameters should be manually configurable. The MIPv6 MIB should
define managed objects that can be used to configure the related
parameters, for example:
o the preference value the home agent will use in Router
Advertisements;
o the lifetime value the home agent will use in Router
Advertisements;
o whether a home agent will send ICMP Mobile Prefix
Advertisements to mobile nodes;
o whether a home agent will respond to ICMP Mobile Prefix
Solicitation messages from mobile nodes; and
o whether a home agent will process multicast group membership
control messages from mobile nodes.
Keeni, et al. Standards Track [Page 3]
RFC 4295 MOBILEIPV6-MIB April 2006
4. MIB Design
The basic principle has been to keep the MIB as simple as possible
and at the same time to make it effective enough so that the
essential needs of monitoring and control are met. It is envisaged
that wherever possible existing MIBs will be used (e.g., IPSec MIB,
Neighbor Discovery MIB, Tunnel MIB [RFC4087]) for monitor and control
of MIPv6 entities.
It is assumed that the Mobile IPv6 Management Information Base
(MOBILEIPV6-MIB) will always be implemented in conjunction with the
IPv6-capable version of the IP-MIB [RFC4293]. The MOBILEIPV6-MIB
uses the textual conventions defined in the INET-ADDRESS-MIB
[RFC4001].
The Mobile-IPv6 MIB is composed of the following groups of
definitions:
- mip6Core: a generic group containing objects that are
common to all the Mobile IPv6 entities.
- mip6Ha: this group models the home agent service. It is
composed of objects specific to the services and associated
advertisement parameters offered by the home agent on each
of its links. It also contains objects pertaining to the
maintenance of the home agent list on each of the links on
which the service is offered.
- mip6Mn: this group models the mobile node service. It is
composed of objects specific to the Dynamic Home Agent
discovery function and related parameters. It also contains
objects that record the movement of the mobile node.
- mip6Cn: models the correspondent node and is primarily
scoped to its participation in the Return Routability
procedure for achieving Route Optimization triggered by
the mobile node.
- mip6Notifications: defines the set of notifications that
will be used to asynchronously monitor the Mobile IPv6
entities.
The tables contained in the above groups are as follows:
mip6BindingCacheTable : models the binding cache on the home
agent and correspondent node. It
contains details of the Binding Update
requests that have been received and
accepted.
mip6BindingHistoryTable : tracks the history of the binding
cache.
mip6NodeTrafficTable : the mobile node-wise traffic counters.
Keeni, et al. Standards Track [Page 4]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6MnHomeAddressTable : contains all the home addresses
pertaining to the mobile node and
the corresponding registration status.
mip6MnBLTable : models the Binding Update List on the
mobile node. It contains information
about the registration requests sent
by the mobile node and the
corresponding results.
mip6CnCounterTable : contains the mobile node-wise
registration statistics.
mip6HaConfTable : contains the configurable
advertisement parameters for all the
interfaces on which the home agent
service is advertised.
mip6HaCounterTable : contains registration statistics
for all mobile nodes registered
with the home agent.
mip6HaListTable : 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.
mip6HaGlAddrTable : contains the global addresses of
the home agents.
Keeni, et al. Standards Track [Page 5]
RFC 4295 MOBILEIPV6-MIB April 2006
5. The Mobile-IPv6 MIB.
MOBILEIPV6-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32, Integer32, Counter32,
Gauge32, Counter64,
OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
TruthValue, DateAndTime, TimeStamp
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB
ipv6InterfaceIfIndex
FROM IP-MIB
;
mip6MIB MODULE-IDENTITY
LAST-UPDATED "200602010000Z" -- 1st February 2006
ORGANIZATION "IETF mip6 Working Group"
CONTACT-INFO
" 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
Keeni, et al. Standards Track [Page 6]
RFC 4295 MOBILEIPV6-MIB April 2006
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"
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.
"
REVISION "200602010000Z" -- 1st February 2006
DESCRIPTION "Initial version, published as RFC 4295."
::= { mib-2 133 }
-- The major groups
mip6Notifications OBJECT IDENTIFIER ::= { mip6MIB 0 }
mip6Objects OBJECT IDENTIFIER ::= { mip6MIB 1 }
mip6Conformance OBJECT IDENTIFIER ::= { mip6MIB 2 }
mip6Core OBJECT IDENTIFIER ::= { mip6Objects 1 }
mip6Mn OBJECT IDENTIFIER ::= { mip6Objects 2 }
mip6Cn OBJECT IDENTIFIER ::= { mip6Objects 3 }
mip6Ha OBJECT IDENTIFIER ::= { mip6Objects 4 }
-- The sub groups
mip6System OBJECT IDENTIFIER ::= { mip6Core 1 }
mip6Bindings OBJECT IDENTIFIER ::= { mip6Core 2 }
mip6Stats OBJECT IDENTIFIER ::= { mip6Core 3 }
mip6MnSystem OBJECT IDENTIFIER ::= { mip6Mn 1 }
mip6MnConf OBJECT IDENTIFIER ::= { mip6Mn 2 }
mip6MnRegistration OBJECT IDENTIFIER ::= { mip6Mn 3 }
mip6CnSystem OBJECT IDENTIFIER ::= { mip6Cn 1 }
Keeni, et al. Standards Track [Page 7]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6CnStats OBJECT IDENTIFIER ::= { mip6Cn 2 }
mip6HaAdvertisement OBJECT IDENTIFIER ::= { mip6Ha 1 }
mip6HaStats OBJECT IDENTIFIER ::= { mip6Ha 2 }
-- Textual Conventions
Mip6BURequestRejectionCode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of the status field in the Binding
Acknowledgment message when the Binding Update
was rejected.
"
REFERENCE
"RFC 3775 : Section 6.1.8"
SYNTAX INTEGER {
reasonUnspecified (1), --(Code 128)
admProhibited (2), --(Code 129)
insufficientResource (3), --(Code 130)
homeRegistrationNotSupported (4), --(Code 131)
notHomeSubnet (5), --(Code 132)
notHomeAgentForThisMobileNode (6), --(Code 133)
duplicateAddressDetectionFailed (7), --(Code 134)
sequenceNumberOutOfWindow (8), --(Code 135)
expiredHomeNonceIndex (9), --(Code 136)
expiredCareofNonceIndex (10), --(Code 137)
expiredNonces (11), --(Code 138)
registrationTypeChangeDisallowed(12) --(Code 139)
}
Keeni, et al. Standards Track [Page 8]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6Capabilities OBJECT-TYPE
SYNTAX BITS {
mobileNode (0),
homeAgent (1),
correspondentNode (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 3.2, 4.1"
::= { mip6System 1 }
mip6Status OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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.
"
::= { mip6System 2 }
-- mip6BindingCache
Keeni, et al. Standards Track [Page 9]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6BindingCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6BindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 4.5, 9.1, 10.1"
::= { mip6Bindings 1 }
mip6BindingCacheEntry OBJECT-TYPE
SYNTAX Mip6BindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
INDEX { mip6BindingHomeAddressType, mip6BindingHomeAddress }
::= { mip6BindingCacheTable 1 }
Keeni, et al. Standards Track [Page 10]
RFC 4295 MOBILEIPV6-MIB April 2006
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
}
mip6BindingHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mip6BindingHomeAddress
that follows.
"
::= { mip6BindingCacheEntry 1 }
mip6BindingHomeAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 2 }
Keeni, et al. Standards Track [Page 11]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6BindingCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the mip6BindingCOA that
follows.
"
::= { mip6BindingCacheEntry 3 }
mip6BindingCOA OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 4 }
mip6BindingTimeRegistered OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry was
created.
"
::= { mip6BindingCacheEntry 5 }
mip6BindingTimeGranted OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime in seconds granted to the mobile node
for this registration.
"
::= { mip6BindingCacheEntry 6 }
Keeni, et al. Standards Track [Page 12]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6BindingTimeRemaining OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime in seconds remaining for this
registration.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 7 }
mip6BindingHomeRegn OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether or not this Binding
Cache entry is a home registration entry (applicable
only on nodes that support home agent
functionality).
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 8 }
mip6BindingMaxSeq OBJECT-TYPE
SYNTAX Unsigned32 (0..65536)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of the Sequence Number field
received in previous Binding Updates for this home
address (mip6BindingHomeAddress).
"
REFERENCE
"RFC 3775 : Section 9.1, 9.5.1"
::= { mip6BindingCacheEntry 9 }
Keeni, et al. Standards Track [Page 13]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6BindingUsageTS OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this entry was last looked up.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 10 }
mip6BindingUsageCount OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this entry was looked up.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 11 }
mip6BindingAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
active (1),
inactive (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 12 }
Keeni, et al. Standards Track [Page 14]
RFC 4295 MOBILEIPV6-MIB April 2006
-- mip6BindingHistory
-- Once the lifetime expires an entry will be removed from the
-- Binding Cache.
-- For monitoring purposes it will be useful to have access to
-- the history of the Binding Cache. BindingHistoryTable serves
-- this purpose. It records the history of the Bindings.
-- The size of the table will be left to implementors.
mip6BindingHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6BindingHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing a record of the bindings.
"
::= { mip6Bindings 2 }
mip6BindingHistoryEntry OBJECT-TYPE
SYNTAX Mip6BindingHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
INDEX { mip6BindingHstHomeAddressType,
mip6BindingHstHomeAddress ,
mip6BindingHstIndex}
::= { mip6BindingHistoryTable 1 }
Keeni, et al. Standards Track [Page 15]
RFC 4295 MOBILEIPV6-MIB April 2006
Mip6BindingHistoryEntry ::=
SEQUENCE {
mip6BindingHstHomeAddressType InetAddressType,
mip6BindingHstHomeAddress InetAddress,
mip6BindingHstIndex Unsigned32,
mip6BindingHstCOAType InetAddressType,
mip6BindingHstCOA InetAddress,
mip6BindingHstTimeRegistered DateAndTime,
mip6BindingHstTimeExpired DateAndTime,
mip6BindingHstHomeRegn TruthValue,
mip6BindingHstUsageTS DateAndTime,
mip6BindingHstUsageCount Gauge32
}
mip6BindingHstHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the
mip6BindingHstHomeAddress that follows.
"
::= { mip6BindingHistoryEntry 1 }
mip6BindingHstHomeAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Mobile node's home address.
The type of the address represented by this object
is specified by the corresponding
mip6BindingHstHomeAddressType object.
"
::= { mip6BindingHistoryEntry 2 }
mip6BindingHstIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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."
::= { mip6BindingHistoryEntry 3 }
Keeni, et al. Standards Track [Page 16]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6BindingHstCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the mip6BindingHstCOA that
follows.
"
::= { mip6BindingHistoryEntry 4 }
mip6BindingHstCOA OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
::= { mip6BindingHistoryEntry 5 }
mip6BindingHstTimeRegistered OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry was
created.
"
::= { mip6BindingHistoryEntry 6 }
mip6BindingHstTimeExpired OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry expired.
"
::= { mip6BindingHistoryEntry 7 }
Keeni, et al. Standards Track [Page 17]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6BindingHstHomeRegn OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether or not this Binding
Cache entry is a home registration entry (applicable
only on nodes that support home agent
functionality).
"
::= { mip6BindingHistoryEntry 8 }
mip6BindingHstUsageTS OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this entry was last looked up.
"
::= { mip6BindingHistoryEntry 9 }
mip6BindingHstUsageCount OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this entry was looked up.
"
::= { mip6BindingHistoryEntry 10 }
-- mip6TrafficCounters
-- MIPv6 Traffic will be characterized by
-- IPv6 datagrams which satisfy at least one of the following
-- conditions
-- - the datagrams are tunneled to the mobile node by the HA
-- - the datagrams are reverse tunneled by the MN to the HA
-- - the datagrams have the Routing header type 2 set.
-- - the datagrams have the Home Address option set in the
-- Destination Option extension header
-- - the datagrams have the mobility header
mip6TotalTraffic OBJECT IDENTIFIER ::= { mip6Stats 1 }
-- REFERENCE
-- "RFC 3775 : Section 4.1, 6.3, 6.4"
Keeni, et al. Standards Track [Page 18]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6InOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 1 }
mip6HCInOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 2 }
Keeni, et al. Standards Track [Page 19]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6InPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 3 }
mip6HCInPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 4 }
Keeni, et al. Standards Track [Page 20]
RFC 4295 MOBILEIPV6-MIB April 2006
mip6OutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 5 }
mip6HCOutOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS