HPE7-A08 · Question #243
You have successfully configured an 'established' eBGP connection to two ISPs. After additional testing, you discovered that Internet connectivity is not working, and both ISPs report they are not…
The correct answer is D. Configure a static null route to the /24 public network while creating a matching network. To advertise your owned /24, BGP must have that prefix in the routing table and be explicitly told to originate it. A static null route installs the /24 in the routing table, and the matching BGP network statement causes the switch to advertise the prefix to both ISPs.
Question
You have successfully configured an 'established' eBGP connection to two ISPs. After additional testing, you discovered that Internet connectivity is not working, and both ISPs report they are not learning a route for your company’s /24 public address range. What additional configuration is required?
Options
- AApply an inbound route-map allowing a prefix-list matching the /24 to the ISP peering interfaces.
- BConfigure a static route to the /24 via a loopback interface and redistribute connected routes into
- CCreate a loopback interface with an address within the /24 and enable BGP on the loopback
- DConfigure a static null route to the /24 public network while creating a matching network
How the community answered
(20 responses)- A5% (1)
- B5% (1)
- C10% (2)
- D80% (16)
Explanation
To advertise your owned /24, BGP must have that prefix in the routing table and be explicitly told to originate it. A static null route installs the /24 in the routing table, and the matching BGP network statement causes the switch to advertise the prefix to both ISPs.
Topics
Community Discussion
No community discussion yet for this question.