Hotspot question- RIPv2 Troubleshooting I
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.
Answer: C
Explanation:
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.
Leave a Reply