- 积分
- 0
- 鸿鹄币
- 个
- 好评度
- 点
- 精华
- 注册时间
- 2010-9-23
- 最后登录
- 1970-1-1
- 阅读权限
- 0
- 听众
- 收听
游客
|
9 _ i9 m1 D/ u5 Z1 TROUBLE TICKET 1" B" f7 p/ L# ?4 J0 S/ x
R21 should be keeping permanent Flexible NetFlow statistics but is not. Configure R21 such that NetFlow information does not time out on the router.
: B2 |, O; y/ l/ D8 _
/ z* I/ [ y4 p A+ S$ y
7 B9 J4 x& @& v4 T2 A* U5 h* x- {6 ^# c4 o- {2 j1 K- `% ? ~
2 TROUBLE TICKET 2* b5 s; U7 @' D: l% o+ d$ m
R23 is configured with an SLA monitor which periodically pings the 1.1.1.1 host at the far end of the VPN. The SLA probe is returning status Determine why The SLA probe is failing and correct the issue.
: L/ l. u3 Q/ g8 ]. a
P5 T' Y$ w! C9 ~
) y1 S/ M3 ^ X7 i! F0 G$ S/ }+ e4 H) v+ X
3 TROUBLE TICKET 3% ?3 m# H1 M6 B0 ]3 ?3 G3 r
R20 adjacency tables are not populating. Determine the cause and correct the issue.% [ j6 x* V' F5 P
" c* c: I! m' r" N
7 E6 G6 F& V0 f8 q
8 {4 n& Y1 p8 [; u
4 TROUBLE TICKET 4, j$ I& B# L, e& l* v6 F6 f
R29 should be installing a default route received via the area 0 CE. R30 should also see this default route. Determine where the problem lines and correct the issue such that R29 and R30 receive a default route where the ultimate gateway of last resort is via 19168.218.21.' _+ i& d7 F' A/ Z# z( g
5 S& S4 r6 M5 p0 M! t V* o% q
0 ?9 F% e: H" E+ N7 F% Z: W- [$ g" Q
5 TROUBLE TICKET 5
4 i0 |, @ |6 RR1 should be seeing OSPF neighbors with hostnames not IP addresses. Modify R1 so that it will see hostnames for show ip ospf neighbor output.( U, t, s" @/ F5 T( H
K& ]4 A, I' A3 K4 R1 K: D# Y3 R- W4 S9 ~, d9 g t, H9 O+ C9 i
$ E" O( r( I& T3 B2 {' F# C' k
6 TROUBLE TICKET 6; _9 w2 j% l3 ~& k) [" l
R10 and R11 are not seeing routes for the R21-R28 network or for the VPN host 1.1.1.1. Determine the cause and correct the issue.+ S J |% Q& Q. M& U. i
: C- F* x" U# ~& q$ I
. j5 \8 v: x" l0 _6 c+ m6 A+ x, h- @& g7 i9 A9 @
7 TROUBLE TICKET 7. _/ C5 n! q3 Y0 N8 d, O2 H
R14 cannot ping 99.99.99.17. Determine the cause and correct the issue.+ V P7 W; F1 g3 }5 B) p) r
* i( n- o: R) Q/ d V" c3 K- M: J1 W
: x+ K5 J6 \5 v: p7 Q% i% K8 TROUBLE TICKET 8# X; S$ L1 u5 b! H; g1 g
Traffic sourced from the 19168.48.0/24 network to 99.99.99.1 (R1) should move only through R2 and never R3. A traceroute from R8 indicates that this is not currently true. Find the issue and correct it.8 E7 s, v; y, g7 l! e3 O4 b
' l' C$ _1 R- u8 }( T5 W! T
# d) H6 w: B% r2 a! a* V+ e
( s. `1 {. w! i1 [4 r9 TROUBLE TICKET 9% c: h' h7 i- I! D4 f2 T
R26 should be seeing two equal cost paths to 19168.227.0/24. Determine the reason it does not and configure R23/R24/R25/R26/R27 as needed to address this issue. Do not modify any global configurations.
) Q$ X: ?% C- {- Z
7 a9 B2 J5 N1 ^' L5 q' q
- j. }( W7 w/ z
; Y0 d4 E4 z4 x, d10 TROUBLE TICKET 10 W' _1 [$ \4 G' X8 j% r
R30 should be able ping and traceroute to 2001:2:2:2::1 (configured on R28) but can not. Determine the reason and configure as needed to rectify. Note that the Frame Relay network between R28 and R29 must be an IPv4-only network.
" ~! \' {& u/ y2 c% U
1 H; e! K- E. O `- V6 g
) f7 d0 }+ O5 M9 U# w; A( ` |
|