why is the 200.1.0.0/16 prefix failing to be advertised in BGP?

— Exhibit — — Exhibit — Click the Exhibit button. Referring to the exhibit, why is the
200.1.0.0/16 prefix failing to be advertised in BGP?

— Exhibit — — Exhibit — Click the Exhibit button. Referring to the exhibit, why is the
200.1.0.0/16 prefix failing to be advertised in BGP?

A.
The IS-IS route is less preferred than the aggregate route.

B.
The policy works for internal BGP only.

C.
BGP needs a next-hop self policy.

D.
The aggregate route is set to reject.

Explanation:



Leave a Reply 0

Your email address will not be published. Required fields are marked *