28.06.2014 Views

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Now let’s explore some of the other options for static routes:<br />

optik(config)#ip route 1.0.0.0 255.0.0.0 serial0/1 ?<br />

Distance metric for this route<br />

A.B.C.D Forwarding router's address<br />

name Specify name of the next hop<br />

permanent permanent route<br />

tag Set tag for this route<br />

The first option we see a distance metric for this route. Each routing protocol has<br />

a different default distance metric assigned to it. RIP has a default static route<br />

distance of 120. So actually we already put that in our command, even though it<br />

does not appear in our ip route command. What this is used for is when we want<br />

to put in more than one static route on our router. The router will automatically<br />

select the static route with the lowest distance metric first then, if that route is not<br />

available, go to the route with the second lowest distance metric and then so on.<br />

Distance metrics, as you can see, vary from 1 to 255. Here are some common<br />

metrics for you to know about here at this time:<br />

Connected interface 0<br />

Static route 1<br />

RIP 120<br />

Unknown 255<br />

If we were to add another router in then we would need to add in another static<br />

route. Using that methodology if we had a network with many routers we could<br />

bury ourselves in static routes which has the possibility of causing major<br />

problems. In our example we just did instead of setting a static route between the<br />

two routers we could set a default network route on optik. This will essentially<br />

allow us to add routers at will without all those static routes. Setting many static<br />

routes essentially defeats the purposes of having routers make decisions anyways.<br />

So there. In the next couple of labs you will learn more about different types of<br />

routes and their uses. In the meantime let’s try to do some more exercises and<br />

learn <strong>by</strong> doing!<br />

9. Ok. Let’s try putting a loop back into our network. Connect another serial line<br />

from s0/1 (DTE) on phiber to s0/0 (DCE) on optik. Use 56000 for the clockrate.<br />

We know from our routing loop labs that our split-horizon is set <strong>by</strong> default to<br />

prevent routing loops, but if we have two paths wouldn’t we want to take<br />

advantage of that? Absolutely! If all of our metrics are equal, then our routers<br />

will perform load-balancing across the equal lines. Now, of course, you know we<br />

can change that. The command to change load-balancing is “variance.” Use your<br />

knowledge of the <strong>CISCO</strong> technical support site and router help features to find<br />

out more about this command and how to use it. What we are more concerned<br />

with in this lab is static routing. Set your new serial connection to have a<br />

different administrative distance than the main line so it will act as a backup line.<br />

10. Ping and trace the route between workstation A and B.<br />

233

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!