Octet

Inbound traffic keeps arriving on the backup ISP despite AS path prepending

TroubleshootingExpert

The ticket

R1 (AS 64500) announces 203.0.113.0/24 to ISP1 (AS 64496, primary) and ISP2 (AS 64497, backup). ISP1 and ISP2 peer with each other. To keep inbound traffic on ISP1, the team prepends 64500 64500 64500 toward ISP2. Outbound already prefers ISP1 through local preference. Even so, about a third of inbound traffic arrives on the ISP2 link, and the backup circuit is billed on usage. Management asks why the prepend "does not work".

peeringGi0/0/0192.0.2.0/30Gi0/0/1198.51.100.0/30NETRest of the internetISP1AS 64496 primaryISP2AS 64497 backupR1AS 64500

Book 4.1 Global Internet

Step 1 of 3

Before changing anything, what do you confirm?