CCIE R&S v5 Exam Review on 13 October2015
1. access-list on sw1 was blocking user traffic and i removed that access list and then only i can get desired output. mac address was configured incorrectly in sw2
2. frame relay encap was there and i removed that one and configured ppp. later i asked one of ccie candiate and he told me that there is no need to remove frame relay and just configured ppp and then tunnel came up.
3. r22 ospf router-id was wrong.
4. passive interface on r13
5. mpls was not enable on eth 0/0 connecting to r4 and r6 which is breaking connectivity. on r6 change metric value to prefer path for 220.127.116.11 via R6.
6. r22 and r25 is not making neighborship and there is access-list on r22 and you can modify that one. Instead point to next hop ipv6 add on ipv4 and then can ping .
7. there is wrong network advertisement on r17 and you can verify with R18 and r19 and one you fix R17 neighborship come up.
8. you have to check ip nat ins/out on r7 and r8 and check bgp neighborship also. on sw3, advertise network on ospf same as sw4 and then you get ip on pc105.
in this section we have to do 2 traceroute and im able to get traceroute 18.104.22.168 from pc107 but i have to trace 172.16.200.200 ( may be im wrong but have to trace something like this ) from pc105 and couldnt get desired output.
9. everything looks good but couldnt resolve.
may be access list on R21
10. ip http port 8008 missing on nas and fix nat statement for this on R23.
1. i couldnt remember exactly but choose sw3, ask for vtp password like that.
2. i choose r15 and then exclude tun 0 from eigrp config
there is redistribute connected on eigrp config
3. this question is same as in certcollection shared section and for your reference
The idea is, when Host 1 issues pings to Internet, it gets sent to R1.
R1 looks uo the destination IP address in RIB.
It finds E0/3 (connecting to R3) as exit interface.
It changes the source Private IP to NAT/PAT IP.
It forwards ICMP echo requests to R3.
R3 looks up its table and send to Internet.
Internet replies back to host 1 via R2.
R2 sends reply to R1 via interface E0/2.
R1 looks up reverse path in RIB as per uRPF rules.
R1 finds source being learnt via E0/3 (connecting to R3) ? It drops the reply.