20.01.2013 Views

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

RTA have a default route. ISP cannot ping any of the addresses inside the 192.168.1.0/24<br />

address space because it does not have a route. RTA needs a default route pointing to ISP, <strong>and</strong><br />

ISP needs a static route pointing to the 192.168.1.0/24 address space.<br />

Task 5: Configure Static <strong>and</strong> Default Routing<br />

Step 1. For ISP to be able to send Echo replies back to hosts belonging to the 192.168.1.0/24 address<br />

space, it must have a route. Use the following comm<strong>and</strong> on ISP to configure a static route<br />

pointing to the 192.168.1.0/24 address space:<br />

ISP(config)#ip route 192.168.1.0 255.255.255.0 209.165.201.2<br />

Step 2. Now ISP can route back to any host belonging to 192.168.1.0/24. However, RTA, RTB, <strong>and</strong><br />

RTC do not yet have a route for any address space other than 192.168.1.0/24. Because ISP represents<br />

the connection to the rest of the world, you need to configure default routing. A router<br />

without a more specific route in the routing table will send traffic to the default route. Use the<br />

following comm<strong>and</strong> on RTA to configure a default route:<br />

RTA(config)#ip route 0.0.0.0 0.0.0.0 209.165.201.1<br />

Step 3. If you are simulating ISP, use the following comm<strong>and</strong> to configure a default route:<br />

RTA(config)#ip route 0.0.0.0 0.0.0.0 Loopback0<br />

Step 4. Now RTA should be able to ping the Public Web Server. However, RTB <strong>and</strong> RTC still cannot<br />

ping outside the 192.168.1.0/24 address space. The reason is that RTA does not advertise the<br />

default route unless specifically configured to do so. Use the following comm<strong>and</strong> with RIP to<br />

propagate a default route to RTB <strong>and</strong> RTC in the RIP updates:<br />

RTA(config)#router rip<br />

RTA(config-router)#default-information originate<br />

Note: With RIP routing, depending on the platform <strong>and</strong> IOS version, you may need to reload the router that is propagating<br />

the default route before the default route will be sent in routing updates.<br />

Task 6: Verify Connectivity <strong>and</strong> Capture Scripts<br />

Chapter 1: Introduction to Classless Routing 77<br />

Step 1. Verify that all routers now have a default route <strong>and</strong> can ping the Public Web Server.<br />

Note: If you are simulating ISP, test by pinging the loopback interface, 209.165.201.2 on RTA.<br />

RTA>show ip route<br />

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP<br />

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area<br />

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2<br />

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP<br />

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter<br />

area<br />

* - c<strong>and</strong>idate default, U - per-user static route, o - ODR<br />

P - periodic downloaded static route<br />

Gateway of last resort is 209.165.201.1 to network 0.0.0.0<br />

209.165.201.0/30 is subnetted, 1 subnets<br />

C 209.165.201.0 is directly connected, Serial1/0<br />

192.168.1.0/24 is variably subnetted, 6 subnets, 2 masks

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

Saved successfully!

Ooh no, something went wrong!