LISTSERV mailing list manager LISTSERV 16.0

Help for MICE-DISCUSS Archives


MICE-DISCUSS Archives

MICE-DISCUSS Archives


MICE-DISCUSS@LISTS.IPHOUSE.NET


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MICE-DISCUSS Home

MICE-DISCUSS Home

MICE-DISCUSS  April 2017

MICE-DISCUSS April 2017

Subject:

Re: Arista Round 3 Moves

From:

Andrew Hoyos <[log in to unmask]>

Reply-To:

MICE Discuss <[log in to unmask]>

Date:

Wed, 26 Apr 2017 09:46:30 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

I’ll also add, this is currently a draft with the IETF grow WG:

https://tools.ietf.org/html/draft-ietf-grow-bgp-session-culling-01

(and one which I fully support)

--
Andrew Hoyos
[log in to unmask]



> On Apr 26, 2017, at 9:34 AM, Andrew Hoyos <[log in to unmask]> wrote:
> 
> On Apr 26, 2017, at 9:19 AM, Mike Horwath <[log in to unmask]> wrote:
>> 
>> On Wed, Apr 26, 2017 at 08:07:45AM -0500, Andrew Hoyos wrote:
>>> I would suggest that perhaps we look into filtering BGP (tcp/179)
>>> with an ACL prior to maintenance start on those specific ports being
>>> moved.  Many other IXs are doing this for maintenance as a way to
>>> gracefully take things down, and let bilateral and RS sessions time
>>> out without killing active traffic. As we've noticed, not all
>>> members being moved are bothering to shut down sessions prior, which
>>> causes impact to/from those members.  (i.e.:
>>> https://ripe67.ripe.net/presentations/374-WH-IXPMaintReduce.pdf)
>> 
>> Don't even need ACLs.
>> 
>> Just take down the route servers for the 2 hour period.
>> 
>> Bilateral are unaffected and they can arrange things anyway with their
>> peers.
> 
> I’d disagree. The maintenance currently taking place affects more than just the route servers. Plenty of people are doing bi-lateral peering on MICE, and that *IS* affected by maintenance events like these.
> 
> Adding an ACL to the port ensures graceful shutdown/end of traffic, rather than an abrupt drop and hold timer fun.
> I’d much rather that someone running the maintenance and in control of the ultimate link up/down events be the one deciding when things are starting/ending and re-enabling traffic gracefully.
> 
>> Adding another step to the process creates more complications as well,
>> and another point of failure if you screw up along the way.
> 
> Disagree, adding an ACL to a port is pretty trivial. Add (pre-existing) ACL to port 10 minutes before maintenance starts. Remove when complete. 
> Script up into copy/paste thing with port numbers for bonus points and less changes of failure.
> 
>> Clean shutdown of bird is easier, quicker, and will for sure make the
>> multilateral peering not be further affected by bouncing repeatedly.
> 
> Yes, great for MLPA, but not for bilateral. 
> 
> Lastly, In this *specific* case, this presents issues with other members ports who are *NOT* affected by the maintenance and a loss of traffic for them if they are doing MLPA. Why break everyone and cause a total route server outage, when it’s not necessary at all? Yesterday’s maintenance only affected a portion of members. ACL’s on member ports would be the cleanest way to minimize outage duration for all members with the least impact to the IX as a whole.
> 
> 
> 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010

ATOM RSS1 RSS2



LISTS.IPHOUSE.NET

CataList Email List Search Powered by the LISTSERV Email List Manager