From: Fowlie, Colin (Colin.Fowlie@aliant.ca)
Date: Wed Jan 12 2005 - 00:59:18 GMT-3
You will have to still define the router as part of the confederation,
otherwise peers will reject updates as they will belong to their own AS.
So without changing the parent AS on R8, the following should get you up
and running:
R3
router bgp 65000
bgp router-id 5.5.3.3
bgp confederation identifier 100
- bgp confederation peers 61400
+ bgp confederation peers 61400 100
neighbor 5.5.1.1 remote-as 61400
neighbor 5.5.1.1 ebgp-multihop 3
neighbor 5.5.1.1 update-source Loopback0
+ neighbor 5.5.8.8 remote-as 100
+ neighbor 5.5.8.8 ebgp-multihop 3
+ neighbor 5.5.8.8 update-source Loopback0
R8
router bgp 100
bgp router-id 5.5.8.8
+ bgp confederation identifier 100
+ bgp confederation peers 61400 65000
+ neighbor 5.5.3.3 remote-as 6500
+ neighbor 5.5.3.3 ebgp-multihop 3
+ neighbor 5.5.3.3 update-source Loopback0
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:21 GMT-3