 成长值: 57280
|
After adding RTR_2 router, no routing updates are being exchanged between RTR_1 and the new location. All other inter connectivity and internet access for the existing locations of the company are working properly.5 I L& X4 \1 X" K
The task is to identify the fault(s) and correct the router configuration to provide full connectivity between the routers.3 ~. ~9 @+ J" [7 a J
Access to the router CLI can be gained by clicking on the appropriate host.
5 s4 L7 Y1 I' G, h' gAll passwords on all routers are cisco ." `( O" x' P/ x' s
IP addresses are listed in the chart below.% }/ z2 G% h; U( l9 [
RTR_A#show run+ _8 T7 b1 d, z. D% \. U
!" b8 p9 a7 K! T# s v# e7 [
!" B3 j& y% M9 ]) \" [0 Z0 s
interface FastEthernet0/0% \# q3 Y: v$ ]9 L1 ~
ip address 192.168.60.97 255.255.255.240
! \$ j6 o0 @0 A9 `% Y; l!, A0 ?; V) B: l( D
interface FastEthernet0/11 r- t! n' X& @. p& h
ip address 192.168.60.113 255.255.255.240; H$ x e! `/ x
!: q2 H# t2 M9 F' l! s
interface Serial0/02 t" W- D0 @0 W5 ]( }& r: I% L+ Q: c& G
ip address 192.168.36.14 255.255.255.252
. h6 F) r) H: N& U( |+ Sclockrate 64000
6 r) }0 o( z3 l!
9 C7 }# k* c( i' p1 a
* }4 J4 W0 K& Q3 H# f% s: ]3 ?" Frouter eigrp 212
# y9 F D% x/ x- ^" ^network 192.168.36.0. O1 S ?1 w) y# b
network 192.168.60.0* i* N8 X3 M; U" \9 x0 e* N+ L
no auto-summary1 r, @2 O b# N4 ~, N
!- j3 I/ S$ X9 w
8 ~/ k6 g& b$ n( T
RTR_A#show ip route9 y3 x2 B2 j# ]( {
192.168.36.0/30 is subnetted, 1 subnets& T% }) Q; ]! S: Z
C 192.168.36.12 is directly connected, Serial 0/0; G( x$ c" F/ d. d* M& k$ n2 b
192.168.60.0/24 is variably subnetted, 5 subnets, 2 masks& ?% r* s( o4 U- U
C 192.168.60.96/28 is directly connected, FastEthernet0/0
9 S7 q6 D3 \# b/ i+ XC 192.168.60.112/28 is directly connected, FastEthernet0/1
6 R4 L& A6 W* j U) Y6 A, C* qD 192.168.60.128/28 [ 90/21026560 ] via 192.168.36.13, 00:00:57, Serial 0/0
& D/ p/ ?4 z3 K; J0 U0 M. `' SD 192.168.60.144/28 [ 90/21026560 ] via 192.168.36.13, 00:00:57, Serial 0/00 F# ^) V' S9 j& X& `6 e
D 192.168.60.24/30 [ 90/21026560 ] via 192.168.36.13, 00:00:57, Serial 0/0) L; j/ @$ H6 c) @7 Y+ ~* R6 U
D* 198.0.18.0 [ 90/21026560 ] via 192.168.36.13, 00:00:57, Serial 0/0
- R4 a" `5 |1 t. _* Z# D
, ?! M- L6 @- M, |********************************************************************************
) D. L+ R- d, L4 G% y# K8 V
- G5 n/ K* E( k2 K( }) m" vRTR_2#show run
& N+ m' ~/ u0 \! S! G4 ?% ^!# G/ h( ?0 E0 @" o
!3 }5 [" ~6 o- _; c& s
interface FastEthernet0/0
% o# d' K& @1 z+ j. \# Iip address 192.168.77.34 255.255.255.2520 d5 u/ O+ w7 N/ z# y
!
M1 U! r: }; g9 g; l% Minterface FastEthernet0/1
" E R+ v$ \" ~. `' H* Iip address 192.168.60.65 255.255.255.240
+ [" y% T/ U l/ Q# [9 a) \!
, t7 ~: V6 q6 V5 O& T, j6 ninterface FastEthernet1/0
- e9 K* a( L5 f6 w9 zip address 192.168.60.81 255.255.255.240 q I" C1 r" T/ p( a6 B* \
!
$ l+ C9 K* J7 H ~8 \( k7 _, l- D!+ Y+ P) Q" Z4 W* r& {# I" w9 M9 ^
3 v' n$ {2 R- T( B$ a
router eigrp 22
5 Z( Q$ i% s% T+ f/ fnetwork 192.168.77.0
; A7 u/ y/ Y# r* Wnetwork 192.168.60.0
- ? H/ f; f8 a# @ n& |+ Yno auto-summary
/ {" G/ s* _. D }# {2 b$ M1 X!
4 e( ?% o6 M! V: e) D3 \
O& _+ Y# ^1 KRTR_2#show ip route
: D0 P8 p. p' l C5 m192.168.60.0/28 is variably subnetted, 2 subnets( n5 Z! A3 N2 C3 V
C 192.168.60.80 is directly connected, FastEthernet1/06 N8 ^* S" c( q% L5 ^
C 192.168.60.64 is directly connected, FastEthernet0/1
% b7 B7 j5 j f; j8 {& K8 ^192.168.77.0/30 is subnetted, 1 subnets
% A2 }6 |. Z# s1 EC 192.168.77.32 is directly connected, FastEthernet0/0
3 v; @3 D$ E" m$ ^" _% K# k4 {) u4 [& I* A# V
**********************************************************
" v O1 F& J# a3 @! {2 j4 A: T4 J6 ~- q, y# q
RTR_B#show run
8 u+ }7 L( b7 S. m3 A. u!
& f7 Q9 @; I8 n# L/ z1 M- uinterface FastEthernet0/0$ r' [0 h, J+ k1 U# e$ F* w; G
ip address 192.168.60.129 255.255.255.240# F. X3 \, p1 P! |- t4 _
!- z" g% N# X" l" g5 p
interface FastEthernet0/1
) G% ~3 X( m( {% H1 ?. Bip address 192.168.60.145 255.255.255.240 e5 e2 \6 d( B7 l3 m/ l; t2 b2 R
!7 N' I' A ~- Y; D
interface Serial0/1; s, K4 Y |& j4 G
ip address 192.168.60.26 255.255.255.252
4 `2 v- n& h' c5 m: L/ }3 a, p" r7 k7 R" i7 b& R
!: _$ S. y! I' p8 Z
2 ?5 ]# B& ]6 p, ?- L$ Grouter eigrp 212
/ J, f7 b! L+ b: Xnetwork 192.168.60.0
6 x( t) u/ J" |' t!
1 f3 \; y( t# ?; S
' g$ G+ F: \$ qRTR_B#show ip route
* x, K. F; Y) v5 N! H+ t192.168.60.0/24 is variably subnetted, 5 subnets, 2 masks5 e2 d5 O7 H* c' I# _
C 192.168.60.24/30 is directly connected, Serial0/1" d2 r' n' q7 @
C 192.168.60.128/28 is directly connected, FastEthernet0/0; Z2 N+ O2 u8 u- o" ]% w
C 192.168.60.144/28 is directly connected, FastEthernet0/1
/ u" |2 E# C# V# HD 192.168.60.96/28 [ 90/21026560 ] via 192.168.60.25, 00:00:57, Serial 0/1
- |1 M1 \ D4 |. }7 P5 lD 192.168.60.112/28 [ 90/21026560 ] via 192.168.60.25, 00:00:57, Serial 0/1! c8 J* M: c* D. _
192.168.36.0/30 is subnetted, 1 subnets
& n+ M' }4 |: B2 ?4 j; RD 192.168.36.12 [ 90/21026560 ] via 192.168.60.25, 00:00:57, Serial 0/1
1 J4 G; ~# b6 |' ^9 {D* 198.0.18.0 [ 90/21026560 ] via 192.168.60.25, 00:00:57, Serial 0/1
- g1 ~; ^% m# ~( p' ^' P# M% X. H* `, B9 H; ]
**************************************************************************6 U6 J1 |8 ]/ ^% y( g7 Y* o3 i
: V' U1 Q% i4 z* ~
1 a: R0 a! i7 d) I/ a
RTR_1#show run
U5 X* |1 G9 U0 t!2 V3 z- P. g7 G. g
!
) [& @$ U: Q. m& B9 Q" dinterface FastEthernet0/0
! S' Y& q$ L. }0 r7 H* z Qip address 192.168.77.33 255.255.255.252% I5 p+ {+ Z3 I3 m
!
- N7 }3 M% G4 C9 N2 vinterface Serial1/0' h) r$ j9 z% l" I& [ y! V
ip address 198.0.18.6 255.255.255.0
$ s/ \9 v' M' Q6 j6 Z0 u3 p!
3 k9 V% P6 k! T9 d; n( C!, Q% r& @: S: c6 ^$ L
interface Serial0/0
6 G( T Q ~/ P& d; q. Tip address 192.168.36.13 255.255.255.2520 {0 G3 w# `1 k+ j( w
clockrate 64000: ^& C! e! D A4 x+ O
!; |% R& k( {5 W1 E+ D+ g+ z) C( l$ Y
interface Serial0/1
Q) @+ H( J7 I* D+ lip address 192.168.60.25 255.255.255.252
7 ^$ ^: C! D, Uclockrate 64000
; [; k1 F/ W- ?8 `, e/ L& Z( F!2 b. N4 ?4 D2 z$ _! W
!7 j! B! |" b! h* ~
/ f- K2 u% G8 _3 {+ Z3 O, J: y& r
router eigrp 2121 @2 b: [6 D, e n- X: _
network 192.168.36.09 g' @0 n* T; Z- W, x9 X/ E; c
network 192.168.60.05 m+ |8 [/ ^5 i, e# g
network 192.168.85.0; X) G! x4 t! }, A6 v
network 198.0.18.09 ]1 i& l/ x: S; m0 Q C3 h G
no auto-summary
6 [8 A; o+ W% A! 3 b6 F$ ~. b( F( D5 z" x1 C4 N% k3 K
ip classless# [7 c! Y& q C% Q7 V' ^
ip default-network 198.0.18.0
G* M6 H7 q" C9 H% Cip route 0.0.0.0 0.0.0.0 198.0.18.5. t3 D& B' x. W$ V H, p, {
ip http server
4 I: N( f* ^! H1 I+ Y2 q9 N* Y! O M8 e) v u5 R! C r; q
RTR_1#show ip route8 r+ i2 {7 u' K
192.168.36.0/30 is subnetted, 1 subnets) {8 O) P0 _4 l- w! P" q
C 192.168.36.12 is directly connected, Serial 0/0
: Q; _9 q6 {) g! ~* {) q8 b192.168.60.0/24 is variably subnetted, 5 subnets, 2 masks
7 l' V5 i8 ]2 C( K1 |& G5 PC 192.168.60.24/30 is directly connected, Serial0/13 G7 ~4 L2 g0 l
3 @) f! t0 o9 _5 W0 zD 192.168.60.128/28 [ 90/21026560 ] via 192.168.60.26, 00:00:57, Serial 0/1' s0 K* x* C! I
D 192.168.60.144/28 [ 90/21026560 ] via 192.168.60.26, 00:00:57, Serial 0/1 * N; J) `+ C* \7 I# N1 O, s
D 192.168.60.96/28 [ 90/21026560 ] via 192.168.36.14, 00:00:57, Serial 0/0- G/ r4 O, C3 U8 y2 I, r0 r/ E3 c
192.168.77.0/30 is subnetted, 1 subnets9 {. r0 i4 b. C0 m9 f
C 192.168.77.32 is directly connected, FastEthernet0/0; K4 u0 a2 ?0 H4 V
C 192.0.18.0/24 is directly connected, Serial 1/00 ]+ C7 N( O$ l& n; X
*S 0.0.0.0 via 198.0.18.5' z: \* j, D( d# N4 t8 @
. i" v' l# @ B) H4 j0 o( EExplanation:
- N1 |$ R2 b4 m7 g, }Step1:
0 t( t+ B( X) [2 g) x% |0 BIdentify the faults in configuration on RTR_1 and RTR_2. As the SIM specifies all other inter connectivity and internet access for the existing locations of the company are working properly.
& ?( k2 c$ |9 \
, S; z3 u5 }1 V' FRouting Protocols used in the SIM is EIGRP with AS 212 as provided by exhibit.' I) Y0 w& K, u6 M/ \3 m
Faults Identified:
" {* G* b; A+ t, z3 X' ?( l; v% a6 X
2 m$ K. O3 |7 C B# Q1 j
4 r# a8 ?# p" w1 ~& ` I2 j g8 `/ R v) t% P; ~0 M
- Wrong AS (EIGRP 22) provided at RTR_2 (New router)
- RTR_1 does not advertise the new network between RTR_1 and RTR_2 into EIGRP.
We need to correct the above two configuration mistakes to have full connectivity
' k8 I: @' D$ X# K9 c Y, YStep2: Correcting the EIGRP AS to 212
7 M" }3 R/ Q+ [2 \* q" D! `" YWrong AS (EIGRP 22) provided at RTR_2 (New router)
* z7 p' \! J ]% GAll routers that want to exchange routes within EIGRP needs to be in same Autonomous System.
+ m0 M8 Z7 f3 o# R6 m
_" P- ^1 y0 W& `1 p3 o
8 s1 n/ S( n- JStep 2.1:4 q* S9 W: d* I9 F7 }8 P0 @6 e! ?7 p
First we need to remove the current wrong EIGRP AS 22 from Router RTR_2( A. K2 g3 Q! d
Click on Host-F to get CLI of( Y5 H( x! `* K0 S" |) r) S. i
RTR_23 a7 m4 c% N; b |! z+ k
9 h. z( V: i5 u9 ~RTR_2>enable
. C0 w# f) i/ [ BPassword : cisco
2 F3 \' h/ J' l2 k' `" h/ |(Provided by SIM Q )8 Q; {+ r& a8 r/ t# N7 \
RTR_2#conf t
# M, K9 m N+ G( yRTR_2(conf)#
; L o# G6 D) X8 ]Step 2.2:1 V% `' C0 R7 ]. e8 w
Removing the wrong EIGRP routing process with AS 225 N7 N1 F! W% I' N
RTR_2(conf)#no router eigrp 22# _* D& }) s: i8 M& k
The above statement removes all the EIGRP configuration configured for AS 22 .3 D: M: ?4 X9 k+ `7 R
; L' Y: z( ]% z4 k
+ A S* t0 ?9 k0 AStep 2.3:# b- u6 f% l2 y1 X" n
Adding the correct EIGRP configuration0 w* X! i' f# W, p
Start the EIGRP routing process with AS 212+ ~2 n+ K) c. j
RTR_2(conf)#router eigrp 212
( W" o& P* w6 P4 r" fStep 2.4:
8 I3 d. O+ P& c$ V9 Z. M& nAdvertise the directly connected networks into EIGRP on RTR_2
7 [' F' M" K8 P1 N( g/ B, @& q. ^
Fa 0/0 - 192.168.77.34# x/ V; r& P& v" g7 h0 G0 y' {
Fa 1/0 - 192.168.60.81/ S8 } i3 D* @9 m
Fa 0/1 - 192.168.60.651 P `: I6 z2 Z2 D0 r7 A* J
. c# D C# P. L: o f& MRTR_2(config-router)#network 192.168.60.0, \' i1 T- L8 n+ [& l8 n
RTR_2(config-router)#network 192.168.77.0
' [4 @5 Z+ p. p) wRTR_2(config-router)#no auto-summary
2 z7 O5 Q/ H7 j/ }1 I4 x5 ^RTR_2(config-router)#end1 {) S6 G, M. L! c, \
! ?% U4 p: ], e
Step 2.5:- D5 C: J4 Q/ b$ K- W& @
' |$ a# O" Q& BImportant save the changes made to router RTR_2
- w' m3 D0 t8 e# Y+ p3 V7 T4 ~RTR_2#copy run start' ~$ R. j, X* q/ n7 o9 i% b& h. D
: E1 f8 _# _/ ^! s: ]
Step 3:; C" ~+ L; Q' s+ ?# L
\5 ~ M, R# P+ z
E$ t# g+ @1 h! r0 a0 H* o4 E
4 u# j- b5 Q- b! A" s" `4 a5 Z' l" ^$ f) l) R- W* L A
RTR_1 does not advertise the new network between RTR_1 and RTR_2 into EIGRP.7 V2 @1 m( B- B
Click on Host-G to get CLI of
: Z9 _% P& e. X; i: \. qRTR_1* ?6 T8 l9 r- W$ W1 _: X: o7 z
The network
& j6 \2 f% H* R3 q192.168.77.0 is used between RTR_1 Fa0/0, S4 @+ W- r" e- V4 t
- RTR_2 Fa 0/0
# Y; S1 w. M$ L; E; S3 A. EThis network needs to be advertise into EIGRP routing process at RTR_14 Y% l" _$ z1 G" O
RTR_1>enable G" Z7 f4 O9 {$ I5 ~+ Q A
Password : cisco
% d, q7 r4 o8 f$ I# G" \# Y* }, [(Provided by SIM Q ). _# T5 [/ w l# z2 F0 F, J0 w
RTR_1#conf t
8 A/ v y2 W9 w' H+ h. {2 [RTR_1(conf)#
) M M. G6 y) C, A5 w/ v$ Y* h) `Step 3.1:5 h9 Q( B, b4 ?" H& j) @
Enter EIGRP routing process for AS 212
/ ?+ ?6 [% _7 I. X' XRTR_1(conf)#router eigrp 212$ B" ?( ]1 U4 n5 H- m' d8 d
3 j' ] g/ U( `, ]4 @8 r4 e/ p
Step 3.2:
; H- K3 Y* C8 S/ _) a) `+ [' R3 wThe network: w- d; P3 Y2 `/ a9 P6 e9 H& ~; m
192.168.77.0
+ F9 T2 o: |. ^$ ~- L! qis used between RTR_1 Fa0/0
* f0 Z1 S5 K4 q# O& Y/ }- RTR_2 Fa 0/0 . Advertise this network into EIGRP
3 k2 i( F5 e3 p7 {8 `RTR_1(config-router)#network 192.168.77.0
$ {+ U: {1 _. {RTR_1(config-router)#end; u Q$ ]# p' T1 T) e: Z2 t
7 e2 D2 d# ?, `- oStep 3.3:
3 f6 x4 B9 Q, Z" Q9 BImportant save the changes made to router RTR_1: x& p9 ]% k5 ^6 ~' v
RTR_1#copy run start ?; w2 n% L! u: V
( T) T7 n( l6 T* j Q A8 {" r* X S+ X. R0 b; p
Verification:% _/ Q* w5 D* M0 E% b
, Y+ q. y& u7 {; g! d$ b! r z8 m
From RTR_2 CLI( G4 B3 ^ k1 s9 u2 z
ping RTR_1 Serial 1/0 IP address 198.0.18.6
* O* h, y) ?3 F# dRTR_2#ping 198.0.18.6
: q$ Z5 T- {* N' {. m$ V5 }* M!!!!!2 K! q" s4 I" Q$ X5 v1 E
A successful ping shows the new RTR_2 will have full connectivity with other routers.4 F# Q% ^$ z5 B: ?0 |
) O+ j1 y' P; j! M! t6 x& q& w3 sAny Questions are welcomed!!!!! |
|
简体中文
英语
日语
韩语
法语
西班牙语
越南语
泰语
阿拉伯语
俄语
葡萄牙语
德语
意大利语
希腊语
荷兰语
波兰语
保加利亚语
爱沙尼亚语
丹麦语
芬兰语
捷克语
罗马尼亚语
斯洛文尼亚语
瑞典语
匈牙利语
繁体中文
文言文
发表于 2009-4-23 12:17:13
$ p8 ^3 \$ F& ]& @& ~- ]0 g
置顶卡
喧嚣卡
变色卡
千斤顶
