draft-ietf-rtfm-meter-mib-00.txt   draft-ietf-rtfm-meter-mib-01.txt 
Internet Engineering Task Force Nevil Brownlee Internet Engineering Task Force Nevil Brownlee
INTERNET-DRAFT The University of Auckland INTERNET-DRAFT The University of Auckland
Traffic Flow Measurement: Meter MIB Traffic Flow Measurement: Meter MIB
<draft-ietf-rtfm-meter-mib-00.txt> <draft-ietf-rtfm-meter-mib-01.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. This Internet Draft is a product of the documents as Internet Drafts. This Internet Draft is a product of the
Realtime Traffic Flow Measurement Working Group of the IETF. Realtime Traffic Flow Measurement Working Group of the IETF.
Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts are draft documents valid for a maximum of six months.
skipping to change at page 2, line ? skipping to change at page 2, line ?
reference material or to cite them other than as a "working draft" or reference material or to cite them other than as a "working draft" or
"work in progress." "work in progress."
Please check the I-D abstract listing contained in the internet-drafts Please check the I-D abstract listing contained in the internet-drafts
Shadow Directories on nic.ddn.mil, nnsc.nsf.net, nic.nordu.net, Shadow Directories on nic.ddn.mil, nnsc.nsf.net, nic.nordu.net,
ftp.nisc.sri.com or munnari.oz.au to learn the current status of this or ftp.nisc.sri.com or munnari.oz.au to learn the current status of this or
any other Internet Draft. any other Internet Draft.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) for A 'Traffic Meter' collects data relating to traffic flows within a
use with network management protocols in TCP/IP-based internets. In network. This document defines a Management Information Base (MIB) for
particular, this memo defines managed objects used for obtaining traffic use in controlling a traffic meter, in particular for specifying the
flow information from network traffic meters. flows to be measured. It also provides an efficient mechanism for
retrieving flow data from the meter using SNMP. Security issues
concerning the operation of traffic meters are summarised.
Contents Contents
1 Introduction 2 1 Introduction 2
2 The Network Management Framework 2 2 The Network Management Framework 2
3 Objects 3 3 Objects 3
3.1 Format of Definitions . . . . . . . . . . . . . . . . . . . . 3 3.1 Format of Definitions . . . . . . . . . . . . . . . . . . . . 4
4 Overview 4
4.1 Scope of Definitions, Textual Conventions . . . . . . . . . . 4
4.2 Usage of the MIB variables . . . . . . . . . . . . . . . . . . 5
4 Overview 3 5 Changes Introduced Since RFC 2064 6
4.1 Scope of Definitions, Textual Conventions . . . . . . . . . . . 4
4.2 Usage of the MIB variables . . . . . . . . . . . . . . . . . . 4
5 Definitions 6 6 Definitions 7
6 Acknowledgements 40 7 Security Considerations 42
7 References 41 8 Acknowledgements 44
8 Security Considerations 42 9 References 44
9 Author's Address 43 10 Author's Address 45
1 Introduction 1 Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects for managing and collecting particular, it describes objects for managing and collecting data from
data from network Realtime Traffic Flow Meters, as described in [9] network Realtime Traffic Flow Meters, as described in [9].
The MIB is 'basic' in the sense that it provides more than enough
information for everyday traffic measurment. Furthermore, it can be
easily extended by adding new attributes as required. The RTFM Working
group is actively pursuing the development of the meter in this way.
2 The Network Management Framework 2 The Network Management Framework
The Internet-standard Network Management Framework consists of three The Internet-standard Network Management Framework consists of three
components. They are: components. They are:
RFC 1155 defines the SMI, the mechanisms used for describing RFC 1155 defines the SMI, the mechanisms used for describing
and naming objects for the purpose of management. RFC 1212 and naming objects for the purpose of management. RFC 1212
defines a more concise description mechanism, which is wholly defines a more concise description mechanism, which is wholly
consistent with the SMI. consistent with the SMI.
skipping to change at page 3, line 46 skipping to change at page 4, line 7
The encoding of an object type is simply how that object type is The encoding of an object type is simply how that object type is
represented using the object type's syntax. Implicitly tied to the represented using the object type's syntax. Implicitly tied to the
notion of an object type's syntax and encoding is how the object type is notion of an object type's syntax and encoding is how the object type is
represented when being transmitted on the network. represented when being transmitted on the network.
The SMI specifies the use of the basic encoding rules of ASN.1 [7], The SMI specifies the use of the basic encoding rules of ASN.1 [7],
subject to the additional requirements imposed by the SNMP. subject to the additional requirements imposed by the SNMP.
3.1 Format of Definitions 3.1 Format of Definitions
Section 4 contains contains the specification of all object types Section 4 contains the specification of all object types contained in
contained in this MIB module. These object types are defined using the this MIB module. These object types are specified using the conventions
conventions defined in [2] and [3]. defined in [2] and [3].
4 Overview 4 Overview
Traffic Flow Measurement seeks to provide a well-defined method for Traffic Flow Measurement seeks to provide a well-defined method for
gathering traffic flow information from networks and internetworks. The gathering traffic flow information from networks and internetworks. The
background for this is given in "Traffic Flow Measurement: Background" background for this is given in "Traffic Flow Measurement: Background"
[8]. The Realtime Traffic Flow Measurement (rtfm) Working Group has [8]. The Realtime Traffic Flow Measurement (rtfm) Working Group has
produced a measurement architecture to achieve it; this is documented in produced a measurement architecture to achieve this goal; this is
"Traffic Flow Measurement: Architecture" [9]. The architecture defines documented in "Traffic Flow Measurement: Architecture" [9]. The
three entities: architecture defines three entities:
- METERS, which observe network traffic flows and build up a table of - METERS, which observe network traffic flows and build up a table of
flow data records for them, flow data records for them,
- METER READERS, which collect traffic flow data from meters, and - METER READERS, which collect traffic flow data from meters, and
- MANAGERS, which oversee the operation of meters and meter readers. - MANAGERS, which oversee the operation of meters and meter readers.
This memo defines the SNMP management information for a Traffic Flow This memo defines the SNMP management information for a Traffic Flow
Meter (TFM). It documents the earlier work of the Internet Accounting Meter (TFM). Work in this field was begun by the Internet Accounting
Working Group, and is intended to provide a starting point for the Working Group. It has been further developed and expanded by the
Realtime Traffic Flow Measurement Working Group. Realtime Traffic Flow Measurement Working Group.
4.1 Scope of Definitions, Textual Conventions 4.1 Scope of Definitions, Textual Conventions
All objects defined in this memo are registered in a single subtree All objects defined in this memo are registered in a single subtree
within the mib-2 namespace [1,2], and are for use in network devices within the mib-2 namespace [1,2], and are for use in network devices
which may perform a PDU forwarding or monitoring function. For these which may perform a PDU forwarding or monitoring function. For these
devices, the value of the ifSpecific variable in the MIB-II [1] has the devices, the value of the ifSpecific variable in the MIB-II [1] has the
OBJECT IDENTIFIER value: OBJECT IDENTIFIER value:
flowMIB OBJECT IDENTIFIER ::= mib-2 40 flowMIB OBJECT IDENTIFIER ::= mib-2 40
as defined below. as defined below.
The RTFM Meter MIB was first produced and tested using SNMPv1. It has The RTFM Meter MIB was first produced and tested using SNMPv1. It was
been converted into SNMPv2 following the guidelines in RFC 1452 [5]. converted into SNMPv2 following the guidelines in RFC 1908 [5].
4.2 Usage of the MIB variables 4.2 Usage of the MIB variables
The MIB breaks into four parts - control, flows, rules and conformance The MIB is organised in four parts - control, data, rules and
statements. conformance statements.
The rules implement the minumum set of packet-matching actions, as set
out in the "Traffic Flow Measurment: Architecture" document [9]. In The rules implement the set of packet-matching actions, as described in
addition they provide for BASIC-style subroutines, allowing a network the "Traffic Flow Measurment: Architecture" document [9]. In addition
manager to dramatically reduce the number of rules required to monitor a they provide for BASIC-style subroutines, allowing a network manager to
large network. dramatically reduce the number of rules required to monitor a large
network.
Traffic flows are identified by a set of attributes for each of their Traffic flows are identified by a set of attributes for each of their
end-points. Attributes include network addresses for each layer of the end-points. Attributes include network addresses for each layer of the
network protocol stack, and 'subscriber ids,' which may be used to network protocol stack, and 'subscriber ids,' which may be used to
identify an accountable entity for the flow. identify an accountable entity for the flow.
The conformance statements are set out as defined in [4]. They explain The conformance statements are set out as defined in [4]. They explain
what must be implemented in a meter which claims to conform to this MIB. what must be implemented in a meter which claims to conform to this MIB.
To retrieve flow data one could simply do a linear scan of the flow To retrieve flow data one could simply do a linear scan of the flow
table. This would certainly work, but would require a lot of protocol table. This would certainly work, but would require a lot of protocol
exchanges. To reduce the overhead in retrieving flow data the flow exchanges. To reduce the overhead in retrieving flow data the flow
table uses a TimeFilter variable, defined as a Textual Convention in the table uses a TimeFilter variable, defined as a Textual Convention in the
RMON2 MIB [10]. This, when used together with SNMPv2's GetBulk request, RMON2 MIB [10].
allows a meter reader to scan the flow table and upload a specified set
of flow attributes for those rows which have changed since the last
reading.
As an alternative method of reading flow data, the MIB provides an index As an alternative method of reading flow data, the MIB provides a view
into the flow table called flowColumnActivityTable. This is (logically) of the flow table called the flowDataPackageTable. This is (logically)
a three-dimensional array, subscripted by flow attribute, activity time a four-dimensional array, subscripted by package selector, ruleset,
and starting flow number. It allows a meter reader to retrieve (in an activity time and starting flow number. The package selector is a
octet string) data for a column of the flow table with a minimum of SNMP sequence of bytes which specifies a list of flow attributes.
overhead. An attempt has been made to include a full ASN.1 definition
of the flowColumnActivityData object. A data package (as returned by the meter) is a sequence of values for
the attributes specified in its selector, encoded using the Basic
Encoding Rules [7]. It allows a meter reader to retrieve all the
attribute values it requires in a single MIB object. This, when used
together with SNMPv2's GetBulk request, allows a meter reader to scan
the flow table and upload a specified set of attribute values for flows
which have changed since the last reading, and which were created by a
specified rule set.
One aspect of data collection which needs emphasis is that all the MIB One aspect of data collection which needs emphasis is that all the MIB
variables are set up to allow multiple independent meter readers to work variables are set up to allow multiple independent meter readers to work
properly, i.e. the flow table indexes are stateless. An alternative properly, i.e. the flow table indexes are stateless. An alternative
approach would have been to 'snapshot' the flow table, which would mean approach would have been to 'snapshot' the flow table, which would mean
that the meter readers would have to be synchronized. The stateless that the meter readers would have to be synchronized. The stateless
approach does mean that two meter readers will never return exactly the approach does mean that two meter readers will never return exactly the
same set of traffic counts, but over long periods (e.g. 15-minute same set of traffic counts, but over long periods (e.g. 15-minute
collections over a day) the discrepancies are acceptable. If one really collections over a day) the discrepancies are acceptable. If one really
needs a snapshot, this can be achieved by switching to an identical rule needs a snapshot, this can be achieved by switching to an identical rule
skipping to change at page 6, line 5 skipping to change at page 6, line 14
The control variables are the minimum set required for a meter reader. The control variables are the minimum set required for a meter reader.
Their number has been whittled down as experience has been gained with Their number has been whittled down as experience has been gained with
the MIB implementation. A few of them are 'general,' i.e. they control the MIB implementation. A few of them are 'general,' i.e. they control
the overall behaviour of the meter. These are set by a single 'master' the overall behaviour of the meter. These are set by a single 'master'
manager, and no other manager should attempt to change their values. manager, and no other manager should attempt to change their values.
The decision as to which manager is the 'master' must be made by the The decision as to which manager is the 'master' must be made by the
network operations personnel responsible; this MIB does not attempt to network operations personnel responsible; this MIB does not attempt to
define any interaction between managers. define any interaction between managers.
There are three other groups of control groups, arranged into tables in There are three other groups of control variables, arranged into tables
the same way as in the RMON2 MIB [10]. They are used as follows: in the same way as in the RMON2 MIB [10]. They are used as follows:
- RULE SET INFO: Before attempting to download a RuleSet, a manager - RULE SET INFO: Before attempting to download a RuleSet, a manager
must create a row in the flowRuleSetInfoTable with must create a row in the flowRuleSetInfoTable and set its
flowRuleInfoStatus set to 'createAndWait' and set flowRuleInfoSize flowRuleInfoSize to a value large enough to hold the RuleSet. When
to a value large enough to hold the RuleSet. When the rule set is the rule set is ready the manager must set flowRuleInfoStatus to
ready the manager must set flowRuleInfoStatus to 'active,' 'active,' indicating that the rule set is ready for use (but not
indicating that the rule set is ready for use (but not yet yet 'running').
'running').
- METER READER INFO: Any meter reader wishing to collect data - METER READER INFO: Any meter reader wishing to collect data
reliably for all flows should first create a row in the reliably for all flows from a RuleSet should first create a row in
flowReaderInfoTable with flowReaderStatus set to 'active.' It the flowReaderInfoTable with flowReaderRuleSet set to that
should write that row's flowReaderLastTime object each time it RuleSet's index in the flowRuleSetInfoTable. It should write that
starts a collection pass through the flow table. The meter will row's flowReaderLastTime object each time it starts a collection
not recover a flow's memory until every meter reader holding a row pass through the flow table. The meter will not recover a flow's
in this table has collected that flow's data. memory until every meter reader holding a row for that flow's
RuleSet has collected the flow's data.
- MANAGER INFO: Any manager wishing to run a rule set in the meter - MANAGER INFO: Any manager wishing to run a RuleSet in the meter
must create a row in the flowManagerInfo table designating the rule must create a row in the flowManagerInfo table, specifying the
set as either a 'current' or a 'standby' rule set, and set the desired RuleSet to run and its corresponding 'standby' Ruleset (if
row's flowManagerStatus variable to 'active.' one is desired). A current RuleSet is 'running' if its
flowManagerRunningStandby value is false(2), similarly a standby
RuleSet is 'running' if flowManagerRunningStandby is true(1).
5 Definitions 5 Changes Introduced Since RFC 2064
The first version of the Meter MIB was published as RFC 2064 in January
1997. The most significant changes since then are summarised below.
- TEXTUAL CONVENTIONS: Greater use is made of textual conventions to
describe the various types of addresses used by the meter.
- PACKET MATCHING ATTRIBUTES: Computed attributes (e.g. FlowClass
and FlowKind) may now be tested. This allows one to use these
variables to store information during packet matching.
A new attribute, MatchingStoD, has been added. Its value is 1
while a packet is being matched with its adresses in 'wire'
(source-to-destination) order.
- FLOOD MODE: This is now a read-write variable. Setting it to
false(2) switches the meter out of flood mode and back to normal
operation.
- CONTROL TABLES: Several variables have been added to the RuleSet,
Reader and Manager tables to provide more effective control of the
meter's activities.
- FLOW TABLE: 64-bit counters are used for octet and PDU counts.
This reduces the problems caused by the wrap-around of 32-bit
counters in earlier versions.
flowDataRuleSet is now used as an index to the flow table. This
allows a meter reader to collect only those flow table rows created
by a specified RuleSet.
- DATA PACKAGES: This is a new table, allowing a meter reader to
retrieve values for a list of attributes from a flow as a single
object. When used with SNMP GetBulk requests it provides an
efficient way to recover flow data.
Earlier versions had a 'Column Activity Table;' using this it was
difficult to collect all data for a flow efficiently in a single
SNMP request.
6 Definitions
FLOW-METER-MIB DEFINITIONS ::= BEGIN FLOW-METER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64, Integer32 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Counter64, Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TimeStamp, TruthValue TEXTUAL-CONVENTION, RowStatus, TimeStamp, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
mib-2, ifIndex mib-2, ifIndex
FROM RFC1213-MIB FROM RFC1213-MIB
TimeFilter, OwnerString OwnerString
FROM RMON-MIB; FROM RMON-MIB
TimeFilter
FROM RMON2-MIB;
flowMIB MODULE-IDENTITY flowMIB MODULE-IDENTITY
LAST-UPDATED "9703111620Z" LAST-UPDATED "9707071715Z"
ORGANIZATION "IETF Realtime Traffic Flow Measurement Working Group" ORGANIZATION "IETF Realtime Traffic Flow Measurement Working Group"
CONTACT-INFO CONTACT-INFO
"Nevil Brownlee, The University of Auckland "Nevil Brownlee, The University of Auckland
Postal: Information Technology Sytems & Services Postal: Information Technology Sytems & Services
The University of Auckland The University of Auckland
Private Bag 92-019 Private Bag 92-019
Auckland, New Zealand Auckland, New Zealand
Phone: +64 9 373 7599 x8941 Phone: +64 9 373 7599 x8941
E-mail: n.brownlee@auckland.ac.nz" E-mail: n.brownlee@auckland.ac.nz"
DESCRIPTION DESCRIPTION
"MIB for the RTFM Traffic Flow Meter." "MIB for the RTFM Traffic Flow Meter."
VERSION "9706041620Z"
DESCRIPTION
"Significant changes since RFC 2064 include:
- flowDataPackageTable added
- flowColumnActivityTable deprecated
- flowManagerCounterWrap depreacted"
VERSION "9603080208Z"
DESCRIPTION
"Initial version of this MIB (RFC 2064)"
::= { mib-2 40 } ::= { mib-2 40 }
flowControl OBJECT IDENTIFIER ::= { flowMIB 1 } flowControl OBJECT IDENTIFIER ::= { flowMIB 1 }
flowData OBJECT IDENTIFIER ::= { flowMIB 2 } flowData OBJECT IDENTIFIER ::= { flowMIB 2 }
flowRules OBJECT IDENTIFIER ::= { flowMIB 3 } flowRules OBJECT IDENTIFIER ::= { flowMIB 3 }
flowMIBConformance OBJECT IDENTIFIER ::= { flowMIB 4 } flowMIBConformance OBJECT IDENTIFIER ::= { flowMIB 4 }
skipping to change at page 9, line 28 skipping to change at page 10, line 49
Is a superset of MediumAddress and PeerAddress." Is a superset of MediumAddress and PeerAddress."
SYNTAX OCTET STRING (SIZE (3..20)) SYNTAX OCTET STRING (SIZE (3..20))
TransportType ::= TEXTUAL-CONVENTION TransportType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of a TransportAddress (see below). Values "Indicates the type of a TransportAddress (see below). Values
will depend on the actual protocol; for IP they will be those will depend on the actual protocol; for IP they will be those
given in the 'Protocol Numbers' section of the Assigned Numbers given in the 'Protocol Numbers' section of the Assigned Numbers
RFC [11], including icmp(1), tcp(6) and udp(17)." RFC [11], including icmp(1), tcp(6) and udp(17)."
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
TransportAddress ::= TEXTUAL-CONVENTION TransportAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the value of a transport address for various "Specifies the value of a transport address for various
network protocols. Format as follows: network protocols. Format as follows:
IP: IP:
2-octet UDP or TCP port number 2-octet UDP or TCP port number
skipping to change at page 11, line 8 skipping to change at page 12, line 29
sourceKind(39), sourceKind(39),
destKind(40), destKind(40),
flowKind(41) } flowKind(41) }
RuleAttributeNumber ::= TEXTUAL-CONVENTION RuleAttributeNumber ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies an attribute which may be tested in "Uniquely identifies an attribute which may be tested in
a rule. These include attributes whose values come directly a rule. These include attributes whose values come directly
from (or are computed from) the flow's packets, and the five from (or are computed from) the flow's packets, and the five
'meter' variables used to hold an AttributeValue." 'meter' variables used to hold an Attribute Number."
SYNTAX INTEGER { SYNTAX INTEGER {
null(0), null(0),
sourceInterface(4), -- Source Address sourceInterface(4), -- Source Address
sourceAdjacentType(5), sourceAdjacentType(5),
sourceAdjacentAddress(6), sourceAdjacentAddress(6),
sourcePeerType(8), sourcePeerType(8),
sourcePeerAddress(9), sourcePeerAddress(9),
sourceTransType(11), sourceTransType(11),
sourceTransAddress(12), sourceTransAddress(12),
skipping to change at page 12, line 4 skipping to change at page 13, line 25
ActionNumber ::= TEXTUAL-CONVENTION ActionNumber ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies the action of a rule, i.e. the Pattern "Uniquely identifies the action of a rule, i.e. the Pattern
Matching Engine's opcode number. Details of the opcodes Matching Engine's opcode number. Details of the opcodes
are given in the 'Traffic Flow Measurement: Architecture' are given in the 'Traffic Flow Measurement: Architecture'
document [9]." document [9]."
SYNTAX INTEGER { SYNTAX INTEGER {
ignore(1), ignore(1),
fail(2), noMatch(2),
count(3), count(3),
countPkt(4), countPkt(4),
return(5), return(5),
gosub(6), gosub(6),
gosubAct(7), gosubAct(7),
assign(8), assign(8),
assignAct(9), assignAct(9),
goto(10), goto(10),
gotoAct(11), gotoAct(11),
pushRuleTo(12), pushRuleTo(12),
skipping to change at page 13, line 22 skipping to change at page 14, line 43
flowRuleInfoSize Integer32, flowRuleInfoSize Integer32,
flowRuleInfoOwner OwnerString, flowRuleInfoOwner OwnerString,
flowRuleInfoTimeStamp TimeStamp, flowRuleInfoTimeStamp TimeStamp,
flowRuleInfoStatus RowStatus, flowRuleInfoStatus RowStatus,
flowRuleInfoName OCTET STRING, flowRuleInfoName OCTET STRING,
flowRuleInfoRulesReady TruthValue, flowRuleInfoRulesReady TruthValue,
flowRuleInfoFlowRecords Integer32 flowRuleInfoFlowRecords Integer32
} }
flowRuleInfoIndex OBJECT-TYPE flowRuleInfoIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index which selects an entry in the flowRuleSetInfoTable. "An index which selects an entry in the flowRuleSetInfoTable.
Each such entry contains control information for a particular Each such entry contains control information for a particular
rule set which the meter may run." rule set which the meter may run."
::= { flowRuleSetInfoEntry 1 } ::= { flowRuleSetInfoEntry 1 }
flowRuleInfoSize OBJECT-TYPE flowRuleInfoSize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
skipping to change at page 14, line 12 skipping to change at page 15, line 33
DESCRIPTION DESCRIPTION
"Time this row's associated rule set was last changed." "Time this row's associated rule set was last changed."
::= { flowRuleSetInfoEntry 4 } ::= { flowRuleSetInfoEntry 4 }
flowRuleInfoStatus OBJECT-TYPE flowRuleInfoStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this flowRuleSetInfoEntry. If this value is "The status of this flowRuleSetInfoEntry. If this value is
not active(1) the meter must not attempt to use this row's not active(1) the meter must not attempt to use the row's
associated rule set. Once its value has been set to active(1) associated rule set. Once its value has been set to active(1)
a manager may change any of this row's variables except a manager may only change this row's flowRuleInfoSize,
flowRuleInfoOwner and flowRuleInfoTimeStamp." flowRuleInfoName and floeRuleInfoRulesReady variables."
::= { flowRuleSetInfoEntry 5 } ::= { flowRuleSetInfoEntry 5 }
flowRuleInfoName OBJECT-TYPE flowRuleInfoName OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An alphanumeric identifier used by managers and readers to "An alphanumeric identifier used by managers and readers to
identify a rule set. For example, a manager wishing to run a identify a rule set. For example, a manager wishing to run a
rule set named WWW-FLOWS could search the flowRuleSetInfoTable rule set named WWW-FLOWS could search the flowRuleSetInfoTable
to see whether the WWW-FLOWS rule set is already available on to see whether the WWW-FLOWS rule set is already available on
the meter. the meter.
Note that references to rule sets in the flowManagerInfoTable Note that references to rule sets in the flowManagerInfoTable
use indexes for their flowRuleSetInfoTable entries. These may use indexes for their flowRuleSetInfoTable entries. These may
be different each time the rule set is loaded into a meter." be different each time the rule set is loaded into a meter."
::= { flowRuleSetInfoEntry 6 } ::= { flowRuleSetInfoEntry 6 }
flowRuleRulesReady OBJECT-TYPE flowRuleInfoRulesReady OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the rules for this row's associated rule set "Indicates whether the rules for this row's associated rule set
are ready for use. The meter will refuse to 'run' the rule set are ready for use. The meter will refuse to 'run' the rule set
unless this variable has been set to true(1)." unless this variable has been set to true(1)."
::= { flowRuleSetInfoEntry 7 } ::= { flowRuleSetInfoEntry 7 }
flowRuleInfoFlowRecords OBJECT-TYPE flowRuleInfoFlowRecords OBJECT-TYPE
skipping to change at page 16, line 9 skipping to change at page 17, line 29
DESCRIPTION DESCRIPTION
"The number of packets the meter has lost for this interface. "The number of packets the meter has lost for this interface.
Such losses may occur because the meter has been unable to Such losses may occur because the meter has been unable to
keep up with the traffic volume." keep up with the traffic volume."
::= { flowInterfaceEntry 2 } ::= { flowInterfaceEntry 2 }
-- --
-- Control Group: Meter Reader Info Table -- Control Group: Meter Reader Info Table
-- --
-- Any meter reader wishing to collect data reliably for flows
-- should first create a row in this table. It should write that -- should first create a row in this table. It should write that
-- row's flowReaderLastTime object each time it starts a collection -- row's flowReaderLastTime object each time it starts a collection
-- pass through the flow table. -- pass through the flow table.
-- If a meter reader (MR) does not create a row in this table, e.g. -- If a meter reader (MR) does not create a row in this table, e.g.
-- because it failed authentication in the meter's SNMP write -- because it failed authentication in the meter's SNMP write
-- community, collection can still proceed but the meter will not be -- community, collection can still proceed but the meter will not be
-- aware of meter reader MR. This could lead the meter to recover -- aware of meter reader MR. This could lead the meter to recover
-- flows before they have been collected by MR. -- flows before they have been collected by MR.
skipping to change at page 16, line 45 skipping to change at page 18, line 14
INDEX { flowReaderIndex } INDEX { flowReaderIndex }
::= { flowReaderInfoTable 1 } ::= { flowReaderInfoTable 1 }
FlowReaderInfoEntry ::= SEQUENCE { FlowReaderInfoEntry ::= SEQUENCE {
flowReaderIndex Integer32, flowReaderIndex Integer32,
flowReaderTimeout Integer32, flowReaderTimeout Integer32,
flowReaderOwner OwnerString, flowReaderOwner OwnerString,
flowReaderLastTime TimeStamp, flowReaderLastTime TimeStamp,
flowReaderPreviousTime TimeStamp, flowReaderPreviousTime TimeStamp,
flowReaderStatus RowStatus, flowReaderStatus RowStatus,
flowReaderRuleSetName OCTET STRING flowReaderRuleSet Integer32
} }
flowReaderIndex OBJECT-TYPE flowReaderIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index which selects an entry in the flowReaderInfoTable." "An index which selects an entry in the flowReaderInfoTable."
::= { flowReaderInfoEntry 1 } ::= { flowReaderInfoEntry 1 }
flowReaderTimeout OBJECT-TYPE flowReaderTimeout OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the maximum time (in seconds) between flow data "Specifies the maximum time (in seconds) between flow data
collections for this meter reader. If this time elapses collections for this meter reader. If this time elapses
without a collection, the meter should assume that this meter without a collection, the meter should assume that this meter
reader has stopped collecting, and delete this row from the reader has stopped collecting, and delete this row from the
table." table. A value of zero indicates that this row should not be
timed out."
::= { flowReaderInfoEntry 2 } ::= { flowReaderInfoEntry 2 }
flowReaderOwner OBJECT-TYPE flowReaderOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the meter reader which created this row." "Identifies the meter reader which created this row."
::= { flowReaderInfoEntry 3 } ::= { flowReaderInfoEntry 3 }
flowReaderLastTime OBJECT-TYPE flowReaderLastTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time this meter reader began its most recent data collection. "Time this meter reader began its most recent data collection.
This variable should be written by a meter reader as its first This variable should be written by a meter reader as its first
step in reading flow data. The meter will set this LastTime step in reading flow data. The meter will set this LastTime
value to sysUptime and set its PreviousTime value (below) to value to sysUptime and set its PreviousTime value (below) to
the old LastTime. This allows the meter to recover flows the old LastTime. This allows the meter to recover flows
which have been inactive since PreviousTime, for these have which have been inactive since PreviousTime, for these have
been collected at least once. been collected at least once.
skipping to change at page 18, line 13 skipping to change at page 19, line 35
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this FlowReaderInfoEntry. A value of active(1) "The status of this FlowReaderInfoEntry. A value of active(1)
implies that the associated reader should be collecting data implies that the associated reader should be collecting data
from the meter. Once this variable has been set to active(1) from the meter. Once this variable has been set to active(1)
a manager may only change this row's flowReaderLastTime and a manager may only change this row's flowReaderLastTime and
flowReaderTimeout variables." flowReaderTimeout variables."
::= { flowReaderInfoEntry 6 } ::= { flowReaderInfoEntry 6 }
flowReaderRuleSetName OBJECT-TYPE flowReaderRuleSet OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An alphanumeric identifier identifying a rule set of interest "An index to the array of rule sets. Specifies a set of rules
to this meter reader. The reader will attempt to collect any of interest to this meter reader. The reader will attempt to
data generated by the meter for this rule set, and the meter collect any data generated by the meter for this rule set, and
will not recover the memory of any of the rule set's flows the meter will not recover the memory of any of the rule set's
until this collection has taken place. Note that a reader may flows until this collection has taken place. Note that a
have entries in this table for several rule sets." reader may have entries in this table for several rule sets."
::= { flowReaderInfoEntry 7 } ::= { flowReaderInfoEntry 7 }
-- --
-- Control Group: Manager Info Table -- Control Group: Manager Info Table
-- --
-- Any manager wishing to run a rule set must create a row in this -- Any manager wishing to run a rule set must create a row in this
-- table. Once it has a table row, the manager may set the control -- table. Once it has a table row, the manager may set the control
-- variables in its row so as to cause the meter to run any valid -- variables in its row so as to cause the meter to run any valid
-- rule set held by the meter. -- rule set held by the meter.
-- A single manager may run several rule sets; it must create a row -- A single manager may run several rule sets; it must create a row
-- in this table for each of them. In short, each row of this table -- in this table for each of them. In short, each row of this table
-- describes (and controls) a 'task' which the meter is executing. -- describes (and controls) a 'task' which the meter is executing.
flowManagerInfoTable OBJECT-TYPE flowManagerInfoTable OBJECT-TYPE
SYNTAX SEQUENCE OF FlowManagerInfoEntry SYNTAX SEQUENCE OF FlowManagerInfoEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 19, line 29 skipping to change at page 20, line 52
space has abated, it may cause the task to switch back to its space has abated, it may cause the task to switch back to its
CurrentRuleSet by setting its flowManagerRunningStandby CurrentRuleSet by setting its flowManagerRunningStandby
variable to false(2)." variable to false(2)."
INDEX { flowManagerIndex } INDEX { flowManagerIndex }
::= { flowManagerInfoTable 1 } ::= { flowManagerInfoTable 1 }
FlowManagerInfoEntry ::= SEQUENCE { FlowManagerInfoEntry ::= SEQUENCE {
flowManagerIndex Integer32, flowManagerIndex Integer32,
flowManagerCurrentRuleSet Integer32, flowManagerCurrentRuleSet Integer32,
flowManagerStandbyRuleSet Integer32, flowManagerStandbyRuleSet Integer32,
flowManagerHighWaterMark INTEGER, flowManagerHighWaterMark Integer32,
flowManagerCounterWrap INTEGER, flowManagerCounterWrap INTEGER,
flowManagerOwner OwnerString, flowManagerOwner OwnerString,
flowManagerTimeStamp TimeStamp, flowManagerTimeStamp TimeStamp,
flowManagerStatus RowStatus, flowManagerStatus RowStatus,
flowManagerRunningStandby TruthValue flowManagerRunningStandby TruthValue
} }
flowManagerIndex OBJECT-TYPE flowManagerIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index which selects an entry in the flowManagerInfoTable." "An index which selects an entry in the flowManagerInfoTable."
::= { flowManagerInfoEntry 1 } ::= { flowManagerInfoEntry 1 }
flowManagerCurrentRuleSet OBJECT-TYPE flowManagerCurrentRuleSet OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index to the array of rule sets. Specifies which set of "Index to the array of rule sets. Specifies which set of
rules is currently being used for accounting by this task. rules is the 'current' one for this task. The meter will
When the manager sets this variable the meter will close the be 'running' the current ruleset if this row's
task's current rule set and start using the new one, and will flowManagerRunningStandby value is false(2).
set the task's flowManagerRunningStandby value to false(2).
Flows created by the old rule set remain in memory, orphaned When the manager sets this variable the meter will close the
until their data has been read. Specifying rule set 0 (the task's old current rule set and start using the new one.
empty set) stops flow measurement by this manager." Specifying rule set 0 (the empty set) stops flow measurement
by this manager. Flows created by the old rule set remain
in memory, orphaned until their data has been read."
::= { flowManagerInfoEntry 2 } ::= { flowManagerInfoEntry 2 }
flowManagerStandbyRuleSet OBJECT-TYPE flowManagerStandbyRuleSet OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index to the array of rule sets. After reaching HighWaterMark "Index to the array of rule sets. After reaching HighWaterMark
(see below) the manager will switch to using the task's (see below) the manager will switch to using the task's
StandbyRuleSet in place of its CurrentRuleSet. For this to be StandbyRuleSet in place of its CurrentRuleSet. For this to be
effective the designated StandbyRuleSet should have a coarser effective the designated StandbyRuleSet should have a coarser
reporting granularity then the CurrentRuleSet. The manager may reporting granularity then the CurrentRuleSet. The manager may
also need to decrease the meter reading interval so that the also need to decrease the meter reading interval so that the
meter can recover flows measured by the (old) CurrentRuleSet." meter can recover flows measured by the CurrentRuleSet."
DEFVAL { 0 } -- No standby DEFVAL { 0 } -- No standby
::= { flowManagerInfoEntry 3 } ::= { flowManagerInfoEntry 3 }
flowManagerHighWaterMark OBJECT-TYPE flowManagerHighWaterMark OBJECT-TYPE
SYNTAX INTEGER (0..100) SYNTAX Integer32 (0..100)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value expressed as a percentage, interpreted by the meter "A value expressed as a percentage, interpreted by the meter
as an indication of how full the flow table should be before as an indication of how full the flow table should be before
it should switch to the standby rule set (if one has been it should switch to the standby rule set (if one has been
specified) for this task. Values of 0% or 100% disable the specified) for this task. Values of 0% or 100% disable the
checking represented by this variable." checking represented by this variable."
::= { flowManagerInfoEntry 4 } ::= { flowManagerInfoEntry 4 }
skipping to change at page 21, line 29 skipping to change at page 22, line 53
DESCRIPTION DESCRIPTION
"The status of this row in the flowManagerInfoTable. A value "The status of this row in the flowManagerInfoTable. A value
of active(1) implies that this task may be activated, by of active(1) implies that this task may be activated, by
setting its CurrentRuleSet and StandbyRuleSet variables. setting its CurrentRuleSet and StandbyRuleSet variables.
Its HighWaterMark and RunningStandby variables may also be Its HighWaterMark and RunningStandby variables may also be
changed." changed."
::= { flowManagerInfoEntry 8 } ::= { flowManagerInfoEntry 8 }
flowManagerRunningStandby OBJECT-TYPE flowManagerRunningStandby OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-create
STATUS deprecated STATUS current
DESCRIPTION DESCRIPTION
"Set to true(1) by the meter to indicate that it has switched "Set to true(1) by the meter to indicate that it has switched
to runnning this task's StandbyRuleSet in place of its to runnning this task's StandbyRuleSet in place of its
CurrentRuleSet. To switch back to the CurrentRuleSet, the CurrentRuleSet. To switch back to the CurrentRuleSet, the
manager may simply set this variable to false(2)." manager may simply set this variable to false(2)."
DEFVAL { false } DEFVAL { false }
::= { flowManagerInfoEntry 9 } ::= { flowManagerInfoEntry 9 }
-- --
-- Control Group: General Meter Control Variables -- Control Group: General Meter Control Variables
-- --
flowFloodMark OBJECT-TYPE flowFloodMark OBJECT-TYPE
SYNTAX INTEGER (0..100) SYNTAX Integer32 (0..100)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value expressed as a percentage, interpreted by the meter "A value expressed as a percentage, interpreted by the meter
as an indication of how full the flow table should be before as an indication of how full the flow table should be before
it should take some action to avoid running out of resources it should take some action to avoid running out of resources
to handle new flows. Values of 0% or 100% disable the to handle new flows. Values of 0% or 100% disable the
checking represented by this variable." checking represented by this variable."
DEFVAL { 95 } -- Enabled by default. DEFVAL { 95 } -- Enabled by default.
::= { flowControl 5 } ::= { flowControl 5 }
flowInactivityTimeout OBJECT-TYPE flowInactivityTimeout OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time in seconds since the last packet seen, after which a "The time in seconds since the last packet seen, after which
flow may be discarded. Note that although a flow may be 'idle', a flow becomes 'idle.' Note that although a flow may be
it will not be discarded (and its memory recovered) until after idle, it will not be discarded (and its memory recovered)
its data has been collected by all 'registered' meter readers." until after its data has been collected by all the meter
readers registered for its RuleSet."
DEFVAL { 600 } -- 10 minutes DEFVAL { 600 } -- 10 minutes
::= { flowControl 6 } ::= { flowControl 6 }
flowActiveFlows OBJECT-TYPE flowActiveFlows OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The numbers of flows which are currently in use." "The numbers of flows which are currently in use."
::= { flowControl 7 } ::= { flowControl 7 }
skipping to change at page 22, line 37 skipping to change at page 24, line 11
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of flows allowed in the meter's "The maximum number of flows allowed in the meter's
flow table. At present this is determined when the meter flow table. At present this is determined when the meter
is first started up." is first started up."
::= { flowControl 8 } ::= { flowControl 8 }
flowFloodMode OBJECT-TYPE flowFloodMode OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates that the meter has passed its FloodMark and "Indicates that the meter has passed its FloodMark and is
is not running in its normal mode. When a manager notices not running in its normal mode. When a manager notices this
this it should take action to remedy the problem which it should take action to remedy the problem which caused the
caused the flooding." flooding. Once the flood has receded, the manager may set
this variable to false(2) to resume normal operaation."
::= { flowControl 9 } ::= { flowControl 9 }
-- --
-- The Flow Table -- The Flow Table
-- --
-- This is a table kept by a meter, with one flow data entry for every -- This is a table kept by a meter, with one flow data entry for every
-- flow being measured. Each flow data entry stores the attribute -- flow being measured. Each flow data entry stores the attribute
-- values for a traffic flow. Details of flows and their attributes -- values for a traffic flow. Details of flows and their attributes
-- are given in the 'Traffic Flow Measurement: Architecture' -- are given in the 'Traffic Flow Measurement: Architecture'
skipping to change at page 24, line 8 skipping to change at page 25, line 34
flowDataDestAdjacentType AdjacentType, flowDataDestAdjacentType AdjacentType,
flowDataDestAdjacentAddress AdjacentAddress, flowDataDestAdjacentAddress AdjacentAddress,
flowDataDestAdjacentMask AdjacentAddress, flowDataDestAdjacentMask AdjacentAddress,
flowDataDestPeerType PeerType, flowDataDestPeerType PeerType,
flowDataDestPeerAddress PeerAddress, flowDataDestPeerAddress PeerAddress,
flowDataDestPeerMask PeerAddress, flowDataDestPeerMask PeerAddress,
flowDataDestTransType TransportType, flowDataDestTransType TransportType,
flowDataDestTransAddress TransportAddress, flowDataDestTransAddress TransportAddress,
flowDataDestTransMask TransportAddress, flowDataDestTransMask TransportAddress,
flowDataPDUScale INTEGER, flowDataPDUScale Integer32,
flowDataOctetScale INTEGER, flowDataOctetScale Integer32,
flowDataRuleSet INTEGER, flowDataRuleSet Integer32,
flowDataToOctets Counter64, -- Source->Dest flowDataToOctets Counter64, -- Source->Dest
flowDataToPDUs Counter64, flowDataToPDUs Counter64,
flowDataFromOctets Counter64, -- Dest->Source flowDataFromOctets Counter64, -- Dest->Source
flowDataFromPDUs Counter64, flowDataFromPDUs Counter64,
flowDataFirstTime TimeStamp, -- Activity times flowDataFirstTime TimeStamp, -- Activity times
flowDataLastActiveTime TimeStamp, flowDataLastActiveTime TimeStamp,
flowDataSourceSubscriberID OCTET STRING, flowDataSourceSubscriberID OCTET STRING,
flowDataDestSubscriberID OCTET STRING, flowDataDestSubscriberID OCTET STRING,
flowDataSessionID OCTET STRING, flowDataSessionID OCTET STRING,
flowDataSourceClass INTEGER, flowDataSourceClass Integer32,
flowDataDestClass INTEGER, flowDataDestClass Integer32,
flowDataClass INTEGER, flowDataClass Integer32,
flowDataSourceKind INTEGER, flowDataSourceKind Integer32,
flowDataDestKind INTEGER, flowDataDestKind Integer32,
flowDataKind INTEGER flowDataKind Integer32
} }
flowDataIndex OBJECT-TYPE flowDataIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Value of this flow data record's index within the meter's "Value of this flow data record's index within the meter's
flow table." flow table."
::= { flowDataEntry 1 } ::= { flowDataEntry 1 }
flowDataTimeMark OBJECT-TYPE flowDataTimeMark OBJECT-TYPE
SYNTAX TimeFilter SYNTAX TimeFilter
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 28, line 35 skipping to change at page 30, line 10
flowDataDestTransMask OBJECT-TYPE flowDataDestTransMask OBJECT-TYPE
SYNTAX TransportAddress SYNTAX TransportAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"1-bits in this mask indicate which bits must match when "1-bits in this mask indicate which bits must match when
comparing the transport destination address for this flow." comparing the transport destination address for this flow."
::= { flowDataEntry 23 } ::= { flowDataEntry 23 }
flowDataPDUScale OBJECT-TYPE flowDataPDUScale OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The scale factor applied to this particular flow. Indicates "The scale factor applied to this particular flow. Indicates
the number of bits the PDU counter values should be moved left the number of bits the PDU counter values should be moved left
to obtain the actual values." to obtain the actual values."
::= { flowDataEntry 24 } ::= { flowDataEntry 24 }
flowDataOctetScale OBJECT-TYPE flowDataOctetScale OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The scale factor applied to this particular flow. Indicates "The scale factor applied to this particular flow. Indicates
the number of bits the octet counter values should be moved the number of bits the octet counter values should be moved
left to obtain the actual values." left to obtain the actual values."
::= { flowDataEntry 25 } ::= { flowDataEntry 25 }
flowDataRuleSet OBJECT-TYPE flowDataRuleSet OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RuleSet number of the rule set which created this flow." "The RuleSet number of the rule set which created this flow.
Allows a manager to use GetNext or GetBulk requests to find
flows belonging to a particular RuleSet."
::= { flowDataEntry 26 } ::= { flowDataEntry 26 }
flowDataToOctets OBJECT-TYPE flowDataToOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of octets flowing from source to dest address and "The count of octets flowing from source to dest address and
being delivered to the protocol level being metered. In the being delivered to the protocol level being metered. In the
case of IP this would count the number of octets delivered to case of IP this would count the number of octets delivered to
skipping to change at page 30, line 49 skipping to change at page 32, line 26
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Session ID for this flow. Such an ID might be allocated "Session ID for this flow. Such an ID might be allocated
by a network access server to distinguish a series of sessions by a network access server to distinguish a series of sessions
between the same pair of addresses, which would otherwise between the same pair of addresses, which would otherwise
appear to be parts of the same accounting flow." appear to be parts of the same accounting flow."
::= { flowDataEntry 35 } ::= { flowDataEntry 35 }
flowDataSourceClass OBJECT-TYPE flowDataSourceClass OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Source class for this flow. Determined by the rules, set by "Source class for this flow. Determined by the rules, set by
a PushRule action when this flow was entered in the table." a PushRule action when this flow was entered in the table."
::= { flowDataEntry 36 } ::= { flowDataEntry 36 }
flowDataDestClass OBJECT-TYPE flowDataDestClass OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Destination class for this flow. Determined by the rules, set "Destination class for this flow. Determined by the rules, set
by a PushRule action when this flow was entered in the table." by a PushRule action when this flow was entered in the table."
::= { flowDataEntry 37 } ::= { flowDataEntry 37 }
flowDataClass OBJECT-TYPE flowDataClass OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Class for this flow. Determined by the rules, set by a "Class for this flow. Determined by the rules, set by a
PushRule action when this flow was entered in the table." PushRule action when this flow was entered in the table."
::= { flowDataEntry 38 } ::= { flowDataEntry 38 }
flowDataSourceKind OBJECT-TYPE flowDataSourceKind OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Source kind for this flow. Determined by the rules, set by "Source kind for this flow. Determined by the rules, set by
a PushRule action when this flow was entered in the table." a PushRule action when this flow was entered in the table."
::= { flowDataEntry 39 } ::= { flowDataEntry 39 }
flowDataDestKind OBJECT-TYPE flowDataDestKind OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Destination kind for this flow. Determined by the rules, set "Destination kind for this flow. Determined by the rules, set
by a PushRule action when this flow was entered in the table." by a PushRule action when this flow was entered in the table."
::= { flowDataEntry 40 } ::= { flowDataEntry 40 }
flowDataKind OBJECT-TYPE flowDataKind OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Class for this flow. Determined by the rules, set by a "Class for this flow. Determined by the rules, set by a
PushRule action when this flow was entered in the table." PushRule action when this flow was entered in the table."
::= { flowDataEntry 41 } ::= { flowDataEntry 41 }
-- --
-- The Activity Column Table -- The Activity Column Table
-- --
skipping to change at page 32, line 54 skipping to change at page 34, line 32
SYNTAX TimeFilter SYNTAX TimeFilter
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This variable is a copy of flowDataLastActiveTime in the "This variable is a copy of flowDataLastActiveTime in the
flow data record identified by the flowColumnActivityIndex flow data record identified by the flowColumnActivityIndex
value of this flowColumnActivityTable entry." value of this flowColumnActivityTable entry."
::= { flowColumnActivityEntry 2 } ::= { flowColumnActivityEntry 2 }
flowColumnActivityIndex OBJECT-TYPE flowColumnActivityIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Index of a flow table entry which was active at or after "Index of a flow table entry which was active at or after
a specified flowColumnActivityTime." a specified flowColumnActivityTime."
::= { flowColumnActivityEntry 3 } ::= { flowColumnActivityEntry 3 }
flowColumnActivityData OBJECT-TYPE flowColumnActivityData OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (3..1000)) SYNTAX OCTET STRING (SIZE (3..1000))
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 33, line 36 skipping to change at page 35, line 13
specified by their SYNTAX in the flow table (above), i.e. one specified by their SYNTAX in the flow table (above), i.e. one
octet for flowAddressType and small constants, and four octets octet for flowAddressType and small constants, and four octets
for Counter and TimeStamp. Strings are variable-length, with for Counter and TimeStamp. Strings are variable-length, with
the length given in a single leading octet. the length given in a single leading octet.
The following is an attempt at an ASN.1 definition of The following is an attempt at an ASN.1 definition of
flowColumnActivityData: flowColumnActivityData:
flowColumnActivityData ::= SEQUENCE flowRowItemEntry flowColumnActivityData ::= SEQUENCE flowRowItemEntry
flowRowItemEntry ::= SEQUENCE { flowRowItemEntry ::= SEQUENCE {
flowRowNumber INTEGER (1..65535), flowRowNumber Integer32 (1..65535),
-- 0 indicates the end of this column -- 0 indicates the end of this column
flowDataValue flowDataType -- Choice depends on attribute flowDataValue flowDataType -- Choice depends on attribute
} }
flowDataType ::= CHOICE { flowDataType ::= CHOICE {
flowByteValue INTEGER (1..255), flowByteValue Integer32 (1..255),
flowShortValue INTEGER (1..65535), flowShortValue Integer32 (1..65535),
flowLongValue Integer32, flowLongValue Integer32,
flowStringValue OCTET STRING -- Length (n) in first byte, flowStringValue OCTET STRING -- Length (n) in first byte,
-- n+1 bytes total length, trailing zeroes truncated -- n+1 bytes total length, trailing zeroes truncated
}" }"
::= { flowColumnActivityEntry 4 } ::= { flowColumnActivityEntry 4 }
--
-- The Data Package Table
--
flowDataPackageTable OBJECT-TYPE flowDataPackageTable OBJECT-TYPE
SYNTAX SEQUENCE OF FlowDataPackageEntry SYNTAX SEQUENCE OF FlowDataPackageEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into the Flow Table. Allows a meter reader to retrieve "Index into the Flow Table. Allows a meter reader to retrieve
a sequence containing the values of a specified set of a sequence containing the values of a specified set of
attributes for a flow which came from a specified rule set and attributes for a flow which came from a specified rule set and
which was last active at or after a given time." which was last active at or after a given time."
::= { flowData 3 } ::= { flowData 3 }
skipping to change at page 34, line 22 skipping to change at page 35, line 54
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The data package containing selected variables from "The data package containing selected variables from
active rows in the flow table." active rows in the flow table."
INDEX { flowPackageSelector, INDEX { flowPackageSelector,
flowPackageRuleSet, flowPackageTime, flowPackageIndex } flowPackageRuleSet, flowPackageTime, flowPackageIndex }
::= { flowDataPackageTable 1 } ::= { flowDataPackageTable 1 }
FlowDataPackageEntry ::= SEQUENCE { FlowDataPackageEntry ::= SEQUENCE {
flowPackageSelector OCTET STRING, flowPackageSelector OCTET STRING,
flowPackageRuleSet INTEGER, flowPackageRuleSet Integer32,
flowPackageTime TimeFilter, flowPackageTime TimeFilter,
flowPackageIndex Integer32, flowPackageIndex Integer32,
flowPackageData OCTET STRING flowPackageData OCTET STRING
} }
flowPackageSelector OBJECT-TYPE flowPackageSelector OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the attributes for which values are required from "Specifies the attributes for which values are required from
an active flow. These are encoded as a sequence of octets an active flow. These are encoded as a sequence of octets
each containing a FlowAttribute number, preceded by an octet each containing a FlowAttribute number, preceded by an octet
giving the length of the sequence (not including the length giving the length of the sequence (not including the length
octet)." octet)."
::= { flowDataPackageEntry 1 } ::= { flowDataPackageEntry 1 }
flowPackageRuleSet OBJECT-TYPE flowPackageRuleSet OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the index (in the flowRuleSetInfoTable) of the rule "Specifies the index (in the flowRuleSetInfoTable) of the rule
set which produced the required flow." set which produced the required flow."
::= { flowDataPackageEntry 2 } ::= { flowDataPackageEntry 2 }
flowPackageTime OBJECT-TYPE flowPackageTime OBJECT-TYPE
SYNTAX TimeFilter SYNTAX TimeFilter
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is a copy of flowDataLastActiveTime in the "This variable is a copy of flowDataLastActiveTime in the
flow data record identified by the flowColumnActivityIndex flow data record identified by the flowPackageIndex
value of this flowPackageTable entry." value of this flowPackageTable entry."
::= { flowDataPackageEntry 3 } ::= { flowDataPackageEntry 3 }
flowPackageIndex OBJECT-TYPE flowPackageIndex OBJECT-TYPE
SYNTAX INTEGER SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index of a flow table entry which was active at or after "Index of a flow table entry which was active at or after
a specified flowPackageTime." a specified flowPackageTime."
::= { flowDataPackageEntry 4 } ::= { flowDataPackageEntry 4 }
flowPackageData OBJECT-TYPE flowPackageData OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (3..1000)) SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Collection of attribute values for a single flow, as "A Collection of attribute values for a single flow, as
specified by the values of this row's indeces. The attribute specified by this row's indeces. The attribute values are
values are contained within a BER-encoded sequence [7], in the contained within a BER-encoded sequence [7], in the order
order they appear in their flowPackageSelector. For example, they appear in their flowPackageSelector. For example, to
to retrieve a flowPackage containing values for attributes 11, retrieve a flowPackage containing values for attributes 11,
18 and 34, for flows in rule set 7, active since uptime 12345, 18 and 29, for flows in rule set 7, active since uptime 12345,
beginning with the first row after row 3447, one would request beginning with the first row after row 3447, one would request
the package whose OID is the package whose Object Identifier (OID) is
flowPackageData . 3.11.18.34 . 7. 12345 . 3447 " flowPackageData . 3.11.18.29 . 7. 12345 . 3447 "
::= { flowDataPackageEntry 5 } ::= { flowDataPackageEntry 5 }
-- --
-- The Rule Table -- The Rule Table
-- --
-- This is an array of rule tables; the 'running' ones are indicated -- This is an array of rule tables; the 'running' ones are indicated
-- by the entries in the meter's flowManagerInfoTable. Several rule -- by the entries in the meter's flowManagerInfoTable. Several rule
-- sets can be held in a meter so that the manager can change the rules -- sets can be held in a meter so that the manager can change the rules
-- easily, for example with time of day. Note that a manager may -- easily, for example with time of day. Note that a manager may
skipping to change at page 36, line 16 skipping to change at page 37, line 47
flowRuleEntry OBJECT-TYPE flowRuleEntry OBJECT-TYPE
SYNTAX FlowRuleEntry SYNTAX FlowRuleEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The rule record itself." "The rule record itself."
INDEX { flowRuleSet, flowRuleIndex } INDEX { flowRuleSet, flowRuleIndex }
::= { flowRuleTable 1 } ::= { flowRuleTable 1 }
FlowRuleEntry ::= SEQUENCE { FlowRuleEntry ::= SEQUENCE {
flowRuleSet INTEGER, flowRuleSet Integer32,
flowRuleIndex INTEGER, flowRuleIndex Integer32,
flowRuleSelector RuleAttributeNumber, flowRuleSelector RuleAttributeNumber,
flowRuleMask RuleAddress, flowRuleMask RuleAddress,
flowRuleMatchedValue RuleAddress, flowRuleMatchedValue RuleAddress,
flowRuleAction ActionNumber, flowRuleAction ActionNumber,
flowRuleParameter INTEGER flowRuleParameter Integer32
} }
flowRuleSet OBJECT-TYPE flowRuleSet OBJECT-TYPE
SYNTAX INTEGER (1..255) SYNTAX Integer32 (1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Selects a rule set from the array of rule sets." "Selects a rule set from the array of rule sets."
::= { flowRuleEntry 1 } ::= { flowRuleEntry 1 }
flowRuleIndex OBJECT-TYPE flowRuleIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index into the Rule table. N.B: These values will "The index into the Rule table. N.B: These values will
often be consecutive, given the fall-through semantics of normally be consecutive, given the fall-through semantics
processing the table." of processing the table."
::= { flowRuleEntry 2 } ::= { flowRuleEntry 2 }
flowRuleSelector OBJECT-TYPE flowRuleSelector OBJECT-TYPE
SYNTAX RuleAttributeNumber SYNTAX RuleAttributeNumber
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the attribute to be matched. "Indicates the attribute to be matched.
null(0) is a special case; null rules always succeed. null(0) is a special case; null rules always succeed.
skipping to change at page 37, line 51 skipping to change at page 39, line 31
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The action to be taken if this rule's test succeeds, or if "The action to be taken if this rule's test succeeds, or if
the meter's 'test' flag is off. Actions are opcodes for the the meter's 'test' flag is off. Actions are opcodes for the
meter's Packet Matching Engine; details are given in the meter's Packet Matching Engine; details are given in the
'Traffic Flow Measurement: Architecture' document [9]." 'Traffic Flow Measurement: Architecture' document [9]."
::= { flowRuleEntry 6 } ::= { flowRuleEntry 6 }
flowRuleParameter OBJECT-TYPE flowRuleParameter OBJECT-TYPE
SYNTAX INTEGER (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A parameter value providing extra information for the "A parameter value providing extra information for the
rule's action." rule's action."
::= { flowRuleEntry 7 } ::= { flowRuleEntry 7 }
-- --
-- Traffic Flow Meter conformance statement -- Traffic Flow Meter conformance statement
-- --
skipping to change at page 38, line 23 skipping to change at page 40, line 5
flowMIBGroups flowMIBGroups
OBJECT IDENTIFIER ::= { flowMIBConformance 2 } OBJECT IDENTIFIER ::= { flowMIBConformance 2 }
flowControlGroup OBJECT-GROUP flowControlGroup OBJECT-GROUP
OBJECTS { OBJECTS {
flowRuleInfoSize, flowRuleInfoOwner, flowRuleInfoSize, flowRuleInfoOwner,
flowRuleInfoTimeStamp, flowRuleInfoStatus, flowRuleInfoTimeStamp, flowRuleInfoStatus,
flowRuleInfoName, flowRuleInfoRulesReady, flowRuleInfoName, flowRuleInfoRulesReady,
flowRuleInfoFlowRecords, flowRuleInfoFlowRecords,
flowInterfaceRate, flowInterfaceSampleRate,
flowInterfaceLostPackets, flowInterfaceLostPackets,
flowReaderTimeout, flowReaderOwner, flowReaderTimeout, flowReaderOwner,
flowReaderLastTime, flowReaderPreviousTime, flowReaderLastTime, flowReaderPreviousTime,
flowReaderStatus, flowReaderRuleSetName, flowReaderStatus, flowReaderRuleSet,
flowManagerCurrentRuleSet, flowManagerStandbyRuleSet, flowManagerCurrentRuleSet, flowManagerStandbyRuleSet,
flowManagerHighWaterMark, flowManagerHighWaterMark,
-- flowManagerCounterWrap,
flowManagerOwner, flowManagerTimeStamp, flowManagerOwner, flowManagerTimeStamp,
flowManagerStatus, flowManagerRunningStandby, flowManagerStatus, flowManagerRunningStandby,
flowFloodMark, flowFloodMark,
flowInactivityTimeout, flowActiveFlows, flowInactivityTimeout, flowActiveFlows,
flowMaxFlows, flowFloodMode } flowMaxFlows, flowFloodMode }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The control group defines objects which are used to control "The control group defines objects which are used to control
an accounting meter." an accounting meter."
::= {flowMIBGroups 1 } ::= {flowMIBGroups 1 }
flowDataTableGroup OBJECT-GROUP flowDataTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
flowDataIndex, -- flowDataIndex,
flowDataStatus, flowDataStatus,
flowDataSourceInterface, flowDataSourceInterface,
flowDataSourceAdjacentType, flowDataSourceAdjacentType,
flowDataSourceAdjacentAddress, flowDataSourceAdjacentMask, flowDataSourceAdjacentAddress, flowDataSourceAdjacentMask,
flowDataSourcePeerType, flowDataSourcePeerType,
flowDataSourcePeerAddress, flowDataSourcePeerMask, flowDataSourcePeerAddress, flowDataSourcePeerMask,
flowDataSourceTransType, flowDataSourceTransType,
flowDataSourceTransAddress, flowDataSourceTransMask, flowDataSourceTransAddress, flowDataSourceTransMask,
flowDataDestInterface, flowDataDestInterface,
flowDataDestAdjacentType, flowDataDestAdjacentType,
flowDataDestAdjacentAddress, flowDataDestAdjacentMask, flowDataDestAdjacentAddress, flowDataDestAdjacentMask,
flowDataDestPeerType, flowDataDestPeerType,
flowDataDestPeerAddress, flowDataDestPeerMask, flowDataDestPeerAddress, flowDataDestPeerMask,
flowDataDestTransType, flowDataDestTransType,
flowDataDestTransAddress, flowDataDestTransMask, flowDataDestTransAddress, flowDataDestTransMask,
flowDataRuleSet, -- flowDataRuleSet,
flowDataToOctets, flowDataToPDUs, flowDataToOctets, flowDataToPDUs,
flowDataFromOctets, flowDataFromPDUs, flowDataFromOctets, flowDataFromPDUs,
flowDataFirstTime, flowDataLastActiveTime, flowDataFirstTime, flowDataLastActiveTime,
flowDataSourceClass, flowDataDestClass, flowDataClass, flowDataSourceClass, flowDataDestClass, flowDataClass,
flowDataSourceKind, flowDataDestKind, flowDataKind flowDataSourceKind, flowDataDestKind, flowDataKind
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The flow table group defines objects which provide the "The flow table group defines objects which provide the
structure for the rule table, including the creation time structure for the rule table, including the creation time
skipping to change at page 39, line 32 skipping to change at page 41, line 14
adjacent, peer and transport layers, together with a flow's adjacent, peer and transport layers, together with a flow's
counters and times. Finally it defines a flow's class and counters and times. Finally it defines a flow's class and
kind attributes, which are set by rule actions." kind attributes, which are set by rule actions."
::= {flowMIBGroups 2 } ::= {flowMIBGroups 2 }
flowDataScaleGroup OBJECT-GROUP flowDataScaleGroup OBJECT-GROUP
OBJECTS { OBJECTS {
flowManagerCounterWrap, flowManagerCounterWrap,
flowDataPDUScale, flowDataOctetScale flowDataPDUScale, flowDataOctetScale
} }
STATUS current STATUS deprecated
DESCRIPTION DESCRIPTION
"The flow scale group defines objects which specify scale "The flow scale group defines objects which specify scale
factors for counters." factors for counters."
::= {flowMIBGroups 3 } ::= {flowMIBGroups 3 }
flowDataSubscriberGroup OBJECT-GROUP flowDataSubscriberGroup OBJECT-GROUP
OBJECTS { OBJECTS {
flowDataSourceSubscriberID, flowDataDestSubscriberID, flowDataSourceSubscriberID, flowDataDestSubscriberID,
flowDataSessionID flowDataSessionID
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The flow subscriber group defines objects which may be used "The flow subscriber group defines objects which may be used
to identify the end point(s) of a flow." to identify the end point(s) of a flow."
::= {flowMIBGroups 4 } ::= {flowMIBGroups 4 }
flowDataColumnTableGroup OBJECT-GROUP flowDataColumnTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
flowColumnActivityAttribute, flowColumnActivityAttribute,
flowColumnActivityTime,
flowColumnActivityIndex, flowColumnActivityIndex,
flowColumnActivityTime,
flowColumnActivityData flowColumnActivityData
} }
STATUS current STATUS deprecated
DESCRIPTION DESCRIPTION
"The flow column table group defines objects which can be used "The flow column table group defines objects which can be used
to collect part of a column of attribute values from the flow to collect part of a column of attribute values from the flow
table." table."
::= {flowMIBGroups 5 } ::= {flowMIBGroups 5 }
flowDataPackageGroup OBJECT-GROUP flowDataPackageGroup OBJECT-GROUP
OBJECTS { OBJECTS {
flowPackageSelector, flowPackageRuleSet, -- flowPackageSelector, flowPackageRuleSet, flowPackageIndex,
flowPackageIndex, flowPackageData flowPackageData
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The data package group defines objects which can be used "The data package group defines objects which can be used
to collect a specified set of attribute values from a row of to collect a specified set of attribute values from a row of
the flow table." the flow table."
::= {flowMIBGroups 6 } ::= {flowMIBGroups 6 }
flowRuleTableGroup OBJECT-GROUP flowRuleTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 40, line 37 skipping to change at page 42, line 19
flowRuleMask, flowRuleMatchedValue, flowRuleMask, flowRuleMatchedValue,
flowRuleAction, flowRuleParameter flowRuleAction, flowRuleParameter
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The rule table group defines objects which hold the set(s) "The rule table group defines objects which hold the set(s)
of rules specifying which traffic flows are to be accounted of rules specifying which traffic flows are to be accounted
for." for."
::= {flowMIBGroups 7 } ::= {flowMIBGroups 7 }
flowDataScaleGroup2 OBJECT-GROUP
OBJECTS {
-- flowManagerCounterWrap,
flowDataPDUScale, flowDataOctetScale
}
STATUS current
DESCRIPTION
"The flow scale group defines objects which specify scale
factors for counters. This group replaces the earlier
version of flowDataScaleGroup above (now deprecated)."
::= {flowMIBGroups 8}
flowMIBCompliance MODULE-COMPLIANCE flowMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for a Traffic Flow Meter." "The compliance statement for a Traffic Flow Meter."
MODULE MODULE
MANDATORY-GROUPS { MANDATORY-GROUPS {
flowControlGroup, flowControlGroup,
flowDataTableGroup, flowDataTableGroup,
flowDataPackageGroup,
flowRuleTableGroup flowRuleTableGroup
} }
::= { flowMIBCompliances 1 } ::= { flowMIBCompliances 1 }
END END
6 Acknowledgements 7 Security Considerations
This MIB describes how an RTFM traffic meter is controlled, and provides
a way for traffic flow data to be retrieved from it by a meter reader.
This is essentially an application using SNMP as a method of
communication between co-operating hosts; it does not - in itself - have
any inherent security risks.
Since, however, the traffic flow data can be extremely valuable for
network management purposes it is vital that sensible precautions be
taken to keep the meter and its data secure. This requires that access
to the meter for control purposes (e.g. loading RuleSets and reading
flow data) be restricted. Such restriction could be achieved in many
ways, for example
- Physical Separation. Meter(s) and meter reader(s) could be
deployed so that control capabilities are kept within a separate
network, access to which is carefully controlled.
- Application-layer Security. A minimal level of security for SNMP
is provided by using 'community' strings, which are essentially
clear-text passwords. Stronger security for SNMP is being
developed within the IETF; when this becomes available it should be
used to protect managed network equipment.
- Lower-layer Security. Access to the meter can be protected using
encryption at the network layer. For example, one could run SNMP
to the meter through an encrypted TCP tunnel.
When implementing a meter it may be sensible to use separate network
interfaces for control and for metering. If this is done the control
network can be set up so that it doesn't carry any 'user' traffic, and
the metering interfaces can ignore any user attempts to take control of
the meter.
Users should also consider how they will address attempts to circumvent
a meter, i.e. to prevent it from measuring flows. Such attempts are
essentially denial-of-service attacks on the metering interfaces. For
example
- Port Scan attacks. The attacker sends packets to each of a very
large number of IP (Address : Port) pairs. Each of these packets
creates a new flow in the meter; if there are enough of them the
meter will recognise a 'flood' condition, and will probably stop
creating new flows. As a minimum, users (and implementors) should
ensure that meters can recover from flood conditions as soon as
possible after they occur.
- Counter Wrap attacks: The attacker sends enough packets to cause
the counters in a flow to wrap several times between meter
readings, thus causing the counts to be artificially low. The
change to using 64-bit counters in this MIB reduces this problem
significantly.
Users can reduce the severity of both the above attacks by ensuring that
their meters are read often enough to prevent them being flooded. The
resulting flow data will contain a record of the attacking packets,
which may well be useful in determining where any attack came from.
8 Acknowledgements
An early draft of this document was produced under the auspices of the An early draft of this document was produced under the auspices of the
IETF's Accounting Working Group with assistance from SNMP and SAAG IETF's Accounting Working Group with assistance from the SNMP Working
working groups. Particular thanks are due to Jim Barnes, Sig Handelman Group and the Security Area Advisory Group. Particular thanks are due
and Stephen Stibler for their support and their assistance with checking to Jim Barnes, Sig Handelman and Stephen Stibler for their support and
the MIB. their assistance with checking early versions of the MIB.
7 References Stephen Stibler shared the development workload of producing the MIB
changes summarized in chpter 5 (above).
9 References
[1] McCloghrie, K., and Rose, M., Editors, "Management [1] McCloghrie, K., and Rose, M., Editors, "Management
Information Base for Network Management of TCP/IP-based Information Base for Network Management of TCP/IP-based
internets," RFC 1213, Performance Systems International, March internets," RFC 1213, Performance Systems International, March
1991. 1991.
[2] Case J., McCloghrie K., Rose M., and Waldbusser S., [2] Case J., McCloghrie K., Rose M., and Waldbusser S.,
"Structure of Management Information for version 2 of the "Structure of Management Information for version 2 of the
Simple Network Managemenet Protocol," RFC 1902, SNMP Research Simple Network Managemenet Protocol," RFC 1902, SNMP Research
Inc., Hughes LAN Systems, Dover Beach Consulting, Carnegie Inc., Hughes LAN Systems, Dover Beach Consulting, Carnegie
skipping to change at page 42, line 29 skipping to change at page 45, line 39
[11] Reynolds, J., Postel, J., "Assigned Numbers," RFC 1700, [11] Reynolds, J., Postel, J., "Assigned Numbers," RFC 1700,
ISI, October 1994. ISI, October 1994.
[12] Case, J., "FDDI Management Information Base," RFC 1285, [12] Case, J., "FDDI Management Information Base," RFC 1285,
SNMP Research Incorporated, January 1992. SNMP Research Incorporated, January 1992.
[13] Hinden, R., Deering, S., "IP Version 6 Addressing [13] Hinden, R., Deering, S., "IP Version 6 Addressing
Architecture," RFC 1884, Ipsilon Networks, Xerox PARC, December Architecture," RFC 1884, Ipsilon Networks, Xerox PARC, December
1995. 1995.
8 Security Considerations 10 Author's Address
This MIB describes how an RTFM traffic meter is controlled, and provides
a way for traffic flow data to be retrieved from it by a meter reader.
This is essentially an application using SNMP as a method of
communication between co-operating hosts; the meter seems unlikely to
have any inherent security risks.
Since, however, the traffic flow data can be extremely valuable for
network management purposes it is vital that sensible precautions be
taken to keep the meter and its data secure. This could be achieved in
many ways, for example
- Physical Separation. Meter(s) and meter reader(s) could be
deployed within a separate network, access to which is carefully
controlled.
- Application-layer Security. A minimal level of security for SNMP
is provided by using 'community' strings, which are essentially
clear-text passwords. Stronger security for SNMP is being
developed within the IETF; when this becomes available it should be
used to protect managed network equipment.
- Lower-layer Security. Access to the meter can be protected using
encryption at the network layer. For example, one could run SNMP
to the meter through an encrypted TCP tunnel.
When implementing a meter it may be sensible to use separate network
interfaces for control and for metering. If this is done the control
interface can be made physically secure, which also guards against
denial-of-service attacks. Denial-of-service attacks on the metering
interfaces are not a concern, since they appear as extra traffic flows
which can be measured!
9 Author's Address
Nevil Brownlee Nevil Brownlee
Information Technology Sytems & Services Information Technology Systems & Services
The University of Auckland The University of Auckland
Phone: +64 9 373 7599 x8941 Phone: +64 9 373 7599 x8941
E-mail: n.brownlee @auckland.ac.nz E-mail: n.brownlee @auckland.ac.nz
 End of changes. 100 change blocks. 
205 lines changed or deleted 327 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/