Network Working Group Glenn M. Keeni
INTERNET-DRAFT Cyber Solutions Inc.
Expires: November 15, 2004 Kazuhide Koide
Network Working Group Tohoku University
Kenichi Nagami
INTEC NetCore Inc.
Sri Gundavelli
Cisco Systems Inc.
May 16, 2004
A Management Information Base for Mobile IPv6
<draft-ietf-mip6-mipv6-mib-02.txt>
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 15, 2004.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
This memo defines a portion of the Management Information Base (MIB),
the Mobile-IPv6 MIB , for use with network management protocols
Expires: November 15, 2004 [Page 1]
Internet Draft February 16, 2004
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 .................... 3
2. Overview ...................................................... 3
3. Mobile IPv6 Monitoring and Control Requirements ............... 4
4. MIB Design .................................................... 5
5. The Mobile-IPv6 MIB ........................................... 7
6. Intellectual Property .........................................39
7. Acknowledgments ...............................................39
References ........................................................40
Security Considerations ...........................................42
Authors' Addresses ................................................44
Full Copyright Statement ..........................................45
Expires: November 15, 2004 [Page 2]
Internet Draft February 16, 2004
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) [MIPv6] specifies a protocol which allows nodes
to remain reachable while moving around in the IPv6 Internet. An
entity which implements the MIPv6 protocol is an 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 corespondent 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 the managed objects that will be required to
monitor and control MIPv6 entities.
Expires: November 15, 2004 [Page 3]
Internet Draft February 16, 2004
2.2 Terminology.
The terminolgy used in this document is consistent with the
definitions used in Mobile IPv6 protocol specification[MIPv6].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD 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 HA, CN, MN )
o binding details (at HA, CN)
o history of Binding Updates (at HA, CN, MN)
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 e.g.
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.
Expires: November 15, 2004 [Page 4]
Internet Draft February 16, 2004
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,
Neighbour Discovery MIB, Tunnel MIB.) for monitor and control of
MIPv6 entities.
The Mobile-IPv6 MIB comprises of following sets of groups
- mipv6IP: a generic group containing objects that are common
to all the Mobile IPv6 entities.
- mipv6Ha: this group models the home agent service. It
comprises of objects specific to the services and associated
advertisement parameters offerred 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.
- mipv6Mn: this group models the mobile node service. It
comprises 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.
- mipv6Cn: 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.
- mipv6Notifications: 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-
mipv6BindingCacheTable : 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.
mipv6BindingHistoryTable : tracks the history of the binding cache.
mipv6NodeTrafficTable : the mobile node-wise traffic counters.
mipv6MnHomeAddressTable : contains all the home addresses
pertaining to the mobile node and
the corresponding registration status.
mipv6MnBLTable : 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.
mipv6CnCounterTable : contains the mobile node-wise
registration statistics.
mipv6HaConfTable : contains the configurable
Expires: November 15, 2004 [Page 5]
Internet Draft February 16, 2004
advertisement parameters for all
the interfaces on which the which
the home agent service is
advertised.
mipv6HaCounterTable : contains registration statistics
for all mobile nodes registered
with the home agent.
mipv6HaListTable : 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.
mipv6HaGlobalAddrTable : contains the global addresses of
the jome agents.
Expires: November 15, 2004 [Page 6]
Internet Draft February 16, 2004
5. The Mobile-IPv6 MIB.
MOBILEIPV6-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, experimental, Unsigned32, Integer32,
Gauge32, Counter64,
OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
TruthValue, DateAndTime, TimeStamp
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
-- SnmpAdminString
-- FROM SNMP-FRAMEWORK-MIB
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB
ipv6IfIndex
FROM IPV6-MIB
;
mipv6MIB MODULE-IDENTITY
LAST-UPDATED "200310210000Z" -- 21th October, 2003
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
Postal: Kazuhide Koide
Tohoku University
Katahira Campus
Sendai
Japan
Expires: November 15, 2004 [Page 7]
Internet Draft February 16, 2004
Tel: +81-22-217-5454
E-mail: koide@shiratori.riec.tohoku.ac.jp
Sri Gundavelli
Postal: Cisco Systems
170 W.Tasman Drive,
San Jose, CA 95134
USA
Tel: +1-408-527-6109
Email: sgundave@cisco.com
Support Group E-mail: mip6@ietf.org"
DESCRIPTION
" The MIB for monitoring Mobile-IPv6 entities.
Copyright (C) The Internet Society (2003).
This version of this MIB module is part of
RFC xxxx; see the RFC itself for full legal
notices.
"
-- RFC Ed.: replace xxxx with actual RFC number & remove this note
REVISION "200310210000Z" -- 21th October, 2003
DESCRIPTION "Initial version, published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { experimental 999 } -- will be assigned by IANA
-- The major groups
mipv6Notifications OBJECT IDENTIFIER ::= { mipv6MIB 0 }
mipv6Objects OBJECT IDENTIFIER ::= { mipv6MIB 1 }
mipv6Conformance OBJECT IDENTIFIER ::= { mipv6MIB 2 }
mipv6Core OBJECT IDENTIFIER ::= { mipv6Objects 1 }
mipv6Mn OBJECT IDENTIFIER ::= { mipv6Objects 2 }
mipv6Cn OBJECT IDENTIFIER ::= { mipv6Objects 3 }
mipv6Ha OBJECT IDENTIFIER ::= { mipv6Objects 4 }
-- The sub groups
mipv6System OBJECT IDENTIFIER ::= { mipv6Core 1 }
mipv6Bindings OBJECT IDENTIFIER ::= { mipv6Core 2 }
mipv6Stats OBJECT IDENTIFIER ::= { mipv6Core 3 }
Expires: November 15, 2004 [Page 8]
Internet Draft February 16, 2004
mipv6MnSystem OBJECT IDENTIFIER ::= { mipv6Mn 1 }
mipv6MnConf OBJECT IDENTIFIER ::= { mipv6Mn 2 }
mipv6MnRegistration OBJECT IDENTIFIER ::= { mipv6Mn 3 }
mipv6CnSystem OBJECT IDENTIFIER ::= { mipv6Cn 1 }
mipv6CnStats OBJECT IDENTIFIER ::= { mipv6Cn 2 }
mipv6HaAdvertisement OBJECT IDENTIFIER ::= { mipv6Ha 1 }
mipv6HaStats OBJECT IDENTIFIER ::= { mipv6Ha 2 }
-- Textual Conventions
Mipv6BURequestRejectionCode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of the status field in the Binding
Acknowledgement message when the Binding Update
was rejected.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8"
SYNTAX BITS {
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)
}
mipv6Capabilities 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
Expires: November 15, 2004 [Page 9]
Internet Draft February 16, 2004
functions may be supported by a single entity.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8"
::= { mipv6System 1 }
mipv6Status OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the Mobile IPv6 protocol 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.
"
::= { mipv6System 2 }
-- mipv6BindingCache
mipv6BindingCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mipv6BindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table representing the Binding Cache on the managed
entity. This cache is maintained by home agents and
correspondent nodes. The cache contains both
correspondent registration entries and home registration
entries.
"
REFERENCE
"RFC-MIPV6 : Section 4.5, 9.1 , 10.1"
::= { mipv6Bindings 1 }
mipv6BindingCacheEntry OBJECT-TYPE
SYNTAX Mipv6BindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the binding cache table. It represents a
single Binding Update.
Expires: November 15, 2004 [Page 10]
Internet Draft February 16, 2004
"
INDEX { mipv6BindingHomeAddressType, mipv6BindingHomeAddress }
::= { mipv6BindingCacheTable 1 }
Mipv6BindingCacheEntry ::=
SEQUENCE {
mipv6BindingHomeAddressType InetAddressType,
mipv6BindingHomeAddress InetAddress,
mipv6BindingCOAType InetAddressType,
mipv6BindingCOA InetAddress,
mipv6BindingTimeRegistered DateAndTime,
mipv6BindingTimeGranted Gauge32,
mipv6BindingTimeRemaining Gauge32,
mipv6BindingHomeRegn TruthValue,
mipv6BindingMaxSeq Unsigned32,
mipv6BindingUsageTS DateAndTime,
mipv6BindingUsageCount Counter32,
mipv6BindingAdminStatus INTEGER
}
mipv6BindingHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mipv6BindingHomeAddress
that follows.
"
::= { mipv6BindingCacheEntry 1 }
mipv6BindingHomeAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (16|20))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The home address of the mobile node for which this is
the Binding Cache entry. This field is used as the key
for searching the Binding Cache for the destination
address of a packet being sent.
"
REFERENCE
"RFC-MIPV6 : Section 9.1"
::= { mipv6BindingCacheEntry 2 }
mipv6BindingCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
Expires: November 15, 2004 [Page 11]
Internet Draft February 16, 2004
DESCRIPTION
"The InetAddressType of the mipv6BindingCOA that follows.
"
::= { mipv6BindingCacheEntry 3 }
mipv6BindingCOA OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The care-of address for the mobile node indicated by
the home address field (mipv6BindingHomeAddress) in this
Binding Cache entry. A mobile node can have multiple
care-of-addresses.
"
REFERENCE
"RFC-MIPV6 : Section 9.1"
::= { mipv6BindingCacheEntry 4 }
mipv6BindingTimeRegistered OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry was created.
"
::= { mipv6BindingCacheEntry 5 }
mipv6BindingTimeGranted 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.
"
::= { mipv6BindingCacheEntry 6 }
mipv6BindingTimeRemaining OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime in seconds remaining for this registration.
"
REFERENCE
Expires: November 15, 2004 [Page 12]
Internet Draft February 16, 2004
"RFC-MIPV6 : Section 9.1"
::= { mipv6BindingCacheEntry 7 }
mipv6BindingHomeRegn 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 which support home agent functionality).
"
REFERENCE
"RFC-MIPV6 : Section 9.1"
::= { mipv6BindingCacheEntry 8 }
mipv6BindingMaxSeq OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of the Sequence Number field received
in previous Binding Updates for this home address
(mipv6BindingHomeAddress).
"
::= { mipv6BindingCacheEntry 9 }
mipv6BindingUsageTS OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this entry was last looked up.
"
REFERENCE
"RFC-MIPV6 : Section 9.1"
::= { mipv6BindingCacheEntry 10 }
mipv6BindingUsageCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this entry was looked up.
"
REFERENCE
"RFC-MIPV6 : Section 9.1"
::= { mipv6BindingCacheEntry 11 }
Expires: November 15, 2004 [Page 13]
Internet Draft February 16, 2004
mipv6BindingAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
active (1),
inactive (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This is an administrative 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(1) to
inactive(2) by operator intervention.
Causing the state to change to active results
in the entry being deleted from the cache.
Attempts to change the status from 'inactive'
to 'active' will be rejected.
"
REFERENCE
"RFC-MIPV6 : Section 9.1"
::= { mipv6BindingCacheEntry 12 }
-- mipv6BindingHistory
-- 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.
mipv6BindingHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mipv6BindingHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing a record of the bindings.
"
::= { mipv6Bindings 2 }
mipv6BindingHistoryEntry OBJECT-TYPE
SYNTAX Mipv6BindingHistoryEntry
Expires: November 15, 2004 [Page 14]
Internet Draft February 16, 2004
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The record of a binding ."
INDEX { mipv6BindingHstHomeAddressType,
mipv6BindingHstHomeAddress ,
mipv6BindingHstIndex}
::= { mipv6BindingHistoryTable 1 }
Mipv6BindingHistoryEntry ::=
SEQUENCE {
mipv6BindingHstHomeAddressType InetAddressType,
mipv6BindingHstHomeAddress InetAddress,
mipv6BindingHstCOAType InetAddressType,
mipv6BindingHstCOA InetAddress,
mipv6BindingHstIndex Unsigned32,
mipv6BindingHstTimeRegistered DateAndTime,
mipv6BindingHstTimeExpired DateAndTime,
mipv6BindingHstHomeRegn TruthValue,
mipv6BindingHstUsageTS DateAndTime,
mipv6BindingHstUsageCount Unsigned32
}
mipv6BindingHstHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mipv6BindingHomeAddress
that follows.
"
::= { mipv6BindingHistoryEntry 1 }
mipv6BindingHstHomeAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (16|20))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Mobile node's home (IP) address.
"
::= { mipv6BindingHistoryEntry 2 }
mipv6BindingHstCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the mipv6BindingCOA that follows.
Expires: November 15, 2004 [Page 15]
Internet Draft February 16, 2004
"
::= { mipv6BindingHistoryEntry 3 }
mipv6BindingHstCOA 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."
::= { mipv6BindingHistoryEntry 4 }
mipv6BindingHstIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index to uniquely identify this record along with
the Mobile nodes HomeAddress type and HomeAddress. It
should be monotonically increasing. It may wrap after
reaching its max value."
::= { mipv6BindingHistoryEntry 5 }
mipv6BindingHstTimeRegistered OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry was created.
"
::= { mipv6BindingHistoryEntry 6 }
mipv6BindingHstTimeExpired OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry expired.
"
::= { mipv6BindingHistoryEntry 7 }
mipv6BindingHstHomeRegn OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether or not this Binding Cache
Expires: November 15, 2004 [Page 16]
Internet Draft February 16, 2004
entry is a home registration entry (applicable only on
nodes which support home agent functionality).
"
::= { mipv6BindingHistoryEntry 8 }
mipv6BindingHstUsageTS OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this entry was last looked up.
"
::= { mipv6BindingHistoryEntry 9 }
mipv6BindingHstUsageCount OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this entry was looked up.
"
::= { mipv6BindingHistoryEntry 10 }
-- mipv6TrafficCounters
-- MIPv6 Traffic will be characterized by
-- IPv6 datagrams which satisfy atleast 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 which have the Routing header type 2
-- set.
-- - the datagrams have the Home Address option set in the
-- Destination Option extension header
-- - IPv6 datagrams with the mobility header
mipv6TotalTraffic OBJECT IDENTIFIER ::= { mipv6Stats 1 }
-- REFERENCE
-- "RFC-MIPV6 : Section 4.1, 6.3"
mipv6InOctets 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 the datagrams with
the Mobility Header, the Home Address option in the
Expires: November 15, 2004 [Page 17]
Internet Draft February 16, 2004
Destination Option extension header (Next Header value = 60),
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6TotalTraffic 1 }
mipv6HCInOctets 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 the datagrams with
the Mobility Header, the Home Address option in the
Destination Option extension header (Next Header value = 60),
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 mipv6InOctets.
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6TotalTraffic 2 }
mipv6InPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams received by the MIPv6 entity.
This will include the datagrams with the Mobility Header,
the Home Address option in the Destination Option extension
header (Next Header value = 60), 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 mipv6CounterDiscontinuityTime.
Expires: November 15, 2004 [Page 18]
Internet Draft February 16, 2004
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6TotalTraffic 3 }
mipv6HCInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams received by the MIPv6 entity.
This will include the datagrams with the Mobility Header,
the Home Address option in the Destination Option extension
header (Next Header value = 60), 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 mipv6InPkts.
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6TotalTraffic 4 }
mipv6OutOctets 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 the datagrams with
the Mobility Header, the Home Address option in the
Destination Option extension header (Next Header value = 60),
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6TotalTraffic 5 }
mipv6HCOutOctets OBJECT-TYPE
Expires: November 15, 2004 [Page 19]
Internet Draft February 16, 2004
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 the datagrams with
the Mobility Header, the Home Address option in the
Destination Option extension header (Next Header value = 60),
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 mipv6OutOctets.
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6TotalTraffic 6 }
mipv6OutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams sent by the MIPv6 entity.
This will include the datagrams with the Mobility Header,
the Home Address option in the Destination Option extension
header (Next Header value = 60), 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6TotalTraffic 7 }
mipv6HCOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams sent by the MIPv6 entity.
This will include the datagrams with the Mobility Header,
the Home Address option in the Destination Option extension
header (Next Header value = 60), the type 2 Routing Header.
Expires: November 15, 2004 [Page 20]
Internet Draft February 16, 2004
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 mipv6OutPkts.
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6TotalTraffic 8 }
mipv6CounterDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 'mipv6TotalTraffic' or
'mipv6CnGlobalStats' or 'mipv6HaGlobalStats' 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.
"
::= { mipv6TotalTraffic 9 }
-- mipv6NodeTrafficCounters
mipv6NodeTrafficTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mipv6NodeTrafficEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing MIPv6 traffic counters per mobile
node.
"
::= { mipv6Stats 2 }
mipv6NodeTrafficEntry OBJECT-TYPE
SYNTAX Mipv6NodeTrafficEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The MIPv6 traffic counters for a mobile node."
INDEX { mipv6BindingHomeAddressType, mipv6BindingHomeAddress }
::= { mipv6NodeTrafficTable 1 }
Expires: November 15, 2004 [Page 21]
Internet Draft February 16, 2004
Mipv6NodeTrafficEntry ::=
SEQUENCE {
mipv6NodeInOctets Counter32,
mipv6HCNodeInOctets Counter64,
mipv6NodeInPkts Counter32,
mipv6HCNodeInPkts Counter64,
mipv6NodeOutOctets Counter32,
mipv6HCNodeOutOctets Counter64,
mipv6NodeOutPkts Counter32,
mipv6HCNodeOutPkts Counter64,
mipv6NodeCtrDiscontinuityTime TimeStamp
}
mipv6NodeInOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams received
from the mobile node by the MIPv6 entity. This will include
the datagrams with the Mobility Header and, 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 mipv6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6NodeTrafficEntry 1 }
mipv6HCNodeInOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams received
from the mobile node by the MIPv6 entity. This will include
the datagrams with the Mobility Header and, 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 mipv6NodeInOctets.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
Expires: November 15, 2004 [Page 22]
Internet Draft February 16, 2004
as indicated by the value of mipv6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6NodeTrafficEntry 2 }
mipv6NodeInPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams received from the mobile node
by the MIPv6 entity. This will include the datagrams with the
Mobility Header and, 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 mipv6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6NodeTrafficEntry 3 }
mipv6HCNodeInPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams received from the mobile node
by the MIPv6 entity. This will include the datagrams with the
Mobility Header and, 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 mipv6NodeInPkts.
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 mipv6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6NodeTrafficEntry 4 }
mipv6NodeOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
Expires: November 15, 2004 [Page 23]
Internet Draft February 16, 2004
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams sent to
the mobile node by the MIPv6 entity. This will include the
datagrams with the Mobility Header and 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 mipv6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6NodeTrafficEntry 5 }
mipv6HCNodeOutOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams sent to
the mobile node by the MIPv6 entity. This will include the
datagrams with the Mobility Header and 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 mipv6NodeOutOctets.
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 mipv6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6NodeTrafficEntry 6 }
mipv6NodeOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams sent to the mobile node by the
MIPv6 entity. This will include the datagrams with the
Mobility Header, 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 mipv6NodeCtrDiscontinuityTime.
"
Expires: November 15, 2004 [Page 24]
Internet Draft February 16, 2004
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6NodeTrafficEntry 7 }
mipv6HCNodeOutPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams sent to the mobile node by the
MIPv6 entity. This will include the datagrams with the
Mobility Header, 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 mipv6NodeOutOctets.
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 mipv6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mipv6NodeTrafficEntry 8 }
mipv6NodeCtrDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
::= { mipv6NodeTrafficEntry 9 }
-- mipv6MnSystem Group
mipv6MnHomeAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mipv6MnHomeAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing registration status for all the home
addresses pertaining to the mobile node.
Expires: November 15, 2004 [Page 25]
Internet Draft February 16, 2004
"
::= { mipv6MnSystem 1 }
mipv6MnHomeAddressEntry OBJECT-TYPE
SYNTAX Mipv6MnHomeAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The registration status for a homeaddress."
INDEX { mipv6MnHomeAddressType, mipv6MnHomeAddress }
::= { mipv6MnHomeAddressTable 1 }
Mipv6MnHomeAddressEntry ::=
SEQUENCE {
mipv6MnHomeAddressType InetAddressType,
mipv6MnHomeAddress InetAddress,
mipv6MnHomeAddressState INTEGER
}
mipv6MnHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mipv6MnHomeAddress that
follows.
"
::= { mipv6MnHomeAddressEntry 1 }
mipv6MnHomeAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (16|20))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC-MIPV6 : Section 3.2"
::= { mipv6MnHomeAddressEntry 2 }
mipv6MnHomeAddressState OBJECT-TYPE
SYNTAX INTEGER {
Expires: November 15, 2004 [Page 26]
Internet Draft February 16, 2004
unknown(1),
home(2),
registered(3),
pending(4),
isolated(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates mobile node's state of Mobile IP:
unknown -- The state of the MN cannot be determined
home, -- MN is connected to home network.
registered, -- MN is on a foreign network and is
registered with the home agent
pending, -- MN has sent registration request
to the home agent and is waiting for the reply
isolated, -- MN is isolated from network i.e. it is not
in its home network, it is not registered and
no registration ack is pending
"
::= { mipv6MnHomeAddressEntry 3 }
-- Mobile Node Discovery and Advertisement Group Counters
mipv6MnDiscoveryRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.5, 11.4.1"
::= { mipv6MnConf 1 }
mipv6MnDiscoveryReplies OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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
Expires: November 15, 2004 [Page 27]
Internet Draft February 16, 2004
re-initialization of the management system, and at other times
as indicated by the value of mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.5, 11.4.1"
::= { mipv6MnConf 2 }
mipv6MnDiscoveryTimeouts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.5, 11.4.1, 12"
::= { mipv6MnConf 3 }
mipv6MnPrefixSolicitationsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.5, 11.4.2"
::= { mipv6MnConf 4 }
mipv6MnPrefixAdvsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of ICMP Mobile Prefix Advertisements received by
the mobile node. This will include the ICMP Mobile Prefix
Advertisements that are 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
Expires: November 15, 2004 [Page 28]
Internet Draft February 16, 2004
as indicated by the value of mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.6, 11.4.3"
::= { mipv6MnConf 5 }
mipv6MnPrefixAdvsIgnored OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.6, 11.4.3"
::= { mipv6MnConf 6 }
mipv6MnMovedToFN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of times the mobile node has detected movement
from 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 11.5.1"
::= { mipv6MnConf 7 }
mipv6MnMovedToHN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
Expires: November 15, 2004 [Page 29]
Internet Draft February 16, 2004
"
REFERENCE
"RFC-MIPV6 : Section 11.5.4"
::= { mipv6MnConf 8 }
-- Mobile Node Registration Group
-- Registration table of mobile node
mipv6MnBLTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mipv6MnBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC-MIPV6 : Section 4.5, 11.1"
::= { mipv6MnRegistration 1 }
mipv6MnBLEntry OBJECT-TYPE
SYNTAX Mipv6MnBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a Binding Update send by the mobile node
to a either to its home agent or one of its correspondent
nodes.
"
INDEX { mipv6MnBLNodeAddressType,
mipv6MnBLNodeAddress,
mipv6MnHomeAddressType,
mipv6MnHomeAddress
}
::= { mipv6MnBLTable 1 }
Mipv6MnBLEntry ::= SEQUENCE {
mipv6MnBLNodeAddressType InetAddressType,
mipv6MnBLNodeAddress InetAddress,
mipv6MnBLCOAType InetAddressType,
mipv6MnBLCOA InetAddress,
mipv6MnBLLifeTimeRequested Unsigned32,
mipv6MnBLLifeTimeGranted Unsigned32,
Expires: November 15, 2004 [Page 30]
Internet Draft February 16, 2004
mipv6MnBLMaxSeq Unsigned32,
mipv6MnBLTimeSent DateAndTime,
mipv6MnBLAccepted TruthValue,
mipv6MnBLAcceptedTime DateAndTime,
mipv6MnBLRetransmissions Integer32
}
mipv6MnBLNodeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mipv6MnBLNodeAddress
that follows.
"
::= { mipv6MnBLEntry 1 }
mipv6MnBLNodeAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (16|20))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"IP address of the agent as used in the destination
IP address of the Binding Update. The agent
may be a home agent or a correspondent node."
REFERENCE
"RFC-MIPV6 : Section 11.1"
::= { mipv6MnBLEntry 2 }
mipv6MnBLCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mipv6MnBLCOA that follows.
"
::= { mipv6MnBLEntry 3 }
mipv6MnBLCOA OBJECT-TYPE
SYNTAX InetAddress (SIZE (16|20))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Care-of address that the mobile node intends to register
in the Binding Update request."
REFERENCE
"RFC-MIPV6 : Section 11.1"
::= { mipv6MnBLEntry 4 }
Expires: November 15, 2004 [Page 31]
Internet Draft February 16, 2004
mipv6MnBLLifeTimeRequested OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime requested by the mobile node (in seconds)
in the Binding Update.
"
REFERENCE
"RFC-MIPV6 : Section 11.1"
::= { mipv6MnBLEntry 5 }
mipv6MnBLLifeTimeGranted OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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), mipv6MnBLAcceptedTime (aT) and mipv6MnBLLifeTimeGranted
(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."
::= { mipv6MnBLEntry 6 }
mipv6MnBLMaxSeq OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of the Sequence Number field sent in
previous Binding Updates to this destination.
"
REFERENCE
"RFC-MIPV6 : Section 11.1"
::= { mipv6MnBLEntry 7 }
mipv6MnBLTimeSent OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the last (re-)transmission occurred."
Expires: November 15, 2004 [Page 32]
Internet Draft February 16, 2004
REFERENCE
"RFC-MIPV6 : Section 11.1"
::= { mipv6MnBLEntry 8 }
mipv6MnBLAccepted OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
::= { mipv6MnBLEntry 9 }
mipv6MnBLAcceptedTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
::= { mipv6MnBLEntry 10 }
mipv6MnBLRetransmissions OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Binding Update retransmissions.
"
REFERENCE
"RFC-MIPV6 : Section 11.1"
::= { mipv6MnBLEntry 11 }
-- Mobile Node Registration Group Counters
mipv6MnRegnCounters OBJECT IDENTIFIER ::= { mipv6MnRegistration 2 }
mipv6MnMobilityMessagesSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
Expires: November 15, 2004 [Page 33]
Internet Draft February 16, 2004
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 4.2, 6.1"
::= { mipv6MnRegnCounters 1 }
mipv6MnMobilityMessagesRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 Acknowledgement, 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 4.2, 6.1"
::= { mipv6MnRegnCounters 2 }
mipv6MnBUsToHA OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 11.7.1"
::= { mipv6MnRegnCounters 3 }
mipv6MnBUAcksFromHA OBJECT-TYPE
Expires: November 15, 2004 [Page 34]
Internet Draft February 16, 2004
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of valid binding acknowledgements received
from the the mobile nodes 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 11.7.3"
::= { mipv6MnRegnCounters 4 }
mipv6MnBUsToCN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 11.7.2"
::= { mipv6MnRegnCounters 5 }
mipv6MnBUAcksFromCN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 11.7.3"
::= { mipv6MnRegnCounters 6 }
mipv6MnBindingErrorsFromCN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
Expires: November 15, 2004 [Page 35]
Internet Draft February 16, 2004
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
::= { mipv6MnRegnCounters 7 }
mipv6MnICMPErrorsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of ICMP Error messages of type ICMP
Parameter Problem, Code 1 or Code 2 received by
the mobile node from a CN 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 11.3.5"
::= { mipv6MnRegnCounters 8 }
mipv6MnBRRequestsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Refresh requests
received by the mobile node from Corresponding 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 11.7.4"
::= { mipv6MnRegnCounters 9 }
-- Registration Group counters used for CN
mipv6CnGlobalStats OBJECT IDENTIFIER ::= { mipv6CnStats 1 }
mipv6CnHomeTestInitsRecd OBJECT-TYPE
SYNTAX Counter32
Expires: November 15, 2004 [Page 36]
Internet Draft February 16, 2004
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.4.1"
::= { mipv6CnGlobalStats 1 }
mipv6CnHomeTestsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.4.3"
::= { mipv6CnGlobalStats 2 }
mipv6CnCareOfTestInitsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Care-of Test Init messages received."
REFERENCE
"RFC-MIPV6 : Section 9.4.2"
::= { mipv6CnGlobalStats 3 }
mipv6CnCareOfTestsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
Expires: November 15, 2004 [Page 37]
Internet Draft February 16, 2004
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.4.4"
::= { mipv6CnGlobalStats 4 }
mipv6CnBUsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.5.1"
::= { mipv6CnGlobalStats 5 }
mipv6CnBUAcksSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.5.4"
::= { mipv6CnGlobalStats 6 }
mipv6CnBRsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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
Expires: November 15, 2004 [Page 38]
Internet Draft February 16, 2004
as indicated by the value of mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.5.5"
::= { mipv6CnGlobalStats 7 }
mipv6CnBindingErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.3.3"
::= { mipv6CnGlobalStats 8 }
mipv6CnBUsAccepted OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
::= { mipv6CnGlobalStats 9 }
mipv6CnBUsRejected OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 grather than or equal to
128. Otherwise the Binding Update request has been
Expires: November 15, 2004 [Page 39]
Internet Draft February 16, 2004
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.5.1"
::= { mipv6CnGlobalStats 10 }
mipv6CnReasonUnspecified OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the correspondent node with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8"
::= { mipv6CnGlobalStats 11 }
mipv6CnInsufficientResource OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the correspondent node with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8"
::= { mipv6CnGlobalStats 12 }
mipv6CnHomeRegnNotSupported OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Expires: November 15, 2004 [Page 40]
Internet Draft February 16, 2004
"Total number of Binding Update requests rejected by
correspondent node with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6CnGlobalStats 13 }
mipv6CnSeqNumberOutOfWindow OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Updates rejected by
correspondent node with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8 9.5.1"
::= { mipv6CnGlobalStats 14 }
mipv6CnExpiredHomeNonceIndex OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Updates rejected by
correspondent node with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8 9.5.1"
::= { mipv6CnGlobalStats 15 }
mipv6CnExpiredCareOfNonceIndex OBJECT-TYPE
SYNTAX Counter32
Expires: November 15, 2004 [Page 41]
Internet Draft February 16, 2004
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Updates rejected by
correspondent node with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8 9.5.1"
::= { mipv6CnGlobalStats 16 }
mipv6CnExpiredNonce OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Updates rejected by
correspondent node with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8 9.5.1"
::= { mipv6CnGlobalStats 17 }
mipv6CnRegTypeChangeDisallowed OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Updates rejected by
correspondent node with status code in the Binding
Acknowledgement 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
Expires: November 15, 2004 [Page 42]
Internet Draft February 16, 2004
as indicated by the value of mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8 9.5.1"
::= { mipv6CnGlobalStats 18 }
-- The Correspondent Node statistics by mobile node
mipv6CnCounterTable OBJECT-TYPE
SYNTAX SEQUENCE OF CnCounterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing each mobile ."
::= { mipv6CnStats 2 }
mipv6CnCounterEntry OBJECT-TYPE
SYNTAX CnCounterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The set of CN counters for a mobile node."
INDEX { mipv6BindingHomeAddressType,
mipv6BindingHomeAddress
}
::= { mipv6CnCounterTable 1 }
CnCounterEntry ::=
SEQUENCE {
mipv6CnBURequestsAccepted Counter32,
mipv6CnBURequestsRejected Counter32,
mipv6CnBCEntryCreationTime DateAndTime,
mipv6CnBUAcceptedTime DateAndTime,
mipv6CnBURejectionTime DateAndTime,
mipv6CnBURejectionCode Mipv6BURequestRejectionCode,
mipv6CnCtrDiscontinuityTime TimeStamp
}
mipv6CnBURequestsAccepted OBJECT-TYPE --(Code 0,1)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests from the mobile
node accepted by the correspondent node.
If Binding Acknowledgement messages are sent then the
Expires: November 15, 2004 [Page 43]
Internet Draft February 16, 2004
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 mipv6CnCtrDiscontinuityTime.
"
::= { mipv6CnCounterEntry 1 }
mipv6CnBURequestsRejected OBJECT-TYPE
-- (Code 128 through Code 159)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests from the mobile
node which have been rejected by the corespondent 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 which 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 mipv6CnCtrDiscontinuityTime.
"
::= { mipv6CnCounterEntry 2 }
mipv6CnBCEntryCreationTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the current Binding Cache entry was created
for the mobile node.
"
::= { mipv6CnCounterEntry 3 }
mipv6CnBUAcceptedTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the last Binding Update was accepted by
the corespondent node and the corresponding Binding Cache
entry was updated.
"
::= { mipv6CnCounterEntry 4 }
Expires: November 15, 2004 [Page 44]
Internet Draft February 16, 2004
mipv6CnBURejectionTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the last Binding Update message was
rejected by the corespondent node.
If there have been no rejections then this object will
be inaccessible.
"
::= { mipv6CnCounterEntry 5 }
mipv6CnBURejectionCode OBJECT-TYPE
SYNTAX Mipv6BURequestRejectionCode
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 that of the Status code
that corresponds to the reason of the rejection.
If there have been no rejections then this object will
be inaccessible.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8"
::= { mipv6CnCounterEntry 6 }
mipv6CnCtrDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion at which
any one or more of counters in this row viz, instances of
'mipv6CnBURequestsAccepted' and 'mipv6CnBURequestsRejected'
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.
"
::= { mipv6CnCounterEntry 7 }
-- Home agent group
Expires: November 15, 2004 [Page 45]
Internet Draft February 16, 2004
mipv6HaAdvsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8 9.5.1"
::= { mipv6HaAdvertisement 1 }
mipv6HaAdvsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC-MIPV6 : Section 6.1.8 9.5.1"
::= { mipv6HaAdvertisement 2 }
mipv6HaConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mipv6HaConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing configurable advertisement
parameters for all interfaces on which the
which the home agent service is advertised.
"
::= { mipv6HaAdvertisement 3 }
mipv6HaConfEntry OBJECT-TYPE
SYNTAX Mipv6HaConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Advertisement parameters for one advertisement
interface.
"
Expires: November 15, 2004 [Page 46]
Internet Draft February 16, 2004
INDEX { ipv6IfIndex }
::= { mipv6HaConfTable 1 }
Mipv6HaConfEntry ::= SEQUENCE {
mipv6HaAdvPreference Integer32,
mipv6HaAdvLifetime Integer32,
mipv6HaPrefixAdv INTEGER,
mipv6HaPrefixSolicitation INTEGER,
mipv6HaMCastCtlMsgSupport INTEGER
}
mipv6HaAdvPreference OBJECT-TYPE
SYNTAX Integer32 (0..65536)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The preference value for the home agent to
be used in the Router Advertisements. Higher
value denotes greater preference.
"
REFERENCE
"RFC-MIPV6 : Section 7.4, 8.4"
::= { mipv6HaConfEntry 1 }
mipv6HaAdvLifetime OBJECT-TYPE
SYNTAX Integer32 (1..65535)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The lifetime value for the home agent to be
used in the Router Advertisements.
"
REFERENCE
"RFC-MIPV6 : Section 7.4"
::= { mipv6HaConfEntry 2 }
mipv6HaPrefixAdv OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the home agent should support
sending of the ICMP Mobile Prefix Advertisements.
If it is disabled, the home agent will not send
ICMP Mobile Prefix Advertisements to the mobile
nodes."
REFERENCE
Expires: November 15, 2004 [Page 47]
Internet Draft February 16, 2004
"RFC-MIPV6 : Section 8.4"
::= { mipv6HaConfEntry 3}
mipv6HaPrefixSolicitation OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the home agent should respond
to ICMP Mobile Prefix Solicitation messages from
mobile nodes. If it is disabled,
the home agent will not respond to any ICMP
Mobile Prefix Solicitation messages it received
from the mobile node."
REFERENCE
"RFC-MIPV6 : Section 8.4"
::= { mipv6HaConfEntry 4}
mipv6HaMCastCtlMsgSupport OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the home agent should enable
support for the processing of the multicast group
membership control messages it received from the
mobile nodes. If it is disabled, the home agent will
silently ignore the multicast group control messages
it received from the mobile nodes."
REFERENCE
"RFC-MIPV6 : Section 10.4.3"
::= { mipv6HaConfEntry 5}
-- Registration Group counters HA
mipv6HaGlobalStats OBJECT IDENTIFIER ::= { mipv6HaStats 1 }
mipv6HaHomeTestInitsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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
Expires: November 15, 2004 [Page 48]
Internet Draft February 16, 2004
re-initialization of the management system, and at other times
as indicated by the value of mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 5.2.5"
::= { mipv6HaGlobalStats 1 }
mipv6HaHomeTestsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 5.2.5"
::= { mipv6HaGlobalStats 2 }
mipv6HaBUsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total nubmer 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 3 }
mipv6HaBUAcksSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Acknowledgements 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 mipv6CounterDiscontinuityTime.
"
Expires: November 15, 2004 [Page 49]
Internet Draft February 16, 2004
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 4 }
mipv6HaBRAdviceSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Acknowledgements 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 5 }
mipv6HaBUsAccepted OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 6 }
mipv6HaPrefDiscoverReqd OBJECT-TYPE -- (Code 1)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgments sent 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
Expires: November 15, 2004 [Page 50]
Internet Draft February 16, 2004
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 7 }
mipv6HaReasonUnspecified OBJECT-TYPE -- (Code 128)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 8 }
mipv6HaAdmProhibited OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 9 }
mipv6HaInsufficientResource OBJECT-TYPE -- (Code 130)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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
Expires: November 15, 2004 [Page 51]
Internet Draft February 16, 2004
as indicated by the value of mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.5.2"
::= { mipv6HaGlobalStats 10 }
mipv6HaHomeRegnNotSupported OBJECT-TYPE -- (Code 131)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 11 }
mipv6HaNotHomeSubnet OBJECT-TYPE -- (Code 132)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 12 }
mipv6HaNotHomeAgentForThisMN OBJECT-TYPE -- (Code 133)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement message indicating 'not home agent
Expires: November 15, 2004 [Page 52]
Internet Draft February 16, 2004
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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.2"
::= { mipv6HaGlobalStats 13 }
mipv6HaDupAddrDetectionFailed OBJECT-TYPE -- (Code 134)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 10.3.1"
::= { mipv6HaGlobalStats 14 }
mipv6HaSeqNumberOutOfWindow OBJECT-TYPE -- (Code 135)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.5.1"
::= { mipv6HaGlobalStats 15 }
mipv6HaExpiredHomeNonceIndex OBJECT-TYPE -- (Code 136)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Expires: November 15, 2004 [Page 53]
Internet Draft February 16, 2004
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.5.1"
::= { mipv6HaGlobalStats 16 }
mipv6HaRegTypeChangeDisallowed OBJECT-TYPE -- (Code 139)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the home agent with status code in the Binding
Acknowledgement 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 mipv6CounterDiscontinuityTime.
"
REFERENCE
"RFC-MIPV6 : Section 9.5.1"
::= { mipv6HaGlobalStats 17 }
-- Home agent registration Counters per node
mipv6HaCounterTable OBJECT-TYPE
SYNTAX SEQUENCE OF HaCounterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing registration statistics for all
mobile nodes registered with the home agent.
"
::= { mipv6HaStats 2 }
mipv6HaCounterEntry OBJECT-TYPE
SYNTAX HaCounterEntry
MAX-ACCESS not-accessible
STATUS current
Expires: November 15, 2004 [Page 54]
Internet Draft February 16, 2004
DESCRIPTION
"Home agent registration statistics for a mobile node."
INDEX { mipv6BindingHomeAddressType,
mipv6BindingHomeAddress
}
::= { mipv6HaCounterTable 1 }
HaCounterEntry ::= SEQUENCE {
mipv6HaBURequestsAccepted Counter32,
mipv6HaBURequestsDenied Counter32,
mipv6HaBCEntryCreationTime DateAndTime,
mipv6HaBUAcceptedTime DateAndTime,
mipv6HaBURejectionTime DateAndTime,
mipv6HaRecentBURejectionCode Mipv6BURequestRejectionCode,
mipv6HaCtrDiscontinuityTime TimeStamp
}
mipv6HaBURequestsAccepted OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6HaCtrDiscontinuityTime.
"
::= { mipv6HaCounterEntry 1 }
mipv6HaBURequestsDenied OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 mipv6HaCtrDiscontinuityTime.
"
::= { mipv6HaCounterEntry 2 }
mipv6HaBCEntryCreationTime OBJECT-TYPE
SYNTAX DateAndTime
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
Expires: November 15, 2004 [Page 55]
Internet Draft February 16, 2004
DESCRIPTION
"The time when the current Binding Cache entry was
created for the mobile node.
"
::= { mipv6HaCounterEntry 3 }
mipv6HaBUAcceptedTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the last Binding Update was accepted
by the home agent for this mobile node.
"
::= { mipv6HaCounterEntry 4 }
mipv6HaBURejectionTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
::= { mipv6HaCounterEntry 5 }
mipv6HaRecentBURejectionCode OBJECT-TYPE
SYNTAX Mipv6BURequestRejectionCode
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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 that of the Status code
that corresponds to the reason of the rejection.
If there have been no rejections then this object will
be inaccessible.
"
::= { mipv6HaCounterEntry 6 }
mipv6HaCtrDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
Expires: November 15, 2004 [Page 56]
Internet Draft February 16, 2004
DESCRIPTION
"The value of sysUpTime on the most recent occasion at which
any one or more of counters in this row viz, instances of
'mipv6HaBURequestsAccepted' and 'mipv6HaBURequestsRejected'
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.
"
::= { mipv6HaCounterEntry 7 }
-- Home Agent List Table
mipv6HaListTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mipv6HaListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC-MIPV6 : Section 10.1"
::= { mipv6HaAdvertisement 4 }
mipv6HaListEntry OBJECT-TYPE
SYNTAX Mipv6HaListEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a router that is offering home
agent service.
"
INDEX { ipv6IfIndex, mipv6HaLinkLocalAddressType,
mipv6HaLinkLocalAddressType }
::= { mipv6HaListTable 1 }
Mipv6HaListEntry ::= SEQUENCE {
mipv6HaLinkLocalAddressType InetAddressType,
mipv6HaLinkLocalAddress InetAddress,
mipv6HaPreference Integer32,
mipv6HaRecvLifeTime Gauge32,
mipv6HaRecvTimeStamp DateAndTime
}
mipv6HaLinkLocalAddressType OBJECT-TYPE
Expires: November 15, 2004 [Page 57]
Internet Draft February 16, 2004
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address type for the link-local address
of the home agent that follows.
"
REFERENCE
"RFC-MIPV6 : Section 10.1"
::= { mipv6HaListEntry 1 }
mipv6HaLinkLocalAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The link local address of the home agent .
"
REFERENCE
"RFC-MIPV6 : Section 10.1"
::= { mipv6HaListEntry 2 }
mipv6HaPreference OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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.
"
REFERENCE
"RFC-MIPV6 : Section 10.1"
::= { mipv6HaListEntry 3 }
mipv6HaRecvLifeTime OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime for this home agent.
"
REFERENCE
"RFC-MIPV6 : Section 10.1"
::= { mipv6HaListEntry 4 }
Expires: November 15, 2004 [Page 58]
Internet Draft February 16, 2004
mipv6HaRecvTimeStamp OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the home agent advertisement was received.
"
::= { mipv6HaListEntry 5 }
--
-- The list of global addresses of a home agent in the
-- home agent list
--
mipv6HaGlAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mipv6HaGlAddrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the global addresses of the home
agents in the Home Agents List.
"
REFERENCE
"RFC-MIPV6 : Section 10.1"
::= { mipv6HaAdvertisement 5 }
mipv6HaGlAddrEntry OBJECT-TYPE
SYNTAX Mipv6HaGlAddrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A global address for a home agent in the Home Agents List.
"
INDEX { ipv6IfIndex, mipv6HaLinkLocalAddressType,
mipv6HaLinkLocalAddressType, mipv6HaGaAddrSeqNo }
::= { mipv6HaGlAddrTable 1 }
Mipv6HaGlAddrEntry ::= SEQUENCE {
mipv6HaGaAddrSeqNo Integer32,
mipv6HaGaGlobalAddressType InetAddressType,
mipv6HaGaGlobalAddress InetAddress
}
mipv6HaGaAddrSeqNo OBJECT-TYPE
SYNTAX Integer32 (1..1024) -- put the max value GYM
MAX-ACCESS not-accessible
STATUS current
Expires: November 15, 2004 [Page 59]
Internet Draft February 16, 2004
DESCRIPTION
"The index that along with ipv6IfIndex, mipv6HaLinkLocalAddressType
and mipv6HaLinkLocalAddressType uniquely identifies this row.
"
REFERENCE
"RFC-MIPV6 : Section 10.1"
::= { mipv6HaGlAddrEntry 1 }
mipv6HaGaGlobalAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address type for the global address of the
home agent that follows.
"
::= { mipv6HaGlAddrEntry 2 }
mipv6HaGaGlobalAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A global address of the home agent.
"
::= { mipv6HaGlAddrEntry 3 }
--
-- Notifications
--
mipv6HaNotifications OBJECT IDENTIFIER ::= { mipv6Notifications 0 }
mipv6MnRegistered NOTIFICATION-TYPE
OBJECTS {
mipv6BindingTimeRegistered,
mipv6BindingCOAType,
mipv6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent every time a mobile node
registers with the home agent for the first time.
Notifications will not be sent for subsequent updates
and/or refreshes.
"
::= { mipv6HaNotifications 1 }
Expires: November 15, 2004 [Page 60]
Internet Draft February 16, 2004
mipv6MnDeRegistered NOTIFICATION-TYPE
OBJECTS {
mipv6BindingTimeRegistered,
mipv6BindingCOAType,
mipv6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent every time a mobile node
de-registers with the home agent by sending a
Notifications will not be sent for subsequent updates
and/or refreshes.
"
::= { mipv6HaNotifications 2 }
mipv6MnMoved NOTIFICATION-TYPE
OBJECTS {
mipv6BindingTimeRegistered,
mipv6BindingCOAType,
mipv6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent every time a mobile node
sends a Binding Update with a new Care-of address.
Notifications will not be sent for subsequent updates
and/or refreshes for the same Care-of address.
"
::= { mipv6HaNotifications 3 }
mipv6MnBindingExpiredAtHA NOTIFICATION-TYPE
OBJECTS {
mipv6BindingTimeRegistered,
mipv6BindingCOAType,
mipv6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent when a binding for the
mobile node at the home agent expires and no timely
Binding Updates are received.
"
::= { mipv6HaNotifications 4 }
mipv6MnBindingExpiredAtCN NOTIFICATION-TYPE
OBJECTS {
mipv6BindingTimeRegistered,
mipv6BindingCOAType,
Expires: November 15, 2004 [Page 61]
Internet Draft February 16, 2004
mipv6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent when a binding for the
mobile node at the CN expires and no timely
Binding Updates are received.
"
::= { mipv6HaNotifications 5 }
Expires: November 15, 2004 [Page 62]
Internet Draft February 16, 2004
-- Conformance information
mipv6Groups OBJECT IDENTIFIER ::= { mipv6Conformance 1 }
mipv6Compliances OBJECT IDENTIFIER ::= { mipv6Conformance 2 }
-- Units of conformance
mipv6SystemGroup OBJECT-GROUP
OBJECTS {
mipv6Capabilities,
mipv6Status
}
STATUS current
DESCRIPTION
" A collection of objects for basic MIPv6
monitoring."
::= { mipv6Groups 1 }
mipv6BindingCacheGroup OBJECT-GROUP
OBJECTS {
-- mipv6BindingHomeAddressType,
-- mipv6BindingHomeAddress,
mipv6BindingCOAType,
mipv6BindingCOA,
mipv6BindingTimeRegistered,
mipv6BindingTimeGranted,
mipv6BindingTimeRemaining,
mipv6BindingMaxSeq,
mipv6BindingHomeRegn,
mipv6BindingUsageTS,
mipv6BindingUsageCount,
mipv6BindingAdminStatus
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
Binding cache.
"
::= { mipv6Groups 2 }
mipv6BindingHstGroup OBJECT-GROUP
OBJECTS {
-- mipv6BindingHstHomeAddressType,
-- mipv6BindingHstHomeAddress,
mipv6BindingHstCOAType,
mipv6BindingHstCOA,
-- mipv6BindingHstIndex,
mipv6BindingHstTimeRegistered,
mipv6BindingHstTimeExpired,
mipv6BindingHstHomeRegn,
Expires: November 15, 2004 [Page 63]
Internet Draft February 16, 2004
mipv6BindingHstUsageTS,
mipv6BindingHstUsageCount
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
binding history. This can be used to monitor
the movement of the mobile node.
"
::= { mipv6Groups 3 }
mipv6TotalTrafficGroup OBJECT-GROUP
OBJECTS {
mipv6InOctets,
mipv6HCInOctets,
mipv6InPkts,
mipv6HCInPkts,
mipv6OutOctets,
mipv6HCOutOctets,
mipv6OutPkts,
mipv6HCOutPkts,
mipv6CounterDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
total MIPv6 traffic.
"
::= { mipv6Groups 4 }
mipv6NodeTrafficGroup OBJECT-GROUP
OBJECTS {
mipv6NodeInOctets,
mipv6HCNodeInOctets,
mipv6NodeInPkts,
mipv6HCNodeInPkts,
mipv6NodeOutOctets,
mipv6HCNodeOutOctets,
mipv6NodeOutPkts,
mipv6HCNodeOutPkts,
mipv6NodeCtrDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
MIPv6 traffic due to a mobile node.
"
::= { mipv6Groups 5 }
Expires: November 15, 2004 [Page 64]
Internet Draft February 16, 2004
mipv6MnSystemGroup OBJECT-GROUP
OBJECTS {
-- mipv6MnHomeAddressType,
-- mipv6MnHomeAddress,
mipv6MnHomeAddressState
}
STATUS current
DESCRIPTION
" A collection of objects for basic monitoring
of the mobile node.
"
::= { mipv6Groups 6 }
mipv6MnConfGroup OBJECT-GROUP
OBJECTS {
mipv6MnDiscoveryRequests,
mipv6MnDiscoveryReplies,
mipv6MnDiscoveryTimeouts,
mipv6MnPrefixSolicitationsSent,
mipv6MnPrefixAdvsRecd,
mipv6MnPrefixAdvsIgnored,
mipv6MnMovedToFN,
mipv6MnMovedToHN
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the advertisement related info on the
mobile node.
"
::= { mipv6Groups 7 }
mipv6MnRegistrationGroup OBJECT-GROUP
OBJECTS {
-- mipv6MnBLNodeAddressType,
-- mipv6MnBLNodeAddress,
-- mipv6MnBLCOAType,
-- mipv6MnBLCOA,
mipv6MnBLLifeTimeRequested,
mipv6MnBLLifeTimeGranted,
mipv6MnBLMaxSeq,
mipv6MnBLTimeSent,
mipv6MnBLAccepted,
mipv6MnBLAcceptedTime,
mipv6MnBLRetransmissions,
--
-- Binding Update List
--
Expires: November 15, 2004 [Page 65]
Internet Draft February 16, 2004
mipv6MnMobilityMessagesSent,
mipv6MnMobilityMessagesRecd,
mipv6MnBUsToHA,
mipv6MnBUAcksFromHA,
mipv6MnBUsToCN,
mipv6MnBUAcksFromCN,
mipv6MnBindingErrorsFromCN,
mipv6MnICMPErrorsRecd,
mipv6MnBRRequestsRecd
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the registration statistics for the mobile node.
"
::= { mipv6Groups 8 }
mipv6CnStatsGroup OBJECT-GROUP
OBJECTS {
mipv6CnBURequestsAccepted,
mipv6CnBURequestsRejected,
mipv6CnBCEntryCreationTime,
mipv6CnBUAcceptedTime,
mipv6CnBURejectionTime,
mipv6CnBURejectionCode,
mipv6CnCtrDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the control messages and corresponding
statistics for each mobile node
communicating with the correspondent
node.
"
::= { mipv6Groups 9 }
mipv6HaSystemGroup OBJECT-GROUP
OBJECTS {
mipv6HaAdvsRecd,
mipv6HaAdvsSent,
mipv6HaAdvPreference,
mipv6HaAdvLifetime,
mipv6HaPrefixAdv,
mipv6HaPrefixSolicitation,
mipv6HaMCastCtlMsgSupport
}
STATUS current
Expires: November 15, 2004 [Page 66]
Internet Draft February 16, 2004
DESCRIPTION
" A collection of objects for monitoring
the Advertisement related parameters and
statistics for the home agent.
"
::= { mipv6Groups 10 }
mipv6HaListGroup OBJECT-GROUP
OBJECTS {
-- mipv6HaLinkLocalAddressType,
-- mipv6HaLinkLocalAddress,
mipv6HaPreference,
mipv6HaRecvLifeTime,
mipv6HaRecvTimeStamp,
-- mipv6HaGaAddrSeqNo,
mipv6HaGaGlobalAddressType,
mipv6HaGaGlobalAddress
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
Home Agent List on the home agent.
"
::= { mipv6Groups 11 }
mipv6HaStatsGroup OBJECT-GROUP
OBJECTS {
mipv6HaBURequestsAccepted,
mipv6HaBURequestsDenied,
mipv6HaBCEntryCreationTime,
mipv6HaBUAcceptedTime,
mipv6HaBURejectionTime,
mipv6HaRecentBURejectionCode,
mipv6HaCtrDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
registration related statistics on the home agent.
"
::= { mipv6Groups 12 }
mipv6CnGlobalStatsGroup OBJECT-GROUP
OBJECTS {
mipv6CnHomeTestInitsRecd,
mipv6CnHomeTestsSent,
mipv6CnCareOfTestInitsRecd,
Expires: November 15, 2004 [Page 67]
Internet Draft February 16, 2004
mipv6CnCareOfTestsSent,
mipv6CnBUsRecd,
mipv6CnBUAcksSent,
mipv6CnBRsSent,
mipv6CnBindingErrors,
mipv6CnBUsAccepted,
mipv6CnBUsRejected,
mipv6CnReasonUnspecified,
mipv6CnInsufficientResource,
mipv6CnHomeRegnNotSupported,
mipv6CnSeqNumberOutOfWindow,
mipv6CnExpiredHomeNonceIndex,
mipv6CnExpiredCareOfNonceIndex,
mipv6CnExpiredNonce,
mipv6CnRegTypeChangeDisallowed
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
advertisement and registration statistics on
a correspondent node.
"
::= { mipv6Groups 13 }
mipv6HaGlobalStatsGroup OBJECT-GROUP
OBJECTS {
mipv6HaHomeTestInitsRecd,
mipv6HaHomeTestsSent,
mipv6HaBUsRecd,
mipv6HaBUAcksSent,
mipv6HaBRAdviceSent,
mipv6HaBUsAccepted,
mipv6HaPrefDiscoverReqd,
mipv6HaReasonUnspecified,
mipv6HaAdmProhibited,
mipv6HaInsufficientResource,
mipv6HaHomeRegnNotSupported,
mipv6HaNotHomeSubnet,
mipv6HaNotHomeAgentForThisMN,
mipv6HaDupAddrDetectionFailed,
mipv6HaSeqNumberOutOfWindow,
mipv6HaExpiredHomeNonceIndex,
mipv6HaRegTypeChangeDisallowed
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
Expires: November 15, 2004 [Page 68]
Internet Draft February 16, 2004
advertisement and registration statistics on
a home agent.
"
::= { mipv6Groups 14 }
mipv6BindingCacheCtlGroup OBJECT-GROUP
OBJECTS {
mipv6BindingAdminStatus
}
STATUS current
DESCRIPTION
"A collection of objects for controlling the
Binding cache.
"
::= { mipv6Groups 15 }
mipv6NotificationGroup OBJECT-GROUP
OBJECTS {
mipv6MnRegistered,
mipv6MnDeRegistered,
mipv6MnMoved,
mipv6MnBindingExpiredAtHA,
mipv6MnBindingExpiredAtCN
}
STATUS current
DESCRIPTION
"A collection of objects for sending Notifications
from a home agent or correspondent node to the Manager
about the status of a mobile node.
"
::= { mipv6Groups 16 }
-- Compliance statements
mipv6CoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB."
MODULE -- this module
MANDATORY-GROUPS { mipv6SystemGroup }
::= { mipv6Compliances 1 }
mipv6Compliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
Expires: November 15, 2004 [Page 69]
Internet Draft February 16, 2004
which implement the MOBILE-IPV6-MIB and support
monitoring of the BindingCache and the Total Traffic.
"
MODULE -- this module
MANDATORY-GROUPS { mipv6SystemGroup,
mipv6BindingCacheGroup,
mipv6TotalTrafficGroup
}
::= { mipv6Compliances 2 }
mipv6Compliance3 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support monitoring of the BindingCache,
the Binding History, the total traffic and
the mobile node-wide traffic.
"
MODULE -- this module
MANDATORY-GROUPS { mipv6SystemGroup,
mipv6BindingCacheGroup,
mipv6BindingHstGroup,
mipv6TotalTrafficGroup,
mipv6NodeTrafficGroup
}
::= { mipv6Compliances 3 }
mipv6MnCoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support monitoring of the basic mobile node
functionality.
"
MODULE -- this module
MANDATORY-GROUPS { mipv6MnSystemGroup
}
::= { mipv6Compliances 4 }
mipv6MnCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support monitoring of the mobile node
functionality specifically the Discovery and
Expires: November 15, 2004 [Page 70]
Internet Draft February 16, 2004
Registration related statistics,
"
MODULE -- this module
MANDATORY-GROUPS { mipv6MnSystemGroup,
mipv6MnConfGroup,
mipv6MnRegistrationGroup,
mipv6TotalTrafficGroup
}
::= { mipv6Compliances 5 }
mipv6CnCoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support monitoring of the basic correspondent node
functionality.
"
MODULE -- this module
MANDATORY-GROUPS { mipv6CnGlobalStatsGroup,
mipv6TotalTrafficGroup
}
::= { mipv6Compliances 6 }
mipv6CnCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support monitoring of the basic correspondent node
functionality.
"
MODULE -- this module
MANDATORY-GROUPS { mipv6CnGlobalStatsGroup,
mipv6CnStatsGroup,
mipv6TotalTrafficGroup
}
::= { mipv6Compliances 7 }
mipv6HaCoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support monitoring of the basic home agent
functionality.
"
MODULE -- this module
Expires: November 15, 2004 [Page 71]
Internet Draft February 16, 2004
MANDATORY-GROUPS { mipv6HaSystemGroup
}
::= { mipv6Compliances 8 }
mipv6HaCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support monitoring of the home agent
functionality specifically the Home Agent List
and the home agent registration related statistics,
"
MODULE -- this module
MANDATORY-GROUPS { mipv6HaSystemGroup,
mipv6HaListGroup,
mipv6HaStatsGroup,
mipv6HaGlobalStatsGroup,
mipv6TotalTrafficGroup
}
::= { mipv6Compliances 9 }
mipv6HaCompliance3 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support monitoring and control of the home agent
functionality specifically the Home Agent List
and the home agent registration related statistics,
"
MODULE -- this module
MANDATORY-GROUPS { mipv6HaSystemGroup,
mipv6HaListGroup,
mipv6HaStatsGroup,
mipv6HaGlobalStatsGroup,
mipv6BindingCacheCtlGroup,
mipv6TotalTrafficGroup
}
::= { mipv6Compliances 10 }
mipv6NotificationCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the MOBILE-IPV6-MIB and
support Notification from HA or CN to management
stations about the mobile node status.
Expires: November 15, 2004 [Page 72]
Internet Draft February 16, 2004
"
MODULE -- this module
MANDATORY-GROUPS { mipv6NotificationGroup
}
::= { mipv6Compliances 11 }
END
Expires: November 15, 2004 [Page 73]
Internet Draft February 16, 2004
6. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
7. Acknowledgments
This draft is the product of discussions and deliberations carried out
in the WIDE-netman group.
Expires: November 15, 2004 [Page 74]
Internet Draft February 16, 2004
References
[Normative References]
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999
[MIPv6] Johnson, D., Perkins, C., Arkko J., "Mobility Support in IPv6"
draft-ietf-mobileip-ipv6-24.txt, work in progress,
June 30, 2003.
[Informative References]
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, April
1999
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
RFC 2573, April 1999
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for the
Internet-Standard Management Framework", RFC 3410,
Expires: November 15, 2004 [Page 75]
Internet Draft February 16, 2004
December 2002.
Expires: November 15, 2004 [Page 76]
Internet Draft February 16, 2004
Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
mipv6Status: This value of this object is used to enable or
disable the MIPv6 functionality on a MIPv6 entity.
Access to this MO may be abused to disrupt the
MIPv6 communication.
mipv6HaAdvPreference: Access to this object may be abused to
force
MNs into selecting the wrong HA.
mipv6HaAdvLifetime: Access to this object may be abused to set
the
advertised lifetime to incorrect values. That will
have an adverse impact on the MIPv6 communication.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
The address related objects in this MIB may be considered to be
particularly sensitive and/or private. The care of address related
objects reveal the location and movement of the mobile node. This
information may be considered to be private and sensitive and must
be carefully handled.
mipv6BindingHstCOAType
mipv6BindingHstCOA
mipv6MnBLCOAType
mipv6MnBLCOA
The mobile node's home address and home agent related information
may be considered to be sensitive too as these may provide clues to
a malicious party on ways to disrupt the mobile nodes communication
channels.
mipv6BindingHstHomeAddressType,
mipv6BindingHstHomeAddress,
mipv6MnHomeAddressType,
mipv6MnHomeAddress
The correspondent node's addresses related MOs will reveal the nodes
Expires: November 15, 2004 [Page 77]
Internet Draft February 16, 2004
with whom the mobile node is corresponding. This information may be
considered private and sensitive.
mipv6MnBLNodeAddressType,
mipv6MnBLNodeAddress
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
Expires: November 15, 2004 [Page 78]
Internet Draft February 16, 2004
Authors' Addresses
Glenn Mansfield Keeni
Cyber Solutions Inc.
6-6-3 Minami Yoshinari
Aoba-ku, Sendai 989-3204
Japan
Phone: +81-22-303-4012
EMail: glenn@cysols.com
Kenichi Nagami
INTEC NetCore Inc.
1-3-3, Shin-suna
Koto-ku, Tokyo, 135-0075
Japan
Phone: +81-3-5665-5069
E-mail: nagami@inetcore.com
Kazuhide Koide
Tohoku University
Katahira Campus
Sendai
Japan
Phone: +81-22-217-5454
E-mail: koide@shiratori.riec.tohoku.ac.jp
Sri Gundavelli
Cisco Systems
170 W.Tasman Drive,
San Jose, CA 95134
USA
Phone: +1-408-527-6109
Email: sgundave@cisco.com
Expires: November 15, 2004 [Page 79]
Internet Draft February 16, 2004
Full Copyright statement
"Copyright (C) The Internet Society (2003). All Rights
Reserved.
This document and translations of it may be copied and
furnished to others, and derivative works that comment on or
otherwise explain it or assist in its implmentation may be
prepared, copied, published and distributed, in whole or in
part, without restriction of any kind, provided that the above
copyright notice and this paragraph are included on all such
copies and derivative works. However, this document itself may
not be modified in any way, such as by removing the copyright
notice or references to the Internet Society or other Internet
organizations, except as needed for the purpose of developing
Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or
as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will
not be revoked by the Internet Society or its successors or
assigns.
This document and the information contained herein is provided
on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE."
Expires: November 15, 2004 [Page 80]
