RMON2-MIB (1.3.6.1.2.1.16)

A list of interface entries.  The number of
entries is given by the value of ifNumber.

An interface entry containing objects at the
subnetwork layer and below for a particular
interface.

A unique value for each interface.  Its value
ranges between 1 and the value of ifNumber.  The
value for each interface must remain constant at
least from one re-initialization of the entity's
network management system to the next re-
initialization.

A list of Ethernet statistics entries.

A collection of statistics kept for a particular
Ethernet interface.  As an example, an instance of the
etherStatsPkts object might be named etherStatsPkts.1

A list of Mac-Layer Token Ring statistics
entries.

A collection of Mac-Layer statistics kept for a
particular Token Ring interface.

A list of promiscuous Token Ring statistics
entries.

A collection of promiscuous statistics kept for
non-MAC packets on a particular Token Ring
interface.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last
activated. This can be used by the management station to
ensure that the table has not been deleted and recreated
between polls.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last activated.
This can be used by the management station to ensure that the
table has not been deleted and recreated between polls.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last activated.
This can be used by the management station to ensure that the
table has not been deleted and recreated between polls.

A list of history control entries.

A list of parameters that set up a periodic sampling of
statistics.  As an example, an instance of the
historyControlInterval object might be named
historyControlInterval.2

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

A list of host table control entries.

A list of parameters that set up the discovery of hosts
on a particular interface and the collection of statistics
about these hosts.  For example, an instance of the
hostControlTableSize object might be named
hostControlTableSize.1

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last
activated. This can be used by the management station to
ensure that the table has not been deleted and recreated
between polls.

A list of information entries for the
traffic matrix on each interface.

Information about a traffic matrix on a particular


interface.  For example, an instance of the
matrixControlLastDeleteTime object might be named
matrixControlLastDeleteTime.1

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last
activated. This can be used by the management station to
ensure that the table has not been deleted and recreated
between polls.

A list of packet filter entries.

A set of parameters for a packet filter applied on a
particular interface.  As an example, an instance of the
filterPktData object might be named filterPktData.12

A list of packet channel entries.

A set of parameters for a packet channel applied on a
particular interface.  As an example, an instance of the
channelMatches object might be named channelMatches.3

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last
activated. This can be used by the management station to
ensure that the table has not been deleted and recreated
between polls.

Provides a variable-length packet filter feature to the
RMON-1 filter table.

Provides a variable-length packet filter feature to the
RMON-1 filter table.

When this object is set to a non-zero value, the filter that
it is associated with performs the following operations on
every packet:

1) - If the packet doesn't match the protocol directory entry
     identified by this object, discard the packet and exit
     (i.e., discard the packet if it is not of the identified
     protocol).
2) - If the associated filterProtocolDirLocalIndex is non-zero
     and the packet doesn't match the protocol directory
     entry identified by that object, discard the packet and
     exit
3) - If the packet matches, perform the regular filter
     algorithm as if the beginning of this named protocol is
     the beginning of the packet, potentially applying the
     filterOffset value to move further into the packet.

When this object is set to a non-zero value, the filter that
it is associated with will discard the packet if the packet
doesn't match this protocol directory entry.

A list of ringStation table control entries.

A list of parameters that set up the discovery of
stations on a particular interface and the
collection of statistics about these stations.

A list of source routing statistics entries.

A collection of source routing statistics kept
for a particular Token Ring interface.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last activated.
This can be used by the management station to ensure that the
table has not been deleted and recreated between polls.

Contains the RMON-2 augmentations to RMON-1.

Contains the RMON-2 augmentations to RMON-1.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last activated.
This can be used by the management station to ensure that the
table has not been deleted and recreated between polls.

The value of sysUpTime at the time the protocol directory
was last modified, either through insertions or deletions,
or through modifications of either the
protocolDirAddressMapConfig, protocolDirHostConfig, or
protocolDirMatrixConfig.

This table lists the protocols that this agent has the
capability to decode and count.  There is one entry in this
table for each such protocol.  These protocols represent
different network layer, transport layer, and higher-layer
protocols.  The agent should boot up with this table
preconfigured with those protocols that it knows about and
wishes to monitor.  Implementations are strongly encouraged to
support protocols higher than the network layer (at least for
the protocol distribution group), even for implementations
that don't support the application layer groups.

A conceptual row in the protocolDirTable.

An example of the indexing of this entry is
protocolDirLocalIndex.8.0.0.0.1.0.0.8.0.2.0.0, which is the
encoding of a length of 8, followed by 8 subids encoding the
protocolDirID of 1.2048, followed by a length of 2 and the
2 subids encoding zero-valued parameters.

