Network Working Group D. Cong & M. Hamlen, Editors Request for Comments: 2006 Motorola Category: Standards Track C. Perkins, Editor IBM October 1996 The Definitions of Managed Objects for IP Mobility Support using SMIv2 Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Abstract This memo defines the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol. Table of Contents 1. The Network Management Framework ...................... 2 2. Objects ............................................... 2 2.1 Object Definitions ................................... 2 3. Overview .............................................. 2 3.1 Object Selection Criteria ............................ 2 3.2 Structure of the Mobile IP ........................... 3 3.3 MIB Groups ........................................... 4 4. Definitions ........................................... 5 5. Acknowledgements ...................................... 49 6. Security Considerations ............................... 49 7. References ............................................ 50 8. Chair's Address ....................................... 51 9. Editors' Addresses .................................... 52 Cong, Hamlen & Perkins Standards Track [Page 1] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 1. The SNMP Network Management Framework The Internet-standard Network Management Framework presently consists of three major components. They are: The SMI, described in RFC 1902 [1] - the mechanisms used for describing and naming objects for the purpose of management. The MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects for the Internet suite of protocols. The protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for accessing managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 2. Objects 2.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. 3. Overview 3.1. Object Selection Criteria To be consistent with IAB directives and good engineering practice, the authors have applied some criteria to select managed objects for the Mobile IP Protocol. (1) Partition management functionality among the Mobile Node, Home Agent, and Foreign Agent according to the partitioning seen in the Mobile IP Protocol. (2) Require that objects be essential for either fault or configuration management. (3) Limit the total number of objects. Cong, Hamlen & Perkins Standards Track [Page 2] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 (4) Exclude objects which are simply derivable from others in this or other MIBs. 3.2. Structure of the Mobile IP This section describes the basic model of Mobile IP used in developing the Mobile IP MIB. This information should be useful to the implementor in understanding some of the basic design decisions of the MIB. The Mobile IP Protocol introduces these new funtional entities: Mobile Node A host or router that changes its point of attachment from one network or subnetwork to another. A mobile node may change its location without losing connectivity and without changing its IP address; it may continue to communicate with other Internet nodes at any location using its (constant) IP address, assuming link- layer connectivity to a point of attachment is available. Home Agent A router on a mobile node's home network which tunnels packets for delivery to the mobile node when it is away from home, and maintains current location information for the mobile node. Foreign Agent A router on a mobile node's visited network which provides routing services to the mobile node while registered. The foreign agent detunnels and delivers packets to the mobile node that were tunneled by the mobile node's home agent. For datagrams sent by a mobile node, the foreign agent may serve as a default router for registered mobile nodes. This document specifies the objects used in managing these entities; namely, the Mobile Node, the Home Agent, and the Foreign Agent. Cong, Hamlen & Perkins Standards Track [Page 3] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 3.3. MIB Groups Objects in this MIB are arranged into groups. Each group is organized as a set of related objects. The overall structure and the relationship between groups and the Mobile IP entities are shown below: Groups Mobile Node Foreign Agent Home Agent mipSystemGroup X X X mipSecAssociationGroup X X X mipSecViolationGroup X X X mnSystemGroup X mnDiscoveryGroup X mnRegistrationGroup X maAdvertisementGroup X X faSystemGroup X faAdvertisementGroup X faRegistrationGroup X haRegistrationGroup X haRegNodeCountersGroup X Cong, Hamlen & Perkins Standards Track [Page 4] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 4. Definitions MIP-MIB DEFINITIONS ::= BEGIN IMPORTS Counter32, Gauge32, Integer32, IpAddress, experimental, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE FROM SNMPv2-SMI RowStatus, TruthValue, TimeStamp, TEXTUAL-CONVENTION FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; mipMIB MODULE-IDENTITY LAST-UPDATED "9606040000Z" ORGANIZATION "IETF Mobile IP Working Group" CONTACT-INFO " David Cong Postal: Motorola 1301 E. Algonquin Rd. Schaumburg, IL 60196 Phone: +1-847-576-1357 Email: cong@comm.mot.com" DESCRIPTION "The MIB Module for the Mobile IP." ::= { mib-2 44 } mipMIBObjects OBJECT IDENTIFIER ::= { mipMIB 1 } -- Groups under mipMIBObjects mipSystem OBJECT IDENTIFIER ::= { mipMIBObjects 1 } mipSecurity OBJECT IDENTIFIER ::= { mipMIBObjects 2 } mipMN OBJECT IDENTIFIER ::= { mipMIBObjects 3 } mipMA OBJECT IDENTIFIER ::= { mipMIBObjects 4 } mipFA OBJECT IDENTIFIER ::= { mipMIBObjects 5 } mipHA OBJECT IDENTIFIER ::= { mipMIBObjects 6 } mnSystem OBJECT IDENTIFIER ::= { mipMN 1 } mnDiscovery OBJECT IDENTIFIER ::= { mipMN 2 } mnRegistration OBJECT IDENTIFIER ::= { mipMN 3 } maAdvertisement OBJECT IDENTIFIER ::= { mipMA 2 } faSystem OBJECT IDENTIFIER ::= { mipFA 1 } faAdvertisement OBJECT IDENTIFIER ::= { mipFA 2 } faRegistration OBJECT IDENTIFIER ::= { mipFA 3 } Cong, Hamlen & Perkins Standards Track [Page 5] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 haRegistration OBJECT IDENTIFIER ::= { mipHA 3 } -- Textual convention RegistrationFlags ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is used to define the registration flags for Mobile IP registration extension: vjCompression -- Request to use VJ compression gre -- Request to use GRE minEnc -- Request to use minimal encapsulation decapsulationByMN -- Decapsulation by mobile node broadcastDatagram -- Request to receive broadcasts simultaneoursBindings -- Request to retain prior binding(s)." SYNTAX BITS { vjCompression(0), gre(1), minEnc(2), decapsulationbyMN(3), broadcastDatagram(4), simultaneousBindings(5) } -- mipSystem Group mipEntities OBJECT-TYPE SYNTAX BITS { mobileNode(0), foreignAgent(1), homeAgent(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object describes which Mobile IP entities are supported by this managed entity. The entity may support more than one Mobile IP entities. For example, the entity supports both Foreign Agent (FA) and Home Agent (HA). Therefore, bit 1 and bit 2 are set to 1 for this object." ::= { mipSystem 1 } Cong, Hamlen & Perkins Standards Track [Page 6] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 mipEnable OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether the Mobile IP protocol should be enabled for the managed entity. If it is disabled, the entity should disable both agent discovery and registration functions." ::= { mipSystem 2 } mipEncapsulationSupported OBJECT-TYPE SYNTAX BITS { ipInIp(0), gre(1), minEnc(2), other(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Encapsulation methods supported by the Mobile IP entity. The entity may support multiple encapsulation methods or none of them: ipInIp(0), -- IP Encapsulation within IP gre(1), -- Generic Routing Encapsulation, -- refers to RFC1701 minEnc(2), -- Minimal Encapsulation within IP." ::= { mipSystem 3 } -- mipSecurity Group mipSecAssocTable OBJECT-TYPE SYNTAX SEQUENCE OF MipSecAssocEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing Mobility Security Associations." ::= { mipSecurity 1 } mipSecAssocEntry OBJECT-TYPE SYNTAX MipSecAssocEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "One particular Mobility Security Association." INDEX { mipSecPeerAddress, mipSecSPI } ::= { mipSecAssocTable 1 } Cong, Hamlen & Perkins Standards Track [Page 7] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 MipSecAssocEntry ::= SEQUENCE { mipSecPeerAddress IpAddress, mipSecSPI Unsigned32, mipSecAlgorithmType INTEGER, mipSecAlgorithmMode INTEGER, mipSecKey OCTET STRING, mipSecReplayMethod INTEGER } mipSecPeerAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP address of the peer entity with which this node shares the mobility security association." ::= { mipSecAssocEntry 1 } mipSecSPI OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The SPI is the 4-byte opaque index within the Mobility Security Association which selects the specific security parameters to be used to authenticate the peer, i.e. the rest of the variables in this MipSecAssocEntry." ::= { mipSecAssocEntry 2 } mipSecAlgorithmType OBJECT-TYPE SYNTAX INTEGER { other(1), md5(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "Type of security algorithm." ::= { mipSecAssocEntry 3 } mipSecAlgorithmMode OBJECT-TYPE SYNTAX INTEGER { other(1), prefixSuffix(2) } MAX-ACCESS read-create Cong, Hamlen & Perkins Standards Track [Page 8] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 STATUS current DESCRIPTION "Security mode used by this algorithm." ::= { mipSecAssocEntry 4 } mipSecKey OBJECT-TYPE SYNTAX OCTET STRING (SIZE(16)) MAX-ACCESS read-create STATUS current DESCRIPTION "The shared secret key for the security associations. Reading this object will always return zero length value." ::= { mipSecAssocEntry 5 } mipSecReplayMethod OBJECT-TYPE SYNTAX INTEGER { other(1), timestamps(2), nonces(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "The replay-protection method supported for this SPI within this Mobility Security Association." ::= { mipSecAssocEntry 6 } -- Mobile IP security violation total counter mipSecTotalViolations OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of security violations in the entity" ::= { mipSecurity 2 } -- Mobile IP security violation table mipSecViolationTable OBJECT-TYPE SYNTAX SEQUENCE OF MipSecViolationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing information about security violations." ::= { mipSecurity 3 } Cong, Hamlen & Perkins Standards Track [Page 9] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 mipSecViolationEntry OBJECT-TYPE SYNTAX MipSecViolationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about one particular security violation." INDEX { mipSecViolatorAddress } ::= { mipSecViolationTable 1 } MipSecViolationEntry ::= SEQUENCE { mipSecViolatorAddress IpAddress, mipSecViolationCounter Counter32, mipSecRecentViolationSPI Integer32, mipSecRecentViolationTime TimeStamp, mipSecRecentViolationIDLow Integer32, mipSecRecentViolationIDHigh Integer32, mipSecRecentViolationReason INTEGER } mipSecViolatorAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "Violator's IP address. The violator is not necessary in the mipSecAssocTable." ::= { mipSecViolationEntry 1 } mipSecViolationCounter OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of security violations for this peer." ::= { mipSecViolationEntry 2 } mipSecRecentViolationSPI OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "SPI of the most recent security violation for this peer. If the security violation is due to an identification mismatch, then this is the SPI from the Mobile-Home Authentication Extension. If the security violation is due to an invalid authenticator, then this is the SPI from the offending authentication Cong, Hamlen & Perkins Standards Track [Page 10] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 extension. In all other cases, it should be set to zero." ::= { mipSecViolationEntry 3 } mipSecRecentViolationTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "Time of the most recent security violation for this peer." ::= { mipSecViolationEntry 4 } mipSecRecentViolationIDLow OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Low-order 32 bits of identification used in request or reply of the most recent security violation for this peer." ::= { mipSecViolationEntry 5 } mipSecRecentViolationIDHigh OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "High-order 32 bits of identification used in request or reply of the most recent security violation for this peer." ::= { mipSecViolationEntry 6 } mipSecRecentViolationReason OBJECT-TYPE SYNTAX INTEGER { noMobilitySecurityAssociation(1), badAuthenticator(2), badIdentifier(3), badSPI(4), missingSecurityExtension(5), other(6) } MAX-ACCESS read-only STATUS current DESCRIPTION "Reason for the most recent security violation for this peer." ::= { mipSecViolationEntry 7 } Cong, Hamlen & Perkins Standards Track [Page 11] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 -- mipMN Group -- mipSystem Group mnState OBJECT-TYPE SYNTAX INTEGER { home(1), registered(2), pending(3), isolated(4), unknown(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates mobile node's state of Mobile IP: home, -- MN is connected to home network. registered, -- MN has registered on foreign network pending, -- MN has sent registration request and is waiting for the reply isolated, -- MN is isolated from network unknown -- MN can not determine its state." ::= { mnSystem 1 } mnHomeAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "An IP address that is assigned for an extended period of time to the mobile node. It remains unchanged regardless of the mobile node's current point of attachment." ::= { mnSystem 2 } -- Mobile node's home agent list mnHATable OBJECT-TYPE SYNTAX SEQUENCE OF MnHAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Cong, Hamlen & Perkins Standards Track [Page 12] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 "A table containing all of the mobile node's potential home agents." ::= { mnSystem 3 } mnHAEntry OBJECT-TYPE SYNTAX MnHAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information for a particular Home Agent." INDEX { mnHAAddress } ::= { mnHATable 1 } MnHAEntry ::= SEQUENCE { mnHAAddress IpAddress, mnCurrentHA TruthValue, mnHAStatus RowStatus } mnHAAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "IP address of mobile node's Home Agent." ::= { mnHAEntry 1 } mnCurrentHA OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Whether this home agent is the current home agent for the mobile node. If it is true, the mobile node is registered with that home agent." ::= { mnHAEntry 2 } mnHAStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The row status for this home agent entry. If the status is set to 'createAndGo' or 'active', then the mobile node can use mnHAAddress as a valid candidate for a home agent. If the status is set to 'destroy', then the mobile node should delete this row, and deregister from that home agent." Cong, Hamlen & Perkins Standards Track [Page 13] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 ::= { mnHAEntry 3 } mnFATable OBJECT-TYPE SYNTAX SEQUENCE OF MnFAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing all foreign agents that the mobile node knows about and their corresponding COA (care-of address). This COA is an address of a foreign agent with which the mobile node is registered. The table is updated when advertisements are received by the mobile node. If an advertisement expires, its entry(s) should be deleted from the table. One foreign agent can provide more than one COA in its advertisements." ::= { mnDiscovery 1 } mnFAEntry OBJECT-TYPE SYNTAX MnFAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "One pair of foreign agent IP address and COA for that foreign agent." INDEX { mnFAAddress, mnCOA } ::= { mnFATable 1 } MnFAEntry ::= SEQUENCE { mnFAAddress IpAddress, mnCOA IpAddress } mnFAAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "Foreign agent's IP address." ::= { mnFAEntry 1 } mnCOA OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "A care-of address being offered by this foreign agent or a co-located care-of address which the mobile node has associated with one of its own network Cong, Hamlen & Perkins Standards Track [Page 14] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 interfaces." ::= { mnFAEntry 2 } -- Mobile node could store multiple agent advertisements, however, -- only the most recently received agent advertisement information -- is required to be made available to the manager station. mnRecentAdvReceived OBJECT IDENTIFIER ::= { mnDiscovery 2 } mnAdvSourceAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The source IP address of the most recently received Agent Advertisement. This address could be the address of a home agent or a foreign agent." ::= { mnRecentAdvReceived 1 } mnAdvSequence OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The sequence number of the most recently received advertisement. The sequence number ranges from 0 to 0xffff. After the sequence number attains the value 0xffff, it will roll over to 256." ::= { mnRecentAdvReceived 2 } mnAdvFlags OBJECT-TYPE SYNTAX BITS { vjCompression(0), gre(1), minEnc(2), foreignAgent(3), homeAgent(4), busy(5), regRequired(6) } MAX-ACCESS read-only STATUS current DESCRIPTION "The flags are contained in the 7th byte in the extension of the most recently received mobility agent advertisement: vjCompression -- Agent supports Van Jacobson compression Cong, Hamlen & Perkins Standards Track [Page 15] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 gre -- Agent offers Generice Routing Encapsulation minEnc, -- Agent offers Minimal Encapsulation foreignAgent, -- Agent is a Foreign Agent homeAgent, -- Agent is a Home Agent busy, -- Foreign Agent is busy regRequired, -- FA registration is required." ::= { mnRecentAdvReceived 3 } mnAdvMaxRegLifetime OBJECT-TYPE SYNTAX INTEGER (0..65535) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The longest lifetime in seconds that the agent is willing to accept in any registration request." ::= { mnRecentAdvReceived 4 } mnAdvMaxAdvLifetime OBJECT-TYPE SYNTAX INTEGER (0..65535) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum length of time that the Advertisement is considered valid in the absence of further Advertisements." REFERENCE "AdvertisementLifeTime in RFC1256." ::= { mnRecentAdvReceived 5 } mnAdvTimeReceived OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time at which the most recently received advertisement was received." ::= { mnRecentAdvReceived 6 } -- Mobile Node Discovery Group Counter Cong, Hamlen & Perkins Standards Track [Page 16] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 mnSolicitationsSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Solicitation sent by the mobile node." ::= { mnDiscovery 3 } mnAdvertisementsReceived OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of advertisements received by the mobile node." ::= { mnDiscovery 4 } mnAdvsDroppedInvalidExtension OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of advertisements dropped by the mobile node due to both poorly formed extensions and unrecognized extensions with extension number in the range 0-127." ::= { mnDiscovery 5 } mnAdvsIgnoredUnknownExtension OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of unrecognized extensions in the range 128-255 that were ignored by the mobile node." ::= { mnDiscovery 6 } mnMoveFromHAToFA OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of times that the mobile node has decided to move from its home network to a foreign network." ::= { mnDiscovery 7 } mnMoveFromFAToFA OBJECT-TYPE Cong, Hamlen & Perkins Standards Track [Page 17] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of times that the mobile node has decided to move from one foreign network to another foreign network." ::= { mnDiscovery 8 } mnMoveFromFAToHA OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of times that the mobile node has decided to move from a foreign network to its home network." ::= { mnDiscovery 9 } mnGratuitousARPsSend OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Gratuitous ARPs sent by mobile node in order to clear out any stale ARP entries in the ARP caches of nodes on the home network." ::= { mnDiscovery 10 } mnAgentRebootsDectected OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of agent reboots detected by the mobile node through sequence number of the advertisement." ::= { mnDiscovery 11 } -- Mobile Node Registration Group -- Registration table of mobile node mnRegistrationTable OBJECT-TYPE SYNTAX SEQUENCE OF MnRegistrationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing information about the mobile node's attempted registration(s). The mobile node Cong, Hamlen & Perkins Standards Track [Page 18] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 updates this table based upon Registration Requests sent and Registration Replies received in response to these requests. Certain variables within this table are also updated if when Registration Requests are retransmitted." ::= { mnRegistration 1 } mnRegistrationEntry OBJECT-TYPE SYNTAX MnRegistrationEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about one registration attempt." INDEX { mnRegAgentAddress, mnRegCOA} ::= { mnRegistrationTable 1 } MnRegistrationEntry ::= SEQUENCE { mnRegAgentAddress IpAddress, mnRegCOA IpAddress, mnRegFlags RegistrationFlags, mnRegIDLow Integer32, mnRegIDHigh Integer32, mnRegTimeRequested Integer32, mnRegTimeRemaining Gauge32, mnRegTimeSent TimeStamp, mnRegIsAccepted TruthValue, mnCOAIsLocal TruthValue } mnRegAgentAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "IP address of the agent as used in the destination IP address of the Registration Request. The agent may be a home agent or a foreign agent." ::= { mnRegistrationEntry 1 } mnRegCOA OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "Care-of address for the registration." ::= { mnRegistrationEntry 2 } mnRegFlags OBJECT-TYPE Cong, Hamlen & Perkins Standards Track [Page 19] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 SYNTAX RegistrationFlags MAX-ACCESS read-only STATUS current DESCRIPTION "Registration flags sent by the mobile node. It is the second byte in the Mobile IP Registratation Request message." ::= { mnRegistrationEntry 3 } mnRegIDLow OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Low-order 32 bits of the Identification used in that registration by the mobile node." ::= { mnRegistrationEntry 4 } mnRegIDHigh OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "High-order 32 bits of the Identification used in that registration by the mobile node." ::= { mnRegistrationEntry 5 } mnRegTimeRequested OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "If the registration is pending, then this is the lifetime requested by the mobile node (in seconds). If the registration has been accepted, then this is the lifetime actually granted by the home agent in the reply." ::= { mnRegistrationEntry 6 } mnRegTimeRemaining OBJECT-TYPE SYNTAX Gauge32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of seconds remaining until this registration expires. It has the same initial value Cong, Hamlen & Perkins Standards Track [Page 20] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 as mnRegTimeRequested and is only valid if mnRegIsAccepted is TRUE." ::= { mnRegistrationEntry 7 } mnRegTimeSent OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The time when the last (re-)transmission occured." ::= { mnRegistrationEntry 8 } mnRegIsAccepted OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "true(1) if the mobile node has received a Registration Reply indicating that service has been accepted; false(2) otherwise. false(2) implies that the registration is still pending." ::= { mnRegistrationEntry 9 } mnCOAIsLocal OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Whether the COA is local to (dynamically acquired by) the mobile node or not. If it is false(2), the COA is an address of the foreign agent." ::= { mnRegistrationEntry 10 } -- Mobile Node Registration Group Counters mnRegRequestsSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of registration requests sent by the mobile node. This does not include deregistrations (those with Lifetime equal to zero)." ::= { mnRegistration 2 } mnDeRegRequestsSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only Cong, Hamlen & Perkins Standards Track [Page 21] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 STATUS current DESCRIPTION "Total number of deregistration requests sent by the mobile node (those with Lifetime equal to zero)." ::= { mnRegistration 3 } mnRegRepliesRecieved OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of registration replies received by the mobile node in which the Lifetime is greater than zero." ::= { mnRegistration 4 } mnDeRegRepliesRecieved OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of (de)registration replies received by the mobile node in which the Lifetime is equal to zero." ::= { mnRegistration 5 } mnRepliesInvalidHomeAddress OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of replies with invalid home address for the mobile node." ::= { mnRegistration 6 } mnRepliesUnknownHA OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of replies with unknown home agents (not in home agent table)." ::= { mnRegistration 7 } mnRepliesUnknownFA OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current Cong, Hamlen & Perkins Standards Track [Page 22] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 DESCRIPTION "Total number of replies with unknown foreign agents if replies relayed through foreign agent." ::= { mnRegistration 8 } mnRepliesInvalidID OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of replies with invalid Identification fields." ::= { mnRegistration 9 } mnRepliesDroppedInvalidExtension OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Registration Replies dropped by the mobile node due to both poorly formed extensions and unrecognized extensions with extension number in the range 0-127." ::= { mnRegistration 10 } mnRepliesIgnoredUnknownExtension OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Registration Replies that contained one or more unrecognized extensions in the range 128-255 that were ignored by the mobile node." ::= { mnRegistration 11 } mnRepliesHAAuthenticationFailure OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of replies without a valid Home Agent to Mobile Node authenticator." ::= { mnRegistration 12 } mnRepliesFAAuthenticationFailure OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current Cong, Hamlen & Perkins Standards Track [Page 23] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 DESCRIPTION "Total number of replies without a valid Foreign Agent to Mobile Node authenticator." ::= { mnRegistration 13 } mnRegRequestsAccepted OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of registration requests accepted by the mobile node's home agent (Code 0 and Code 1)." ::= { mnRegistration 14 } mnRegRequestsDeniedByHA OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of registration requests denied by mobile node's home agent (Sum of Code 128 through Code 191)." ::= { mnRegistration 15 } mnRegRequestsDeniedByFA OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of registration requests denied by the foreign agent (Sum of Codes 64 through Code 127)." ::= { mnRegistration 16 } mnRegRequestsDeniedByHADueToID OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Registration Request denied by home agent due to identification mismatch." ::= { mnRegistration 17 } mnRegRequestsWithDirectedBroadcast OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Registration Requests sent by mobile Cong, Hamlen & Perkins Standards Track [Page 24] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 node with a directed broadcast address in the home agent field." ::= { mnRegistration 18 } -- MA Advertisement Group -- Mobility agent advertisement configuration table maAdvConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF MaAdvConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing configurable advertisement parameters for all advertisement interfaces in the mobility agent." ::= { maAdvertisement 1 } maAdvConfigEntry OBJECT-TYPE SYNTAX MaAdvConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Advertisement parameters for one advertisement interface." INDEX { maInterfaceAddress } ::= { maAdvConfigTable 1 } MaAdvConfigEntry ::= SEQUENCE { maInterfaceAddress IpAddress, maAdvMaxRegLifetime Integer32, maAdvPrefixLengthInclusion TruthValue, maAdvAddress IpAddress, maAdvMaxInterval Integer32, maAdvMinInterval Integer32, maAdvMaxAdvLifetime Integer32, maAdvResponseSolicitationOnly TruthValue, maAdvStatus RowStatus } maInterfaceAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "IP address for advertisement interface." ::= { maAdvConfigEntry 1 } Cong, Hamlen & Perkins Standards Track [Page 25] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 maAdvMaxRegLifetime OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The longest lifetime in seconds that mobility agent is willing to accept in any Registration Request." ::= { maAdvConfigEntry 2 } maAdvPrefixLengthInclusion OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Whether the advertisement should include the Prefix- Lengths Extension. If it is true, all advertisements sent over this interface should include the Prefix-Lengths Extension." ::= { maAdvConfigEntry 3 } maAdvAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The IP destination address to be used for advertisements sent from the interface. The only permissible values are the all-systems multicast address (224.0.0.1) or the limited-broadcast address (255.255.255.255)." REFERENCE "AdvertisementAddress in RFC1256." ::= { maAdvConfigEntry 4 } maAdvMaxInterval OBJECT-TYPE SYNTAX Integer32 (4..1800) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum time in seconds between successive transmissions of Agent Advertisements from this interface." REFERENCE "MaxAdvertisementInterval in RFC1256." ::= { maAdvConfigEntry 5 } Cong, Hamlen & Perkins Standards Track [Page 26] RFC 2006 Mobile IP MIB Definition using SMIv2 October 1996 maAdvMinInterval OBJECT-TYPE SYNTAX Integer32 (3..1800) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum time in seconds between successive transmissions of Agent Advertisements from this interface." REFERENCE "MinAdvertisementInterval in RFC1256." ::= { maAdvConfigEntry 6 } maAdvMaxAdvLifetime OBJECT-TYPE SYNTAX Integer32 (4..9000) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The time (in seconds) to be placed in the Lifetime field of the RFC 1256-portion of the Agent Advertisements sent over this interface." REFERENCE "AdvertisementLifetime in RFC1256." ::= { maAdvConfigEntry 7 } maAdvResponseSolicitationOnly OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "The flag indicates whether the advertisement from that interface should be sent only in response to an Agent Solicitation message." DEFVAL { false } ::= { maAdvConfigEntry 8 } maAdvStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The row status for the agent advertisement table. If