Network Working Group G. Keeni
Request for Comments: 4295 Cyber Solutions Inc.
Category: Standards Track K. Koide
Tohoku University
K. Nagami
INTEC NetCore Inc.
S. Gundavelli
Cisco Systems Inc.
April 2006
Mobile IPv6 Management Information Base
Status of This Memo
このメモのステータス
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
この文書は、インターネットコミュニティのためのインターネット標準トラックプロトコルを指定し、改善のための議論と提案を要求します。このプロトコルの標準化状態と状態への「インターネット公式プロトコル標準」（STD 1）の最新版を参照してください。このメモの配布は無制限です。
Copyright Notice
著作権表示
Copyright (C) The Internet Society (2006).
著作権（C）インターネット協会（2006）。
Abstract
抽象
This memo defines a portion of the Management Information Base (MIB), the Mobile-IPv6 MIB, for use with network management protocols in the Internet community. In particular, the Mobile-IPv6 MIB will be used to monitor and control the mobile node, home agent, and correspondent node functions of a Mobile IPv6 (MIPv6) entity.
このメモは、インターネットコミュニティでのネットワーク管理プロトコルで使用するために、管理情報ベース（MIB）、モバイルIPv6のMIBの部分を定義します。特に、モバイルIPv6のMIB監視およびモバイルIPv6（MIPv6の）エンティティの移動ノード、ホーム・エージェント、及び通信相手ノードの機能を制御するために使用されます。
Table of Contents
目次
1. The Internet-Standard Management Framework ......................2
2. Overview ........................................................2
2.1. The Mobile IPv6 Protocol Entities ..........................2
2.2. Terminology ................................................3
3. Mobile IPv6 Monitoring and Control Requirements .................3
4. MIB Design ......................................................4
5. The Mobile-IPv6 MIB .............................................6
6. Security Considerations .......................................104
7. IANA Considerations ...........................................106
8. References ....................................................106
8.1. Normative References .....................................106
8.2. Informative References ...................................107
9. Acknowledgements ..............................................107
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
現在のインターネット標準の管理フレームワークを記述したドキュメントの詳細な概要については、RFC 3410 [RFC3410]のセクション7を参照してください。
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).
管理対象オブジェクトが仮想情報店を介してアクセスされ、管理情報ベースまたはMIBと呼ばれます。 MIBオブジェクトは、一般的に簡易ネットワーク管理プロトコル（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].
MIBのオブジェクトは、管理情報（SMI）の構造で定義されたメカニズムを使用して定義されています。このメモは、STD 58、RFC 2578 [RFC2578]、STD 58、RFC 2579 [RFC2579]とSTD 58、RFC 2580 [RFC2580]に記載されているSMIv2のに準拠しているMIBモジュールを指定します。
Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol that allows nodes to remain reachable while moving around in the IPv6 Internet. An entity that implements the MIPv6 protocol is a MIPv6 entity. There are three types of entities envisaged by the MIPv6 protocol.
モバイルIPv6（MIPv6の）[RFC3775]はIPv6インターネットの周りを移動しながらノードが到達可能なままであることを可能にするプロトコルを指定します。 MIPv6のプロトコルを実装するエンティティは、MIPv6のエンティティです。 MIPv6のプロトコルによって想定される事業体の3つのタイプがあります。
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.
モバイルノード（MN）：まだそのホームアドレス経由で到達可能でありながら、別のリンクから接続点を変更することができますノード。
correspondent node (CN): A peer node with which a mobile node is communicating. The correspondent node may be either mobile or stationary. (Note that a correspondent node does not necessarily require MIPv6 support.)
コレスポンデントノード（CN）：モバイルノードが通信しているピア・ノード。コレスポンデントノードは、モバイルまたは固定のいずれであってもよいです。 （コレスポンデントノードは必ずしもMIPv6のサポートを必要としないことに注意してください。）
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.
ホームエージェント（HA）：モバイルノードが現在の気付アドレスを登録していると、モバイルノードのホームリンク上のルータ。モバイルノードがホームから離れている間、ホームエージェントは、モバイルノードのホームアドレス宛てのホームリンク上のパケットを傍受し、それらをカプセル化し、モバイルノードの登録気付アドレスへのルートそれらを。
This document defines a set of managed objects (MOs) that can be used to monitor and control MIPv6 entities.
この文書では、MIPv6のエンティティを監視および制御するために使用することができる管理対象オブジェクト（MOS）のセットを定義します。
The terminology used in this document is consistent with the definitions used in Mobile IPv6 protocol specification [RFC3775].
本書で使用される用語は、モバイルIPv6プロトコル仕様[RFC3775]で使用される定義と一致しています。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].
キーワード "MUST"、 "MUST NOT"、 "REQUIRED"、 "SHALL"、 "SHOULD"、 "ないもの"、 "推奨" "ない（SHOULD NOT）"、 "MAY"、 "推奨NOT"、および「OPTIONAL BCP 14、RFC 2119 [RFC2119]に記載されているように「この文書に解釈されるべきです。
For managing a MIPv6 entity it is necessary to monitor the following:
MIPv6のエンティティを管理するためには、次のことを監視する必要があります。
o capabilities of MIPv6 entities
o traffic due to MIPv6
o binding-related statistics (at home agent, correspondent
node, and mobile node)
o binding details (at home agent and correspondent node)
o history of Binding Updates (at home agent, correspondent
node, and mobile node)
The MIPv6 protocol document stipulates that several MIPv6-related parameters should be manually configurable. The MIPv6 MIB should define managed objects that can be used to configure the related parameters, for example:
MIPv6のプロトコル文書は、いくつかのMIPv6関連パラメータを手動で設定可能であることを規定しています。 MIPv6のMIBは、例えば、関連するパラメータを設定するために使用することができ、管理対象オブジェクトを定義する必要があります。
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.
The basic principle has been to keep the MIB as simple as possible and at the same time to make it effective enough so that the essential needs of monitoring and control are met. It is envisaged that wherever possible existing MIBs will be used (e.g., IPSec MIB, Neighbor Discovery MIB, Tunnel MIB [RFC4087]) for monitor and control of MIPv6 entities.
基本的な原理は、監視と制御の基本的なニーズが満たされるように十分それを有効にするためにできるだけ簡単にMIBを維持すると同時にすることでした。可能な限り既存のMIBはモニターとMIPv6のエンティティの制御のために（例えば、IPSecのMIB、近隣探索MIB、トンネルMIB [RFC4087]）が使用されることが想定されます。
It is assumed that the Mobile IPv6 Management Information Base (MOBILEIPV6-MIB) will always be implemented in conjunction with the IPv6-capable version of the IP-MIB [RFC4293]. The MOBILEIPV6-MIB uses the textual conventions defined in the INET-ADDRESS-MIB [RFC4001].
モバイルIPv6管理情報ベース（モバイルIPv6-MIB）は常にIP-MIB [RFC4293]のIPv6対応のバージョンに関連して実施されることが想定されます。モバイルIPv6-MIBは、INET-ADDRESS-MIB [RFC4001]で定義されたテキストの表記法を使用します。
The Mobile-IPv6 MIB is composed of the following groups of definitions:
モバイルIPv6のMIBは定義の次のグループで構成されています。
- mip6Core: a generic group containing objects that are
common to all the Mobile IPv6 entities.
- mip6Ha: this group models the home agent service. It is
composed of objects specific to the services and associated
advertisement parameters offered by the home agent on each
of its links. It also contains objects pertaining to the
maintenance of the home agent list on each of the links on
which the service is offered.
- mip6Mn: this group models the mobile node service. It is
composed of objects specific to the Dynamic Home Agent
discovery function and related parameters. It also contains
objects that record the movement of the mobile node.
- mip6Cn: models the correspondent node and is primarily
scoped to its participation in the Return Routability
procedure for achieving Route Optimization triggered by
the mobile node.
- mip6Notifications: defines the set of notifications that
will be used to asynchronously monitor the Mobile IPv6
entities.
The tables contained in the above groups are as follows:
次のように上記の基に含まれるテーブルは、次のとおりです。
mip6BindingCacheTable : models the binding cache on the home
agent and correspondent node. It
contains details of the Binding Update
requests that have been received and
accepted.
mip6BindingHistoryTable : tracks the history of the binding
cache.
mip6NodeTrafficTable : the mobile node-wise traffic counters.
mip6MnHomeAddressTable : contains all the home addresses pertaining to the mobile node and the corresponding registration status. mip6MnBLTable : models the Binding Update List on the mobile node. It contains information about the registration requests sent by the mobile node and the corresponding results. mip6CnCounterTable : contains the mobile node-wise registration statistics. mip6HaConfTable : contains the configurable advertisement parameters for all the interfaces on which the home agent service is advertised. mip6HaCounterTable : contains registration statistics for all mobile nodes registered with the home agent. mip6HaListTable : contains the list of all routers that are acting as home agents on each of the interfaces on which the home agent service is offered by this router. mip6HaGlAddrTable : contains the global addresses of the home agents.
mip6MnHomeAddressTableは：モバイルノードと対応する登録ステータスに関連するすべてのホームアドレスが含まれています。 mip6MnBLTable：モバイル・ノード上のモデルバインディング更新リストを。これは、モバイルノードによって送信された登録要求と対応する結果に関する情報が含まれています。 mip6CnCounterTableは：モバイル・ノード毎の登録の統計情報が含まれています。 mip6HaConfTableは：ホームエージェントサービスが宣伝されているすべてのインターフェイスに対して設定可能な広告のパラメータが含まれています。 mip6HaCounterTableは：ホームエージェントに登録されているすべてのモバイルノードの登録統計情報が含まれています。 mip6HaListTableは：ホームエージェントサービスは、このルータによって提供されているインターフェイスのそれぞれのホームエージェントとして動作しているすべてのルータのリストが含まれています。 mip6HaGlAddrTableは：ホームエージェントのグローバルアドレスが含まれています。
MOBILEIPV6-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32, Integer32, Counter32,
Gauge32, Counter64,
OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
TEXTUAL-CONVENTION,
TruthValue, DateAndTime, TimeStamp
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB
ipv6InterfaceIfIndex
FROM IP-MIB
;
mip6MIB MODULE-IDENTITY LAST-UPDATED "200602010000Z" -- 1st February 2006 ORGANIZATION "IETF mip6 Working Group" CONTACT-INFO " Glenn Mansfield Keeni Postal: Cyber Solutions Inc. 6-6-3, Minami Yoshinari Aoba-ku, Sendai, Japan 989-3204. Tel: +81-22-303-4012 Fax: +81-22-303-4015 E-mail: glenn@cysols.com
mip6MIBのMODULE-IDENTITY LAST-UPDATED "200602010000Z" - 2006年2月1日ORGANIZATION "IETF MIP6ワーキンググループ" CONTACT-INFO「グレンマンスフィールドKeeni郵便：サイバー・ソリューションズ6-6-3、南良成青葉区、仙台市、日本989-3204電話：+ 81-22-303-4012ファックス：+ 81-22-303-4015 Eメール：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
電話：+ 81-3-5665-5069 Eメール：nagami@inetcore.com
Kazuhide Koide Postal: Tohoku University 2-1-1, Katahira Aoba-ku, Sendai, 980-8577 Japan
かずひで こいで ぽｓたｌ： とほく うにゔぇｒしｔｙ ２ー１ー１、 かたひら あおばーく、 せんだい、 ９８０ー８５７７ じゃぱん
Tel: +81-22-217-5454 E-mail: koide@shiratori.riec.tohoku.ac.jp
電話：+ 81-22-217-5454 Eメール：koide@shiratori.riec.tohoku.ac.jp
Sri Gundavelli Postal: Cisco Systems 170 W.Tasman Drive, San Jose, CA 95134 USA
スリGundavelli郵便：シスコシステムズ170 W.Tasmanドライブ、サンノゼ、CA 95134 USA
Tel: +1-408-527-6109 E-mail: sgundave@cisco.com
電話：+ 1-408-527-6109 Eメール：sgundave@cisco.com
Support Group E-mail: mip6@ietf.org"
サポートグループEメール：mip6@ietf.org」
DESCRIPTION "The MIB module for monitoring Mobile-IPv6 entities.
DESCRIPTION「モバイルIPv6のエンティティを監視するためのMIBモジュール。
Copyright (C) The Internet Society 2006. This
version of this MIB module is part of RFC 4295;
see the RFC itself for full legal notices.
"
REVISION "200602010000Z" -- 1st February 2006 DESCRIPTION "Initial version, published as RFC 4295."
REVISION「200602010000Z」 - 2006年2月1日の説明「初期バージョン、RFC 4295.として公開」
::= { mib-2 133 }
-- The major groups
- 主要なグループ
mip6Notifications OBJECT IDENTIFIER ::= { mip6MIB 0 }
mip6Objects OBJECT IDENTIFIER ::= { mip6MIB 1 }
mip6Conformance OBJECT IDENTIFIER ::= { mip6MIB 2 }
mip6Core OBJECT IDENTIFIER ::= { mip6Objects 1 }
mip6Mn OBJECT IDENTIFIER ::= { mip6Objects 2 }
mip6Cn OBJECT IDENTIFIER ::= { mip6Objects 3 }
mip6Ha OBJECT IDENTIFIER ::= { mip6Objects 4 }
-- The sub groups
- サブグループ
mip6System OBJECT IDENTIFIER ::= { mip6Core 1 }
mip6Bindings OBJECT IDENTIFIER ::= { mip6Core 2 }
mip6Stats OBJECT IDENTIFIER ::= { mip6Core 3 }
mip6MnSystem OBJECT IDENTIFIER ::= { mip6Mn 1 }
mip6MnConf OBJECT IDENTIFIER ::= { mip6Mn 2 }
mip6MnRegistration OBJECT IDENTIFIER ::= { mip6Mn 3 }
mip6CnSystem OBJECT IDENTIFIER ::= { mip6Cn 1 } mip6CnStats OBJECT IDENTIFIER ::= { mip6Cn 2 }
mip6HaAdvertisement OBJECT IDENTIFIER ::= { mip6Ha 1 }
mip6HaStats OBJECT IDENTIFIER ::= { mip6Ha 2 }
-- Textual Conventions
Mip6BURequestRejectionCode ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of the status field in the Binding
Acknowledgment message when the Binding Update
was rejected.
"
REFERENCE
"RFC 3775 : Section 6.1.8"
SYNTAX INTEGER {
reasonUnspecified (1), --(Code 128)
admProhibited (2), --(Code 129)
insufficientResource (3), --(Code 130)
homeRegistrationNotSupported (4), --(Code 131)
notHomeSubnet (5), --(Code 132)
notHomeAgentForThisMobileNode (6), --(Code 133)
duplicateAddressDetectionFailed (7), --(Code 134)
sequenceNumberOutOfWindow (8), --(Code 135)
expiredHomeNonceIndex (9), --(Code 136)
expiredCareofNonceIndex (10), --(Code 137)
expiredNonces (11), --(Code 138)
registrationTypeChangeDisallowed(12) --(Code 139)
}
mip6Capabilities OBJECT-TYPE
SYNTAX BITS {
mobileNode (0),
homeAgent (1),
correspondentNode (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the Mobile IPv6 functions that
are supported by this managed entity. Multiple
Mobile IPv6 functions may be supported by a single
entity.
"
REFERENCE
"RFC 3775 : Section 3.2, 4.1"
::= { mip6System 1 }
mip6Status OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object indicates whether the Mobile IPv6 function is enabled for the managed entity. If it is enabled, the agent discovery and registration functions will be operational. Changing the status from enabled(1) to disabled(2) will terminate the agent discovery and registration functions. On the other hand, changing the status from disabled(2) to enabled(1) will start the agent discovery and registration functions.
mip6StatusのOBJECT-TYPE SYNTAX INTEGER {イネーブル（1）、（2）無効} MAX-ACCESS読み取りと書き込みステータス現在の説明は「このオブジェクトはモバイルIPv6機能が管理されたエンティティに対して有効になっているかどうかを示す。これが有効になっている場合、エージェント発見登録機能が動作になります。無効に有効（1）からのステータスを変更する（2）エージェント発見および登録機能を終了します。一方、無効からのステータスを変更する（2）有効にするために（1）を開始しますエージェント発見と登録機能。
The value of this object SHOULD remain unchanged
across reboots of the managed entity.
"
::= { mip6System 2 }
-- mip6BindingCache
- p6Bi ndingCache
mip6BindingCacheTable OBJECT-TYPE SYNTAX SEQUENCE OF Mip6BindingCacheEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table models the Binding Cache on the managed entity. The cache is maintained by home agents and correspondent nodes. It contains both correspondent registration entries and home registration entries.
管理エンティティのMip6BindingCacheEntry MAX-ACCESSステータス現在の説明は「このテーブルモデルバインディングキャッシュmip6BindingCacheTable OBJECT-TYPE構文配列。キャッシュは、ホームエージェントとコレスポンデントノードによって維持されている。これは、通信員登録エントリおよびホーム登録エントリの両方が含まれています。
Entries in this table are not required to survive
a reboot of the managed entity.
"
REFERENCE
"RFC 3775 : Section 4.5, 9.1, 10.1"
::= { mip6Bindings 1 }
mip6BindingCacheEntry OBJECT-TYPE SYNTAX Mip6BindingCacheEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry represents a conceptual row in the binding cache table. It represents a single Binding Update.
mip6BindingCacheEntry OBJECT-TYPE構文Mip6BindingCacheEntry MAX-ACCESSステータス現在の説明は「このエントリは、バインディングキャッシュテーブルの概念的な列を表す。これは、単一の結合更新を表します。
Implementors need to be aware that if the total
number of octets in mip6BindingHomeAddress
exceeds 113, then OIDs of column
instances in this row will have more than 128
sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { mip6BindingHomeAddressType, mip6BindingHomeAddress }
::= { mip6BindingCacheTable 1 }
Mip6BindingCacheEntry ::=
SEQUENCE {
mip6BindingHomeAddressType InetAddressType,
mip6BindingHomeAddress InetAddress,
mip6BindingCOAType InetAddressType,
mip6BindingCOA InetAddress,
mip6BindingTimeRegistered DateAndTime,
mip6BindingTimeGranted Gauge32,
mip6BindingTimeRemaining Gauge32,
mip6BindingHomeRegn TruthValue,
mip6BindingMaxSeq Unsigned32,
mip6BindingUsageTS DateAndTime,
mip6BindingUsageCount Gauge32,
mip6BindingAdminStatus INTEGER
}
mip6BindingHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mip6BindingHomeAddress
that follows.
"
::= { mip6BindingCacheEntry 1 }
mip6BindingHomeAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The home address of the mobile node corresponding to the Binding Cache entry. This field is used as the key for searching the mobile node's current care-of address in the Binding Cache.
mip6BindingHomeAddressのOBJECT-TYPE構文InetAddress MAX-ACCESSステータス現在の説明は「Binding Cacheエントリーに対応するモバイルノードのホームアドレス。このフィールドは、バインディングにモバイルノードの現在の気付アドレスを検索するためのキーとして使用されていますキャッシュ。
The type of the address represented by this object
is specified by the corresponding
mip6BindingHomeAddressType object.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 2 }
mip6BindingCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the mip6BindingCOA that
follows.
"
::= { mip6BindingCacheEntry 3 }
mip6BindingCOA OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The care-of address of the mobile node indicated by the home address field (mip6BindingHomeAddress) in this Binding Cache entry.
mip6BindingCOAのOBJECT-TYPE構文InetAddress MAX-ACCESS read-onlyステータス現在の説明「気付けこの結合キャッシュ項目にホーム・アドレス・フィールド（mip6BindingHomeAddress）で示されるモバイルノードのアドレス。
The type of the address represented by this object
is specified by the corresponding mip6BindingCOAType
object.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 4 }
mip6BindingTimeRegistered OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry was
created.
"
::= { mip6BindingCacheEntry 5 }
mip6BindingTimeGranted OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime in seconds granted to the mobile node
for this registration.
"
::= { mip6BindingCacheEntry 6 }
mip6BindingTimeRemaining OBJECT-TYPE
SYNTAX Gauge32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime in seconds remaining for this
registration.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 7 }
mip6BindingHomeRegn OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether or not this Binding
Cache entry is a home registration entry (applicable
only on nodes that support home agent
functionality).
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 8 }
mip6BindingMaxSeq OBJECT-TYPE
SYNTAX Unsigned32 (0..65536)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of the Sequence Number field
received in previous Binding Updates for this home
address (mip6BindingHomeAddress).
"
REFERENCE
"RFC 3775 : Section 9.1, 9.5.1"
::= { mip6BindingCacheEntry 9 }
mip6BindingUsageTS OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this entry was last looked up.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 10 }
mip6BindingUsageCount OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this entry was looked up.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 11 }
mip6BindingAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
active (1),
inactive (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This is an administrative object used to control
the status of a binding cache entry. By default
the value will be 'active'(1).
A value of 'inactive'(2) will indicate that the
validity of the entry is suspended. It does not
exist in the binding cache for all practical
purposes.
The state can be changed from 'active' to
'inactive' by operator intervention.
Causing the state to change to 'inactive' results
in the entry being deleted from the cache.
Attempts to change the status from 'inactive'
to 'active' will be rejected.
"
REFERENCE
"RFC 3775 : Section 9.1"
::= { mip6BindingCacheEntry 12 }
-- mip6BindingHistory -- Once the lifetime expires an entry will be removed from the -- Binding Cache. -- For monitoring purposes it will be useful to have access to -- the history of the Binding Cache. BindingHistoryTable serves -- this purpose. It records the history of the Bindings. -- The size of the table will be left to implementors.
- mip6BindingHistory - バインディングキャッシュ - 寿命がエントリを満了した後から削除されます。 - バインディングキャッシュの歴史 - 監視の目的のために、へのアクセス権を持っていることが有用であろう。 BindingHistoryTableがあります - この目的を。これは、バインディングの履歴を記録します。 - テーブルのサイズは、実装者に任されます。
mip6BindingHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6BindingHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing a record of the bindings.
"
::= { mip6Bindings 2 }
mip6BindingHistoryEntry OBJECT-TYPE SYNTAX Mip6BindingHistoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The record of a binding.
mip6BindingHistoryEntryのOBJECT-TYPE SYNTAX Mip6BindingHistoryEntry MAX-ACCESSステータス現在の説明は「結合の記録。
Implementors need to be aware that if the total
number of octets in mip6BindingHstHomeAddress
exceeds 112, then OIDs of column
instances in this row will have more than 128
sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { mip6BindingHstHomeAddressType,
mip6BindingHstHomeAddress ,
mip6BindingHstIndex}
::= { mip6BindingHistoryTable 1 }
Mip6BindingHistoryEntry ::=
SEQUENCE {
mip6BindingHstHomeAddressType InetAddressType,
mip6BindingHstHomeAddress InetAddress,
mip6BindingHstIndex Unsigned32,
mip6BindingHstCOAType InetAddressType,
mip6BindingHstCOA InetAddress,
mip6BindingHstTimeRegistered DateAndTime,
mip6BindingHstTimeExpired DateAndTime,
mip6BindingHstHomeRegn TruthValue,
mip6BindingHstUsageTS DateAndTime,
mip6BindingHstUsageCount Gauge32
}
mip6BindingHstHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the
mip6BindingHstHomeAddress that follows.
"
::= { mip6BindingHistoryEntry 1 }
mip6BindingHstHomeAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "Mobile node's home address.
mip6BindingHstHomeAddressのOBJECT-TYPE構文InetAddress MAX-ACCESSステータス現在の説明「モバイルノードのホームアドレス。
The type of the address represented by this object
is specified by the corresponding
mip6BindingHstHomeAddressType object.
"
::= { mip6BindingHistoryEntry 2 }
mip6BindingHstIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index to uniquely identify this record along
with the mobile node's HomeAddress type and
HomeAddress. It should be monotonically increasing.
It may wrap after reaching its max value."
::= { mip6BindingHistoryEntry 3 }
mip6BindingHstCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the mip6BindingHstCOA that
follows.
"
::= { mip6BindingHistoryEntry 4 }
mip6BindingHstCOA OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Mobile node's care-of address. One mobile node can
have multiple bindings with different
care-of addresses.
The type of the address represented by this object
is specified by the corresponding
mip6BindingHstCOAType object.
"
::= { mip6BindingHistoryEntry 5 }
mip6BindingHstTimeRegistered OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry was
created.
"
::= { mip6BindingHistoryEntry 6 }
mip6BindingHstTimeExpired OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this Binding Cache entry expired.
"
::= { mip6BindingHistoryEntry 7 }
mip6BindingHstHomeRegn OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether or not this Binding
Cache entry is a home registration entry (applicable
only on nodes that support home agent
functionality).
"
::= { mip6BindingHistoryEntry 8 }
mip6BindingHstUsageTS OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp when this entry was last looked up.
"
::= { mip6BindingHistoryEntry 9 }
mip6BindingHstUsageCount OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times this entry was looked up.
"
::= { mip6BindingHistoryEntry 10 }
-- mip6TrafficCounters
- mip6TrafficCounters
-- MIPv6 Traffic will be characterized by -- IPv6 datagrams which satisfy at least one of the following -- conditions -- - the datagrams are tunneled to the mobile node by the HA -- - the datagrams are reverse tunneled by the MN to the HA -- - the datagrams have the Routing header type 2 set. -- - the datagrams have the Home Address option set in the -- Destination Option extension header -- - the datagrams have the mobility header
- 条件 - - 以下の少なくとも一つを満たすIPv6データグラム - MIPv6のトラフィックによって特徴付けされる - データグラムは、HAによってモバイルノードにトンネリングされる - - データグラムは逆にMNによってトンネリングされますHA - - データグラムルーティングヘッダタイプ2セットを有しています。 - - デスティネーションオプション拡張ヘッダ - - - データグラムは、モビリティヘッダを持つデータグラムは、に設定されたホームアドレスオプションを持っています
mip6TotalTraffic OBJECT IDENTIFIER ::= { mip6Stats 1 }
-- REFERENCE
-- "RFC 3775 : Section 4.1, 6.3, 6.4"
mip6InOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams
received by the MIPv6 entity. This will include
datagrams with the Mobility Header, the Home Address
option in the Destination Option extension header
(Next Header value = 60), or the type 2 Routing
Header. It will also include the IPv6 datagrams that
are reverse tunneled to a home agent from a mobile
node's home address.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 1 }
mip6HCInOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams
received by the MIPv6 entity. This will include
datagrams with the Mobility Header, the Home Address
option in the Destination Option extension header
(Next Header value = 60), or the type 2 Routing
Header. It will also include the IPv6 datagrams that
are reverse tunneled to a home agent from a mobile
node's home address.
This object is a 64-bit version of mip6InOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 2 }
mip6InPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams received by the MIPv6
entity. This will include datagrams with the
Mobility Header, the Home Address option in the
Destination Option extension header (Next Header
value = 60), or the type 2 Routing Header.
It will also include the IPv6 datagrams that are
reverse tunneled to a home agent from a mobile
node's home address.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 3 }
mip6HCInPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams received by the MIPv6
entity. This will include datagrams with the
Mobility Header, the Home Address option in the
Destination Option extension header (Next Header
value = 60), or the type 2 Routing Header. It will
also include the IPv6 datagrams that are reverse
tunneled to a home agent from a mobile node's home
address.
This object is a 64-bit version of mip6InPkts.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 4 }
mip6OutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams
sent by the MIPv6 entity. This will include
datagrams with the Mobility Header, the Home Address
option in the Destination Option extension header
(Next Header value = 60), or the type 2 Routing
Header. It will also include the IPv6 datagrams that
are reverse tunneled to a home agent from a mobile
node's home address.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 5 }
mip6HCOutOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams
sent by the MIPv6 entity. This will include
datagrams with the Mobility Header, the Home Address
option in the Destination Option extension header
(Next Header value = 60), or the type 2 Routing
Header. It will also include the IPv6 datagrams that
are reverse tunneled to a home agent from a mobile
node's home address.
This object is a 64-bit version of mip6OutOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 6 }
mip6OutPkts 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
Mobility Header, the Home Address option in the
Destination Option extension header (Next Header
value = 60), or the type 2 Routing Header. It will
also include the IPv6 datagrams that are reverse
tunneled to a home agent from a mobile node's home
address.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 7 }
mip6HCOutPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams sent by the MIPv6
entity. This will include datagrams with the
Mobility Header, the Home Address option in the
Destination Option extension header (Next Header
value = 60), or the type 2 Routing Header. It will
also include the IPv6 datagrams that are reverse
tunneled to a home agent from a mobile node's home
address.
This object is a 64-bit version of mip6OutPkts.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6TotalTraffic 8 }
mip6CounterDiscontinuityTime 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
'mip6TotalTraffic' or 'mip6CnGlobalStats' or
'mip6HaGlobalStats' suffered a discontinuity.
If no such discontinuities have occurred since the
last re-initialization of the local management
subsystem, then this object will have a zero value.
"
::= { mip6TotalTraffic 9 }
-- mip6NodeTrafficCounters
- mip6NodeTrafficCounters
mip6NodeTrafficTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6NodeTrafficEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing MIPv6 traffic counters per mobile
node.
"
::= { mip6Stats 2 }
mip6NodeTrafficEntry OBJECT-TYPE SYNTAX Mip6NodeTrafficEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The MIPv6 traffic statistics for a mobile node.
mip6NodeTrafficEntryのOBJECT-TYPE SYNTAX Mip6NodeTrafficEntry MAX-ACCESSステータス現在の説明「モバイルノードのためのMIPv6トラフィック統計情報。
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 }
::= { mip6NodeTrafficTable 1 }
Mip6NodeTrafficEntry ::=
SEQUENCE {
mip6NodeInOctets Counter32,
mip6HCNodeInOctets Counter64,
mip6NodeInPkts Counter32,
mip6HCNodeInPkts Counter64,
mip6NodeOutOctets Counter32,
mip6HCNodeOutOctets Counter64,
mip6NodeOutPkts Counter32,
mip6HCNodeOutPkts Counter64,
mip6NodeCtrDiscontinuityTime TimeStamp
}
mip6NodeInOctets 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 datagrams with the Mobility
Header or the Home Address option in the Destination
Option extension header (Next Header value = 60).
It will also include the IPv6 datagrams that are
reverse tunneled to a home agent from the mobile
node's home address.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 1 }
mip6HCNodeInOctets 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 datagrams with the Mobility
Header or the Home Address option in the Destination
Option extension header (Next Header value = 60).
It will also include the IPv6 datagrams that are
reverse tunneled to a home agent from the mobile
node's home address.
This object is a 64-bit version of mip6NodeInOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 2 }
mip6NodeInPkts 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 or
the Home Address option in the Destination
Option extension header (Next Header value = 60).
It will also include the IPv6 datagrams that are
reverse tunneled to a home agent from the mobile
node's home address.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 3 }
mip6HCNodeInPkts 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
datagrams with the Mobility Header or the Home
Address option in the Destination Option extension
header (Next Header value = 60). It will also
include the IPv6 datagrams that are reverse tunneled
to a home agent from the mobile node's home address.
This object is a 64-bit version of mip6NodeInPkts.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 4 }
mip6NodeOutOctets OBJECT-TYPE
SYNTAX Counter32
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 datagrams with the Mobility Header
or the type 2 Routing Header. It will also include
the IPv6 datagrams that are tunneled by a home agent
to the mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 5 }
mip6HCNodeOutOctets 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 datagrams with the Mobility Header
or the type 2 Routing Header. It will also include
the IPv6 datagrams that are tunneled by a home agent
to the mobile node.
This object is a 64-bit version of mip6NodeOutOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 6 }
mip6NodeOutPkts 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
datagrams with the Mobility Header or the type 2
Routing Header. It will also include the IPv6
datagrams that are tunneled by a home agent to the
mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 7 }
mip6HCNodeOutPkts 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
datagrams with the Mobility Header or the type 2
Routing Header. It will also include the IPv6
datagrams that are tunneled by a home agent to the
mobile node.
This object is a 64-bit version of mip6NodeOutOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 8 }
mip6NodeCtrDiscontinuityTime 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.
"
::= { mip6NodeTrafficEntry 9 }
-- mip6MnSystem Group
- mip6MnSystemグループ
mip6MnHomeAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6MnHomeAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing registration status for all the
home addresses pertaining to the mobile node.
"
::= { mip6MnSystem 1 }
mip6MnHomeAddressEntry OBJECT-TYPE SYNTAX Mip6MnHomeAddressEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The registration status for a home address.
mip6MnHomeAddressEntryのOBJECT-TYPE SYNTAX Mip6MnHomeAddressEntry MAX-ACCESSステータス現在の説明「ホームアドレスの登録ステータス。
Implementors need to be aware that if the total
number of octets in mip6MnHomeAddress
exceeds 113, then OIDs of column instances in
this row will have more than 128 sub-identifiers and
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { mip6MnHomeAddressType, mip6MnHomeAddress }
::= { mip6MnHomeAddressTable 1 }
Mip6MnHomeAddressEntry ::=
SEQUENCE {
mip6MnHomeAddressType InetAddressType,
mip6MnHomeAddress InetAddress,
mip6MnHomeAddressState INTEGER
}
mip6MnHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mip6MnHomeAddress that
follows.
"
::= { mip6MnHomeAddressEntry 1 }
mip6MnHomeAddress OBJECT-TYPE SYNTAX InetAddress 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.
mip6MnHomeAddressのOBJECT-TYPE構文InetAddress MAX-ACCESSステータス現在の説明は「モバイル・ノードに割り当てられたユニキャストルーティング可能なアドレス。これは、それに関係なく、移動の変わらないという意味で、移動ノードの 『永久的なアドレス』として使用され添付ファイルのノードの現在のポイント。モバイルノードがまだ割り当てられたホームアドレスを持っていない場合、このオブジェクトは、デフォルトの「不定」の値:: 0になります。
The type of the address represented by this object
is specified by the corresponding
mip6MnHomeAddressType object.
"
REFERENCE
"RFC 3775 : Section 3.2"
::= { mip6MnHomeAddressEntry 2 }
mip6MnHomeAddressState OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
home(2),
registered(3),
pending(4),
isolated(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the state of the mobile node:
unknown -- The state of the mobile node
cannot be determined.
home -- mobile node is on the home network.
registered -- mobile node is on a foreign network
and is registered with the home
agent.
pending -- mobile node has sent registration
request to the home agent and is
waiting for the reply.
isolated -- mobile node is isolated from network,
i.e., it is not in its home network,
it is not registered, and no
registration ack is pending.
"
::= { mip6MnHomeAddressEntry 3 }
-- Mobile Node Discovery and Advertisement Group Counters
- モバイルノードの発見と広告グループカウンタ
mip6MnDiscoveryRequests 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1"
::= { mip6MnConf 1 }
mip6MnDiscoveryReplies 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 re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1"
::= { mip6MnConf 2 }
mip6MnDiscoveryTimeouts 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1, 12"
::= { mip6MnConf 3 }
mip6MnPrefixSolicitationsSent 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.2"
::= { mip6MnConf 4 }
mip6MnPrefixAdvsRecd 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 failed the
validity checks.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.6, 11.4.3"
::= { mip6MnConf 5 }
mip6MnPrefixAdvsIgnored 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.6, 11.4.3"
::= { mip6MnConf 6 }
mip6MnMovedToFN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of times the mobile node has detected
movement to a foreign network from another
foreign network or from the home network, has
reconstructed its care-of address and has initiated
the care-of address registration process.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.5.1"
::= { mip6MnConf 7 }
mip6MnMovedToHN 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.5.4"
::= { mip6MnConf 8 }
-- Mobile Node Registration Group
- モバイルノード登録グループ
-- Registration table of mobile node mip6MnBLTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6MnBLEntry
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 3775 : Section 4.5, 11.1"
::= { mip6MnRegistration 1 }
mip6MnBLEntry OBJECT-TYPE SYNTAX Mip6MnBLEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a Binding Update sent by the mobile node either to its home agent or to one of its correspondent nodes.
そのホームエージェントにまたはその通信相手ノードのいずれかにいずれかのモバイルノードによって送信されたバインディングアップデートについてmip6MnBLEntryのOBJECT-TYPE SYNTAX Mip6MnBLEntry MAX-ACCESSステータス現在の説明は「情報。
Implementors need to be aware that if the total
number of octets in mip6MnHomeAddress and
mip6MnBLNodeAddress exceeds 111, then OIDs of column
instances in this row will have more than 128
sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { mip6MnHomeAddressType,
mip6MnHomeAddress,
mip6MnBLNodeAddressType,
mip6MnBLNodeAddress
}
::= { mip6MnBLTable 1 }
Mip6MnBLEntry ::= SEQUENCE {
mip6MnBLNodeAddressType InetAddressType,
mip6MnBLNodeAddress InetAddress,
mip6MnBLCOAType InetAddressType,
mip6MnBLCOA InetAddress,
mip6MnBLLifeTimeRequested Unsigned32,
mip6MnBLLifeTimeGranted Unsigned32,
mip6MnBLMaxSeq Unsigned32,
mip6MnBLTimeSent DateAndTime,
mip6MnBLAccepted TruthValue,
mip6MnBLAcceptedTime DateAndTime,
mip6MnBLRetransmissions Gauge32,
mip6MnBLDontSendBUFlag TruthValue
}
mip6MnBLNodeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mip6MnBLNodeAddress
that follows.
"
::= { mip6MnBLEntry 1 }
mip6MnBLNodeAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The address of the agent as used in the destination address of the Binding Update. The agent may be a home agent or a correspondent node.
バインディングアップデートの送信先アドレスに使用されるようなmip6MnBLNodeAddressのOBJECT-TYPE構文InetAddress MAX-ACCESSステータス現在の説明は「エージェントのアドレス。エージェントは、ホームエージェントやコレスポンデントノードかもしれません。
The type of the address represented by this object
is specified by the corresponding
mip6MnBLNodeAddressType object.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 2 }
mip6MnBLCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the mip6MnBLCOA that follows.
"
::= { mip6MnBLEntry 3 }
mip6MnBLCOA OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "Care-of address that the mobile node intends to register in the Binding Update request.
mip6MnBLCOAのOBJECT-TYPE構文InetAddress MAX-ACCESS read-onlyステータス現在の説明「気付アドレスモバイルノードは、バインディング更新要求に登録する予定。
The type of the address represented by this object
is specified by the corresponding mip6MnBLCOAType
object.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 4 }
mip6MnBLLifeTimeRequested 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 3775 : Section 11.1"
::= { mip6MnBLEntry 5 }
mip6MnBLLifeTimeGranted 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), mip6MnBLAcceptedTime (aT) and
mip6MnBLLifeTimeGranted (lG) as follows:
lR = lG - (cT - aT).
When lR is zero, this entry will be deleted from the
Binding Update List and consequently from this
table.
"
::= { mip6MnBLEntry 6 }
mip6MnBLMaxSeq OBJECT-TYPE
SYNTAX Unsigned32 (0..65536)
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 3775 : Section 11.1"
::= { mip6MnBLEntry 7 }
mip6MnBLTimeSent OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the last (re-)transmission occurred."
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 8 }
mip6MnBLAccepted 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.
"
::= { mip6MnBLEntry 9 }
mip6MnBLAcceptedTime 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.
"
::= { mip6MnBLEntry 10 }
mip6MnBLRetransmissions OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Binding Update retransmissions.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 11 }
mip6MnBLDontSendBUFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"true(1) indicates that future binding updates
will not be sent to mip6MnBLNodeAddress.
false(2) implies that binding updates will be
sent to mip6MnBLNodeAddress.
The mobile node sets this flag in the when it
receives an ICMP Parameter Problem, Code 1,
error message in response to a return
routability message or Binding Update sent to
mip6MnBLNodeAddress.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 12 }
-- Mobile Node Registration Group Counters
- モバイルノード登録グループカウンタ
mip6MnRegnCounters OBJECT IDENTIFIER ::= { mip6MnRegistration 2 }
mip6MnMobilityMessagesSent 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. There are 3 types of mobility messages, viz.,
Home Test Init, Care-of Test Init, and Binding
Updates, that are sent by mobile nodes.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 4.2, 6.1"
::= { mip6MnRegnCounters 1 }
mip6MnMobilityMessagesRecd 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
Acknowledgment, Binding Refresh Request, and Binding
Error, that are sent to mobile nodes.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 4.2, 6.1"
::= { mip6MnRegnCounters 2 }
mip6MnBUsToHA 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.1"
::= { mip6MnRegnCounters 3 }
mip6MnBUAcksFromHA OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of valid binding acknowledgments
received from the mobile node's home agent(s).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.3"
::= { mip6MnRegnCounters 4 }
mip6MnBUsToCN 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.2"
::= { mip6MnRegnCounters 5 }
mip6MnBUAcksFromCN 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.3"
::= { mip6MnRegnCounters 6 }
mip6MnBindingErrorsFromCN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
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
mip6CounterDiscontinuityTime.
"
::= { mip6MnRegnCounters 7 }
mip6MnICMPErrorsRecd 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 correspondent node in
response to a return routability procedure, a
Binding Update, or a packet with the Home Address
option.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.3.5"
::= { mip6MnRegnCounters 8 }
mip6MnBRRequestsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Refresh requests
received by the mobile node from correspondent
nodes.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.4"
::= { mip6MnRegnCounters 9 }
-- Registration Group counters used for Correspondent Node
mip6CnGlobalStats OBJECT IDENTIFIER ::= { mip6CnStats 1 }
mip6CnHomeTestInitsRecd OBJECT-TYPE
SYNTAX Counter32
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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.4.1"
::= { mip6CnGlobalStats 1 }
mip6CnHomeTestsSent 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.4.3"
::= { mip6CnGlobalStats 2 }
mip6CnCareOfTestInitsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Care-of Test Init messages received.
"
REFERENCE
"RFC 3775 : Section 9.4.2"
::= { mip6CnGlobalStats 3 }
mip6CnCareOfTestsSent 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.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.4.4"
::= { mip6CnGlobalStats 4 }
mip6CnBUsRecd 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1"
::= { mip6CnGlobalStats 5 }
mip6CnBUAcksSent 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.4"
::= { mip6CnGlobalStats 6 }
mip6CnBRsSent 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 as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.5"
::= { mip6CnGlobalStats 7 }
mip6CnBindingErrors 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.3.3"
::= { mip6CnGlobalStats 8 }
mip6CnBUsAccepted 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1, 9.5.4"
::= { mip6CnGlobalStats 9 }
mip6CnBUsRejected 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 greater than or equal to
128. Otherwise the Binding Update request will be
silently discarded.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1, 9.5.4"
::= { mip6CnGlobalStats 10 }
mip6CnReasonUnspecified 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 Acknowledgment message indicating 'reason
unspecified' (Code 128).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8"
::= { mip6CnGlobalStats 11 }
mip6CnInsufficientResource 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 Acknowledgment message indicating
'insufficient resources' (Code 130).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8"
::= { mip6CnGlobalStats 12 }
mip6CnHomeRegnNotSupported OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
correspondent node with status code in the Binding
Acknowledgment message indicating 'home registration
not supported' (Code 131).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6CnGlobalStats 13 }
mip6CnSeqNumberOutOfWindow 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
Acknowledgment message indicating 'sequence number
out of window' (Code 135).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8, 9.5.1"
::= { mip6CnGlobalStats 14 }
mip6CnExpiredHomeNonceIndex 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
Acknowledgment message indicating 'expired home
nonce index' (Code 136).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8, 9.5.1"
::= { mip6CnGlobalStats 15 }
mip6CnExpiredCareOfNonceIndex 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
Acknowledgment message indicating 'expired
care-of nonce index' (Code 137).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8, 9.5.1"
::= { mip6CnGlobalStats 16 }
mip6CnExpiredNonce 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
Acknowledgment message indicating 'expired nonces'
(Code 138), i.e., the correspondent node no longer
recognizes the Home Nonce Index value and the
Care-of Nonce Index value.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8, 9.5.1"
::= { mip6CnGlobalStats 17 }
mip6CnRegTypeChangeDisallowed 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
Acknowledgment message indicating 'registration
type change disallowed' (Code 139), i.e., a binding
already exists for the given home address and the
home registration flag has a different value than
the Home Registration (H) bit in the Binding Update.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8, 9.5.1"
::= { mip6CnGlobalStats 18 }
-- The Correspondent Node statistics by mobile node
- モバイルノードが通信相手ノードの統計情報
mip6CnCounterTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6CnCounterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing each mobile ."
::= { mip6CnStats 2 }
mip6CnCounterEntry OBJECT-TYPE SYNTAX Mip6CnCounterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The set of correspondent node counters for a mobile node.
mip6CnCounterEntryのOBJECT-TYPE SYNTAX Mip6CnCounterEntry MAX-ACCESSステータス現在の説明「モバイルノードのためのコレスポンデントノードのカウンタのセット。
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
}
::= { mip6CnCounterTable 1 }
Mip6CnCounterEntry ::=
SEQUENCE {
mip6CnBURequestsAccepted Counter32,
mip6CnBURequestsRejected Counter32,
mip6CnBCEntryCreationTime DateAndTime,
mip6CnBUAcceptedTime DateAndTime,
mip6CnBURejectionTime DateAndTime,
mip6CnBURejectionCode Mip6BURequestRejectionCode,
mip6CnCtrDiscontinuityTime TimeStamp
}
mip6CnBURequestsAccepted 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 Acknowledgment messages are sent, then
the status code in the message will have a value
less than 128.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CnCtrDiscontinuityTime.
"
::= { mip6CnCounterEntry 1 }
mip6CnBURequestsRejected 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 that have been rejected by the
correspondent node. This includes the Binding Update
requests for which a Binding Acknowledgment message
has been sent with status code value greater than or
equal to 128 and the Binding Acknowledgment requests
that have been silently discarded.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CnCtrDiscontinuityTime.
"
::= { mip6CnCounterEntry 2 }
mip6CnBCEntryCreationTime 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.
"
::= { mip6CnCounterEntry 3 }
mip6CnBUAcceptedTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the last Binding Update was
accepted by the correspondent node and the
corresponding Binding Cache entry was updated.
"
::= { mip6CnCounterEntry 4 }
mip6CnBURejectionTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the last Binding Update message
was rejected by the correspondent node.
If there have been no rejections, then this object
will be inaccessible.
"
::= { mip6CnCounterEntry 5 }
mip6CnBURejectionCode OBJECT-TYPE SYNTAX Mip6BURequestRejectionCode 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 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 3775 : Section 6.1.8"
結合確認をモバイルノードに送信される場合mip6CnBURejectionCode OBJECT-TYPE構文Mip6BURequestRejectionCode MAX-ACCESS read-onlyステータス現在の説明は」、これはバインディング肯定応答で返されたステータスコード（> 128）である。ここで結合確認でありますモバイルノードに送信されていない、これは拒否の理由に該当するステータスコードの値となり、このオブジェクトにアクセスできなくなり、何の拒絶反応がなかった場合は、「REFERENCE」RFC 3775：セクション6.1.8 "
::= { mip6CnCounterEntry 6 }
mip6CnCtrDiscontinuityTime 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 'mip6CnBURequestsAccepted' and
'mip6CnBURequestsRejected', suffered a discontinuity.
If no such discontinuities have occurred since the
last re-initialization of the local management
subsystem, then this object will have a zero value.
"
::= { mip6CnCounterEntry 7 }
-- Home agent group mip6HaAdvsRecd 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.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 7"
::= { mip6HaAdvertisement 1 }
mip6HaAdvsSent 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.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 7"
::= { mip6HaAdvertisement 2 }
mip6HaConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6HaConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing configurable advertisement
parameters for all interfaces on which the
home agent service is advertised.
It is RECOMMENDED that the last written values
of the objects in the conceptual rows of this table will remain unchanged across reboots of
the managed entity provided that the interfaces
have not been renumbered after the reboot.
"
::= { mip6HaAdvertisement 3 }
mip6HaConfEntry OBJECT-TYPE
SYNTAX Mip6HaConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Advertisement parameters for an interface.
The instances of the columnar objects in this entry
pertain to the interface that is uniquely identified
by the ipv6InterfaceIfIndex of the interface. The
same ipv6InterfaceIfIndex object is used to uniquely
identify instances of the columnar objects of this
conceptual row.
"
INDEX { ipv6InterfaceIfIndex }
::= { mip6HaConfTable 1 }
Mip6HaConfEntry ::= SEQUENCE {
mip6HaAdvPreference Integer32,
mip6HaAdvLifetime Integer32,
mip6HaPrefixAdv INTEGER,
mip6HaPrefixSolicitation INTEGER,
mip6HaMCastCtlMsgSupport INTEGER
}
mip6HaAdvPreference 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 3775 : Section 7.4, 8.4"
::= { mip6HaConfEntry 1 }
mip6HaAdvLifetime 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 3775 : Section 7.4"
::= { mip6HaConfEntry 2 }
mip6HaPrefixAdv 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(2), the home agent will not
send ICMP Mobile Prefix Advertisements to the
mobile nodes.
The state can be changed from enabled(1) to
disabled(2) and vice versa by operator
intervention.
Causing the state to change from enabled(1) to
disabled(2) will result in the home agent
disabling the Prefix advertisement function.
On the other hand, changing the status from
disabled(2) to enabled(1) will start the prefix
advertisement function.
"
REFERENCE
"RFC 3775 : Section 8.4"
::= { mip6HaConfEntry 3}
mip6HaPrefixSolicitation 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 it
receives from the mobile nodes. By default, the
value will be set to enabled(1). If it is
disabled(2), the home agent will not respond to
any ICMP Mobile Prefix Solicitation messages.
The state can be changed from enabled(1) to
disabled(2), by operator intervention. Causing
the state to change from enabled(1) to
disabled(2) will result in the home agent not
responding to any ICMP Mobile Prefix
Solicitation messages it receives from the
mobile nodes.
"
REFERENCE
"RFC 3775 : Section 8.4"
::= { mip6HaConfEntry 4}
mip6HaMCastCtlMsgSupport 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 receives
from the mobile nodes. By default, the value
will be set to enabled(1). If it is
disabled(2), the home agent will not process
any multicast group control messages it receives
from the mobile nodes.
The state can be changed from enabled(1) to
disabled(2), by operator intervention. Causing
the state to change from enabled(1) to
disabled(2) will result in the home agent
disabling the processing of the multicast group
control messages it received from the mobile
nodes.
"
REFERENCE
"RFC 3775 : Section 10.4.3"
::= { mip6HaConfEntry 5}
-- Registration Group counters HA
- 登録グループカウンタHA
mip6HaGlobalStats OBJECT IDENTIFIER ::= { mip6HaStats 1 }
mip6HaHomeTestInitsRecd 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 re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 5.2.5"
::= { mip6HaGlobalStats 1 }
mip6HaHomeTestsSent 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 5.2.5"
::= { mip6HaGlobalStats 2 }
mip6HaBUsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Updates received by the
home agent.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 3 }
mip6HaBUAcksSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Acknowledgments sent
by the home agent.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 4 }
mip6HaBRAdviceSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Acknowledgments sent
by the home agent with Binding Refresh Advice
mobility option included.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 5 }
mip6HaBUsAccepted 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
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 6 }
mip6HaPrefDiscoverReqd OBJECT-TYPE -- (Code 1)
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Acknowledgments sent by
the home agent with status code indicating 'accepted
but prefix discovery necessary' (Code 1).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 7 }
mip6HaReasonUnspecified 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
Acknowledgment message indicating 'reason
unspecified' (Code 128).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 8 }
mip6HaAdmProhibited 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
Acknowledgment message indicating 'administratively
prohibited' (Code 129).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 9 }
mip6HaInsufficientResource 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
Acknowledgment message indicating 'insufficient
resources' (Code 130).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.2"
::= { mip6HaGlobalStats 10 }
mip6HaHomeRegnNotSupported 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
Acknowledgment message indicating 'home
registration not supported' (Code 131).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 11 }
mip6HaNotHomeSubnet 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
Acknowledgment message indicating 'not home subnet'
(Code 132).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 12 }
mip6HaNotHomeAgentForThisMN 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
Acknowledgment message indicating 'not home agent
for this mobile node' (Code 133).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.2"
::= { mip6HaGlobalStats 13 }
mip6HaDupAddrDetectionFailed 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
Acknowledgment message indicating 'Duplicate
Address Detection failed' (Code 134).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6HaGlobalStats 14 }
mip6HaSeqNumberOutOfWindow 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
Acknowledgment message indicating 'sequence number
out of window' (Code 135).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1"
::= { mip6HaGlobalStats 15 }
mip6HaExpiredHomeNonceIndex OBJECT-TYPE -- (Code 136)
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
Acknowledgment message indicating 'expired home
nonce index' (Code 136).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1"
::= { mip6HaGlobalStats 16 }
mip6HaRegTypeChangeDisallowed 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
Acknowledgment message indicating 'registration
type change disallowed' (Code 139), i.e., a binding
already exists for the given home address and the
home registration flag has a different value than
the Home Registration (H) bit in the Binding Update.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1"
::= { mip6HaGlobalStats 17 }
-- Home agent registration Counters per node mip6HaCounterTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6HaCounterEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing registration statistics for all
mobile nodes registered with the home agent.
"
::= { mip6HaStats 2 }
mip6HaCounterEntry OBJECT-TYPE SYNTAX Mip6HaCounterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Home agent registration statistics for a mobile node.
モバイルノードのためのmip6HaCounterEntryのOBJECT-TYPE SYNTAX Mip6HaCounterEntry MAX-ACCESSステータス現在の説明は「ホームエージェント登録統計。
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
}
::= { mip6HaCounterTable 1 }
Mip6HaCounterEntry ::= SEQUENCE {
mip6HaBURequestsAccepted Counter32,
mip6HaBURequestsDenied Counter32,
mip6HaBCEntryCreationTime DateAndTime,
mip6HaBUAcceptedTime DateAndTime,
mip6HaBURejectionTime DateAndTime,
mip6HaRecentBURejectionCode Mip6BURequestRejectionCode,
mip6HaCtrDiscontinuityTime TimeStamp
}
mip6HaBURequestsAccepted 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
mip6HaCtrDiscontinuityTime.
"
::= { mip6HaCounterEntry 1 }
mip6HaBURequestsDenied 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
mip6HaCtrDiscontinuityTime.
"
::= { mip6HaCounterEntry 2 }
mip6HaBCEntryCreationTime OBJECT-TYPE
SYNTAX DateAndTime
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the current Binding Cache entry was
created for the mobile node.
"
::= { mip6HaCounterEntry 3 }
mip6HaBUAcceptedTime 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.
"
::= { mip6HaCounterEntry 4 }
mip6HaBURejectionTime 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.
"
::= { mip6HaCounterEntry 5 }
mip6HaRecentBURejectionCode OBJECT-TYPE
SYNTAX Mip6BURequestRejectionCode
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 of the
status code that corresponds to the reason of the
rejection.
If there have been no rejections, then this object
will be inaccessible.
"
::= { mip6HaCounterEntry 6 }
mip6HaCtrDiscontinuityTime 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 'mip6HaBURequestsAccepted' and
'mip6HaBURequestsRejected', suffered a discontinuity.
If no such discontinuities have occurred since the
last re-initialization of the local management
subsystem, then this object will have a zero value.
"
::= { mip6HaCounterEntry 7 }
-- Home Agent List Table mip6HaListTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6HaListEntry
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 3775 : Section 10.1"
::= { mip6HaAdvertisement 4 }
mip6HaListEntry OBJECT-TYPE SYNTAX Mip6HaListEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a router that is offering home agent service. The instances of the columnar objects in this entry pertain to an interface for a particular value of mip6HaLinkLocalAddressType and mip6HaLinkLocalAddress. The interface is uniquely identified by its ipv6InterfaceIfIndex. The same ipv6InterfaceIfIndex object is used in conjunction with the mip6HaLinkLocalAddressType and mip6HaLinkLocalAddress to uniquely identify instances of the columnar objects of this row.
ホーム・エージェント・サービスを提供しているルータについてmip6HaListEntryのOBJECT-TYPE SYNTAX Mip6HaListEntry MAX-ACCESSステータス現在の説明「情報。このエントリ内の円柱状のオブジェクトのインスタンスはmip6HaLinkLocalAddressTypeとmip6HaLinkLocalAddressの特定の値のためのインタフェースに関連ザインタフェースは、一意にipv6InterfaceIfIndexによって識別される。同じipv6InterfaceIfIndexオブジェクトを一意にこの列の円柱状のオブジェクトのインスタンスを識別するためにmip6HaLinkLocalAddressTypeとmip6HaLinkLocalAddressと組み合わせて使用されます。
Implementors need to be aware that if the total
number of octets in mip6HaLinkLocalAddress
exceeds 112, then OIDs of column instances in
this row will have more than 128 sub-identifiers and
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { ipv6InterfaceIfIndex, mip6HaLinkLocalAddressType,
mip6HaLinkLocalAddress }
::= { mip6HaListTable 1 }
Mip6HaListEntry ::= SEQUENCE {
mip6HaLinkLocalAddressType InetAddressType,
mip6HaLinkLocalAddress InetAddress,
mip6HaPreference Integer32,
mip6HaRecvLifeTime Gauge32,
mip6HaRecvTimeStamp DateAndTime
}
mip6HaLinkLocalAddressType OBJECT-TYPE
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 3775 : Section 10.1"
::= { mip6HaListEntry 1 }
mip6HaLinkLocalAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The link local address of the home agent.
mip6HaLinkLocalAddressのOBJECT-TYPE構文InetAddress MAX-ACCESSステータス現在の説明「ホームエージェントのリンクローカルアドレス。
The type of the address represented by this object
is specified by the corresponding
mip6HaLinkLocalAddressType object.
"
REFERENCE
"RFC 3775 : Section 10.1"
::= { mip6HaListEntry 2 }
mip6HaPreference 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 3775 : Section 10.1"
::= { mip6HaListEntry 3 }
mip6HaRecvLifeTime OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime for this home agent.
"
REFERENCE
"RFC 3775 : Section 10.1"
::= { mip6HaListEntry 4 }
mip6HaRecvTimeStamp OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the home agent advertisement was
received.
"
::= { mip6HaListEntry 5 }
-- -- The list of global addresses of a home agent in the -- home agent list --
- - ホームエージェントリスト - ホームエージェントのグローバルアドレスのリスト -
mip6HaGlAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6HaGlAddrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the global addresses of the home
agents in the Home Agents List.
"
REFERENCE
"RFC 3775 : Section 10.1"
::= { mip6HaAdvertisement 5 }
mip6HaGlAddrEntry OBJECT-TYPE SYNTAX Mip6HaGlAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A global address for a home agent in the Home Agents List. The instances of the columnar objects in this entry pertain to an interface for a particular value of mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress and mip6HaGaAddrSeqNo. The mip6HaGaAddrSeqNo object is used to distinguish between multiple instances of the home agent global addresses on the same interface for the same set of mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress, values. There is no upper-bound on the maximum number of global addresses on an interface but, for practical purposes, the upper-bound of the value mip6HaGaAddrSeqNo is set to 1024. The interface is uniquely identified by its ipv6InterfaceIfIndex. The same ipv6InterfaceIfIndex object is used in conjunction with the mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress, and mip6HaGaAddrSeqNo to uniquely identify instances of the columnar objects of this row.
mip6HaGlAddrEntryのOBJECT-TYPE SYNTAX Mip6HaGlAddrEntry MAX-ACCESSステータス現在の説明「ホームエージェントリストにあるホームエージェントのグローバルアドレス。このエントリ内の円柱状のオブジェクトのインスタンスがmip6HaLinkLocalAddressType、mip6HaLinkLocalAddressの特定の値のためのインタフェースに関連しますそしてmip6HaGaAddrSeqNoはmip6HaGaAddrSeqNoオブジェクトはmip6HaLinkLocalAddressType、mip6HaLinkLocalAddress、同じ値のセットに対して同じインタフェース上のホームエージェントのグローバルアドレスの複数のインスタンスを区別するために使用される。あるなし上限インターフェイスにグローバルアドレスの最大数実用的な目的のために、上限値mip6HaGaAddrSeqNoのが1024に設定されているものの、インタフェースは一意にipv6InterfaceIfIndexによって識別される。同じipv6InterfaceIfIndexオブジェクトが一意のインスタンスを識別するためにmip6HaLinkLocalAddressType、mip6HaLinkLocalAddress、及びmip6HaGaAddrSeqNoと組み合わせて使用されの円柱状のオブジェクトこの行。
Implementors need to be aware that if the total
number of octets in mip6HaLinkLocalAddress
exceeds 111, then OIDs of column instances in
this row will have more than 128 sub-identifiers and
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { ipv6InterfaceIfIndex, mip6HaLinkLocalAddressType,
mip6HaLinkLocalAddress, mip6HaGaAddrSeqNo }
::= { mip6HaGlAddrTable 1 }
Mip6HaGlAddrEntry ::= SEQUENCE {
mip6HaGaAddrSeqNo Integer32,
mip6HaGaGlobalAddressType InetAddressType,
mip6HaGaGlobalAddress InetAddress
} mip6HaGaAddrSeqNo OBJECT-TYPE
SYNTAX Integer32 (1..1024)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index that along with ipv6InterfaceIfIndex,
mip6HaLinkLocalAddressType, and
mip6HaLinkLocalAddress uniquely identifies this row.
"
REFERENCE
"RFC 3775 : Section 10.1"
::= { mip6HaGlAddrEntry 1 }
mip6HaGaGlobalAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address type for the global address of the
home agent that follows.
"
::= { mip6HaGlAddrEntry 2 }
mip6HaGaGlobalAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "A global address of the home agent.
mip6HaGaGlobalAddressのOBJECT-TYPE構文InetAddress MAX-ACCESS read-onlyステータス現在の説明「ホームエージェントのグローバルアドレス。
The type of the address represented by this object
is specified by the corresponding
mip6HaGaGlobalAddressType object.
"
::= { mip6HaGlAddrEntry 3 }
-- -- Notifications --
- - お知らせ -
mip6MnRegistered NOTIFICATION-TYPE
OBJECTS {
mip6BindingTimeRegistered,
mip6BindingCOAType,
mip6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent by a home agent when
a mobile node registers with the home agent
for the first time.
Notifications will not be sent for subsequent
updates and/or refreshes.
The MO instances in the notifications will be
identified by the mip6BindingHomeAddressType
and mip6BindingHomeAddress for the mobile node
in the mip6BindingCacheTable.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6Notifications 1 }
mip6MnDeRegistered NOTIFICATION-TYPE
OBJECTS {
mip6BindingTimeRegistered,
mip6BindingCOAType,
mip6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent by a home agent every
time a mobile node de-registers with the home
agent by sending a Binding Update that requests
the home agent to delete a binding.
The MO instances in the notifications will be
identified by the mip6BindingHomeAddressType
and mip6BindingHomeAddress for the mobile node
in the mip6BindingCacheTable.
"
REFERENCE
"RFC 3775 : Section 10.3.2"
::= { mip6Notifications 2 }
mip6MnCOAChanged NOTIFICATION-TYPE
OBJECTS {
mip6BindingTimeRegistered,
mip6BindingCOAType,
mip6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent by a home agent every
time a mobile node sends a Binding Update with
a new care-of address (for an existing Binding
Cache entry).
Notifications will not be sent for subsequent
updates and/or refreshes for the same Care-of
address.
The registration of a new care-of address may
indicate that the mobile node has moved or that
the primary care-of address of the mobile node
has become deprecated.
The MO instances in the notifications will be
identified by the mip6BindingHomeAddressType
and mip6BindingHomeAddress for the mobile node
in the mip6BindingCacheTable.
"
REFERENCE
"RFC 3775 : Section 11.5.2, 11.7.1"
::= { mip6Notifications 3 }
mip6MnBindingExpiredAtHA NOTIFICATION-TYPE
OBJECTS {
mip6BindingTimeRegistered,
mip6BindingCOAType,
mip6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent by a home agent when a
binding for the mobile node at the home agent
expired (no timely Binding Updates were received).
The MO instances in the notifications will be
identified by the mip6BindingHomeAddressType
and mip6BindingHomeAddress for the mobile node
in the mip6BindingCacheTable.
"
REFERENCE
"RFC 3775 : Section 10.3.2"
::= { mip6Notifications 4 }
mip6MnBindingExpiredAtCN NOTIFICATION-TYPE
OBJECTS {
mip6BindingTimeRegistered,
mip6BindingCOAType,
mip6BindingCOA
}
STATUS current
DESCRIPTION
"This notification is sent by a correspondent node
when a binding for the mobile node at the
correspondent node expired (no timely Binding
Updates were received).
The MO instances in the notifications will be
identified by the mip6BindingHomeAddressType
and mip6BindingHomeAddress for the mobile node
in the mip6BindingCacheTable.
"
::= { mip6Notifications 5 }
-- Conformance information
mip6Groups OBJECT IDENTIFIER ::= { mip6Conformance 1 }
mip6Compliances OBJECT IDENTIFIER ::= { mip6Conformance 2 }
-- Units of conformance
mip6SystemGroup OBJECT-GROUP
OBJECTS {
mip6Capabilities,
mip6Status
}
STATUS current
DESCRIPTION
" A collection of objects for basic MIPv6
monitoring."
::= { mip6Groups 1 }
mip6BindingCacheGroup OBJECT-GROUP
OBJECTS {
mip6BindingCOAType,
mip6BindingCOA,
mip6BindingTimeRegistered,
mip6BindingTimeGranted,
mip6BindingTimeRemaining,
mip6BindingMaxSeq,
mip6BindingHomeRegn,
mip6BindingUsageTS,
mip6BindingUsageCount,
mip6BindingAdminStatus
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
Binding Cache.
"
::= { mip6Groups 2 }
mip6BindingHstGroup OBJECT-GROUP
OBJECTS {
mip6BindingHstCOAType,
mip6BindingHstCOA,
mip6BindingHstTimeRegistered,
mip6BindingHstTimeExpired,
mip6BindingHstHomeRegn,
mip6BindingHstUsageTS,
mip6BindingHstUsageCount
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
Binding History. This can be used to monitor
the movement of the mobile node.
"
::= { mip6Groups 3 }
mip6TotalTrafficGroup OBJECT-GROUP
OBJECTS {
mip6InOctets,
mip6HCInOctets,
mip6InPkts,
mip6HCInPkts,
mip6OutOctets,
mip6HCOutOctets,
mip6OutPkts,
mip6HCOutPkts,
mip6CounterDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
total MIPv6 traffic.
"
::= { mip6Groups 4 }
mip6NodeTrafficGroup OBJECT-GROUP
OBJECTS {
mip6NodeInOctets,
mip6HCNodeInOctets,
mip6NodeInPkts,
mip6HCNodeInPkts,
mip6NodeOutOctets,
mip6HCNodeOutOctets,
mip6NodeOutPkts,
mip6HCNodeOutPkts,
mip6NodeCtrDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring the
MIPv6 traffic due to a mobile node.
"
::= { mip6Groups 5 }
mip6MnSystemGroup OBJECT-GROUP
OBJECTS {
mip6MnHomeAddressState
}
STATUS current
DESCRIPTION
" A collection of objects for basic monitoring
of the mobile node.
"
::= { mip6Groups 6 }
mip6MnConfGroup OBJECT-GROUP
OBJECTS {
mip6MnDiscoveryRequests,
mip6MnDiscoveryReplies,
mip6MnDiscoveryTimeouts,
mip6MnPrefixSolicitationsSent,
mip6MnPrefixAdvsRecd,
mip6MnPrefixAdvsIgnored,
mip6MnMovedToFN,
mip6MnMovedToHN
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the advertisement-related info on the
mobile node.
"
::= { mip6Groups 7 }
mip6MnRegistrationGroup OBJECT-GROUP
OBJECTS {
mip6MnBLCOAType,
mip6MnBLCOA,
mip6MnBLLifeTimeRequested,
mip6MnBLLifeTimeGranted,
mip6MnBLMaxSeq,
mip6MnBLTimeSent,
mip6MnBLAccepted,
mip6MnBLAcceptedTime,
mip6MnBLRetransmissions,
mip6MnBLDontSendBUFlag,
--
-- Binding Update List
--
mip6MnMobilityMessagesSent,
mip6MnMobilityMessagesRecd,
mip6MnBUsToHA,
mip6MnBUAcksFromHA,
mip6MnBUsToCN,
mip6MnBUAcksFromCN,
mip6MnBindingErrorsFromCN,
mip6MnICMPErrorsRecd,
mip6MnBRRequestsRecd
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the registration statistics for the mobile node.
"
::= { mip6Groups 8 }
mip6CnStatsGroup OBJECT-GROUP
OBJECTS {
mip6CnBURequestsAccepted,
mip6CnBURequestsRejected,
mip6CnBCEntryCreationTime,
mip6CnBUAcceptedTime,
mip6CnBURejectionTime,
mip6CnBURejectionCode,
mip6CnCtrDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the control messages and corresponding
statistics for each mobile node
communicating with the correspondent
node.
"
::= { mip6Groups 9 }
mip6HaSystemGroup OBJECT-GROUP
OBJECTS {
mip6HaAdvsRecd,
mip6HaAdvsSent,
mip6HaAdvPreference,
mip6HaAdvLifetime,
mip6HaPrefixAdv,
mip6HaPrefixSolicitation,
mip6HaMCastCtlMsgSupport
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the advertisement-related parameters and
statistics for the home agent.
"
::= { mip6Groups 10 }
mip6HaListGroup OBJECT-GROUP
OBJECTS {
mip6HaPreference,
mip6HaRecvLifeTime,
mip6HaRecvTimeStamp,
mip6HaGaGlobalAddressType,
mip6HaGaGlobalAddress
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
the Home Agent List on the home agent.
"
::= { mip6Groups 11 }
mip6HaStatsGroup OBJECT-GROUP OBJECTS { mip6HaBURequestsAccepted, mip6HaBURequestsDenied, mip6HaBCEntryCreationTime, mip6HaBUAcceptedTime, mip6HaBURejectionTime, mip6HaRecentBURejectionCode, mip6HaCtrDiscontinuityTime
mip6HaStatsGroupオブジェクト・グループオブジェクト{mip6HaBURequestsAccepted、mip6HaBURequestsDenied、mip6HaBCEntryCreationTime、mip6HaBUAcceptedTime、mip6HaBURejectionTime、mip6HaRecentBURejectionCode、mip6HaCtrDiscontinuityTime
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
registration-related statistics on the home agent.
"
::= { mip6Groups 12 }
mip6CnGlobalStatsGroup OBJECT-GROUP
OBJECTS {
mip6CnHomeTestInitsRecd,
mip6CnHomeTestsSent,
mip6CnCareOfTestInitsRecd,
mip6CnCareOfTestsSent,
mip6CnBUsRecd,
mip6CnBUAcksSent,
mip6CnBRsSent,
mip6CnBindingErrors,
mip6CnBUsAccepted,
mip6CnBUsRejected,
mip6CnReasonUnspecified,
mip6CnInsufficientResource,
mip6CnHomeRegnNotSupported,
mip6CnSeqNumberOutOfWindow,
mip6CnExpiredHomeNonceIndex,
mip6CnExpiredCareOfNonceIndex,
mip6CnExpiredNonce,
mip6CnRegTypeChangeDisallowed
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
advertisement and registration statistics on
a correspondent node.
"
::= { mip6Groups 13 }
mip6HaGlobalStatsGroup OBJECT-GROUP OBJECTS { mip6HaHomeTestInitsRecd, mip6HaHomeTestsSent, mip6HaBUsRecd, mip6HaBUAcksSent, mip6HaBRAdviceSent, mip6HaBUsAccepted, mip6HaPrefDiscoverReqd, mip6HaReasonUnspecified, mip6HaAdmProhibited, mip6HaInsufficientResource, mip6HaHomeRegnNotSupported, mip6HaNotHomeSubnet, mip6HaNotHomeAgentForThisMN, mip6HaDupAddrDetectionFailed, mip6HaSeqNumberOutOfWindow, mip6HaExpiredHomeNonceIndex, mip6HaRegTypeChangeDisallowed
mip6HaGlobalStatsGroupオブジェクト・グループオブジェクト{mip6HaHomeTestInitsRecd、mip6HaHomeTestsSent、mip6HaBUsRecd、mip6HaBUAcksSent、mip6HaBRAdviceSent、mip6HaBUsAccepted、mip6HaPrefDiscoverReqd、mip6HaReasonUnspecified、mip6HaAdmProhibited、mip6HaInsufficientResource、mip6HaHomeRegnNotSupported、mip6HaNotHomeSubnet、mip6HaNotHomeAgentForThisMN、mip6HaDupAddrDetectionFailed、mip6HaSeqNumberOutOfWindow、mip6HaExpiredHomeNonceIndex、mip6HaRegTypeChangeDisallowed
}
STATUS current
DESCRIPTION
" A collection of objects for monitoring
advertisement and registration statistics on
a home agent.
"
::= { mip6Groups 14 }
mip6BindingCacheCtlGroup OBJECT-GROUP
OBJECTS {
mip6BindingAdminStatus
}
STATUS current
DESCRIPTION
"A collection of objects for controlling the
Binding Cache.
"
::= { mip6Groups 15 }
mip6NotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mip6MnRegistered,
mip6MnDeRegistered,
mip6MnCOAChanged,
mip6MnBindingExpiredAtHA,
mip6MnBindingExpiredAtCN
}
STATUS current
DESCRIPTION
"A collection of notifications from a home agent
or correspondent node to the Manager about the
status of a mobile node.
"
::= { mip6Groups 16 }
-- Compliance statements
- コンプライアンスステートメント
mip6CoreCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB. " MODULE -- this module MANDATORY-GROUPS { mip6SystemGroup }
mip6CoreCompliance MODULE-COMPLIANCEステータス現在の説明 "モバイルIPv6-MIBを実装するSNMPエンティティのための準拠宣言。" MODULE - このモジュールMANDATORY-GROUPS {} mip6SystemGroup
::= { mip6Compliances 1 }
mip6Compliance2 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
that implement the MOBILEIPV6-MIB and support
monitoring of the Binding Cache and the Total
Traffic.
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { mip6SystemGroup,
mip6BindingCacheGroup,
mip6TotalTrafficGroup
}
::= { mip6Compliances 2 }
mip6Compliance3 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the Binding Cache, the Binding History, the total traffic, and the mobile node-wide traffic. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHstHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. -- -- OBJECT mip6BindingHstHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. -- " MODULE -- this module MANDATORY-GROUPS { mip6SystemGroup, mip6BindingCacheGroup, mip6BindingHstGroup, mip6TotalTrafficGroup, mip6NodeTrafficGroup }
mip6Compliance3 MODULE-COMPLIANCEステータス現在の説明モバイルIPv6-MIBを実装し、バインディングキャッシュ、バインディング歴史、総トラフィック、およびモバイルノード全体のトラフィックの監視をサポートするSNMPエンティティのための「準拠宣言。INDEXの数があります。コンプライアンス要件があるが、そのためSMIv2のOBJECT節の形で表現できないオブジェクトは、この説明内のオブジェクト句形式で表現： - オブジェクトmip6BindingHomeAddressType - 構文InetAddressType {IPv6の（2）} - 記述 - mip6BindingHomeAddressのIPv6アドレス - - オブジェクト - このMIBモジュールは、グローバルのサポートを必要とする。 - オブジェクトmip6BindingHomeAddress - 構文InetAddress（SIZE（16）） - 説明 - このMIBモジュールはグローバルのためのサポートを必要とする - のIPv6アドレスオブジェクト - - - オブジェクトmip6BindingHstHomeAddressType - 構文InetAddressType {IPv6の（2）} - 説明 - このMIBモジュールはグローバルのためのサポートが必要 - IPV mip6BindingHomeAddress用mip6BindingHstHomeAddressオブジェクト - 6つのアドレス。 - - オブジェクトmip6BindingHstHomeAddress - 構文InetAddress（SIZE（16）） - 説明 - このMIBモジュールグローバルのためのサポートが必要 - mip6BindingHstHomeAddressオブジェクト - のIPv6アドレス。 - "MODULE - このモジュールMANDATORY-GROUPS {mip6SystemGroup、mip6BindingCacheGroup、mip6BindingHstGroup、mip6TotalTrafficGroup、mip6NodeTrafficGroup}
::= { mip6Compliances 3 }
mip6CoreReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode). " MODULE -- this module MANDATORY-GROUPS { mip6SystemGroup }
mip6CoreReadOnlyCompliance MODULE-COMPLIANCEステータス現在の説明 "読み書き（すなわち、読み取り専用モードで）のためのサポートなしでモバイルIPv6-MIBを実装するSNMPエンティティのための準拠宣言。" MODULE - このモジュールMANDATORY-GROUPS {mip6SystemGroup}
OBJECT mip6Status
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { mip6Compliances 4 }
mip6ReadOnlyCompliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the Binding Cache and Total Traffic. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- " MODULE -- this module
mip6ReadOnlyCompliance2 MODULE-COMPLIANCEステータス現在の説明「読み書きのためのサポートなしでモバイルIPv6-MIBを実装するSNMPエンティティのための準拠宣言（すなわち、読み取り専用モードで）とバインディングキャッシュと総トラフィックの監視をサポートしています。いくつかありますOBJECTのmip6BindingHomeAddressType - - 構文InetAddressType {IPv6の（2）} - DESCRIPTION：SMIv2のOBJECT節の形で表されるが、そのため、コンプライアンス要件が存在することができず、この説明内のオブジェクト句形式で表現インデックスオブジェクトの - mip6BindingHomeAddressのIPv6アドレス - - このMIBモジュールは、グローバルのサポートを必要とするオブジェクト - - オブジェクトmip6BindingHomeAddress - 構文InetAddress（SIZE（16）） - 説明 - このMIBモジュールはグローバルのためのサポートが必要 - mip6BindingHomeAddressのIPv6アドレス - オブジェクト - 。 "MODULE - このモジュール
MANDATORY-GROUPS { mip6SystemGroup,
mip6BindingCacheGroup,
mip6TotalTrafficGroup
}
OBJECT mip6Status
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mip6BindingAdminStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { mip6Compliances 5 }
mip6ReadOnlyCompliance3 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the Binding Cache, the Binding History, the total traffic, and the mobile node-wide traffic. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHstHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. --
mip6ReadOnlyCompliance3 MODULE-COMPLIANCEステータス現在の説明「読み書き（すなわち、読み取り専用モードで）とバインディングキャッシュ、バインディング歴史、総トラフィックの監視のサポートのためのサポートなしでモバイルIPv6-MIBを実装するSNMPエンティティのための準拠宣言。、モバイルノード全体のトラフィックSMIv2のOBJECT節の形で表すことができないインデックスオブジェクトの数があるが、そのためのコンプライアンス要件があり、この説明内のオブジェクト句形式で表現： - オブジェクトmip6BindingHomeAddressType - 構文InetAddressType {IPv6の（2）} - DESCRIPTION - mip6BindingHomeAddressのIPv6アドレス - - オブジェクト - このMIBモジュールは、グローバルのサポートを必要とする。 - オブジェクトmip6BindingHomeAddress - 構文InetAddress（SIZE（16）） - - DESCRIPTION - mip6BindingHomeAddressのIPv6アドレス - - オブジェクト - このMIBモジュールはグローバルのサポートを必要とする。 - オブジェクトmip6BindingHstHomeAddressType - 構文InetAddressType {IPv6の（2）} - DESCRIPTION - mip6BindingHstHomeAddressオブジェクト - のIPv6アドレス - このMIBモジュールは、グローバルのサポートが必要です。 -
-- OBJECT mip6BindingHstHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the
-- mip6BindingHstHomeAddress object.
--
"
MODULE -- this module
MANDATORY-GROUPS { mip6SystemGroup,
mip6BindingCacheGroup,
mip6BindingHstGroup,
mip6TotalTrafficGroup,
mip6NodeTrafficGroup
}
OBJECT mip6Status
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mip6BindingAdminStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { mip6Compliances 6 }
mip6MnCoreCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic mobile node functionality. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global
mip6MnCoreCompliance MODULE-COMPLIANCEステータス現在の説明「モバイルIPv6-MIB、および基本的なモバイルノード機能のサポートの監視を実装するSNMPエンティティのための準拠宣言は、SMIv2のOBJECT節の形で表現することはできませんINDEXオブジェクトの数がありますしかしそのため、コンプライアンス要件があり、この説明内のオブジェクト句形式で表現： - オブジェクトmip6MnHomeAddressType - 構文InetAddressType {IPv6の（2）} - DESCRIPTION - mip6MnHomeAddressのIPv6アドレス - このMIBモジュールはグローバルのサポートを必要と - オブジェクト - - オブジェクトmip6MnHomeAddress - 構文InetAddress（SIZE（16）） - 説明 - このMIBモジュールはグローバルのサポートを必要と
-- ipv6 addresses for the mip6MnHomeAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { mip6MnSystemGroup
}
::= { mip6Compliances 7 }
mip6MnCompliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the mobile node functionality specifically the Discovery- and Registration-related statistics, There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnBLNodeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnBLNodeAddress -- object. -- -- OBJECT mip6MnBLNodeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnBLNodeAddress -- object.
mip6MnCompliance2 MODULE-COMPLIANCEステータス現在の説明「モバイルIPv6-MIBを実装し、モバイルノードの機能、特にディスカバリーと登録関連の統計の監視をサポートするSNMPエンティティのための準拠宣言、で表現できないINDEXオブジェクトの数があります。 SMIv2のOBJECT節の形が、対象のコンプライアンス要件があるが、この説明内のオブジェクト句形式で表現： - オブジェクトmip6MnHomeAddressType - 構文InetAddressType {IPv6の（2）} - 説明 - このMIBモジュールがサポートを必要としますグローバル - mip6MnHomeAddressのIPv6アドレス - オブジェクト - - オブジェクトmip6MnHomeAddress - 構文InetAddress（SIZE（16）） - DESCRIPTION - mip6MnHomeAddressのIPv6アドレス - - このMIBモジュールはグローバルのサポートを必要とする対象。 - - オブジェクトmip6MnBLNodeAddressType - 構文InetAddressType {IPv6の（2）} - 説明 - このMIBモジュールはグローバルのためのサポートが必要 - MIのIPv6アドレスp6MnBLNodeAddress - オブジェクト。 - - オブジェクトmip6MnBLNodeAddress - 構文InetAddress（SIZE（16）） - 説明 - このMIBモジュールグローバルのためのサポートが必要 - mip6MnBLNodeAddressのIPv6アドレス - オブジェクト。
--
"
MODULE -- this module
MANDATORY-GROUPS { mip6MnSystemGroup,
mip6MnConfGroup,
mip6MnRegistrationGroup,
mip6TotalTrafficGroup
}
::= { mip6Compliances 8 }
mip6CnCoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
that implement the MOBILEIPV6-MIB and
support monitoring of the basic correspondent node
functionality.
"
MODULE -- this module
MANDATORY-GROUPS { mip6CnGlobalStatsGroup,
mip6TotalTrafficGroup
}
::= { mip6Compliances 9 }
mip6CnCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic correspondent node functionality. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object.
mip6CnCompliance MODULE-COMPLIANCEステータス現在の説明「モバイルIPv6-MIB、および基本的な対応ノード機能のサポートの監視を実装するSNMPエンティティのための準拠宣言は、SMIv2のOBJECT節の形で表現することはできませんINDEXオブジェクトの数がありますしかしそのため、コンプライアンス要件があり、この説明内のオブジェクト句形式で表現： - オブジェクトmip6BindingHomeAddressType - 構文InetAddressType {IPv6の（2）} - DESCRIPTION - mip6BindingHomeAddressのIPv6アドレス - このMIBモジュールはグローバルのサポートを必要と - オブジェクト - - オブジェクトmip6BindingHomeAddress - 構文InetAddress（SIZE（16）） - DESCRIPTION - mip6BindingHomeAddressのIPv6アドレス - - オブジェクトこのMIBモジュールは、グローバルのサポートを必要とします。
"
MODULE -- this module
MANDATORY-GROUPS { mip6CnGlobalStatsGroup,
mip6CnStatsGroup,
mip6TotalTrafficGroup
}
::= { mip6Compliances 10 }
mip6HaCoreCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities
that implement the MOBILEIPV6-MIB and
support monitoring of the basic home agent
functionality.
"
MODULE -- this module
MANDATORY-GROUPS { mip6HaSystemGroup
}
::= { mip6Compliances 11 }
mip6HaCompliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics, There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType
mip6HaCompliance2 MODULE-COMPLIANCEステータス現在の説明「モバイルIPv6-MIBを実装し、ホームエージェント機能、特にホームエージェントリストとホームエージェント登録関連の統計の監視をサポートするSNMPエンティティのための準拠宣言、INDEXの数があります。コンプライアンス要件があるが、そのためSMIv2のOBJECT節の形で表現できないオブジェクトは、この説明内のオブジェクト句形式で表現： - オブジェクトmip6BindingHomeAddressType - 構文InetAddressType {IPv6の（2）} - 記述 - mip6BindingHomeAddressのIPv6アドレス - - オブジェクト - このMIBモジュールは、グローバルのサポートを必要とする。 - オブジェクトmip6BindingHomeAddress - 構文InetAddress（SIZE（16）） - 説明 - このMIBモジュールはグローバルのためのサポートを必要とする - のIPv6アドレスオブジェクト - - 。 - オブジェクトmip6HaLinkLocalAddressType mip6BindingHomeAddressについて
-- SYNTAX InetAddressType { ipv6z(4) }
-- DESCRIPTION
-- This MIB module requires support for local
-- ipv6 addresses for the mip6HaLinkLocalAddress
-- object.
--
-- OBJECT mip6HaLinkLocalAddress
-- SYNTAX InetAddress (SIZE(20))
-- DESCRIPTION
-- This MIB module requires support for local
-- ipv6 addresses for the mip6HaLinkLocalAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { mip6HaSystemGroup,
mip6HaListGroup,
mip6HaStatsGroup,
mip6HaGlobalStatsGroup,
mip6TotalTrafficGroup
}
::= { mip6Compliances 12 }
mip6HaCompliance3 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring and control of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics,
mip6HaCompliance3 MODULE-COMPLIANCEステータス現在の説明「特異的にホームエージェントリストとホームエージェント登録関連の統計をモバイルIPv6-MIBを実装し、ホームエージェント機能の監視と制御をサポートするSNMPエンティティのための準拠宣言、
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6HaLinkLocalAddressType
-- SYNTAX InetAddressType { ipv6z(4) }
-- DESCRIPTION
-- This MIB module requires support for local
-- ipv6 addresses for the mip6HaLinkLocalAddress
-- object.
--
-- OBJECT mip6HaLinkLocalAddress
-- SYNTAX InetAddress (SIZE(20))
-- DESCRIPTION
-- This MIB module requires support for local
-- ipv6 addresses for the mip6HaLinkLocalAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { mip6HaSystemGroup,
mip6HaListGroup,
mip6HaStatsGroup,
mip6HaGlobalStatsGroup,
mip6BindingCacheCtlGroup,
mip6TotalTrafficGroup
}
::= { mip6Compliances 13 }
mip6HaCoreReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the basic home agent functionality. " MODULE -- this module MANDATORY-GROUPS { mip6HaSystemGroup } OBJECT mip6HaAdvPreference MIN-ACCESS read-only DESCRIPTION "Write access is not required."
mip6HaCoreReadOnlyCompliance MODULE-COMPLIANCEステータス現在の説明「読み書きのためのサポートなしでモバイルIPv6-MIBを実装するSNMPエンティティのための準拠宣言（すなわち、読み取り専用モードで）と基本的なホームエージェント機能のモニタリングをサポートしています。」MODULE - このモジュールMANDATORY-GROUPS {mip6HaSystemGroup} OBJECT mip6HaAdvPreference MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされません。"
OBJECT mip6HaAdvLifetime
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mip6HaPrefixAdv MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaPrefixAdv MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaPrefixSolicitation MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaPrefixSolicitation MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaMCastCtlMsgSupport MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaMCastCtlMsgSupport MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
::= { mip6Compliances 14 }
mip6HaReadOnlyCompliance2 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics.
mip6HaReadOnlyCompliance2 MODULE-COMPLIANCEステータス現在の説明「読み書きのためのサポートなしでモバイルIPv6-MIBを実装するSNMPエンティティのための準拠宣言（すなわち、読み取り専用モードで）とホームエージェント機能の監視をサポートすることは、特にホームエージェントリストとホームエージェント登録関連の統計。
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6HaLinkLocalAddressType
-- SYNTAX InetAddressType { ipv6z(4) }
-- DESCRIPTION
-- This MIB module requires support for local
-- ipv6 addresses for the mip6HaLinkLocalAddress
-- object.
--
-- OBJECT mip6HaLinkLocalAddress
-- SYNTAX InetAddress (SIZE(20))
-- DESCRIPTION
-- This MIB module requires support for local
-- ipv6 addresses for the mip6HaLinkLocalAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { mip6HaSystemGroup,
mip6HaListGroup,
mip6HaStatsGroup,
mip6HaGlobalStatsGroup, mip6TotalTrafficGroup
}
OBJECT mip6HaAdvPreference MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaAdvPreference MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaAdvLifetime MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaAdvLifetime MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaPrefixAdv MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaPrefixAdv MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaPrefixSolicitation MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaPrefixSolicitation MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaMCastCtlMsgSupport MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaMCastCtlMsgSupport MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
::= { mip6Compliances 15 }
mip6HaReadOnlyCompliance3 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring and control of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics,
mip6HaReadOnlyCompliance3 MODULE-COMPLIANCEステータス現在の説明「読み書きのためのサポートなしでモバイルIPv6-MIBを実装するSNMPエンティティのための準拠宣言（すなわち、読み取り専用モードで）とホームエージェント機能の監視と制御をサポートし、特にホームエージェントリストそして、ホームエージェント登録関連の統計、
There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2,
but for which there are compliance requirements,
expressed in OBJECT clause form in this description:
-- OBJECT mip6BindingHomeAddressType
-- SYNTAX InetAddressType { ipv6(2) }
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6BindingHomeAddress
-- SYNTAX InetAddress (SIZE(16))
-- DESCRIPTION
-- This MIB module requires support for global
-- ipv6 addresses for the mip6BindingHomeAddress
-- object.
--
-- OBJECT mip6HaLinkLocalAddressType
-- SYNTAX InetAddressType { ipv6z(4) }
-- DESCRIPTION
-- This MIB module requires support for local
-- ipv6 addresses for the mip6HaLinkLocalAddress
-- object.
--
-- OBJECT mip6HaLinkLocalAddress
-- SYNTAX InetAddress (SIZE(20))
-- DESCRIPTION
-- This MIB module requires support for local
-- ipv6 addresses for the mip6HaLinkLocalAddress
-- object.
--
"
MODULE -- this module
MANDATORY-GROUPS { mip6HaSystemGroup,
mip6HaListGroup,
mip6HaStatsGroup,
mip6HaGlobalStatsGroup, mip6BindingCacheCtlGroup,
mip6TotalTrafficGroup
}
OBJECT mip6HaAdvPreference MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaAdvPreference MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaAdvLifetime MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaAdvLifetime MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaPrefixAdv MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaPrefixAdv MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaPrefixSolicitation MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaPrefixSolicitation MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6HaMCastCtlMsgSupport MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6HaMCastCtlMsgSupport MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
OBJECT mip6BindingAdminStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
OBJECT mip6BindingAdminStatus MIN-ACCESS読み取り専用説明 "書き込みアクセスが必要とされていません。"
::= { mip6Compliances 16 }
mip6NotificationCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support Notification from home agent or correspondent node to management stations about the mobile node status. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description:
mip6NotificationCompliance MODULE-COMPLIANCEステータス現在の説明「モバイルノードのステータスに関する管理ステーションにホームエージェントやコレスポンデントノードからモバイルIPv6-MIBおよびサポートの通知を実装するSNMPエンティティのための準拠宣言。で表現することはできませんINDEXオブジェクトの数があります。 SMIv2のOBJECT節の形が、そのためにコンプライアンス要件があるが、この説明ではOBJECT節の形で表現しました：
-- 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 { mip6NotificationGroup
}
::= { mip6Compliances 17 }
END
終わり
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 the corresponding sensitivity/vulnerability:
読み書きのMAX-ACCESS節でこのMIBモジュールで定義された管理オブジェクトの数があります。そのようなオブジェクトは、いくつかのネットワーク環境に敏感又は脆弱と考えることができます。適切な保護のない非安全な環境におけるSET操作のサポートはネットワーク操作のときにマイナスの影響を与える可能性があります。これらは、テーブルとオブジェクトおよび対応する感度/脆弱性です：
mip6Status: The 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.
mip6HaAdvPreference: Access to this object may be abused to
force MNs into selecting the wrong HA.
mip6HaAdvLifetime: 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.
mip6BindingAdminStatus: The value of this object is used to
control the status of a Binding Cache entry.
Access to this object may be abused to deny Mobile
IPv6 connectivity to a legitimate user or to
grant Mobile IPv6 connectivity to an illegal user.
mip6HaPrefixAdv: The value of this object indicates whether
the home agent will send ICMP Mobile Prefix
Advertisements to the mobile node.
Access to this object may be abused to send
unwanted/wrong prefix information or to deny the
mobile node from receiving information about the
changes in the home prefixes.
This may result in disruption of the Mobile IPv6
connectivity.
mip6HaPrefixSolicitation: The value of this object indicates
whether the home agent should respond to ICMP
Mobile Prefix Solicitation messages from a mobile
node. Access to this object may be abused to deny
the mobile node information about its home prefix.
This may result in disruption of the Mobile IPv6
connectivity.
mip6HaMCastCtlMsgSupport: The value of this object decides
whether the home agent should process the
multicast group membership control messages it
receives from mobile nodes. Access to this object
may be used to subvert administrate policy on
multicasting or to disrupt the multicast
communication with the mobile node.
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:
このMIBモジュールで読み取り可能なオブジェクトの一部（すなわち、アクセス可能ではない以外MAX-ACCESS持つオブジェクト）は、いくつかのネットワーク環境に敏感又は脆弱と考えることができます。 GETおよび/またはこれらのオブジェクトへのアクセスを通知し、おそらくSNMPを通してネットワークの上にそれらを送信する場合でも、これらのオブジェクトの値を暗号化するためにも、制御することが重要です。これらは、テーブルと、オブジェクトとそれらの感度/脆弱性です：
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. mip6BindingHstCOAType mip6BindingHstCOA mip6MnBLCOAType mip6MnBLCOA
このMIBのアドレスに関連するオブジェクトは、特に感受性および/またはプライベートであると考えることができます。気付アドレスに関連するオブジェクトは、モバイルノードの位置と動きを明らかにする。この情報は、プライベートと敏感であると考えられてもよいし、慎重に扱わなければなりません。 mip6BindingHstCOAType mip6BindingHstCOA mip6MnBLCOAType mip6MnBLCOA
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. mip6BindingHstHomeAddressType, mip6BindingHstHomeAddress, mip6MnHomeAddressType, mip6MnHomeAddress
モバイルノードのホーム・アドレス - とホームエージェントに関連する情報は、これらは、モバイルノードの通信チャネルを破壊する方法で悪質なパーティへの手がかりを提供することができるよう、あまりにも敏感であるとみなすことができます。 mip6BindingHstHomeAddressType、mip6BindingHstHomeAddress、mip6MnHomeAddressType、mip6MnHomeAddress
The correspondent node's address-related MOs will reveal the nodes with whom the mobile node is corresponding. This information may be considered private and sensitive. mip6MnBLNodeAddressType, mip6MnBLNodeAddress
コレスポンデントノードのアドレスに関連するMOは、モバイルノードが対応している誰とノードを明らかにします。この情報は、プライベートで機密と見なすことができます。 mip6MnBLNodeAddressType、mip6MnBLNodeAddress
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.
SNMPv3の前のSNMPバージョンは十分なセキュリティを含んでいませんでした。ネットワーク自体が（IPSecを使用することにより、例えば）安全であっても、その後も、安全なネットワーク上で/ SETにアクセスし、GETだれに許容されているかのように何の制御（読み取り/変更/作成/削除）この内のオブジェクトが存在しませんMIBモジュール。
It is RECOMMENDED that implementors 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).
実装がSNMPv3フレームワークで提供するようにセキュリティ機能を考えることが推奨される（認証とプライバシーのために）SNMPv3の暗号化メカニズムの完全なサポートを含む、（[RFC3410]セクション8を参照）。
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.
さらに、SNMPv3の前のSNMPバージョンの展開はお勧めしません。代わりに、SNMPv3を展開すると、暗号化セキュリティを有効にすることをお勧めします。このMIBモジュールのインスタンスへのアクセスを与えるSNMP実体が適切にのみプリンシパル（ユーザ）にオブジェクトへのアクセスを提供するように設定されていることを確認するために、顧客/オペレータ責任実際にGETまたはSET（変化への正当な権利を有することです/）/削除、それらを作成します。
IANA has assigned a base arc in the 'mib-2' (standards track) OID tree for the 'mip6MIB' MODULE-IDENTITY defined in the Mobile-IPv6 MIB. The mib-2 number is 133 for mip6MIB.
IANAは、モバイルIPv6のMIBで定義された「mip6MIB」MODULE-IDENTITYは「MIB-2」（標準化過程）OIDツリー内のベースアークを割り当てました。 MIB-2数はmip6MIB 133です。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]ブラドナーの、S.、 "要件レベルを示すためにRFCsにおける使用のためのキーワード"、BCP 14、RFC 2119、1997年3月。
[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.
[RFC2578] McCloghrie、K.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、M.、およびS. Waldbusser、 "経営情報バージョン2（SMIv2）の構造"、STD 58、RFC 2578 、1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579] McCloghrie、K.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、M.、およびS. Waldbusser、 "SMIv2のためのテキストの表記法"、STD 58、RFC 2579、1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580] McCloghrie、K.、パーキンス、D.、Schoenwaelder、J.、ケース、J.、ローズ、M.、およびS. Waldbusser、 "SMIv2のための適合性宣言"、STD 58、RFC 2580、1999年4月。
[RFC3775] Johnson, D., Perkins, C., and Arkko J., Mobility Support in IPv6" RFC 3775, June 2004.
[RFC3775]ジョンソン、D.、パーキンス、C.、およびArkko J.、IPv6" におけるモビリティサポートRFC 3775、2004年6月。
[RFC4293] Routhier, S., Ed., "Management Information Base for the Internet Protocol (IP)", RFC 4293, April 2006.
[RFC4293] Routhier、S.、エド。、 "インターネットプロトコル（IP）のための管理情報ベース"、RFC 4293、2006年4月。
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.
[RFC4001]ダニエル、M.、ハーバーマン、B.、Routhier、S.、およびJ. Schoenwaelder、 "インターネットネットワークアドレスのためのテキストの表記法"、RFC 4001、2005年2月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]ケース、J.、マンディ、R.、パーテイン、D.、およびB.スチュワート、 "インターネット標準の管理フレームワークのための序論と適用性声明"、RFC 3410、2002年12月。
[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, June 2005.
[RFC4087]ターラー、D.、 "IPトンネルMIB"、RFC 4087、2005年6月。
The following groups and individuals have contributed to this document with discussions and comments:
次のグループや個人が議論とコメントし、この文書に貢献しています：
WIDE-netman group
C.M. Heard
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
電話：+ 81-22-303-4012 Eメール：glenn@cysols.com
Kenichi Nagami INTEC NetCore Inc. 1-3-3, Shin-suna Koto-ku, Tokyo, 135-0075 Japan
けにち ながみ いんてＣ ねｔこれ いんｃ。 １ー３ー３、 しんーすな ことーく、 ときょ、 １３５ー００７５ じゃぱん
Phone: +81-3-5665-5069 EMail: nagami@inetcore.com
電話：+ 81-3-5665-5069 Eメール：nagami@inetcore.com
Kazuhide Koide Tohoku University 2-1-1, Katahira Aoba-ku, Sendai, 980-8577 Japan
かずひで こいで とほく うにゔぇｒしｔｙ ２ー１ー１、 かたひら あおばーく、 せんだい、 ９８０ー８５７７ じゃぱん
Phone: +81-22-217-5454 EMail: koide@shiratori.riec.tohoku.ac.jp
電話：+ 81-22-217-5454 Eメール：koide@shiratori.riec.tohoku.ac.jp
Sri Gundavelli Cisco Systems 170 W.Tasman Drive, San Jose, CA 95134 USA
スリGundavelliシスコシステムズ170 W.Tasmanドライブ、サンノゼ、CA 95134 USA
Phone: +1-408-527-6109 EMail: sgundave@cisco.com
電話：+ 1-408-527-6109 Eメール：sgundave@cisco.com
Full Copyright Statement
完全な著作権声明
Copyright (C) The Internet Society (2006).
著作権（C）インターネット協会（2006）。
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.
この文書では、BCP 78に含まれる権利と許可と制限の適用を受けており、その中の記載を除いて、作者は彼らのすべての権利を保有します。
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 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.
この文書とここに含まれている情報は、基礎とCONTRIBUTOR「そのまま」、ORGANIZATION HE / SHEが表すまたはインターネットソサエティおよびインターネット・エンジニアリング・タスク・フォース放棄すべての保証、明示または、（もしあれば）後援ISに設けられています。黙示、情報の利用は、特定の目的に対する権利または商品性または適合性の黙示の保証を侵害しない任意の保証含むがこれらに限定されません。
Intellectual Property
知的財産
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.
IETFは、本書またはそのような権限下で、ライセンスがたりないかもしれない程度に記載された技術の実装や使用に関係すると主張される可能性があります任意の知的財産権やその他の権利の有効性または範囲に関していかなる位置を取りません利用可能です。またそれは、それがどのような権利を確認する独自の取り組みを行ったことを示すものでもありません。 RFC文書の権利に関する手続きの情報は、BCP 78および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.
IPRの開示のコピーが利用できるようにIETF事務局とライセンスの保証に行われた、または本仕様の実装者または利用者がそのような所有権の使用のための一般的なライセンスまたは許可を取得するために作られた試みの結果を得ることができますhttp://www.ietf.org/iprのIETFのオンライン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.
IETFは、その注意にこの標準を実装するために必要とされる技術をカバーすることができる任意の著作権、特許または特許出願、またはその他の所有権を持ってすべての利害関係者を招待します。 ietf-ipr@ietf.orgのIETFに情報を記述してください。
Acknowledgement
謝辞
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFCエディタ機能のための資金は、IETF管理サポート活動（IASA）によって提供されます。