HW has a Frame Relay network with two sites (a headquarters site and a remote site) connected by a single PVC. RIP version 2 is running in the network. A new remote site is added and HW has ordered a second PVC between this site and the headquarters site. All Frame Relay interface IP addresses are in a single subnet. The customer configured Frame Relay DLCI mappings and can successfully ping from the new remote to the headquarters site as well as to the other remote site. However, the new router does not have a route in its route table to the other remote site's LAN, and cannot ping the LAN interface or any hosts on that LAN. What is most likely causing the problem?
- A: Triggered updates should be configured on the headquarters router, to directly forward routing updates between the two remote sites
- B: The headquarters site router has split-horizon enabled on the frame-relay interface
- C: Neighbor statements are not configured on the two remote sites, pointing to all other sites
- D: The frame-relay IP to DLCI mappings are incorrectly configured
- E: RIP cannot propagate routing updates over a partial mesh frame-relay configuration, so another routing protocol should be selected