A unique identifier for a particular protocol.  Standard
identifiers will be defined in a manner such that they
can often be used as specifications for new protocols - i.e.
a tree-structured assignment mechanism that matches the
protocol encapsulation `tree' and which has algorithmic
assignment mechanisms for certain subtrees. See RFC XXX for
more details.

Despite the algorithmic mechanism, the probe will only place
entries in here for those protocols it chooses to collect.  In
other words, it need not populate this table with all of the
possible ethernet protocol types, nor need it create them on
the fly when it sees them.  Whether or not it does these
things is a matter of product definition (cost/benefit,
usability), and is up to the designer of the product.

If an entry is written to this table with a protocolDirID that
the agent doesn't understand, either directly or
algorithmically, the SET request will be rejected with an
inconsistentName or badValue (for SNMPv1) error.

A set of parameters for the associated protocolDirID.
See the associated RMON2 Protocol Identifiers document
for a description of the possible parameters. There
will be one octet in this string for each sub-identifier in
the protocolDirID, and the parameters will appear here in the
same order as the associated sub-identifiers appear in the
protocolDirID.

Every node in the protocolDirID tree has a different, optional
set of parameters defined (that is, the definition of
parameters for a node is optional).  The proper parameter
value for each node is included in this string.  Note that the
inclusion of a parameter value in this string for each node is
not optional - what is optional is that a node may have no
parameters defined, in which case the parameter field for that
node will be zero.

The locally arbitrary, but unique identifier associated
with this protocolDir entry.

The value for each supported protocol must remain constant at
least from one re-initialization of the entity's network
management system to the next re-initialization, except that
if a protocol is deleted and re-created, it must be re-created
with a new value that has not been used since the last
re-initialization.

The specific value is meaningful only within a given SNMP
entity. A protocolDirLocalIndex must not be re-used until the
next agent-restart in the event the protocol directory entry
is deleted.

A textual description of the protocol encapsulation.
A probe may choose to describe only a subset of the
entire encapsulation (e.g. only the highest layer).

This object is intended for human consumption only.

This object may not be modified if the associated
protocolDirStatus object is equal to active(1).

This object describes 2 attributes of this protocol
directory entry.

The presence or absence of the `extensible' bit describes
whether or not this protocol directory entry can be extended
by the user by creating protocol directory entries which are
children of this protocol.

