[j-nsp] Alternatives to floating static routes?

[Erdem Sener]

Hi Dario,

 Please see in-line for my 'personal' comments :)


>        Networks1 -- Customer 1 ------ BGP1 -----|
>                                |                               |------ Juniper
>        Networks2 -- Customer 2 ------ BGP2 -----|
>

 Since you'll have eBGP with private-as with your customers, you might
want to assign different AS's for each, and build a BGP session
between them as well. This of course would be a little bit more
configuration on the customer side but you will avoid many static
routes :)

> We'll announce default route to each customer and they announce their networks and the
> networks of the other customer (with one prepend for example). We need also to decrease
> bgp timers in order to fas re-route.

I think this is a good idea :)

>
> Each customer needs to configure an static route to the networks of the other, via the link
> between then. An, to provide out access when their link with us fails, they need to configure
> other static route (default) via the link between them, with more metric than BGP (to only
> be active when BGP fails).

If you choose to go with BGP between your customers as well, they may
both announce default route information (which they'll learn via BGP
from you) to eachother to avoid any problems.



> Is that correct? Anything wrong? We don't have any test-bed to check this configuration so
> we need to be sure before implement it :)

 As long as your configuration on customers' routers are set up and
you have a nice filter on Juniper side, you shouldn't have problems
with this scenario. Of course, it's always a good idea to aggree with
your customers upon a maintenance window and stimulate any failures
you can think of.

HTH
Erdem