flowRuleSetInfoTable OBJECT-TYPE
SYNTAX SEQUENCE OF FlowRuleSetInfoEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An array of information about the RuleSets held in the
meter.
Any manager may configure a new RuleSet for the meter by
creating a row in this table with status active(1), and setting
values for all the objects in its rules. At this stage the new
RuleSet is available but not
unning, i.e. it is not being
used by the meter to produce entries in the flow table.
To actually
un a RuleSet a manager must create a row in
the flowManagerInfoTable, set its flowManagerStatus to
active(1), and set either its CurrentRuleSet or StandbyRuleSet
to point to the RuleSet to be run.
Once a RuleSet is running a manager may not change any of the
objects within the RuleSet itself. Any attempt to do so should
result in a notWritable(17) SNMP error-status for such objects.
A manager may stop a RuleSet running by removing all
references to it in the flowManagerInfoTable (i.e. by setting
CurrentRuleSet and StandbyRuleSet values to 0). This provides
a way to stop RuleSets left running if a manager fails.
For example, when a manager is started, it could search the
meters flowManager table and stop all RuleSets having a
specified value of flowRuleInfoOwner.
To prevent a manager from interfering with variables belonging
to another manager, the meter should use MIB views [RFC2575] so
as to limit each managers access to the meters variables,
effectively dividing the single meter into several virtual
meters, one for each independent manager."
View at oid-info.com
An array of information about the RuleSets held in the
meter.
Any manager may configure a new RuleSet for the meter by
creating a row in this table with status active(1), and setting
values for all the objects in its rules. At this stage the new
RuleSet is available but not 'running', i.e. it is not being
used by the meter to produce entries in the flow table.
To actually 'run' a RuleSet a manager must create a row in
the flowManagerInfoTable, set it's flowManagerStatus to
active(1), and set either its CurrentRuleSet or StandbyRuleSet
to point to the RuleSet to be run.
Once a RuleSet is running a manager may not change any of the
objects within the RuleSet itself. Any attempt to do so should
result in a notWritable(17) SNMP error-status for such objects.
A manager may stop a RuleSet running by removing all
references to it in the flowManagerInfoTable (i.e. by setting
CurrentRuleSet and StandbyRuleSet values to 0). This provides
a way to stop RuleSets left running if a manager fails.
For example, when a manager is started, it could search the
meter's flowManager table and stop all RuleSets having a
specified value of flowRuleInfoOwner.
To prevent a manager from interfering with variables belonging
to another manager, the meter should use MIB views [RFC2575] so
as to limit each manager's access to the meter's variables,
effectively dividing the single meter into several virtual
meters, one for each independent manager.
Parsed from file rfc2720-Traffic-Flow-Measurement---Meter.mib.txt
Company: None
Module: FLOW-METER-MIB
An array of information about the RuleSets held in the
meter.
Any manager may configure a new RuleSet for the meter by
creating a row in this table with status active(1), and setting
values for all the objects in its rules. At this stage the new
RuleSet is available but not 'running', i.e. it is not being
used by the meter to produce entries in the flow table.
To actually 'run' a RuleSet a manager must create a row in
the flowManagerInfoTable, set it's flowManagerStatus to
active(1), and set either its CurrentRuleSet or StandbyRuleSet
to point to the RuleSet to be run.
Once a RuleSet is running a manager may not change any of the
objects within the RuleSet itself. Any attempt to do so should
result in a notWritable(17) SNMP error-status for such objects.
A manager may stop a RuleSet running by removing all
references to it in the flowManagerInfoTable (i.e. by setting
CurrentRuleSet and StandbyRuleSet values to 0). This provides
a way to stop RuleSets left running if a manager fails.
For example, when a manager is started, it could search the
meter's flowManager table and stop all RuleSets having a
specified value of flowRuleInfoOwner.
To prevent a manager from interfering with variables belonging
to another manager, the meter should use MIB views [RFC2575] so
as to limit each manager's access to the meter's variables,
effectively dividing the single meter into several virtual
meters, one for each independent manager.
Parsed from file FLOW-METER-MIB.mib
Module: FLOW-METER-MIB
Automatically extracted from RFC2720
flowRuleSetInfoTable OBJECT-TYPE SYNTAX SEQUENCE OF FlowRuleSetInfoEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An array of information about the RuleSets held in the meter. Any manager may configure a new RuleSet for the meter by creating a row in this table with status active(1), and setting values for all the objects in its rules. At this stage the new RuleSet is available but not 'running', i.e. it is not being used by the meter to produce entries in the flow table. To actually 'run' a RuleSet a manager must create a row in the flowManagerInfoTable, set it's flowManagerStatus to active(1), and set either its CurrentRuleSet or StandbyRuleSet to point to the RuleSet to be run. Once a RuleSet is running a manager may not change any of the objects within the RuleSet itself. Any attempt to do so should result in a notWritable(17) SNMP error-status for such objects. A manager may stop a RuleSet running by removing all references to it in the flowManagerInfoTable (i.e. by setting CurrentRuleSet and StandbyRuleSet values to 0). This provides a way to stop RuleSets left running if a manager fails. For example, when a manager is started, it could search the meter's flowManager table and stop all RuleSets having a specified value of flowRuleInfoOwner. To prevent a manager from interfering with variables belonging to another manager, the meter should use MIB views [RFC2575] so as to limit each manager's access to the meter's variables, effectively dividing the single meter into several virtual meters, one for each independent manager." ::= { flowControl 1 }
flowRuleSetInfoTable OBJECT-TYPE SYNTAX SEQUENCE OF FlowRuleSetInfoEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An array of information about the RuleSets held in the meter. Any manager may configure a new RuleSet for the meter by creating a row in this table with status active(1), and setting values for all the objects in its rules. At this stage the new RuleSet is available but not 'running', i.e. it is not being used by the meter to produce entries in the flow table. To actually 'run' a RuleSet a manager must create a row in the flowManagerInfoTable, set it's flowManagerStatus to active(1), and set either its CurrentRuleSet or StandbyRuleSet to point to the RuleSet to be run. Once a RuleSet is running a manager may not change any of the objects within the RuleSet itself. Any attempt to do so should result in a notWritable(17) SNMP error-status for such objects. A manager may stop a RuleSet running by removing all references to it in the flowManagerInfoTable (i.e. by setting CurrentRuleSet and StandbyRuleSet values to 0). This provides a way to stop RuleSets left running if a manager fails. For example, when a manager is started, it could search the meter's flowManager table and stop all RuleSets having a specified value of flowRuleInfoOwner. To prevent a manager from interfering with variables belonging to another manager, the meter should use MIB views [RFC2575] so as to limit each manager's access to the meter's variables, effectively dividing the single meter into several virtual meters, one for each independent manager." ::= { flowControl 1 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.40.1.1.1 | flowRuleSetInfoEntry | 8 | 8 | Information about a particular RuleSet. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.40.1.2 | flowInterfaceTable | 1 | 3 | An array of information specific to each meter interface. |
| 1.3.6.1.2.1.40.1.3 | flowReaderInfoTable | 1 | 8 | An array of information about meter readers which have registered their intent to collect flow data from this meter. |
| 1.3.6.1.2.1.40.1.4 | flowManagerInfoTable | 1 | 10 | An array of information about managers which have registered their intent to run RuleSets on this meter. |
| 1.3.6.1.2.1.40.1.5 | flowFloodMark | 1 | 1 | A value expressed as a percentage, interpreted by the meter as an indication of how full the flow table should be before it shoul… |
| 1.3.6.1.2.1.40.1.6 | flowInactivityTimeout | 1 | 1 | The time in seconds since the last packet seen, after which a flow becomes 'idle.' Note that although a flow may be idle, it wil… |
| 1.3.6.1.2.1.40.1.7 | flowActiveFlows | 1 | 1 | The number of flows which are currently in use. |
| 1.3.6.1.2.1.40.1.8 | flowMaxFlows | 1 | 1 | The maximum number of flows allowed in the meter's flow table. At present this is determined when the meter is first started up. |
| 1.3.6.1.2.1.40.1.9 | flowFloodMode | 1 | 1 | Indicates that the meter has passed its FloodMark and is not running in its normal mode. When the manager notices this it should … |