All MIBs › FLOW-METER-MIB › flowRuleSelector
flowRuleSelector
Module: FLOW-METER-MIB
OID (symbolic): FLOW-METER-MIB::flowRuleSelector
OID (numeric): 1.3.6.1.2.1.40.3.1.1.3
Node type: OBJECT-TYPE
Type: RuleAttributeNumber
Access: read-write
Description: Indicates the attribute to be matched.
null(0) is a special case; null rules always succeed.
matchingStoD(50) is set by the meter's Packet Matching Engine. Its value is true(1) if the PME is attempting to match the packet with its addresses in Source-to-Destination order (i.e. as they appear in the packet), and false(2) otherwise. Details of how packets are matched are given in the 'Traffic Flow Measurement: Architecture' document [RTFM-ARC]. v1(51), v2(52), v3(53), v4(54) and v5(55) select meter variables, each of which can hold the name (i.e. selector value) of an address attribute. When one of these is used as a selector, its value specifies the attribute to be tested. Variable values are set by an Assign action.
What is flowRuleSelector?
Specifies which packet or meter attribute this rule tests; null(0) always succeeds, matchingStoD(50) reflects the Packet Matching Engine's current source-to-destination direction, and v1 through v5 read back whatever attribute name a prior Assign action stored in that meter variable. An admin sets this when writing a rule to define exactly what condition it checks.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.40.3.1.1.3 snmpwalk -v2c -c public <target> FLOW-METER-MIB::flowRuleSelector
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.40.3.1.1.3.1 snmpget -v2c -c public <target> FLOW-METER-MIB::flowRuleSelector.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.40.3.1.1.3.1 s <value>
Start monitoring Vendor-neutral RTFM traffic flow meter/router, any manufacturer (RFC 2720) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the FLOW-METER-MIB::flowRuleSelector OID value, configure state conditions and alerts, and monitor any Vendor-neutral RTFM traffic flow meter/router, any manufacturer (RFC 2720) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.40 | flowMIB | FLOW-METER-MIB |
| 1.3.6.1.2.1.40.3 | flowRules | FLOW-METER-MIB |
| 1.3.6.1.2.1.40.3.1 | flowRuleTable | FLOW-METER-MIB |
| 1.3.6.1.2.1.40.3.1.1 | flowRuleEntry | FLOW-METER-MIB |
| 1.3.6.1.2.1.40.3.1.1.3 | flowRuleSelector | FLOW-METER-MIB |