Projects › Arista EOS BGP Prefix Advertisement to an Upstream Provider
Arista EOS BGP Prefix Advertisement to an Upstream Provider
Northgate Colo (AS 65030) has its own provider-independent prefix, 198.51.100.0/24, and is bringing up transit from its upstream (UPSTREAM-PE, AS 65040, already configured on 192.0.2.48/30 and announcing 203.0.113.0/24). Configure the Arista edge (DC-EDGE): the peering interface, an anchor route for the prefix, the BGP session, and the announcement of exactly that prefix.
Difficulty: intermediate · Time: about 45 minutes
Why it matters
Advertising the wrong prefix, or nothing at all, is how a new peering silently achieves nothing. A network statement only advertises what is in the routing table exactly, so the prefix is anchored to Null0, which keeps the announcement stable however the inside of the network changes. The peering /30 is not yours to announce.
Technologies
- Arista EOS
- eBGP
- Route Advertisement
- Routed Interfaces
Related projects
- Dual-Homed eBGP Edge Routing with AS-Path Prepending
- Service Provider MPLS L3VPN for Two Overlapping Customers
- DDoS Mitigation with BGP Flowspec at a Regional ISP
- MPLS Traffic Engineering with RSVP-TE and Fast Reroute
- Replacing LDP with Segment Routing (SR-MPLS) in a Six-Router Core
- Advanced BGP Traffic Engineering with Standard & Extended Communities
- Junos eBGP Peering at a Regional Internet Exchange
- Arista EOS eBGP Between Two Business Units After a Merger