350-501 · Question #259
A network engineer is configuring RIP as the routing protocol between multiple PEs and CEs. The engineer must avoid advertising the same routes back to their sources. Which action should be performed
The correct answer is B. Define the site of origin on each interface.. To prevent routing loops and avoid advertising routes back to their sources when redistributing between RIP on CE routers and BGP on PE routers, the Site of Origin (SoO) attribute should be configured on each interface. The SoO attribute acts as a loop prevention mechanism in MPL
Question
A network engineer is configuring RIP as the routing protocol between multiple PEs and CEs. The engineer must avoid advertising the same routes back to their sources. Which action should be performed on the routers to accomplish this task?
Options
- AConfigure a different route distinguisher for each prefix.
- BDefine the site of origin on each interface.
- CDefine VRFs on each device to separate the traffic.
- DEnable bidirectional forwarding detection on each device.
How the community answered
(29 responses)- A3% (1)
- B79% (23)
- C7% (2)
- D10% (3)
Why each option
To prevent routing loops and avoid advertising routes back to their sources when redistributing between RIP on CE routers and BGP on PE routers, the Site of Origin (SoO) attribute should be configured on each interface. The SoO attribute acts as a loop prevention mechanism in MPLS VPNs.
Route distinguishers (RDs) are used to make VPNv4 routes unique in the global BGP table, but they are not primarily for preventing routing loops when redistributing into an IGP like RIP back to the source.
In an MPLS VPN environment where a PE router redistributes routes between a VRF (connected to a CE via RIP) and BGP, the Site of Origin (SoO) is used to prevent routing loops. When a route is learned from a CE and has an SoO applied, the PE router will not re-advertise that same route back to any interface on that VRF if it has the matching SoO, effectively preventing the CE from receiving its own routes.
Defining VRFs (Virtual Routing and Forwarding instances) separates traffic logically, but VRFs alone do not prevent routing loops when redistributing routes between the VRF and the connected CE device without additional mechanisms like SoO.
Bidirectional Forwarding Detection (BFD) is a fast link failure detection protocol that speeds up convergence but does not address routing loop prevention for redistributed routes.
Concept tested: MPLS VPN routing loop prevention (Site of Origin)
Source: https://www.cisco.com/c/en/us/td/docs/ios/mp_l3vpn/configuration/guide/m3_l3vpn_cfg_guide_xe/m3_redist_igp_mpls_l3vpn.html
Topics
Community Discussion
No community discussion yet for this question.