The status of the information contained in this
route entry.
Setting this object to the value bad(4) has the
effect of invalidating the corresponding entry
in the rtmpTable. That is, it effectively
disassociates the mapping 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 from agents
tabular information corresponding to entries not
currently in use. Proper interpretation of such
entries requires examination of the relevant
rtmpState object.
rtmpState OBJECT-TYPE
SYNTAX INTEGER {
good(1),
suspect(2),
badZero(3),
badOne(4),
invalid(5)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The status of the information contained in this
route entry.
Setting this object to the value invalid(5) has the
effect of invalidating the corresponding entry in
the rtmpTable. That is, it effectively
disassociates the mapping 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 from agents tabular
information corresponding to entries not currently
in use. Proper interpretation of such entries
requires examination of the relevant rtmpState
object."
View at oid-info.com
The status of the information contained in this
route entry.
Setting this object to the value invalid(5) has the
effect of invalidating the corresponding entry in
the rtmpTable. That is, it effectively
disassociates the mapping 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 from agents tabular
information corresponding to entries not currently
in use. Proper interpretation of such entries
requires examination of the relevant rtmpState
object.
Parsed from file rfc1742-AppleTalk.mib.txt
Company: None
Module: APPLETALK-MIB
The status of the information contained in this
route entry.
Setting this object to the value invalid(5) has the
effect of invalidating the corresponding entry in
the rtmpTable. That is, it effectively
disassociates the mapping 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 from agents tabular
information corresponding to entries not currently
in use. Proper interpretation of such entries
requires examination of the relevant rtmpState
object.
Parsed from file APPLETALK-MIB.mib
Module: APPLETALK-MIB
rtmpState OBJECT-TYPE SYNTAX INTEGER { good(1), suspect(2), goingBad(3), bad(4) } ACCESS read-write STATUS mandatory DESCRIPTION "The status of the information contained in this route entry. Setting this object to the value bad(4) has the effect of invalidating the corresponding entry in the rtmpTable. That is, it effectively disassociates the mapping 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 from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant rtmpState object." ::= { rtmpEntry 7 }
Automatically extracted from RFC1742
rtmpState OBJECT-TYPE SYNTAX INTEGER { good(1), suspect(2), badZero(3), badOne(4), invalid(5) } ACCESS read-write STATUS mandatory DESCRIPTION "The status of the information contained in this route entry. Setting this object to the value invalid(5) has the effect of invalidating the corresponding entry in the rtmpTable. That is, it effectively disassociates the mapping 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 from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant rtmpState object." ::= { rtmpEntry 7 }
rtmpState OBJECT-TYPE SYNTAX INTEGER { good(1), suspect(2), badZero(3), badOne(4), invalid(5) } ACCESS read-write STATUS mandatory DESCRIPTION "The status of the information contained in this route entry. Setting this object to the value invalid(5) has the effect of invalidating the corresponding entry in the rtmpTable. That is, it effectively disassociates the mapping 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 from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant rtmpState object." ::= { rtmpEntry 7 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.13.5.1.1.1 | rtmpRangeStart | 0 | 0 | The first DDP network address in the network range to which this routing entry pertains. This is a two octet DDP network address… |
| 1.3.6.1.2.1.13.5.1.1.2 | rtmpRangeEnd | 0 | 0 | The last DDP network address in the network range to which this routing entry pertains. This is a two octet DDP network address … |
| 1.3.6.1.2.1.13.5.1.1.3 | rtmpNextHop | 0 | 0 | The next hop in the route to this entry's destination network. If the type of this route is Appletalk, this address takes the sa… |
| 1.3.6.1.2.1.13.5.1.1.4 | rtmpType | 0 | 0 | The type of network over which this route points. |
| 1.3.6.1.2.1.13.5.1.1.5 | rtmpPort | 0 | 0 | The index of the AppleTalk port over which this route points. |
| 1.3.6.1.2.1.13.5.1.1.6 | rtmpHops | 0 | 0 | The number of hops required to reach the destination network to which this routing entry pertains. |