- mice-discuss - lists.micemn.net

Re: Saturated ports

by Darin Steffl

My original thread is about DCN, not SDN. On Wed, Aug 21, 2019, 4:00 PM Matthew Beckwell <mbeckwell(a)evolveip.net> wrote: > I feel like we’re mixing up “SDN” and “DCN” here? > > > > > > *From: *MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Corey > Hauer <coreyhauer(a)GMAIL.COM> > *Reply-To: *MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > *Date: *Wednesday, August 21, 2019 at 3:10 PM > *To: *"MICE-DISCUSS(a)LISTS.IPHOUSE.NET" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > *Subject: *Re: [MICE-DISCUSS] Saturated ports > > > > Honestly, as an eyeball network, I would fix saturating that pipe that by > filtering prefixes or adding capacity. My customers would vote with their > feet if we started having packet loss or adverse latency because we filled > our IX facing pipes. I can't imagine SDN and their members choosing to > endure thousands of customer complaints. > > > > SDN is a well run, well capitalized network - they'll fix it one way or > another. I am sure once this lands on the right person's desk - it gets > fixed. > > > > > > On Wed, Aug 21, 2019 at 12:17 PM Ben Wiechman <ben.wiechman(a)arvig.com> > wrote: > > Is it possible to send a weekly/monthly reporting showing a high water > mark for utilization for each member? Is that appropriate? Or do we just > ask each member to monitor the utilization graphs if this is of interest to > them? > > > > For my part it is easier to ingest and handle a periodic review if we are > pushed the information versus having to have someone remember to go and > pull the information. I'm interested in what others would find useful. > > > > *Ben Wiechman* > > Director of IP Strategy and Engineering > > 320.247.3224 | ben.wiechman(a)arvig.com > > Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com > > > > > > > > On Wed, Aug 21, 2019 at 1:59 PM Jay Hanke <jayhanke(a)southfront.io> wrote: > > > To be clear, I was not advocating for punitive action, and we can go and > pull the bandwidth reports periodically. I was just posing the question > regarding whether a more proactive stance regarding visibility would be > appropriate. > > What would you propose? > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Aug. 21, 2019

Re: Saturated ports

by AnthonyAnderberg＠nuvera.net

I think there is some confusion – the original thread was talking about DCN, not SDN. SDN is a long-time MICE member and hasn’t ever had any issues that I recall. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Gary Glissendorf <Gary.Glissendorf(a)SDNCOMMUNICATIONS.COM> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Date: Wednesday, August 21, 2019 at 3:45 PM To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] Saturated ports I noticed this thread today but wasn’t sure what topic started the thread. SDN like Corey said our customers report latency, packet loss quickly if we have saturation. We monitor and alert on network saturation at 60% and if needed we adjust prefix advertisements until we can find the proper balance and then increase bandwidth when needed. We have not developed a cool automatic was to do this yet but we rarely have issues with Peaks or DDoS Attacks. It’s the occasional fiber cuts that can cause us issues and the need to adjust bandwidth. What was topic that started the Thread about BW and reports. Gary Glissendorf | Network Architect gary.glissendorf(a)sdncommunications.com 2900 W. 10th St. | Sioux Falls, SD 57104 (w) 605.978.3558 | (c) 605.359-3737 | (tf) 800.247.1442 SDN NOC 877.287.8023 NOC Support email: sdnsupport(a)sdncommunications.com “Ausgezeichnet Zueinander Sein” [cid:image001.jpg@01D55838.820116E0] <http://www.facebook.com/sdncommunications> [cid:image002.jpg@01D55838.820116E0] <http://twitter.com/sdncomm> [cid:image003.jpg@01D55838.820116E0] <http://plus.google.com/107192460129695945716/posts> [cid:image004.jpg@01D55838.820116E0] <http://www.linkedin.com/company/sdn-communications> [cid:image005.jpg@01D55838.820116E0] <http://www.youtube.com/user/sdncomm> From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Corey Hauer Sent: Wednesday, August 21, 2019 3:10 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Saturated ports Honestly, as an eyeball network, I would fix saturating that pipe that by filtering prefixes or adding capacity. My customers would vote with their feet if we started having packet loss or adverse latency because we filled our IX facing pipes. I can't imagine SDN and their members choosing to endure thousands of customer complaints. SDN is a well run, well capitalized network - they'll fix it one way or another. I am sure once this lands on the right person's desk - it gets fixed. On Wed, Aug 21, 2019 at 12:17 PM Ben Wiechman <ben.wiechman(a)arvig.com<mailto:ben.wiechman@arvig.com>> wrote: Is it possible to send a weekly/monthly reporting showing a high water mark for utilization for each member? Is that appropriate? Or do we just ask each member to monitor the utilization graphs if this is of interest to them? For my part it is easier to ingest and handle a periodic review if we are pushed the information versus having to have someone remember to go and pull the information. I'm interested in what others would find useful. Ben Wiechman Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com<mailto:ben.wiechman@arvig.com> Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com<http://arvig.com> On Wed, Aug 21, 2019 at 1:59 PM Jay Hanke <jayhanke(a)southfront.io<mailto:jayhanke@southfront.io>> wrote: > To be clear, I was not advocating for punitive action, and we can go and pull the bandwidth reports periodically. I was just posing the question regarding whether a more proactive stance regarding visibility would be appropriate. What would you propose? ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ***This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.*** ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 21, 2019