An example of an entry that will often allow extensibility is
`ip.udp'.  The probe may automatically populate some children
of this node such as `ip.udp.snmp' and `ip.udp.dns'.
A probe administrator or user may also populate additional
children via remote SNMP requests that create entries in this
table.  When a child node is added for a protocol for which the
probe has no built in support, extending a parent node (for
which the probe does have built in support),
that child node is not extendible.  This is termed `limited
extensibility'.

When a child node is added through this extensibility
mechanism, the values of protocolDirLocalIndex and
protocolDirType shall be assigned by the agent.

The other objects in the entry will be assigned by the
manager who is creating the new entry.

This object also describes whether or not this agent can
recognize addresses for this protocol, should it be a network
level protocol.  That is, while a probe may be able to
recognize packets of a particular network layer protocol and
count them, it takes additional logic to be able to recognize
the addresses in this protocol and to populate network layer
or application layer tables with the addresses in this
protocol.  If this bit is set, the agent will recognize
network layer addresses for this protoocl and populate the
network and application layer host and matrix tables with
these protocols.

Note that when an entry is created, the agent will supply
values for the bits that match the capabilities of the agent
with respect to this protocol.  Note that since row creations
usually exercise the limited extensibility feature, these
bits will usually be set to zero.

This object describes and configures the probe's support for
address mapping for this protocol.  When the probe creates
entries in this table for all protocols that it understands,
it will set the entry to notSupported(1) if it doesn't have
the capability to perform address mapping for the protocol or
if this protocol is not a network-layer protocol.  When
an entry is created in this table by a management operation as
part of the limited extensibility feature, the probe must set
this value to notSupported(1), because limited extensibility
of the protocolDirTable does not extend to interpreting
addresses of the extended protocols.

If the value of this object is notSupported(1), the probe
will not perform address mapping for this protocol and
shall not allow this object to be changed to any other value.
If the value of this object is supportedOn(3), the probe
supports address mapping for this protocol and is configured
to perform address mapping for this protocol for all
addressMappingControlEntries and all interfaces.
If the value of this object is supportedOff(2), the probe
supports address mapping for this protocol but is configured
to not perform address mapping for this protocol for any
addressMappingControlEntries and all interfaces.
Whenever this value changes from supportedOn(3) to
supportedOff(2), the probe shall delete all related entries in
the addressMappingTable.

This object describes and configures the probe's support for
the network layer and application layer host tables for this
protocol.  When the probe creates entries in this table for
all protocols that it understands, it will set the entry to
notSupported(1) if it doesn't have the capability to track the
nlHostTable for this protocol or if the alHostTable is
implemented but doesn't have the capability to track this
protocol.  Note that if the alHostTable is implemented, the
probe may only support a protocol if it is supported in both
the nlHostTable and the alHostTable.

If the associated protocolDirType object has the
addressRecognitionCapable bit set, then this is a network
layer protocol for which the probe recognizes addresses, and
thus the probe will populate the nlHostTable and alHostTable
with addresses it discovers for this protocol.

If the value of this object is notSupported(1), the probe
will not track the nlHostTable or alHostTable for this
protocol and shall not allow this object to be changed to any
other value. If the value of this object is supportedOn(3),
the probe supports tracking of the nlHostTable and alHostTable
for this protocol and is configured to track both tables
for this protocol for all control entries and all interfaces.
If the value of this object is supportedOff(2), the probe
supports tracking of the nlHostTable and alHostTable for this
protocol but is configured to not track these tables
for any control entries or interfaces.
Whenever this value changes from supportedOn(3) to
supportedOff(2), the probe shall delete all related entries in
the nlHostTable and alHostTable.

Note that since each alHostEntry references 2 protocol
directory entries, one for the network address and one for the
type of the highest protocol recognized, that an entry will
only be created in that table if this value is supportedOn(3)
for both protocols.

This object describes and configures the probe's support for
the network layer and application layer matrix tables for this
protocol.  When the probe creates entries in this table for
all protocols that it understands, it will set the entry to
notSupported(1) if it doesn't have the capability to track the
nlMatrixTables for this protocol or if the alMatrixTables are
implemented but don't have the capability to track this
protocol.  Note that if the alMatrix tables are implemented,
the probe may only support a protocol if it is supported in
the the both of the nlMatrixTables and both of the
alMatrixTables.

If the associated protocolDirType object has the
addressRecognitionCapable bit set, then this is a network
layer protocol for which the probe recognizes addresses, and
thus the probe will populate both of the nlMatrixTables and
both of the alMatrixTables with addresses it discovers for
this protocol.

If the value of this object is notSupported(1), the probe
will not track either of the nlMatrixTables or the
alMatrixTables for this protocol and shall not allow this
object to be changed to any other value. If the value of this
object is supportedOn(3), the probe supports tracking of both
of the nlMatrixTables and (if implemented) both of the
alMatrixTables for this protocol and is configured to track
these tables for this protocol for all control entries and all
interfaces. If the value of this object is supportedOff(2),
the probe supports tracking of both of the nlMatrixTables and
(if implemented) both of the alMatrixTables for this protocol
but is configured to not track these tables for this
protocol for any control entries or interfaces.
Whenever this value changes from supportedOn(3) to
supportedOff(2), the probe shall delete all related entries in
the nlMatrixTables and the alMatrixTables.

Note that since each alMatrixEntry references 2 protocol
directory entries, one for the network address and one for the
type of the highest protocol recognized, that an entry will
only be created in that table if this value is supportedOn(3)
for both protocols.

The entity that configured this entry and is
therefore using the resources assigned to it.

The status of this protocol directory entry.

An entry may not exist in the active state unless all
objects in the entry have an appropriate value.

If this object is not equal to active(1), all associated
entries in the nlHostTable, nlMatrixSDTable, nlMatrixDSTable,
alHostTable, alMatrixSDTable, and alMatrixDSTable shall be
deleted.

Controls the setup of protocol type distribution statistics
tables.

Implementations are encouraged to add an entry per monitored
interface upon initialization so that a default collection
of protocol statistics is available.

Rationale:
This table controls collection of very basic statistics
for any or all of the protocols detected on a given interface.
An NMS can use this table to quickly determine bandwidth
allocation utilized by different protocols.

A media-specific statistics collection could also
be configured (e.g. etherStats, trPStats) to easily obtain
total frame, octet, and droppedEvents for the same
interface.

A conceptual row in the protocolDistControlTable.

An example of the indexing of this entry is
protocolDistControlDroppedFrames.7

A unique index for this protocolDistControlEntry.

The source of data for the this protocol distribution.

The statistics in this group reflect all packets
on the local network segment attached to the
identified interface.

This object may not be modified if the associated
protocolDistControlStatus object is equal to active(1).

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The value of sysUpTime when this control entry was last
activated. This can be used by the management station to
ensure that the table has not been deleted and recreated
between polls.

The entity that configured this entry and is
therefore using the resources assigned to it.

The status of this row.

An entry may not exist in the active state unless all
objects in the entry have an appropriate value.

If this object is not equal to active(1), all associated
entries in the protocolDistStatsTable shall be deleted.

An entry is made in this table for every protocol in the
protocolDirTable which has been seen in at least one packet.
Counters are updated in this table for every protocol type
that is encountered when parsing a packet, but no counters are
updated for packets with MAC-layer errors.

Note that if a protocolDirEntry is deleted, all associated
entries in this table are removed.

A conceptual row in the protocolDistStatsTable.

The index is composed of the protocolDistControlIndex of the
associated protocolDistControlEntry followed by the
protocolDirLocalIndex of the associated protocol that this
entry represents.  In other words, the index identifies the
protocol distribution an entry is a part of as well as the
particular protocol that it represents.

An example of the indexing of this entry is
protocolDistStatsPkts.1.18

The number of packets without errors received of this
protocol type.  Note that this is the number of link-layer
packets, so if a single network-layer packet is fragmented
into several link-layer frames, this counter is incremented
several times.

The number of octets in packets received of this protocol
type since it was added to the protocolDistStatsTable
(excluding framing bits but including FCS octets), except for
those octets in packets that contained errors.

Note this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained
the protocol.

The number of times an address mapping entry has been
inserted into the addressMapTable.  If an entry is inserted,
then deleted, and then inserted, this counter will be
incremented by 2.

Note that the table size can be determined by subtracting
addressMapDeletes from addressMapInserts.

The number of times an address mapping entry has been
deleted from the addressMapTable (for any reason).  If
an entry is deleted, then inserted, and then deleted, this
counter will be incremented by 2.

Note that the table size can be determined by subtracting
addressMapDeletes from addressMapInserts.

The maximum number of entries that are desired in the
addressMapTable. The probe will not create more than
this number of entries in the table, but may choose to create
fewer entries in this table for any reason including the lack
of resources.

If this object is set to a value less than the current number
of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object.

If this value is set to -1, the probe may create any number
of entries in this table.

This object may be used to control how resources are allocated
on the probe for the various RMON functions.

A table to control the collection of network layer address to
physical address to interface mappings.

Note that this is not like the typical RMON
controlTable and dataTable in which each entry creates
its own data table.  Each entry in this table enables the
discovery of addresses on a new interface and the placement
of address mappings into the central addressMapTable.

Implementations are encouraged to add an entry per monitored
interface upon initialization so that a default collection
of address mappings is available.

A conceptual row in the addressMapControlTable.
An example of the indexing of this entry is
addressMapControlDroppedFrames.1

A unique index for this entry in the addressMapControlTable.

The source of data for this addressMapControlEntry.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The entity that configured this entry and is
therefore using the resources assigned to it.

The status of this addressMap control entry.

An entry may not exist in the active state unless all
objects in the entry have an appropriate value.

If this object is not equal to active(1), all associated
entries in the addressMapTable shall be deleted.

A table of network layer address to physical address to
interface mappings.

The probe will add entries to this table based on the source
MAC and network addresses seen in packets without MAC-level
errors. The probe will populate this table for all protocols
in the protocol directory table whose value of
protocolDirAddressMapConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or
has a protocolDirAddressMapConfig value of supportedOff(2).

A conceptual row in the addressMapTable.
The protocolDirLocalIndex in the index identifies the network
layer protocol of the addressMapNetworkAddress.
An example of the indexing of this entry is
addressMapSource.783495.18.4.128.2.6.6.11.1.3.6.1.2.1.2.2.1.1.1

A TimeFilter for this entry.  See the TimeFilter textual
convention to see how this works.

The network address for this relation.

This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the
index.

For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order.

The interface or port on which the associated network
address was most recently seen.

If this address mapping was discovered on an interface, this
object shall identify the instance of the ifIndex
object, defined in [3,5], for the desired interface.
For example, if an entry were to receive data from
interface #1, this object would be set to ifIndex.1.

If this address mapping was discovered on a port, this
object shall identify the instance of the rptrGroupPortIndex
object, defined in [RFC1516], for the desired port.
For example, if an entry were to receive data from
group #1, port #1, this object would be set to
rptrGroupPortIndex.1.1.

Note that while the dataSource associated with this entry
may only point to index objects, this object may at times
point to repeater port objects. This situation occurs when
the dataSource points to an interface which is a locally
attached repeater and the agent has additional information
about the source port of traffic seen on that repeater.

The last source physical address on which the associated
network address was seen.  If the protocol of the associated
network address was encapsulated inside of a network-level or
higher protocol, this will be the address of the next-lower
protocol with the addressRecognitionCapable bit enabled and
will be formatted as specified for that protocol.

The value of sysUpTime at the time this entry was last
created or the values of the physical address changed.

This can be used to help detect duplicate address problems, in
which case this object will be updated frequently.

A list of higher layer (i.e. non-MAC) host table control entries.

These entries will enable the collection of the network and
application level host tables indexed by network addresses.
Both the network and application level host tables are
controlled by this table is so that they will both be created
and deleted at the same time, further increasing the ease with
which they can be implemented as a single datastore (note that
if an implementation stores application layer host records in
memory, it can derive network layer host records from them).

Entries in the nlHostTable will be created on behalf of each
entry in this table. Additionally, if this probe implements
the alHostTable, entries in the alHostTable will be created on
behalf of each entry in this table.

Implementations are encouraged to add an entry per monitored
interface upon initialization so that a default collection
of host statistics is available.

A conceptual row in the hlHostControlTable.

An example of the indexing of this entry is
hlHostControlNlDroppedFrames.1

An index that uniquely identifies an entry in the
hlHostControlTable.  Each such entry defines
a function that discovers hosts on a particular
interface and places statistics about them in the
nlHostTable, and optionally in the alHostTable, on
behalf of this hlHostControlEntry.

The source of data for the associated host tables.

The statistics in this group reflect all packets
on the local network segment attached to the
identified interface.

This object may not be modified if the associated
hlHostControlStatus object is equal to active(1).

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for the associated
nlHost entries for whatever reason.  Most often, this event
occurs when the probe is out of some resources and decides to
shed load from this collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that if the nlHostTable is inactive because no protocols
are enabled in the protocol directory, this value should be 0.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The number of times an nlHost entry has been
inserted into the nlHost table.  If an entry is inserted, then
deleted, and then inserted, this counter will be incremented
by 2.

To allow for efficient implementation strategies, agents may
delay updating this object for short periods of time.  For
example, an implementation strategy may allow internal
data structures to differ from those visible via SNMP for
short periods of time.  This counter may reflect the internal
data structures for those short periods of time.

Note that the table size can be determined by subtracting
hlHostControlNlDeletes from hlHostControlNlInserts.

The number of times an nlHost entry has been
deleted from the nlHost table (for any reason).  If an entry
is deleted, then inserted, and then deleted, this counter will
be incremented by 2.

To allow for efficient implementation strategies, agents may
delay updating this object for short periods of time.  For
example, an implementation strategy may allow internal
data structures to differ from those visible via SNMP for
short periods of time.  This counter may reflect the internal
data structures for those short periods of time.

Note that the table size can be determined by subtracting
hlHostControlNlDeletes from hlHostControlNlInserts.

The maximum number of entries that are desired in the
nlHostTable on behalf of this control entry. The probe will
not create more than this number of associated entries in the
table, but may choose to create fewer entries in this table
for any reason including the lack of resources.

If this object is set to a value less than the current number
of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object.

If this value is set to -1, the probe may create any number
of entries in this table.  If the associated
hlHostControlStatus object is equal to `active', this
object may not be modified.

