9.3.2 Checking route information

Check information about static routes.

Figure 9-6: Result of show ip static route
> show ip static route Date 20XX/07/14 12:00:00 UTC Status Codes: * valid, > active, r RIB failure Destination Next Hop Distance Weight Status Flag > 0.0.0.0/0 10.1.1.50 2 0 IFdown - > 192.168.1/24 10.1.1.100 100 0 Act - * 192.168.1/24 172.16.1.100 200 0 Act NoResolve > 192.168.2/24 172.16.1.100 2 0 Act NoResolve 172.16.2.100 2 0 Act NoResolve > 192.168.3/24 10.2.1.100 2 0 Act Reach Poll 192.168.4/24 10.2.1.101 2 0 UnReach Poll

Figure 9-6: Result of show ip static route

> show ip static route
Date 20XX/07/14 12:00:00 UTC
Status Codes: * valid, > active, r RIB failure
   Destination        Next Hop       Distance Weight Status      Flag
*> 0.0.0.0/0          10.1.1.50       2       0      IFdown      -
*> 192.168.1/24       10.1.1.100      100     0      Act         -
*  192.168.1/24       172.16.1.100    200     0      Act         NoResolve
*> 192.168.2/24       172.16.1.100    2       0      Act         NoResolve
                      172.16.2.100    2       0      Act         NoResolve
*> 192.168.3/24       10.2.1.100      2       0      Act Reach   Poll
   192.168.4/24       10.2.1.101      2       0      UnReach     Poll

Notes

When a route is registered in the routing table, an asterisk and angle bracket (*>) appear in the leftmost Status Codes field.
For an alternate route not registered in the routing table, the angle bracket (>) is omitted but the asterisk (*) appears in the Status Codes field if the route is valid.
For an invalid route, neither the asterisk nor angle bracket appears in the Status Codes field, and a problem of some sort is indicated in the Status field. IFdown means that the route is invalid due to a failure in an interface. UnReach means that the dynamic monitoring functionality has not confirmed that the route is reachable.