On which device is the fault condition located?

Ticket 3 R1ACL

TROUBLE TICKET STATEMENT:

The implementation group has been using the test bed to do a ‘proof-of-concept’ that required both client 1 and client 2 to access the Web Server at 209.65.200.241. After several changed to interface status, network addressing, routing schemes and layer 2 connectivity, at trouble ticket has been opened indicating that client 1 cannot ping the 209.65.200.241 (internet Server).

The following information needs yourself show run:

Client 1 is not able to reach the WebServer at 209.65.200.241. Initial

troubleshooting shows that R1 is also

not able to reach the WebServer. R1 also does not have any active BGP

neighbor.

Configuration on R1

!

interface Serial0/0/0/1

description link to ISP

ip address 209.65.200.224 255.255.255.252

ip access-group edge_security in

ip nat outside

ip virtual-reassembly

ntp brasdcast client

net broadcast key 1

no cdp enable

!

!

ip access-list nat_traffic permit 10.1.0.0 0.0.255.255

ip access-list nat_traffic permit 10.2.0.0 0.0.255.255

!

ip access-list edge_security deny ip 10.0.0.0 0.255.255.255 any

ip access-list edge_security deny ip 172.16.0.0 0.15.255.255 any

ip access-list edge_security deny ip 192.168.0.0 0.0.255.255 any

ip access-list edge_security deny ip 127.0.0.0 0.255.255.255 any

ip access-list edge_security permit ip host 209.65.200.241 any

On which device is the fault condition located?
A . R1
B . R2
C . R3
D . R4
E . DSW1
F . DSW2
G . ASW1

View Answer

Answer: A

Explanation:

Since we know that R1 does not have any BGP neighbors, we can deduce that the problem lies with R1.