Click the Exhibit button.
RR:
protocols {
bgp {
group ebgd {
type external;
peer-as 100;
neighbor 172.16.1.1 {
description R1;
}
}
group ibgp {
type internal;
neighbor 172.16.1.2 {
description R2;
}
group cluster {
type internal;
neighbor 172.16.1.3 {
description R3;
}
neighbor 172.16.1.4 {
description R4;
}
neighbor 172.16.1.5 {
description R5;
}
cluster 0.0.0.1;
no-client-reflect;}
}
}
Router RR is receiving routes from R1, R2, R3, and R4 as shown in the exhibit.
Which routes will RR advertise to R5? (Choose two.)
A.
routes from R4
B.
routes from R1
C.
routes from R2
D.
routes from R3
correct answer should be B and C
I agree with B and C and this is why. Looking at the topology R1 is an EBGP and R2 is IBGP not part of the cluster even though the diagram makes it looks like is. Pay attention to the config. RR will reflect route to RR clients. All routes learned from R1 and 2 will automatically be advertised to all the clients
agree B&C
cluster 0.0.0.1;
no-client-reflect;
Disable intracluster route redistribution by the system acting as the route reflector. Include this statement when the client cluster is fully meshed to prevent the sending of redundant route advertisements.
If the RR receives a route from a client peer, it reflects the route to all nonclients and all client peers except the client who originated the route. (Note: If you configure the parameter no-client-reflect,the RR does not reflect routes to other clients. Include this statement only when all the clients are fully meshed.)
https://jncie.files.wordpress.com/2008/09/350009_-junos-bgp-route-reflection-configuration-and-operation.pdf
OOOO, good catch! Nice, that makes perfect sense.
yes B, C
B & C are correct.
Silly question as you have no-client-reflect configured without direct IBGP peerings to your Internal peers!