All MIBs › RFC1354-MIB › ipForwardType
ipForwardType
Module: RFC1354-MIB
OID (symbolic): RFC1354-MIB::ipForwardType
OID (numeric): 1.3.6.1.2.1.4.24.2.1.6
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for which the next hop is not the final destina- tion.
Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipForwardTable object. That is, it effectively disassociates the destination identified with said entry from the route iden- tified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not current- ly in use. Proper interpretation of such en- tries requires examination of the relevant ip- ForwardType object.
What is ipForwardType?
This value classifies a forwarding table entry as local, meaning the destination is directly reachable, or remote, meaning it is reached via a next hop, and setting it to invalid(2) effectively deletes the route. Admins use the local and remote classification to distinguish directly connected networks from routed ones, and can set this field to invalid(2) to administratively remove a stale or unwanted route without necessarily removing the table row itself. For example, an admin troubleshooting a bad static route could set its ipForwardType to invalid(2) to disable that route from being used for forwarding.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.4.24.2.1.6 snmpwalk -v2c -c public <target> RFC1354-MIB::ipForwardType
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.4.24.2.1.6.1 snmpget -v2c -c public <target> RFC1354-MIB::ipForwardType.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.4.24.2.1.6.1 i <value>
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::ipForwardType 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.6 | ipForwardType | RFC1354-MIB |