As per Relevance of the word reference, we have this rfc below:
Network Working Group F.
Request for Comments: 1248
R.
Computer Science
July 1991
OSPF Version 2 Management Information
Status of this
This RFC specifies an IAB standards track protocol for the
community, and requests discussion and suggestions for improvements
Please refer to the current edition of the "IAB Official
Standards" for the standardization state and status of this protocol
Distribution of this memo is unlimited
Table of
1. Abstract ............................................. 2
2. The Network Management Framework...................... 2
3. Objects .............................................. 2
3.1 Format of Definitions ............................... 3
4. Overview ............................................. 3
4.1 Textual Conventions ................................. 3
4.2 Structure of MIB .................................... 3
4.2.1 General Variables ................................. 4
4.2.2 Area Data Structure and Area Stub Metric Table .... 4
4.2.3 Link State Database ............................... 4
4.2.4 Address Table and Host Tables ..................... 4
4.2.5 Interface and Interface Metric Tables ............. 4
4.2.6 Virtual Interface Table ........................... 4
4.2.7 Neighbor and Virtual Neighbor Tables .............. 4
4.3 Conceptual Row Creation ............................. 5
4.4 Default Configuration ............................... 5
5. Definitions .......................................... 7
5.1 OSPF General Variables .............................. 8
5.2 OSPF Area Data Structure ............................ 11
5.3 OSPF Area Default Metric Table ...................... 14
5.4 OSPF Link State Database ............................ 16
5.5 OSPF Address Range Table ............................ 19
5.6 OSPF Host Table ..................................... 21
5.7 OSPF Interface Table ................................ 23
5.8 OSPF Interface Metric Table ......................... 28
5.9 OSPF Virtual Interface Table ........................ 31
5.10 OSPF Neighbor Table ................................ 34
5.11 OSPF Virtual Neighbor Table ........................ 38
6. Acknowledgements ..................................... 40
Baker & Coltun [Page 1]
RFC 1248 OSPF Version 2 MIB July 1991
7. References ........................................... 40
8. Security Considerations............................... 41
9. Authors' Addresses.................................... 42
1.
This memo defines an experimental portion of the
Information Base (MIB) for use with network management protocols
TCP/IP-based internets. In particular, it defines objects
managing OSPF Version 2.
2. The Network Management
The Internet-standard Network Management Framework consists of
components. They are
RFC 1155 which defines the SMI, the mechanisms used for
and naming objects for the purpose of management. RFC 1212
defines a more concise description mechanism, which is
consistent with the SMI
RFC 1156 which defines MIB-I, the core set of managed objects
the Internet suite of protocols. RFC 1213, defines MIB-II,
evolution of MIB-I based on implementation experience and
operational requirements
RFC 1157 which defines the SNMP, the protocol used for
access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
3.
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) [7]
defined in the SMI. In particular, each object has a name, a syntax
and an encoding. The name is an object identifier,
administratively assigned name, which specifies an object type.
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, to also refer to the object type
The syntax of an object type defines the abstract data
corresponding to that object type. The ASN.1 language is used
this purpose. However, the SMI [3] purposely restricts the ASN.1
Baker & Coltun [Page 2]
RFC 1248 OSPF Version 2 MIB July 1991
constructs which may be used. These restrictions are explicitly
for simplicity
The encoding of an object type is simply how that object type
represented using the object type's syntax. Implicitly tied to
notion of an object type's syntax and encoding is how the object
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
3.1. Format of
Section 5 contains contains the specification of all object
contained in this MIB module. The object types are defined using
conventions defined in the SMI, as amended by the
specified in [9].
4.
4.1. 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
TruthValue, Status, Validation, PositiveInteger, HelloRange
UpToMaxAge, InterfaceIndex, and DesignatedRouterPriority
4.2. Structure of
The MIB is composed of the following sections
General
Area Data
Area Stub Metric
Link State
Address Range
Baker & Coltun [Page 3]
RFC 1248 OSPF Version 2 MIB July 1991
Host
Interface
Interface Metric
Virtual Interface
Neighbor
Virtual Neighbor
4.2.1. General
The General Variables are about what they sound like; variables
are global to the OSPF Process
4.2.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).
4.2.3. Link State
The Link State Database is provided primarily to provide
information for network debugging
4.2.4. Address Table and Host
The Address Range Table and Host Table are provided to
configured Network Summary and Host Route information
4.2.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
4.2.6. Virtual Interface
Likewise, the Virtual Interface Table describe virtual links to
OSPF Process
4.2.7. Neighbor and Virtual Neighbor
The Neighbor Table and the Virtual Neighbor Table describe
neighbors to the OSPF Process
Baker & Coltun [Page 4]
RFC 1248 OSPF Version 2 MIB July 1991
4.3. Conceptual Row
For the benefit of row-creation in "conceptual" (see [9]) tables
DEFVAL (Default Value) clauses are included in the definitions
section 5, 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
Counter or Gauge
For those objects not having a DEFVAL clause, both
stations and agents should heed the Robustness Principle of
Internet (see RFC-791):
"be liberal in what you accept, conservative in
you 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
4.4. 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
Baker & Coltun [Page 5]
RFC 1248 OSPF Version 2 MIB July 1991
- ifSpeed is estimated by the interface
- The OSPF Process automatically discovers all
Interfaces and creates corresponding OSPF
- The TOS 0 metrics are autonomously derived
- The OSPF Process automatically creates the
required for the
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 will be neither an Area Border Router
an Autonomous System Border Router
- Every IP Interface, with or without an address,
be 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
Baker & Coltun [Page 6]
RFC 1248 OSPF Version 2 MIB July 1991
- no addresses will be
- Metrics, being a measure of bit duration,
unambiguous and intelligent
- No Virtual Links will be configured
5.
RFC1248-MIB DEFINITIONS ::=
experimental, Counter, Gauge,
FROM RFC1155-
OBJECT-
FROM RFC-1212;
-- This MIB module uses the extended OBJECT-TYPE macro
-- defined in [9].
ospf OBJECT IDENTIFIER ::= { standard-mib 13 }
-- 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 ::=
-- The Router ID, in OSPF, has the same format as an IP Address
-- but identifies the router independent of its IP Address
RouterID ::=
-- The OSPF Metric is defined as an unsigned value in the
Metric ::= INTEGER (1..'FFFF'h
BigMetric ::= INTEGER (1..'FFFFFF'h
-- Boolean
TruthValue ::= INTEGER { true (1), false (2) }
-- Status
Status ::= INTEGER { enabled (1), disabled (2) }
Baker & Coltun [Page 7]
RFC 1248 OSPF Version 2 MIB July 1991
-- Row Creation/Deletion
Validation ::= INTEGER { valid (1), invalid (2) }
-- Time Durations measured in
PositiveInteger ::= INTEGER (1..'FFFFFFFF'h
HelloRange ::= INTEGER (1..'FFFF'h
UpToMaxAge ::= INTEGER (1..3600)
-- The range of ifIndex, i.e. (1..ifNumber
InterfaceIndex ::=
-- Potential Priorities for the Designated Router
DesignatedRouterPriority ::= INTEGER (0..'FF'h
-- Type of Service is defined as a mapping to the IP Type
-- Service Flags as defined in the Router
-- Document
--
-- D => Low Delay R => Reliable
-- T => High
-- D T R TOS D T R
-- 0 0 0 => 0 0 0 1 => 4
-- 0 1 0 => 8 0 1 1 => 12
-- 1 0 0 => 16 1 0 1 => 20
-- 1 1 0 => 24 1 1 1 => 28
-- The remaining values are left for future definition
TOSType ::= INTEGER (0..31)
-- OSPF General
-- These parameters apply globally to the Router'
-- OSPF Process
ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 }
ospfRouterId OBJECT-
SYNTAX
ACCESS read-
STATUS
"A 32-bit integer uniquely identifying the router
Baker & Coltun [Page 8]
RFC 1248 OSPF Version 2 MIB July 1991
the Autonomous System
By convention, to ensure uniqueness, this
default to the value of one of the router's
interface addresses."
"OSPF Version 2, C.1 Global parameters
::= { ospfGeneralGroup 1 }
ospfAdminStat OBJECT-
SYNTAX
ACCESS read-
STATUS
"The administrative status of OSPF in the router.
value 'enabled' denotes that the OSPF Process is
on at least one interface; 'disabled' disables it
all interfaces."
::= { ospfGeneralGroup 2 }
ospfVersionNumber OBJECT-
SYNTAX INTEGER { version2 (2) }
ACCESS read-
STATUS
"The current version number of the OSPF protocol is 2."
"OSPF Version 2, Title
::= { ospfGeneralGroup 3 }
ospfAreaBdrRtrStatus OBJECT-
SYNTAX
ACCESS read-
STATUS
"A flag to note whether this router is an area
router."
"OSPF Version 2, Section 3 Splitting the AS into Areas
::= { ospfGeneralGroup 4 }
ospfASBdrRtrStatus OBJECT-
SYNTAX
ACCESS read-
STATUS
"A flag to note whether this router is an
System border router."
Baker & Coltun [Page 9]
RFC 1248 OSPF Version 2 MIB July 1991
"OSPF Version 2, Section 3.3 Classification of routers
::= { ospfGeneralGroup 5 }
ospfExternLSACount OBJECT-
SYNTAX
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
ACCESS read-
STATUS
"The 32-bit unsigned sum of the LS checksums of
external link-state advertisements contained in
link-state database. This sum can be used to
if there has been a change in a router's link
database, and to compare the link-state database of
routers."
::= { ospfGeneralGroup 7 }
ospfTOSSupport OBJECT-
SYNTAX
ACCESS read-
STATUS
"The router's support for type-of-service routing."
"OSPF Version 2, Appendix F.1.2 Optional TOS support
::= { ospfGeneralGroup 8 }
ospfOriginateNewLSAs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of new link-state advertisements that
been originated. This number is incremented each
the router originates a new LSA."
::= { ospfGeneralGroup 9 }
Baker & Coltun [Page 10]
RFC 1248 OSPF Version 2 MIB July 1991
ospfRxNewLSAs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of link-state advertisements
determined to be new instantiations. This number
not include newer instantiations of self-
link-state advertisements."
::= { ospfGeneralGroup 10 }
-- 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
ACCESS not-
STATUS
"Information describing the configured parameters
cumulative statistics of the router's attached areas."
"OSPF Version 2, Section 6 The Area Data Structure
::= { ospf 2 }
ospfAreaEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Information describing the configured parameters
cumulative statistics of one of the router's
areas."
INDEX { ospfAreaID }
::= { ospfAreaTable 1 }
OspfAreaEntry ::=
SEQUENCE {
AreaID
INTEGER
TruthValue
Baker & Coltun [Page 11]
RFC 1248 OSPF Version 2 MIB July 1991
Counter
Gauge
Gauge
Gauge
}
ospfAreaId OBJECT-
SYNTAX
ACCESS read-
STATUS
"A 32-bit integer uniquely identifying an area.
ID 0.0.0.0 is used for the OSPF backbone."
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfAreaEntry 1 }
ospfAuthType OBJECT-
SYNTAX
-- none (0),
-- simplePassword (1)
-- reserved for specification by IANA (> 1)
ACCESS read-
STATUS
"The authentication type specified for an area
Additional authentication types may be assigned
on a per Area basis."
"OSPF Version 2, Appendix E Authentication
DEFVAL { 0 } -- no authentication, by
::= { ospfAreaEntry 2 }
ospfImportASExtern OBJECT-
SYNTAX
ACCESS read-
STATUS
"The area's support for importing AS external link
state advertisements."
"OSPF Version 2, Appendix C.2 Area parameters
DEFVAL { true }
Baker & Coltun [Page 12]
RFC 1248 OSPF Version 2 MIB July 1991
::= { ospfAreaEntry 3 }
ospfSpfRuns OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times that the intra-area route
has been calculated using this area's link-
database. This is typically done using Dijkstra'
algorithm."
DEFVAL { 0 }
::= { ospfAreaEntry 4 }
ospfAreaBdrRtrCount OBJECT-
SYNTAX
ACCESS read-
STATUS
"The total number of area border routers
within this area. This is initially zero, and
calculated in each SPF Pass."
DEFVAL { 0 }
::= { ospfAreaEntry 5 }
ospfASBdrRtrCount OBJECT-
SYNTAX
ACCESS read-
STATUS
"The total number of Autonomous System border
reachable within this area. This is initially zero
and is calculated in each SPF Pass."
DEFVAL { 0 }
::= { ospfAreaEntry 6 }
ospfAreaLSACount OBJECT-
SYNTAX
ACCESS read-
STATUS
"The total number of link-state advertisements in
area's link-state database, excluding AS
LSA's."
DEFVAL { 0 }
::= { ospfAreaEntry 7 }
Baker & Coltun [Page 13]
RFC 1248 OSPF Version 2 MIB July 1991
ospfAreaLSACksumSum OBJECT-
SYNTAX
ACCESS read-
STATUS
"The 32-bit unsigned sum of the link-
advertisements' LS checksums contained in this area'
link-state database. This sum excludes external (
type 5) link-state advertisements. The sum can be
to determine if there has been a change in a router'
link state database, and to compare the link-
database of two routers."
DEFVAL { 0 }
::= { ospfAreaEntry 8 }
-- 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
ACCESS not-
STATUS
"The set of metrics that will be advertised by
default Area Border Router into a stub area."
"OSPF Version 2, Appendix C.2, Area Parameters
::= { ospf 3 }
ospfStubAreaEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"The metric for a given Type of Service that will
advertised by a default Area Border Router into a
area."
"OSPF Version 2, Appendix C.2, Area Parameters
INDEX { ospfStubAreaID, ospfStubTOS }
::= { ospfStubAreaTable 1 }
Baker & Coltun [Page 14]
RFC 1248 OSPF Version 2 MIB July 1991
OspfStubAreaEntry ::=
SEQUENCE {
AreaID
TOSType
BigMetric
}
ospfStubAreaID OBJECT-
SYNTAX
ACCESS read-
STATUS
"The 32 bit identifier for the Stub Area. On creation
this can be derived from the instance."
::= { ospfStubAreaEntry 1 }
ospfStubTOS OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Type of Service associated with the metric.
creation, this can be derived from the instance."
::= { ospfStubAreaEntry 2 }
ospfStubMetric OBJECT-
SYNTAX
ACCESS read-
STATUS
"The metric value applied at the indicated type
service. By default, this equals the least metric
the type of service among the interfaces to
areas."
::= { ospfStubAreaEntry 3 }
ospfStubStatus OBJECT-
SYNTAX
ACCESS read-
STATUS
"This variable displays the validity or invalidity
Baker & Coltun [Page 15]
RFC 1248 OSPF Version 2 MIB July 1991
the entry. Setting it to 'invalid' has the effect
rendering it inoperative. The internal effect (
removal) is implementation dependent."
DEFVAL { valid }
::= { ospfStubAreaEntry 4 }
-- 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
ACCESS not-
STATUS
"The OSPF Process's Links State Database."
"OSPF Version 2, Section 12 Link State Advertisements
::= { ospf 4 }
ospfLsdbEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"A single Link State Advertisement."
INDEX { ospfLsdbAreaId, ospfLsdbType
ospfLsdbLSID, ospfLsdbRouterId }
::= { ospfLsdbTable 1 }
OspfLsdbEntry ::=
SEQUENCE {
AreaID
INTEGER
IpAddress
RouterID
INTEGER
INTEGER
Baker & Coltun [Page 16]
RFC 1248 OSPF Version 2 MIB July 1991
INTEGER
OCTET
}
ospfLsdbAreaId OBJECT-
SYNTAX
ACCESS read-
STATUS
"The 32 bit identifier of the Area from which the
was received."
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfLsdbEntry 1 }
ospfLsdbType OBJECT-
SYNTAX INTEGER {
routerLink (1),
networkLink (2),
summaryLink (3),
asSummaryLink (4),
asExternalLink (5)
}
ACCESS read-
STATUS
"The type of the link state advertisement. Each
state type has a separate advertisement format."
"OSPF Version 2, Appendix A.4.1 The Link
Advertisement header
::= { ospfLsdbEntry 2 }
ospfLsdbLSID OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Link State ID is an LS Type Specific
containing either a Router ID or an IP Address;
identifies the piece of the routing domain that
being described by the advertisement."
"OSPF Version 2, Section 12.1.4 Link State ID
::= { ospfLsdbEntry 3 }
Baker & Coltun [Page 17]
RFC 1248 OSPF Version 2 MIB July 1991
ospfLsdbRouterId OBJECT-
SYNTAX
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
ACCESS read-
STATUS
"The sequence number field is a signed 32-bit integer
It is used to detect old and duplicate link
advertisements. The space of sequence numbers
linearly ordered. The larger the sequence number
more recent the advertisement."
"OSPF Version 2, Section 12.1.6 LS sequence number
::= { ospfLsdbEntry 5 }
ospfLsdbAge OBJECT-
SYNTAX INTEGER -- Should be 0..
ACCESS read-
STATUS
"This field is the age of the link state
in seconds."
"OSPF Version 2, Section 12.1.1 LS age
::= { ospfLsdbEntry 6 }
ospfLsdbChecksum OBJECT-
SYNTAX
ACCESS read-
STATUS
"This field is the checksum of the complete contents
the advertisement, excepting the age field. The
Baker & Coltun [Page 18]
RFC 1248 OSPF Version 2 MIB July 1991
field is excepted so that an advertisement's age can
incremented without updating the checksum.
checksum used is the same that is used for
connectionless datagrams; it is commonly referred to
the Fletcher checksum."
"OSPF Version 2, Section 12.1.7 LS checksum
::= { ospfLsdbEntry 7 }
ospfLsdbAdvertisement OBJECT-
SYNTAX OCTET
ACCESS read-
STATUS
"The entire Link State Advertisement, including
header."
"OSPF Version 2, Section 12 Link State Advertisements
::= { 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
ACCESS not-
STATUS
"A range if IP addresses specified by an IP address/
network mask pair. For example, class B address
of X.X.X.X with a network mask of 255.255.0.0
all IP addresses from X.X.0.0 to X.X.255.255"
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospf 5 }
ospfAreaRangeEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"A range if IP addresses specified by an IP address/
Baker & Coltun [Page 19]
RFC 1248 OSPF Version 2 MIB July 1991
network mask pair. For example, class B address
of X.X.X.X with a network mask of 255.255.0.0
all IP addresses 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
}
ospfAreaRangeAreaID OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Area the Address Range is to be found within."
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfAreaRangeEntry 1 }
ospfAreaRangeNet OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP Address of the Net or Subnet indicated by
range."
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfAreaRangeEntry 2 }
ospfAreaRangeMask OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Subnet Mask that pertains to the Net or Subnet."
Baker & Coltun [Page 20]
RFC 1248 OSPF Version 2 MIB July 1991
"OSPF Version 2, Appendix C.2 Area parameters
::= { ospfAreaRangeEntry 3 }
ospfAreaRangeStatus OBJECT-
SYNTAX
ACCESS read-
STATUS
"This variable displays the validity or invalidity
the entry. Setting it to 'invalid' has the effect
rendering it inoperative. The internal effect (
removal) is implementation dependent."
DEFVAL { valid }
::= { ospfAreaRangeEntry 4 }
-- OSPF Host
-- The Host/Metric Table indicates what hosts are
-- attached to the Router, and what metrics and types
-- service should be advertised for them
ospfHostTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"The list of Hosts, and their metrics, that the
will advertise as host routes."
"OSPF Version 2, Appendix C.6 Host route parameters
::= { ospf 6 }
ospfHostEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"A metric to be advertised, for a given type of service
when a given host is reachable."
INDEX { ospfHostIpAddress, ospfHostTOS }
::= { ospfHostTable 1 }
OspfHostEntry ::=
SEQUENCE {
IpAddress
Baker & Coltun [Page 21]
RFC 1248 OSPF Version 2 MIB July 1991
TOSType
Metric
}
ospfHostIpAddress OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP Address of the Host."
"OSPF Version 2, Appendix C.6 Host route parameters
::= { ospfHostEntry 1 }
ospfHostTOS OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Type of Service of the route being configured."
"OSPF Version 2, Appendix C.6 Host route parameters
::= { ospfHostEntry 2 }
ospfHostMetric OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Metric to be advertised."
"OSPF Version 2, Appendix C.6 Host route parameters
::= { ospfHostEntry 3 }
ospfHostStatus OBJECT-
SYNTAX
ACCESS read-
STATUS
"This variable displays the validity or invalidity
the entry. Setting it to 'invalid' has the effect
rendering it inoperative. The internal effect (
removal) is implementation dependent."
DEFVAL { valid }
::= { ospfHostEntry 4 }
Baker & Coltun [Page 22]
RFC 1248 OSPF Version 2 MIB July 1991
-- OSPF Interface
-- The OSPF Interface Table augments the ifTable with
-- specific information
ospfIfTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"The OSPF Interface Table describes the interfaces
the viewpoint of OSPF."
"OSPF Version 2, Appendix C.3 Router
parameters
::= { ospf 7 }
ospfIfEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"The OSPF Interface Entry describes one interface
the viewpoint of OSPF."
INDEX { ospfIfIpAddress, ospfAddressLessIf }
::= { ospfIfTable 1 }
OspfIfEntry ::=
SEQUENCE {
IpAddress
INTEGER
AreaID
INTEGER
Status
DesignatedRouterPriority
UpToMaxAge
UpToMaxAge
HelloRange
Baker & Coltun [Page 23]
RFC 1248 OSPF Version 2 MIB July 1991
PositiveInteger
PositiveInteger
INTEGER
IpAddress
IpAddress
Counter
OCTET
}
ospfIfIpAddress OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP address of this OSPF interface."
::= { ospfIfEntry 1 }
ospfAddressLessIf OBJECT-
SYNTAX
ACCESS read-
STATUS
"For the purpose of easing the instancing of
and addressless interfaces; This variable takes
value 0 on interfaces with IP Addresses, and
corresponding value of ifIndex for interfaces having
IP Address."
::= { ospfIfEntry 2 }
ospfIfAreaId OBJECT-
SYNTAX
ACCESS read-
STATUS
"A 32-bit integer uniquely identifying the area
which the interface connects. Area ID 0.0.0.0 is
for the OSPF backbone."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 3 }
Baker & Coltun [Page 24]
RFC 1248 OSPF Version 2 MIB July 1991
ospfIfType OBJECT-
SYNTAX INTEGER {
broadcast (1),
nbma (2),
pointToPoint (3)
}
ACCESS read-
STATUS
"The OSPF interface type
By way of a default, this field may be intuited
the corresponding value of ifType. Broadcast LANs
such as Ethernet and IEEE 802.5, take the
'broadcast', X.25, Frame Relay, and
technologies take the value 'nbma', and links that
definitively point to point take the
'pointToPoint'."
::= { ospfIfEntry 4 }
ospfIfAdminStat OBJECT-
SYNTAX
ACCESS read-
STATUS
"The OSPF interface's administrative status. The
'enabled' denotes that neighbor relationships may
formed on the interface, and the interface will
advertised as an internal route to some area.
value 'disabled' denotes that the interface is
to OSPF."
DEFVAL { enabled }
::= { ospfIfEntry 5 }
ospfIfRtrPriority OBJECT-
SYNTAX
ACCESS read-
STATUS
"The priority of this interface. Used in multi-
networks, this field is used in the designated
election algorithm. The value 0 signifies that
router is not eligible to become the designated
on this particular network. In the event of a tie
this value, routers will use their router id as a
breaker."
DEFVAL { 1 }
::= { ospfIfEntry 6 }
Baker & Coltun [Page 25]
RFC 1248 OSPF Version 2 MIB July 1991
ospfIfTransitDelay OBJECT-
SYNTAX
ACCESS read-
STATUS
"The estimated number of seconds it takes to transmit
link- state update packet over this interface."
DEFVAL { 1 }
::= { ospfIfEntry 7 }
ospfIfRetransInterval OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of seconds between link-state
retransmissions, for adjacencies belonging to
interface. This value is also used when
database description and link-state request packets."
DEFVAL { 5 }
::= { ospfIfEntry 8 }
ospfIfHelloInterval OBJECT-
SYNTAX
ACCESS read-
STATUS
"The length of time, in seconds, between the
packets that the router sends on the interface.
value must be the same for all routers attached to
common network."
DEFVAL { 10 }
::= { ospfIfEntry 9 }
ospfIfRtrDeadInterval OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of seconds that a router's Hello
have not been seen before it's neighbors declare
router down. This should be some multiple of the
interval. This value must be the same for all
attached to a common network."
DEFVAL { 40 }
::= { ospfIfEntry 10 }
Baker & Coltun [Page 26]
RFC 1248 OSPF Version 2 MIB July 1991
ospfIfPollInterval OBJECT-
SYNTAX
ACCESS read-
STATUS
"The larger time interval, in seconds, between
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)
}
ACCESS read-
STATUS
"The OSPF Interface State."
DEFVAL { down }
::= { ospfIfEntry 12 }
ospfIfDesignatedRouter OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP Address of the Designated Router."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 13 }
ospfIfBackupDesignatedRouter OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP Address of the Backup Designated Router."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfIfEntry 14 }
Baker & Coltun [Page 27]
RFC 1248 OSPF Version 2 MIB July 1991
ospfIfEvents OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times this OSPF interface has
its state, or an error has occurred."
DEFVAL { 0 }
::= { ospfIfEntry 15 }
ospfIfAuthKey OBJECT-
SYNTAX OCTET
ACCESS read-
STATUS
"The Authentication Key. If the Area's
Type is simplePassword, and the key length is
than 8 octets, the agent will left adjust and zero
to 8 octets
When read, ospfIfAuthKey always returns an Octet
of length zero."
"OSPF Version 2, Section 9 The Interface
Structure
DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
::= { ospfIfEntry 16 }
-- 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
Baker & Coltun [Page 28]
RFC 1248 OSPF Version 2 MIB July 1991
-- Network Type/bit rate
-- >= 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)
ospfIfMetricTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"The TOS metrics for a non-virtual interface
by the interface index."
"OSPF Version 2, Appendix C.3 Router
parameters
::= { ospf 8 }
ospfIfMetricEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"A particular TOS metric for a non-virtual
identified by the interface index."
"OSPF Version 2, Appendix C.3 Router
parameters
INDEX { ospfIfMetricIpAddress
ospfIfMetricAddressLessIf
ospfIfMetricTOS }
::= { ospfIfMetricTable 1 }
OspfIfMetricEntry ::=
SEQUENCE {
IpAddress
INTEGER
TOSType
Baker & Coltun [Page 29]
RFC 1248 OSPF Version 2 MIB July 1991
Metric
}
ospfIfMetricIpAddress OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP address of this OSPF interface. On
creation, this can be derived from the instance."
::= { ospfIfMetricEntry 1 }
ospfIfMetricAddressLessIf OBJECT-
SYNTAX
ACCESS read-
STATUS
"For the purpose of easing the instancing of
and addressless interfaces; This variable takes
value 0 on interfaces with IP Addresses, and the
of ifIndex for interfaces having no IP Address. On
creation, this can be derived from the instance."
::= { ospfIfMetricEntry 2 }
ospfIfMetricTOS OBJECT-
SYNTAX
ACCESS read-
STATUS
"The type of service metric being referenced. On
creation, this can be derived from the instance."
::= { ospfIfMetricEntry 3 }
ospfIfMetricMetric OBJECT-
SYNTAX
ACCESS read-
STATUS
"The metric of using this type of service on
interface. The default value of the TOS 0 Metric
10^8 / ifSpeed
The value FFFF is distinguished to mean 'no route
this TOS'."
::= { ospfIfMetricEntry 4 }
Baker & Coltun [Page 30]
RFC 1248 OSPF Version 2 MIB July 1991
ospfIfMetricStatus OBJECT-
SYNTAX
ACCESS read-
STATUS
"This variable displays the validity or invalidity
the entry. Setting it to 'invalid' has the effect
rendering it inoperative. The internal effect (
removal) is implementation dependent."
DEFVAL { valid }
::= { 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
ACCESS not-
STATUS
"Information about this router's virtual interfaces."
"OSPF Version 2, Appendix C.4 Virtual link parameters
::= { ospf 9 }
ospfVirtIfEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Information about a single Virtual Interface."
INDEX { ospfVirtIfAreaID, ospfVirtIfNeighbor }
::= { ospfVirtIfTable 1 }
OspfVirtIfEntry ::=
SEQUENCE {
AreaID
RouterID
UpToMaxAge
UpToMaxAge
Baker & Coltun [Page 31]
RFC 1248 OSPF Version 2 MIB July 1991
HelloRange
PositiveInteger
INTEGER
Counter
OCTET STRING
}
ospfVirtIfAreaID OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Transit Area that the Virtual Link traverses.
definition, this is not 0.0.0.0"
::= { ospfVirtIfEntry 1 }
ospfVirtIfNeighbor OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Router ID of the Virtual Neighbor."
::= { ospfVirtIfEntry 2 }
ospfVirtIfTransitDelay OBJECT-
SYNTAX
ACCESS read-
STATUS
"The estimated number of seconds it takes to transmit
link- state update packet over this interface."
DEFVAL { 1 }
::= { ospfVirtIfEntry 3 }
ospfVirtIfRetransInterval OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of seconds between link-state
retransmissions, for adjacencies belonging to
Baker & Coltun [Page 32]
RFC 1248 OSPF Version 2 MIB July 1991
interface. This value is also used when
database description and link-state request packets
This value should be well over the expected round-
time."
DEFVAL { 5 }
::= { ospfVirtIfEntry 4 }
ospfVirtIfHelloInterval OBJECT-
SYNTAX
ACCESS read-
STATUS
"The length of time, in seconds, between the
packets that the router sends on the interface.
value must be the same for the virtual neighbor."
DEFVAL { 10 }
::= { ospfVirtIfEntry 5 }
ospfVirtIfRtrDeadInterval OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of seconds that a router's Hello
have not been seen before it's neighbors declare
router down. This should be some multiple of the
interval. This value must be the same for the
neighbor."
DEFVAL { 60 }
::= { ospfVirtIfEntry 6 }
ospfVirtIfState OBJECT-
SYNTAX INTEGER {
down (1), -- these use the same
pointToPoint (4) -- as the
}
ACCESS read-
STATUS
"OSPF virtual interface states."
DEFVAL { down }
::= { ospfVirtIfEntry 7 }
ospfVirtIfEvents OBJECT-
SYNTAX
ACCESS read-
STATUS
Baker & Coltun [Page 33]
RFC 1248 OSPF Version 2 MIB July 1991
"The number of state changes or error events on
Virtual Link
DEFVAL { 0 }
::= { ospfVirtIfEntry 8 }
ospfVirtIfAuthKey OBJECT-
SYNTAX OCTET
ACCESS read-
STATUS
"If Authentication Type is simplePassword, the
will left adjust and zero fill to 8 octets
When read, ospfVifAuthKey always returns a string
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
ACCESS read-
STATUS
"This variable displays the validity or invalidity
the entry. Setting it to 'invalid' has the effect
rendering it inoperative. The internal effect (
removal) is implementation dependent."
DEFVAL { valid }
::= { ospfVirtIfEntry 10 }
-- OSPF Neighbor
-- The OSPF Neighbor Table describes all neighbors
-- the locality of the subject router
ospfNbrTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"A table of non-virtual neighbor information."
"OSPF Version 2, Section 10 The Neighbor
Structure
Baker & Coltun [Page 34]
RFC 1248 OSPF Version 2 MIB July 1991
::= { ospf 10 }
ospfNbrEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"The information regarding a single neighbor."
"OSPF Version 2, Section 10 The Neighbor
Structure
INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex }
::= { ospfNbrTable 1 }
OspfNbrEntry ::=
SEQUENCE {
IpAddress
InterfaceIndex
RouterID
INTEGER
DesignatedRouterPriority
INTEGER
Counter
Gauge
}
ospfNbrIpAddr OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP address of this neighbor."
::= { ospfNbrEntry 1 }
ospfNbrAddressLessIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
Baker & Coltun [Page 35]
RFC 1248 OSPF Version 2 MIB July 1991
" On an interface having an IP Address, zero.
addressless interfaces, the corresponding value
ifIndex in the Internet Standard MIB. On row creation
this can be derived from the instance."
::= { ospfNbrEntry 2 }
ospfNbrRtrId OBJECT-
SYNTAX
ACCESS read-
STATUS
"A 32-bit integer (represented as a type IpAddress
uniquely identifying the neighboring router in
Autonomous System."
DEFVAL { '00000000'H } -- 0.0.0.0
::= { ospfNbrEntry 3 }
ospfNbrOptions OBJECT-
SYNTAX
ACCESS read-
STATUS
"A Bit Mask corresponding to the neighbor's
field
Bit 0, if set, indicates that the area accepts
operates on external information; if zero, it is a
area
Bit 1, if set, indicates that the system will
on Type of Service metrics other than TOS 0. If zero
the neighbor will ignore all metrics except the TOS 0
metric."
"OSPF Version 2, Section 12.1.2 Options
DEFVAL { 0 }
::= { ospfNbrEntry 4 }
ospfNbrPriority OBJECT-
SYNTAX
ACCESS read-
STATUS
"The priority of this neighbor in the designated
election algorithm. The value 0 signifies that
neighbor is not eligible to become the
router on this particular network."
Baker & Coltun [Page 36]
RFC 1248 OSPF Version 2 MIB July 1991
DEFVAL { 1 }
::= { ospfNbrEntry 5 }
ospfNbrState OBJECT-
SYNTAX INTEGER {
down (1),
attempt (2),
init (3),
twoWay (4),
exchangeStart (5),
exchange (6),
loading (7),
full (8)
}
ACCESS read-
STATUS
"The State of the relationship with this Neighbor."
"OSPF Version 2, Section 10.1 Neighbor States
DEFVAL { down }
::= { ospfNbrEntry 6 }
ospfNbrEvents OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times this neighbor relationship
changed state, or an error has occurred."
DEFVAL { 0 }
::= { ospfNbrEntry 7 }
ospfNbrLSRetransQLen OBJECT-
SYNTAX
ACCESS read-
STATUS
"The current length of the retransmission queue."
DEFVAL { 0 }
::= { ospfNbrEntry 8 }
ospfNBMANbrStatus OBJECT-
SYNTAX
ACCESS read-
STATUS
"This variable displays the validity or invalidity
Baker & Coltun [Page 37]
RFC 1248 OSPF Version 2 MIB July 1991
the entry. Setting it to 'invalid' has the effect
rendering it inoperative. The internal effect (
removal) is implementation dependent."
DEFVAL { valid }
::= { ospfNbrEntry 9 }
-- OSPF Virtual Neighbor
-- This table describes all virtual neighbors
-- Since Virtual Links are configured in
-- virtual interface table, this table is read-only
ospfVirtNbrTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"A table of virtual neighbor information."
"OSPF Version 2, Section 15 Virtual Links
::= { ospf 11 }
ospfVirtNbrEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"Virtual neighbor information."
INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId }
::= { ospfVirtNbrTable 1 }
OspfVirtNbrEntry ::=
SEQUENCE {
AreaID
RouterID
IpAddress
INTEGER
INTEGER
Counter
Baker & Coltun [Page 38]
RFC 1248 OSPF Version 2 MIB July 1991
}
ospfVirtNbrArea OBJECT-
SYNTAX
ACCESS read-
STATUS
"The Transit Area Identifier."
::= { ospfVirtNbrEntry 1 }
ospfVirtNbrRtrId OBJECT-
SYNTAX
ACCESS read-
STATUS
"A 32-bit integer uniquely identifying the
router in the Autonomous System."
::= { ospfVirtNbrEntry 2 }
ospfVirtNbrIpAddr OBJECT-
SYNTAX
ACCESS read-
STATUS
"The IP address this Virtual Neighbor is using."
::= { ospfVirtNbrEntry 3 }
ospfVirtNbrOptions OBJECT-
SYNTAX
ACCESS read-
STATUS
"A bit map corresponding to the neighbor's
field. Thus, Bit 1, if set, indicates that
neighbor supports Type of Service Routing; if zero,
metrics other than TOS 0 are in use by the neighbor."
::= { ospfVirtNbrEntry 4 }
ospfVirtNbrState OBJECT-
SYNTAX INTEGER {
down (1),
attempt (2),
init (3),
twoWay (4),
exchangeStart (5),
exchange (6),
loading (7),
full (8)
Baker & Coltun [Page 39]
RFC 1248 OSPF Version 2 MIB July 1991
}
ACCESS read-
STATUS
"The state of the Virtual Neighbor Relationship."
::= { ospfVirtNbrEntry 5 }
ospfVirtNbrEvents OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times this virtual link has changed
state, or an error has occurred."
DEFVAL { 0 }
::= { ospfVirtNbrEntry 6 }
ospfVirtNbrLSRetransQLen OBJECT-
SYNTAX
ACCESS read-
STATUS
"The current length of the retransmission queue."
::= { ospfVirtNbrEntry 7 }
6.
This document was produced by the OSPF Working Group, of which
Chairman is John Moy of Proteon
In addition, the comments of the following individuals are
acknowledged
John Moy Proteon,
Dino Farinacci 3
Stan Froyd Advanced Computer
Steve Willis
John Burress
Keith McCloghrie Hughes LAN
7.
[1] Cerf, V., "IAB Recommendations for the Development of
Network Management Standards", RFC 1052, NRI, April 1988.
[2] Cerf, V., "Report of the Second Ad Hoc Network Management
Baker & Coltun [Page 40]
RFC 1248 OSPF Version 2 MIB July 1991
Group", RFC 1109, NRI, August 1989.
[3] Rose M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
[4] McCloghrie K., and M. Rose, "Management Information Base
Network Management of TCP/IP-based internets", RFC 1156,
LAN Systems, Performance Systems International, May 1990.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "
Network Management Protocol", RFC 1157, SNMP Research
Performance Systems International, Performance
International, MIT Laboratory for Computer Science, May 1990.
[6] Rose M., Editor, "Management Information Base for
Management of TCP/IP-based internets: MIB-II", RFC 1213,
Performance Systems International, March 1991.
[7] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization,
Standard 8824, December 1987.
[8] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation
(ASN.1), International Organization for Standardization
International Standard 8825, December 1987.
[9] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
RFC 1212, Performance Systems International, Hughes LAN Systems
March 1991.
[10] Moy, J., Editor, "The OSPF Specification, Version 2", RFC 1247,
Proteon, Inc., July 1991.
8. Security
Security issues are not discussed in this memo
Baker & Coltun [Page 41]
RFC 1248 OSPF Version 2 MIB July 1991
9. Authors'
Fred
Advanced Computer
720 Santa Barbara
Santa Barbara, California 93101
Phone: (805) 963-9431
EMail: fbaker@acc.
Rob
Computer Science
Computer and Space Sciences
College Park, Maryland 20742
Phone: (301) 921-8600
EMail: rcoltun@ni.umd.
Or send comments to ospf@trantor.umd.edu
Baker & Coltun [Page 42]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
