Information Technology Reference
In-Depth Information
Initial Configuration for R1 (Continued)
Example 6-6
neighbor 172.160.1.2 remote-as 300
neighbor 172.160.1.2 update-source loopback0
neighbor 172.160.1.3 remote-as 300
neighbor 172.160.1.3 update-source loopback0
neighbor 100.100.100.1 remote-as 100
no auto-summary
!
Initial Configuration for R2
Example 6-7
R2#show running-config | begin bgp
router bgp 300
no synchronization
bgp log-neighbor-changes
network 172.160.0.0
neighbor 172.160.1.1 remote-as 300
neighbor 172.160.1.1 update-source loopback0
neighbor 172.160.1.3 remote-as 300
neighbor 172.160.1.3 update-source loopback0
neighbor 100.100.150.1 remote-as 100
no auto-summary
!
Initial Configuration for R3
Example 6-8
R3#show running-config | begin bgp
router bgp 300
no synchronization
bgp log-neighbor-changes
network 172.160.0.0
neighbor 172.160.1.1 remote-as 300
neighbor 172.160.1.1 update-source loopback0
neighbor 172.160.1.2 remote-as 300
neighbor 172.160.1.2 update-source loopback0
neighbor 200.200.200.1 remote-as 200
no auto-summary
!
Inbound Traffic Policy
The initial configuration does not provide any preference to inbound traffic flows. Traffic
takes the optimal path into the network based on AS_PATH when deciding between using
AS 100 and AS 200. This could result in overloading the DS3 link from AS 200. Traffic
entering through AS 100 takes either the DS3 or the OC-3, depending on the IGP metric to
the next-hop address, which could overload the DS3 link from AS 100.
