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.

We can see routes 161.20.2.0, 161.20.3.0, and 161.20.4.0 are directly connected<br />

with 161.20.5.0 being learned over the serial line but the 161.20.1.0 network is<br />

not listed because it was summarized. Likewise we similar things on Optik:<br />

optik#sh 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, * - candidate default<br />

U - per-user static route, o - ODR<br />

Gateway of last resort is not set<br />

C<br />

C<br />

C<br />

R<br />

161.20.0.0/16 is variably subnetted, 4 subnets, 2 masks<br />

161.20.5.0/30 is directly connected, Loopback0<br />

161.20.4.0/30 is directly connected, Serial0/1<br />

161.20.1.0/24 is directly connected, Ethernet0/0<br />

161.20.3.0/30 [120/1] via 161.20.4.1, 00:00:06, Serial0/1<br />

3. Let’s also see what is happening with RIP. Turn on debug ip rip on both routers to<br />

view the updates sent and received. You should see on Phiber:<br />

phiber#debug ip rip<br />

RIP protocol debugging is on<br />

phiber#<br />

01:26:15: RIP: received v1 update from 161.20.4.2 on Serial0/0<br />

01:26:15: 161.20.5.0 in 1 hops<br />

01:26:19: RIP:sending v1 update to 255.255.255.255 via Ethernet0/0 (161.20.2.1)<br />

- suppressing null update<br />

01:26:19: RIP: sending v1 update to 255.255.255.255 via Serial0/0 (161.20.4.1)<br />

01:26:19: subnet 161.20.3.0, metric 1<br />

01:26:19: RIP: sending v1 update to 255.255.255.255 via Loopback0 (161.20.3.1)<br />

01:26:19: subnet 161.20.5.0, metric 2<br />

01:26:19: subnet 161.20.4.0, metric 1<br />

01:26:41: RIP: received v1 update from 161.20.4.2 on Serial0/0<br />

01:26:41: 161.20.5.0 in 1 hops<br />

01:26:49: RIP: sending v1 update to 255.255.255.255 via Ethernet0/0<br />

(161.20.2.1) - suppressing null update<br />

01:26:49: RIP: sending v1 update to 255.255.255.255 via Serial0/0 (161.20.4.1)<br />

01:26:49: subnet 161.20.3.0, metric 1<br />

01:26:49: RIP: sending v1 update to 255.255.255.255 via Loopback0 (161.20.3.1)<br />

01:26:49: subnet 161.20.5.0, metric 2<br />

phiber#undebug ip rip<br />

RIP protocol debugging is off<br />

212

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

Saved successfully!

Ooh no, something went wrong!