Referring to the exhibit, what are three configuration commands that would solve this problem?

Exhibit

R1 and R8 are not receiving each other’s routes

Referring to the exhibit, what are three configuration commands that would solve this problem? (Choose three.)
A . Configure loops and advertise-peer-as on routers in AS 64497 and AS 64450.
B . Configure loops on routers in AS 65412 and advertise-peer-as on routers in AS 64498.
C . Configure as-override on advertisement from AS 64500 toward AS 64512.
D . Configure remove-private on advertisements from AS 64497 toward AS 64498
E . Configure remove-private on advertisements from AS 64500 toward AS 64499

View Answer

Answer: C,D,E

Explanation:

In the scenario described in the exhibit where R1 and R8 are not receiving each other’s routes, here are three configuration commands that could potentially solve the problem, based on common BGP configurations and issues:

Configure as-override on advertisement from AS 64500 toward AS 64512.

The as-override command replaces the originating AS number with the local AS number in the AS_PATH attribute when sending BGP updates to a client in a confederation or when routes are advertised to eBGP peers in the same AS. This can be necessary when routers in different ASNs are not accepting routes due to AS path loop prevention mechanisms.

Configure remove-private on advertisements from AS 64497 toward AS 64498.

The remove-private command removes private AS numbers from the AS_PATH in BGP updates. This is often used when advertising routes to the internet, where private AS numbers should not be present. If R1 and R8 are filtering routes based on the presence of private AS numbers, this command could resolve the issue.

Configure remove-private on advertisements from AS 64500 toward AS 64499.

Similarly to the previous point, this command would remove private AS numbers from the AS_PATH when AS 64500 is advertising to AS 64499. If these routes are then being advertised to R1 and R8, and the presence of private AS numbers is causing route rejection, this could resolve the issue.