As per Relevance of the word reference, we have this rfc below:
Network Working Group F.
Request For Comments: 1850 Cisco
Obsoletes: 1253 R.
Category: Standards Track RainbowBridge
November 1995
OSPF Version 2 Management Information
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
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
First Routing Protocol
Table of
1. The SNMPv2 Network Management Framework .............. 2
1.1 Object Definitions .................................. 3
2. Overview ............................................. 3
2.1 Changes from RFC 1253 ............................... 3
2.2 Textual Conventions ................................. 6
2.3 Structure of MIB .................................... 6
2.3.1 General Variables ................................. 6
2.3.2 Area Data Structure and Area Stub Metric Table .... 7
2.3.3 Link State Database and External Link
Database .......................................... 7
2.3.4 Address Table and Host Tables ..................... 7
2.3.5 Interface and Interface Metric Tables ............. 7
2.3.6 Virtual Interface Table ........................... 7
2.3.7 Neighbor and Virtual Neighbor Tables .............. 7
2.4 Conceptual Row Creation ............................. 7
2.5 Default Configuration ............................... 8
3. Definitions .......................................... 10
3.1 OSPF General Variables .............................. 13
3.2 OSPF Area Table ..................................... 17
Baker & Coltun Standards Track [Page 1]
RFC 1850 OSPF MIB November 1995
3.3 OSPF Area Default Metrics ........................... 21
3.4 OSPF Link State Database ............................ 25
3.5 OSPF Address Range Table ............................ 27
3.6 OSPF Host Table ..................................... 29
3.7 OSPF Interface Table ................................ 32
3.8 OSPF Interface Metrics .............................. 39
3.9 OSPF Virtual Interface Table ........................ 42
3.10 OSPF Neighbor Table ................................ 46
3.11 OSPF Virtual Neighbor Table ........................ 51
3.12 OSPF External Link State Database .................. 54
3.13 OSPF Route Table Use ............................... 57
3.14 OSPF Area Aggregate Table .......................... 58
4. OSPF Traps ........................................... 66
4.1 Format Of Trap Definitions .......................... 67
4.2 Approach ............................................ 67
4.3 Ignoring Initial Activity ........................... 67
4.4 Throttling Traps .................................... 67
4.5 One Trap Per OSPF Event ............................. 68
4.6 Polling Event Counters .............................. 68
5. OSPF Trap Definitions ................................ 69
5.1 Trap Support Objects ................................ 69
5.2 Traps ............................................... 71
6. Acknowledgements ...................................... 78
7. References ............................................ 78
8. Security Considerations ............................... 80
9. Authors' Addresses .................................... 80
1. The SNMPv2 Network Management
The SNMPv2 Network Management Framework consists of four
components. They are
o RFC 1441 which defines the SMI, the mechanisms used
describing and naming objects for the purpose
management
o STD 17, RFC 1213 defines MIB-II, the core set of managed
for the Internet suite of protocols
o RFC 1445 which defines the administrative and
architectural aspects of the framework
o RFC 1448 which defines the protocol used for
access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
Baker & Coltun Standards Track [Page 2]
RFC 1850 OSPF MIB November 1995
1.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object object type is
by an OBJECT IDENTIFIER, an administratively assigned name.
object type together with an object instance serves to
identify a specific instantiation of the object. For
convenience, we often use a textual string, termed the descriptor,
refer to the object type
2.
2.1. Changes from RFC 1253
The changes from RFC 1253 are the following
(1) The textual convention PositiveInteger was changed
1..'FFFFFFFF'h to 1..'7FFFFFFF'h at the request
Marshall Rose
(2) The textual convention TOSType was changed to reflect
TOS values defined in the Router Requirements Draft,
in accordance with the IP Forwarding Table MIB's values
(3) The names of some objects were changed, conforming to
convention that an acronym (for example, LSA) is a
word ("Lsa") in most SNMP names
(4) textual changes were made to make the MIB readable
Dave Perkins' SMIC MIB Compiler in addition to Mosy
This involved changing the case of some characters
certain names and removing the DEFVAL clauses
Counters
(5) The variables ospfAreaStatus and ospfIfStatus were added
having been overlooked in the original MIB
(6) The range of the variable ospfLsdbType was extended
include multicastLink (Group-membership LSA)
nssaExternalLink (NSSA LSA).
(7) The variable ospfIfMetricMetric was
ospfIfMetricValue, and the following text was
from its description
"The value FFFF is distinguished to mean 'no route
Baker & Coltun Standards Track [Page 3]
RFC 1850 OSPF MIB November 1995
this TOS'."
(8) The variable ospfNbmaNbrPermanence was added, with
values 'dynamic' and 'permanent'; by this means
dynamically learned and configured neighbors can
distinguished
(9) The DESCRIPTION of the variable ospfNbrIpAddr was
"The IP address of this neighbor."
"The IP address this neighbor is using in its IP
Address. Note that, on addressless links, this will
be 0.0.0.0, but the address of another of the neighbor'
interfaces."
This is by way of clarification and does not change
specification
(10) The OSPF External Link State Database was added.
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
External LSAs, and they are relicated in all non-
Areas
(11) The variable ospfAreaSummary was added to control
import of summary LSAs into stub areas. If it
noAreaSummary (default) the router will neither
nor propagate summary LSAs into the stub area. It
rely entirely on its default route. If it
sendAreaSummary, the router will both summarize
propagate summary LSAs
(12) The general variables ospfExtLsdbLimit
ExitOverflowInterval were introduced to help handle
overflow
(13) The use of the IP Forwarding Table is defined
(14) The ospfAreaRangeTable was obsoleted and replaced
the ospfAreaAggregateTable to accommodate two
indexes. The ospfAreaAggregateEntry keys now include
LsdbType (which can be used to differentiate between
traditional type-3 Aggregates and NSSA Aggregates) and
Baker & Coltun Standards Track [Page 4]
RFC 1850 OSPF MIB November 1995
ospfAreaAggregateMask (which will more clearly
the range).
(15) The variable ospfAreaAggregateEffect was added.
permits the network manager to hide a subnet within
area
(16) Normally, the border router of a stub area advertises
default route as an OSPF network summary. An NSSA
router will generate a type-7 LSA indicating a
route, and import it into the NSSA.
(ospf internal, type 1 external, or type 2 external
indicates the type of the default metric advertised
(17) ospfMulticastExtensions is added to the OSPF
Group. This indicates the router's ability to forward
multicast (Class D) datagrams
(18) ospfIfMulticastForwarding is added to the
Group. It indicates whether, and if so, how,
should be forwarded on the interface
(19) The MIB is converted to SNMP Version 2. Beyond
text changes and the addition of the MODULE-IDENTITY
MODULE-COMPLIANCE macros, this involved trading
TruthValue Textual Convention for SNMP Version 2's,
has the same values, and trading the Validation
Convention for SNMP Version 2's RowStatus
(20) ospfAuthType (area authentication type) was changed to
interface authentication type to match the key. It
has an additional value, to indicate the use of MD5
authentication
(21) ospfIfIntfType has a new value, pointToMultipoint
(22) ospfIfDemand (read/write) is added, to permit control
Demand OSPF features
(23) ospfNbrHelloSuppressed and
were added, (read only). They indicate whether Hellos
being suppressed to the neighbor
(24) ospfDemandExtensions was added to indicate whether
Demand OSPF extensions have been implemented, and
disable them if appropriate
Baker & Coltun Standards Track [Page 5]
RFC 1850 OSPF MIB November 1995
2.2. Textual
Several new data types are introduced as a textual convention in
MIB document. These textual conventions enhance the readability
the specification and can ease comparison with other
if appropriate. It should be noted that the introduction of
these textual conventions has no effect on either the syntax nor
semantics of any managed objects. The use of these is merely
artifact of the explanatory method used. Objects defined in terms
one of these methods are always encoded by means of the rules
define the primitive type. Hence, no changes to the SMI or the
are necessary to accommodate these textual conventions which
adopted merely for the convenience of readers and writers in
of the elusive goal of clear, concise, and unambiguous MIB documents
The new data types are AreaID, RouterID, TOSType, Metric, BigMetric
Status, PositiveInteger, HelloRange, UpToMaxAge, InterfaceIndex,
DesignatedRouterPriority
2.3. Structure of
The MIB is composed of the following sections
General
Area Data
Area Stub Metric
Link State
Address Range
Host
Interface
Interface Metric
Virtual Interface
Neighbor
Virtual Neighbor
External Link State
Aggregate Range
There exists a separate MIB for notifications ("traps"), which
entirely optional
2.3.1. General
The General Variables are about what they sound like; variables
are global to the OSPF Process
Baker & Coltun Standards Track [Page 6]
RFC 1850 OSPF MIB November 1995
2.3.2. Area Data Structure and Area Stub Metric
The Area Data Structure describes the OSPF Areas that the
participates in. The Area Stub Metric Table describes the
advertised into a stub area by the default router(s).
2.3.3. Link State Database and External Link State
The Link State Database is provided primarily to provide
information for network debugging
2.3.4. Address Table and Host
The Address Range Table and Host Table are provided to
configured Network Summary and Host Route information
2.3.5. Interface and Interface Metric
The Interface Table and the Interface Metric Table together
the various IP interfaces to OSPF. The metrics are placed
separate tables in order to simplify dealing with multiple types
service, and to provide flexibility in the event that the IP
definition is changed in the future. A Default Value
is supplied for the TOS 0 (default) metric
2.3.6. Virtual Interface
Likewise, the Virtual Interface Table describe virtual links to
OSPF Process
2.3.7. Neighbor and Virtual Neighbor
The Neighbor Table and the Virtual Neighbor Table describe
neighbors to the OSPF Process
2.4. Conceptual Row
For the benefit of row-creation in "conceptual" (see [9]) tables
DEFVAL (Default Value) clauses are included in the definitions
section 3, suggesting values which an agent should use for
of variables which need to be created due to a Set-Request, but
are not specified in the Set-Request. DEFVAL clauses have not
specified for some objects which are read-only, implying that
are zeroed upon row creation. These objects are of the
Counter32 or Gauge32.
For those objects not having a DEFVAL clause, both
stations and agents should heed the Robustness Principle of
Baker & Coltun Standards Track [Page 7]
RFC 1850 OSPF MIB November 1995
Internet (see RFC-791):
"be liberal in what you accept, conservative in what
send
That is, management stations should include as many of these
objects as possible (e.g., all read-write objects) in a Set-
when creating a conceptual row; agents should accept a Set-
with as few of these as they need (e.g., the minimum contents of
row creating SET consists of those objects for which, as they
be intuited, no default is specified.).
There are numerous read-write objects in this MIB, as it is
for SNMP management of the protocol, not just SNMP monitoring of
state. However, in the absence of a standard SNMP
architecture, it is acceptable for implementations to implement
as read-only with an alternative interface for their modification
2.5. Default
OSPF is a powerful routing protocol, equipped with features to
virtually any configuration requirement that might reasonably
found within an Autonomous System. With this power comes a
degree of complexity, which the sheer number of objects in the
will attest to. Care has therefore been taken, in constructing
MIB, to define default values for virtually every object, to
the amount of parameterization required in the typical case.
default configuration is as follows
Given the following assumptions
- IP has already been
- The ifTable has already been
- ifSpeed is estimated by the interface
- The OSPF Process automatically discovers all
Interfaces and creates corresponding OSPF
- The TOS 0 metrics are autonomously derived from
- The OSPF Process automatically creates the Areas
for the
The simplest configuration of an OSPF process requires that
- The OSPF Process be Enabled
Baker & Coltun Standards Track [Page 8]
RFC 1850 OSPF MIB November 1995
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 will be neither an Area Border Router nor
Autonomous System Border Router
- Every IP Interface, with or without an address, will
an OSPF Interface
- The AreaID of each interface will be 0.0.0.0,
Backbone
- Authentication will be
- All Broadcast and Point to Point interfaces will
operational. NBMA Interfaces require the
of at least one neighbor
- Timers on all direct interfaces will be
Hello Interval: 10
Dead Timeout: 40
Retransmission: 5
Transit Delay: 1
Poll Interval: 120
- no direct links to hosts will be configured
- no addresses will be
- Metrics, being a measure of bit duration, are
and intelligent
- No Virtual Links will be configured
Baker & Coltun Standards Track [Page 9]
RFC 1850 OSPF MIB November 1995
3.
OSPF-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32,
Integer32,
FROM SNMPv2-
TEXTUAL-CONVENTION, TruthValue,
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-
mib-2 FROM RFC1213-MIB
-- This MIB module uses the extended OBJECT-TYPE macro
-- defined in [9].
ospf MODULE-
LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
ORGANIZATION "IETF OSPF Working Group
CONTACT-
" Fred
Postal: Cisco
519 Lado
Santa Barbara, California 93111
Tel: +1 805 681 0115
E-Mail: fred@cisco.
Rob
Postal: RainbowBridge
Tel: (301) 340-9416
E-Mail: rcoltun@rainbow-bridge.com
"The MIB module to describe the OSPF Version 2
Protocol
::= { 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
-- Link State
AreaID ::= TEXTUAL-
STATUS
"An OSPF Area Identifier."
SYNTAX
-- The Router ID, in OSPF, has the same format as an IP Address
Baker & Coltun Standards Track [Page 10]
RFC 1850 OSPF MIB November 1995
-- but identifies the router independent of its IP Address
RouterID ::= TEXTUAL-
STATUS
"A OSPF Router Identifier."
SYNTAX
-- The OSPF Metric is defined as an unsigned value in the
Metric ::= TEXTUAL-
STATUS
"The OSPF Internal Metric."
SYNTAX Integer32 (0..'FFFF'h
BigMetric ::= TEXTUAL-
STATUS
"The OSPF External Metric."
SYNTAX Integer32 (0..'FFFFFF'h
-- Status
Status ::= TEXTUAL-
STATUS
"The status of an interface: 'enabled' indicates
it is willing to communicate with other OSPF Routers
while 'disabled' indicates that it is not."
SYNTAX INTEGER { enabled (1), disabled (2) }
-- Time Durations measured in
PositiveInteger ::= TEXTUAL-
STATUS
"A positive integer. Values in excess are precluded
unnecessary and prone to interoperability issues."
SYNTAX Integer32 (0..'7FFFFFFF'h
HelloRange ::= TEXTUAL-
STATUS
"The range of intervals on which hello messages
exchanged."
SYNTAX Integer32 (1..'FFFF'h
Baker & Coltun Standards Track [Page 11]
RFC 1850 OSPF MIB November 1995
UpToMaxAge ::= TEXTUAL-
STATUS
"The values that one might find or configure
variables bounded by the maximum age of an LSA."
SYNTAX Integer32 (0..3600)
-- The range of
InterfaceIndex ::= TEXTUAL-
STATUS
"The range of ifIndex."
SYNTAX Integer32
-- Potential Priorities for the Designated Router
DesignatedRouterPriority ::= TEXTUAL-
STATUS
"The values defined for the priority of a system
becoming the designated router."
SYNTAX Integer32 (0..'FF'h
TOSType ::= TEXTUAL-
STATUS
"Type of Service is defined as a mapping to the IP Type
Service Flags as defined in the IP Forwarding Table
+-----+-----+-----+-----+-----+-----+-----+-----+
| | | |
| PRECEDENCE | TYPE OF SERVICE | 0 |
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+
IP TOS IP
Field Policy Field
Contents Code Contents
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
Baker & Coltun Standards Track [Page 12]
RFC 1850 OSPF MIB November 1995
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)
-- OSPF General
-- These parameters apply globally to the Router'
-- OSPF Process
ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 }
ospfRouterId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A 32-bit integer uniquely identifying
router in the Autonomous System
By convention, to ensure uniqueness,
should default to the value of one of
router's IP interface addresses."
"OSPF Version 2, C.1 Global parameters
::= { ospfGeneralGroup 1 }
ospfAdminStat OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The administrative status of OSPF in
router. The value 'enabled' denotes that
OSPF Process is active on at least one inter
face; 'disabled' disables it on all inter
faces."
::= { ospfGeneralGroup 2 }
ospfVersionNumber OBJECT-
SYNTAX INTEGER { version2 (2) }
MAX-ACCESS read-
STATUS
Baker & Coltun Standards Track [Page 13]
RFC 1850 OSPF MIB November 1995
"The current version number of the OSPF proto
col is 2."
"OSPF Version 2, Title
::= { ospfGeneralGroup 3 }
ospfAreaBdrRtrStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag to note whether this router is an
border router."
"OSPF Version 2, Section 3 Splitting the AS
Areas
::= { ospfGeneralGroup 4 }
ospfASBdrRtrStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag to note whether this router is config
ured as an Autonomous System border router."
"OSPF Version 2, Section 3.3 Classification
routers
::= { ospfGeneralGroup 5 }
ospfExternLsaCount OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"The number of external (LS type 5) link-
advertisements in the link-state database."
"OSPF Version 2, Appendix A.4.5 AS external
advertisements
::= { ospfGeneralGroup 6 }
ospfExternLsaCksumSum OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
Baker & Coltun Standards Track [Page 14]
RFC 1850 OSPF MIB November 1995
STATUS
"The 32-bit unsigned sum of the LS checksums
the external link-state advertisements con
tained in the link-state database. This
can be used to determine if there has been
change in a router's link state database,
to compare the link-state database of
routers."
::= { ospfGeneralGroup 7 }
ospfTOSSupport OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The router's support for type-of-service rout
ing."
"OSPF Version 2, Appendix F.1.2 Optional
support
::= { ospfGeneralGroup 8 }
ospfOriginateNewLsas OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of new link-state
that have been originated. This number is in
cremented each time the router originates a
LSA."
::= { ospfGeneralGroup 9 }
ospfRxNewLsas OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"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 }
Baker & Coltun Standards Track [Page 15]
RFC 1850 OSPF MIB November 1995
ospfExtLsdbLimit OBJECT-
SYNTAX Integer32 (-1..'7FFFFFFF'h
MAX-ACCESS read-
STATUS
"The maximum number of non-default AS
external-LSAs entries that can be stored in
link-state database. If the value is -1,
there is no limit
When the number of non-default AS-external-
in a router's link-state database
ospfExtLsdbLimit, the router enters Overflow
State. The router never holds more
ospfExtLsdbLimit non-default AS-external-
in its database. OspfExtLsdbLimit MUST be
identically in all routers attached to the
backbone and/or any regular OSPF area. (i.e.,
OSPF stub areas and NSSAs are excluded)."
DEFVAL { -1 }
::= { ospfGeneralGroup 11 }
ospfMulticastExtensions OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"A Bit Mask indicating whether the router
forwarding IP multicast (Class D)
based on the algorithms defined in the Multi
cast Extensions to OSPF
Bit 0, if set, indicates that the router
forward IP multicast datagrams in the router'
directly attached areas (called intra-area mul
ticast routing).
Bit 1, if set, indicates that the router
forward IP multicast datagrams between
areas (called inter-area multicast routing).
Bit 2, if set, indicates that the router
forward IP multicast datagrams between Auto
nomous Systems (called inter-AS multicast rout
ing).
Only certain combinations of bit settings
allowed, namely: 0 (no multicast forwarding
Baker & Coltun Standards Track [Page 16]
RFC 1850 OSPF MIB November 1995
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 mul
ticast forwarding is enabled."
DEFVAL { 0 }
::= { ospfGeneralGroup 12 }
ospfExitOverflowInterval OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of seconds that, after
OverflowState, a router will attempt to
OverflowState. This allows the router to
originate non-default AS-external-LSAs.
set to 0, the router will not leave Overflow
State until restarted."
DEFVAL { 0 }
::= { ospfGeneralGroup 13 }
ospfDemandExtensions OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The router's support for demand routing."
"OSPF Version 2, Appendix on Demand Routing
::= { ospfGeneralGroup 14 }
-- The OSPF Area Data Structure contains
-- regarding the various areas. The interfaces
-- virtual links are configured as part of these areas
-- Area 0.0.0.0, by definition, is the Backbone
ospfAreaTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Information describing the configured parame
ters and cumulative statistics of the router'
attached areas."
Baker & Coltun Standards Track [Page 17]
RFC 1850 OSPF MIB November 1995
"OSPF Version 2, Section 6 The Area Data Struc
ture
::= { ospf 2 }
ospfAreaEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information describing the configured parame
ters and cumulative statistics of one of
router's attached areas."
INDEX { ospfAreaId }
::= { ospfAreaTable 1 }
OspfAreaEntry ::=
SEQUENCE {
AreaID
Integer32,
INTEGER
Counter32,
Gauge32,
Gauge32,
Gauge32,
Integer32,
INTEGER
}
ospfAreaId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A 32-bit integer uniquely identifying an area
Area ID 0.0.0.0 is used for the OSPF backbone."
Baker & Coltun Standards Track [Page 18]
RFC 1850 OSPF MIB November 1995
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfAreaEntry 1 }
ospfAuthType OBJECT-
SYNTAX Integer32
-- none (0),
-- simplePassword (1)
-- md5 (2)
-- reserved for specification by IANA (> 2)
MAX-ACCESS read-
STATUS
"The authentication type specified for an area
Additional authentication types may be
locally on a per Area basis."
"OSPF Version 2, Appendix E Authentication
DEFVAL { 0 } -- no authentication, by
::= { ospfAreaEntry 2 }
ospfImportAsExtern OBJECT-
SYNTAX INTEGER {
importExternal (1),
importNoExternal (2),
importNssa (3)
}
MAX-ACCESS read-
STATUS
"The area's support for importing AS
link- state advertisements."
"OSPF Version 2, Appendix C.2 Area parameters
DEFVAL { importExternal }
::= { ospfAreaEntry 3 }
ospfSpfRuns OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times that the intra-area
table has been calculated using this area'
link-state database. This is typically
using Dijkstra's algorithm."
Baker & Coltun Standards Track [Page 19]
RFC 1850 OSPF MIB November 1995
::= { ospfAreaEntry 4 }
ospfAreaBdrRtrCount OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"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 }
ospfAsBdrRtrCount OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"The total number of Autonomous System
routers reachable within this area. This
initially zero, and is calculated in each
Pass."
::= { ospfAreaEntry 6 }
ospfAreaLsaCount OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"The total number of link-state
in this area's link-state database,
AS External LSA's."
::= { ospfAreaEntry 7 }
ospfAreaLsaCksumSum OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The 32-bit unsigned sum of the link-state ad
vertisements' LS checksums contained in
area's link-state database. This sum
external (LS type 5) link-state advertisements
The sum can be used to determine if there
been a change in a router's link state data
base, and to compare the link-state database
Baker & Coltun Standards Track [Page 20]
RFC 1850 OSPF MIB November 1995
two routers."
DEFVAL { 0 }
::= { ospfAreaEntry 8 }
ospfAreaSummary OBJECT-
SYNTAX INTEGER {
noAreaSummary (1),
sendAreaSummary (2)
}
MAX-ACCESS read-
STATUS
"The variable ospfAreaSummary controls the im
port of summary LSAs into stub areas. It
no effect on other areas
If it is noAreaSummary, the router will
originate nor propagate summary LSAs into
stub area. It will rely entirely on its de
fault route
If it is sendAreaSummary, the router will
summarize and propagate summary LSAs."
DEFVAL { noAreaSummary }
::= { ospfAreaEntry 9 }
ospfAreaStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This variable displays the status of the en
try. Setting it to 'invalid' has the effect
rendering it inoperative. The internal
(row removal) is implementation dependent."
::= { ospfAreaEntry 10 }
-- OSPF Area Default Metric
-- The OSPF Area Default Metric Table describes the
-- that a default Area Border Router will advertise into
-- Stub area
ospfStubAreaTable OBJECT-
SYNTAX SEQUENCE OF
Baker & Coltun Standards Track [Page 21]
RFC 1850 OSPF MIB November 1995
MAX-ACCESS not-
STATUS
"The set of metrics that will be advertised
a default Area Border Router into a stub area."
"OSPF Version 2, Appendix C.2, Area Parameters
::= { ospf 3 }
ospfStubAreaEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The metric for a given Type of Service
will be advertised by a default Area
Router into a stub area."
"OSPF Version 2, Appendix C.2, Area Parameters
INDEX { ospfStubAreaId, ospfStubTOS }
::= { ospfStubAreaTable 1 }
OspfStubAreaEntry ::=
SEQUENCE {
AreaID
TOSType
BigMetric
RowStatus
}
ospfStubAreaId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The 32 bit identifier for the Stub Area.
creation, this can be derived from the in
stance."
::= { ospfStubAreaEntry 1 }
Baker & Coltun Standards Track [Page 22]
RFC 1850 OSPF MIB November 1995
ospfStubTOS OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Type of Service associated with
metric. On creation, this can be derived
the instance."
::= { ospfStubAreaEntry 2 }
ospfStubMetric OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The metric value applied at the indicated
of service. By default, this equals the
metric at the type of service among the inter
faces to other areas."
::= { ospfStubAreaEntry 3 }
ospfStubStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This variable displays the status of the en
try. Setting it to 'invalid' has the effect
rendering it inoperative. The internal
(row removal) is implementation dependent."
::= { ospfStubAreaEntry 4 }
ospfStubMetricType OBJECT-
SYNTAX INTEGER {
ospfMetric (1), -- OSPF
comparableCost (2), -- external type 1
nonComparable (3) -- external type 2
}
MAX-ACCESS read-
STATUS
"This variable displays the type of metric ad
vertised as a default route."
DEFVAL { ospfMetric }
::= { ospfStubAreaEntry 5 }
Baker & Coltun Standards Track [Page 23]
RFC 1850 OSPF MIB November 1995
-- OSPF Link State
-- The Link State Database contains the Link
-- Advertisements from throughout the areas that
-- device is attached to
ospfLsdbTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The OSPF Process's Link State Database."
"OSPF Version 2, Section 12 Link State Adver
tisements
::= { ospf 4 }
ospfLsdbEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A single Link State Advertisement."
INDEX { ospfLsdbAreaId, ospfLsdbType
ospfLsdbLsid, ospfLsdbRouterId }
::= { ospfLsdbTable 1 }
OspfLsdbEntry ::=
SEQUENCE {
AreaID
INTEGER
IpAddress
RouterID
Integer32,
Integer32,
Integer32,
OCTET
}
Baker & Coltun Standards Track [Page 24]
RFC 1850 OSPF MIB November 1995
ospfLsdbAreaId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The 32 bit identifier of the Area from
the LSA was received."
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfLsdbEntry 1 }
-- External Link State Advertisements are
-- for backward compatibility, but should be displayed
-- the ospfExtLsdbTable rather than here
ospfLsdbType OBJECT-
SYNTAX INTEGER {
routerLink (1),
networkLink (2),
summaryLink (3),
asSummaryLink (4),
asExternalLink (5), -- but see
multicastLink (6),
nssaExternalLink (7)
}
MAX-ACCESS read-
STATUS
"The type of the link state advertisement
Each link state type has a separate advertise
ment format."
"OSPF Version 2, Appendix A.4.1 The Link
Advertisement header
::= { ospfLsdbEntry 2 }
ospfLsdbLsid OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Link State ID is an LS Type Specific
containing either a Router ID or an IP Address
it identifies the piece of the routing
that is being described by the advertisement."
"OSPF Version 2, Section 12.1.4 Link State ID
::= { ospfLsdbEntry 3 }
Baker & Coltun Standards Track [Page 25]
RFC 1850 OSPF MIB November 1995
ospfLsdbRouterId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The 32 bit number that uniquely identifies
originating router in the Autonomous System."
"OSPF Version 2, Appendix C.1 Global parameters
::= { ospfLsdbEntry 4 }
-- Note that the OSPF Sequence Number is a 32 bit
-- integer. It starts with the value '80000001'h
-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'
-- Thus, a typical sequence number will be very negative
ospfLsdbSequence OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The sequence number field is a signed 32-
integer. It is used to detect old and dupli
cate link state advertisements. The space
sequence numbers is linearly ordered.
larger the sequence number the more recent
advertisement."
"OSPF Version 2, Section 12.1.6 LS
number
::= { ospfLsdbEntry 5 }
ospfLsdbAge OBJECT-
SYNTAX Integer32 -- Should be 0..
MAX-ACCESS read-
STATUS
"This field is the age of the link state adver
tisement in seconds."
"OSPF Version 2, Section 12.1.1 LS age
::= { ospfLsdbEntry 6 }
ospfLsdbChecksum OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
Baker & Coltun Standards Track [Page 26]
RFC 1850 OSPF MIB November 1995
"This field is the checksum of the
contents of the advertisement, excepting
age field. The age field is excepted so
an advertisement's age can be
without updating the checksum. The
used is the same that is used for ISO connec
tionless datagrams; it is commonly referred
as the Fletcher checksum."
"OSPF Version 2, Section 12.1.7 LS checksum
::= { ospfLsdbEntry 7 }
ospfLsdbAdvertisement OBJECT-
SYNTAX OCTET STRING (SIZE (1..65535))
MAX-ACCESS read-
STATUS
"The entire Link State Advertisement,
its header."
"OSPF Version 2, Section 12 Link State Adver
tisements
::= { ospfLsdbEntry 8 }
-- Address Range
-- The Address Range Table acts as an adjunct to the
-- Table; It describes those Address Range Summaries
-- are configured to be propagated from an Area to
-- the amount of information about it which is known
-- its borders
ospfAreaRangeTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A range if IP addresses specified by an
address/IP network mask pair. For example
class B address range of X.X.X.X with a
mask of 255.255.0.0 includes all IP
from X.X.0.0 to X.X.255.255"
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospf 5 }
Baker & Coltun Standards Track [Page 27]
RFC 1850 OSPF MIB November 1995
ospfAreaRangeEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A range if IP addresses specified by an
address/IP network mask pair. For example
class B address range of X.X.X.X with a
mask of 255.255.0.0 includes all IP
from X.X.0.0 to X.X.255.255"
"OSPF Version 2, Appendix C.2 Area parameters
INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet }
::= { ospfAreaRangeTable 1 }
OspfAreaRangeEntry ::=
SEQUENCE {
AreaID
IpAddress
IpAddress
RowStatus
}
ospfAreaRangeAreaId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Area the Address Range is to be
within."
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfAreaRangeEntry 1 }
ospfAreaRangeNet OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP Address of the Net or Subnet
by the range."
Baker & Coltun Standards Track [Page 28]
RFC 1850 OSPF MIB November 1995
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfAreaRangeEntry 2 }
ospfAreaRangeMask OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Subnet Mask that pertains to the Net
Subnet."
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfAreaRangeEntry 3 }
ospfAreaRangeStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This variable displays the status of the en
try. Setting it to 'invalid' has the effect
rendering it inoperative. The internal
(row removal) is implementation dependent."
::= { ospfAreaRangeEntry 4 }
ospfAreaRangeEffect OBJECT-
SYNTAX INTEGER {
advertiseMatching (1),
doNotAdvertiseMatching (2)
}
MAX-ACCESS read-
STATUS
"Subnets subsumed by ranges either trigger
advertisement of the indicated summary (adver
tiseMatching), or result in the subnet's
being advertised at all outside the area."
DEFVAL { advertiseMatching }
::= { ospfAreaRangeEntry 5 }
-- OSPF Host
-- The Host/Metric Table indicates what hosts are
Baker & Coltun Standards Track [Page 29]
RFC 1850 OSPF MIB November 1995
-- attached to the Router, and what metrics and types
-- service should be advertised for them
ospfHostTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The list of Hosts, and their metrics, that
router will advertise as host routes."
"OSPF Version 2, Appendix C.6 Host route param
eters
::= { ospf 6 }
ospfHostEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A metric to be advertised, for a given type
service, when a given host is reachable."
INDEX { ospfHostIpAddress, ospfHostTOS }
::= { ospfHostTable 1 }
OspfHostEntry ::=
SEQUENCE {
IpAddress
TOSType
Metric
RowStatus
}
ospfHostIpAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP Address of the Host."
"OSPF Version 2, Appendix C.6 Host route parame
Baker & Coltun Standards Track [Page 30]
RFC 1850 OSPF MIB November 1995
ters
::= { ospfHostEntry 1 }
ospfHostTOS OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Type of Service of the route being config
ured."
"OSPF Version 2, Appendix C.6 Host route parame
ters
::= { ospfHostEntry 2 }
ospfHostMetric OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Metric to be advertised."
"OSPF Version 2, Appendix C.6 Host route parame
ters
::= { ospfHostEntry 3 }
ospfHostStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This variable displays the status of the en
try. Setting it to 'invalid' has the effect
rendering it inoperative. The internal
(row removal) is implementation dependent."
::= { ospfHostEntry 4 }
ospfHostAreaID OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Area the Host Entry is to be found within
By default, the area that a subsuming OSPF in
terface is in, or 0.0.0.0"
Baker & Coltun Standards Track [Page 31]
RFC 1850 OSPF MIB November 1995
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfHostEntry 5 }
-- OSPF Interface
-- The OSPF Interface Table augments the
-- with OSPF specific information
ospfIfTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The OSPF Interface Table describes the inter
faces from the viewpoint of OSPF."
"OSPF Version 2, Appendix C.3 Router
parameters
::= { ospf 7 }
ospfIfEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The OSPF Interface Entry describes one inter
face from the viewpoint of OSPF."
INDEX { ospfIfIpAddress, ospfAddressLessIf }
::= { ospfIfTable 1 }
OspfIfEntry ::=
SEQUENCE {
IpAddress
Integer32,
AreaID
INTEGER
Status
DesignatedRouterPriority
Baker & Coltun Standards Track [Page 32]
RFC 1850 OSPF MIB November 1995
UpToMaxAge
UpToMaxAge
HelloRange
PositiveInteger
PositiveInteger
INTEGER
IpAddress
IpAddress
Counter32,
INTEGER
OCTET STRING
RowStatus
INTEGER
}
ospfIfIpAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP address of this OSPF interface."
::= { ospfIfEntry 1 }
ospfAddressLessIf OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"For the purpose of easing the instancing
addressed and addressless interfaces;
variable takes the value 0 on interfaces
IP Addresses, and the corresponding value
ifIndex for interfaces having no IP Address."
::= { ospfIfEntry 2 }
Baker & Coltun Standards Track [Page 33]
RFC 1850 OSPF MIB November 1995
ospfIfAreaId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A 32-bit integer uniquely identifying the
to which the interface connects. Area
0.0.0.0 is used for the OSPF backbone."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 3 }
ospfIfType OBJECT-
SYNTAX INTEGER {
broadcast (1),
nbma (2),
pointToPoint (3),
pointToMultipoint (5)
}
MAX-ACCESS read-
STATUS
"The OSPF interface type
By way of a default, this field may be
from the corresponding value of ifType. Broad
cast LANs, such as Ethernet and IEEE 802.5,
take the value 'broadcast', X.25 and
technologies take the value 'nbma', and
that are definitively point to point take
value 'pointToPoint'."
::= { ospfIfEntry 4 }
ospfIfAdminStat OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The OSPF interface's administrative status
The value formed on the interface, and the in
terface will be advertised as an internal
to some area. The value 'disabled'
that the interface is external to OSPF."
DEFVAL { enabled }
::= { ospfIfEntry 5 }
ospfIfRtrPriority OBJECT-
SYNTAX
Baker & Coltun Standards Track [Page 34]
RFC 1850 OSPF MIB November 1995
MAX-ACCESS read-
STATUS
"The priority of this interface. Used
multi-access networks, this field is used
the designated router election algorithm.
value 0 signifies that the router is not eligi
ble to become the designated router on
particular network. In the event of a tie
this value, routers will use their Router ID
a tie breaker."
DEFVAL { 1 }
::= { ospfIfEntry 6 }
ospfIfTransitDelay OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The estimated number of seconds it takes
transmit a link state update packet over
interface."
DEFVAL { 1 }
::= { ospfIfEntry 7 }
ospfIfRetransInterval OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of seconds between link-state ad
vertisement retransmissions, for
belonging to this interface. This value
also used when retransmitting database descrip
tion and link-state request packets."
DEFVAL { 5 }
::= { ospfIfEntry 8 }
ospfIfHelloInterval OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The length of time, in seconds, between
Hello packets that the router sends on the in
Baker & Coltun Standards Track [Page 35]
RFC 1850 OSPF MIB November 1995
terface. This value must be the same for
routers attached to a common network."
DEFVAL { 10 }
::= { ospfIfEntry 9 }
ospfIfRtrDeadInterval OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of seconds that a router's
packets have not been seen before it's neigh
bors declare the router down. This should
some multiple of the Hello interval.
value must be the same for all routers
to a common network."
DEFVAL { 40 }
::= { ospfIfEntry 10 }
ospfIfPollInterval OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The larger time interval, in seconds,
the Hello packets sent to an inactive non
broadcast multi- access neighbor."
DEFVAL { 120 }
::= { ospfIfEntry 11 }
ospfIfState OBJECT-
SYNTAX INTEGER {
down (1),
loopback (2),
waiting (3),
pointToPoint (4),
designatedRouter (5),
backupDesignatedRouter (6),
otherDesignatedRouter (7)
}
MAX-ACCESS read-
STATUS
"The OSPF Interface State."
DEFVAL { down }
Baker & Coltun Standards Track [Page 36]
RFC 1850 OSPF MIB November 1995
::= { ospfIfEntry 12 }
ospfIfDesignatedRouter OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP Address of the Designated Router."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 13 }
ospfIfBackupDesignatedRouter OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP Address of the Backup
Router."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 14 }
ospfIfEvents OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times this OSPF interface
changed its state, or an error has occurred."
::= { ospfIfEntry 15 }
ospfIfAuthKey OBJECT-
SYNTAX OCTET STRING (SIZE (0..256))
MAX-ACCESS read-
STATUS
"The Authentication Key. If the Area's Author
ization Type is simplePassword, and the
length is shorter than 8 octets, the agent
left adjust and zero fill to 8 octets
Note that unauthenticated interfaces need
authentication key, and simple password authen
tication cannot use a key of more than 8 oc
tets. Larger keys are useful only with authen
tication mechanisms not specified in this docu
Baker & Coltun Standards Track [Page 37]
RFC 1850 OSPF MIB November 1995
ment
When read, ospfIfAuthKey always returns an Oc
tet String of length zero."
"OSPF Version 2, Section 9 The Interface
Structure
DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
::= { ospfIfEntry 16 }
ospfIfStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This variable displays the status of the en
try. Setting it to 'invalid' has the effect
rendering it inoperative. The internal
(row removal) is implementation dependent."
::= { ospfIfEntry 17 }
ospfIfMulticastForwarding OBJECT-
SYNTAX INTEGER {
blocked (1), -- no multicast
multicast (2), -- using multicast
unicast (3) -- to each OSPF
}
MAX-ACCESS read-
STATUS
"The way multicasts should forwarded on
interface; not forwarded, forwarded as
link multicasts, or forwarded as data link uni
casts. Data link multicasting is not meaning
ful on point to point and NBMA interfaces,
setting ospfMulticastForwarding to 0 effective
ly disables all multicast forwarding."
DEFVAL { blocked }
::= { ospfIfEntry 18 }
ospfIfDemand OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Indicates whether Demand OSPF procedures (hel
Baker & Coltun Standards Track [Page 38]
RFC 1850 OSPF MIB November 1995
lo supression to FULL neighbors and setting
DoNotAge flag on proogated LSAs) should be per
formed on this interface."
DEFVAL { false }
::= { ospfIfEntry 19 }
ospfIfAuthType OBJECT-
SYNTAX INTEGER (0..255)
-- none (0),
-- simplePassword (1)
-- md5 (2)
-- reserved for specification by IANA (> 2)
MAX-ACCESS read-
STATUS
"The authentication type specified for an in
terface. Additional authentication types
be assigned locally."
"OSPF Version 2, Appendix E Authentication
DEFVAL { 0 } -- no authentication, by
::= { ospfIfEntry 20 }
-- OSPF Interface Metric
-- The Metric Table describes the metrics to be
-- for a specified interface at the various types of service
-- As such, this table is an adjunct of the OSPF
-- Table
-- Types of service, as defined by RFC 791, have the
-- to request low delay, high bandwidth, or reliable linkage
-- For the purposes of this specification, the measure
--
-- Metric = 10^8 /
-- is the default value. For multiple link interfaces,
-- that ifSpeed is the sum of the individual link speeds
-- This yields a number having the following typical values
-- Network Type/bit rate
-- >= 100 MBPS 1
-- Ethernet/802.3 10
Baker & Coltun Standards Track [Page 39]
RFC 1850 OSPF MIB November 1995
-- 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)
ospfIfMetricTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The TOS metrics for a non-virtual
identified by the interface index."
"OSPF Version 2, Appendix C.3 Router
parameters
::= { ospf 8 }
ospfIfMetricEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A particular TOS metric for a non-virtual in
terface identified by the interface index."
"OSPF Version 2, Appendix C.3 Router
parameters
INDEX { ospfIfMetricIpAddress
ospfIfMetricAddressLessIf
ospfIfMetricTOS }
::= { ospfIfMetricTable 1 }
OspfIfMetricEntry ::=
SEQUENCE {
IpAddress
Integer32,
TOSType
Metric
Baker & Coltun Standards Track [Page 40]
RFC 1850 OSPF MIB November 1995
}
ospfIfMetricIpAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP address of this OSPF interface. On
creation, this can be derived from the in
stance."
::= { ospfIfMetricEntry 1 }
ospfIfMetricAddressLessIf OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"For the purpose of easing the instancing
addressed and addressless interfaces;
variable takes the value 0 on interfaces
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-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of service metric being referenced
On row creation, this can be derived from
instance."
::= { ospfIfMetricEntry 3 }
ospfIfMetricValue OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The metric of using this type of service
this interface. The default value of the TOS 0
Metric is 10^8 / ifSpeed."
::= { ospfIfMetricEntry 4 }
ospfIfMetricStatus OBJECT-
Baker & Coltun Standards Track [Page 41]
RFC 1850 OSPF MIB November 1995
SYNTAX
MAX-ACCESS read-
STATUS
"This variable displays the status of the en
try. Setting it to 'invalid' has the effect
rendering it inoperative. The internal
(row removal) is implementation dependent."
::= { ospfIfMetricEntry 5 }
-- OSPF Virtual Interface
-- The Virtual Interface Table describes the
-- links that the OSPF Process is configured
-- carry on
ospfVirtIfTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Information about this router's virtual inter
faces."
"OSPF Version 2, Appendix C.4 Virtual
parameters
::= { ospf 9 }
ospfVirtIfEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a single Virtual Interface."
INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor }
::= { ospfVirtIfTable 1 }
OspfVirtIfEntry ::=
SEQUENCE {
AreaID
RouterID
UpToMaxAge
Baker & Coltun Standards Track [Page 42]
RFC 1850 OSPF MIB November 1995
UpToMaxAge
HelloRange
PositiveInteger
INTEGER
Counter32,
INTEGER
OCTET STRING
}
ospfVirtIfAreaId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Transit Area that the Virtual
traverses. By definition, this is not 0.0.0.0"
::= { ospfVirtIfEntry 1 }
ospfVirtIfNeighbor OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Router ID of the Virtual Neighbor."
::= { ospfVirtIfEntry 2 }
ospfVirtIfTransitDelay OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The estimated number of seconds it takes
transmit a link- state update packet over
interface."
DEFVAL { 1 }
::= { ospfVirtIfEntry 3 }
Baker & Coltun Standards Track [Page 43]
RFC 1850 OSPF MIB November 1995
ospfVirtIfRetransInterval OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of seconds between link-state ad
vertisement retransmissions, for
belonging to this interface. This value
also used when retransmitting database descrip
tion and link-state request packets.
value should be well over the expected round
trip time."
DEFVAL { 5 }
::= { ospfVirtIfEntry 4 }
ospfVirtIfHelloInterval OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The length of time, in seconds, between
Hello packets that the router sends on the in
terface. This value must be the same for
virtual neighbor."
DEFVAL { 10 }
::= { ospfVirtIfEntry 5 }
ospfVirtIfRtrDeadInterval OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The number of seconds that a router's
packets have not been seen before it's neigh
bors declare the router down. This should
some multiple of the Hello interval.
value must be the same for the virtual neigh
bor."
DEFVAL { 60 }
::= { ospfVirtIfEntry 6 }
ospfVirtIfState OBJECT-
SYNTAX INTEGER {
down (1), -- these use the same
pointToPoint (4) -- as the
Baker & Coltun Standards Track [Page 44]
RFC 1850 OSPF MIB November 1995
}
MAX-ACCESS read-
STATUS
"OSPF virtual interface states."
DEFVAL { down }
::= { ospfVirtIfEntry 7 }
ospfVirtIfEvents OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of state changes or error events
this Virtual Link
::= { ospfVirtIfEntry 8 }
ospfVirtIfAuthKey OBJECT-
SYNTAX OCTET STRING (SIZE(0..256))
MAX-ACCESS read-
STATUS
"If Authentication Type is simplePassword,
device will left adjust and zero fill to 8 oc
tets
Note that unauthenticated interfaces need
authentication key, and simple password authen
tication cannot use a key of more than 8 oc
tets. Larger keys are useful only with authen
tication mechanisms not specified in this docu
ment
When read, ospfVifAuthKey always returns
string of length zero."
"OSPF Version 2, Section 9 The Interface
Structure
DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
::= { ospfVirtIfEntry 9 }
ospfVirtIfStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Baker & Coltun Standards Track [Page 45]
RFC 1850 OSPF MIB November 1995
"This variable displays the status of the en
try. Setting it to 'invalid' has the effect
rendering it inoperative. The internal
(row removal) is implementation dependent."
::= { ospfVirtIfEntry 10 }
ospfVirtIfAuthType OBJECT-
SYNTAX INTEGER (0..255)
-- none (0),
-- simplePassword (1)
-- md5 (2)
-- reserved for specification by IANA (> 2)
MAX-ACCESS read-
STATUS
"The authentication type specified for a virtu
al interface. Additional authentication
may be assigned locally."
"OSPF Version 2, Appendix E Authentication
DEFVAL { 0 } -- no authentication, by
::= { ospfVirtIfEntry 11 }
-- OSPF Neighbor
-- The OSPF Neighbor Table describes all neighbors
-- the locality of the subject router
ospfNbrTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table of non-virtual neighbor information."
"OSPF Version 2, Section 10 The Neighbor
Structure
::= { ospf 10 }
ospfNbrEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
Baker & Coltun Standards Track [Page 46]
RFC 1850 OSPF MIB November 1995
"The information regarding a single neighbor."
"OSPF Version 2, Section 10 The Neighbor
Structure
INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex }
::= { ospfNbrTable 1 }
OspfNbrEntry ::=
SEQUENCE {
IpAddress
InterfaceIndex
RouterID
Integer32,
DesignatedRouterPriority
INTEGER
Counter32,
Gauge32,
RowStatus
INTEGER
}
ospfNbrIpAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP address this neighbor is using in
IP Source Address. Note that, on
links, this will not be 0.0.0.0, but the ad
dress of another of the neighbor's interfaces."
::= { ospfNbrEntry 1 }
ospfNbrAddressLessIndex OBJECT-
SYNTAX
MAX-ACCESS read-
Baker & Coltun Standards Track [Page 47]
RFC 1850 OSPF MIB November 1995
STATUS
"On an interface having an IP Address, zero
On addressless interfaces, the
value of ifIndex in the Internet Standard MIB
On row creation, this can be derived from
instance."
::= { ospfNbrEntry 2 }
ospfNbrRtrId OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A 32-bit integer (represented as a type IpAd
dress) uniquely identifying the
router in the Autonomous System."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfNbrEntry 3 }
ospfNbrOptions OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"A Bit Mask corresponding to the neighbor's op
tions field
Bit 0, if set, indicates that the system
operate on Type of Service metrics other
TOS 0. If zero, the neighbor will ignore
metrics except the TOS 0 metric
Bit 1, if set, indicates that the
area accepts and operates on external informa
tion; if zero, it is a stub area
Bit 2, if set, indicates that the system is ca
pable of routing IP Multicast datagrams; i.e.,
that it implements the Multicast Extensions
OSPF
Bit 3, if set, indicates that the
area is an NSSA. These areas are capable
carrying type 7 