- mice-discuss - lists.micemn.net

Re: zayo again?

by James Urwiller

I have been told they cannot reach a cyan shelf in belle plaine. they also asked me how to gain access to the location and provide a local contact. I tried explaining that it is their hut, not mine and I don't have access...because its not my hut. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: James Urwiller <james.urwiller(a)turnkey-telecom.com> Sent: Friday, August 30, 2019 02:16 To: 'MICE-DISCUSS(a)LISTS.IPHOUSE.NET' <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: RE: zayo again? My initial down was at 00:14 CST, and came back 01:04 CST. Then back down again 01:20 CST, and then back around 01:43CST. Seems to be stable at the moment. Anyone else experience this? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: James Urwiller <james.urwiller(a)turnkey-telecom.com> Sent: Friday, August 30, 2019 01:37 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: zayo again? been seeing BGP seesion bounces sine around midnight. anyone else zayo2belleplaine??? Sent from my iPhone 7

Aug. 30, 2019

Re: zayo again?

by James Urwiller

My initial down was at 00:14 CST, and came back 01:04 CST. Then back down again 01:20 CST, and then back around 01:43CST. Seems to be stable at the moment. Anyone else experience this? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: James Urwiller <james.urwiller(a)turnkey-telecom.com> Sent: Friday, August 30, 2019 01:37 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: zayo again? been seeing BGP seesion bounces sine around midnight. anyone else zayo2belleplaine??? Sent from my iPhone 7

Aug. 30, 2019

zayo again?

by James Urwiller

been seeing BGP seesion bounces sine around midnight. anyone else zayo2belleplaine??? Sent from my iPhone 7

Aug. 30, 2019

Re: Of minor note

by Bahls, Dean

Yeah, I forgot to notify the group when we did a software update this morning. Sorry about that. Dean On Mon, Aug 26, 2019 at 8:33 PM Frank Bulk <fbulk(a)mypremieronline.com> wrote: > FYI, saw it again this morning: > > Aug 26 05:42:02 207.32.15.28 Rib: mpbgp_recv_mpreach: peer > 2001:504:27::d1af:0:1 (AS 53679) link-local next hop > fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop > Aug 26 05:42:02 207.32.15.28 Rib: mpbgp_recv_mpreach: peer > 2001:504:27::d1af:0:2 (AS 53679) link-local next hop > fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop > > Frank > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank > Bulk > Sent: Wednesday, August 21, 2019 8:00 AM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] Of minor note > > Our route logged these two items Monday morning with MICE's AS: > > Aug 19 10:35:41 207.32.15.28 Rib: mpbgp_recv_mpreach: peer > 2001:504:27::d1af:0:2 (AS 53679) link-local next hop > fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop > Aug 19 11:08:50 207.32.15.28 Rib: mpbgp_recv_mpreach: peer > 2001:504:27::d1af:0:2 (AS 53679) link-local next hop > fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop > > Not sure what that was about. > > Frank > -- *Dean Bahls* Network Services Manager | Cooperative Network Services, LLC 14 Main St SW | P.O. Box J | Menahga, MN 56464 218.346.3635 (Direct) | 218.564.3000 (Main Office) dean.bahls(a)cooperative-networks.com

Aug. 27, 2019

Re: Of minor note

by Frank Bulk

FYI, saw it again this morning: Aug 26 05:42:02 207.32.15.28 Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:1 (AS 53679) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop Aug 26 05:42:02 207.32.15.28 Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:2 (AS 53679) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Frank Bulk Sent: Wednesday, August 21, 2019 8:00 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Of minor note Our route logged these two items Monday morning with MICE's AS: Aug 19 10:35:41 207.32.15.28 Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:2 (AS 53679) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop Aug 19 11:08:50 207.32.15.28 Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:2 (AS 53679) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop Not sure what that was about. Frank

Aug. 27, 2019

Re: ADV: [MICE-DISCUSS] Can a PTR be created for Google IP?

by Doug McIntyre

On Fri, Aug 23, 2019 at 04:45:35AM +0000, Frank Bulk wrote: >Can a PTR be created for this IP: 206.108.255.141 (AS 15169: Google LLC, US) Sure, I've setup the newest batch of IPv4/IPv6 reverses for the MICE block. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Aug. 23, 2019

Can a PTR be created for Google IP?

by Frank Bulk

Can a PTR be created for this IP: 206.108.255.141 (AS 15169: Google LLC, US) Frank

Aug. 23, 2019

Re: Saturated ports

by Jay Hanke

> If someone's port is full on a regular basis, having someone from the Board contact the member and ask if they are aware of the issue seems approprate and reasonable. Basically asking, "have you noticed your port is full quite a bit lately?" But its the member's responsibility to manage their network as they see fit, including their ports to the exchange. I'd tweak this a little to encourage the member reach out directly to the other peer whenever there might be a problem. If you need help getting attention of a non-responsive peer we can help with some "peer pressure". :) -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Aug. 22, 2019

Re: Saturated ports

by David Farmer

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? > First, let's not make a federal case of this, links fill up it happens, get over it. In this case it occurred right after big changes by a big content provider. I'm actually surprised more participants' links didn't fill up. Second, you should send a polite note to any another member, if you notice anything that isn't quite right, their link is full, they are leaking routes, or something just looks weird. We are a community, talk to your neighbors, be their early warning system. Hopefully, they already know about what ever it is, but we are all busy and things slip through the cracks all the time. So if you notice something that doesn't seem right, let your neighbors know about it. But be polite about it, next time it might be you who has something weird happening. Third, the IX is an optimization, if you are having issues sending traffic to another member you have other routes, use them. We have had to do this, not because the other member ignored us or wouldn't upgrade their link, but sometimes upgrades can take a little time. A few weeks or even a couple months to complete an upgrade isn't that unrealistic and not uncommon depending on the circumstances. Not everyone has extra 10G or 100G ports just sitting around, and if you have to backhaul the traffic, arranging that upgrade can easily take several months. The policy we have for remote switches makes sense, but members need to manage their own capacity. Even if we were to forced them to add port capacity to the exchange the bottleneck could just move to the next hop. None of us has sufficient visibility into the other guys network or business to be making those kinds of judgements for them. If someone's port is full on a regular basis, having someone from the Board contact the member and ask if they are aware of the issue seems approprate and reasonable. Basically asking, "have you noticed your port is full quite a bit lately?" But its the member's responsibility to manage their network as they see fit, including their ports to the exchange. Thanks -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

Aug. 22, 2019

Re: Saturated ports

by Corey Hauer

Indeed I did! 😮 On Wed, Aug 21, 2019 at 2: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 > <https://www.google.com/maps/search/224+East+Main+Street+%7C+Melrose,+MN+563…> > | 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