idnits 2.17.1 draft-ietf-mip6-mipv6-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 3538. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3549. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3556. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3562. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 3530), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 43. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 80 longer pages, the longest (page 2) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 506 instances of too long lines in the document, the longest one being 16 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 148 has weird spacing: '...mple as possi...' == Line 431 has weird spacing: '...essType of th...' == Line 625 has weird spacing: '...essType of th...' == Line 1147 has weird spacing: '...essType of th...' == Line 1200 has weird spacing: '...equests sent ...' == (2 more instances...) == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 19, 2004) is 7220 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'MIPv6' is mentioned on line 114, but not defined == Missing Reference: 'RFC2119' is mentioned on line 120, but not defined == Unused Reference: 'RFC3775' is defined on line 3450, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 3455, but no explicit reference was found in the text == Unused Reference: 'RFC2571' is defined on line 3459, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 3463, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 3467, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 3470, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 3474, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Downref: Normative reference to an Informational RFC: RFC 3410 Summary: 19 errors (**), 0 flaws (~~), 19 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Mip6 Working Group Glenn M. Keeni 2 INTERNET-DRAFT Cyber Solutions Inc. 3 Expires: January 18, 2005 Kazuhide Koide 4 Tohoku University 5 Kenichi Nagami 6 INTEC NetCore Inc. 7 Sri Gundavelli 8 Cisco Systems Inc. 9 July 19, 2004 11 A Management Information Base for Mobile IPv6 12 14 Status of this Memo 16 By submitting this Internet-Draft, we certify that any applicable 17 patent or other IPR claims of which we are aware have been disclosed, or 18 will be disclosed, and any of which we become aware will be disclosed, 19 in accordance with RFC 3668. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that other 23 groups may also distribute working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than a "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html" 36 This document is a product of the mip6 Working Group. Comments should 37 be addressed to the authors or the mailing list at mip6@ietf.org 39 This Internet-Draft will expire on January 18, 2005. 41 Copyright Notice 43 Copyright (C) The Internet Society (2004). All Rights Reserved. 45 Abstract 47 This memo defines a portion of the Management Information Base (MIB), 48 the Mobile-IPv6 MIB , for use with network management protocols 49 in the Internet community. In particular, the Mobile-IPv6 MIB will be 50 used to monitor and control the mobile node, home agent and 51 correspondent node functions of a Mobile IPv6 (MIPv6) entity. 53 Table of Contents 55 1. The Internet-Standard Management Framework .................... 3 56 2. Overview ...................................................... 3 57 3. Mobile IPv6 Monitoring and Control Requirements ............... 4 58 4. MIB Design .................................................... 5 59 5. The Mobile-IPv6 MIB ........................................... 7 60 6. Security Considerations .......................................74 61 7. IANA Considerations ...........................................75 62 8. References ....................................................76 63 9. Acknowledgments ...............................................77 64 10. Authors' Addresses ............................................78 65 11. Full Copyright Statement ......................................79 66 Appendix: History of Changes 68 1. The Internet-Standard Management Framework 70 For a detailed overview of the documents that describe the current 71 Internet-Standard Management Framework, please refer to section 7 of 72 RFC 3410 [RFC3410]. 74 Managed objects are accessed via a virtual information store, termed 75 the Management Information Base or MIB. MIB objects are generally 76 accessed through the Simple Network Management Protocol (SNMP). 78 Objects in the MIB are defined using the mechanisms defined in the 79 Structure of Management Information (SMI). This memo specifies a MIB 80 module that is compliant to the SMIv2, which is described in STD 58, 81 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 82 [RFC2580]. 84 2. Overview 86 2.1 The Mobile IPv6 Protocol entities. 88 Mobile IPv6 (MIPv6) [MIPv6] specifies a protocol which allows nodes 89 to remain reachable while moving around in the IPv6 Internet. An 90 entity which implements the MIPv6 protocol is an MIPv6 entity. There 91 are three types of entities envisaged by the MIPv6 protocol. 93 mobile node (MN): A node that can change its point of attachment 94 from one link to another, while still being reachable via its home 95 address. 97 correspondent node (CN): A peer node with which a mobile node is 98 communicating. The correspondent node may be either mobile or 99 stationary. [Note that a corespondent node does not necessarily 100 require MIPv6 support.] 102 home agent (HA): A router on a mobile node's home link with which 103 the mobile node has registered its current care-of address. While 104 the mobile node is away from home, the home agent intercepts 105 packets on the home link destined to the mobile node's home address, 106 encapsulates them, and routes them to the mobile node's registered 107 care-of address. 109 This document defines the managed objects that will be required to 110 monitor and control MIPv6 entities. 112 2.2 Terminology. 113 The terminolgy used in this document is consistent with the 114 definitions used in Mobile IPv6 protocol specification[MIPv6]. 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in BCP 14, RFC 2119 119 [RFC2119]. 121 3. Mobile IPv6 Monitoring and Control Requirements 123 For managing a MIPv6 entity it is necessary to monitor 124 the following 125 o capabilities of MIPv6 entities 126 o traffic due to MIPv6 127 o binding related statistics (at HA, CN, MN ) 128 o binding details (at HA, CN) 129 o history of Binding Updates (at HA, CN, MN) 131 The MIPv6 protocol document stipulates that several MIPv6 related 132 parameters should be manually configurable. The MIPv6 MIB should 133 define managed objects that can be used to configure the related 134 parameters e.g. 135 o the preference value the home agent will use in Router 136 Advertisements, 137 o the lifetime value the home agent will use in Router 138 Advertisements, 139 o whether a home agent will send ICMP Mobile Prefix 140 Advertisements to mobile nodes, 141 o whether a home agent will respond to ICMP Mobile Prefix 142 Solicitation messages from mobile nodes and, 143 o whether a home agent will process multicast group membership 144 control messages from mobile nodes. 146 4. MIB Design. 148 The basic principle has been to keep the MIB as simple as possible 149 and at the same time to make it effective enough so that the 150 essential needs of monitoring and control are met. It is envisaged 151 that wherever possible existing MIBS will be used (e.g. IPSec MIB, 152 Neighbour Discovery MIB, Tunnel MIB.) for monitor and control of 153 MIPv6 entities. 155 The Mobile-IPv6 MIB comprises of following sets of groups 156 - mip6IP: a generic group containing objects that are common 157 to all the Mobile IPv6 entities. 158 - mip6Ha: this group models the home agent service. It 159 comprises of objects specific to the services and associated 160 advertisement parameters offerred by the home agent on each 161 of its links. It also contains objects pertaining to the 162 maintenance of the home agent list on each of the links on 163 which the service is offered. 164 - mip6Mn: this group models the mobile node service. It 165 comprises of objects specific to the Dynamic Home Agent 166 discovery function and related parameters. It also contains 167 objects that record the movement of the mobile node. 168 - mip6Cn: models the correspondent node and is primarily 169 scoped to its participation in the Return Routability 170 procedure for achieving Route Optimization triggered by 171 the mobile node. 172 - mip6Notifications: defines the set of notifications that 173 will be used to asynchronously monitor the Mobile IPv6 174 entities. 176 The tables contained in the above groups are as follows- 177 mip6BindingCacheTable : models the binding cache on the home agent 178 and correspondent node. It contains details 179 of the Binding Update requests that have been 180 received and accepted. 181 mip6BindingHistoryTable : tracks the history of the binding cache. 182 mip6NodeTrafficTable : the mobile node-wise traffic counters. 183 mip6MnHomeAddressTable : contains all the home addresses 184 pertaining to the mobile node and 185 the corresponding registration status. 186 mip6MnBLTable : models the Binding Update List on the 187 mobile node. It contains information 188 about the registration requests sent 189 by the mobile node and the corresponding 190 results. 191 mip6CnCounterTable : contains the mobile node-wise 192 registration statistics. 193 mip6HaConfTable : contains the configurable 194 advertisement parameters for all 195 the interfaces on which the which 196 the home agent service is 197 advertised. 198 mip6HaCounterTable : contains registration statistics 199 for all mobile nodes registered 200 with the home agent. 201 mip6HaListTable : contains the list of all routers 202 that are acting as home agents on 203 each of the interfaces on which 204 the home agent service is offered 205 by this router. 206 mip6HaGlobalAddrTable : contains the global addresses of 207 the jome agents. 209 5. The Mobile-IPv6 MIB. 211 MOBILEIPV6-MIB DEFINITIONS ::= BEGIN 212 IMPORTS 213 MODULE-IDENTITY, mib-2, Unsigned32, Integer32, 214 Gauge32, Counter64, 215 OBJECT-TYPE, NOTIFICATION-TYPE 216 FROM SNMPv2-SMI 217 TEXTUAL-CONVENTION, 218 TruthValue, DateAndTime, TimeStamp 219 FROM SNMPv2-TC 220 MODULE-COMPLIANCE, OBJECT-GROUP 221 FROM SNMPv2-CONF 222 -- SnmpAdminString 223 -- FROM SNMP-FRAMEWORK-MIB 224 InetAddressType, InetAddress 225 FROM INET-ADDRESS-MIB 226 ipv6IfIndex 227 FROM IPV6-MIB 228 ; 230 mip6MIB MODULE-IDENTITY 231 LAST-UPDATED "200407190000Z" -- 19th July, 2004 232 ORGANIZATION "IETF mip6 Working Group" 233 CONTACT-INFO 234 " Glenn Mansfield Keeni 235 Postal: Cyber Solutions Inc. 236 6-6-3, Minami Yoshinari 237 Aoba-ku, Sendai, Japan 989-3204. 238 Tel: +81-22-303-4012 239 Fax: +81-22-303-4015 240 E-mail: glenn@cysols.com 242 Kenichi Nagami 243 Postal: INTEC NetCore Inc. 244 1-3-3, Shin-suna 245 Koto-ku, Tokyo, 135-0075 246 Japan 248 Tel: +81-3-5665-5069 249 E-mail: nagami@inetcore.com 251 Postal: Kazuhide Koide 252 Tohoku University 253 Katahira Campus 254 Sendai 255 Japan 257 Tel: +81-22-217-5454 258 E-mail: koide@shiratori.riec.tohoku.ac.jp 260 Sri Gundavelli 261 Postal: Cisco Systems 262 170 W.Tasman Drive, 263 San Jose, CA 95134 264 USA 266 Tel: +1-408-527-6109 267 Email: sgundave@cisco.com 269 Support Group E-mail: mip6@ietf.org" 271 DESCRIPTION 272 " The MIB for monitoring Mobile-IPv6 entities. 273 Copyright (C) The Internet Society . The 274 initial version of this MIB module was published 275 in RFC xxxx; for full legal notices see the RFC 276 itself. Supplementary information may be available 277 on http://www.ietf.org/copyrights/ianamib.html. 278 " 279 -- RFC Ed.: replace xxxx with actual RFC number & remove this note 281 REVISION "200407190000Z" -- 19th July, 2004 282 DESCRIPTION "Initial version, published as RFC yyyy." 284 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 286 ::= { mib-2 XXX } -- will be assigned by IANA 288 -- IANA Reg.: Please assign a value for "XXX" under the 'mib-2' 289 -- subtree and to record the assignment in the SMI Numbers registry. 291 -- RFC Ed.: When the above assignment has been made, please 292 -- remove the above note 293 -- replace "XXX" (here and in the MIB module) with the assigned 294 -- value and 295 -- remove this note. 297 -- The major groups 299 mip6Notifications OBJECT IDENTIFIER ::= { mip6MIB 0 } 300 mip6Objects OBJECT IDENTIFIER ::= { mip6MIB 1 } 301 mip6Conformance OBJECT IDENTIFIER ::= { mip6MIB 2 } 302 mip6Core OBJECT IDENTIFIER ::= { mip6Objects 1 } 303 mip6Mn OBJECT IDENTIFIER ::= { mip6Objects 2 } 304 mip6Cn OBJECT IDENTIFIER ::= { mip6Objects 3 } 305 mip6Ha OBJECT IDENTIFIER ::= { mip6Objects 4 } 307 -- The sub groups 309 mip6System OBJECT IDENTIFIER ::= { mip6Core 1 } 310 mip6Bindings OBJECT IDENTIFIER ::= { mip6Core 2 } 311 mip6Stats OBJECT IDENTIFIER ::= { mip6Core 3 } 313 mip6MnSystem OBJECT IDENTIFIER ::= { mip6Mn 1 } 314 mip6MnConf OBJECT IDENTIFIER ::= { mip6Mn 2 } 315 mip6MnRegistration OBJECT IDENTIFIER ::= { mip6Mn 3 } 317 mip6CnSystem OBJECT IDENTIFIER ::= { mip6Cn 1 } 318 mip6CnStats OBJECT IDENTIFIER ::= { mip6Cn 2 } 320 mip6HaAdvertisement OBJECT IDENTIFIER ::= { mip6Ha 1 } 321 mip6HaStats OBJECT IDENTIFIER ::= { mip6Ha 2 } 323 -- Textual Conventions 324 Mipv6BURequestRejectionCode ::= TEXTUAL-CONVENTION 325 STATUS current 326 DESCRIPTION 327 "The value of the status field in the Binding 328 Acknowledgement message when the Binding Update 329 was rejected. 330 " 331 REFERENCE 332 "RFC3775 : Section 6.1.8" 333 SYNTAX BITS { 334 reasonUnspecified (1), -- (Code 128), 335 admProhibited (2), -- (Code 129), 336 insufficientResource (3), -- (Code 130), 337 homeRegistrationNotSupported (4), -- (Code 131), 338 notHomeSubnet (5), -- (Code 132), 339 notHomeAgentForThisMobileNode (6), -- (Code 133), 340 duplicateAddressDetectionFailed (7), -- (Code 134), 341 sequenceNumberOutOfWindow (8), -- (Code 135), 342 expiredHomeNonceIndex (9), -- (Code 136), 343 expiredCareofNonceIndex (10), -- (Code 137), 344 expiredNonces (11), -- (Code 138), 345 registrationTypeChangeDisallowed(12) -- (Code 139) 346 } 348 mip6Capabilities OBJECT-TYPE 349 SYNTAX BITS { 350 mobileNode (0), 351 homeAgent (1), 352 correspondentNode (2) 353 } 354 MAX-ACCESS read-only 355 STATUS current 356 DESCRIPTION 357 "This object indicates the mobile ipv6 functions that are 358 supported by this managed entity. Multiple Mobile IPv6 359 functions may be supported by a single entity. 360 " 361 REFERENCE 362 "RFC3775 : Section 6.1.8" 363 ::= { mip6System 1 } 365 mip6Status OBJECT-TYPE 366 SYNTAX INTEGER { enabled(1), disabled(2) } 367 MAX-ACCESS read-write 368 STATUS current 369 DESCRIPTION 370 "Indicates whether the Mobile IPv6 protocol is enabled for 371 the managed entity. If it is enabled, the agent discovery 372 and registration functions will be operational. 373 Changing the status from enabled(1) to disabled(2) will 374 terminate the agent discovery and registration functions. 375 On the other hand changing the status from disabled(2) to 376 enabled(1) will start the agent discovery and registration 377 functions. 378 " 379 ::= { mip6System 2 } 381 -- mip6BindingCache 383 mip6BindingCacheTable OBJECT-TYPE 384 SYNTAX SEQUENCE OF Mipv6BindingCacheEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "A table representing the Binding Cache on the managed 389 entity. This cache is maintained by home agents and 390 correspondent nodes. The cache contains both 391 correspondent registration entries and home registration 392 entries. 393 " 394 REFERENCE 395 "RFC3775 : Section 4.5, 9.1 , 10.1" 397 ::= { mip6Bindings 1 } 399 mip6BindingCacheEntry OBJECT-TYPE 400 SYNTAX Mipv6BindingCacheEntry 401 MAX-ACCESS not-accessible 402 STATUS current 403 DESCRIPTION 404 "An entry in the binding cache table. It represents a 405 single Binding Update. 406 " 407 INDEX { mip6BindingHomeAddressType, mip6BindingHomeAddress } 408 ::= { mip6BindingCacheTable 1 } 410 Mipv6BindingCacheEntry ::= 411 SEQUENCE { 412 mip6BindingHomeAddressType InetAddressType, 413 mip6BindingHomeAddress InetAddress, 414 mip6BindingCOAType InetAddressType, 415 mip6BindingCOA InetAddress, 416 mip6BindingTimeRegistered DateAndTime, 417 mip6BindingTimeGranted Gauge32, 418 mip6BindingTimeRemaining Gauge32, 419 mip6BindingHomeRegn TruthValue, 420 mip6BindingMaxSeq Unsigned32, 421 mip6BindingUsageTS DateAndTime, 422 mip6BindingUsageCount Counter32, 423 mip6BindingAdminStatus INTEGER 424 } 426 mip6BindingHomeAddressType OBJECT-TYPE 427 SYNTAX InetAddressType 428 MAX-ACCESS not-accessible 429 STATUS current 430 DESCRIPTION 431 "The InetAddressType of the mip6BindingHomeAddress 432 that follows. 433 " 434 ::= { mip6BindingCacheEntry 1 } 436 mip6BindingHomeAddress OBJECT-TYPE 437 SYNTAX InetAddress (SIZE (16|20)) 438 MAX-ACCESS not-accessible 439 STATUS current 440 DESCRIPTION 441 "The home address of the mobile node for which this is 442 the Binding Cache entry. This field is used as the key 443 for searching the Binding Cache for the destination 444 address of a packet being sent. 446 " 447 REFERENCE 448 "RFC3775 : Section 9.1" 449 ::= { mip6BindingCacheEntry 2 } 451 mip6BindingCOAType OBJECT-TYPE 452 SYNTAX InetAddressType 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "The InetAddressType of the mip6BindingCOA that follows. 457 " 458 ::= { mip6BindingCacheEntry 3 } 460 mip6BindingCOA OBJECT-TYPE 461 SYNTAX InetAddress 462 MAX-ACCESS read-only 463 STATUS current 464 DESCRIPTION 465 "The care-of address for the mobile node indicated by 466 the home address field (mip6BindingHomeAddress) in this 467 Binding Cache entry. A mobile node can have multiple 468 care-of-addresses. 469 " 470 REFERENCE 471 "RFC3775 : Section 9.1" 472 ::= { mip6BindingCacheEntry 4 } 474 mip6BindingTimeRegistered OBJECT-TYPE 475 SYNTAX DateAndTime 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The timestamp when this Binding Cache entry was created. 480 " 481 ::= { mip6BindingCacheEntry 5 } 483 mip6BindingTimeGranted OBJECT-TYPE 484 SYNTAX Gauge32 485 UNITS "seconds" 486 MAX-ACCESS read-only 487 STATUS current 488 DESCRIPTION 489 "The lifetime in seconds granted to the mobile node for 490 this registration. 491 " 492 ::= { mip6BindingCacheEntry 6 } 494 mip6BindingTimeRemaining OBJECT-TYPE 495 SYNTAX Gauge32 496 UNITS "seconds" 497 MAX-ACCESS read-only 498 STATUS current 499 DESCRIPTION 500 "The lifetime in seconds remaining for this registration. 501 " 502 REFERENCE 503 "RFC3775 : Section 9.1" 504 ::= { mip6BindingCacheEntry 7 } 506 mip6BindingHomeRegn OBJECT-TYPE 507 SYNTAX TruthValue 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "This object indicates whether or not this Binding Cache 512 entry is a home registration entry (applicable only on 513 nodes which support home agent functionality). 514 " 515 REFERENCE 516 "RFC3775 : Section 9.1" 517 ::= { mip6BindingCacheEntry 8 } 519 mip6BindingMaxSeq OBJECT-TYPE 520 SYNTAX Unsigned32 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The maximum value of the Sequence Number field received 525 in previous Binding Updates for this home address 526 (mip6BindingHomeAddress). 527 " 528 ::= { mip6BindingCacheEntry 9 } 530 mip6BindingUsageTS OBJECT-TYPE 531 SYNTAX DateAndTime 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "The timestamp when this entry was last looked up. 536 " 537 REFERENCE 538 "RFC3775 : Section 9.1" 539 ::= { mip6BindingCacheEntry 10 } 541 mip6BindingUsageCount OBJECT-TYPE 542 SYNTAX Counter32 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "The number of times this entry was looked up. 547 " 548 REFERENCE 549 "RFC3775 : Section 9.1" 550 ::= { mip6BindingCacheEntry 11 } 552 mip6BindingAdminStatus OBJECT-TYPE 553 SYNTAX INTEGER { 554 active (1), 555 inactive (2) 556 } 557 MAX-ACCESS read-write 558 STATUS current 559 DESCRIPTION 560 "This is an administrative used to control the 561 status of a binding cache entry. By default the 562 value will be 'active(1). 563 A value of 'inactive (2) will indicate that the 564 validity of the entry is suspended. It does not 565 exist in the binding cache for all practical 566 purposes. 567 The state can be changed from active(1) to 568 inactive(2) by operator intervention. 569 Causing the state to change to active results 570 in the entry being deleted from the cache. 571 Attempts to change the status from 'inactive' 572 to 'active' will be rejected. 573 " 574 REFERENCE 575 "RFC3775 : Section 9.1" 576 ::= { mip6BindingCacheEntry 12 } 578 -- mip6BindingHistory 579 -- Once the lifetime expires an entry will be removed from the 580 -- Binding Cache. 581 -- For monitoring purposes it will be useful to have access to the 582 -- history of the Binding Cache. BindingHistoryTable serves 583 -- this purpose. It records the history of the Bindings. 584 -- The size of the table will be left to implementors. 586 mip6BindingHistoryTable OBJECT-TYPE 587 SYNTAX SEQUENCE OF Mipv6BindingHistoryEntry 588 MAX-ACCESS not-accessible 589 STATUS current 590 DESCRIPTION 591 "A table containing a record of the bindings. 592 " 593 ::= { mip6Bindings 2 } 595 mip6BindingHistoryEntry OBJECT-TYPE 596 SYNTAX Mipv6BindingHistoryEntry 597 MAX-ACCESS not-accessible 598 STATUS current 599 DESCRIPTION 600 "The record of a binding ." 601 INDEX { mip6BindingHstHomeAddressType, 602 mip6BindingHstHomeAddress , 603 mip6BindingHstIndex} 604 ::= { mip6BindingHistoryTable 1 } 606 Mipv6BindingHistoryEntry ::= 607 SEQUENCE { 608 mip6BindingHstHomeAddressType InetAddressType, 609 mip6BindingHstHomeAddress InetAddress, 610 mip6BindingHstCOAType InetAddressType, 611 mip6BindingHstCOA InetAddress, 612 mip6BindingHstIndex Unsigned32, 613 mip6BindingHstTimeRegistered DateAndTime, 614 mip6BindingHstTimeExpired DateAndTime, 615 mip6BindingHstHomeRegn TruthValue, 616 mip6BindingHstUsageTS DateAndTime, 617 mip6BindingHstUsageCount Unsigned32 618 } 620 mip6BindingHstHomeAddressType OBJECT-TYPE 621 SYNTAX InetAddressType 622 MAX-ACCESS not-accessible 623 STATUS current 624 DESCRIPTION 625 "The InetAddressType of the mip6BindingHomeAddress 626 that follows. 627 " 628 ::= { mip6BindingHistoryEntry 1 } 630 mip6BindingHstHomeAddress OBJECT-TYPE 631 SYNTAX InetAddress (SIZE (16|20)) 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "Mobile node's home (IP) address. 636 " 637 ::= { mip6BindingHistoryEntry 2 } 639 mip6BindingHstCOAType OBJECT-TYPE 640 SYNTAX InetAddressType 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The InetAddressType of the mip6BindingCOA that follows. 645 " 646 ::= { mip6BindingHistoryEntry 3 } 648 mip6BindingHstCOA OBJECT-TYPE 649 SYNTAX InetAddress 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "Mobile node's care-of-address. One mobile node can 654 have multiple bindings with different 655 care-of-addresses." 656 ::= { mip6BindingHistoryEntry 4 } 658 mip6BindingHstIndex OBJECT-TYPE 659 SYNTAX Unsigned32 660 MAX-ACCESS not-accessible 661 STATUS current 662 DESCRIPTION 663 "The index to uniquely identify this record along with 664 the Mobile nodes HomeAddress type and HomeAddress. It 665 should be monotonically increasing. It may wrap after 666 reaching its max value." 667 ::= { mip6BindingHistoryEntry 5 } 669 mip6BindingHstTimeRegistered OBJECT-TYPE 670 SYNTAX DateAndTime 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The timestamp when this Binding Cache entry was created. 675 " 676 ::= { mip6BindingHistoryEntry 6 } 678 mip6BindingHstTimeExpired OBJECT-TYPE 679 SYNTAX DateAndTime 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "The timestamp when this Binding Cache entry expired. 684 " 685 ::= { mip6BindingHistoryEntry 7 } 687 mip6BindingHstHomeRegn OBJECT-TYPE 688 SYNTAX TruthValue 689 MAX-ACCESS read-only 690 STATUS current 691 DESCRIPTION 692 "This object indicates whether or not this Binding Cache 693 entry is a home registration entry (applicable only on 694 nodes which support home agent functionality). 695 " 696 ::= { mip6BindingHistoryEntry 8 } 698 mip6BindingHstUsageTS OBJECT-TYPE 699 SYNTAX DateAndTime 700 MAX-ACCESS read-only 701 STATUS current 702 DESCRIPTION 703 "The timestamp when this entry was last looked up. 704 " 705 ::= { mip6BindingHistoryEntry 9 } 707 mip6BindingHstUsageCount OBJECT-TYPE 708 SYNTAX Unsigned32 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "The number of times this entry was looked up. 713 " 714 ::= { mip6BindingHistoryEntry 10 } 716 -- mip6TrafficCounters 718 -- MIPv6 Traffic will be characterized by 719 -- IPv6 datagrams which satisfy atleast one of the following 720 -- conditions 721 -- - the datagrams are tunneled to the mobile node by the HA 722 -- - the datagrams are reverse tunneled by the MN to the HA 723 -- - the datagrams have which have the Routing header type 2 724 -- set. 725 -- - the datagrams have the Home Address option set in the 726 -- Destination Option extension header 727 -- - IPv6 datagrams with the mobility header 729 mip6TotalTraffic OBJECT IDENTIFIER ::= { mip6Stats 1 } 730 -- REFERENCE 731 -- "RFC3775 : Section 4.1, 6.3" 733 mip6InOctets OBJECT-TYPE 734 SYNTAX Counter32 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "The total number of octets in the MIPv6 datagrams received 739 by the MIPv6 entity. This will include the datagrams with 740 the Mobility Header, the Home Address option in the 741 Destination Option extension header (Next Header value = 60), 742 the type 2 Routing Header. It will also include the IPv6 743 datagrams that are reverse tunneled to a home agent from 744 a mobile node's home address. 745 Discontinuities in the value of this counter can occur at 746 re-initialization of the management system, and at other times 747 as indicated by the value of mip6CounterDiscontinuityTime. 748 " 749 REFERENCE 750 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 751 ::= { mip6TotalTraffic 1 } 753 mip6HCInOctets OBJECT-TYPE 754 SYNTAX Counter32 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "The total number of octets in the MIPv6 datagrams received 759 by the MIPv6 entity. This will include the datagrams with 760 the Mobility Header, the Home Address option in the 761 Destination Option extension header (Next Header value = 60), 762 the type 2 Routing Header. It will also include the IPv6 763 datagrams that are reverse tunneled to a home agent from 764 a mobile node's home address. 765 This object is a 64-bit version of mip6InOctets. 766 Discontinuities in the value of this counter can occur at 767 re-initialization of the management system, and at other times 768 as indicated by the value of mip6CounterDiscontinuityTime. 769 " 770 REFERENCE 771 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 772 ::= { mip6TotalTraffic 2 } 774 mip6InPkts OBJECT-TYPE 775 SYNTAX Counter32 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "The number of MIPv6 datagrams received by the MIPv6 entity. 780 This will include the datagrams with the Mobility Header, 781 the Home Address option in the Destination Option extension 782 header (Next Header value = 60), the type 2 Routing Header. 783 It will also include the IPv6 datagrams that are reverse 784 tunneled to a home agent from a mobile node's home address. 785 Discontinuities in the value of this counter can occur at 786 re-initialization of the management system, and at other times 787 as indicated by the value of mip6CounterDiscontinuityTime. 788 " 789 REFERENCE 790 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 791 ::= { mip6TotalTraffic 3 } 793 mip6HCInPkts OBJECT-TYPE 794 SYNTAX Counter32 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "The number of MIPv6 datagrams received by the MIPv6 entity. 799 This will include the datagrams with the Mobility Header, 800 the Home Address option in the Destination Option extension 801 header (Next Header value = 60), the type 2 Routing Header. 802 It will also include the IPv6 datagrams that are reverse 803 tunneled to a home agent from a mobile node's home address. 804 This object is a 64-bit version of mip6InPkts. 805 Discontinuities in the value of this counter can occur at 806 re-initialization of the management system, and at other times 807 as indicated by the value of mip6CounterDiscontinuityTime. 808 " 809 REFERENCE 810 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 811 ::= { mip6TotalTraffic 4 } 813 mip6OutOctets OBJECT-TYPE 814 SYNTAX Counter32 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "The total number of octets in the MIPv6 datagrams sent 819 by the MIPv6 entity. This will include the datagrams with 820 the Mobility Header, the Home Address option in the 821 Destination Option extension header (Next Header value = 60), 822 the type 2 Routing Header. It will also include the IPv6 823 datagrams that are reverse tunneled to a home agent from 824 a mobile node's home address. 826 Discontinuities in the value of this counter can occur at 827 re-initialization of the management system, and at other times 828 as indicated by the value of mip6CounterDiscontinuityTime. 829 " 830 REFERENCE 831 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 832 ::= { mip6TotalTraffic 5 } 834 mip6HCOutOctets OBJECT-TYPE 835 SYNTAX Counter32 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The total number of octets in the MIPv6 datagrams sent 840 by the MIPv6 entity. This will include the datagrams with 841 the Mobility Header, the Home Address option in the 842 Destination Option extension header (Next Header value = 60), 843 the type 2 Routing Header. It will also include the IPv6 844 datagrams that are reverse tunneled to a home agent from 845 a mobile node's home address. 846 This object is a 64-bit version of mip6OutOctets. 847 Discontinuities in the value of this counter can occur at 848 re-initialization of the management system, and at other times 849 as indicated by the value of mip6CounterDiscontinuityTime. 850 " 851 REFERENCE 852 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 853 ::= { mip6TotalTraffic 6 } 855 mip6OutPkts OBJECT-TYPE 856 SYNTAX Counter32 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "The number of MIPv6 datagrams sent by the MIPv6 entity. 861 This will include the datagrams with the Mobility Header, 862 the Home Address option in the Destination Option extension 863 header (Next Header value = 60), the type 2 Routing Header. 864 It will also include the IPv6 datagrams that are reverse 865 tunneled to a home agent from a mobile node's home address. 866 Discontinuities in the value of this counter can occur at 867 re-initialization of the management system, and at other times 868 as indicated by the value of mip6CounterDiscontinuityTime. 869 " 870 REFERENCE 871 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 872 ::= { mip6TotalTraffic 7 } 874 mip6HCOutPkts OBJECT-TYPE 875 SYNTAX Counter32 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The number of MIPv6 datagrams sent by the MIPv6 entity. 880 This will include the datagrams with the Mobility Header, 881 the Home Address option in the Destination Option extension 882 header (Next Header value = 60), the type 2 Routing Header. 883 It will also include the IPv6 datagrams that are reverse 884 tunneled to a home agent from a mobile node's home address. 885 This object is a 64-bit version of mip6OutPkts. 886 Discontinuities in the value of this counter can occur at 887 re-initialization of the management system, and at other times 888 as indicated by the value of mip6CounterDiscontinuityTime. 889 " 890 REFERENCE 891 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 892 ::= { mip6TotalTraffic 8 } 894 mip6CounterDiscontinuityTime OBJECT-TYPE 895 SYNTAX TimeStamp 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "The value of sysUpTime on the most recent occasion at which 900 any one or more of this MIPv6 entities global counters viz, 901 counters with OID prefix 'mip6TotalTraffic' or 902 'mip6CnGlobalStats' or 'mip6HaGlobalStats' suffered a 903 discontinuity. 904 If no such discontinuities have occurred since the last re- 905 initialization of the local management subsystem, then this 906 object will have a zero value. 907 " 908 ::= { mip6TotalTraffic 9 } 910 -- mip6NodeTrafficCounters 912 mip6NodeTrafficTable OBJECT-TYPE 913 SYNTAX SEQUENCE OF Mipv6NodeTrafficEntry 914 MAX-ACCESS not-accessible 915 STATUS current 916 DESCRIPTION 917 "A table containing MIPv6 traffic counters per mobile 918 node. 919 " 920 ::= { mip6Stats 2 } 922 mip6NodeTrafficEntry OBJECT-TYPE 923 SYNTAX Mipv6NodeTrafficEntry 924 MAX-ACCESS not-accessible 925 STATUS current 926 DESCRIPTION 927 "The MIPv6 traffic counters for a mobile node." 928 INDEX { mip6BindingHomeAddressType, mip6BindingHomeAddress } 929 ::= { mip6NodeTrafficTable 1 } 931 Mipv6NodeTrafficEntry ::= 932 SEQUENCE { 933 mip6NodeInOctets Counter32, 934 mip6HCNodeInOctets Counter64, 935 mip6NodeInPkts Counter32, 936 mip6HCNodeInPkts Counter64, 937 mip6NodeOutOctets Counter32, 938 mip6HCNodeOutOctets Counter64, 939 mip6NodeOutPkts Counter32, 940 mip6HCNodeOutPkts Counter64, 941 mip6NodeCtrDiscontinuityTime TimeStamp 942 } 944 mip6NodeInOctets OBJECT-TYPE 945 SYNTAX Counter32 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION 949 "The total number of octets in the MIPv6 datagrams received 950 from the mobile node by the MIPv6 entity. This will include 951 the datagrams with the Mobility Header and, the Home Address 952 option in the Destination Option extension header (Next 953 Header value = 60). It will also include the IPv6 datagrams 954 that are reverse tunneled to a home agent from the mobile 955 node's home address. 956 Discontinuities in the value of this counter can occur at 957 re-initialization of the management system, and at other times 958 as indicated by the value of mip6NodeCtrDiscontinuityTime. 959 " 960 REFERENCE 961 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 962 ::= { mip6NodeTrafficEntry 1 } 964 mip6HCNodeInOctets OBJECT-TYPE 965 SYNTAX Counter64 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "The total number of octets in the MIPv6 datagrams received 970 from the mobile node by the MIPv6 entity. This will include 971 the datagrams with the Mobility Header and, the Home Address 972 option in the Destination Option extension header (Next 973 Header value = 60). It will also include the IPv6 datagrams 974 that are reverse tunneled to a home agent from the mobile 975 node's home address. 976 This object is a 64-bit version of mip6NodeInOctets. 977 Discontinuities in the value of this counter can occur at 978 re-initialization of the management system, and at other times 979 as indicated by the value of mip6NodeCtrDiscontinuityTime. 980 " 981 REFERENCE 982 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 983 ::= { mip6NodeTrafficEntry 2 } 985 mip6NodeInPkts OBJECT-TYPE 986 SYNTAX Counter32 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "The number of MIPv6 datagrams received from the mobile node 991 by the MIPv6 entity. This will include the datagrams with the 992 Mobility Header and, the Home Address option in the Destination 993 Option extension header (Next Header value = 60). It will also 994 include the IPv6 datagrams that are reverse tunneled to a home 995 agent from the mobile node's home address. 996 Discontinuities in the value of this counter can occur at 997 re-initialization of the management system, and at other times 998 as indicated by the value of mip6NodeCtrDiscontinuityTime. 999 " 1000 REFERENCE 1001 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1002 ::= { mip6NodeTrafficEntry 3 } 1004 mip6HCNodeInPkts OBJECT-TYPE 1005 SYNTAX Counter64 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The number of MIPv6 datagrams received from the mobile node 1010 by the MIPv6 entity. This will include the datagrams with the 1011 Mobility Header and, the Home Address option in the Destination 1012 Option extension header (Next Header value = 60). It will also 1013 include the IPv6 datagrams that are reverse tunneled to a home 1014 agent from the mobile node's home address. 1015 This object is a 64-bit version of mip6NodeInPkts. 1016 Discontinuities in the value of this counter can occur at 1017 re-initialization of the management system, and at other times 1018 as indicated by the value of mip6NodeCtrDiscontinuityTime. 1019 " 1020 REFERENCE 1021 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1022 ::= { mip6NodeTrafficEntry 4 } 1024 mip6NodeOutOctets OBJECT-TYPE 1025 SYNTAX Counter32 1026 MAX-ACCESS read-only 1027 STATUS current 1028 DESCRIPTION 1029 "The total number of octets in the MIPv6 datagrams sent to 1030 the mobile node by the MIPv6 entity. This will include the 1031 datagrams with the Mobility Header and the type 2 Routing 1032 Header. It will also include the IPv6 datagrams that are 1033 tunneled by a home agent to the mobile node. 1034 Discontinuities in the value of this counter can occur at 1035 re-initialization of the management system, and at other times 1036 as indicated by the value of mip6NodeCtrDiscontinuityTime. 1037 " 1038 REFERENCE 1039 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1040 ::= { mip6NodeTrafficEntry 5 } 1042 mip6HCNodeOutOctets OBJECT-TYPE 1043 SYNTAX Counter64 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "The total number of octets in the MIPv6 datagrams sent to 1048 the mobile node by the MIPv6 entity. This will include the 1049 datagrams with the Mobility Header and the type 2 Routing 1050 Header. It will also include the IPv6 datagrams that are 1051 tunneled by a home agent to the mobile node. 1052 This object is a 64-bit version of mip6NodeOutOctets. 1053 Discontinuities in the value of this counter can occur at 1054 re-initialization of the management system, and at other times 1055 as indicated by the value of mip6NodeCtrDiscontinuityTime. 1056 " 1057 REFERENCE 1058 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1059 ::= { mip6NodeTrafficEntry 6 } 1061 mip6NodeOutPkts OBJECT-TYPE 1062 SYNTAX Counter32 1063 MAX-ACCESS read-only 1064 STATUS current 1065 DESCRIPTION 1066 "The number of MIPv6 datagrams sent to the mobile node by the 1067 MIPv6 entity. This will include the datagrams with the 1068 Mobility Header, the type 2 Routing Header. It will also 1069 include the IPv6 datagrams that are tunneled by a home agent 1070 to the mobile node. 1071 Discontinuities in the value of this counter can occur at 1072 re-initialization of the management system, and at other times 1073 as indicated by the value of mip6NodeCtrDiscontinuityTime. 1074 " 1075 REFERENCE 1076 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1077 ::= { mip6NodeTrafficEntry 7 } 1079 mip6HCNodeOutPkts OBJECT-TYPE 1080 SYNTAX Counter64 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "The number of MIPv6 datagrams sent to the mobile node by the 1085 MIPv6 entity. This will include the datagrams with the 1086 Mobility Header, the type 2 Routing Header. It will also 1087 include the IPv6 datagrams that are tunneled by a home agent 1088 to the mobile node. 1089 This object is a 64-bit version of mip6NodeOutOctets. 1090 Discontinuities in the value of this counter can occur at 1091 re-initialization of the management system, and at other times 1092 as indicated by the value of mip6NodeCtrDiscontinuityTime. 1093 " 1094 REFERENCE 1095 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1096 ::= { mip6NodeTrafficEntry 8 } 1098 mip6NodeCtrDiscontinuityTime OBJECT-TYPE 1099 SYNTAX TimeStamp 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "The value of sysUpTime on the most recent occasion at which 1104 any one or more of the counters in this row suffered a 1105 discontinuity. The relevant counters are the specific 1106 instances of any Counter32 or Counter64 objects in this 1107 row. 1108 If no such discontinuities have occurred since the last re- 1109 initialization of the local management subsystem, then this 1110 object contains a zero value. 1111 " 1112 ::= { mip6NodeTrafficEntry 9 } 1114 -- mip6MnSystem Group 1116 mip6MnHomeAddressTable OBJECT-TYPE 1117 SYNTAX SEQUENCE OF Mipv6MnHomeAddressEntry 1118 MAX-ACCESS not-accessible 1119 STATUS current 1120 DESCRIPTION 1121 "A table containing registration status for all the home 1122 addresses pertaining to the mobile node. 1123 " 1124 ::= { mip6MnSystem 1 } 1126 mip6MnHomeAddressEntry OBJECT-TYPE 1127 SYNTAX Mipv6MnHomeAddressEntry 1128 MAX-ACCESS not-accessible 1129 STATUS current 1130 DESCRIPTION 1131 "The registration status for a homeaddress." 1132 INDEX { mip6MnHomeAddressType, mip6MnHomeAddress } 1133 ::= { mip6MnHomeAddressTable 1 } 1135 Mipv6MnHomeAddressEntry ::= 1136 SEQUENCE { 1137 mip6MnHomeAddressType InetAddressType, 1138 mip6MnHomeAddress InetAddress, 1139 mip6MnHomeAddressState INTEGER 1140 } 1142 mip6MnHomeAddressType OBJECT-TYPE 1143 SYNTAX InetAddressType 1144 MAX-ACCESS not-accessible 1145 STATUS current 1146 DESCRIPTION 1147 "The InetAddressType of the mip6MnHomeAddress that 1148 follows. 1149 " 1150 ::= { mip6MnHomeAddressEntry 1 } 1152 mip6MnHomeAddress OBJECT-TYPE 1153 SYNTAX InetAddress (SIZE (16|20)) 1154 MAX-ACCESS not-accessible 1155 STATUS current 1156 DESCRIPTION 1157 "A unicast routable address assigned to the mobile node. 1158 This is used as the 'permanent address' of the mobile node. 1159 in the sense that it remains unchanged regardless of the 1160 mobile node's current point of attachment. If mobile node 1161 doesn't have a home address assigned yet then this object 1162 will take the default 'unspecified' value ::0. 1163 " 1164 REFERENCE 1165 "RFC3775 : Section 3.2" 1166 ::= { mip6MnHomeAddressEntry 2 } 1168 mip6MnHomeAddressState OBJECT-TYPE 1169 SYNTAX INTEGER { 1170 unknown(1), 1171 home(2), 1172 registered(3), 1173 pending(4), 1174 isolated(5) 1175 } 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "Indicates mobile node's state of Mobile IP: 1180 unknown -- The state of the MN cannot be determined 1181 home, -- MN is connected to home network. 1182 registered, -- MN is on a foreign network and is 1183 registered with the home agent 1184 pending, -- MN has sent registration request 1185 to the home agent and is waiting for the reply 1186 isolated, -- MN is isolated from network i.e. it is not 1187 in its home network, it is not registered and 1188 no registration ack is pending 1189 " 1190 ::= { mip6MnHomeAddressEntry 3 } 1192 -- Mobile Node Discovery and Advertisement Group Counters 1194 mip6MnDiscoveryRequests OBJECT-TYPE 1195 SYNTAX Counter32 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "Total number of ICMP Dynamic Home Agent Address Discovery 1200 Requests sent by the mobile node. 1201 Discontinuities in the value of this counter can occur at 1202 re-initialization of the management system, and at other times 1203 as indicated by the value of mip6CounterDiscontinuityTime. 1204 " 1205 REFERENCE 1206 "RFC3775 : Section 10.5, 11.4.1" 1207 ::= { mip6MnConf 1 } 1209 mip6MnDiscoveryReplies OBJECT-TYPE 1210 SYNTAX Counter32 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "Total number of ICMP Dynamic Home Agent Address Discovery 1215 Replies received by the mobile node. 1216 Discontinuities in the value of this counter can occur at 1217 re-initialization of the management system, and at other times 1218 as indicated by the value of mip6CounterDiscontinuityTime. 1219 " 1220 REFERENCE 1221 "RFC3775 : Section 10.5, 11.4.1" 1222 ::= { mip6MnConf 2 } 1224 mip6MnDiscoveryTimeouts OBJECT-TYPE 1225 SYNTAX Counter32 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "Total number of ICMP Dynamic Home Agent Address Discovery 1230 Requests that timed out. 1231 Discontinuities in the value of this counter can occur at 1232 re-initialization of the management system, and at other times 1233 as indicated by the value of mip6CounterDiscontinuityTime. 1234 " 1235 REFERENCE 1236 "RFC3775 : Section 10.5, 11.4.1, 12" 1237 ::= { mip6MnConf 3 } 1239 mip6MnPrefixSolicitationsSent OBJECT-TYPE 1240 SYNTAX Counter32 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "Total number of ICMP Mobile Prefix Solicitations sent by the 1245 mobile node. 1246 Discontinuities in the value of this counter can occur at 1247 re-initialization of the management system, and at other times 1248 as indicated by the value of mip6CounterDiscontinuityTime. 1249 " 1250 REFERENCE 1251 "RFC3775 : Section 10.5, 11.4.2" 1252 ::= { mip6MnConf 4 } 1254 mip6MnPrefixAdvsRecd OBJECT-TYPE 1255 SYNTAX Counter32 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "Total number of ICMP Mobile Prefix Advertisements received by 1260 the mobile node. This will include the ICMP Mobile Prefix 1261 Advertisements that are discarded by the validity check. 1262 Discontinuities in the value of this counter can occur at 1263 re-initialization of the management system, and at other times 1264 as indicated by the value of mip6CounterDiscontinuityTime. 1265 " 1266 REFERENCE 1267 "RFC3775 : Section 10.6, 11.4.3" 1268 ::= { mip6MnConf 5 } 1270 mip6MnPrefixAdvsIgnored OBJECT-TYPE 1271 SYNTAX Counter32 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "Total number of Mobile Prefix Advertisements discarded by the 1276 validity check. 1277 Discontinuities in the value of this counter can occur at 1278 re-initialization of the management system, and at other times 1279 as indicated by the value of mip6CounterDiscontinuityTime. 1280 " 1281 REFERENCE 1282 "RFC3775 : Section 10.6, 11.4.3" 1283 ::= { mip6MnConf 6 } 1285 mip6MnMovedToFN OBJECT-TYPE 1286 SYNTAX Counter32 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "Number of times the mobile node has detected movement 1291 from to a foreign network from another foreign network or 1292 from the home network, has reconstructed its care-of address 1293 and has initiated the care-of address registration process. 1294 Discontinuities in the value of this counter can occur at 1295 re-initialization of the management system, and at other times 1296 as indicated by the value of mip6CounterDiscontinuityTime. 1297 " 1298 REFERENCE 1299 "RFC3775 : Section 11.5.1" 1300 ::= { mip6MnConf 7 } 1302 mip6MnMovedToHN OBJECT-TYPE 1303 SYNTAX Counter32 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "Number of times the mobile node has detected movement 1308 from a foreign network to its home network. 1309 Discontinuities in the value of this counter can occur at 1310 re-initialization of the management system, and at other times 1311 as indicated by the value of mip6CounterDiscontinuityTime. 1312 " 1313 REFERENCE 1314 "RFC3775 : Section 11.5.4" 1315 ::= { mip6MnConf 8 } 1317 -- Mobile Node Registration Group 1319 -- Registration table of mobile node 1321 mip6MnBLTable OBJECT-TYPE 1322 SYNTAX SEQUENCE OF Mipv6MnBLEntry 1323 MAX-ACCESS not-accessible 1324 STATUS current 1325 DESCRIPTION 1326 "This table corresponds to the Binding Update List (BL) that 1327 is maintained by the mobile node. The list holds an item 1328 for every binding that the mobile node has established or is 1329 trying to establish. Both correspondent and home registrations 1330 are included in this table. Entries from the table are deleted 1331 as the lifetime of the binding expires. 1332 " 1333 REFERENCE 1334 "RFC3775 : Section 4.5, 11.1" 1335 ::= { mip6MnRegistration 1 } 1337 mip6MnBLEntry OBJECT-TYPE 1338 SYNTAX Mipv6MnBLEntry 1339 MAX-ACCESS not-accessible 1340 STATUS current 1341 DESCRIPTION 1342 "Information about a Binding Update send by the mobile node 1343 to a either to its home agent or one of its correspondent 1344 nodes. 1345 " 1346 INDEX { mip6MnBLNodeAddressType, 1347 mip6MnBLNodeAddress, 1348 mip6MnHomeAddressType, 1349 mip6MnHomeAddress 1350 } 1351 ::= { mip6MnBLTable 1 } 1353 Mipv6MnBLEntry ::= SEQUENCE { 1354 mip6MnBLNodeAddressType InetAddressType, 1355 mip6MnBLNodeAddress InetAddress, 1356 mip6MnBLCOAType InetAddressType, 1357 mip6MnBLCOA InetAddress, 1358 mip6MnBLLifeTimeRequested Unsigned32, 1359 mip6MnBLLifeTimeGranted Unsigned32, 1360 mip6MnBLMaxSeq Unsigned32, 1361 mip6MnBLTimeSent DateAndTime, 1362 mip6MnBLAccepted TruthValue, 1363 mip6MnBLAcceptedTime DateAndTime, 1364 mip6MnBLRetransmissions Integer32 1365 } 1367 mip6MnBLNodeAddressType OBJECT-TYPE 1368 SYNTAX InetAddressType 1369 MAX-ACCESS not-accessible 1370 STATUS current 1371 DESCRIPTION 1372 "The InetAddressType of the mip6MnBLNodeAddress 1373 that follows. 1374 " 1375 ::= { mip6MnBLEntry 1 } 1377 mip6MnBLNodeAddress OBJECT-TYPE 1378 SYNTAX InetAddress (SIZE (16|20)) 1379 MAX-ACCESS not-accessible 1380 STATUS current 1381 DESCRIPTION 1382 "IP address of the agent as used in the destination 1383 IP address of the Binding Update. The agent 1384 may be a home agent or a correspondent node." 1385 REFERENCE 1386 "RFC3775 : Section 11.1" 1387 ::= { mip6MnBLEntry 2 } 1389 mip6MnBLCOAType OBJECT-TYPE 1390 SYNTAX InetAddressType 1391 MAX-ACCESS not-accessible 1392 STATUS current 1393 DESCRIPTION 1394 "The InetAddressType of the mip6MnBLCOA that follows. 1395 " 1396 ::= { mip6MnBLEntry 3 } 1398 mip6MnBLCOA OBJECT-TYPE 1399 SYNTAX InetAddress (SIZE (16|20)) 1400 MAX-ACCESS not-accessible 1401 STATUS current 1402 DESCRIPTION 1403 "Care-of address that the mobile node intends to register 1404 in the Binding Update request." 1405 REFERENCE 1406 "RFC3775 : Section 11.1" 1407 ::= { mip6MnBLEntry 4 } 1409 mip6MnBLLifeTimeRequested OBJECT-TYPE 1410 SYNTAX Unsigned32 1411 UNITS "seconds" 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "The lifetime requested by the mobile node (in seconds) 1416 in the Binding Update. 1417 " 1418 REFERENCE 1419 "RFC3775 : Section 11.1" 1420 ::= { mip6MnBLEntry 5 } 1422 mip6MnBLLifeTimeGranted OBJECT-TYPE 1423 SYNTAX Unsigned32 1424 UNITS "seconds" 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "The lifetime granted to the mobile node for this binding. 1429 This field will be inaccessible if the Binding Update request 1430 has not been accepted. 1431 The lifetime remaining (lR) can be calculated using the current 1432 time (cT), mip6MnBLAcceptedTime (aT) and mip6MnBLLifeTimeGranted 1433 (lG) as follows 1434 lR = lG - (cT - aT). 1435 When lR is zero this entry will be deleted from the Binding Update 1436 List and consequently from this table." 1437 ::= { mip6MnBLEntry 6 } 1439 mip6MnBLMaxSeq OBJECT-TYPE 1440 SYNTAX Unsigned32 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "The maximum value of the Sequence Number field sent in 1445 previous Binding Updates to this destination. 1446 " 1447 REFERENCE 1448 "RFC3775 : Section 11.1" 1450 ::= { mip6MnBLEntry 7 } 1452 mip6MnBLTimeSent OBJECT-TYPE 1453 SYNTAX DateAndTime 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 "The time when the last (re-)transmission occurred." 1458 REFERENCE 1459 "RFC3775 : Section 11.1" 1460 ::= { mip6MnBLEntry 8 } 1462 mip6MnBLAccepted OBJECT-TYPE 1463 SYNTAX TruthValue 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "true(1) if the mobile node has received a 1468 binding acknowledgment indicating that service has been 1469 accepted (status code 0 or 1); false(2) otherwise. 1470 false(2) implies that the registration is still pending. 1471 " 1472 ::= { mip6MnBLEntry 9 } 1474 mip6MnBLAcceptedTime OBJECT-TYPE 1475 SYNTAX DateAndTime 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "The time at which the mobile node receives a binding 1480 acknowledgment indicating that Binding Update has been 1481 accepted (status code 0 or 1); 1482 This object will be inaccessible if the Binding Update 1483 request is still pending. 1484 " 1485 ::= { mip6MnBLEntry 10 } 1487 mip6MnBLRetransmissions OBJECT-TYPE 1488 SYNTAX Integer32 1489 MAX-ACCESS read-only 1490 STATUS current 1491 DESCRIPTION 1492 "The number of Binding Update retransmissions. 1493 " 1494 REFERENCE 1495 "RFC3775 : Section 11.1" 1496 ::= { mip6MnBLEntry 11 } 1498 -- Mobile Node Registration Group Counters 1500 mip6MnRegnCounters OBJECT IDENTIFIER ::= { mip6MnRegistration 2 } 1502 mip6MnMobilityMessagesSent OBJECT-TYPE 1503 SYNTAX Counter32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "The total number of mobility messages, i.e. IPv6 datagrams 1508 with Mobility Header, sent by the mobile node. There are 1509 3 types of mobility messages viz. Home Test Init, Care-of 1510 Test Init, and Binding Updates that are sent by mobile nodes. 1511 Discontinuities in the value of this counter can occur at 1512 re-initialization of the management system, and at other times 1513 as indicated by the value of mip6CounterDiscontinuityTime. 1514 " 1515 REFERENCE 1516 "RFC3775 : Section 4.2, 6.1" 1517 ::= { mip6MnRegnCounters 1 } 1519 mip6MnMobilityMessagesRecd OBJECT-TYPE 1520 SYNTAX Counter32 1521 MAX-ACCESS read-only 1522 STATUS current 1523 DESCRIPTION 1524 "The total number of mobility messages, i.e. IPv6 datagrams 1525 with Mobility Header, received by the mobile node. There are 1526 5 types of mobility messages viz. Home Test, Care-of Test, 1527 Binding Acknowledgement, Binding Refresh Request and Binding 1528 Error that are sent to mobile nodes. 1529 Discontinuities in the value of this counter can occur at 1530 re-initialization of the management system, and at other times 1531 as indicated by the value of mip6CounterDiscontinuityTime. 1532 " 1533 REFERENCE 1534 "RFC3775 : Section 4.2, 6.1" 1535 ::= { mip6MnRegnCounters 2 } 1537 mip6MnBUsToHA OBJECT-TYPE 1538 SYNTAX Counter32 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "Total number of Binding Updates sent to the mobile node's 1543 home agent(s). 1544 Discontinuities in the value of this counter can occur at 1545 re-initialization of the management system, and at other times 1546 as indicated by the value of mip6CounterDiscontinuityTime. 1547 " 1548 REFERENCE 1549 "RFC3775 : Section 11.7.1" 1550 ::= { mip6MnRegnCounters 3 } 1552 mip6MnBUAcksFromHA OBJECT-TYPE 1553 SYNTAX Counter32 1554 MAX-ACCESS read-only 1555 STATUS current 1556 DESCRIPTION 1557 "Total number of valid binding acknowledgements received 1558 from the the mobile nodes home agent(s). 1559 Discontinuities in the value of this counter can occur at 1560 re-initialization of the management system, and at other times 1561 as indicated by the value of mip6CounterDiscontinuityTime. 1562 " 1563 REFERENCE 1564 "RFC3775 : Section 11.7.3" 1565 ::= { mip6MnRegnCounters 4 } 1567 mip6MnBUsToCN OBJECT-TYPE 1568 SYNTAX Counter32 1569 MAX-ACCESS read-only 1570 STATUS current 1571 DESCRIPTION 1572 "Total number of Binding Updates sent to 1573 correspondent nodes by the mobile node. 1574 Discontinuities in the value of this counter can occur at 1575 re-initialization of the management system, and at other times 1576 as indicated by the value of mip6CounterDiscontinuityTime. 1577 " 1578 REFERENCE 1579 "RFC3775 : Section 11.7.2" 1580 ::= { mip6MnRegnCounters 5 } 1582 mip6MnBUAcksFromCN OBJECT-TYPE 1583 SYNTAX Counter32 1584 MAX-ACCESS read-only 1585 STATUS current 1586 DESCRIPTION 1587 "Total number of valid Binding Update ACKs 1588 received from all the correspondent nodes. 1589 Discontinuities in the value of this counter can occur at 1590 re-initialization of the management system, and at other times 1591 as indicated by the value of mip6CounterDiscontinuityTime. 1592 " 1593 REFERENCE 1594 "RFC3775 : Section 11.7.3" 1595 ::= { mip6MnRegnCounters 6 } 1597 mip6MnBindingErrorsFromCN OBJECT-TYPE 1598 SYNTAX Counter32 1599 MAX-ACCESS read-only 1600 STATUS current 1601 DESCRIPTION 1602 "Total number of Binding Error messages received 1603 by mobile node from CN. 1604 Discontinuities in the value of this counter can occur at 1605 re-initialization of the management system, and at other times 1606 as indicated by the value of mip6CounterDiscontinuityTime. 1607 " 1608 ::= { mip6MnRegnCounters 7 } 1610 mip6MnICMPErrorsRecd OBJECT-TYPE 1611 SYNTAX Counter32 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "Total number of ICMP Error messages of type ICMP 1616 Parameter Problem, Code 1 or Code 2 received by 1617 the mobile node from a CN in response to a return routability 1618 procedure, a Binding Update or a packet with the 1619 Home Address option. 1620 Discontinuities in the value of this counter can occur at 1621 re-initialization of the management system, and at other times 1622 as indicated by the value of mip6CounterDiscontinuityTime. 1623 " 1624 REFERENCE 1625 "RFC3775 : Section 11.3.5" 1626 ::= { mip6MnRegnCounters 8 } 1628 mip6MnBRRequestsRecd OBJECT-TYPE 1629 SYNTAX Counter32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "The total number of Binding Refresh requests 1634 received by the mobile node from Corresponding nodes. 1635 Discontinuities in the value of this counter can occur at 1636 re-initialization of the management system, and at other times 1637 as indicated by the value of mip6CounterDiscontinuityTime. 1638 " 1639 REFERENCE 1640 "RFC3775 : Section 11.7.4" 1641 ::= { mip6MnRegnCounters 9 } 1643 -- Registration Group counters used for CN 1644 mip6CnGlobalStats OBJECT IDENTIFIER ::= { mip6CnStats 1 } 1646 mip6CnHomeTestInitsRecd OBJECT-TYPE 1647 SYNTAX Counter32 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "Total number of Home Test Init messages received. 1652 Discontinuities in the value of this counter can occur at 1653 re-initialization of the management system, and at other times 1654 as indicated by the value of mip6CounterDiscontinuityTime. 1655 " 1656 REFERENCE 1657 "RFC3775 : Section 9.4.1" 1658 ::= { mip6CnGlobalStats 1 } 1660 mip6CnHomeTestsSent OBJECT-TYPE 1661 SYNTAX Counter32 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION 1665 "Total number of Home Test messages sent. If a Home 1666 Test Init message is found to be valid, a Home Test 1667 message will be generated and sent. Otherwise the 1668 Home Test message is silently discarded. 1669 Discontinuities in the value of this counter can occur at 1670 re-initialization of the management system, and at other times 1671 as indicated by the value of mip6CounterDiscontinuityTime. 1672 " 1673 REFERENCE 1674 "RFC3775 : Section 9.4.3" 1675 ::= { mip6CnGlobalStats 2 } 1677 mip6CnCareOfTestInitsRecd OBJECT-TYPE 1678 SYNTAX Counter32 1679 MAX-ACCESS read-only 1680 STATUS current 1681 DESCRIPTION 1682 "Total number of Care-of Test Init messages received." 1683 REFERENCE 1684 "RFC3775 : Section 9.4.2" 1685 ::= { mip6CnGlobalStats 3 } 1687 mip6CnCareOfTestsSent OBJECT-TYPE 1688 SYNTAX Counter32 1689 MAX-ACCESS read-only 1690 STATUS current 1691 DESCRIPTION 1692 "Total number of Care-of Test messages sent. If a Care-of 1693 Test Init message is found to be valid, a Care-of Test 1694 message will be generated and sent. Otherwise the 1695 Care-of Test message is silently discarded. 1696 Discontinuities in the value of this counter can occur at 1697 re-initialization of the management system, and at other times 1698 as indicated by the value of mip6CounterDiscontinuityTime. 1699 " 1700 REFERENCE 1701 "RFC3775 : Section 9.4.4" 1702 ::= { mip6CnGlobalStats 4 } 1704 mip6CnBUsRecd OBJECT-TYPE 1705 SYNTAX Counter32 1706 MAX-ACCESS read-only 1707 STATUS current 1708 DESCRIPTION 1709 "Total number of Binding Updates received by the 1710 correspondent node from mobile nodes. 1711 Discontinuities in the value of this counter can occur at 1712 re-initialization of the management system, and at other times 1713 as indicated by the value of mip6CounterDiscontinuityTime. 1714 " 1715 REFERENCE 1716 "RFC3775 : Section 9.5.1" 1717 ::= { mip6CnGlobalStats 5 } 1719 mip6CnBUAcksSent OBJECT-TYPE 1720 SYNTAX Counter32 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "Total number of acknowledgments sent by the 1725 correspondent node for the Binding Updates received. 1726 Discontinuities in the value of this counter can occur at 1727 re-initialization of the management system, and at other times 1728 as indicated by the value of mip6CounterDiscontinuityTime. 1729 " 1730 REFERENCE 1731 "RFC3775 : Section 9.5.4" 1732 ::= { mip6CnGlobalStats 6 } 1734 mip6CnBRsSent OBJECT-TYPE 1735 SYNTAX Counter32 1736 MAX-ACCESS read-only 1737 STATUS current 1738 DESCRIPTION 1739 "Total number of Binding Refresh Request messages sent 1740 by the correspondent node. 1741 Discontinuities in the value of this counter can occur at 1742 re-initialization of the management system, and at other times 1743 as indicated by the value of mip6CounterDiscontinuityTime. 1744 " 1745 REFERENCE 1746 "RFC3775 : Section 9.5.5" 1747 ::= { mip6CnGlobalStats 7 } 1749 mip6CnBindingErrors OBJECT-TYPE 1750 SYNTAX Counter32 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "Total number of Binding Error messages sent by the 1755 correspondent node to the mobile node. 1756 Discontinuities in the value of this counter can occur at 1757 re-initialization of the management system, and at other times 1758 as indicated by the value of mip6CounterDiscontinuityTime. 1759 " 1760 REFERENCE 1761 "RFC3775 : Section 9.3.3" 1762 ::= { mip6CnGlobalStats 8 } 1764 mip6CnBUsAccepted OBJECT-TYPE 1765 SYNTAX Counter32 1766 MAX-ACCESS read-only 1767 STATUS current 1768 DESCRIPTION 1769 "Total number of Binding Updates accepted by the 1770 correspondent node. If a Binding Acknowledgment 1771 message is sent for the Binding Update request, 1772 the Status code field in the message will have 1773 a value less than 128. 1774 Discontinuities in the value of this counter can occur at 1775 re-initialization of the management system, and at other times 1776 as indicated by the value of mip6CounterDiscontinuityTime. 1777 " 1778 ::= { mip6CnGlobalStats 9 } 1780 mip6CnBUsRejected OBJECT-TYPE 1781 SYNTAX Counter32 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "Total number of Binding Update requests rejected 1786 by the correspondent node. If a Binding 1787 Acknowledgment message has been sent for the Binding 1788 Update request, the Status code field in the 1789 message will have a value grather than or equal to 1790 128. Otherwise the Binding Update request has been 1791 silently discarded. 1792 Discontinuities in the value of this counter can occur at 1793 re-initialization of the management system, and at other times 1794 as indicated by the value of mip6CounterDiscontinuityTime. 1795 " 1796 REFERENCE 1797 "RFC3775 : Section 9.5.1" 1798 ::= { mip6CnGlobalStats 10 } 1800 mip6CnReasonUnspecified OBJECT-TYPE 1801 SYNTAX Counter32 1802 MAX-ACCESS read-only 1803 STATUS current 1804 DESCRIPTION 1805 "Total number of Binding Update requests rejected by 1806 the correspondent node with status code in the Binding 1807 Acknowledgement message indicating 'reason unspecified' 1808 (Code 128). 1809 Discontinuities in the value of this counter can occur at 1810 re-initialization of the management system, and at other times 1811 as indicated by the value of mip6CounterDiscontinuityTime. 1812 " 1813 REFERENCE 1814 "RFC3775 : Section 6.1.8" 1815 ::= { mip6CnGlobalStats 11 } 1817 mip6CnInsufficientResource OBJECT-TYPE 1818 SYNTAX Counter32 1819 MAX-ACCESS read-only 1820 STATUS current 1821 DESCRIPTION 1822 "Total number of Binding Update requests rejected by 1823 the correspondent node with status code in the Binding 1824 Acknowledgement message indicating 'insufficient 1825 resources' (Code 130). 1826 Discontinuities in the value of this counter can occur at 1827 re-initialization of the management system, and at other times 1828 as indicated by the value of mip6CounterDiscontinuityTime. 1829 " 1830 REFERENCE 1831 "RFC3775 : Section 6.1.8" 1832 ::= { mip6CnGlobalStats 12 } 1834 mip6CnHomeRegnNotSupported OBJECT-TYPE 1835 SYNTAX Counter32 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION 1839 "Total number of Binding Update requests rejected by 1840 correspondent node with status code in the Binding 1841 Acknowledgement message indicating 'home registration 1842 not supported' (Code 131). 1843 Discontinuities in the value of this counter can occur at 1844 re-initialization of the management system, and at other times 1845 as indicated by the value of mip6CounterDiscontinuityTime. 1846 " 1847 REFERENCE 1848 "RFC3775 : Section 10.3.1" 1849 ::= { mip6CnGlobalStats 13 } 1851 mip6CnSeqNumberOutOfWindow OBJECT-TYPE 1852 SYNTAX Counter32 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "Total number of Binding Updates rejected by 1857 correspondent node with status code in the Binding 1858 Acknowledgement message indicating 'sequence number 1859 out of window' (Code 135). 1860 Discontinuities in the value of this counter can occur at 1861 re-initialization of the management system, and at other times 1862 as indicated by the value of mip6CounterDiscontinuityTime. 1863 " 1864 REFERENCE 1865 "RFC3775 : Section 6.1.8 9.5.1" 1866 ::= { mip6CnGlobalStats 14 } 1868 mip6CnExpiredHomeNonceIndex OBJECT-TYPE 1869 SYNTAX Counter32 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "The total number of Binding Updates rejected by 1874 correspondent node with status code in the Binding 1875 Acknowledgement message indicating 'expired home nonce 1876 index' (Code 136). 1877 Discontinuities in the value of this counter can occur at 1878 re-initialization of the management system, and at other times 1879 as indicated by the value of mip6CounterDiscontinuityTime. 1880 " 1881 REFERENCE 1882 "RFC3775 : Section 6.1.8 9.5.1" 1883 ::= { mip6CnGlobalStats 15 } 1885 mip6CnExpiredCareOfNonceIndex OBJECT-TYPE 1886 SYNTAX Counter32 1887 MAX-ACCESS read-only 1888 STATUS current 1889 DESCRIPTION 1890 "The total number of Binding Updates rejected by 1891 correspondent node with status code in the Binding 1892 Acknowledgement message indicating 'expired 1893 care-of nonce index' (Code 137). 1894 Discontinuities in the value of this counter can occur at 1895 re-initialization of the management system, and at other times 1896 as indicated by the value of mip6CounterDiscontinuityTime. 1897 " 1898 REFERENCE 1899 "RFC3775 : Section 6.1.8 9.5.1" 1900 ::= { mip6CnGlobalStats 16 } 1902 mip6CnExpiredNonce OBJECT-TYPE 1903 SYNTAX Counter32 1904 MAX-ACCESS read-only 1905 STATUS current 1906 DESCRIPTION 1907 "The total number of Binding Updates rejected by 1908 correspondent node with status code in the Binding 1909 Acknowledgement message indicating 'expired nonces' 1910 (Code 138) i.e. the correspondent node no longer 1911 recognizes the Home Nonce Index value and the Care-of 1912 Nonce Index value. 1913 Discontinuities in the value of this counter can occur at 1914 re-initialization of the management system, and at other times 1915 as indicated by the value of mip6CounterDiscontinuityTime. 1916 " 1917 REFERENCE 1918 "RFC3775 : Section 6.1.8 9.5.1" 1919 ::= { mip6CnGlobalStats 17 } 1921 mip6CnRegTypeChangeDisallowed OBJECT-TYPE 1922 SYNTAX Counter32 1923 MAX-ACCESS read-only 1924 STATUS current 1925 DESCRIPTION 1926 "The total number of Binding Updates rejected by 1927 correspondent node with status code in the Binding 1928 Acknowledgement message indicating 'registration type 1929 change disallowed' (Code 139 i.e. a binding already 1930 exists for the given home address and the home registration 1931 flag has a different value than the Home Registration 1932 (H) bit in the Binding Update. 1933 Discontinuities in the value of this counter can occur at 1934 re-initialization of the management system, and at other times 1935 as indicated by the value of mip6CounterDiscontinuityTime. 1936 " 1937 REFERENCE 1938 "RFC3775 : Section 6.1.8 9.5.1" 1939 ::= { mip6CnGlobalStats 18 } 1941 -- The Correspondent Node statistics by mobile node 1943 mip6CnCounterTable OBJECT-TYPE 1944 SYNTAX SEQUENCE OF CnCounterEntry 1945 MAX-ACCESS not-accessible 1946 STATUS current 1947 DESCRIPTION 1948 "A table containing each mobile ." 1949 ::= { mip6CnStats 2 } 1951 mip6CnCounterEntry OBJECT-TYPE 1952 SYNTAX CnCounterEntry 1953 MAX-ACCESS not-accessible 1954 STATUS current 1955 DESCRIPTION 1956 "The set of CN counters for a mobile node." 1957 INDEX { mip6BindingHomeAddressType, 1958 mip6BindingHomeAddress 1959 } 1960 ::= { mip6CnCounterTable 1 } 1962 CnCounterEntry ::= 1963 SEQUENCE { 1964 mip6CnBURequestsAccepted Counter32, 1965 mip6CnBURequestsRejected Counter32, 1966 mip6CnBCEntryCreationTime DateAndTime, 1967 mip6CnBUAcceptedTime DateAndTime, 1968 mip6CnBURejectionTime DateAndTime, 1969 mip6CnBURejectionCode Mipv6BURequestRejectionCode, 1970 mip6CnCtrDiscontinuityTime TimeStamp 1971 } 1973 mip6CnBURequestsAccepted OBJECT-TYPE --(Code 0,1) 1974 SYNTAX Counter32 1975 MAX-ACCESS read-only 1976 STATUS current 1977 DESCRIPTION 1978 "Total number of Binding Update requests from the mobile 1979 node accepted by the correspondent node. 1980 If Binding Acknowledgement messages are sent then the 1981 Status code in the message will have a value less than 1982 128. 1983 Discontinuities in the value of this counter can occur at 1984 re-initialization of the management system, and at other times 1985 as indicated by the value of mip6CnCtrDiscontinuityTime. 1986 " 1987 ::= { mip6CnCounterEntry 1 } 1989 mip6CnBURequestsRejected OBJECT-TYPE 1990 -- (Code 128 through Code 159) 1991 SYNTAX Counter32 1992 MAX-ACCESS read-only 1993 STATUS current 1994 DESCRIPTION 1995 "Total number of Binding Update requests from the mobile 1996 node which have been rejected by the corespondent node. 1997 This includes the Binding Update requests for which 1998 a Binding Acknowledgment message has been sent with 1999 Status code value greater than or equal to 128 and the 2000 Binding Acknowledgment requests which have been silently 2001 discarded. 2002 Discontinuities in the value of this counter can occur at 2003 re-initialization of the management system, and at other times 2004 as indicated by the value of mip6CnCtrDiscontinuityTime. 2005 " 2006 ::= { mip6CnCounterEntry 2 } 2008 mip6CnBCEntryCreationTime OBJECT-TYPE 2009 SYNTAX DateAndTime 2010 MAX-ACCESS read-only 2011 STATUS current 2012 DESCRIPTION 2013 "The time when the current Binding Cache entry was created 2014 for the mobile node. 2015 " 2016 ::= { mip6CnCounterEntry 3 } 2018 mip6CnBUAcceptedTime OBJECT-TYPE 2019 SYNTAX DateAndTime 2020 MAX-ACCESS read-only 2021 STATUS current 2022 DESCRIPTION 2023 "The time at which the last Binding Update was accepted by 2024 the corespondent node and the corresponding Binding Cache 2025 entry was updated. 2026 " 2027 ::= { mip6CnCounterEntry 4 } 2029 mip6CnBURejectionTime OBJECT-TYPE 2030 SYNTAX DateAndTime 2031 MAX-ACCESS read-only 2032 STATUS current 2033 DESCRIPTION 2034 "The time at which the last Binding Update message was 2035 rejected by the corespondent node. 2036 If there have been no rejections then this object will 2037 be inaccessible. 2038 " 2039 ::= { mip6CnCounterEntry 5 } 2041 mip6CnBURejectionCode OBJECT-TYPE 2042 SYNTAX Mipv6BURequestRejectionCode 2043 MAX-ACCESS read-only 2044 STATUS current 2045 DESCRIPTION 2046 "If a Binding Acknowledgment is sent to the mobile node, 2047 this is the Status code (> 128) that is returned in the 2048 Binding Acknowledgment. 2049 In case a Binding Acknowledgment is not sent to the mobile 2050 node then this will be the value that of the Status code 2051 that corresponds to the reason of the rejection. 2052 If there have been no rejections then this object will 2053 be inaccessible. 2054 " 2055 REFERENCE 2056 "RFC3775 : Section 6.1.8" 2058 ::= { mip6CnCounterEntry 6 } 2060 mip6CnCtrDiscontinuityTime OBJECT-TYPE 2061 SYNTAX TimeStamp 2062 MAX-ACCESS read-only 2063 STATUS current 2064 DESCRIPTION 2065 "The value of sysUpTime on the most recent occasion at which 2066 any one or more of counters in this row viz, instances of 2067 'mip6CnBURequestsAccepted' and 'mip6CnBURequestsRejected' 2068 suffered a discontinuity. 2069 If no such discontinuities have occurred since the last re- 2070 initialization of the local management subsystem, then this 2071 object will have a zero value. 2073 " 2074 ::= { mip6CnCounterEntry 7 } 2076 -- Home agent group 2078 mip6HaAdvsRecd OBJECT-TYPE 2079 SYNTAX Counter32 2080 MAX-ACCESS read-only 2081 STATUS current 2082 DESCRIPTION 2083 "Total number of valid Router Advertisements 2084 received with the Home Agent (H) bit set, on 2085 all the links on which it is serving as a Home 2086 Agent. 2087 " 2088 REFERENCE 2089 "RFC3775 : Section 6.1.8 9.5.1" 2090 ::= { mip6HaAdvertisement 1 } 2092 mip6HaAdvsSent OBJECT-TYPE 2093 SYNTAX Counter32 2094 MAX-ACCESS read-only 2095 STATUS current 2096 DESCRIPTION 2097 "Total number of unsolicited multicast Router Advertisements 2098 sent with the Home Agent (H) bit set, on all the links on 2099 which the router is serving as a Home Agent. 2100 " 2101 REFERENCE 2102 "RFC3775 : Section 6.1.8 9.5.1" 2103 ::= { mip6HaAdvertisement 2 } 2105 mip6HaConfTable OBJECT-TYPE 2106 SYNTAX SEQUENCE OF Mipv6HaConfEntry 2107 MAX-ACCESS not-accessible 2108 STATUS current 2109 DESCRIPTION 2110 "A table containing configurable advertisement 2111 parameters for all interfaces on which the 2112 which the home agent service is advertised. 2113 " 2114 ::= { mip6HaAdvertisement 3 } 2116 mip6HaConfEntry OBJECT-TYPE 2117 SYNTAX Mipv6HaConfEntry 2118 MAX-ACCESS not-accessible 2119 STATUS current 2120 DESCRIPTION 2121 "Advertisement parameters for one advertisement 2122 interface. 2123 " 2124 INDEX { ipv6IfIndex } 2125 ::= { mip6HaConfTable 1 } 2127 Mipv6HaConfEntry ::= SEQUENCE { 2128 mip6HaAdvPreference Integer32, 2129 mip6HaAdvLifetime Integer32, 2130 mip6HaPrefixAdv INTEGER, 2131 mip6HaPrefixSolicitation INTEGER, 2132 mip6HaMCastCtlMsgSupport INTEGER 2133 } 2135 mip6HaAdvPreference OBJECT-TYPE 2136 SYNTAX Integer32 (0..65536) 2137 MAX-ACCESS read-write 2138 STATUS current 2139 DESCRIPTION 2140 "The preference value for the home agent to 2141 be used in the Router Advertisements. Higher 2142 value denotes greater preference. 2143 " 2144 REFERENCE 2145 "RFC3775 : Section 7.4, 8.4" 2146 ::= { mip6HaConfEntry 1 } 2148 mip6HaAdvLifetime OBJECT-TYPE 2149 SYNTAX Integer32 (1..65535) 2150 UNITS "seconds" 2151 MAX-ACCESS read-write 2152 STATUS current 2153 DESCRIPTION 2154 "The lifetime value for the home agent to be 2155 used in the Router Advertisements. 2156 " 2157 REFERENCE 2158 "RFC3775 : Section 7.4" 2159 ::= { mip6HaConfEntry 2 } 2161 mip6HaPrefixAdv OBJECT-TYPE 2162 SYNTAX INTEGER { enabled(1), disabled(2) } 2163 MAX-ACCESS read-write 2164 STATUS current 2165 DESCRIPTION 2166 "Indicates whether the home agent should support 2167 sending of the ICMP Mobile Prefix Advertisements. 2168 If it is disabled, the home agent will not send 2169 ICMP Mobile Prefix Advertisements to the mobile 2170 nodes." 2171 REFERENCE 2172 "RFC3775 : Section 8.4" 2173 ::= { mip6HaConfEntry 3} 2175 mip6HaPrefixSolicitation OBJECT-TYPE 2176 SYNTAX INTEGER { enabled(1), disabled(2) } 2177 MAX-ACCESS read-write 2178 STATUS current 2179 DESCRIPTION 2180 "Indicates whether the home agent should respond 2181 to ICMP Mobile Prefix Solicitation messages from 2182 mobile nodes. If it is disabled, 2183 the home agent will not respond to any ICMP 2184 Mobile Prefix Solicitation messages it received 2185 from the mobile node." 2186 REFERENCE 2187 "RFC3775 : Section 8.4" 2188 ::= { mip6HaConfEntry 4} 2190 mip6HaMCastCtlMsgSupport OBJECT-TYPE 2191 SYNTAX INTEGER { enabled(1), disabled(2) } 2192 MAX-ACCESS read-write 2193 STATUS current 2194 DESCRIPTION 2195 "Indicates whether the home agent should enable 2196 support for the processing of the multicast group 2197 membership control messages it received from the 2198 mobile nodes. If it is disabled, the home agent will 2199 silently ignore the multicast group control messages 2200 it received from the mobile nodes." 2201 REFERENCE 2202 "RFC3775 : Section 10.4.3" 2203 ::= { mip6HaConfEntry 5} 2205 -- Registration Group counters HA 2207 mip6HaGlobalStats OBJECT IDENTIFIER ::= { mip6HaStats 1 } 2209 mip6HaHomeTestInitsRecd OBJECT-TYPE 2210 SYNTAX Counter32 2211 MAX-ACCESS read-only 2212 STATUS current 2213 DESCRIPTION 2214 "Total number of Home Test Init messages received by 2215 the home agent. This will include Home Test Init messages 2216 that failed the validity checks. 2217 Discontinuities in the value of this counter can occur at 2218 re-initialization of the management system, and at other times 2219 as indicated by the value of mip6CounterDiscontinuityTime. 2220 " 2221 REFERENCE 2222 "RFC3775 : Section 5.2.5" 2223 ::= { mip6HaGlobalStats 1 } 2225 mip6HaHomeTestsSent OBJECT-TYPE 2226 SYNTAX Counter32 2227 MAX-ACCESS read-only 2228 STATUS current 2229 DESCRIPTION 2230 "Total number of Home Test messages sent by the 2231 home agent. 2232 Discontinuities in the value of this counter can occur at 2233 re-initialization of the management system, and at other times 2234 as indicated by the value of mip6CounterDiscontinuityTime. 2235 " 2236 REFERENCE 2237 "RFC3775 : Section 5.2.5" 2238 ::= { mip6HaGlobalStats 2 } 2240 mip6HaBUsRecd OBJECT-TYPE 2241 SYNTAX Counter32 2242 MAX-ACCESS read-only 2243 STATUS current 2244 DESCRIPTION 2245 "Total nubmer of Binding Updates received by the 2246 home agent. 2247 Discontinuities in the value of this counter can occur at 2248 re-initialization of the management system, and at other times 2249 as indicated by the value of mip6CounterDiscontinuityTime. 2250 " 2251 REFERENCE 2252 "RFC3775 : Section 10.3.1" 2253 ::= { mip6HaGlobalStats 3 } 2255 mip6HaBUAcksSent OBJECT-TYPE 2256 SYNTAX Counter32 2257 MAX-ACCESS read-only 2258 STATUS current 2259 DESCRIPTION 2260 "Total number of Binding Acknowledgements sent 2261 by the home agent. 2262 Discontinuities in the value of this counter can occur at 2263 re-initialization of the management system, and at other times 2264 as indicated by the value of mip6CounterDiscontinuityTime. 2265 " 2266 REFERENCE 2267 "RFC3775 : Section 10.3.1" 2268 ::= { mip6HaGlobalStats 4 } 2270 mip6HaBRAdviceSent OBJECT-TYPE 2271 SYNTAX Counter32 2272 MAX-ACCESS read-only 2273 STATUS current 2274 DESCRIPTION 2275 "Total number of Binding Acknowledgements sent 2276 by the home agent with Binding Refresh Advice 2277 mobility option included. 2278 Discontinuities in the value of this counter can occur at 2279 re-initialization of the management system, and at other times 2280 as indicated by the value of mip6CounterDiscontinuityTime. 2281 " 2282 REFERENCE 2283 "RFC3775 : Section 10.3.1" 2284 ::= { mip6HaGlobalStats 5 } 2286 mip6HaBUsAccepted OBJECT-TYPE 2287 SYNTAX Counter32 2288 MAX-ACCESS read-only 2289 STATUS current 2290 DESCRIPTION 2291 "Total number of Binding Updates accepted by this HA. 2292 Binding Acknowledgment with Status code of 0 or 1. 2293 Discontinuities in the value of this counter can occur at 2294 re-initialization of the management system, and at other times 2295 as indicated by the value of mip6CounterDiscontinuityTime. 2296 " 2297 REFERENCE 2298 "RFC3775 : Section 10.3.1" 2299 ::= { mip6HaGlobalStats 6 } 2301 mip6HaPrefDiscoverReqd OBJECT-TYPE -- (Code 1) 2302 SYNTAX Counter32 2303 MAX-ACCESS read-only 2304 STATUS current 2305 DESCRIPTION 2306 "The total number of Binding Acknowledgments sent the 2307 home agent with Status code indicating 'accepted but 2308 prefix discovery necessary' (Code 1). 2310 Discontinuities in the value of this counter can occur at 2311 re-initialization of the management system, and at other times 2312 as indicated by the value of mip6CounterDiscontinuityTime. 2313 " 2314 REFERENCE 2315 "RFC3775 : Section 10.3.1" 2316 ::= { mip6HaGlobalStats 7 } 2318 mip6HaReasonUnspecified OBJECT-TYPE -- (Code 128) 2319 SYNTAX Counter32 2320 MAX-ACCESS read-only 2321 STATUS current 2322 DESCRIPTION 2323 "Total number of Binding Update requests rejected by 2324 the home agent with status code in the Binding 2325 Acknowledgement message indicating 'reason unspecified' 2326 (Code 128). 2327 Discontinuities in the value of this counter can occur at 2328 re-initialization of the management system, and at other times 2329 as indicated by the value of mip6CounterDiscontinuityTime. 2330 " 2331 REFERENCE 2332 "RFC3775 : Section 10.3.1" 2333 ::= { mip6HaGlobalStats 8 } 2335 mip6HaAdmProhibited OBJECT-TYPE 2336 SYNTAX Counter32 2337 MAX-ACCESS read-only 2338 STATUS current 2339 DESCRIPTION 2340 "Total number of Binding Update requests rejected by 2341 the home agent with status code in the Binding 2342 Acknowledgement message indicating 'administratively 2343 prohibited' (Code 129). 2344 Discontinuities in the value of this counter can occur at 2345 re-initialization of the management system, and at other times 2346 as indicated by the value of mip6CounterDiscontinuityTime. 2347 " 2348 REFERENCE 2349 "RFC3775 : Section 10.3.1" 2350 ::= { mip6HaGlobalStats 9 } 2352 mip6HaInsufficientResource OBJECT-TYPE -- (Code 130) 2353 SYNTAX Counter32 2354 MAX-ACCESS read-only 2355 STATUS current 2356 DESCRIPTION 2357 "Total number of Binding Update requests rejected by 2358 the home agent with status code in the Binding 2359 Acknowledgement message indicating 'insufficient 2360 resources' (Code 130). 2361 Discontinuities in the value of this counter can occur at 2362 re-initialization of the management system, and at other times 2363 as indicated by the value of mip6CounterDiscontinuityTime. 2364 " 2365 REFERENCE 2366 "RFC3775 : Section 9.5.2" 2367 ::= { mip6HaGlobalStats 10 } 2369 mip6HaHomeRegnNotSupported OBJECT-TYPE -- (Code 131) 2370 SYNTAX Counter32 2371 MAX-ACCESS read-only 2372 STATUS current 2373 DESCRIPTION 2374 "Total number of Binding Update requests rejected by 2375 the home agent with status code in the Binding 2376 Acknowledgement message indicating 'home registration 2377 not supported' (Code 131). 2378 Discontinuities in the value of this counter can occur at 2379 re-initialization of the management system, and at other times 2380 as indicated by the value of mip6CounterDiscontinuityTime. 2381 " 2382 REFERENCE 2383 "RFC3775 : Section 10.3.1" 2384 ::= { mip6HaGlobalStats 11 } 2386 mip6HaNotHomeSubnet OBJECT-TYPE -- (Code 132) 2387 SYNTAX Counter32 2388 MAX-ACCESS read-only 2389 STATUS current 2390 DESCRIPTION 2391 "Total number of Binding Update requests rejected by 2392 the home agent with status code in the Binding 2393 Acknowledgement message indicating 'not home subnet' 2394 (Code 132). 2395 Discontinuities in the value of this counter can occur at 2396 re-initialization of the management system, and at other times 2397 as indicated by the value of mip6CounterDiscontinuityTime. 2398 " 2399 REFERENCE 2400 "RFC3775 : Section 10.3.1" 2401 ::= { mip6HaGlobalStats 12 } 2403 mip6HaNotHomeAgentForThisMN OBJECT-TYPE -- (Code 133) 2404 SYNTAX Counter32 2405 MAX-ACCESS read-only 2406 STATUS current 2407 DESCRIPTION 2408 "Total number of Binding Update requests rejected by 2409 the home agent with status code in the Binding 2410 Acknowledgement message indicating 'not home agent 2411 for this mobile node' (Code 133). 2412 Discontinuities in the value of this counter can occur at 2413 re-initialization of the management system, and at other times 2414 as indicated by the value of mip6CounterDiscontinuityTime. 2415 " 2416 REFERENCE 2417 "RFC3775 : Section 10.3.2" 2418 ::= { mip6HaGlobalStats 13 } 2420 mip6HaDupAddrDetectionFailed OBJECT-TYPE -- (Code 134) 2421 SYNTAX Counter32 2422 MAX-ACCESS read-only 2423 STATUS current 2424 DESCRIPTION 2425 "Total number of Binding Update requests rejected by 2426 the home agent with status code in the Binding 2427 Acknowledgement message indicating 'Duplicate Address 2428 Detection failed' (Code 134). 2429 Discontinuities in the value of this counter can occur at 2430 re-initialization of the management system, and at other times 2431 as indicated by the value of mip6CounterDiscontinuityTime. 2432 " 2433 REFERENCE 2434 "RFC3775 : Section 10.3.1" 2435 ::= { mip6HaGlobalStats 14 } 2437 mip6HaSeqNumberOutOfWindow OBJECT-TYPE -- (Code 135) 2438 SYNTAX Counter32 2439 MAX-ACCESS read-only 2440 STATUS current 2441 DESCRIPTION 2442 "Total number of Binding Update requests rejected by 2443 the home agent with status code in the Binding 2444 Acknowledgement message indicating 'sequence number 2445 out of window' (Code 135). 2446 Discontinuities in the value of this counter can occur at 2447 re-initialization of the management system, and at other times 2448 as indicated by the value of mip6CounterDiscontinuityTime. 2449 " 2450 REFERENCE 2451 "RFC3775 : Section 9.5.1" 2452 ::= { mip6HaGlobalStats 15 } 2454 mip6HaExpiredHomeNonceIndex OBJECT-TYPE -- (Code 136) 2455 SYNTAX Counter32 2456 MAX-ACCESS read-only 2457 STATUS current 2458 DESCRIPTION 2459 "Total number of Binding Update requests rejected by 2460 the home agent with status code in the Binding 2461 Acknowledgement message indicating 'expired home 2462 nonce index' (Code 136). 2463 Discontinuities in the value of this counter can occur at 2464 re-initialization of the management system, and at other times 2465 as indicated by the value of mip6CounterDiscontinuityTime. 2466 " 2467 REFERENCE 2468 "RFC3775 : Section 9.5.1" 2469 ::= { mip6HaGlobalStats 16 } 2471 mip6HaRegTypeChangeDisallowed OBJECT-TYPE -- (Code 139) 2472 SYNTAX Counter32 2473 MAX-ACCESS read-only 2474 STATUS current 2475 DESCRIPTION 2476 "Total number of Binding Update requests rejected by 2477 the home agent with status code in the Binding 2478 Acknowledgement message indicating 'registration type 2479 change disallowed' (Code 139) i.e. a binding already 2480 exists for the given home address and the home registration 2481 flag has a different value than the Home Registration 2482 (H) bit in the Binding Update. 2483 Discontinuities in the value of this counter can occur at 2484 re-initialization of the management system, and at other times 2485 as indicated by the value of mip6CounterDiscontinuityTime. 2486 " 2487 REFERENCE 2488 "RFC3775 : Section 9.5.1" 2489 ::= { mip6HaGlobalStats 17 } 2491 -- Home agent registration Counters per node 2493 mip6HaCounterTable OBJECT-TYPE 2494 SYNTAX SEQUENCE OF HaCounterEntry 2495 MAX-ACCESS not-accessible 2496 STATUS current 2497 DESCRIPTION 2498 "A table containing registration statistics for all 2499 mobile nodes registered with the home agent. 2500 " 2501 ::= { mip6HaStats 2 } 2503 mip6HaCounterEntry OBJECT-TYPE 2504 SYNTAX HaCounterEntry 2505 MAX-ACCESS not-accessible 2506 STATUS current 2507 DESCRIPTION 2508 "Home agent registration statistics for a mobile node." 2509 INDEX { mip6BindingHomeAddressType, 2510 mip6BindingHomeAddress 2511 } 2512 ::= { mip6HaCounterTable 1 } 2514 HaCounterEntry ::= SEQUENCE { 2515 mip6HaBURequestsAccepted Counter32, 2516 mip6HaBURequestsDenied Counter32, 2517 mip6HaBCEntryCreationTime DateAndTime, 2518 mip6HaBUAcceptedTime DateAndTime, 2519 mip6HaBURejectionTime DateAndTime, 2520 mip6HaRecentBURejectionCode Mipv6BURequestRejectionCode, 2521 mip6HaCtrDiscontinuityTime TimeStamp 2522 } 2524 mip6HaBURequestsAccepted OBJECT-TYPE 2525 SYNTAX Counter32 2526 MAX-ACCESS read-only 2527 STATUS current 2528 DESCRIPTION 2529 "Total number of service requests for the mobile node 2530 accepted by the home agent. 2531 Discontinuities in the value of this counter can occur at 2532 re-initialization of the management system, and at other times 2533 as indicated by the value of mip6HaCtrDiscontinuityTime. 2534 " 2535 ::= { mip6HaCounterEntry 1 } 2537 mip6HaBURequestsDenied OBJECT-TYPE 2538 SYNTAX Counter32 2539 MAX-ACCESS read-only 2540 STATUS current 2541 DESCRIPTION 2542 "Total number of service requests for the mobile node 2543 rejected by the home agent. 2544 Discontinuities in the value of this counter can occur at 2545 re-initialization of the management system, and at other times 2546 as indicated by the value of mip6HaCtrDiscontinuityTime. 2547 " 2548 ::= { mip6HaCounterEntry 2 } 2550 mip6HaBCEntryCreationTime OBJECT-TYPE 2551 SYNTAX DateAndTime 2552 UNITS "seconds" 2553 MAX-ACCESS read-only 2554 STATUS current 2555 DESCRIPTION 2556 "The time when the current Binding Cache entry was 2557 created for the mobile node. 2558 " 2559 ::= { mip6HaCounterEntry 3 } 2561 mip6HaBUAcceptedTime OBJECT-TYPE 2562 SYNTAX DateAndTime 2563 MAX-ACCESS read-only 2564 STATUS current 2565 DESCRIPTION 2566 "The time at which the last Binding Update was accepted 2567 by the home agent for this mobile node. 2568 " 2569 ::= { mip6HaCounterEntry 4 } 2571 mip6HaBURejectionTime OBJECT-TYPE 2572 SYNTAX DateAndTime 2573 MAX-ACCESS read-only 2574 STATUS current 2575 DESCRIPTION 2576 "The time at which the last Binding Update was rejected 2577 by the home agent for this mobile node. 2578 If there have been no rejections then this object will 2579 be inaccessible. 2580 " 2581 ::= { mip6HaCounterEntry 5 } 2583 mip6HaRecentBURejectionCode OBJECT-TYPE 2584 SYNTAX Mipv6BURequestRejectionCode 2585 MAX-ACCESS read-only 2586 STATUS current 2587 DESCRIPTION 2588 "If a Binding Acknowledgment is sent to the mobile node, 2589 this is the Status code (> 128) that is returned in the 2590 Binding Acknowledgment. 2591 In case a Binding Acknowledgment is not sent to the mobile 2592 node then this will be the value that of the Status code 2593 that corresponds to the reason of the rejection. 2594 If there have been no rejections then this object will 2595 be inaccessible. 2596 " 2597 ::= { mip6HaCounterEntry 6 } 2599 mip6HaCtrDiscontinuityTime OBJECT-TYPE 2600 SYNTAX TimeStamp 2601 MAX-ACCESS read-only 2602 STATUS current 2603 DESCRIPTION 2604 "The value of sysUpTime on the most recent occasion at which 2605 any one or more of counters in this row viz, instances of 2606 'mip6HaBURequestsAccepted' and 'mip6HaBURequestsRejected' 2607 suffered a discontinuity. 2608 If no such discontinuities have occurred since the last re- 2609 initialization of the local management subsystem, then this 2610 object will have a zero value. 2611 " 2612 ::= { mip6HaCounterEntry 7 } 2614 -- Home Agent List Table 2616 mip6HaListTable OBJECT-TYPE 2617 SYNTAX SEQUENCE OF Mipv6HaListEntry 2618 MAX-ACCESS not-accessible 2619 STATUS current 2620 DESCRIPTION 2621 "This table models the Home Agents List that contains 2622 the list of all routers that are acting as home agents 2623 on each of the interfaces on which the home agent 2624 service is offered by this router. 2625 " 2626 REFERENCE 2627 "RFC3775 : Section 10.1" 2628 ::= { mip6HaAdvertisement 4 } 2630 mip6HaListEntry OBJECT-TYPE 2631 SYNTAX Mipv6HaListEntry 2632 MAX-ACCESS not-accessible 2633 STATUS current 2634 DESCRIPTION 2635 "Information about a router that is offering home 2636 agent service. 2637 " 2638 INDEX { ipv6IfIndex, mip6HaLinkLocalAddressType, 2639 mip6HaLinkLocalAddressType } 2640 ::= { mip6HaListTable 1 } 2642 Mipv6HaListEntry ::= SEQUENCE { 2643 mip6HaLinkLocalAddressType InetAddressType, 2644 mip6HaLinkLocalAddress InetAddress, 2645 mip6HaPreference Integer32, 2646 mip6HaRecvLifeTime Gauge32, 2647 mip6HaRecvTimeStamp DateAndTime 2648 } 2650 mip6HaLinkLocalAddressType OBJECT-TYPE 2651 SYNTAX InetAddressType 2652 MAX-ACCESS not-accessible 2653 STATUS current 2654 DESCRIPTION 2655 "The address type for the link-local address 2656 of the home agent that follows. 2657 " 2658 REFERENCE 2659 "RFC3775 : Section 10.1" 2660 ::= { mip6HaListEntry 1 } 2662 mip6HaLinkLocalAddress OBJECT-TYPE 2663 SYNTAX InetAddress 2664 MAX-ACCESS not-accessible 2665 STATUS current 2666 DESCRIPTION 2667 "The link local address of the home agent . 2668 " 2669 REFERENCE 2670 "RFC3775 : Section 10.1" 2671 ::= { mip6HaListEntry 2 } 2673 mip6HaPreference OBJECT-TYPE 2674 SYNTAX Integer32 2675 MAX-ACCESS read-only 2676 STATUS current 2677 DESCRIPTION 2678 "The preference value of this home agent. 2679 Higher values indicate a more preferable home 2680 agent. The preference value is obtained from 2681 the preference field of the received Router 2682 Advertisement. 2683 " 2684 REFERENCE 2685 "RFC3775 : Section 10.1" 2686 ::= { mip6HaListEntry 3 } 2688 mip6HaRecvLifeTime OBJECT-TYPE 2689 SYNTAX Gauge32 2690 MAX-ACCESS read-only 2691 STATUS current 2692 DESCRIPTION 2693 "The lifetime for this home agent. 2694 " 2696 REFERENCE 2697 "RFC3775 : Section 10.1" 2698 ::= { mip6HaListEntry 4 } 2700 mip6HaRecvTimeStamp OBJECT-TYPE 2701 SYNTAX DateAndTime 2702 MAX-ACCESS read-only 2703 STATUS current 2704 DESCRIPTION 2705 "The time when the home agent advertisement was received. 2706 " 2707 ::= { mip6HaListEntry 5 } 2709 -- 2710 -- The list of global addresses of a home agent in the 2711 -- home agent list 2712 -- 2714 mip6HaGlAddrTable OBJECT-TYPE 2715 SYNTAX SEQUENCE OF Mipv6HaGlAddrEntry 2716 MAX-ACCESS not-accessible 2717 STATUS current 2718 DESCRIPTION 2719 "This table contains the global addresses of the home 2720 agents in the Home Agents List. 2721 " 2722 REFERENCE 2723 "RFC3775 : Section 10.1" 2724 ::= { mip6HaAdvertisement 5 } 2726 mip6HaGlAddrEntry OBJECT-TYPE 2727 SYNTAX Mipv6HaGlAddrEntry 2728 MAX-ACCESS not-accessible 2729 STATUS current 2730 DESCRIPTION 2731 "A global address for a home agent in the Home Agents List. 2732 " 2733 INDEX { ipv6IfIndex, mip6HaLinkLocalAddressType, 2734 mip6HaLinkLocalAddressType, mip6HaGaAddrSeqNo } 2735 ::= { mip6HaGlAddrTable 1 } 2737 Mipv6HaGlAddrEntry ::= SEQUENCE { 2738 mip6HaGaAddrSeqNo Integer32, 2739 mip6HaGaGlobalAddressType InetAddressType, 2740 mip6HaGaGlobalAddress InetAddress 2741 } 2742 mip6HaGaAddrSeqNo OBJECT-TYPE 2743 SYNTAX Integer32 (1..1024) -- put the max value GYM 2744 MAX-ACCESS not-accessible 2745 STATUS current 2746 DESCRIPTION 2747 "The index that along with ipv6IfIndex, mip6HaLinkLocalAddressType 2748 and mip6HaLinkLocalAddressType uniquely identifies this row. 2749 " 2750 REFERENCE 2751 "RFC3775 : Section 10.1" 2752 ::= { mip6HaGlAddrEntry 1 } 2754 mip6HaGaGlobalAddressType OBJECT-TYPE 2755 SYNTAX InetAddressType 2756 MAX-ACCESS read-only 2757 STATUS current 2758 DESCRIPTION 2759 "The address type for the global address of the 2760 home agent that follows. 2761 " 2762 ::= { mip6HaGlAddrEntry 2 } 2764 mip6HaGaGlobalAddress OBJECT-TYPE 2765 SYNTAX InetAddress 2766 MAX-ACCESS read-only 2767 STATUS current 2768 DESCRIPTION 2769 "A global address of the home agent. 2770 " 2771 ::= { mip6HaGlAddrEntry 3 } 2773 -- 2774 -- Notifications 2775 -- 2777 mip6HaNotifications OBJECT IDENTIFIER ::= { mip6Notifications 0 } 2779 mip6MnRegistered NOTIFICATION-TYPE 2780 OBJECTS { 2781 mip6BindingTimeRegistered, 2782 mip6BindingCOAType, 2783 mip6BindingCOA 2784 } 2785 STATUS current 2786 DESCRIPTION 2787 "This notification is sent every time a mobile node 2788 registers with the home agent for the first time. 2789 Notifications will not be sent for subsequent updates 2790 and/or refreshes. 2791 The MO instances in the notifications will be identified 2792 by the mip6BindingHomeAddressType, mip6BindingHomeAddress 2793 for the mobile node in the mip6BindingCacheTable. 2794 " 2795 ::= { mip6HaNotifications 1 } 2797 mip6MnDeRegistered NOTIFICATION-TYPE 2798 OBJECTS { 2799 mip6BindingTimeRegistered, 2800 mip6BindingCOAType, 2801 mip6BindingCOA 2802 } 2803 STATUS current 2804 DESCRIPTION 2805 "This notification is sent every time a mobile node 2806 de-registers with the home agent by sending a 2807 Notifications will not be sent for subsequent updates 2808 and/or refreshes. 2809 The MO instances in the notifications will be identified 2810 by the mip6BindingHomeAddressType, mip6BindingHomeAddress 2811 for the mobile node in the mip6BindingCacheTable. 2812 " 2813 ::= { mip6HaNotifications 2 } 2815 mip6MnMoved NOTIFICATION-TYPE 2816 OBJECTS { 2817 mip6BindingTimeRegistered, 2818 mip6BindingCOAType, 2819 mip6BindingCOA 2820 } 2821 STATUS current 2822 DESCRIPTION 2823 "This notification is sent every time a mobile node 2824 sends a Binding Update with a new Care-of address. 2825 Notifications will not be sent for subsequent updates 2826 and/or refreshes for the same Care-of address. 2827 The MO instances in the notifications will be identified 2828 by the mip6BindingHomeAddressType, mip6BindingHomeAddress 2829 for the mobile node in the mip6BindingCacheTable. 2830 " 2831 ::= { mip6HaNotifications 3 } 2833 mip6MnBindingExpiredAtHA NOTIFICATION-TYPE 2834 OBJECTS { 2835 mip6BindingTimeRegistered, 2836 mip6BindingCOAType, 2837 mip6BindingCOA 2839 } 2840 STATUS current 2841 DESCRIPTION 2842 "This notification is sent when a binding for the 2843 mobile node at the home agent expires and no timely 2844 Binding Updates are received. 2845 The MO instances in the notifications will be identified 2846 by the mip6BindingHomeAddressType, mip6BindingHomeAddress 2847 for the mobile node in the mip6BindingCacheTable. 2848 " 2849 ::= { mip6HaNotifications 4 } 2851 mip6MnBindingExpiredAtCN NOTIFICATION-TYPE 2852 OBJECTS { 2853 mip6BindingTimeRegistered, 2854 mip6BindingCOAType, 2855 mip6BindingCOA 2856 } 2857 STATUS current 2858 DESCRIPTION 2859 "This notification is sent when a binding for the 2860 mobile node at the CN expires and no timely 2861 Binding Updates are received. 2862 The MO instances in the notifications will be identified 2863 by the mip6BindingHomeAddressType, mip6BindingHomeAddress 2864 for the mobile node in the mip6BindingCacheTable. 2865 " 2866 ::= { mip6HaNotifications 5 } 2868 -- Conformance information 2869 mip6Groups OBJECT IDENTIFIER ::= { mip6Conformance 1 } 2870 mip6Compliances OBJECT IDENTIFIER ::= { mip6Conformance 2 } 2872 -- Units of conformance 2873 mip6SystemGroup OBJECT-GROUP 2874 OBJECTS { 2875 mip6Capabilities, 2876 mip6Status 2877 } 2878 STATUS current 2879 DESCRIPTION 2880 " A collection of objects for basic MIPv6 2881 monitoring." 2882 ::= { mip6Groups 1 } 2884 mip6BindingCacheGroup OBJECT-GROUP 2885 OBJECTS { 2886 -- mip6BindingHomeAddressType, 2887 -- mip6BindingHomeAddress, 2888 mip6BindingCOAType, 2889 mip6BindingCOA, 2890 mip6BindingTimeRegistered, 2891 mip6BindingTimeGranted, 2892 mip6BindingTimeRemaining, 2893 mip6BindingMaxSeq, 2894 mip6BindingHomeRegn, 2895 mip6BindingUsageTS, 2896 mip6BindingUsageCount, 2897 mip6BindingAdminStatus 2898 } 2899 STATUS current 2900 DESCRIPTION 2901 " A collection of objects for monitoring the 2902 Binding cache. 2903 " 2904 ::= { mip6Groups 2 } 2906 mip6BindingHstGroup OBJECT-GROUP 2907 OBJECTS { 2908 -- mip6BindingHstHomeAddressType, 2909 -- mip6BindingHstHomeAddress, 2910 mip6BindingHstCOAType, 2911 mip6BindingHstCOA, 2912 -- mip6BindingHstIndex, 2913 mip6BindingHstTimeRegistered, 2914 mip6BindingHstTimeExpired, 2915 mip6BindingHstHomeRegn, 2916 mip6BindingHstUsageTS, 2917 mip6BindingHstUsageCount 2918 } 2919 STATUS current 2920 DESCRIPTION 2921 " A collection of objects for monitoring the 2922 binding history. This can be used to monitor 2923 the movement of the mobile node. 2924 " 2925 ::= { mip6Groups 3 } 2927 mip6TotalTrafficGroup OBJECT-GROUP 2928 OBJECTS { 2929 mip6InOctets, 2930 mip6HCInOctets, 2931 mip6InPkts, 2932 mip6HCInPkts, 2933 mip6OutOctets, 2934 mip6HCOutOctets, 2935 mip6OutPkts, 2936 mip6HCOutPkts, 2937 mip6CounterDiscontinuityTime 2938 } 2939 STATUS current 2940 DESCRIPTION 2941 " A collection of objects for monitoring the 2942 total MIPv6 traffic. 2943 " 2944 ::= { mip6Groups 4 } 2946 mip6NodeTrafficGroup OBJECT-GROUP 2947 OBJECTS { 2948 mip6NodeInOctets, 2949 mip6HCNodeInOctets, 2950 mip6NodeInPkts, 2951 mip6HCNodeInPkts, 2952 mip6NodeOutOctets, 2953 mip6HCNodeOutOctets, 2954 mip6NodeOutPkts, 2955 mip6HCNodeOutPkts, 2956 mip6NodeCtrDiscontinuityTime 2957 } 2958 STATUS current 2959 DESCRIPTION 2960 " A collection of objects for monitoring the 2961 MIPv6 traffic due to a mobile node. 2962 " 2963 ::= { mip6Groups 5 } 2965 mip6MnSystemGroup OBJECT-GROUP 2966 OBJECTS { 2967 -- mip6MnHomeAddressType, 2968 -- mip6MnHomeAddress, 2969 mip6MnHomeAddressState 2970 } 2971 STATUS current 2972 DESCRIPTION 2973 " A collection of objects for basic monitoring 2974 of the mobile node. 2975 " 2976 ::= { mip6Groups 6 } 2978 mip6MnConfGroup OBJECT-GROUP 2979 OBJECTS { 2980 mip6MnDiscoveryRequests, 2981 mip6MnDiscoveryReplies, 2982 mip6MnDiscoveryTimeouts, 2983 mip6MnPrefixSolicitationsSent, 2984 mip6MnPrefixAdvsRecd, 2985 mip6MnPrefixAdvsIgnored, 2986 mip6MnMovedToFN, 2987 mip6MnMovedToHN 2988 } 2989 STATUS current 2990 DESCRIPTION 2991 " A collection of objects for monitoring 2992 the advertisement related info on the 2993 mobile node. 2994 " 2995 ::= { mip6Groups 7 } 2997 mip6MnRegistrationGroup OBJECT-GROUP 2998 OBJECTS { 2999 -- mip6MnBLNodeAddressType, 3000 -- mip6MnBLNodeAddress, 3001 -- mip6MnBLCOAType, 3002 -- mip6MnBLCOA, 3003 mip6MnBLLifeTimeRequested, 3004 mip6MnBLLifeTimeGranted, 3005 mip6MnBLMaxSeq, 3006 mip6MnBLTimeSent, 3007 mip6MnBLAccepted, 3008 mip6MnBLAcceptedTime, 3009 mip6MnBLRetransmissions, 3010 -- 3011 -- Binding Update List 3012 -- 3013 mip6MnMobilityMessagesSent, 3014 mip6MnMobilityMessagesRecd, 3015 mip6MnBUsToHA, 3016 mip6MnBUAcksFromHA, 3017 mip6MnBUsToCN, 3018 mip6MnBUAcksFromCN, 3019 mip6MnBindingErrorsFromCN, 3020 mip6MnICMPErrorsRecd, 3021 mip6MnBRRequestsRecd 3022 } 3023 STATUS current 3024 DESCRIPTION 3025 " A collection of objects for monitoring 3026 the registration statistics for the mobile node. 3027 " 3028 ::= { mip6Groups 8 } 3030 mip6CnStatsGroup OBJECT-GROUP 3031 OBJECTS { 3032 mip6CnBURequestsAccepted, 3033 mip6CnBURequestsRejected, 3034 mip6CnBCEntryCreationTime, 3035 mip6CnBUAcceptedTime, 3036 mip6CnBURejectionTime, 3037 mip6CnBURejectionCode, 3038 mip6CnCtrDiscontinuityTime 3039 } 3040 STATUS current 3041 DESCRIPTION 3042 " A collection of objects for monitoring 3043 the control messages and corresponding 3044 statistics for each mobile node 3045 communicating with the correspondent 3046 node. 3047 " 3048 ::= { mip6Groups 9 } 3050 mip6HaSystemGroup OBJECT-GROUP 3051 OBJECTS { 3052 mip6HaAdvsRecd, 3053 mip6HaAdvsSent, 3054 mip6HaAdvPreference, 3055 mip6HaAdvLifetime, 3056 mip6HaPrefixAdv, 3057 mip6HaPrefixSolicitation, 3058 mip6HaMCastCtlMsgSupport 3059 } 3060 STATUS current 3061 DESCRIPTION 3062 " A collection of objects for monitoring 3063 the Advertisement related parameters and 3064 statistics for the home agent. 3065 " 3066 ::= { mip6Groups 10 } 3068 mip6HaListGroup OBJECT-GROUP 3069 OBJECTS { 3070 -- mip6HaLinkLocalAddressType, 3071 -- mip6HaLinkLocalAddress, 3072 mip6HaPreference, 3073 mip6HaRecvLifeTime, 3074 mip6HaRecvTimeStamp, 3075 -- mip6HaGaAddrSeqNo, 3076 mip6HaGaGlobalAddressType, 3077 mip6HaGaGlobalAddress 3078 } 3079 STATUS current 3080 DESCRIPTION 3081 " A collection of objects for monitoring 3082 Home Agent List on the home agent. 3083 " 3084 ::= { mip6Groups 11 } 3086 mip6HaStatsGroup OBJECT-GROUP 3087 OBJECTS { 3088 mip6HaBURequestsAccepted, 3089 mip6HaBURequestsDenied, 3090 mip6HaBCEntryCreationTime, 3091 mip6HaBUAcceptedTime, 3092 mip6HaBURejectionTime, 3093 mip6HaRecentBURejectionCode, 3094 mip6HaCtrDiscontinuityTime 3096 } 3097 STATUS current 3098 DESCRIPTION 3099 " A collection of objects for monitoring 3100 registration related statistics on the home agent. 3101 " 3102 ::= { mip6Groups 12 } 3104 mip6CnGlobalStatsGroup OBJECT-GROUP 3105 OBJECTS { 3106 mip6CnHomeTestInitsRecd, 3107 mip6CnHomeTestsSent, 3108 mip6CnCareOfTestInitsRecd, 3109 mip6CnCareOfTestsSent, 3110 mip6CnBUsRecd, 3111 mip6CnBUAcksSent, 3112 mip6CnBRsSent, 3113 mip6CnBindingErrors, 3114 mip6CnBUsAccepted, 3115 mip6CnBUsRejected, 3116 mip6CnReasonUnspecified, 3117 mip6CnInsufficientResource, 3118 mip6CnHomeRegnNotSupported, 3119 mip6CnSeqNumberOutOfWindow, 3120 mip6CnExpiredHomeNonceIndex, 3121 mip6CnExpiredCareOfNonceIndex, 3122 mip6CnExpiredNonce, 3123 mip6CnRegTypeChangeDisallowed 3124 } 3125 STATUS current 3126 DESCRIPTION 3127 " A collection of objects for monitoring 3128 advertisement and registration statistics on 3129 a correspondent node. 3130 " 3131 ::= { mip6Groups 13 } 3133 mip6HaGlobalStatsGroup OBJECT-GROUP 3134 OBJECTS { 3135 mip6HaHomeTestInitsRecd, 3136 mip6HaHomeTestsSent, 3137 mip6HaBUsRecd, 3138 mip6HaBUAcksSent, 3139 mip6HaBRAdviceSent, 3140 mip6HaBUsAccepted, 3141 mip6HaPrefDiscoverReqd, 3142 mip6HaReasonUnspecified, 3143 mip6HaAdmProhibited, 3144 mip6HaInsufficientResource, 3145 mip6HaHomeRegnNotSupported, 3146 mip6HaNotHomeSubnet, 3147 mip6HaNotHomeAgentForThisMN, 3148 mip6HaDupAddrDetectionFailed, 3149 mip6HaSeqNumberOutOfWindow, 3150 mip6HaExpiredHomeNonceIndex, 3151 mip6HaRegTypeChangeDisallowed 3153 } 3154 STATUS current 3155 DESCRIPTION 3156 " A collection of objects for monitoring 3157 advertisement and registration statistics on 3158 a home agent. 3159 " 3160 ::= { mip6Groups 14 } 3162 mip6BindingCacheCtlGroup OBJECT-GROUP 3163 OBJECTS { 3164 mip6BindingAdminStatus 3165 } 3166 STATUS current 3167 DESCRIPTION 3168 "A collection of objects for controlling the 3169 Binding cache. 3170 " 3171 ::= { mip6Groups 15 } 3173 mip6NotificationGroup OBJECT-GROUP 3174 OBJECTS { 3175 mip6MnRegistered, 3176 mip6MnDeRegistered, 3177 mip6MnMoved, 3178 mip6MnBindingExpiredAtHA, 3179 mip6MnBindingExpiredAtCN 3180 } 3181 STATUS current 3182 DESCRIPTION 3183 "A collection of objects for sending Notifications 3184 from a home agent or correspondent node to the Manager 3185 about the status of a mobile node. 3186 " 3187 ::= { mip6Groups 16 } 3189 -- Compliance statements 3190 mip6CoreCompliance MODULE-COMPLIANCE 3191 STATUS current 3192 DESCRIPTION 3193 "The compliance statement for SNMP entities 3194 which implement the MOBILEIPV6-MIB." 3195 MODULE -- this module 3196 MANDATORY-GROUPS { mip6SystemGroup } 3197 ::= { mip6Compliances 1 } 3199 mip6Compliance2 MODULE-COMPLIANCE 3200 STATUS current 3201 DESCRIPTION 3202 "The compliance statement for SNMP entities 3203 which implement the MOBILEIPV6-MIB and support 3204 monitoring of the BindingCache and the Total Traffic. 3205 " 3206 MODULE -- this module 3207 MANDATORY-GROUPS { mip6SystemGroup, 3208 mip6BindingCacheGroup, 3209 mip6TotalTrafficGroup 3210 } 3211 ::= { mip6Compliances 2 } 3213 mip6Compliance3 MODULE-COMPLIANCE 3214 STATUS current 3215 DESCRIPTION 3216 "The compliance statement for SNMP entities 3217 which implement the MOBILEIPV6-MIB and 3218 support monitoring of the BindingCache, 3219 the Binding History, the total traffic and 3220 the mobile node-wide traffic. 3221 " 3222 MODULE -- this module 3223 MANDATORY-GROUPS { mip6SystemGroup, 3224 mip6BindingCacheGroup, 3225 mip6BindingHstGroup, 3226 mip6TotalTrafficGroup, 3227 mip6NodeTrafficGroup 3228 } 3229 ::= { mip6Compliances 3 } 3231 mip6MnCoreCompliance MODULE-COMPLIANCE 3232 STATUS current 3233 DESCRIPTION 3234 "The compliance statement for SNMP entities 3235 which implement the MOBILEIPV6-MIB and 3236 support monitoring of the basic mobile node 3237 functionality. 3238 " 3239 MODULE -- this module 3240 MANDATORY-GROUPS { mip6MnSystemGroup 3241 } 3242 ::= { mip6Compliances 4 } 3244 mip6MnCompliance2 MODULE-COMPLIANCE 3245 STATUS current 3246 DESCRIPTION 3247 "The compliance statement for SNMP entities 3248 which implement the MOBILEIPV6-MIB and 3249 support monitoring of the mobile node 3250 functionality specifically the Discovery and 3251 Registration related statistics, 3252 " 3253 MODULE -- this module 3254 MANDATORY-GROUPS { mip6MnSystemGroup, 3255 mip6MnConfGroup, 3256 mip6MnRegistrationGroup, 3257 mip6TotalTrafficGroup 3258 } 3259 ::= { mip6Compliances 5 } 3261 mip6CnCoreCompliance MODULE-COMPLIANCE 3262 STATUS current 3263 DESCRIPTION 3264 "The compliance statement for SNMP entities 3265 which implement the MOBILEIPV6-MIB and 3266 support monitoring of the basic correspondent node 3267 functionality. 3268 " 3269 MODULE -- this module 3270 MANDATORY-GROUPS { mip6CnGlobalStatsGroup, 3271 mip6TotalTrafficGroup 3272 } 3273 ::= { mip6Compliances 6 } 3275 mip6CnCompliance MODULE-COMPLIANCE 3276 STATUS current 3277 DESCRIPTION 3278 "The compliance statement for SNMP entities 3279 which implement the MOBILEIPV6-MIB and 3280 support monitoring of the basic correspondent node 3281 functionality. 3282 " 3283 MODULE -- this module 3284 MANDATORY-GROUPS { mip6CnGlobalStatsGroup, 3285 mip6CnStatsGroup, 3286 mip6TotalTrafficGroup 3287 } 3288 ::= { mip6Compliances 7 } 3290 mip6HaCoreCompliance MODULE-COMPLIANCE 3291 STATUS current 3292 DESCRIPTION 3293 "The compliance statement for SNMP entities 3294 which implement the MOBILEIPV6-MIB and 3295 support monitoring of the basic home agent 3296 functionality. 3297 " 3298 MODULE -- this module 3299 MANDATORY-GROUPS { mip6HaSystemGroup 3300 } 3301 ::= { mip6Compliances 8 } 3303 mip6HaCompliance2 MODULE-COMPLIANCE 3304 STATUS current 3305 DESCRIPTION 3306 "The compliance statement for SNMP entities 3307 which implement the MOBILEIPV6-MIB and 3308 support monitoring of the home agent 3309 functionality specifically the Home Agent List 3310 and the home agent registration related statistics, 3311 " 3312 MODULE -- this module 3313 MANDATORY-GROUPS { mip6HaSystemGroup, 3314 mip6HaListGroup, 3315 mip6HaStatsGroup, 3316 mip6HaGlobalStatsGroup, 3317 mip6TotalTrafficGroup 3318 } 3319 ::= { mip6Compliances 9 } 3321 mip6HaCompliance3 MODULE-COMPLIANCE 3322 STATUS current 3323 DESCRIPTION 3324 "The compliance statement for SNMP entities 3325 which implement the MOBILEIPV6-MIB and 3326 support monitoring and control of the home agent 3327 functionality specifically the Home Agent List 3328 and the home agent registration related statistics, 3329 " 3330 MODULE -- this module 3331 MANDATORY-GROUPS { mip6HaSystemGroup, 3332 mip6HaListGroup, 3333 mip6HaStatsGroup, 3334 mip6HaGlobalStatsGroup, 3335 mip6BindingCacheCtlGroup, 3336 mip6TotalTrafficGroup 3337 } 3338 ::= { mip6Compliances 10 } 3340 mip6NotificationCompliance MODULE-COMPLIANCE 3341 STATUS current 3342 DESCRIPTION 3343 "The compliance statement for SNMP entities 3344 which implement the MOBILEIPV6-MIB and 3345 support Notification from HA or CN to management 3346 stations about the mobile node status. 3348 " 3349 MODULE -- this module 3350 MANDATORY-GROUPS { mip6NotificationGroup 3351 } 3352 ::= { mip6Compliances 11 } 3354 END 3356 6. Security Considerations 3358 There are a number of management objects defined in this MIB module 3359 with a MAX-ACCESS clause of read-write and/or read-create. Such 3360 objects may be considered sensitive or vulnerable in some network 3361 environments. The support for SET operations in a non-secure 3362 environment without proper protection can have a negative effect on 3363 network operations. These are the tables and objects and their 3364 sensitivity/vulnerability: 3365 mip6Status: This value of this object is used to enable or 3366 disable the MIPv6 functionality on a MIPv6 entity. 3367 Access to this MO may be abused to disrupt the 3368 MIPv6 communication. 3369 mip6HaAdvPreference: Access to this object may be abused to 3370 force 3371 MNs into selecting the wrong HA. 3372 mip6HaAdvLifetime: Access to this object may be abused to set 3373 the 3374 advertised lifetime to incorrect values. That will 3375 have an adverse impact on the MIPv6 communication. 3376 Some of the readable objects in this MIB module (i.e., objects with a 3377 MAX-ACCESS other than not-accessible) may be considered sensitive or 3378 vulnerable in some network environments. It is thus important to 3379 control even GET and/or NOTIFY access to these objects and possibly 3380 to even encrypt the values of these objects when sending them over 3381 the network via SNMP. These are the tables and objects and their 3382 sensitivity/vulnerability: 3384 The address related objects in this MIB may be considered to be 3385 particularly sensitive and/or private. The care of address related 3386 objects reveal the location and movement of the mobile node. This 3387 information may be considered to be private and sensitive and must 3388 be carefully handled. 3389 mip6BindingHstCOAType 3390 mip6BindingHstCOA 3391 mip6MnBLCOAType 3392 mip6MnBLCOA 3394 The mobile node's home address and home agent related information 3395 may be considered to be sensitive too as these may provide clues to 3396 a malicious party on ways to disrupt the mobile nodes communication 3397 channels. 3398 mip6BindingHstHomeAddressType, 3399 mip6BindingHstHomeAddress, 3400 mip6MnHomeAddressType, 3401 mip6MnHomeAddress 3403 The correspondent node's addresses related MOs will reveal the nodes 3404 with whom the mobile node is corresponding. This information may be 3405 considered private and sensitive. 3406 mip6MnBLNodeAddressType, 3407 mip6MnBLNodeAddress 3409 SNMP versions prior to SNMPv3 did not include adequate security. 3410 Even if the network itself is secure (for example by using IPSec), 3411 even then, there is no control as to who on the secure network is 3412 allowed to access and GET/SET (read/change/create/delete) the objects 3413 in this MIB module. 3415 It is RECOMMENDED that implementers consider the security features as 3416 provided by the SNMPv3 framework (see [RFC3410], section 8), 3417 including full support for the SNMPv3 cryptographic mechanisms (for 3418 authentication and privacy). 3420 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3421 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3422 enable cryptographic security. It is then a customer/operator 3423 responsibility to ensure that the SNMP entity giving access to an 3424 instance of this MIB module is properly configured to give access to 3425 the objects only to those principals (users) that have legitimate 3426 rights to indeed GET or SET (change/create/delete) them. 3428 7. IANA Considerations 3430 IANA should assign a base arc in the 'mib-2' (standards track) OID 3431 tree for the 'mipv6MIB' MODULE-IDENTITY defined in the Mobile-IPv6 3432 MIB. 3434 8. References 3436 [Normative References] 3438 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3439 Rose, M., and S. Waldbusser, "Structure of Management 3440 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 3442 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3443 Rose, M., and S. Waldbusser, "Textual Conventions for 3444 SMIv2", STD 58, RFC 2579, April 1999 3446 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3447 Rose, M., and S. Waldbusser, "Conformance Statements for 3448 SMIv2", STD 58, RFC 2580, April 1999 3450 [RFC3775] Johnson, D., Perkins, C., Arkko J., "Mobility Support in IPv6" 3451 RFC 3775, June 2004. 3453 [Informative References] 3455 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 3456 "Introduction to Version 3 of the Internet-standard Network 3457 Management Framework", RFC 2570, April 1999 3459 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 3460 for Describing SNMP Management Frameworks", RFC 2571, April 3461 1999 3463 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 3464 Processing and Dispatching for the Simple Network Management 3465 Protocol (SNMP)", RFC 2572, April 1999 3467 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 3468 RFC 2573, April 1999 3470 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 3471 (USM) for version 3 of the Simple Network Management 3472 Protocol (SNMPv3)", RFC 2574, April 1999 3474 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 3475 Access Control Model (VACM) for the Simple Network 3476 Management Protocol (SNMP)", RFC 2575, April 1999. 3478 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3479 "Introduction and Applicability Statements for the 3480 Internet-Standard Management Framework", RFC 3410, 3481 December 2002. 3483 9. Acknowledgments 3485 The WIDE-netman group has contributed to this draft with discussions 3486 and comments. 3488 10. Authors' Addresses 3490 Glenn Mansfield Keeni 3491 Cyber Solutions Inc. 3492 6-6-3 Minami Yoshinari 3493 Aoba-ku, Sendai 989-3204 3494 Japan 3496 Phone: +81-22-303-4012 3497 EMail: glenn@cysols.com 3499 Kenichi Nagami 3500 INTEC NetCore Inc. 3501 1-3-3, Shin-suna 3502 Koto-ku, Tokyo, 135-0075 3503 Japan 3505 Phone: +81-3-5665-5069 3506 E-mail: nagami@inetcore.com 3508 Kazuhide Koide 3509 Tohoku University 3510 Katahira Campus 3511 Sendai 3512 Japan 3514 Phone: +81-22-217-5454 3515 E-mail: koide@shiratori.riec.tohoku.ac.jp 3517 Sri Gundavelli 3518 Cisco Systems 3519 170 W.Tasman Drive, 3520 San Jose, CA 95134 3521 USA 3523 Phone: +1-408-527-6109 3524 Email: sgundave@cisco.com 3526 11. Full Copyright Statement 3528 Copyright (C) The Internet Society (2004). This document is subject 3529 to the rights, licenses and restrictions contained in BCP 78 and 3530 except as set forth therein, the authors retain all their rights. 3532 This document and the information contained herein are provided on an 3533 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 3534 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 3535 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 3536 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 3537 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3538 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3540 Intellectual Property 3542 The IETF takes no position regarding the validity or scope of any 3543 Intellectual Property Rights or other rights that might be claimed 3544 to pertain to the implementation or use of the technology 3545 described in this document or the extent to which any license 3546 under such rights might or might not be available; nor does it 3547 represent that it has made any independent effort to identify any 3548 such rights. Information on the procedures with respect to 3549 rights in RFC documents can be found in BCP 78 and BCP 79. 3551 Copies of IPR disclosures made to the IETF Secretariat and any 3552 assurances of licenses to be made available, or the result of an 3553 attempt made to obtain a general license or permission for the use 3554 of such proprietary rights by implementers or users of this 3555 specification can be obtained from the IETF on-line IPR repository 3556 at http://www.ietf.org/ipr. 3558 The IETF invites any interested party to bring to its attention 3559 any copyrights, patents or patent applications, or other 3560 proprietary rights that may cover technology that may be required 3561 to implement this standard. Please address the information to the 3562 IETF at ietf-ipr@ietf.org. 3564 Acknowledgement 3566 Funding for the RFC Editor function is currently provided by the 3567 Internet Society. 3569 Changes since draft-ietf-mip6-mipv6-mib-02.txt 3571 a. Aligned with the new I-D format requirements 3572 "Status of this memo" is updated 3573 IANA considerations section is added 3574 Copyright is included in the MIB MODULE IDENTITY Description 3575 Full Copyright Statement updated 3576 b. Changed the MO name prefix from mipv6 to mip6 3577 c. Added the instance specifications for MOs included in Notifications 3578 d. Reference to the base MIP6 document is updated from the I-D to RFC3775