This object may be used to control how resources are allocated
on the probe for the various RMON functions.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for the associated
alHost entries for whatever reason.  Most often, this event
occurs when the probe is out of some resources and decides to
shed load from this collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that if the alHostTable is not implemented or is inactive
because no protocols are enabled in the protocol directory,
this value should be 0.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The number of times an alHost entry has been
inserted into the alHost table.  If an entry is inserted, then
deleted, and then inserted, this counter will be incremented
by 2.

To allow for efficient implementation strategies, agents may
delay updating this object for short periods of time.  For
example, an implementation strategy may allow internal
data structures to differ from those visible via SNMP for
short periods of time.  This counter may reflect the internal
data structures for those short periods of time.

Note that the table size can be determined by subtracting
hlHostControlAlDeletes from hlHostControlAlInserts.

The number of times an alHost entry has been
deleted from the alHost table (for any reason).  If an entry
is deleted, then inserted, and then deleted, this counter will
be incremented by 2.

To allow for efficient implementation strategies, agents may
delay updating this object for short periods of time.  For
example, an implementation strategy may allow internal
data structures to differ from those visible via SNMP for
short periods of time.  This counter may reflect the internal
data structures for those short periods of time.

Note that the table size can be determined by subtracting
hlHostControlAlDeletes from hlHostControlAlInserts.

