As per Relevance of the word monitoring, we have this rfc below:
Network Working Group S.
Request for Comments: 2819 Lucent
STD: 59 May 2000
Obsoletes: 1757
Category: Standards
Remote Network Monitoring 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
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
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 remote
monitoring devices
This memo obsoletes RFC 1757. This memo extends that specification
documenting the RMON MIB in SMIv2 format while remaining
identical to the existing SMIv1-based MIB
Waldbusser Standards Track [Page 1]
RFC 2819 Remote Network Monitoring MIB May 2000
Table of
1 The SNMP Management Framework .............................. 2
2 Overview ................................................... 3
2.1 Remote Network Management Goals .......................... 4
2.2 Textual Conventions ...................................... 5
2.3 Structure of MIB ......................................... 5
2.3.1 The Ethernet Statistics Group .......................... 6
2.3.2 The History Control Group .............................. 6
2.3.3 The Ethernet History Group ............................. 6
2.3.4 The Alarm Group ........................................ 7
2.3.5 The Host Group ......................................... 7
2.3.6 The HostTopN Group ..................................... 7
2.3.7 The Matrix Group ....................................... 7
2.3.8 The Filter Group ....................................... 7
2.3.9 The Packet Capture Group ............................... 8
2.3.10 The Event Group ....................................... 8
3 Control of Remote Network Monitoring Devices ............... 8
3.1 Resource Sharing Among Multiple Management Stations ... 9
3.2 Row Addition Among Multiple Management Stations .......... 10
4 Conventions ................................................ 11
5 Definitions ................................................ 12
6 Security Considerations .................................... 94
7 Acknowledgments ............................................ 95
8 Author's Address ........................................... 95
9 References ................................................. 95
10 Intellectual Property ..................................... 97
11 Full Copyright Statement .................................. 98
1. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described in
16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
second version, called SMIv2, is described in STD 58, RFC 2578
[5], RFC 2579 [6] and RFC 2580 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9] and
Waldbusser Standards Track [Page 2]
RFC 2819 Remote Network Monitoring MIB May 2000
1906 [10]. The third version of the message protocol is
SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [22].
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
2.
Remote network monitoring devices, often called monitors or probes
are instruments that exist for the purpose of managing a network
Often these remote probes are stand-alone devices and
significant internal resources for the sole purpose of managing
network. An organization may employ many of these devices, one
network segment, to manage its internet. In addition, these
may be used for a network management service provider to access
client network, often geographically remote
The objects defined in this document are intended as an
between an RMON agent and an RMON management application and are
intended for direct manipulation by humans. While some users
tolerate the direct display of some of these objects, few
Waldbusser Standards Track [Page 3]
RFC 2819 Remote Network Monitoring MIB May 2000
tolerate the complexity of manually manipulating objects
accomplish row creation. These functions should be handled by
management application
While most of the objects in this document are suitable for
management of any type of network, there are some which are
to managing Ethernet networks. These are the objects in
etherStatsTable, the etherHistoryTable, and some attributes of
filterPktStatus and capturBufferPacketStatus objects. The design
this MIB allows similar objects to be defined for other
types. It is intended that future versions of this document
additional documents will define extensions for other network types
There are a number of companion documents to the RMON MIB. The
Ring RMON MIB [19] provides objects specific to managing Token
networks. The RMON-2 MIB [20] extends RMON by providing RMON
up to the application layer. The SMON MIB [21] extends RMON
providing RMON analysis for switched networks
2.1. Remote Network Management
o Offline
There are sometimes conditions when a management station
not be in constant contact with its remote monitoring devices
This is sometimes by design in an attempt to
communications costs (especially when communicating over a
or dialup link), or by accident as network failures affect
communications between the management station and the probe
For this reason, this MIB allows a probe to be configured
perform diagnostics and to collect statistics continuously,
when communication with the management station may not
possible or efficient. The probe may then attempt to notify
management station when an exceptional condition occurs. Thus
even in circumstances where communication between
station and probe is not continuous, fault, performance,
configuration information may be continuously accumulated
communicated to the management station conveniently
efficiently
o Proactive
Given the resources available on the monitor, it is
helpful for it continuously to run diagnostics and to
network performance. The monitor is always available at
onset of any failure. It can notify the management station
the failure and can store historical statistical
Waldbusser Standards Track [Page 4]
RFC 2819 Remote Network Monitoring MIB May 2000
about the failure. This historical information can be
back by the management station in an attempt to perform
diagnosis into the cause of the problem
o Problem Detection and
The monitor can be configured to recognize conditions,
notably error conditions, and continuously to check for them
When one of these conditions occurs, the event may be logged
and management stations may be notified in a number of ways
o Value Added
Because a remote monitoring device represents a network
dedicated exclusively to network management functions,
because it is located directly on the monitored portion of
network, the remote network monitoring device has
opportunity to add significant value to the data it collects
For instance, by highlighting those hosts on the network
generate the most traffic or errors, the probe can give
management station precisely the information it needs to solve
class of problems
o Multiple
An organization may have multiple management stations
different units of the organization, for different
(e.g. engineering and operations), and in an attempt to
disaster recovery. Because environments with
management stations are common, the remote network
device has to deal with more than own management station
potentially using its resources concurrently
2.2. Textual
Two new data types are introduced as a textual convention in this
document, OwnerString and EntryStatus
2.3. Structure of
The objects are arranged into the following groups
- ethernet
- history
- ethernet
-
-
Waldbusser Standards Track [Page 5]
RFC 2819 Remote Network Monitoring MIB May 2000
-
-
-
- packet
-
These groups are the basic unit of conformance. If a
monitoring device implements a group, then it must implement
objects in that group. For example, a managed agent that
the host group must implement the hostControlTable, the hostTable
the hostTimeTable. While this section provides an overview
grouping and conformance information for this MIB, the
reference for such information is contained in the MODULE-
and OBJECT-GROUP macros later in this MIB
All groups in this MIB are optional. Implementations of this
must also implement the system group of MIB-II [16] and the IF-
[17]. MIB-II may also mandate the implementation of
groups
These groups are defined to provide a means of assigning
identifiers, and to provide a method for implementors of
agents to know which objects they must implement
2.3.1. The Ethernet Statistics
The ethernet statistics group contains statistics measured by
probe for each monitored Ethernet interface on this device.
group consists of the etherStatsTable
2.3.2. The History Control
The history control group controls the periodic statistical
of data from various types of networks. This group consists of
historyControlTable
2.3.3. The Ethernet History
The ethernet history group records periodic statistical samples
an ethernet network and stores them for later retrieval. This
consists of the etherHistoryTable
Waldbusser Standards Track [Page 6]
RFC 2819 Remote Network Monitoring MIB May 2000
2.3.4. The Alarm
The alarm group periodically takes statistical samples from
in the probe and compares them to previously configured thresholds
If the monitored variable crosses a threshold, an event is generated
A hysteresis mechanism is implemented to limit the generation
alarms. This group consists of the alarmTable and requires
implementation of the event group
2.3.5. The Host
The host group contains statistics associated with each
discovered on the network. This group discovers hosts on the
by keeping a list of source and destination MAC Addresses seen
good packets promiscuously received from the network. This
consists of the hostControlTable, the hostTable, and
hostTimeTable
2.3.6. The HostTopN
The hostTopN group is used to prepare reports that describe the
that top a list ordered by one of their statistics. The
statistics are samples of one of their base statistics over
interval specified by the management station. Thus, these
are rate based. The management station also selects how many
hosts are reported. This group consists of the
and the hostTopNTable, and requires the implementation of the
group
2.3.7. The Matrix
The matrix group stores statistics for conversations between sets
two addresses. As the device detects a new conversation, it
a new entry in its tables. This group consists of
matrixControlTable, the matrixSDTable and the matrixDSTable
2.3.8. The Filter
The filter group allows packets to be matched by a filter equation
These matched packets form a data stream that may be captured or
generate events. This group consists of the filterTable and
channelTable
Waldbusser Standards Track [Page 7]
RFC 2819 Remote Network Monitoring MIB May 2000
2.3.9. The Packet Capture
The Packet Capture group allows packets to be captured after
flow through a channel. This group consists of
bufferControlTable and the captureBufferTable, and requires
implementation of the filter group
2.3.10. The Event
The event group controls the generation and notification of
from this device. This group consists of the eventTable and
logTable
3. Control of Remote Network Monitoring
Due to the complex nature of the available functions in
devices, the functions often need user configuration. In many cases
the function requires parameters to be set up for a data
operation. The operation can proceed only after these parameters
fully set up
Many functional groups in this MIB have one or more tables in
to set up control parameters, and one or more data tables in which
place the results of the operation. The control tables are
read-write in nature, while the data tables are typically read-only
Because the parameters in the control table often describe
data in the data table, many of the parameters can be modified
when the control entry is invalid. Thus, the method for
these parameters is to invalidate the control entry, causing
deletion and the deletion of any associated data entries, and
create a new control entry with the proper parameters. Deleting
control entry also gives a convenient method for reclaiming
resources used by the associated data
Some objects in this MIB provide a mechanism to execute an action
the remote monitoring device. These objects may execute an action
a result of a change in the state of the object. For those
in this MIB, a request to set an object to the same value as
currently holds would thus cause no action to occur
To facilitate control by multiple managers, resources have to
shared among the managers. These resources are typically the
and computation resources that a function requires
Waldbusser Standards Track [Page 8]
RFC 2819 Remote Network Monitoring MIB May 2000
3.1. Resource Sharing Among Multiple Management
When multiple management stations wish to use functions that
for a finite amount of resources on a device, a method to
this sharing of resources is required. Potential conflicts include
o Two management stations wish to simultaneously use
that together would exceed the capability of the device
o A management station uses a significant amount of resources
a long period of time
o A management station uses resources and then crashes
forgetting to free the resources so others may use them
A mechanism is provided for each management station
function in this MIB to avoid these conflicts and to help
them when they occur. Each function has a label identifying
initiator (owner) of the function. This label is set by
initiator to provide for the following possibilities
o A management station may recognize resources it owns and
longer needs
o A network operator can find the management station that
the resource and negotiate for it to be freed
o A network operator may decide to unilaterally free
another network operator has reserved
o Upon initialization, a management station may
resources it had reserved in the past. With this
it may free the resources if it no longer needs them
Management stations and probes should support any format of the
string dictated by the local policy of the organization. It
suggested that this name contain one or more of the following:
address, management station name, network manager's name, location
or phone number. This information will help users to share
resources more effectively
There is often default functionality that the device or
administrator of the probe (often the network administrator)
to set up. The resources associated with this functionality are
owned by the device itself or by the network administrator, and
intended to be long-lived. In this case, the device or
administrator will set the relevant owner object to a string
with 'monitor'. Indiscriminate modification of the monitor-
configuration by network management stations is discouraged.
fact, a network management station should only modify these
under the direction of the administrator of the probe
Waldbusser Standards Track [Page 9]
RFC 2819 Remote Network Monitoring MIB May 2000
Resources on a probe are scarce and are typically allocated
control rows are created by an application. Since many
may be using a probe simultaneously, indiscriminate allocation
resources to particular applications is very likely to cause
shortages in the probe
When a network management station wishes to utilize a function in
monitor, it is encouraged to first scan the control table of
function to find an instance with similar parameters to share.
is especially true for those instances owned by the monitor,
can be assumed to change infrequently. If a management
decides to share an instance owned by another management station,
should understand that the management station that owns the
may indiscriminately modify or delete it
It should be noted that a management application should have the
trust in a monitor-owned row because it should be changed
infrequently. A row owned by the management application is
long-lived because a network administrator is more likely to re
assign resources from a row that is in use by one user than from
monitor-owned row that is potentially in use by many users. A
owned by another application would be even less long-lived
the other application may delete or modify that row completely at
discretion
3.2. Row Addition Among Multiple Management
The addition of new rows is achieved using the method described
RFC 1905 [13]. In this MIB, rows are often added to a table in
to configure a function. This configuration usually
parameters that control the operation of the function. The
must check these parameters to make sure they are appropriate
restrictions defined in this MIB as well as any
specific restrictions such as lack of resources. The
implementor may be confused as to when to check these parameters
when to signal to the management station that the parameters
invalid. There are two opportunities
o When the management station sets each parameter object
o When the management station sets the entry status object
valid
If the latter is chosen, it would be unclear to the
station which of the several parameters was invalid and caused
badValue error to be emitted. Thus, wherever possible,
implementor should choose the former as it will provide
information to the management station
Waldbusser Standards Track [Page 10]
RFC 2819 Remote Network Monitoring MIB May 2000
A problem can arise when multiple management stations attempt to
configuration information simultaneously using SNMP. When
involves the addition of a new conceptual row in the same
table, the managers may collide, attempting to create the same entry
To guard against these collisions, each such control entry contains
status object with special semantics that help to arbitrate among
managers. If an attempt is made with the row addition mechanism
create such a status object and that object already exists, an
is returned. When more than one manager simultaneously attempts
create the same conceptual row, only the first can succeed.
others will receive an error
When a manager wishes to create a new control entry, it needs
choose an index for that row. It may choose this index in a
of ways, hopefully minimizing the chances that the index is in use
another manager. If the index is in use, the mechanism
previously will guard against collisions. Examples of schemes
choose index values include random selection or scanning the
table looking for the first unused index. Because index values
be any valid value in the range and they are chosen by the manager
the agent must allow a row to be created with any unused index
if it has the resources to create a new row
Some tables in this MIB reference other tables within this MIB.
creating or deleting entries in these tables, it is
allowable for dangling references to exist. There is no
order for creating or deleting entries in these tables
4.
The following conventions are used throughout the RMON MIB and
companion documents
Good
Good packets are error-free packets that have a valid frame length
For example, on Ethernet, good packets are error-free packets
are between 64 octets long and 1518 octets long. They follow
form defined in IEEE 802.3 section 3.2.all
Bad
Bad packets are packets that have proper framing and are
recognized as packets, but contain errors within the packet or
an invalid length. For example, on Ethernet, bad packets have
valid preamble and SFD, but have a bad CRC, or are either
than 64 octets or longer than 1518 octets
Waldbusser Standards Track [Page 11]
RFC 2819 Remote Network Monitoring MIB May 2000
5.
RMON-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY
NOTIFICATION-TYPE, mib-2, Counter32,
Integer32, TimeTicks FROM SNMPv2-
TEXTUAL-CONVENTION, DisplayString FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP
NOTIFICATION-GROUP FROM SNMPv2-CONF
-- Remote Network Monitoring
rmonMibModule MODULE-
LAST-UPDATED "200005110000Z" -- 11 May, 2000
ORGANIZATION "IETF RMON MIB Working Group
CONTACT-
"Steve
Phone: +1-650-948-6500
Fax: +1-650-745-0671
Email: waldbusser@nextbeacon.com
"Remote network monitoring devices, often
monitors or probes, are instruments that exist
the purpose of managing a network. This MIB
objects for managing remote network monitoring devices."
REVISION "200005110000Z" -- 11 May, 2000
"Reformatted into SMIv2 format
This version published as RFC 2819."
REVISION "199502010000Z" -- 1 Feb, 1995
"Bug fixes, clarifications and minor changes based
implementation experience, published as RFC1757 [18].
Two changes were made to object definitions
1) A new status bit has been defined for
captureBufferPacketStatus object, indicating that
packet order within the capture buffer may not be identical
the packet order as received off the wire. This bit may
Waldbusser Standards Track [Page 12]
RFC 2819 Remote Network Monitoring MIB May 2000
be used for packets transmitted by the probe. Older
applications can safely ignore this status bit, which might
used by newer agents
2) The packetMatch trap has been removed. This trap was
actually 'approved' and was not added to this document
with the risingAlarm and fallingAlarm traps. The
trap could not be throttled, which could cause disruption
normal network traffic under some circumstances. An NMS
configure a risingAlarm threshold on the
channelMatches instance if a trap is desired for a
event. Note that logging of packetMatch events is
supported--only trap generation for such events has
removed
In addition, several clarifications to individual
definitions have been added to assist agent and
implementors
- global definition of 'good packets' and 'bad packets
- more detailed text governing conceptual row creation
- instructions for probes relating to interface changes
- clarification of some ethernet counter
- recommended formula for calculating network
- clarification of channel and captureBuffer behavior for
unusual
- examples of proper instance naming for each table
REVISION "199111010000Z" -- 1 Nov, 1991
"The original version of this MIB, published as RFC1271."
::= { rmonConformance 8 }
rmon OBJECT IDENTIFIER ::= { mib-2 16 }
-- textual
OwnerString ::= TEXTUAL-
STATUS
Waldbusser Standards Track [Page 13]
RFC 2819 Remote Network Monitoring MIB May 2000
"This data type is used to model an
assigned name of the owner of a resource.
must accept values composed of well-formed NVT
sequences. In addition, implementations should
values composed of well-formed UTF-8 sequences
It is suggested that this name contain one or more
the following: IP address, management station name
network manager's name, location, or phone number
In some cases the agent itself will be the owner
an entry. In these cases, this string shall be
to a string starting with 'monitor'.
SNMP access control is articulated entirely in
of the contents of MIB views; access to a
SNMP object instance depends only upon its
or absence in a particular MIB view and never
its value or the value of related object instances
Thus, objects of this type afford resolution
resource contention only among
managers; they realize no access control
with respect to uncooperative parties."
SYNTAX OCTET STRING (SIZE (0..127))
EntryStatus ::= TEXTUAL-
STATUS
"The status of a table entry
Setting this object to the value invalid(4) has
effect of invalidating the corresponding entry
That is, it effectively disassociates the
identified with said entry
It is an implementation-specific matter as to
the agent removes an invalidated entry from the table
Accordingly, management stations must be prepared
receive tabular information from agents that
to entries currently not in use.
interpretation of such entries requires
of the relevant EntryStatus object
An existing instance of this object cannot be set
createRequest(2). This object may only be set
createRequest(2) when this instance is created.
this object is created, the agent may wish to
supplemental object instances with default
to complete a conceptual row in this table. Because
Waldbusser Standards Track [Page 14]
RFC 2819 Remote Network Monitoring MIB May 2000
creation of these default objects is entirely at the
of the agent, the manager must not assume that any will
created, but may make use of any that are created
Immediately after completing the create operation, the
must set this object to underCreation(3).
When in the underCreation(3) state, an entry is allowed
exist in a possibly incomplete, possibly inconsistent state
usually to allow it to be modified in multiple PDUs. When
this state, an entry is not fully active
Entries shall exist in the underCreation(3) state
the management station is finished configuring the
and sets this object to valid(1) or aborts, setting
object to invalid(4). If the agent determines that
entry has been in the underCreation(3) state for
abnormally long time, it may decide that the
station has crashed. If the agent makes this decision
it may set this object to invalid(4) to reclaim
entry. A prudent agent will understand that
management station may need to wait for human
and will allow for that possibility in
determination of this abnormally long period
An entry in the valid(1) state is fully configured
consistent and fully represents the configuration
operation such a row is intended to represent.
example, it could be a statistical function that
configured and active, or a filter that is
in the list of filters processed by the packet
process
A manager is restricted to changing the state of an entry
the following ways
To: valid createRequest underCreation
From
valid OK NO OK
createRequest N/A N/A N/A N/
underCreation OK NO OK
invalid NO NO NO
nonExistent NO OK NO
In the table above, it is not applicable to move the
from the createRequest state to any other state because
manager will never find the variable in that state.
nonExistent state is not a value of the enumeration,
it means that the entryStatus variable does not exist at all
Waldbusser Standards Track [Page 15]
RFC 2819 Remote Network Monitoring MIB May 2000
An agent may allow an entryStatus variable to change state
additional ways, so long as the semantics of the states
followed. This allowance is made to ease the implementation
the agent and is made despite the fact that managers
never exercise these additional state transitions."
SYNTAX INTEGER {
valid(1),
createRequest(2),
underCreation(3),
invalid(4)
}
statistics OBJECT IDENTIFIER ::= { rmon 1 }
history OBJECT IDENTIFIER ::= { rmon 2 }
alarm OBJECT IDENTIFIER ::= { rmon 3 }
hosts OBJECT IDENTIFIER ::= { rmon 4 }
hostTopN OBJECT IDENTIFIER ::= { rmon 5 }
matrix OBJECT IDENTIFIER ::= { rmon 6 }
filter OBJECT IDENTIFIER ::= { rmon 7 }
capture OBJECT IDENTIFIER ::= { rmon 8 }
event OBJECT IDENTIFIER ::= { rmon 9 }
rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }
-- The Ethernet Statistics
--
-- Implementation of the Ethernet Statistics group is optional
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The ethernet statistics group contains statistics measured by
-- probe for each monitored interface on this device.
-- statistics take the form of free running counters that start
-- zero when a valid entry is created
--
-- This group currently has statistics defined only
-- Ethernet interfaces. Each etherStatsEntry contains
-- for one Ethernet interface. The probe must create
-- etherStats entry for each monitored Ethernet
-- on the device
etherStatsTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of Ethernet statistics entries."
::= { statistics 1 }
Waldbusser Standards Track [Page 16]
RFC 2819 Remote Network Monitoring MIB May 2000
etherStatsEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A collection of statistics kept for a
Ethernet interface. As an example, an instance of
etherStatsPkts object might be named etherStatsPkts.1"
INDEX { etherStatsIndex }
::= { etherStatsTable 1 }
EtherStatsEntry ::= SEQUENCE {
etherStatsIndex Integer32,
etherStatsDataSource OBJECT IDENTIFIER
etherStatsDropEvents Counter32,
etherStatsOctets Counter32,
etherStatsPkts Counter32,
etherStatsBroadcastPkts Counter32,
etherStatsMulticastPkts Counter32,
etherStatsCRCAlignErrors Counter32,
etherStatsUndersizePkts Counter32,
etherStatsOversizePkts Counter32,
etherStatsFragments Counter32,
etherStatsJabbers Counter32,
etherStatsCollisions Counter32,
etherStatsPkts64Octets Counter32,
etherStatsPkts65to127Octets Counter32,
etherStatsPkts128to255Octets Counter32,
etherStatsPkts256to511Octets Counter32,
etherStatsPkts512to1023Octets Counter32,
etherStatsPkts1024to1518Octets Counter32,
etherStatsOwner OwnerString
etherStatsStatus
}
etherStatsIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The value of this object uniquely identifies
etherStats entry."
::= { etherStatsEntry 1 }
etherStatsDataSource OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 17]
RFC 2819 Remote Network Monitoring MIB May 2000
"This object identifies the source of the data
this etherStats entry is configured to analyze.
source can be any ethernet interface on this device
In order to identify a particular interface, this
shall identify the instance of the ifIndex object
defined in RFC 2233 [17], for the desired interface
For example, if an entry were to receive data
interface #1, this object would be set to ifIndex.1.
The statistics in this group reflect all
on the local network segment attached to the
interface
An agent may or may not be able to tell if
changes to the media of the interface have occurred
necessitate an invalidation of this entry. For example,
hot-pluggable ethernet card could be pulled out and
by a token-ring card. In such a case, if the agent has
knowledge of the change, it is recommended that
invalidate this entry
This object may not be modified if the
etherStatsStatus object is equal to valid(1)."
::= { etherStatsEntry 2 }
etherStatsDropEvents OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of events in which
were dropped by the probe due to lack of resources
Note that this number is not necessarily the number
packets dropped; it is just the number of times
condition has been detected."
::= { etherStatsEntry 3 }
etherStatsOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The total number of octets of data (
those in bad packets) received on
network (excluding framing bits but
FCS octets).
Waldbusser Standards Track [Page 18]
RFC 2819 Remote Network Monitoring MIB May 2000
This object can be used as a reasonable estimate
10-Megabit ethernet utilization. If greater precision
desired, the etherStatsPkts and etherStatsOctets
should be sampled before and after a common interval.
differences in the sampled values are Pkts and Octets
respectively, and the number of seconds in the interval
Interval. These values are used to calculate the
as follows
Pkts * (9.6 + 6.4) + (Octets * .8)
Utilization = -------------------------------------
Interval * 10,000
The result of this equation is the value Utilization
is the percent utilization of the ethernet segment on
scale of 0 to 100 percent."
::= { etherStatsEntry 4 }
etherStatsPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including bad packets
broadcast packets, and multicast packets) received."
::= { etherStatsEntry 5 }
etherStatsBroadcastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of good packets received that
directed to the broadcast address. Note that
does not include multicast packets."
::= { etherStatsEntry 6 }
etherStatsMulticastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of good packets received that
directed to a multicast address. Note that this
does not include packets directed to the
Waldbusser Standards Track [Page 19]
RFC 2819 Remote Network Monitoring MIB May 2000
address."
::= { etherStatsEntry 7 }
etherStatsCRCAlignErrors OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets received
had a length (excluding framing bits,
including FCS octets) of between 64 and 1518
octets, inclusive, but had either a
Frame Check Sequence (FCS) with an
number of octets (FCS Error) or a bad FCS
a non-integral number of octets (Alignment Error)."
::= { etherStatsEntry 8 }
etherStatsUndersizePkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets received that
less than 64 octets long (excluding framing bits
but including FCS octets) and were otherwise
formed."
::= { etherStatsEntry 9 }
etherStatsOversizePkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets received that
longer than 1518 octets (excluding framing bits
but including FCS octets) and were
well formed."
::= { etherStatsEntry 10 }
etherStatsFragments OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 20]
RFC 2819 Remote Network Monitoring MIB May 2000
"The total number of packets received that were less
64 octets in length (excluding framing bits but
FCS octets) and had either a bad Frame Check
(FCS) with an integral number of octets (FCS Error) or
bad FCS with a non-integral number of octets (
Error).
Note that it is entirely normal for etherStatsFragments
increment. This is because it counts both runts (which
normal occurrences due to collisions) and noise hits."
::= { etherStatsEntry 11 }
etherStatsJabbers OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets received that
longer than 1518 octets (excluding framing bits
but including FCS octets), and had either a
Frame Check Sequence (FCS) with an integral
of octets (FCS Error) or a bad FCS with a non-
number of octets (Alignment Error).
Note that this definition of jabber is
than the definition in IEEE-802.3 section 8.2.1.5
(10BASE5) and section 10.3.1.4 (10BASE2).
documents define jabber as the condition where
packet exceeds 20 ms. The allowed range to
jabber is between 20 ms and 150 ms."
::= { etherStatsEntry 12 }
etherStatsCollisions OBJECT-
SYNTAX Counter32
UNITS "Collisions
MAX-ACCESS read-
STATUS
"The best estimate of the total number of
on this Ethernet segment
The value returned will depend on the location of
RMON probe. Section 8.2.1.3 (10BASE-5) and
10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that
station must detect a collision, in the receive mode,
three or more stations are transmitting simultaneously.
repeater port must detect a collision when two or
Waldbusser Standards Track [Page 21]
RFC 2819 Remote Network Monitoring MIB May 2000
stations are transmitting simultaneously. Thus a
placed on a repeater port could record more
than a probe connected to a station on the same
would
Probe location plays a much smaller role when
10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3
defines a collision as the simultaneous presence of
on the DO and RD circuits (transmitting and
at the same time). A 10BASE-T station can only
collisions when it is transmitting. Thus probes placed
a station and a repeater, should report the same number
collisions
Note also that an RMON probe inside a repeater
ideally report collisions between the repeater and one
more other hosts (transmit collisions as defined by
802.3k) plus receiver collisions observed on any
segments to which the repeater is connected."
::= { etherStatsEntry 13 }
etherStatsPkts64Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including
packets) received that were 64 octets in
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 14 }
etherStatsPkts65to127Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including
packets) received that were
65 and 127 octets in length
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 15 }
etherStatsPkts128to255Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
Waldbusser Standards Track [Page 22]
RFC 2819 Remote Network Monitoring MIB May 2000
STATUS
"The total number of packets (including
packets) received that were
128 and 255 octets in length
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 16 }
etherStatsPkts256to511Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including
packets) received that were
256 and 511 octets in length
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 17 }
etherStatsPkts512to1023Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including
packets) received that were
512 and 1023 octets in length
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 18 }
etherStatsPkts1024to1518Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including
packets) received that were
1024 and 1518 octets in length
(excluding framing bits but including FCS octets)."
::= { etherStatsEntry 19 }
etherStatsOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 23]
RFC 2819 Remote Network Monitoring MIB May 2000
"The entity that configured this entry and is
using the resources assigned to it."
::= { etherStatsEntry 20 }
etherStatsStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this etherStats entry."
::= { etherStatsEntry 21 }
-- The History Control
-- Implementation of the History Control group is optional
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The history control group controls the periodic
-- sampling of data from various types of networks.
-- historyControlTable stores configuration entries that
-- define an interface, polling period, and other parameters
-- Once samples are taken, their data is stored in an
-- in a media-specific table. Each such entry defines
-- sample, and is associated with the historyControlEntry
-- caused the sample to be taken. Each counter in
-- etherHistoryEntry counts the same event as its similarly-
-- counterpart in the etherStatsEntry, except that each value
-- is a cumulative sum during a sampling period
--
-- If the probe keeps track of the time of day, it should
-- the first sample of the history at a time such
-- when the next hour of the day begins, a sample
-- started at that instant. This tends to make
-- user-friendly reports, and enables comparison of
-- from different probes that have relatively accurate
-- of day
--
-- The probe is encouraged to add two history control
-- per monitored interface upon initialization that describe a
-- term and a long term polling period. Suggested parameters are 30
-- seconds for the short term polling period and 30 minutes
-- the long term period
historyControlTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
Waldbusser Standards Track [Page 24]
RFC 2819 Remote Network Monitoring MIB May 2000
STATUS
"A list of history control entries."
::= { history 1 }
historyControlEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A list of parameters that set up a periodic sampling
statistics. As an example, an instance of
historyControlInterval object might be
historyControlInterval.2"
INDEX { historyControlIndex }
::= { historyControlTable 1 }
HistoryControlEntry ::= SEQUENCE {
historyControlIndex Integer32,
historyControlDataSource OBJECT IDENTIFIER
historyControlBucketsRequested Integer32,
historyControlBucketsGranted Integer32,
historyControlInterval Integer32,
historyControlOwner OwnerString
historyControlStatus
}
historyControlIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an entry in
historyControl table. Each such entry defines
set of samples at a particular interval for
interface on the device."
::= { historyControlEntry 1 }
historyControlDataSource OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"This object identifies the source of the data
which historical data was collected
placed in a media-specific table on behalf of
historyControlEntry. This source can be
interface on this device. In order to
Waldbusser Standards Track [Page 25]
RFC 2819 Remote Network Monitoring MIB May 2000
a particular interface, this object shall
the instance of the ifIndex object,
in RFC 2233 [17], for the desired interface
For example, if an entry were to receive data
interface #1, this object would be set to ifIndex.1.
The statistics in this group reflect all
on the local network segment attached to the
interface
An agent may or may not be able to tell if
changes to the media of the interface have occurred
necessitate an invalidation of this entry. For example,
hot-pluggable ethernet card could be pulled out and
by a token-ring card. In such a case, if the agent has
knowledge of the change, it is recommended that
invalidate this entry
This object may not be modified if the
historyControlStatus object is equal to valid(1)."
::= { historyControlEntry 2 }
historyControlBucketsRequested OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The requested number of discrete time
over which data is to be saved in the part of
media-specific table associated with
historyControlEntry
When this object is created or modified, the
should set historyControlBucketsGranted as closely
this object as is possible for the particular
implementation and available resources."
DEFVAL { 50 }
::= { historyControlEntry 3 }
historyControlBucketsGranted OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The number of discrete sampling
over which data shall be saved in the part
the media-specific table associated with
historyControlEntry
Waldbusser Standards Track [Page 26]
RFC 2819 Remote Network Monitoring MIB May 2000
When the associated
object is created or modified, the
should set this object as closely to the
value as is possible for the
probe implementation and available resources.
probe must not lower this value except as a
of a modification to the
historyControlBucketsRequested object
There will be times when the actual number
buckets associated with this entry is less
the value of this object. In this case, at
end of each sampling interval, a new bucket
be added to the media-specific table
When the number of buckets reaches the value
this object and a new bucket is to be added to
media-specific table, the oldest bucket
with this historyControlEntry shall be deleted
the agent so that the new bucket can be added
When the value of this object changes to a value
than the current value, entries are
from the media-specific table associated with
historyControlEntry. Enough of the oldest of
entries shall be deleted by the agent so that
number remains less than or equal to the new value
this object
When the value of this object changes to a value
than the current value, the number of associated media
specific entries may be allowed to grow."
::= { historyControlEntry 4 }
historyControlInterval OBJECT-
SYNTAX Integer32 (1..3600)
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The interval in seconds over which the data
sampled for each bucket in the part of
media-specific table associated with
historyControlEntry. This interval
be set to any number of seconds between 1
3600 (1 hour).
Because the counters in a bucket may overflow at
Waldbusser Standards Track [Page 27]
RFC 2819 Remote Network Monitoring MIB May 2000
maximum value with no indication, a prudent manager
take into account the possibility of overflow in any
the associated counters. It is important to consider
minimum time in which any counter could overflow on
particular media type and set the
object to a value less than this interval. This
typically most important for the 'octets' counter in
media-specific table. For example, on an
network, the etherHistoryOctets counter could
in about one hour at the Ethernet's
utilization
This object may not be modified if the
historyControlStatus object is equal to valid(1)."
DEFVAL { 1800 }
::= { historyControlEntry 5 }
historyControlOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it."
::= { historyControlEntry 6 }
historyControlStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this historyControl entry
Each instance of the media-specific table
with this historyControlEntry will be deleted by the
if this historyControlEntry is not equal to valid(1)."
::= { historyControlEntry 7 }
-- The Ethernet History
-- Implementation of the Ethernet History group is optional
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The Ethernet History group records periodic statistical
-- from a network and stores them for later retrieval
-- Once samples are taken, their data is stored in an
-- in a media-specific table. Each such entry defines
Waldbusser Standards Track [Page 28]
RFC 2819 Remote Network Monitoring MIB May 2000
-- sample, and is associated with the historyControlEntry
-- caused the sample to be taken. This group defines
-- etherHistoryTable, for Ethernet networks
--
etherHistoryTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of Ethernet history entries."
::= { history 2 }
etherHistoryEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An historical sample of Ethernet statistics on a
Ethernet interface. This sample is associated with
historyControlEntry which set up the parameters
a regular collection of these samples. As an example,
instance of the etherHistoryPkts object might be
etherHistoryPkts.2.89"
INDEX { etherHistoryIndex , etherHistorySampleIndex }
::= { etherHistoryTable 1 }
EtherHistoryEntry ::= SEQUENCE {
etherHistoryIndex Integer32,
etherHistorySampleIndex Integer32,
etherHistoryIntervalStart TimeTicks
etherHistoryDropEvents Counter32,
etherHistoryOctets Counter32,
etherHistoryPkts Counter32,
etherHistoryBroadcastPkts Counter32,
etherHistoryMulticastPkts Counter32,
etherHistoryCRCAlignErrors Counter32,
etherHistoryUndersizePkts Counter32,
etherHistoryOversizePkts Counter32,
etherHistoryFragments Counter32,
etherHistoryJabbers Counter32,
etherHistoryCollisions Counter32,
etherHistoryUtilization Integer32
}
etherHistoryIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
Waldbusser Standards Track [Page 29]
RFC 2819 Remote Network Monitoring MIB May 2000
STATUS
"The history of which this entry is a part.
history identified by a particular value of
index is the same history as
by the same value of historyControlIndex."
::= { etherHistoryEntry 1 }
etherHistorySampleIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies the
sample this entry represents among all
associated with the same historyControlEntry
This index starts at 1 and increases by
as each new sample is taken."
::= { etherHistoryEntry 2 }
etherHistoryIntervalStart OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the start of the
over which this sample was measured. If the
keeps track of the time of day, it should
the first sample of the history at a time such
when the next hour of the day begins, a sample
started at that instant. Note that following
rule may require the probe to delay collecting
first sample of the history, as each sample must
of the same interval. Also note that the sample
is currently being collected is not accessible in
table until the end of its interval."
::= { etherHistoryEntry 3 }
etherHistoryDropEvents OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of events in which
were dropped by the probe due to lack of
during this sampling interval. Note that this
is not necessarily the number of packets dropped,
is just the number of times this condition has
Waldbusser Standards Track [Page 30]
RFC 2819 Remote Network Monitoring MIB May 2000
detected."
::= { etherHistoryEntry 4 }
etherHistoryOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The total number of octets of data (
those in bad packets) received on
network (excluding framing bits but
FCS octets)."
::= { etherHistoryEntry 5 }
etherHistoryPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets (including bad packets
received during this sampling interval."
::= { etherHistoryEntry 6 }
etherHistoryBroadcastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets received during
sampling interval that were directed to
broadcast address."
::= { etherHistoryEntry 7 }
etherHistoryMulticastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets received during
sampling interval that were directed to
multicast address. Note that this number does
include packets addressed to the broadcast address."
::= { etherHistoryEntry 8 }
Waldbusser Standards Track [Page 31]
RFC 2819 Remote Network Monitoring MIB May 2000
etherHistoryCRCAlignErrors OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets received during
sampling interval that had a length (
framing bits but including FCS octets)
64 and 1518 octets, inclusive, but had either a bad
Check Sequence (FCS) with an integral number of
(FCS Error) or a bad FCS with a non-integral
of octets (Alignment Error)."
::= { etherHistoryEntry 9 }
etherHistoryUndersizePkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets received during
sampling interval that were less than 64
long (excluding framing bits but including
octets) and were otherwise well formed."
::= { etherHistoryEntry 10 }
etherHistoryOversizePkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets received during
sampling interval that were longer than 1518
octets (excluding framing bits but
FCS octets) but were otherwise well formed."
::= { etherHistoryEntry 11 }
etherHistoryFragments OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets received during
sampling interval that were less than 64 octets
length (excluding framing bits but including
Waldbusser Standards Track [Page 32]
RFC 2819 Remote Network Monitoring MIB May 2000
octets) had either a bad Frame Check Sequence (FCS
with an integral number of octets (FCS Error) or a
FCS with a non-integral number of octets (
Error).
Note that it is entirely normal for etherHistoryFragments
increment. This is because it counts both runts (which
normal occurrences due to collisions) and noise hits."
::= { etherHistoryEntry 12 }
etherHistoryJabbers OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets received during
sampling interval that were longer than 1518
(excluding framing bits but including FCS octets),
and had either a bad Frame Check Sequence (FCS
with an integral number of octets (FCS Error)
a bad FCS with a non-integral number of
(Alignment Error).
Note that this definition of jabber is
than the definition in IEEE-802.3 section 8.2.1.5
(10BASE5) and section 10.3.1.4 (10BASE2).
documents define jabber as the condition where
packet exceeds 20 ms. The allowed range to
jabber is between 20 ms and 150 ms."
::= { etherHistoryEntry 13 }
etherHistoryCollisions OBJECT-
SYNTAX Counter32
UNITS "Collisions
MAX-ACCESS read-
STATUS
"The best estimate of the total number of
on this Ethernet segment during this
interval
The value returned will depend on the location of
RMON probe. Section 8.2.1.3 (10BASE-5) and
10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that
station must detect a collision, in the receive mode,
three or more stations are transmitting simultaneously.
repeater port must detect a collision when two or
Waldbusser Standards Track [Page 33]
RFC 2819 Remote Network Monitoring MIB May 2000
stations are transmitting simultaneously. Thus a
placed on a repeater port could record more
than a probe connected to a station on the same
would
Probe location plays a much smaller role when
10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3
defines a collision as the simultaneous presence of
on the DO and RD circuits (transmitting and
at the same time). A 10BASE-T station can only
collisions when it is transmitting. Thus probes placed
a station and a repeater, should report the same number
collisions
Note also that an RMON probe inside a repeater
ideally report collisions between the repeater and one
more other hosts (transmit collisions as defined by
802.3k) plus receiver collisions observed on any
segments to which the repeater is connected."
::= { etherHistoryEntry 14 }
etherHistoryUtilization OBJECT-
SYNTAX Integer32 (0..10000)
MAX-ACCESS read-
STATUS
"The best estimate of the mean physical
network utilization on this interface during
sampling interval, in hundredths of a percent."
::= { etherHistoryEntry 15 }
-- The Alarm
-- Implementation of the Alarm group is optional. The Alarm
-- requires the implementation of the Event group
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The Alarm group periodically takes statistical samples
-- variables in the probe and compares them to thresholds that
-- been configured. The alarm table stores
-- entries that each define a variable, polling period,
-- threshold parameters. If a sample is found to cross
-- threshold values, an event is generated. Only variables
-- resolve to an ASN.1 primitive type of INTEGER (INTEGER, Integer32,
-- Counter32, Counter64, Gauge32, or TimeTicks) may be monitored
-- this way
--
Waldbusser Standards Track [Page 34]
RFC 2819 Remote Network Monitoring MIB May 2000
-- This function has a hysteresis mechanism to limit the
-- of events. This mechanism generates one event as a
-- is crossed in the appropriate direction. No more events
-- generated for that threshold until the opposite threshold
-- crossed
--
-- In the case of a sampling a deltaValue, a probe may
-- this mechanism with more precision if it takes a delta
-- twice per period, each time comparing the sum of the latest
-- samples to the threshold. This allows the detection of
-- crossings that span the sampling boundary. Note that this
-- not require any special configuration of the threshold value
-- It is suggested that probes implement this more precise algorithm
alarmTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of alarm entries."
::= { alarm 1 }
alarmEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A list of parameters that set up a periodic
for alarm conditions. For example, an instance of
alarmValue object might be named alarmValue.8"
INDEX { alarmIndex }
::= { alarmTable 1 }
AlarmEntry ::= SEQUENCE {
alarmIndex Integer32,
alarmInterval Integer32,
alarmVariable OBJECT IDENTIFIER
alarmSampleType INTEGER
alarmValue Integer32,
alarmStartupAlarm INTEGER
alarmRisingThreshold Integer32,
alarmFallingThreshold Integer32,
alarmRisingEventIndex Integer32,
alarmFallingEventIndex Integer32,
alarmOwner OwnerString
alarmStatus
}
Waldbusser Standards Track [Page 35]
RFC 2819 Remote Network Monitoring MIB May 2000
alarmIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an entry in
alarm table. Each such entry defines
diagnostic sample at a particular
for an object on the device."
::= { alarmEntry 1 }
alarmInterval OBJECT-
SYNTAX Integer32
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The interval in seconds over which the data
sampled and compared with the rising and
thresholds. When setting this variable,
should be taken in the case of
sampling - the interval should be set short
that the sampled variable is very unlikely
increase or decrease by more than 2^31 - 1
a single sampling interval
This object may not be modified if the
alarmStatus object is equal to valid(1)."
::= { alarmEntry 2 }
alarmVariable OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"The object identifier of the particular variable to
sampled. Only variables that resolve to an ASN.1
type of INTEGER (INTEGER, Integer32, Counter32, Counter64,
Gauge, or TimeTicks) may be sampled
Because SNMP access control is articulated
in terms of the contents of MIB views, no
control mechanism exists that can restrict the value
this object to identify only those objects that
in a particular MIB view. Because there is thus
acceptable means of restricting the read access
could be obtained through the alarm mechanism,
probe must only grant write access to this object
Waldbusser Standards Track [Page 36]
RFC 2819 Remote Network Monitoring MIB May 2000
those views that have read access to all objects
the probe
During a set operation, if the supplied variable name
not available in the selected MIB view, a badValue
must be returned. If at any time the variable name
an established alarmEntry is no longer available in
selected MIB view, the probe must change the status
this alarmEntry to invalid(4).
This object may not be modified if the
alarmStatus object is equal to valid(1)."
::= { alarmEntry 3 }
alarmSampleType OBJECT-
SYNTAX INTEGER {
absoluteValue(1),
deltaValue(2)
}
MAX-ACCESS read-
STATUS
"The method of sampling the selected variable
calculating the value to be compared against
thresholds. If the value of this object
absoluteValue(1), the value of the selected
will be compared directly with the thresholds at
end of the sampling interval. If the value of
object is deltaValue(2), the value of the
variable at the last sample will be subtracted
the current value, and the difference compared
the thresholds
This object may not be modified if the
alarmStatus object is equal to valid(1)."
::= { alarmEntry 4 }
alarmValue OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The value of the statistic during the last
period. For example, if the sample type is deltaValue
this value will be the difference between the
at the beginning and end of the period. If the
type is absoluteValue, this value will be the
value at the end of the period
Waldbusser Standards Track [Page 37]
RFC 2819 Remote Network Monitoring MIB May 2000
This is the value that is compared with the rising
falling thresholds
The value during the current sampling period is
made available until the period is completed and
remain available until the next period completes."
::= { alarmEntry 5 }
alarmStartupAlarm OBJECT-
SYNTAX INTEGER {
risingAlarm(1),
fallingAlarm(2),
risingOrFallingAlarm(3)
}
MAX-ACCESS read-
STATUS
"The alarm that may be sent when this entry is
set to valid. If the first sample after this
becomes valid is greater than or equal to
risingThreshold and alarmStartupAlarm is equal
risingAlarm(1) or risingOrFallingAlarm(3), then a
rising alarm will be generated. If the first
after this entry becomes valid is less than or
to the fallingThreshold and alarmStartupAlarm is
to fallingAlarm(2) or risingOrFallingAlarm(3), then
single falling alarm will be generated
This object may not be modified if the
alarmStatus object is equal to valid(1)."
::= { alarmEntry 6 }
alarmRisingThreshold OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"A threshold for the sampled statistic. When the
sampled value is greater than or equal to this threshold
and the value at the last sampling interval was less
this threshold, a single event will be generated
A single event will also be generated if the
sample after this entry becomes valid is greater than
equal to this threshold and the
alarmStartupAlarm is equal to risingAlarm(1)
risingOrFallingAlarm(3).
After a rising event is generated, another such
Waldbusser Standards Track [Page 38]
RFC 2819 Remote Network Monitoring MIB May 2000
will not be generated until the sampled
falls below this threshold and reaches
alarmFallingThreshold
This object may not be modified if the
alarmStatus object is equal to valid(1)."
::= { alarmEntry 7 }
alarmFallingThreshold OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"A threshold for the sampled statistic. When the
sampled value is less than or equal to this threshold
and the value at the last sampling interval was greater
this threshold, a single event will be generated
A single event will also be generated if the
sample after this entry becomes valid is less than
equal to this threshold and the
alarmStartupAlarm is equal to fallingAlarm(2)
risingOrFallingAlarm(3).
After a falling event is generated, another such
will not be generated until the sampled
rises above this threshold and reaches
alarmRisingThreshold
This object may not be modified if the
alarmStatus object is equal to valid(1)."
::= { alarmEntry 8 }
alarmRisingEventIndex OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The index of the eventEntry that
used when a rising threshold is crossed.
eventEntry identified by a particular value
this index is the same as identified by the same
of the eventIndex object. If there is
corresponding entry in the eventTable,
no association exists. In particular, if this
is zero, no associated event will be generated,
zero is not a valid event index
This object may not be modified if the
Waldbusser Standards Track [Page 39]
RFC 2819 Remote Network Monitoring MIB May 2000
alarmStatus object is equal to valid(1)."
::= { alarmEntry 9 }
alarmFallingEventIndex OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The index of the eventEntry that
used when a falling threshold is crossed.
eventEntry identified by a particular value
this index is the same as identified by the same
of the eventIndex object. If there is
corresponding entry in the eventTable,
no association exists. In particular, if this
is zero, no associated event will be generated,
zero is not a valid event index
This object may not be modified if the
alarmStatus object is equal to valid(1)."
::= { alarmEntry 10 }
alarmOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it."
::= { alarmEntry 11 }
alarmStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this alarm entry."
::= { alarmEntry 12 }
-- The Host
-- Implementation of the Host group is optional
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The host group discovers new hosts on the network
-- keeping a list of source and destination MAC Addresses
-- in good packets. For each of these addresses, the host
Waldbusser Standards Track [Page 40]
RFC 2819 Remote Network Monitoring MIB May 2000
-- keeps a set of statistics. The hostControlTable
-- which interfaces this function is performed on, and
-- some information about the process. On behalf of
-- hostControlEntry, data is collected on an interface and
-- in both the hostTable and the hostTimeTable. If
-- monitoring device finds itself short of resources, it
-- delete entries as needed. It is suggested that the
-- delete the least recently used entries first
-- The hostTable contains entries for each address discovered
-- a particular interface. Each entry contains
-- data about that host. This table is indexed by
-- MAC address of the host, through which a random
-- may be achieved
-- The hostTimeTable contains data in the same format as
-- hostTable, and must contain the same set of hosts, but
-- indexed using hostTimeCreationOrder rather than hostAddress
-- The hostTimeCreationOrder is an integer which
-- the relative order in which a particular entry was
-- and thus inserted into the table. As this order, and
-- the index, is among those entries currently in the table
-- the index for a particular entry may change if
-- (earlier) entry is deleted. Thus the association
-- hostTimeCreationOrder and hostTimeEntry may be broken
-- any time
-- The hostTimeTable has two important uses. The first is
-- fast download of this potentially large table. Because
-- index of this table runs from 1 to the size of the table
-- inclusive, its values are predictable. This allows
-- efficient packing of variables into SNMP PDU's and
-- a table transfer to have multiple packets outstanding
-- These benefits increase transfer rates tremendously
-- The second use of the hostTimeTable is the efficient
-- by the management station of new entries added to the table
-- After the management station has downloaded the entire table
-- it knows that new entries will be added immediately after
-- end of the current table. It can thus detect new entries
-- and retrieve them easily
-- Because the association between hostTimeCreationOrder
-- hostTimeEntry may be broken at any time, the
-- station must monitor the related
-- object. When the management station thus detects a deletion
-- it must assume that any such associations have been broken
-- and invalidate any it has stored locally. This
Waldbusser Standards Track [Page 41]
RFC 2819 Remote Network Monitoring MIB May 2000
-- restarting any download of the hostTimeTable that may have
-- in progress, as well as rediscovering the end of
-- hostTimeTable so that it may detect new entries. If
-- management station does not detect the broken association
-- it may continue to refer to a particular host by
-- creationOrder while unwittingly retrieving the data
-- with another host entirely. If this happens while
-- the host table, the management station may fail to
-- all of the entries in the table
hostControlTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of host table control entries."
::= { hosts 1 }
hostControlEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A list of parameters that set up the discovery of
on a particular interface and the collection of
about these hosts. For example, an instance of
hostControlTableSize object might be
hostControlTableSize.1"
INDEX { hostControlIndex }
::= { hostControlTable 1 }
HostControlEntry ::= SEQUENCE {
hostControlIndex Integer32,
hostControlDataSource OBJECT IDENTIFIER
hostControlTableSize Integer32,
hostControlLastDeleteTime TimeTicks
hostControlOwner OwnerString
hostControlStatus
}
hostControlIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an entry in
Waldbusser Standards Track [Page 42]
RFC 2819 Remote Network Monitoring MIB May 2000
hostControl table. Each such entry
a function that discovers hosts on a particular
and places statistics about them in the hostTable
the hostTimeTable on behalf of this hostControlEntry."
::= { hostControlEntry 1 }
hostControlDataSource OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"This object identifies the source of the data
this instance of the host function. This
can be any interface on this device. In
to identify a particular interface, this object
identify the instance of the ifIndex object,
in RFC 2233 [17], for the desired interface
For example, if an entry were to receive data
interface #1, this object would be set to ifIndex.1.
The statistics in this group reflect all
on the local network segment attached to the
interface
An agent may or may not be able to tell if
changes to the media of the interface have occurred
necessitate an invalidation of this entry. For example,
hot-pluggable ethernet card could be pulled out and
by a token-ring card. In such a case, if the agent has
knowledge of the change, it is recommended that
invalidate this entry
This object may not be modified if the
hostControlStatus object is equal to valid(1)."
::= { hostControlEntry 2 }
hostControlTableSize OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The number of hostEntries in the hostTable and
hostTimeTable associated with this hostControlEntry."
::= { hostControlEntry 3 }
hostControlLastDeleteTime OBJECT-
SYNTAX
MAX-ACCESS read-
Waldbusser Standards Track [Page 43]
RFC 2819 Remote Network Monitoring MIB May 2000
STATUS
"The value of sysUpTime when the last
was deleted from the portion of the
associated with this hostControlEntry. If
deletions have occurred, this value shall be zero."
::= { hostControlEntry 4 }
hostControlOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it."
::= { hostControlEntry 5 }
hostControlStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this hostControl entry
If this object is not equal to valid(1), all
entries in the hostTable, hostTimeTable, and
hostTopNTable shall be deleted by the agent."
::= { hostControlEntry 6 }
hostTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of host entries."
::= { hosts 2 }
hostEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A collection of statistics for a particular host that
been discovered on an interface of this device. For example
an instance of the hostOutBroadcastPkts object might
named hostOutBroadcastPkts.1.6.8.0.32.27.3.176"
INDEX { hostIndex, hostAddress }
::= { hostTable 1 }
Waldbusser Standards Track [Page 44]
RFC 2819 Remote Network Monitoring MIB May 2000
HostEntry ::= SEQUENCE {
hostAddress OCTET STRING
hostCreationOrder Integer32,
hostIndex Integer32,
hostInPkts Counter32,
hostOutPkts Counter32,
hostInOctets Counter32,
hostOutOctets Counter32,
hostOutErrors Counter32,
hostOutBroadcastPkts Counter32,
hostOutMulticastPkts Counter32
}
hostAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The physical address of this host."
::= { hostEntry 1 }
hostCreationOrder OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that defines the relative ordering
the creation time of hosts captured for
particular hostControlEntry. This index
be between 1 and N, where N is the value
the associated hostControlTableSize. The
of the indexes is based on the order of each entry'
insertion into the table, in which entries added
have a lower index value than entries added later
It is important to note that the order for
particular entry may change as an (earlier)
is deleted from the table. Because this order
change, management stations should make use of
hostControlLastDeleteTime variable in
hostControlEntry associated with the
portion of the hostTable. By
this variable, the management station may
the circumstances where a previous
between a value of
and a hostEntry may no longer hold."
::= { hostEntry 2 }
Waldbusser Standards Track [Page 45]
RFC 2819 Remote Network Monitoring MIB May 2000
hostIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The set of collected host statistics of
this entry is a part. The set of
identified by a particular value of
index is associated with the
as identified by the same value of hostControlIndex."
::= { hostEntry 3 }
hostInPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets transmitted to
address since it was added to the hostTable."
::= { hostEntry 4 }
hostOutPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets, including bad packets,
by this address since it was added to the hostTable."
::= { hostEntry 5 }
hostInOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted to this address
it was added to the hostTable (excluding
bits but including FCS octets), except for
octets in bad packets."
::= { hostEntry 6 }
hostOutOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
Waldbusser Standards Track [Page 46]
RFC 2819 Remote Network Monitoring MIB May 2000
STATUS
"The number of octets transmitted by this address
it was added to the hostTable (excluding
bits but including FCS octets), including
octets in bad packets."
::= { hostEntry 7 }
hostOutErrors OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of bad packets transmitted by this
since this host was added to the hostTable."
::= { hostEntry 8 }
hostOutBroadcastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets transmitted by
address that were directed to the broadcast
since this host was added to the hostTable."
::= { hostEntry 9 }
hostOutMulticastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets transmitted by
address that were directed to a multicast
since this host was added to the hostTable
Note that this number does not include
directed to the broadcast address."
::= { hostEntry 10 }
-- host Time
hostTimeTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
Waldbusser Standards Track [Page 47]
RFC 2819 Remote Network Monitoring MIB May 2000
"A list of time-ordered host table entries."
::= { hosts 3 }
hostTimeEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A collection of statistics for a particular host that
been discovered on an interface of this device.
collection includes the relative ordering of the
time of this object. For example, an instance of
hostTimeOutBroadcastPkts object might be
hostTimeOutBroadcastPkts.1.687"
INDEX { hostTimeIndex, hostTimeCreationOrder }
::= { hostTimeTable 1 }
HostTimeEntry ::= SEQUENCE {
hostTimeAddress OCTET STRING
hostTimeCreationOrder Integer32,
hostTimeIndex Integer32,
hostTimeInPkts Counter32,
hostTimeOutPkts Counter32,
hostTimeInOctets Counter32,
hostTimeOutOctets Counter32,
hostTimeOutErrors Counter32,
hostTimeOutBroadcastPkts Counter32,
hostTimeOutMulticastPkts Counter32
}
hostTimeAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The physical address of this host."
::= { hostTimeEntry 1 }
hostTimeCreationOrder OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an entry
the hostTime table among those entries
with the same hostControlEntry. This index
be between 1 and N, where N is the value
Waldbusser Standards Track [Page 48]
RFC 2819 Remote Network Monitoring MIB May 2000
the associated hostControlTableSize. The
of the indexes is based on the order of each entry'
insertion into the table, in which entries added
have a lower index value than entries added later
Thus the management station has the ability
learn of new entries added to this table
downloading the entire table
It is important to note that the index for
particular entry may change as an (earlier)
is deleted from the table. Because this order
change, management stations should make use of
hostControlLastDeleteTime variable in
hostControlEntry associated with the
portion of the hostTimeTable. By
this variable, the management station may
the circumstances where a download of the
may have missed entries, and where a
association between a value of
and a hostTimeEntry may no longer hold."
::= { hostTimeEntry 2 }
hostTimeIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The set of collected host statistics of
this entry is a part. The set of
identified by a particular value of
index is associated with the
as identified by the same value of hostControlIndex."
::= { hostTimeEntry 3 }
hostTimeInPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets transmitted to
address since it was added to the hostTimeTable."
::= { hostTimeEntry 4 }
hostTimeOutPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
Waldbusser Standards Track [Page 49]
RFC 2819 Remote Network Monitoring MIB May 2000
STATUS
"The number of packets, including bad packets,
by this address since it was added to the hostTimeTable."
::= { hostTimeEntry 5 }
hostTimeInOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted to this address
it was added to the hostTimeTable (excluding
bits but including FCS octets), except for
octets in bad packets."
::= { hostTimeEntry 6 }
hostTimeOutOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted by this address
it was added to the hostTimeTable (excluding
bits but including FCS octets), including
octets in bad packets."
::= { hostTimeEntry 7 }
hostTimeOutErrors OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of bad packets transmitted by this
since this host was added to the hostTimeTable."
::= { hostTimeEntry 8 }
hostTimeOutBroadcastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets transmitted by
address that were directed to the broadcast
Waldbusser Standards Track [Page 50]
RFC 2819 Remote Network Monitoring MIB May 2000
since this host was added to the hostTimeTable."
::= { hostTimeEntry 9 }
hostTimeOutMulticastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets transmitted by
address that were directed to a multicast
since this host was added to the hostTimeTable
Note that this number does not include packets
to the broadcast address."
::= { hostTimeEntry 10 }
-- The Host Top "N"
-- Implementation of the Host Top N group is optional. The Host Top
-- group requires the implementation of the host group
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The Host Top N group is used to prepare reports that
-- the hosts that top a list ordered by one of their statistics
-- The available statistics are samples of one of
-- base statistics, over an interval specified by the
-- station. Thus, these statistics are rate based. The
-- station also selects how many such hosts are reported
-- The hostTopNControlTable is used to initiate the generation
-- such a report. The management station may select the
-- of such a report, such as which interface, which statistic
-- how many hosts, and the start and stop times of the sampling
-- When the report is prepared, entries are created in
-- hostTopNTable associated with the relevant hostTopNControlEntry
-- These entries are static for each report after it has
-- prepared
hostTopNControlTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of top N host control entries."
::= { hostTopN 1 }
hostTopNControlEntry OBJECT-
Waldbusser Standards Track [Page 51]
RFC 2819 Remote Network Monitoring MIB May 2000
SYNTAX
MAX-ACCESS not-
STATUS
"A set of parameters that control the creation of a
of the top N hosts according to several metrics.
example, an instance of the hostTopNDuration object
be named hostTopNDuration.3"
INDEX { hostTopNControlIndex }
::= { hostTopNControlTable 1 }
HostTopNControlEntry ::= SEQUENCE {
hostTopNControlIndex Integer32,
hostTopNHostIndex Integer32,
hostTopNRateBase INTEGER
hostTopNTimeRemaining Integer32,
hostTopNDuration Integer32,
hostTopNRequestedSize Integer32,
hostTopNGrantedSize Integer32,
hostTopNStartTime TimeTicks
hostTopNOwner OwnerString
hostTopNStatus
}
hostTopNControlIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an
in the hostTopNControl table. Each
entry defines one top N report prepared
one interface."
::= { hostTopNControlEntry 1 }
hostTopNHostIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The host table for which a top N report will be
on behalf of this entry. The host table identified by
particular value of this index is associated with the
host table as identified by the same value
hostIndex
This object may not be modified if the
hostTopNStatus object is equal to valid(1)."
Waldbusser Standards Track [Page 52]
RFC 2819 Remote Network Monitoring MIB May 2000
::= { hostTopNControlEntry 2 }
hostTopNRateBase OBJECT-
SYNTAX INTEGER {
hostTopNInPkts(1),
hostTopNOutPkts(2),
hostTopNInOctets(3),
hostTopNOutOctets(4),
hostTopNOutErrors(5),
hostTopNOutBroadcastPkts(6),
hostTopNOutMulticastPkts(7)
}
MAX-ACCESS read-
STATUS
"The variable for each host that the
variable is based upon
This object may not be modified if the
hostTopNStatus object is equal to valid(1)."
::= { hostTopNControlEntry 3 }
hostTopNTimeRemaining OBJECT-
SYNTAX Integer32
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The number of seconds left in the report currently
collected. When this object is modified by the
station, a new collection is started, possibly
a currently running report. The new value is
as the requested duration of this report, which
loaded into the associated hostTopNDuration object
When this object is set to a non-zero value,
associated hostTopNEntries shall be
inaccessible by the monitor. While the value of
object is non-zero, it decrements by one per second
it reaches zero. During this time, all
hostTopNEntries shall remain inaccessible. At the
that this object decrements to zero, the report is
accessible in the hostTopNTable. Thus, the
table needs to be created only at the end of the
interval."
DEFVAL { 0 }
::= { hostTopNControlEntry 4 }
Waldbusser Standards Track [Page 53]
RFC 2819 Remote Network Monitoring MIB May 2000
hostTopNDuration OBJECT-
SYNTAX Integer32
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The number of seconds that this report has
during the last sampling interval, or if
report is currently being collected, the
of seconds that this report is being
during this sampling interval
When the associated hostTopNTimeRemaining object is set
this object shall be set by the probe to the same
and shall not be modified until the next
the hostTopNTimeRemaining is set
This value shall be zero if no reports have
requested for this hostTopNControlEntry."
DEFVAL { 0 }
::= { hostTopNControlEntry 5 }
hostTopNRequestedSize OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The maximum number of hosts requested for the top
table
When this object is created or modified, the
should set hostTopNGrantedSize as closely to
object as is possible for the particular
implementation and available resources."
DEFVAL { 10 }
::= { hostTopNControlEntry 6 }
hostTopNGrantedSize OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The maximum number of hosts in the top N table
When the associated hostTopNRequestedSize object
created or modified, the probe should set
object as closely to the requested value as is
for the particular implementation and
Waldbusser Standards Track [Page 54]
RFC 2819 Remote Network Monitoring MIB May 2000
resources. The probe must not lower this value
as a result of a set to the
hostTopNRequestedSize object
Hosts with the highest value of hostTopNRate shall
placed in this table in decreasing order of this
until there is no more room or until there are no
hosts."
::= { hostTopNControlEntry 7 }
hostTopNStartTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime when this top N report
last started. In other words, this is the time
the associated hostTopNTimeRemaining object
modified to start the requested report."
::= { hostTopNControlEntry 8 }
hostTopNOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it."
::= { hostTopNControlEntry 9 }
hostTopNStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this hostTopNControl entry
If this object is not equal to valid(1), all
hostTopNEntries shall be deleted by the agent."
::= { hostTopNControlEntry 10 }
hostTopNTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of top N host entries."
::= { hostTopN 2 }
Waldbusser Standards Track [Page 55]
RFC 2819 Remote Network Monitoring MIB May 2000
hostTopNEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A set of statistics for a host that is part of a top
report. For example, an instance of the
object might be named hostTopNRate.3.10"
INDEX { hostTopNReport, hostTopNIndex }
::= { hostTopNTable 1 }
HostTopNEntry ::= SEQUENCE {
hostTopNReport Integer32,
hostTopNIndex Integer32,
hostTopNAddress OCTET STRING
hostTopNRate Integer32
}
hostTopNReport OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"This object identifies the top N report of
this entry is a part. The set of
identified by a particular value of
object is part of the same report as
by the same value of the hostTopNControlIndex object."
::= { hostTopNEntry 1 }
hostTopNIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an entry
the hostTopN table among those in the same report
This index is between 1 and N, where N is
number of entries in this table. Increasing
of hostTopNIndex shall be assigned to entries
decreasing values of hostTopNRate until index
is assigned to the entry with the lowest value
hostTopNRate or there are no more hostTopNEntries."
::= { hostTopNEntry 2 }
hostTopNAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
Waldbusser Standards Track [Page 56]
RFC 2819 Remote Network Monitoring MIB May 2000
STATUS
"The physical address of this host."
::= { hostTopNEntry 3 }
hostTopNRate OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The amount of change in the selected
during this sampling interval. The
variable is this host's instance of the
selected by hostTopNRateBase."
::= { hostTopNEntry 4 }
-- The Matrix
-- Implementation of the Matrix group is optional
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The Matrix group consists of the matrixControlTable,
-- and the matrixDSTable. These tables store statistics for
-- particular conversation between two addresses. As the
-- detects a new conversation, including those to a non-
-- address, it creates a new entry in both of the matrix tables
-- It must only create new entries based on
-- received in good packets. If the monitoring device
-- itself short of resources, it may delete entries as needed
-- It is suggested that the device delete the least recently
-- entries first
matrixControlTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of information entries for
traffic matrix on each interface."
::= { matrix 1 }
matrixControlEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a traffic matrix on a
Waldbusser Standards Track [Page 57]
RFC 2819 Remote Network Monitoring MIB May 2000
interface. For example, an instance of
matrixControlLastDeleteTime object might be
matrixControlLastDeleteTime.1"
INDEX { matrixControlIndex }
::= { matrixControlTable 1 }
MatrixControlEntry ::= SEQUENCE {
matrixControlIndex Integer32,
matrixControlDataSource OBJECT IDENTIFIER
matrixControlTableSize Integer32,
matrixControlLastDeleteTime TimeTicks
matrixControlOwner OwnerString
matrixControlStatus
}
matrixControlIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an entry in
matrixControl table. Each such entry
a function that discovers conversations on a
interface and places statistics about them in
matrixSDTable and the matrixDSTable on behalf of
matrixControlEntry."
::= { matrixControlEntry 1 }
matrixControlDataSource OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"This object identifies the source
the data from which this entry creates a traffic matrix
This source can be any interface on this device.
order to identify a particular interface, this
shall identify the instance of the ifIndex object
defined in RFC 2233 [17], for the
interface. For example, if an entry were to receive
from interface #1, this object would be set to ifIndex.1.
The statistics in this group reflect all
on the local network segment attached to the
interface
An agent may or may not be able to tell if
changes to the media of the interface have occurred
Waldbusser Standards Track [Page 58]
RFC 2819 Remote Network Monitoring MIB May 2000
necessitate an invalidation of this entry. For example,
hot-pluggable ethernet card could be pulled out and
by a token-ring card. In such a case, if the agent has
knowledge of the change, it is recommended that
invalidate this entry
This object may not be modified if the
matrixControlStatus object is equal to valid(1)."
::= { matrixControlEntry 2 }
matrixControlTableSize OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The number of matrixSDEntries in the
for this interface. This must also be the value
the number of entries in the matrixDSTable for
interface."
::= { matrixControlEntry 3 }
matrixControlLastDeleteTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime when the last
was deleted from the portion of the
or matrixDSTable associated with this matrixControlEntry
If no deletions have occurred, this value shall
zero."
::= { matrixControlEntry 4 }
matrixControlOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it."
::= { matrixControlEntry 5 }
matrixControlStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this matrixControl entry
Waldbusser Standards Track [Page 59]
RFC 2819 Remote Network Monitoring MIB May 2000
If this object is not equal to valid(1), all
entries in the matrixSDTable and the
shall be deleted by the agent."
::= { matrixControlEntry 6 }
matrixSDTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of traffic matrix entries indexed
source and destination MAC address."
::= { matrix 2 }
matrixSDEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A collection of statistics for communications
two addresses on a particular interface. For example
an instance of the matrixSDPkts object might be
matrixSDPkts.1.6.8.0.32.27.3.176.6.8.0.32.10.8.113"
INDEX { matrixSDIndex
matrixSDSourceAddress, matrixSDDestAddress }
::= { matrixSDTable 1 }
MatrixSDEntry ::= SEQUENCE {
matrixSDSourceAddress OCTET STRING
matrixSDDestAddress OCTET STRING
matrixSDIndex Integer32,
matrixSDPkts Counter32,
matrixSDOctets Counter32,
matrixSDErrors Counter32
}
matrixSDSourceAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The source physical address."
::= { matrixSDEntry 1 }
matrixSDDestAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 60]
RFC 2819 Remote Network Monitoring MIB May 2000
"The destination physical address."
::= { matrixSDEntry 2 }
matrixSDIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The set of collected matrix statistics of
this entry is a part. The set of matrix
identified by a particular value of this
is associated with the same
as identified by the same value of matrixControlIndex."
::= { matrixSDEntry 3 }
matrixSDPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets transmitted from the
address to the destination address (this number
bad packets)."
::= { matrixSDEntry 4 }
matrixSDOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets (excluding framing bits
including FCS octets) contained in all
transmitted from the source address to
destination address."
::= { matrixSDEntry 5 }
matrixSDErrors OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of bad packets transmitted
the source address to the destination address."
::= { matrixSDEntry 6 }
Waldbusser Standards Track [Page 61]
RFC 2819 Remote Network Monitoring MIB May 2000
-- Traffic matrix tables from destination to
matrixDSTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of traffic matrix entries indexed
destination and source MAC address."
::= { matrix 3 }
matrixDSEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A collection of statistics for communications
two addresses on a particular interface. For example
an instance of the matrixSDPkts object might be
matrixSDPkts.1.6.8.0.32.10.8.113.6.8.0.32.27.3.176"
INDEX { matrixDSIndex
matrixDSDestAddress, matrixDSSourceAddress }
::= { matrixDSTable 1 }
MatrixDSEntry ::= SEQUENCE {
matrixDSSourceAddress OCTET STRING
matrixDSDestAddress OCTET STRING
matrixDSIndex Integer32,
matrixDSPkts Counter32,
matrixDSOctets Counter32,
matrixDSErrors Counter32
}
matrixDSSourceAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The source physical address."
::= { matrixDSEntry 1 }
matrixDSDestAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The destination physical address."
::= { matrixDSEntry 2 }
Waldbusser Standards Track [Page 62]
RFC 2819 Remote Network Monitoring MIB May 2000
matrixDSIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The set of collected matrix statistics of
this entry is a part. The set of matrix
identified by a particular value of this
is associated with the same
as identified by the same value of matrixControlIndex."
::= { matrixDSEntry 3 }
matrixDSPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets transmitted from the
address to the destination address (this number
bad packets)."
::= { matrixDSEntry 4 }
matrixDSOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets (excluding framing
but including FCS octets) contained in all
transmitted from the source address to
destination address."
::= { matrixDSEntry 5 }
matrixDSErrors OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of bad packets transmitted
the source address to the destination address."
::= { matrixDSEntry 6 }
-- The Filter
-- Implementation of the Filter group is optional
Waldbusser Standards Track [Page 63]
RFC 2819 Remote Network Monitoring MIB May 2000
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The Filter group allows packets to be captured with
-- arbitrary filter expression. A logical data
-- event stream or "channel" is formed by the
-- that match the filter expression
--
-- This filter mechanism allows the creation of an
-- logical expression with which to filter packets.
-- filter associated with a channel is OR'ed with the others
-- Within a filter, any bits checked in the data and status
-- AND'ed with respect to other bits in the same filter.
-- NotMask also allows for checking for inequality. Finally
-- the channelAcceptType object allows for inversion of
-- whole equation
--
-- If a management station wishes to receive a trap to alert
-- that new packets have been captured and are available
-- download, it is recommended that it set up an alarm entry
-- monitors the value of the relevant channelMatches instance
--
-- The channel can be turned on or off, and can
-- generate events when packets pass through it
filterTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of packet filter entries."
::= { filter 1 }
filterEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A set of parameters for a packet filter applied on
particular interface. As an example, an instance of
filterPktData object might be named filterPktData.12"
INDEX { filterIndex }
::= { filterTable 1 }
FilterEntry ::= SEQUENCE {
filterIndex Integer32,
filterChannelIndex Integer32,
filterPktDataOffset Integer32,
Waldbusser Standards Track [Page 64]
RFC 2819 Remote Network Monitoring MIB May 2000
filterPktData OCTET STRING
filterPktDataMask OCTET STRING
filterPktDataNotMask OCTET STRING
filterPktStatus Integer32,
filterPktStatusMask Integer32,
filterPktStatusNotMask Integer32,
filterOwner OwnerString
filterStatus
}
filterIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an
in the filter table. Each such entry
one filter that is to be applied to every
received on an interface."
::= { filterEntry 1 }
filterChannelIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"This object identifies the channel of which this
is a part. The filters identified by a particular
of this object are associated with the same channel
identified by the same value of the channelIndex object."
::= { filterEntry 2 }
filterPktDataOffset OBJECT-
SYNTAX Integer32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The offset from the beginning of each packet
a match of packet data will be attempted. This
is measured from the point in the physical
packet after the framing bits, if any. For example
in an Ethernet frame, this point is at the beginning
the destination MAC address
This object may not be modified if the
filterStatus object is equal to valid(1)."
DEFVAL { 0 }
Waldbusser Standards Track [Page 65]
RFC 2819 Remote Network Monitoring MIB May 2000
::= { filterEntry 3 }
filterPktData OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The data that is to be matched with the input packet
For each packet received, this filter and the
filterPktDataMask and filterPktDataNotMask will
adjusted for the offset. The only bits relevant to
match algorithm are those that have the
filterPktDataMask bit equal to one. The following
rules are then applied to every packet
(1) If the packet is too short and does not have
corresponding to part of the filterPktData, the
will fail this data match
(2) For each relevant bit from the packet with
corresponding filterPktDataNotMask bit set to zero,
the bit from the packet is not equal to the
bit from the filterPktData, then the packet will
this data match
(3) If for every relevant bit from the packet with
corresponding filterPktDataNotMask bit set to one,
bit from the packet is equal to the corresponding
from the filterPktData, then the packet will fail
data match
Any packets that have not failed any of the three
above have passed this data match. In particular, a
length filter will match any packet
This object may not be modified if the
filterStatus object is equal to valid(1)."
::= { filterEntry 4 }
filterPktDataMask OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The mask that is applied to the match process
After adjusting this mask for the offset, only
bits in the received packet that correspond to bits
in this mask are relevant for further processing by
Waldbusser Standards Track [Page 66]
RFC 2819 Remote Network Monitoring MIB May 2000
match algorithm. The offset is applied to
in the same way it is applied to the filter. For
purposes of the matching algorithm, if the
filterPktData object is longer than this mask, this mask
conceptually extended with '1' bits until it reaches
length of the filterPktData object
This object may not be modified if the
filterStatus object is equal to valid(1)."
::= { filterEntry 5 }
filterPktDataNotMask OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The inversion mask that is applied to the
process. After adjusting this mask for the offset
those relevant bits in the received packet that
to bits cleared in this mask must all be equal to
corresponding bits in the filterPktData object for the
to be accepted. In addition, at least one of those
bits in the received packet that correspond to bits set
this mask must be different to its corresponding bit in
filterPktData object
For the purposes of the matching algorithm, if the
filterPktData object is longer than this mask, this mask
conceptually extended with '0' bits until it reaches
length of the filterPktData object
This object may not be modified if the
filterStatus object is equal to valid(1)."
::= { filterEntry 6 }
filterPktStatus OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The status that is to be matched with the input packet
The only bits relevant to this match algorithm are those
have the corresponding filterPktStatusMask bit equal to one
The following two rules are then applied to every packet
(1) For each relevant bit from the packet status with
corresponding filterPktStatusNotMask bit set to zero,
the bit from the packet status is not equal to
Waldbusser Standards Track [Page 67]
RFC 2819 Remote Network Monitoring MIB May 2000
corresponding bit from the filterPktStatus, then
packet will fail this status match
(2) If for every relevant bit from the packet status with
corresponding filterPktStatusNotMask bit set to one,
bit from the packet status is equal to the
bit from the filterPktStatus, then the packet will
this status match
Any packets that have not failed either of the two
above have passed this status match. In particular, a
length status filter will match any packet's status
The value of the packet status is a sum. This
initially takes the value zero. Then, for
error, E, that has been discovered in this packet
2 raised to a value representing E is added to the sum
The errors and the bits that represent them are
on the media type of the interface that this
is receiving packets from
The errors defined for a packet captured off of
Ethernet interface are as follows
bit #
0 Packet is longer than 1518
1 Packet is shorter than 64
2 Packet experienced a CRC or Alignment
For example, an Ethernet fragment would have
value of 6 (2^1 + 2^2).
As this MIB is expanded to new media types, this
will have other media-specific errors defined
For the purposes of this status matching algorithm, if
packet status is longer than this filterPktStatus object
this object is conceptually extended with '0' bits until
reaches the size of the packet status
This object may not be modified if the
filterStatus object is equal to valid(1)."
::= { filterEntry 7 }
filterPktStatusMask OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 68]
RFC 2819 Remote Network Monitoring MIB May 2000
"The mask that is applied to the status match process
Only those bits in the received packet that correspond
bits set in this mask are relevant for further
by the status match algorithm. For the
of the matching algorithm, if the associated
object is longer than this mask, this mask is
extended with '1' bits until it reaches the size of
filterPktStatus. In addition, if a packet status is
than this mask, this mask is conceptually extended with '0'
bits until it reaches the size of the packet status
This object may not be modified if the
filterStatus object is equal to valid(1)."
::= { filterEntry 8 }
filterPktStatusNotMask OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"The inversion mask that is applied to the status
process. Those relevant bits in the received packet
that correspond to bits cleared in this mask must all
equal to their corresponding bits in the
object for the packet to be accepted. In addition, at
one of those relevant bits in the received packet
that correspond to bits set in this mask must be
to its corresponding bit in the filterPktStatus object
the packet to be accepted
For the purposes of the matching algorithm, if the
filterPktStatus object or a packet status is longer than
mask, this mask is conceptually extended with '0' bits
it reaches the longer of the lengths of the
object and the packet status
This object may not be modified if the
filterStatus object is equal to valid(1)."
::= { filterEntry 9 }
filterOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it."
Waldbusser Standards Track [Page 69]
RFC 2819 Remote Network Monitoring MIB May 2000
::= { filterEntry 10 }
filterStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this filter entry."
::= { filterEntry 11 }
channelTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of packet channel entries."
::= { filter 2 }
channelEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A set of parameters for a packet channel applied on
particular interface. As an example, an instance of
channelMatches object might be named channelMatches.3"
INDEX { channelIndex }
::= { channelTable 1 }
ChannelEntry ::= SEQUENCE {
channelIndex Integer32,
channelIfIndex Integer32,
channelAcceptType INTEGER
channelDataControl INTEGER
channelTurnOnEventIndex Integer32,
channelTurnOffEventIndex Integer32,
channelEventIndex Integer32,
channelEventStatus INTEGER
channelMatches Counter32,
channelDescription DisplayString
channelOwner OwnerString
channelStatus
}
channelIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 70]
RFC 2819 Remote Network Monitoring MIB May 2000
"An index that uniquely identifies an entry in the
table. Each such entry defines one channel, a
data and event stream
It is suggested that before creating a channel,
application should scan all instances of
filterChannelIndex object to make sure that there are
pre-existing filters that would be inadvertently be
to the channel."
::= { channelEntry 1 }
channelIfIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The value of this object uniquely identifies
interface on this remote network monitoring device to
the associated filters are applied to allow data into
channel. The interface identified by a particular
of this object is the same interface as identified by
same value of the ifIndex object, defined in RFC 2233 [17].
The filters in this group are applied to all packets
the local network segment attached to the
interface
An agent may or may not be able to tell if
changes to the media of the interface have occurred
necessitate an invalidation of this entry. For example,
hot-pluggable ethernet card could be pulled out and
by a token-ring card. In such a case, if the agent has
knowledge of the change, it is recommended that
invalidate this entry
This object may not be modified if the
channelStatus object is equal to valid(1)."
::= { channelEntry 2 }
channelAcceptType OBJECT-
SYNTAX INTEGER {
acceptMatched(1),
acceptFailed(2)
}
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 71]
RFC 2819 Remote Network Monitoring MIB May 2000
"This object controls the action of the
associated with this channel. If this object is
to acceptMatched(1), packets will be accepted to
channel if they are accepted by both the packet data
packet status matches of an associated filter.
this object is equal to acceptFailed(2), packets
be accepted to this channel only if they fail
the packet data match or the packet status match
each of the associated filters
In particular, a channel with no associated filters
match no packets if set to acceptMatched(1) case and
match all packets in the acceptFailed(2) case
This object may not be modified if the
channelStatus object is equal to valid(1)."
::= { channelEntry 3 }
channelDataControl OBJECT-
SYNTAX INTEGER {
on(1),
off(2)
}
MAX-ACCESS read-
STATUS
"This object controls the flow of data through this channel
If this object is on(1), data, status and events
through this channel. If this object is off(2), data
status and events will not flow through this channel."
DEFVAL { off }
::= { channelEntry 4 }
channelTurnOnEventIndex OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The value of this object identifies the
that is configured to turn the
channelDataControl from off to on when the event
generated. The event identified by a particular
of this object is the same event as identified by
same value of the eventIndex object. If there is
corresponding entry in the eventTable, then
association exists. In fact, if no event is
for this channel, channelTurnOnEventIndex must
set to zero, a non-existent event index
Waldbusser Standards Track [Page 72]
RFC 2819 Remote Network Monitoring MIB May 2000
This object may not be modified if the
channelStatus object is equal to valid(1)."
::= { channelEntry 5 }
channelTurnOffEventIndex OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The value of this object identifies the
that is configured to turn the
channelDataControl from on to off when the event
generated. The event identified by a particular
of this object is the same event as identified by
same value of the eventIndex object. If there is
corresponding entry in the eventTable, then
association exists. In fact, if no event is
for this channel, channelTurnOffEventIndex must
set to zero, a non-existent event index
This object may not be modified if the
channelStatus object is equal to valid(1)."
::= { channelEntry 6 }
channelEventIndex OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The value of this object identifies the
that is configured to be generated when
associated channelDataControl is on and a
is matched. The event identified by a particular
of this object is the same event as identified by
same value of the eventIndex object. If there is
corresponding entry in the eventTable, then
association exists. In fact, if no event is
for this channel, channelEventIndex must
set to zero, a non-existent event index
This object may not be modified if the
channelStatus object is equal to valid(1)."
::= { channelEntry 7 }
channelEventStatus OBJECT-
SYNTAX INTEGER {
eventReady(1),
eventFired(2),
Waldbusser Standards Track [Page 73]
RFC 2819 Remote Network Monitoring MIB May 2000
eventAlwaysReady(3)
}
MAX-ACCESS read-
STATUS
"The event status of this channel
If this channel is configured to generate
when packets are matched, a means of
the flow of those events is often needed.
this object is equal to eventReady(1), a
event may be generated, after which this
will be set by the probe to eventFired(2).
in the eventFired(2) state, no events will
generated until the object is modified
eventReady(1) (or eventAlwaysReady(3)).
management station can thus easily respond to
notification of an event by re-enabling this object
If the management station wishes to disable
flow control and allow events to be
at will, this object may be set
eventAlwaysReady(3). Disabling the flow
is discouraged as it can result in high
traffic or other performance problems."
DEFVAL { eventReady }
::= { channelEntry 8 }
channelMatches OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times this channel has matched a packet
Note that this object is updated even
channelDataControl is set to off."
::= { channelEntry 9 }
channelDescription OBJECT-
SYNTAX DisplayString (SIZE (0..127))
MAX-ACCESS read-
STATUS
"A comment describing this channel."
::= { channelEntry 10 }
channelOwner OBJECT-
Waldbusser Standards Track [Page 74]
RFC 2819 Remote Network Monitoring MIB May 2000
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it."
::= { channelEntry 11 }
channelStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this channel entry."
::= { channelEntry 12 }
-- The Packet Capture
-- Implementation of the Packet Capture group is optional. The
-- Capture Group requires implementation of the Filter Group
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The Packet Capture group allows packets to be
-- upon a filter match. The bufferControlTable
-- the captured packets output from a channel that
-- associated with it. The captured packets are
-- in entries in the captureBufferTable. These entries
-- associated with the bufferControlEntry on whose behalf
-- were stored
bufferControlTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of buffers control entries."
::= { capture 1 }
bufferControlEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A set of parameters that control the collection of a
of packets that have matched filters. As an example,
instance of the bufferControlCaptureSliceSize object
be named bufferControlCaptureSliceSize.3"
Waldbusser Standards Track [Page 75]
RFC 2819 Remote Network Monitoring MIB May 2000
INDEX { bufferControlIndex }
::= { bufferControlTable 1 }
BufferControlEntry ::= SEQUENCE {
bufferControlIndex Integer32,
bufferControlChannelIndex Integer32,
bufferControlFullStatus INTEGER
bufferControlFullAction INTEGER
bufferControlCaptureSliceSize Integer32,
bufferControlDownloadSliceSize Integer32,
bufferControlDownloadOffset Integer32,
bufferControlMaxOctetsRequested Integer32,
bufferControlMaxOctetsGranted Integer32,
bufferControlCapturedPackets Integer32,
bufferControlTurnOnTime TimeTicks
bufferControlOwner OwnerString
bufferControlStatus
}
bufferControlIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an
in the bufferControl table. The value of
index shall never be zero. Each
entry defines one set of packets that
captured and controlled by one or more filters."
::= { bufferControlEntry 1 }
bufferControlChannelIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that identifies the channel that is
source of packets for this bufferControl table
The channel identified by a particular value of
index is the same as identified by the same value
the channelIndex object
This object may not be modified if the
bufferControlStatus object is equal to valid(1)."
::= { bufferControlEntry 2 }
bufferControlFullStatus OBJECT-
SYNTAX INTEGER {
Waldbusser Standards Track [Page 76]
RFC 2819 Remote Network Monitoring MIB May 2000
spaceAvailable(1),
full(2)
}
MAX-ACCESS read-
STATUS
"This object shows whether the buffer has room
accept new packets or if it is full
If the status is spaceAvailable(1), the buffer
accepting new packets normally. If the status
full(2) and the associated
object is wrapWhenFull, the buffer is accepting
packets by deleting enough of the oldest
to make room for new ones as they arrive. Otherwise
if the status is full(2) and
bufferControlFullAction object is lockWhenFull
then the buffer has stopped collecting packets
When this object is set to full(2) the probe
not later set it to spaceAvailable(1) except in
case of a significant gain in resources such
an increase of bufferControlOctetsGranted.
particular, the wrap-mode action of deleting
packets to make room for newly arrived
must not affect the value of this object."
::= { bufferControlEntry 3 }
bufferControlFullAction OBJECT-
SYNTAX INTEGER {
lockWhenFull(1),
wrapWhenFull(2) --
}
MAX-ACCESS read-
STATUS
"Controls the action of the buffer when
reaches the full status. When in the lockWhenFull(1)
state and a packet is added to the buffer
fills the buffer, the bufferControlFullStatus
be set to full(2) and this buffer will stop
packets."
::= { bufferControlEntry 4 }
bufferControlCaptureSliceSize OBJECT-
SYNTAX Integer32
UNITS "Octets
MAX-ACCESS read-
Waldbusser Standards Track [Page 77]
RFC 2819 Remote Network Monitoring MIB May 2000
STATUS
"The maximum number of octets of each
that will be saved in this capture buffer
For example, if a 1500 octet packet is received
the probe and this object is set to 500, then
500 octets of the packet will be stored in
associated capture buffer. If this variable is
to 0, the capture buffer will save as many
as is possible
This object may not be modified if the
bufferControlStatus object is equal to valid(1)."
DEFVAL { 100 }
::= { bufferControlEntry 5 }
bufferControlDownloadSliceSize OBJECT-
SYNTAX Integer32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The maximum number of octets of each
in this capture buffer that will be returned
an SNMP retrieval of that packet. For example
if 500 octets of a packet have been stored in
associated capture buffer, the
bufferControlDownloadOffset is 0, and
object is set to 100, then the
object that contains the packet will contain
the first 100 octets of the packet
A prudent manager will take into account
interoperability or fragmentation problems that
occur if the download slice size is set too large
In particular, conformant SNMP implementations are
required to accept messages whose length exceeds 484
octets, although they are encouraged to support
datagrams whenever feasible."
DEFVAL { 100 }
::= { bufferControlEntry 6 }
bufferControlDownloadOffset OBJECT-
SYNTAX Integer32
UNITS "Octets
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 78]
RFC 2819 Remote Network Monitoring MIB May 2000
"The offset of the first octet of each
in this capture buffer that will be returned
an SNMP retrieval of that packet. For example
if 500 octets of a packet have been stored in
associated capture buffer and this object is set
100, then the captureBufferPacket object
contains the packet will contain bytes
100 octets into the packet."
DEFVAL { 0 }
::= { bufferControlEntry 7 }
bufferControlMaxOctetsRequested OBJECT-
SYNTAX Integer32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The requested maximum number of octets to
saved in this captureBuffer, including
implementation-specific overhead. If this
is set to -1, the capture buffer will save as
octets as is possible
When this object is created or modified, the
should set bufferControlMaxOctetsGranted as
to this object as is possible for the particular
implementation and available resources. However,
the object has the special value of -1, the
must set bufferControlMaxOctetsGranted to -1."
DEFVAL { -1 }
::= { bufferControlEntry 8 }
bufferControlMaxOctetsGranted OBJECT-
SYNTAX Integer32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The maximum number of octets that can
saved in this captureBuffer, including overhead
If this variable is -1, the capture buffer will
as many octets as possible
When the bufferControlMaxOctetsRequested object
created or modified, the probe should set this
as closely to the requested value as is possible for
particular probe implementation and available resources
However, if the request object has the special
Waldbusser Standards Track [Page 79]
RFC 2819 Remote Network Monitoring MIB May 2000
of -1, the probe must set this object to -1.
The probe must not lower this value except as a result
a modification to the
bufferControlMaxOctetsRequested object
When this maximum number of octets is
and a new packet is to be added to
capture buffer and the
bufferControlFullAction is set to wrapWhenFull(2),
enough of the oldest packets associated with
capture buffer shall be deleted by the agent
that the new packet can be added. If the
bufferControlFullAction is set to lockWhenFull(1),
the new packet shall be discarded. In either case
the probe must set bufferControlFullStatus
full(2).
When the value of this object changes to a value
than the current value, entries are deleted
the captureBufferTable associated with
bufferControlEntry. Enough of
oldest of these captureBufferEntries shall
deleted by the agent so that the number of
used remains less than or equal to the new value
this object
When the value of this object changes to a value
than the current value, the number of
captureBufferEntries may be allowed to grow."
::= { bufferControlEntry 9 }
bufferControlCapturedPackets OBJECT-
SYNTAX Integer32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets currently in this captureBuffer."
::= { bufferControlEntry 10 }
bufferControlTurnOnTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime when this capture buffer
first turned on."
Waldbusser Standards Track [Page 80]
RFC 2819 Remote Network Monitoring MIB May 2000
::= { bufferControlEntry 11 }
bufferControlOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it."
::= { bufferControlEntry 12 }
bufferControlStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this buffer Control Entry."
::= { bufferControlEntry 13 }
captureBufferTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of packets captured off of a channel."
::= { capture 2 }
captureBufferEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A packet captured off of an attached network. As
example, an instance of the
object might be named captureBufferPacketData.3.1783"
INDEX { captureBufferControlIndex, captureBufferIndex }
::= { captureBufferTable 1 }
CaptureBufferEntry ::= SEQUENCE {
captureBufferControlIndex Integer32,
captureBufferIndex Integer32,
captureBufferPacketID Integer32,
captureBufferPacketData OCTET STRING
captureBufferPacketLength Integer32,
captureBufferPacketTime Integer32,
captureBufferPacketStatus Integer32
}
Waldbusser Standards Track [Page 81]
RFC 2819 Remote Network Monitoring MIB May 2000
captureBufferControlIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The index of the bufferControlEntry with
this packet is associated."
::= { captureBufferEntry 1 }
captureBufferIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an
in the captureBuffer table associated with
particular bufferControlEntry. This index
start at 1 and increase by one for each new
added with the same captureBufferControlIndex
Should this value reach 2147483647, the next
added with the same captureBufferControlIndex
cause this value to wrap around to 1."
::= { captureBufferEntry 2 }
captureBufferPacketID OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"An index that describes the order of
that are received on a particular interface
The packetID of a packet captured on
interface is defined to be greater than
packetID's of all packets captured previously
the same interface. As the
object has a maximum positive value of 2^31 - 1,
any captureBufferPacketID object shall have
value of the associated packet's packetID mod 2^31."
::= { captureBufferEntry 3 }
captureBufferPacketData OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The data inside the packet, starting at the
of the packet plus any offset specified in
Waldbusser Standards Track [Page 82]
RFC 2819 Remote Network Monitoring MIB May 2000
associated bufferControlDownloadOffset, including
link level headers. The length of the data in this
is the minimum of the length of the captured packet
the offset, the length of the
bufferControlCaptureSliceSize minus the offset, and
associated bufferControlDownloadSliceSize. If this
is less than zero, this object shall have a length of zero."
::= { captureBufferEntry 4 }
captureBufferPacketLength OBJECT-
SYNTAX Integer32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The actual length (off the wire) of the packet
in this entry, including FCS octets."
::= { captureBufferEntry 5 }
captureBufferPacketTime OBJECT-
SYNTAX Integer32
UNITS "Milliseconds
MAX-ACCESS read-
STATUS
"The number of milliseconds that had passed
this capture buffer was first turned on when
packet was captured."
::= { captureBufferEntry 6 }
captureBufferPacketStatus OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"A value which indicates the error status of this packet
The value of this object is defined in the same way
filterPktStatus. The value is a sum. This
initially takes the value zero. Then, for
error, E, that has been discovered in this packet
2 raised to a value representing E is added to the sum
The errors defined for a packet captured off of
Ethernet interface are as follows
bit #
0 Packet is longer than 1518
Waldbusser Standards Track [Page 83]
RFC 2819 Remote Network Monitoring MIB May 2000
1 Packet is shorter than 64
2 Packet experienced a CRC or Alignment
3 First packet in this capture buffer
it was detected that some packets
not processed correctly
4 Packet's order in buffer is only
(May only be set for packets sent
the probe
For example, an Ethernet fragment would have
value of 6 (2^1 + 2^2).
As this MIB is expanded to new media types, this
will have other media-specific errors defined."
::= { captureBufferEntry 7 }
-- The Event
-- Implementation of the Event group is optional
-- Consult the MODULE-COMPLIANCE macro for the
-- conformance information for this MIB
--
-- The Event group controls the generation and
-- of events from this device. Each entry in the
-- describes the parameters of the event that can be triggered
-- Each event entry is fired by an associated condition
-- elsewhere in the MIB. An event entry may also be
-- with a function elsewhere in the MIB that will be
-- when the event is generated. For example, a channel
-- be turned on or off by the firing of an event
--
-- Each eventEntry may optionally specify that a log
-- be created on its behalf whenever the event occurs
-- Each entry may also specify that notification
-- occur by way of SNMP trap messages. In this case,
-- community for the trap message is given in the
-- eventCommunity object. The enterprise and specific
-- fields of the trap are determined by the condition
-- triggered the event. Two traps are defined: risingAlarm
-- fallingAlarm. If the eventTable is triggered by a
-- specified elsewhere, the enterprise and specific trap
-- must be specified for traps generated for that condition
eventTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
Waldbusser Standards Track [Page 84]
RFC 2819 Remote Network Monitoring MIB May 2000
"A list of events to be generated."
::= { event 1 }
eventEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A set of parameters that describe an event to be
when certain conditions are met. As an example, an
of the eventLastTimeSent object might be
eventLastTimeSent.6"
INDEX { eventIndex }
::= { eventTable 1 }
EventEntry ::= SEQUENCE {
eventIndex Integer32,
eventDescription DisplayString
eventType INTEGER
eventCommunity OCTET STRING
eventLastTimeSent TimeTicks
eventOwner OwnerString
eventStatus
}
eventIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an entry in
event table. Each such entry defines one event
is to be generated when the appropriate
occur."
::= { eventEntry 1 }
eventDescription OBJECT-
SYNTAX DisplayString (SIZE (0..127))
MAX-ACCESS read-
STATUS
"A comment describing this event entry."
::= { eventEntry 2 }
eventType OBJECT-
SYNTAX INTEGER {
none(1),
log(2),
Waldbusser Standards Track [Page 85]
RFC 2819 Remote Network Monitoring MIB May 2000
snmptrap(3), -- send an SNMP
logandtrap(4)
}
MAX-ACCESS read-
STATUS
"The type of notification that the probe will
about this event. In the case of log, an entry
made in the log table for each event. In the case
snmp-trap, an SNMP trap is sent to one or
management stations."
::= { eventEntry 3 }
eventCommunity OBJECT-
SYNTAX OCTET STRING (SIZE (0..127))
MAX-ACCESS read-
STATUS
"If an SNMP trap is to be sent, it will be sent
the SNMP community specified by this octet string."
::= { eventEntry 4 }
eventLastTimeSent OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the time this
entry last generated an event. If this entry
not generated any events, this value will
zero."
::= { eventEntry 5 }
eventOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and is
using the resources assigned to it
If this object contains a string starting with 'monitor
and has associated entries in the log table, all
management stations should retrieve those log entries
as they may have significance to all management
connected to this device
::= { eventEntry 6 }
Waldbusser Standards Track [Page 86]
RFC 2819 Remote Network Monitoring MIB May 2000
eventStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this event entry
If this object is not equal to valid(1), all
log entries shall be deleted by the agent."
::= { eventEntry 7 }
--
logTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A list of events that have been logged."
::= { event 2 }
logEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A set of data describing an event that has
logged. For example, an instance of the
object might be named logDescription.6.47"
INDEX { logEventIndex, logIndex }
::= { logTable 1 }
LogEntry ::= SEQUENCE {
logEventIndex Integer32,
logIndex Integer32,
logTime TimeTicks
logDescription
}
logEventIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The event entry that generated this
entry. The log identified by a
value of this index is associated with the
eventEntry as identified by the same
of eventIndex."
Waldbusser Standards Track [Page 87]
RFC 2819 Remote Network Monitoring MIB May 2000
::= { logEntry 1 }
logIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"An index that uniquely identifies an
in the log table amongst those generated by
same eventEntries. These indexes
assigned beginning with 1 and increase by
with each new log entry. The
between values of logIndex and
is fixed for the lifetime of each logEntry
The agent may choose to delete the
instances of logEntry as required because
lack of memory. It is an implementation-
matter as to when this deletion may occur."
::= { logEntry 2 }
logTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime when this log entry was created."
::= { logEntry 3 }
logDescription OBJECT-
SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-
STATUS
"An implementation dependent description of
event that activated this log entry."
::= { logEntry 4 }
-- Remote Network Monitoring
rmonEventsV2 OBJECT-
STATUS
DESCRIPTION "Definition point for RMON notifications."
::= { rmon 0 }
risingAlarm NOTIFICATION-
OBJECTS { alarmIndex, alarmVariable, alarmSampleType
alarmValue, alarmRisingThreshold }
STATUS
Waldbusser Standards Track [Page 88]
RFC 2819 Remote Network Monitoring MIB May 2000
"The SNMP trap that is generated when an
entry crosses its rising threshold and
an event that is configured for sending
traps."
::= { rmonEventsV2 1 }
fallingAlarm NOTIFICATION-
OBJECTS { alarmIndex, alarmVariable, alarmSampleType
alarmValue, alarmFallingThreshold }
STATUS
"The SNMP trap that is generated when an
entry crosses its falling threshold and
an event that is configured for sending
traps."
::= { rmonEventsV2 2 }
-- Conformance
rmonCompliances OBJECT IDENTIFIER ::= { rmonConformance 9 }
rmonGroups OBJECT IDENTIFIER ::= { rmonConformance 10 }
-- Compliance
rmonCompliance MODULE-
STATUS
"The requirements for conformance to the RMON MIB. At
one of the groups in this module must be implemented
conform to the RMON MIB. Implementations of this
must also implement the system group of MIB-II [16] and
IF-MIB [17]."
MODULE -- this
GROUP
"The RMON Ethernet Statistics Group is optional."
GROUP
"The RMON History Control Group is optional."
GROUP
"The RMON Ethernet History Group is optional."
GROUP
Waldbusser Standards Track [Page 89]
RFC 2819 Remote Network Monitoring MIB May 2000
"The RMON Alarm Group is optional."
GROUP
"The RMON Host Group is mandatory when
rmonHostTopNGroup is implemented."
GROUP
"The RMON Host Top N Group is optional."
GROUP
"The RMON Matrix Group is optional."
GROUP
"The RMON Filter Group is mandatory when
rmonPacketCaptureGroup is implemented."
GROUP
"The RMON Packet Capture Group is optional."
GROUP
"The RMON Event Group is mandatory when
rmonAlarmGroup is implemented."
::= { rmonCompliances 1 }
rmonEtherStatsGroup OBJECT-
OBJECTS {
etherStatsIndex, etherStatsDataSource
etherStatsDropEvents, etherStatsOctets, etherStatsPkts
etherStatsBroadcastPkts, etherStatsMulticastPkts
etherStatsCRCAlignErrors, etherStatsUndersizePkts
etherStatsOversizePkts, etherStatsFragments
etherStatsJabbers, etherStatsCollisions
etherStatsPkts64Octets, etherStatsPkts65to127Octets
etherStatsPkts128to255Octets
etherStatsPkts256to511Octets
etherStatsPkts512to1023Octets
etherStatsPkts1024to1518Octets
etherStatsOwner,
}
STATUS
"The RMON Ethernet Statistics Group."
Waldbusser Standards Track [Page 90]
RFC 2819 Remote Network Monitoring MIB May 2000
::= { rmonGroups 1 }
rmonHistoryControlGroup OBJECT-
OBJECTS {
historyControlIndex, historyControlDataSource
historyControlBucketsRequested
historyControlBucketsGranted, historyControlInterval
historyControlOwner,
}
STATUS
"The RMON History Control Group."
::= { rmonGroups 2 }
rmonEthernetHistoryGroup OBJECT-
OBJECTS {
etherHistoryIndex, etherHistorySampleIndex
etherHistoryIntervalStart, etherHistoryDropEvents
etherHistoryOctets, etherHistoryPkts
etherHistoryBroadcastPkts, etherHistoryMulticastPkts
etherHistoryCRCAlignErrors, etherHistoryUndersizePkts
etherHistoryOversizePkts, etherHistoryFragments
etherHistoryJabbers, etherHistoryCollisions
}
STATUS
"The RMON Ethernet History Group."
::= { rmonGroups 3 }
rmonAlarmGroup OBJECT-
OBJECTS {
alarmIndex, alarmInterval, alarmVariable
alarmSampleType, alarmValue, alarmStartupAlarm
alarmRisingThreshold, alarmFallingThreshold
alarmRisingEventIndex, alarmFallingEventIndex
alarmOwner,
}
STATUS
"The RMON Alarm Group."
::= { rmonGroups 4 }
rmonHostGroup OBJECT-
OBJECTS {
hostControlIndex, hostControlDataSource
hostControlTableSize, hostControlLastDeleteTime
hostControlOwner, hostControlStatus
Waldbusser Standards Track [Page 91]
RFC 2819 Remote Network Monitoring MIB May 2000
hostAddress, hostCreationOrder, hostIndex
hostInPkts, hostOutPkts, hostInOctets
hostOutOctets, hostOutErrors, hostOutBroadcastPkts
hostOutMulticastPkts, hostTimeAddress
hostTimeCreationOrder, hostTimeIndex
hostTimeInPkts, hostTimeOutPkts, hostTimeInOctets
hostTimeOutOctets, hostTimeOutErrors
hostTimeOutBroadcastPkts,
}
STATUS
"The RMON Host Group."
::= { rmonGroups 5 }
rmonHostTopNGroup OBJECT-
OBJECTS {
hostTopNControlIndex, hostTopNHostIndex
hostTopNRateBase, hostTopNTimeRemaining
hostTopNDuration, hostTopNRequestedSize
hostTopNGrantedSize, hostTopNStartTime
hostTopNOwner, hostTopNStatus
hostTopNReport, hostTopNIndex
hostTopNAddress,
}
STATUS
"The RMON Host Top 'N' Group."
::= { rmonGroups 6 }
rmonMatrixGroup OBJECT-
OBJECTS {
matrixControlIndex, matrixControlDataSource
matrixControlTableSize, matrixControlLastDeleteTime
matrixControlOwner, matrixControlStatus
matrixSDSourceAddress, matrixSDDestAddress
matrixSDIndex, matrixSDPkts
matrixSDOctets, matrixSDErrors
matrixDSSourceAddress, matrixDSDestAddress
matrixDSIndex, matrixDSPkts
matrixDSOctets,
}
STATUS
"The RMON Matrix Group."
::= { rmonGroups 7 }
rmonFilterGroup OBJECT-
OBJECTS {
Waldbusser Standards Track [Page 92]
RFC 2819 Remote Network Monitoring MIB May 2000
filterIndex, filterChannelIndex, filterPktDataOffset
filterPktData, filterPktDataMask
filterPktDataNotMask, filterPktStatus
filterPktStatusMask, filterPktStatusNotMask
filterOwner, filterStatus
channelIndex, channelIfIndex, channelAcceptType
channelDataControl, channelTurnOnEventIndex
channelTurnOffEventIndex, channelEventIndex
channelEventStatus, channelMatches
channelDescription, channelOwner,
}
STATUS
"The RMON Filter Group."
::= { rmonGroups 8 }
rmonPacketCaptureGroup OBJECT-
OBJECTS {
bufferControlIndex, bufferControlChannelIndex
bufferControlFullStatus, bufferControlFullAction
bufferControlCaptureSliceSize
bufferControlDownloadSliceSize
bufferControlDownloadOffset
bufferControlMaxOctetsRequested
bufferControlMaxOctetsGranted
bufferControlCapturedPackets
bufferControlTurnOnTime
bufferControlOwner, bufferControlStatus
captureBufferControlIndex, captureBufferIndex
captureBufferPacketID, captureBufferPacketData
captureBufferPacketLength, captureBufferPacketTime
}
STATUS
"The RMON Packet Capture Group."
::= { rmonGroups 9 }
rmonEventGroup OBJECT-
OBJECTS {
eventIndex, eventDescription, eventType
eventCommunity, eventLastTimeSent
eventOwner, eventStatus
logEventIndex, logIndex, logTime
}
STATUS
Waldbusser Standards Track [Page 93]
RFC 2819 Remote Network Monitoring MIB May 2000
"The RMON Event Group."
::= { rmonGroups 10 }
rmonNotificationGroup NOTIFICATION-
NOTIFICATIONS { risingAlarm, fallingAlarm }
STATUS
"The RMON Notification Group."
::= { rmonGroups 11 }
6. Security
In order to implement this MIB, a probe must capture all packets
the locally-attached network, including packets between
parties. These packets are analyzed to collect network addresses
protocol usage information, and conversation statistics. Data of
nature may be considered sensitive in some environments. In
environments the administrator may wish to restrict SNMP access
the probe
This MIB also includes functions for returning the contents
captured packets, potentially including sensitive user data
passwords. It is recommended that SNMP access to these functions
restricted
There are a number of management objects defined in this MIB
have a MAX-ACCESS clause of read-write and/or read-create.
objects may be considered sensitive or vulnerable in some
environments. The support for SET operations in a non-
environment without proper protection can have a negative effect
network operations
SNMPv1 by itself is not a secure environment. Even if the
itself is secure (for example by using IPSec), even then, there is
control as to who on the secure network is allowed to access
GET/SET (read/change/create/delete) the objects in this MIB
It is recommended that the implementors consider the
features as provided by the SNMPv3 framework. Specifically, the
of the User-based Security Model RFC 2574 [12] and the View-
Access Control Model RFC 2575 [15] is recommended
It is then a customer/user responsibility to ensure that the
entity giving access to an instance of this MIB, is
configured to give access to the objects only to those
(users) that have legitimate rights to indeed GET or
(change/create/delete) them
Waldbusser Standards Track [Page 94]
RFC 2819 Remote Network Monitoring MIB May 2000
7.
This document was produced by the IETF Remote Network
Working Group
8. Author's
Steve
Phone: +1-650-948-6500
Fax: +1-650-745-0671
Email: waldbusser@nextbeacon.
9.
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M. and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based Internets", STD 16,
1155, May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[4] Rose, M., "A Convention for Defining Traps for use with
SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Conformance Statements for SMIv2",
58, RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser
"Introduction to Community-based SNMPv2", RFC 1901,
1996.
Waldbusser Standards Track [Page 95]
RFC 2819 Remote Network Monitoring MIB May 2000
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Mappings for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "
Processing and Dispatching for the Simple Network
Protocol (SNMP)", RFC 2572, April 1999.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM
for version 3 of the Simple Network Management
(SNMPv3)", RFC 2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Operations for Version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications",
2573, April 1999.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management
(SNMP)", RFC 2575, April 1999.
[16] McCloghrie, K. and M. Rose, Editors, "Management
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, March 1991.
[17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
using SMIv2", RFC 2233, November 1997.
[18] Waldbusser, S., "Remote Network Monitoring MIB", RFC 1757,
February 1995.
[19] Waldbusser, S., "Token Ring Extensions to the Remote
Monitoring MIB", RFC 1513, September 1993.
[20] Waldbusser, S., "Remote Network Monitoring
Information Base Version 2 using SMIv2", RFC 2021, January 1997.
[21] Waterman, R., Lahaye, B., Romascanu, D. and S. Waldbusser
"Remote Network Monitoring MIB Extensions for Switched
Version 1.0", RFC 2613, June 1999.
[22] Case, J., Mundy, R., Partain, D. and B. Stewart, "
to Version 3 of the Internet-standard Network
Framework", RFC 2570, April 1999.
Waldbusser Standards Track [Page 96]
RFC 2819 Remote Network Monitoring MIB May 2000
10. Intellectual
The IETF takes no position regarding the validity or scope of
intellectual property or other rights that might be claimed
pertain to the implementation or use of the technology described
this document or the extent to which any license under such
might or might not be available; neither does it represent that
has made any effort to identify any such rights. Information on
IETF's procedures with respect to rights in standards-track
standards-related documentation can be found in BCP-11. Copies
claims of rights made available for publication and any assurances
licenses to be made available, or the result of an attempt made
obtain a general license or permission for the use of
proprietary rights by implementors or users of this specification
be obtained from the IETF Secretariat
The IETF invites any interested party to bring to its attention
copyrights, patents or patent applications, or other
rights which may cover technology that may be required to
this standard. Please address the information to the IETF
Director
Waldbusser Standards Track [Page 97]
RFC 2819 Remote Network Monitoring MIB May 2000
11. Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Waldbusser Standards Track [Page 98]
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
