___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
On 6/9/09 4:05 PM, "m...@adv.gcomm.com.au" wrote:
> Hi,
>
> We are receiving a /24 from one of our upstreams, that we need to
> redistribute into our IGP (OSPF), so that all of our cores are aware
> that they can reach this /24 primarily through this upstream(Then, if
> this upstream is down,
You could run iBGP from your borders into your core.
On 10/06/09 9:05 AM, "m...@adv.gcomm.com.au" wrote:
Hi,
We are receiving a /24 from one of our upstreams, that we need to
redistribute into our IGP (OSPF), so that all of our cores are aware
that they can reach this /24 primarily through thi
Hi,
We are receiving a /24 from one of our upstreams, that we need to
redistribute into our IGP (OSPF), so that all of our cores are aware
that they can reach this /24 primarily through this upstream(Then, if
this upstream is down, traffic destined to this /24 would go via our
other upstreams
Hi,
On Wed, Jun 10, 2009 at 9:05 AM, wrote:
> I know redistributing bgp->ospf is considered a bad idea, but other than
> adding a static route, is there another option?
You could use a 'reliable static' (using IP SLA and the 'track'
keyword on the 'ip route' command) and redistribute that, but I
