The network administrator has found the following problem.
The remote networks 172.16.10.0, 172.16.20.0, and 172.16.30.0 are accessed through the
Central router’s serial 0/0 interface. No users are able to access 172.16.20.0. After reviewing the
command output shown in the graphic, what is the most likely cause of the problem?
A.
no gateway of last resort on Central
B.
Central router’s not receiving 172.16.20.0 update
C.
incorrect static route for 172.16.20.0
D.
172.16.20.0 not located in Central’s routing table
Explanation:
Explanation :
From the above CLI output we can figure out the topology.
http://lh3.ggpht.com/-sOTjdc5Hm_c/Uh0tupJrBpI/AAAAAAAAAes/YTIlZDuBYWI/3_thumb%25255B2%25255D.jpg?imgmax=800
Also check the configuration error in Exhibit.
http://lh5.ggpht.com/-tC0JlEv9S3A/Uh0txVceAzI/AAAAAAAAAe8/Kby4LNVVA60/74_2_thumb%25255B2%25255D.jpg?imgmax=800
If we use 172.16.20.0 to route to 172.16.150.15, then the packet will route back. To clear this error we have to use #no ip route 172.16.20.0 255.255.255.0 172.16.150.15 command in configuration mode.
0
0
users are able to access 172.16.20.0, so most likely incorrect static IP route for it
0
0