Download as pdf or txt
Download as pdf or txt
You are on page 1of 1

Traffic Engineering BGP Ingress Routing

AS 65345

AS 65002
R2 2001:db8:3::/128 2001:db8::5::/128
::2 2001:db8:2:3::/64 ::3 2001:db8:3:5::/64
R5
::3 R3
::2 ::5

2001:db8:4:3::/64

2001:db8:5:6::/64
2001:db8:1:2::/64
OSPFv3

64
& iBGP

:/
5::
:4
b8
:d
01
20
::1 ::4 R4 ::6
::1 2001:db8:1:4::/64
R1 R6
2001:db8::1::/128 2001:db8::4::/128 2001:db8::6::/128

AS 65001

Consider the topology. R1 is a small business with two Internet uplinks, one through R2 and one through R4.
R2 provides transit service for R1 into AS 65345, a large regional carrier. R1’s link to R4 is much slower
(or higher latency, higher monetary cost, lower reliability, etc.) and should only be used as a backup.
This policy decision should be implemented bidirectionally, applying to traffic egressing from R1 and for traffic ingressing to R1.

You might also like