Figure 631 The routing table of RTA in Figure 632

DTAJUghgnM ip rnutr:

Cü[|£!í: L tuniiétrad, Li staticj t kíIíH. ü ¡íí?, tí mobile, u íscíf'

ü EIGBPj L> ■ E1GRP external, í> 0SP1 , ia OSPí Inter area iti osfi ffhsa external type i, 1« oy-pi nsha external tysie 2

E1 OSPI t-xtí-rnaL íyfni 1, 12 ÍÍSPl' ïxT Ci'riil 1 tyfïC 2, L t(iP

1 is L1 es iflvoJ 1, L2 es IS lwol 2. * candidate df-fault

Gateway of last resort ís nt: set ia.û.a,fl/24 is subnettetf, ! subnets C lí.1.1.0 Is directly connected, Sanan i 102.160.1.9/2-1 |1(wy8676| via 172.17.16.56 , 00:68:36, Ethernet«

I 192,16ft.2.0/24 I1W/12WI vis 172.17,10.56, W:e0;ïB. Ethorn&tB

: 1FI2.1Gñ.S.fí,'2J, vía 17^.^.17.9, M JOB: 13, Snn.llB

17Z. Kj.a.WJU is SubnetLéd, 1 SutariEtS

C 112. i ti _ ■: /.tí lí directly connected, Seríale

172.17.a.8/28 lü subnetldc . i s^miLí <; 172,17.16,-IS is directly connect«], Ethernets

'ATAD

Figure 6.32. The internetwork for Troubleshooting Exercise 1.

Figure 6.32. The internetwork for Troubleshooting Exercise 1.

Figure 6.33. The IGRP updates sent and received by RTA in Figure 6.32.

■IIA^JcLiug ip igrp transactions iUFtf prr t ocol netiuqgjnQ is on RTA#

lijttH: received update fro.i 172.17.15,56 nm ltKernel ft network 192.16S.1.0, metric OG/ii (neighbor »570) network «trie (neighbor -law)

iurH: sending update to zss.255.255.255 via Ethernet® (172.17,16,55) network 10.0.0.0, metric 6476 network 192.168.3.0, i:ctrir, 12476 network 172.16.0.0, metric 6476 IGRP: sending update to 255.255,255.255 via Serial» (172.16.17,10) network 10,0.0.0, nniric ai7t network 132.168.1.0, metric 067,* network 102.iea.2.0r metric 120a network 172.17,0,0, metric HOG liittP; sending Update to 255.255.255.255 via Serial 1 (10.1.1.1) network 192.168,1.0, natric 6676 network 132,168.2.0, metric 1200 network 192.168.3.0, metric 12476 network 172.16.0-0, metric 6476 network 172.17.0.0, metric 1100 IGftP l received update iron 172.15.17,9 011 $erlal0

network 192,160,1.0, retnc 10476 (neighbor 6476) network 192.168.2.0, metric 1057G (neighbor G576) network 192.168,3.0, rctrn; 12476 (neighbor 10476)

Figure 6.34. The IGRP updates sent and received by RTB in Figure 6.32.

RTB#tfebuQ ip lgrp transactions IGRP protocol debugging is RTB#

IGRP: received update iron 172,17.to,on Ethernet® network 10.0,0,0, metric 8576 (neighbor 6476) network 192.168.3.0, metric 12570 (neiehbor 12476} network 172.16.0,0, inetric 8576 (neighbor 8476) IGRP: sendlno update to 255.255.255.255 via Ethernato (172.17.16.56) network 192.168.1.0, metric F357n network 102.168.2.0r metric 1100 IGRP: sending update to 255.255.255.255 via Ethernetl (192,166.2.1) network ia.e.o.a7 metric 8E76 nt;trk 172.16.0.0, metric 0576 network 172.17.0.0, metric 1100 IGRP; received update iron 132.168.2.2 on Ethernetl network 192,168,1,0, netric 8576 (neighbor 6476) network 192.168.3.0, metric B57& (neighbor 6476)

Figure 6.35. The IGRP updates sent and received by RTC in Figure 6.32.

RTC#d&Dufl m; tgrp transactions liiHP protocol debugging on

IGRP: serdirg update to 255,255.255.255 via Serial® (172.16.17.9} network 1D2. "G8.1.0, metric network 192.166.2,0, mplr-ir: !>57G network 192.168.3.0, metric ■ 10476 LORH: SCiidirg update to 255,255.255.255 via Seriall (192.168.1.5) iict-A-C310.0.0.0, metric 10-I7G network i72.i6H0.fflj «etric=e476 network 172.17.0.0, petric=8576 IGRP: received update i ront 172.16.17.10 on SerialB network 10.0.0.0, metric 10'17G (neighbor 8476) network 192.166.1,0, metric 19676 (fleighbor 8576) network 192.166.2.0, metric 6676 (neighbor 12B0) network 172.17.0.0, metric B576 (neighbor 110») IGftP: received jpealo from 192.100.1.6 on Seriall network 10,0.0,0, metric 10676 (neighbor 8676) network 192.166.2.0, metric 8576 (neighbor 11») network 192.166.3.0, molr-ic 1047(1 (neighbor B478) network 172.16.0.0, Rotnc 10G7G 0Q7C1

network I72.i7-0.0j oetric 8676 (neighbor 12B3)

Figure 6.36. The IGRP updates sent and received by RTD in Figure 6.32.

RTDKdetme iQ^P transactions igrp protocol debugging is on

RTDJK

:grp: received update froan 192.163.2.1 on Ethernet® network 10.0.0.0, metric 8G7G <Mi.'ii;rit!G057G} network 172.16.0.0, metric BG7G (neighbor 857G) network 172.17.0.0, aetrie 1200 (neighbor 110»; igrp: sending update to 255.256.255.255 via Ethernet0 {192.168.2.2) network 192.166.1.0, metric 647E network 192.166.3.0, metric 8476 igrp; sending upiJilTO to 255.255,255.255 Via Serial® {192. ibb. 1 .6) network 10.0.0.0, metric SG7G network 192.1GB.2.0, metric 1100 network 192.168.3.0, metric-fl476 network 172.16.0.0, metric b67g network 172.17.0.0, metric 1200 igrp; sending update to 255.255.255.255 via Seriall (192,168.3.1) network 10.0.0.0, me trie 8G7G network 192.168.1.0, metric-8476 network 192.168.2.0, metric 1100 network 172.16.0.0, metric BG7G network 172,17,0,0, metric 1200 ■grp: received update iron 192.168.1.5 on Serial®

network 18.0.0.0, metric 12476 (neighbor 104/8) network 172.16.0.0, metric 10478 (neighbor 3476) network 172.17.0.0, metric 1W575 (neighbor 3576)

Q: Users on subnets 172.16.1.8/29 and 172.16.2.16/29 in Figure 6.37 are reporting that they cannot connect to servers on sub net 172.17.1.8/29. Figures 6.38 through 6.41 show analyzer captures of the IGRP updates on the two Ethernet links. Part of the IP header is also shown in each screen. Determine which router originated each update and then find the problem.

Figure 6.37. The internetwork for Troubleshooting Exercise 2.

Figure 6.37. The internetwork for Troubleshooting Exercise 2.

FtTA PlTC

Figure 6.38. An analyzer capture of an 1GRP update from the internetwork in Figure 6.37.

Figure 6.38. An analyzer capture of an 1GRP update from the internetwork in Figure 6.37.

Figure 6.40. An analyzer capture of an 1GRP update from the internetwork in Figure 6.37.
0 0

Post a comment