As per Relevance of the word associated, we have this rfc below:
Network Working Group S.
Request for Comments: 3273 July 2002
Category: Standards
Remote Network Monitoring Management Information Base for
Capacity
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 (2002). 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 (RMON) devices for use on high speed networks.
document contains a MIB Module that defines these new objects
also contains definitions of some updated objects from the RMON-
in RFC 2819 and the RMON2-MIB in RFC 2021.
Table of
1 The SNMP Management Framework ............................... 2
2 Overview .................................................... 3
2.1 Structure of MIB .......................................... 3
3 Updates to RMON MIB and RMON2 MIB objects ................... 4
4 Conventions ................................................. 6
5 Definitions ................................................. 7
6 Security Considerations .....................................73
7 Acknowledgments .............................................73
8 References ..................................................73
9 Notices .....................................................75
10 Author's Address.............................................76
11 Full Copyright Statement.....................................77
Waldbusser Standards Track [Page 1]
RFC 3273 Remote Network Monitoring Management July 2002
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
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3], and RFC 1215 [4].
The second version, called SMIv2, is described in STD 58,
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
is described in STD 15, RFC 1157 [8]. A second version of
SNMP message protocol, which is not an Internet standards
protocol, is called SNMPv2c and is described in RFC 1901 [9],
and RFC 1906 [10]. The third version of the message
is called SNMPv3 and is 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]
and the view-based access control mechanism described in
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
Waldbusser Standards Track [Page 2]
RFC 3273 Remote Network Monitoring Management July 2002
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
2.
This document continues the architecture created in the RMON MIB [
2819] by supporting high speed networks
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
tolerate the complexity of manually manipulating objects
accomplish row creation. These functions should be handled by
management application
2.1 Structure of
Except for the mediaIndependentTable, each of the tables in this
adds high capacity capability to an associated table in the RMON-1
MIB or RMON-2 MIB
The objects are arranged into the following groups
-
-
-
-
-
-
-
Waldbusser Standards Track [Page 3]
RFC 3273 Remote Network Monitoring Management July 2002
-
-
-
-
-
-
-
-
These groups are the basic units of conformance. If a
monitoring device implements a group, then it must implement
objects in that group. For example, a managed agent that
the network layer matrix group must implement
nlMatrixSDHighCapacityTable and the nlMatrixDSHighCapacityTable
Implementations of this MIB must also implement the system
interfaces group of MIB-II [16,17]. MIB-II may also mandate
implementation of additional groups
These groups are defined to provide a means of assigning
identifiers, and to provide a method for agent implementors to
which objects they must implement
3. Updates to RMON MIB and RMON2 MIB
This document extends the enumerations in the following objects
the RMON MIB [18] and the RMON2 MIB [20].
From the RMON MIB
hostTopNRateBase OBJECT-
SYNTAX INTEGER {
hostTopNInPkts(1),
hostTopNOutPkts(2),
hostTopNInOctets(3),
hostTopNOutOctets(4),
hostTopNOutErrors(5),
hostTopNOutBroadcastPkts(6),
hostTopNOutMulticastPkts(7),
hostTopNHCInPkts(8),
hostTopNHCOutPkts(9),
Waldbusser Standards Track [Page 4]
RFC 3273 Remote Network Monitoring Management July 2002
hostTopNHCInOctets(10),
hostTopNHCOutOctets(11)
}
MAX-ACCESS read-
STATUS
"The variable for each host that the
variable is based upon, as well as a
for the table that the results will be reported in
This object may not be modified if the
hostTopNStatus object is equal to valid(1).
If this value is less than or equal to 7, when the
is prepared, entries are created in the
associated with this object
If this value is greater than or equal to 8, when the
is prepared, entries are created in
hostTopNHighCapacityTable associated with this object."
::= { hostTopNControlEntry 3 }
From the RMON2 MIB
nlMatrixTopNControlRateBase OBJECT-
SYNTAX INTEGER {
nlMatrixTopNPkts(1),
nlMatrixTopNOctets(2),
nlMatrixTopNHighCapacityPkts(3),
nlMatrixTopNHighCapacityOctets(4)
}
MAX-ACCESS read-
STATUS
"The variable for each nlMatrix[SD/DS] entry that
nlMatrixTopNEntries are sorted by, as well as a
for the table that the results will be reported in
This object may not be modified if the
nlMatrixTopNControlStatus object is equal to active(1).
If this value is less than or equal to 2, when the
is prepared, entries are created in the
associated with this object
If this value is greater than or equal to 3, when the
is prepared, entries are created in
nlMatrixTopNHighCapacityTable associated with this object."
::= { nlMatrixTopNControlEntry 3 }
Waldbusser Standards Track [Page 5]
RFC 3273 Remote Network Monitoring Management July 2002
From the RMON2 MIB
alMatrixTopNControlRateBase OBJECT-
SYNTAX INTEGER {
alMatrixTopNTerminalsPkts(1),
alMatrixTopNTerminalsOctets(2),
alMatrixTopNAllPkts(3),
alMatrixTopNAllOctets(4),
alMatrixTopNTerminalsHighCapacityPkts(5),
alMatrixTopNTerminalsHighCapacityOctets(6),
alMatrixTopNAllHighCapacityPkts(7),
alMatrixTopNAllHighCapacityOctets(8)
}
MAX-ACCESS read-
STATUS
"The variable for each alMatrix[SD/DS] entry that
alMatrixTopNEntries are sorted by, as well as
selector of the view of the matrix table that will
used, as well as a control for the table that the
will be reported in
The values alMatrixTopNTerminalsPkts
alMatrixTopNTerminalsOctets
alMatrixTopNTerminalsHighCapacityPkts,
alMatrixTopNTerminalsHighCapacityOctets cause
only from protocols that have no child protocols that
counted. The values alMatrixTopNAllPkts
alMatrixTopNAllOctets, alMatrixTopNAllHighCapacityPkts,
alMatrixTopNAllHighCapacityOctets cause collection from
alMatrix entries
This object may not be modified if the
alMatrixTopNControlStatus object is equal to active(1)."
::= { alMatrixTopNControlEntry 3 }
For convenience, updated MIB modules containing these objects may
found at
ftp://ftp.rfc-editor.org/in-notes/mibs/current.mibs/rmon.
ftp://ftp.rfc-editor.org/in-notes/mibs/current.mibs/rmon2.
4.
The following conventions are used throughout the RMON MIB and
companion documents
Waldbusser Standards Track [Page 6]
RFC 3273 Remote Network Monitoring Management July 2002
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in RFC 2119.
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. Implementors are
to consult the appropriate media-specific specifications
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 (Start of Frame Delimiter), but have a bad
(Frame Check Sequence), or are either shorter than 64 octets
longer than 1518 octets. Implementors are urged to consult
appropriate media-specific specifications
5.
HC-RMON-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32,
Gauge32, Counter64 FROM SNMPv2-
RowStatus, TimeStamp FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-
rmon, OwnerString, statistics, history, hosts, hostTopN, matrix
etherStatsIndex, etherHistoryIndex, etherHistorySampleIndex
hostIndex, hostAddress, hostTimeIndex, hostTimeCreationOrder
hostTopNReport, hostTopNIndex
matrixSDIndex, matrixSDSourceAddress, matrixSDDestAddress
matrixDSIndex, matrixDSDestAddress, matrixDSSourceAddress
capture, captureBufferControlIndex,
FROM RMON-
protocolDirLocalIndex, protocolDistControlIndex
protocolDist, hlHostControlIndex
nlHost, nlHostTimeMark, nlHostAddress
hlMatrixControlIndex, nlMatrix
nlMatrixSDTimeMark, nlMatrixSDSourceAddress, nlMatrixSDDestAddress
nlMatrixDSTimeMark, nlMatrixDSDestAddress, nlMatrixDSSourceAddress
nlMatrixTopNControlIndex, nlMatrixTopNIndex
alHost, alHostTimeMark
alMatrix, alMatrixSDTimeMark, alMatrixDSTimeMark
alMatrixTopNControlIndex, alMatrixTopNIndex
Waldbusser Standards Track [Page 7]
RFC 3273 Remote Network Monitoring Management July 2002
usrHistory, usrHistoryControlIndex
usrHistorySampleIndex, usrHistoryObjectIndex
rmonConformance, ZeroBasedCounter32,
FROM RMON2-
ZeroBasedCounter64, CounterBasedGauge64
FROM HCNUM-TC
-- Remote Network Monitoring
hcRMON MODULE-
LAST-UPDATED "200205080000Z" -- May 08, 2002
ORGANIZATION "IETF RMON MIB Working Group
CONTACT-
"Steve
Phone: +1-650-948-6500
Fax: +1-650-745-0671
Email: waldbusser@nextbeacon.
Andy
WG
abierman@cisco.
RMONMIB WG Mailing
rmonmib@ietf.
http://www.ietf.org/mailman/listinfo/rmonmib
"The MIB module for managing remote
device implementations. This MIB
augments the original RMON MIB as specified
RFC 2819 and RFC 1513 and RMON-2 MIB as specified
RFC 2021."
REVISION "200205080000Z" -- May 08, 2002
"The original version of this MIB, published as RFC3273."
::= { rmonConformance 5 }
-- { rmon 1 } through { rmon 20 } are defined in RMON [RFC 2819]
-- the Token Ring RMON MIB [RFC 1513] and the RMON-2 MIB [RFC 2021].
mediaIndependentStats OBJECT IDENTIFIER ::= { rmon 21 }
mediaIndependentTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
Waldbusser Standards Track [Page 8]
RFC 3273 Remote Network Monitoring Management July 2002
"Media independent statistics for promiscuous monitoring
any media
The following table defines media independent statistics
provide information for full and/or half-duplex links as
as high capacity links
For half-duplex links, or full-duplex-capable links
in half-duplex mode, the mediaIndependentIn* objects shall
used and the mediaIndependentOut* objects shall not increment
For full-duplex links, the mediaIndependentOut* objects
be present and shall increment. Whenever possible, the
should count packets moving away from the closest
equipment as output packets. Failing that, the probe
count packets moving away from the DTE as output packets."
::= { mediaIndependentStats 1 }
mediaIndependentEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Media independent statistics for promiscuous monitoring
any media."
INDEX { mediaIndependentIndex }
::= { mediaIndependentTable 1 }
MediaIndependentEntry ::= SEQUENCE {
mediaIndependentIndex Integer32,
mediaIndependentDataSource OBJECT IDENTIFIER
mediaIndependentDropEvents Counter32,
mediaIndependentDroppedFrames Counter32,
mediaIndependentInPkts Counter32,
mediaIndependentInOverflowPkts Counter32,
mediaIndependentInHighCapacityPkts Counter64,
mediaIndependentOutPkts Counter32,
mediaIndependentOutOverflowPkts Counter32,
mediaIndependentOutHighCapacityPkts Counter64,
mediaIndependentInOctets Counter32,
mediaIndependentInOverflowOctets Counter32,
mediaIndependentInHighCapacityOctets Counter64,
mediaIndependentOutOctets Counter32,
mediaIndependentOutOverflowOctets Counter32,
mediaIndependentOutHighCapacityOctets Counter64,
mediaIndependentInNUCastPkts Counter32,
mediaIndependentInNUCastOverflowPkts Counter32,
Waldbusser Standards Track [Page 9]
RFC 3273 Remote Network Monitoring Management July 2002
mediaIndependentInNUCastHighCapacityPkts Counter64,
mediaIndependentOutNUCastPkts Counter32,
mediaIndependentOutNUCastOverflowPkts Counter32,
mediaIndependentOutNUCastHighCapacityPkts Counter64,
mediaIndependentInErrors Counter32,
mediaIndependentOutErrors Counter32,
mediaIndependentInputSpeed Gauge32,
mediaIndependentOutputSpeed Gauge32,
mediaIndependentDuplexMode INTEGER
mediaIndependentDuplexChanges Counter32,
mediaIndependentDuplexLastChange TimeStamp
mediaIndependentOwner OwnerString
mediaIndependentStatus
mediaIndependentIndex OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-
STATUS
"The value of this object uniquely identifies
mediaIndependent entry."
::= { mediaIndependentEntry 1 }
mediaIndependentDataSource OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"This object identifies the source of the data
this mediaIndependent entry is configured to analyze.
source can be any interface on this device
In order to identify a particular interface,
object shall identify the instance of the
object, defined in RFC 1213 and RFC 2233 [16,17],
the desired interface. For example, if an
were to receive data from interface #1, this
would be set to ifIndex.1.
The statistics in this group reflect all
on the local network segment attached to
identified interface
An agent may or may not be able to tell
fundamental changes to the media of the
have occurred and necessitate a deletion
this entry. For example, a hot-pluggable
card could be pulled out and replaced by
Waldbusser Standards Track [Page 10]
RFC 3273 Remote Network Monitoring Management July 2002
token-ring card. In such a case, if the agent
such knowledge of the change, it is recommended
it delete this entry
This object may not be modified if the
mediaIndependentStatus object is equal to active(1)."
::= { mediaIndependentEntry 2 }
mediaIndependentDropEvents OBJECT-
SYNTAX Counter32
UNITS "Events
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."
::= { mediaIndependentEntry 3 }
mediaIndependentDroppedFrames OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of frames which were received by the
and therefore not accounted for in
mediaIndependentDropEvents, but for which the probe chose
to count for this entry for whatever reason. Most often,
event occurs when the probe is out of some resources
decides to shed load from this collection
This count does not include packets that were not
because they had MAC-layer errors
Note that, unlike the dropEvents counter, this number is
exact number of frames dropped."
::= { mediaIndependentEntry 4 }
mediaIndependentInPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including bad packets
Waldbusser Standards Track [Page 11]
RFC 3273 Remote Network Monitoring Management July 2002
broadcast packets, and multicast packets)
on a half-duplex link or on the inbound connection of
full-duplex link."
::= { mediaIndependentEntry 5 }
mediaIndependentInOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the
mediaIndependentInPkts counter has overflowed."
::= { mediaIndependentEntry 6 }
mediaIndependentInHighCapacityPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including bad packets
broadcast packets, and multicast packets)
on a half-duplex link or on the inbound connection of
full-duplex link."
::= { mediaIndependentEntry 7 }
mediaIndependentOutPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including bad packets
broadcast packets, and multicast packets) received on
full-duplex link in the direction of the network."
::= { mediaIndependentEntry 8 }
mediaIndependentOutOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the
mediaIndependentOutPkts counter has overflowed."
::= { mediaIndependentEntry 9 }
Waldbusser Standards Track [Page 12]
RFC 3273 Remote Network Monitoring Management July 2002
mediaIndependentOutHighCapacityPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including bad packets
broadcast packets, and multicast packets) received on
full-duplex link in the direction of the network."
::= { mediaIndependentEntry 10 }
mediaIndependentInOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The total number of octets of data (including those in
packets) received (excluding framing bits but including
octets) on a half-duplex link or on the inbound connection
a full-duplex link."
::= { mediaIndependentEntry 11 }
mediaIndependentInOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the
mediaIndependentInOctets counter has overflowed."
::= { mediaIndependentEntry 12 }
mediaIndependentInHighCapacityOctets OBJECT-
SYNTAX Counter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The total number of octets of data (including those in
packets) received (excluding framing bits
including FCS octets) on a half-duplex link or on the
connection of a full-duplex link."
::= { mediaIndependentEntry 13 }
mediaIndependentOutOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
Waldbusser Standards Track [Page 13]
RFC 3273 Remote Network Monitoring Management July 2002
MAX-ACCESS read-
STATUS
"The total number of octets of data (including those in
packets) received on a full-duplex link in the direction
the network (excluding framing bits but including
octets)."
::= { mediaIndependentEntry 14 }
mediaIndependentOutOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the
mediaIndependentOutOctets counter has overflowed."
::= { mediaIndependentEntry 15 }
mediaIndependentOutHighCapacityOctets OBJECT-
SYNTAX Counter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The total number of octets of data (including those in
packets) received on a full-duplex link in the direction
the network (excluding framing bits but including
octets)."
::= { mediaIndependentEntry 16 }
mediaIndependentInNUCastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of non-unicast packets (including
packets) received on a half-duplex link or on the
connection of a full-duplex link."
::= { mediaIndependentEntry 17 }
mediaIndependentInNUCastOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 14]
RFC 3273 Remote Network Monitoring Management July 2002
"The number of times the
mediaIndependentInNUCastPkts counter has overflowed."
::= { mediaIndependentEntry 18 }
mediaIndependentInNUCastHighCapacityPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of non-unicast packets (including
packets) received on a half-duplex link or on the
connection of a full-duplex link."
::= { mediaIndependentEntry 19 }
mediaIndependentOutNUCastPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of non-unicast packets (including
packets) received on a full-duplex link in the direction
the network."
::= { mediaIndependentEntry 20 }
mediaIndependentOutNUCastOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the
mediaIndependentOutNUCastPkts counter has overflowed."
::= { mediaIndependentEntry 21 }
mediaIndependentOutNUCastHighCapacityPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including bad packets
received on a full-duplex link in the direction of
network."
::= { mediaIndependentEntry 22 }
mediaIndependentInErrors OBJECT-
Waldbusser Standards Track [Page 15]
RFC 3273 Remote Network Monitoring Management July 2002
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of bad packets received on
half-duplex link or on the inbound connection of
full-duplex link."
::= { mediaIndependentEntry 23 }
mediaIndependentOutErrors OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of bad packets received on a full-
link in the direction of the network."
::= { mediaIndependentEntry 24 }
mediaIndependentInputSpeed OBJECT-
SYNTAX Gauge32
UNITS "Kilobits per Second
MAX-ACCESS read-
STATUS
"The nominal maximum speed in kilobits per second of
half-duplex link or on the inbound connection of
full-duplex link. If the speed is unknown or there is no
maximum (e.g. a compressed link), this value shall be zero."
::= { mediaIndependentEntry 25 }
mediaIndependentOutputSpeed OBJECT-
SYNTAX Gauge32
UNITS "Kilobits per Second
MAX-ACCESS read-
STATUS
"The nominal maximum speed in kilobits per second of
full-duplex link in the direction of the network. If the
is unknown, the link is half-duplex, or there is no
maximum (e.g. a compressed link), this value shall be zero."
::= { mediaIndependentEntry 26 }
mediaIndependentDuplexMode OBJECT-
SYNTAX INTEGER {
halfduplex(1),
fullduplex(2)
Waldbusser Standards Track [Page 16]
RFC 3273 Remote Network Monitoring Management July 2002
}
MAX-ACCESS read-
STATUS
"The current mode of this link
Note that if the link has full-duplex capabilities
is operating in half-duplex mode, this value will
halfduplex(1)."
::= { mediaIndependentEntry 27 }
mediaIndependentDuplexChanges OBJECT-
SYNTAX Counter32
UNITS "Events
MAX-ACCESS read-
STATUS
"The number of times this link has changed from full-
mode to half-duplex mode or from half-duplex mode
full-duplex mode."
::= { mediaIndependentEntry 28 }
mediaIndependentDuplexLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the time the duplex
of this link last changed."
::= { mediaIndependentEntry 29 }
mediaIndependentOwner OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The entity that configured this entry and
therefore using the resources assigned to it."
::= { mediaIndependentEntry 30 }
mediaIndependentStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The status of this media independent statistics entry."
::= { mediaIndependentEntry 31 }
Waldbusser Standards Track [Page 17]
RFC 3273 Remote Network Monitoring Management July 2002
-- High Capacity extensions for the
etherStatsHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
etherStatsTable."
::= { statistics 7 }
etherStatsHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
etherStatsEntry. These objects will be created by the
for all etherStatsEntries it deems appropriate."
INDEX { etherStatsIndex }
::= { etherStatsHighCapacityTable 1 }
EtherStatsHighCapacityEntry ::= SEQUENCE {
etherStatsHighCapacityOverflowPkts Counter32,
etherStatsHighCapacityPkts Counter64,
etherStatsHighCapacityOverflowOctets Counter32,
etherStatsHighCapacityOctets Counter64,
etherStatsHighCapacityOverflowPkts64Octets Counter32,
etherStatsHighCapacityPkts64Octets Counter64,
etherStatsHighCapacityOverflowPkts65to127Octets Counter32,
etherStatsHighCapacityPkts65to127Octets Counter64,
etherStatsHighCapacityOverflowPkts128to255Octets Counter32,
etherStatsHighCapacityPkts128to255Octets Counter64,
etherStatsHighCapacityOverflowPkts256to511Octets Counter32,
etherStatsHighCapacityPkts256to511Octets Counter64,
etherStatsHighCapacityOverflowPkts512to1023Octets Counter32,
etherStatsHighCapacityPkts512to1023Octets Counter64,
etherStatsHighCapacityOverflowPkts1024to1518Octets Counter32,
etherStatsHighCapacityPkts1024to1518Octets Counter64
etherStatsHighCapacityOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 18]
RFC 3273 Remote Network Monitoring Management July 2002
"The number of times the associated
counter has overflowed."
::= { etherStatsHighCapacityEntry 1 }
etherStatsHighCapacityPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including bad packets
broadcast packets, and multicast packets) received."
::= { etherStatsHighCapacityEntry 2 }
etherStatsHighCapacityOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { etherStatsHighCapacityEntry 3 }
etherStatsHighCapacityOctets OBJECT-
SYNTAX Counter64
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).
If the network is half-duplex Fast Ethernet,
object can be used as a reasonable estimate
utilization. If greater precision is desired,
etherStatsHighCapacityPkts
etherStatsHighCapacityOctets objects should be
before and after a common interval. The
in the sampled values are Pkts and Octets
respectively, and the number of seconds in
interval is Interval. These
are used to calculate the Utilization as follows
Waldbusser Standards Track [Page 19]
RFC 3273 Remote Network Monitoring Management July 2002
Pkts * (.96 + .64) + (Octets * .08)
Utilization = -------------------------------------
Interval * 10,000
The result of this equation is the value
which is the percent utilization of the
segment on a scale of 0 to 100 percent
This table is not appropriate for monitoring full-
ethernets. If the network is a full-duplex ethernet and
mediaIndependentTable is monitoring that network,
utilization can be calculated as follows
1) Determine the utilization of the inbound path by
the appropriate equation (for ethernet or fast ethernet
to determine the utilization,
mediaIndependentInPkts for etherStatsHighCapacityPkts,
mediaIndependentInOctets for etherStatsHighCapacityOctets
Call the resulting utilization inUtilization
2) Determine the utilization of the outbound path by
the same equation to determine the utilization,
mediaIndependentOutPkts for etherStatsHighCapacityPkts,
mediaIndependentOutOctets for etherStatsHighCapacityOctets
Call the resulting utilization outUtilization
3) The utilization is the maximum of inUtilization
outUtilization. This metric shows the amount of
of bandwidth that is left before congestion will
experienced on the link."
::= { etherStatsHighCapacityEntry 4 }
etherStatsHighCapacityOverflowPkts64Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated etherStatsPkts64
counter has overflowed."
::= { etherStatsHighCapacityEntry 5 }
etherStatsHighCapacityPkts64Octets OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 20]
RFC 3273 Remote Network Monitoring Management July 2002
"The total number of packets (including
packets) received that were 64 octets in
(excluding framing bits but including FCS octets)."
::= { etherStatsHighCapacityEntry 6 }
etherStatsHighCapacityOverflowPkts65to127Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated etherStatsPkts65to127
counter has overflowed."
::= { etherStatsHighCapacityEntry 7 }
etherStatsHighCapacityPkts65to127Octets OBJECT-
SYNTAX Counter64
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)."
::= { etherStatsHighCapacityEntry 8 }
etherStatsHighCapacityOverflowPkts128to255Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated etherStatsPkts128to255
counter has overflowed."
::= { etherStatsHighCapacityEntry 9 }
etherStatsHighCapacityPkts128to255Octets OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including
packets) received that were
128 and 255 octets in length
(excluding framing bits but including FCS octets)."
::= { etherStatsHighCapacityEntry 10 }
Waldbusser Standards Track [Page 21]
RFC 3273 Remote Network Monitoring Management July 2002
etherStatsHighCapacityOverflowPkts256to511Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated etherStatsPkts256to511
counter has overflowed."
::= { etherStatsHighCapacityEntry 11 }
etherStatsHighCapacityPkts256to511Octets OBJECT-
SYNTAX Counter64
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)."
::= { etherStatsHighCapacityEntry 12 }
etherStatsHighCapacityOverflowPkts512to1023Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the
etherStatsPkts512to1023Octets counter has overflowed."
::= { etherStatsHighCapacityEntry 13 }
etherStatsHighCapacityPkts512to1023Octets OBJECT-
SYNTAX Counter64
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)."
::= { etherStatsHighCapacityEntry 14 }
etherStatsHighCapacityOverflowPkts1024to1518Octets OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
Waldbusser Standards Track [Page 22]
RFC 3273 Remote Network Monitoring Management July 2002
STATUS
"The number of times the
etherStatsPkts1024to1518Octets counter has overflowed."
::= { etherStatsHighCapacityEntry 15 }
etherStatsHighCapacityPkts1024to1518Octets OBJECT-
SYNTAX Counter64
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)."
::= { etherStatsHighCapacityEntry 16 }
-- High Capacity extensions for the
etherHistoryHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
etherHistoryTable."
::= { history 6 }
etherHistoryHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
etherHistoryEntry. These objects will be created by the
for all etherHistoryEntries associated with
historyControlEntries it deems appropriate. (i.e., either
etherHistoryHighCapacityEntries associated with a
historyControlEntry will be created, or none of them
be.)"
INDEX { etherHistoryIndex, etherHistorySampleIndex }
::= { etherHistoryHighCapacityTable 1 }
EtherHistoryHighCapacityEntry ::= SEQUENCE {
etherHistoryHighCapacityOverflowPkts Gauge32,
etherHistoryHighCapacityPkts CounterBasedGauge64,
etherHistoryHighCapacityOverflowOctets Gauge32,
Waldbusser Standards Track [Page 23]
RFC 3273 Remote Network Monitoring Management July 2002
etherHistoryHighCapacityOctets CounterBasedGauge64
etherHistoryHighCapacityOverflowPkts OBJECT-
SYNTAX Gauge32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
Gauge overflowed during this sampling interval."
::= { etherHistoryHighCapacityEntry 1 }
etherHistoryHighCapacityPkts OBJECT-
SYNTAX CounterBasedGauge64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The total number of packets (including bad packets
broadcast packets, and multicast packets) received
this sampling interval."
::= { etherHistoryHighCapacityEntry 2 }
etherHistoryHighCapacityOverflowOctets OBJECT-
SYNTAX Gauge32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed during this sampling interval."
::= { etherHistoryHighCapacityEntry 3 }
etherHistoryHighCapacityOctets OBJECT-
SYNTAX CounterBasedGauge64
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) during this sampling interval."
::= { etherHistoryHighCapacityEntry 4 }
-- High Capacity Extensions for the
Waldbusser Standards Track [Page 24]
RFC 3273 Remote Network Monitoring Management July 2002
hostHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
hostTable."
::= { hosts 5 }
hostHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
hostEntry. These objects will be created by the
for all hostEntries associated with
hostControlEntries it deems appropriate. (i.e., either
hostHighCapacityEntries associated with a
hostControlEntry will be created, or none of them
be.)"
INDEX { hostIndex, hostAddress }
::= { hostHighCapacityTable 1 }
HostHighCapacityEntry ::= SEQUENCE {
hostHighCapacityInOverflowPkts Counter32,
hostHighCapacityInPkts Counter64,
hostHighCapacityOutOverflowPkts Counter32,
hostHighCapacityOutPkts Counter64,
hostHighCapacityInOverflowOctets Counter32,
hostHighCapacityInOctets Counter64,
hostHighCapacityOutOverflowOctets Counter32,
hostHighCapacityOutOctets Counter64
hostHighCapacityInOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { hostHighCapacityEntry 1 }
hostHighCapacityInPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
Waldbusser Standards Track [Page 25]
RFC 3273 Remote Network Monitoring Management July 2002
MAX-ACCESS read-
STATUS
"The number of good packets transmitted
this address since it was added to
hostHighCapacityTable."
::= { hostHighCapacityEntry 2 }
hostHighCapacityOutOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { hostHighCapacityEntry 3 }
hostHighCapacityOutPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets, including bad packets,
by this address since it was added to
hostHighCapacityTable."
::= { hostHighCapacityEntry 4 }
hostHighCapacityInOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { hostHighCapacityEntry 5 }
hostHighCapacityInOctets OBJECT-
SYNTAX Counter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted to this
since it was added to the hostHighCapacityTable (
framing bits but including FCS octets), except
Waldbusser Standards Track [Page 26]
RFC 3273 Remote Network Monitoring Management July 2002
those octets in bad packets."
::= { hostHighCapacityEntry 6 }
hostHighCapacityOutOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { hostHighCapacityEntry 7 }
hostHighCapacityOutOctets OBJECT-
SYNTAX Counter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted by this
since it was added to the hostHighCapacityTable (
framing bits but including FCS octets),
those octets in bad packets."
::= { hostHighCapacityEntry 8 }
-- High Capacity extensions for the
hostTimeHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
hostTimeTable."
::= { hosts 6 }
hostTimeHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
hostTimeEntry. These objects will be created by the
for all hostTimeEntries associated with
hostControlEntries it deems appropriate. (i.e., either
hostTimeHighCapacityEntries associated with a
hostControlEntry will be created, or none of them
be.)"
Waldbusser Standards Track [Page 27]
RFC 3273 Remote Network Monitoring Management July 2002
INDEX { hostTimeIndex, hostTimeCreationOrder }
::= { hostTimeHighCapacityTable 1 }
HostTimeHighCapacityEntry ::= SEQUENCE {
hostTimeHighCapacityInOverflowPkts Counter32,
hostTimeHighCapacityInPkts Counter64,
hostTimeHighCapacityOutOverflowPkts Counter32,
hostTimeHighCapacityOutPkts Counter64,
hostTimeHighCapacityInOverflowOctets Counter32,
hostTimeHighCapacityInOctets Counter64,
hostTimeHighCapacityOutOverflowOctets Counter32,
hostTimeHighCapacityOutOctets Counter64
hostTimeHighCapacityInOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { hostTimeHighCapacityEntry 1 }
hostTimeHighCapacityInPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of good packets transmitted to this
since it was added to the hostTimeHighCapacityTable."
::= { hostTimeHighCapacityEntry 2 }
hostTimeHighCapacityOutOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { hostTimeHighCapacityEntry 3 }
hostTimeHighCapacityOutPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
Waldbusser Standards Track [Page 28]
RFC 3273 Remote Network Monitoring Management July 2002
STATUS
"The number of packets, including bad packets,
by this address since it was added to
hostTimeHighCapacityTable."
::= { hostTimeHighCapacityEntry 4 }
hostTimeHighCapacityInOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { hostTimeHighCapacityEntry 5 }
hostTimeHighCapacityInOctets OBJECT-
SYNTAX Counter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted to this
since it was added to the
(excluding framing bits but including FCS octets),
except for those octets in bad packets."
::= { hostTimeHighCapacityEntry 6 }
hostTimeHighCapacityOutOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { hostTimeHighCapacityEntry 7 }
hostTimeHighCapacityOutOctets OBJECT-
SYNTAX Counter64
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
Waldbusser Standards Track [Page 29]
RFC 3273 Remote Network Monitoring Management July 2002
octets in bad packets."
::= { hostTimeHighCapacityEntry 8 }
-- High Capacity Extensions for the
hostTopNHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
hostTopNTable when hostTopNRateBase specifies a High
TopN Report."
::= { hostTopN 3 }
hostTopNHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
hostTopNEntry when hostTopNRateBase specifies a High
TopN Report. These objects will be created by the
for all hostTopNEntries associated with
hostTopNControlEntries have a hostTopNRateBase that
a high capacity report."
INDEX { hostTopNReport, hostTopNIndex }
::= { hostTopNHighCapacityTable 1 }
HostTopNHighCapacityEntry ::= SEQUENCE {
hostTopNHighCapacityAddress OCTET STRING
hostTopNHighCapacityBaseRate Gauge32,
hostTopNHighCapacityOverflowRate Gauge32,
hostTopNHighCapacityRate CounterBasedGauge64
hostTopNHighCapacityAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The physical address of this host."
::= { hostTopNHighCapacityEntry 1 }
hostTopNHighCapacityBaseRate OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
Waldbusser Standards Track [Page 30]
RFC 3273 Remote Network Monitoring Management July 2002
"The amount of change in the selected
during this sampling interval, modulo 2^32.
selected variable is this host's instance of
object selected by hostTopNRateBase."
::= { hostTopNHighCapacityEntry 2 }
hostTopNHighCapacityOverflowRate OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"The amount of change in the selected
during this sampling interval, divided by 2^32,
fractions (i.e., X DIV 2^32). The selected variable
this host's instance of the object selected
hostTopNRateBase."
::= { hostTopNHighCapacityEntry 3 }
hostTopNHighCapacityRate OBJECT-
SYNTAX CounterBasedGauge64
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."
::= { hostTopNHighCapacityEntry 4 }
-- High Capacity Extensions for the
matrixSDHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
matrixSDTable."
::= { matrix 5 }
matrixSDHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
matrixSDEntry. These objects will be created by the
Waldbusser Standards Track [Page 31]
RFC 3273 Remote Network Monitoring Management July 2002
for all matrixSDEntries associated with
matrixControlEntries it deems appropriate. (i.e., either
matrixSDHighCapacityEntries associated with a
matrixControlEntry will be created, or none of them
be.)"
INDEX { matrixSDIndex
matrixSDSourceAddress, matrixSDDestAddress }
::= { matrixSDHighCapacityTable 1 }
MatrixSDHighCapacityEntry ::= SEQUENCE {
matrixSDHighCapacityOverflowPkts Counter32,
matrixSDHighCapacityPkts Counter64,
matrixSDHighCapacityOverflowOctets Counter32,
matrixSDHighCapacityOctets Counter64
matrixSDHighCapacityOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { matrixSDHighCapacityEntry 1 }
matrixSDHighCapacityPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets transmitted from the
address to the destination address (this
includes bad packets)."
::= { matrixSDHighCapacityEntry 2 }
matrixSDHighCapacityOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { matrixSDHighCapacityEntry 3 }
matrixSDHighCapacityOctets OBJECT-
Waldbusser Standards Track [Page 32]
RFC 3273 Remote Network Monitoring Management July 2002
SYNTAX Counter64
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."
::= { matrixSDHighCapacityEntry 4 }
-- High Capacity extensions for the
matrixDSHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
matrixDSTable."
::= { matrix 6 }
matrixDSHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
matrixDSEntry. These objects will be created by the
for all matrixDSEntries associated with
matrixControlEntries it deems appropriate. (i.e., either
matrixDSHighCapacityEntries associated with a
matrixControlEntry will be created, or none of them
be.)"
INDEX { matrixDSIndex
matrixDSDestAddress, matrixDSSourceAddress }
::= { matrixDSHighCapacityTable 1 }
MatrixDSHighCapacityEntry ::= SEQUENCE {
matrixDSHighCapacityOverflowPkts Counter32,
matrixDSHighCapacityPkts Counter64,
matrixDSHighCapacityOverflowOctets Counter32,
matrixDSHighCapacityOctets Counter64
matrixDSHighCapacityOverflowPkts OBJECT-
SYNTAX Counter32
UNITS "Packets
Waldbusser Standards Track [Page 33]
RFC 3273 Remote Network Monitoring Management July 2002
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { matrixDSHighCapacityEntry 1 }
matrixDSHighCapacityPkts OBJECT-
SYNTAX Counter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets transmitted from the
address to the destination address (this
includes bad packets)."
::= { matrixDSHighCapacityEntry 2 }
matrixDSHighCapacityOverflowOctets OBJECT-
SYNTAX Counter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { matrixDSHighCapacityEntry 3 }
matrixDSHighCapacityOctets OBJECT-
SYNTAX Counter64
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."
::= { matrixDSHighCapacityEntry 4 }
-- High Capacity extensions for the
captureBufferHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
Waldbusser Standards Track [Page 34]
RFC 3273 Remote Network Monitoring Management July 2002
captureBufferTable."
::= { capture 3 }
captureBufferHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-1
captureBufferEntry. These objects will be created by the
for all captureBufferEntries associated with
bufferControlEntries it deems appropriate. (i.e., either
captureBufferHighCapacityEntries associated with a
bufferControlEntry will be created, or none of them
be.)"
INDEX { captureBufferControlIndex, captureBufferIndex }
::= { captureBufferHighCapacityTable 1 }
CaptureBufferHighCapacityEntry ::= SEQUENCE {
captureBufferPacketHighCapacityTime Integer32
captureBufferPacketHighCapacityTime OBJECT-
SYNTAX Integer32 (0..999999)
UNITS "nanoseconds
MAX-ACCESS read-
STATUS
"The number of nanoseconds that had passed since this
buffer was first turned on when this packet was captured
modulo 10^6.
This object is used in conjunction with
captureBufferPacketTime object. This object returns
number of nano-seconds to be added to to number
milli-seconds obtained from the
object, to obtain more accurate inter packet arrival time."
::= { captureBufferHighCapacityEntry 1 }
-- High Capacity extensions for the
protocolDistStatsHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
protocolDistStatsTable."
Waldbusser Standards Track [Page 35]
RFC 3273 Remote Network Monitoring Management July 2002
::= { protocolDist 3 }
protocolDistStatsHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
protocolDistStatsTable. These objects will be created by
agent for all protocolDistStatsEntries associated
whichever protocolDistControlEntries it deems appropriate
(i.e., either all
associated with a particular protocolDistControlEntry will
created, or none of them will be.)"
INDEX { protocolDistControlIndex, protocolDirLocalIndex }
::= { protocolDistStatsHighCapacityTable 1 }
ProtocolDistStatsHighCapacityEntry ::= SEQUENCE {
protocolDistStatsHighCapacityOverflowPkts ZeroBasedCounter32,
protocolDistStatsHighCapacityPkts ZeroBasedCounter64,
protocolDistStatsHighCapacityOverflowOctets ZeroBasedCounter32,
protocolDistStatsHighCapacityOctets ZeroBasedCounter64
protocolDistStatsHighCapacityOverflowPkts OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { protocolDistStatsHighCapacityEntry 1 }
protocolDistStatsHighCapacityPkts OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets without errors received of
protocol type. Note that this is the number of link-
packets, so if a single network-layer packet is
into several link-layer frames, this counter is
several times."
::= { protocolDistStatsHighCapacityEntry 2 }
protocolDistStatsHighCapacityOverflowOctets OBJECT-
Waldbusser Standards Track [Page 36]
RFC 3273 Remote Network Monitoring Management July 2002
SYNTAX ZeroBasedCounter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { protocolDistStatsHighCapacityEntry 3 }
protocolDistStatsHighCapacityOctets OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets in packets received of this
type since it was added to the
(excluding framing bits but including FCS octets), except
those octets in packets that contained errors
Note this doesn't count just those octets in the
protocol frames, but includes the entire packet that
the protocol."
::= { protocolDistStatsHighCapacityEntry 4 }
-- High Capacity extensions for the nlHostTable
nlHostHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
nlHostTable."
::= { nlHost 3 }
nlHostHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
nlHostEntry. These objects will be created by the
for all nlHostEntries associated with
hlHostControlEntries it deems appropriate. (i.e., either
nlHostHighCapacityEntries associated with a
hlHostControlEntry will be created, or none of them
be.)"
Waldbusser Standards Track [Page 37]
RFC 3273 Remote Network Monitoring Management July 2002
INDEX { hlHostControlIndex, nlHostTimeMark
protocolDirLocalIndex, nlHostAddress }
::= { nlHostHighCapacityTable 1 }
NlHostHighCapacityEntry ::= SEQUENCE {
nlHostHighCapacityInOverflowPkts ZeroBasedCounter32,
nlHostHighCapacityInPkts ZeroBasedCounter64,
nlHostHighCapacityOutOverflowPkts ZeroBasedCounter32,
nlHostHighCapacityOutPkts ZeroBasedCounter64,
nlHostHighCapacityInOverflowOctets ZeroBasedCounter32,
nlHostHighCapacityInOctets ZeroBasedCounter64,
nlHostHighCapacityOutOverflowOctets ZeroBasedCounter32,
nlHostHighCapacityOutOctets ZeroBasedCounter64
nlHostHighCapacityInOverflowPkts OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { nlHostHighCapacityEntry 1 }
nlHostHighCapacityInPkts OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets without errors transmitted
this address since it was added to the nlHostHighCapacityTable
Note that this is the number of link-layer packets, so if
single network-layer packet is fragmented into
link-layer frames, this counter is incremented several times."
::= { nlHostHighCapacityEntry 2 }
nlHostHighCapacityOutOverflowPkts OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { nlHostHighCapacityEntry 3 }
Waldbusser Standards Track [Page 38]
RFC 3273 Remote Network Monitoring Management July 2002
nlHostHighCapacityOutPkts OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets without errors transmitted
this address since it was added to the nlHostHighCapacityTable
Note that this is the number of link-layer packets, so if
single network-layer packet is fragmented into
link-layer frames, this counter is incremented several times."
::= { nlHostHighCapacityEntry 4 }
nlHostHighCapacityInOverflowOctets OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { nlHostHighCapacityEntry 5 }
nlHostHighCapacityInOctets OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted to this
since it was added to the
(excluding framing bits but including FCS octets),
excluding those octets in packets that
errors
Note this doesn't count just those octets in
particular protocol frames, but includes the
packet that contained the protocol."
::= { nlHostHighCapacityEntry 6 }
nlHostHighCapacityOutOverflowOctets OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
Waldbusser Standards Track [Page 39]
RFC 3273 Remote Network Monitoring Management July 2002
::= { nlHostHighCapacityEntry 7 }
nlHostHighCapacityOutOctets OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted by this
since it was added to the
(excluding framing bits but including FCS octets),
excluding those octets in packets that
errors
Note this doesn't count just those octets in
particular protocol frames, but includes the
packet that contained the protocol."
::= { nlHostHighCapacityEntry 8 }
-- High Capacity extensions for the
nlMatrixSDHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
nlMatrixTable."
::= { nlMatrix 6 }
nlMatrixSDHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
nlMatrixEntry. These objects will be created by the
for all nlMatrixSDEntries associated with
hlMatrixControlEntries it deems appropriate. (i.e., either
nlMatrixSDHighCapacityEntries associated with a
hlMatrixControlEntry will be created, or none of them
be.)"
INDEX { hlMatrixControlIndex, nlMatrixSDTimeMark
protocolDirLocalIndex
nlMatrixSDSourceAddress, nlMatrixSDDestAddress }
::= { nlMatrixSDHighCapacityTable 1 }
NlMatrixSDHighCapacityEntry ::= SEQUENCE {
Waldbusser Standards Track [Page 40]
RFC 3273 Remote Network Monitoring Management July 2002
nlMatrixSDHighCapacityOverflowPkts ZeroBasedCounter32,
nlMatrixSDHighCapacityPkts ZeroBasedCounter64,
nlMatrixSDHighCapacityOverflowOctets ZeroBasedCounter32,
nlMatrixSDHighCapacityOctets ZeroBasedCounter64
nlMatrixSDHighCapacityOverflowPkts OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { nlMatrixSDHighCapacityEntry 1 }
nlMatrixSDHighCapacityPkts OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets without errors transmitted from
source address to the destination address since this entry
added to the nlMatrixSDHighCapacityTable. Note that this
the number of link-layer packets, so if a single network-
packet is fragmented into several link-layer frames,
counter is incremented several times."
::= { nlMatrixSDHighCapacityEntry 2 }
nlMatrixSDHighCapacityOverflowOctets OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { nlMatrixSDHighCapacityEntry 3 }
nlMatrixSDHighCapacityOctets OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted from the source address
the destination address since this entry was added to
Waldbusser Standards Track [Page 41]
RFC 3273 Remote Network Monitoring Management July 2002
nlMatrixSDHighCapacityTable (excluding framing bits
including FCS octets), excluding those octets in packets
contained errors
Note this doesn't count just those octets in the
protocol frames, but includes the entire packet that
the protocol."
::= { nlMatrixSDHighCapacityEntry 4 }
-- High Capacity extensions for the
nlMatrixDSHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
nlMatrixDSTable."
::= { nlMatrix 7 }
nlMatrixDSHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
nlMatrixDSEntry. These objects will be created by the
for all nlMatrixDSEntries associated with
hlmatrixControlEntries it deems appropriate. (i.e., either
nlMatrixDSHighCapacityEntries associated with a
hlMatrixControlEntry will be created, or none of them
be.)"
INDEX { hlMatrixControlIndex, nlMatrixDSTimeMark
protocolDirLocalIndex
nlMatrixDSDestAddress, nlMatrixDSSourceAddress }
::= { nlMatrixDSHighCapacityTable 1 }
NlMatrixDSHighCapacityEntry ::= SEQUENCE {
nlMatrixDSHighCapacityOverflowPkts ZeroBasedCounter32,
nlMatrixDSHighCapacityPkts ZeroBasedCounter64,
nlMatrixDSHighCapacityOverflowOctets ZeroBasedCounter32,
nlMatrixDSHighCapacityOctets ZeroBasedCounter64
nlMatrixDSHighCapacityOverflowPkts OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Packets
MAX-ACCESS read-
Waldbusser Standards Track [Page 42]
RFC 3273 Remote Network Monitoring Management July 2002
STATUS
"The number of times the associated
counter has overflowed."
::= { nlMatrixDSHighCapacityEntry 1 }
nlMatrixDSHighCapacityPkts OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets without errors transmitted from
source address to the destination address since this entry
added to the nlMatrixDSHighCapacityTable. Note that this
the number of link-layer packets, so if a single network-
packet is fragmented into several link-layer frames,
counter is incremented several times."
::= { nlMatrixDSHighCapacityEntry 2 }
nlMatrixDSHighCapacityOverflowOctets OBJECT-
SYNTAX ZeroBasedCounter32
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of times the associated
counter has overflowed."
::= { nlMatrixDSHighCapacityEntry 3 }
nlMatrixDSHighCapacityOctets OBJECT-
SYNTAX ZeroBasedCounter64
UNITS "Octets
MAX-ACCESS read-
STATUS
"The number of octets transmitted from the source
to the destination address since this entry was added to
nlMatrixDSHighCapacityTable (excluding framing bits
including FCS octets), excluding those octets in packets
contained errors
Note this doesn't count just those octets in the
protocol frames, but includes the entire packet that
the protocol."
::= { nlMatrixDSHighCapacityEntry 4 }
-- High Capacity extensions for the
Waldbusser Standards Track [Page 43]
RFC 3273 Remote Network Monitoring Management July 2002
nlMatrixTopNHighCapacityTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
nlMatrixTopNTable when nlMatrixTopNControlRateBase
a High Capacity TopN Report."
::= { nlMatrix 8 }
nlMatrixTopNHighCapacityEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Contains the High Capacity RMON extensions to the RMON-2
nlMatrixTopNEntry when nlMatrixTopNControlRateBase
a High Capacity TopN Report. These objects will be created
the agent for all nlMatrixTopNEntries associated with
nlMatrixTopNControlEntries have a
that specify a high capacity report."
INDEX { nlMatrixTopNControlIndex, nlMatrixTopNIndex }
::= { nlMatrixTopNHighCapacityTable 1 }
NlMatrixTopNHighCapacityEntry ::= SEQUENCE {
nlMatrixTopNHighCapacityProtocolDirLocalIndex Integer32,
nlMatrixTopNHighCapacitySourceAddress OCTET STRING
nlMatrixTopNHighCapacityDestAddress OCTET STRING
nlMatrixTopNHighCapacityBasePktRate Gauge32,
nlMatrixTopNHighCapacityOverflowPktRate Gauge32,
nlMatrixTopNHighCapacityPktRate CounterBasedGauge64,
nlMatrixTopNHighCapacityReverseBasePktRate Gauge32,
nlMatrixTopNHighCapacityReverseOverflowPktRate Gauge32,
nlMatrixTopNHighCapacityReversePktRate CounterBasedGauge64,
nlMatrixTopNHighCapacityBaseOctetRate Gauge32,
nlMatrixTopNHighCapacityOverflowOctetRate Gauge32,
nlMatrixTopNHighCapacityOctetRate CounterBasedGauge64,
nlMatrixTopNHighCapacityReverseBaseOctetRate Gauge32,
nlMatrixTopNHighCapacityReverseOverflowOctetRate Gauge32,
nlMatrixTopNHighCapacityReverseOctetRate CounterBasedGauge64
nlMatrixTopNHighCapacityProtocolDirLocalIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"The protocolDirLocalIndex of the network layer protocol
Waldbusser Standards Track [Page 44]
RFC 3273 Remote Network Monitoring Management July 2002
this entry's network address."
::= { nlMatrixTopNHighCapacityEntry 1 }
nlMatrixTopNHighCapacitySourceAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The network layer address of the source host in
conversation
This is represented as an octet string
specific semantics and length as
by the associated nlMatrixTopNProtocolDirLocalIndex
For example, if the protocolDirLocalIndex indicates
encapsulation of ip, this object is encoded as a
octet of 4, followed by the 4 octets of the ip address
in network byte order."
::= { nlMatrixTopNHighCapacityEntry 2 }
nlMatrixTopNHighCapacityDestAddress OBJECT-
SYNTAX OCTET
MAX-ACCESS read-
STATUS
"The network layer address of the destination host in
conversation
This is represented as an octet string
specific semantics and length as
by the associated nlMatrixTopNProtocolDirLocalIndex
For example, if the
indicates an encapsulation of ip, this object is encoded as
length octet of 4, followed by the 4 octets of the ip address
in network byte order."
::= { nlMatrixTopNHighCapacityEntry 3 }
nlMatrixTopNHighCapacityBasePktRate OBJECT-
SYNTAX Gauge32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets seen from the source
to the destination host during this sampling interval
modulo 2^32, counted using the rules for counting
Waldbusser Standards Track [Page 45]
RFC 3273 Remote Network Monitoring Management July 2002
nlMatrixSDPkts object."
::= { nlMatrixTopNHighCapacityEntry 4 }
nlMatrixTopNHighCapacityOverflowPktRate OBJECT-
SYNTAX Gauge32
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets seen from the source
to the destination host during this sampling interval
divided by 2^32, truncating fractions (i.e., X DIV 2^32),
and counted using the rules for counting
nlMatrixSDPkts object."
::= { nlMatrixTopNHighCapacityEntry 5 }
nlMatrixTopNHighCapacityPktRate OBJECT-
SYNTAX CounterBasedGauge64
UNITS "Packets
MAX-ACCESS read-
STATUS
"The number of packets seen from the source host to
destination host during this sampling 