Which two BGP route reflector attributes should be implemented to prevent routing loops? (Choose two)

The correct answer is B. ORIGINATOR_ID C. CLUSTER_LIST. BGP Route Reflectors (RR) use two attributes specifically designed to prevent routing loops. ORIGINATOR_ID (choice B) is set by the RR to the Router ID of the route's original client; if a router receives a route with its own Router ID as the ORIGINATOR_ID, it discards the route.

Core Routing

Question

Options

ACLUSTER_ID
BORIGINATOR_ID
CCLUSTER_LIST
DCOMMUNITY
EAS_PATH

How the community answered

(63 responses)

A
2% (1)
B
90% (57)
D
3% (2)
E
5% (3)

Explanation

BGP Route Reflectors (RR) use two attributes specifically designed to prevent routing loops. ORIGINATOR_ID (choice B) is set by the RR to the Router ID of the route's original client; if a router receives a route with its own Router ID as the ORIGINATOR_ID, it discards the route. CLUSTER_LIST (choice C) contains the list of CLUSTER_IDs the route has traversed; if a router receives a route containing its own CLUSTER_ID in the list, it discards the route. AS_PATH (choice E) prevents loops in eBGP but is not a route reflector-specific mechanism. COMMUNITY (choice D) and CLUSTER_ID (choice A) alone do not provide loop prevention-CLUSTER_ID is only meaningful when included in the CLUSTER_LIST.

Topics

#BGP#Route Reflector#Loop Prevention#BGP Attributes

Community Discussion

No community discussion yet for this question.

Full 300-510 Practice