Chapter 12: Routing Protocols Labs:
12.1.6 | In this lab you will configure a static route between neighboring routers.
12.3.5 | In this lab you will configure RIP as the routing protocol.
12.5.1 | As a system administrator, there will be times where configuring static routes can be very useful. Static routes are useful for stub networks because there is only one way to get to that network. Security is anther reason to use static routes, if you have a network or networks that you don't want the rest of the network to be able to "see" you would not want RIP or other routing protocols sending periodic updates to other routers. With simple networks (few routers) it is sometimes more efficient to use static routes since it conserves bandwidth on WAN links. In this lab you will use static routes for troubleshooting purposes and to see their relationship to dynamic routes and routing protocols.
12.5.2 | In this lab you will setup a WAN connection between Lab-A and Lab-E to create alternate paths in the standard router lab setup. Using a set of WAN serial cables, connect Lab-A Serial 1 to Lab-E Serial 0. Remember to set the clock rate on the DCE side of the cable (Lab-E's Serial 0 interface).
12.5.3 | In the previous challenge lab, you saw how long it took to converge when a link went down. In this lab, your task is to find out how to prevent and control routing loops. The use of hold-down timers, defining a maximum hop count, counting to infinity, poison reverse and split-horizon are all methods of controlling routing loops. You will use the RIP hop count metric to control routing loops in this lab.