OID repository
OID Repository
http://oid-info.com
Display OID:
 
Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemmgmt(2) Action itemmib-2(1) Action itemflowMIB(40) Action itemflowControl(1)  

Navigating the OID tree

flowRuleSetInfoTable(1)
child OID: Child OID delimiter flowRuleSetInfoEntry(1) Child OID delimiter
 
Separation line
 
OID description

   
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

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."



Information:

Automatically extracted from IETF RFC 2720.

 
Short URL for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved, Orange © 2023
Tree display Parent OID: flowControl(1) First child OID: flowRuleSetInfoEntry(1) Next sibling OID: flowInterfaceTable(2) Last sibling OID: flowFloodMode(9)
Separation line
OID helper Webmaster Bullet 25 Dec 2019 Bullet Page top