draft-ietf-rmonmib-rmon2-v2-05.txt   rfc4502.txt 
Network Working Group S. Waldbusser
Request for Comments: 4502 May 2006
Obsoletes: 2021
Updates: 3273
Category: Standards Track
Remote Network Monitoring Remote Network Monitoring
Management Information Base Management Information Base
Version 2 Version 2
<draft-ietf-rmonmib-rmon2-v2-05.txt>
October 3, 2005
Steven Waldbusser
waldbusser@nextbeacon.com
Status of this Memo
This document is an Internet-Draft and is subject to all
provisions of Section 3 of RFC 3978.
By submitting this Internet-Draft, each author represents
that any applicable patent or other IPR claims of which he
or she is aware have been or will be disclosed, and any of
which he or she becomes aware will be disclosed, in
accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by
other documents at any time. It is inappropriate to use
Internet-Drafts as reference material or to cite them other
than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be Status of This Memo
accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 3, 2006.
Distribution of this document is unlimited. Please send This document specifies an Internet standards track protocol for the
comments to the RMON WG mailing list <rmonmib@ietf.org>. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a portion of the Management This document defines a portion of the Management Information Base
Information Base (MIB) for use with network management (MIB) for use with network management protocols in TCP/IP-based
protocols in TCP/IP-based internets. In particular, it internets. In particular, it defines objects for managing remote
defines objects for managing remote network monitoring network monitoring devices.
devices.
This document obsoletes RFC 2021 and the RMON2-MIB module
contained in this memo obsoletes the RMON2-MIB module at
RFC3273 level.
XXX Note To RFC Editor: This document obsoletes RFC 2021, updates RFC 3273, and contains a
Please replace the module at: new version of the RMON2-MIB module.
ftp://ftp.rfc-editor.org/in-notes/mibs/current.mibs/rmon2.mib
with the RMON2-MIB module in this document
XXX
Table of Contents Table of Contents
1 The Internet-Standard Management Framework ............ 4 1. The Internet-Standard Management Framework ......................2
2 Overview .............................................. 5 2. Overview ........................................................2
2.1 Remote Network Management Goals ..................... 5 2.1. Remote Network Management Goals ............................3
2.2 Structure of MIB .................................... 7 2.2. Structure of MIB ...........................................4
3 Control of Remote Network Monitoring Devices .......... 9 3. Control of Remote Network Monitoring Devices ....................6
3.1 Resource Sharing Among Multiple Management Sta- 3.1. Resource Sharing among Multiple Management Stations ........7
tions .............................................. 9 3.2. Row Addition among Multiple Management Stations ............8
3.2 Row Addition Among Multiple Management Stations ..... 11 4. Conventions .....................................................9
4 Conventions ........................................... 14 5. RMON 2 Conventions .............................................10
5 RMON 2 Conventions .................................... 15 5.1. Usage of the Term Application Level .......................10
5.1 Usage of the term Application Level ................. 15 5.2. Protocol Directory and Limited Extensibility ..............10
5.2 Protocol Directory and Limited Extensibility ........ 15 5.3. Errors in Packets .........................................11
5.3 Errors in packets ................................... 16 6. Definitions ....................................................11
6 Definitions ........................................... 16 7. Security Considerations .......................................130
7 Security Considerations ............................... 149 8. Appendix - TimeFilter Implementation Notes ....................132
8 IANA Considerations ................................... 150 9. Changes since RFC 2021 ........................................138
9 Appendix - TimeFilter Implementation Notes ............ 151 10. Acknowledgements .............................................140
10 Changes since RFC 2021 ............................... 157 11. References ...................................................140
11 Acknowledgments ...................................... 160 11.1. Normative References ....................................140
12 Author's Address ..................................... 160 11.2. Informative References ..................................140
13 References ........................................... 161
13.1 Normative References ............................... 161
13.2 Informative References ............................. 162
14 Full Copyright Statement ............................. 162
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the For a detailed overview of the documents that describe the current
current Internet-Standard Management Framework, please Internet-Standard Management Framework, please refer to section 7 of
refer to section 7 of RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information Managed objects are accessed via a virtual information store, termed
store, termed the Management Information Base or MIB. MIB the Management Information Base or MIB. MIB objects are generally
objects are generally accessed through the Simple Network accessed through the Simple Network Management Protocol (SNMP).
Management Protocol (SNMP). Objects in the MIB are defined Objects in the MIB are defined using the mechanisms defined in the
using the mechanisms defined in the Structure of Management Structure of Management Information (SMI). This memo specifies a MIB
Information (SMI). This memo specifies a MIB module that module that is compliant to the SMIv2, which is described in STD 58,
is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, [RFC2580].
RFC 2580 [RFC2580].
2. Overview 2. Overview
The RMON2 MIB defines objects that provide RMON analysis up to The RMON2 MIB defines objects that provide RMON analysis up to the
the application layer. application layer.
Remote network monitoring devices, often called monitors or Remote network monitoring devices, often called monitors or probes,
probes, are instruments that exist for the purpose of managing are instruments that exist for the purpose of managing a network.
a network. Often these remote probes are stand-alone devices Often, these remote probes are stand-alone devices and devote
and devote significant internal resources for the sole purpose significant internal resources for the sole purpose of managing a
of managing a network. An organization may employ many of network. An organization may employ many of these devices, one per
these devices, one per network segment, to manage its network segment, to manage its internet. In addition, these devices
internet. In addition, these devices may be used for a may be used for a network management service provider to access a
network management service provider to access a client client network, which is often geographically remote.
network, often geographically remote.
The objects defined in this document are intended as an The objects defined in this document are intended to serve as an
interface between an RMON agent and an RMON management interface between an RMON agent and an RMON management application
application and are not intended for direct manipulation by and are not intended for direct manipulation by humans. While some
humans. While some users may tolerate the direct display of users may tolerate the direct display of some of these objects, few
some of these objects, few will tolerate the complexity of will tolerate the complexity of manually manipulating objects to
manually manipulating objects to accomplish row creation. accomplish row creation. The management application should handle
These functions should be handled by the management these functions.
application.
2.1. Remote Network Management Goals 2.1. Remote Network Management Goals
o Offline Operation o Offline Operation
There are sometimes conditions when a management
station will not be in constant contact with its There are times when a management station will not be in constant
remote monitoring devices. This is sometimes by contact with its remote monitoring devices. This sometimes occurs
design in an attempt to lower communications costs by design, in an attempt to lower communications costs (especially
(especially when communicating over a WAN or when communicating over a WAN or dialup link), or by accident, as
dialup link), or by accident as network failures network failures affect the communications between the management
affect the communications between the management
station and the probe. station and the probe.
For this reason, this MIB allows a probe to be For this reason, this MIB allows a probe to be configured to
configured to perform diagnostics and to collect perform diagnostics and to collect statistics continuously, even
statistics continuously, even when communication with when communication with the management station may not be possible
the management station may not be possible or or efficient. The probe may then attempt to notify the management
efficient. The probe may then attempt to notify station when an exceptional condition occurs. Thus, even in
the management station when an exceptional condition circumstances where communication between the management station
occurs. Thus, even in circumstances where and probe is not continuous, fault, performance, and configuration
communication between management station and probe is information may be continuously accumulated and communicated to
not continuous, fault, performance, and configuration the management station conveniently and efficiently.
information may be continuously accumulated and
communicated to the management station conveniently
and efficiently.
o Proactive Monitoring o Proactive Monitoring
Given the resources available on the monitor, it
is potentially helpful for it continuously to run Given the resources available on the monitor, it is potentially
diagnostics and to log network performance. The helpful for it to run diagnostics continuously and to log network
monitor is always available at the onset of any performance. The monitor is always available at the onset of any
failure. It can notify the management station of the failure. It can notify the management station of the failure and
failure and can store historical statistical can store historical statistical information about the failure.
information about the failure. This historical This historical information can be played back by the management
information can be played back by the management station in an attempt to perform further diagnosis of the cause of
station in an attempt to perform further diagnosis the problem.
into the cause of the problem.
o Problem Detection and Reporting o Problem Detection and Reporting
The monitor can be configured to recognize
conditions, most notably error conditions, and The monitor can be configured to recognize conditions, most
continuously to check for them. When one of these notably error conditions, and to check for them continuously.
conditions occurs, the event may be logged, and When one of these conditions occurs, the event may be logged, and
management stations may be notified in a number of management stations may be notified in a number of ways.
ways.
o Value Added Data o Value Added Data
Because a remote monitoring device represents a
network resource dedicated exclusively to network Because a remote monitoring device represents a network resource
management functions, and because it is located dedicated exclusively to network management functions, and because
directly on the monitored portion of the network, the it is located directly on the monitored portion of the network,
remote network monitoring device has the opportunity the remote network monitoring device has the opportunity to add
to add significant value to the data it collects. significant value to the data it collects. For instance, by
For instance, by highlighting those hosts on the highlighting those hosts on the network that generate the most
network that generate the most traffic or errors, the traffic or errors, the probe can give the management station
probe can give the management station precisely the precisely the information it needs to solve a class of problems.
information it needs to solve a class of problems.
o Multiple Managers o Multiple Managers
An organization may have multiple management stations
for different units of the organization, for different An organization may have multiple management stations for
functions (e.g. engineering and operations), and in an different units of the organization, for different functions
attempt to provide disaster recovery. Because (e.g., engineering and operations), and in order to provide
environments with multiple management stations are disaster recovery. Because environments with multiple management
common, the remote network monitoring device has to stations are common, the remote network monitoring device has to
deal with more than own management station, deal with more than one management station, potentially using its
potentially using its resources concurrently. resources concurrently.
2.2. Structure of MIB 2.2. Structure of MIB
The objects are arranged into the following groups: The objects are arranged into the following groups:
- protocol directory - protocol directory
- protocol distribution - protocol distribution
- address mapping - address mapping
skipping to change at page 7, line 27 skipping to change at page 5, line 4
- network layer host - network layer host
- network layer matrix - network layer matrix
- application layer host - application layer host
- application layer matrix - application layer matrix
- user history - user history
- probe configuration - probe configuration
These groups are the basic units of conformance. If a remote These groups are the basic units of conformance. If a remote
monitoring device implements a group, then it must implement monitoring device implements a group, then it must implement all
all objects in that group. For example, a managed agent that objects in that group. For example, a managed agent that implements
implements the network layer matrix group must implement the the network layer matrix group must implement the nlMatrixSDTable and
nlMatrixSDTable and the nlMatrixDSTable. the nlMatrixDSTable.
Implementations of this MIB must also implement the IF-MIB Implementations of this MIB must also implement the IF-MIB [RFC2863].
[RFC2863].
These groups are defined to provide a means of assigning These groups are defined to provide a means of assigning object
object identifiers, and to provide a method for managed agents identifiers, and to provide a method for managed agents to know which
to know which objects they must implement. objects they must implement.
This document also contains enhancements to tables defined in This document also contains AUGMENTing tables to extend some tables
the RMON MIB [RFC2819]. These enhancements include: defined in the RMON MIB [RFC2819]. These extensions include the
following:
1) Adding the DroppedFrames and LastCreateTime 1) Adding the DroppedFrames and LastCreateTime conventions to each
conventions to each table defined in the RMON MIB. table defined in the RMON MIB.
2) Augmenting the RMON filter table with a mechanism 2) Augmenting the RMON filter table with a mechanism that allows
that allows filtering based on an offset from the filtering based on an offset from the beginning of a particular
beginning of a particular protocol, even if the protocol, even if the protocol headers are of variable length.
protocol headers are variable length.
3) Augmenting the RMON filter and capture status bits 3) Augmenting the RMON filter and capture status bits with
with additional bits for WAN media and generic media. additional bits for WAN media and generic media. These bits
These bits are defined here as: are defined here as follows:
Bit Definition Bit Definition
6 For WAN media, this bit is set for packets 6 For WAN media, this bit is set for packets
coming from one direction and cleared for coming from one direction and cleared for
packets coming from the other direction. packets coming from the other direction.
It is an implementation specific matter It is an implementation-specific matter
as to which bit is assigned to which as to which bit is assigned to which
direction, but it must be consistent for direction, but it must be consistent for
all packets received by the agent, and if all packets received by the agent. If
the agent knows which end of the link is the agent knows which end of the link is
"local" and which end is "network", the bit "local" and which end is "network", the bit
should be set for packets from the "local" should be set for packets from the "local"
side and should be cleared for packets from side and should be cleared for packets from
the "network" side. the "network" side.
7 For any media, this bit is set for any packet 7 For any media, this bit is set for any packet
with a physical layer error. This bit may be with a physical layer error. This bit may be
set in addition to other media-specific bits set in addition to other media-specific bits
that denote the same condition. that denote the same condition.
skipping to change at page 8, line 38 skipping to change at page 6, line 9
7 For any media, this bit is set for any packet 7 For any media, this bit is set for any packet
with a physical layer error. This bit may be with a physical layer error. This bit may be
set in addition to other media-specific bits set in addition to other media-specific bits
that denote the same condition. that denote the same condition.
8 For any media, this bit is set for any packet 8 For any media, this bit is set for any packet
that is too short for the media. This bit may that is too short for the media. This bit may
be set in addition to other media-specific be set in addition to other media-specific
bits that denote the same condition. bits that denote the same condition.
9 For any media, this bit is set for any packet 9 For any media, this bit is set for any packet
that is too long for the media. This bit may that is too long for the media. This bit may
be set in addition to other media-specific bits be set in addition to other media-specific bits
that denote the same condition. that denote the same condition.
These enhancements are implemented by RMON-2 probes that also These enhancements are implemented by RMON-2 probes that also
implement RMON and do not add any requirements to probes that implement RMON and do not add any requirements to probes that are
are compliant to just RMON. compliant to just RMON.
3. Control of Remote Network Monitoring Devices 3. Control of Remote Network Monitoring Devices
Due to the complex nature of the available functions in these Due to the complex nature of the available functions in these
devices, the functions often need user configuration. In many devices, the functions often need user configuration. In many cases,
cases, the function requires parameters to be set up for a the function requires that parameters be set up for a data collection
data collection operation. The operation can proceed only operation. The operation can proceed only after these parameters are
after these parameters are fully set up. fully set up.
Many functional groups in this MIB have one or more tables in Many functional groups in this MIB have one or more tables in which
which to set up control parameters, and one or more data to set up control parameters, and one or more data tables in which to
tables in which to place the results of the operation. The place the results of the operation. The control tables are typically
control tables are typically read/write in nature, while the read/write in nature, while the data tables are typically read-only.
data tables are typically read/only. Because the parameters Because the parameters in the control table often describe resulting
in the control table often describe resulting data in the data data in the data table, many of the parameters can be modified only
table, many of the parameters can be modified only when the when the control entry is not active. Thus, the method for modifying
control entry is not active. Thus, the method for modifying these parameters is to deactivate the entry, perform the SNMP Set
these parameters is to de-activate the entry, perform the SNMP operations to modify the entry, and then reactivate the entry.
Set operations to modify the entry, and then re-activate the Deleting the control entry causes the deletion of any associated data
entry. Deleting the control entry causes the deletion of any entries, which also gives a convenient method for reclaiming the
associated data entries, which also gives a convenient method resources used by the associated data.
for reclaiming the resources used by the associated data.
Some objects in this MIB provide a mechanism to execute an Some objects in this MIB provide a mechanism to execute an action on
action on the remote monitoring device. These objects may the remote monitoring device. These objects may execute an action as
execute an action as a result of a change in the state of the a result of a change in the state of the object. For those objects
object. For those objects in this MIB, a request to set an in this MIB, a request to set an object to the same value as it
object to the same value as it currently holds would thus currently holds would thus cause no action to occur.
cause no action to occur.
To facilitate control by multiple managers, resources have to To facilitate control by multiple managers, resources have to be
be shared among the managers. These resources are typically shared among the managers. These resources are typically the memory
the memory and computation resources that a function requires. and computation resources that a function requires.
3.1. Resource Sharing Among Multiple Management Stations 3.1. Resource Sharing among Multiple Management Stations
When multiple management stations wish to use functions that When multiple management stations wish to use functions that compete
compete for a finite amount of resources on a device, a method for a finite amount of resources on a device, a method to facilitate
to facilitate this sharing of resources is required. this sharing of resources is required. Potential conflicts include
Potential conflicts include: the following:
o Two management stations wish to simultaneously use o Two management stations wish to use resources simultaneously
resources that together would exceed the capability of that together would exceed the capability of the device.
the device.
o A management station uses a significant amount of resources for
a long period of time.
o A management station uses a significant amount of
resources for a long period of time.
o A management station uses resources and then crashes, o A management station uses resources and then crashes,
forgetting to free the resources so others may forgetting to free the resources so that others may use them.
use them.
The OwnerString mechanism is provided for each management The OwnerString mechanism is provided for each management station-
station initiated function in this MIB to avoid these initiated function in this MIB to avoid these conflicts and to help
conflicts and to help resolve them when they occur. Each resolve them when they occur. Each function has a label identifying
function has a label identifying the initiator (owner) of the the initiator (owner) of the function. This label is set by the
function. This label is set by the initiator to provide for initiator to provide for the following possibilities:
the following possibilities:
o A management station may recognize resources it owns and no
longer needs.
o A network operator can find the management station that owns
the resource and negotiate for it to be freed.
o A network operator may decide unilaterally to free resources
another network operator has reserved.
o A management station may recognize resources it owns
and no longer needs.
o A network operator can find the management station that
owns the resource and negotiate for it to be freed.
o A network operator may decide to unilaterally free
resources another network operator has reserved.
o Upon initialization, a management station may recognize o Upon initialization, a management station may recognize
resources it had reserved in the past. With this resources it had reserved in the past. With this information,
information it may free the resources if it no longer it may free the resources if it no longer needs them.
needs them.
Management stations and probes should support any format of Management stations and probes should support any format of the owner
the owner string dictated by the local policy of the string dictated by the local policy of the organization. It is
organization. It is suggested that this name contain one or suggested that this name contain one or more of the following: IP
more of the following: IP address, management station name, address, management station name, network manager's name, location,
network manager's name, location, or phone number. This or phone number. This information will help users share the
information will help users to share the resources more resources more effectively.
effectively.
There is often default functionality that the device or the There is often default functionality that the device or the
administrator of the probe (often the network administrator) administrator of the probe (often the network administrator) wishes
wishes to set up. The resources associated with this to set up. The resources associated with this functionality are then
functionality are then owned by the device itself or by the owned by the device itself or by the network administrator, and they
network administrator, and are intended to be long-lived. In are intended to be long-lived. In this case, the device or the
this case, the device or the administrator will set the administrator will set the relevant owner object to a string starting
relevant owner object to a string starting with 'monitor'. with 'monitor'. Indiscriminate modification of the monitor-owned
Indiscriminate modification of the monitor-owned configuration configuration by network management stations is discouraged. In
by network management stations is discouraged. In fact, a fact, a network management station should only modify these objects
network management station should only modify these objects
under the direction of the administrator of the probe. under the direction of the administrator of the probe.
Resources on a probe are scarce and are typically allocated Resources on a probe are scarce and are typically allocated when
when control rows are created by an application. Since many control rows are created by an application. Since many applications
applications may be using a probe simultaneously, may be using a probe simultaneously, indiscriminate allocation of
indiscriminate allocation of resources to particular resources to particular applications is very likely to cause resource
applications is very likely to cause resource shortages in the shortages in the probe.
probe.
When a network management station wishes to utilize a function When a network management station wishes to utilize a function in a
in a monitor, it is encouraged to first scan the control table monitor, it is encouraged first to scan the control table of that
of that function to find an instance with similar parameters function to find an instance with similar parameters to share. This
to share. This is especially true for those instances owned is especially true for those instances owned by the monitor, which
by the monitor, which can be assumed to change infrequently. can be assumed to change infrequently. If a management station
If a management station decides to share an instance owned by decides to share an instance owned by another management station, it
another management station, it should understand that the should understand that the management station that owns the instance
management station that owns the instance may indiscriminately may indiscriminately modify or delete it.
modify or delete it.
It should be noted that a management application should have Note that a management application should have the most trust in a
the most trust in a monitor-owned row because it should be monitor-owned row, because it should be changed very infrequently. A
changed very infrequently. A row owned by the management row owned by the management application is less long-lived because a
application is less long-lived because a network administrator network administrator is more likely to reassign resources from a row
is more likely to re-assign resources from a row that is in that is in use by one user than those from a monitor-owned row that
use by one user than from a monitor-owned row that is is potentially in use by many users. A row owned by another
potentially in use by many users. A row owned by another
application would be even less long-lived because the other application would be even less long-lived because the other
application may delete or modify that row completely at its application may delete or modify that row completely at its
discretion. discretion.
3.2. Row Addition Among Multiple Management Stations 3.2. Row Addition among Multiple Management Stations
The addition of new rows is achieved using the RowStatus The addition of new rows is achieved using the RowStatus Textual
Textual Convention [RFC2579]. In this MIB, rows are often Convention [RFC2579]. In this MIB, rows are often added to a table
added to a table in order to configure a function. This in order to configure a function. This configuration usually
configuration usually involves parameters that control the involves parameters that control the operation of the function. The
operation of the function. The agent must check these agent must check these parameters to make sure they are appropriate
parameters to make sure they are appropriate given given the restrictions defined in this MIB, as well as any
restrictions defined in this MIB as well as any implementation implementation-specific restrictions, such as lack of resources. The
specific restrictions such as lack of resources. The agent agent implementor may be confused as to when to check these
implementor may be confused as to when to check these parameters and when to signal to the management station that the
parameters and when to signal to the management station that parameters are invalid. There are two opportunities:
the parameters are invalid. There are two opportunities:
o When the management station sets each parameter object. o When the management station sets each parameter object.
o When the management station sets the row status object o When the management station sets the row status object to
to active. active.
If the latter is chosen, it would be unclear to the management
station which of the several parameters was invalid and caused
the badValue error to be emitted. Thus, wherever possible,
the implementor should choose the former as it will provide
more information to the management station.
A problem can arise when multiple management stations attempt If the latter option is chosen, it would be unclear to the management
to set configuration information simultaneously using SNMP. station which of the several parameters was invalid and caused the
When this involves the addition of a new conceptual row in the badValue error to be emitted. Thus, wherever possible, the
same control table, the managers may collide, attempting to implementor should choose the former option, as it will provide more
create the same entry. To guard against these collisions, information to the management station.
each such control entry contains a status object with special
semantics that help to arbitrate among the managers. If an
attempt is made with the row addition mechanism to create such
a status object and that object already exists, an error is
returned. When more than one manager simultaneously attempts
to create the same conceptual row, only the first will
succeed. The others will receive an error.
In the RMON MIB [RFC2819], the EntryStatus textual convention A problem can arise when multiple management stations attempt to set
was introduced to provide this mutual exclusion function. configuration information simultaneously using SNMP. When this
Since then, this function was added to the SNMP framework as involves the addition of a new conceptual row in the same control
the RowStatus textual convention. The RowStatus textual table, the managers may collide, attempting to create the same entry.
convention is used for the definition of all new tables. To guard against these collisions, each such control entry contains a
status object with special semantics that help arbitrate among the
managers. If an attempt is made with the row addition mechanism to
create such a status object and that object already exists, an error
is returned. When more than one manager simultaneously attempts to
create the same conceptual row, only the first will succeed. The
others will receive an error.
When a manager wishes to create a new control entry, it needs In the RMON MIB [RFC2819], the EntryStatus textual convention was
to choose an index for that row. It may choose this index in introduced to provide this mutual exclusion function. Since then,
a variety of ways, hopefully minimizing the chances that the this function was added to the SNMP framework as the RowStatus
index is in use by another manager. If the index is in use, textual convention. The RowStatus textual convention is used for the
the mechanism mentioned previously will guard against definition of all new tables.
collisions. Examples of schemes to choose index values
include random selection or scanning the control table looking
for the first unused index. Because index values may be any
valid value in the range and they are chosen by the manager,
the agent must allow a row to be created with any unused index
value if it has the resources to create a new row.
Some tables in this MIB reference other tables within this When a manager wishes to create a new control entry, it needs to
MIB. When creating or deleting entries in these tables, it is choose an index for that row. It may choose this index in a variety
generally allowable for dangling references to exist. There of ways, hopefully minimizing the chances that the index is in use by
is no defined order for creating or deleting entries in these another manager. If the index is in use, the mechanism mentioned
previously will guard against collisions. Examples of schemes to
choose index values include random selection or scanning the control
table while looking for the first unused index. Because index values
may be any valid value in the range and are chosen by the manager,
the agent must allow a row to be created with any unused index value
if it has the resources to create a new row.
tables. Some tables in this MIB reference other tables within this MIB. When
creating or deleting entries in these tables, it is generally
allowable for dangling references to exist. There is no defined
order for creating or deleting entries in these tables.
4. Conventions 4. Conventions
The following conventions are used throughout the RMON MIB and The following conventions are used throughout the RMON MIB and its
its companion documents. companion documents.
Good Packets Good Packets
Good packets are error-free packets that have a valid frame Good packets are error-free packets that have a valid frame
length. For example, on Ethernet, good packets are error-free length. For example, on Ethernet, good packets are error-free
packets that are between 64 octets long and 1518 octets long. packets that are between 64 octets and 1518 octets long. They
They follow the form defined in IEEE 802.3 section 3.2.all. follow the form defined in IEEE 802.3 section 3.2.all.
Bad Packets Bad Packets
Bad packets are packets that have proper framing and are Bad packets are packets that have proper framing and are therefore
therefore recognized as packets, but contain errors within the recognized as packets, but that contain errors within the packet
packet or have an invalid length. For example, on Ethernet, or have an invalid length. For example, on Ethernet, bad packets
bad packets have a valid preamble and SFD, but have a bad CRC, have a valid preamble and SFD but have a bad CRC, or they are
or are either shorter than 64 octets or longer than 1518 either shorter than 64 octets or longer than 1518 octets.
octets.
5. RMON 2 Conventions 5. RMON 2 Conventions
The following practices and conventions are introduced in the The following practices and conventions are introduced in the RMON 2
RMON 2 MIB. MIB.
5.1. Usage of the term Application Level 5.1. Usage of the Term "Application Level"
There are many cases in this MIB where the term Application There are many cases in this MIB where the term "Application Level"
Level is used to describe a class of protocols or a is used to describe a class of protocols or a capability. This does
capability. This does not typically mean a protocol that is not typically mean a protocol that is an OSI Layer 7 protocol.
an OSI Layer 7 protocol. Rather, it is used to identify a Rather, it is used to identify a class of protocols that is not
class of protocols that is not limited to MAC-layer and limited to MAC-layer and network-layer protocols, but can also
network-layer protocols, but can also include transport, include transport, session, presentation, and application-layer
session, presentation, and application-layer protocols. protocols.
5.2. Protocol Directory and Limited Extensibility 5.2. Protocol Directory and Limited Extensibility
Every RMON 2 implementation will have the capability to parse Every RMON 2 implementation will have the capability to parse certain
certain types of packets and identify their protocol type at types of packets and identify their protocol type at multiple levels.
multiple levels. The protocol directory presents an inventory The protocol directory presents an inventory of protocol types the
of those protocol types the probe is capable of monitoring, probe is capable of monitoring and allows the addition, deletion, and
and allows the addition, deletion, and configuration of configuration of protocol types in this list.
protocol types in this list.
One concept deserves special attention: the "limited One concept deserves special attention: the "limited extensibility"
extensibility" of the protocol directory table. The RMON 2 of the protocol directory table. Using the RMON 2 model, protocols
model is that protocols are detected by static software that are detected by static software that has been written at
has been written at implementation time. Therefore, as a implementation time. Therefore, as a matter of configuration, an
matter of configuration, an implementation does not have the implementation cannot suddenly learn how to parse new packet types.
ability to suddenly learn how to parse new packet types. However, an implementation may be written such that the software
However, an implementation may be written such that the knows where the demultiplexing field is for a particular protocol,
software knows where the demultiplexing field is for a and it can be written in such a way that the decoding of the next
particular protocol, and can be written in such a way that the layer up is table driven. This works when the code has been written
decoding of the next layer up is table-driven. This works to accommodate it and can be extended no more than one level higher.
when the code has been written to accomodate it and can be
extended no more than one level higher. This extensibility is
called "limited extensibility" to highlight these limitations.
However, this can be a very useful tool.
For example, suppose that an implementation has C code that This extensibility is called "limited extensibility" to highlight
understands how to decode IP packets on any of several these limitations. However, this can be a very useful tool.
ethernet encapsulations, and also knows how to interpret the
IP protocol field to recognize UDP packets and how to decode For example, suppose that an implementation has C code that
the UDP port number fields. That implementation may be table- understands how to decode IP packets on any of several ethernet
driven so that among the many different UDP port numbers encapsulations, and also knows how to interpret the IP protocol field
possible, it is configured to recognize 161 as SNMP, port 53 to recognize UDP packets and how to decode the UDP port number
as DNS, and port 69 as TFTP. The limited extensibility of the fields. That implementation may be table driven so that among the
protocol directory table would allow an SNMP operation to many different UDP port numbers possible, it is configured to
create an entry that would create an additional table mapping recognize 161 as SNMP, port 53 as DNS, and port 69 as TFTP. The
for UDP that would recognize UDP port 123 as NTP and begin limited extensibility of the protocol directory table would allow an
counting such packets. SNMP operation to create an entry that would create an additional
table mapping for UDP that would recognize UDP port 123 as NTP and
begin counting such packets.
This limited extensibility is an option that an implementation This limited extensibility is an option that an implementation can
can choose to allow or disallow for any protocol that has choose to allow or disallow for any protocol that has child
child protocols. protocols.
5.3. Errors in packets 5.3. Errors in Packets
Packets with link-level errors are not counted anywhere in Packets with link-level errors are not counted anywhere in this MIB
this MIB because most variables in this MIB requires the because most variables in this MIB require the decoding of the
decoding of the contents of the packet, which is meaningless contents of the packet, which is meaningless if there is a link-level
if there is a link-level error. error.
Packets in which protocol errors are detected are counted for Packets in which protocol errors are detected are counted for all
all protocols below the layer in which the error was protocols below the layer in which the error was encountered. The
encountered. The implication of this is that packets in which implication of this is that packets in which errors are detected at
errors are detected at the network-layer are not counted the network-layer are not counted anywhere in this MIB, while packets
anywhere in this MIB, while packets with errors detected at with errors detected at the transport layer may have network-layer
the transport layer may have network-layer statistics counted. statistics counted.
6. Definitions 6. Definitions
RMON2-MIB DEFINITIONS ::= BEGIN RMON2-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32,
Gauge32, IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI Gauge32, IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, DisplayString, TimeStamp TEXTUAL-CONVENTION, RowStatus, DisplayString, TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
skipping to change at page 17, line 10 skipping to change at page 12, line 9
OwnerString, statistics, history, hosts, OwnerString, statistics, history, hosts,
matrix, filter, etherStatsEntry, historyControlEntry, matrix, filter, etherStatsEntry, historyControlEntry,
hostControlEntry, matrixControlEntry, filterEntry, hostControlEntry, matrixControlEntry, filterEntry,
channelEntry FROM RMON-MIB channelEntry FROM RMON-MIB
tokenRing, tokenRingMLStatsEntry, tokenRingPStatsEntry, tokenRing, tokenRingMLStatsEntry, tokenRingPStatsEntry,
ringStationControlEntry, sourceRoutingStatsEntry ringStationControlEntry, sourceRoutingStatsEntry
FROM TOKEN-RING-RMON-MIB; FROM TOKEN-RING-RMON-MIB;
-- Remote Network Monitoring MIB -- Remote Network Monitoring MIB
rmon MODULE-IDENTITY rmon MODULE-IDENTITY
LAST-UPDATED "200510031500Z" -- October 3, 2005 LAST-UPDATED "200605020000Z" -- May 2, 2006
ORGANIZATION "IETF RMON MIB Working Group" ORGANIZATION "IETF RMON MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Author: "Author:
Steve Waldbusser Steve Waldbusser
Phone: +1-650-948-6500 Phone: +1-650-948-6500
Fax : +1-650-745-0671 Fax : +1-650-745-0671
Email: waldbusser@nextbeacon.com Email: waldbusser@nextbeacon.com
Working Group Chair: Working Group Chair:
Andy Bierman Andy Bierman
E-mail: ietf@andybierman.com E-mail: ietf@andybierman.com
Working Group Mailing List: <rmonmib@ietf.org> Working Group Mailing List: <rmonmib@ietf.org>
To subscribe send email to: <rmonmib-request@ietf.org> " To subscribe send email to: <rmonmib-request@ietf.org> "
DESCRIPTION DESCRIPTION
"The MIB module for managing remote monitoring "The MIB module for managing remote monitoring
device implementations. This MIB module device implementations. This MIB module
extends the architecture introduced in the original extends the architecture introduced in the original
RMON MIB as specified in RFC 2819. RMON MIB as specified in RFC 2819.
Copyright (C) The Internet Society (2005). This version of Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC yyyy; see the RFC itself for this MIB module is part of RFC 4502; see the RFC itself for
full legal notices." full legal notices."
REVISION "200510031500Z" -- October 3, 2005 REVISION "200605020000Z" -- May 2, 2006
DESCRIPTION DESCRIPTION
"This version updates the proposed-standard version of the "This version updates the proposed-standard version of the
RMON2 MIB (published as RFC 2021) by adding 2 new enumerations RMON2 MIB (published as RFC 2021) by adding 2 new
to the nlMatrixTopNControlRateBase object and 4 new enumerations to the nlMatrixTopNControlRateBase object and
enumerations to the alMatrixTopNControlRateBase object. These 4 new enumerations to the alMatrixTopNControlRateBase object.
new enumerations support the creation of high capacity topN These new enumerations support the creation of high-capacity
reports in the High Capacity RMON MIB [RFC3273]. topN reports in the High Capacity RMON MIB [RFC3273].
Additionally, the following objects have been deprecated as Additionally, the following objects have been deprecated, as
they have not had enough independent implementations to they have not had enough independent implementations to
demonstrate interoperability to meet the requirements of a demonstrate interoperability to meet the requirements of a
Draft Standard: Draft Standard:
probeDownloadFile probeDownloadFile
probeDownloadTFTPServer probeDownloadTFTPServer
probeDownloadAction probeDownloadAction
probeDownloadStatus probeDownloadStatus
serialMode serialMode
serialProtocol serialProtocol
skipping to change at page 18, line 47 skipping to change at page 13, line 42
sourceRoutingStats2CreateTime sourceRoutingStats2CreateTime
trapDestIndex trapDestIndex
trapDestCommunity trapDestCommunity
trapDestProtocol trapDestProtocol
trapDestAddress trapDestAddress
trapDestOwner trapDestOwner
trapDestStatus trapDestStatus
In addition, two corrections were made. The LastCreateTime In addition, two corrections were made. The LastCreateTime
Textual Convention had been defined with a base type of Textual Convention had been defined with a base type of
another textual convention which isn't allowed in SMIv2. The another textual convention, which isn't allowed in SMIv2. The
definition has been modified to use TimeTicks as the base definition has been modified to use TimeTicks as the base
type. type.
Further, the SerialConfigEntry SEQUENCE definition included Further, the SerialConfigEntry SEQUENCE definition included
sub-typing information that is not allowed in SMIv2. This sub-typing information that is not allowed in SMIv2. This
information has been deleted. Ranges were added to a number of information has been deleted. Ranges were added to a number of
objects and textual-conventions to constrain their maximum objects and textual-conventions to constrain their maximum
(and sometimes minimum) sizes. The addition of these ranges (and sometimes minimum) sizes. The addition of these ranges
documents existing practice for these objects. These objects documents existing practice for these objects. These objects
are: are:
skipping to change at page 19, line 38 skipping to change at page 14, line 30
alMatrixTopNDestAddress alMatrixTopNDestAddress
Finally, the TimeFilter TC has been updated to encourage agent Finally, the TimeFilter TC has been updated to encourage agent
implementations that allow a MIB walk to behave well even when implementations that allow a MIB walk to behave well even when
performed by an application that is not aware of the special performed by an application that is not aware of the special
TimeFilter semantics." TimeFilter semantics."
REVISION "200207080000Z" -- 08 July, 2002 REVISION "200207080000Z" -- 08 July, 2002
DESCRIPTION DESCRIPTION
"Added new enumerations to support the High-Capacity RMON "Added new enumerations to support the High-Capacity RMON
MIB as defined in RFC 3273. Also fixed some typos and add MIB as defined in RFC 3273. Also fixed some typos and
clarifications." added clarifications."
REVISION "199605270000Z" -- 27 May, 1996 REVISION "199605270000Z" -- 27 May, 1996
DESCRIPTION DESCRIPTION
"Original version. Published as RFC 2021." "Original version. Published as RFC 2021."
::= { mib-2 16 } ::= { mib-2 16 }
-- { rmon 1 } through { rmon 10 } are defined in RMON and -- { rmon 1 } through { rmon 10 } are defined in RMON and
-- the Token Ring RMON MIB [RFC1513] -- the Token Ring RMON MIB [RFC1513]
protocolDir OBJECT IDENTIFIER ::= { rmon 11 } protocolDir OBJECT IDENTIFIER ::= { rmon 11 }
protocolDist OBJECT IDENTIFIER ::= { rmon 12 } protocolDist OBJECT IDENTIFIER ::= { rmon 12 }
addressMap OBJECT IDENTIFIER ::= { rmon 13 } addressMap OBJECT IDENTIFIER ::= { rmon 13 }
nlHost OBJECT IDENTIFIER ::= { rmon 14 } nlHost OBJECT IDENTIFIER ::= { rmon 14 }
nlMatrix OBJECT IDENTIFIER ::= { rmon 15 } nlMatrix OBJECT IDENTIFIER ::= { rmon 15 }
alHost OBJECT IDENTIFIER ::= { rmon 16 } alHost OBJECT IDENTIFIER ::= { rmon 16 }
alMatrix OBJECT IDENTIFIER ::= { rmon 17 } alMatrix OBJECT IDENTIFIER ::= { rmon 17 }
usrHistory OBJECT IDENTIFIER ::= { rmon 18 } usrHistory OBJECT IDENTIFIER ::= { rmon 18 }
probeConfig OBJECT IDENTIFIER ::= { rmon 19 } probeConfig OBJECT IDENTIFIER ::= { rmon 19 }
rmonConformance OBJECT IDENTIFIER ::= { rmon 20 } rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }
skipping to change at page 21, line 10 skipping to change at page 15, line 10
alMatrix OBJECT IDENTIFIER ::= { rmon 17 } alMatrix OBJECT IDENTIFIER ::= { rmon 17 }
usrHistory OBJECT IDENTIFIER ::= { rmon 18 } usrHistory OBJECT IDENTIFIER ::= { rmon 18 }
probeConfig OBJECT IDENTIFIER ::= { rmon 19 } probeConfig OBJECT IDENTIFIER ::= { rmon 19 }
rmonConformance OBJECT IDENTIFIER ::= { rmon 20 } rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }
-- Textual Conventions -- Textual Conventions
ZeroBasedCounter32 ::= TEXTUAL-CONVENTION ZeroBasedCounter32 ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This TC describes an object which counts events with the "This TC describes an object that counts events with the
following semantics: objects of this type will be set to following semantics: objects of this type will be set to
zero(0) on creation and will thereafter count appropriate zero(0) on creation and will thereafter count appropriate
events, wrapping back to zero(0) when the value 2^32 is events, wrapping back to zero(0) when the value 2^32 is
reached. reached.
Provided that an application discovers the new object within Provided that an application discovers the new object within
the minimum time to wrap it can use the initial value as a the minimum time to wrap, it can use the initial value as a
delta since it last polled the table of which this object is delta since it last polled the table of which this object is
part. It is important for a management station to be aware of part. It is important for a management station to be aware of
this minimum time and the actual time between polls, and to this minimum time and the actual time between polls, and to
discard data if the actual time is too long or there is no discard data if the actual time is too long or there is no
defined minimum time. defined minimum time.
Typically this TC is used in tables where the INDEX space is Typically, this TC is used in tables where the INDEX space is
constantly changing and/or the TimeFilter mechanism is in use." constantly changing and/or the TimeFilter mechanism is in use."
SYNTAX Gauge32 SYNTAX Gauge32
LastCreateTime ::= TEXTUAL-CONVENTION LastCreateTime ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This TC describes an object that stores the value of the "This TC describes an object that stores the value of the
sysUpTime object at the last time its entry was created. sysUpTime object at the last time its entry was created.
This can be used for polling applications to determine that an This can be used for polling applications to determine that an
entry has been deleted and re-created between polls, causing entry has been deleted and re-created between polls, causing
an otherwise undetectable discontinuity in the data. an otherwise undetectable discontinuity in the data.
If sysUpTime is reset to zero as a result of a re- If sysUpTime is reset to zero as a result of a re-
initialization of the network management (sub)system, then initialization of the network management (sub)system, then
the values of all LastCreateTime objects are also reset. the values of all LastCreateTime objects are also reset.
However, after approximately 497 days without a re- However, after approximately 497 days without a re-
initialization, the sysUpTime object will reach 2^^32-1 and initialization, the sysUpTime object will reach 2^^32-1 and
then increment around to zero; in this case, existing values then increment to zero; in this case, existing values
of TimeStamp objects do not change. This can lead to of TimeStamp objects do not change. This can lead to
ambiguities in the value of TimeStamp objects." ambiguities in the value of TimeStamp objects."
SYNTAX TimeTicks SYNTAX TimeTicks
TimeFilter ::= TEXTUAL-CONVENTION TimeFilter ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To be used for the index to a table. Allows an application "To be used for the index to a table. Allows an application
to download only those rows changed since a particular time. to download only those rows changed since a particular time.
Note that this is not a history mechanism. Only current values Note that this is not a history mechanism. Only current values
of underlying objects are returned, not saved instance values of underlying objects are returned; saved instance values
associated with particular values of sysUpTime. associated with particular values of sysUpTime are not.
An entry is considered changed if the value of any object in the An entry is considered changed if the value of any object in the
entry changes, if the row is created, or if any object in the entry changes, if the row is created, or if any object in the
entry is created or deleted. Note that deleted entries cannot entry is created or deleted. Note that deleted entries cannot
be detected or downloaded. be detected or downloaded.
A time-filtered conceptual table is created by inserting a A time-filtered conceptual table is created by inserting a
single object of SYNTAX TimeFilter as the first INDEX component single object of SYNTAX TimeFilter as the first INDEX component
in a copy of an existing basic conceptual table (i.e., any in a copy of an existing basic conceptual table (i.e., any
SEQUENCE without a TimeFilter INDEX component). Thus, for SEQUENCE without a TimeFilter INDEX component). Thus, for
each conceptual entry 'I' in the basic table, there exists N each conceptual entry 'I' in the basic table, there exists N
conceptual entries in the time-filtered version, (indexed N.I) conceptual entries in the time-filtered version, indexed N.I,
where 'N' is equal to the value of sysUpTime. where 'N' is equal to the value of sysUpTime.
When an application retrieves conceptual instances from a When an application retrieves conceptual instances from a
time-filtered table, and an INDEX value is provided for the time-filtered table, and an INDEX value is provided for the
TimeFilter INDEX component 'N', the agent will only consider TimeFilter INDEX component 'N', the agent will only consider
returning basic conceptual entries (e.g., 'fooColumn.N.I') if returning basic conceptual entries (e.g., 'fooColumn.N.I') if
any column within the basic conceptual entry has changed since any column within the basic conceptual entry has changed since
sysUpTime equals 'N'. If not, the basic conceptual entry will sysUpTime 'N'. If not, the basic conceptual entry will
be ignored for the particular retrieval operation. be ignored for the particular retrieval operation.
When sysUpTime is equal to zero, this table shall be empty. When sysUpTime is equal to zero, this table shall be empty.
One conceptual entry exists for each past value of sysUpTime, One conceptual entry exists for each past value of sysUpTime,
except that the whole table is purged should sysUpTime wrap. except that the whole table is purged should sysUpTime wrap.
As an entry in a time-filtered table is updated (i.e., one of As an entry in a time-filtered table is updated (i.e., one of
the columns in the basic conceptual table is changed), new the columns in the basic conceptual table is changed), new
conceptual entries are also created in the time-filtered version conceptual entries are also created in the time-filtered version
(which still share the now updated object values with all other (which still shares the now updated object values with all other
instances). The number of unique time-filtered instances which instances). The number of unique time-filtered instances that
are created is determined by the value of sysUpTime at which the are created is determined by the value of sysUpTime at which the
basic entry was last updated. One unique instance will exist basic entry was last updated. One unique instance will exist
for each value of sysUpTime at the last update time for the row. for each value of sysUpTime at the last update time for the row.
However, a new TimeFilter index instance is created for each new However, a new TimeFilter index instance is created for each new
sysUpTime value. The TimeFilter index values not associated sysUpTime value. The TimeFilter index values not associated
with entry updates are called duplicate time-filtered instances. with entry updates are called duplicate time-filtered instances.
After some deployment experience, it has been determined that After some deployment experience, it has been determined that
a time-filtered table is more efficient to use if the agent a time-filtered table is more efficient if the agent
stops a 'MIB walk' operation by skipping over rows with a stops a MIB walk operation by skipping over rows with a
TimeFilter index value higher than the value in the received TimeFilter index value higher than the value in the received
GetNext/GetBulk request. That is, instead of incrementing a GetNext/GetBulk request. That is, instead of incrementing a
TimeFilter index value, the agent will continue to the next TimeFilter index value, the agent will continue to the next
object or table. As a consequence, GetNext or GetBulk object or table. As a consequence, GetNext or GetBulk
operations will provide only one pass through a time-filtered operations will provide only one pass through a time-filtered
table. table.
It is suggested for an agent to implement a time-filtered table It is suggested that an agent implement a time-filtered table
in this manner to improve performance and avoid a 'MIB walk' in this manner to improve performance and avoid a MIB walk
getting stuck in time-filtered tables. It is, however, still getting stuck in time-filtered tables. It is, however, still
acceptable for an agent to implement a time-filtered table in acceptable for an agent to implement a time-filtered table in
the traditional manner (i.e., every conceptual time-filtered the traditional manner (i.e., every conceptual time-filtered
instance is returned in GetNext and GetBulk PDU responses) and instance is returned in GetNext and GetBulk PDU responses), and
management applications must be able to deal with such management applications must be able to deal with such
traditional implementations. traditional implementations.
See the appendix for further discussion of this textual See the appendix for further discussion of this textual
convention. convention.
The following example is provided to demonstrate TimeFilter The following example is provided to demonstrate TimeFilter
behavior: behavior:
Consider the following basic conceptual table basicFooTable Consider the following basic conceptual table, basicFooTable.
(Note that the basic version of a time-filtered table may not (Note that the basic version of a time-filtered table may not
actually be defined.) actually be defined.)
basicFooTable: basicFooTable:
basicFooTable ... basicFooTable ...
INDEX { fooIndex } INDEX { fooIndex }
BasicFooEntry { BasicFooEntry {
fooIndex Integer32, fooIndex Integer32,
skipping to change at page 24, line 28 skipping to change at page 18, line 16
fooCounts Counter32 fooCounts Counter32
} }
Note that entries exist in the time-filtered conceptual table Note that entries exist in the time-filtered conceptual table
only if they actually exist in the underlying (basic) table. only if they actually exist in the underlying (basic) table.
For this example, the fooTable will have three underlying For this example, the fooTable will have three underlying
basic entries (fooIndex == 1, 2, and 3), with the following basic entries (fooIndex == 1, 2, and 3), with the following
activity (for sysUpTime equal 0 to 9): activity (for sysUpTime equal 0 to 9):
- fooEntry.N.1 is created at time '0', and most recently - fooEntry.N.1 is created at time '0' and most recently
updated at time '6' to the value '5'. updated at time '6' to the value '5'.
- fooEntry.N.2 is created at time '0', and most recently - fooEntry.N.2 is created at time '0' and most recently
updated at time '8' to the value '9'. updated at time '8' to the value '9'.
- fooEntry.N.3 is created at time '3', updated at time '5' - fooEntry.N.3 is created at time '3', updated at time '5'
to the value '17', and deleted at time '7'. to the value '17', and deleted at time '7'.
The following tables show the values that would be returned for The following tables show the values that would be returned for
'MIB walk' operations with various TimeFilter values, done at MIB walk operations with various TimeFilter values, done at
different times. An application issues a retrieval request at different times. An application issues a retrieval request at
time 'T', with a TimeFilter value 'N' (typically set to a lower time 'T', with a TimeFilter value, 'N' (typically set to a lower
value, such as the value of sysUpTime at the last polling cycle). value, such as the value of sysUpTime at the last polling cycle).
The following values would be returned in a MIB walk of The following values would be returned in a MIB walk of
fooCounts.N if T equals '0' and N equals '0': fooCounts.N if T equals '0' and N equals '0':
fooCounts.N.I Value fooCounts.N.I Value
========================== ==========================
fooCounts.0.1 0 fooCounts.0.1 0
fooCounts.0.2 0 fooCounts.0.2 0
Note there is nothing returned for fooCounts.0.3 since that Note that nothing is returned for fooCounts.0.3, since that
entry does not exist at sysUpTime equals '0'. entry does not exist at sysUpTime equals '0'.
The following values would be returned in a full (traditional) MIB The following values would be returned in a full (traditional) MIB
walk of fooCounts.N if T equals '3' and N equals '0': walk of fooCounts.N if T equals '3' and N equals '0':
fooCounts.N.I Value fooCounts.N.I Value
======================= =======================
fooCounts.0.1 0 fooCounts.0.1 0
fooCounts.0.2 0 fooCounts.0.2 0
fooCounts.0.3 0 fooCounts.0.3 0
fooCounts.1.3 0 fooCounts.1.3 0
fooCounts.2.3 0 fooCounts.2.3 0
fooCounts.3.3 0 fooCounts.3.3 0
Note that there are no instances for T equals 1 or 2 for the
Note that there are no instances for T equals 1 or 2, for the first two values of N, as these entries did not change
first two values of N, since these entries did not change
since they were created at time '0'. since they were created at time '0'.
Note that the current value for 'fooCounts.N.3' is returned Note that the current value for 'fooCounts.N.3' is returned
here, even for values of N less than '3' (when the entry was here, even for values of N less than '3' (when the entry was
created). The agent only considers the current existence of an created). The agent only considers the current existence of an
entry in the TimeFilter algorithm, not the time when the entry entry in the TimeFilter algorithm, not the time when the entry
was created. was created.
Note that the instances 'fooCounts.0.3', 'fooCounts.1.3' Note that the instances 'fooCounts.0.3', 'fooCounts.1.3',
and 'fooCounts.2.3' are duplicates and can be suppressed by the and 'fooCounts.2.3' are duplicates and can be suppressed by the
agent in a MIB walk. agent in a MIB walk.
The following values would be returned in a full (traditional) The following values would be returned in a full (traditional)
MIB walk of fooCounts.N if T equals '6' and N equals '3': MIB walk of fooCounts.N if T equals '6' and N equals '3':
fooCounts.N.I Value fooCounts.N.I Value
======================= =======================
fooCounts.3.1 5 fooCounts.3.1 5
fooCounts.3.3 17 fooCounts.3.3 17
fooCounts.4.1 5 fooCounts.4.1 5
fooCounts.4.3 17 fooCounts.4.3 17
fooCounts.5.1 5 fooCounts.5.1 5
fooCounts.5.3 17 fooCounts.5.3 17
fooCounts.6.1 5 fooCounts.6.1 5
Note that no instances for entry 'fooCounts.N.2' are returned
Note that no instances for entry 'fooCounts.N.2' are returned,
since it has not changed since time '3'. since it has not changed since time '3'.
Note that all instances except 'fooCounts.5.3' and Note that all instances except 'fooCounts.5.3' and
'fooCounts.6.1' are duplicates and can be suppressed by the 'fooCounts.6.1' are duplicates and can be suppressed by the
agent in a MIB walk. agent in a MIB walk.
The following values would be returned in a full (traditional) The following values would be returned in a full (traditional)
MIB walk of fooCounts.N if T equals '9' and N equals '6': MIB walk of fooCounts.N if T equals '9' and N equals '6':
fooCounts.N.I Value fooCounts.N.I Value
======================= =======================
fooCounts.6.1 5 fooCounts.6.1 5
fooCounts.6.2 9 fooCounts.6.2 9
fooCounts.7.2 9 fooCounts.7.2 9
fooCounts.8.2 9 fooCounts.8.2 9
Note that no instances for entry 'fooCounts.N.3' are returned Note that no instances for entry 'fooCounts.N.3' are returned,
since it was deleted at time '7'. since it was deleted at time '7'.
Note that instances 'fooCounts.6.2' and 'fooCounts.7.2' Note that instances 'fooCounts.6.2' and 'fooCounts.7.2'
are duplicates and can be suppressed by the agent in a MIB are duplicates and can be suppressed by the agent in a MIB
walk." walk."
SYNTAX TimeTicks SYNTAX TimeTicks
DataSource ::= TEXTUAL-CONVENTION DataSource ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 27, line 19 skipping to change at page 20, line 38
-- monitoring and allows the addition, deletion, and configuration of -- monitoring and allows the addition, deletion, and configuration of
-- entries in this list. -- entries in this list.
protocolDirLastChange OBJECT-TYPE protocolDirLastChange OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time the protocol directory "The value of sysUpTime at the time the protocol directory
was last modified, either through insertions or deletions, was last modified, either through insertions or deletions,
or through modifications of either the or through modifications of the
protocolDirAddressMapConfig, protocolDirHostConfig, or protocolDirAddressMapConfig, protocolDirHostConfig, or
protocolDirMatrixConfig." protocolDirMatrixConfig."
::= { protocolDir 1 } ::= { protocolDir 1 }
protocolDirTable OBJECT-TYPE protocolDirTable OBJECT-TYPE
SYNTAX SEQUENCE OF ProtocolDirEntry SYNTAX SEQUENCE OF ProtocolDirEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table lists the protocols that this agent has the "This table lists the protocols that this agent has the
capability to decode and count. There is one entry in this capability to decode and count. There is one entry in this
table for each such protocol. These protocols represent table for each such protocol. These protocols represent
different network layer, transport layer, and higher-layer different network-layer, transport-layer, and higher-layer
protocols. The agent should boot up with this table protocols. The agent should boot up with this table
preconfigured with those protocols that it knows about and preconfigured with those protocols that it knows about and
wishes to monitor. Implementations are strongly encouraged to wishes to monitor. Implementations are strongly encouraged to
support protocols higher than the network layer (at least for support protocols higher than the network layer (at least for
the protocol distribution group), even for implementations the protocol distribution group), even for implementations
that don't support the application layer groups." that don't support the application-layer groups."
::= { protocolDir 2 } ::= { protocolDir 2 }
protocolDirEntry OBJECT-TYPE protocolDirEntry OBJECT-TYPE
SYNTAX ProtocolDirEntry SYNTAX ProtocolDirEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the protocolDirTable. "A conceptual row in the protocolDirTable.
An example of the indexing of this entry is 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 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 encoding of a length of 8, followed by 8 subids encoding the
protocolDirID of 1.2048, followed by a length of 2 and the protocolDirID of 1.2048, followed by a length of 2 and the
2 subids encoding zero-valued parameters. 2 subids encoding zero-valued parameters.
Note that some combinations of index values may result in an Note that some combinations of index values may result in an
index that exceeds 128 sub-identifiers in length which exceeds index that exceeds 128 sub-identifiers in length, which exceeds
the maximum for the SNMP protocol. Implementations should take the maximum for the SNMP protocol. Implementations should take
care to avoid such combinations." care to avoid such combinations."
INDEX { protocolDirID, protocolDirParameters } INDEX { protocolDirID, protocolDirParameters }
::= { protocolDirTable 1 } ::= { protocolDirTable 1 }
ProtocolDirEntry ::= SEQUENCE { ProtocolDirEntry ::= SEQUENCE {
protocolDirID OCTET STRING, protocolDirID OCTET STRING,
protocolDirParameters OCTET STRING, protocolDirParameters OCTET STRING,
protocolDirLocalIndex Integer32, protocolDirLocalIndex Integer32,
protocolDirDescr DisplayString, protocolDirDescr DisplayString,
skipping to change at page 28, line 35 skipping to change at page 21, line 51
protocolDirOwner OwnerString, protocolDirOwner OwnerString,
protocolDirStatus RowStatus protocolDirStatus RowStatus
} }
protocolDirID OBJECT-TYPE protocolDirID OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4..128)) SYNTAX OCTET STRING (SIZE (4..128))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier for a particular protocol. Standard "A unique identifier for a particular protocol. Standard
identifiers will be defined in a manner such that they identifiers will be defined in such a manner that they
can often be used as specifications for new protocols - i.e. can often be used as specifications for new protocols - i.e.,
a tree-structured assignment mechanism that matches the a tree-structured assignment mechanism that matches the
protocol encapsulation `tree' and which has algorithmic protocol encapsulation 'tree' and that has algorithmic
assignment mechanisms for certain subtrees. See RFC 2074 for assignment mechanisms for certain subtrees. See RFC 2074 for
more details. more details.
Despite the algorithmic mechanism, the probe will only place Despite the algorithmic mechanism, the probe will only place
entries in here for those protocols it chooses to collect. In entries in here for those protocols it chooses to collect. In
other words, it need not populate this table with all of the other words, it need not populate this table with all
possible ethernet protocol types, nor need it create them on possible ethernet protocol types, nor need it create them on
the fly when it sees them. Whether or not it does these the fly when it sees them. Whether it does these
things is a matter of product definition (cost/benefit, things is a matter of product definition (cost/benefit,
usability), and is up to the designer of the product. usability) and is up to the designer of the product.
If an entry is written to this table with a protocolDirID that If an entry is written to this table with a protocolDirID that
the agent doesn't understand, either directly or the agent doesn't understand, either directly or
algorithmically, the SET request will be rejected with an algorithmically, the SET request will be rejected with an
inconsistentName or badValue (for SNMPv1) error." inconsistentName or badValue (for SNMPv1) error."
::= { protocolDirEntry 1 } ::= { protocolDirEntry 1 }
protocolDirParameters OBJECT-TYPE protocolDirParameters OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..32)) SYNTAX OCTET STRING (SIZE (1..32))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 29, line 30 skipping to change at page 22, line 42
will be one octet in this string for each sub-identifier in will be one octet in this string for each sub-identifier in
the protocolDirID, and the parameters will appear here in the the protocolDirID, and the parameters will appear here in the
same order as the associated sub-identifiers appear in the same order as the associated sub-identifiers appear in the
protocolDirID. protocolDirID.
Every node in the protocolDirID tree has a different, optional Every node in the protocolDirID tree has a different, optional
set of parameters defined (that is, the definition of set of parameters defined (that is, the definition of
parameters for a node is optional). The proper parameter parameters for a node is optional). The proper parameter
value for each node is included in this string. Note that the value for each node is included in this string. Note that the
inclusion of a parameter value in this string for each node is inclusion of a parameter value in this string for each node is
not optional - what is optional is that a node may have no not optional. What is optional is that a node may have no
parameters defined, in which case the parameter field for that parameters defined, in which case the parameter field for that
node will be zero." node will be zero."
::= { protocolDirEntry 2 } ::= { protocolDirEntry 2 }
protocolDirLocalIndex OBJECT-TYPE protocolDirLocalIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The locally arbitrary, but unique identifier associated "The locally arbitrary but unique identifier associated
with this protocolDir entry. with this protocolDir entry.
The value for each supported protocol must remain constant at The value for each supported protocol must remain constant at
least from one re-initialization of the entity's network least from one re-initialization of the entity's network
management system to the next re-initialization, except that management system to the next re-initialization, except that
if a protocol is deleted and re-created, it must be re-created 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 with a new value that has not been used since the last
re-initialization. re-initialization.
The specific value is meaningful only within a given SNMP The specific value is meaningful only within a given SNMP
entity. A protocolDirLocalIndex must not be re-used until the entity. A protocolDirLocalIndex must not be re-used until the
next agent restart in the event the protocol directory entry next agent restart in the event that the protocol directory
is deleted." entry is deleted."
::= { protocolDirEntry 3 } ::= { protocolDirEntry 3 }
protocolDirDescr OBJECT-TYPE protocolDirDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..64)) SYNTAX DisplayString (SIZE (1..64))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of the protocol encapsulation. "A textual description of the protocol encapsulation.
A probe may choose to describe only a subset of the A probe may choose to describe only a subset of the
entire encapsulation (e.g. only the highest layer). entire encapsulation (e.g., only the highest layer).
This object is intended for human consumption only. This object is intended for human consumption only.
This object may not be modified if the associated This object may not be modified if the associated
protocolDirStatus object is equal to active(1)." protocolDirStatus object is equal to active(1)."
::= { protocolDirEntry 4 } ::= { protocolDirEntry 4 }
protocolDirType OBJECT-TYPE protocolDirType OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
extensible(0), extensible(0),
addressRecognitionCapable(1) addressRecognitionCapable(1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object describes 2 attributes of this protocol "This object describes 2 attributes of this protocol
directory entry. directory entry.
The presence or absence of the `extensible' bit describes The presence or absence of the 'extensible' bit describes
whether or not this protocol directory entry can be extended whether this protocol directory entry can be extended
by the user by creating protocol directory entries which are by the user by creating protocol directory entries that are
children of this protocol. children of this protocol.
An example of an entry that will often allow extensibility is An example of an entry that will often allow extensibility is
`ip.udp'. The probe may automatically populate some children 'ip.udp'. The probe may automatically populate some children
of this node such as `ip.udp.snmp' and `ip.udp.dns'. of this node, such as 'ip.udp.snmp' and 'ip.udp.dns'.
A probe administrator or user may also populate additional A probe administrator or user may also populate additional
children via remote SNMP requests that create entries in this children via remote SNMP requests that create entries in this
table. When a child node is added for a protocol for which the table. When a child node is added for a protocol for which the
probe has no built in support, extending a parent node (for probe has no built-in support extending a parent node (for
which the probe does have built in support), which the probe does have built-in support),
that child node is not extendible. This is termed `limited that child node is not extendable. This is termed 'limited
extensibility'. extensibility'.
When a child node is added through this extensibility When a child node is added through this extensibility
mechanism, the values of protocolDirLocalIndex and mechanism, the values of protocolDirLocalIndex and
protocolDirType shall be assigned by the agent. protocolDirType shall be assigned by the agent.
The other objects in the entry will be assigned by the The other objects in the entry will be assigned by the
manager who is creating the new entry. manager who is creating the new entry.
This object also describes whether or not this agent can This object also describes whether this agent can
recognize addresses for this protocol, should it be a network recognize addresses for this protocol, should it be a
level protocol. That is, while a probe may be able to network-level protocol. That is, while a probe may be able
recognize packets of a particular network layer protocol and to recognize packets of a particular network-layer protocol
count them, it takes additional logic to be able to recognize and count them, it takes additional logic to be able to
the addresses in this protocol and to populate network layer recognize the addresses in this protocol and to populate
or application layer tables with the addresses in this network-layer or application-layer tables with the addresses
protocol. If this bit is set, the agent will recognize in this protocol. If this bit is set, the agent will
network layer addresses for this protoocl and populate the recognize network-layer addresses for this protocol and
network and application layer host and matrix tables with populate the network- and application-layer host and matrix
these protocols. tables with these protocols.
Note that when an entry is created, the agent will supply Note that when an entry is created, the agent will supply
values for the bits that match the capabilities of the agent values for the bits that match the capabilities of the agent
with respect to this protocol. Note that since row creations with respect to this protocol. Note that since row creations
usually exercise the limited extensibility feature, these usually exercise the limited extensibility feature, these
bits will usually be set to zero." bits will usually be set to zero."
::= { protocolDirEntry 5 } ::= { protocolDirEntry 5 }
protocolDirAddressMapConfig OBJECT-TYPE protocolDirAddressMapConfig OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 32, line 39 skipping to change at page 25, line 39
protocolDirHostConfig OBJECT-TYPE protocolDirHostConfig OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSupported(1), notSupported(1),
supportedOff(2), supportedOff(2),
supportedOn(3) supportedOn(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object describes and configures the probe's support for "This object describes and configures the probe's support for
the network layer and application layer host tables for this the network-layer and application-layer host tables for this
protocol. When the probe creates entries in this table for protocol. When the probe creates entries in this table for
all protocols that it understands, it will set the entry to all protocols that it understands, it will set the entry to
notSupported(1) if it doesn't have the capability to track the notSupported(1) if it doesn't have the capability to track the
nlHostTable for this protocol or if the alHostTable is nlHostTable for this protocol or if the alHostTable is
implemented but doesn't have the capability to track this implemented but doesn't have the capability to track this
protocol. Note that if the alHostTable is implemented, the protocol. Note that if the alHostTable is implemented, the
probe may only support a protocol if it is supported in both probe may only support a protocol if it is supported in both
the nlHostTable and the alHostTable. the nlHostTable and the alHostTable.
If the associated protocolDirType object has the If the associated protocolDirType object has the
addressRecognitionCapable bit set, then this is a network addressRecognitionCapable bit set, then this is a network-
layer protocol for which the probe recognizes addresses, and layer protocol for which the probe recognizes addresses, and
thus the probe will populate the nlHostTable and alHostTable thus the probe will populate the nlHostTable and alHostTable
with addresses it discovers for this protocol. with addresses it discovers for this protocol.
If the value of this object is notSupported(1), the probe If the value of this object is notSupported(1), the probe
will not track the nlHostTable or alHostTable for this will not track the nlHostTable or alHostTable for this
protocol and shall not allow this object to be changed to any protocol and shall not allow this object to be changed to any
other value. If the value of this object is supportedOn(3), other value. If the value of this object is supportedOn(3),
the probe supports tracking of the nlHostTable and alHostTable the probe supports tracking of the nlHostTable and alHostTable
for this protocol and is configured to track both tables for this protocol and is configured to track both tables
skipping to change at page 33, line 28 skipping to change at page 26, line 24
If the value of this object is supportedOff(2), the probe If the value of this object is supportedOff(2), the probe
supports tracking of the nlHostTable and alHostTable for this supports tracking of the nlHostTable and alHostTable for this
protocol but is configured to not track these tables protocol but is configured to not track these tables
for any control entries or interfaces. for any control entries or interfaces.
Whenever this value changes from supportedOn(3) to Whenever this value changes from supportedOn(3) to
supportedOff(2), the probe shall delete all related entries in supportedOff(2), the probe shall delete all related entries in
the nlHostTable and alHostTable. the nlHostTable and alHostTable.
Note that since each alHostEntry references 2 protocol Note that since each alHostEntry references 2 protocol
directory entries, one for the network address and one for the directory entries, one for the network address and one for the
type of the highest protocol recognized, that an entry will type of the highest protocol recognized, an entry will
only be created in that table if this value is supportedOn(3) only be created in that table if this value is supportedOn(3)
for both protocols." for both protocols."
::= { protocolDirEntry 7 } ::= { protocolDirEntry 7 }
protocolDirMatrixConfig OBJECT-TYPE protocolDirMatrixConfig OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSupported(1), notSupported(1),
supportedOff(2), supportedOff(2),
supportedOn(3) supportedOn(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object describes and configures the probe's support for "This object describes and configures the probe's support for
the network layer and application layer matrix tables for this the network-layer and application-layer matrix tables for this
protocol. When the probe creates entries in this table for protocol. When the probe creates entries in this table for
all protocols that it understands, it will set the entry to all protocols that it understands, it will set the entry to
notSupported(1) if it doesn't have the capability to track the notSupported(1) if it doesn't have the capability to track the
nlMatrixTables for this protocol or if the alMatrixTables are nlMatrixTables for this protocol or if the alMatrixTables are
implemented but don't have the capability to track this implemented but don't have the capability to track this
protocol. Note that if the alMatrix tables are implemented, protocol. Note that if the alMatrix tables are implemented,
the probe may only support a protocol if it is supported in the probe may only support a protocol if it is supported in
the the both of the nlMatrixTables and both of the both of the nlMatrixTables and both of the
alMatrixTables. alMatrixTables.
If the associated protocolDirType object has the If the associated protocolDirType object has the
addressRecognitionCapable bit set, then this is a network addressRecognitionCapable bit set, then this is a network-
layer protocol for which the probe recognizes addresses, and layer protocol for which the probe recognizes addresses, and
thus the probe will populate both of the nlMatrixTables and thus the probe will populate both of the nlMatrixTables and
both of the alMatrixTables with addresses it discovers for both of the alMatrixTables with addresses it discovers for
this protocol. this protocol.
If the value of this object is notSupported(1), the probe If the value of this object is notSupported(1), the probe
will not track either of the nlMatrixTables or the will not track either of the nlMatrixTables or the
alMatrixTables for this protocol and shall not allow this alMatrixTables for this protocol and shall not allow this
object to be changed to any other value. If the value of this object to be changed to any other value. If the value of this
object is supportedOn(3), the probe supports tracking of both object is supportedOn(3), the probe supports tracking of both
skipping to change at page 34, line 35 skipping to change at page 27, line 28
the probe supports tracking of both of the nlMatrixTables and the probe supports tracking of both of the nlMatrixTables and
(if implemented) both of the alMatrixTables for this protocol (if implemented) both of the alMatrixTables for this protocol
but is configured to not track these tables for this but is configured to not track these tables for this
protocol for any control entries or interfaces. protocol for any control entries or interfaces.
Whenever this value changes from supportedOn(3) to Whenever this value changes from supportedOn(3) to
supportedOff(2), the probe shall delete all related entries in supportedOff(2), the probe shall delete all related entries in
the nlMatrixTables and the alMatrixTables. the nlMatrixTables and the alMatrixTables.
Note that since each alMatrixEntry references 2 protocol Note that since each alMatrixEntry references 2 protocol
directory entries, one for the network address and one for the directory entries, one for the network address and one for the
type of the highest protocol recognized, that an entry will type of the highest protocol recognized, an entry will
only be created in that table if this value is supportedOn(3) only be created in that table if this value is supportedOn(3)
for both protocols." for both protocols."
::= { protocolDirEntry 8 } ::= { protocolDirEntry 8 }
protocolDirOwner OBJECT-TYPE protocolDirOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entity that configured this entry and is "The entity that configured this entry and is
skipping to change at page 35, line 48 skipping to change at page 28, line 38
interface upon initialization so that a default collection interface upon initialization so that a default collection
of protocol statistics is available. of protocol statistics is available.
Rationale: Rationale:
This table controls collection of very basic statistics This table controls collection of very basic statistics
for any or all of the protocols detected on a given interface. for any or all of the protocols detected on a given interface.
An NMS can use this table to quickly determine bandwidth An NMS can use this table to quickly determine bandwidth
allocation utilized by different protocols. allocation utilized by different protocols.
A media-specific statistics collection could also A media-specific statistics collection could also
be configured (e.g. etherStats, trPStats) to easily obtain be configured (e.g., etherStats, trPStats) to easily obtain
total frame, octet, and droppedEvents for the same total frame, octet, and droppedEvents for the same
interface." interface."
::= { protocolDist 1 } ::= { protocolDist 1 }
protocolDistControlEntry OBJECT-TYPE protocolDistControlEntry OBJECT-TYPE
SYNTAX ProtocolDistControlEntry SYNTAX ProtocolDistControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the protocolDistControlTable. "A conceptual row in the protocolDistControlTable.
skipping to change at page 37, line 14 skipping to change at page 29, line 43
This object may not be modified if the associated This object may not be modified if the associated
protocolDistControlStatus object is equal to active(1)." protocolDistControlStatus object is equal to active(1)."
::= { protocolDistControlEntry 2 } ::= { protocolDistControlEntry 2 }
protocolDistControlDroppedFrames OBJECT-TYPE protocolDistControlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the probe
is out of some resources and decides to shed load from this is out of some resources and decides to shed load from this
collection. collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { protocolDistControlEntry 3 } ::= { protocolDistControlEntry 3 }
skipping to change at page 38, line 24 skipping to change at page 30, line 50
entries in the protocolDistStatsTable shall be deleted." entries in the protocolDistStatsTable shall be deleted."
::= { protocolDistControlEntry 6 } ::= { protocolDistControlEntry 6 }
-- per interface protocol distribution statistics table -- per interface protocol distribution statistics table
protocolDistStatsTable OBJECT-TYPE protocolDistStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF ProtocolDistStatsEntry SYNTAX SEQUENCE OF ProtocolDistStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry is made in this table for every protocol in the "An entry is made in this table for every protocol in the
protocolDirTable which has been seen in at least one packet. protocolDirTable that has been seen in at least one packet.
Counters are updated in this table for every protocol type Counters are updated in this table for every protocol type
that is encountered when parsing a packet, but no counters are that is encountered when parsing a packet, but no counters are
updated for packets with MAC-layer errors. updated for packets with MAC-layer errors.
Note that if a protocolDirEntry is deleted, all associated Note that if a protocolDirEntry is deleted, all associated
entries in this table are removed." entries in this table are removed."
::= { protocolDist 2 } ::= { protocolDist 2 }
protocolDistStatsEntry OBJECT-TYPE protocolDistStatsEntry OBJECT-TYPE
SYNTAX ProtocolDistStatsEntry SYNTAX ProtocolDistStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the protocolDistStatsTable. "A conceptual row in the protocolDistStatsTable.
The index is composed of the protocolDistControlIndex of the The index is composed of the protocolDistControlIndex of the
associated protocolDistControlEntry followed by the associated protocolDistControlEntry, followed by the
protocolDirLocalIndex of the associated protocol that this protocolDirLocalIndex of the associated protocol that this
entry represents. In other words, the index identifies the entry represents. In other words, the index identifies the
protocol distribution an entry is a part of as well as the protocol distribution an entry is a part of and the
particular protocol that it represents. particular protocol that it represents.
An example of the indexing of this entry is An example of the indexing of this entry is
protocolDistStatsPkts.1.18" protocolDistStatsPkts.1.18"
INDEX { protocolDistControlIndex, protocolDirLocalIndex } INDEX { protocolDistControlIndex, protocolDirLocalIndex }
::= { protocolDistStatsTable 1 } ::= { protocolDistStatsTable 1 }
ProtocolDistStatsEntry ::= SEQUENCE { ProtocolDistStatsEntry ::= SEQUENCE {
protocolDistStatsPkts ZeroBasedCounter32, protocolDistStatsPkts ZeroBasedCounter32,
protocolDistStatsOctets ZeroBasedCounter32 protocolDistStatsOctets ZeroBasedCounter32
} }
protocolDistStatsPkts OBJECT-TYPE protocolDistStatsPkts OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets without errors received of this "The number of packets of this protocol type received
protocol type. Note that this is the number of link-layer without errors. Note that this is the number of
packets, so if a single network-layer packet is fragmented link-layer packets, so if a single network-layer packet
into several link-layer frames, this counter is incremented is fragmented into several link-layer frames, this counter
several times." is incremented several times."
::= { protocolDistStatsEntry 1 } ::= { protocolDistStatsEntry 1 }
protocolDistStatsOctets OBJECT-TYPE protocolDistStatsOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets in packets received of this protocol "The number of octets in packets of this protocol type
type since it was added to the protocolDistStatsTable received since it was added to the protocolDistStatsTable
(excluding framing bits but including FCS octets), except for (excluding framing bits, but including FCS octets), except for
those octets in packets that contained errors. those octets in packets that contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the
protocol frames, but includes the entire packet that contained particular protocol frames but includes the entire packet
the protocol." that contained the protocol."
::= { protocolDistStatsEntry 2 } ::= { protocolDistStatsEntry 2 }
-- --
-- Address Map Group (addressMap) -- Address Map Group (addressMap)
-- --
-- Lists MAC address to network address bindings discovered by the -- Lists MAC address to network address bindings discovered by the
-- probe and what interface they were last seen on. -- probe and what interface they were last seen on.
-- addressMapControlTable -- addressMapControlTable
-- addressMapTable -- addressMapTable
skipping to change at page 40, line 48 skipping to change at page 33, line 8
addressMapDeletes from addressMapInserts." addressMapDeletes from addressMapInserts."
::= { addressMap 2 } ::= { addressMap 2 }
addressMapMaxDesiredEntries OBJECT-TYPE addressMapMaxDesiredEntries OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of entries that are desired in the "The maximum number of entries that are desired in the
addressMapTable. The probe will not create more than addressMapTable. The probe will not create more than
this number of entries in the table, but may choose to create this number of entries in the table but may choose to create
fewer entries in this table for any reason including the lack fewer entries in this table for any reason, including the lack
of resources. of resources.
If this object is set to a value less than the current number If this object is set to a value less than the current number
of entries, enough entries are chosen in an of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object. of entries in the table equals the value of this object.
If this value is set to -1, the probe may create any number If this value is set to -1, the probe may create any number
of entries in this table. of entries in this table.
This object may be used to control how resources are allocated This object may be used to control how resources are allocated
on the probe for the various RMON functions." on the probe for the various RMON functions."
::= { addressMap 3 } ::= { addressMap 3 }
addressMapControlTable OBJECT-TYPE addressMapControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF AddressMapControlEntry SYNTAX SEQUENCE OF AddressMapControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table to control the collection of network layer address to "A table to control the collection of mappings from network
physical address to interface mappings. layer address to physical address to interface.
Note that this is not like the typical RMON Note that this is not like the typical RMON
controlTable and dataTable in which each entry creates controlTable and dataTable in which each entry creates
its own data table. Each entry in this table enables the its own data table. Each entry in this table enables the
discovery of addresses on a new interface and the placement discovery of addresses on a new interface and the placement
of address mappings into the central addressMapTable. of address mappings into the central addressMapTable.
Implementations are encouraged to add an entry per monitored Implementations are encouraged to add an entry per monitored
interface upon initialization so that a default collection interface upon initialization so that a default collection
of address mappings is available." of address mappings is available."
skipping to change at page 42, line 35 skipping to change at page 34, line 36
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The source of data for this addressMapControlEntry." "The source of data for this addressMapControlEntry."
::= { addressMapControlEntry 2 } ::= { addressMapControlEntry 2 }
addressMapControlDroppedFrames OBJECT-TYPE addressMapControlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the probe
is out of some resources and decides to shed load from this is out of some resources and decides to shed load from this
collection. collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { addressMapControlEntry 3 } ::= { addressMapControlEntry 3 }
skipping to change at page 43, line 33 skipping to change at page 35, line 30
If this object is not equal to active(1), all associated If this object is not equal to active(1), all associated
entries in the addressMapTable shall be deleted." entries in the addressMapTable shall be deleted."
::= { addressMapControlEntry 5 } ::= { addressMapControlEntry 5 }
addressMapTable OBJECT-TYPE addressMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF AddressMapEntry SYNTAX SEQUENCE OF AddressMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of network layer address to physical address to "A table of mappings from network layer address to physical
interface mappings. address to interface.
The probe will add entries to this table based on the source The probe will add entries to this table based on the source
MAC and network addresses seen in packets without MAC-level MAC and network addresses seen in packets without MAC-level
errors. The probe will populate this table for all protocols errors. The probe will populate this table for all protocols
in the protocol directory table whose value of in the protocol directory table whose value of
protocolDirAddressMapConfig is equal to supportedOn(3), and protocolDirAddressMapConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or will delete any entries whose protocolDirEntry is deleted or
has a protocolDirAddressMapConfig value of supportedOff(2)." has a protocolDirAddressMapConfig value of supportedOff(2)."
::= { addressMap 5 } ::= { addressMap 5 }
skipping to change at page 44, line 14 skipping to change at page 36, line 9
DESCRIPTION DESCRIPTION
"A conceptual row in the addressMapTable. "A conceptual row in the addressMapTable.
The protocolDirLocalIndex in the index identifies the network The protocolDirLocalIndex in the index identifies the network
layer protocol of the addressMapNetworkAddress. layer protocol of the addressMapNetworkAddress.
An example of the indexing of this entry is 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. addressMapSource.783495.18.4.128.2.6.6.11.1.3.6.1.2.1.2.2.1.1.1.
Note that some combinations of index values may result in an Note that some combinations of index values may result in an
index that exceeds 128 sub-identifiers in length which exceeds index that exceeds 128 sub-identifiers in length, which exceeds
the maximum for the SNMP protocol. Implementations should take the maximum for the SNMP protocol. Implementations should take
care to avoid such combinations." care to avoid such combinations."
INDEX { addressMapTimeMark, protocolDirLocalIndex, INDEX { addressMapTimeMark, protocolDirLocalIndex,
addressMapNetworkAddress, addressMapSource } addressMapNetworkAddress, addressMapSource }
::= { addressMapTable 1 } ::= { addressMapTable 1 }
AddressMapEntry ::= SEQUENCE { AddressMapEntry ::= SEQUENCE {
addressMapTimeMark TimeFilter, addressMapTimeMark TimeFilter,
addressMapNetworkAddress OCTET STRING, addressMapNetworkAddress OCTET STRING,
addressMapSource OBJECT IDENTIFIER, addressMapSource OBJECT IDENTIFIER,
skipping to change at page 45, line 8 skipping to change at page 36, line 47
DESCRIPTION DESCRIPTION
"The network address for this relation. "The network address for this relation.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the protocolDirLocalIndex component of the by the protocolDirLocalIndex component of the
index. index.
For example, if the protocolDirLocalIndex indicates an For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address, octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { addressMapEntry 2 } ::= { addressMapEntry 2 }
addressMapSource OBJECT-TYPE addressMapSource OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface or port on which the associated network "The interface or port on which the associated network
address was most recently seen. address was most recently seen.
skipping to change at page 45, line 36 skipping to change at page 37, line 26
If this address mapping was discovered on a port, this If this address mapping was discovered on a port, this
object shall identify the instance of the rptrGroupPortIndex object shall identify the instance of the rptrGroupPortIndex
object, defined in [RFC2108], for the desired port. object, defined in [RFC2108], for the desired port.
For example, if an entry were to receive data from For example, if an entry were to receive data from
group #1, port #1, this object would be set to group #1, port #1, this object would be set to
rptrGroupPortIndex.1.1. rptrGroupPortIndex.1.1.
Note that while the dataSource associated with this entry Note that while the dataSource associated with this entry
may only point to index objects, this object may at times may only point to index objects, this object may at times
point to repeater port objects. This situation occurs when point to repeater port objects. This situation occurs when
the dataSource points to an interface which is a locally the dataSource points to an interface that is a locally
attached repeater and the agent has additional information attached repeater and the agent has additional information
about the source port of traffic seen on that repeater." about the source port of traffic seen on that repeater."
::= { addressMapEntry 3 } ::= { addressMapEntry 3 }
addressMapPhysicalAddress OBJECT-TYPE addressMapPhysicalAddress OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last source physical address on which the associated "The last source physical address on which the associated
skipping to change at page 47, line 19 skipping to change at page 38, line 23
-- discovered by the probe. -- discovered by the probe.
-- Note that while the hlHostControlTable also has objects that -- Note that while the hlHostControlTable also has objects that
-- control an optional alHostTable, implementation of the alHostTable is -- control an optional alHostTable, implementation of the alHostTable is
-- not required to fully implement this group. -- not required to fully implement this group.
hlHostControlTable OBJECT-TYPE hlHostControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF HlHostControlEntry SYNTAX SEQUENCE OF HlHostControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of higher layer (i.e. non-MAC) host table control "A list of higher-layer (i.e., non-MAC) host table control
entries. entries.
These entries will enable the collection of the network and These entries will enable the collection of the network- and
application level host tables indexed by network addresses. application-level host tables indexed by network addresses.
Both the network and application level host tables are Both the network- and application-level host tables are
controlled by this table is so that they will both be created controlled by this table so that they will both be created
and deleted at the same time, further increasing the ease with and deleted at the same time, further increasing the ease with
which they can be implemented as a single datastore (note that which they can be implemented as a single datastore. (Note that
if an implementation stores application layer host records in if an implementation stores application-layer host records in
memory, it can derive network layer host records from them). memory, it can derive network-layer host records from them.)
Entries in the nlHostTable will be created on behalf of each Entries in the nlHostTable will be created on behalf of each
entry in this table. Additionally, if this probe implements entry in this table. Additionally, if this probe implements
the alHostTable, entries in the alHostTable will be created on the alHostTable, entries in the alHostTable will be created on
behalf of each entry in this table. behalf of each entry in this table.
Implementations are encouraged to add an entry per monitored Implementations are encouraged to add an entry per monitored
interface upon initialization so that a default collection interface upon initialization so that a default collection
of host statistics is available." of host statistics is available."
::= { nlHost 1 } ::= { nlHost 1 }
skipping to change at page 49, line 12 skipping to change at page 40, line 8
This object may not be modified if the associated This object may not be modified if the associated
hlHostControlStatus object is equal to active(1)." hlHostControlStatus object is equal to active(1)."
::= { hlHostControlEntry 2 } ::= { hlHostControlEntry 2 }
hlHostControlNlDroppedFrames OBJECT-TYPE hlHostControlNlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for the associated that the probe chose not to count for the associated
nlHost entries for whatever reason. Most often, this event nlHost entries for whatever reason. Most often, this event
occurs when the probe is out of some resources and decides to occurs when the probe is out of some resources and decides to
shed load from this collection. shed load from this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that if the nlHostTable is inactive because no protocols Note that if the nlHostTable is inactive because no protocols
are enabled in the protocol directory, this value should be 0. are enabled in the protocol directory, this value should be 0.
skipping to change at page 50, line 35 skipping to change at page 41, line 27
::= { hlHostControlEntry 5 } ::= { hlHostControlEntry 5 }
hlHostControlNlMaxDesiredEntries OBJECT-TYPE hlHostControlNlMaxDesiredEntries OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of entries that are desired in the "The maximum number of entries that are desired in the
nlHostTable on behalf of this control entry. The probe will nlHostTable on behalf of this control entry. The probe will
not create more than this number of associated entries in the not create more than this number of associated entries in the
table, but may choose to create fewer entries in this table table but may choose to create fewer entries in this table
for any reason including the lack of resources. for any reason, including the lack of resources.
If this object is set to a value less than the current number If this object is set to a value less than the current number
of entries, enough entries are chosen in an of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object. of entries in the table equals the value of this object.
If this value is set to -1, the probe may create any number If this value is set to -1, the probe may create any number
of entries in this table. If the associated of entries in this table. If the associated
hlHostControlStatus object is equal to `active', this hlHostControlStatus object is equal to 'active', this
object may not be modified. object may not be modified.
This object may be used to control how resources are allocated This object may be used to control how resources are allocated
on the probe for the various RMON functions." on the probe for the various RMON functions."
::= { hlHostControlEntry 6 } ::= { hlHostControlEntry 6 }
hlHostControlAlDroppedFrames OBJECT-TYPE hlHostControlAlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for the associated that the probe chose not to count for the associated
alHost entries for whatever reason. Most often, this event alHost entries for whatever reason. Most often, this event
occurs when the probe is out of some resources and decides to occurs when the probe is out of some resources and decides to
shed load from this collection. shed load from this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that if the alHostTable is not implemented or is inactive Note that if the alHostTable is not implemented or is inactive
because no protocols are enabled in the protocol directory, because no protocols are enabled in the protocol directory,
this value should be 0. this value should be 0.
skipping to change at page 52, line 38 skipping to change at page 43, line 21
::= { hlHostControlEntry 9 } ::= { hlHostControlEntry 9 }
hlHostControlAlMaxDesiredEntries OBJECT-TYPE hlHostControlAlMaxDesiredEntries OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of entries that are desired in the alHost "The maximum number of entries that are desired in the alHost
table on behalf of this control entry. The probe will not table on behalf of this control entry. The probe will not
create more than this number of associated entries in the create more than this number of associated entries in the
table, but may choose to create fewer entries in this table table but may choose to create fewer entries in this table
for any reason including the lack of resources. for any reason, including the lack of resources.
If this object is set to a value less than the current number If this object is set to a value less than the current number
of entries, enough entries are chosen in an of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object. of entries in the table equals the value of this object.
If this value is set to -1, the probe may create any number If this value is set to -1, the probe may create any number
of entries in this table. If the associated of entries in this table. If the associated
hlHostControlStatus object is equal to `active', this hlHostControlStatus object is equal to 'active', this
object may not be modified. object may not be modified.
This object may be used to control how resources are allocated This object may be used to control how resources are allocated
on the probe for the various RMON functions." on the probe for the various RMON functions."
::= { hlHostControlEntry 10 } ::= { hlHostControlEntry 10 }
hlHostControlOwner OBJECT-TYPE hlHostControlOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 54, line 27 skipping to change at page 44, line 50
The hlHostControlIndex value in the index identifies the The hlHostControlIndex value in the index identifies the
hlHostControlEntry on whose behalf this entry was created. hlHostControlEntry on whose behalf this entry was created.
The protocolDirLocalIndex value in the index identifies the The protocolDirLocalIndex value in the index identifies the
network layer protocol of the nlHostAddress. network layer protocol of the nlHostAddress.
An example of the indexing of this entry is An example of the indexing of this entry is
nlHostOutPkts.1.783495.18.4.128.2.6.6. nlHostOutPkts.1.783495.18.4.128.2.6.6.
Note that some combinations of index values may result in an Note that some combinations of index values may result in an
index that exceeds 128 sub-identifiers in length which exceeds index that exceeds 128 sub-identifiers in length, which exceeds
the maximum for the SNMP protocol. Implementations should take the maximum for the SNMP protocol. Implementations should take
care to avoid such combinations." care to avoid such combinations."
INDEX { hlHostControlIndex, nlHostTimeMark, INDEX { hlHostControlIndex, nlHostTimeMark,
protocolDirLocalIndex, nlHostAddress } protocolDirLocalIndex, nlHostAddress }
::= { nlHostTable 1 } ::= { nlHostTable 1 }
NlHostEntry ::= SEQUENCE { NlHostEntry ::= SEQUENCE {
nlHostTimeMark TimeFilter, nlHostTimeMark TimeFilter,
nlHostAddress OCTET STRING, nlHostAddress OCTET STRING,
nlHostInPkts ZeroBasedCounter32, nlHostInPkts ZeroBasedCounter32,
skipping to change at page 55, line 21 skipping to change at page 45, line 41
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network address for this nlHostEntry. "The network address for this nlHostEntry.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the protocolDirLocalIndex component of the index. by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length encapsulation of IP, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address, octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { nlHostEntry 2 } ::= { nlHostEntry 2 }
nlHostInPkts OBJECT-TYPE nlHostInPkts OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets without errors transmitted to "The number of packets without errors transmitted to
this address since it was added to the nlHostTable. Note that this address since it was added to the nlHostTable. Note that
skipping to change at page 56, line 13 skipping to change at page 46, line 29
frames, this counter is incremented several times." frames, this counter is incremented several times."
::= { nlHostEntry 4 } ::= { nlHostEntry 4 }
nlHostInOctets OBJECT-TYPE nlHostInOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets transmitted to this address "The number of octets transmitted to this address
since it was added to the nlHostTable (excluding since it was added to the nlHostTable (excluding
framing bits but including FCS octets), excluding framing bits, but including FCS octets), excluding
those octets in packets that contained errors. octets in packets that contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained protocol frames but includes the entire packet that contained
the protocol." the protocol."
::= { nlHostEntry 5 } ::= { nlHostEntry 5 }
nlHostOutOctets OBJECT-TYPE nlHostOutOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets transmitted by this address "The number of octets transmitted by this address
since it was added to the nlHostTable (excluding since it was added to the nlHostTable (excluding
framing bits but including FCS octets), excluding framing bits, but including FCS octets), excluding
those octets in packets that contained errors. octets in packets that contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained protocol frames but includes the entire packet that contained
the protocol." the protocol."
::= { nlHostEntry 6 } ::= { nlHostEntry 6 }
nlHostOutMacNonUnicastPkts OBJECT-TYPE nlHostOutMacNonUnicastPkts OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets without errors transmitted by this "The number of packets without errors transmitted by this
address that were directed to any MAC broadcast addresses address that were directed to any MAC broadcast addresses
skipping to change at page 58, line 19 skipping to change at page 47, line 43
-- addresses discovered by the probe. -- addresses discovered by the probe.
-- Note that while the hlMatrixControlTable also has objects that -- Note that while the hlMatrixControlTable also has objects that
-- control optional alMatrixTables, implementation of the -- control optional alMatrixTables, implementation of the
-- alMatrixTables is not required to fully implement this group. -- alMatrixTables is not required to fully implement this group.
hlMatrixControlTable OBJECT-TYPE hlMatrixControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF HlMatrixControlEntry SYNTAX SEQUENCE OF HlMatrixControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of higher layer (i.e. non-MAC) matrix control entries. "A list of higher-layer (i.e., non-MAC) matrix control entries.
These entries will enable the collection of the network and These entries will enable the collection of the network- and
application level matrix tables containing conversation application-level matrix tables containing conversation
statistics indexed by pairs of network addresses. statistics indexed by pairs of network addresses.
Both the network and application level matrix tables are Both the network- and application-level matrix tables are
controlled by this table is so that they will both be created controlled by this table so that they will both be created
and deleted at the same time, further increasing the ease with and deleted at the same time, further increasing the ease with
which they can be implemented as a single datastore (note that which they can be implemented as a single datastore. (Note that
if an implementation stores application layer matrix records if an implementation stores application-layer matrix records
in memory, it can derive network layer matrix records from in memory, it can derive network-layer matrix records from
them). them.)
Entries in the nlMatrixSDTable and nlMatrixDSTable will be Entries in the nlMatrixSDTable and nlMatrixDSTable will be
created on behalf of each entry in this table. Additionally, created on behalf of each entry in this table. Additionally,
if this probe implements the alMatrix tables, entries in the if this probe implements the alMatrix tables, entries in the
alMatrix tables will be created on behalf of each entry in alMatrix tables will be created on behalf of each entry in
this table." this table."
::= { nlMatrix 1 } ::= { nlMatrix 1 }
hlMatrixControlEntry OBJECT-TYPE hlMatrixControlEntry OBJECT-TYPE
SYNTAX HlMatrixControlEntry SYNTAX HlMatrixControlEntry
skipping to change at page 60, line 11 skipping to change at page 49, line 27
This object may not be modified if the associated This object may not be modified if the associated
hlMatrixControlStatus object is equal to active(1)." hlMatrixControlStatus object is equal to active(1)."
::= { hlMatrixControlEntry 2 } ::= { hlMatrixControlEntry 2 }
hlMatrixControlNlDroppedFrames OBJECT-TYPE hlMatrixControlNlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the probe
is out of some resources and decides to shed load from this is out of some resources and decides to shed load from this
collection. collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that if the nlMatrixTables are inactive because no Note that if the nlMatrixTables are inactive because no
protocols are enabled in the protocol directory, this value protocols are enabled in the protocol directory, this value
should be 0. should be 0.
skipping to change at page 61, line 43 skipping to change at page 51, line 7
::= { hlMatrixControlEntry 5 } ::= { hlMatrixControlEntry 5 }
hlMatrixControlNlMaxDesiredEntries OBJECT-TYPE hlMatrixControlNlMaxDesiredEntries OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of entries that are desired in the "The maximum number of entries that are desired in the
nlMatrix tables on behalf of this control entry. The probe nlMatrix tables on behalf of this control entry. The probe
will not create more than this number of associated entries in will not create more than this number of associated entries in
the table, but may choose to create fewer entries in this the table but may choose to create fewer entries in this
table for any reason including the lack of resources. table for any reason, including the lack of resources.
If this object is set to a value less than the current number If this object is set to a value less than the current number
of entries, enough entries are chosen in an of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object. of entries in the table equals the value of this object.
If this value is set to -1, the probe may create any number If this value is set to -1, the probe may create any number
of entries in this table. If the associated of entries in this table. If the associated
hlMatrixControlStatus object is equal to `active', this hlMatrixControlStatus object is equal to 'active', this
object may not be modified. object may not be modified.
This object may be used to control how resources are allocated This object may be used to control how resources are allocated
on the probe for the various RMON functions." on the probe for the various RMON functions."
::= { hlMatrixControlEntry 6 } ::= { hlMatrixControlEntry 6 }
hlMatrixControlAlDroppedFrames OBJECT-TYPE hlMatrixControlAlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the probe
is out of some resources and decides to shed load from this is out of some resources and decides to shed load from this
collection. collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that if the alMatrixTables are not implemented or are Note that if the alMatrixTables are not implemented or are
inactive because no protocols are enabled in the protocol inactive because no protocols are enabled in the protocol
directory, this value should be 0. directory, this value should be 0.
skipping to change at page 64, line 6 skipping to change at page 53, line 7
::= { hlMatrixControlEntry 9 } ::= { hlMatrixControlEntry 9 }
hlMatrixControlAlMaxDesiredEntries OBJECT-TYPE hlMatrixControlAlMaxDesiredEntries OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of entries that are desired in the "The maximum number of entries that are desired in the
alMatrix tables on behalf of this control entry. The probe alMatrix tables on behalf of this control entry. The probe
will not create more than this number of associated entries in will not create more than this number of associated entries in
the table, but may choose to create fewer entries in this the table but may choose to create fewer entries in this
table for any reason including the lack of resources. table for any reason, including the lack of resources.
If this object is set to a value less than the current number If this object is set to a value less than the current number
of entries, enough entries are chosen in an of entries, enough entries are chosen in an
implementation-dependent manner and deleted so that the number implementation-dependent manner and deleted so that the number
of entries in the table equals the value of this object. of entries in the table equals the value of this object.
If this value is set to -1, the probe may create any number If this value is set to -1, the probe may create any number
of entries in this table. If the associated of entries in this table. If the associated
hlMatrixControlStatus object is equal to `active', this hlMatrixControlStatus object is equal to 'active', this
object may not be modified. object may not be modified.
This object may be used to control how resources are allocated This object may be used to control how resources are allocated
on the probe for the various RMON functions." on the probe for the various RMON functions."
::= { hlMatrixControlEntry 10 } ::= { hlMatrixControlEntry 10 }
hlMatrixControlOwner OBJECT-TYPE hlMatrixControlOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 64, line 44 skipping to change at page 53, line 45
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this hlMatrixControlEntry. "The status of this hlMatrixControlEntry.
An entry may not exist in the active state unless all An entry may not exist in the active state unless all
objects in the entry have an appropriate value. objects in the entry have an appropriate value.
If this object is not equal to active(1), all If this object is not equal to active(1), all
associated entries in the nlMatrixSDTable, associated entries in the nlMatrixSDTable,
nlMatrixDSTable, alMatrixSDTable, and the alMatrixDSTable nlMatrixDSTable, alMatrixSDTable, and alMatrixDSTable
shall be deleted by the agent." shall be deleted by the agent."
::= { hlMatrixControlEntry 12 } ::= { hlMatrixControlEntry 12 }
nlMatrixSDTable OBJECT-TYPE nlMatrixSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF NlMatrixSDEntry SYNTAX SEQUENCE OF NlMatrixSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of traffic matrix entries which collect statistics for "A list of traffic matrix entries that collect statistics for
conversations between two network-level addresses. This table conversations between two network-level addresses. This table
is indexed first by the source address and then by the is indexed first by the source address and then by the
destination address to make it convenient to collect all destination address to make it convenient to collect all
conversations from a particular address. conversations from a particular address.
The probe will populate this table for all network layer The probe will populate this table for all network layer
protocols in the protocol directory table whose value of protocols in the protocol directory table whose value of
protocolDirMatrixConfig is equal to supportedOn(3), and protocolDirMatrixConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or will delete any entries whose protocolDirEntry is deleted or
has a protocolDirMatrixConfig value of supportedOff(2). has a protocolDirMatrixConfig value of supportedOff(2).
The probe will add to this table all pairs of addresses The probe will add to this table all pairs of addresses
seen in all packets with no MAC errors, and will increment seen in all packets with no MAC errors and will increment
octet and packet counts in the table for all packets with no octet and packet counts in the table for all packets with no
MAC errors. MAC errors.
Further, this table will only contain entries that have a Further, this table will only contain entries that have a
corresponding entry in the nlMatrixDSTable with the same corresponding entry in the nlMatrixDSTable with the same
source address and destination address." source address and destination address."
::= { nlMatrix 2 } ::= { nlMatrix 2 }
nlMatrixSDEntry OBJECT-TYPE nlMatrixSDEntry OBJECT-TYPE
SYNTAX NlMatrixSDEntry SYNTAX NlMatrixSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the nlMatrixSDTable. "A conceptual row in the nlMatrixSDTable.
The hlMatrixControlIndex value in the index identifies the The hlMatrixControlIndex value in the index identifies the
hlMatrixControlEntry on whose behalf this entry was created. hlMatrixControlEntry on whose behalf this entry was created.
The protocolDirLocalIndex value in the index identifies the The protocolDirLocalIndex value in the index identifies the
network layer protocol of the nlMatrixSDSourceAddress and network-layer protocol of the nlMatrixSDSourceAddress and
nlMatrixSDDestAddress. nlMatrixSDDestAddress.
An example of the indexing of this table is An example of the indexing of this table is
nlMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7. nlMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7.
Note that some combinations of index values may result in an Note that some combinations of index values may result in an
index that exceeds 128 sub-identifiers in length which exceeds index that exceeds 128 sub-identifiers in length, which exceeds
the maximum for the SNMP protocol. Implementations should take the maximum for the SNMP protocol. Implementations should take
care to avoid such combinations." care to avoid such combinations."
INDEX { hlMatrixControlIndex, nlMatrixSDTimeMark, INDEX { hlMatrixControlIndex, nlMatrixSDTimeMark,
protocolDirLocalIndex, protocolDirLocalIndex,
nlMatrixSDSourceAddress, nlMatrixSDDestAddress } nlMatrixSDSourceAddress, nlMatrixSDDestAddress }
::= { nlMatrixSDTable 1 } ::= { nlMatrixSDTable 1 }
NlMatrixSDEntry ::= SEQUENCE { NlMatrixSDEntry ::= SEQUENCE {
nlMatrixSDTimeMark TimeFilter, nlMatrixSDTimeMark TimeFilter,
nlMatrixSDSourceAddress OCTET STRING, nlMatrixSDSourceAddress OCTET STRING,
skipping to change at page 66, line 42 skipping to change at page 55, line 35
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network source address for this nlMatrixSDEntry. "The network source address for this nlMatrixSDEntry.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the protocolDirLocalIndex component of the index. by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length encapsulation of IP, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address, octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { nlMatrixSDEntry 2 } ::= { nlMatrixSDEntry 2 }
nlMatrixSDDestAddress OBJECT-TYPE nlMatrixSDDestAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network destination address for this "The network destination address for this
nlMatrixSDEntry. nlMatrixSDEntry.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the protocolDirLocalIndex component of the index. by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length encapsulation of IP, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address, octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { nlMatrixSDEntry 3 } ::= { nlMatrixSDEntry 3 }
nlMatrixSDPkts OBJECT-TYPE nlMatrixSDPkts OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets without errors transmitted from the "The number of packets without errors transmitted from the
source address to the destination address since this entry was source address to the destination address since this entry was
skipping to change at page 67, line 41 skipping to change at page 56, line 29
incremented several times." incremented several times."
::= { nlMatrixSDEntry 4 } ::= { nlMatrixSDEntry 4 }
nlMatrixSDOctets OBJECT-TYPE nlMatrixSDOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets transmitted from the source address to "The number of octets transmitted from the source address to
the destination address since this entry was added to the the destination address since this entry was added to the
nlMatrixSDTable (excluding framing bits but nlMatrixSDTable (excluding framing bits, but
including FCS octets), excluding those octets in packets that including FCS octets), excluding octets in packets that
contained errors. contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained protocol frames but includes the entire packet that contained
the protocol." the protocol."
::= { nlMatrixSDEntry 5 } ::= { nlMatrixSDEntry 5 }
nlMatrixSDCreateTime OBJECT-TYPE nlMatrixSDCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this entry was last activated. "The value of sysUpTime when this entry was last activated.
This can be used by the management station to ensure that the This can be used by the management station to ensure that the
entry has not been deleted and recreated between polls." entry has not been deleted and recreated between polls."
::= { nlMatrixSDEntry 6 } ::= { nlMatrixSDEntry 6 }
-- Traffic matrix tables from destination to source -- Traffic matrix tables from destination to source
nlMatrixDSTable OBJECT-TYPE nlMatrixDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF NlMatrixDSEntry SYNTAX SEQUENCE OF NlMatrixDSEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of traffic matrix entries which collect statistics for "A list of traffic matrix entries that collect statistics for
conversations between two network-level addresses. This table conversations between two network-level addresses. This table
is indexed first by the destination address and then by the is indexed first by the destination address and then by the
source address to make it convenient to collect all source address to make it convenient to collect all
conversations to a particular address. conversations to a particular address.
The probe will populate this table for all network layer The probe will populate this table for all network layer
protocols in the protocol directory table whose value of protocols in the protocol directory table whose value of
protocolDirMatrixConfig is equal to supportedOn(3), and protocolDirMatrixConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or will delete any entries whose protocolDirEntry is deleted or
has a protocolDirMatrixConfig value of supportedOff(2). has a protocolDirMatrixConfig value of supportedOff(2).
The probe will add to this table all pairs of addresses The probe will add to this table all pairs of addresses
seen in all packets with no MAC errors, and will increment seen in all packets with no MAC errors and will increment
octet and packet counts in the table for all packets with no octet and packet counts in the table for all packets with no
MAC errors. MAC errors.
Further, this table will only contain entries that have a Further, this table will only contain entries that have a
corresponding entry in the nlMatrixSDTable with the same corresponding entry in the nlMatrixSDTable with the same
source address and destination address." source address and destination address."
::= { nlMatrix 3 } ::= { nlMatrix 3 }
nlMatrixDSEntry OBJECT-TYPE nlMatrixDSEntry OBJECT-TYPE
SYNTAX NlMatrixDSEntry SYNTAX NlMatrixDSEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the nlMatrixDSTable. "A conceptual row in the nlMatrixDSTable.
The hlMatrixControlIndex value in the index identifies the The hlMatrixControlIndex value in the index identifies the
hlMatrixControlEntry on whose behalf this entry was created. hlMatrixControlEntry on whose behalf this entry was created.
The protocolDirLocalIndex value in the index identifies the The protocolDirLocalIndex value in the index identifies the
network layer protocol of the nlMatrixDSSourceAddress and network-layer protocol of the nlMatrixDSSourceAddress and
nlMatrixDSDestAddress. nlMatrixDSDestAddress.
An example of the indexing of this table is An example of the indexing of this table is
nlMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6. nlMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6.
Note that some combinations of index values may result in an Note that some combinations of index values may result in an
index that exceeds 128 sub-identifiers in length which exceeds index that exceeds 128 sub-identifiers in length, which exceeds
the maximum for the SNMP protocol. Implementations should take the maximum for the SNMP protocol. Implementations should take
care to avoid such combinations." care to avoid such combinations."
INDEX { hlMatrixControlIndex, nlMatrixDSTimeMark, INDEX { hlMatrixControlIndex, nlMatrixDSTimeMark,
protocolDirLocalIndex, protocolDirLocalIndex,
nlMatrixDSDestAddress, nlMatrixDSSourceAddress } nlMatrixDSDestAddress, nlMatrixDSSourceAddress }
::= { nlMatrixDSTable 1 } ::= { nlMatrixDSTable 1 }
NlMatrixDSEntry ::= SEQUENCE { NlMatrixDSEntry ::= SEQUENCE {
nlMatrixDSTimeMark TimeFilter, nlMatrixDSTimeMark TimeFilter,
nlMatrixDSSourceAddress OCTET STRING, nlMatrixDSSourceAddress OCTET STRING,
skipping to change at page 70, line 13 skipping to change at page 58, line 37
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network source address for this nlMatrixDSEntry. "The network source address for this nlMatrixDSEntry.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the protocolDirLocalIndex component of the index. by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length encapsulation of IP, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address, octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { nlMatrixDSEntry 2 } ::= { nlMatrixDSEntry 2 }
nlMatrixDSDestAddress OBJECT-TYPE nlMatrixDSDestAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network destination address for this "The network destination address for this
nlMatrixDSEntry. nlMatrixDSEntry.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the protocolDirLocalIndex component of the index. by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length encapsulation of IP, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address, octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { nlMatrixDSEntry 3 } ::= { nlMatrixDSEntry 3 }
nlMatrixDSPkts OBJECT-TYPE nlMatrixDSPkts OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets without errors transmitted from the "The number of packets without errors transmitted from the
source address to the destination address since this entry was source address to the destination address since this entry was
skipping to change at page 71, line 12 skipping to change at page 59, line 32
incremented several times." incremented several times."
::= { nlMatrixDSEntry 4 } ::= { nlMatrixDSEntry 4 }
nlMatrixDSOctets OBJECT-TYPE nlMatrixDSOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets transmitted from the source address "The number of octets transmitted from the source address
to the destination address since this entry was added to the to the destination address since this entry was added to the
nlMatrixDSTable (excluding framing bits but nlMatrixDSTable (excluding framing bits, but
including FCS octets), excluding those octets in packets that including FCS octets), excluding octets in packets that
contained errors. contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained protocol frames but includes the entire packet that contained
the protocol." the protocol."
::= { nlMatrixDSEntry 5 } ::= { nlMatrixDSEntry 5 }
nlMatrixDSCreateTime OBJECT-TYPE nlMatrixDSCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this entry was last activated. "The value of sysUpTime when this entry was last activated.
This can be used by the management station to ensure that the This can be used by the management station to ensure that the
skipping to change at page 73, line 40 skipping to change at page 62, line 4
nlMatrixTopNControlTimeRemaining OBJECT-TYPE nlMatrixTopNControlTimeRemaining OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds left in the report currently "The number of seconds left in the report currently
being collected. When this object is modified by being collected. When this object is modified by
the management station, a new collection is started, the management station, a new collection is started,
possibly aborting a currently running report. The possibly aborting a currently running report. The
new value is used as the requested duration of this new value is used as the requested duration of this
report, and is immediately loaded into the associated report and is immediately loaded into the associated
nlMatrixTopNControlDuration object. nlMatrixTopNControlDuration object.
When the report finishes, the probe will automatically When the report finishes, the probe will automatically
start another collection with the same initial value start another collection with the same initial value
of nlMatrixTopNControlTimeRemaining. Thus the management of nlMatrixTopNControlTimeRemaining. Thus, the management
station may simply read the resulting reports repeatedly, station may simply read the resulting reports repeatedly,
checking the startTime and duration each time to ensure that a checking the startTime and duration each time to ensure that a
report was not missed or that the report parameters were not report was not missed or that the report parameters were not
changed. changed.
While the value of this object is non-zero, it decrements While the value of this object is non-zero, it decrements
by one per second until it reaches zero. At the time by one per second until it reaches zero. At the time
that this object decrements to zero, the report is made that this object decrements to zero, the report is made
accessible in the nlMatrixTopNTable, overwriting any report accessible in the nlMatrixTopNTable, overwriting any report
that may be there. that may be there.
When this object is modified by the management station, any When this object is modified by the management station, any
associated entries in the nlMatrixTopNTable shall be deleted. associated entries in the nlMatrixTopNTable shall be deleted.
(Note that this is a different algorithm than the one used in (Note that this is a different algorithm than the one used
the hostTopNTable)." in the hostTopNTable)."
DEFVAL { 1800 } DEFVAL { 1800 }
::= { nlMatrixTopNControlEntry 4 } ::= { nlMatrixTopNControlEntry 4 }
nlMatrixTopNControlGeneratedReports OBJECT-TYPE nlMatrixTopNControlGeneratedReports OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of reports that have been generated by this entry." "The number of reports that have been generated by this entry."
::= { nlMatrixTopNControlEntry 5 } ::= { nlMatrixTopNControlEntry 5 }
skipping to change at page 75, line 8 skipping to change at page 63, line 15
nlMatrixTopNControlRequestedSize OBJECT-TYPE nlMatrixTopNControlRequestedSize OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of matrix entries requested for this report. "The maximum number of matrix entries requested for this report.
When this object is created or modified, the probe When this object is created or modified, the probe
should set nlMatrixTopNControlGrantedSize as closely to this should set nlMatrixTopNControlGrantedSize as closely to this
object as is possible for the particular probe object as possible for the particular probe
implementation and available resources." implementation and available resources."
DEFVAL { 150 } DEFVAL { 150 }
::= { nlMatrixTopNControlEntry 7 } ::= { nlMatrixTopNControlEntry 7 }
nlMatrixTopNControlGrantedSize OBJECT-TYPE nlMatrixTopNControlGrantedSize OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of matrix entries in this report. "The maximum number of matrix entries in this report.
When the associated nlMatrixTopNControlRequestedSize object is When the associated nlMatrixTopNControlRequestedSize object is
created or modified, the probe should set this created or modified, the probe should set this
object as closely to the requested value as is object as closely to the requested value as
possible for the particular implementation and possible for the particular implementation and
available resources. The probe must not lower this available resources. The probe must not lower this
value except as a result of a set to the associated value except as a side-effect of a set to the associated
nlMatrixTopNControlRequestedSize object. nlMatrixTopNControlRequestedSize object.
If the value of nlMatrixTopNControlRateBase is equal to If the value of nlMatrixTopNControlRateBase is equal to
nlMatrixTopNPkts, when the next topN report is generated, nlMatrixTopNPkts, when the next topN report is generated,
matrix entries with the highest value of nlMatrixTopNPktRate matrix entries with the highest value of nlMatrixTopNPktRate
shall be placed in this table in decreasing order of this rate shall be placed in this table in decreasing order of this rate
until there is no more room or until there are no more until there is no more room or until there are no more
matrix entries. matrix entries.
If the value of nlMatrixTopNControlRateBase is equal to If the value of nlMatrixTopNControlRateBase is equal to
nlMatrixTopNOctets, when the next topN report is generated, nlMatrixTopNOctets, when the next topN report is generated,
matrix entries with the highest value of nlMatrixTopNOctetRate matrix entries with the highest value of nlMatrixTopNOctetRate
shall be placed in this table in decreasing order of this rate shall be placed in this table in decreasing order of this rate
until there is no more room or until there are no more until there is no more room or until there are no more
matrix entries. matrix entries.
It is an implementation-specific matter how entries with the It is an implementation-specific matter how entries with the
same value of nlMatrixTopNPktRate or nlMatrixTopNOctetRate are same value of nlMatrixTopNPktRate or nlMatrixTopNOctetRate are
sorted. It is also an implementation-specific matter as to sorted. It is also an implementation-specific matter as to
whether or not zero-valued entries are available." whether zero-valued entries are available."
::= { nlMatrixTopNControlEntry 8 } ::= { nlMatrixTopNControlEntry 8 }
nlMatrixTopNControlStartTime OBJECT-TYPE nlMatrixTopNControlStartTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this top N report was "The value of sysUpTime when this top N report was
last started. In other words, this is the time that last started. In other words, this is the time that
the associated nlMatrixTopNControlTimeRemaining object was the associated nlMatrixTopNControlTimeRemaining object was
modified to start the requested report or the time modified to start the requested report or the time
the report was last automatically (re)started. the report was last automatically (re)started.
This object may be used by the management station to This object may be used by the management station to
determine if a report was missed or not." determine whether a report was missed."
::= { nlMatrixTopNControlEntry 9 } ::= { nlMatrixTopNControlEntry 9 }
nlMatrixTopNControlOwner OBJECT-TYPE nlMatrixTopNControlOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entity that configured this entry and is "The entity that configured this entry and is
therefore using the resources assigned to it." therefore using the resources assigned to it."
::= { nlMatrixTopNControlEntry 10 } ::= { nlMatrixTopNControlEntry 10 }
skipping to change at page 77, line 4 skipping to change at page 64, line 51
If this object is not equal to active(1), all If this object is not equal to active(1), all
associated entries in the nlMatrixTopNTable shall be deleted associated entries in the nlMatrixTopNTable shall be deleted
by the agent." by the agent."
::= { nlMatrixTopNControlEntry 11 } ::= { nlMatrixTopNControlEntry 11 }
nlMatrixTopNTable OBJECT-TYPE nlMatrixTopNTable OBJECT-TYPE
SYNTAX SEQUENCE OF NlMatrixTopNEntry SYNTAX SEQUENCE OF NlMatrixTopNEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of statistics for those network layer matrix entries "A set of statistics for those network-layer matrix entries
that have counted the highest number of octets or packets." that have counted the highest number of octets or packets."
::= { nlMatrix 5 } ::= { nlMatrix 5 }
nlMatrixTopNEntry OBJECT-TYPE nlMatrixTopNEntry OBJECT-TYPE
SYNTAX NlMatrixTopNEntry SYNTAX NlMatrixTopNEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the nlMatrixTopNTable. "A conceptual row in the nlMatrixTopNTable.
skipping to change at page 78, line 19 skipping to change at page 66, line 14
shall be assigned to entries with decreasing values of shall be assigned to entries with decreasing values of
nlMatrixTopNOctetRate until index N is assigned or there are nlMatrixTopNOctetRate until index N is assigned or there are
no more nlMatrixTopNEntries." no more nlMatrixTopNEntries."
::= { nlMatrixTopNEntry 1 } ::= { nlMatrixTopNEntry 1 }
nlMatrixTopNProtocolDirLocalIndex OBJECT-TYPE nlMatrixTopNProtocolDirLocalIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The protocolDirLocalIndex of the network layer protocol of "The protocolDirLocalIndex of the network-layer protocol of
this entry's network address." this entry's network address."
::= { nlMatrixTopNEntry 2 } ::= { nlMatrixTopNEntry 2 }
nlMatrixTopNSourceAddress OBJECT-TYPE nlMatrixTopNSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network layer address of the source host in this "The network-layer address of the source host in this
conversation. conversation.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the associated nlMatrixTopNProtocolDirLocalIndex. by the associated nlMatrixTopNProtocolDirLocalIndex.
For example, if the protocolDirLocalIndex indicates an For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length encapsulation of IP, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address, octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { nlMatrixTopNEntry 3 } ::= { nlMatrixTopNEntry 3 }
nlMatrixTopNDestAddress OBJECT-TYPE nlMatrixTopNDestAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network layer address of the destination host in this "The network-layer address of the destination host in this
conversation. conversation.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the associated nlMatrixTopNProtocolDirLocalIndex. by the associated nlMatrixTopNProtocolDirLocalIndex.
For example, if the nlMatrixTopNProtocolDirLocalIndex For example, if the nlMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a indicates an encapsulation of IP, this object is encoded as a
length octet of 4, followed by the 4 octets of the ip address, length octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { nlMatrixTopNEntry 4 } ::= { nlMatrixTopNEntry 4 }
nlMatrixTopNPktRate OBJECT-TYPE nlMatrixTopNPktRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets seen from the source host "The number of packets seen from the source host
to the destination host during this sampling interval, counted to the destination host during this sampling interval, counted
skipping to change at page 79, line 35 skipping to change at page 67, line 26
report." report."
::= { nlMatrixTopNEntry 5 } ::= { nlMatrixTopNEntry 5 }
nlMatrixTopNReversePktRate OBJECT-TYPE nlMatrixTopNReversePktRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets seen from the destination host to the "The number of packets seen from the destination host to the
source host during this sampling interval, counted source host during this sampling interval, counted
using the rules for counting the nlMatrixSDPkts object (note using the rules for counting the nlMatrixSDPkts object. (Note
that the corresponding nlMatrixSDPkts object selected is the that the corresponding nlMatrixSDPkts object selected is the
one whose source address is equal to nlMatrixTopNDestAddress one whose source address is equal to nlMatrixTopNDestAddress
and whose destination address is equal to and whose destination address is equal to
nlMatrixTopNSourceAddress.) nlMatrixTopNSourceAddress.)
Note that if the value of nlMatrixTopNControlRateBase is equal Note that if the value of nlMatrixTopNControlRateBase is equal
to nlMatrixTopNPkts, the sort of topN entries is based to nlMatrixTopNPkts, the sort of topN entries is based
entirely on nlMatrixTopNPktRate, and not on the value of this entirely on nlMatrixTopNPktRate, and not on the value of this
object." object."
::= { nlMatrixTopNEntry 6 } ::= { nlMatrixTopNEntry 6 }
skipping to change at page 80, line 22 skipping to change at page 68, line 10
report." report."
::= { nlMatrixTopNEntry 7 } ::= { nlMatrixTopNEntry 7 }
nlMatrixTopNReverseOctetRate OBJECT-TYPE nlMatrixTopNReverseOctetRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets seen from the destination host to the "The number of octets seen from the destination host to the
source host during this sampling interval, counted source host during this sampling interval, counted
using the rules for counting the nlMatrixDSOctets object (note using the rules for counting the nlMatrixDSOctets object. (Note
that the corresponding nlMatrixSDOctets object selected is the that the corresponding nlMatrixSDOctets object selected is the
one whose source address is equal to nlMatrixTopNDestAddress one whose source address is equal to nlMatrixTopNDestAddress
and whose destination address is equal to and whose destination address is equal to
nlMatrixTopNSourceAddress.) nlMatrixTopNSourceAddress.)
Note that if the value of nlMatrixTopNControlRateBase is equal Note that if the value of nlMatrixTopNControlRateBase is equal
to nlMatrixTopNOctets, the sort of topN entries is based to nlMatrixTopNOctets, the sort of topN entries is based
entirely on nlMatrixTopNOctetRate, and not on the value of entirely on nlMatrixTopNOctetRate, and not on the value of
this object." this object."
::= { nlMatrixTopNEntry 8 } ::= { nlMatrixTopNEntry 8 }
skipping to change at page 81, line 38 skipping to change at page 69, line 7
interface of this device. interface of this device.
The probe will populate this table for all protocols in the The probe will populate this table for all protocols in the
protocol directory table whose value of protocol directory table whose value of
protocolDirHostConfig is equal to supportedOn(3), and protocolDirHostConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or will delete any entries whose protocolDirEntry is deleted or
has a protocolDirHostConfig value of supportedOff(2). has a protocolDirHostConfig value of supportedOff(2).
The probe will add to this table all addresses The probe will add to this table all addresses
seen as the source or destination address in all packets with seen as the source or destination address in all packets with
no MAC errors, and will increment octet and packet counts in no MAC errors and will increment octet and packet counts in
the table for all packets with no MAC errors. Further, the table for all packets with no MAC errors. Further,
entries will only be added to this table if their address entries will only be added to this table if their address
exists in the nlHostTable and will be deleted from this table exists in the nlHostTable and will be deleted from this table
if their address is deleted from the nlHostTable." if their address is deleted from the nlHostTable."
::= { alHost 1 } ::= { alHost 1 }
alHostEntry OBJECT-TYPE alHostEntry OBJECT-TYPE
SYNTAX AlHostEntry SYNTAX AlHostEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the alHostTable. "A conceptual row in the alHostTable.
The hlHostControlIndex value in the index identifies the The hlHostControlIndex value in the index identifies the
hlHostControlEntry on whose behalf this entry was created. hlHostControlEntry on whose behalf this entry was created.
The first protocolDirLocalIndex value in the index identifies The first protocolDirLocalIndex value in the index identifies
the network layer protocol of the address. the network-layer protocol of the address.
The nlHostAddress value in the index identifies the network The nlHostAddress value in the index identifies the network-
layer address of this entry. layer address of this entry.
The second protocolDirLocalIndex value in the index identifies The second protocolDirLocalIndex value in the index identifies
the protocol that is counted by this entry. the protocol that is counted by this entry.
An example of the indexing in this entry is An example of the indexing in this entry is
alHostOutPkts.1.783495.18.4.128.2.6.6.34. alHostOutPkts.1.783495.18.4.128.2.6.6.34.
Note that some combinations of index values may result in an Note that some combinations of index values may result in an
index that exceeds 128 sub-identifiers in length which exceeds index that exceeds 128 sub-identifiers in length, which exceeds
the maximum for the SNMP protocol. Implementations should take the maximum for the SNMP protocol. Implementations should take
care to avoid such combinations." care to avoid such combinations."
INDEX { hlHostControlIndex, alHostTimeMark, INDEX { hlHostControlIndex, alHostTimeMark,
protocolDirLocalIndex, nlHostAddress, protocolDirLocalIndex, nlHostAddress,
protocolDirLocalIndex } protocolDirLocalIndex }
::= { alHostTable 1 } ::= { alHostTable 1 }
AlHostEntry ::= SEQUENCE { AlHostEntry ::= SEQUENCE {
alHostTimeMark TimeFilter, alHostTimeMark TimeFilter,
alHostInPkts ZeroBasedCounter32, alHostInPkts ZeroBasedCounter32,
skipping to change at page 83, line 35 skipping to change at page 70, line 44
several times." several times."
::= { alHostEntry 3 } ::= { alHostEntry 3 }
alHostInOctets OBJECT-TYPE alHostInOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets transmitted to this address "The number of octets transmitted to this address
of this protocol type since it was added to the of this protocol type since it was added to the
alHostTable (excluding framing bits but including alHostTable (excluding framing bits, but including
FCS octets), excluding those octets in packets that FCS octets), excluding octets in packets that
contained errors. contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained protocol frames but includes the entire packet that contained
the protocol." the protocol."
::= { alHostEntry 4 } ::= { alHostEntry 4 }
alHostOutOctets OBJECT-TYPE alHostOutOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets transmitted by this address "The number of octets transmitted by this address
of this protocol type since it was added to the of this protocol type since it was added to the
alHostTable (excluding framing bits but including alHostTable (excluding framing bits, but including
FCS octets), excluding those octets in packets that FCS octets), excluding octets in packets that
contained errors. contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained protocol frames but includes the entire packet that contained
the protocol." the protocol."
::= { alHostEntry 5 } ::= { alHostEntry 5 }
alHostCreateTime OBJECT-TYPE alHostCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this entry was last activated. "The value of sysUpTime when this entry was last activated.
This can be used by the management station to ensure that the This can be used by the management station to ensure that the
skipping to change at page 85, line 18 skipping to change at page 71, line 44
-- Counts the amount of traffic, by protocol, sent between each pair -- Counts the amount of traffic, by protocol, sent between each pair
-- of network addresses discovered by the probe. -- of network addresses discovered by the probe.
-- Implementation of this group requires implementation of the Network -- Implementation of this group requires implementation of the Network
-- Layer Matrix Group. -- Layer Matrix Group.
alMatrixSDTable OBJECT-TYPE alMatrixSDTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlMatrixSDEntry SYNTAX SEQUENCE OF AlMatrixSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of application traffic matrix entries which collect "A list of application traffic matrix entries that collect
statistics for conversations of a particular protocol between statistics for conversations of a particular protocol between
two network-level addresses. This table is indexed first by two network-level addresses. This table is indexed first by
the source address and then by the destination address to make the source address and then by the destination address to make
it convenient to collect all statistics from a particular it convenient to collect all statistics from a particular
address. address.
The probe will populate this table for all protocols in the The probe will populate this table for all protocols in the
protocol directory table whose value of protocol directory table whose value of
protocolDirMatrixConfig is equal to supportedOn(3), and protocolDirMatrixConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or will delete any entries whose protocolDirEntry is deleted or
has a protocolDirMatrixConfig value of supportedOff(2). has a protocolDirMatrixConfig value of supportedOff(2).
The probe will add to this table all pairs of addresses for The probe will add to this table all pairs of addresses for
all protocols seen in all packets with no MAC errors, and will all protocols seen in all packets with no MAC errors and will
increment octet and packet counts in the table for all packets increment octet and packet counts in the table for all packets
with no MAC errors. Further, entries will only be added to with no MAC errors. Further, entries will only be added to
this table if their address pair exists in the nlMatrixSDTable this table if their address pair exists in the nlMatrixSDTable
and will be deleted from this table if the address pair is and will be deleted from this table if the address pair is
deleted from the nlMatrixSDTable." deleted from the nlMatrixSDTable."
::= { alMatrix 1 } ::= { alMatrix 1 }
alMatrixSDEntry OBJECT-TYPE alMatrixSDEntry OBJECT-TYPE
SYNTAX AlMatrixSDEntry SYNTAX AlMatrixSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 86, line 4 skipping to change at page 72, line 26
alMatrixSDEntry OBJECT-TYPE alMatrixSDEntry OBJECT-TYPE
SYNTAX AlMatrixSDEntry SYNTAX AlMatrixSDEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the alMatrixSDTable. "A conceptual row in the alMatrixSDTable.
The hlMatrixControlIndex value in the index identifies the The hlMatrixControlIndex value in the index identifies the
hlMatrixControlEntry on whose behalf this entry was created. hlMatrixControlEntry on whose behalf this entry was created.
The first protocolDirLocalIndex value in the index identifies The first protocolDirLocalIndex value in the index identifies
the network layer protocol of the nlMatrixSDSourceAddress and the network-layer protocol of the nlMatrixSDSourceAddress and
nlMatrixSDDestAddress. nlMatrixSDDestAddress.
The nlMatrixSDSourceAddress value in the index identifies the The nlMatrixSDSourceAddress value in the index identifies the
network layer address of the source host in this conversation. network-layer address of the source host in this conversation.
The nlMatrixSDDestAddress value in the index identifies the The nlMatrixSDDestAddress value in the index identifies the
network layer address of the destination host in this network-layer address of the destination host in this
conversation. conversation.
The second protocolDirLocalIndex value in the index identifies The second protocolDirLocalIndex value in the index identifies
the protocol that is counted by this entry. the protocol that is counted by this entry.
An example of the indexing of this entry is An example of the indexing of this entry is
alMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7.34. alMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7.34.
Note that some combinations of index values may result in an Note that some combinations of index values may result in an
index that exceeds 128 sub-identifiers in length which exceeds index that exceeds 128 sub-identifiers in length, which exceeds
the maximum for the SNMP protocol. Implementations should take the maximum for the SNMP protocol. Implementations should take
care to avoid such combinations." care to avoid such combinations."
INDEX { hlMatrixControlIndex, alMatrixSDTimeMark, INDEX { hlMatrixControlIndex, alMatrixSDTimeMark,
protocolDirLocalIndex, protocolDirLocalIndex,
nlMatrixSDSourceAddress, nlMatrixSDDestAddress, nlMatrixSDSourceAddress, nlMatrixSDDestAddress,
protocolDirLocalIndex } protocolDirLocalIndex }
::= { alMatrixSDTable 1 } ::= { alMatrixSDTable 1 }
AlMatrixSDEntry ::= SEQUENCE { AlMatrixSDEntry ::= SEQUENCE {
alMatrixSDTimeMark TimeFilter, alMatrixSDTimeMark TimeFilter,
skipping to change at page 87, line 21 skipping to change at page 73, line 39
::= { alMatrixSDEntry 2 } ::= { alMatrixSDEntry 2 }
alMatrixSDOctets OBJECT-TYPE alMatrixSDOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets in packets of this protocol type "The number of octets in packets of this protocol type
transmitted from the source address to the destination address transmitted from the source address to the destination address
since this entry was added to the alMatrixSDTable (excluding since this entry was added to the alMatrixSDTable (excluding
framing bits but including FCS octets), excluding those octets framing bits, but including FCS octets), excluding octets
in packets that contained errors. in packets that contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained protocol frames but includes the entire packet that contained
the protocol." the protocol."
::= { alMatrixSDEntry 3 } ::= { alMatrixSDEntry 3 }
alMatrixSDCreateTime OBJECT-TYPE alMatrixSDCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this entry was last activated. "The value of sysUpTime when this entry was last activated.
This can be used by the management station to ensure that the This can be used by the management station to ensure that the
entry has not been deleted and recreated between polls." entry has not been deleted and recreated between polls."
::= { alMatrixSDEntry 4 } ::= { alMatrixSDEntry 4 }
-- Traffic matrix tables from destination to source -- Traffic matrix tables from destination to source
alMatrixDSTable OBJECT-TYPE alMatrixDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlMatrixDSEntry SYNTAX SEQUENCE OF AlMatrixDSEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of application traffic matrix entries which collect "A list of application traffic matrix entries that collect
statistics for conversations of a particular protocol between statistics for conversations of a particular protocol between
two network-level addresses. This table is indexed first by two network-level addresses. This table is indexed first by
the destination address and then by the source address to make the destination address and then by the source address to make
it convenient to collect all statistics to a particular it convenient to collect all statistics to a particular
address. address.
The probe will populate this table for all protocols in the The probe will populate this table for all protocols in the
protocol directory table whose value of protocol directory table whose value of
protocolDirMatrixConfig is equal to supportedOn(3), and protocolDirMatrixConfig is equal to supportedOn(3), and
will delete any entries whose protocolDirEntry is deleted or will delete any entries whose protocolDirEntry is deleted or
has a protocolDirMatrixConfig value of supportedOff(2). has a protocolDirMatrixConfig value of supportedOff(2).
The probe will add to this table all pairs of addresses for The probe will add to this table all pairs of addresses for
all protocols seen in all packets with no MAC errors, and will all protocols seen in all packets with no MAC errors and will
increment octet and packet counts in the table for all packets increment octet and packet counts in the table for all packets
with no MAC errors. Further, entries will only be added to with no MAC errors. Further, entries will only be added to
this table if their address pair exists in the nlMatrixDSTable this table if their address pair exists in the nlMatrixDSTable
and will be deleted from this table if the address pair is and will be deleted from this table if the address pair is
deleted from the nlMatrixDSTable." deleted from the nlMatrixDSTable."
::= { alMatrix 2 } ::= { alMatrix 2 }
alMatrixDSEntry OBJECT-TYPE alMatrixDSEntry OBJECT-TYPE
SYNTAX AlMatrixDSEntry SYNTAX AlMatrixDSEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the alMatrixDSTable. "A conceptual row in the alMatrixDSTable.
The hlMatrixControlIndex value in the index identifies the The hlMatrixControlIndex value in the index identifies the
hlMatrixControlEntry on whose behalf this entry was created. hlMatrixControlEntry on whose behalf this entry was created.
The first protocolDirLocalIndex value in the index identifies The first protocolDirLocalIndex value in the index identifies
the network layer protocol of the alMatrixDSSourceAddress and the network-layer protocol of the alMatrixDSSourceAddress and
alMatrixDSDestAddress. alMatrixDSDestAddress.
The nlMatrixDSDestAddress value in the index identifies the The nlMatrixDSDestAddress value in the index identifies the
network layer address of the destination host in this network-layer address of the destination host in this
conversation. conversation.
The nlMatrixDSSourceAddress value in the index identifies the The nlMatrixDSSourceAddress value in the index identifies the
network layer address of the source host in this conversation. network-layer address of the source host in this conversation.
The second protocolDirLocalIndex value in the index identifies The second protocolDirLocalIndex value in the index identifies
the protocol that is counted by this entry. the protocol that is counted by this entry.
An example of the indexing of this entry is An example of the indexing of this entry is
alMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6.34. alMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6.34.
Note that some combinations of index values may result in an Note that some combinations of index values may result in an
index that exceeds 128 sub-identifiers in length which exceeds index that exceeds 128 sub-identifiers in length, which exceeds
the maximum for the SNMP protocol. Implementations should take the maximum for the SNMP protocol. Implementations should take
care to avoid such combinations." care to avoid such combinations."
INDEX { hlMatrixControlIndex, alMatrixDSTimeMark, INDEX { hlMatrixControlIndex, alMatrixDSTimeMark,
protocolDirLocalIndex, protocolDirLocalIndex,
nlMatrixDSDestAddress, nlMatrixDSSourceAddress, nlMatrixDSDestAddress, nlMatrixDSSourceAddress,
protocolDirLocalIndex } protocolDirLocalIndex }
::= { alMatrixDSTable 1 } ::= { alMatrixDSTable 1 }
AlMatrixDSEntry ::= SEQUENCE { AlMatrixDSEntry ::= SEQUENCE {
alMatrixDSTimeMark TimeFilter, alMatrixDSTimeMark TimeFilter,
skipping to change at page 90, line 6 skipping to change at page 76, line 13
::= { alMatrixDSEntry 2 } ::= { alMatrixDSEntry 2 }
alMatrixDSOctets OBJECT-TYPE alMatrixDSOctets OBJECT-TYPE
SYNTAX ZeroBasedCounter32 SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets in packets of this protocol type "The number of octets in packets of this protocol type
transmitted from the source address to the destination address transmitted from the source address to the destination address
since this entry was added to the alMatrixDSTable (excluding since this entry was added to the alMatrixDSTable (excluding
framing bits but including FCS octets), excluding those octets framing bits, but including FCS octets), excluding octets
in packets that contained errors. in packets that contained errors.
Note this doesn't count just those octets in the particular Note that this doesn't count just those octets in the particular
protocol frames, but includes the entire packet that contained protocol frames but includes the entire packet that contained
the protocol." the protocol."
::= { alMatrixDSEntry 3 } ::= { alMatrixDSEntry 3 }
alMatrixDSCreateTime OBJECT-TYPE alMatrixDSCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this entry was last activated. "The value of sysUpTime when this entry was last activated.
This can be used by the management station to ensure that the This can be used by the management station to ensure that the
skipping to change at page 92, line 12 skipping to change at page 78, line 10
alMatrixTopNAllPkts(3), alMatrixTopNAllPkts(3),
alMatrixTopNAllOctets(4), alMatrixTopNAllOctets(4),
alMatrixTopNTerminalsHighCapacityPkts(5), alMatrixTopNTerminalsHighCapacityPkts(5),
alMatrixTopNTerminalsHighCapacityOctets(6), alMatrixTopNTerminalsHighCapacityOctets(6),
alMatrixTopNAllHighCapacityPkts(7), alMatrixTopNAllHighCapacityPkts(7),
alMatrixTopNAllHighCapacityOctets(8) alMatrixTopNAllHighCapacityOctets(8)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The variable for each alMatrix[SD/DS] entry that the "This object controls which alMatrix[SD/DS] entry that the
alMatrixTopNEntries are sorted by, as well as the alMatrixTopNEntries are sorted by, which view of the matrix
selector of the view of the matrix table that will be table that will be used, as well as which table the results
used, as well as a control for the table that the results
will be reported in. will be reported in.
The values alMatrixTopNTerminalsPkts, The values alMatrixTopNTerminalsPkts,
alMatrixTopNTerminalsOctets, alMatrixTopNTerminalsOctets,
alMatrixTopNTerminalsHighCapacityPkts, and alMatrixTopNTerminalsHighCapacityPkts, and
alMatrixTopNTerminalsHighCapacityOctets cause collection alMatrixTopNTerminalsHighCapacityOctets cause collection
only from protocols that have no child protocols that are only from protocols that have no child protocols that are
counted. The values alMatrixTopNAllPkts, counted. The values alMatrixTopNAllPkts,
alMatrixTopNAllOctets, alMatrixTopNAllHighCapacityPkts, and alMatrixTopNAllOctets, alMatrixTopNAllHighCapacityPkts, and
alMatrixTopNAllHighCapacityOctets cause collection from all alMatrixTopNAllHighCapacityOctets cause collection from all
skipping to change at page 92, line 42 skipping to change at page 78, line 39
alMatrixTopNControlTimeRemaining OBJECT-TYPE alMatrixTopNControlTimeRemaining OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds left in the report currently "The number of seconds left in the report currently
being collected. When this object is modified by being collected. When this object is modified by
the management station, a new collection is started, the management station, a new collection is started,
possibly aborting a currently running report. The possibly aborting a currently running report. The
new value is used as the requested duration of this new value is used as the requested duration of this
report, and is immediately loaded into the associated report and is immediately loaded into the associated
alMatrixTopNControlDuration object. alMatrixTopNControlDuration object.
When the report finishes, the probe will automatically When the report finishes, the probe will automatically
start another collection with the same initial value start another collection with the same initial value
of alMatrixTopNControlTimeRemaining. Thus the management of alMatrixTopNControlTimeRemaining. Thus, the management
station may simply read the resulting reports repeatedly, station may simply read the resulting reports repeatedly,
checking the startTime and duration each time to ensure that a checking the startTime and duration each time to ensure that a
report was not missed or that the report parameters were not report was not missed or that the report parameters were not
changed. changed.
While the value of this object is non-zero, it decrements While the value of this object is non-zero, it decrements
by one per second until it reaches zero. At the time by one per second until it reaches zero. At the time
that this object decrements to zero, the report is made that this object decrements to zero, the report is made
accessible in the alMatrixTopNTable, overwriting any report accessible in the alMatrixTopNTable, overwriting any report
that may be there. that may be there.
When this object is modified by the management station, any When this object is modified by the management station, any
associated entries in the alMatrixTopNTable shall be deleted. associated entries in the alMatrixTopNTable shall be deleted.
(Note that this is a different algorithm than the one used in (Note that this is a different algorithm than the one used
the hostTopNTable)." in the hostTopNTable)."
DEFVAL { 1800 } DEFVAL { 1800 }
::= { alMatrixTopNControlEntry 4 } ::= { alMatrixTopNControlEntry 4 }
alMatrixTopNControlGeneratedReports OBJECT-TYPE alMatrixTopNControlGeneratedReports OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of reports that have been generated by this entry." "The number of reports that have been generated by this entry."
::= { alMatrixTopNControlEntry 5 } ::= { alMatrixTopNControlEntry 5 }
skipping to change at page 94, line 12 skipping to change at page 79, line 50
alMatrixTopNControlRequestedSize OBJECT-TYPE alMatrixTopNControlRequestedSize OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of matrix entries requested for this report. "The maximum number of matrix entries requested for this report.
When this object is created or modified, the probe When this object is created or modified, the probe
should set alMatrixTopNControlGrantedSize as closely to this should set alMatrixTopNControlGrantedSize as closely to this
object as is possible for the particular probe object as possible for the particular probe
implementation and available resources." implementation and available resources."
DEFVAL { 150 } DEFVAL { 150 }
::= { alMatrixTopNControlEntry 7 } ::= { alMatrixTopNControlEntry 7 }
alMatrixTopNControlGrantedSize OBJECT-TYPE alMatrixTopNControlGrantedSize OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of matrix entries in this report. "The maximum number of matrix entries in this report.
When the associated alMatrixTopNControlRequestedSize object When the associated alMatrixTopNControlRequestedSize object
is created or modified, the probe should set this is created or modified, the probe should set this
object as closely to the requested value as is object as closely to the requested value as
possible for the particular implementation and possible for the particular implementation and
available resources. The probe must not lower this available resources. The probe must not lower this
value except as a result of a set to the associated value except as a side-effect of a set to the associated
alMatrixTopNControlRequestedSize object. alMatrixTopNControlRequestedSize object.
If the value of alMatrixTopNControlRateBase is equal to If the value of alMatrixTopNControlRateBase is equal to
alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, when the alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, when the
next topN report is generated, matrix entries with the highest next topN report is generated, matrix entries with the highest
value of alMatrixTopNPktRate shall be placed in this table in value of alMatrixTopNPktRate shall be placed in this table in
decreasing order of this rate until there is no more room or decreasing order of this rate until there is no more room or
until there are no more matrix entries. until there are no more matrix entries.
If the value of alMatrixTopNControlRateBase is equal to If the value of alMatrixTopNControlRateBase is equal to
alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, when the alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, when the
next topN report is generated, matrix entries with the highest next topN report is generated, matrix entries with the highest
value of alMatrixTopNOctetRate shall be placed in this table value of alMatrixTopNOctetRate shall be placed in this table
in decreasing order of this rate until there is no more room in decreasing order of this rate until there is no more room
or until there are no more matrix entries. or until there are no more matrix entries.
It is an implementation-specific matter how entries with the It is an implementation-specific matter how entries with the
same value of alMatrixTopNPktRate or alMatrixTopNOctetRate are same value of alMatrixTopNPktRate or alMatrixTopNOctetRate are
sorted. It is also an implementation-specific matter as to sorted. It is also an implementation-specific matter as to
whether or not zero-valued entries are available." whether zero-valued entries are available."
::= { alMatrixTopNControlEntry 8 } ::= { alMatrixTopNControlEntry 8 }
alMatrixTopNControlStartTime OBJECT-TYPE alMatrixTopNControlStartTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime when this top N report was "The value of sysUpTime when this top N report was
last started. In other words, this is the time that last started. In other words, this is the time that
the associated alMatrixTopNControlTimeRemaining object the associated alMatrixTopNControlTimeRemaining object
was modified to start the requested report or the time was modified to start the requested report or the time
the report was last automatically (re)started. the report was last automatically (re)started.
This object may be used by the management station to This object may be used by the management station to
determine if a report was missed or not." determine whether a report was missed."
::= { alMatrixTopNControlEntry 9 } ::= { alMatrixTopNControlEntry 9 }
alMatrixTopNControlOwner OBJECT-TYPE alMatrixTopNControlOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entity that configured this entry and is "The entity that configured this entry and is
therefore using the resources assigned to it." therefore using the resources assigned to it."
::= { alMatrixTopNControlEntry 10 } ::= { alMatrixTopNControlEntry 10 }
skipping to change at page 96, line 8 skipping to change at page 81, line 38
If this object is not equal to active(1), all If this object is not equal to active(1), all
associated entries in the alMatrixTopNTable shall be associated entries in the alMatrixTopNTable shall be
deleted by the agent." deleted by the agent."
::= { alMatrixTopNControlEntry 11 } ::= { alMatrixTopNControlEntry 11 }
alMatrixTopNTable OBJECT-TYPE alMatrixTopNTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlMatrixTopNEntry SYNTAX SEQUENCE OF AlMatrixTopNEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of statistics for those application layer matrix "A set of statistics for those application-layer matrix
entries that have counted the highest number of octets or entries that have counted the highest number of octets or
packets." packets."
::= { alMatrix 4 } ::= { alMatrix 4 }
alMatrixTopNEntry OBJECT-TYPE alMatrixTopNEntry OBJECT-TYPE
SYNTAX AlMatrixTopNEntry SYNTAX AlMatrixTopNEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in the alMatrixTopNTable. "A conceptual row in the alMatrixTopNTable.
skipping to change at page 97, line 26 skipping to change at page 82, line 51
increasing values of alMatrixTopNIndex shall be assigned to increasing values of alMatrixTopNIndex shall be assigned to
entries with decreasing values of alMatrixTopNOctetRate until entries with decreasing values of alMatrixTopNOctetRate until
index N is assigned or there are no more alMatrixTopNEntries." index N is assigned or there are no more alMatrixTopNEntries."
::= { alMatrixTopNEntry 1 } ::= { alMatrixTopNEntry 1 }
alMatrixTopNProtocolDirLocalIndex OBJECT-TYPE alMatrixTopNProtocolDirLocalIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The protocolDirLocalIndex of the network layer protocol of "The protocolDirLocalIndex of the network-layer protocol of
this entry's network address." this entry's network address."
::= { alMatrixTopNEntry 2 } ::= { alMatrixTopNEntry 2 }
alMatrixTopNSourceAddress OBJECT-TYPE alMatrixTopNSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network layer address of the source host in this "The network-layer address of the source host in this
conversation. conversation.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the associated alMatrixTopNProtocolDirLocalIndex. by the associated alMatrixTopNProtocolDirLocalIndex.
For example, if the alMatrixTopNProtocolDirLocalIndex For example, if the alMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a indicates an encapsulation of IP, this object is encoded as a
length octet of 4, followed by the 4 octets of the ip address, length octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { alMatrixTopNEntry 3 } ::= { alMatrixTopNEntry 3 }
alMatrixTopNDestAddress OBJECT-TYPE alMatrixTopNDestAddress OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network layer address of the destination host in this "The network-layer address of the destination host in this
conversation. conversation.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
by the associated alMatrixTopNProtocolDirLocalIndex. by the associated alMatrixTopNProtocolDirLocalIndex.
For example, if the alMatrixTopNProtocolDirLocalIndex For example, if the alMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a indicates an encapsulation of IP, this object is encoded as a
length octet of 4, followed by the 4 octets of the ip address, length octet of 4, followed by the 4 octets of the IP address,
in network byte order." in network byte order."
::= { alMatrixTopNEntry 4 } ::= { alMatrixTopNEntry 4 }
alMatrixTopNAppProtocolDirLocalIndex OBJECT-TYPE alMatrixTopNAppProtocolDirLocalIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the protocol counted by this matrix entry." "The type of the protocol counted by this matrix entry."
::= { alMatrixTopNEntry 5 } ::= { alMatrixTopNEntry 5 }
skipping to change at page 99, line 8 skipping to change at page 84, line 25
::= { alMatrixTopNEntry 6 } ::= { alMatrixTopNEntry 6 }
alMatrixTopNReversePktRate OBJECT-TYPE alMatrixTopNReversePktRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets seen of this protocol from the "The number of packets seen of this protocol from the
destination host to the source host during this sampling destination host to the source host during this sampling
interval, counted using the rules for counting the interval, counted using the rules for counting the
alMatrixDSPkts object (note that the corresponding alMatrixDSPkts object. (Note that the corresponding
alMatrixSDPkts object selected is the one whose source address alMatrixSDPkts object selected is the one whose source address
is equal to alMatrixTopNDestAddress and whose destination is equal to alMatrixTopNDestAddress and whose destination
address is equal to alMatrixTopNSourceAddress.) address is equal to alMatrixTopNSourceAddress.)
Note that if the value of alMatrixTopNControlRateBase is equal Note that if the value of alMatrixTopNControlRateBase is equal
to alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, the sort to alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, the sort
of topN entries is based entirely on alMatrixTopNPktRate, and of topN entries is based entirely on alMatrixTopNPktRate, and
not on the value of this object." not on the value of this object."
::= { alMatrixTopNEntry 7 } ::= { alMatrixTopNEntry 7 }
skipping to change at page 99, line 42 skipping to change at page 85, line 11
::= { alMatrixTopNEntry 8 } ::= { alMatrixTopNEntry 8 }
alMatrixTopNReverseOctetRate OBJECT-TYPE alMatrixTopNReverseOctetRate OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets seen of this protocol from the "The number of octets seen of this protocol from the
destination host to the source host during this sampling destination host to the source host during this sampling
interval, counted using the rules for counting the interval, counted using the rules for counting the
alMatrixDSOctets object (note that the corresponding alMatrixDSOctets object. (Note that the corresponding
alMatrixSDOctets object selected is the one whose source alMatrixSDOctets object selected is the one whose source
address is equal to alMatrixTopNDestAddress and whose address is equal to alMatrixTopNDestAddress and whose
destination address is equal to alMatrixTopNSourceAddress.) destination address is equal to alMatrixTopNSourceAddress.)
Note that if the value of alMatrixTopNControlRateBase is equal Note that if the value of alMatrixTopNControlRateBase is equal
to alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, the to alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, the
sort of topN entries is based entirely on sort of topN entries is based entirely on
alMatrixTopNOctetRate, and not on the value of this object." alMatrixTopNOctetRate, and not on the value of this object."
::= { alMatrixTopNEntry 9 } ::= { alMatrixTopNEntry 9 }
skipping to change at page 100, line 20 skipping to change at page 85, line 33
-- User History Collection Group (usrHistory) -- User History Collection Group (usrHistory)
-- --
-- The usrHistory group combines mechanisms seen in the alarm and -- The usrHistory group combines mechanisms seen in the alarm and
-- history groups to provide user-specified history collection, -- history groups to provide user-specified history collection,
-- utilizing two additional control tables and one additional data -- utilizing two additional control tables and one additional data
-- table. This function has traditionally been done by NMS -- table. This function has traditionally been done by NMS
-- applications, via periodic polling. The usrHistory group allows -- applications, via periodic polling. The usrHistory group allows
-- this task to be offloaded to an RMON probe. -- this task to be offloaded to an RMON probe.
-- --
-- Data (an ASN.1 INTEGER based object) is collected in the same -- Data (an ASN.1 INTEGER based object) is collected in the same
-- manner as any history data table (e.g., etherHistoryTable) except
-- that the user specifies the MIB instances to be collected. Objects -- that the user specifies the MIB instances to be collected. Objects
-- are collected in bucket-groups, with the intent that all MIB -- are collected in bucket-groups, with the intent that all MIB
-- instances in the same bucket-group are collected as atomically as -- instances in the same bucket-group are collected as atomically as
-- possible by the RMON probe. -- possible by the RMON probe.
-- --
-- The usrHistoryControlTable is a one-dimensional read-create table. -- The usrHistoryControlTable is a one-dimensional read-create table.
-- Each row configures a collection of user history buckets, much -- Each row configures a collection of user history buckets, much
-- the same as a historyControlEntry, except that the creation of a -- the same as a historyControlEntry, except that the creation of a
-- row in this table will cause one or more associated instances in -- row in this table will cause one or more associated instances in
-- the usrHistoryObjectTable to be created. The user specifies the -- the usrHistoryObjectTable to be created. The user specifies the
skipping to change at page 101, line 18 skipping to change at page 86, line 27
-- --
-- The static nature of the usrHistoryObjectTable creates -- The static nature of the usrHistoryObjectTable creates
-- some row creation/modification issues. The rows in this -- some row creation/modification issues. The rows in this
-- table need to be set before the associated -- table need to be set before the associated
-- usrHistoryControlEntry can be activated. -- usrHistoryControlEntry can be activated.
-- --
-- Note that the usrHistoryObject entries associated with a -- Note that the usrHistoryObject entries associated with a
-- particular usrHistoryControlEntry are not required to -- particular usrHistoryControlEntry are not required to
-- be active before the control entry is activated. However, -- be active before the control entry is activated. However,
-- the usrHistory data entries associated with an inactive -- the usrHistory data entries associated with an inactive
-- usrHistoryObject entry will be inactive (i.e.,
-- usrHistoryValStatus == valueNotAvailable). -- usrHistoryValStatus == valueNotAvailable).
-- --
usrHistoryControlTable OBJECT-TYPE usrHistoryControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF UsrHistoryControlEntry SYNTAX SEQUENCE OF UsrHistoryControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of data-collection configuration entries." "A list of data-collection configuration entries."
::= { usrHistory 1 } ::= { usrHistory 1 }
skipping to change at page 102, line 44 skipping to change at page 87, line 50
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The requested number of discrete time intervals "The requested number of discrete time intervals
over which data is to be saved in the part of the over which data is to be saved in the part of the
usrHistoryTable associated with this usrHistoryControlEntry. usrHistoryTable associated with this usrHistoryControlEntry.
When this object is created or modified, the probe When this object is created or modified, the probe
should set usrHistoryControlBucketsGranted as closely to should set usrHistoryControlBucketsGranted as closely to
this object as is possible for the particular probe this object as possible for the particular probe
implementation and available resources." implementation and available resources."
DEFVAL { 50 } DEFVAL { 50 }
::= { usrHistoryControlEntry 3 } ::= { usrHistoryControlEntry 3 }
usrHistoryControlBucketsGranted OBJECT-TYPE usrHistoryControlBucketsGranted OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of discrete sampling intervals "The number of discrete sampling intervals
over which data shall be saved in the part of over which data shall be saved in the part of
the usrHistoryTable associated with this the usrHistoryTable associated with this
usrHistoryControlEntry. usrHistoryControlEntry.
When the associated usrHistoryControlBucketsRequested When the associated usrHistoryControlBucketsRequested
object is created or modified, the probe should set object is created or modified, the probe should set
this object as closely to the requested value as is this object as closely to the requested value as
possible for the particular probe implementation and possible for the particular probe implementation and
available resources. The probe must not lower this available resources. The probe must not lower this
value except as a result of a modification to the associated value except as a result of a modification to the associated
usrHistoryControlBucketsRequested object. usrHistoryControlBucketsRequested object.
The associated usrHistoryControlBucketsRequested object The associated usrHistoryControlBucketsRequested object
should be set before or at the same time as this object should be set before or at the same time as this object
to allow the probe to accurately estimate the resources to allow the probe to accurately estimate the resources
required for this usrHistoryControlEntry. required for this usrHistoryControlEntry.
skipping to change at page 104, line 20 skipping to change at page 89, line 19
DESCRIPTION DESCRIPTION
"The interval in seconds over which the data is "The interval in seconds over which the data is
sampled for each bucket in the part of the usrHistory sampled for each bucket in the part of the usrHistory
table associated with this usrHistoryControlEntry. table associated with this usrHistoryControlEntry.
Because the counters in a bucket may overflow at their Because the counters in a bucket may overflow at their
maximum value with no indication, a prudent manager will maximum value with no indication, a prudent manager will
take into account the possibility of overflow in any of take into account the possibility of overflow in any of
the associated counters. It is important to consider the the associated counters. It is important to consider the
minimum time in which any counter could overflow on a minimum time in which any counter could overflow on a
particular media type and set the usrHistoryControlInterval particular media type and to set the usrHistoryControlInterval
object to a value less than this interval. object to a value less than this interval.
This object may not be modified if the associated This object may not be modified if the associated
usrHistoryControlStatus object is equal to active(1)." usrHistoryControlStatus object is equal to active(1)."
DEFVAL { 1800 } DEFVAL { 1800 }
::= { usrHistoryControlEntry 5 } ::= { usrHistoryControlEntry 5 }
usrHistoryControlOwner OBJECT-TYPE usrHistoryControlOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 107, line 31 skipping to change at page 92, line 16
usrHistoryControlStatus object is equal to active(1)." usrHistoryControlStatus object is equal to active(1)."
::= { usrHistoryObjectEntry 3 } ::= { usrHistoryObjectEntry 3 }
-- data table -- data table
usrHistoryTable OBJECT-TYPE usrHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF UsrHistoryEntry SYNTAX SEQUENCE OF UsrHistoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of user defined history entries." "A list of user-defined history entries."
::= { usrHistory 3 } ::= { usrHistory 3 }
usrHistoryEntry OBJECT-TYPE usrHistoryEntry OBJECT-TYPE
SYNTAX UsrHistoryEntry SYNTAX UsrHistoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A historical sample of user-defined variables. This sample "A historical sample of user-defined variables. This sample
is associated with the usrHistoryControlEntry which set up the is associated with the usrHistoryControlEntry that set up the
parameters for a regular collection of these samples. parameters for a regular collection of these samples.
The usrHistoryControlIndex value in the index identifies the The usrHistoryControlIndex value in the index identifies the
usrHistoryControlEntry on whose behalf this entry was created. usrHistoryControlEntry on whose behalf this entry was created.
The usrHistoryObjectIndex value in the index identifies the The usrHistoryObjectIndex value in the index identifies the
usrHistoryObjectEntry on whose behalf this entry was created. usrHistoryObjectEntry on whose behalf this entry was created.
For example, an instance of usrHistoryAbsValue, which represents For example, an instance of usrHistoryAbsValue, which represents
the 14th sample of a variable collected as specified by the 14th sample of a variable collected as specified by
usrHistoryControlEntry.1 and usrHistoryObjectEntry.1.5, usrHistoryControlEntry.1 and usrHistoryObjectEntry.1.5,
skipping to change at page 108, line 43 skipping to change at page 93, line 22
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the start of the interval over "The value of sysUpTime at the start of the interval over
which this sample was measured. If the probe keeps track of which this sample was measured. If the probe keeps track of
the time of day, it should start the first sample of the the time of day, it should start the first sample of the
history at a time such that when the next hour of the day history at a time such that when the next hour of the day
begins, a sample is started at that instant. begins, a sample is started at that instant.
Note that following this rule may require the probe to delay Note that following this rule may require that the probe delay
collecting the first sample of the history, as each sample collecting the first sample of the history, as each sample
must be of the same interval. Also note that the sample which must be of the same interval. Also note that the sample that
is currently being collected is not accessible in this table is currently being collected is not accessible in this table
until the end of its interval." until the end of its interval."
::= { usrHistoryEntry 2 } ::= { usrHistoryEntry 2 }
usrHistoryIntervalEnd OBJECT-TYPE usrHistoryIntervalEnd OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the end of the interval over which "The value of sysUpTime at the end of the interval over which
this sample was measured." this sample was measured."
::= { usrHistoryEntry 3 } ::= { usrHistoryEntry 3 }
usrHistoryAbsValue OBJECT-TYPE usrHistoryAbsValue OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The absolute value (i.e. unsigned value) of the "The absolute value (i.e., unsigned value) of the
user-specified statistic during the last sampling period. The user-specified statistic during the last sampling period. The
value during the current sampling period is not made available value during the current sampling period is not made available
until the period is completed. until the period is completed.
To obtain the true value for this sampling interval, the To obtain the true value for this sampling interval, the
associated instance of usrHistoryValStatus must be checked, associated instance of usrHistoryValStatus must be checked,
and usrHistoryAbsValue adjusted as necessary. and usrHistoryAbsValue adjusted as necessary.
If the MIB instance could not be accessed during the sampling If the MIB instance could not be accessed during the sampling
interval, then this object will have a value of zero and the interval, then this object will have a value of zero, and the
associated instance of usrHistoryValStatus will be set to associated instance of usrHistoryValStatus will be set to
'valueNotAvailable(1)'. 'valueNotAvailable(1)'.
The access control check prescribed in the definition of The access control check prescribed in the definition of
usrHistoryObjectVariable SHOULD be checked for each sampling usrHistoryObjectVariable SHOULD be checked for each sampling
interval. If this check determines that access should not be interval. If this check determines that access should not be
allowed, then this object will have a value of zero and the allowed, then this object will have a value of zero, and the
associated instance of usrHistoryValStatus will be set to associated instance of usrHistoryValStatus will be set to
'valueNotAvailable(1)'." 'valueNotAvailable(1)'."
::= { usrHistoryEntry 4 } ::= { usrHistoryEntry 4 }
usrHistoryValStatus OBJECT-TYPE usrHistoryValStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
valueNotAvailable(1), valueNotAvailable(1),
valuePositive(2), valuePositive(2),
valueNegative(3) valueNegative(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the validity and sign of the data in "This object indicates the validity and sign of the data in
the associated instance of usrHistoryAbsValue. the associated instance of usrHistoryAbsValue.
If the MIB instance could not be accessed during the sampling If the MIB instance could not be accessed during the sampling
interval, then 'valueNotAvailable(1)' will be returned. interval, then 'valueNotAvailable(1)' will be returned.
If the sample is valid and actual value of the sample is If the sample is valid and the actual value of the sample is
greater than or equal to zero then 'valuePositive(2)' is greater than or equal to zero, then 'valuePositive(2)' is
returned. returned.
If the sample is valid and the actual value of the sample is If the sample is valid and the actual value of the sample is
less than zero, 'valueNegative(3)' will be returned. The less than zero, 'valueNegative(3)' will be returned. The
associated instance of usrHistoryAbsValue should be multiplied associated instance of usrHistoryAbsValue should be multiplied
by -1 to obtain the true sample value." by -1 to obtain the true sample value."
::= { usrHistoryEntry 5 } ::= { usrHistoryEntry 5 }
-- The Probe Configuration Group -- The Probe Configuration Group
-- --
-- This group controls the configuration of various operating -- This group controls the configuration of various operating
-- parameters of the probe. -- parameters of the probe.
ControlString ::= TEXTUAL-CONVENTION ControlString ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used to communicate with a modem or a "This data type is used to communicate with a modem or a
serial data switch. A ControlString contains embedded serial data switch. A ControlString contains embedded
commands to control how the device will interact with the commands to control how the device will interact with the
remote device through the serial interface. Commands are remote device through the serial interface. Commands are
represented as two character sequences beginning with represented as two-character sequences beginning with
the `^' character. the '^' character.
The following commands are recognized by the device (note The following commands are recognized by the device (note
that command characters are case sensitive): that command characters are case sensitive):
^s Send string that follows which is terminated by the ^s Send string that follows, which is terminated by the
next command or the end of string. next command or the end of string.
^c Delay for the number of seconds that follows. Toss ^c Delay for the number of seconds that follows. Toss
out any data received rather than storing it in a out any data received rather than store it in a
buffer for parsing. buffer for parsing.
^t Set timeout to the value represented by the decimal ^t Set timeout to the value represented by the decimal
digits that follow. The default timeout is 20 digits that follow. The default timeout is 20
seconds. Note that this timeout may be overridden seconds. Note that this timeout may be overridden
by a smaller serialTimeout configured for the by a smaller serialTimeout configured for the
associated serial interface (see serialConfigTable). associated serial interface (see serialConfigTable).
^w Wait for the reply string that follows which is ^w Wait for the reply string that follows, which is
terminated by the next command or the end of string. terminated by the next command or the end of string.
Partial and case insensitive matching is applied, ie. Partial and case-insensitive matching is applied, i.e.,
if the reply string (any case combination) is found if the reply string (any case combination) is found
anywhere in the received string, then the a match is anywhere in the received string, then the a match is
found. If the current timeout elapses without a match, found. If the current timeout elapses without a match,
then the remaining control string is ignored. then the remaining control string is ignored.
^! The ^ character. ^! The ^ character.
^d Delay the number of seconds specified by the decimal ^d Delay the number of seconds specified by the decimal
digits that follow. digits that follow.
^b Send break for the number of milliseconds specified by ^b Send break for the number of milliseconds specified by
the decimal digits that follow. If no digits follow, the decimal digits that follow. If no digits follow,
break will be enforced for 250 milliseconds by default. break will be enforced for 250 milliseconds by default.
The following ASCII control characters may be inserted into The following ASCII control characters may be inserted into
the `^s' send string or the `^w' reply string: the '^s' send string or the '^w' reply string:
^@ 0x00 ^@ 0x00
^A 0x01 ^A 0x01
.. ..
^M 0x0D ^M 0x0D
.. ..
^Z 0x1A ^Z 0x1A
^[ 0x1B ^[ 0x1B
^ 0x1C ^ 0x1C
^] 0x1D ^] 0x1D
skipping to change at page 111, line 34 skipping to change at page 96, line 4
^A 0x01 ^A 0x01
.. ..
^M 0x0D ^M 0x0D
.. ..
^Z 0x1A ^Z 0x1A
^[ 0x1B ^[ 0x1B
^ 0x1C ^ 0x1C
^] 0x1D ^] 0x1D
^^ 0x1E ^^ 0x1E
^_ 0x1F ^_ 0x1F
Binary data may also be inserted into the data stream. The Binary data may also be inserted into the data stream. The
control sequence for each byte of binary data is ^0x##, where control sequence for each byte of binary data is ^0x##, where
## is the hexadecimal representation of the data byte. Two ## is the hexadecimal representation of the data byte. Two
ASCII characters (0-9, a-f, A-F) must follow the `^0x' ASCII characters (0-9, a-f, A-F) must follow the '^0x'
control prefix. For example, `^0x0D^0x0A' is interpreted as a control prefix. For example, '^0x0D^0x0A' is interpreted as a
carriage return followed by a line feed." carriage return followed by a line feed."
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
probeCapabilities OBJECT-TYPE probeCapabilities OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
etherStats(0), etherStats(0),
historyControl(1), historyControl(1),
etherHistory(2), etherHistory(2),
alarm(3), alarm(3),
hosts(4), hosts(4),
skipping to change at page 113, line 38 skipping to change at page 97, line 47
9 10 hours from UTC 0..11 9 10 hours from UTC 0..11
10 11 minutes from UTC 0..59 10 11 minutes from UTC 0..59
For example, Tuesday May 26, 1992 at 1:30:15 PM For example, Tuesday May 26, 1992 at 1:30:15 PM
EDT would be displayed as: EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0 1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then Note that if only local time is known, then
timezone information (fields 8-10) is not timezone information (fields 8-10) is not
present, and if no time information is known, the null present, and that if no time information is known, the
string is returned." null string is returned."
::= { probeConfig 4 } ::= { probeConfig 4 }
probeResetControl OBJECT-TYPE probeResetControl OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
running(1), running(1),
warmBoot(2), warmBoot(2),
coldBoot(3) coldBoot(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Setting this object to warmBoot(2) causes the device to "Setting this object to warmBoot(2) causes the device to
restart the application software with current configuration restart the application software with current configuration
parameters saved in non-volatile memory. Setting this parameters saved in non-volatile memory. Setting this
object to coldBoot(3) causes the device to reinitialize object to coldBoot(3) causes the device to reinitialize
configuration parameters in non-volatile memory to default configuration parameters in non-volatile memory to default
values and restart the application software. When the device values and to restart the application software. When the device
is running normally, this variable has a value of is running normally, this variable has a value of
running(1)." running(1)."
::= { probeConfig 5 } ::= { probeConfig 5 }
-- The following download objects do not restrict an implementation -- The following download objects do not restrict an implementation
-- from implementing additional download mechanisms (controlled in an -- from implementing additional download mechanisms (controlled in an
-- implementation-specific manner). Further, in the case where the RMON -- implementation-specific manner). Further, in the case where the RMON
-- agent shares a processor with other types of systems, the -- agent shares a processor with other types of systems, the
-- implementation is not required to download those non-RMON functions -- implementation is not required to download those non-RMON functions
-- with this mechanism. -- with this mechanism.
probeDownloadFile OBJECT-TYPE probeDownloadFile OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..127)) SYNTAX DisplayString (SIZE(0..127))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The file name to be downloaded from the TFTP server when a "The file name to be downloaded from the TFTP server when a
download is next requested via this MIB. This value is set to download is next requested via this MIB. This value is set to
the zero length string when no file name has been specified. the zero-length string when no file name has been specified.
This object has been deprecated as it has not had enough This object has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability to
meet the requirements of a Draft Standard." meet the requirements of a Draft Standard."
::= { probeConfig 6 } ::= { probeConfig 6 }
probeDownloadTFTPServer OBJECT-TYPE probeDownloadTFTPServer OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The IP address of the TFTP server that contains the boot "The IP address of the TFTP server that contains the boot
image to load when a download is next requested via this MIB. image to load when a download is next requested via this MIB.
This value is set to `0.0.0.0' when no IP address has been This value is set to '0.0.0.0' when no IP address has been
specified. specified.
This object has been deprecated as it has not had enough This object has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability to
meet the requirements of a Draft Standard." meet the requirements of a Draft Standard."
::= { probeConfig 7 } ::= { probeConfig 7 }
probeDownloadAction OBJECT-TYPE probeDownloadAction OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notDownloading(1), notDownloading(1),
downloadToPROM(2), downloadToPROM(2),
downloadToRAM(3) downloadToRAM(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"When this object is set to downloadToRAM(3) or "When this object is set to downloadToRAM(3) or
downloadToPROM(2), the device will discontinue its downloadToPROM(2), the device will discontinue its
normal operation and begin download of the image specified normal operation and begin download of the image specified
by probeDownloadFile from the server specified by by probeDownloadFile from the server specified by
probeDownloadTFTPServer using the TFTP protocol. If probeDownloadTFTPServer using the TFTP protocol. If
downloadToRAM(3) is specified, the new image is copied downloadToRAM(3) is specified, the new image is copied
to RAM only (the old image remains unaltered in the flash to RAM only (the old image remains unaltered in the flash
EPROM). If downloadToPROM(2) is specified EPROM). If downloadToPROM(2) is specified,
the new image is written to the flash EPROM the new image is written to the flash EPROM
memory after its checksum has been verified to be correct. memory after its checksum has been verified to be correct.
When the download process is completed, the device will When the download process is completed, the device will
warm boot to restart the newly loaded application. warm boot to restart the newly loaded application.
When the device is not downloading, this object will have When the device is not downloading, this object will have
a value of notDownloading(1). a value of notDownloading(1).
This object has been deprecated as it has not had enough This object has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability to
meet the requirements of a Draft Standard." meet the requirements of a Draft Standard."
::= { probeConfig 8 } ::= { probeConfig 8 }
probeDownloadStatus OBJECT-TYPE probeDownloadStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
downloadSuccess(1), downloadSuccess(1),
downloadStatusUnknown(2), downloadStatusUnknown(2),
downloadGeneralError(3), downloadGeneralError(3),
downloadNoResponseFromServer(4), downloadNoResponseFromServer(4),
skipping to change at page 116, line 12 skipping to change at page 100, line 10
downloadTftpFileNotFound(7), downloadTftpFileNotFound(7),
downloadTftpAccessViolation(8) downloadTftpAccessViolation(8)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The status of the last download procedure, if any. This "The status of the last download procedure, if any. This
object will have a value of downloadStatusUnknown(2) if no object will have a value of downloadStatusUnknown(2) if no
download process has been performed. download process has been performed.
This object has been deprecated as it has not had enough This object has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability to
meet the requirements of a Draft Standard." meet the requirements of a Draft Standard."
::= { probeConfig 9 } ::= { probeConfig 9 }
serialConfigTable OBJECT-TYPE serialConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF SerialConfigEntry SYNTAX SEQUENCE OF SerialConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A table of serial interface configuration entries. This data "A table of serial interface configuration entries. This data
will be stored in non-volatile memory and preserved across will be stored in non-volatile memory and preserved across
probe resets or power loss. probe resets or power loss.
This table has been deprecated as it has not had enough This table has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability to
meet the requirements of a Draft Standard." meet the requirements of a Draft Standard."
::= { probeConfig 10 } ::= { probeConfig 10 }
serialConfigEntry OBJECT-TYPE serialConfigEntry OBJECT-TYPE
SYNTAX SerialConfigEntry SYNTAX SerialConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A set of configuration parameters for a particular "A set of configuration parameters for a particular
skipping to change at page 117, line 21 skipping to change at page 101, line 15
} }
serialMode OBJECT-TYPE serialMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
direct(1), direct(1),
modem(2) modem(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The type of incoming connection to expect on this serial "The type of incoming connection to be expected on this
interface." serial interface."
DEFVAL { direct } DEFVAL { direct }
::= { serialConfigEntry 1 } ::= { serialConfigEntry 1 }
serialProtocol OBJECT-TYPE serialProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
slip(2), slip(2),
ppp(3) ppp(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 118, line 15 skipping to change at page 102, line 5
serialDialoutTimeout in the case where the probe has initiated serialDialoutTimeout in the case where the probe has initiated
the connection for the purpose of sending a trap." the connection for the purpose of sending a trap."
DEFVAL { 300 } DEFVAL { 300 }
::= { serialConfigEntry 3 } ::= { serialConfigEntry 3 }
serialModemInitString OBJECT-TYPE serialModemInitString OBJECT-TYPE
SYNTAX ControlString (SIZE (0..255)) SYNTAX ControlString (SIZE (0..255))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A control string which controls how a modem attached to this "A control string that controls how a modem attached to this
serial interface should be initialized. The initialization serial interface should be initialized. The initialization
is performed once during startup and again after each is performed once during startup and again after each
connection is terminated if the associated serialMode has the connection is terminated if the associated serialMode has the
value of modem(2). value of modem(2).
A control string that is appropriate for a wide variety of A control string that is appropriate for a wide variety of
modems is: '^s^MATE0Q0V1X4 S0=1 S2=43^M'." modems is: '^s^MATE0Q0V1X4 S0=1 S2=43^M'."
::= { serialConfigEntry 4 } ::= { serialConfigEntry 4 }
serialModemHangUpString OBJECT-TYPE serialModemHangUpString OBJECT-TYPE
SYNTAX ControlString (SIZE (0..255)) SYNTAX ControlString (SIZE (0..255))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A control string which specifies how to disconnect a modem "A control string that specifies how to disconnect a modem
connection on this serial interface. This object is only connection on this serial interface. This object is only
meaningful if the associated serialMode has the value meaningful if the associated serialMode has the value
of modem(2). of modem(2).
A control string that is appropriate for a wide variety of A control string that is appropriate for a wide variety of
modems is: '^d2^s+++^d2^sATH0^M^d2'." modems is: '^d2^s+++^d2^sATH0^M^d2'."
::= { serialConfigEntry 5 } ::= { serialConfigEntry 5 }
serialModemConnectResp OBJECT-TYPE serialModemConnectResp OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255)) SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"An ASCII string containing substrings that describe the "An ASCII string containing substrings that describe the
skipping to change at page 120, line 28 skipping to change at page 104, line 12
objects in the entry have an appropriate value." objects in the entry have an appropriate value."
::= { serialConfigEntry 9 } ::= { serialConfigEntry 9 }
netConfigTable OBJECT-TYPE netConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF NetConfigEntry SYNTAX SEQUENCE OF NetConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A table of netConfigEntries. "A table of netConfigEntries.
This table has been deprecated as it has not had enough This table has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability to
meet the requirements of a Draft Standard." meet the requirements of a Draft Standard."
::= { probeConfig 11 } ::= { probeConfig 11 }
netConfigEntry OBJECT-TYPE netConfigEntry OBJECT-TYPE
SYNTAX NetConfigEntry SYNTAX NetConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A set of configuration parameters for a particular "A set of configuration parameters for a particular
skipping to change at page 121, line 16 skipping to change at page 104, line 44
netConfigStatus RowStatus netConfigStatus RowStatus
} }
netConfigIPAddress OBJECT-TYPE netConfigIPAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The IP address of this Net interface. The default value "The IP address of this Net interface. The default value
for this object is 0.0.0.0. If either the netConfigIPAddress for this object is 0.0.0.0. If either the netConfigIPAddress
or netConfigSubnetMask are 0.0.0.0, then when the device or netConfigSubnetMask is 0.0.0.0, then when the device
boots, it may use BOOTP to try to figure out what these boots, it may use BOOTP to try to figure out what these
values should be. If BOOTP fails, before the device values should be. If BOOTP fails before the device
can talk on the network, this value must be configured can talk on the network, this value must be configured
(e.g., through a terminal attached to the device). If BOOTP is (e.g., through a terminal attached to the device). If BOOTP is
used, care should be taken to not send BOOTP broadcasts too used, care should be taken to not send BOOTP broadcasts too
frequently and to eventually send very infrequently if no frequently and to eventually send them very infrequently if no
replies are received." replies are received."
::= { netConfigEntry 1 } ::= { netConfigEntry 1 }
netConfigSubnetMask OBJECT-TYPE netConfigSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The subnet mask of this Net interface. The default value "The subnet mask of this Net interface. The default value
for this object is 0.0.0.0. If either the netConfigIPAddress for this object is 0.0.0.0. If either the netConfigIPAddress
or netConfigSubnetMask are 0.0.0.0, then when the device or netConfigSubnetMask is 0.0.0.0, then when the device
boots, it may use BOOTP to try to figure out what these boots, it may use BOOTP to try to figure out what these
values should be. If BOOTP fails, before the device values should be. If BOOTP fails before the device
can talk on the network, this value must be configured can talk on the network, this value must be configured
(e.g., through a terminal attached to the device). If BOOTP is (e.g., through a terminal attached to the device). If BOOTP is
used, care should be taken to not send BOOTP broadcasts too used, care should be taken to not send BOOTP broadcasts too
frequently and to eventually send very infrequently if no frequently and to eventually send them very infrequently if no
replies are received." replies are received."
::= { netConfigEntry 2 } ::= { netConfigEntry 2 }
netConfigStatus OBJECT-TYPE netConfigStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The status of this netConfigEntry. "The status of this netConfigEntry.
skipping to change at page 122, line 28 skipping to change at page 105, line 51
-- Trap Destination Table -- Trap Destination Table
-- --
-- This table defines the destination addresses for traps generated -- This table defines the destination addresses for traps generated
-- from the device. This table maps a community to one or more trap -- from the device. This table maps a community to one or more trap
-- destination entries. -- destination entries.
-- --
-- The same trap will be sent to all destinations specified in the -- The same trap will be sent to all destinations specified in the
-- entries that have the same trapDestCommunity as the eventCommunity -- entries that have the same trapDestCommunity as the eventCommunity
-- (as defined by RMON MIB), as long as no access control mechanism -- (as defined by RMON MIB), as long as no access control mechanism
-- (e.g., VACM) prohibits sending to one or more of the destinations.
-- Information in this table will be stored in non-volatile memory. -- Information in this table will be stored in non-volatile memory.
-- If the device has gone through a hard restart, this information -- If the device has gone through a hard restart, this information
-- will be reset to its default state. -- will be reset to its default state.
trapDestTable OBJECT-TYPE trapDestTable OBJECT-TYPE
SYNTAX SEQUENCE OF TrapDestEntry SYNTAX SEQUENCE OF TrapDestEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A list of trap destination entries." "A list of trap destination entries."
::= { probeConfig 13 } ::= { probeConfig 13 }
skipping to change at page 122, line 46 skipping to change at page 106, line 21
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A list of trap destination entries." "A list of trap destination entries."
::= { probeConfig 13 } ::= { probeConfig 13 }
trapDestEntry OBJECT-TYPE trapDestEntry OBJECT-TYPE
SYNTAX TrapDestEntry SYNTAX TrapDestEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This entry includes a destination IP address to which to send "This entry includes a destination IP address to which
traps for this community." traps are sent for this community."
INDEX { trapDestIndex } INDEX { trapDestIndex }
::= { trapDestTable 1 } ::= { trapDestTable 1 }
TrapDestEntry ::= SEQUENCE { TrapDestEntry ::= SEQUENCE {
trapDestIndex Integer32, trapDestIndex Integer32,
trapDestCommunity OCTET STRING, trapDestCommunity OCTET STRING,
trapDestProtocol INTEGER, trapDestProtocol INTEGER,
trapDestAddress OCTET STRING, trapDestAddress OCTET STRING,
trapDestOwner OwnerString, trapDestOwner OwnerString,
trapDestStatus RowStatus trapDestStatus RowStatus
skipping to change at page 123, line 34 skipping to change at page 107, line 4
trapDestCommunity OBJECT-TYPE trapDestCommunity OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..127)) SYNTAX OCTET STRING (SIZE(0..127))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A community to which this destination address belongs. "A community to which this destination address belongs.
This entry is associated with any eventEntries in the RMON This entry is associated with any eventEntries in the RMON
MIB whose value of eventCommunity is equal to the value of MIB whose value of eventCommunity is equal to the value of
this object. Every time an associated event entry sends a this object. Every time an associated event entry sends a
trap due to an event, that trap will be sent to each trap due to an event, that trap will be sent to each
address in the trapDestTable with a trapDestCommunity equal to address in the trapDestTable with a trapDestCommunity equal
eventCommunity, as long as no access control mechanism to eventCommunity, as long as no access control mechanism
precludes it (e.g., VACM). precludes it (e.g., VACM).
This object may not be modified if the associated This object may not be modified if the associated
trapDestStatus object is equal to active(1)." trapDestStatus object is equal to active(1)."
::= { trapDestEntry 2 } ::= { trapDestEntry 2 }
trapDestProtocol OBJECT-TYPE trapDestProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ip(1), ip(1),
ipx(2) ipx(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The protocol with which to send this trap." "The protocol with which this trap is to be sent."
::= { trapDestEntry 3 } ::= { trapDestEntry 3 }
trapDestAddress OBJECT-TYPE trapDestAddress OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The address to send traps on behalf of this entry. "The destination address for traps on behalf of this entry.
If the associated trapDestProtocol object is equal to ip(1), If the associated trapDestProtocol object is equal to ip(1),
the encoding of this object is the same as the snmpUDPAddress the encoding of this object is the same as the snmpUDPAddress
textual convention in RFC 3417 'Transport Mappings for the textual convention in RFC 3417, 'Transport Mappings for the
Simple Network Management Protocol(SNMP)' [RFC3417]: Simple Network Management Protocol(SNMP)' [RFC3417]:
-- for a SnmpUDPAddress of length 6: -- for a SnmpUDPAddress of length 6:
-- --
-- octets contents encoding -- octets contents encoding
-- 1-4 IP-address network-byte order -- 1-4 IP-address network-byte order
-- 5-6 UDP-port network-byte order -- 5-6 UDP-port network-byte order
If the associated trapDestProtocol object is equal to ipx(2), If the associated trapDestProtocol object is equal to ipx(2),
the encoding of this object is the same as the snmpIPXAddress the encoding of this object is the same as the snmpIPXAddress
textual convention in RFC 3417 "Transport Mappings for the textual convention in RFC 3417, 'Transport Mappings for the
Simple Network Management Protocol(SNMP)" [RFC3417]: Simple Network Management Protocol (SNMP)' [RFC3417]:
-- for a SnmpIPXAddress of length 12: -- for a SnmpIPXAddress of length 12:
-- --
-- octets contents encoding -- octets contents encoding
-- 1-4 network-number network-byte order -- 1-4 network-number network-byte order
-- 5-10 physical-address network-byte order -- 5-10 physical-address network-byte order
-- 11-12 socket-number network-byte order -- 11-12 socket-number network-byte order
This object may not be modified if the associated This object may not be modified if the associated
trapDestStatus object is equal to active(1)." trapDestStatus object is equal to active(1)."
::= { trapDestEntry 4 } ::= { trapDestEntry 4 }
skipping to change at page 125, line 32 skipping to change at page 108, line 42
-- serialConnectionTable stores the parameters for such connection -- serialConnectionTable stores the parameters for such connection
-- initiation. -- initiation.
serialConnectionTable OBJECT-TYPE serialConnectionTable OBJECT-TYPE
SYNTAX SEQUENCE OF SerialConnectionEntry SYNTAX SEQUENCE OF SerialConnectionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A list of serialConnectionEntries. "A list of serialConnectionEntries.
This table has been deprecated as it has not had enough This table has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability
meet the requirements of a Draft Standard." to meet the requirements of a Draft Standard."
::= { probeConfig 14 } ::= { probeConfig 14 }
serialConnectionEntry OBJECT-TYPE serialConnectionEntry OBJECT-TYPE
SYNTAX SerialConnectionEntry SYNTAX SerialConnectionEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Configuration for a SLIP link over a serial line." "Configuration for a SLIP link over a serial line."
INDEX { serialConnectIndex } INDEX { serialConnectIndex }
::= { serialConnectionTable 1 } ::= { serialConnectionTable 1 }
skipping to change at page 126, line 44 skipping to change at page 110, line 4
serialConnectType OBJECT-TYPE serialConnectType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
direct(1), direct(1),
modem(2), modem(2),
switch(3), switch(3),
modemSwitch(4) modemSwitch(4)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The type of outgoing connection to make. If this object "The type of outgoing connection to be made. If this object
has the value direct(1), then a direct serial connection has the value direct(1), then a direct serial connection
is assumed. If this object has the value modem(2), is assumed. If this object has the value modem(2),
then serialConnectDialString will be used to make a modem then serialConnectDialString will be used to make a modem
connection. If this object has the value switch(3), connection. If this object has the value switch(3),
then serialConnectSwitchConnectSeq will be used to establish then serialConnectSwitchConnectSeq will be used to establish
the connection over a serial data switch, and the connection over a serial data switch, and
serialConnectSwitchDisconnectSeq will be used to terminate serialConnectSwitchDisconnectSeq will be used to terminate
the connection. If this object has the value the connection. If this object has the value
modem-switch(4), then a modem connection will be made first modem-switch(4), then a modem connection will be made first,
followed by the switch connection. followed by the switch connection.
This object may not be modified if the associated This object may not be modified if the associated
serialConnectStatus object is equal to active(1)." serialConnectStatus object is equal to active(1)."
DEFVAL { direct } DEFVAL { direct }
::= { serialConnectionEntry 3 } ::= { serialConnectionEntry 3 }
serialConnectDialString OBJECT-TYPE serialConnectDialString OBJECT-TYPE
SYNTAX ControlString (SIZE(0..255)) SYNTAX ControlString (SIZE(0..255))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A control string which specifies how to dial the phone "A control string that specifies how to dial the phone
number in order to establish a modem connection. The number in order to establish a modem connection. The
string should include dialing prefix and suffix. For string should include the dialing prefix and suffix. For
example: ``^s^MATD9,888-1234^M'' will instruct the Probe example: '^s^MATD9,888-1234^M' will instruct the Probe
to send a carriage return followed by the dialing prefix to send a carriage return, followed by the dialing prefix
``ATD'', the phone number ``9,888-1234'', and a carriage 'ATD', the phone number '9,888-1234', and a carriage
return as the dialing suffix. return as the dialing suffix.
This object may not be modified if the associated This object may not be modified if the associated
serialConnectStatus object is equal to active(1)." serialConnectStatus object is equal to active(1)."
::= { serialConnectionEntry 4 } ::= { serialConnectionEntry 4 }
serialConnectSwitchConnectSeq OBJECT-TYPE serialConnectSwitchConnectSeq OBJECT-TYPE
SYNTAX ControlString (SIZE(0..255)) SYNTAX ControlString (SIZE(0..255))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A control string which specifies how to establish a "A control string that specifies how to establish a
data switch connection. data switch connection.
This object may not be modified if the associated This object may not be modified if the associated
serialConnectStatus object is equal to active(1)." serialConnectStatus object is equal to active(1)."
::= { serialConnectionEntry 5 } ::= { serialConnectionEntry 5 }
serialConnectSwitchDisconnectSeq OBJECT-TYPE serialConnectSwitchDisconnectSeq OBJECT-TYPE
SYNTAX ControlString (SIZE(0..255)) SYNTAX ControlString (SIZE(0..255))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A control string which specifies how to terminate a "A control string that specifies how to terminate a
data switch connection. data switch connection.
This object may not be modified if the associated This object may not be modified if the associated
serialConnectStatus object is equal to active(1)." serialConnectStatus object is equal to active(1)."
::= { serialConnectionEntry 6 } ::= { serialConnectionEntry 6 }
serialConnectSwitchResetSeq OBJECT-TYPE serialConnectSwitchResetSeq OBJECT-TYPE
SYNTAX ControlString (SIZE(0..255)) SYNTAX ControlString (SIZE(0..255))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A control string which specifies how to reset a data "A control string that specifies how to reset a data
switch in the event of a timeout. switch in the event of a timeout.
This object may not be modified if the associated This object may not be modified if the associated
serialConnectStatus object is equal to active(1)." serialConnectStatus object is equal to active(1)."
::= { serialConnectionEntry 7 } ::= { serialConnectionEntry 7 }
serialConnectOwner OBJECT-TYPE serialConnectOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The entity that configured this entry and is "The entity that configured this entry and is
skipping to change at page 129, line 5 skipping to change at page 112, line 4
If the manager attempts to set this object to active(1) when If the manager attempts to set this object to active(1) when
the serialConnectType is set to modem(2) or modem-switch(4) the serialConnectType is set to modem(2) or modem-switch(4)
and the serialConnectDialString is a zero-length string or and the serialConnectDialString is a zero-length string or
cannot be correctly parsed as a ConnectString, the set cannot be correctly parsed as a ConnectString, the set
request will be rejected with badValue(3). request will be rejected with badValue(3).
If the manager attempts to set this object to active(1) when If the manager attempts to set this object to active(1) when
the serialConnectType is set to switch(3) or modem-switch(4) the serialConnectType is set to switch(3) or modem-switch(4)
and the serialConnectSwitchConnectSeq, and the serialConnectSwitchConnectSeq,
the serialConnectSwitchDisconnectSeq, or the serialConnectSwitchDisconnectSeq, or
the serialConnectSwitchResetSeq are zero-length strings the serialConnectSwitchResetSeq is a zero-length string
or cannot be correctly parsed as ConnectStrings, the set or cannot be correctly parsed as a ConnectString, the set
request will be rejected with badValue(3). request will be rejected with badValue(3).
An entry may not exist in the active state unless all An entry may not exist in the active state unless all
objects in the entry have an appropriate value." objects in the entry have an appropriate value."
::= { serialConnectionEntry 9 } ::= { serialConnectionEntry 9 }
-- --
-- Extensions to the RMON 1 MIB for RMON 2 devices -- Extensions to the RMON 1 MIB for RMON 2 devices
-- --
-- These extensions include the standard LastCreateTime Textual -- These extensions include the standard LastCreateTime Textual
skipping to change at page 130, line 10 skipping to change at page 113, line 4
EtherStats2Entry ::= SEQUENCE { EtherStats2Entry ::= SEQUENCE {
etherStatsDroppedFrames Counter32, etherStatsDroppedFrames Counter32,
etherStatsCreateTime LastCreateTime etherStatsCreateTime LastCreateTime
} }
etherStatsDroppedFrames OBJECT-TYPE etherStatsDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { etherStats2Entry 1 } ::= { etherStats2Entry 1 }
etherStatsCreateTime OBJECT-TYPE etherStatsCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
skipping to change at page 131, line 16 skipping to change at page 114, line 7
HistoryControl2Entry ::= SEQUENCE { HistoryControl2Entry ::= SEQUENCE {
historyControlDroppedFrames Counter32 historyControlDroppedFrames Counter32
} }
historyControlDroppedFrames OBJECT-TYPE historyControlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { historyControl2Entry 1 } ::= { historyControl2Entry 1 }
hostControl2Table OBJECT-TYPE hostControl2Table OBJECT-TYPE
SYNTAX SEQUENCE OF HostControl2Entry SYNTAX SEQUENCE OF HostControl2Entry
skipping to change at page 132, line 13 skipping to change at page 114, line 48
HostControl2Entry ::= SEQUENCE { HostControl2Entry ::= SEQUENCE {
hostControlDroppedFrames Counter32, hostControlDroppedFrames Counter32,
hostControlCreateTime LastCreateTime hostControlCreateTime LastCreateTime
} }
hostControlDroppedFrames OBJECT-TYPE hostControlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { hostControl2Entry 1 } ::= { hostControl2Entry 1 }
hostControlCreateTime OBJECT-TYPE hostControlCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
skipping to change at page 133, line 21 skipping to change at page 116, line 4
MatrixControl2Entry ::= SEQUENCE { MatrixControl2Entry ::= SEQUENCE {
matrixControlDroppedFrames Counter32, matrixControlDroppedFrames Counter32,
matrixControlCreateTime LastCreateTime matrixControlCreateTime LastCreateTime
} }
matrixControlDroppedFrames OBJECT-TYPE matrixControlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { matrixControl2Entry 1 } ::= { matrixControl2Entry 1 }
matrixControlCreateTime OBJECT-TYPE matrixControlCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
skipping to change at page 134, line 29 skipping to change at page 117, line 8
Channel2Entry ::= SEQUENCE { Channel2Entry ::= SEQUENCE {
channelDroppedFrames Counter32, channelDroppedFrames Counter32,
channelCreateTime LastCreateTime channelCreateTime LastCreateTime
} }
channelDroppedFrames OBJECT-TYPE channelDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { channel2Entry 1 } ::= { channel2Entry 1 }
channelCreateTime OBJECT-TYPE channelCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
skipping to change at page 135, line 17 skipping to change at page 117, line 40
between polls." between polls."
::= { channel2Entry 2 } ::= { channel2Entry 2 }
tokenRingMLStats2Table OBJECT-TYPE tokenRingMLStats2Table OBJECT-TYPE
SYNTAX SEQUENCE OF TokenRingMLStats2Entry SYNTAX SEQUENCE OF TokenRingMLStats2Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Contains the RMON-2 augmentations to RMON-1. "Contains the RMON-2 augmentations to RMON-1.
This table has been deprecated as it has not had enough This table has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability
meet the requirements of a Draft Standard." to meet the requirements of a Draft Standard."
::= { statistics 5 } ::= { statistics 5 }
tokenRingMLStats2Entry OBJECT-TYPE tokenRingMLStats2Entry OBJECT-TYPE
SYNTAX TokenRingMLStats2Entry SYNTAX TokenRingMLStats2Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Contains the RMON-2 augmentations to RMON-1." "Contains the RMON-2 augmentations to RMON-1."
AUGMENTS { tokenRingMLStatsEntry } AUGMENTS { tokenRingMLStatsEntry }
::= { tokenRingMLStats2Table 1 } ::= { tokenRingMLStats2Table 1 }
skipping to change at page 135, line 41 skipping to change at page 118, line 16
TokenRingMLStats2Entry ::= SEQUENCE { TokenRingMLStats2Entry ::= SEQUENCE {
tokenRingMLStatsDroppedFrames Counter32, tokenRingMLStatsDroppedFrames Counter32,
tokenRingMLStatsCreateTime LastCreateTime tokenRingMLStatsCreateTime LastCreateTime
} }
tokenRingMLStatsDroppedFrames OBJECT-TYPE tokenRingMLStatsDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { tokenRingMLStats2Entry 1 } ::= { tokenRingMLStats2Entry 1 }
tokenRingMLStatsCreateTime OBJECT-TYPE tokenRingMLStatsCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
skipping to change at page 136, line 30 skipping to change at page 118, line 48
between polls." between polls."
::= { tokenRingMLStats2Entry 2 } ::= { tokenRingMLStats2Entry 2 }
tokenRingPStats2Table OBJECT-TYPE tokenRingPStats2Table OBJECT-TYPE
SYNTAX SEQUENCE OF TokenRingPStats2Entry SYNTAX SEQUENCE OF TokenRingPStats2Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Contains the RMON-2 augmentations to RMON-1. "Contains the RMON-2 augmentations to RMON-1.
This table has been deprecated as it has not had enough This table has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability
meet the requirements of a Draft Standard." to meet the requirements of a Draft Standard."
::= { statistics 6 } ::= { statistics 6 }
tokenRingPStats2Entry OBJECT-TYPE tokenRingPStats2Entry OBJECT-TYPE
SYNTAX TokenRingPStats2Entry SYNTAX TokenRingPStats2Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Contains the RMON-2 augmentations to RMON-1." "Contains the RMON-2 augmentations to RMON-1."
AUGMENTS { tokenRingPStatsEntry } AUGMENTS { tokenRingPStatsEntry }
::= { tokenRingPStats2Table 1 } ::= { tokenRingPStats2Table 1 }
skipping to change at page 137, line 10 skipping to change at page 119, line 24
TokenRingPStats2Entry ::= SEQUENCE { TokenRingPStats2Entry ::= SEQUENCE {
tokenRingPStatsDroppedFrames Counter32, tokenRingPStatsDroppedFrames Counter32,
tokenRingPStatsCreateTime LastCreateTime tokenRingPStatsCreateTime LastCreateTime
} }
tokenRingPStatsDroppedFrames OBJECT-TYPE tokenRingPStatsDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { tokenRingPStats2Entry 1 } ::= { tokenRingPStats2Entry 1 }
tokenRingPStatsCreateTime OBJECT-TYPE tokenRingPStatsCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
skipping to change at page 137, line 42 skipping to change at page 120, line 7
between polls." between polls."
::= { tokenRingPStats2Entry 2 } ::= { tokenRingPStats2Entry 2 }
ringStationControl2Table OBJECT-TYPE ringStationControl2Table OBJECT-TYPE
SYNTAX SEQUENCE OF RingStationControl2Entry SYNTAX SEQUENCE OF RingStationControl2Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Contains the RMON-2 augmentations to RMON-1. "Contains the RMON-2 augmentations to RMON-1.
This table has been deprecated as it has not had enough This table has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability
meet the requirements of a Draft Standard." to meet the requirements of a Draft Standard."
::= { tokenRing 7 } ::= { tokenRing 7 }
ringStationControl2Entry OBJECT-TYPE ringStationControl2Entry OBJECT-TYPE
SYNTAX RingStationControl2Entry SYNTAX RingStationControl2Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Contains the RMON-2 augmentations to RMON-1." "Contains the RMON-2 augmentations to RMON-1."
AUGMENTS { ringStationControlEntry } AUGMENTS { ringStationControlEntry }
::= { ringStationControl2Table 1 } ::= { ringStationControl2Table 1 }
skipping to change at page 138, line 21 skipping to change at page 120, line 31
RingStationControl2Entry ::= SEQUENCE { RingStationControl2Entry ::= SEQUENCE {
ringStationControlDroppedFrames Counter32, ringStationControlDroppedFrames Counter32,
ringStationControlCreateTime LastCreateTime ringStationControlCreateTime LastCreateTime
} }
ringStationControlDroppedFrames OBJECT-TYPE ringStationControlDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { ringStationControl2Entry 1 } ::= { ringStationControl2Entry 1 }
ringStationControlCreateTime OBJECT-TYPE ringStationControlCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
skipping to change at page 139, line 9 skipping to change at page 121, line 15
between polls." between polls."
::= { ringStationControl2Entry 2 } ::= { ringStationControl2Entry 2 }
sourceRoutingStats2Table OBJECT-TYPE sourceRoutingStats2Table OBJECT-TYPE
SYNTAX SEQUENCE OF SourceRoutingStats2Entry SYNTAX SEQUENCE OF SourceRoutingStats2Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Contains the RMON-2 augmentations to RMON-1. "Contains the RMON-2 augmentations to RMON-1.
This table has been deprecated as it has not had enough This table has been deprecated, as it has not had enough
independent implementations to demonstrate interoperability to independent implementations to demonstrate interoperability
meet the requirements of a Draft Standard." to meet the requirements of a Draft Standard."
::= { tokenRing 8 } ::= { tokenRing 8 }
sourceRoutingStats2Entry OBJECT-TYPE sourceRoutingStats2Entry OBJECT-TYPE
SYNTAX SourceRoutingStats2Entry SYNTAX SourceRoutingStats2Entry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Contains the RMON-2 augmentations to RMON-1." "Contains the RMON-2 augmentations to RMON-1."
AUGMENTS { sourceRoutingStatsEntry } AUGMENTS { sourceRoutingStatsEntry }
::= { sourceRoutingStats2Table 1 } ::= { sourceRoutingStats2Table 1 }
skipping to change at page 139, line 33 skipping to change at page 121, line 39
SourceRoutingStats2Entry ::= SEQUENCE { SourceRoutingStats2Entry ::= SEQUENCE {
sourceRoutingStatsDroppedFrames Counter32, sourceRoutingStatsDroppedFrames Counter32,
sourceRoutingStatsCreateTime LastCreateTime sourceRoutingStatsCreateTime LastCreateTime
} }
sourceRoutingStatsDroppedFrames OBJECT-TYPE sourceRoutingStatsDroppedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The total number of frames which were received by the probe "The total number of frames that were received by the probe
and therefore not accounted for in the *StatsDropEvents, but and therefore not accounted for in the *StatsDropEvents, but
for which the probe chose not to count for this entry for that the probe chose not to count for this entry for
whatever reason. Most often, this event occurs when the probe whatever reason. Most often, this event occurs when the
is out of some resources and decides to shed load from this probe is out of some resources and decides to shed load from
collection. this collection.
This count does not include packets that were not counted This count does not include packets that were not counted
because they had MAC-layer errors. because they had MAC-layer errors.
Note that, unlike the dropEvents counter, this number is the Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped." exact number of frames dropped."
::= { sourceRoutingStats2Entry 1 } ::= { sourceRoutingStats2Entry 1 }
sourceRoutingStatsCreateTime OBJECT-TYPE sourceRoutingStatsCreateTime OBJECT-TYPE
SYNTAX LastCreateTime SYNTAX LastCreateTime
skipping to change at page 140, line 47 skipping to change at page 122, line 49
filterProtocolDirDataLocalIndex OBJECT-TYPE filterProtocolDirDataLocalIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When this object is set to a non-zero value, the filter that "When this object is set to a non-zero value, the filter that
it is associated with performs the following operations on it is associated with performs the following operations on
every packet: every packet:
1) - If the packet doesn't match the protocol directory entry 1) If the packet doesn't match the protocol directory entry
identified by this object, discard the packet and exit identified by this object, discard the packet and exit
(i.e., discard the packet if it is not of the identified (i.e., discard the packet if it is not of the identified
protocol). protocol).
2) - If the associated filterProtocolDirLocalIndex is non-zero
2) If the associated filterProtocolDirLocalIndex is non-zero
and the packet doesn't match the protocol directory and the packet doesn't match the protocol directory
entry identified by that object, discard the packet and entry identified by that object, discard the packet and
exit exit.
3) - If the packet matches, perform the regular filter 3) If the packet matches, perform the regular filter
algorithm as if the beginning of this named protocol is algorithm as if the beginning of this named protocol is
the beginning of the packet, potentially applying the the beginning of the packet, potentially applying the
filterOffset value to move further into the packet." filterOffset value to move further into the packet."
DEFVAL { 0 } DEFVAL { 0 }
::= { filter2Entry 1 } ::= { filter2Entry 1 }
filterProtocolDirLocalIndex OBJECT-TYPE filterProtocolDirLocalIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 142, line 16 skipping to change at page 124, line 10
nlMatrixTopNPkts(1), nlMatrixTopNPkts(1),
nlMatrixTopNOctets(2) nlMatrixTopNOctets(2)
} }
DESCRIPTION DESCRIPTION
"Conformance to RMON2 requires only support for these "Conformance to RMON2 requires only support for these
values of nlMatrixTopNControlRateBase." values of nlMatrixTopNControlRateBase."
GROUP rmon1EnhancementGroup GROUP rmon1EnhancementGroup
DESCRIPTION DESCRIPTION
"The rmon1EnhancementGroup is mandatory for systems "The rmon1EnhancementGroup is mandatory for systems
which implement RMON [RFC2819]" that implement RMON [RFC2819]."
GROUP rmon1EthernetEnhancementGroup GROUP rmon1EthernetEnhancementGroup
DESCRIPTION DESCRIPTION
"The rmon1EthernetEnhancementGroup is optional and is "The rmon1EthernetEnhancementGroup is optional and is
appropriate for systems that implement the Ethernet appropriate for systems that implement the Ethernet
group of RMON [RFC2819]" group of RMON [RFC2819]."
::= { rmon2MIBCompliances 1 } ::= { rmon2MIBCompliances 1 }
rmon2MIBApplicationLayerCompliance MODULE-COMPLIANCE rmon2MIBApplicationLayerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to "Describes the requirements for conformance to
the RMON2 MIB with Application Layer Enhancements." the RMON2 MIB with Application-Layer Enhancements."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { protocolDirectoryGroup, MANDATORY-GROUPS { protocolDirectoryGroup,
protocolDistributionGroup, protocolDistributionGroup,
addressMapGroup, addressMapGroup,
nlHostGroup, nlHostGroup,
nlMatrixGroup, nlMatrixGroup,
alHostGroup, alHostGroup,
alMatrixGroup, alMatrixGroup,
usrHistoryGroup, usrHistoryGroup,
probeInformationGroup } probeInformationGroup }
skipping to change at page 143, line 18 skipping to change at page 125, line 9
alMatrixTopNAllPkts(3), alMatrixTopNAllPkts(3),
alMatrixTopNAllOctets(4) alMatrixTopNAllOctets(4)
} }
DESCRIPTION DESCRIPTION
"Conformance to RMON2 requires only support for these "Conformance to RMON2 requires only support for these
values of alMatrixTopNControlRateBase." values of alMatrixTopNControlRateBase."
GROUP rmon1EnhancementGroup GROUP rmon1EnhancementGroup
DESCRIPTION DESCRIPTION
"The rmon1EnhancementGroup is mandatory for systems "The rmon1EnhancementGroup is mandatory for systems
which implement RMON [RFC2819]" that implement RMON [RFC2819]."
GROUP rmon1EthernetEnhancementGroup GROUP rmon1EthernetEnhancementGroup
DESCRIPTION DESCRIPTION
"The rmon1EthernetEnhancementGroup is optional and is "The rmon1EthernetEnhancementGroup is optional and is
appropriate for systems that implement the Ethernet appropriate for systems that implement the Ethernet
group of RMON [RFC2819]" group of RMON [RFC2819]."
::= { rmon2MIBCompliances 2 } ::= { rmon2MIBCompliances 2 }
protocolDirectoryGroup OBJECT-GROUP protocolDirectoryGroup OBJECT-GROUP
OBJECTS { protocolDirLastChange, OBJECTS { protocolDirLastChange,
protocolDirLocalIndex, protocolDirDescr, protocolDirLocalIndex, protocolDirDescr,
protocolDirType, protocolDirAddressMapConfig, protocolDirType, protocolDirAddressMapConfig,
protocolDirHostConfig, protocolDirMatrixConfig, protocolDirHostConfig, protocolDirMatrixConfig,
protocolDirOwner, protocolDirStatus } protocolDirOwner, protocolDirStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Lists the inventory of protocols the probe has the capability "Lists the inventory of protocols the probe has the
of monitoring and allows the addition, deletion, and capability of monitoring and allows the addition, deletion,
configuration of entries in this list." and configuration of entries in this list."
::= { rmon2MIBGroups 1 } ::= { rmon2MIBGroups 1 }
protocolDistributionGroup OBJECT-GROUP protocolDistributionGroup OBJECT-GROUP
OBJECTS { protocolDistControlDataSource, OBJECTS { protocolDistControlDataSource,
protocolDistControlDroppedFrames, protocolDistControlDroppedFrames,
protocolDistControlCreateTime, protocolDistControlCreateTime,
protocolDistControlOwner, protocolDistControlStatus, protocolDistControlOwner, protocolDistControlStatus,
protocolDistStatsPkts, protocolDistStatsOctets } protocolDistStatsPkts, protocolDistStatsOctets }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 144, line 38 skipping to change at page 126, line 25
hlHostControlAlDeletes, hlHostControlAlDeletes,
hlHostControlAlMaxDesiredEntries, hlHostControlOwner, hlHostControlAlMaxDesiredEntries, hlHostControlOwner,
hlHostControlStatus, nlHostInPkts, nlHostOutPkts, hlHostControlStatus, nlHostInPkts, nlHostOutPkts,
nlHostInOctets, nlHostOutOctets, nlHostInOctets, nlHostOutOctets,
nlHostOutMacNonUnicastPkts, nlHostCreateTime } nlHostOutMacNonUnicastPkts, nlHostCreateTime }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Counts the amount of traffic sent from and to each network "Counts the amount of traffic sent from and to each network
address discovered by the probe. Note that while the address discovered by the probe. Note that while the
hlHostControlTable also has objects that control an optional hlHostControlTable also has objects that control an optional
alHostTable, implementation of the alHostTable is not required alHostTable, implementation of the alHostTable is not
to fully implement this group." required to fully implement this group."
::= { rmon2MIBGroups 4 } ::= { rmon2MIBGroups 4 }
nlMatrixGroup OBJECT-GROUP nlMatrixGroup OBJECT-GROUP
OBJECTS { hlMatrixControlDataSource, OBJECTS { hlMatrixControlDataSource,
hlMatrixControlNlDroppedFrames, hlMatrixControlNlDroppedFrames,
hlMatrixControlNlInserts, hlMatrixControlNlDeletes, hlMatrixControlNlInserts, hlMatrixControlNlDeletes,
hlMatrixControlNlMaxDesiredEntries, hlMatrixControlNlMaxDesiredEntries,
hlMatrixControlAlDroppedFrames, hlMatrixControlAlDroppedFrames,
hlMatrixControlAlInserts, hlMatrixControlAlDeletes, hlMatrixControlAlInserts, hlMatrixControlAlDeletes,
hlMatrixControlAlMaxDesiredEntries, hlMatrixControlAlMaxDesiredEntries,
skipping to change at page 145, line 25 skipping to change at page 127, line 8
nlMatrixTopNControlGrantedSize, nlMatrixTopNControlGrantedSize,
nlMatrixTopNControlStartTime, nlMatrixTopNControlStartTime,
nlMatrixTopNControlOwner, nlMatrixTopNControlStatus, nlMatrixTopNControlOwner, nlMatrixTopNControlStatus,
nlMatrixTopNProtocolDirLocalIndex, nlMatrixTopNProtocolDirLocalIndex,
nlMatrixTopNSourceAddress, nlMatrixTopNDestAddress, nlMatrixTopNSourceAddress, nlMatrixTopNDestAddress,
nlMatrixTopNPktRate, nlMatrixTopNReversePktRate, nlMatrixTopNPktRate, nlMatrixTopNReversePktRate,
nlMatrixTopNOctetRate, nlMatrixTopNReverseOctetRate } nlMatrixTopNOctetRate, nlMatrixTopNReverseOctetRate }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Counts the amount of traffic sent between each pair of "Counts the amount of traffic sent between each pair of
network addresses discovered by the probe. Note that while the network addresses discovered by the probe. Note that while
hlMatrixControlTable also has objects that control optional the hlMatrixControlTable also has objects that control
alMatrixTables, implementation of the alMatrixTables is not optional alMatrixTables, implementation of the
required to fully implement this group." alMatrixTables is not required to fully implement this
group."
::= { rmon2MIBGroups 5 } ::= { rmon2MIBGroups 5 }
alHostGroup OBJECT-GROUP alHostGroup OBJECT-GROUP
OBJECTS { alHostInPkts, alHostOutPkts, OBJECTS { alHostInPkts, alHostOutPkts,
alHostInOctets, alHostOutOctets, alHostCreateTime } alHostInOctets, alHostOutOctets, alHostCreateTime }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Counts the amount of traffic, by protocol, sent from and to "Counts the amount of traffic, by protocol, sent from and to
each network address discovered by the probe. Implementation each network address discovered by the probe. Implementation
of this group requires implementation of the Network Layer of this group requires implementation of the Network-Layer
Host Group." Host Group."
::= { rmon2MIBGroups 6 } ::= { rmon2MIBGroups 6 }
alMatrixGroup OBJECT-GROUP alMatrixGroup OBJECT-GROUP
OBJECTS { alMatrixSDPkts, alMatrixSDOctets, alMatrixSDCreateTime, OBJECTS { alMatrixSDPkts, alMatrixSDOctets, alMatrixSDCreateTime,
alMatrixDSPkts, alMatrixDSOctets, alMatrixDSCreateTime, alMatrixDSPkts, alMatrixDSOctets, alMatrixDSCreateTime,
alMatrixTopNControlMatrixIndex, alMatrixTopNControlMatrixIndex,
alMatrixTopNControlRateBase, alMatrixTopNControlRateBase,
alMatrixTopNControlTimeRemaining, alMatrixTopNControlTimeRemaining,
alMatrixTopNControlGeneratedReports, alMatrixTopNControlGeneratedReports,
skipping to change at page 146, line 19 skipping to change at page 127, line 47
alMatrixTopNControlOwner, alMatrixTopNControlStatus, alMatrixTopNControlOwner, alMatrixTopNControlStatus,
alMatrixTopNProtocolDirLocalIndex, alMatrixTopNProtocolDirLocalIndex,
alMatrixTopNSourceAddress, alMatrixTopNDestAddress, alMatrixTopNSourceAddress, alMatrixTopNDestAddress,
alMatrixTopNAppProtocolDirLocalIndex, alMatrixTopNAppProtocolDirLocalIndex,
alMatrixTopNPktRate, alMatrixTopNReversePktRate, alMatrixTopNPktRate, alMatrixTopNReversePktRate,
alMatrixTopNOctetRate, alMatrixTopNReverseOctetRate } alMatrixTopNOctetRate, alMatrixTopNReverseOctetRate }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Counts the amount of traffic, by protocol, sent between each "Counts the amount of traffic, by protocol, sent between each
pair of network addresses discovered by the pair of network addresses discovered by the
probe. Implementation of this group requires implementation of probe. Implementation of this group requires implementation
the Network Layer Matrix Group." of the Network-Layer Matrix Group."
::= { rmon2MIBGroups 7 } ::= { rmon2MIBGroups 7 }
usrHistoryGroup OBJECT-GROUP usrHistoryGroup OBJECT-GROUP
OBJECTS { usrHistoryControlObjects, OBJECTS { usrHistoryControlObjects,
usrHistoryControlBucketsRequested, usrHistoryControlBucketsRequested,
usrHistoryControlBucketsGranted, usrHistoryControlBucketsGranted,
usrHistoryControlInterval, usrHistoryControlInterval,
usrHistoryControlOwner, usrHistoryControlStatus, usrHistoryControlOwner, usrHistoryControlStatus,
usrHistoryObjectVariable, usrHistoryObjectSampleType, usrHistoryObjectVariable, usrHistoryObjectSampleType,
usrHistoryIntervalStart, usrHistoryIntervalEnd, usrHistoryIntervalStart, usrHistoryIntervalEnd,
skipping to change at page 146, line 44 skipping to change at page 128, line 24
"The usrHistoryGroup provides user-defined collection of "The usrHistoryGroup provides user-defined collection of
historical information from MIB objects on the probe." historical information from MIB objects on the probe."
::= { rmon2MIBGroups 8 } ::= { rmon2MIBGroups 8 }
probeInformationGroup OBJECT-GROUP probeInformationGroup OBJECT-GROUP
OBJECTS { probeCapabilities, OBJECTS { probeCapabilities,
probeSoftwareRev, probeHardwareRev, probeDateTime } probeSoftwareRev, probeHardwareRev, probeDateTime }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group describes various operating parameters of the "This group describes various operating parameters of the
probe as well as controlling the local time of the probe." probe and controls the local time of the probe."
::= { rmon2MIBGroups 9 } ::= { rmon2MIBGroups 9 }
probeConfigurationGroup OBJECT-GROUP probeConfigurationGroup OBJECT-GROUP
OBJECTS { probeResetControl, probeDownloadFile, OBJECTS { probeResetControl, probeDownloadFile,
probeDownloadTFTPServer, probeDownloadAction, probeDownloadTFTPServer, probeDownloadAction,
probeDownloadStatus, probeDownloadStatus,
serialMode, serialProtocol, serialTimeout, serialMode, serialProtocol, serialTimeout,
serialModemInitString, serialModemHangUpString, serialModemInitString, serialModemHangUpString,
serialModemConnectResp, serialModemNoConnectResp, serialModemConnectResp, serialModemNoConnectResp,
serialDialoutTimeout, serialStatus, serialDialoutTimeout, serialStatus,
skipping to change at page 149, line 7 skipping to change at page 130, line 7
DESCRIPTION DESCRIPTION
"This group adds some enhancements to RMON-1 that help "This group adds some enhancements to RMON-1 that help
management stations. This group is not referenced by any management stations. This group is not referenced by any
MODULE-COMPLIANCE macro because it is 'grandfathered' from MODULE-COMPLIANCE macro because it is 'grandfathered' from
more recent MIB review rules that would require it." more recent MIB review rules that would require it."
::= { rmon2MIBGroups 13 } ::= { rmon2MIBGroups 13 }
END END
7. Security Considerations 7. Security Considerations
In order to implement this MIB, a probe must capture all In order to implement this MIB, a probe must capture all packets on
packets on the locally-attached network, including packets the locally-attached network, including packets between third
between third parties. These packets are analyzed to collect parties. These packets are analyzed to collect network addresses,
network addresses, protocol usage information, and protocol usage information, and conversation statistics. Data of
conversation statistics. Data of this nature may be considered this nature may be considered sensitive in some environments. In
sensitive in some environments. In such environments the such environments, the administrator may wish to restrict SNMP access
administrator may wish to restrict SNMP access to the probe. to the probe.
The usrHistoryGroup periodically samples the values of user- The usrHistoryGroup periodically samples the values of user-specified
specified variables on the probe and stores them in another variables on the probe and stores them in another table. Since the
table. Since the access-control specified for stored snapshot access-control specified for a stored snapshot may be different from
may be different than the access-control for the sampled the access-control for the sampled variable, the agent MUST ensure
variable, the agent MUST ensure that usrHistoryObjectVariable that usrHistoryObjectVariable is not writable in MIB views that don't
is not writable in MIB views that don't already have read already have read access to the entire agent. Because the access
access to the entire agent. Because the access control control configuration can change over time, information could later
configuration can change over time, information could later be be deemed sensitive that would still be accessible to this function.
deemed sensitive that would still be accessible to this For this reason, an agent SHOULD check the access control on every
function. For this reason, an agent SHOULD check the access sample. If an agent doesn't implement the latter check, there is
control on every sample. If an agent doesn't implement the potential for sensitive information to be revealed.
latter check, there is a potential for sensitive information
to be revealed.
A probe implementing this MIB is likely to also implement RMON A probe implementing this MIB is likely to also implement RMON
[RFC2819], which includes functions for returning the contents [RFC2819], which includes functions for returning the contents of
of captured packets, potentially including sensitive user data captured packets, potentially including sensitive user data or
or passwords. It is recommended that SNMP access to these passwords. It is recommended that SNMP access to these functions be
functions be restricted. restricted.
There are a number of management objects defined in this MIB There are a number of management objects defined in this MIB that
that have a MAX-ACCESS clause of read-write and/or read- have a MAX-ACCESS clause of read-write and/or read-create. Such
create. Such objects may be considered sensitive or objects may be considered sensitive or vulnerable in some network
vulnerable in some network environments. The support for SET environments. The support for SET operations in a non-secure
operations in a non-secure environment without proper environment without proper protection can have a negative effect on
protection can have a negative effect on network operations. network operations.
Some of the readable objects in this MIB module (i.e., objects Some of the readable objects in this MIB module (i.e., objects with a
with a MAX-ACCESS other than not-accessible) may be considered MAX-ACCESS other than not-accessible) may be considered sensitive or
sensitive or vulnerable in some network environments. It is vulnerable in some network environments. It is thus important to
thus important to control even GET and/or NOTIFY access to control even GET and/or NOTIFY access to these objects and possibly
these objects and possibly to even encrypt the values of these to even encrypt the values of these objects when sending them over
objects when sending them over the network via SNMP. the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate SNMP versions prior to SNMPv3 did not include adequate security.
security. Even if the network itself is secure (for example Even if the network itself is secure (for example by using IPSec),
by using IPSec), even then, there is no control as to who on even then, there is no control as to who on the secure network is
the secure network is allowed to access and GET/SET allowed to access and GET/SET (read/change/create/delete) the objects
(read/change/create/delete) the objects in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security It is RECOMMENDED that implementers consider the security features as
features as provided by the SNMPv3 framework (see [RFC3410], provided by the SNMPv3 framework (see [RFC3410], section 8),
section 8), including full support for the SNMPv3 including full support for the SNMPv3 cryptographic mechanisms (for
cryptographic mechanisms (for authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
to enable cryptographic security. It is then a enable cryptographic security. It is then a customer/operator
customer/operator responsibility to ensure that the SNMP responsibility to ensure that the SNMP entity giving access to an
entity giving access to an instance of this MIB module is instance of this MIB module is properly configured to give access to
properly configured to give access to the objects only to the objects only to those principals (users) that have legitimate
those principals (users) that have legitimate rights to indeed rights to indeed GET or SET (change/create/delete) them.