My scenario is quite simple actually. @Mark Tinka hit on it. A remote ISP fed by a single fiber path. I want to fail to another connection (cable) that apparently is fed on a different path. (Not a lot of options in rural areas).
On Fri, May 8, 2015 at 2:01 PM, Mark Tinka <[email protected]> wrote: > > > On 8/May/15 22:40, Saku Ytti wrote: > > I'm not entirely sure what is the scenario. Is the scenario one where > you have > > PE and CE, where PE may become isolated and if such, it should not inject > > default to CE? > > I've seen use-cases for this where customers are asking that if there is > is backbone failure beyond the local PoP they connect to, any default > routes announced to them should also disappear. Which makes sense. > > > > > > > b) generate static route in core boxes, via lets say discard route. > > In the use-case I describe above, the issue still remains if the local > core routers are fine, but the backbone links to the rest of the network > are down. > > In such a case, the only solution would be to originate the default > route from a core router closer to where traffic normally > ingresses/egresses the AS. The issue is that in large networks, this is > not feasible, as traffic ingresses/egresses the network from all sorts > of locations. It would be easier to focus on guaranteeing backbone > uptime instead :-\. > > Mark. > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Bill Blackford Logged into reality and abusing my sudo privileges..... _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
