By setting this object to true(1), the user indicates the
desire to use hardware routing for this entry. To disable
hardware routing for this entry, set this object to false(2).
If the underlying switch fabric does not support hardware
routing, this object is ignored.
There is usually limited space in the hardware routing table.
Consequently, if the user enables hardware routing on 'too'
many entries, the agent assigns routes on a first come, first
serve basis (i.e., the user may not get the expected results).
Parsed from file tms-l3-mib.txt
Company: None
Module: TMS-L3-MIB
By setting this object to true(1), the user indicates the
desire to use hardware routing for this entry. To disable
hardware routing for this entry, set this object to false(2).
If the underlying switch fabric does not support hardware
routing, this object is ignored.
There is usually limited space in the hardware routing table.
Consequently, if the user enables hardware routing on 'too'
many entries, the agent assigns routes on a first come, first
serve basis (i.e., the user may not get the expected results).
Parsed from file TMS-L3-MIB.mib
Module: TMS-L3-MIB
Vendor: Wind River Systems
Module: TMS-L3-MIB
[Automatically extracted from oidview.com]
tmsL3IpDynamicUseHw OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "By setting this object to true(1), the user indicates the desire to use hardware routing for this entry. To disable hardware routing for this entry, set this object to false(2). If the underlying switch fabric does not support hardware routing, this object is ignored. There is usually limited space in the hardware routing table. Consequently, if the user enables hardware routing on 'too' many entries, the agent assigns routes on a first come, first serve basis (i.e., the user may not get the expected results)." DEFVAL { true } ::= { tmsL3IpDynamicRouteEntry 5 }
tmsL3IpDynamicUseHw OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "By setting this object to true(1), the user indicates the desire to use hardware routing for this entry. To disable hardware routing for this entry, set this object to false(2). If the underlying switch fabric does not support hardware routing, this object is ignored. There is usually limited space in the hardware routing table. Consequently, if the user enables hardware routing on 'too' many entries, the agent assigns routes on a first come, first serve basis (i.e., the user may not get the expected results)." DEFVAL { true } ::= { tmsL3IpDynamicRouteEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.731.2.2.2.4.2.1.1 | tmsL3IpDynamicDestIpAddr | 0 | 0 | The dynamic route host or subnet IP destination address. All IP destination addresses must be non-zero. |
| 1.3.6.1.4.1.731.2.2.2.4.2.1.2 | tmsL3IpDynamicMask | 0 | 0 | The mask for this IP destination. It contains 1's in the bit positions for the net and subnet IDs and 0's in the bit positions f… |
| 1.3.6.1.4.1.731.2.2.2.4.2.1.3 | tmsL3IpDynamicNextHop | 0 | 0 | The IP address of the next hop of this route. (In the case of a route bound to an interface which is realized via a broadcast med… |
| 1.3.6.1.4.1.731.2.2.2.4.2.1.4 | tmsL3IpDynamicName | 0 | 0 | A user reference name for this Dynamic Route. |
| 1.3.6.1.4.1.731.2.2.2.4.2.1.6 | tmsL3IpDynamicInHw | 0 | 0 | If this object is true(1), this dynamic route is actually in the hardware Route Table. Otherwise it is false(2). |
| 1.3.6.1.4.1.731.2.2.2.4.2.1.7 | tmsL3IpDynamicGateway | 0 | 0 | By setting this object to true(1), the user indicates that this subnet route is a gateway route (i.e., connected to external rout… |
| 1.3.6.1.4.1.731.2.2.2.4.2.1.8 | tmsL3IpDynamicRowStatus | 0 | 0 | This object indicates the status of this entry. A row in this table must be created using the createAndWait(5) action state (i.e… |