The maximum number of entries that are desired in the alHost
table on behalf of this control entry. The probe will not
create more than this number of associated entries in the
table, but may choose to create fewer entries in this table
for any reason including the lack of resources.

If this object is set to a value less than the current number
of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object.

If this value is set to -1, the probe may create any number
of entries in this table.  If the associated
hlHostControlStatus object is equal to `active', this
object may not be modified.

This object may be used to control how resources are allocated
on the probe for the various RMON functions.

The entity that configured this entry and is
therefore using the resources assigned to it.

The status of this hlHostControlEntry.

An entry may not exist in the active state unless all
objects in the entry have an appropriate value.

If this object is not equal to active(1), all associated
entries in the nlHostTable and alHostTable shall be deleted.

A collection of statistics for a particular network layer
address that has been discovered on an interface of this
device.

The probe will populate this table for all network layer
protocols in the protocol directory table whose value of
protocolDirHostConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or
has a protocolDirHostConfig value of supportedOff(2).

The probe will add to this table all addresses seen
as the source or destination address in all packets with no
MAC errors, and will increment octet and packet counts in the
table for all packets with no MAC errors.

A conceptual row in the nlHostTable.

The hlHostControlIndex value in the index identifies the
hlHostControlEntry on whose behalf this entry was created.
The protocolDirLocalIndex value in the index identifies the
network layer protocol of the nlHostAddress.

An example of the indexing of this entry is
nlHostOutPkts.1.783495.18.4.128.2.6.6.

A TimeFilter for this entry.  See the TimeFilter textual
convention to see how this works.

The network address for this nlHostEntry.

This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.

For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order.

The number of packets without errors transmitted to
this address since it was added to the nlHostTable.  Note that
this is the number of link-layer packets, so if a single
network-layer packet is fragmented into several link-layer
frames, this counter is incremented several times.

The number of packets without errors transmitted by
this address since it was added to the nlHostTable.  Note that
this is the number of link-layer packets, so if a single
network-layer packet is fragmented into several link-layer
frames, this counter is incremented several times.

The number of octets transmitted to this address
since it was added to the nlHostTable (excluding
framing bits but including FCS octets), excluding
those octets in packets that contained errors.

Note this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained
the protocol.

The number of octets transmitted by this address
since it was added to the nlHostTable (excluding
framing bits but including FCS octets), excluding
those octets in packets that contained errors.

Note this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained
the protocol.

The number of packets without errors transmitted by this
address that were directed to any MAC broadcast addresses
or to any MAC multicast addresses since this host was
added to the nlHostTable. Note that this is the number of
link-layer packets, so if a single network-layer packet is
fragmented into several link-layer frames, this counter is
incremented several times.

The value of sysUpTime when this entry was last activated.
This can be used by the management station to ensure that the
entry has not been deleted and recreated between polls.

A list of higher layer (i.e. non-MAC) matrix control entries.

These entries will enable the collection of the network and
application level matrix tables containing conversation
statistics indexed by pairs of network addresses.
Both the network and application level matrix tables are
controlled by this table is so that they will both be created
and deleted at the same time, further increasing the ease with
which they can be implemented as a single datastore (note that
if an implementation stores application layer matrix records
in memory, it can derive network layer matrix records from
them).

Entries in the nlMatrixSDTable and nlMatrixDSTable will be
created on behalf of each entry in this table.  Additionally,
if this probe implements the alMatrix tables, entries in the
alMatrix tables will be created on behalf of each entry in
this table.

A conceptual row in the hlMatrixControlTable.

An example of indexing of this entry is
hlMatrixControlNlDroppedFrames.1

An index that uniquely identifies an entry in the
hlMatrixControlTable.  Each such entry defines
a function that discovers conversations on a particular
interface and places statistics about them in the
nlMatrixSDTable and the nlMatrixDSTable, and optionally the
alMatrixSDTable and alMatrixDSTable, on behalf of this
hlMatrixControlEntry.

The source of the data for the associated matrix tables.

The statistics in this group reflect all packets
on the local network segment attached to the
identified interface.

This object may not be modified if the associated
hlMatrixControlStatus object is equal to active(1).

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that if the nlMatrixTables are inactive because no
protocols are enabled in the protocol directory, this value
should be 0.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The number of times an nlMatrix entry has been
inserted into the nlMatrix tables.  If an entry is inserted,
then deleted, and then inserted, this counter will be
incremented by 2.  The addition of a conversation into both
the nlMatrixSDTable and nlMatrixDSTable shall be counted as
two insertions (even though every addition into one table must
be accompanied by an insertion into the other).

To allow for efficient implementation strategies, agents may
delay updating this object for short periods of time.  For
example, an implementation strategy may allow internal
data structures to differ from those visible via SNMP for
short periods of time.  This counter may reflect the internal
data structures for those short periods of time.

Note that the sum of then nlMatrixSDTable and nlMatrixDSTable
sizes can be determined by subtracting
hlMatrixControlNlDeletes from hlMatrixControlNlInserts.

The number of times an nlMatrix entry has been
deleted from the nlMatrix tables (for any reason).  If an
entry is deleted, then inserted, and then deleted, this
counter will be incremented by 2.  The deletion of a
conversation from both the nlMatrixSDTable and nlMatrixDSTable
shall be counted as two deletions (even though every deletion
from one table must be accompanied by a deletion from the
other).

To allow for efficient implementation strategies, agents may
delay updating this object for short periods of time.  For
example, an implementation strategy may allow internal
data structures to differ from those visible via SNMP for
short periods of time.  This counter may reflect the internal
data structures for those short periods of time.

Note that the table size can be determined by subtracting
hlMatrixControlNlDeletes from hlMatrixControlNlInserts.

The maximum number of entries that are desired in the
nlMatrix tables on behalf of this control entry. The probe
will not create more than this number of associated entries in
the table, but may choose to create fewer entries in this
table for any reason including the lack of resources.

If this object is set to a value less than the current number
of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object.

If this value is set to -1, the probe may create any number
of entries in this table.  If the associated
hlMatrixControlStatus object is equal to `active', this
object may not be modified.

