All MIBs › RFC1354-MIB › ipForwardPolicy
ipForwardPolicy
Module: RFC1354-MIB
OID (symbolic): RFC1354-MIB::ipForwardPolicy
OID (numeric): 1.3.6.1.2.1.4.24.2.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The general set of conditions that would cause
the selection of one multipath route (set of
next hops for a given destination) is referred
to as 'policy'.
Unless the mechanism indicated by ipForwardPro-
to specifies otherwise, the policy specifier is
the IP TOS Field. The encoding of IP TOS is as
specified by the following convention. Zero
indicates the default path if no more specific
policy applies.
+-----+-----+-----+-----+-----+-----+-----+-----+
| | | |
| PRECEDENCE | TYPE OF SERVICE | 0 |
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+
IP TOS IP TOS
Field Policy Field Policy
Contents Code Contents Code
0 0 0 0 ==> 0 0 0 0 1 ==> 2
0 0 1 0 ==> 4 0 0 1 1 ==> 6
0 1 0 0 ==> 8 0 1 0 1 ==> 10
0 1 1 0 ==> 12 0 1 1 1 ==> 14
1 0 0 0 ==> 16 1 0 0 1 ==> 18
1 0 1 0 ==> 20 1 0 1 1 ==> 22
1 1 0 0 ==> 24 1 1 0 1 ==> 26
1 1 1 0 ==> 28 1 1 1 1 ==> 30
Protocols defining 'policy' otherwise must ei-
ther define a set of values which are valid for
this object or must implement an integer-
instanced policy table for which this object's
value acts as an index.What is ipForwardPolicy?
This value represents the routing "policy", typically encoded from the packet's IP Type-of-Service field, that determines which of several possible routes to a destination is selected when multiple paths exist. Admins encounter this on devices implementing policy-based or TOS-based routing, where it explains why two entries can share the same destination but apply to different classes of traffic. For example, a value of 16 corresponds to a specific TOS precedence and type-of-service combination, meaning that route entry only applies to traffic marked with that particular TOS bit pattern.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.4.24.2.1.3 snmpwalk -v2c -c public <target> RFC1354-MIB::ipForwardPolicy
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.4.24.2.1.3.1 snmpget -v2c -c public <target> RFC1354-MIB::ipForwardPolicy.1
Start monitoring vendor-neutral, standards-based MIB, IP routers and Layer-3 switches (extended IP forwarding table) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1354-MIB::ipForwardPolicy OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, IP routers and Layer-3 switches (extended IP forwarding table) from a single console.
OID Breakdown
Upper-level ancestors (10 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 |
| 1.3.6.1.2.1.4 | ip | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.4.24 | ipForward | IP-FORWARD-MIB |
| 1.3.6.1.2.1.4.24.2 | ipForwardTable | IP-FORWARD-MIB |
| 1.3.6.1.2.1.4.24.2.1 | ipForwardEntry | IP-FORWARD-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.4.24.2.1.3 | ipForwardPolicy | RFC1354-MIB |