Internet Draft OSPF MIB November 1992
OSPF Version 2 Management Information Base
Tue Nov 3 11:27:41 PST 1992
Fred Baker
Advanced Computer Communications
315 Bollay Drive
Santa Barbara, California 93117
fbaker@acc.com
Rob Coltun
Consultant
(301) 340-9416
rcoltun@ni.umd.edu
1. Status of this Memo
This document is an Internet Draft. Internet Drafts are
working documents of the Internet Engineering Task Force
(IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet
Drafts.
Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or obsoleted
by other documents at any time. It is not appropriate to use
Internet Drafts as reference material or to cite them other
than as a "working draft" or "work in progress."
Please check the I-D abstract listing contained in each
Internet Draft directory to learn the current status of this
or any other Internet Draft.
Baker and Coltun Expires May 31 1993 [Page 1]
Internet Draft OSPF MIB November 1992
2. 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 the Open Shortest Path First Routing Protocol.
This memo does not, in its draft form, specify a standard for
the Internet community.
Baker and Coltun Expires May 31 1993 [Page 2]
Internet Draft OSPF MIB November 1992
3. The Network Management Framework
The Internet-standard Network Management Framework consists of
three components. They are:
RFC 1155 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management.
RFC 1212 defines a more concise description mechanism, which
is wholly consistent with the SMI.
RFC 1156 which defines MIB-I, the core set of managed objects
for the Internet suite of protocols. RFC 1213 defines MIB-II,
an evolution of MIB-I based on implementation experience and
new operational requirements.
RFC 1157 which defines the SNMP, the protocol used for network
access to managed objects.
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
Baker and Coltun Expires May 31 1993 [Page 3]
Internet Draft OSPF MIB November 1992
4. Objects
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) [7] defined in the SMI. In particular, each
object has a name, a syntax, and an encoding. The name is an
object identifier, an administratively assigned name, which
specifies an object type. 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 OBJECT DESCRIPTOR, to also
refer to the object type.
The syntax of an object type defines the abstract data
structure corresponding to that object type. The ASN.1
language is used for this purpose. However, the SMI [3]
purposely restricts the ASN.1 constructs which may be used.
These restrictions are explicitly made for simplicity.
The encoding of an object type is simply how that object type
is represented using the object type's syntax. Implicitly
tied to the notion of an object type's syntax and encoding is
how the object type is represented when being transmitted on
the network.
The SMI specifies the use of the basic encoding rules of ASN.1
[8], subject to the additional requirements imposed by the
SNMP.
4.1. Format of Definitions
Section 6 contains contains the specification of all object
types contained in this MIB module. The object types are
defined using the conventions defined in the SMI, as amended
by the extensions specified in RFC1212 [13].
4.2. Changes from RFC 1253
The changes from RFC 1253 are the following:
(1) The textual convention PositiveInteger was changed from
1..'FFFFFFFF'h to 1..'7FFFFFFF'h at the request of
Marshall Rose.
Baker and Coltun Expires May 31 1993 [Page 4]
Internet Draft OSPF MIB November 1992
(2) The textual convention TOSType was changed to reflect the
TOS values defined in the Router Requirements Draft, and
in accordance with the IP Forwarding Table MIB's values.
(3) The names of some objects were changed, conforming to the
convention that an acronym (for example, LSA) is a single
word ("Lsa") in most SNMP names.
(4) textual changes were made to make the MIB readable by
Dave Perkins' SMIC MIB Compiler in addition to Mosy.
This involved changing the case of some characters in
certain names and removing the DEFVAL clauses for
Counters. (This would appear to violate RFC 1212, which
explicitly states that DEFVALs are for the purpose of
initializing read-only objects???)
(5) The variables ospfAreaStatus and ospfIfStatus were added,
having been overlooked in the original MIB.
(6) The range of the variable ospfLsdbType was extended to
include multicastLink (Multicast LSA) and
nssaExternalLink (NSSA LSA).
(7) The variable ospfIfMetricMetric was renamed
ospfIfMetricValue, and the following text was removed
from its description:
"The value FFFF is distinguished to mean 'no route via
this TOS'."
(8) The range of the variable ospfNBMANbrStatus was extended
from by this means, dynamically learned and configured
neighbors can be distinguished.
(9) The DESCRIPTION of the variable ospfNbrIpAddr was changed
from
"The IP address of this neighbor."
to
"The IP address this neighbor is using in its IP Source
Address. Note that, on addressless links, this will not
be 0.0.0.0, but the address of another of the neighbor's
interfaces."
Baker and Coltun Expires May 31 1993 [Page 5]
Internet Draft OSPF MIB November 1992
This is by way of clarification and does not change the
specification.
(10) The OSPF External Link State Database was added. The
OSPF Link State Database used to display all LSAs stored;
in this MIB, it displays all but the AS External LSAs.
This is because there are usually a large number of
External LSAs, and they are relicated in all non-Stub
Areas.
(11) The variable ospfAreaSummary was added to control the
import of summary LSAs into stub areas. If it is
noAreaSummary (default) the router will neither originate
nor propagate summary LSAs into the stub area. It will
rely entirely on its default route. If it is
sendAreaSummary, the router will both summarize and
propagate summary LSAs.
(12) The general variable ospfExtLsdbLimit was introduced to
help handle LSDB overflow.
(13) The use of the IP Forwarding Table is defined.
(14) The range of the variable ospfAreaRangeStatus was
extended to include the concepts advertiseMatching,
invalid (delete), and doNotAdvertiseMatching. This
permits the network manager to hide a subnet within an
area.
(15) Normally, the border router of a stub area advertises a
default route as an OSPF network summary. An NSSA border
router will generate a type-5 LSA indicating a default
route, and import it into the NSSA. ospfStubMetricType
(ospf internal, type 1 external, or type 2 external)
indicates the type of the default metric advertised.
(16) ospfMulticastForwarding is added to the OSPF General
Group. This indicates the router's ability to forward IP
multicast (class D) datagrams.
(17) ospfIfMulticastForwarding in the Interface Group. It
indicates whether, and if so, how, multicasts should be
forwarded on the interface.
Baker and Coltun Expires May 31 1993 [Page 6]
Internet Draft OSPF MIB November 1992
5. Overview
5.1. Textual Conventions
Several new data types are introduced as a textual convention
in this MIB document. These textual conventions enhance the
readability of the specification and can ease comparison with
other specifications if appropriate. It should be noted that
the introduction of the these textual conventions has no
effect on either the syntax nor the semantics of any managed
objects. The use of these is merely an artifact of the
explanatory method used. Objects defined in terms of one of
these methods are always encoded by means of the rules that
define the primitive type. Hence, no changes to the SMI or
the SNMP are necessary to accommodate these textual
conventions which are adopted merely for the convenience of
readers and writers in pursuit of the elusive goal of clear,
concise, and unambiguous MIB documents.
The new data types are AreaID, RouterID, TOSType, Metric,
BigMetric, TruthValue, Status, Validation, PositiveInteger,
HelloRange, UpToMaxAge, InterfaceIndex, and
DesignatedRouterPriority.
5.2. Structure of MIB
The MIB is composed of the following sections:
General Variables
Area Data Structure
Area Stub Metric Table
Link State Database
Address Range Table
Host Table
Interface Table
Interface Metric Table
Virtual Interface Table
Neighbor Table
Virtual Neighbor Table
External Link State Database
5.2.1. General Variables
The General Variables are about what they sound like;
variables which are global to the OSPF Process.
Baker and Coltun Expires May 31 1993 [Page 7]
Internet Draft OSPF MIB November 1992
5.2.2. Area Data Structure and Area Stub Metric Table
The Area Data Structure describes the OSPF Areas that the
router participates in. The Area Stub Metric Table describes
the metrics advertised into a stub area by the default
router(s).
5.2.3. Link State Database and External Link State Database
The Link State Database is provided primarily to provide
detailed information for network debugging.
5.2.4. Address Table and Host Tables
The Address Range Table and Host Table are provided to view
configured Network Summary and Host Route information.
5.2.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, and to provide flexibility in the
event that the IP TOS definition is changed in the future. A
Default Value specification is supplied for the TOS 0
(default) metric.
5.2.6. Virtual Interface Table
Likewise, the Virtual Interface Table describe virtual links
to the OSPF Process.
5.2.7. Neighbor and Virtual Neighbor Tables
The Neighbor Table and the Virtual Neighbor Table describe the
neighbors to the OSPF Process.
5.3. Conceptual Row Creation
For the benefit of row-creation in "conceptual" (see [9])
tables, DEFVAL (Default Value) clauses are included in the
definitions in section 5, suggesting values which an agent
should use for instances of variables which need to be created
due to a Set-Request, but which are not specified in the Set-
Request. DEFVAL clauses have not been specified for some
Baker and Coltun Expires May 31 1993 [Page 8]
Internet Draft OSPF MIB November 1992
objects which are read-only, implying that they are zeroed
upon row creation. These objects are of the SYNTAX Counter or
Gauge.
For those objects not having a DEFVAL clause, both management
stations and agents should heed the Robustness Principle of
the Internet (see RFC-791):
"be liberal in what you accept, conservative in what you
send"
That is, 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 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.).
There are numerous read-write objects in this MIB, as it is
designed for SNMP management of the protocol, not just SNMP
monitoring of its state. However, in the absence of a
standard SNMP Security architecture, it is acceptable for
implementations to implement these as read-only with an
alternative interface for their modification.
5.4. 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. 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
Baker and Coltun Expires May 31 1993 [Page 9]
Internet Draft OSPF MIB November 1992
- ifSpeed is estimated by the interface drivers
- The OSPF Process automatically discovers all IP
Interfaces and creates corresponding OSPF Interfaces
- The TOS 0 metrics are autonomously derived from ifSpeed
- The OSPF Process automatically creates the Areas required
for the Interfaces
The simplest configuration of an OSPF process requires that:
- 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
- All Broadcast and Point to Point interfaces will be
operational. 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
Baker and Coltun Expires May 31 1993 [Page 10]
Internet Draft OSPF MIB November 1992
- 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.
Baker and Coltun Expires May 31 1993 [Page 11]
Internet Draft OSPF MIB November 1992
6. Definitions
RFC1253-MIB DEFINITIONS ::= BEGIN
IMPORTS
Counter, Gauge, IpAddress
FROM RFC1155-SMI
mib-2
FROM RFC1213-MIB
OBJECT-TYPE
FROM RFC-1212;
-- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in [9].
ospf OBJECT IDENTIFIER ::= { mib-2 14 }
-- 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
AreaID ::= IpAddress
-- The Router ID, in OSPF, has the same format as an IP Address,
-- but identifies the router independent of its IP Address.
RouterID ::= IpAddress
-- The OSPF Metric is defined as an unsigned value in the range
Metric ::= INTEGER (1..'FFFF'h)
BigMetric ::= INTEGER (1..'FFFFFF'h)
-- Boolean Values
TruthValue ::= INTEGER { true (1), false (2) }
-- Status Values
Status ::= INTEGER { enabled (1), disabled (2) }
-- Row Creation/Deletion Values
Validation ::= INTEGER { valid (1), invalid (2) }
Baker and Coltun Expires May 31 1993 [Page 12]
Internet Draft OSPF MIB November 1992
-- Time Durations measured in seconds
PositiveInteger ::= INTEGER (1..'7FFFFFFF'h)
HelloRange ::= INTEGER (1..'FFFF'h)
UpToMaxAge ::= INTEGER (1..3600)
-- The range of ifIndex, i.e. (1..ifNumber)
InterfaceIndex ::= INTEGER
-- Potential Priorities for the Designated Router Election
DesignatedRouterPriority ::= INTEGER (0..'FF'h)
-- Type of Service 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.
TOSType ::= INTEGER (0..31)
Baker and Coltun Expires May 31 1993 [Page 13]
Internet Draft OSPF MIB November 1992
-- OSPF General Variables
-- These parameters apply globally to the Router's
-- OSPF Process.
ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 }
ospfRouterId OBJECT-TYPE
SYNTAX RouterID
ACCESS read-write
STATUS mandatory
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."
REFERENCE
"OSPF Version 2, C.1 Global parameters"
::= { ospfGeneralGroup 1 }
ospfAdminStat OBJECT-TYPE
SYNTAX Status
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The administrative status of OSPF in the
router. The value 'enabled' denotes that the
OSPF Process is active on at least one inter-
face; 'disabled' disables it on all inter-
faces."
::= { ospfGeneralGroup 2 }
Baker and Coltun Expires May 31 1993 [Page 14]
Internet Draft OSPF MIB November 1992
ospfVersionNumber OBJECT-TYPE
SYNTAX INTEGER { version2 (2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current version number of the OSPF proto-
col is 2."
REFERENCE
"OSPF Version 2, Title"
::= { ospfGeneralGroup 3 }
ospfAreaBdrRtrStatus OBJECT-TYPE
SYNTAX TruthValue
ACCESS read-only
STATUS mandatory
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
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A flag to note whether this router is config-
ured as an Autonomous System border router."
REFERENCE
"OSPF Version 2, Section 3.3 Classification of
routers"
::= { ospfGeneralGroup 5 }
Baker and Coltun Expires May 31 1993 [Page 15]
Internet Draft OSPF MIB November 1992
ospfExternLsaCount OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
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 INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The 32-bit unsigned sum of the LS checksums of
the external link-state advertisements con-
tained 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."
::= { ospfGeneralGroup 7 }
ospfTOSSupport OBJECT-TYPE
SYNTAX TruthValue
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The router's support for type-of-service rout-
ing."
REFERENCE
"OSPF Version 2, Appendix F.1.2 Optional TOS
support"
::= { ospfGeneralGroup 8 }
Baker and Coltun Expires May 31 1993 [Page 16]
Internet Draft OSPF MIB November 1992
ospfOriginateNewLsas OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of new link-state advertisements
that have been originated. This number is in-
cremented each time the router originates a new
LSA."
::= { ospfGeneralGroup 9 }
ospfRxNewLsas OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of link-state advertisements re-
ceived determined to be new instantiations.
This number does not include newer instantia-
tions of self-originated link-state advertise-
ments."
::= { ospfGeneralGroup 10 }
ospfExtLsdbLimit OBJECT-TYPE
SYNTAX INTEGER (-1..'7FFFFFFF'h)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum number of external link-state en-
tries that can be stored in the link-state da-
tabase. If the value is -1, then there is no
limit."
DEFVAL { -1 }
::= { ospfGeneralGroup 11 }
Baker and Coltun Expires May 31 1993 [Page 17]
Internet Draft OSPF MIB November 1992
ospfMulticastForwarding OBJECT-TYPE
SYNTAX INTEGER
-- 0 no multicast forwarding
-- 1 intra-area multicast forwarding
-- 2 inter-area multicast forwarding
-- 3 inter-area and intra-area multicast forwarding
-- 4 inter-AS multicast forwarding
-- 5 inter-AS and intra-Area multicast forwarding
-- 6 inter-AS and inter-Area multicast forwarding
-- 7 multicast forwarding anywhere
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A bit mask indicating the limits on Network
Layer multicast (Class D) forwarding. It is
represented as a sum of the following:
if intra-Area forwarding is permitted, 1; else 0
if inter-Area forwarding is permitted, 2; else 0
if inter-AS forwarding is permitted, 4; else 0
By default, no multicast forwarding is enabled."
DEFVAL { 0 }
::= { ospfGeneralGroup 12 }
Baker and Coltun Expires May 31 1993 [Page 18]
Internet Draft OSPF MIB November 1992
-- The OSPF Area Data Structure contains information
-- regarding the various areas. The interfaces and
-- virtual links are configured as part of these areas.
-- Area 0.0.0.0, by definition, is the Backbone Area
ospfAreaTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfAreaEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information describing the configured parame-
ters and cumulative statistics of the router's
attached areas."
REFERENCE
"OSPF Version 2, Section 6 The Area Data Struc-
ture"
::= { ospf 2 }
ospfAreaEntry OBJECT-TYPE
SYNTAX OspfAreaEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information describing the configured parame-
ters and cumulative statistics of one of the
router's attached areas."
INDEX { ospfAreaId }
::= { ospfAreaTable 1 }
OspfAreaEntry ::=
SEQUENCE {
ospfAreaId
AreaID,
ospfAuthType
INTEGER,
ospfImportAsExtern
INTEGER,
ospfSpfRuns
Counter,
ospfAreaBdrRtrCount
Gauge,
ospfAsBdrRtrCount
Gauge,
Baker and Coltun Expires May 31 1993 [Page 19]
Internet Draft OSPF MIB November 1992
ospfAreaLsaCount
Gauge,
ospfAreaLsaCksumSum
INTEGER,
ospfAreaSummary
INTEGER,
ospfAreaStatus
Validation
}
ospfAreaId OBJECT-TYPE
SYNTAX AreaID
ACCESS read-write
STATUS mandatory
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 INTEGER
-- none (0),
-- simplePassword (1)
-- reserved for specification by IANA (> 1)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The authentication type specified for an area.
Additional authentication types may be assigned
locally on a per Area basis."
REFERENCE
"OSPF Version 2, Appendix E Authentication"
DEFVAL { 0 } -- no authentication, by default
::= { ospfAreaEntry 2 }
Baker and Coltun Expires May 31 1993 [Page 20]
Internet Draft OSPF MIB November 1992
ospfImportAsExtern OBJECT-TYPE
SYNTAX INTEGER {
importExternal (1),
importNoExternal (2),
importNssa (3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The area's support for importing AS external
link- state advertisements."
REFERENCE
"OSPF Version 2, Appendix C.2 Area parameters"
DEFVAL { importExternal }
::= { ospfAreaEntry 3 }
ospfSpfRuns OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
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."
::= { ospfAreaEntry 4 }
ospfAreaBdrRtrCount OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of area border routers reach-
able within this area. This is initially zero,
and is calculated in each SPF Pass."
::= { ospfAreaEntry 5 }
Baker and Coltun Expires May 31 1993 [Page 21]
Internet Draft OSPF MIB November 1992
ospfAsBdrRtrCount OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
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 Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of link-state advertisements
in this area's link-state database, excluding
AS External LSA's."
::= { ospfAreaEntry 7 }
ospfAreaLsaCksumSum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The 32-bit unsigned sum of the link-state ad-
vertisements' 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 data-
base, and to compare the link-state database of
two routers."
DEFVAL { 0 }
::= { ospfAreaEntry 8 }
Baker and Coltun Expires May 31 1993 [Page 22]
Internet Draft OSPF MIB November 1992
ospfAreaSummary OBJECT-TYPE
SYNTAX INTEGER {
noAreaSummary (1),
sendAreaSummary (2)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The variable ospfAreaSummary controls the im-
port of summary LSAs into stub areas. It has
no effect on other areas.
If it is noAreaSummary, the router will neither
originate nor propagate summary LSAs into the
stub area. It will rely entirely on its de-
fault route.
If it is sendAreaSummary, the router will both
summarize and propagate summary LSAs."
DEFVAL { noAreaSummary }
::= { ospfAreaEntry 9 }
ospfAreaStatus OBJECT-TYPE
SYNTAX Validation
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the status of the en-
try. Setting it to 'invalid' has the effect of
rendering it inoperative. The internal effect
(row removal) is implementation dependent."
DEFVAL { valid }
::= { ospfAreaEntry 10 }
Baker and Coltun Expires May 31 1993 [Page 23]
Internet Draft OSPF MIB November 1992
-- OSPF Area Default Metric Table
-- The OSPF Area Default Metric Table describes the metrics
-- that a default Area Border Router will advertise into a
-- Stub area.
ospfStubAreaTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfStubAreaEntry
ACCESS not-accessible
STATUS mandatory
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
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The metric for a given Type of Service that
will be advertised by a default Area Border
Router into a stub area."
REFERENCE
"OSPF Version 2, Appendix C.2, Area Parameters"
INDEX { ospfStubAreaID, ospfStubTOS }
::= { ospfStubAreaTable 1 }
OspfStubAreaEntry ::=
SEQUENCE {
ospfStubAreaID
AreaID,
ospfStubTOS
TOSType,
ospfStubMetric
BigMetric,
ospfStubStatus
Validation,
ospfStubMetricType
INTEGER
}
Baker and Coltun Expires May 31 1993 [Page 24]
Internet Draft OSPF MIB November 1992
ospfStubAreaID OBJECT-TYPE
SYNTAX AreaID
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The 32 bit identifier for the Stub Area. On
creation, this can be derived from the in-
stance."
::= { ospfStubAreaEntry 1 }
ospfStubTOS OBJECT-TYPE
SYNTAX TOSType
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Type of Service associated with the
metric. On creation, this can be derived from
the instance."
::= { ospfStubAreaEntry 2 }
ospfStubMetric OBJECT-TYPE
SYNTAX BigMetric
ACCESS read-write
STATUS mandatory
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 inter-
faces to other areas."
::= { ospfStubAreaEntry 3 }
Baker and Coltun Expires May 31 1993 [Page 25]
Internet Draft OSPF MIB November 1992
ospfStubStatus OBJECT-TYPE
SYNTAX Validation
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the status of the en-
try. Setting it to 'invalid' has the effect of
rendering it inoperative. The internal effect
(row removal) is implementation dependent."
DEFVAL { valid }
::= { ospfStubAreaEntry 4 }
ospfStubMetricType OBJECT-TYPE
SYNTAX INTEGER {
ospfMetric (1), -- OSPF Metric
comparableCost (2), -- external type 1
nonComparable (3) -- external type 2
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the type of metric ad-
vertised as a default route."
DEFVAL { ospfMetric }
::= { ospfStubAreaEntry 5 }
Baker and Coltun Expires May 31 1993 [Page 26]
Internet Draft OSPF MIB November 1992
-- OSPF Link State Database
-- The Link State Database contains the Link State
-- Advertisements from throughout the areas that the
-- device is attached to.
ospfLsdbTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfLsdbEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The OSPF Process's Link State Database."
REFERENCE
"OSPF Version 2, Section 12 Link State Adver-
tisements"
::= { ospf 4 }
ospfLsdbEntry OBJECT-TYPE
SYNTAX OspfLsdbEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A single Link State Advertisement."
INDEX { ospfLsdbAreaId, ospfLsdbType,
ospfLsdbLsid, ospfLsdbRouterId }
::= { ospfLsdbTable 1 }
OspfLsdbEntry ::=
SEQUENCE {
ospfLsdbAreaId
AreaID,
ospfLsdbType
INTEGER,
ospfLsdbLsid
IpAddress,
ospfLsdbRouterId
RouterID,
ospfLsdbSequence
INTEGER,
ospfLsdbAge
INTEGER,
ospfLsdbChecksum
INTEGER,
Baker and Coltun Expires May 31 1993 [Page 27]
Internet Draft OSPF MIB November 1992
ospfLsdbAdvertisement
OCTET STRING
}
ospfLsdbAreaId OBJECT-TYPE
SYNTAX AreaID
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The 32 bit identifier of the Area from which
the LSA was received."
REFERENCE
"OSPF Version 2, Appendix C.2 Area parameters"
::= { ospfLsdbEntry 1 }
-- External Link State Advertisements are permitted
-- for backward compatibility, but should be displayed in
-- the ospfExtLsdbTable rather than here.
ospfLsdbType OBJECT-TYPE
SYNTAX INTEGER {
routerLink (1),
networkLink (2),
summaryLink (3),
asSummaryLink (4),
asExternalLink (5), -- but see ospfExtLsdbTable
multicastLink (6),
nssaExternalLink (7)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type of the link state advertisement.
Each link state type has a separate advertise-
ment format."
REFERENCE
"OSPF Version 2, Appendix A.4.1 The Link State
Advertisement header"
::= { ospfLsdbEntry 2 }
Baker and Coltun Expires May 31 1993 [Page 28]
Internet Draft OSPF MIB November 1992
ospfLsdbLsid OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
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
ACCESS read-only
STATUS mandatory
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 }
-- Note that the OSPF Sequence Number is a 32 bit signed
-- 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.
Baker and Coltun Expires May 31 1993 [Page 29]
Internet Draft OSPF MIB November 1992
ospfLsdbSequence OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The sequence number field is a signed 32-bit
integer. It is used to detect old and dupli-
cate 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 INTEGER -- Should be 0..MaxAge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This field is the age of the link state adver-
tisement in seconds."
REFERENCE
"OSPF Version 2, Section 12.1.1 LS age"
::= { ospfLsdbEntry 6 }
Baker and Coltun Expires May 31 1993 [Page 30]
Internet Draft OSPF MIB November 1992
ospfLsdbChecksum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
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 connec-
tionless 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
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The entire Link State Advertisement, including
its header."
REFERENCE
"OSPF Version 2, Section 12 Link State Adver-
tisements"
::= { ospfLsdbEntry 8 }
Baker and Coltun Expires May 31 1993 [Page 31]
Internet Draft OSPF MIB November 1992
-- Address Range Table
-- 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 which is known beyond
-- its borders.
ospfAreaRangeTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfAreaRangeEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A range if IP addresses 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"
REFERENCE
"OSPF Version 2, Appendix C.2 Area parameters"
::= { ospf 5 }
ospfAreaRangeEntry OBJECT-TYPE
SYNTAX OspfAreaRangeEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A range if IP addresses 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"
REFERENCE
"OSPF Version 2, Appendix C.2 Area parameters"
INDEX { ospfAreaRangeAreaID, ospfAreaRangeNet }
::= { ospfAreaRangeTable 1 }
OspfAreaRangeEntry ::=
SEQUENCE {
ospfAreaRangeAreaID
AreaID,
ospfAreaRangeNet
IpAddress,
Baker and Coltun Expires May 31 1993 [Page 32]
Internet Draft OSPF MIB November 1992
ospfAreaRangeMask
IpAddress,
ospfAreaRangeStatus
INTEGER
}
ospfAreaRangeAreaID OBJECT-TYPE
SYNTAX AreaID
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Area the Address Range is to be found
within."
REFERENCE
"OSPF Version 2, Appendix C.2 Area parameters"
::= { ospfAreaRangeEntry 1 }
ospfAreaRangeNet OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP Address of the Net or Subnet indicated
by the range."
REFERENCE
"OSPF Version 2, Appendix C.2 Area parameters"
::= { ospfAreaRangeEntry 2 }
ospfAreaRangeMask OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Subnet Mask that pertains to the Net or
Subnet."
REFERENCE
"OSPF Version 2, Appendix C.2 Area parameters"
::= { ospfAreaRangeEntry 3 }
Baker and Coltun Expires May 31 1993 [Page 33]
Internet Draft OSPF MIB November 1992
ospfAreaRangeStatus OBJECT-TYPE
SYNTAX INTEGER {
advertiseMatching (1),
invalid (2),
doNotAdvertiseMatching (3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the status of the en-
try. Setting it to 'invalid' has the effect of
rendering it inoperative. The internal effect
(row removal) is implementation dependent.
Subnets subsumed by ranges either trigger the
advertisement of the indicated summary (adver-
tiseMatching), or result in the subnet's not
being advertised at all outside the area."
DEFVAL { advertiseMatching }
::= { ospfAreaRangeEntry 4 }
Baker and Coltun Expires May 31 1993 [Page 34]
Internet Draft OSPF MIB November 1992
-- OSPF Host Table
-- The Host/Metric Table indicates what hosts are directly
-- attached to the Router, and what metrics and types of
-- service should be advertised for them.
ospfHostTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfHostEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The list of Hosts, and their metrics, that the
router will advertise as host routes."
REFERENCE
"OSPF Version 2, Appendix C.6 Host route param-
eters"
::= { ospf 6 }
ospfHostEntry OBJECT-TYPE
SYNTAX OspfHostEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A metric to be advertised, for a given type of
service, when a given host is reachable."
INDEX { ospfHostIpAddress, ospfHostTOS }
::= { ospfHostTable 1 }
OspfHostEntry ::=
SEQUENCE {
ospfHostIpAddress
IpAddress,
ospfHostTOS
TOSType,
ospfHostMetric
Metric,
ospfHostStatus
Validation
}
Baker and Coltun Expires May 31 1993 [Page 35]
Internet Draft OSPF MIB November 1992
ospfHostIpAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP Address of the Host."
REFERENCE
"OSPF Version 2, Appendix C.6 Host route parame-
ters"
::= { ospfHostEntry 1 }
ospfHostTOS OBJECT-TYPE
SYNTAX TOSType
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Type of Service of the route being config-
ured."
REFERENCE
"OSPF Version 2, Appendix C.6 Host route parame-
ters"
::= { ospfHostEntry 2 }
ospfHostMetric OBJECT-TYPE
SYNTAX Metric
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Metric to be advertised."
REFERENCE
"OSPF Version 2, Appendix C.6 Host route parame-
ters"
::= { ospfHostEntry 3 }
Baker and Coltun Expires May 31 1993 [Page 36]
Internet Draft OSPF MIB November 1992
ospfHostStatus OBJECT-TYPE
SYNTAX Validation
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the status of the en-
try. Setting it to 'invalid' has the effect of
rendering it inoperative. The internal effect
(row removal) is implementation dependent."
DEFVAL { valid }
::= { ospfHostEntry 4 }
Baker and Coltun Expires May 31 1993 [Page 37]
Internet Draft OSPF MIB November 1992
-- OSPF Interface Table
-- The OSPF Interface Table augments the ipAddrTable
-- with OSPF specific information.
ospfIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfIfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The OSPF Interface Table describes the inter-
faces from the viewpoint of OSPF."
REFERENCE
"OSPF Version 2, Appendix C.3 Router interface
parameters"
::= { ospf 7 }
ospfIfEntry OBJECT-TYPE
SYNTAX OspfIfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The OSPF Interface Entry describes one inter-
face from the viewpoint of OSPF."
INDEX { ospfIfIpAddress, ospfAddressLessIf }
::= { ospfIfTable 1 }
OspfIfEntry ::=
SEQUENCE {
ospfIfIpAddress
IpAddress,
ospfAddressLessIf
INTEGER,
ospfIfAreaId
AreaID,
ospfIfType
INTEGER,
ospfIfAdminStat
Status,
ospfIfRtrPriority
DesignatedRouterPriority,
ospfIfTransitDelay
UpToMaxAge,
Baker and Coltun Expires May 31 1993 [Page 38]
Internet Draft OSPF MIB November 1992
ospfIfRetransInterval
UpToMaxAge,
ospfIfHelloInterval
HelloRange,
ospfIfRtrDeadInterval
PositiveInteger,
ospfIfPollInterval
PositiveInteger,
ospfIfState
INTEGER,
ospfIfDesignatedRouter
IpAddress,
ospfIfBackupDesignatedRouter
IpAddress,
ospfIfEvents
Counter,
ospfIfAuthKey
OCTET STRING,
ospfIfStatus
Validation,
ospfIfMulticastForwarding
INTEGER
}
ospfIfIpAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP address of this OSPF interface."
::= { ospfIfEntry 1 }
ospfAddressLessIf OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"For the purpose of easing the instancing of
addressed and addressless interfaces; This
variable takes the value 0 on interfaces with
IP Addresses, and the corresponding value of
ifIndex for interfaces having no IP Address."
::= { ospfIfEntry 2 }
Baker and Coltun Expires May 31 1993 [Page 39]
Internet Draft OSPF MIB November 1992
ospfIfAreaId OBJECT-TYPE
SYNTAX AreaID
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A 32-bit integer uniquely identifying the area
to which the interface connects. Area ID
0.0.0.0 is used for the OSPF backbone."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 3 }
ospfIfType OBJECT-TYPE
SYNTAX INTEGER {
broadcast (1),
nbma (2),
pointToPoint (3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The OSPF interface type.
By way of a default, this field may be intuited
from the corresponding value of ifType. Broad-
cast LANs, such as Ethernet and IEEE 802.5,
take the value 'broadcast', X.25 and similar
technologies take the value 'nbma', and links
that are definitively point to point take the
value 'pointToPoint'."
::= { ospfIfEntry 4 }
Baker and Coltun Expires May 31 1993 [Page 40]
Internet Draft OSPF MIB November 1992
ospfIfAdminStat OBJECT-TYPE
SYNTAX Status
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The OSPF interface's administrative status.
The value formed on the interface, and the in-
terface will be advertised as an internal route
to some area. The value 'disabled' denotes
that the interface is external to OSPF."
DEFVAL { enabled }
::= { ospfIfEntry 5 }
ospfIfRtrPriority OBJECT-TYPE
SYNTAX DesignatedRouterPriority
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The priority of this interface. Used in
multi-access networks, this field is used in
the designated router election algorithm. The
value 0 signifies that the router is not eligi-
ble to become the designated router on this
particular network. In the event of a tie in
this value, routers will use their Router ID as
a tie breaker."
DEFVAL { 1 }
::= { ospfIfEntry 6 }
ospfIfTransitDelay OBJECT-TYPE
SYNTAX UpToMaxAge
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The estimated number of seconds it takes to
transmit a link state update packet over this
interface."
DEFVAL { 1 }
::= { ospfIfEntry 7 }
Baker and Coltun Expires May 31 1993 [Page 41]
Internet Draft OSPF MIB November 1992
ospfIfRetransInterval OBJECT-TYPE
SYNTAX UpToMaxAge
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The number of seconds between link-state ad-
vertisement retransmissions, for adjacencies
belonging to this interface. This value is
also used when retransmitting database descrip-
tion and link-state request packets."
DEFVAL { 5 }
::= { ospfIfEntry 8 }
ospfIfHelloInterval OBJECT-TYPE
SYNTAX HelloRange
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The length of time, in seconds, between the
Hello packets that the router sends on the in-
terface. This value must be the same for all
routers attached to a common network."
DEFVAL { 10 }
::= { ospfIfEntry 9 }
ospfIfRtrDeadInterval OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The number of seconds that a router's Hello
packets have not been seen before it's neigh-
bors declare the router down. This should be
some multiple of the Hello interval. This
value must be the same for all routers attached
to a common network."
DEFVAL { 40 }
::= { ospfIfEntry 10 }
Baker and Coltun Expires May 31 1993 [Page 42]
Internet Draft OSPF MIB November 1992
ospfIfPollInterval OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The larger time interval, in seconds, between
the Hello packets sent to an inactive non-
broadcast multi- access neighbor."
DEFVAL { 120 }
::= { ospfIfEntry 11 }
ospfIfState OBJECT-TYPE
SYNTAX INTEGER {
down (1),
loopback (2),
waiting (3),
pointToPoint (4),
designatedRouter (5),
backupDesignatedRouter (6),
otherDesignatedRouter (7)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The OSPF Interface State."
DEFVAL { down }
::= { ospfIfEntry 12 }
ospfIfDesignatedRouter OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP Address of the Designated Router."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 13 }
Baker and Coltun Expires May 31 1993 [Page 43]
Internet Draft OSPF MIB November 1992
ospfIfBackupDesignatedRouter OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP Address of the Backup Designated
Router."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 14 }
ospfIfEvents OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times this OSPF interface has
changed its state, or an error has occurred."
::= { ospfIfEntry 15 }
ospfIfAuthKey OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Authentication Key. If the Area's Author-
ization Type is simplePassword, and the key
length is shorter than 8 octets, the agent will
left adjust and zero fill to 8 octets.
When read, ospfIfAuthKey always returns an Oc-
tet String of length zero."
REFERENCE
"OSPF Version 2, Section 9 The Interface Data
Structure"
DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
::= { ospfIfEntry 16 }
Baker and Coltun Expires May 31 1993 [Page 44]
Internet Draft OSPF MIB November 1992
ospfIfStatus OBJECT-TYPE
SYNTAX Validation
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the status of the en-
try. Setting it to 'invalid' has the effect of
rendering it inoperative. The internal effect
(row removal) is implementation dependent."
DEFVAL { valid }
::= { ospfIfEntry 17 }
ospfIfMulticastForwarding OBJECT-TYPE
SYNTAX INTEGER {
disabled (1), -- no multicast forwarding
multicast (2), -- using multicast address
unicast (3) -- to each OSPF neighbor
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The way multicasts should forwarded on this
interface; not forwarded, forwarded as data
link multicasts, or forwarded as data link uni-
casts. Data link multicasting is not meaningul
on point to point and NBMA interfaces, and set-
ting ospfMulticastForwarding to 0 effectively
disables all multicast forwarding."
DEFVAL { disabled }
::= { ospfIfEntry 18 }
Baker and Coltun Expires May 31 1993 [Page 45]
Internet Draft OSPF MIB November 1992
-- OSPF Interface Metric Table
-- The Metric Table describes the metrics to be advertised
-- for a specified interface at the various types of service.
-- As such, this table is an adjunct of the OSPF Interface
-- Table.
-- Types of service, as defined by RFC 791, have the ability
-- to request low delay, high bandwidth, or reliable linkage.
-- For the purposes of this specification, the measure of
-- bandwidth
-- Metric = 10^8 / ifSpeed
-- is the default value. For multiple link interfaces, note
-- that ifSpeed is the sum of the individual link speeds.
-- This yields a number having the following typical values:
-- Network Type/bit rate Metric
-- >= 100 MBPS 1
-- Ethernet/802.3 10
-- E1 48
-- T1 (ESF) 65
-- 64 KBPS 1562
-- 56 KBPS 1785
-- 19.2 KBPS 5208
-- 9.6 KBPS 10416
-- Routes that are not specified use the default (TOS 0) metric
ospfIfMetricTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfIfMetricEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The TOS metrics for a non-virtual interface
identified by the interface index."
REFERENCE
"OSPF Version 2, Appendix C.3 Router interface
parameters"
::= { ospf 8 }
Baker and Coltun Expires May 31 1993 [Page 46]
Internet Draft OSPF MIB November 1992
ospfIfMetricEntry OBJECT-TYPE
SYNTAX OspfIfMetricEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A particular TOS metric for a non-virtual in-
terface identified by the interface index."
REFERENCE
"OSPF Version 2, Appendix C.3 Router interface
parameters"
INDEX { ospfIfMetricIpAddress,
ospfIfMetricAddressLessIf,
ospfIfMetricTOS }
::= { ospfIfMetricTable 1 }
OspfIfMetricEntry ::=
SEQUENCE {
ospfIfMetricIpAddress
IpAddress,
ospfIfMetricAddressLessIf
INTEGER,
ospfIfMetricTOS
TOSType,
ospfIfMetricValue
Metric,
ospfIfMetricStatus
Validation
}
ospfIfMetricIpAddress OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP address of this OSPF interface. On row
creation, this can be derived from the in-
stance."
::= { ospfIfMetricEntry 1 }
Baker and Coltun Expires May 31 1993 [Page 47]
Internet Draft OSPF MIB November 1992
ospfIfMetricAddressLessIf OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"For the purpose of easing the instancing of
addressed and addressless interfaces; This
variable takes the value 0 on interfaces with
IP Addresses, and the value of ifIndex for in-
terfaces having no IP Address. On row crea-
tion, this can be derived from the instance."
::= { ospfIfMetricEntry 2 }
ospfIfMetricTOS OBJECT-TYPE
SYNTAX TOSType
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The type of service metric being referenced.
On row creation, this can be derived from the
instance."
::= { ospfIfMetricEntry 3 }
ospfIfMetricValue OBJECT-TYPE
SYNTAX Metric
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The metric of using this type of service on
this interface. The default value of the TOS 0
Metric is 10^8 / ifSpeed."
::= { ospfIfMetricEntry 4 }
Baker and Coltun Expires May 31 1993 [Page 48]
Internet Draft OSPF MIB November 1992
ospfIfMetricStatus OBJECT-TYPE
SYNTAX Validation
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the status of the en-
try. Setting it to 'invalid' has the effect of
rendering it inoperative. The internal effect
(row removal) is implementation dependent."
DEFVAL { valid }
::= { ospfIfMetricEntry 5 }
Baker and Coltun Expires May 31 1993 [Page 49]
Internet Draft OSPF MIB November 1992
-- OSPF Virtual Interface Table
-- The Virtual Interface Table describes the virtual
-- links that the OSPF Process is configured to
-- carry on.
ospfVirtIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfVirtIfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information about this router's virtual inter-
faces."
REFERENCE
"OSPF Version 2, Appendix C.4 Virtual link
parameters"
::= { ospf 9 }
ospfVirtIfEntry OBJECT-TYPE
SYNTAX OspfVirtIfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information about a single Virtual Interface."
INDEX { ospfVirtIfAreaID, ospfVirtIfNeighbor }
::= { ospfVirtIfTable 1 }
OspfVirtIfEntry ::=
SEQUENCE {
ospfVirtIfAreaID
AreaID,
ospfVirtIfNeighbor
RouterID,
ospfVirtIfTransitDelay
UpToMaxAge,
ospfVirtIfRetransInterval
UpToMaxAge,
ospfVirtIfHelloInterval
HelloRange,
ospfVirtIfRtrDeadInterval
PositiveInteger,
ospfVirtIfState
Baker and Coltun Expires May 31 1993 [Page 50]
Internet Draft OSPF MIB November 1992
INTEGER,
ospfVirtIfEvents
Counter,
ospfVirtIfAuthKey
OCTET STRING,
ospfVirtIfStatus
Validation
}
ospfVirtIfAreaID OBJECT-TYPE
SYNTAX AreaID
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Transit Area that the Virtual Link
traverses. By definition, this is not 0.0.0.0"
::= { ospfVirtIfEntry 1 }
ospfVirtIfNeighbor OBJECT-TYPE
SYNTAX RouterID
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Router ID of the Virtual Neighbor."
::= { ospfVirtIfEntry 2 }
ospfVirtIfTransitDelay OBJECT-TYPE
SYNTAX UpToMaxAge
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The estimated number of seconds it takes to
transmit a link- state update packet over this
interface."
DEFVAL { 1 }
::= { ospfVirtIfEntry 3 }
Baker and Coltun Expires May 31 1993 [Page 51]
Internet Draft OSPF MIB November 1992
ospfVirtIfRetransInterval OBJECT-TYPE
SYNTAX UpToMaxAge
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The number of seconds between link-state ad-
vertisement retransmissions, for adjacencies
belonging to this interface. This value is
also used when retransmitting database descrip-
tion and link-state request packets. This
value should be well over the expected round-
trip time."
DEFVAL { 5 }
::= { ospfVirtIfEntry 4 }
ospfVirtIfHelloInterval OBJECT-TYPE
SYNTAX HelloRange
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The length of time, in seconds, between the
Hello packets that the router sends on the in-
terface. This value must be the same for the
virtual neighbor."
DEFVAL { 10 }
::= { ospfVirtIfEntry 5 }
ospfVirtIfRtrDeadInterval OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The number of seconds that a router's Hello
packets have not been seen before it's neigh-
bors declare the router down. This should be
some multiple of the Hello interval. This
value must be the same for the virtual neigh-
bor."
DEFVAL { 60 }
::= { ospfVirtIfEntry 6 }
Baker and Coltun Expires May 31 1993 [Page 52]
Internet Draft OSPF MIB November 1992
ospfVirtIfState OBJECT-TYPE
SYNTAX INTEGER {
down (1), -- these use the same encoding
pointToPoint (4) -- as the ospfIfTable
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"OSPF virtual interface states."
DEFVAL { down }
::= { ospfVirtIfEntry 7 }
ospfVirtIfEvents OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of state changes or error events on
this Virtual Link"
::= { ospfVirtIfEntry 8 }
ospfVirtIfAuthKey OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write
STATUS mandatory
DESCRIPTION
"If Authentication Type is simplePassword, the
device will left adjust and zero fill to 8 oc-
tets.
When read, ospfVifAuthKey always returns a
string of length zero."
REFERENCE
"OSPF Version 2, Section 9 The Interface Data
Structure"
DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
::= { ospfVirtIfEntry 9 }
Baker and Coltun Expires May 31 1993 [Page 53]
Internet Draft OSPF MIB November 1992
ospfVirtIfStatus OBJECT-TYPE
SYNTAX Validation
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the status of the en-
try. Setting it to 'invalid' has the effect of
rendering it inoperative. The internal effect
(row removal) is implementation dependent."
DEFVAL { valid }
::= { ospfVirtIfEntry 10 }
Baker and Coltun Expires May 31 1993 [Page 54]
Internet Draft OSPF MIB November 1992
-- OSPF Neighbor Table
-- The OSPF Neighbor Table describes all neighbors in
-- the locality of the subject router.
ospfNbrTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfNbrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table of non-virtual neighbor information."
REFERENCE
"OSPF Version 2, Section 10 The Neighbor Data
Structure"
::= { ospf 10 }
ospfNbrEntry OBJECT-TYPE
SYNTAX OspfNbrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The information regarding a single neighbor."
REFERENCE
"OSPF Version 2, Section 10 The Neighbor Data
Structure"
INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex }
::= { ospfNbrTable 1 }
OspfNbrEntry ::=
SEQUENCE {
ospfNbrIpAddr
IpAddress,
ospfNbrAddressLessIndex
InterfaceIndex,
ospfNbrRtrId
RouterID,
ospfNbrOptions
INTEGER,
ospfNbrPriority
DesignatedRouterPriority,
ospfNbrState
INTEGER,
Baker and Coltun Expires May 31 1993 [Page 55]
Internet Draft OSPF MIB November 1992
ospfNbrEvents
Counter,
ospfNbrLSRetransQLen
Gauge,
ospfNbmaNbrStatus
INTEGER
}
ospfNbrIpAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP address this neighbor is using in its
IP Source Address. Note that, on addressless
links, this will not be 0.0.0.0, but the ad-
dress of another of the neighbor's interfaces."
::= { ospfNbrEntry 1 }
ospfNbrAddressLessIndex OBJECT-TYPE
SYNTAX InterfaceIndex
ACCESS read-write
STATUS mandatory
DESCRIPTION
"On an interface having an IP Address, zero.
On addressless interfaces, the corresponding
value of ifIndex in the Internet Standard MIB.
On row creation, this can be derived from the
instance."
::= { ospfNbrEntry 2 }
ospfNbrRtrId OBJECT-TYPE
SYNTAX RouterID
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A 32-bit integer (represented as a type IpAd-
dress) uniquely identifying the neighboring
router in the Autonomous System."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfNbrEntry 3 }
Baker and Coltun Expires May 31 1993 [Page 56]
Internet Draft OSPF MIB November 1992
ospfNbrOptions OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A Bit Mask corresponding to the neighbor's op-
tions field.
Bit 0, if set, indicates that the area accepts
and operates on external information; if zero,
it is a stub area.
Bit 1, if set, indicates that the system will
operate on Type of Service metrics other than
TOS 0. If zero, the neighbor will ignore all
metrics except the TOS 0 metric.
Bit 2, if set, indicates that the system is
Network Multicast capable; ie, that it imple-
ments OSPF Multicast Routing."
REFERENCE
"OSPF Version 2, Section 12.1.2 Options"
DEFVAL { 0 }
::= { ospfNbrEntry 4 }
ospfNbrPriority OBJECT-TYPE
SYNTAX DesignatedRouterPriority
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The priority of this neighbor in the designat-
ed router election algorithm. The value 0 sig-
nifies that the neighbor is not eligible to be-
come the designated router on this particular
network."
DEFVAL { 1 }
::= { ospfNbrEntry 5 }
Baker and Coltun Expires May 31 1993 [Page 57]
Internet Draft OSPF MIB November 1992
ospfNbrState OBJECT-TYPE
SYNTAX INTEGER {
down (1),
attempt (2),
init (3),
twoWay (4),
exchangeStart (5),
exchange (6),
loading (7),
full (8)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The State of the relationship with this Neigh-
bor."
REFERENCE
"OSPF Version 2, Section 10.1 Neighbor States"
DEFVAL { down }
::= { ospfNbrEntry 6 }
ospfNbrEvents OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times this neighbor relationship
has changed state, or an error has occurred."
::= { ospfNbrEntry 7 }
ospfNbrLSRetransQLen OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current length of the retransmission
queue."
::= { ospfNbrEntry 8 }
Baker and Coltun Expires May 31 1993 [Page 58]
Internet Draft OSPF MIB November 1992
ospfNbmaNbrStatus OBJECT-TYPE
SYNTAX INTEGER {
dynamic (1), -- learned through protocol
invalid (2), -- set to delete
permanent (3) -- configured address
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable displays the status of the en-
try. Setting it to 'invalid' has the effect of
rendering it inoperative. The internal effect
(row removal) is implementation dependent."
DEFVAL { permanent }
::= { ospfNbrEntry 9 }
Baker and Coltun Expires May 31 1993 [Page 59]
Internet Draft OSPF MIB November 1992
-- OSPF Virtual Neighbor Table
-- This table describes all virtual neighbors.
-- Since Virtual Links are configured in the
-- virtual interface table, this table is read-only.
ospfVirtNbrTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfVirtNbrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table of virtual neighbor information."
REFERENCE
"OSPF Version 2, Section 15 Virtual Links"
::= { ospf 11 }
ospfVirtNbrEntry OBJECT-TYPE
SYNTAX OspfVirtNbrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Virtual neighbor information."
INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId }
::= { ospfVirtNbrTable 1 }
OspfVirtNbrEntry ::=
SEQUENCE {
ospfVirtNbrArea
AreaID,
ospfVirtNbrRtrId
RouterID,
ospfVirtNbrIpAddr
IpAddress,
ospfVirtNbrOptions
INTEGER,
ospfVirtNbrState
INTEGER,
ospfVirtNbrEvents
Counter,
ospfVirtNbrLSRetransQLen
Gauge
}
Baker and Coltun Expires May 31 1993 [Page 60]
Internet Draft OSPF MIB November 1992
ospfVirtNbrArea OBJECT-TYPE
SYNTAX AreaID
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Transit Area Identifier."
::= { ospfVirtNbrEntry 1 }
ospfVirtNbrRtrId OBJECT-TYPE
SYNTAX RouterID
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A 32-bit integer uniquely identifying the
neighboring router in the Autonomous System."
::= { ospfVirtNbrEntry 2 }
ospfVirtNbrIpAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP address this Virtual Neighbor is us-
ing."
::= { ospfVirtNbrEntry 3 }
Baker and Coltun Expires May 31 1993 [Page 61]
Internet Draft OSPF MIB November 1992
ospfVirtNbrOptions OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A Bit Mask corresponding to the neighbor's op-
tions field.
Bit 1, if set, indicates that the system will
operate on Type of Service metrics other than
TOS 0. If zero, the neighbor will ignore all
metrics except the TOS 0 metric.
Bit 2, if set, indicates that the system is
Network Multicast capable; ie, that it imple-
ments OSPF Multicast Routing."
::= { ospfVirtNbrEntry 4 }
ospfVirtNbrState OBJECT-TYPE
SYNTAX INTEGER {
down (1),
attempt (2),
init (3),
twoWay (4),
exchangeStart (5),
exchange (6),
loading (7),
full (8)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The state of the Virtual Neighbor Relation-
ship."
::= { ospfVirtNbrEntry 5 }
Baker and Coltun Expires May 31 1993 [Page 62]
Internet Draft OSPF MIB November 1992
ospfVirtNbrEvents OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times this virtual link has
changed its state, or an error has occurred."
::= { ospfVirtNbrEntry 6 }
ospfVirtNbrLSRetransQLen OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current length of the retransmission
queue."
::= { ospfVirtNbrEntry 7 }
Baker and Coltun Expires May 31 1993 [Page 63]
Internet Draft OSPF MIB November 1992
-- OSPF Link State Database, External
-- The Link State Database contains the Link State
-- Advertisements from throughout the areas that the
-- device is attached to.
-- This table is identical to the OSPF LSDB Table in
-- format, but contains only External Link State
-- Advertisements. The purpose is to allow external
-- LSAs to be displayed once for the router rather
-- than once in each non-stub area.
ospfExtLsdbTable OBJECT-TYPE
SYNTAX SEQUENCE OF OspfExtLsdbEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The OSPF Process's Links State Database."
REFERENCE
"OSPF Version 2, Section 12 Link State Adver-
tisements"
::= { ospf 12 }
ospfExtLsdbEntry OBJECT-TYPE
SYNTAX OspfExtLsdbEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A single Link State Advertisement."
INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId }
::= { ospfExtLsdbTable 1 }
OspfExtLsdbEntry ::=
SEQUENCE {
ospfExtLsdbType
INTEGER,
ospfExtLsdbLsid
IpAddress,
ospfExtLsdbRouterId
RouterID,
ospfExtLsdbSequence
INTEGER,
ospfExtLsdbAge
Baker and Coltun Expires May 31 1993 [Page 64]
Internet Draft OSPF MIB November 1992
INTEGER,
ospfExtLsdbChecksum
INTEGER,
ospfExtLsdbAdvertisement
OCTET STRING
}
ospfExtLsdbType OBJECT-TYPE
SYNTAX INTEGER {
asExternalLink (5)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type of the link state advertisement.
Each link state type has a separate advertise-
ment format."
REFERENCE
"OSPF Version 2, Appendix A.4.1 The Link State
Advertisement header"
::= { ospfExtLsdbEntry 1 }
ospfExtLsdbLsid OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
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"
::= { ospfExtLsdbEntry 2 }
Baker and Coltun Expires May 31 1993 [Page 65]
Internet Draft OSPF MIB November 1992
ospfExtLsdbRouterId OBJECT-TYPE
SYNTAX RouterID
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The 32 bit number that uniquely identifies the
originating router in the Autonomous System."
REFERENCE
"OSPF Version 2, Appendix C.1 Global parameters"
::= { ospfExtLsdbEntry 3 }
-- Note that the OSPF Sequence Number is a 32 bit signed
-- 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.
ospfExtLsdbSequence OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The sequence number field is a signed 32-bit
integer. It is used to detect old and dupli-
cate 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"
::= { ospfExtLsdbEntry 4 }
ospfExtLsdbAge OBJECT-TYPE
SYNTAX INTEGER -- Should be 0..MaxAge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This field is the age of the link state adver-
tisement in seconds."
REFERENCE
"OSPF Version 2, Section 12.1.1 LS age"
::= { ospfExtLsdbEntry 5 }
Baker and Coltun Expires May 31 1993 [Page 66]
Internet Draft OSPF MIB November 1992
ospfExtLsdbChecksum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
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 connec-
tionless datagrams; it is commonly referred to
as the Fletcher checksum."
REFERENCE
"OSPF Version 2, Section 12.1.7 LS checksum"
::= { ospfExtLsdbEntry 6 }
ospfExtLsdbAdvertisement OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The entire Link State Advertisement, including
its header."
REFERENCE
"OSPF Version 2, Section 12 Link State Adver-
tisements"
::= { ospfExtLsdbEntry 7 }
Baker and Coltun Expires May 31 1993 [Page 67]
Internet Draft OSPF MIB November 1992
-- OSPF Use of the IP Forwarding Table
ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 }
-- The IP Forwarding Table defines a number of objects for use by
-- the routing protocol to externalize its information. Most of
-- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy,
-- ipForwardNextHop, ipForwardIfIndex, ipForwardType,
-- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are
-- defined there.
-- Those that leave some discretion are defined here.
-- ipForwardProto is, of course, ospf (13).
-- ipForwardAge is the time since the route was first calculated,
-- as opposed to the time since the last SPF run.
-- ipForwardInfo is an OBJECT IDENTIFIER for use by the routing
-- protocol. The following values shall be found there depending
-- on the way the route was calculated.
ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 }
ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 }
ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 }
ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 }
-- ipForwardMetric1 is, by definition, the primary routing
-- metric. Therefore, it should be the metric that route
-- selection is based on. For intra-area and inter-area routes,
-- it is an OSPF metric. For External Type 1 (comparable value)
-- routes, it is an OSPF metric plus the External Metric. For
-- external Type 2 (non-comparable value) routes, it is the
-- external metric.
-- ipForwardMetric2 is, by definition, a secondary routing
-- metric. Therefore, it should be the metric that breaks a tie
-- among routes having equal metric1 values and the same
-- calculation rule. For intra-area, inter-area routes, and
-- External Type 1 (comparable value) routes, it is unused. For
-- external Type 2 (non-comparable value) routes, it is the metric
-- to the AS border router.
-- ipForwardMetric3, ipForwardMetric4, and ipForwardMetric5 are
-- unused.
Baker and Coltun Expires May 31 1993 [Page 68]
Internet Draft OSPF MIB November 1992
END
Baker and Coltun Expires May 31 1993 [Page 69]
Internet Draft OSPF MIB November 1992
7. Acknowledgements
This document was produced by the OSPF Working Group.
8. References
[1] V. Cerf, IAB Recommendations for the Development of
Internet Network Management Standards. Internet Working
Group Request for Comments 1052. Network Information
Center, SRI International, Menlo Park, California,
(April, 1988).
[2] V. Cerf, Report of the Second Ad Hoc Network Management
Review Group, Internet Working Group Request for Comments
1109. Network Information Center, SRI International,
Menlo Park, California, (August, 1989).
[3] M.T. Rose and K. McCloghrie, Structure and Identification
of Management Information for TCP/IP-based internets,
Internet Working Group Request for Comments 1155.
Network Information Center, SRI International, Menlo
Park, California, (May, 1990).
[4] K. McCloghrie and M.T. Rose, Management Information Base
for Network Management of TCP/IP-based internets,
Internet Working Group Request for Comments 1156.
Network Information Center, SRI International, Menlo
Park, California, (May, 1990).
[5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin,
Simple Network Management Protocol, Internet Working
Group Request for Comments 1157. Network Information
Center, SRI International, Menlo Park, California, (May,
1990).
[6] M.T. Rose (editor), Management Information Base for
Network Management of TCP/IP-based internets, Internet
Working Group Request for Comments 1213. Network
Information Center, SRI International, Menlo Park,
California, (May, 1990).
[7] Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax
Notation One (ASN.1), International Organization for
Standardization. International Standard 8824, (December,
Baker and Coltun Expires May 31 1993 [Page 70]
Internet Draft OSPF MIB November 1992
1987).
[8] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules
for Abstract Notation One (ASN.1), International
Organization for Standardization. International Standard
8825, (December, 1987).
[9] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB
Definitions, Internet Draft, Internet Engineering Task
Force, (September, 1990).
[10] M.T. Rose (editor), A Convention for Defining Traps for
use with the SNMP, Internet Draft, Internet Engineering
Task Force, (September, 1990).
Baker and Coltun Expires May 31 1993 [Page 71]
Internet Draft OSPF MIB November 1992
Table of Contents
1 Status of this Memo ................................... 1
2 Abstract .............................................. 2
3 The Network Management Framework ...................... 3
4 Objects ............................................... 4
4.1 Format of Definitions ............................... 4
4.2 Changes from RFC 1253 ............................... 4
5 Overview .............................................. 7
5.1 Textual Conventions ................................. 7
5.2 Structure of MIB .................................... 7
5.2.1 General Variables ................................. 7
5.2.2 Area Data Structure and Area Stub Metric Table .... 8
5.2.3 Link State Database and External Link State Da-
tabase ............................................. 8
5.2.4 Address Table and Host Tables ..................... 8
5.2.5 Interface and Interface Metric Tables ............. 8
5.2.6 Virtual Interface Table ........................... 8
5.2.7 Neighbor and Virtual Neighbor Tables .............. 8
5.3 Conceptual Row Creation ............................. 8
5.4 Default Configuration ............................... 9
6 Definitions ........................................... 12
6.1 OSPF General Variables .............................. 13
6.2 OSPF Area Table ..................................... 18
6.3 OSPF Area Default Metrics ........................... 23
6.4 OSPF Link State Database ............................ 26
6.5 OSPF Address Range Table ............................ 31
6.6 OSPF Host Table ..................................... 34
6.7 OSPF Interface Table ................................ 37
6.8 OSPF Interface Metrics .............................. 45
6.9 OSPF Virtual Interface Table ........................ 49
6.10 OSPF Neighbor Table ................................ 54
6.11 OSPF Virtual Neighbor Table ........................ 59
6.12 OSPF External Link State Database .................. 63
6.13 OSPF Route Table Use ............................... 68
7 Acknowledgements ...................................... 70
8 References ............................................ 70
Baker and Coltun Expires May 31 1993 [Page 72]