This object may be used to control how resources are allocated
on the probe for the various RMON functions.

The total number of frames which were received by the probe
and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for
whatever reason.  Most often, this event occurs when the probe
is out of some resources and decides to shed load from this
collection.

This count does not include packets that were not counted
because they had MAC-layer errors.

Note that if the alMatrixTables are not implemented or are
inactive because no protocols are enabled in the protocol
directory, this value should be 0.

Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped.

The number of times an alMatrix entry has been
inserted into the alMatrix tables.  If an entry is inserted,
then deleted, and then inserted, this counter will be
incremented by 2.  The addition of a conversation into both
the alMatrixSDTable and alMatrixDSTable shall be counted as
two insertions (even though every addition into one table must
be accompanied by an insertion into the other).

To allow for efficient implementation strategies, agents may
delay updating this object for short periods of time.  For
example, an implementation strategy may allow internal
data structures to differ from those visible via SNMP for
short periods of time.  This counter may reflect the internal
data structures for those short periods of time.

Note that the table size can be determined by subtracting
hlMatrixControlAlDeletes from hlMatrixControlAlInserts.

The number of times an alMatrix entry has been
deleted from the alMatrix tables.  If an entry is deleted,
then inserted, and then deleted, this counter will be
incremented by 2.  The deletion of a conversation from both
the alMatrixSDTable and alMatrixDSTable shall be counted as
two deletions (even though every deletion from one table must
be accompanied by a deletion from the other).

