If you have redundant RRs with the same cluster ID, they will discard each other's routes. If they have different cluster IDs, they will accept each other's routes.
Since the route is advertised using ebgp, nexthop is the address of each of RR1 and RR2.
AB
A. RR1 and RR2 must have the same cluster ID to exchange routes learned from the client.
B. RR1 and RR2 append the cluster ID when advertising routes from client to client.
These statements are correct because:
Cluster ID: Both route reflectors need to have the same cluster ID to ensure they can exchange routes learned from their clients.
Appending Cluster ID: When advertising routes from one client to another, the route reflectors append the cluster ID to prevent routing loops.
C. RR1 and RR2 advertise routes learned from the clients to EBGP peers, using itself as the next hop.
This statement is incorrect. In a typical BGP setup, route reflectors do not change the next hop attribute when advertising routes learned from clients to EBGP peers. The next hop remains the IP address of the client that originated the route.
D. RR1 advertises routes from the client to RR2, using itself as the next hop.
This statement is also incorrect. When RR1 advertises routes to RR2, it does not use itself as the next hop. Instead, it maintains the original next hop attribute to ensure proper routing within the network.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
tsukasa123
Highly Voted 11 months, 3 weeks agoAvee123
Most Recent 2 months, 3 weeks agoGuru29
6 months, 2 weeks agoeasynet13
8 months ago