BGP Community-Based Traffic Attraction

A remote datacenter is attracting traffic for a prefix that should stay local. Investigate the BGP table, identify the community causing the issue, and fix it by modifying the route policy.

Guided

From:To IP:

junos

> show route 172.16.1.0/24 detail

172.16.1.0/24 *[BGP/170] LocalPref: 100, Communities: 65000:1001
                    > to 10.0.10.2 via et-0/0/0
              [BGP/170] LocalPref: 150, Communities: 65000:1001 65000:9999
                    > to 10.0.20.2 via et-0/0/1

Let's start by checking the BGP table on spine-1. We should see two paths for 172.16.1.0/24 — one from leaf-1 (local) and one from leaf-2 (remote).

Step 1 of 4