flowManagerInfoEntry OBJECT-TYPE
SYNTAX FlowManagerInfoEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular meter ask. By creating
an entry in this table and activating it, a manager requests
that the meter
un the indicated RuleSet.
The entry also specifies a HighWaterMark and a StandbyRuleSet.
If the meters flow table usage exceeds this tasks
HighWaterMark the meter will stop running the tasks
CurrentRuleSet and switch to its StandbyRuleSet.
If the value of the tasks StandbyRuleSet is 0 when its
HighWaterMark is exceeded, the meter simply stops running the
tasks CurrentRuleSet. By careful selection of HighWaterMarks
for the various tasks a manager can ensure that the most
critical RuleSets are the last to stop running as the number
of flows increases.
When a manager has determined that the demand for flow table
space has abated, it may cause the task to switch back to its
CurrentRuleSet by setting its flowManagerRunningStandby
variable to false(2)."
INDEX { flowManagerIndex }
View at oid-info.com
Information about a particular meter 'task.' By creating
an entry in this table and activating it, a manager requests
that the meter 'run' the indicated RuleSet.
The entry also specifies a HighWaterMark and a StandbyRuleSet.
If the meter's flow table usage exceeds this task's
HighWaterMark the meter will stop running the task's
CurrentRuleSet and switch to its StandbyRuleSet.
If the value of the task's StandbyRuleSet is 0 when its
HighWaterMark is exceeded, the meter simply stops running the
task's CurrentRuleSet. By careful selection of HighWaterMarks
for the various tasks a manager can ensure that the most
critical RuleSets are the last to stop running as the number
of flows increases.
When a manager has determined that the demand for flow table
space has abated, it may cause the task to switch back to its
CurrentRuleSet by setting its flowManagerRunningStandby
variable to false(2).
Parsed from file rfc2720-Traffic-Flow-Measurement---Meter.mib.txt
Company: None
Module: FLOW-METER-MIB
Information about a particular meter 'task.' By creating
an entry in this table and activating it, a manager requests
that the meter 'run' the indicated RuleSet.
The entry also specifies a HighWaterMark and a StandbyRuleSet.
If the meter's flow table usage exceeds this task's
HighWaterMark the meter will stop running the task's
CurrentRuleSet and switch to its StandbyRuleSet.
If the value of the task's StandbyRuleSet is 0 when its
HighWaterMark is exceeded, the meter simply stops running the
task's CurrentRuleSet. By careful selection of HighWaterMarks
for the various tasks a manager can ensure that the most
critical RuleSets are the last to stop running as the number
of flows increases.
When a manager has determined that the demand for flow table
space has abated, it may cause the task to switch back to its
CurrentRuleSet by setting its flowManagerRunningStandby
variable to false(2).
Parsed from file FLOW-METER-MIB.mib
Module: FLOW-METER-MIB
Automatically extracted from RFC2720
flowManagerInfoEntry OBJECT-TYPE SYNTAX FlowManagerInfoEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular meter 'task.' By creating an entry in this table and activating it, a manager requests that the meter 'run' the indicated RuleSet. The entry also specifies a HighWaterMark and a StandbyRuleSet. If the meter's flow table usage exceeds this task's HighWaterMark the meter will stop running the task's CurrentRuleSet and switch to its StandbyRuleSet. If the value of the task's StandbyRuleSet is 0 when its HighWaterMark is exceeded, the meter simply stops running the task's CurrentRuleSet. By careful selection of HighWaterMarks for the various tasks a manager can ensure that the most critical RuleSets are the last to stop running as the number of flows increases. When a manager has determined that the demand for flow table space has abated, it may cause the task to switch back to its CurrentRuleSet by setting its flowManagerRunningStandby variable to false(2)." INDEX { flowManagerIndex } ::= { flowManagerInfoTable 1 }
flowManagerInfoEntry OBJECT-TYPE SYNTAX FlowManagerInfoEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular meter 'task.' By creating an entry in this table and activating it, a manager requests that the meter 'run' the indicated RuleSet. The entry also specifies a HighWaterMark and a StandbyRuleSet. If the meter's flow table usage exceeds this task's HighWaterMark the meter will stop running the task's CurrentRuleSet and switch to its StandbyRuleSet. If the value of the task's StandbyRuleSet is 0 when its HighWaterMark is exceeded, the meter simply stops running the task's CurrentRuleSet. By careful selection of HighWaterMarks for the various tasks a manager can ensure that the most critical RuleSets are the last to stop running as the number of flows increases. When a manager has determined that the demand for flow table space has abated, it may cause the task to switch back to its CurrentRuleSet by setting its flowManagerRunningStandby variable to false(2)." INDEX { flowManagerIndex } ::= { flowManagerInfoTable 1 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.40.1.4.1.1 | flowManagerIndex | 0 | 0 | An index which selects an entry in the flowManagerInfoTable. |
| 1.3.6.1.2.1.40.1.4.1.2 | flowManagerCurrentRuleSet | 0 | 0 | Index to the array of RuleSets. Specifies which set of rules is the 'current' one for this task. The meter will be 'running' th… |
| 1.3.6.1.2.1.40.1.4.1.3 | flowManagerStandbyRuleSet | 0 | 0 | Index to the array of RuleSets. After reaching HighWaterMark (see below) the manager will switch to using the task's StandbyRule… |
| 1.3.6.1.2.1.40.1.4.1.4 | flowManagerHighWaterMark | 0 | 0 | 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.4.1.5 | flowManagerCounterWrap | 0 | 0 | Specifies whether PDU and octet counters should wrap when they reach the top of their range (normal behaviour for Counter64 objec… |
| 1.3.6.1.2.1.40.1.4.1.6 | flowManagerOwner | 0 | 0 | Identifies the manager which created this row. |
| 1.3.6.1.2.1.40.1.4.1.7 | flowManagerTimeStamp | 0 | 0 | Time this row was last changed by its manager. |
| 1.3.6.1.2.1.40.1.4.1.8 | flowManagerStatus | 0 | 0 | The status of this row in the flowManagerInfoTable. A value of active(1) implies that this task may be activated, by setting its… |
| 1.3.6.1.2.1.40.1.4.1.9 | flowManagerRunningStandby | 0 | 0 | Set to true(1) by the meter to indicate that it has switched to runnning this task's StandbyRuleSet in place of its CurrentRuleSe… |