| OID | 1.3.6.1.2.1.4.21.1.8 |
| Module | RFC1213-MIB (DELL) |
| Nom | ipRouteType |
| Acces | readwrite |
| Status | mandatory |
| Description | The type of route. Note that the values
direct(3) and indirect(4) refer to the notion of
direct and indirect routing in the IP
architecture.
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding entry
in the ipRouteTable object. That is, it
effectively dissasociates 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 ipRouteType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-direct, 4-indirect) |
| Module | RFC1213-MIB (ietf) |
| Nom | ipRouteType |
| Acces | readwrite |
| Status | mandatory |
| Description | The type of route. Note that the values
direct(3) and indirect(4) refer to the notion of
direct and indirect routing in the IP
architecture.
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding entry
in the ipRouteTable object. That is, it
effectively dissasociates 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 ipRouteType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-direct, 4-indirect) |
| Module | RFC1213-MIB (Force10-9.14.2.1) |
| Nom | ipRouteType |
| Acces | readwrite |
| Status | mandatory |
| Description | The type of route. Note that the values
direct(3) and indirect(4) refer to the notion of
direct and indirect routing in the IP
architecture.
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding entry
in the ipRouteTable object. That is, it
effectively dissasociates 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 ipRouteType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-direct, 4-indirect) |
| Module | IP-MIB (FS) |
| Nom | ipRouteType |
| Acces | readwrite |
| Status | deprecated |
| Description | The type of route. Note that the values
direct(3) and indirect(4) refer to the notion of
direct and indirect routing in the IP
architecture.
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding entry
in the ipRouteTable object. That is, it
effectively dissasociates 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 ipRouteType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-direct, 4-indirect) |
| Module | RFC1213-MIB (FS) |
| Nom | ipRouteType |
| Acces | readwrite |
| Status | mandatory |
| Description | The type of route. Note that the values
direct(3) and indirect(4) refer to the notion of
direct and indirect routing in the IP
architecture.
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding entry
in the ipRouteTable object. That is, it
effectively dissasociates 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 ipRouteType object. |
| Syntaxe | Enumeration (1-other, 2-invalid, 3-direct, 4-indirect) |