| OID | 1.3.6.1.2.1.4.24.2.1.6 |
| Module | IP-FORWARD-MIB (CISCO) |
| Nom | ipForwardType |
| Acces | readwrite |
| Status | obsolete |
| 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. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-local, 4-remote) |
| Module | IP-FORWARD-MIB (DELL) |
| Nom | ipForwardType |
| Acces | readwrite |
| Status | obsolete |
| 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 destination.
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 identified 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 currently in use. Proper
interpretation of such entries requires examination of
the relevant ipForwardType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-local, 4-remote) |
| Module | IP-FORWARD-MIB (ietf) |
| Nom | ipForwardType |
| Acces | readwrite |
| Status | obsolete |
| 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 destination.
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 identified 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 currently in use. Proper
interpretation of such entries requires examination of
the relevant ipForwardType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-local, 4-remote) |
| Module | IP-FORWARD-MIB (Alcatel) |
| Nom | ipForwardType |
| Acces | readwrite |
| Status | obsolete |
| 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. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-local, 4-remote) |
| Module | IP-FORWARD-MIB (Force10-9.14.2.1) |
| Nom | ipForwardType |
| Acces | readwrite |
| Status | obsolete |
| 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 destination.
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 identified 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 currently in use. Proper
interpretation of such entries requires examination of
the relevant ipForwardType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-local, 4-remote) |
| Module | IP-FORWARD-MIB (FS) |
| Nom | ipForwardType |
| Acces | readwrite |
| Status | obsolete |
| 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 destination.
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 identified 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 currently in use. Proper
interpretation of such entries requires examination of
the relevant ipForwardType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-local, 4-remote) |