[c-nsp] eBGP & backup static route

[Saku Ytti]

On (2009-02-17 15:53 +0000), Timothy Arnold wrote:

> > don't think this will help as a locally-originated route is preferred
> > over almost anything due to the higher weight (32768, if I recall
> > correctly), so the eBGP path will not be installed (and would win over
> > the static due to admin distance). you need to set the weight on the
> > eBGP path to be the same (or higher) value or reduce it to zero (to
> > match the eBGP path) when redistributing the static (not 100% sure if
> > the latter works, I think it does)..
> 
> Setting the weight to 32768 has solved the problem. I'm going to try and set the weight to 0 on redistributed static routes as that would be a better approach for me!

Is this one or more boxes? Weight does not travel. So if it is multiple
boxes, only thing you need to do, is to ensure that the backup route is
seen by network as worse as the primary route, when the primary route
comes back.
So if after outage is over, and primary is back on, primary PE still
uses the backup route, it is not because of weight, since the primary
does not experience the weight of the backup.
Only thing setting weight 0 on the backup does, is makes sure that
also local traffic behind backup PE, starts to flow via primary,
instead of choosing the local backup route.

If it is indeed same box (ouch, backup and primary in same box,
I hope not) then resetting weight is needed.
-- 
  ++ytti