Network Working Group D. Joyal, Ed. Request for Comments: 4750 Nortel Obsoletes: 1850 P. Galecki, Ed. Category: Standards Track Airvana S. Giacalone, Ed. CSFB Original Authors: R. Coltun Touch Acoustra F. Baker Cisco Systems December 2006 OSPF Version 2 Management Information Base Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The IETF Trust (2006). Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing version 2 of the Open Shortest Path First Routing Protocol. Version 2 of the OSPF protocol is specific to the IPv4 address family. Version 3 of the OSPF protocol is specific to the IPv6 address family. This memo obsoletes RFC 1850; however, it is designed to be backwards compatible. The functional differences between this memo and RFC 1850 are explained in Appendix B. Galecki, et al. Standards Track [Page 1] RFC 4750 OSPFv2 MIB December 2006 Table of Contents 1. Overview ........................................................3 1.1. The Internet-Standard Management Framework .................3 1.2. Conceptual Row Creation ....................................3 1.3. Default Configuration ......................................4 1.4. OSPF Counters ..............................................5 1.5. Multiple OSPF Instances ....................................5 1.6. Conventions ................................................6 2. Structure of This MIB ...........................................6 2.1. The Purposes of the Sections in This MIB ...................6 2.1.1. General Variables ...................................6 2.1.2. Area Data Structure and Area Stub Metric Table ......6 2.1.3. Link State Database and External Link State Database ............................................7 2.1.4. Address Table and Host Tables .......................7 2.1.5. Interface and Interface Metric Tables ...............7 2.1.6. Virtual Interface Table .............................7 2.1.7. Neighbor and Virtual Neighbor Tables ................7 2.1.8. Local Link State Database Table and Virtual Local Link State Database Table .....................7 2.1.9. AS-scope Link State Database Table ..................7 2.1.10. Area LSA Count Table ...............................7 3. OSPF MIB Module .................................................8 4. OSPF Trap Overview .............................................94 4.1. Introduction ..............................................94 4.2. Approach ..................................................95 4.3. Ignoring Initial Activity .................................95 4.4. Throttling Traps ..........................................95 4.5. One Trap Per OSPF Event ...................................96 4.6. Polling Event Counters ....................................96 4.7. Translating Notification Parameters .......................97 4.8. Historical Artifacts ......................................97 5. OSPF Trap Definitions ..........................................98 6. Security Considerations .......................................110 7. IANA Considerations ...........................................111 8. Acknowledgements ..............................................111 9. References ....................................................111 9.1. Normative References .....................................111 9.2. Informative References ...................................111 Appendix A. TOS Support ..........................................113 Appendix B. Changes from RFC 1850 ................................113 B.1. General Group Changes ....................................113 B.2. OSPF NSSA Enhancement Support ............................113 B.3. Opaque LSA Support .......................................114 B.4. Graceful Restart Support .................................116 B.5. OSPF Compliances .........................................116 B.6. OSPF Authentication and Security .........................117 Galecki, et al. Standards Track [Page 2] RFC 4750 OSPFv2 MIB December 2006 B.7. OSPF Trap MIB ............................................117 B.8. Miscellaneous ............................................118 1. Overview 1.1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 1.2. Conceptual Row Creation For the benefit of row-creation in "conceptual" tables, DEFVAL (Default Value) clauses are included in the definitions in section 3, suggesting values that an agent should use for instances of variables that need to be created due to a Set-Request, but that are not specified in the Set-Request. DEFVAL clauses have not been specified for some objects that are read-only, implying that they are zeroed upon row creation. These objects are of the SYNTAX Counter32 or Gauge32. For those objects not having a DEFVAL clause, both management stations and agents should heed the Robustness Principle of the Internet (see [RFC791]): "be liberal in what you accept, conservative in what you send" Therefore, management stations should include as many of these columnar objects as possible (e.g., all read-write objects) in a Set-Request when creating a conceptual row. Agents should accept a Set-Request with as few of these columnar objects as they need (e.g., the minimum contents of a "row-creating" SET consists of those objects for which, as they cannot be intuited, no default is specified). Galecki, et al. Standards Track [Page 3] RFC 4750 OSPFv2 MIB December 2006 1.3. Default Configuration OSPF is a powerful routing protocol, equipped with features to handle virtually any configuration requirement that might reasonably be found within an Autonomous System (AS). With this power comes a fair degree of complexity, which the sheer number of objects in the MIB will attest to. Care has therefore been taken, in constructing this MIB, to define default values for virtually every object, to minimize the amount of parameterization required in the typical case. That default configuration is as follows: Given the following assumptions: - IP has already been configured. - The ifTable has already been configured. - ifSpeed is estimated by the interface drivers. - The OSPF process automatically discovers all IP interfaces and creates corresponding OSPF interfaces. - The OSPF process automatically creates the areas required for the interfaces. The simplest configuration of an OSPF process requires the following: - The OSPF process be enabled. This can be accomplished with a single SET: ospfAdminStat := enabled. The configured system will have the following attributes: - The RouterID will be one of the IP addresses of the device. - The device will be neither an Area Border Router nor an Autonomous System Border Router. - Every IP interface, with or without an address, will be an OSPF interface. - The AreaID of each interface will be 0.0.0.0, the backbone. - Authentication will be disabled. Galecki, et al. Standards Track [Page 4] RFC 4750 OSPFv2 MIB December 2006 - All broadcast and point-to-point interfaces will be operational. Non-broadcast multi-access (NBMA) interfaces require the configuration of at least one neighbor. - Timers on all direct interfaces will be: Hello Interval: 10 seconds Dead Timeout: 40 Seconds Retransmission: 5 Seconds Transit Delay: 1 Second Poll Interval: 120 Seconds - No direct links to hosts will be configured. - No addresses will be summarized. - Metrics, being a measure of bit duration, are unambiguous and intelligent. - No virtual links will be configured. 1.4. OSPF Counters This MIB defines several counters, namely: - ospfOriginateNewLsas, ospfRxNewLsas in the ospfGeneralGroup - ospfSpfRuns, ospfAreaNssaTranslatorEvents in the ospfAreaTable - ospfIfEvents in the ospfIfTable - ospfVirtIfEvents in the ospfVirtIfTable - ospfNbrEvents in the ospfNbrTable - ospfVirtNbrEvents in the ospfVirtNbrTable As a best practice, a management entity, when reading these counters, should use the discontinuity object, ospfDiscontinuityTime, to determine if an event that would invalidate the management entity understanding of the counters has occurred. A restart of the OSPF routing process is a possible example of a discontinuity event. 1.5. Multiple OSPF Instances SNMPv3 supports "Contexts" that can be used to implement MIB views on multiple OSPF instances on the same system. See [RFC3411] or its successors for details. Galecki, et al. Standards Track [Page 5] RFC 4750 OSPFv2 MIB December 2006 1.6. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2. Structure of This MIB This MIB is composed of the following sections: General Variables Area Data Structure Area Stub Metric Table Link State Database (LSDB) Address Range Table Host Table Interface Table Interface Metric Table Virtual Interface Table Neighbor Table Virtual Neighbor Table External Link State Database Aggregate Range Table Local Link State Database AS-scope Link State Database It supports the base OSPFv2 specification [RFC2328] and extensions to OSPFv2 such as [RFC1765], [RFC1793], [RFC2370], [RFC3101] and [RFC3623]. There exists a separate MIB for notifications ("traps"), which is entirely optional. 2.1. The Purposes of the Sections in This MIB 2.1.1. General Variables The general variables describe (as it may seem from the name) variables that are global to the OSPF Process. 2.1.2. Area Data Structure and Area Stub Metric Table The Area Data Structure describes all of the OSPF Areas that the router participates in. The Area Table includes data for Not-So- Stubby-Area (NSSA) translation. The Area Stub Metric Table describes the metrics advertised into a stub area by the default router(s). Galecki, et al. Standards Track [Page 6] RFC 4750 OSPFv2 MIB December 2006 2.1.3. Link State Database and External Link State Database The link state database is provided primarily to provide detailed information for network debugging. 2.1.4. Address Table and Host Tables The Address Range Table and Host Table are provided to view configured Network Summary and host route information. 2.1.5. Interface and Interface Metric Tables The Interface Table and the Interface Metric Table together describe the various IP interfaces to OSPF. The metrics are placed in separate tables in order to simplify dealing with multiple types of service. The Interface table includes link-local (Opaque type-9) link state advertisement (LSA) statistics. 2.1.6. Virtual Interface Table The Virtual Interface Table describes virtual links to the OSPF Process, similarly to the (non-virtual) Interface Tables. This Table includes link-local (Opaque type-9) LSA statistics. 2.1.7. Neighbor and Virtual Neighbor Tables The Neighbor Table and the Virtual Neighbor Table describe the neighbors to the OSPF Process. 2.1.8. Local Link State Database Table and Virtual Local Link State Database Table The Local Link State Database Table and Virtual Local Link State Database Table are identical to the OSPF LSDB Table in format, but contain only link-local (Opaque type-9) link state advertisements for non-virtual and virtual links. 2.1.9. AS-scope Link State Database Table The AS-scope Link State Database Table is identical to the OSPF LSDB Table in format, but contains only AS-scoped link state advertisements. 2.1.10. Area LSA Count Table The table, which maintains number of link state advertisements on the per-area, per-LSA-type basis. Galecki, et al. Standards Track [Page 7] RFC 4750 OSPFv2 MIB December 2006 3. OSPF MIB Module OSPF-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32, Integer32, Unsigned32, IpAddress, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeStamp FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF InterfaceIndexOrZero FROM IF-MIB; ospf MODULE-IDENTITY LAST-UPDATED "200611100000Z" -- November 10, 2006 00:00:00 EST ORGANIZATION "IETF OSPF Working Group" CONTACT-INFO "WG E-Mail: ospf@ietf.org WG Chairs: acee@cisco.com rohit@gmail.com Editors: Dan Joyal Nortel 600 Technology Park Drive Billerica, MA 01821 djoyal@nortel.com Piotr Galecki Airvana 19 Alpha Road Chelmsford, MA 01824 pgalecki@airvana.com Spencer Giacalone CSFB Eleven Madison Ave New York, NY 10010-3629 spencer.giacalone@gmail.com" DESCRIPTION "The MIB module to describe the OSPF Version 2 Protocol. Note that some objects in this MIB module may pose a significant security risk. Refer to the Security Considerations section in RFC 4750 for more information. Galecki, et al. Standards Track [Page 8] RFC 4750 OSPFv2 MIB December 2006 Copyright (C) The IETF Trust (2006). This version of this MIB module is part of RFC 4750; see the RFC itself for full legal notices." REVISION "200611100000Z" -- November 10, 2006 09:00:00 EST DESCRIPTION "Updated for latest changes to OSPF Version 2: - updated the General Group with the new ospfRFC1583Compatibility, ospfReferenceBandwidth and ospfDiscontinuityTime objects - added graceful-restart-related objects - added stub-router-related objects - updated the Area Table with NSSA-related objects - added ospfAreaAggregateExtRouteTag object - added Opaque LSA-related objects - updates to the Compliances and Security sections - added area LSA counter table - added section describing translation of notification parameters between SNMP versions - added ospfComplianceObsolete to contain obsolete object groups - deprecated ospfExtLsdbTable See Appendix B of RFC 4750 for more details. This version published as part of RFC 4750" REVISION "199501201225Z" -- Fri Jan 20 12:25:50 PST 1995 DESCRIPTION "The initial SMIv2 revision of this MIB module, published in RFC 1850." ::= { mib-2 14 } AreaID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An OSPF Area Identifier. Note that the Area ID, in OSPF, has the same format as an IP address, but has the function of defining a summarization point for link state advertisements." SYNTAX IpAddress RouterID ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A OSPF Router Identifier. Note that the Router ID, in OSPF, has the same format as an IP address, but identifies the router independent Galecki, et al. Standards Track [Page 9] RFC 4750 OSPFv2 MIB December 2006 of its IP address." SYNTAX IpAddress Metric ::= TEXTUAL-CONVENTION DISPLAY-HINT "d-0" STATUS current DESCRIPTION "The OSPF internal metric. Note that the OSPF metric is defined as an unsigned value in the range." SYNTAX Integer32 (0..'FFFF'h) BigMetric ::= TEXTUAL-CONVENTION DISPLAY-HINT "d-0" STATUS current DESCRIPTION "The OSPF external metric." SYNTAX Integer32 (0..'FFFFFF'h) Status ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An indication of the operability of an OSPF function or feature. For example, the status of an interface: 'enabled' indicates that it is willing to communicate with other OSPF routers, and 'disabled' indicates that it is not." SYNTAX INTEGER { enabled (1), disabled (2) } PositiveInteger ::= TEXTUAL-CONVENTION DISPLAY-HINT "d-0" STATUS current DESCRIPTION "A positive integer. Values in excess are precluded as unnecessary and prone to interoperability issues." SYNTAX Integer32 (0..'7FFFFFFF'h) HelloRange ::= TEXTUAL-CONVENTION DISPLAY-HINT "d-0" STATUS current DESCRIPTION "The range of intervals in seconds on which Hello messages are exchanged." SYNTAX Integer32 (1..'FFFF'h) UpToMaxAge ::= TEXTUAL-CONVENTION DISPLAY-HINT "d-0" STATUS current Galecki, et al. Standards Track [Page 10] RFC 4750 OSPFv2 MIB December 2006 DESCRIPTION "The values in seconds that one might find or configure for variables bounded by the maximum age of an LSA." SYNTAX Integer32 (0..3600) DesignatedRouterPriority ::= TEXTUAL-CONVENTION DISPLAY-HINT "d-0" STATUS current DESCRIPTION "The range of values defined for the priority of a system for becoming the designated router." SYNTAX Integer32 (0..'FF'h) TOSType ::= TEXTUAL-CONVENTION DISPLAY-HINT "d-0" STATUS current DESCRIPTION "Type of Service (TOS) is defined as a mapping to the IP Type of Service Flags as defined in the IP Forwarding Table MIB +-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+ IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 0 0 1 0 ==> 4 0 0 1 1 ==> 6 0 1 0 0 ==> 8 0 1 0 1 ==> 10 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1 1 1 0 ==> 28 1 1 1 1 ==> 30 The remaining values are left for future definition." SYNTAX Integer32 (0..30) OspfAuthenticationType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The authentication type." SYNTAX INTEGER { Galecki, et al. Standards Track [Page 11] RFC 4750 OSPFv2 MIB December 2006 none (0), simplePassword (1), md5 (2) -- reserved for specification by IANA (> 2) } -- OSPF General Variables -- Note: These parameters apply globally to the Router's -- OSPF Process. ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 } ospfRouterId OBJECT-TYPE SYNTAX RouterID MAX-ACCESS read-write STATUS current DESCRIPTION "A 32-bit integer uniquely identifying the router in the Autonomous System. By convention, to ensure uniqueness, this should default to the value of one of the router's IP interface addresses. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." REFERENCE "OSPF Version 2, C.1 Global parameters" ::= { ospfGeneralGroup 1 } ospfAdminStat OBJECT-TYPE SYNTAX Status MAX-ACCESS read-write STATUS current DESCRIPTION "The administrative status of OSPF in the router. The value 'enabled' denotes that the OSPF Process is active on at least one interface; 'disabled' disables it on all interfaces. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." ::= { ospfGeneralGroup 2 } ospfVersionNumber OBJECT-TYPE SYNTAX INTEGER { version2 (2) } MAX-ACCESS read-only STATUS current Galecki, et al. Standards Track [Page 12] RFC 4750 OSPFv2 MIB December 2006 DESCRIPTION "The current version number of the OSPF protocol is 2." REFERENCE "OSPF Version 2, Title" ::= { ospfGeneralGroup 3 } ospfAreaBdrRtrStatus OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "A flag to note whether this router is an Area Border Router." REFERENCE "OSPF Version 2, Section 3 Splitting the AS into Areas" ::= { ospfGeneralGroup 4 } ospfASBdrRtrStatus OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "A flag to note whether this router is configured as an Autonomous System Border Router. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." REFERENCE "OSPF Version 2, Section 3.3 Classification of routers" ::= { ospfGeneralGroup 5 } ospfExternLsaCount OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of external (LS type-5) link state advertisements in the link state database." REFERENCE "OSPF Version 2, Appendix A.4.5 AS external link advertisements" ::= { ospfGeneralGroup 6 } ospfExternLsaCksumSum OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only Galecki, et al. Standards Track [Page 13] RFC 4750 OSPFv2 MIB December 2006 STATUS current DESCRIPTION "The 32-bit sum of the LS checksums of the external link state advertisements contained in the link state database. This sum can be used to determine if there has been a change in a router's link state database and to compare the link state database of two routers. The value should be treated as unsigned when comparing two sums of checksums." ::= { ospfGeneralGroup 7 } ospfTOSSupport OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "The router's support for type-of-service routing. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." REFERENCE "OSPF Version 2, Appendix F.1.2 Optional TOS support" ::= { ospfGeneralGroup 8 } ospfOriginateNewLsas OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of new link state advertisements that have been originated. This number is incremented each time the router originates a new LSA. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime." ::= { ospfGeneralGroup 9 } ospfRxNewLsas OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION Galecki, et al. Standards Track [Page 14] RFC 4750 OSPFv2 MIB December 2006 "The number of link state advertisements received that are determined to be new instantiations. This number does not include newer instantiations of self-originated link state advertisements. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime." ::= { ospfGeneralGroup 10 } ospfExtLsdbLimit OBJECT-TYPE SYNTAX Integer32 (-1..'7FFFFFFF'h) MAX-ACCESS read-write STATUS current DESCRIPTION "The maximum number of non-default AS-external LSAs entries that can be stored in the link state database. If the value is -1, then there is no limit. When the number of non-default AS-external LSAs in a router's link state database reaches ospfExtLsdbLimit, the router enters overflow state. The router never holds more than ospfExtLsdbLimit non-default AS-external LSAs in its database. OspfExtLsdbLimit MUST be set identically in all routers attached to the OSPF backbone and/or any regular OSPF area (i.e., OSPF stub areas and NSSAs are excluded). This object is persistent and when written the entity SHOULD save the change to non-volatile storage." DEFVAL { -1 } ::= { ospfGeneralGroup 11 } ospfMulticastExtensions OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "A bit mask indicating whether the router is forwarding IP multicast (Class D) datagrams based on the algorithms defined in the multicast extensions to OSPF. Bit 0, if set, indicates that the router can Galecki, et al. Standards Track [Page 15] RFC 4750 OSPFv2 MIB December 2006 forward IP multicast datagrams in the router's directly attached areas (called intra-area multicast routing). Bit 1, if set, indicates that the router can forward IP multicast datagrams between OSPF areas (called inter-area multicast routing). Bit 2, if set, indicates that the router can forward IP multicast datagrams between Autonomous Systems (called inter-AS multicast routing). Only certain combinations of bit settings are allowed, namely: 0 (no multicast forwarding is enabled), 1 (intra-area multicasting only), 3 (intra-area and inter-area multicasting), 5 (intra-area and inter-AS multicasting), and 7 (multicasting everywhere). By default, no multicast forwarding is enabled. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." DEFVAL { 0 } ::= { ospfGeneralGroup 12 } ospfExitOverflowInterval OBJECT-TYPE SYNTAX PositiveInteger MAX-ACCESS read-write STATUS current DESCRIPTION "The number of seconds that, after entering OverflowState, a router will attempt to leave OverflowState. This allows the router to again originate non-default AS-external LSAs. When set to 0, the router will not leave overflow state until restarted. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." DEFVAL { 0 } ::= { ospfGeneralGroup 13 } ospfDemandExtensions OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write Galecki, et al. Standards Track [Page 16] RFC 4750 OSPFv2 MIB December 2006 STATUS current DESCRIPTION "The router's support for demand routing. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." REFERENCE "Extending OSPF to Support Demand Circuits" ::= { ospfGeneralGroup 14 } ospfRFC1583Compatibility OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates metrics used to choose among multiple AS-external LSAs. When RFC1583Compatibility is set to enabled, only cost will be used when choosing among multiple AS-external LSAs advertising the same destination. When RFC1583Compatibility is set to disabled, preference will be driven first by type of path using cost only to break ties. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." REFERENCE "OSPF Version 2, Section 16.4.1 External path preferences" ::= { ospfGeneralGroup 15 } ospfOpaqueLsaSupport OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The router's support for Opaque LSA types." REFERENCE "The OSPF Opaque LSA Option" ::= { ospfGeneralGroup 16 } ospfReferenceBandwidth OBJECT-TYPE SYNTAX Unsigned32 UNITS "kilobits per second" MAX-ACCESS read-write STATUS current DESCRIPTION "Reference bandwidth in kilobits/second for Galecki, et al. Standards Track [Page 17] RFC 4750 OSPFv2 MIB December 2006 calculating default interface metrics. The default value is 100,000 KBPS (100 MBPS). This object is persistent and when written the entity SHOULD save the change to non-volatile storage." ::= { ospfGeneralGroup 17 } ospfRestartSupport OBJECT-TYPE SYNTAX INTEGER { none (1), plannedOnly (2), plannedAndUnplanned (3) } MAX-ACCESS read-write STATUS current DESCRIPTION "The router's support for OSPF graceful restart. Options include: no restart support, only planned restarts, or both planned and unplanned restarts. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." ::= { ospfGeneralGroup 18 } ospfRestartInterval OBJECT-TYPE SYNTAX Integer32 (1..1800) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Configured OSPF graceful restart timeout interval. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." ::= { ospfGeneralGroup 19 } ospfRestartStrictLsaChecking OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates if strict LSA checking is enabled for graceful restart. This object is persistent and when written the entity SHOULD save the change to non-volatile Galecki, et al. Standards Track [Page 18] RFC 4750 OSPFv2 MIB December 2006 storage." ::= { ospfGeneralGroup 20 } ospfRestartStatus OBJECT-TYPE SYNTAX INTEGER { notRestarting (1), plannedRestart (2), unplannedRestart (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Current status of OSPF graceful restart." ::= { ospfGeneralGroup 21 } ospfRestartAge OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Remaining time in current OSPF graceful restart interval." ::= { ospfGeneralGroup 22 } ospfRestartExitReason OBJECT-TYPE SYNTAX INTEGER { none (1), -- none attempted inProgress (2), -- restart in -- progress completed (3), -- successfully -- completed timedOut (4), -- timed out topologyChanged (5) -- aborted due to -- topology change. } MAX-ACCESS read-only STATUS current DESCRIPTION "Describes the outcome of the last attempt at a graceful restart. If the value is 'none', no restart has yet been attempted. If the value is 'inProgress', a restart attempt is currently underway." ::= { ospfGeneralGroup 23 } ospfAsLsaCount OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current Galecki, et al. Standards Track [Page 19] RFC 4750 OSPFv2 MIB December 2006 DESCRIPTION "The number of AS-scope link state advertisements in the AS-scope link state database." ::= { ospfGeneralGroup 24 } ospfAsLsaCksumSum OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The 32-bit unsigned sum of the LS checksums of the AS link state advertisements contained in the AS-scope link state database. This sum can be used to determine if there has been a change in a router's AS-scope link state database, and to compare the AS-scope link state database of two routers." ::= { ospfGeneralGroup 25 } ospfStubRouterSupport OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The router's support for stub router functionality." REFERENCE "OSPF Stub Router Advertisement" ::= { ospfGeneralGroup 26 } ospfStubRouterAdvertisement OBJECT-TYPE SYNTAX INTEGER { doNotAdvertise (1), advertise(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls the advertisement of stub router LSAs by the router. The value doNotAdvertise will result in the advertisement of a standard router LSA and is the default value. This object is persistent and when written the entity SHOULD save the change to non-volatile storage." ::= { ospfGeneralGroup 27 } ospfDiscontinuityTime OBJECT-TYPE SYNTAX TimeStamp Galecki, et al. Standards Track [Page 20] RFC 4750 OSPFv2 MIB December 2006 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime on the most recent occasion at which any one of this MIB's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value." ::= { ospfGeneralGroup 28 } -- OSPF Area Table -- The OSPF Area Table contains information -- regarding the various areas. ospfAreaTable OBJECT-TYPE SYNTAX SEQUENCE OF OspfAreaEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the configured parameters and cumulative statistics of the router's attached areas. The interfaces and virtual links are configured as part of these areas. Area 0.0.0.0, by definition, is the backbone area." REFERENCE "OSPF Version 2, Section 6 The Area Data Structure" ::= { ospf 2 } ospfAreaEntry OBJECT-TYPE SYNTAX OspfAreaEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information describing the configured parameters and cumulative statistics of one of the router's attached areas. The interfaces and virtual links are configured as part of these areas. Area 0.0.0.0, by definition, is the backbone area. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage." INDEX { ospfAreaId } ::= { ospfAreaTable 1 } Galecki, et al. Standards Track [Page 21] RFC 4750 OSPFv2 MIB December 2006 OspfAreaEntry ::= SEQUENCE { ospfAreaId AreaID, ospfAuthType OspfAuthenticationType, ospfImportAsExtern INTEGER, ospfSpfRuns Counter32, ospfAreaBdrRtrCount Gauge32, ospfAsBdrRtrCount Gauge32, ospfAreaLsaCount Gauge32, ospfAreaLsaCksumSum Integer32, ospfAreaSummary INTEGER, ospfAreaStatus RowStatus, ospfAreaNssaTranslatorRole INTEGER, ospfAreaNssaTranslatorState INTEGER, ospfAreaNssaTranslatorStabilityInterval PositiveInteger, ospfAreaNssaTranslatorEvents Counter32 } ospfAreaId OBJECT-TYPE SYNTAX AreaID MAX-ACCESS read-only -- read-only since originally -- an SMIv1 index STATUS current DESCRIPTION "A 32-bit integer uniquely identifying an area. Area ID 0.0.0.0 is used for the OSPF backbone." REFERENCE "OSPF Version 2, Appendix C.2 Area parameters" ::= { ospfAreaEntry 1 } ospfAuthType OBJECT-TYPE SYNTAX OspfAuthenticationType MAX-ACCESS read-create STATUS obsolete Galecki, et al. Standards Track [Page 22] RFC 4750 OSPFv2 MIB December 2006 DESCRIPTION "The authentication type specified for an area." REFERENCE "OSPF Version 2, Appendix D Authentication" DEFVAL { none } -- no authentication, by default ::= { ospfAreaEntry 2 } ospfImportAsExtern OBJECT-TYPE SYNTAX INTEGER { importExternal (1), importNoExternal (2), importNssa (3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates if an area is a stub area, NSSA, or standard area. Type-5 AS-external LSAs and type-11 Opaque LSAs are not imported into stub areas or NSSAs. NSSAs import AS-external data as type-7 LSAs" REFERENCE "OSPF Version 2, Appendix C.2 Area parameters" DEFVAL { importExternal } ::= { ospfAreaEntry 3 } ospfSpfRuns OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times that the intra-area route table has been calculated using this area's link state database. This is typically done using Dijkstra's algorithm. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime." ::= { ospfAreaEntry 4 } ospfAreaBdrRtrCount OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of Area Border Routers reachable within this area. This is initially zero and is calculated in each Shortest Path First (SPF) pass." Galecki, et al. Standards Track [Page 23] RFC 4750 OSPFv2 MIB December 2006 ::= { ospfAreaEntry 5 } ospfAsBdrRtrCount OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of Autonomous System Border Routers reachable within this area. This is initially zero and is calculated in each SPF pass." ::= { ospfAreaEntry 6 } ospfAreaLsaCount OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of link state advertisements in this area's link state database, excluding AS-external LSAs." ::= { ospfAreaEntry 7 } ospfAreaLsaCksumSum OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The 32-bit sum of the link state advertisements' LS checksums contained in this area's link state database. This sum excludes external (LS type-5) link state advertisements. The sum can be used to determine if there has been a change in a router's link state database, and to compare the link state database of two routers. The value should be treated as unsigned when comparing two sums of checksums." DEFVAL { 0 } ::= { ospfAreaEntry 8 } ospfAreaSummary OBJECT-TYPE SYNTAX INTEGER { noAreaSummary (1), sendAreaSummary (2) } MAX-ACCESS read-create STATUS current DESCRIPTION Galecki, et al. Standards Track [Page 24] RFC 4750 OSPFv2 MIB December 2006 "The variable ospfAreaSummary controls the import of summary LSAs into stub and NSSA areas. It has no effect on other areas. If it is noAreaSummary, the router will not originate summary LSAs into the stub or NSSA area. It will rely entirely on its default route. If it is sendAreaSummary, the router will both summarize and propagate summary LSAs." DEFVAL { noAreaSummary } ::= { ospfAreaEntry 9 } ospfAreaStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified." ::= { ospfAreaEntry 10 } ospfAreaNssaTranslatorRole OBJECT-TYPE SYNTAX INTEGER { always (1), candidate (2) } MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates an NSSA border router's ability to perform NSSA translation of type-7 LSAs into type-5 LSAs." DEFVAL { candidate } ::= { ospfAreaEntry 11 } ospfAreaNssaTranslatorState OBJECT-TYPE SYNTAX INTEGER { enabled (1), elected (2), disabled (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates if and how an NSSA border router is performing NSSA translation of type-7 LSAs into type-5 Galecki, et al. Standards Track [Page 25] RFC 4750 OSPFv2 MIB December 2006 LSAs. When this object is set to enabled, the NSSA Border router's OspfAreaNssaExtTranslatorRole has been set to always. When this object is set to elected, a candidate NSSA Border router is Translating type-7 LSAs into type-5. When this object is set to disabled, a candidate NSSA border router is NOT translating type-7 LSAs into type-5." ::= { ospfAreaEntry 12 } ospfAreaNssaTranslatorStabilityInterval OBJECT-TYPE SYNTAX PositiveInteger UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The number of seconds after an elected translator determines its services are no longer required, that it should continue to perform its translation duties." DEFVAL { 40 } ::= { ospfAreaEntry 13 } ospfAreaNssaTranslatorEvents OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of translator state changes that have occurred since the last boot-up. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime." ::= { ospfAreaEntry 14 } -- OSPF Area Default Metric Table ospfStubAreaTable OBJECT-TYPE SYNTAX SEQUENCE OF OspfStubAreaEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The set of metrics that will be advertised by a default Area Border Router into a stub area." REFERENCE "OSPF Version 2, Appendix C.2, Area Parameters" ::= { ospf 3 } ospfStubAreaEntry OBJECT-TYPE SYNTAX OspfStubAreaEntry Galecki, et al. Standards Track [Page 26] RFC 4750 OSPFv2 MIB December 2006 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The metric for a given Type of Service that will be advertised by a default Area Border Router into a stub area. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage." REFERENCE "OSPF Version 2, Appendix C.2, Area Parameters" INDEX { ospfStubAreaId, ospfStubTOS } ::= { ospfStubAreaTable 1 } OspfStubAreaEntry ::= SEQUENCE { ospfStubAreaId AreaID, ospfStubTOS TOSType, ospfStubMetric BigMetric, ospfStubStatus RowStatus, ospfStubMetricType INTEGER } ospfStubAreaId OBJECT-TYPE SYNTAX AreaID MAX-ACCESS read-only -- read-only since originally an -- SMIv1 index STATUS current DESCRIPTION "The 32-bit identifier for the stub area. On creation, this can be derived from the instance." ::= { ospfStubAreaEntry 1 } ospfStubTOS OBJECT-TYPE SYNTAX TOSType MAX-ACCESS read-only -- read-only since originally an -- SMIv1 index STATUS current DESCRIPTION "The Type of Service associated with the metric. On creation, this can be derived from Galecki, et al. Standards Track [Page 27] RFC 4750 OSPFv2 MIB December 2006 the instance." ::= { ospfStubAreaEntry 2 } ospfStubMetric OBJECT-TYPE SYNTAX BigMetric MAX-ACCESS read-create STATUS current DESCRIPTION "The metric value applied at the indicated Type of Service. By default, this equals the least metric at the Type of Service among the interfaces to other areas." ::= { ospfStubAreaEntry 3 } ospfStubStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified." ::= { ospfStubAreaEntry 4 } ospfStubMetricType OBJECT-TYPE SYNTAX INTEGER { ospfMetric (1), -- OSPF Metric comparableCost (2), -- external type 1 nonComparable (3) -- external type 2 } MAX-ACCESS read-create STATUS current DESCRIPTION "This variable displays the type of metric advertised as a default route." DEFVAL { ospfMetric } ::= { ospfStubAreaEntry 5 } -- OSPF Link State Database ospfLsdbTable OBJECT-TYPE SYNTAX SEQUENCE OF OspfLsdbEntry MAX-ACCESS not-accessible STATUS current Galecki, et al. Standards Track [Page 28] RFC 4750 OSPFv2 MIB December 2006 DESCRIPTION "The OSPF Process's link state database (LSDB). The LSDB contains the link state advertisements from throughout the areas that the device is attached to." REFERENCE "OSPF Version 2, Section 12 Link State Advertisements" ::= { ospf 4 } ospfLsdbEntry OBJECT-TYPE SYNTAX OspfLsdbEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A single link state advertisement." INDEX { ospfLsdbAreaId, ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId } ::= { ospfLsdbTable 1 } OspfLsdbEntry ::= SEQUENCE { ospfLsdbAreaId AreaID, ospfLsdbType INTEGER, ospfLsdbLsid IpAddress, ospfLsdbRouterId RouterID, ospfLsdbSequence Integer32, ospfLsdbAge Integer32, ospfLsdbChecksum Integer32, ospfLsdbAdvertisement OCTET STRING } ospfLsdbAreaId OBJECT-TYPE SYNTAX AreaID MAX-ACCESS read-only -- read-only since originally an -- SMIv1 index STATUS current DESCRIPTION "The 32-bit identifier of the area from which the LSA was received." REFERENCE "OSPF Version 2, Appendix C.2 Area parameters" Galecki, et al. Standards Track [Page 29] RFC 4750 OSPFv2 MIB December 2006 ::= { ospfLsdbEntry 1 } ospfLsdbType OBJECT-TYPE SYNTAX INTEGER { routerLink (1), networkLink (2), summaryLink (3), asSummaryLink (4), asExternalLink (5), -- but see ospfAsLsdbTable multicastLink (6), nssaExternalLink (7), areaOpaqueLink (10) } MAX-ACCESS read-only -- read-only since originally an -- SMIv1 index STATUS current DESCRIPTION "The type of the link state advertisement. Each link state type has a separate advertisement format. Note: External link state advertisements are permitted for backward compatibility, but should be displayed in the ospfAsLsdbTable rather than here." REFERENCE "OSPF Version 2, Appendix A.4.1 The Link State Advertisement header" ::= { ospfLsdbEntry 2 } ospfLsdbLsid OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only -- read-only since originally an -- SMIv1 index STATUS current DESCRIPTION "The Link State ID is an LS Type Specific field containing either a Router ID or an IP address; it identifies the piece of the routing domain that is being described by the advertisement." REFERENCE "OSPF Version 2, Section 12.1.4 Link State ID" ::= { ospfLsdbEntry 3 } ospfLsdbRouterId OBJECT-TYPE SYNTAX RouterID MAX-ACCESS read-only -- read-only since originally an -- SMIv1 index STATUS current Galecki, et al. Standards Track [Page 30] RFC 4750 OSPFv2 MIB December 2006 DESCRIPTION "The 32-bit number that uniquely identifies the originating router in the Autonomous System." REFERENCE "OSPF Version 2, Appendix C.1 Global parameters" ::= { ospfLsdbEntry 4 } ospfLsdbSequence OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The sequence number field is a signed 32-bit integer. It starts with the value '80000001'h, or -'7FFFFFFF'h, and increments until '7FFFFFFF'h. Thus, a typical sequence number will be very negative. It is used to detect old and duplicate Link State Advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement." REFERENCE "OSPF Version 2, Section 12.1.6 LS sequence number" ::= { ospfLsdbEntry 5 } ospfLsdbAge OBJECT-TYPE SYNTAX Integer32 -- Should be 0..MaxAge, except when -- doNotAge bit is set UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This field is the age of the link state advertisement in seconds." REFERENCE "OSPF Version 2, Section 12.1.1 LS age" ::= { ospfLsdbEntry 6 } ospfLsdbChecksum OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless Galecki, et al. Standards Track [Page 31] RFC 4750 OSPFv2 MIB December 2006 datagrams; it is commonly referred to as the Fletcher checksum." REFERENCE "OSPF Version 2, Section 12.1.7 LS checksum" ::= { ospfLsdbEntry 7 } ospfLsdbAdvertisement OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..65535)) MAX-ACCESS read-only STATUS current DESCRIPTION "The entire link state advertisement, including its header. Note that for variable length LSAs, SNMP agents may not be able to return the largest string size." REFERENCE "OSPF Version 2, Section 12 Link State Advertisements" ::= { ospfLsdbEntry 8 } -- Address Range Table ospfAreaRangeTable OBJECT-TYPE SYNTAX SEQUENCE OF OspfAreaRangeEntry MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION "The Address Range Table acts as an adjunct to the Area Table. It describes those Address Range Summaries that are configured to be propagated from an Area to reduce the amount of information about it that is known beyond its borders. It contains a set of IP address ranges specified by an IP address/IP network mask pair. For example, class B address range of X.X.X.X with a network mask of 255.255.0.0 includes all IP addresses from X.X.0.0 to X.X.255.255. Note that this table is obsoleted and is replaced by the Area Aggregate Table." REFERENCE "OSPF Version 2, Appendix C.2 Area parameters" ::= { ospf 5 } ospfAreaRangeEntry OBJECT-TYPE SYNTAX OspfAreaRangeEntry MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION Galecki, et al. Standards Track [Page 32] RFC 4750 OSPFv2 MIB December 2006 "A single area address range. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage." REFERENCE "OSPF Version 2, Appendix C.2 Area parameters" INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet } ::= { ospfAreaRangeTable 1 } OspfAreaRangeEntry ::= SEQUENCE { ospfAreaRangeAreaId AreaID, ospfAreaRangeNet IpAddress, ospfAreaRangeMask IpAddress, ospfAreaRangeStatus RowStatus, ospfAreaRangeEffect INTEGER } ospfAreaRangeAreaId OBJECT-TYPE SYNTAX AreaID MAX-ACCESS read-only -- read-only since originally an -- SMIv1 index STATUS obsolete DESCRIPTION "The area that the address range is to be found within." REFERENCE "OSPF Version 2, Appendix C.2 Area parameters" ::= { ospfAreaRangeEntry 1 } ospfAreaRangeNet OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only -- read-only since originally an -- SMIv1 index STATUS obsolete DESCRIPTION "The IP address of the net or subnet indicated by the range." REFERENCE "OSPF Version 2, Appendix C.2 Area parameters" ::= { ospfAreaRangeEntry 2 } Galecki, et al. Standards Track [Page 33] RFC 4750 OSPFv2 MIB December 2006 ospfAreaRangeMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS obsolete DESCRIPTION "The subnet mask that pertains to the net or subnet." REFERENCE "OSPF Version 2, Appendix C.2 Area parameters" ::= { ospfAreaRangeEntry 3 } ospfAreaRangeStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS obsolete DESCRIPTION "This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified." ::= { ospfAreaRangeEntry 4 } ospfAreaRangeEffect OBJECT-TYPE SYNTAX INTEGER { advertiseMatching (1), doNotAdvertiseMatching (2) } MAX-ACCESS read-create STATUS obsolete DESCRIPTION "Subnets subsumed by ranges either trigger the advertisement of the indicated summary (advertiseMatching) or result in the subnet's not being advertised at all outside the area." DEFVAL { advertiseMatching } ::= { ospfAreaRangeEntry 5 } -- OSPF Host Table ospfHostTable OBJECT-TYPE SYNTAX SEQUENCE OF OspfHostEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Host/Metric Table indicates what hosts are directly Galecki, et al. Standards Track [Page 34] RFC 4750 OSPFv2 MIB December 2006 attached to the router, what metrics and types of service should be advertised for them, and what areas they are found within." REFERENCE "OSPF Version 2, Appendix C.7 Host route parameters" ::= { ospf 6 } ospfHostEntry OBJECT-TYPE SYNTAX OspfHostEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A metric to be advertised, for a given type of service, when a given host is reachable. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage." INDEX { ospfHostIpAddress, ospfHostTOS } ::= { ospfHostTable 1 } OspfHostEntry ::= SEQUENCE { ospfHostIpAddress IpAddress, ospfHostTOS TOSType, ospfHostMetric