In this post CCNP 642-832 TSHOOT TROUBLE TICKETS (TT) Questions, i have introduced the trouble tickets questions of 642-832 exam.
And you can reading it carefully, any questions then contact me.
Also, i have uploaded the topology. Lab-Sim Topology.pdf
Solution Guide:
Problem: Client 1 is able to ping 209.65.200.226 but can’t ping the Web Server 209.65.200.241.
Configuration on R1:
router bgp 65001
no synchronization
bgp log-neighbor-changes
network 209.65.200.224 mask 255.255.255.252
neighbor 209.56.200.226 remote-as 65002
no auto-summary
check bgp neighborship. **** show ip bgp sum****
The neighbor’s address in the neighbor command is wrong under router BGP. (use ipv4 Layer 3)
Answer: need change on router mode on R1 neighbor 209.65.200.226
Ans1) R1
Ans2) BGP
Ans3) delete the wrong neighbor statement and enter the correct neighbor address in the neighbor command (change “neighbor 209.56.200.226 remote-as 65002″ to “neighbor 209.65.200.226 remote-as 65002″)
———————————————–
Correction in problem statement:-
In the above ticket R1 and all others are able to ping 209.65.200.226 but not the Web Server only. This is because R1 is directly connected to 209.65.200.226 and BGP is not required in order to ping directly connected network and as soon as R1 knows about 209.65.200.224 network all other devices are also able to ping 209.65.200.226, since they are coming to R1 for any unknown route, because of default route propagate through R1′s OSPF (using ‘default-information originate always’ command). However Web Server is not accessible until BGP configured properly between R1 and ISP(209.65.200.226) because only then R1 will receive the information about Web Server’s network.
Following are the symptoms of above ticket:-
1- No one is able to ping Web Server.
2- Client 1 and all others can ping upto 209.65.200.226.
3- ‘sh ip route BGP’, you will not see any BGP route.
4- ‘sh ip bgp neighbor’ on R1, you will not see any active BGP neighbor.
