Using the IP Routing Table Window
7-4
Route Info
A reference to MIB definitions specific to the particular routing protocol which is
responsible for this route, as determined by the value specified in the route’s
ipRouteProto value. If this information is not present, its value should be set to the
OBJECT IDENTIFIER {0,0}, which is a syntactically valid object identifier, and any
conformant implementation o f ASN.1 and BER must be ab le to generate and
recognize this value. This field displays the ipRouteInfo.
Route Metrics
Displays the Routing Metrics for the route. Metrics may be Primary or Alternate
as explained below:
Route Metric 1 The primary routing metric for this route, according to
the ipRouteMetric1. The semantics of this metric are
determined by the routing-protocol type specified in the
route’s ipRouteProto value. If this metric is not used, its
value should be set to -1.
Route Metrics 2-5 An alternate routing metric for this route, according to
the ipRouteMetric2, ipRouteMetric3, ipRouteMetric4, and
ipRouteMetric5 (the fifth route metric is available only for
devices supporting MIB-II). The semantics of this metric
are determined by the routing-protocol type specified in
the route’s ipRouteProto value. If this metric is not used,
the value should be set to -1.
Route Type
The type of route, according to the ipRouteType. To change the Route T ype, click on
the appropriate option button:
• Other (1)None of the following.
• Invalid (2)An invalidated route.
• Direct (3)Route to directly connected (sub)network.
• Indirect (4)Route to a non-local host/network/subnetwork.
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 of invalid (2) has
the effect of invalidating the corresponding entry in the ipRouteTable object. 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
correspond to entries not currently in use. Proper interpretation of such entries
requires examination of the relevant ipRouteType object.
NOTE
Fields not supported by the device’s firmware will display a value of “Not avail in device”.