[6bone] IPv6 route server

[Nicolas DEFFAYET]

On Thu, 2002-08-08 at 15:57, John Fraizer wrote:
> 
> I think the root cause of it only showing one prefix originally in this
> case was that it was configured as an iBGP peer, on top of the fact that
> bestpath selection on the two border routers is preventing them from
> sending all paths they see to the route-server.
> 
> I have thought about this a bit and may have come up with a solution that
> will give the route-server a "full" view of what the borders have.
> 
> On the borders, if Nicholas were to do like this:
> 
> 
> !This is the MAIN view, the one for bestpath selection that will be used
> !by the border router.
> router bgp 65501
>  neighbor a::a remote-as AAAA
>  no neighbor a::a activate
>  neighbor b::b remote-as BBBB
>  no neighbor b::b activate
>  neighbor c::c remote-as CCCC
>  no neighbor c::c activate
> !
>  address-family ipv6
>  network [announce your networks here]
>  neighbor a::a activate
>  neighbor b::b activate
>  neighbor c::c activate
>  exit-address-family
> !
> !This is the AAAA view for the route-server
> router bgp 65501 view AAAA
>  neighbor a::a remote-as AAAA
>  no neighbor a::a activate
>  neighbor route::server remote-as 65501
>  no neighbor route::server activate
> !
>  address-family ipv6
>  neighbor a::a activate
>  neighbor a::a filter-list 2 out
>  neighbor route::server activate
>  neighbor route::server attribute-unchanged
> !
> !This is the BBBB view for the route-server
> router bgp 65501 view BBBB
>  neighbor b::b remote-as BBBB
>  no neighbor b::b activate
>  neighbor route::server remote-as 65501
>  no neighbor route::server activate
> !
>  address-family ipv6
>  neighbor b::b activate
>  neighbor b::b filter-list 2 out
>  neighbor route::server activate
>  neighbor route::server attribute-unchanged
> !
> !This is the CCCC view for the route-server
> router bgp 65501 view CCCC
>  neighbor c::c remote-as CCCC
>  no neighbor c::c activate
>  neighbor route::server remote-as 65501
>  no neighbor route::server activate
> !
>  address-family ipv6
>  neighbor c::c activate
>  neighbor c::c filter-list 2 out
>  neighbor route::server activate
>  neighbor route::server attribute-unchanged
> !
> ip as-path access-list 2 deny .*
> 
> 
> We're simply creating a "view" for each of our eBGP peers.  Since it is
> the only peer (besides the route-server) in that view, it will always be
> the bestpath to any prefixes it sends us.  Since the route-server is
> peered in all "views" but, not in the MAIN (bestpath) view, it will get
> everything that the border router(s) get.  We use filter-list 2 (deny
> *) outbound on the peers within our special views because we are already
> announcing our routes to them in our MAIN view.
> 
> This *should* give the route-server *full* views of all your eBGP peers
> (at least the ones you set up views for).  IMHO, this makes it a much more
> useful utility to the general community since they will then get to see
> ALL of the paths you see to a particular path vs just the selected
> bestpath on each border router.
> 
> Note: You shouldn't have to change ANY of the configuration on the
> route-server itself.  Simply remove the route-server from the MAIN view on
> the border routers and create a view for each peer you want to appear in
> route-server queries with [peer] and [route-server] being the only
> configured neighbors in that view.
> 

I can't do that for more than 50 neighbors...

If you check route servers on
http://www.traceroute.org/#Route%20Servers, the route server display
only best-paths of the remote routers or the best path from the
route-server...

Best Regards,

Nicolas DEFFAYET