You work for a company that provides managed network services, and of your real estate clients running a small office is experiencing network issues,
Troubleshoot the network issues.
Router R1 connects the main office to internet, and routers R2 and R3 are internal routers NAT is enabled on Router R1.
The routing protocol that is enable between routers R1, R2, and R3 is RIPv2.
R1 sends default route into RIPv2 for internal routers to forward internet traffic to R1.
Server1 and Server2 are placed in VLAN 100 and 200 respectively, and dare still running router on stick configuration with router R2.
You have console access on R1, R2, R3, and L2SW1 devices.
Use only show commands to troubleshoot the issues.
—– Enter IOS commands on the device to verify network operation and answer the multiple-choice questions.
—– This task does not require device configuration.
—– Click the device icon to gain access to the console of the device. No console or enable passwords are required.
—– To access the multiple-choice questions, click the numbered boxes on the left of the top panel.
There are four multiple-choice questions with this task. Be sure to answer all four questions before clicking Next.Examine R2 configuration, the traffic that is destined to R3 LAN network sourced from Router R2 is forwarded to R1 instead R3. What could be an issue?
- A. RIPv2 enabled on R3, but R3 LAN network that is not advertised into RIPv2 domain.
- B. RIPv2 routing updates are suppressed between R2 and R3 using passive interface feature.
- C. RIPv2 not enabled on R3.
- D. No issue that is identified; this behavior is normal since default route propagated into RIPv2 domain by Router R1.
First we should check the routing table of R2 with the “show ip route” command.In this table we cannot find the subnet “10.10.12.0/24” (R3 LAN network) so R2 will use the default route advertised from R1 (with the command “default- information originate” on R1) to reach unknown destination, in this case subnet 10.10.12.0/24 -> R2 will send traffic to 10.10.12.0/24 to R1.
Next we need to find out why R3 did not advertise this subnet to R2. A quick check with the “show running-config” on R3 we will see that R3 was not configured with RIP ( no “router rip” section). Therefore we can conclude RIPv2 was not enabled on R3.