Skip to main content

Posts

Showing posts with the label CCNA RIP Route

The network administrator needs to address seven LANs.

The network administrator needs to address seven LANs. RIP version 1 is the only routing protocol in use on the network and subnet-zero is not being used. What is the maximum number of usable IP addresses that can be supported on each LAN if the organization is using one class C address block? A. 6 B. 8 C. 14 D. 16 E. 30 F. 32 Answer : E Explaination: We need 7 LANs also subnet-zero (1st subnet must be not be included). So we need 7 subnets, then the appropriate mask will be 255.255.255.224. For example: assume that our IP address will be on 192.168.100.0 network. Then the subnet would be 192.168.100.0 192.168.100.32 192.168.100.64 192.168.100.96 192.168.100.128 192.168.100.160 192.168.100.192 192.168.100.224 For each subnet it will have 30 usable ip addresses. Refer to the question, the below is the topology of the network 7 network

What is the most likely cause of the problem?

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 Answer : C Explanation : From the above CLI output we can figure out the topology. Also check the configuration error in Exhibit. 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.