CCNP TSHOOT - Ticket 2

Lab topology will be the same as in Ticket 1.

You can also download complete topology file from Cisco website in PDF file. Check here https://learningnetwork.cisco.com/servlet/JiveServlet/download/52366-8599/TSHOOT%20Exam%20Topology.pdf

For demo exam, check out in http://www.cisco.com/web/learning/le3/le2/le37/le10/tshoot_demo.html

After wait for 2 minutes, check whether client1 get IP address or not.


Client1#sh ip int brief
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            10.2.1.3        YES DHCP   up                    up
FastEthernet0/1            unassigned      YES NVRAM  administratively down down

Client 1 is getting IP address from DHCP server R4. So, let's ping to 10.1.1.1 as usual.


Client1#ping 10.1.1.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
!!!!!

Success. Client1 can ping to 10.1.1.1 all the way up to R1.

Let's ping one interface after another steps by steps as follow.

Client1#ping 209.65.200.225

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 209.65.200.225, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 56/92/112 ms

Client1#ping 209.65.200.226

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 209.65.200.226, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 208/228/248 ms

Client1#ping 209.65.200.241

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 209.65.200.241, timeout is 2 seconds:

U.U.U

Success rate is 0 percent (0/5)

Ping success up to 209.65.200.224 network and failed only in 209.65.200.240 network.

So, it's clear that two possible case;

- BGP neighbour relationship (or)

- IP access list

Let's check in R1's BGP and IP access-list

Check R1's BGP neighbour as follow.

R1#sh ip bgp summary

BGP router identifier 1.1.1.1, local AS number 65001

BGP table version is 2, main routing table version 2

1 network entries using 117 bytes of memory

1 path entries using 52 bytes of memory

2/1 BGP path/bestpath attribute entries using 248 bytes of memory

0 BGP route-map cache entries using 0 bytes of memory

0 BGP filter-list cache entries using 0 bytes of memory

BGP using 417 total bytes of memory

BGP activity 1/0 prefixes, 1/0 paths, scan interval 60 secs

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd

209.56.200.226  4 65002       0       0        0    0    0 never    Idle

Neighbour is idle and haven't received any message to and from.

Let's check neighbour configuration as follow in R1.

R1#sh run | include neighbor

 bgp log-neighbor-changes

 neighbor 209.56.200.226 remote-as 65002

Here is the problem. Actual neighbour IP address of next BGP router should be 209.65.200.226.

Let's fix it and it will worked. 

So, the problem lies in R1, topology error is in BGP and fixed by changing the IP address of neighbour to 209.65.200.226.