Re: Saturated ports

by Matthew Beckwell

I feel like we’re mixing up “SDN” and “DCN” here? From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Corey Hauer <coreyhauer(a)GMAIL.COM> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Date: Wednesday, August 21, 2019 at 3:10 PM To: "MICE-DISCUSS(a)LISTS.IPHOUSE.NET" <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] Saturated ports Honestly, as an eyeball network, I would fix saturating that pipe that by filtering prefixes or adding capacity. My customers would vote with their feet if we started having packet loss or adverse latency because we filled our IX facing pipes. I can't imagine SDN and their members choosing to endure thousands of customer complaints. SDN is a well run, well capitalized network - they'll fix it one way or another. I am sure once this lands on the right person's desk - it gets fixed. On Wed, Aug 21, 2019 at 12:17 PM Ben Wiechman <ben.wiechman(a)arvig.com<mailto:ben.wiechman@arvig.com>> wrote: Is it possible to send a weekly/monthly reporting showing a high water mark for utilization for each member? Is that appropriate? Or do we just ask each member to monitor the utilization graphs if this is of interest to them? For my part it is easier to ingest and handle a periodic review if we are pushed the information versus having to have someone remember to go and pull the information. I'm interested in what others would find useful. Ben Wiechman Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com<mailto:ben.wiechman@arvig.com> Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com<http://arvig.com> On Wed, Aug 21, 2019 at 1:59 PM Jay Hanke <jayhanke(a)southfront.io<mailto:jayhanke@southfront.io>> wrote: > To be clear, I was not advocating for punitive action, and we can go and pull the bandwidth reports periodically. I was just posing the question regarding whether a more proactive stance regarding visibility would be appropriate. What would you propose? ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 21, 2019

Re: Saturated ports

by Gary Glissendorf

I noticed this thread today but wasn’t sure what topic started the thread. SDN like Corey said our customers report latency, packet loss quickly if we have saturation. We monitor and alert on network saturation at 60% and if needed we adjust prefix advertisements until we can find the proper balance and then increase bandwidth when needed. We have not developed a cool automatic was to do this yet but we rarely have issues with Peaks or DDoS Attacks. It’s the occasional fiber cuts that can cause us issues and the need to adjust bandwidth. What was topic that started the Thread about BW and reports. Gary Glissendorf | Network Architect gary.glissendorf(a)sdncommunications.com 2900 W. 10th St. | Sioux Falls, SD 57104 (w) 605.978.3558 | (c) 605.359-3737 | (tf) 800.247.1442 SDN NOC 877.287.8023 NOC Support email: sdnsupport(a)sdncommunications.com “Ausgezeichnet Zueinander Sein” [cid:image001.jpg@01D55837.7362FB90] <http://www.facebook.com/sdncommunications> [cid:image002.jpg@01D55837.7362FB90] <http://twitter.com/sdncomm> [cid:image003.jpg@01D55837.7362FB90] <http://plus.google.com/107192460129695945716/posts> [cid:image004.jpg@01D55837.7362FB90] <http://www.linkedin.com/company/sdn-communications> [cid:image005.jpg@01D55837.7362FB90] <http://www.youtube.com/user/sdncomm> From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Corey Hauer Sent: Wednesday, August 21, 2019 3:10 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Saturated ports Honestly, as an eyeball network, I would fix saturating that pipe that by filtering prefixes or adding capacity. My customers would vote with their feet if we started having packet loss or adverse latency because we filled our IX facing pipes. I can't imagine SDN and their members choosing to endure thousands of customer complaints. SDN is a well run, well capitalized network - they'll fix it one way or another. I am sure once this lands on the right person's desk - it gets fixed. On Wed, Aug 21, 2019 at 12:17 PM Ben Wiechman <ben.wiechman(a)arvig.com<mailto:ben.wiechman@arvig.com>> wrote: Is it possible to send a weekly/monthly reporting showing a high water mark for utilization for each member? Is that appropriate? Or do we just ask each member to monitor the utilization graphs if this is of interest to them? For my part it is easier to ingest and handle a periodic review if we are pushed the information versus having to have someone remember to go and pull the information. I'm interested in what others would find useful. Ben Wiechman Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com<mailto:ben.wiechman@arvig.com> Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com<http://arvig.com> On Wed, Aug 21, 2019 at 1:59 PM Jay Hanke <jayhanke(a)southfront.io<mailto:jayhanke@southfront.io>> wrote: > To be clear, I was not advocating for punitive action, and we can go and pull the bandwidth reports periodically. I was just posing the question regarding whether a more proactive stance regarding visibility would be appropriate. What would you propose? ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ***This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.***

