| TOC |
|
By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.
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 May 24, 2009.
This memo defines a portion of the Management Information Base (MIB), the network mobility support (NEMO) MIB, for use with network management protocols in the Internet community. In particular, the NEMO MIB will be used to monitor and control a Mobile IPv6 node with NEMO functionality.
1.
The Internet-Standard Management Framework
2.
Overview
2.1.
The Mobile IPv6 Protocol and NEMO entities
2.2.
Implementation Guidance
2.3.
Terminology
2.4.
MIB Design
2.5.
The NEMO MIB
2.6.
IANA Considerations
2.7.
Security Considerations
2.8.
Acknowledgments
2.9.
References
2.10.
Normative References
2.11.
Informative References
§
Authors' Addresses
§
Intellectual Property and Copyright Statements
| TOC |
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].
| TOC |
| TOC |
Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol which allows nodes to remain reachable while moving around in the IPv6 Internet. Network Mobility Basic Support (NEMO) [RFC3963] is an extension to the Mobile IPv6 protocol which facilitates the movement of an entire network. The goals of Network Mobility support and related terminology are discussed in [RFC4886] and [RFC4885], respectively.
Typically mobile routers implement NEMO functionality for achieving network mobility. However, a mobile router may also function as a mobile node. In the context of this document, an entity that implements the NEMO protocol is a NEMO entity.
This document defines a set of managed objects (MOs) that can be used to monitor and control NEMO entities.
| TOC |
This document focuses on the management of a NEMO entity. The MIPv6MIB [RFC4295] defines the managed objects for a mobile node. Implementations supporting both the mobile node and NEMO functionality SHOULD implement the managed objects defined for the NEMO entities and mobile nodes from both the MIPv6MIB and NEMOMIB.
| TOC |
The terminology used in this document is consistent with the definitions used in the Mobile IPv6 protocol specification [RFC3775] and the NEMO Basic Support specification [RFC3963].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].
| TOC |
The NEMO MIB comprises of the following groups of definitions:
- nemoCore: a generic group containing objects that are common to all the NEMO entities.
- nemoHa: this group models the home agent service. It is composed of objects specific to the services and associated advertisement parameters offered by the home agent on each of its links. It also contains objects pertaining to the maintenance of the home agent list on each of the links on which the service is offered.
- nemoMr: this group models the mobile router service. It is composed of objects specific to the Dynamic Home Agent discovery function and related parameters. It also contains objects that record the movement of the mobile router.
- nemoNotifications: defines the set of notifications that will be used to asynchronously monitor the NEMO entities.
The tables contained in the above groups are as follows:
nemoBindingCacheTable : 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.
nemoMrEgressIfTable : contains information on the configured egress interfaces.
nemoMrBLTable : models the Binding Update List on the mobile router. It contains information about the registration requests sent by the mobile router and the corresponding results.
nemoHaCounterTable : contains registration statistics for all mobile routers registered with the home agent.
nemoHaMobileNetworkPrefixTable : contains the list of the mobile network prefixes that are maintained by the home agent.
| TOC |
NEMO-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32, Counter32,
Integer32, Gauge32,
-- Counter64,
OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
TruthValue, DateAndTime, TimeStamp
FROM SNMPv2-TC
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InetAddressType, InetAddress, InetAddressPrefixLength
FROM INET-ADDRESS-MIB
InterfaceIndex
FROM IF-MIB
mip6BindingHomeAddressType, mip6BindingHomeAddress,
mip6MnBLEntry, mip6BindingCacheEntry,
-- mip6MnHomeAddressType, mip6MnHomeAddress,
mip6MnBLCOAType, mip6MnBLCOA
FROM MOBILEIPV6-MIB
;
nemoMIB MODULE-IDENTITY
LAST-UPDATED "200811160000Z" -- 16th November, 2008
ORGANIZATION "IETF MEXT Working Group"
CONTACT-INFO
" Sri Gundavelli
Postal: Cisco
170 W.Tasman Drive,
San Jose, CA 95134
USA
Tel: +1-408-527-6109
Email: sgundave@cisco.com
Glenn Mansfield Keeni
Postal: Cyber Solutions Inc.
6-6-3, Minami Yoshinari
Aoba-ku, Sendai, Japan 989-3204.
Tel: +81-22-303-4012
Fax: +81-22-303-4015
E-mail: glenn@cysols.com
Kenichi Nagami
Postal: INTEC NetCore Inc.
1-3-3, Shin-suna
Koto-ku, Tokyo, 135-0075
Japan
Tel: +81-3-5665-5069
E-mail: nagami@inetcore.com
Kazuhide Koide
Postal: Tohoku University
Research Institute of Electrical Communication,
Tohoku University.
2-1-1 Katahira, Aoba-ku,
Sendai, Miyagi, Japan 980-8577.
Tel: +81-22-217-5455
E-mail: koide@shiratori.riec.tohoku.ac.jp
Support Group E-mail: mext@ietf.org
"
DESCRIPTION
"The MIB module for monitoring a NEMO entity.
Copyright (C) The IETF Trust (2008). 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 and remove this
-- note
REVISION "200811160000Z" -- 16th November 2008
DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number and remove this
-- note
::= { mib-2 YYY } -- will be assigned by IANA
-- IANA Reg.: Please assign a value for "YYY" under the 'mib-2'
-- subtree and record the assignment in the SMI Numbers
-- registry.
--
-- RFC Ed.: When the above assignment has been made, please
-- remove the above note
-- replace "YYY" here with the assigned value and
-- remove this note.
-- The NEMO MIB has the following primary groups
nemoNotifications OBJECT IDENTIFIER ::= { nemoMIB 0 }
nemoObjects OBJECT IDENTIFIER ::= { nemoMIB 1 }
nemoConformance OBJECT IDENTIFIER ::= { nemoMIB 3 }
nemoCore OBJECT IDENTIFIER ::= { nemoObjects 1 }
nemoMr OBJECT IDENTIFIER ::= { nemoObjects 2 }
nemoCn OBJECT IDENTIFIER ::= { nemoObjects 3 }
nemoHa OBJECT IDENTIFIER ::= { nemoObjects 4 }
-- The sub groups
nemoSystem OBJECT IDENTIFIER ::= { nemoCore 1 }
nemoBindings OBJECT IDENTIFIER ::= { nemoCore 2 }
nemoConfiguration OBJECT IDENTIFIER ::= { nemoCore 3 }
nemoStats OBJECT IDENTIFIER ::= { nemoCore 4 }
nemoMrSystem OBJECT IDENTIFIER ::= { nemoMr 1 }
nemoMrConf OBJECT IDENTIFIER ::= { nemoMr 2 }
nemoMrRegistration OBJECT IDENTIFIER ::= { nemoMr 3 }
nemoMrGlobalStats OBJECT IDENTIFIER ::= { nemoMr 4 }
nemoHaAdvertisement OBJECT IDENTIFIER ::= { nemoHa 1 }
nemoHaStats OBJECT IDENTIFIER ::= { nemoHa 2 }
nemoHaRegistration OBJECT IDENTIFIER ::= { nemoHa 3 }
nemoHaGlobalStats OBJECT IDENTIFIER ::= { nemoHaStats 1 }
-- Textual Conventions
-- NemoStatus ::= TEXTUAL-CONVENTION
-- STATUS current
-- DESCRIPTION
-- "This object represents the state of the NEMO
-- entity. The entity could be at home, isolated,
-- roaming or in unknown state.
-- "
-- SYNTAX INTEGER {
-- isolated (1),
-- roaming (2),
-- home (3),
-- unknown (4)
-- }
NemoBURequestRejectionCode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of the status field in the Binding
Acknowledgment message when the Binding Update
was rejected for NEMO specific conditions.
"
REFERENCE
"RFC 3963 : Section 4.2"
SYNTAX INTEGER {
mobileRouterOperationNotPermitted (1), --(Code 140)
invalidPrefix (2), --(Code 141)
notAuthorizedForPrefix (3), --(Code 142)
forwardingSetupFailed (4) --(Code 143)
}
--
--
-- nemoSystem group
--
--
nemoCapabilities OBJECT-TYPE
SYNTAX BITS {
mobileRouter (0),
homeAgentSupport (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the NEMO functions that
are supported by this managed entity. Multiple
NEMO functions may be supported by a
single entity.
"
REFERENCE
"RFC 3963 : Section 3"
::= { nemoSystem 1 }
nemoStatus OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates whether the NEMO
function is enabled for the managed entity. If it
is enabled, the agent discovery and registration
functions will be operational.
Changing the status from enabled(1) to disabled(2)
will terminate the agent discovery and registration
functions. On the other hand, changing the status
from disabled(2) to enabled(1) will start the agent
discovery and registration functions.
The value of this object SHOULD remain unchanged
across reboots of the managed entity.
"
::= { nemoSystem 2 }
nemoCounterDiscontinuityTime 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 NEMO entity's
counters viz, counters with OID prefix 'nemoMrConf'
or 'nemoMrRegnCounters' or 'nemoMrGlobalStats'
or 'nemoHaGlobalStats' 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.
"
::= { nemoStats 1 } -- This will change !! GLENN
--
--
-- nemoConfiguration group
--
--
nemoMrBLTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoMrBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table corresponds to the Binding Update List
(BL) that includes NEMO related information and
is maintained by the mobile router. The table
holds a row for every binding that the mobile
router has established or is trying to establish.
Entries from the table are deleted as the lifetime
of the binding expires.
"
REFERENCE
"RFC 3775 : Section 4.5, 11.1, RFC 3963 : Section 5.2"
::= { nemoMrRegistration 1 }
nemoMrBLEntry OBJECT-TYPE
SYNTAX NemoMrBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing additional information contained
in a Binding Update sent by a nemo-enabled mobile
router to its home agent.
"
AUGMENTS {mip6MnBLEntry}
::= { nemoMrBLTable 1 }
NemoMrBLEntry ::= SEQUENCE {
nemoMrBLMode BITS,
nemoMrBLMrFlag TruthValue,
nemoMrBLHomeAddressPrefixLength InetAddressPrefixLength,
nemoMrBLCareofAddressPrefixLength InetAddressPrefixLength,
nemoMrBLActiveEgressIfIndex InterfaceIndex,
nemoMrBLEstablishedHomeTunnelIfIndex InterfaceIndex
}
nemoMrBLMode OBJECT-TYPE
SYNTAX BITS {
implicitMode (0),
explicitMode (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"implicitMode(0) if the Mobile Router does not include a
Mobile Network Prefix Option in the Binding Update. The
Home Agent can use any mechanism (not defined in this
document) to determine the Mobile Network Prefix(es)
owned by the Mobile Router and to set up forwarding for
the Mobile Network. One example would be manual
configuration at the Home Agent mapping the Mobile
Router's Home Address to the information required for
setting up forwarding for the Mobile Network.
explicitMode(1) if the Mobile Router includes one or
more Mobile Network Prefix Options in the Binding
Update. These options contain information about the
Mobile Network Prefix(es) configured on the Mobile
Network.
"
REFERENCE
"RFC 3963 : Section 5.2"
::= { nemoMrBLEntry 1 }
nemoMrBLMrFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"true(1) if the mobile router sent the binding update
with Mobile Router Flag that indicates to the home
agent that the binding update is from a mobile router.
false(0) implies that the mobile router is acting
as a mobile node.
"
REFERENCE
"RFC 3963 : Section 4.1, 5.1"
::= { nemoMrBLEntry 2 }
nemoMrBLHomeAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The prefix length of the home address that the
mobile router is using for roaming.
"
REFERENCE
"RFC 3963 : Section 3"
::= { nemoMrBLEntry 3 }
nemoMrBLCareofAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The prefix length of the care-of Address that the
mobile router currently is using for roaming.
"
REFERENCE
"RFC 3963 : Section 3"
::= { nemoMrBLEntry 4 }
nemoMrBLActiveEgressIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interface index of the currently active
egress interface.
"
REFERENCE
"RFC 3963 : Section 5.5"
::= { nemoMrBLEntry 5 }
nemoMrBLEstablishedHomeTunnelIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interface index of the tunnel established
between the mobile router and the home agent
for NEMO traffic.
"
REFERENCE
"RFC 3963 : Section 5.5"
::= { nemoMrBLEntry 6 }
-- Mobile Router Registration Group Counters
nemoMrRegnCounters OBJECT IDENTIFIER ::= { nemoMrRegistration 2 }
nemoMrMobilityMessagesSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of mobility messages, i.e. IPv6
datagrams with Mobility Header, sent by the mobile
node. This will include Binding Updates sent by a
mobile router with the Mobile Router Flag set.
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC3775 : Section 4.2, 6.1, RFC 3963: Section 4.1"
::= { nemoMrRegnCounters 1 }
nemoMrMobilityMessagesRecd 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. This will include Binding
Acknowledgements with Mobile Router Flag set, that
are sent to a mobile router.
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC3775 : Section 4.2, 6.1, RFC 3963: Section 4.1, 4.2"
::= { nemoMrRegnCounters 2 }
nemoMrPrefixRegMode OBJECT-TYPE
SYNTAX BITS {
other (0),
implicitMode (1),
explicitMode (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the mode in which
the mobile network prefixes will be
registered with the Home Agent.
"
REFERENCE
"RFC 3963 : Section 5.2"
::= { nemoMrRegistration 3 }
nemoHaMobileNetworkPrefixTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoHaMobileNetworkPrefixEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the mobile network prefixes
that the home agent maintains for the Mobile Router.
"
REFERENCE
"RFC 3963 : Section 6.1.2"
::= { nemoHaRegistration 1 }
nemoHaMobileNetworkPrefixEntry OBJECT-TYPE
SYNTAX NemoHaMobileNetworkPrefixEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This entry represents the mobile network prefixes
that are maintained by the home agent.
There are two modes for setting the mobile network
prefixes on a home agent.
In implicit mode, the mobile network prefixes is
configured by some method(ex. pre-defined).
In explicit mode, the binding update from the mobile
router contains the mobile network prefix list.
The home agent maintains Prefix Table that contains
the home address of the mobile router for verifying
the prefix list from the mobile router.
This entry contains only the mobile network prefixes
that are registered by the corresponding binding
update. It does not include the prefixes learned
through the dynamic routing process between the home
agent and the mobile router.
The instances of the columnar objects in this entry
pertain to an interface for a particular value of
mip6BindingHomeAddressType, mip6BindingHomeAddress,
and nemoHaMobileNetworkPrefixSeqNo.
The nemoHaMobileNetworkPrefixSeqNo object is used to
distinguish between multiple instances of
the mobile network prefix on the same binding update
for the same set of
mip6BindingHomeAddressType, mip6BindingHomeAddress.
There is no upper-bound on the maximum number of
mobile network prefixes on a binding update but, for
practical purposes, the upper bound of the value
nemoHaMobileNetworkPrefixSeqNo is set to 1024.
Implementers need to be aware that if the total
number of octets in mip6BindingHomeAddress
exceeds 112, then OIDs of column
instances in this row will have more than 128
sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { mip6BindingHomeAddressType,
mip6BindingHomeAddress,
nemoHaMobileNetworkPrefixSeqNo
}
::= { nemoHaMobileNetworkPrefixTable 1 }
NemoHaMobileNetworkPrefixEntry ::= SEQUENCE {
nemoHaMobileNetworkPrefixSeqNo Integer32,
nemoHaMobileNetworkPrefixType InetAddressType,
nemoHaMobileNetworkPrefix InetAddress,
nemoHaMobileNetworkPrefixLength Unsigned32,
nemoHaMobileNetworkPrefixSource BITS
}
nemoHaMobileNetworkPrefixSeqNo OBJECT-TYPE
SYNTAX Integer32 (1..1024)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index that along with mip6BindingHomeAddressType,
and mip6BindingHomeAddress uniquely identifies this
row.
One binding update has some mobile network prefixes.
So when we describe the prefix list corresponding to
the binding cache, it will be needed as a sub index.
"
REFERENCE
"RFC 3963 : Section 2, 6.1, 6.2"
::= { nemoHaMobileNetworkPrefixEntry 1 }
nemoHaMobileNetworkPrefixType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address type for the mobile network prefix
that follows.
"
::= { nemoHaMobileNetworkPrefixEntry 2 }
nemoHaMobileNetworkPrefix OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A mobile network prefix related to the
corresponding Binding Update.
The type of the address represented by this object
is specified by the corresponding
nemoHaMobileNetworkPrefixType object.
"
REFERENCE
"RFC 3963 : Section 2 , 6.1, 6.2"
::= { nemoHaMobileNetworkPrefixEntry 3 }
nemoHaMobileNetworkPrefixLength OBJECT-TYPE
SYNTAX Unsigned32 (0..128)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The length of the prefix specified by the corresponding
nemoHaMobileNetworkPrefix Object.
"
REFERENCE
"RFC 3963 : Section 4.3, 6.1, 6.2"
::= { nemoHaMobileNetworkPrefixEntry 4 }
nemoHaMobileNetworkPrefixSource OBJECT-TYPE
SYNTAX BITS{
configured (0),
bindingUpdate (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The information source of the mobile network prefix
configured with the binding update.
Configured(0) represents that the information is
introduced to the home agent without binding update.
Binding Update(1) represents that the information is
introduced to the home agent by the mobile network
prefix option in the binding update and verified
by the Prefix Table that the home agent maintains
for each home addresses of the mobile router.
"
REFERENCE
"RFC 3963 : Section 4.3, 6.1, 6.2"
::= { nemoHaMobileNetworkPrefixEntry 5 }
nemoBindingCacheTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoBindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table models the Binding Cache
that includes NEMO related information and
is maintained by the home agent.
Entries in this table are not required to survive
a reboot of the Home Agent.
"
REFERENCE
"RFC 3775 : Section 4.5, 9.1, 10.1,
RFC 3963 : Section 6.1"
::= { nemoBindings 1 }
nemoBindingCacheEntry OBJECT-TYPE
SYNTAX NemoBindingCacheEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing additional information related
to nemo-enabled entries in the binding cache table
of the Home Agent.
"
AUGMENTS {mip6BindingCacheEntry}
::= { nemoBindingCacheTable 1 }
NemoBindingCacheEntry ::= SEQUENCE {
nemoBindingMrFlag TruthValue,
nemoBindingMrMode BITS
}
nemoBindingMrFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"true(1) indicates that the binding cache entry is from
an entity acting as a mobile router.
false(0) implies that the binding cache entry is from
an entity acting as a mobile node.
"
REFERENCE
"RFC 3963 : Section 6.1.1, 6.2"
::= { nemoBindingCacheEntry 1 }
nemoBindingMrMode OBJECT-TYPE
SYNTAX BITS {
implicitMode(0),
explicitMode(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the mode of mobile router
to tell the home agent to determine which prefixes
belong to the mobile router.
"
REFERENCE
"RFC 3963 : Section 5.2, 6.1.1, 6.2"
::= { nemoBindingCacheEntry 2 }
--
-- nemoMrEgressIfTable
--
nemoMrEgressIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoMrEgressIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table representing the egress interfaces that
will be used by the mobile router for roaming to
foreign networks. Each entry in this table
represents a configured egress interface.
"
::= { nemoMrSystem 1 }
nemoMrEgressIfEntry OBJECT-TYPE
SYNTAX NemoMrEgressIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the egress interface table. It
represents a single egress interface entry.
"
INDEX { nemoMrEgressIfIndex, nemoMrEgressIfPriority }
::= { nemoMrEgressIfTable 1 }
NemoMrEgressIfEntry ::=
SEQUENCE {
nemoMrEgressIfIndex InterfaceIndex,
nemoMrEgressIfPriority Unsigned32,
nemoMrEgressIfDescription SnmpAdminString,
nemoMrEgressIfRoamHoldDownTime Gauge32
}
nemoMrEgressIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index of the interface on the mobile router.
"
::= { nemoMrEgressIfEntry 1 }
nemoMrEgressIfPriority OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The priority configured to the egress interface.
This value will be configured to a value between 0
and 255.
"
::= { nemoMrEgressIfEntry 2 }
nemoMrEgressIfDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The description of the egress interface on the
mobile router, that will be used for roaming to
foreign networks.
"
::= { nemoMrEgressIfEntry 3 }
nemoMrEgressIfRoamHoldDownTime OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object indicates the time for which the
egress interface will be held down during roaming
to avoid interface flapping.
"
::= { nemoMrEgressIfEntry 4 }
nemoMrDiscoveryRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Modified Dynamic Home Agent Address
Discovery Requests, with Mobile Router Support Flag
set, sent by the mobile router.
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.1"
::= { nemoMrConf 1 }
nemoMrDiscoveryReplies OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Modified Dynamic Home Agent Address
Discovery Replies, with Mobile Router Support Flag
set, received by the mobile router.
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.2"
::= { nemoMrConf 2 }
nemoMrDiscoveryRepliesRouterFlagZero OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Modified Dynamic Home Agent Address
Discovery Replies with Mobile Router Support Flag set
to 0 although the flag in the corresponding request
is set to 1.
It implies that there is no home agent that supports
Mobile Router functionality in the 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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1, RFC 3963: Section 7.2"
::= { nemoMrConf 3 }
nemoMrMovedHome OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of times the mobile router 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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 3."
::= { nemoMrConf 4 }
nemoMrMovedOutofHome OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of times the mobile router has detected
movement to a foreign network from the home
network, has acquired a 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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 3."
::= { nemoMrConf 5 }
nemoMrMovedFNtoFN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of times the mobile router has detected
movement to/from a foreign network from/to another
foreign network. Note that 'movement' implies
movement in layer 3, i.e. the mobile routers care-of
address changed and it initiated the care-of address
registration process.
If there are multiple egress interfaces, this counter
counts the total number of movements.
The movement as a mobile node of the mobile entity
is not counted.
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 3."
::= { nemoMrConf 6 }
nemoMrBetterIfDetected OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of times the NEMO entity has found egress
interface with better priority.
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
nemoCounterDiscontinuityTime.
"
::= { nemoMrConf 7 }
--
-- nemoStats:nemoMrGlobalStats
--
nemoMrBindingAcksWONemoSupport OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgements without
NEMO support received by the mobile router.
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 5.3."
::= { nemoMrGlobalStats 1 }
nemoMrBindingRegTypeChanged OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgements
received by the mobile router with status code
indicating
'Registration type change disallowed' (Code 139).
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1, RFC 3963 : Section 6.2"
::= { nemoMrGlobalStats 2 }
nemoMrOpNotPermitted OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgement
received by the mobile router with status code
indicating
'Mobile Router Operation not permitted'
(Code 140).
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 6.6"
::= { nemoMrGlobalStats 3 }
nemoMrInvalidPrefix OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgement
received by the mobile router with status code
indicating 'Invalid Prefix' (Code 141).
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 6.6."
::= { nemoMrGlobalStats 4 }
nemoMrNotAuthorizedForPrefix OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgements
received by the mobile router with status code
indicating
'Not Authorized for Prefix' (Code 142).
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 6.6."
::= { nemoMrGlobalStats 5 }
nemoMrForwardingSetupFailed OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgements
received by the mobile router with status code
indicating 'Forwarding Setup failed' (Code 143).
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 6.6."
::= { nemoMrGlobalStats 6 }
--
-- nemoStats:nemoHaGlobalStats
--
nemoHaBindingAcksWONemoSupport OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgements
without NEMO support 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
nemoHaCtrDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 5.3"
::= { nemoHaGlobalStats 1 }
nemoHaBindingRegTypeChanged OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Update requests
rejected by the home agent with status code
in the Binding Acknowledgement indicating
'Registration type change disallowed' (Code 139).
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
nemoHaCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1, RFC 3963 : Section 6.2"
::= { nemoHaGlobalStats 2 }
nemoHaOpNotPermitted OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Update requests
rejected by the home agent with status code in
the Binding Acknowledgement indicating
'Mobile Router Operation not permitted'
(Code 140).
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
nemoHaCtrDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 6.6"
::= { nemoHaGlobalStats 3 }
nemoHaInvalidPrefix OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Update requests
rejected by the home agent with status code in
the Binding Acknowledgement indicating
'Invalid Prefix' (Code 141).
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
nemoHaCtrDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 6.6"
::= { nemoHaGlobalStats 4 }
nemoHaNotAuthorizedForPrefix OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Update requests
rejected by the home agent with status code in
the Binding Acknowledgement indicating
'Not Authorized for Prefix' (Code 142).
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 6.6"
::= { nemoHaGlobalStats 5 }
nemoHaForwardingSetupFailed OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Update requests
rejected by the home agent with status code in
the Binding Acknowledgement indicating
'Forwarding Setup failed' (Code 143).
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
nemoCounterDiscontinuityTime.
"
REFERENCE
"RFC 3963 : Section 6.6"
::= { nemoHaGlobalStats 6 }
nemoHaCounterTable OBJECT-TYPE
SYNTAX SEQUENCE OF NemoHaCounterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing registration statistics for all
mobile routers registered with the home agent.
"
::= { nemoHaStats 2 }
nemoHaCounterEntry OBJECT-TYPE
SYNTAX NemoHaCounterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Home agent registration statistics for a mobile
router.
Implementors need to be aware that if the total
number of octets in mip6BindingHomeAddress
exceeds 113 then OIDs of column instances in
this row will have more than 128 sub-identifiers and
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { mip6BindingHomeAddressType,
mip6BindingHomeAddress
}
::= { nemoHaCounterTable 1 }
NemoHaCounterEntry ::= SEQUENCE {
nemoHaBURequestsAccepted Counter32,
nemoHaBURequestsDenied Counter32,
nemoHaBCEntryCreationTime DateAndTime,
nemoHaBUAcceptedTime DateAndTime,
nemoHaBURejectionTime DateAndTime,
nemoHaRecentBURejectionCode NemoBURequestRejectionCode,
nemoHaCtrDiscontinuityTime TimeStamp
}
nemoHaBURequestsAccepted OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests from the
mobile router 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
nemoHaCtrDiscontinuityTime.
"
::= { nemoHaCounterEntry 1 }
nemoHaBURequestsDenied OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests from the
mobile router 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
nemoHaCtrDiscontinuityTime.
"
::= { nemoHaCounterEntry 2 }
nemoHaBCEntryCreationTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the current Binding Cache entry was
created for the mobile router.
"
::= { nemoHaCounterEntry 3 }
nemoHaBUAcceptedTime 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 router.
"
::= { nemoHaCounterEntry 4 }
nemoHaBURejectionTime 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 router.
If there have been no rejections then this object
will be inaccessible.
"
::= { nemoHaCounterEntry 5 }
nemoHaRecentBURejectionCode OBJECT-TYPE
SYNTAX NemoBURequestRejectionCode
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If a Binding Acknowledgment is sent to the mobile
router, this is the Status code (>= 128) that is
returned in the Binding Acknowledgment.
In case a Binding Acknowledgment is not sent to the
mobile router then this will be the value of the
Status code that corresponds to the reason of the
rejection.
If there have been no rejections then this object
will be inaccessible.
"
::= { nemoHaCounterEntry 6 }
nemoHaCtrDiscontinuityTime 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 'nemoHaBURequestsAccepted',
'nemoHaBURequestsDenied' and 'nemoHaGlobalStats'
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.
"
::= { nemoHaCounterEntry 7 }
--
--
-- nemoNotifications
--
--
nemoHomeTunnelEstablished NOTIFICATION-TYPE
OBJECTS {
nemoMrBLActiveEgressIfIndex,
nemoMrBLEstablishedHomeTunnelIfIndex,
-- mip6MnHomeAddressType,
-- mip6MnHomeAddress,
mip6MnBLCOAType,
mip6MnBLCOA,
nemoMrBLHomeAddressPrefixLength,
nemoMrBLCareofAddressPrefixLength
}
STATUS current
DESCRIPTION
"This notification is sent by the mobile router
every time the tunnel is established between the
home agent and the mobile router.
"
REFERENCE
"RFC 3963 : Section 5.5"
::= { nemoNotifications 1 }
nemoHomeTunnelReleased NOTIFICATION-TYPE
OBJECTS {
nemoMrBLActiveEgressIfIndex,
nemoMrBLEstablishedHomeTunnelIfIndex,
-- mip6MnHomeAddressType,
-- mip6MnHomeAddress,
mip6MnBLCOAType,
mip6MnBLCOA,
nemoMrBLHomeAddressPrefixLength,
nemoMrBLCareofAddressPrefixLength
}
STATUS current
DESCRIPTION
"This notification is sent by the mobile router
every time the tunnel is deleted between the home
agent and the mobile router.
"
REFERENCE
"RFC 3963 : Section 5.5"
::= { nemoNotifications 2}
-- Conformance information
nemoGroups OBJECT IDENTIFIER ::= { nemoConformance 1 }
nemoCompliances OBJECT IDENTIFIER ::= { nemoConformance 2 }
-- Units of conformance
nemoSystemGroup OBJECT-GROUP
OBJECTS {
nemoCapabilities,
nemoStatus
}
STATUS current
DESCRIPTION
" A collection of objects for basic NEMO
monitoring."
::= { nemoGroups 1 }
nemoBindingCacheGroup OBJECT-GROUP
OBJECTS {
nemoBindingMrFlag,
nemoBindingMrMode
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
NEMO extensions of the Binding Cache."
::= { nemoGroups 2 }
nemoStatsGroup OBJECT-GROUP
OBJECTS {
nemoCounterDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for
monitoring NEMO statistics."
::= { nemoGroups 3 }
nemoMrConfGroup OBJECT-GROUP
OBJECTS {
-- nemoMrEgressIfIndex,
-- nemoMrEgressIfPriority,
nemoMrEgressIfDescription,
nemoMrEgressIfRoamHoldDownTime,
nemoMrDiscoveryRequests,
nemoMrDiscoveryReplies,
nemoMrDiscoveryRepliesRouterFlagZero,
nemoMrMovedHome,
nemoMrMovedOutofHome,
nemoMrMovedFNtoFN,
nemoMrBetterIfDetected
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the configuration-related information on
the mobile router.
"
::= { nemoGroups 4 }
nemoMrRegistrationGroup OBJECT-GROUP
OBJECTS {
nemoMrBLMode,
nemoMrBLMrFlag,
nemoMrBLHomeAddressPrefixLength,
nemoMrBLCareofAddressPrefixLength,
nemoMrBLActiveEgressIfIndex,
nemoMrBLEstablishedHomeTunnelIfIndex,
nemoMrMobilityMessagesSent,
nemoMrMobilityMessagesRecd,
nemoMrPrefixRegMode,
nemoMrBindingAcksWONemoSupport,
nemoMrBindingRegTypeChanged,
nemoMrOpNotPermitted,
nemoMrInvalidPrefix,
nemoMrNotAuthorizedForPrefix,
nemoMrForwardingSetupFailed
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the registration details and statistics for
the mobile router.
"
::= { nemoGroups 5 }
nemoHaSystemGroup OBJECT-GROUP
OBJECTS {
-- nemoHaMobileNetworkPrefixSeqNo,
nemoHaMobileNetworkPrefixType,
nemoHaMobileNetworkPrefix,
nemoHaMobileNetworkPrefixLength,
nemoHaMobileNetworkPrefixSource
}
STATUS current
DESCRIPTION
" A collection of objects for basic NEMO
configuration monitoring at the Home Agent."
::= { nemoGroups 6 }
nemoHaStatsGroup OBJECT-GROUP
OBJECTS {
nemoHaBURequestsAccepted,
nemoHaBURequestsDenied,
nemoHaBCEntryCreationTime,
nemoHaBUAcceptedTime,
nemoHaBURejectionTime,
nemoHaRecentBURejectionCode,
nemoHaCtrDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
NEMO registration-related statistics on the
home agent.
"
::= { nemoGroups 7 }
nemoHaGlobalStatsGroup OBJECT-GROUP
OBJECTS {
nemoHaBindingAcksWONemoSupport,
nemoHaBindingRegTypeChanged,
nemoHaOpNotPermitted,
nemoHaInvalidPrefix,
nemoHaNotAuthorizedForPrefix,
nemoHaForwardingSetupFailed
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring basic
NEMO advertisement and registration statistics
on a Home Agent."
::= { nemoGroups 8 }
nemoNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
nemoHomeTunnelEstablished,
nemoHomeTunnelReleased
}
STATUS current
DESCRIPTION
"A collection of notifications from a home agent
or correspondent node to the Manager about the
tunnel status of the mobile router.
"
::= { nemoGroups 9 }
-- Compliance statements
nemoCoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB.
"
MODULE -- this module
MANDATORY-GROUPS { nemoSystemGroup
}
::= { nemoCompliances 1 }
nemoCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB and support
monitoring of the Binding Cache.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { nemoSystemGroup,
nemoBindingCacheGroup
}
::= { nemoCompliances 2 }
nemoCoreReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB without support
for read-write (i.e., in read-only mode).
"
MODULE -- this module
MANDATORY-GROUPS { nemoSystemGroup
}
OBJECT nemoStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { nemoCompliances 3 }
nemoReadOnlyCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB without support
for read-write (i.e., in read-only mode) and
support monitoring of the Binding Cache.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { nemoSystemGroup,
nemoBindingCacheGroup
}
OBJECT nemoStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { nemoCompliances 4 }
nemoMrCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB for monitoring
configuration-related information, registration
details and statistics on a mobile router.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6MnHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6MnHomeAddress
-- object.
--
-- OBJECT mip6MnHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6MnHomeAddress
-- object.
--
-- OBJECT mip6MnBLNodeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6MnBLNodeAddress
-- object.
--
-- OBJECT mip6MnBLNodeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6MnBLNodeAddress
-- object.
"
MODULE -- this module
MANDATORY-GROUPS { nemoStatsGroup,
nemoMrConfGroup,
nemoMrRegistrationGroup
}
::= { nemoCompliances 5 }
nemoMrReadOnlyCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB without support
for read-write (i.e., in read-only mode) and
support for monitoring configuration-related
information, registration details and statistics
on a mobile router.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6MnHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6MnHomeAddress
-- object.
--
-- OBJECT mip6MnHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6MnHomeAddress
-- object.
--
-- OBJECT mip6MnBLNodeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6MnBLNodeAddress
-- object.
--
-- OBJECT mip6MnBLNodeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6MnBLNodeAddress
-- object.
"
MODULE -- this module
MANDATORY-GROUPS { nemoStatsGroup,
nemoMrConfGroup,
nemoMrRegistrationGroup
}
OBJECT nemoMrEgressIfDescription
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT nemoMrEgressIfRoamHoldDownTime
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT nemoMrPrefixRegMode
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { nemoCompliances 6 }
nemoHaCoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB for configuration
monitoring at the Home Agent.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { nemoHaSystemGroup
}
::= { nemoCompliances 7 }
nemoHaCompliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB with support for
monitoring of the home agent functionality
specifically the home-agent-registration-related
statistics.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { nemoHaSystemGroup,
nemoHaStatsGroup,
nemoHaGlobalStatsGroup
}
::= { nemoCompliances 8 }
nemoNotificationCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
which implement the NEMO-MIB and support
Notification from home agent.
"
MODULE -- this module
MANDATORY-GROUPS { nemoNotificationGroup
}
::= { nemoCompliances 9 }
END
| TOC |
IANA should assign a base arc in the mib-2 (standards track) OID tree for the 'nemoMIB' MODULE-IDENTITY defined in the NEMO MIB.
| TOC |
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write. 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: nemoStatus: The value of this object is used to enable or disable the NEMO functionality on a NEMO entity. Access to this MO may be abused to disrupt the communication that depends on NEMO. nemoMrPrefixRegMode: The value of this object is used to control the mode in which mobile network prefixes will be registered with the Home Agent. Access to this object may be abused to disrupt the setting up of mobile network prefixes.
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 mobile network prefix- related objects reveal the configuration of the mobile router. This information may be considered to be private and sensitive and must be carefully handled. nemoHaMobileNetworkPrefixType nemoHaMobileNetworkPrefix nemoHaMobileNetworkPrefixLength
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.
| TOC |
The authors would like to thank Alex Petrescu, Pascal Thubert, Kent Leung, T.J Kniveton and Thierry Ernst for their review comments on this document.
| TOC |
| TOC |
[RFC2119] Bradner, S., Key words for use in RFCs to Indicate Requirements Levels, BCP 14, RFC 2119, March 1997.
[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.
[RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility Support in IPv6 RFC 3775, June 2004.
[RFC3963] Thubert, P., Petrescu, A., Wakikawa, R. and V. Devarapalli, Network Mobility (NEMO) Basic Support Protocol, RFC 3963, Jan 2005.
[RFC4295] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, The Mobile IPv6 MIB, RFC 4295, April 2006.
| TOC |
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, Introduction and Applicability Statements for Internet-Standard Management Framework, RFC 3410, December 2002.
[RFC4885] T. Ernst and H.-Y. Lach., Network Mobility Support Terminology, RFC 4885, July 2007.
[RFC4886] T. Ernst. Network Mobility Support Goals and Requirements, RFC 4886, July 2007.
| TOC |
| Sri Gundavelli | |
| Cisco | |
| 170 West Tasman Drive | |
| San Jose, CA 95134 | |
| USA | |
| Phone: | +1-408-527-6109 |
| Email: | sgundave@cisco.com |
| Glenn Mansfield Keeni | |
| Cyber Solutions | |
| 6-6-3 Minami Yoshinari, Aoba-ku | |
| Sendai 989-3204, | |
| Japan | |
| Phone: | +81-22-303-4012 |
| Email: | glenn@cysols.com |
| Kazuhide Koide | |
| Tohoku University | |
| 2-1-1 Katahira, Aoba-ku | |
| Sendai 980-8577, | |
| Japan | |
| Phone: | +81-22-217-5455 |
| Email: | koide@shiratori.riec.tohoku.ac.jp |
| Kenichi Nagami | |
| INTEC NetCore | |
| 1-3-3, Shin-suna | |
| Koto-ku, Tokyo, 135-0075, | |
| Japan | |
| Phone: | +81-3-5665-5069 |
| Email: | nagami@inetcore.com |
| TOC |
Copyright © The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.