Refer to the exhibit. The exhibited network contains a mixture of Cisco and non-Cisco routers. The command debug ip rip was entered on the JAX router. All routers are running the same version of RIP. Router CHI and Router ORL are not able to reach the 192.168.1.16/28 network. What is a possible solution to this problem? | |
Enable split horizon in the network. | |
Configure RIPv2 on routers. | |
Add network 192.168.1.0 to the RIP configuration on the JAX router. | |
Configure JAX Fa0/0 as a passive interface. | |
Enable the Serial0/0/0 interface on the JAX router. | |
Change the IP address on the Fa0/0 interface of the JAX router to 192.168.1.1/24. | |
Refer to the exhibit. Routers East and West are configured using RIPv1. Both routers are sending updates about their directly connected routes. The East router can ping the West router serial interface and West can ping the serial interface of East. However, neither router has dynamically learned routes from the other. What is most likely the problem? |
A gateway of last resort is required. |
Subnetting is not supported by RIPv1. |
VLSM is not supported by RIPv1. |
One of the routers needs a clock rate on the serial interface. |
Refer to the exhibit. All routers are running RIP version 2. JAX is configured to just advertise the 10.0.0.0/24 network. CHI is configured to advertise the 172.16.0.0/16 network. A network administrator enters the commands shown in the exhibit. What changes will occur in this network? |
The JAX router will ignore updates for the 172.16.0.0/16 network due to split horizon issues. |
The CHI router will install a route to the 192.168.0.0/16 network in its routing table. |
The routing table for CHI will have the 192.168.0.0/16 route but it will have an S next to the route. |
The ORL router will apply a 255.255.0.0 subnet mask to all networks in the routing updates it forwards. |
