Reference record for OID 1.3.6.1.2.1.40.1.1

Parent
1.3.6.1.2.1.40.1 (flowControl)
Node code
1
Node name
flowRuleSetInfoTable
Numeric OID
1.3.6.1.2.1.40.1.1
URN notation
urn:oid:1.3.6.1.2.1.40.1.1
Type
OBJECT-TYPE
ASN.1 notation

{1 3 6 1 2 1 40 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) flowMIB(40) flowControl(1) flowRuleSetInfoTable(1)}
OID-IRI notation
  • /1/3/6/1/2/1/40/1/1
  • /ISO/Identified-Organization/6/1/2/1/40/1/1
  • /ISO/3/6/1/2/1/40/1/1
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/identified-organization/dod/internet/mgmt/mib/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/org/dod/internet/mgmt/mib-2/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/org/dod/internet/mgmt/mib/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/org/dod/internet/mgmt/stdmib-2/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/iso-identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/iso-identified-organization/dod/internet/mgmt/stdmib-2/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/iso-organization/dod/internet/mgmt/mib-2/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/iso-organization/dod/internet/mgmt/mib/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/iso-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/flowMIB/flowControl/flowRuleSetInfoTable
  • /iso/iso-organization/dod/internet/mgmt/stdmib-2/flowMIB/flowControl/flowRuleSetInfoTable

Descriptions

Descriptions may differ between sources. The primary description is shown first.

Primary description: OID Repository

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-base.com
Automatically extracted from RFC2720

Alternative description: Circitor

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

Source file: Download FLOW-METER-MIB.txt · Publisher's file

Copy from Netdisco; File: rfc/FLOW-METER-MIB.txt; 66,014 bytes

Vendor MIB copy from the Netdisco archive.

Related source files and packages:

Source file: Download FLOW-METER-MIB · Publisher's file

Copy from Observium Community; File: rfc/FLOW-METER-MIB; 66,014 bytes

Vendor MIB copy from the Observium Community archive.

Related source files and packages:

Source file: Download RFC 2720 · Publisher's file · RFC errata

File: rfc/rfc2720.txt; 103,781 bytes

Source file: Download FLOW-METER-MIB.mib

Publisher path: Mibs; 68,092 bytes

Alternative description: MIBdepot

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.

Source file: Download rfc2720-Traffic-Flow-Measurement---Meter.mib.txt

File: ietf_rfcs/rfc2720-Traffic-Flow-Measurement---Meter.mib.txt; 68,245 bytes

flowRuleSetInfoTable — MIBdepot, RFC Editor

An array of information about the rule sets held in the meter. Rule set 1 is the meter default, used when the meter starts up. It is built in to the meter; it may not be changed.

Source records

flowRuleSetInfoTable

Status in source: current.

Names: flowRuleSetInfoTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "flowRuleSetInfoTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "FlowRuleSetInfoEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An array of information about the rule sets held in the meter. Rule set 1 is the meter default, used when the meter starts up. It is built in to the meter; it may not be changed.\"",
    "::=",
    "{",
    "flowControl",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "FlowRuleSetInfoEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An array of information about the rule sets held in the meter. Rule set 1 is the meter default, used when the meter starts up. It is built in to the meter; it may not be changed."
    ],
    null,
    null,
    null,
    null
  ]
}
  • RFC Editor · RFC 2064 · RFC errata · Publisher's source file: Traffic Flow Measurement: Meter MIB

    Module: FLOW-METER-MIB

    Published definition
    flowRuleSetInfoTable OBJECT-TYPE
    SYNTAX  SEQUENCE OF FlowRuleSetInfoEntry
    MAX-ACCESS  not-accessible
    STATUS  current
    DESCRIPTION
        "An array of information about the rule sets held in the
        meter.   Rule set 1 is the meter default, used when the meter
        starts up.  It is built in to the meter; it may not be
        changed."
    ::= { flowControl 1 }
    Module imports
    {'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'Integer32', 'TimeTicks'], 'RFC1213-MIB': ['mib-2', 'ifIndex'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE']}
    · Download Traffic Flow Measurement: Meter MIB
    Source location: FLOW-METER-MIB::flowRuleSetInfoTable.
    Source version and references

    Downloaded: 2026-10-19T00:18:23.171326+00:00.

  • Preserved mibdepot archive

    Module: FLOW-METER-MIB

    Published definition
    flowRuleSetInfoTable OBJECT-TYPE
    SYNTAX  SEQUENCE OF FlowRuleSetInfoEntry
    MAX-ACCESS  not-accessible
    STATUS  current
    DESCRIPTION
        "An array of information about the rule sets held in the
        meter.   Rule set 1 is the meter default, used when the meter
        starts up.  It is built in to the meter; it may not be
        changed."
    ::= { flowControl 1 }
    Module imports
    {'RMON-MIB': ['OwnerString'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'Integer32', 'TimeTicks'], 'RFC1213-MIB': ['mib-2', 'ifIndex'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE']}
    · Download rfc2064-Traffic-Flow-Measurement---Meter.mib.txt
    Source location: FLOW-METER-MIB::flowRuleSetInfoTable.
    Source version and references

    Archived: 2026-10-19T00:22:09.558700+00:00.

Information from MIBdepot

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 }

Information from Circitor

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 }

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.40.1.1.1 flowRuleSetInfoEntry88 flowRuleSetInfoEntry OBJECT-TYPE
SYNTAX FlowRuleSetInfoEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information …

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.40.1.2 flowInterfaceTable13 flowInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF FlowInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An a…
1.3.6.1.2.1.40.1.3 flowReaderInfoTable18 flowReaderInfoTable OBJECT-TYPE
SYNTAX SEQUENCE OF FlowReaderInfoEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An…
1.3.6.1.2.1.40.1.4 flowManagerInfoTable110 flowManagerInfoTable OBJECT-TYPE
SYNTAX SEQUENCE OF FlowManagerInfoEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"…
1.3.6.1.2.1.40.1.5 flowFloodMark11 flowFloodMark OBJECT-TYPE
SYNTAX Integer32 (0..100)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A value expressed as a pe…
1.3.6.1.2.1.40.1.6 flowInactivityTimeout11 flowInactivityTimeout OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The time in seconds since …
1.3.6.1.2.1.40.1.7 flowActiveFlows11 flowActiveFlows OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of flows which are cur…
1.3.6.1.2.1.40.1.8 flowMaxFlows11 flowMaxFlows OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of flows allowed …
1.3.6.1.2.1.40.1.9 flowFloodMode11 flowFloodMode OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates that the meter has pass…