To allow for efficient implementation strategies, agents may
delay updating this object for short periods of time.  For
example, an implementation strategy may allow internal
data structures to differ from those visible via SNMP for
short periods of time.  This counter may reflect the internal
data structures for those short periods of time.

Note that the table size can be determined by subtracting
hlMatrixControlAlDeletes from hlMatrixControlAlInserts.

The maximum number of entries that are desired in the
alMatrix tables on behalf of this control entry. The probe
will not create more than this number of associated entries in
the table, but may choose to create fewer entries in this
table for any reason including the lack of resources.

If this object is set to a value less than the current number
of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object.

If this value is set to -1, the probe may create any number
of entries in this table.  If the associated
hlMatrixControlStatus object is equal to `active', this
object may not be modified.

This object may be used to control how resources are allocated
on the probe for the various RMON functions.

The entity that configured this entry and is
therefore using the resources assigned to it.

The status of this hlMatrixControlEntry.

An entry may not exist in the active state unless all
objects in the entry have an appropriate value.

If this object is not equal to active(1), all
associated entries in the nlMatrixSDTable,
nlMatrixDSTable, alMatrixSDTable, and the alMatrixDSTable
shall be deleted by the agent.

A list of traffic matrix entries which collect statistics for
conversations between two network-level addresses.  This table
is indexed first by the source address and then by the
destination address to make it convenient to collect all
conversations from a particular address.

The probe will populate this table for all network layer
protocols in the protocol directory table whose value of
protocolDirMatrixConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or
has a protocolDirMatrixConfig value of supportedOff(2).

The probe will add to this table all pairs of addresses
seen in all packets with no MAC errors, and will increment
octet and packet counts in the table for all packets with no
MAC errors.

Further, this table will only contain entries that have a
corresponding entry in the nlMatrixDSTable with the same
source address and destination address.

A conceptual row in the nlMatrixSDTable.

The hlMatrixControlIndex value in the index identifies the
hlMatrixControlEntry on whose behalf this entry was created.
The protocolDirLocalIndex value in the index identifies the
network layer protocol of the nlMatrixSDSourceAddress and
nlMatrixSDDestAddress.

An example of the indexing of this table is
nlMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7

A TimeFilter for this entry.  See the TimeFilter textual
convention to see how this works.

The network source address for this nlMatrixSDEntry.

This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.

For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order.

The network destination address for this
nlMatrixSDEntry.

This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.

For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order.

The number of packets without errors transmitted from the
source address to the destination address since this entry was
added to the nlMatrixSDTable.  Note that this is the number of
link-layer packets, so if a single network-layer packet is
fragmented into several link-layer frames, this counter is
incremented several times.

The number of octets transmitted from the source address to
the destination address since this entry was added to the
nlMatrixSDTable (excluding framing bits but
including FCS octets), excluding those octets in packets that
contained errors.

Note this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained
the protocol.

The value of sysUpTime when this entry was last activated.
This can be used by the management station to ensure that the
entry has not been deleted and recreated between polls.

A list of traffic matrix entries which collect statistics for
conversations between two network-level addresses.  This table
is indexed first by the destination address and then by the
source address to make it convenient to collect all
conversations to a particular address.

The probe will populate this table for all network layer
protocols in the protocol directory table whose value of
protocolDirMatrixConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or
has a protocolDirMatrixConfig value of supportedOff(2).

The probe will add to this table all pairs of addresses
seen in all packets with no MAC errors, and will increment
octet and packet counts in the table for all packets with no
MAC errors.

Further, this table will only contain entries that have a
corresponding entry in the nlMatrixSDTable with the same
source address and destination address.

A conceptual row in the nlMatrixDSTable.

The hlMatrixControlIndex value in the index identifies the
hlMatrixControlEntry on whose behalf this entry was created.
The protocolDirLocalIndex value in the index identifies the
network layer protocol of the nlMatrixDSSourceAddress and
nlMatrixDSDestAddress.

An example of the indexing of this table is
nlMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6

A TimeFilter for this entry.  See the TimeFilter textual
convention to see how this works.

The network source address for this nlMatrixDSEntry.

This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.

For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order.

The network destination address for this
nlMatrixDSEntry.

This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.

For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order.

The number of packets without errors transmitted from the
source address to the destination address since this entry was
added to the nlMatrixDSTable.  Note that this is the number of
link-layer packets, so if a single network-layer packet is
fragmented into several link-layer frames, this counter is
incremented several times.

The number of octets transmitted from the source address
to the destination address since this entry was added to the
nlMatrixDSTable (excluding framing bits but
including FCS octets), excluding those octets in packets that
contained errors.

Note this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained
the protocol.

The value of sysUpTime when this entry was last activated.
This can be used by the management station to ensure that the
entry has not been deleted and recreated between polls.

A set of parameters that control the creation of a
report of the top N matrix entries according to
a selected metric.

A conceptual row in the nlMatrixTopNControlTable.

An example of the indexing of this table is
nlMatrixTopNControlDuration.3

An index that uniquely identifies an entry
in the nlMatrixTopNControlTable.  Each such
entry defines one top N report prepared for
one interface.

The nlMatrix[SD/DS] table for which a top N report will be
prepared on behalf of this entry.  The nlMatrix[SD/DS] table
is identified by the value of the hlMatrixControlIndex
for that table - that value is used here to identify the
particular table.

This object may not be modified if the associated
nlMatrixTopNControlStatus object is equal to active(1).

The variable for each nlMatrix[SD/DS] entry that the
nlMatrixTopNEntries are sorted by.

This object may not be modified if the associated
nlMatrixTopNControlStatus object is equal to active(1).

The number of seconds left in the report currently
being collected.  When this object is modified by
the management station, a new collection is started,
possibly aborting a currently running report.  The
new value is used as the requested duration of this
report, and is immediately loaded into the associated
nlMatrixTopNControlDuration object.
When the report finishes, the probe will automatically
start another collection with the same initial value
of nlMatrixTopNControlTimeRemaining.  Thus the management
station may simply read the resulting reports repeatedly,
checking the startTime and duration each time to ensure that a
report was not missed or that the report parameters were not
changed.

While the value of this object is non-zero, it decrements
by one per second until it reaches zero.  At the time
that this object decrements to zero, the report is made
accessible in the nlMatrixTopNTable, overwriting any report
that may be there.

When this object is modified by the management station, any
associated entries in the nlMatrixTopNTable shall be deleted.

(Note that this is a different algorithm than the one used in
the hostTopNTable).

The number of reports that have been generated by this entry.