When using the ip route command, you can identify where packets should be routed to in two ways:
Both ways are shown in both the "Configuration Example: Static Routes" section and the "Default Routing" section.
The permanent Keyword (Optional)
Without the permanent keyword in a static route statement, a static route will be removed if an interface goes down. If you don't tighten those serial cables or if you have a bad connector on a UTP cable, a cable can easily become loose, causing an interface to go down. But plugging the cable back in does not add that static route back into the routing table. The only way to get that route back into the table is to reload the router or use the permanent keyword in your ip route command. This option is especially useful when the night janitor knocks a cable loose and replaces it, hoping no one will notice.... Can your network afford to lose a route for a few hours until the next morning when you or your IT staff comes in to work? The permanent keyword is also useful in helping to avoid constant shortest path first (SPF) calculations in OSPF when there is a flapping link; if the link goes down, the route will stay in the routing table.
However, you must be careful when using this optional keyword. You might want that route to be removed from the routing table. You might also want to know why the night janitor was in your wiring closet in the first place.
Static Routes and Administrative Distance (Optional)
By default, a static route is assigned an administrative distance (AD) of 1. Administrative distance rates the "trustworthiness" of a route. AD is a number from 0-255, where 0 is absolutely trusted, and 255 cannot be trusted at all. Therefore, an AD of 1 is an extremely reliable rating, with only an AD of 0 being better. An AD of 0 is assigned to a directly connected route. The following table lists the administrative distance for each type of route.
By default, a static route will always be used instead of a routing protocol. By adding an AD number to your ip route statement, however, you can effectively create a backup route to your routing protocol. If your network is using EIGRP, and you need a backup route, add a static route with an AD greater than 90. EIGRP will be used because its AD is better (lower) than the static route. But if EIGRP goes down, the static route will be used in its place. This is known as a floating static route. See Appendix A, "Complete Configuration Example," for an example where a floating static route is used as a backup route.