On 18/Jul/18 08:39, Gert Doering wrote:
> If you do this, be aware that every OSPF come-and-go is very likely to lead
> to a churn in BGP, as metrics change. This might or might not be a problem,
> but everything that leads to externally visible BGP updates should be
> considered well.
If I
Systems, Inc. All rights reserved. 1 Session Number
> Presentation_ID Cisco Confidential Deploying OSPF for ISPs ISP/IXP Workshops
>
>
>
>
>
>
>
>
>
>
>
> --
> *From:* cisco-nsp on behalf of Lee
> Starnes
> *Sent:* Tuesday, Jul
> Lee Starnes
> Sent: Tuesday, July 17, 2018 10:17 PM
>
> Is there a
> way to allow the /22 block to propagate to the edge routers and still
maintain
> the hold down routes we need to announce that /22 via BGP to our various
> upstream carriers?
>
One problem I'd see with this setup is potential
Hi,
On Wed, Jul 18, 2018 at 02:57:37AM +, Erik Sundberg wrote:
> Change the Floating static route to an administrative distance of 254, so it
> is higher than OSPF.
>
>
> router static
> address-family ipv4 unicast
> 45.x.x.0/22 Null0 254
>
>
> When the route is learned via OSPF it
Hi,
On Tue, Jul 17, 2018 at 02:17:25PM -0700, Lee Starnes wrote:
> I have a question about OSPF route redistribution. We have no issues
> redistributing subnets in the network out of our /19 blocks. But we have a
> /22 block that the entire /22 is allocated to a single client. The routes
>
SP/IXP Workshops
From: cisco-nsp on behalf of Lee Starnes
Sent: Tuesday, July 17, 2018 4:17:25 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] OSPF routing question
Hello everyone,
I have a question about OSPF route redistribution. We have no issues
redistributing subnet
Hello everyone,
I have a question about OSPF route redistribution. We have no issues
redistributing subnets in the network out of our /19 blocks. But we have a
/22 block that the entire /22 is allocated to a single client. The routes
redistribute across all the all switches except back to the
