Request for Comments: 1213 Hughes LAN Systems, Inc.
Obsoletes: RFC1158 M. Rose
Performance Systems International
Editors
March 1991
Management Information Base for Network Management
of TCP/IP-based internets:
MIB-II
Status of this Memo
This memo defines the second version of the Management Information
Base (MIB-II) for use with network management protocols in TCP/IP-
based internets. This RFCspecifies an IAB standards track protocol
for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the "IAB
Official Protocol Standards" for the standardization state and status
of this protocol. Distribution of this memo is unlimited.
Table of Contents
1. Abstract............................................... 2
2. Introduction .......................................... 2
3. Changes from RFC1156 ................................. 3
3.1 Deprecated Objects ................................... 3
3.2 Display Strings ...................................... 4
3.3 Physical Addresses ................................... 4
3.4 The System Group ..................................... 5
3.5 The Interfaces Group ................................. 5
3.6 The Address Translation Group ........................ 6
3.7 The IP Group ......................................... 6
3.8 The ICMP Group ....................................... 7
3.9 The TCP Group ........................................ 7
3.10 The UDP Group ....................................... 7
3.11 The EGP Group ....................................... 7
3.12 The Transmission Group .............................. 8
3.13 The SNMP Group ...................................... 8
3.14 Changes from RFC1158 ................. ............. 9
4. Objects ............................................... 10
4.1 Format of Definitions ................................ 10
5. Overview .............................................. 10
6. Definitions ........................................... 12
6.1 Textual Conventions .................................. 12
6.2 Groups in MIB-II ..................................... 13
6.3 The System Group ..................................... 13
6.4 The Interfaces Group ................................. 16
6.5 The Address Translation Group ........................ 23
6.6 The IP Group ......................................... 26
6.7 The ICMP Group ....................................... 41
6.8 The TCP Group ........................................ 46
6.9 The UDP Group ........................................ 52
6.10 The EGP Group ....................................... 54
6.11 The Transmission Group .............................. 60
6.12 The SNMP Group ...................................... 60
7. Acknowledgements ...................................... 67
8. References ............................................ 69
9. Security Considerations ............................... 70
10. Authors' Addresses ................................... 70
1. Abstract
This memo defines the second version of the Management Information
Base (MIB-II) for use with network management protocols in TCP/IP-
based internets. In particular, together with its companion memos
which describe the structure of management information (RFC1155)
along with the network management protocol (RFC1157) for TCP/IP-
based internets, these documents provide a simple, workable
architecture and system for managing TCP/IP-based internets and in
particular the Internet community.
2. Introduction
As reported in RFC1052, IAB Recommendations for the Development of
Internet Network Management Standards [1], a two-prong strategy for
network management of TCP/IP-based internets was undertaken. In the
short-term, the Simple Network Management Protocol (SNMP) was to be
used to manage nodes in the Internet community. In the long-term,
the use of the OSI network management framework was to be examined.
Two documents were produced to define the management information: RFC
1065, which defined the Structure of Management Information (SMI)
[2], and RFC1066, which defined the Management Information Base
(MIB) [3]. Both of these documents were designed so as to be
compatible with both the SNMP and the OSI network management
framework.
This strategy was quite successful in the short-term: Internet-based
network management technology was fielded, by both the research and
commercial communities, within a few months. As a result of this,
portions of the Internet community became network manageable in a
timely fashion.
As reported in RFC1109, Report of the Second Ad Hoc Network
Management Review Group [4], the requirements of the SNMP and the OSI
network management frameworks were more different than anticipated.
As such, the requirement for compatibility between the SMI/MIB and
both frameworks was suspended. This action permitted the operational
network management framework, the SNMP, to respond to new operational
needs in the Internet community by producing this document.
As such, the current network management framework for TCP/IP- based
internets consists of: Structure and Identification of Management
Information for TCP/IP-based internets, RFC1155 [12], which
describes how managed objects contained in the MIB are defined;
Management Information Base for Network Management of TCP/IP-based
internets: MIB-II, this memo, which describes the managed objects
contained in the MIB (and supercedes RFC1156 [13]); and, the Simple
Network Management Protocol, RFC1098 [5], which defines the protocol
used to manage these objects.
3. Changes from RFC1156
Features of this MIB include:
(1) incremental additions to reflect new operational
requirements;
(2) upwards compatibility with the SMI/MIB and the SNMP;
(3) improved support for multi-protocol entities; and,
(4) textual clean-up of the MIB to improve clarity and
readability.
The objects defined in MIB-II have the OBJECT IDENTIFIER prefix:
mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
which is identical to the prefix used in MIB-I.
3.1. Deprecated Objects
In order to better prepare implementors for future changes in the
MIB, a new term "deprecated" may be used when describing an object.
A deprecated object in the MIB is one which must be supported, but
one which will most likely be removed from the next version of the
MIB (e.g., MIB-III).
MIB-II marks one object as being deprecated:
atTable
As a result of deprecating the atTable object, the entire Address
Translation group is deprecated.
Note that no functionality is lost with the deprecation of these
objects: new objects providing equivalent or superior functionality
are defined in MIB-II.
3.2. Display Strings
In the past, there have been misinterpretations of the MIB as to when
a string of octets should contain printable characters, meant to be
displayed to a human. As a textual convention in the MIB, the
datatype
DisplayString ::=
OCTET STRING
is introduced. A DisplayString is restricted to the NVT ASCII
character set, as defined in pages 10-11 of [6].
The following objects are now defined in terms of DisplayString:
sysDescr
ifDescr
It should be noted that this change has no effect on either the
syntax nor semantics of these objects. The use of the DisplayString
notation is merely an artifact of the explanatory method used in
MIB-II and future MIBs.
Further it should be noted that any object defined in terms of OCTET
STRING may contain arbitrary binary data, in which each octet may
take any value from 0 to 255 (decimal).
3.3. Physical Addresses
As a further, textual convention in the MIB, the datatype
PhysAddress ::=
OCTET STRING
is introduced to represent media- or physical-level addresses.
The following objects are now defined in terms of PhysAddress:
ifPhysAddress
atPhysAddress
ipNetToMediaPhysAddress
It should be noted that this change has no effect on either the
syntax nor semantics of these objects. The use of the PhysAddress
notation is merely an artifact of the explanatory method used in
MIB-II and future MIBs.
3.4. The System Group
Four new objects are added to this group:
sysContact
sysName
sysLocation
sysServices
These provide contact, administrative, location, and service
information regarding the managed node.
3.5. The Interfaces Group
The definition of the ifNumber object was incorrect, as it required
all interfaces to support IP. (For example, devices without IP, such
as MAC-layer bridges, could not be managed if this definition was
strictly followed.) The description of the ifNumber object is
changed accordingly.
The ifTable object was mistaken marked as read-write, it has been
(correctly) re-designated as not-accessible. In addition, several
new values have been added to the ifType column in the ifTable
object:
ppp(23)
softwareLoopback(24)
eon(25)
ethernet-3Mbit(26)
nsip(27)
slip(28)
ultra(29)
ds3(30)
sip(31)
frame-relay(32)
Finally, a new column has been added to the ifTable object:
ifSpecific
which provides information about information specific to the media
being used to realize the interface.
3.6. The Address Translation Group
In MIB-I this group contained a table which permitted mappings from
network addresses (e.g., IP addresses) to physical addresses (e.g.,
MAC addresses). Experience has shown that efficient implementations
of this table make two assumptions: a single network protocol
environment, and mappings occur only from network address to physical
address.
The need to support multi-protocol nodes (e.g., those with both the
IP and CLNP active), and the need to support the inverse mapping
(e.g., for ES-IS), have invalidated both of these assumptions. As
such, the atTable object is declared deprecated.
In order to meet both the multi-protocol and inverse mapping
requirements, MIB-II and its successors will allocate up to two
address translation tables inside each network protocol group. That
is, the IP group will contain one address translation table, for
going from IP addresses to physical addresses. Similarly, when a
document defining MIB objects for the CLNP is produced (e.g., [7]),
it will contain two tables, for mappings in both directions, as this
is required for full functionality.
It should be noted that the choice of two tables (one for each
direction of mapping) provides for ease of implementation in many
cases, and does not introduce undue burden on implementations which
realize the address translation abstraction through a single internal
table.
3.7. The IP Group
The access attribute of the variable ipForwarding has been changed
from read-only to read-write.
In addition, there is a new column to the ipAddrTable object,
ipAdEntReasmMaxSize
which keeps track of the largest IP datagram that can be re-assembled
on a particular interface.
The descriptor of the ipRoutingTable object has been changed to
ipRouteTable for consistency with the other IP routing objects.
There are also three new columns in the ipRouteTable object,
ipRouteMask
ipRouteMetric5
ipRouteInfo
the first is used for IP routing subsystems that support arbitrary
subnet masks, and the latter two are IP routing protocol-specific.
Two new objects are added to the IP group:
ipNetToMediaTable
ipRoutingDiscards
the first is the address translation table for the IP group
(providing identical functionality to the now deprecated atTable in
the address translation group), and the latter provides information
when routes are lost due to a lack of buffer space.
3.8. The ICMP Group
There are no changes to this group.
3.9. The TCP Group
Two new variables are added:
tcpInErrs
tcpOutRsts
which keep track of the number of incoming TCP segments in error and
the number of resets generated by a TCP.
3.10. The UDP Group
A new table:
udpTable
is added.
3.11. The EGP Group
Experience has indicated a need for additional objects that are
useful in EGP monitoring. In addition to making several additions to
the egpNeighborTable object, i.e.,
egpNeighAs
egpNeighInMsgs
egpNeighInErrs
egpNeighOutMsgs
egpNeighOutErrs
egpNeighInErrMsgs
egpNeighOutErrMsgs
egpNeighStateUps
egpNeighStateDowns
egpNeighIntervalHello
egpNeighIntervalPoll
egpNeighMode
egpNeighEventTrigger
a new variable is added:
egpAs
which gives the autonomous system associated with this EGP entity.
3.12. The Transmission Group
MIB-I was lacking in that it did not distinguish between different
types of transmission media. A new group, the Transmission group, is
allocated for this purpose:
transmission OBJECT IDENTIFIER ::= { mib-2 10 }
When Internet-standard definitions for managing transmission media
are defined, the transmission group is used to provide a prefix for
the names of those objects.
Typically, such definitions reside in the experimental portion of the
MIB until they are "proven", then as a part of the Internet
standardization process, the definitions are accordingly elevated and
a new object identifier, under the transmission group is defined. By
convention, the name assigned is:
type OBJECT IDENTIFIER ::= { transmission number }
where "type" is the symbolic value used for the media in the ifType
column of the ifTable object, and "number" is the actual integer
value corresponding to the symbol.
3.13. The SNMP Group
The application-oriented working groups of the IETF have been tasked
to be receptive towards defining MIB variables specific to their
respective applications.
For the SNMP, it is useful to have statistical information. A new
group, the SNMP group, is allocated for this purpose:
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
3.14. Changes from RFC1158
Features of this MIB include:
(1) The managed objects in this document have been defined
using the conventions defined in the Internet-standard
SMI, as amended by the extensions specified in [14]. It
must be emphasized that definitions made using these
extensions are semantically identically to those in RFC
1158.
(2) The PhysAddress textual convention has been introduced to
represent media addresses.
(3) The ACCESS clause of sysLocation is now read-write.
(4) The definition of sysServices has been clarified.
(5) New ifType values (29-32) have been defined. In
addition, the textual-descriptor for the DS1 and E1
interface types has been corrected.
(6) The definition of ipForwarding has been clarified.
(7) The definition of ipRouteType has been clarified.
(8) The ipRouteMetric5 and ipRouteInfo objects have been
defined.
(9) The ACCESS clause of tcpConnState is now read-write, to
support deletion of the TCB associated with a TCP
connection. The definition of this object has been
clarified to explain this usage.
(10) The definition of egpNeighEventTrigger has been
clarified.
(11) The definition of several of the variables in the new
snmp group have been clarified. In addition, the
snmpInBadTypes and snmpOutReadOnlys objects are no longer
present. (However, the object identifiers associated
with those objects are reserved to prevent future use.)
(12) The definition of snmpInReadOnlys has been clarified.
(13) The textual descriptor of the snmpEnableAuthTraps has
been changed to snmpEnableAuthenTraps, and the definition
has been clarified.
(14) The ipRoutingDiscards object was added.
(15) The optional use of an implementation-dependent, small
positive integer was disallowed when identifying
instances of the IP address and routing tables.
4. Objects
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1) [8]
defined in the SMI. In particular, each object has a name, a syntax,
and an encoding. The name is an object identifier, an
administratively assigned name, which specifies an object type. The
object type together with an object instance serves to uniquely
identify a specific instantiation of the object. For human
convenience, we often use a textual string, termed the OBJECT
DESCRIPTOR, to also refer to the object type.
The syntax of an object type defines the abstract data structure
corresponding to that object type. The ASN.1 language is used for
this purpose. However, the SMI [12] purposely restricts the ASN.1
constructs which may be used. These restrictions are explicitly made
for simplicity.
The encoding of an object type is simply how that object type is
represented using the object type's syntax. Implicitly tied to the
notion of an object type's syntax and encoding is how the object type
is represented when being transmitted on the network.
The SMI specifies the use of the basic encoding rules of ASN.1 [9],
subject to the additional requirements imposed by the SNMP.
4.1. Format of Definitions
Section 6 contains contains the specification of all object types
contained in this MIB module. The object types are defined using the
conventions defined in the SMI, as amended by the extensions
specified in [14].
5. Overview
Consistent with the IAB directive to produce simple, workable systems
in the short-term, the list of managed objects defined here, has been
derived by taking only those elements which are considered essential.
This approach of taking only the essential objects is NOT
restrictive, since the SMI defined in the companion memo provides
three extensibility mechanisms: one, the addition of new standard
objects through the definitions of new versions of the MIB; two, the
addition of widely-available but non-standard objects through the
experimental subtree; and three, the addition of private objects
through the enterprises subtree. Such additional objects can not
only be used for vendor-specific elements, but also for
experimentation as required to further the knowledge of which other
objects are essential.
The design of MIB-II is heavily influenced by the first extensibility
mechanism. Several new variables have been added based on
operational experience and need. Based on this, the criteria for
including an object in MIB-II are remarkably similar to the MIB-I
criteria:
(1) An object needed to be essential for either fault or
configuration management.
(2) Only weak control objects were permitted (by weak, it is
meant that tampering with them can do only limited
damage). This criterion reflects the fact that the
current management protocols are not sufficiently secure
to do more powerful control operations.
(3) Evidence of current use and utility was required.
(4) In MIB-I, an attempt was made to limit the number of
objects to about 100 to make it easier for vendors to
fully instrument their software. In MIB-II, this limit
was raised given the wide technological base now
implementing MIB-I.
(5) To avoid redundant variables, it was required that no
object be included that can be derived from others in the
MIB.
(6) Implementation specific objects (e.g., for BSD UNIX) were
excluded.
(7) It was agreed to avoid heavily instrumenting critical
sections of code. The general guideline was one counter
per critical section per layer.
MIB-II, like its predecessor, the Internet-standard MIB, contains
only essential elements. There is no need to allow individual
objects to be optional. Rather, the objects are arranged into the
following groups:
- System
- Interfaces
- Address Translation (deprecated)
- IP
- ICMP
- TCP
- UDP
- EGP
- Transmission
- SNMP
These groups are the basic unit of conformance: This method is as
follows: if the semantics of a group is applicable to an
implementation, then it must implement all objects in that group.
For example, an implementation must implement the EGP group if and
only if it implements the EGP.
There are two reasons for defining these groups: to provide a means
of assigning object identifiers; and, to provide a method for
implementations of managed agents to know which objects they must
implement.
6. Definitions
RFC1213-MIB DEFINITIONS ::= BEGIN
IMPORTS
mgmt, NetworkAddress, IpAddress, Counter, Gauge,
TimeTicks
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212;
-- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in [14];
-- MIB-II (same prefix as MIB-I)
mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
-- textual conventions
DisplayString ::=
OCTET STRING
-- This data type is used to model textual information taken
-- from the NVT ASCII character set. By convention, objects
-- with this syntax are declared as having
--
-- SIZE (0..255)
PhysAddress ::=
OCTET STRING
-- This data type is used to model media addresses. For many
-- types of media, this will be in a binary representation.
-- For example, an ethernet address would be represented as
-- a string of 6 octets.
-- groups in MIB-II
system OBJECT IDENTIFIER ::= { mib-2 1 }
interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
at OBJECT IDENTIFIER ::= { mib-2 3 }
ip OBJECT IDENTIFIER ::= { mib-2 4 }
icmp OBJECT IDENTIFIER ::= { mib-2 5 }
tcp OBJECT IDENTIFIER ::= { mib-2 6 }
udp OBJECT IDENTIFIER ::= { mib-2 7 }
egp OBJECT IDENTIFIER ::= { mib-2 8 }
-- historical (some say hysterical)
-- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
transmission OBJECT IDENTIFIER ::= { mib-2 10 }
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
-- the System group
-- Implementation of the System group is mandatory for all
-- systems. If an agent is not configured to have a value
-- for any of these variables, a string of length 0 is
-- returned.
sysDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A textual description of the entity. This value
should include the full name and version
identification of the system's hardware type,
software operating-system, and networking
software. It is mandatory that this only contain
printable ASCII characters."
::= { system 1 }
sysObjectID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The vendor's authoritative identification of the
network management subsystem contained in the
entity. This value is allocated within the SMI
enterprises subtree (1.3.6.1.4.1) and provides an
easy and unambiguous means for determining `what
kind of box' is being managed. For example, if
vendor `Flintstones, Inc.' was assigned the
subtree 1.3.6.1.4.1.4242, it could assign the
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred
Router'."
::= { system 2 }
sysUpTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized."
::= { system 3 }
sysContact OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The textual identification of the contact person
for this managed node, together with information
on how to contact this person."
::= { system 4 }
sysName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An administratively-assigned name for this
managed node. By convention, this is the node's
fully-qualified domain name."
::= { system 5 }
sysLocation OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The physical location of this node (e.g.,
`telephone closet, 3rd floor')."
::= { system 6 }
sysServices OBJECT-TYPE
SYNTAX INTEGER (0..127)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value which indicates the set of services that
this entity primarily offers.
The value is a sum. This sum initially takes the
value zero, Then, for each layer, L, in the range
1 through 7, that this node performs transactions
for, 2 raised to (L - 1) is added to the sum. For
example, a node which performs primarily routing
functions would have a value of 4 (2^(3-1)). In
contrast, a node which is a host offering
application services would have a value of 72
(2^(4-1) + 2^(7-1)). Note that in the context of
the Internet suite of protocols, values should be
calculated accordingly:
layer functionality
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., IP gateways)
4 end-to-end (e.g., IP hosts)
7 applications (e.g., mail relays)
For systems including OSI protocols, layers 5 and
6 may also be counted."
::= { system 7 }
-- the Interfaces group
-- Implementation of the Interfaces group is mandatory for
-- all systems.
ifNumber OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of network interfaces (regardless of
their current state) present on this system."
::= { interfaces 1 }
-- the Interfaces table
-- The Interfaces table contains information on the entity's
-- interfaces. Each interface is thought of as being
-- attached to a `subnetwork'. Note that this term should
-- not be confused with `subnet' which refers to an
-- addressing partitioning scheme used in the Internet suite
-- of protocols.
ifTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of interface entries. The number of
entries is given by the value of ifNumber."
::= { interfaces 2 }
ifEntry OBJECT-TYPE
SYNTAX IfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An interface entry containing objects at the
subnetwork layer and below for a particular
interface."
INDEX { ifIndex }
::= { ifTable 1 }
IfEntry ::=
SEQUENCE {
ifIndex
INTEGER,
ifDescr
DisplayString,
ifType
INTEGER,
ifMtu
INTEGER,
ifSpeed
Gauge,
ifPhysAddress
PhysAddress,
ifAdminStatus
INTEGER,
ifOperStatus
INTEGER,
ifLastChange
TimeTicks,
ifInOctets
Counter,
ifInUcastPkts
Counter,
ifInNUcastPkts
Counter,
ifInDiscards
Counter,
ifInErrors
Counter,
ifInUnknownProtos
Counter,
ifOutOctets
Counter,
ifOutUcastPkts
Counter,
ifOutNUcastPkts
Counter,
ifOutDiscards
Counter,
ifOutErrors
Counter,
ifOutQLen
Gauge,
ifSpecific
OBJECT IDENTIFIER
}
ifIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value for each interface. Its value
ranges between 1 and the value of ifNumber. The
value for each interface must remain constant at
least from one re-initialization of the entity's
network management system to the next re-
initialization."
::= { ifEntry 1 }
ifDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A textual string containing information about the
interface. This string should include the name of
the manufacturer, the product name and the version
of the hardware interface."
::= { ifEntry 2 }
ifType OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- none of the following
regular1822(2),
hdh1822(3),
ddn-x25(4),
rfc877-x25(5),
ethernet-csmacd(6),
iso88023-csmacd(7),
iso88024-tokenBus(8),
iso88025-tokenRing(9),
iso88026-man(10),
starLan(11),
proteon-10Mbit(12),
proteon-80Mbit(13),
hyperchannel(14),
fddi(15),
lapb(16),
sdlc(17),
ds1(18), -- T-1
e1(19), -- european equiv. of T-1
basicISDN(20),
primaryISDN(21), -- proprietary serial
propPointToPointSerial(22),
ppp(23),
softwareLoopback(24),
eon(25), -- CLNP over IP [11]
ethernet-3Mbit(26),
nsip(27), -- XNS over IP
slip(28), -- generic SLIP
ultra(29), -- ULTRA technologies
ds3(30), -- T-3
sip(31), -- SMDS
frame-relay(32)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type of interface, distinguished according to
the physical/link protocol(s) immediately `below'
the network layer in the protocol stack."
::= { ifEntry 3 }
ifMtu OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The size of the largest datagram which can be
sent/received on the interface, specified in
octets. For interfaces that are used for
transmitting network datagrams, this is the size
of the largest network datagram that can be sent
on the interface."
::= { ifEntry 4 }
ifSpeed OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An estimate of the interface's current bandwidth
in bits per second. For interfaces which do not
vary in bandwidth or for those where no accurate
estimation can be made, this object should contain
the nominal bandwidth."
::= { ifEntry 5 }
ifPhysAddress OBJECT-TYPE
SYNTAX PhysAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The interface's address at the protocol layer
immediately `below' the network layer in the
protocol stack. For interfaces which do not have
such an address (e.g., a serial line), this object
should contain an octet string of zero length."
::= { ifEntry 6 }
ifAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1), -- ready to pass packets
down(2),
testing(3) -- in some test mode
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The desired state of the interface. The
testing(3) state indicates that no operational
packets can be passed."
::= { ifEntry 7 }
ifOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1), -- ready to pass packets
down(2),
testing(3) -- in some test mode
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current operational state of the interface.
The testing(3) state indicates that no operational
packets can be passed."
::= { ifEntry 8 }
ifLastChange OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of sysUpTime at the time the interface
entered its current operational state. If the
current state was entered prior to the last re-
initialization of the local network management
subsystem, then this object contains a zero
value."
::= { ifEntry 9 }
ifInOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of octets received on the
interface, including framing characters."
::= { ifEntry 10 }
ifInUcastPkts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of subnetwork-unicast packets
delivered to a higher-layer protocol."
::= { ifEntry 11 }
ifInNUcastPkts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of non-unicast (i.e., subnetwork-
broadcast or subnetwork-multicast) packets
delivered to a higher-layer protocol."
::= { ifEntry 12 }
ifInDiscards OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of inbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being deliverable to a
higher-layer protocol. One possible reason for
discarding such a packet could be to free up
buffer space."
::= { ifEntry 13 }
ifInErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of inbound packets that contained
errors preventing them from being deliverable to a
higher-layer protocol."
::= { ifEntry 14 }
ifInUnknownProtos OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of packets received via the interface
which were discarded because of an unknown or
unsupported protocol."
::= { ifEntry 15 }
ifOutOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of octets transmitted out of the
interface, including framing characters."
::= { ifEntry 16 }
ifOutUcastPkts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of packets that higher-level
protocols requested be transmitted to a
subnetwork-unicast address, including those that
were discarded or not sent."
::= { ifEntry 17 }
ifOutNUcastPkts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of packets that higher-level
protocols requested be transmitted to a non-
unicast (i.e., a subnetwork-broadcast or
subnetwork-multicast) address, including those
that were discarded or not sent."
::= { ifEntry 18 }
ifOutDiscards OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of outbound packets which were chosen
to be discarded even though no errors had been
detected to prevent their being transmitted. One
possible reason for discarding such a packet could
be to free up buffer space."
::= { ifEntry 19 }
ifOutErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of outbound packets that could not be
transmitted because of errors."
::= { ifEntry 20 }
ifOutQLen OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The length of the output packet queue (in
packets)."
::= { ifEntry 21 }
ifSpecific OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A reference to MIB definitions specific to the
particular media being used to realize the
interface. For example, if the interface is
realized by an ethernet, then the value of this
object refers to a document defining objects
specific to ethernet. If this information is not
present, its value should be set to the OBJECT
IDENTIFIER { 0 0 }, which is a syntatically valid
object identifier, and any conformant
implementation of ASN.1 and BER must be able to
generate and recognize this value."
::= { ifEntry 22 }
-- the Address Translation group
-- Implementation of the Address Translation group is
-- mandatory for all systems. Note however that this group
-- is deprecated by MIB-II. That is, it is being included
-- solely for compatibility with MIB-I nodes, and will most
-- likely be excluded from MIB-III nodes. From MIB-II and
-- onwards, each network protocol group contains its own
-- address translation tables.
-- The Address Translation group contains one table which is
-- the union across all interfaces of the translation tables
-- for converting a NetworkAddress (e.g., an IP address) into
-- a subnetwork-specific address. For lack of a better term,
-- this document refers to such a subnetwork-specific address
-- as a `physical' address.
-- Examples of such translation tables are: for broadcast
-- media where ARP is in use, the translation table is
-- equivalent to the ARP cache; or, on an X.25 network where
-- non-algorithmic translation to X.121 addresses is
-- required, the translation table contains the
-- NetworkAddress to X.121 address equivalences.
atTable OBJECT-TYPE
SYNTAX SEQUENCE OF AtEntry
ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"The Address Translation tables contain the
NetworkAddress to `physical' address equivalences.
Some interfaces do not use translation tables for
determining address equivalences (e.g., DDN-X.25
has an algorithmic method); if all interfaces are
of this type, then the Address Translation table
is empty, i.e., has zero entries."
::= { at 1 }
atEntry OBJECT-TYPE
SYNTAX AtEntry
ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"Each entry contains one NetworkAddress to
`physical' address equivalence."
INDEX { atIfIndex,
atNetAddress }
::= { atTable 1 }
AtEntry ::=
SEQUENCE {
atIfIndex
INTEGER,
atPhysAddress
PhysAddress,
atNetAddress
NetworkAddress
}
atIfIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS deprecated
DESCRIPTION
"The interface on which this entry's equivalence
is effective. The interface identified by a
particular value of this index is the same
interface as identified by the same value of
ifIndex."
::= { atEntry 1 }
atPhysAddress OBJECT-TYPE
SYNTAX PhysAddress
ACCESS read-write
STATUS deprecated
DESCRIPTION
"The media-dependent `physical' address.
Setting this object to a null string (one of zero
length) has the effect of invaliding the
corresponding entry in the atTable object. That
is, it effectively dissasociates the interface
identified with said entry from the mapping
identified with said entry. It is an
implementation-specific matter as to whether the
agent removes an invalidated entry from the table.
Accordingly, management stations must be prepared
to receive tabular information from agents that
corresponds to entries not currently in use.
Proper interpretation of such entries requires
examination of the relevant atPhysAddress object."
::= { atEntry 2 }
atNetAddress OBJECT-TYPE
SYNTAX NetworkAddress
ACCESS read-write
STATUS deprecated
DESCRIPTION
"The NetworkAddress (e.g., the IP address)
corresponding to the media-dependent `physical'
address."
::= { atEntry 3 }
-- the IP group
-- Implementation of the IP group is mandatory for all
-- systems.
ipForwarding OBJECT-TYPE
SYNTAX INTEGER {
forwarding(1), -- acting as a gateway
not-forwarding(2) -- NOT acting as a gateway
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The indication of whether this entity is acting
as an IP gateway in respect to the forwarding of
datagrams received by, but not addressed to, this
entity. IP gateways forward datagrams. IP hosts
do not (except those source-routed via the host).
Note that for some managed nodes, this object may
take on only a subset of the values possible.
Accordingly, it is appropriate for an agent to
return a `badValue' response if a management
station attempts to change this object to an
inappropriate value."
::= { ip 1 }
ipDefaultTTL OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The default value inserted into the Time-To-Live
field of the IP header of datagrams originated at
this entity, whenever a TTL value is not supplied
by the transport layer protocol."
::= { ip 2 }
ipInReceives OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of input datagrams received from
interfaces, including those received in error."
::= { ip 3 }
ipInHdrErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of input datagrams discarded due to
errors in their IP headers, including bad
checksums, version number mismatch, other format
errors, time-to-live exceeded, errors discovered
in processing their IP options, etc."
::= { ip 4 }
ipInAddrErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of input datagrams discarded because
the IP address in their IP header's destination
field was not a valid address to be received at
this entity. This count includes invalid
addresses (e.g., 0.0.0.0) and addresses of
unsupported Classes (e.g., Class E). For entities
which are not IP Gateways and therefore do not
forward datagrams, this counter includes datagrams
discarded because the destination address was not
a local address."
::= { ip 5 }
ipForwDatagrams OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of input datagrams for which this
entity was not their final IP destination, as a
result of which an attempt was made to find a
route to forward them to that final destination.
In entities which do not act as IP Gateways, this
counter will include only those packets which were
Source-Routed via this entity, and the Source-
Route option processing was successful."
::= { ip 6 }
ipInUnknownProtos OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of locally-addressed datagrams
received successfully but discarded because of an
unknown or unsupported protocol."
::= { ip 7 }
ipInDiscards OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of input IP datagrams for which no
problems were encountered to prevent their
continued processing, but which were discarded
(e.g., for lack of buffer space). Note that this
counter does not include any datagrams discarded
while awaiting re-assembly."
::= { ip 8 }
ipInDelivers OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of input datagrams successfully
delivered to IP user-protocols (including ICMP)."
::= { ip 9 }
ipOutRequests OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of IP datagrams which local IP
user-protocols (including ICMP) supplied to IP in
requests for transmission. Note that this counter
does not include any datagrams counted in
ipForwDatagrams."
::= { ip 10 }
ipOutDiscards OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of output IP datagrams for which no
problem was encountered to prevent their
transmission to their destination, but which were
discarded (e.g., for lack of buffer space). Note
that this counter would include datagrams counted
in ipForwDatagrams if any such packets met this
(discretionary) discard criterion."
::= { ip 11 }
ipOutNoRoutes OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of IP datagrams discarded because no
route could be found to transmit them to their
destination. Note that this counter includes any
packets counted in ipForwDatagrams which meet this
`no-route' criterion. Note that this includes any
datagarms which a host cannot route because all of
its default gateways are down."
::= { ip 12 }
ipReasmTimeout OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The maximum number of seconds which received
fragments are held while they are awaiting
reassembly at this entity."
::= { ip 13 }
ipReasmReqds OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of IP fragments received which needed
to be reassembled at this entity."
::= { ip 14 }
ipReasmOKs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of IP datagrams successfully re-
assembled."
::= { ip 15 }
ipReasmFails OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of failures detected by the IP re-
assembly algorithm (for whatever reason: timed
out, errors, etc). Note that this is not
necessarily a count of discarded IP fragments
since some algorithms (notably the algorithm in
RFC815) can lose track of the number of fragments
by combining them as they are received."
::= { ip 16 }
ipFragOKs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of IP datagrams that have been
successfully fragmented at this entity."
::= { ip 17 }
ipFragFails OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of IP datagrams that have been
discarded because they needed to be fragmented at
this entity but could not be, e.g., because their
Don't Fragment flag was set."
::= { ip 18 }
ipFragCreates OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of IP datagram fragments that have
been generated as a result of fragmentation at
this entity."
::= { ip 19 }
-- the IP address table
-- The IP address table contains this entity's IP addressing
-- information.
ipAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpAddrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The table of addressing information relevant to
this entity's IP addresses."
::= { ip 20 }
ipAddrEntry OBJECT-TYPE
SYNTAX IpAddrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The addressing information for one of this
entity's IP addresses."
INDEX { ipAdEntAddr }
::= { ipAddrTable 1 }
IpAddrEntry ::=
SEQUENCE {
ipAdEntAddr
IpAddress,
ipAdEntIfIndex
INTEGER,
ipAdEntNetMask
IpAddress,
ipAdEntBcastAddr
INTEGER,
ipAdEntReasmMaxSize
INTEGER (0..65535)
}
ipAdEntAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP address to which this entry's addressing
information pertains."
::= { ipAddrEntry 1 }
ipAdEntIfIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The index value which uniquely identifies the
interface to which this entry is applicable. The
interface identified by a particular value of this
index is the same interface as identified by the
same value of ifIndex."
::= { ipAddrEntry 2 }
ipAdEntNetMask OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The subnet mask associated with the IP address of
this entry. The value of the mask is an IP
address with all the network bits set to 1 and all
the hosts bits set to 0."
::= { ipAddrEntry 3 }
ipAdEntBcastAddr OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the least-significant bit in the IP
broadcast address used for sending datagrams on
the (logical) interface associated with the IP
address of this entry. For example, when the
Internet standard all-ones broadcast address is
used, the value will be 1. This value applies to