Projects › Junos eBGP Peering at a Regional Internet Exchange
Junos eBGP Peering at a Regional Internet Exchange
Tor Valley Broadband (AS 65100) has joined a regional internet exchange with its Junos edge router (EDGE-MX). Its first bilateral peer on the exchange LAN (192.0.2.0/24) is a content network, CDN-PEER (AS 65200, 192.0.2.100), already configured. Address the exchange port, set the AS, bring up the session, and announce exactly the member prefix 203.0.113.0/24, anchored so it is always in the routing table. The lab router forwards in packet-based mode, so no zones are needed.
Difficulty: intermediate · Time: about 55 minutes
Why it matters
Junos does not announce a prefix because a "network" line says so: an export policy decides what BGP sends, and the prefix must be in the routing table to be sent. Announcing exactly your own prefix, and nothing else (not the exchange LAN), is the basic manners of peering, and a leak is how outages start.
Technologies
- Juniper Junos
- eBGP
- Route Policy
- Route Advertisement
- Junos Commit Model
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
- Arista EOS eBGP Between Two Business Units After a Merger
- Arista EOS BGP Prefix Advertisement to an Upstream Provider