Aug. 21, 2019

Re: Saturated ports

by Corey Hauer

Honestly, as an eyeball network, I would fix saturating that pipe that by filtering prefixes or adding capacity. My customers would vote with their feet if we started having packet loss or adverse latency because we filled our IX facing pipes. I can't imagine SDN and their members choosing to endure thousands of customer complaints. SDN is a well run, well capitalized network - they'll fix it one way or another. I am sure once this lands on the right person's desk - it gets fixed. On Wed, Aug 21, 2019 at 12:17 PM Ben Wiechman <ben.wiechman(a)arvig.com> wrote: > Is it possible to send a weekly/monthly reporting showing a high water > mark for utilization for each member? Is that appropriate? Or do we just > ask each member to monitor the utilization graphs if this is of interest to > them? > > For my part it is easier to ingest and handle a periodic review if we are > pushed the information versus having to have someone remember to go and > pull the information. I'm interested in what others would find useful. > > Ben Wiechman > > Director of IP Strategy and Engineering > > 320.247.3224 | ben.wiechman(a)arvig.com > > Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com > > > > > On Wed, Aug 21, 2019 at 1:59 PM Jay Hanke <jayhanke(a)southfront.io> wrote: > >> > To be clear, I was not advocating for punitive action, and we can go >> and pull the bandwidth reports periodically. I was just posing the question >> regarding whether a more proactive stance regarding visibility would be >> appropriate. >> >> What would you propose? >> > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Aug. 21, 2019

Re: Saturated ports

by Andy Koch

On 8/21/19 2:17 PM, Ben Wiechman wrote: > Is it possible to send a weekly/monthly reporting showing a high water > mark for utilization for each member? Is that appropriate? Or do we > just ask each member to monitor the utilization graphs if this is of > interest to them? > > For my part it is easier to ingest and handle a periodic review if we > are pushed the information versus having to have someone remember to > go and pull the information. I'm interested in what others would find > useful. I don't mind if this is an opt-in item on a per-participant basis, but I am not in-favor of having yet more to my inbox. I feel that any good participant should have their own monitoring and be properly alerted based on that - possibly directly into a capacity planning workflow. If you want to have a periodic email, I am sure a curl request to the MICE monitoring server on a cron would be fairly simple to setup if you have cleared it with US Internet who graciously hosts that for us. If the recommendation is for a mass-email to the mailing list with all participant data, that I am even less in support of. We have several participants that do not publicly share their capacity data and we should respect that - not blast it out weekly/monthly, even if the recipient list is opt-in. Regards, Andy Andy Koch Hoyos Consulting LLC ofc: +1 608 616 9950 andyk(a)hoyosconsulting.com http://www.hoyosconsulting.com

Aug. 21, 2019

Re: Saturated ports

by Ben Wiechman

Is it possible to send a weekly/monthly reporting showing a high water mark for utilization for each member? Is that appropriate? Or do we just ask each member to monitor the utilization graphs if this is of interest to them? For my part it is easier to ingest and handle a periodic review if we are pushed the information versus having to have someone remember to go and pull the information. I'm interested in what others would find useful. Ben Wiechman Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com On Wed, Aug 21, 2019 at 1:59 PM Jay Hanke <jayhanke(a)southfront.io> wrote: > > To be clear, I was not advocating for punitive action, and we can go and > pull the bandwidth reports periodically. I was just posing the question > regarding whether a more proactive stance regarding visibility would be > appropriate. > > What would you propose? >

Aug. 21, 2019

Re: Saturated ports

by Jay Hanke

> To be clear, I was not advocating for punitive action, and we can go and pull the bandwidth reports periodically. I was just posing the question regarding whether a more proactive stance regarding visibility would be appropriate. What would you propose?

Aug. 21, 2019

Re: Saturated ports

by Ben Wiechman

To be clear, I was not advocating for punitive action, and we can go and pull the bandwidth reports periodically. I was just posing the question regarding whether a more proactive stance regarding visibility would be appropriate. Ben Wiechman Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com On Wed, Aug 21, 2019 at 11:55 AM Jay Hanke <jayhanke(a)southfront.io> wrote: > > I don't think blocking a port is a good idea but I think proactive > notifications is a good first step then more harshly worded emails if that > doesn't work. > > We're already doing this. Just not automated. > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 >

Aug. 21, 2019

Re: Of minor note

by Steve Howard

Aug. 21, 2019