idnits 2.17.1 draft-ietf-mip6-mipv6-mib-07.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 20. -- Found old boilerplate from RFC 3978, Section 5.5 on line 4416. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4427. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4434. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4440. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 4408), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 44. ** 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. ** 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? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 115 longer pages, the longest (page 2) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 4468 has weird spacing: '...geCount to ...' == Line 4476 has weird spacing: '...issions to Ga...' -- 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 (March 7, 2005) is 6980 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 4582, but not defined ** Obsolete normative reference: RFC 3775 (Obsoleted by RFC 6275) ** Obsolete normative reference: RFC 2011 (Obsoleted by RFC 4293) ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) Summary: 10 errors (**), 0 flaws (~~), 6 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Mip6 Working Group Glenn M. Keeni 3 INTERNET-DRAFT Cyber Solutions Inc. 4 Expires: September 6, 2005 Kazuhide Koide 5 Tohoku University 6 Kenichi Nagami 7 INTEC NetCore Inc. 8 Sri Gundavelli 9 Cisco Systems Inc. 10 March 7, 2005 12 Mobile IPv6 Management Information Base 13 15 Status of this Memo 17 By submitting this Internet-Draft, we certify that any applicable 18 patent or other IPR claims of which we are aware have been disclosed, 19 or will be disclosed, and any of which we become aware will be 20 disclosed, in accordance with RFC 3668. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that other 24 groups may also distribute working documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than a "work in progress". 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/1id-abstracts.html 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html 37 This document is a product of the mip6 Working Group. Comments should 38 be addressed to the authors or the mailing list at mip6@ietf.org 40 This Internet-Draft will expire on September 6, 2005. 42 Copyright Notice 44 Copyright (C) The Internet Society (2005). All Rights Reserved. 46 Abstract 48 This memo defines a portion of the Management Information Base (MIB), 49 the Mobile-IPv6 MIB , for use with network management protocols 50 in the Internet community. In particular, the Mobile-IPv6 MIB will be 51 used to monitor and control the mobile node, home agent and 52 correspondent node functions of a Mobile IPv6 (MIPv6) entity. 54 Table of Contents 56 1. The Internet-Standard Management Framework ................... 3 57 2. Overview ..................................................... 3 58 3. Mobile IPv6 Monitoring and Control Requirements .............. 4 59 4. MIB Design ................................................... 5 60 5. The Mobile-IPv6 MIB .......................................... 7 61 6. Security Considerations ......................................106 62 7. IANA Considerations ..........................................108 63 8. References ...................................................109 64 9. Acknowledgments ..............................................109 65 10. Authors' Addresses ...........................................110 66 11. Full Copyright Statement .....................................111 67 Appendix: History of Changes 69 1. The Internet-Standard Management Framework 71 For a detailed overview of the documents that describe the current 72 Internet-Standard Management Framework, please refer to section 7 of 73 RFC 3410 [RFC3410]. 75 Managed objects are accessed via a virtual information store, termed 76 the Management Information Base or MIB. MIB objects are generally 77 accessed through the Simple Network Management Protocol (SNMP). 79 Objects in the MIB are defined using the mechanisms defined in the 80 Structure of Management Information (SMI). This memo specifies a MIB 81 module that is compliant to the SMIv2, which is described in STD 58, 82 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 83 [RFC2580]. 85 2. Overview 87 2.1 The Mobile IPv6 Protocol entities. 89 Mobile IPv6 (MIPv6) [RFC3775] specifies a protocol which allows nodes 90 to remain reachable while moving around in the IPv6 Internet. An 91 entity which implements the MIPv6 protocol is a MIPv6 entity. There 92 are three types of entities envisaged by the MIPv6 protocol. 94 mobile node (MN): A node that can change its point of attachment 95 from one link to another, while still being reachable via its home 96 address. 98 correspondent node (CN): A peer node with which a mobile node is 99 communicating. The correspondent node may be either mobile or 100 stationary. [Note that a correspondent node does not necessarily 101 require MIPv6 support.] 103 home agent (HA): A router on a mobile node's home link with which 104 the mobile node has registered its current care-of address. While 105 the mobile node is away from home, the home agent intercepts 106 packets on the home link destined to the mobile node's home 107 address, encapsulates them, and routes them to the mobile node's 108 registered care-of address. 110 This document defines a set of managed objects (MOs) that can be used 111 to monitor and control MIPv6 entities. 113 2.2 Terminology. 114 The terminology used in this document is consistent with the 115 definitions used in Mobile IPv6 protocol specification[RFC3775]. 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 119 "OPTIONAL" in this document are to be interpreted as described in 120 BCP 14, RFC 2119 [RFC2119]. 122 3. Mobile IPv6 Monitoring and Control Requirements 124 For managing a MIPv6 entity it is necessary to monitor 125 the following: 126 o capabilities of MIPv6 entities 127 o traffic due to MIPv6 128 o binding related statistics (at home agent, correspondent 129 node and mobile node) 130 o binding details (at home agent and correspondent node) 131 o history of Binding Updates (at home agent, correspondent 132 node and mobile node) 134 The MIPv6 protocol document stipulates that several MIPv6 related 135 parameters should be manually configurable. The MIPv6 MIB should 136 define managed objects that can be used to configure the related 137 parameters e.g.: 138 o the preference value the home agent will use in Router 139 Advertisements; 140 o the lifetime value the home agent will use in Router 141 Advertisements; 142 o whether a home agent will send ICMP Mobile Prefix 143 Advertisements to mobile nodes; 144 o whether a home agent will respond to ICMP Mobile Prefix 145 Solicitation messages from mobile nodes; and 146 o whether a home agent will process multicast group membership 147 control messages from mobile nodes. 149 4. MIB Design. 151 The basic principle has been to keep the MIB as simple as possible 152 and at the same time to make it effective enough so that the 153 essential needs of monitoring and control are met. It is envisaged 154 that wherever possible existing MIBS will be used (e.g. IPSec MIB, 155 Neighbor Discovery MIB, Tunnel MIB.) for monitor and control of MIPv6 156 entities. 158 It is assumed that the Mobile IPv6 Management Information Base 159 (MOBILEIPV6-MIB) will always be implemented in conjunction with the 160 IPv6-capable version of the IP-MIB [RFC2011bis]. The MOBILEIPV6-MIB 161 uses the textual conventions defined in the INET-ADDRESS-MIB 162 [RFC3291bis]. 164 The Mobile-IPv6 MIB comprises of following groups of definitions: 165 - mip6Core: a generic group containing objects that are 166 common to all the Mobile IPv6 entities. 167 - mip6Ha: this group models the home agent service. It 168 comprises of objects specific to the services and associated 169 advertisement parameters offered by the home agent on each 170 of its links. It also contains objects pertaining to the 171 maintenance of the home agent list on each of the links on 172 which the service is offered. 173 - mip6Mn: this group models the mobile node service. It 174 comprises of objects specific to the Dynamic Home Agent 175 discovery function and related parameters. It also contains 176 objects that record the movement of the mobile node. 177 - mip6Cn: models the correspondent node and is primarily 178 scoped to its participation in the Return Routability 179 procedure for achieving Route Optimization triggered by 180 the mobile node. 181 - mip6Notifications: defines the set of notifications that 182 will be used to asynchronously monitor the Mobile IPv6 183 entities. 185 The tables contained in the above groups are as follows- 186 mip6BindingCacheTable : models the binding cache on the home 187 agent and correspondent node. It 188 contains details of the Binding Update 189 requests that have been received and 190 accepted. 191 mip6BindingHistoryTable : tracks the history of the binding 192 cache. 193 mip6NodeTrafficTable : the mobile node-wise traffic counters. 194 mip6MnHomeAddressTable : contains all the home addresses 195 pertaining to the mobile node and 196 the corresponding registration status. 198 mip6MnBLTable : models the Binding Update List on the 199 mobile node. It contains information 200 about the registration requests sent 201 by the mobile node and the 202 corresponding results. 203 mip6CnCounterTable : contains the mobile node-wise 204 registration statistics. 205 mip6HaConfTable : contains the configurable 206 advertisement parameters for all the 207 interfaces on which the home agent 208 service is advertised. 209 mip6HaCounterTable : contains registration statistics 210 for all mobile nodes registered 211 with the home agent. 212 mip6HaListTable : contains the list of all routers 213 that are acting as home agents on 214 each of the interfaces on which 215 the home agent service is offered 216 by this router. 217 mip6HaGlAddrTable : contains the global addresses of 218 the home agents. 220 5. The Mobile-IPv6 MIB. 222 MOBILEIPV6-MIB DEFINITIONS ::= BEGIN 223 IMPORTS 224 MODULE-IDENTITY, mib-2, Unsigned32, Integer32, Counter32, 225 Gauge32, Counter64, 226 OBJECT-TYPE, NOTIFICATION-TYPE 227 FROM SNMPv2-SMI 228 TEXTUAL-CONVENTION, 229 TruthValue, DateAndTime, TimeStamp 230 FROM SNMPv2-TC 231 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 232 FROM SNMPv2-CONF 233 InetAddressType, InetAddress 234 FROM INET-ADDRESS-MIB 235 ipv6InterfaceIfIndex 236 FROM IP-MIB 237 ; 239 mip6MIB MODULE-IDENTITY 240 LAST-UPDATED "200410160000Z" -- 16th October, 2004 241 ORGANIZATION "IETF mip6 Working Group" 242 CONTACT-INFO 243 " Glenn Mansfield Keeni 244 Postal: Cyber Solutions Inc. 245 6-6-3, Minami Yoshinari 246 Aoba-ku, Sendai, Japan 989-3204. 247 Tel: +81-22-303-4012 248 Fax: +81-22-303-4015 249 E-mail: glenn@cysols.com 251 Kenichi Nagami 252 Postal: INTEC NetCore Inc. 253 1-3-3, Shin-suna 254 Koto-ku, Tokyo, 135-0075 255 Japan 257 Tel: +81-3-5665-5069 258 E-mail: nagami@inetcore.com 260 Kazuhide Koide 261 Postal: Tohoku University 262 Katahira Campus 263 Sendai 264 Japan 266 Tel: +81-22-217-5454 267 E-mail: koide@shiratori.riec.tohoku.ac.jp 268 Sri Gundavelli 269 Postal: Cisco Systems 270 170 W.Tasman Drive, 271 San Jose, CA 95134 272 USA 274 Tel: +1-408-527-6109 275 E-mail: sgundave@cisco.com 277 Support Group E-mail: mip6@ietf.org" 279 DESCRIPTION 280 "The MIB module for monitoring Mobile-IPv6 281 entities. 283 Copyright (C) The Internet Society 2004. This 284 version of this MIB module is part of RFC XXXX; 285 see the RFC itself for full legal notices. 286 " 287 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 289 REVISION "200410160000Z" -- 16th October 2004 290 DESCRIPTION "Initial version, published as RFC XXXX." 292 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 294 ::= { mib-2 XXX } -- will be assigned by IANA 296 -- IANA Reg.: Please assign a value for "XXX" under the 'mib-2' 297 -- subtree and record the assignment in the SMI Numbers registry. 299 -- RFC Ed.: When the above assignment has been made, please 300 -- remove the above note 301 -- replace "XXX" here with the assigned value and 302 -- remove this note. 304 -- The major groups 306 mip6Notifications OBJECT IDENTIFIER ::= { mip6MIB 0 } 307 mip6Objects OBJECT IDENTIFIER ::= { mip6MIB 1 } 308 mip6Conformance OBJECT IDENTIFIER ::= { mip6MIB 2 } 309 mip6Core OBJECT IDENTIFIER ::= { mip6Objects 1 } 310 mip6Mn OBJECT IDENTIFIER ::= { mip6Objects 2 } 311 mip6Cn OBJECT IDENTIFIER ::= { mip6Objects 3 } 312 mip6Ha OBJECT IDENTIFIER ::= { mip6Objects 4 } 313 -- The sub groups 315 mip6System OBJECT IDENTIFIER ::= { mip6Core 1 } 316 mip6Bindings OBJECT IDENTIFIER ::= { mip6Core 2 } 317 mip6Stats OBJECT IDENTIFIER ::= { mip6Core 3 } 319 mip6MnSystem OBJECT IDENTIFIER ::= { mip6Mn 1 } 320 mip6MnConf OBJECT IDENTIFIER ::= { mip6Mn 2 } 321 mip6MnRegistration OBJECT IDENTIFIER ::= { mip6Mn 3 } 323 mip6CnSystem OBJECT IDENTIFIER ::= { mip6Cn 1 } 324 mip6CnStats OBJECT IDENTIFIER ::= { mip6Cn 2 } 326 mip6HaAdvertisement OBJECT IDENTIFIER ::= { mip6Ha 1 } 327 mip6HaStats OBJECT IDENTIFIER ::= { mip6Ha 2 } 329 -- Textual Conventions 330 Mip6BURequestRejectionCode ::= TEXTUAL-CONVENTION 331 STATUS current 332 DESCRIPTION 333 "The value of the status field in the Binding 334 Acknowledgment message when the Binding Update 335 was rejected. 336 " 337 REFERENCE 338 "RFC3775 : Section 6.1.8" 339 SYNTAX INTEGER { 340 reasonUnspecified (1), --(Code 128) 341 admProhibited (2), --(Code 129) 342 insufficientResource (3), --(Code 130) 343 homeRegistrationNotSupported (4), --(Code 131) 344 notHomeSubnet (5), --(Code 132) 345 notHomeAgentForThisMobileNode (6), --(Code 133) 346 duplicateAddressDetectionFailed (7), --(Code 134) 347 sequenceNumberOutOfWindow (8), --(Code 135) 348 expiredHomeNonceIndex (9), --(Code 136) 349 expiredCareofNonceIndex (10), --(Code 137) 350 expiredNonces (11), --(Code 138) 351 registrationTypeChangeDisallowed(12) --(Code 139) 352 } 354 mip6Capabilities OBJECT-TYPE 355 SYNTAX BITS { 356 mobileNode (0), 357 homeAgent (1), 358 correspondentNode (2) 359 } 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "This object indicates the Mobile IPv6 functions that 364 are supported by this managed entity. Multiple 365 Mobile IPv6 functions may be supported by a single 366 entity. 367 " 368 REFERENCE 369 "RFC3775 : Section 3.2, 4.1" 370 ::= { mip6System 1 } 372 mip6Status OBJECT-TYPE 373 SYNTAX INTEGER { enabled(1), disabled(2) } 374 MAX-ACCESS read-write 375 STATUS current 376 DESCRIPTION 377 "This object indicates whether the Mobile IPv6 378 function is enabled for the managed entity. If it 379 is enabled, the agent discovery and registration 380 functions will be operational. 381 Changing the status from enabled(1) to disabled(2) 382 will terminate the agent discovery and registration 383 functions. On the other hand, changing the status 384 from disabled(2) to enabled(1) will start the agent 385 discovery and registration functions. 387 The value of this object SHOULD remain unchanged 388 across reboots of the managed entity. 389 " 390 ::= { mip6System 2 } 392 -- mip6BindingCache 393 mip6BindingCacheTable OBJECT-TYPE 394 SYNTAX SEQUENCE OF Mip6BindingCacheEntry 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "This table models the Binding Cache on the 399 managed entity. The cache is maintained by home 400 agents and correspondent nodes. It contains 401 both correspondent registration entries and home 402 registration entries. 404 Entries in this table are not required to survive 405 a reboot of the managed entity. 406 " 407 REFERENCE 408 "RFC3775 : Section 4.5, 9.1, 10.1" 409 ::= { mip6Bindings 1 } 411 mip6BindingCacheEntry OBJECT-TYPE 412 SYNTAX Mip6BindingCacheEntry 413 MAX-ACCESS not-accessible 414 STATUS current 415 DESCRIPTION 416 "This entry represents a conceptual row in the 417 binding cache table. It represents a single Binding 418 Update. 420 Implementors need to be aware that if the total 421 number of octets in mip6BindingHomeAddress 422 exceeds 113 then OIDs of column 423 instances in this row will have more than 128 424 sub-identifiers and cannot be accessed using 425 SNMPv1, SNMPv2c, or SNMPv3. 426 " 427 INDEX { mip6BindingHomeAddressType, mip6BindingHomeAddress } 428 ::= { mip6BindingCacheTable 1 } 430 Mip6BindingCacheEntry ::= 431 SEQUENCE { 432 mip6BindingHomeAddressType InetAddressType, 433 mip6BindingHomeAddress InetAddress, 434 mip6BindingCOAType InetAddressType, 435 mip6BindingCOA InetAddress, 436 mip6BindingTimeRegistered DateAndTime, 437 mip6BindingTimeGranted Gauge32, 438 mip6BindingTimeRemaining Gauge32, 439 mip6BindingHomeRegn TruthValue, 440 mip6BindingMaxSeq Unsigned32, 441 mip6BindingUsageTS DateAndTime, 442 mip6BindingUsageCount Gauge32, 443 mip6BindingAdminStatus INTEGER 444 } 446 mip6BindingHomeAddressType OBJECT-TYPE 447 SYNTAX InetAddressType 448 MAX-ACCESS not-accessible 449 STATUS current 450 DESCRIPTION 451 "The InetAddressType of the mip6BindingHomeAddress 452 that follows. 453 " 454 ::= { mip6BindingCacheEntry 1 } 456 mip6BindingHomeAddress OBJECT-TYPE 457 SYNTAX InetAddress 458 MAX-ACCESS not-accessible 459 STATUS current 460 DESCRIPTION 461 "The home address of the mobile node corresponding 462 to the Binding Cache entry. This field is used as 463 the key for searching the mobile node's current 464 care-of address in the Binding Cache. 466 The type of the address represented by this object 467 is specified by the corresponding 468 mip6BindingHomeAddressType object. 469 " 470 REFERENCE 471 "RFC3775 : Section 9.1" 472 ::= { mip6BindingCacheEntry 2 } 474 mip6BindingCOAType OBJECT-TYPE 475 SYNTAX InetAddressType 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The InetAddressType of the mip6BindingCOA that 480 follows. 481 " 482 ::= { mip6BindingCacheEntry 3 } 484 mip6BindingCOA OBJECT-TYPE 485 SYNTAX InetAddress 486 MAX-ACCESS read-only 487 STATUS current 488 DESCRIPTION 489 "The care-of address of the mobile node indicated by 490 the home address field (mip6BindingHomeAddress) in 491 this Binding Cache entry. 493 The type of the address represented by this object 494 is specified by the corresponding mip6BindingCOAType 495 object. 496 " 497 REFERENCE 498 "RFC3775 : Section 9.1" 499 ::= { mip6BindingCacheEntry 4 } 501 mip6BindingTimeRegistered OBJECT-TYPE 502 SYNTAX DateAndTime 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The timestamp when this Binding Cache entry was 507 created. 508 " 509 ::= { mip6BindingCacheEntry 5 } 511 mip6BindingTimeGranted OBJECT-TYPE 512 SYNTAX Gauge32 513 UNITS "seconds" 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "The lifetime in seconds granted to the mobile node 518 for this registration. 519 " 520 ::= { mip6BindingCacheEntry 6 } 522 mip6BindingTimeRemaining OBJECT-TYPE 523 SYNTAX Gauge32 524 UNITS "seconds" 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "The lifetime in seconds remaining for this 529 registration. 530 " 531 REFERENCE 532 "RFC3775 : Section 9.1" 533 ::= { mip6BindingCacheEntry 7 } 535 mip6BindingHomeRegn OBJECT-TYPE 536 SYNTAX TruthValue 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "This object indicates whether or not this Binding 541 Cache entry is a home registration entry (applicable 542 only on nodes which support home agent 543 functionality). 544 " 545 REFERENCE 546 "RFC3775 : Section 9.1" 547 ::= { mip6BindingCacheEntry 8 } 549 mip6BindingMaxSeq OBJECT-TYPE 550 SYNTAX Unsigned32 (0..65536) 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "The maximum value of the Sequence Number field 555 received in previous Binding Updates for this home 556 address (mip6BindingHomeAddress). 557 " 558 REFERENCE 559 "RFC3775 : Section 9.1, 9.5.1" 560 ::= { mip6BindingCacheEntry 9 } 562 mip6BindingUsageTS OBJECT-TYPE 563 SYNTAX DateAndTime 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "The timestamp when this entry was last looked up. 568 " 569 REFERENCE 570 "RFC3775 : Section 9.1" 571 ::= { mip6BindingCacheEntry 10 } 573 mip6BindingUsageCount OBJECT-TYPE 574 SYNTAX Gauge32 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The number of times this entry was looked up. 579 " 580 REFERENCE 581 "RFC3775 : Section 9.1" 582 ::= { mip6BindingCacheEntry 11 } 584 mip6BindingAdminStatus OBJECT-TYPE 585 SYNTAX INTEGER { 586 active (1), 587 inactive (2) 588 } 589 MAX-ACCESS read-write 590 STATUS current 591 DESCRIPTION 592 "This is an administrative object used to control 593 the status of a binding cache entry. By default 594 the value will be 'active'(1). 595 A value of 'inactive'(2) will indicate that the 596 validity of the entry is suspended. It does not 597 exist in the binding cache for all practical 598 purposes. 599 The state can be changed from 'active' to 600 'inactive' by operator intervention. 601 Causing the state to change to 'inactive' results 602 in the entry being deleted from the cache. 603 Attempts to change the status from 'inactive' 604 to 'active' will be rejected. 605 " 606 REFERENCE 607 "RFC3775 : Section 9.1" 608 ::= { mip6BindingCacheEntry 12 } 610 -- mip6BindingHistory 611 -- Once the lifetime expires an entry will be removed from the 612 -- Binding Cache. 613 -- For monitoring purposes it will be useful to have access to 614 -- the history of the Binding Cache. BindingHistoryTable serves 615 -- this purpose. It records the history of the Bindings. 616 -- The size of the table will be left to implementers. 618 mip6BindingHistoryTable OBJECT-TYPE 619 SYNTAX SEQUENCE OF Mip6BindingHistoryEntry 620 MAX-ACCESS not-accessible 621 STATUS current 622 DESCRIPTION 623 "A table containing a record of the bindings. 624 " 625 ::= { mip6Bindings 2 } 627 mip6BindingHistoryEntry OBJECT-TYPE 628 SYNTAX Mip6BindingHistoryEntry 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "The record of a binding. 634 Implementors need to be aware that if the total 635 number of octets in mip6BindingHstHomeAddress 636 exceeds 112 then OIDs of column 637 instances in this row will have more than 128 638 sub-identifiers and cannot be accessed using 639 SNMPv1, SNMPv2c, or SNMPv3. 640 " 641 INDEX { mip6BindingHstHomeAddressType, 642 mip6BindingHstHomeAddress , 643 mip6BindingHstIndex} 644 ::= { mip6BindingHistoryTable 1 } 646 Mip6BindingHistoryEntry ::= 647 SEQUENCE { 648 mip6BindingHstHomeAddressType InetAddressType, 649 mip6BindingHstHomeAddress InetAddress, 650 mip6BindingHstIndex Unsigned32, 651 mip6BindingHstCOAType InetAddressType, 652 mip6BindingHstCOA InetAddress, 653 mip6BindingHstTimeRegistered DateAndTime, 654 mip6BindingHstTimeExpired DateAndTime, 655 mip6BindingHstHomeRegn TruthValue, 656 mip6BindingHstUsageTS DateAndTime, 657 mip6BindingHstUsageCount Gauge32 658 } 660 mip6BindingHstHomeAddressType OBJECT-TYPE 661 SYNTAX InetAddressType 662 MAX-ACCESS not-accessible 663 STATUS current 664 DESCRIPTION 665 "The InetAddressType of the 666 mip6BindingHstHomeAddress that follows. 667 " 668 ::= { mip6BindingHistoryEntry 1 } 670 mip6BindingHstHomeAddress OBJECT-TYPE 671 SYNTAX InetAddress 672 MAX-ACCESS not-accessible 673 STATUS current 674 DESCRIPTION 675 "Mobile node's home address. 677 The type of the address represented by this object 678 is specified by the corresponding 679 mip6BindingHstHomeAddressType object. 680 " 681 ::= { mip6BindingHistoryEntry 2 } 683 mip6BindingHstIndex OBJECT-TYPE 684 SYNTAX Unsigned32 (1..4294967295) 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "The index to uniquely identify this record along 689 with the mobile node's HomeAddress type and 690 HomeAddress. It should be monotonically increasing. 691 It may wrap after reaching its max value." 692 ::= { mip6BindingHistoryEntry 3 } 694 mip6BindingHstCOAType OBJECT-TYPE 695 SYNTAX InetAddressType 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "The InetAddressType of the mip6BindingHstCOA that 700 follows. 701 " 702 ::= { mip6BindingHistoryEntry 4 } 704 mip6BindingHstCOA OBJECT-TYPE 705 SYNTAX InetAddress 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "Mobile node's care-of address. One mobile node can 710 have multiple bindings with different 711 care-of addresses. 712 The type of the address represented by this object 713 is specified by the corresponding 714 mip6BindingHstCOAType object. 715 " 716 ::= { mip6BindingHistoryEntry 5 } 718 mip6BindingHstTimeRegistered OBJECT-TYPE 719 SYNTAX DateAndTime 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "The timestamp when this Binding Cache entry was 724 created. 725 " 726 ::= { mip6BindingHistoryEntry 6 } 728 mip6BindingHstTimeExpired OBJECT-TYPE 729 SYNTAX DateAndTime 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "The timestamp when this Binding Cache entry expired. 734 " 735 ::= { mip6BindingHistoryEntry 7 } 737 mip6BindingHstHomeRegn OBJECT-TYPE 738 SYNTAX TruthValue 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION 742 "This object indicates whether or not this Binding 743 Cache entry is a home registration entry (applicable 744 only on nodes which support home agent 745 functionality). 746 " 747 ::= { mip6BindingHistoryEntry 8 } 749 mip6BindingHstUsageTS OBJECT-TYPE 750 SYNTAX DateAndTime 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "The timestamp when this entry was last looked up. 755 " 756 ::= { mip6BindingHistoryEntry 9 } 758 mip6BindingHstUsageCount OBJECT-TYPE 759 SYNTAX Gauge32 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "The number of times this entry was looked up. 764 " 765 ::= { mip6BindingHistoryEntry 10 } 767 -- mip6TrafficCounters 769 -- MIPv6 Traffic will be characterized by 770 -- IPv6 datagrams which satisfy at least one of the following 771 -- conditions 772 -- - the datagrams are tunneled to the mobile node by the HA 773 -- - the datagrams are reverse tunneled by the MN to the HA 774 -- - the datagrams have the Routing header type 2 set. 775 -- - the datagrams have the Home Address option set in the 776 -- Destination Option extension header 777 -- - the datagrams have the mobility header 779 mip6TotalTraffic OBJECT IDENTIFIER ::= { mip6Stats 1 } 780 -- REFERENCE 781 -- "RFC3775 : Section 4.1, 6.3, 6.4" 782 mip6InOctets OBJECT-TYPE 783 SYNTAX Counter32 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "The total number of octets in the MIPv6 datagrams 788 received by the MIPv6 entity. This will include 789 datagrams with the Mobility Header, the Home Address 790 option in the Destination Option extension header 791 (Next Header value = 60) or the type 2 Routing 792 Header. It will also include the IPv6 datagrams that 793 are reverse tunneled to a home agent from a mobile 794 node's home address. 795 Discontinuities in the value of this counter can 796 occur at re-initialization of the management system, 797 and at other times as indicated by the value of 798 mip6CounterDiscontinuityTime. 799 " 800 REFERENCE 801 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 802 ::= { mip6TotalTraffic 1 } 804 mip6HCInOctets OBJECT-TYPE 805 SYNTAX Counter64 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "The total number of octets in the MIPv6 datagrams 810 received by the MIPv6 entity. This will include 811 datagrams with the Mobility Header, the Home Address 812 option in the Destination Option extension header 813 (Next Header value = 60) or the type 2 Routing 814 Header. It will also include the IPv6 datagrams that 815 are reverse tunneled to a home agent from a mobile 816 node's home address. 817 This object is a 64-bit version of mip6InOctets. 818 Discontinuities in the value of this counter can 819 occur at re-initialization of the management system, 820 and at other times as indicated by the value of 821 mip6CounterDiscontinuityTime. 822 " 823 REFERENCE 824 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 825 ::= { mip6TotalTraffic 2 } 827 mip6InPkts OBJECT-TYPE 828 SYNTAX Counter32 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "The number of MIPv6 datagrams received by the MIPv6 833 entity. This will include datagrams with the 834 Mobility Header, the Home Address option in the 835 Destination Option extension header (Next Header 836 value = 60) or the type 2 Routing Header. 837 It will also include the IPv6 datagrams that are 838 reverse tunneled to a home agent from a mobile 839 node's home address. 840 Discontinuities in the value of this counter can 841 occur at re-initialization of the management system, 842 and at other times as indicated by the value of 843 mip6CounterDiscontinuityTime. 844 " 845 REFERENCE 846 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 847 ::= { mip6TotalTraffic 3 } 849 mip6HCInPkts OBJECT-TYPE 850 SYNTAX Counter64 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The number of MIPv6 datagrams received by the MIPv6 855 entity. This will include datagrams with the 856 Mobility Header, the Home Address option in the 857 Destination Option extension header (Next Header 858 value = 60) or the type 2 Routing Header. It will 859 also include the IPv6 datagrams that are reverse 860 tunneled to a home agent from a mobile node's home 861 address. 862 This object is a 64-bit version of mip6InPkts. 863 Discontinuities in the value of this counter can 864 occur at re-initialization of the management system, 865 and at other times as indicated by the value of 866 mip6CounterDiscontinuityTime. 867 " 868 REFERENCE 869 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 870 ::= { mip6TotalTraffic 4 } 872 mip6OutOctets OBJECT-TYPE 873 SYNTAX Counter32 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION 877 "The total number of octets in the MIPv6 datagrams 878 sent by the MIPv6 entity. This will include 879 datagrams with the Mobility Header, the Home Address 880 option in the Destination Option extension header 881 (Next Header value = 60) or the type 2 Routing 882 Header. It will also include the IPv6 datagrams that 883 are reverse tunneled to a home agent from a mobile 884 node's home address. 885 Discontinuities in the value of this counter can 886 occur at re-initialization of the management system, 887 and at other times as indicated by the value of 888 mip6CounterDiscontinuityTime. 889 " 890 REFERENCE 891 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 892 ::= { mip6TotalTraffic 5 } 894 mip6HCOutOctets OBJECT-TYPE 895 SYNTAX Counter64 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "The total number of octets in the MIPv6 datagrams 900 sent by the MIPv6 entity. This will include 901 datagrams with the Mobility Header, the Home Address 902 option in the Destination Option extension header 903 (Next Header value = 60) or the type 2 Routing 904 Header. It will also include the IPv6 datagrams that 905 are reverse tunneled to a home agent from a mobile 906 node's home address. 907 This object is a 64-bit version of mip6OutOctets. 908 Discontinuities in the value of this counter can 909 occur at re-initialization of the management system, 910 and at other times as indicated by the value of 911 mip6CounterDiscontinuityTime. 912 " 913 REFERENCE 914 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 915 ::= { mip6TotalTraffic 6 } 917 mip6OutPkts OBJECT-TYPE 918 SYNTAX Counter32 919 MAX-ACCESS read-only 920 STATUS current 921 DESCRIPTION 922 "The number of MIPv6 datagrams sent by the MIPv6 923 entity. This will include the datagrams with 924 Mobility Header, the Home Address option in the 925 Destination Option extension header (Next Header 926 value = 60) or the type 2 Routing Header. It will 927 also include the IPv6 datagrams that are reverse 928 tunneled to a home agent from a mobile node's home 929 address. 930 Discontinuities in the value of this counter can 931 occur at re-initialization of the management system, 932 and at other times as indicated by the value of 933 mip6CounterDiscontinuityTime. 934 " 935 REFERENCE 936 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 937 ::= { mip6TotalTraffic 7 } 939 mip6HCOutPkts OBJECT-TYPE 940 SYNTAX Counter64 941 MAX-ACCESS read-only 942 STATUS current 943 DESCRIPTION 944 "The number of MIPv6 datagrams sent by the MIPv6 945 entity. This will include datagrams with the 946 Mobility Header, the Home Address option in the 947 Destination Option extension header (Next Header 948 value = 60) or the type 2 Routing Header. It will 949 also include the IPv6 datagrams that are reverse 950 tunneled to a home agent from a mobile node's home 951 address. 952 This object is a 64-bit version of mip6OutPkts. 953 Discontinuities in the value of this counter can 954 occur at re-initialization of the management system, 955 and at other times as indicated by the value of 956 mip6CounterDiscontinuityTime. 957 " 958 REFERENCE 959 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 960 ::= { mip6TotalTraffic 8 } 962 mip6CounterDiscontinuityTime OBJECT-TYPE 963 SYNTAX TimeStamp 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION 967 "The value of sysUpTime on the most recent occasion 968 at which any one or more of this MIPv6 entities 969 global counters viz, counters with OID prefix 970 'mip6TotalTraffic' or 'mip6CnGlobalStats' or 971 'mip6HaGlobalStats' suffered a discontinuity. 972 If no such discontinuities have occurred since the 973 last re-initialization of the local management 974 subsystem, then this object will have a zero value. 975 " 976 ::= { mip6TotalTraffic 9 } 978 -- mip6NodeTrafficCounters 980 mip6NodeTrafficTable OBJECT-TYPE 981 SYNTAX SEQUENCE OF Mip6NodeTrafficEntry 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "A table containing MIPv6 traffic counters per mobile 986 node. 987 " 988 ::= { mip6Stats 2 } 990 mip6NodeTrafficEntry OBJECT-TYPE 991 SYNTAX Mip6NodeTrafficEntry 992 MAX-ACCESS not-accessible 993 STATUS current 994 DESCRIPTION 995 "The MIPv6 traffic statistics for a mobile node. 997 Implementors need to be aware that if the total 998 number of octets in mip6BindingHomeAddress 999 exceeds 113 then OIDs of column 1000 instances in this row will have more than 128 1001 sub-identifiers and cannot be accessed using 1002 SNMPv1, SNMPv2c, or SNMPv3. 1003 " 1004 INDEX { mip6BindingHomeAddressType, mip6BindingHomeAddress } 1005 ::= { mip6NodeTrafficTable 1 } 1007 Mip6NodeTrafficEntry ::= 1008 SEQUENCE { 1009 mip6NodeInOctets Counter32, 1010 mip6HCNodeInOctets Counter64, 1011 mip6NodeInPkts Counter32, 1012 mip6HCNodeInPkts Counter64, 1013 mip6NodeOutOctets Counter32, 1014 mip6HCNodeOutOctets Counter64, 1015 mip6NodeOutPkts Counter32, 1016 mip6HCNodeOutPkts Counter64, 1017 mip6NodeCtrDiscontinuityTime TimeStamp 1018 } 1020 mip6NodeInOctets OBJECT-TYPE 1021 SYNTAX Counter32 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "The total number of octets in the MIPv6 datagrams 1026 received from the mobile node by the MIPv6 entity. 1027 This will include datagrams with the Mobility 1028 Header or the Home Address option in the Destination 1029 Option extension header (Next Header value = 60). 1030 It will also include the IPv6 datagrams that are 1031 reverse tunneled to a home agent from the mobile 1032 node's home address. 1033 Discontinuities in the value of this counter can 1034 occur at re-initialization of the management system, 1035 and at other times as indicated by the value of 1036 mip6NodeCtrDiscontinuityTime. 1037 " 1038 REFERENCE 1039 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1040 ::= { mip6NodeTrafficEntry 1 } 1042 mip6HCNodeInOctets 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 1048 received from the mobile node by the MIPv6 entity. 1049 This will include datagrams with the Mobility 1050 Header or the Home Address option in the Destination 1051 Option extension header (Next Header value = 60). It 1052 will also include the IPv6 datagrams that are 1053 reverse tunneled to a home agent from the mobile 1054 node's home address. 1055 This object is a 64-bit version of mip6NodeInOctets. 1056 Discontinuities in the value of this counter can 1057 occur at re-initialization of the management system, 1058 and at other times as indicated by the value of 1059 mip6NodeCtrDiscontinuityTime. 1060 " 1061 REFERENCE 1062 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1063 ::= { mip6NodeTrafficEntry 2 } 1065 mip6NodeInPkts OBJECT-TYPE 1066 SYNTAX Counter32 1067 MAX-ACCESS read-only 1068 STATUS current 1069 DESCRIPTION 1070 "The number of MIPv6 datagrams received from the 1071 mobile node by the MIPv6 entity. This will include 1072 the datagrams with the Mobility Header or 1073 the Home Address option in the Destination 1074 Option extension header (Next Header value = 60). It 1075 will also include the IPv6 datagrams that are 1076 reverse tunneled to a home agent from the mobile 1077 node's home address. 1078 Discontinuities in the value of this counter can 1079 occur at re-initialization of the management system, 1080 and at other times as indicated by the value of 1081 mip6NodeCtrDiscontinuityTime. 1082 " 1083 REFERENCE 1084 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1085 ::= { mip6NodeTrafficEntry 3 } 1087 mip6HCNodeInPkts OBJECT-TYPE 1088 SYNTAX Counter64 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "The number of MIPv6 datagrams received from the 1093 mobile node by the MIPv6 entity. This will include 1094 datagrams with the Mobility Header or the Home 1095 Address option in the Destination Option extension 1096 header (Next Header value = 60). It will also 1097 include the IPv6 datagrams that are reverse tunneled 1098 to a home agent from the mobile node's home address. 1099 This object is a 64-bit version of mip6NodeInPkts. 1100 Discontinuities in the value of this counter can 1101 occur at re-initialization of the management system, 1102 and at other times as indicated by the value of 1103 mip6NodeCtrDiscontinuityTime. 1104 " 1105 REFERENCE 1106 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1107 ::= { mip6NodeTrafficEntry 4 } 1109 mip6NodeOutOctets OBJECT-TYPE 1110 SYNTAX Counter32 1111 MAX-ACCESS read-only 1112 STATUS current 1113 DESCRIPTION 1114 "The total number of octets in the MIPv6 datagrams 1115 sent to the mobile node by the MIPv6 entity. This 1116 will include datagrams with the Mobility Header 1117 or the type 2 Routing Header. It will also include 1118 the IPv6 datagrams that are tunneled by a home agent 1119 to the mobile node. 1120 Discontinuities in the value of this counter can 1121 occur at re-initialization of the management system, 1122 and at other times as indicated by the value of 1123 mip6NodeCtrDiscontinuityTime. 1124 " 1125 REFERENCE 1126 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1127 ::= { mip6NodeTrafficEntry 5 } 1129 mip6HCNodeOutOctets OBJECT-TYPE 1130 SYNTAX Counter64 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "The total number of octets in the MIPv6 datagrams 1135 sent to the mobile node by the MIPv6 entity. This 1136 will include datagrams with the Mobility Header 1137 or the type 2 Routing Header. It will also include 1138 the IPv6 datagrams that are tunneled by a home agent 1139 to the mobile node. 1140 This object is a 64-bit version of mip6NodeOutOctets. 1141 Discontinuities in the value of this counter can 1142 occur at re-initialization of the management system, 1143 and at other times as indicated by the value of 1144 mip6NodeCtrDiscontinuityTime. 1145 " 1146 REFERENCE 1147 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1148 ::= { mip6NodeTrafficEntry 6 } 1150 mip6NodeOutPkts OBJECT-TYPE 1151 SYNTAX Counter32 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "The number of MIPv6 datagrams sent to the mobile 1156 node by the MIPv6 entity. This will include 1157 datagrams with the Mobility Header or the type 2 1158 Routing Header. It will also include the IPv6 1159 datagrams that are tunneled by a home agent to the 1160 mobile node. 1161 Discontinuities in the value of this counter can 1162 occur at re-initialization of the management system, 1163 and at other times as indicated by the value of 1164 mip6NodeCtrDiscontinuityTime. 1165 " 1166 REFERENCE 1167 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1168 ::= { mip6NodeTrafficEntry 7 } 1170 mip6HCNodeOutPkts OBJECT-TYPE 1171 SYNTAX Counter64 1172 MAX-ACCESS read-only 1173 STATUS current 1174 DESCRIPTION 1175 "The number of MIPv6 datagrams sent to the mobile 1176 node by the MIPv6 entity. This will include 1177 datagrams with the Mobility Header or the type 2 1178 Routing Header. It will also include the IPv6 1179 datagrams that are tunneled by a home agent to the 1180 mobile node. 1181 This object is a 64-bit version of mip6NodeOutOctets. 1182 Discontinuities in the value of this counter can 1183 occur at re-initialization of the management system, 1184 and at other times as indicated by the value of 1185 mip6NodeCtrDiscontinuityTime. 1186 " 1187 REFERENCE 1188 "RFC3775 : Section 6.1, 6.3, 6.4, 10.4.5" 1189 ::= { mip6NodeTrafficEntry 8 } 1191 mip6NodeCtrDiscontinuityTime OBJECT-TYPE 1192 SYNTAX TimeStamp 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The value of sysUpTime on the most recent occasion 1197 at which any one or more of the counters in this row 1198 suffered a discontinuity. The relevant counters are 1199 the specific instances of any Counter32 or Counter64 1200 objects in this row. 1201 If no such discontinuities have occurred since the 1202 last re-initialization of the local management 1203 subsystem, then this object contains a zero value. 1204 " 1205 ::= { mip6NodeTrafficEntry 9 } 1207 -- mip6MnSystem Group 1209 mip6MnHomeAddressTable OBJECT-TYPE 1210 SYNTAX SEQUENCE OF Mip6MnHomeAddressEntry 1211 MAX-ACCESS not-accessible 1212 STATUS current 1213 DESCRIPTION 1214 "A table containing registration status for all the 1215 home addresses pertaining to the mobile node. 1216 " 1217 ::= { mip6MnSystem 1 } 1219 mip6MnHomeAddressEntry OBJECT-TYPE 1220 SYNTAX Mip6MnHomeAddressEntry 1221 MAX-ACCESS not-accessible 1222 STATUS current 1223 DESCRIPTION 1224 "The registration status for a home address. 1226 Implementors need to be aware that if the total 1227 number of octets in mip6MnHomeAddress 1228 exceeds 113 then OIDs of column instances in 1229 this row will have more than 128 sub-identifiers and 1230 cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 1231 " 1232 INDEX { mip6MnHomeAddressType, mip6MnHomeAddress } 1233 ::= { mip6MnHomeAddressTable 1 } 1235 Mip6MnHomeAddressEntry ::= 1236 SEQUENCE { 1237 mip6MnHomeAddressType InetAddressType, 1238 mip6MnHomeAddress InetAddress, 1239 mip6MnHomeAddressState INTEGER 1240 } 1242 mip6MnHomeAddressType OBJECT-TYPE 1243 SYNTAX InetAddressType 1244 MAX-ACCESS not-accessible 1245 STATUS current 1246 DESCRIPTION 1247 "The InetAddressType of the mip6MnHomeAddress that 1248 follows. 1249 " 1250 ::= { mip6MnHomeAddressEntry 1 } 1252 mip6MnHomeAddress OBJECT-TYPE 1253 SYNTAX InetAddress 1254 MAX-ACCESS not-accessible 1255 STATUS current 1256 DESCRIPTION 1257 "A unicast routable address assigned to the mobile 1258 node. This is used as the 'permanent address' of the 1259 mobile node in the sense that it remains unchanged 1260 regardless of the mobile node's current point of 1261 attachment. If mobile node doesn't have a home 1262 address assigned yet then this object will take the 1263 default 'unspecified' value ::0. 1265 The type of the address represented by this object 1266 is specified by the corresponding 1267 mip6MnHomeAddressType object. 1268 " 1269 REFERENCE 1270 "RFC3775 : Section 3.2" 1271 ::= { mip6MnHomeAddressEntry 2 } 1273 mip6MnHomeAddressState OBJECT-TYPE 1274 SYNTAX INTEGER { 1275 unknown(1), 1276 home(2), 1277 registered(3), 1278 pending(4), 1279 isolated(5) 1280 } 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "This object indicates the state of the mobile node: 1285 unknown -- The state of the mobile node 1286 cannot be determined 1287 home -- mobile node is on the home network. 1288 registered -- mobile node is on a foreign network 1289 and is registered with the home 1290 agent 1291 pending -- mobile node has sent registration 1292 request to the home agent and is 1293 waiting for the reply 1294 isolated -- mobile node is isolated from network 1295 i.e. it is not in its home network, 1296 it is not registered and no 1297 registration ack is pending 1298 " 1299 ::= { mip6MnHomeAddressEntry 3 } 1301 -- Mobile Node Discovery and Advertisement Group Counters 1303 mip6MnDiscoveryRequests OBJECT-TYPE 1304 SYNTAX Counter32 1305 MAX-ACCESS read-only 1306 STATUS current 1307 DESCRIPTION 1308 "Total number of ICMP Dynamic Home Agent Address 1309 Discovery Requests sent by the mobile node. 1310 Discontinuities in the value of this counter can 1311 occur at re-initialization of the management system, 1312 and at other times as indicated by the value of 1313 mip6CounterDiscontinuityTime. 1314 " 1315 REFERENCE 1316 "RFC3775 : Section 10.5, 11.4.1" 1317 ::= { mip6MnConf 1 } 1319 mip6MnDiscoveryReplies OBJECT-TYPE 1320 SYNTAX Counter32 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "Total number of ICMP Dynamic Home Agent Address 1325 Discovery Replies received by the mobile node. 1326 Discontinuities in the value of this counter can 1327 occur at re-initialization of the management system, 1328 and at other times as indicated by the value of 1329 mip6CounterDiscontinuityTime. 1330 " 1331 REFERENCE 1332 "RFC3775 : Section 10.5, 11.4.1" 1333 ::= { mip6MnConf 2 } 1335 mip6MnDiscoveryTimeouts OBJECT-TYPE 1336 SYNTAX Counter32 1337 MAX-ACCESS read-only 1338 STATUS current 1339 DESCRIPTION 1340 "Total number of ICMP Dynamic Home Agent Address 1341 Discovery Requests that timed out. 1342 Discontinuities in the value of this counter can 1343 occur at re-initialization of the management system, 1344 and at other times as indicated by the value of 1345 mip6CounterDiscontinuityTime. 1346 " 1347 REFERENCE 1348 "RFC3775 : Section 10.5, 11.4.1, 12" 1349 ::= { mip6MnConf 3 } 1351 mip6MnPrefixSolicitationsSent OBJECT-TYPE 1352 SYNTAX Counter32 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "Total number of ICMP Mobile Prefix Solicitations 1357 sent by the mobile node. 1358 Discontinuities in the value of this counter can 1359 occur at re-initialization of the management system, 1360 and at other times as indicated by the value of 1361 mip6CounterDiscontinuityTime. 1362 " 1363 REFERENCE 1364 "RFC3775 : Section 10.5, 11.4.2" 1365 ::= { mip6MnConf 4 } 1367 mip6MnPrefixAdvsRecd OBJECT-TYPE 1368 SYNTAX Counter32 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "Total number of ICMP Mobile Prefix Advertisements 1373 received by the mobile node. This will include the 1374 ICMP Mobile Prefix Advertisements that failed the 1375 validity checks. 1376 Discontinuities in the value of this counter can 1377 occur at re-initialization of the management system, 1378 and at other times as indicated by the value of 1379 mip6CounterDiscontinuityTime. 1380 " 1381 REFERENCE 1382 "RFC3775 : Section 10.6, 11.4.3" 1383 ::= { mip6MnConf 5 } 1385 mip6MnPrefixAdvsIgnored OBJECT-TYPE 1386 SYNTAX Counter32 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "Total number of Mobile Prefix Advertisements 1391 discarded by the validity check. 1392 Discontinuities in the value of this counter can 1393 occur at re-initialization of the management system, 1394 and at other times as indicated by the value of 1395 mip6CounterDiscontinuityTime. 1396 " 1397 REFERENCE 1398 "RFC3775 : Section 10.6, 11.4.3" 1399 ::= { mip6MnConf 6 } 1401 mip6MnMovedToFN OBJECT-TYPE 1402 SYNTAX Counter32 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "Number of times the mobile node has detected 1407 movement to a foreign network from another 1408 foreign network or from the home network, has 1409 reconstructed its care-of address and has initiated 1410 the care-of address registration process. 1411 Discontinuities in the value of this counter can 1412 occur at re-initialization of the management system, 1413 and at other times as indicated by the value of 1414 mip6CounterDiscontinuityTime. 1415 " 1416 REFERENCE 1417 "RFC3775 : Section 11.5.1" 1418 ::= { mip6MnConf 7 } 1420 mip6MnMovedToHN OBJECT-TYPE 1421 SYNTAX Counter32 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "Number of times the mobile node has detected 1426 movement from a foreign network to its home 1427 network. 1428 Discontinuities in the value of this counter can 1429 occur at re-initialization of the management system, 1430 and at other times as indicated by the value of 1431 mip6CounterDiscontinuityTime. 1432 " 1433 REFERENCE 1434 "RFC3775 : Section 11.5.4" 1435 ::= { mip6MnConf 8 } 1437 -- Mobile Node Registration Group 1439 -- Registration table of mobile node 1440 mip6MnBLTable OBJECT-TYPE 1441 SYNTAX SEQUENCE OF Mip6MnBLEntry 1442 MAX-ACCESS not-accessible 1443 STATUS current 1444 DESCRIPTION 1445 "This table corresponds to the Binding Update List 1446 (BL) that is maintained by the mobile node. The list 1447 holds an item for every binding that the mobile node 1448 has established or is trying to establish. Both 1449 correspondent and home registrations are included in 1450 this table. Entries from the table are deleted as 1451 the lifetime of the binding expires. 1452 " 1453 REFERENCE 1454 "RFC3775 : Section 4.5, 11.1" 1455 ::= { mip6MnRegistration 1 } 1457 mip6MnBLEntry OBJECT-TYPE 1458 SYNTAX Mip6MnBLEntry 1459 MAX-ACCESS not-accessible 1460 STATUS current 1461 DESCRIPTION 1462 "Information about a Binding Update sent by the 1463 mobile node either to its home agent or to one of 1464 its correspondent nodes. 1466 Implementors need to be aware that if the total 1467 number of octets in mip6MnHomeAddress and 1468 mip6MnBLNodeAddress exceeds 111 then OIDs of column 1469 instances in this row will have more than 128 1470 sub-identifiers and cannot be accessed using 1471 SNMPv1, SNMPv2c, or SNMPv3. 1472 " 1473 INDEX { mip6MnHomeAddressType, 1474 mip6MnHomeAddress, 1475 mip6MnBLNodeAddressType, 1476 mip6MnBLNodeAddress 1477 } 1478 ::= { mip6MnBLTable 1 } 1480 Mip6MnBLEntry ::= SEQUENCE { 1481 mip6MnBLNodeAddressType InetAddressType, 1482 mip6MnBLNodeAddress InetAddress, 1483 mip6MnBLCOAType InetAddressType, 1484 mip6MnBLCOA InetAddress, 1485 mip6MnBLLifeTimeRequested Unsigned32, 1486 mip6MnBLLifeTimeGranted Unsigned32, 1487 mip6MnBLMaxSeq Unsigned32, 1488 mip6MnBLTimeSent DateAndTime, 1489 mip6MnBLAccepted TruthValue, 1490 mip6MnBLAcceptedTime DateAndTime, 1491 mip6MnBLRetransmissions Gauge32, 1492 mip6MnBLDontSendBUFlag TruthValue 1493 } 1495 mip6MnBLNodeAddressType OBJECT-TYPE 1496 SYNTAX InetAddressType 1497 MAX-ACCESS not-accessible 1498 STATUS current 1499 DESCRIPTION 1500 "The InetAddressType of the mip6MnBLNodeAddress 1501 that follows. 1502 " 1503 ::= { mip6MnBLEntry 1 } 1505 mip6MnBLNodeAddress OBJECT-TYPE 1506 SYNTAX InetAddress 1507 MAX-ACCESS not-accessible 1508 STATUS current 1509 DESCRIPTION 1510 "The address of the agent as used in the destination 1511 address of the Binding Update. The agent 1512 may be a home agent or a correspondent node. 1514 The type of the address represented by this object 1515 is specified by the corresponding 1516 mip6MnBLNodeAddressType object. 1518 " 1519 REFERENCE 1520 "RFC3775 : Section 11.1" 1521 ::= { mip6MnBLEntry 2 } 1523 mip6MnBLCOAType OBJECT-TYPE 1524 SYNTAX InetAddressType 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "The InetAddressType of the mip6MnBLCOA that follows. 1529 " 1530 ::= { mip6MnBLEntry 3 } 1532 mip6MnBLCOA OBJECT-TYPE 1533 SYNTAX InetAddress 1534 MAX-ACCESS read-only 1535 STATUS current 1536 DESCRIPTION 1537 "Care-of address that the mobile node intends to 1538 register in the Binding Update request. 1540 The type of the address represented by this object 1541 is specified by the corresponding mip6MnBLCOAType 1542 object. 1543 " 1544 REFERENCE 1545 "RFC3775 : Section 11.1" 1546 ::= { mip6MnBLEntry 4 } 1548 mip6MnBLLifeTimeRequested OBJECT-TYPE 1549 SYNTAX Unsigned32 1550 UNITS "seconds" 1551 MAX-ACCESS read-only 1552 STATUS current 1553 DESCRIPTION 1554 "The lifetime requested by the mobile node (in 1555 seconds) in the Binding Update. 1556 " 1557 REFERENCE 1558 "RFC3775 : Section 11.1" 1559 ::= { mip6MnBLEntry 5 } 1561 mip6MnBLLifeTimeGranted OBJECT-TYPE 1562 SYNTAX Unsigned32 1563 UNITS "seconds" 1564 MAX-ACCESS read-only 1565 STATUS current 1566 DESCRIPTION 1567 "The lifetime granted to the mobile node for this 1568 binding. This field will be inaccessible if the 1569 Binding Update request has not been accepted. 1570 The lifetime remaining (lR) can be calculated using 1571 the current time (cT), mip6MnBLAcceptedTime (aT) and 1572 mip6MnBLLifeTimeGranted (lG) as follows 1573 lR = lG - (cT - aT). 1574 When lR is zero this entry will be deleted from the 1575 Binding Update List and consequently from this 1576 table. 1577 " 1578 ::= { mip6MnBLEntry 6 } 1580 mip6MnBLMaxSeq OBJECT-TYPE 1581 SYNTAX Unsigned32 (0..65536) 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "The maximum value of the Sequence Number field sent 1586 in previous Binding Updates to this destination. 1587 " 1588 REFERENCE 1589 "RFC3775 : Section 11.1" 1590 ::= { mip6MnBLEntry 7 } 1592 mip6MnBLTimeSent OBJECT-TYPE 1593 SYNTAX DateAndTime 1594 MAX-ACCESS read-only 1595 STATUS current 1596 DESCRIPTION 1597 "The time when the last (re-)transmission occurred." 1598 REFERENCE 1599 "RFC3775 : Section 11.1" 1600 ::= { mip6MnBLEntry 8 } 1602 mip6MnBLAccepted OBJECT-TYPE 1603 SYNTAX TruthValue 1604 MAX-ACCESS read-only 1605 STATUS current 1606 DESCRIPTION 1607 "true(1) if the mobile node has received a 1608 binding acknowledgment indicating that service has 1609 been accepted (status code 0 or 1); false(2) 1610 otherwise. false(2) implies that the registration 1611 is still pending. 1612 " 1613 ::= { mip6MnBLEntry 9 } 1615 mip6MnBLAcceptedTime OBJECT-TYPE 1616 SYNTAX DateAndTime 1617 MAX-ACCESS read-only 1618 STATUS current 1619 DESCRIPTION 1620 "The time at which the mobile node receives a binding 1621 acknowledgment indicating that Binding Update has 1622 been accepted (status code 0 or 1); 1623 This object will be inaccessible if the Binding 1624 Update request is still pending. 1625 " 1626 ::= { mip6MnBLEntry 10 } 1628 mip6MnBLRetransmissions OBJECT-TYPE 1629 SYNTAX Gauge32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "The number of Binding Update retransmissions. 1634 " 1635 REFERENCE 1636 "RFC3775 : Section 11.1" 1637 ::= { mip6MnBLEntry 11 } 1639 mip6MnBLDontSendBUFlag OBJECT-TYPE 1640 SYNTAX TruthValue 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "true(1) indicates that future binding updates 1645 will not be sent to mip6MnBLNodeAddress. 1646 false(2) implies that binding updates will be 1647 sent to mip6MnBLNodeAddress. 1648 The mobile node sets this flag in the when it 1649 receives an ICMP Parameter Problem, Code 1, 1650 error message in response to a return 1651 routability message or Binding Update sent to 1652 mip6MnBLNodeAddress. 1653 " 1654 REFERENCE 1655 "RFC3775 : Section 11.1" 1656 ::= { mip6MnBLEntry 12 } 1658 -- Mobile Node Registration Group Counters 1660 mip6MnRegnCounters OBJECT IDENTIFIER ::= { mip6MnRegistration 2 } 1662 mip6MnMobilityMessagesSent OBJECT-TYPE 1663 SYNTAX Counter32 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "The total number of mobility messages, i.e. IPv6 1668 datagrams with Mobility Header, sent by the mobile 1669 node. There are 3 types of mobility messages viz. 1670 Home Test Init, Care-of Test Init, and Binding 1671 Updates that are sent by mobile nodes. 1672 Discontinuities in the value of this counter can 1673 occur at re-initialization of the management system, 1674 and at other times as indicated by the value of 1675 mip6CounterDiscontinuityTime. 1676 " 1677 REFERENCE 1678 "RFC3775 : Section 4.2, 6.1" 1679 ::= { mip6MnRegnCounters 1 } 1681 mip6MnMobilityMessagesRecd OBJECT-TYPE 1682 SYNTAX Counter32 1683 MAX-ACCESS read-only 1684 STATUS current 1685 DESCRIPTION 1686 "The total number of mobility messages, i.e. IPv6 1687 datagrams with Mobility Header, received by the 1688 mobile node. There are 5 types of mobility messages 1689 viz. Home Test, Care-of Test, Binding 1690 Acknowledgment, Binding Refresh Request and Binding 1691 Error that are sent to mobile nodes. 1692 Discontinuities in the value of this counter can 1693 occur at re-initialization of the management system, 1694 and at other times as indicated by the value of 1695 mip6CounterDiscontinuityTime. 1696 " 1697 REFERENCE 1698 "RFC3775 : Section 4.2, 6.1" 1699 ::= { mip6MnRegnCounters 2 } 1701 mip6MnBUsToHA OBJECT-TYPE 1702 SYNTAX Counter32 1703 MAX-ACCESS read-only 1704 STATUS current 1705 DESCRIPTION 1706 "Total number of Binding Updates sent to the mobile 1707 node's home agent(s). 1708 Discontinuities in the value of this counter can 1709 occur at re-initialization of the management system, 1710 and at other times as indicated by the value of 1711 mip6CounterDiscontinuityTime. 1712 " 1713 REFERENCE 1714 "RFC3775 : Section 11.7.1" 1715 ::= { mip6MnRegnCounters 3 } 1717 mip6MnBUAcksFromHA OBJECT-TYPE 1718 SYNTAX Counter32 1719 MAX-ACCESS read-only 1720 STATUS current 1721 DESCRIPTION 1722 "Total number of valid binding acknowledgments 1723 received from the mobile nodes home agent(s). 1724 Discontinuities in the value of this counter can 1725 occur at re-initialization of the management system, 1726 and at other times as indicated by the value of 1727 mip6CounterDiscontinuityTime. 1728 " 1729 REFERENCE 1730 "RFC3775 : Section 11.7.3" 1731 ::= { mip6MnRegnCounters 4 } 1733 mip6MnBUsToCN OBJECT-TYPE 1734 SYNTAX Counter32 1735 MAX-ACCESS read-only 1736 STATUS current 1737 DESCRIPTION 1738 "Total number of Binding Updates sent to 1739 correspondent nodes by the mobile node. 1740 Discontinuities in the value of this counter can 1741 occur at re-initialization of the management system, 1742 and at other times as indicated by the value of 1743 mip6CounterDiscontinuityTime. 1744 " 1745 REFERENCE 1746 "RFC3775 : Section 11.7.2" 1747 ::= { mip6MnRegnCounters 5 } 1749 mip6MnBUAcksFromCN OBJECT-TYPE 1750 SYNTAX Counter32 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "Total number of valid Binding Update acks 1755 received from all the correspondent nodes. 1756 Discontinuities in the value of this counter can 1757 occur at re-initialization of the management system, 1758 and at other times as indicated by the value of 1759 mip6CounterDiscontinuityTime. 1760 " 1761 REFERENCE 1762 "RFC3775 : Section 11.7.3" 1763 ::= { mip6MnRegnCounters 6 } 1765 mip6MnBindingErrorsFromCN OBJECT-TYPE 1766 SYNTAX Counter32 1767 MAX-ACCESS read-only 1768 STATUS current 1769 DESCRIPTION 1770 "Total number of Binding Error messages received 1771 by mobile node from CN. 1772 Discontinuities in the value of this counter can 1773 occur at re-initialization of the management system, 1774 and at other times as indicated by the value of 1775 mip6CounterDiscontinuityTime. 1776 " 1777 ::= { mip6MnRegnCounters 7 } 1779 mip6MnICMPErrorsRecd OBJECT-TYPE 1780 SYNTAX Counter32 1781 MAX-ACCESS read-only 1782 STATUS current 1783 DESCRIPTION 1784 "Total number of ICMP Error messages of type ICMP 1785 Parameter Problem, Code 1 or Code 2 received by 1786 the mobile node from a correspondent node in 1787 response to a return routability procedure, a 1788 Binding Update or a packet with the Home Address 1789 option. 1790 Discontinuities in the value of this counter can 1791 occur at re-initialization of the management system, 1792 and at other times as indicated by the value of 1793 mip6CounterDiscontinuityTime. 1794 " 1795 REFERENCE 1796 "RFC3775 : Section 11.3.5" 1797 ::= { mip6MnRegnCounters 8 } 1799 mip6MnBRRequestsRecd OBJECT-TYPE 1800 SYNTAX Counter32 1801 MAX-ACCESS read-only 1802 STATUS current 1803 DESCRIPTION 1804 "The total number of Binding Refresh requests 1805 received by the mobile node from Corresponding 1806 nodes. 1807 Discontinuities in the value of this counter can 1808 occur at re-initialization of the management system, 1809 and at other times as indicated by the value of 1810 mip6CounterDiscontinuityTime. 1811 " 1812 REFERENCE 1813 "RFC3775 : Section 11.7.4" 1814 ::= { mip6MnRegnCounters 9 } 1816 -- Registration Group counters used for Correspondent Node 1817 mip6CnGlobalStats OBJECT IDENTIFIER ::= { mip6CnStats 1 } 1819 mip6CnHomeTestInitsRecd OBJECT-TYPE 1820 SYNTAX Counter32 1821 MAX-ACCESS read-only 1822 STATUS current 1823 DESCRIPTION 1824 "Total number of Home Test Init messages received. 1825 Discontinuities in the value of this counter can 1826 occur at re-initialization of the management system, 1827 and at other times as indicated by the value of 1828 mip6CounterDiscontinuityTime. 1829 " 1830 REFERENCE 1831 "RFC3775 : Section 9.4.1" 1832 ::= { mip6CnGlobalStats 1 } 1834 mip6CnHomeTestsSent OBJECT-TYPE 1835 SYNTAX Counter32 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION 1839 "Total number of Home Test messages sent. If a Home 1840 Test Init message is found to be valid, a Home Test 1841 message will be generated and sent. Otherwise the 1842 Home Test message is silently discarded. 1843 Discontinuities in the value of this counter can 1844 occur at re-initialization of the management system, 1845 and at other times as indicated by the value of 1846 mip6CounterDiscontinuityTime. 1847 " 1848 REFERENCE 1849 "RFC3775 : Section 9.4.3" 1850 ::= { mip6CnGlobalStats 2 } 1852 mip6CnCareOfTestInitsRecd OBJECT-TYPE 1853 SYNTAX Counter32 1854 MAX-ACCESS read-only 1855 STATUS current 1856 DESCRIPTION 1857 "Total number of Care-of Test Init messages received. 1858 " 1859 REFERENCE 1860 "RFC3775 : Section 9.4.2" 1861 ::= { mip6CnGlobalStats 3 } 1863 mip6CnCareOfTestsSent OBJECT-TYPE 1864 SYNTAX Counter32 1865 MAX-ACCESS read-only 1866 STATUS current 1867 DESCRIPTION 1868 "Total number of Care-of Test messages sent. If a 1869 Care-of Test Init message is found to be valid, a 1870 Care-of Test message will be generated and sent. 1871 Otherwise the Care-of Test message is silently 1872 discarded. 1873 Discontinuities in the value of this counter can 1874 occur at re-initialization of the management system, 1875 and at other times as indicated by the value of 1876 mip6CounterDiscontinuityTime. 1877 " 1878 REFERENCE 1879 "RFC3775 : Section 9.4.4" 1880 ::= { mip6CnGlobalStats 4 } 1882 mip6CnBUsRecd OBJECT-TYPE 1883 SYNTAX Counter32 1884 MAX-ACCESS read-only 1885 STATUS current 1886 DESCRIPTION 1887 "Total number of Binding Updates received by the 1888 correspondent node from mobile nodes. 1889 Discontinuities in the value of this counter can 1890 occur at re-initialization of the management system, 1891 and at other times as indicated by the value of 1892 mip6CounterDiscontinuityTime. 1893 " 1894 REFERENCE 1895 "RFC3775 : Section 9.5.1" 1896 ::= { mip6CnGlobalStats 5 } 1898 mip6CnBUAcksSent OBJECT-TYPE 1899 SYNTAX Counter32 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "Total number of acknowledgments sent by the 1904 correspondent node for the Binding Updates received. 1905 Discontinuities in the value of this counter can 1906 occur at re-initialization of the management system, 1907 and at other times as indicated by the value of 1908 mip6CounterDiscontinuityTime. 1909 " 1910 REFERENCE 1911 "RFC3775 : Section 9.5.4" 1912 ::= { mip6CnGlobalStats 6 } 1914 mip6CnBRsSent OBJECT-TYPE 1915 SYNTAX Counter32 1916 MAX-ACCESS read-only 1917 STATUS current 1918 DESCRIPTION 1919 "Total number of Binding Refresh Request messages 1920 sent by the correspondent node. 1921 Discontinuities in the value of this counter can 1922 occur at re-initialization of the management system, 1923 and at other times as indicated by the value of 1924 mip6CounterDiscontinuityTime. 1925 " 1926 REFERENCE 1927 "RFC3775 : Section 9.5.5" 1928 ::= { mip6CnGlobalStats 7 } 1930 mip6CnBindingErrors OBJECT-TYPE 1931 SYNTAX Counter32 1932 MAX-ACCESS read-only 1933 STATUS current 1934 DESCRIPTION 1935 "Total number of Binding Error messages sent by the 1936 correspondent node to the mobile node. 1937 Discontinuities in the value of this counter can 1938 occur at re-initialization of the management system, 1939 and at other times as indicated by the value of 1940 mip6CounterDiscontinuityTime. 1941 " 1942 REFERENCE 1943 "RFC3775 : Section 9.3.3" 1944 ::= { mip6CnGlobalStats 8 } 1946 mip6CnBUsAccepted OBJECT-TYPE 1947 SYNTAX Counter32 1948 MAX-ACCESS read-only 1949 STATUS current 1950 DESCRIPTION 1951 "Total number of Binding Updates accepted by the 1952 correspondent node. If a Binding Acknowledgment 1953 message is sent for the Binding Update request, 1954 the Status code field in the message will have 1955 a value less than 128. 1956 Discontinuities in the value of this counter can 1957 occur at re-initialization of the management system, 1958 and at other times as indicated by the value of 1959 mip6CounterDiscontinuityTime. 1960 " 1961 REFERENCE 1962 "RFC3775 : Section 9.5.1, 9.5.4" 1963 ::= { mip6CnGlobalStats 9 } 1965 mip6CnBUsRejected OBJECT-TYPE 1966 SYNTAX Counter32 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 "Total number of Binding Update requests rejected 1971 by the correspondent node. If a Binding 1972 Acknowledgment message has been sent for the Binding 1973 Update request, the Status code field in the 1974 message will have a value greater than or equal to 1975 128. Otherwise the Binding Update request will be 1976 silently discarded. 1977 Discontinuities in the value of this counter can 1978 occur at re-initialization of the management system, 1979 and at other times as indicated by the value of 1980 mip6CounterDiscontinuityTime. 1981 " 1982 REFERENCE 1983 "RFC3775 : Section 9.5.1, 9.5.4" 1984 ::= { mip6CnGlobalStats 10 } 1986 mip6CnReasonUnspecified OBJECT-TYPE 1987 SYNTAX Counter32 1988 MAX-ACCESS read-only 1989 STATUS current 1990 DESCRIPTION 1991 "Total number of Binding Update requests rejected by 1992 the correspondent node with status code in the 1993 Binding Acknowledgment message indicating 'reason 1994 unspecified' (Code 128). 1995 Discontinuities in the value of this counter can 1996 occur at re-initialization of the management system, 1997 and at other times as indicated by the value of 1998 mip6CounterDiscontinuityTime. 1999 " 2000 REFERENCE 2001 "RFC3775 : Section 6.1.8" 2002 ::= { mip6CnGlobalStats 11 } 2004 mip6CnInsufficientResource OBJECT-TYPE 2005 SYNTAX Counter32 2006 MAX-ACCESS read-only 2007 STATUS current 2008 DESCRIPTION 2009 "Total number of Binding Update requests rejected by 2010 the correspondent node with status code in the 2011 Binding Acknowledgment message indicating 2012 'insufficient resources' (Code 130). 2013 Discontinuities in the value of this counter can 2014 occur at re-initialization of the management system, 2015 and at other times as indicated by the value of 2016 mip6CounterDiscontinuityTime. 2017 " 2018 REFERENCE 2019 "RFC3775 : Section 6.1.8" 2020 ::= { mip6CnGlobalStats 12 } 2022 mip6CnHomeRegnNotSupported OBJECT-TYPE 2023 SYNTAX Counter32 2024 MAX-ACCESS read-only 2025 STATUS current 2026 DESCRIPTION 2027 "Total number of Binding Update requests rejected by 2028 correspondent node with status code in the Binding 2029 Acknowledgment message indicating 'home registration 2030 not supported' (Code 131). 2031 Discontinuities in the value of this counter can 2032 occur at re-initialization of the management system, 2033 and at other times as indicated by the value of 2034 mip6CounterDiscontinuityTime. 2035 " 2036 REFERENCE 2037 "RFC3775 : Section 10.3.1" 2038 ::= { mip6CnGlobalStats 13 } 2040 mip6CnSeqNumberOutOfWindow OBJECT-TYPE 2041 SYNTAX Counter32 2042 MAX-ACCESS read-only 2043 STATUS current 2044 DESCRIPTION 2045 "Total number of Binding Updates rejected by 2046 correspondent node with status code in the Binding 2047 Acknowledgment message indicating 'sequence number 2048 out of window' (Code 135). 2049 Discontinuities in the value of this counter can 2050 occur at re-initialization of the management system, 2051 and at other times as indicated by the value of 2052 mip6CounterDiscontinuityTime. 2053 " 2054 REFERENCE 2055 "RFC3775 : Section 6.1.8, 9.5.1" 2056 ::= { mip6CnGlobalStats 14 } 2058 mip6CnExpiredHomeNonceIndex OBJECT-TYPE 2059 SYNTAX Counter32 2060 MAX-ACCESS read-only 2061 STATUS current 2062 DESCRIPTION 2063 "The total number of Binding Updates rejected by 2064 correspondent node with status code in the Binding 2065 Acknowledgment message indicating 'expired home 2066 nonce index' (Code 136). 2067 Discontinuities in the value of this counter can 2068 occur at re-initialization of the management system, 2069 and at other times as indicated by the value of 2070 mip6CounterDiscontinuityTime. 2071 " 2072 REFERENCE 2073 "RFC3775 : Section 6.1.8, 9.5.1" 2074 ::= { mip6CnGlobalStats 15 } 2076 mip6CnExpiredCareOfNonceIndex OBJECT-TYPE 2077 SYNTAX Counter32 2078 MAX-ACCESS read-only 2079 STATUS current 2080 DESCRIPTION 2081 "The total number of Binding Updates rejected by 2082 correspondent node with status code in the Binding 2083 Acknowledgment message indicating 'expired 2084 care-of nonce index' (Code 137). 2085 Discontinuities in the value of this counter can 2086 occur at re-initialization of the management system, 2087 and at other times as indicated by the value of 2088 mip6CounterDiscontinuityTime. 2089 " 2090 REFERENCE 2091 "RFC3775 : Section 6.1.8, 9.5.1" 2092 ::= { mip6CnGlobalStats 16 } 2094 mip6CnExpiredNonce OBJECT-TYPE 2095 SYNTAX Counter32 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION 2099 "The total number of Binding Updates rejected by 2100 correspondent node with status code in the Binding 2101 Acknowledgment message indicating 'expired nonces' 2102 (Code 138) i.e. the correspondent node no longer 2103 recognizes the Home Nonce Index value and the 2104 Care-of Nonce Index value. 2105 Discontinuities in the value of this counter can 2106 occur at re-initialization of the management system, 2107 and at other times as indicated by the value of 2108 mip6CounterDiscontinuityTime. 2109 " 2110 REFERENCE 2111 "RFC3775 : Section 6.1.8, 9.5.1" 2112 ::= { mip6CnGlobalStats 17 } 2114 mip6CnRegTypeChangeDisallowed OBJECT-TYPE 2115 SYNTAX Counter32 2116 MAX-ACCESS read-only 2117 STATUS current 2118 DESCRIPTION 2119 "The total number of Binding Updates rejected by 2120 correspondent node with status code in the Binding 2121 Acknowledgment message indicating 'registration 2122 type change disallowed' (Code 139, i.e., a binding 2123 already exists for the given home address and the 2124 home registration flag has a different value than 2125 the Home Registration (H) bit in the Binding Update. 2126 Discontinuities in the value of this counter can 2127 occur at re-initialization of the management system, 2128 and at other times as indicated by the value of 2129 mip6CounterDiscontinuityTime. 2130 " 2131 REFERENCE 2132 "RFC3775 : Section 6.1.8, 9.5.1" 2133 ::= { mip6CnGlobalStats 18 } 2135 -- The Correspondent Node statistics by mobile node 2137 mip6CnCounterTable OBJECT-TYPE 2138 SYNTAX SEQUENCE OF Mip6CnCounterEntry 2139 MAX-ACCESS not-accessible 2140 STATUS current 2141 DESCRIPTION 2142 "A table containing each mobile ." 2143 ::= { mip6CnStats 2 } 2145 mip6CnCounterEntry OBJECT-TYPE 2146 SYNTAX Mip6CnCounterEntry 2147 MAX-ACCESS not-accessible 2148 STATUS current 2149 DESCRIPTION 2150 "The set of correspondent node counters for a mobile 2151 node. 2153 Implementors need to be aware that if the total 2154 number of octets in mip6BindingHomeAddress 2155 exceeds 113 then OIDs of column instances in 2156 this row will have more than 128 sub-identifiers and 2157 cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 2158 " 2159 INDEX { mip6BindingHomeAddressType, 2160 mip6BindingHomeAddress 2161 } 2162 ::= { mip6CnCounterTable 1 } 2164 Mip6CnCounterEntry ::= 2165 SEQUENCE { 2166 mip6CnBURequestsAccepted Counter32, 2167 mip6CnBURequestsRejected Counter32, 2168 mip6CnBCEntryCreationTime DateAndTime, 2169 mip6CnBUAcceptedTime DateAndTime, 2170 mip6CnBURejectionTime DateAndTime, 2171 mip6CnBURejectionCode Mip6BURequestRejectionCode, 2172 mip6CnCtrDiscontinuityTime TimeStamp 2173 } 2175 mip6CnBURequestsAccepted OBJECT-TYPE --(Code 0,1) 2176 SYNTAX Counter32 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 "Total number of Binding Update requests from the 2181 mobile node accepted by the correspondent node. 2182 If Binding Acknowledgment messages are sent, then 2183 the Status code in the message will have a value 2184 less than 128. 2185 Discontinuities in the value of this counter can 2186 occur at re-initialization of the management system, 2187 and at other times as indicated by the value of 2188 mip6CnCtrDiscontinuityTime. 2189 " 2190 ::= { mip6CnCounterEntry 1 } 2192 mip6CnBURequestsRejected OBJECT-TYPE 2193 -- (Code 128 through Code 159) 2194 SYNTAX Counter32 2195 MAX-ACCESS read-only 2196 STATUS current 2197 DESCRIPTION 2198 "Total number of Binding Update requests from the 2199 mobile node which have been rejected by the 2200 correspondent node. This includes the Binding Update 2201 requests for which a Binding Acknowledgment message 2202 has been sent with Status code value greater than or 2203 equal to 128 and the Binding Acknowledgment requests 2204 which have been silently discarded. 2205 Discontinuities in the value of this counter can 2206 occur at re-initialization of the management system, 2207 and at other times as indicated by the value of 2208 mip6CnCtrDiscontinuityTime. 2209 " 2210 ::= { mip6CnCounterEntry 2 } 2212 mip6CnBCEntryCreationTime OBJECT-TYPE 2213 SYNTAX DateAndTime 2214 MAX-ACCESS read-only 2215 STATUS current 2216 DESCRIPTION 2217 "The time when the current Binding Cache entry was 2218 created for the mobile node. 2219 " 2220 ::= { mip6CnCounterEntry 3 } 2222 mip6CnBUAcceptedTime OBJECT-TYPE 2223 SYNTAX DateAndTime 2224 MAX-ACCESS read-only 2225 STATUS current 2226 DESCRIPTION 2227 "The time at which the last Binding Update was 2228 accepted by the correspondent node and the 2229 corresponding Binding Cache entry was updated. 2230 " 2231 ::= { mip6CnCounterEntry 4 } 2233 mip6CnBURejectionTime OBJECT-TYPE 2234 SYNTAX DateAndTime 2235 MAX-ACCESS read-only 2236 STATUS current 2237 DESCRIPTION 2238 "The time at which the last Binding Update message 2239 was rejected by the correspondent node. 2240 If there have been no rejections then this object 2241 will be inaccessible. 2242 " 2243 ::= { mip6CnCounterEntry 5 } 2245 mip6CnBURejectionCode OBJECT-TYPE 2246 SYNTAX Mip6BURequestRejectionCode 2247 MAX-ACCESS read-only 2248 STATUS current 2249 DESCRIPTION 2250 "If a Binding Acknowledgment is sent to the mobile 2251 node, this is the Status code (> 128) that is 2252 returned in the Binding Acknowledgment. 2253 In case a Binding Acknowledgment is not sent to 2254 the mobile node then this will be the value that 2255 of the Status code that corresponds to the reason 2256 of the rejection. If there have been no rejections 2257 then this object will be inaccessible. 2258 " 2259 REFERENCE 2260 "RFC3775 : Section 6.1.8" 2262 ::= { mip6CnCounterEntry 6 } 2264 mip6CnCtrDiscontinuityTime OBJECT-TYPE 2265 SYNTAX TimeStamp 2266 MAX-ACCESS read-only 2267 STATUS current 2268 DESCRIPTION 2269 "The value of sysUpTime on the most recent occasion 2270 at which any one or more of counters in this row 2271 viz, instances of 'mip6CnBURequestsAccepted' and 2272 'mip6CnBURequestsRejected' suffered a discontinuity. 2273 If no such discontinuities have occurred since the 2274 last re-initialization of the local management 2275 subsystem, then this object will have a zero value. 2276 " 2277 ::= { mip6CnCounterEntry 7 } 2279 -- Home agent group 2280 mip6HaAdvsRecd OBJECT-TYPE 2281 SYNTAX Counter32 2282 MAX-ACCESS read-only 2283 STATUS current 2284 DESCRIPTION 2285 "Total number of valid Router Advertisements 2286 received with the Home Agent (H) bit set, on 2287 all the links on which it is serving as a Home 2288 Agent. 2289 Discontinuities in the value of this counter can 2290 occur at re-initialization of the management system, 2291 and at other times as indicated by the value of 2292 mip6CounterDiscontinuityTime. 2293 " 2294 REFERENCE 2295 "RFC3775 : Section 7" 2296 ::= { mip6HaAdvertisement 1 } 2298 mip6HaAdvsSent OBJECT-TYPE 2299 SYNTAX Counter32 2300 MAX-ACCESS read-only 2301 STATUS current 2302 DESCRIPTION 2303 "Total number of unsolicited multicast Router 2304 Advertisements sent with the Home Agent (H) bit set, 2305 on all the links on which the router is serving as 2306 a Home Agent. 2307 Discontinuities in the value of this counter can 2308 occur at re-initialization of the management system, 2309 and at other times as indicated by the value of 2310 mip6CounterDiscontinuityTime. 2311 " 2312 REFERENCE 2313 "RFC3775 : Section 7" 2314 ::= { mip6HaAdvertisement 2 } 2316 mip6HaConfTable OBJECT-TYPE 2317 SYNTAX SEQUENCE OF Mip6HaConfEntry 2318 MAX-ACCESS not-accessible 2319 STATUS current 2320 DESCRIPTION 2321 "A table containing configurable advertisement 2322 parameters for all interfaces on which the 2323 home agent service is advertised. 2324 It is RECOMMENDED that the last written values 2325 of the objects in the conceptual rows of this 2326 table will remain unchanged across reboots of 2327 the managed entity provided that, the interfaces 2328 have not been renumbered after the reboot. 2329 " 2330 ::= { mip6HaAdvertisement 3 } 2332 mip6HaConfEntry OBJECT-TYPE 2333 SYNTAX Mip6HaConfEntry 2334 MAX-ACCESS not-accessible 2335 STATUS current 2336 DESCRIPTION 2337 "Advertisement parameters for an interface. 2338 The instances of the columnar objects in this entry 2339 pertain to the interface which is uniquely identified 2340 by the ipv6InterfaceIfIndex of the interface. The 2341 same ipv6InterfaceIfIndex object is used to uniquely 2342 identify instances of the columnar objects of this 2343 conceptual row. 2344 " 2345 INDEX { ipv6InterfaceIfIndex } 2346 ::= { mip6HaConfTable 1 } 2348 Mip6HaConfEntry ::= SEQUENCE { 2349 mip6HaAdvPreference Integer32, 2350 mip6HaAdvLifetime Integer32, 2351 mip6HaPrefixAdv INTEGER, 2352 mip6HaPrefixSolicitation INTEGER, 2353 mip6HaMCastCtlMsgSupport INTEGER 2354 } 2356 mip6HaAdvPreference OBJECT-TYPE 2357 SYNTAX Integer32 (0..65536) 2358 MAX-ACCESS read-write 2359 STATUS current 2360 DESCRIPTION 2361 "The preference value for the home agent to 2362 be used in the Router Advertisements. Higher 2363 value denotes greater preference. 2364 " 2365 REFERENCE 2366 "RFC3775 : Section 7.4, 8.4" 2367 ::= { mip6HaConfEntry 1 } 2369 mip6HaAdvLifetime OBJECT-TYPE 2370 SYNTAX Integer32 (1..65535) 2371 UNITS "seconds" 2372 MAX-ACCESS read-write 2373 STATUS current 2374 DESCRIPTION 2375 "The lifetime value for the home agent to be 2376 used in the Router Advertisements. 2377 " 2378 REFERENCE 2379 "RFC3775 : Section 7.4" 2380 ::= { mip6HaConfEntry 2 } 2382 mip6HaPrefixAdv OBJECT-TYPE 2383 SYNTAX INTEGER { enabled(1), disabled(2) } 2384 MAX-ACCESS read-write 2385 STATUS current 2386 DESCRIPTION 2387 "Indicates whether the home agent should support 2388 sending of the ICMP Mobile Prefix Advertisements. 2389 If it is disabled(2), the home agent will not 2390 send ICMP Mobile Prefix Advertisements to the 2391 mobile nodes. 2392 The state can be changed from enabled(1) to 2393 disabled(2) and vice versa by operator 2394 intervention. 2395 Causing the state to change from enabled(1) to 2396 disabled(2) will result in the home agent 2397 disabling the Prefix advertisement function. 2398 On the other hand, changing the status from 2399 disabled(2) to enabled(1) will start the prefix 2400 advertisement funtion. 2401 " 2402 REFERENCE 2403 "RFC3775 : Section 8.4" 2404 ::= { mip6HaConfEntry 3} 2406 mip6HaPrefixSolicitation OBJECT-TYPE 2407 SYNTAX INTEGER { enabled(1), disabled(2) } 2408 MAX-ACCESS read-write 2409 STATUS current 2410 DESCRIPTION 2411 "Indicates whether the home agent should respond 2412 to ICMP Mobile Prefix Solicitation messages it 2413 receives from the mobile nodes. By default, the 2414 value will be set to enabled(1). If it is 2415 disabled(2), the home agent will not respond to 2416 any ICMP Mobile Prefix Solicitation messages. 2417 The state can be changed from enabled(1) to 2418 disabled(2), by operator intervention. Causing 2419 the state to change from enabled(1) to 2420 disabled(2) will result in the home agent not 2421 responding to any ICMP Mobile Prefix 2422 Solicitation messages it receives from the 2423 mobile nodes. 2424 " 2425 REFERENCE 2426 "RFC3775 : Section 8.4" 2427 ::= { mip6HaConfEntry 4} 2429 mip6HaMCastCtlMsgSupport OBJECT-TYPE 2430 SYNTAX INTEGER { enabled(1), disabled(2) } 2431 MAX-ACCESS read-write 2432 STATUS current 2433 DESCRIPTION 2434 "Indicates whether the home agent should enable 2435 support for the processing of the multicast 2436 group membership control messages it receives 2437 from the mobile nodes. By default, the value 2438 will be set to enabled(1). If it is 2439 disabled(2), the home agent will not process 2440 any multicast group control messages it receives 2441 from the mobile nodes. 2442 The state can be changed from enabled(1) to 2443 disabled(2), by operator intervention. Causing 2444 the state to change from enabled(1) to 2445 disabled(2) will result in the home agent 2446 disabling the processing of the multicast group 2447 control messages it received from the mobile 2448 nodes. 2449 " 2450 REFERENCE 2451 "RFC3775 : Section 10.4.3" 2452 ::= { mip6HaConfEntry 5} 2454 -- Registration Group counters HA 2456 mip6HaGlobalStats OBJECT IDENTIFIER ::= { mip6HaStats 1 } 2458 mip6HaHomeTestInitsRecd OBJECT-TYPE 2459 SYNTAX Counter32 2460 MAX-ACCESS read-only 2461 STATUS current 2462 DESCRIPTION 2463 "Total number of Home Test Init messages received by 2464 the home agent. This will include Home Test Init 2465 messages that failed the validity checks. 2466 Discontinuities in the value of this counter can 2467 occur at re-initialization of the management system, 2468 and at other times as indicated by the value of 2469 mip6CounterDiscontinuityTime. 2470 " 2471 REFERENCE 2472 "RFC3775 : Section 5.2.5" 2473 ::= { mip6HaGlobalStats 1 } 2475 mip6HaHomeTestsSent OBJECT-TYPE 2476 SYNTAX Counter32 2477 MAX-ACCESS read-only 2478 STATUS current 2479 DESCRIPTION 2480 "Total number of Home Test messages sent by the 2481 home agent. 2482 Discontinuities in the value of this counter can 2483 occur at re-initialization of the management system, 2484 and at other times as indicated by the value of 2485 mip6CounterDiscontinuityTime. 2486 " 2487 REFERENCE 2488 "RFC3775 : Section 5.2.5" 2489 ::= { mip6HaGlobalStats 2 } 2491 mip6HaBUsRecd OBJECT-TYPE 2492 SYNTAX Counter32 2493 MAX-ACCESS read-only 2494 STATUS current 2495 DESCRIPTION 2496 "Total number of Binding Updates received by the 2497 home agent. 2498 Discontinuities in the value of this counter can 2499 occur at re-initialization of the management system, 2500 and at other times as indicated by the value of 2501 mip6CounterDiscontinuityTime. 2502 " 2503 REFERENCE 2504 "RFC3775 : Section 10.3.1" 2505 ::= { mip6HaGlobalStats 3 } 2507 mip6HaBUAcksSent OBJECT-TYPE 2508 SYNTAX Counter32 2509 MAX-ACCESS read-only 2510 STATUS current 2511 DESCRIPTION 2512 "Total number of Binding Acknowledgments sent 2513 by the home agent. 2514 Discontinuities in the value of this counter can 2515 occur at re-initialization of the management system, 2516 and at other times as indicated by the value of 2517 mip6CounterDiscontinuityTime. 2518 " 2519 REFERENCE 2520 "RFC3775 : Section 10.3.1" 2521 ::= { mip6HaGlobalStats 4 } 2523 mip6HaBRAdviceSent OBJECT-TYPE 2524 SYNTAX Counter32 2525 MAX-ACCESS read-only 2526 STATUS current 2527 DESCRIPTION 2528 "Total number of Binding Acknowledgments sent 2529 by the home agent with Binding Refresh Advice 2530 mobility option included. 2531 Discontinuities in the value of this counter can 2532 occur at re-initialization of the management system, 2533 and at other times as indicated by the value of 2534 mip6CounterDiscontinuityTime. 2535 " 2536 REFERENCE 2537 "RFC3775 : Section 10.3.1" 2538 ::= { mip6HaGlobalStats 5 } 2540 mip6HaBUsAccepted OBJECT-TYPE 2541 SYNTAX Counter32 2542 MAX-ACCESS read-only 2543 STATUS current 2544 DESCRIPTION 2545 "Total number of Binding Updates accepted by this HA. 2546 Binding Acknowledgment with Status code of 0 or 1. 2547 Discontinuities in the value of this counter can 2548 occur at re-initialization of the management system, 2549 and at other times as indicated by the value of 2550 mip6CounterDiscontinuityTime. 2551 " 2552 REFERENCE 2553 "RFC3775 : Section 10.3.1" 2554 ::= { mip6HaGlobalStats 6 } 2556 mip6HaPrefDiscoverReqd OBJECT-TYPE -- (Code 1) 2557 SYNTAX Counter32 2558 MAX-ACCESS read-only 2559 STATUS current 2560 DESCRIPTION 2561 "The total number of Binding Acknowledgments sent by 2562 the home agent with Status code indicating 'accepted 2563 but prefix discovery necessary' (Code 1). 2564 Discontinuities in the value of this counter can 2565 occur at re-initialization of the management system, 2566 and at other times as indicated by the value of 2567 mip6CounterDiscontinuityTime. 2568 " 2569 REFERENCE 2570 "RFC3775 : Section 10.3.1" 2571 ::= { mip6HaGlobalStats 7 } 2573 mip6HaReasonUnspecified OBJECT-TYPE -- (Code 128) 2574 SYNTAX Counter32 2575 MAX-ACCESS read-only 2576 STATUS current 2577 DESCRIPTION 2578 "Total number of Binding Update requests rejected by 2579 the home agent with status code in the Binding 2580 Acknowledgment message indicating 'reason 2581 unspecified' (Code 128). 2582 Discontinuities in the value of this counter can 2583 occur at re-initialization of the management system, 2584 and at other times as indicated by the value of 2585 mip6CounterDiscontinuityTime. 2586 " 2587 REFERENCE 2588 "RFC3775 : Section 10.3.1" 2589 ::= { mip6HaGlobalStats 8 } 2591 mip6HaAdmProhibited OBJECT-TYPE 2592 SYNTAX Counter32 2593 MAX-ACCESS read-only 2594 STATUS current 2595 DESCRIPTION 2596 "Total number of Binding Update requests rejected by 2597 the home agent with status code in the Binding 2598 Acknowledgment message indicating 'administratively 2599 prohibited' (Code 129). 2600 Discontinuities in the value of this counter can 2601 occur at re-initialization of the management system, 2602 and at other times as indicated by the value of 2603 mip6CounterDiscontinuityTime. 2604 " 2605 REFERENCE 2606 "RFC3775 : Section 10.3.1" 2607 ::= { mip6HaGlobalStats 9 } 2609 mip6HaInsufficientResource OBJECT-TYPE -- (Code 130) 2610 SYNTAX Counter32 2611 MAX-ACCESS read-only 2612 STATUS current 2613 DESCRIPTION 2614 "Total number of Binding Update requests rejected by 2615 the home agent with status code in the Binding 2616 Acknowledgment message indicating 'insufficient 2617 resources' (Code 130). 2618 Discontinuities in the value of this counter can 2619 occur at re-initialization of the management system, 2620 and at other times as indicated by the value of 2621 mip6CounterDiscontinuityTime. 2622 " 2623 REFERENCE 2624 "RFC3775 : Section 9.5.2" 2625 ::= { mip6HaGlobalStats 10 } 2627 mip6HaHomeRegnNotSupported OBJECT-TYPE -- (Code 131) 2628 SYNTAX Counter32 2629 MAX-ACCESS read-only 2630 STATUS current 2631 DESCRIPTION 2632 "Total number of Binding Update requests rejected by 2633 the home agent with status code in the Binding 2634 Acknowledgment message indicating 'home 2635 registration not supported' (Code 131). 2636 Discontinuities in the value of this counter can 2637 occur at re-initialization of the management system, 2638 and at other times as indicated by the value of 2639 mip6CounterDiscontinuityTime. 2640 " 2641 REFERENCE 2642 "RFC3775 : Section 10.3.1" 2643 ::= { mip6HaGlobalStats 11 } 2645 mip6HaNotHomeSubnet OBJECT-TYPE -- (Code 132) 2646 SYNTAX Counter32 2647 MAX-ACCESS read-only 2648 STATUS current 2649 DESCRIPTION 2650 "Total number of Binding Update requests rejected by 2651 the home agent with status code in the Binding 2652 Acknowledgment message indicating 'not home subnet' 2653 (Code 132). 2654 Discontinuities in the value of this counter can 2655 occur at re-initialization of the management system, 2656 and at other times as indicated by the value of 2657 mip6CounterDiscontinuityTime. 2658 " 2659 REFERENCE 2660 "RFC3775 : Section 10.3.1" 2661 ::= { mip6HaGlobalStats 12 } 2663 mip6HaNotHomeAgentForThisMN OBJECT-TYPE -- (Code 133) 2664 SYNTAX Counter32 2665 MAX-ACCESS read-only 2666 STATUS current 2667 DESCRIPTION 2668 "Total number of Binding Update requests rejected by 2669 the home agent with status code in the Binding 2670 Acknowledgment message indicating 'not home agent 2671 for this mobile node' (Code 133). 2672 Discontinuities in the value of this counter can 2673 occur at re-initialization of the management system, 2674 and at other times as indicated by the value of 2675 mip6CounterDiscontinuityTime. 2676 " 2677 REFERENCE 2678 "RFC3775 : Section 10.3.2" 2679 ::= { mip6HaGlobalStats 13 } 2681 mip6HaDupAddrDetectionFailed OBJECT-TYPE -- (Code 134) 2682 SYNTAX Counter32 2683 MAX-ACCESS read-only 2684 STATUS current 2685 DESCRIPTION 2686 "Total number of Binding Update requests rejected by 2687 the home agent with status code in the Binding 2688 Acknowledgment message indicating 'Duplicate 2689 Address Detection failed' (Code 134). 2690 Discontinuities in the value of this counter can 2691 occur at re-initialization of the management system, 2692 and at other times as indicated by the value of 2693 mip6CounterDiscontinuityTime. 2694 " 2695 REFERENCE 2696 "RFC3775 : Section 10.3.1" 2697 ::= { mip6HaGlobalStats 14 } 2699 mip6HaSeqNumberOutOfWindow OBJECT-TYPE -- (Code 135) 2700 SYNTAX Counter32 2701 MAX-ACCESS read-only 2702 STATUS current 2703 DESCRIPTION 2704 "Total number of Binding Update requests rejected by 2705 the home agent with status code in the Binding 2706 Acknowledgment message indicating 'sequence number 2707 out of window' (Code 135). 2708 Discontinuities in the value of this counter can 2709 occur at re-initialization of the management system, 2710 and at other times as indicated by the value of 2711 mip6CounterDiscontinuityTime. 2712 " 2713 REFERENCE 2714 "RFC3775 : Section 9.5.1" 2715 ::= { mip6HaGlobalStats 15 } 2717 mip6HaExpiredHomeNonceIndex OBJECT-TYPE -- (Code 136) 2718 SYNTAX Counter32 2719 MAX-ACCESS read-only 2720 STATUS current 2721 DESCRIPTION 2722 "Total number of Binding Update requests rejected by 2723 the home agent with status code in the Binding 2724 Acknowledgment message indicating 'expired home 2725 nonce index' (Code 136). 2726 Discontinuities in the value of this counter can 2727 occur at re-initialization of the management system, 2728 and at other times as indicated by the value of 2729 mip6CounterDiscontinuityTime. 2730 " 2731 REFERENCE 2732 "RFC3775 : Section 9.5.1" 2733 ::= { mip6HaGlobalStats 16 } 2735 mip6HaRegTypeChangeDisallowed OBJECT-TYPE -- (Code 139) 2736 SYNTAX Counter32 2737 MAX-ACCESS read-only 2738 STATUS current 2739 DESCRIPTION 2740 "Total number of Binding Update requests rejected by 2741 the home agent with status code in the Binding 2742 Acknowledgment message indicating 'registration 2743 type change disallowed' (Code 139) i.e. a binding 2744 already exists for the given home address and the 2745 home registration flag has a different value than 2746 the Home Registration (H) bit in the Binding Update. 2747 Discontinuities in the value of this counter can 2748 occur at re-initialization of the management system, 2749 and at other times as indicated by the value of 2750 mip6CounterDiscontinuityTime. 2751 " 2752 REFERENCE 2753 "RFC3775 : Section 9.5.1" 2754 ::= { mip6HaGlobalStats 17 } 2756 -- Home agent registration Counters per node 2757 mip6HaCounterTable OBJECT-TYPE 2758 SYNTAX SEQUENCE OF Mip6HaCounterEntry 2759 MAX-ACCESS not-accessible 2760 STATUS current 2761 DESCRIPTION 2762 "A table containing registration statistics for all 2763 mobile nodes registered with the home agent. 2764 " 2765 ::= { mip6HaStats 2 } 2767 mip6HaCounterEntry OBJECT-TYPE 2768 SYNTAX Mip6HaCounterEntry 2769 MAX-ACCESS not-accessible 2770 STATUS current 2771 DESCRIPTION 2772 "Home agent registration statistics for a mobile 2773 node. 2775 Implementors need to be aware that if the total 2776 number of octets in mip6BindingHomeAddress 2777 exceeds 113 then OIDs of column instances in 2778 this row will have more than 128 sub-identifiers and 2779 cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 2780 " 2781 INDEX { mip6BindingHomeAddressType, 2782 mip6BindingHomeAddress 2783 } 2784 ::= { mip6HaCounterTable 1 } 2786 Mip6HaCounterEntry ::= SEQUENCE { 2787 mip6HaBURequestsAccepted Counter32, 2788 mip6HaBURequestsDenied Counter32, 2789 mip6HaBCEntryCreationTime DateAndTime, 2790 mip6HaBUAcceptedTime DateAndTime, 2791 mip6HaBURejectionTime DateAndTime, 2792 mip6HaRecentBURejectionCode Mip6BURequestRejectionCode, 2793 mip6HaCtrDiscontinuityTime TimeStamp 2794 } 2796 mip6HaBURequestsAccepted OBJECT-TYPE 2797 SYNTAX Counter32 2798 MAX-ACCESS read-only 2799 STATUS current 2800 DESCRIPTION 2801 "Total number of service requests for the mobile node 2802 accepted by the home agent. 2803 Discontinuities in the value of this counter can 2804 occur at re-initialization of the management system, 2805 and at other times as indicated by the value of 2806 mip6HaCtrDiscontinuityTime. 2807 " 2808 ::= { mip6HaCounterEntry 1 } 2810 mip6HaBURequestsDenied OBJECT-TYPE 2811 SYNTAX Counter32 2812 MAX-ACCESS read-only 2813 STATUS current 2814 DESCRIPTION 2815 "Total number of service requests for the mobile node 2816 rejected by the home agent. 2817 Discontinuities in the value of this counter can 2818 occur at re-initialization of the management system, 2819 and at other times as indicated by the value of 2820 mip6HaCtrDiscontinuityTime. 2821 " 2822 ::= { mip6HaCounterEntry 2 } 2824 mip6HaBCEntryCreationTime OBJECT-TYPE 2825 SYNTAX DateAndTime 2826 UNITS "seconds" 2827 MAX-ACCESS read-only 2828 STATUS current 2829 DESCRIPTION 2830 "The time when the current Binding Cache entry was 2831 created for the mobile node. 2832 " 2833 ::= { mip6HaCounterEntry 3 } 2835 mip6HaBUAcceptedTime OBJECT-TYPE 2836 SYNTAX DateAndTime 2837 MAX-ACCESS read-only 2838 STATUS current 2839 DESCRIPTION 2840 "The time at which the last Binding Update was 2841 accepted by the home agent for this mobile node. 2842 " 2843 ::= { mip6HaCounterEntry 4 } 2845 mip6HaBURejectionTime OBJECT-TYPE 2846 SYNTAX DateAndTime 2847 MAX-ACCESS read-only 2848 STATUS current 2849 DESCRIPTION 2850 "The time at which the last Binding Update was 2851 rejected by the home agent for this mobile node. 2852 If there have been no rejections then this object 2853 will be inaccessible. 2854 " 2855 ::= { mip6HaCounterEntry 5 } 2857 mip6HaRecentBURejectionCode OBJECT-TYPE 2858 SYNTAX Mip6BURequestRejectionCode 2859 MAX-ACCESS read-only 2860 STATUS current 2861 DESCRIPTION 2862 "If a Binding Acknowledgment is sent to the mobile 2863 node, this is the Status code (> 128) that is 2864 returned in the Binding Acknowledgment. 2865 In case a Binding Acknowledgment is not sent to the 2866 mobile node then this will be the value of the 2867 Status code that corresponds to the reason of the 2868 rejection. 2869 If there have been no rejections then this object 2870 will be inaccessible. 2871 " 2872 ::= { mip6HaCounterEntry 6 } 2874 mip6HaCtrDiscontinuityTime OBJECT-TYPE 2875 SYNTAX TimeStamp 2876 MAX-ACCESS read-only 2877 STATUS current 2878 DESCRIPTION 2879 "The value of sysUpTime on the most recent occasion 2880 at which any one or more of counters in this row 2881 viz, instances of 'mip6HaBURequestsAccepted' and 2882 'mip6HaBURequestsRejected' suffered a discontinuity. 2883 If no such discontinuities have occurred since the 2884 last re-initialization of the local management 2885 subsystem, then this object will have a zero value. 2886 " 2887 ::= { mip6HaCounterEntry 7 } 2889 -- Home Agent List Table 2890 mip6HaListTable OBJECT-TYPE 2891 SYNTAX SEQUENCE OF Mip6HaListEntry 2892 MAX-ACCESS not-accessible 2893 STATUS current 2894 DESCRIPTION 2895 "This table models the Home Agents List that contains 2896 the list of all routers that are acting as home 2897 agents on each of the interfaces on which the home 2898 agent service is offered by this router. 2899 " 2900 REFERENCE 2901 "RFC3775 : Section 10.1" 2902 ::= { mip6HaAdvertisement 4 } 2904 mip6HaListEntry OBJECT-TYPE 2905 SYNTAX Mip6HaListEntry 2906 MAX-ACCESS not-accessible 2907 STATUS current 2908 DESCRIPTION 2909 "Information about a router that is offering home 2910 agent service. 2911 The instances of the columnar objects in this entry 2912 pertain to an interface for a particular value of 2913 mip6HaLinkLocalAddressType and 2914 mip6HaLinkLocalAddress. The interface is uniquely 2915 identified by its ipv6InterfaceIfIndex. The same 2916 ipv6InterfaceIfIndex object is used in conjunction 2917 with the mip6HaLinkLocalAddressType and 2918 mip6HaLinkLocalAddress to uniquely identify 2919 instances of the columnar objects of this row. 2921 Implementors need to be aware that if the total 2922 number of octets in mip6HaLinkLocalAddress 2923 exceeds 112 then OIDs of column instances in 2924 this row will have more than 128 sub-identifiers and 2925 cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 2926 " 2927 INDEX { ipv6InterfaceIfIndex, mip6HaLinkLocalAddressType, 2928 mip6HaLinkLocalAddress } 2929 ::= { mip6HaListTable 1 } 2931 Mip6HaListEntry ::= SEQUENCE { 2932 mip6HaLinkLocalAddressType InetAddressType, 2933 mip6HaLinkLocalAddress InetAddress, 2934 mip6HaPreference Integer32, 2935 mip6HaRecvLifeTime Gauge32, 2936 mip6HaRecvTimeStamp DateAndTime 2937 } 2939 mip6HaLinkLocalAddressType OBJECT-TYPE 2940 SYNTAX InetAddressType 2941 MAX-ACCESS not-accessible 2942 STATUS current 2943 DESCRIPTION 2944 "The address type for the link-local address 2945 of the home agent that follows. 2946 " 2947 REFERENCE 2948 "RFC3775 : Section 10.1" 2949 ::= { mip6HaListEntry 1 } 2951 mip6HaLinkLocalAddress OBJECT-TYPE 2952 SYNTAX InetAddress 2953 MAX-ACCESS not-accessible 2954 STATUS current 2955 DESCRIPTION 2956 "The link local address of the home agent . 2958 The type of the address represented by this object 2959 is specified by the corresponding 2960 mip6HaLinkLocalAddressType object. 2961 " 2962 REFERENCE 2963 "RFC3775 : Section 10.1" 2964 ::= { mip6HaListEntry 2 } 2966 mip6HaPreference OBJECT-TYPE 2967 SYNTAX Integer32 2968 MAX-ACCESS read-only 2969 STATUS current 2970 DESCRIPTION 2971 "The preference value of this home agent. 2972 Higher values indicate a more preferable home 2973 agent. The preference value is obtained from 2974 the preference field of the received Router 2975 Advertisement. 2976 " 2977 REFERENCE 2978 "RFC3775 : Section 10.1" 2979 ::= { mip6HaListEntry 3 } 2981 mip6HaRecvLifeTime OBJECT-TYPE 2982 SYNTAX Gauge32 2983 MAX-ACCESS read-only 2984 STATUS current 2985 DESCRIPTION 2986 "The lifetime for this home agent. 2987 " 2988 REFERENCE 2989 "RFC3775 : Section 10.1" 2990 ::= { mip6HaListEntry 4 } 2992 mip6HaRecvTimeStamp OBJECT-TYPE 2993 SYNTAX DateAndTime 2994 MAX-ACCESS read-only 2995 STATUS current 2996 DESCRIPTION 2997 "The time when the home agent advertisement was 2998 received. 2999 " 3000 ::= { mip6HaListEntry 5 } 3002 -- 3003 -- The list of global addresses of a home agent in the 3004 -- home agent list 3005 -- 3007 mip6HaGlAddrTable OBJECT-TYPE 3008 SYNTAX SEQUENCE OF Mip6HaGlAddrEntry 3009 MAX-ACCESS not-accessible 3010 STATUS current 3011 DESCRIPTION 3012 "This table contains the global addresses of the home 3013 agents in the Home Agents List. 3014 " 3015 REFERENCE 3016 "RFC3775 : Section 10.1" 3017 ::= { mip6HaAdvertisement 5 } 3019 mip6HaGlAddrEntry OBJECT-TYPE 3020 SYNTAX Mip6HaGlAddrEntry 3021 MAX-ACCESS not-accessible 3022 STATUS current 3023 DESCRIPTION 3024 "A global address for a home agent in the Home Agents 3025 List. 3026 The instances of the columnar objects in this entry 3027 pertain to an interface for a particular value of 3028 mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress 3029 and mip6HaGaAddrSeqNo. 3030 The mip6HaGaAddrSeqNo object is used to distinguish 3031 between multiple instances of the home agent global 3032 addresses on the same interface for the same set of 3033 mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress 3034 values. 3035 There is no upper-bound on the maximum number of 3036 global addresses on an interface but, for practical 3037 purposes the upper-bound of the value 3038 mip6HaGaAddrSeqNo is set to 1024. 3039 The interface is uniquely identified by its 3040 ipv6InterfaceIfIndex. The same ipv6InterfaceIfIndex 3041 object is used in conjunction with the 3042 mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress 3043 and mip6HaGaAddrSeqNo to uniquely identify instances 3044 of the columnar objects of this row. 3046 Implementors need to be aware that if the total 3047 number of octets in mip6HaLinkLocalAddress 3048 exceeds 111 then OIDs of column instances in 3049 this row will have more than 128 sub-identifiers and 3050 cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 3051 " 3052 INDEX { ipv6InterfaceIfIndex, mip6HaLinkLocalAddressType, 3053 mip6HaLinkLocalAddress, mip6HaGaAddrSeqNo } 3054 ::= { mip6HaGlAddrTable 1 } 3056 Mip6HaGlAddrEntry ::= SEQUENCE { 3057 mip6HaGaAddrSeqNo Integer32, 3058 mip6HaGaGlobalAddressType InetAddressType, 3059 mip6HaGaGlobalAddress InetAddress 3060 } 3061 mip6HaGaAddrSeqNo OBJECT-TYPE 3062 SYNTAX Integer32 (1..1024) 3063 MAX-ACCESS not-accessible 3064 STATUS current 3065 DESCRIPTION 3066 "The index that along with ipv6InterfaceIfIndex, 3067 mip6HaLinkLocalAddressType and 3068 mip6HaLinkLocalAddress uniquely identifies this row. 3069 " 3070 REFERENCE 3071 "RFC3775 : Section 10.1" 3072 ::= { mip6HaGlAddrEntry 1 } 3074 mip6HaGaGlobalAddressType OBJECT-TYPE 3075 SYNTAX InetAddressType 3076 MAX-ACCESS read-only 3077 STATUS current 3078 DESCRIPTION 3079 "The address type for the global address of the 3080 home agent that follows. 3081 " 3082 ::= { mip6HaGlAddrEntry 2 } 3084 mip6HaGaGlobalAddress OBJECT-TYPE 3085 SYNTAX InetAddress 3086 MAX-ACCESS read-only 3087 STATUS current 3088 DESCRIPTION 3089 "A global address of the home agent. 3091 The type of the address represented by this object 3092 is specified by the corresponding 3093 mip6HaGaGlobalAddressType object. 3094 " 3095 ::= { mip6HaGlAddrEntry 3 } 3097 -- 3098 -- Notifications 3099 -- 3100 mip6MnRegistered NOTIFICATION-TYPE 3101 OBJECTS { 3102 mip6BindingTimeRegistered, 3103 mip6BindingCOAType, 3104 mip6BindingCOA 3105 } 3106 STATUS current 3107 DESCRIPTION 3108 "This notification is sent by a home agent when 3109 a mobile node registers with the home agent 3110 for the first time. 3111 Notifications will not be sent for subsequent 3112 updates and/or refreshes. 3113 The MO instances in the notifications will be 3114 identified by the mip6BindingHomeAddressType 3115 and mip6BindingHomeAddress for the mobile node 3116 in the mip6BindingCacheTable. 3117 " 3118 REFERENCE 3119 "RFC3775 : Section 10.3.1" 3120 ::= { mip6Notifications 1 } 3122 mip6MnDeRegistered NOTIFICATION-TYPE 3123 OBJECTS { 3124 mip6BindingTimeRegistered, 3125 mip6BindingCOAType, 3126 mip6BindingCOA 3127 } 3128 STATUS current 3129 DESCRIPTION 3130 "This notification is sent by a home agent every 3131 time a mobile node de-registers with the home 3132 agent by sending a Binding Update that requests 3133 the home agent to delete a binding. 3134 The MO instances in the notifications will be 3135 identified by the mip6BindingHomeAddressType 3136 and mip6BindingHomeAddress for the mobile node 3137 in the mip6BindingCacheTable. 3138 " 3139 REFERENCE 3140 "RFC3775 : Section 10.3.2" 3141 ::= { mip6Notifications 2 } 3143 mip6MnCOAChanged NOTIFICATION-TYPE 3144 OBJECTS { 3145 mip6BindingTimeRegistered, 3146 mip6BindingCOAType, 3147 mip6BindingCOA 3148 } 3149 STATUS current 3150 DESCRIPTION 3151 "This notification is sent by a home agent every 3152 time a mobile node sends a Binding Update with 3153 a new care-of address (for an existing Binding 3154 Cache entry). 3155 Notifications will not be sent for subsequent 3156 updates and/or refreshes for the same Care-of 3157 address. 3158 The registration of a new care-of address may 3159 indicate that the mobile node has moved or that 3160 the primary care-of address of the mobile node 3161 has become deprecated. 3162 The MO instances in the notifications will be 3163 identified by the mip6BindingHomeAddressType 3164 and mip6BindingHomeAddress for the mobile node 3165 in the mip6BindingCacheTable. 3166 " 3167 REFERENCE 3168 "RFC3775 : Section 11.5.2, 11.7.1" 3169 ::= { mip6Notifications 3 } 3171 mip6MnBindingExpiredAtHA NOTIFICATION-TYPE 3172 OBJECTS { 3173 mip6BindingTimeRegistered, 3174 mip6BindingCOAType, 3175 mip6BindingCOA 3176 } 3177 STATUS current 3178 DESCRIPTION 3179 "This notification is sent by a home agent when a 3180 binding for the mobile node at the home agent 3181 expired (no timely Binding Updates were received). 3182 The MO instances in the notifications will be 3183 identified by the mip6BindingHomeAddressType 3184 and mip6BindingHomeAddress for the mobile node 3185 in the mip6BindingCacheTable. 3186 " 3187 REFERENCE 3188 "RFC3775 : Section 10.3.2" 3189 ::= { mip6Notifications 4 } 3191 mip6MnBindingExpiredAtCN NOTIFICATION-TYPE 3192 OBJECTS { 3193 mip6BindingTimeRegistered, 3194 mip6BindingCOAType, 3195 mip6BindingCOA 3196 } 3197 STATUS current 3198 DESCRIPTION 3199 "This notification is sent by a correspondent node 3200 when a binding for the mobile node at the 3201 correspondent node expired (no timely Binding 3202 Updates were received). 3203 The MO instances in the notifications will be 3204 identified by the mip6BindingHomeAddressType 3205 and mip6BindingHomeAddress for the mobile node 3206 in the mip6BindingCacheTable. 3207 " 3208 ::= { mip6Notifications 5 } 3210 -- Conformance information 3211 mip6Groups OBJECT IDENTIFIER ::= { mip6Conformance 1 } 3212 mip6Compliances OBJECT IDENTIFIER ::= { mip6Conformance 2 } 3214 -- Units of conformance 3215 mip6SystemGroup OBJECT-GROUP 3216 OBJECTS { 3217 mip6Capabilities, 3218 mip6Status 3219 } 3220 STATUS current 3221 DESCRIPTION 3222 " A collection of objects for basic MIPv6 3223 monitoring." 3224 ::= { mip6Groups 1 } 3226 mip6BindingCacheGroup OBJECT-GROUP 3227 OBJECTS { 3228 mip6BindingCOAType, 3229 mip6BindingCOA, 3230 mip6BindingTimeRegistered, 3231 mip6BindingTimeGranted, 3232 mip6BindingTimeRemaining, 3233 mip6BindingMaxSeq, 3234 mip6BindingHomeRegn, 3235 mip6BindingUsageTS, 3236 mip6BindingUsageCount, 3237 mip6BindingAdminStatus 3238 } 3239 STATUS current 3240 DESCRIPTION 3241 " A collection of objects for monitoring the 3242 Binding cache. 3243 " 3244 ::= { mip6Groups 2 } 3246 mip6BindingHstGroup OBJECT-GROUP 3247 OBJECTS { 3248 mip6BindingHstCOAType, 3249 mip6BindingHstCOA, 3250 mip6BindingHstTimeRegistered, 3251 mip6BindingHstTimeExpired, 3252 mip6BindingHstHomeRegn, 3253 mip6BindingHstUsageTS, 3254 mip6BindingHstUsageCount 3255 } 3256 STATUS current 3257 DESCRIPTION 3258 " A collection of objects for monitoring the 3259 binding history. This can be used to monitor 3260 the movement of the mobile node. 3261 " 3262 ::= { mip6Groups 3 } 3264 mip6TotalTrafficGroup OBJECT-GROUP 3265 OBJECTS { 3266 mip6InOctets, 3267 mip6HCInOctets, 3268 mip6InPkts, 3269 mip6HCInPkts, 3270 mip6OutOctets, 3271 mip6HCOutOctets, 3272 mip6OutPkts, 3273 mip6HCOutPkts, 3274 mip6CounterDiscontinuityTime 3275 } 3276 STATUS current 3277 DESCRIPTION 3278 " A collection of objects for monitoring the 3279 total MIPv6 traffic. 3280 " 3281 ::= { mip6Groups 4 } 3283 mip6NodeTrafficGroup OBJECT-GROUP 3284 OBJECTS { 3285 mip6NodeInOctets, 3286 mip6HCNodeInOctets, 3287 mip6NodeInPkts, 3288 mip6HCNodeInPkts, 3289 mip6NodeOutOctets, 3290 mip6HCNodeOutOctets, 3291 mip6NodeOutPkts, 3292 mip6HCNodeOutPkts, 3293 mip6NodeCtrDiscontinuityTime 3294 } 3295 STATUS current 3296 DESCRIPTION 3297 " A collection of objects for monitoring the 3298 MIPv6 traffic due to a mobile node. 3299 " 3300 ::= { mip6Groups 5 } 3302 mip6MnSystemGroup OBJECT-GROUP 3303 OBJECTS { 3304 mip6MnHomeAddressState 3305 } 3306 STATUS current 3307 DESCRIPTION 3308 " A collection of objects for basic monitoring 3309 of the mobile node. 3310 " 3311 ::= { mip6Groups 6 } 3313 mip6MnConfGroup OBJECT-GROUP 3314 OBJECTS { 3315 mip6MnDiscoveryRequests, 3316 mip6MnDiscoveryReplies, 3317 mip6MnDiscoveryTimeouts, 3318 mip6MnPrefixSolicitationsSent, 3319 mip6MnPrefixAdvsRecd, 3320 mip6MnPrefixAdvsIgnored, 3321 mip6MnMovedToFN, 3322 mip6MnMovedToHN 3323 } 3324 STATUS current 3325 DESCRIPTION 3326 " A collection of objects for monitoring 3327 the advertisement related info on the 3328 mobile node. 3329 " 3330 ::= { mip6Groups 7 } 3332 mip6MnRegistrationGroup OBJECT-GROUP 3333 OBJECTS { 3334 mip6MnBLCOAType, 3335 mip6MnBLCOA, 3336 mip6MnBLLifeTimeRequested, 3337 mip6MnBLLifeTimeGranted, 3338 mip6MnBLMaxSeq, 3339 mip6MnBLTimeSent, 3340 mip6MnBLAccepted, 3341 mip6MnBLAcceptedTime, 3342 mip6MnBLRetransmissions, 3343 mip6MnBLDontSendBUFlag, 3344 -- 3345 -- Binding Update List 3346 -- 3347 mip6MnMobilityMessagesSent, 3348 mip6MnMobilityMessagesRecd, 3349 mip6MnBUsToHA, 3350 mip6MnBUAcksFromHA, 3351 mip6MnBUsToCN, 3352 mip6MnBUAcksFromCN, 3353 mip6MnBindingErrorsFromCN, 3354 mip6MnICMPErrorsRecd, 3355 mip6MnBRRequestsRecd 3356 } 3357 STATUS current 3358 DESCRIPTION 3359 " A collection of objects for monitoring 3360 the registration statistics for the mobile node. 3361 " 3362 ::= { mip6Groups 8 } 3364 mip6CnStatsGroup OBJECT-GROUP 3365 OBJECTS { 3366 mip6CnBURequestsAccepted, 3367 mip6CnBURequestsRejected, 3368 mip6CnBCEntryCreationTime, 3369 mip6CnBUAcceptedTime, 3370 mip6CnBURejectionTime, 3371 mip6CnBURejectionCode, 3372 mip6CnCtrDiscontinuityTime 3373 } 3374 STATUS current 3375 DESCRIPTION 3376 " A collection of objects for monitoring 3377 the control messages and corresponding 3378 statistics for each mobile node 3379 communicating with the correspondent 3380 node. 3381 " 3382 ::= { mip6Groups 9 } 3384 mip6HaSystemGroup OBJECT-GROUP 3385 OBJECTS { 3386 mip6HaAdvsRecd, 3387 mip6HaAdvsSent, 3388 mip6HaAdvPreference, 3389 mip6HaAdvLifetime, 3390 mip6HaPrefixAdv, 3391 mip6HaPrefixSolicitation, 3392 mip6HaMCastCtlMsgSupport 3393 } 3394 STATUS current 3395 DESCRIPTION 3396 " A collection of objects for monitoring 3397 the Advertisement related parameters and 3398 statistics for the home agent. 3399 " 3400 ::= { mip6Groups 10 } 3402 mip6HaListGroup OBJECT-GROUP 3403 OBJECTS { 3404 mip6HaPreference, 3405 mip6HaRecvLifeTime, 3406 mip6HaRecvTimeStamp, 3407 mip6HaGaGlobalAddressType, 3408 mip6HaGaGlobalAddress 3409 } 3410 STATUS current 3411 DESCRIPTION 3412 " A collection of objects for monitoring 3413 Home Agent List on the home agent. 3414 " 3415 ::= { mip6Groups 11 } 3417 mip6HaStatsGroup OBJECT-GROUP 3418 OBJECTS { 3419 mip6HaBURequestsAccepted, 3420 mip6HaBURequestsDenied, 3421 mip6HaBCEntryCreationTime, 3422 mip6HaBUAcceptedTime, 3423 mip6HaBURejectionTime, 3424 mip6HaRecentBURejectionCode, 3425 mip6HaCtrDiscontinuityTime 3427 } 3428 STATUS current 3429 DESCRIPTION 3430 " A collection of objects for monitoring 3431 registration related statistics on the home agent. 3432 " 3433 ::= { mip6Groups 12 } 3435 mip6CnGlobalStatsGroup OBJECT-GROUP 3436 OBJECTS { 3437 mip6CnHomeTestInitsRecd, 3438 mip6CnHomeTestsSent, 3439 mip6CnCareOfTestInitsRecd, 3440 mip6CnCareOfTestsSent, 3441 mip6CnBUsRecd, 3442 mip6CnBUAcksSent, 3443 mip6CnBRsSent, 3444 mip6CnBindingErrors, 3445 mip6CnBUsAccepted, 3446 mip6CnBUsRejected, 3447 mip6CnReasonUnspecified, 3448 mip6CnInsufficientResource, 3449 mip6CnHomeRegnNotSupported, 3450 mip6CnSeqNumberOutOfWindow, 3451 mip6CnExpiredHomeNonceIndex, 3452 mip6CnExpiredCareOfNonceIndex, 3453 mip6CnExpiredNonce, 3454 mip6CnRegTypeChangeDisallowed 3455 } 3456 STATUS current 3457 DESCRIPTION 3458 " A collection of objects for monitoring 3459 advertisement and registration statistics on 3460 a correspondent node. 3461 " 3462 ::= { mip6Groups 13 } 3464 mip6HaGlobalStatsGroup OBJECT-GROUP 3465 OBJECTS { 3466 mip6HaHomeTestInitsRecd, 3467 mip6HaHomeTestsSent, 3468 mip6HaBUsRecd, 3469 mip6HaBUAcksSent, 3470 mip6HaBRAdviceSent, 3471 mip6HaBUsAccepted, 3472 mip6HaPrefDiscoverReqd, 3473 mip6HaReasonUnspecified, 3474 mip6HaAdmProhibited, 3475 mip6HaInsufficientResource, 3476 mip6HaHomeRegnNotSupported, 3477 mip6HaNotHomeSubnet, 3478 mip6HaNotHomeAgentForThisMN, 3479 mip6HaDupAddrDetectionFailed, 3480 mip6HaSeqNumberOutOfWindow, 3481 mip6HaExpiredHomeNonceIndex, 3482 mip6HaRegTypeChangeDisallowed 3484 } 3485 STATUS current 3486 DESCRIPTION 3487 " A collection of objects for monitoring 3488 advertisement and registration statistics on 3489 a home agent. 3490 " 3491 ::= { mip6Groups 14 } 3493 mip6BindingCacheCtlGroup OBJECT-GROUP 3494 OBJECTS { 3495 mip6BindingAdminStatus 3496 } 3497 STATUS current 3498 DESCRIPTION 3499 "A collection of objects for controlling the 3500 Binding cache. 3501 " 3502 ::= { mip6Groups 15 } 3504 mip6NotificationGroup NOTIFICATION-GROUP 3505 NOTIFICATIONS { 3506 mip6MnRegistered, 3507 mip6MnDeRegistered, 3508 mip6MnCOAChanged, 3509 mip6MnBindingExpiredAtHA, 3510 mip6MnBindingExpiredAtCN 3511 } 3512 STATUS current 3513 DESCRIPTION 3514 "A collection of notifications from a home agent 3515 or correspondent node to the Manager about the 3516 status of a mobile node. 3517 " 3518 ::= { mip6Groups 16 } 3520 -- Compliance statements 3522 mip6CoreCompliance MODULE-COMPLIANCE 3523 STATUS current 3524 DESCRIPTION 3525 "The compliance statement for SNMP entities 3526 which implement the MOBILEIPV6-MIB. 3527 " 3528 MODULE -- this module 3529 MANDATORY-GROUPS { mip6SystemGroup } 3531 ::= { mip6Compliances 1 } 3533 mip6Compliance2 MODULE-COMPLIANCE 3534 STATUS current 3535 DESCRIPTION 3536 "The compliance statement for SNMP entities 3537 which implement the MOBILEIPV6-MIB and support 3538 monitoring of the BindingCache and the Total 3539 Traffic. 3540 There are a number of INDEX objects that cannot be 3541 represented in the form of OBJECT clauses in SMIv2, 3542 but for which there are compliance requirements, 3543 expressed in OBJECT clause form in this description: 3544 -- OBJECT mip6BindingHomeAddressType 3545 -- SYNTAX InetAddressType { ipv6(2) } 3546 -- DESCRIPTION 3547 -- This MIB module requires support for global 3548 -- ipv6 addresses for the mip6BindingHomeAddress 3549 -- object. 3550 -- 3551 -- OBJECT mip6BindingHomeAddress 3552 -- SYNTAX InetAddress (SIZE(16)) 3553 -- DESCRIPTION 3554 -- This MIB module requires support for global 3555 -- ipv6 addresses for the mip6BindingHomeAddress 3556 -- object. 3557 -- 3558 " 3559 MODULE -- this module 3560 MANDATORY-GROUPS { mip6SystemGroup, 3561 mip6BindingCacheGroup, 3562 mip6TotalTrafficGroup 3563 } 3564 ::= { mip6Compliances 2 } 3566 mip6Compliance3 MODULE-COMPLIANCE 3567 STATUS current 3568 DESCRIPTION 3569 "The compliance statement for SNMP entities 3570 which implement the MOBILEIPV6-MIB and 3571 support monitoring of the BindingCache, 3572 the Binding History, the total traffic and 3573 the mobile node-wide traffic. 3574 There are a number of INDEX objects that cannot be 3575 represented in the form of OBJECT clauses in SMIv2, 3576 but for which there are compliance requirements, 3577 expressed in OBJECT clause form in this description: 3578 -- OBJECT mip6BindingHomeAddressType 3579 -- SYNTAX InetAddressType { ipv6(2) } 3580 -- DESCRIPTION 3581 -- This MIB module requires support for global 3582 -- ipv6 addresses for the mip6BindingHomeAddress 3583 -- object. 3584 -- 3585 -- OBJECT mip6BindingHomeAddress 3586 -- SYNTAX InetAddress (SIZE(16)) 3587 -- DESCRIPTION 3588 -- This MIB module requires support for global 3589 -- ipv6 addresses for the mip6BindingHomeAddress 3590 -- object. 3591 -- 3592 -- OBJECT mip6BindingHstHomeAddressType 3593 -- SYNTAX InetAddressType { ipv6(2) } 3594 -- DESCRIPTION 3595 -- This MIB module requires support for global 3596 -- ipv6 addresses for the 3597 -- mip6BindingHstHomeAddress object. 3598 -- 3599 -- OBJECT mip6BindingHstHomeAddress 3600 -- SYNTAX InetAddress (SIZE(16)) 3601 -- DESCRIPTION 3602 -- This MIB module requires support for global 3603 -- ipv6 addresses for the 3604 -- mip6BindingHstHomeAddress object. 3605 -- 3606 " 3607 MODULE -- this module 3608 MANDATORY-GROUPS { mip6SystemGroup, 3609 mip6BindingCacheGroup, 3610 mip6BindingHstGroup, 3611 mip6TotalTrafficGroup, 3612 mip6NodeTrafficGroup 3613 } 3615 ::= { mip6Compliances 3 } 3617 mip6CoreReadOnlyCompliance MODULE-COMPLIANCE 3618 STATUS current 3619 DESCRIPTION 3620 "The compliance statement for SNMP entities 3621 which implement the MOBILEIPV6-MIB without support 3622 for read-write (i.e. in read-only mode) . 3623 " 3624 MODULE -- this module 3625 MANDATORY-GROUPS { mip6SystemGroup } 3627 OBJECT mip6Status 3628 MIN-ACCESS read-only 3629 DESCRIPTION 3630 "Write access is not required." 3632 ::= { mip6Compliances 4 } 3634 mip6ReadOnlyCompliance2 MODULE-COMPLIANCE 3635 STATUS current 3636 DESCRIPTION 3637 "The compliance statement for SNMP entities 3638 which implement the MOBILEIPV6-MIB without support 3639 for read-write (i.e. in read-only mode) and, 3640 support monitoring of the BindingCache and Total 3641 Traffic. 3642 There are a number of INDEX objects that cannot be 3643 represented in the form of OBJECT clauses in SMIv2, 3644 but for which there are compliance requirements, 3645 expressed in OBJECT clause form in this description: 3646 -- OBJECT mip6BindingHomeAddressType 3647 -- SYNTAX InetAddressType { ipv6(2) } 3648 -- DESCRIPTION 3649 -- This MIB module requires support for global 3650 -- ipv6 addresses for the mip6BindingHomeAddress 3651 -- object. 3652 -- 3653 -- OBJECT mip6BindingHomeAddress 3654 -- SYNTAX InetAddress (SIZE(16)) 3655 -- DESCRIPTION 3656 -- This MIB module requires support for global 3657 -- ipv6 addresses for the mip6BindingHomeAddress 3658 -- object. 3659 -- 3660 " 3661 MODULE -- this module 3662 MANDATORY-GROUPS { mip6SystemGroup, 3663 mip6BindingCacheGroup, 3664 mip6TotalTrafficGroup 3665 } 3666 OBJECT mip6Status 3667 MIN-ACCESS read-only 3668 DESCRIPTION 3669 "Write access is not required." 3671 OBJECT mip6BindingAdminStatus 3672 MIN-ACCESS read-only 3673 DESCRIPTION 3674 "Write access is not required." 3675 ::= { mip6Compliances 5 } 3677 mip6ReadOnlyCompliance3 MODULE-COMPLIANCE 3678 STATUS current 3679 DESCRIPTION 3680 "The compliance statement for SNMP entities 3681 which implement the MOBILEIPV6-MIB without support 3682 for read-write (i.e. in read-only mode) and, support 3683 monitoring of the BindingCache, the Binding History, 3684 the total traffic and the mobile node-wide traffic. 3685 There are a number of INDEX objects that cannot be 3686 represented in the form of OBJECT clauses in SMIv2, 3687 but for which there are compliance requirements, 3688 expressed in OBJECT clause form in this description: 3689 -- OBJECT mip6BindingHomeAddressType 3690 -- SYNTAX InetAddressType { ipv6(2) } 3691 -- DESCRIPTION 3692 -- This MIB module requires support for global 3693 -- ipv6 addresses for the mip6BindingHomeAddress 3694 -- object. 3695 -- 3696 -- OBJECT mip6BindingHomeAddress 3697 -- SYNTAX InetAddress (SIZE(16)) 3698 -- DESCRIPTION 3699 -- This MIB module requires support for global 3700 -- ipv6 addresses for the mip6BindingHomeAddress 3701 -- object. 3702 -- 3703 -- OBJECT mip6BindingHstHomeAddressType 3704 -- SYNTAX InetAddressType { ipv6(2) } 3705 -- DESCRIPTION 3706 -- This MIB module requires support for global 3707 -- ipv6 addresses for the 3708 -- mip6BindingHstHomeAddress object. 3709 -- 3710 -- OBJECT mip6BindingHstHomeAddress 3711 -- SYNTAX InetAddress (SIZE(16)) 3712 -- DESCRIPTION 3713 -- This MIB module requires support for global 3714 -- ipv6 addresses for the 3715 -- mip6BindingHstHomeAddress object. 3716 -- 3717 " 3718 MODULE -- this module 3719 MANDATORY-GROUPS { mip6SystemGroup, 3720 mip6BindingCacheGroup, 3721 mip6BindingHstGroup, 3722 mip6TotalTrafficGroup, 3723 mip6NodeTrafficGroup 3724 } 3725 OBJECT mip6Status 3726 MIN-ACCESS read-only 3727 DESCRIPTION 3728 "Write access is not required." 3730 OBJECT mip6BindingAdminStatus 3731 MIN-ACCESS read-only 3732 DESCRIPTION 3733 "Write access is not required." 3734 ::= { mip6Compliances 6 } 3736 mip6MnCoreCompliance MODULE-COMPLIANCE 3737 STATUS current 3738 DESCRIPTION 3739 "The compliance statement for SNMP entities 3740 which implement the MOBILEIPV6-MIB and 3741 support monitoring of the basic mobile node 3742 functionality. 3743 There are a number of INDEX objects that cannot be 3744 represented in the form of OBJECT clauses in SMIv2, 3745 but for which there are compliance requirements, 3746 expressed in OBJECT clause form in this description: 3747 -- OBJECT mip6MnHomeAddressType 3748 -- SYNTAX InetAddressType { ipv6(2) } 3749 -- DESCRIPTION 3750 -- This MIB module requires support for global 3751 -- ipv6 addresses for the mip6MnHomeAddress 3752 -- object. 3753 -- 3754 -- OBJECT mip6MnHomeAddress 3755 -- SYNTAX InetAddress (SIZE(16)) 3756 -- DESCRIPTION 3757 -- This MIB module requires support for global 3758 -- ipv6 addresses for the mip6MnHomeAddress 3759 -- object. 3760 -- 3761 " 3762 MODULE -- this module 3763 MANDATORY-GROUPS { mip6MnSystemGroup 3764 } 3765 ::= { mip6Compliances 7 } 3767 mip6MnCompliance2 MODULE-COMPLIANCE 3768 STATUS current 3769 DESCRIPTION 3770 "The compliance statement for SNMP entities 3771 which implement the MOBILEIPV6-MIB and 3772 support monitoring of the mobile node 3773 functionality specifically the Discovery and 3774 Registration related statistics, 3775 There are a number of INDEX objects that cannot be 3776 represented in the form of OBJECT clauses in SMIv2, 3777 but for which there are compliance requirements, 3778 expressed in OBJECT clause form in this description: 3779 -- OBJECT mip6MnHomeAddressType 3780 -- SYNTAX InetAddressType { ipv6(2) } 3781 -- DESCRIPTION 3782 -- This MIB module requires support for global 3783 -- ipv6 addresses for the mip6MnHomeAddress 3784 -- object. 3785 -- 3786 -- OBJECT mip6MnHomeAddress 3787 -- SYNTAX InetAddress (SIZE(16)) 3788 -- DESCRIPTION 3789 -- This MIB module requires support for global 3790 -- ipv6 addresses for the mip6MnHomeAddress 3791 -- object. 3792 -- 3793 -- OBJECT mip6MnBLNodeAddressType 3794 -- SYNTAX InetAddressType { ipv6(2) } 3795 -- DESCRIPTION 3796 -- This MIB module requires support for global 3797 -- ipv6 addresses for the mip6MnBLNodeAddress 3798 -- object. 3799 -- 3800 -- OBJECT mip6MnBLNodeAddress 3801 -- SYNTAX InetAddress (SIZE(16)) 3802 -- DESCRIPTION 3803 -- This MIB module requires support for global 3804 -- ipv6 addresses for the mip6MnBLNodeAddress 3805 -- object. 3807 -- 3808 " 3809 MODULE -- this module 3810 MANDATORY-GROUPS { mip6MnSystemGroup, 3811 mip6MnConfGroup, 3812 mip6MnRegistrationGroup, 3813 mip6TotalTrafficGroup 3814 } 3815 ::= { mip6Compliances 8 } 3817 mip6CnCoreCompliance MODULE-COMPLIANCE 3818 STATUS current 3819 DESCRIPTION 3820 "The compliance statement for SNMP entities 3821 which implement the MOBILEIPV6-MIB and 3822 support monitoring of the basic correspondent node 3823 functionality. 3824 " 3825 MODULE -- this module 3826 MANDATORY-GROUPS { mip6CnGlobalStatsGroup, 3827 mip6TotalTrafficGroup 3828 } 3829 ::= { mip6Compliances 9 } 3831 mip6CnCompliance MODULE-COMPLIANCE 3832 STATUS current 3833 DESCRIPTION 3834 "The compliance statement for SNMP entities 3835 which implement the MOBILEIPV6-MIB and 3836 support monitoring of the basic correspondent node 3837 functionality. 3838 There are a number of INDEX objects that cannot be 3839 represented in the form of OBJECT clauses in SMIv2, 3840 but for which there are compliance requirements, 3841 expressed in OBJECT clause form in this description: 3842 -- OBJECT mip6BindingHomeAddressType 3843 -- SYNTAX InetAddressType { ipv6(2) } 3844 -- DESCRIPTION 3845 -- This MIB module requires support for global 3846 -- ipv6 addresses for the mip6BindingHomeAddress 3847 -- object. 3848 -- 3849 -- OBJECT mip6BindingHomeAddress 3850 -- SYNTAX InetAddress (SIZE(16)) 3851 -- DESCRIPTION 3852 -- This MIB module requires support for global 3853 -- ipv6 addresses for the mip6BindingHomeAddress 3854 -- object. 3856 " 3857 MODULE -- this module 3858 MANDATORY-GROUPS { mip6CnGlobalStatsGroup, 3859 mip6CnStatsGroup, 3860 mip6TotalTrafficGroup 3861 } 3862 ::= { mip6Compliances 10 } 3864 mip6HaCoreCompliance MODULE-COMPLIANCE 3865 STATUS current 3866 DESCRIPTION 3867 "The compliance statement for SNMP entities 3868 which implement the MOBILEIPV6-MIB and 3869 support monitoring of the basic home agent 3870 functionality. 3871 " 3872 MODULE -- this module 3873 MANDATORY-GROUPS { mip6HaSystemGroup 3874 } 3875 ::= { mip6Compliances 11 } 3877 mip6HaCompliance2 MODULE-COMPLIANCE 3878 STATUS current 3879 DESCRIPTION 3880 "The compliance statement for SNMP entities 3881 which implement the MOBILEIPV6-MIB and 3882 support monitoring of the home agent 3883 functionality specifically the Home Agent List 3884 and the home agent registration related statistics, 3885 There are a number of INDEX objects that cannot be 3886 represented in the form of OBJECT clauses in SMIv2, 3887 but for which there are compliance requirements, 3888 expressed in OBJECT clause form in this description: 3889 -- OBJECT mip6BindingHomeAddressType 3890 -- SYNTAX InetAddressType { ipv6(2) } 3891 -- DESCRIPTION 3892 -- This MIB module requires support for global 3893 -- ipv6 addresses for the mip6BindingHomeAddress 3894 -- object. 3895 -- 3896 -- OBJECT mip6BindingHomeAddress 3897 -- SYNTAX InetAddress (SIZE(16)) 3898 -- DESCRIPTION 3899 -- This MIB module requires support for global 3900 -- ipv6 addresses for the mip6BindingHomeAddress 3901 -- object. 3902 -- 3903 -- OBJECT mip6HaLinkLocalAddressType 3904 -- SYNTAX InetAddressType { ipv6z(4) } 3905 -- DESCRIPTION 3906 -- This MIB module requires support for local 3907 -- ipv6 addresses for the mip6HaLinkLocalAddress 3908 -- object 3909 -- 3910 -- OBJECT mip6HaLinkLocalAddress 3911 -- SYNTAX InetAddress (SIZE(20)) 3912 -- DESCRIPTION 3913 -- This MIB module requires support for local 3914 -- ipv6 addresses for the mip6HaLinkLocalAddress 3915 -- object. 3916 -- 3917 " 3918 MODULE -- this module 3919 MANDATORY-GROUPS { mip6HaSystemGroup, 3920 mip6HaListGroup, 3921 mip6HaStatsGroup, 3922 mip6HaGlobalStatsGroup, 3923 mip6TotalTrafficGroup 3924 } 3925 ::= { mip6Compliances 12 } 3927 mip6HaCompliance3 MODULE-COMPLIANCE 3928 STATUS current 3929 DESCRIPTION 3930 "The compliance statement for SNMP entities 3931 which implement the MOBILEIPV6-MIB and 3932 support monitoring and control of the home agent 3933 functionality specifically the Home Agent List 3934 and the home agent registration related statistics, 3936 There are a number of INDEX objects that cannot be 3937 represented in the form of OBJECT clauses in SMIv2, 3938 but for which there are compliance requirements, 3939 expressed in OBJECT clause form in this description: 3940 -- OBJECT mip6BindingHomeAddressType 3941 -- SYNTAX InetAddressType { ipv6(2) } 3942 -- DESCRIPTION 3943 -- This MIB module requires support for global 3944 -- ipv6 addresses for the mip6BindingHomeAddress 3945 -- object. 3946 -- 3947 -- OBJECT mip6BindingHomeAddress 3948 -- SYNTAX InetAddress (SIZE(16)) 3949 -- DESCRIPTION 3950 -- This MIB module requires support for global 3951 -- ipv6 addresses for the mip6BindingHomeAddress 3952 -- object. 3953 -- 3954 -- OBJECT mip6HaLinkLocalAddressType 3955 -- SYNTAX InetAddressType { ipv6z(4) } 3956 -- DESCRIPTION 3957 -- This MIB module requires support for local 3958 -- ipv6 addresses for the mip6HaLinkLocalAddress 3959 -- object 3960 -- 3961 -- OBJECT mip6HaLinkLocalAddress 3962 -- SYNTAX InetAddress (SIZE(20)) 3963 -- DESCRIPTION 3964 -- This MIB module requires support for local 3965 -- ipv6 addresses for the mip6HaLinkLocalAddress 3966 -- object. 3967 -- 3968 " 3969 MODULE -- this module 3970 MANDATORY-GROUPS { mip6HaSystemGroup, 3971 mip6HaListGroup, 3972 mip6HaStatsGroup, 3973 mip6HaGlobalStatsGroup, 3974 mip6BindingCacheCtlGroup, 3975 mip6TotalTrafficGroup 3976 } 3977 ::= { mip6Compliances 13 } 3979 mip6HaCoreReadOnlyCompliance MODULE-COMPLIANCE 3980 STATUS current 3981 DESCRIPTION 3982 "The compliance statement for SNMP entities 3983 which implement the MOBILEIPV6-MIB without support 3984 for read-write (i.e. in read-only mode) and, 3985 support monitoring of the basic home agent 3986 functionality. 3987 " 3988 MODULE -- this module 3989 MANDATORY-GROUPS { mip6HaSystemGroup 3990 } 3991 OBJECT mip6HaAdvPreference 3992 MIN-ACCESS read-only 3993 DESCRIPTION 3994 "Write access is not required." 3996 OBJECT mip6HaAdvLifetime 3997 MIN-ACCESS read-only 3998 DESCRIPTION 3999 "Write access is not required." 4001 OBJECT mip6HaPrefixAdv 4002 MIN-ACCESS read-only 4003 DESCRIPTION 4004 "Write access is not required." 4006 OBJECT mip6HaPrefixSolicitation 4007 MIN-ACCESS read-only 4008 DESCRIPTION 4009 "Write access is not required." 4011 OBJECT mip6HaMCastCtlMsgSupport 4012 MIN-ACCESS read-only 4013 DESCRIPTION 4014 "Write access is not required." 4016 ::= { mip6Compliances 14 } 4018 mip6HaReadOnlyCompliance2 MODULE-COMPLIANCE 4019 STATUS current 4020 DESCRIPTION 4021 "The compliance statement for SNMP entities 4022 which implement the MOBILEIPV6-MIB without support 4023 for read-write (i.e. in read-only mode) and, 4024 support monitoring of the home agent 4025 functionality specifically the Home Agent List 4026 and the home agent registration related statistics, 4028 There are a number of INDEX objects that cannot be 4029 represented in the form of OBJECT clauses in SMIv2, 4030 but for which there are compliance requirements, 4031 expressed in OBJECT clause form in this description: 4032 -- OBJECT mip6BindingHomeAddressType 4033 -- SYNTAX InetAddressType { ipv6(2) } 4034 -- DESCRIPTION 4035 -- This MIB module requires support for global 4036 -- ipv6 addresses for the mip6BindingHomeAddress 4037 -- object. 4038 -- 4039 -- OBJECT mip6BindingHomeAddress 4040 -- SYNTAX InetAddress (SIZE(16)) 4041 -- DESCRIPTION 4042 -- This MIB module requires support for global 4043 -- ipv6 addresses for the mip6BindingHomeAddress 4044 -- object. 4045 -- 4046 -- OBJECT mip6HaLinkLocalAddressType 4047 -- SYNTAX InetAddressType { ipv6z(4) } 4048 -- DESCRIPTION 4049 -- This MIB module requires support for local 4050 -- ipv6 addresses for the mip6HaLinkLocalAddress 4051 -- object 4052 -- 4053 -- OBJECT mip6HaLinkLocalAddress 4054 -- SYNTAX InetAddress (SIZE(20)) 4055 -- DESCRIPTION 4056 -- This MIB module requires support for local 4057 -- ipv6 addresses for the mip6HaLinkLocalAddress 4058 -- object. 4059 -- 4060 " 4061 MODULE -- this module 4062 MANDATORY-GROUPS { mip6HaSystemGroup, 4063 mip6HaListGroup, 4064 mip6HaStatsGroup, 4065 mip6HaGlobalStatsGroup, 4066 mip6TotalTrafficGroup 4067 } 4069 OBJECT mip6HaAdvPreference 4070 MIN-ACCESS read-only 4071 DESCRIPTION 4072 "Write access is not required." 4074 OBJECT mip6HaAdvLifetime 4075 MIN-ACCESS read-only 4076 DESCRIPTION 4077 "Write access is not required." 4079 OBJECT mip6HaPrefixAdv 4080 MIN-ACCESS read-only 4081 DESCRIPTION 4082 "Write access is not required." 4084 OBJECT mip6HaPrefixSolicitation 4085 MIN-ACCESS read-only 4086 DESCRIPTION 4087 "Write access is not required." 4089 OBJECT mip6HaMCastCtlMsgSupport 4090 MIN-ACCESS read-only 4091 DESCRIPTION 4092 "Write access is not required." 4094 ::= { mip6Compliances 15 } 4096 mip6HaReadOnlyCompliance3 MODULE-COMPLIANCE 4097 STATUS current 4098 DESCRIPTION 4099 "The compliance statement for SNMP entities 4100 which implement the MOBILEIPV6-MIB without support 4101 for read-write (i.e. in read-only mode) and, 4102 support monitoring and control of the home agent 4103 functionality specifically the Home Agent List 4104 and the home agent registration related statistics, 4106 There are a number of INDEX objects that cannot be 4107 represented in the form of OBJECT clauses in SMIv2, 4108 but for which there are compliance requirements, 4109 expressed in OBJECT clause form in this description: 4110 -- OBJECT mip6BindingHomeAddressType 4111 -- SYNTAX InetAddressType { ipv6(2) } 4112 -- DESCRIPTION 4113 -- This MIB module requires support for global 4114 -- ipv6 addresses for the mip6BindingHomeAddress 4115 -- object. 4116 -- 4117 -- OBJECT mip6BindingHomeAddress 4118 -- SYNTAX InetAddress (SIZE(16)) 4119 -- DESCRIPTION 4120 -- This MIB module requires support for global 4121 -- ipv6 addresses for the mip6BindingHomeAddress 4122 -- object. 4123 -- 4124 -- OBJECT mip6HaLinkLocalAddressType 4125 -- SYNTAX InetAddressType { ipv6z(4) } 4126 -- DESCRIPTION 4127 -- This MIB module requires support for local 4128 -- ipv6 addresses for the mip6HaLinkLocalAddress 4129 -- object 4130 -- 4131 -- OBJECT mip6HaLinkLocalAddress 4132 -- SYNTAX InetAddress (SIZE(20)) 4133 -- DESCRIPTION 4134 -- This MIB module requires support for local 4135 -- ipv6 addresses for the mip6HaLinkLocalAddress 4136 -- object. 4137 -- 4138 " 4139 MODULE -- this module 4140 MANDATORY-GROUPS { mip6HaSystemGroup, 4141 mip6HaListGroup, 4142 mip6HaStatsGroup, 4143 mip6HaGlobalStatsGroup, 4144 mip6BindingCacheCtlGroup, 4145 mip6TotalTrafficGroup 4146 } 4148 OBJECT mip6HaAdvPreference 4149 MIN-ACCESS read-only 4150 DESCRIPTION 4151 "Write access is not required." 4153 OBJECT mip6HaAdvLifetime 4154 MIN-ACCESS read-only 4155 DESCRIPTION 4156 "Write access is not required." 4158 OBJECT mip6HaPrefixAdv 4159 MIN-ACCESS read-only 4160 DESCRIPTION 4161 "Write access is not required." 4163 OBJECT mip6HaPrefixSolicitation 4164 MIN-ACCESS read-only 4165 DESCRIPTION 4166 "Write access is not required." 4168 OBJECT mip6HaMCastCtlMsgSupport 4169 MIN-ACCESS read-only 4170 DESCRIPTION 4171 "Write access is not required." 4173 OBJECT mip6BindingAdminStatus 4174 MIN-ACCESS read-only 4175 DESCRIPTION 4176 "Write access is not required." 4178 ::= { mip6Compliances 16 } 4180 mip6NotificationCompliance MODULE-COMPLIANCE 4181 STATUS current 4182 DESCRIPTION 4183 "The compliance statement for SNMP entities 4184 which implement the MOBILEIPV6-MIB and 4185 support Notification from home agent or 4186 correspondent node to management stations 4187 about the mobile node status. 4188 There are a number of INDEX objects that cannot be 4189 represented in the form of OBJECT clauses in SMIv2, 4190 but for which there are compliance requirements, 4191 expressed in OBJECT clause form in this description: 4193 -- OBJECT mip6BindingHomeAddressType 4194 -- SYNTAX InetAddressType { ipv6(2) } 4195 -- DESCRIPTION 4196 -- This MIB module requires support for global 4197 -- ipv6 addresses for the mip6BindingHomeAddress 4198 -- object. 4199 -- 4200 -- OBJECT mip6BindingHomeAddress 4201 -- SYNTAX InetAddress (SIZE(16)) 4202 -- DESCRIPTION 4203 -- This MIB module requires support for global 4204 -- ipv6 addresses for the mip6BindingHomeAddress 4205 -- object. 4206 " 4207 MODULE -- this module 4208 MANDATORY-GROUPS { mip6NotificationGroup 4209 } 4210 ::= { mip6Compliances 17 } 4212 END 4214 6. Security Considerations 4216 There are a number of management objects defined in this MIB module 4217 with a MAX-ACCESS clause of read-write. Such objects may be 4218 considered sensitive or vulnerable in some network environments. The 4219 support for SET operations in a non-secure environment without proper 4220 protection can have a negative effect on network operations. These 4221 are the tables and objects and the corresponding 4222 sensitivity/vulnerability: 4223 mip6Status: The value of this object is used to enable or 4224 disable the MIPv6 functionality on a MIPv6 entity. 4225 Access to this MO may be abused to disrupt the 4226 MIPv6 communication. 4227 mip6HaAdvPreference: Access to this object may be abused to 4228 force MNs into selecting the wrong HA. 4229 mip6HaAdvLifetime: Access to this object may be abused to set 4230 the advertised lifetime to incorrect values. That 4231 will have an adverse impact on the MIPv6 4232 communication. 4233 mip6BindingAdminStatus: The value of this object is used to 4234 control the status of a binding cache entry. 4235 Access to this object may be abused to deny mobile 4236 IPv6 connectivity to a legitimate user or, to 4237 grant Mobile IPv6 connectivity to an illegal user. 4238 mip6HaPrefixAdv: The value of this object indicates whether 4239 the home agent will send ICMP Mobile Prefix 4240 Advertisements to the mobile node. 4241 Access to this object may be abused to send 4242 unwanted/wrong prefix information or to deny the 4243 mobile node from receiving information about the 4244 changes in the home prefixes. 4245 This may result in disruption of the Mobile IPv6 4246 connectivity. 4247 mip6HaPrefixSolicitation: The value of this object indicates 4248 whether the home agent should respond to ICMP 4249 Mobile Prefix Solicitation messages from a mobile 4250 node. Access to this object may be abused to deny 4251 the mobile node information about its home prefix. 4252 This may result in disruption of the Mobile IPv6 4253 connectivity. 4254 mip6HaMCastCtlMsgSupport: The value of this object decides 4255 whether the home agent should process the 4256 multicast group membership control messages it 4257 receives from mobile nodes. Access to this object 4258 maybe used to subvert administrate policy on 4259 multicasting, or to disrupt the multicast 4260 communication with the mobile node. 4262 Some of the readable objects in this MIB module (i.e., objects with a 4263 MAX-ACCESS other than not-accessible) may be considered sensitive or 4264 vulnerable in some network environments. It is thus important to 4265 control even GET and/or NOTIFY access to these objects and possibly 4266 to even encrypt the values of these objects when sending them over 4267 the network via SNMP. These are the tables and objects and their 4268 sensitivity/vulnerability: 4270 The address related objects in this MIB may be considered to be 4271 particularly sensitive and/or private. The care-of address related 4272 objects reveal the location and movement of the mobile node. This 4273 information may be considered to be private and sensitive and must 4274 be carefully handled. 4275 mip6BindingHstCOAType 4276 mip6BindingHstCOA 4277 mip6MnBLCOAType 4278 mip6MnBLCOA 4280 The mobile node's home address and home agent related information 4281 may be considered to be sensitive too as these may provide clues to 4282 a malicious party on ways to disrupt the mobile nodes communication 4283 channels. 4284 mip6BindingHstHomeAddressType, 4285 mip6BindingHstHomeAddress, 4286 mip6MnHomeAddressType, 4287 mip6MnHomeAddress 4289 The correspondent node's addresses related MOs will reveal the nodes 4290 with whom the mobile node is corresponding. This information may be 4291 considered private and sensitive. 4292 mip6MnBLNodeAddressType, 4293 mip6MnBLNodeAddress 4295 SNMP versions prior to SNMPv3 did not include adequate security. 4296 Even if the network itself is secure (for example by using IPSec), 4297 even then, there is no control as to who on the secure network is 4298 allowed to access and GET/SET (read/change/create/delete) the objects 4299 in this MIB module. 4301 It is RECOMMENDED that implementers consider the security features as 4302 provided by the SNMPv3 framework (see [RFC3410], section 8), 4303 including full support for the SNMPv3 cryptographic mechanisms (for 4304 authentication and privacy). 4306 Further, deployment of SNMP versions prior to SNMPv3 is NOT 4307 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 4308 enable cryptographic security. It is then a customer/operator 4309 responsibility to ensure that the SNMP entity giving access to an 4310 instance of this MIB module is properly configured to give access to 4311 the objects only to those principals (users) that have legitimate 4312 rights to indeed GET or SET (change/create/delete) them. 4314 7. IANA Considerations 4316 IANA should assign a base arc in the 'mib-2' (standards track) OID 4317 tree for the 'mip6MIB' MODULE-IDENTITY defined in the Mobile-IPv6 4318 MIB. 4320 8. References 4322 8.1 Normative References 4324 [RFC2119] Bradner, S., Key words for use in RFCs to Indicate 4325 Requirements Levels, BCP 14, RFC 2119, March 1997. 4327 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 4328 J., Rose, M. and S. Waldbusser, Structure of 4329 Management Information Version 2 (SMIv2), STD 58, 4330 RFC 2578, April 1999. 4332 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 4333 J., Rose, M. and S. Waldbusser, Textual Conventions 4334 for SMIv2, STD 58, RFC 2579, April 1999. 4336 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 4337 J., Rose, M. and S. Waldbusser, Conformance 4338 Statements for SMIv2, STD 58, RFC 2580, April 1999. 4340 [RFC3775] Johnson, D., Perkins, C. and Arkko J., Mobility 4341 Support in IPv6 RFC 3775, June 2004. 4343 [RFC2011bis] Routhier, S., Management Information Base for the 4344 Internet Protocol (IP), work in progress (currently 4345 ). 4347 [RFC3291bis] Daniele, M., Haberman, B., Routhier, S. and 4348 Schoenwaelder, J., Textual Conventions for Internet 4349 Network Addresses, work in progress (currently 4350 ). 4352 8.2 Informative References 4354 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 4355 Introduction and Applicability Statements for 4356 Internet-Standard Management Framework, RFC 3410, 4357 December 2002. 4359 9. Acknowledgments 4361 The following groups and individuals have contributed to this draft 4362 with discussions and comments: 4363 WIDE-netman group 4364 C.M. Heard 4366 10. Authors' Addresses 4368 Glenn Mansfield Keeni 4369 Cyber Solutions Inc. 4370 6-6-3 Minami Yoshinari 4371 Aoba-ku, Sendai 989-3204 4372 Japan 4374 Phone: +81-22-303-4012 4375 EMail: glenn@cysols.com 4377 Kenichi Nagami 4378 INTEC NetCore Inc. 4379 1-3-3, Shin-suna 4380 Koto-ku, Tokyo, 135-0075 4381 Japan 4383 Phone: +81-3-5665-5069 4384 E-mail: nagami@inetcore.com 4386 Kazuhide Koide 4387 Tohoku University 4388 Katahira Campus 4389 Sendai 4390 Japan 4392 Phone: +81-22-217-5454 4393 E-mail: koide@shiratori.riec.tohoku.ac.jp 4395 Sri Gundavelli 4396 Cisco Systems 4397 170 W.Tasman Drive, 4398 San Jose, CA 95134 4399 USA 4401 Phone: +1-408-527-6109 4402 Email: sgundave@cisco.com 4404 11. Full Copyright Statement 4406 Copyright (C) The Internet Society (2004). This document is subject 4407 to the rights, licenses and restrictions contained in BCP 78, and 4408 except as set forth therein, the authors retain all their rights. 4410 This document and the information contained herein are provided on an 4411 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 4412 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 4413 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 4414 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 4415 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 4416 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4418 Intellectual Property 4420 The IETF takes no position regarding the validity or scope of any 4421 Intellectual Property Rights or other rights that might be claimed 4422 to pertain to the implementation or use of the technology 4423 described in this document or the extent to which any license 4424 under such rights might or might not be available; nor does it 4425 represent that it has made any independent effort to identify any 4426 such rights. Information on the procedures with respect to 4427 rights in RFC documents can be found in BCP 78 and BCP 79. 4429 Copies of IPR disclosures made to the IETF Secretariat and any 4430 assurances of licenses to be made available, or the result of an 4431 attempt made to obtain a general license or permission for the use 4432 of such proprietary rights by implementers or users of this 4433 specification can be obtained from the IETF on-line IPR repository 4434 at http://www.ietf.org/ipr. 4436 The IETF invites any interested party to bring to its attention 4437 any copyrights, patents or patent applications, or other 4438 proprietary rights that may cover technology that may be required 4439 to implement this standard. Please address the information to the 4440 IETF at ietf-ipr@ietf.org. 4442 Acknowledgment 4444 Funding for the RFC Editor function is currently provided by the 4445 Internet Society. 4447 Changes since draft-ietf-mip6-mipv6-mib-06.txt 4448 a. Fixed the DESCRIPTION of mip6BindingCacheTable 4449 reworded second paragraph to 4450 "Entries in this table are not required to survive 4451 a reboot of the managed entity." 4452 b. Fixed the DESCRIPTION of mip6HaCoreReadOnlyCompliance 4453 Irrelevant pseudo-OBJECTS clauses have been removed. 4454 c. Editorial nits 4456 Changes since draft-ietf-mip6-mipv6-mib-05.txt 4457 a. Fixed REFERENCE of mip6Capabilities 4458 RFC3775 : Section 3.2, 4.1 4459 b. Added text in descriptions about the read-write objects 4460 mip6Status: 4461 The value of this object SHOULD remain unchanged 4462 across reboots of the managed entity. 4463 mip6BindingCacheTable: 4464 The values of the mip6BindingAdminStatus object 4465 in the conceptual rows of this table will be 4466 flushed after reboots of the managed entity. 4468 c. Fixed SYNTAX of mip6BindingUsageCount to Gauge32 4469 d. Fixed SYNTAX of mip6BindingMaxSeq to Unsigned32 (0..65536) 4470 e. Fixed SYNTAX of mip6BindingHstUsageCount to Gauge32 4471 f. Fixed SYNTAX of mip6HCInOctets to Counter64 4472 SYNTAX of mip6HCInPkts to Counter64 4473 SYNTAX of mip6HCOutOctets to Counter64 4474 SYNTAX of mip6HCOutPkts to Counter64 4475 SYNTAX of mip6HCOutPkts to Counter64 4476 g. Fixed SYNTAX of mip6MnBLRetransmissions to Gauge32 4477 h. Added MO mip6MnBLDontSendBUFlag 4478 mip6MnBLDontSendBUFlag OBJECT-TYPE 4479 SYNTAX TruthValue 4480 MAX-ACCESS read-only 4481 STATUS current 4482 DESCRIPTION 4483 "true(1) indicates that future binding updates 4484 will not be sent to mip6MnBLNodeAddress. 4485 false(2) implies that binding updates will be 4486 sent to mip6MnBLNodeAddress. 4487 The mobile node sets this flag in the when it 4488 receives an ICMP Parameter Problem, Code 1, 4489 error message in response to a return 4490 routability message or Binding Update sent to 4491 mip6MnBLNodeAddress. 4492 " 4493 REFERENCE 4494 "RFC3775 : Section 11.1" 4496 ::= { mip6MnBLEntry 12 } 4498 i. Fixed SYNTAX of mip6MnBLMaxSeq to Unsigned32 (0..65536) 4499 j. Added REFERENCE for 4500 mip6CnBUsAccepted "RFC3775 : Section 9.5.1, 9.5.4" 4501 k. Added the counter discontinuity clause in the DESCRIPTION of 4502 mip6HaAdvsRecd: 4503 Discontinuities in the value of this counter can 4504 occur at re-initialization of the management system, 4505 and at other times as indicated by the value of 4506 mip6CounterDiscontinuityTime. 4507 l. Fixed REFERENCE of mip6HaAdvsRecd "RFC3775 : Section 7" 4508 m. Added text in DESCRIPTION about the read-write objects in 4509 mip6HaConfTable 4510 It is RECOMMENDED that the last written values 4511 of the objects in the conceptual rows of this 4512 table will remain unchanged across reboots of 4513 the managed entity provided that, the interfaces 4514 have not been renumbered after the reboot. 4515 n. Added text in DESCRIPTION about behaviour of 4516 mip6HaPrefixAdv 4517 The state can be changed from enabled(1) to 4518 disabled(2) and vice versa by operator 4519 intervention. 4520 Causing the state to change from enabled(1) to 4521 disabled(2) will result in the home agent 4522 disabling the Prefix advertisement function. 4523 On the other hand, changing the status from 4524 disabled(2) to enabled(1) will start the prefix 4525 advertisement funtion. 4526 o. Added text in DESCRIPTION of 4527 mip6HaGlAddrEntry 4528 There is no upper-bound on the maximum number of 4529 global addresses on an interface but, for practical 4530 purposes the upper-bound of the value 4531 mip6HaGaAddrSeqNo is set to 1024. 4532 p. Changed the MO name from mip6MnMoved to mip6MnCOAChanged 4533 q. Added REFERENCE to the Notification Object 4534 mip6MnRegistered 4535 mip6MnCOAChanged 4536 mip6MnBindingExpiredAtHA 4538 r. Clarified the DESCRIPTION of the Notification 4539 mip6MnRegistered 4540 mip6MnCOAChanged 4541 mip6MnBindingExpiredAtHA 4542 This notification is sent by a home agent when 4543 a mobile node registers with the home agent 4544 for the first time. 4545 s. Fixed the DESCRIPTIONS of the compliances objects for the 4546 INDEX objects that cannot be represented in the form of 4547 OBJECT clauses in SMIv2, 4549 t. Editorial nits 4551 Changes since draft-ietf-mip6-mipv6-mib-04,txt 4552 a. Fixed the InetAddress/InetAddressType usage. Now there 4553 is provision for supporting protocols other than IPv6. 4554 - the statements constraining the InetAddressType ot 4555 ipv6(2) and ipv6z(4) have been removed from the 4556 DESCRIPTION clauses of the InetAddressType type MOs. 4557 - the statements constraining the InetAddress to a size 4558 of 16 and 20 octets have been removed from the 4559 DESCRIPTION clauses of the corresponding InetAddress 4560 type MOs. 4561 - the DESCRIPTION clauses of conceptual rows that have 4562 InetAddress type MOs as index have been revised to 4563 contain a note like- 4564 Implementors need to be aware that if the total 4565 number of octets in InetAddress type index MOs 4566 (e.g. mip6BindingHomeAddress) exceeds 113 then OIDs 4567 of column instances in this row will have more than 4568 128 sub-identifiers and cannot be accessed using 4569 SNMPv1, SNMPv2c, or SNMPv3. 4570 - fixed the DESCRIPTION of mip6BindingCOA. 4571 deleted the statement - A mobile node can have 4572 multiple care-of addresses. It is correct but not 4573 relevant in the context of the mip6BindingCacheEntry. 4574 There will be only one mip6BindingCOA for a 4575 mip6BindingHomeAddress. 4576 - editorial nits 4577 b. Nits fixed in References Section 4578 - included citation tag for IP-MIB [RFC2011bis] 4579 - included citation tag for INET-ADDRESS-MIB [RFC3291bis] 4580 - added RFC2119 to the references list 4581 - added RFC3291bis to the references list 4582 - changed citation tag from [MIPv6] to [RFC3775] 4583 - fixed the "Normative References" and "Informative References" 4584 section tags. 4586 c. Added OBJECT clause for mip6BindingAdminStatus that specifies 4587 a MIN-ACCESS of read-only for mip6HaReadOnlyCompliance3 4589 d. Fixed editorial nits 4590 - 4592 Changes since draft-ietf-mip6-mipv6-mib-03,txt 4594 a. Title changed to Mobile IPv6 Management Information Base 4595 b. Informative references cleaned up. Aligned with the latest 4596 MIB boilerplate. Unreferenced pointers removed. 4597 c. In the MOBILEIPV6-MIB replaced ipv6IfIndex by ipv6InterfaceIfIndex 4598 This object is now imported from IP-MIB 4599 d. Added normative reference for IP-MIB 4600 e. Added security considerations text for 4601 mip6BindingAdminStatus 4602 mip6HaPrefixAdv 4603 mip6HaPrefixSolicitation 4604 mip6HaMCastCtlMsgSupport 4605 f. Base type of Mipv6BURequestRejectionCode changed from BITS to 4606 enumerated integer. 4607 g. NOTIFICATION-GROUP imported and NOTIFICATION objects included 4608 in the mip6NotificationGroup of type NOTIFICATION-GROUP. 4609 h. mip6BindingHstIndex range changed from (0..4294967295) to 4610 (1..4294967295. 4611 i. Index ordering for mip6MnBLEntry changed 4612 From: 4613 INDEX { mip6MnBLNodeAddressType, 4614 mip6MnBLNodeAddress, 4615 mip6MnHomeAddressType, 4616 mip6MnHomeAddress 4617 } 4618 To: 4619 INDEX { mip6MnHomeAddressType, 4620 mip6MnHomeAddress, 4621 mip6MnBLNodeAddressType, 4622 mip6MnBLNodeAddress 4623 } 4624 j. SIZE constraints for InetAddress objects used indices have 4625 been removed. Instead, appropriate constraints are specified 4626 in the corresponding DESCRIPTION clauses 4627 k. DESCRIPTION clauses of InetAddress objects have been updated 4628 with the specification of the InetAddressType object which 4629 provides the context or type of the InetAddress object.. 4630 l. Description has been added in the form of commented 4631 OBJECT clauses to the DESCRIPTION clauses of the 4632 MODULE-COMPLIANCE for the inaccessible index objects. 4633 m. All notifications have been directly registered under 4634 mip6Notifications. 4636 n. A read-only compliance has been added. 4637 o. Formatting to take care of lines longer than 72 columns. 4639 p. Other editing issues have been addressed. 4641 Changes since draft-ietf-mip6-mipv6-mib-02.txt 4643 a. Aligned with the new I-D format requirements 4644 "Status of this memo" is updated 4645 IANA considerations section is added 4646 Copyright is included in the MIB MODULE IDENTITY Description 4647 Full Copyright Statement updated 4648 b. Changed the MO name prefix from mipv6 to mip6 4649 c. Added the instance specifications for MOs included in 4650 Notifications 4651 d. Reference to the base MIP6 document is updated from the I-D to 4652 RFC3775