- mice-discuss - lists.micemn.net

Re: Akamai bounce and graph

by Jeremy Lumby

My session bounced as well. When Marty was at Akamai, he requested that their graph be private. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Frank Bulk Sent: Thursday, January 18, 2018 9:29 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Akamai bounce and graph We saw our peering session with Akamai bounce around 9:10 am – anyone else? Jan 18 09:11:30 192.168.0.85 BGP: Peer 206.108.255.84 UP (ESTABLISHED) Jan 18 09:11:38 192.168.0.85 BGP: Peer 2001:504:27::51cc:0:1 UP (ESTABLISHED) And for some reason Akamai’s Cacti graph doesn’t show up in the Arista -> Traffic section. Is that opaque on purpose? I ask because when I click through it says “ACCESS DENIED” (in red =) ). Frank AS53347 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 18, 2018

Akamai bounce and graph

by Frank Bulk

We saw our peering session with Akamai bounce around 9:10 am - anyone else? Jan 18 09:11:30 192.168.0.85 BGP: Peer 206.108.255.84 UP (ESTABLISHED) Jan 18 09:11:38 192.168.0.85 BGP: Peer 2001:504:27::51cc:0:1 UP (ESTABLISHED) And for some reason Akamai's Cacti graph doesn't show up in the Arista -> Traffic section. Is that opaque on purpose? I ask because when I click through it says "ACCESS DENIED" (in red =) ). Frank AS53347

Jan. 18, 2018

Re: MICE Looking Glass router

by David Farmer

Thanks, guys, you're the best! On Wed, Jan 17, 2018 at 12:08 PM, Justin Krejci <JKrejci(a)usinternet.com> wrote: > David, ask and thou shall receive, so sayeth Anthony, Jeremy, Doug and > Justin.... > > > > micemn-lg>*show bgp ipv4 u 8.45.162.0/24 <http://8.45.162.0/24>* > BGP routing table entry for 8.45.162.0/24, version 170 > Paths: (2 available, best #1, table default) > Not advertised to any peer > Refresh Epoch 1 > 6939 46887 395343 395343 395343 > 206.108.255.52 from 206.108.255.1 (206.108.255.1) > Origin IGP, metric 265, localpref 100, valid, external, best > Community: 0:2906 0:12989 0:13335 0:15133 0:15169 0:16509 0:20940 > 0:22822 0:36040 > Refresh Epoch 1 > 6939 46887 395343 395343 395343 > 206.108.255.52 from 206.108.255.2 (206.108.255.2) > Origin IGP, metric 265, localpref 100, valid, external > Community: 0:2906 0:12989 0:13335 0:15133 0:15169 0:16509 0:20940 > 0:22822 0:36040 > micemn-lg> > > > > > ------------------------------ > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of David > Farmer <farmer(a)UMN.EDU> > *Sent:* Friday, January 5, 2018 12:13 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] MICE Looking Glass router > > The MICE Looking Glass router doesn't seem to be supporting 4-byte ASNs. > > Could someone upgrade the code please. > > Thanks. > > > -- > =============================================== > David Farmer Email:farmer@umn.edu > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE > <https://maps.google.com/?q=2218+University+Ave+SE&entry=gmail&source=g> > Phone: 612-626-0815 <(612)%20626-0815> > Minneapolis, MN 55414-3029 Cell: 612-812-9952 <(612)%20812-9952> > =============================================== > > ------------------------------ > > 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 > -- =============================================== 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 ===============================================

Jan. 17, 2018

Re: UG 27 / MTA

by Reid Fishler

I can't make Wed after the show, I have to run out back to NY. Reid On Jan 17, 2018 1:07 PM, "Richard Laager" <rlaager(a)wiktel.com> wrote: MTA has agreed to give us a table across from the registration desk. Ideally, we would have someone sit there to talk about MICE with anyone interested. Here are the MTA registration times: Monday, March 26 - 12:00 pm - 6:30 pm Tuesday, March 27 - 7:30 am - 5:00 pm Wednesday, March 28 - 7:30 am - 12:00 pm I'd imagine most people will be registering on Monday or early Tuesday. I'm happy to sit there, but our UG 27 meeting is currently scheduled for Monday at 3:00, which pretty much shoots the whole Monday timeslot. At best, I could setup some things on the table and then rush to 511 for the UG meeting. One option is to move the UG meeting to Tuesday, March 27 at 3:00. This would allow me (and/or anyone else interested) to sit at the MICE table on Monday afternoon and Tuesday morning. On the other hand, if someone was planning on attending both MTA and UG 27, it seems like this would create a conflict. Another option would be to leave the meeting as is, and have someone else (who would skip the UG meeting) volunteer to sit at the table on Monday. A third option would be to reschedule the UG meeting to Wednesday, after MTA concludes. How do you feel about these options? Any other suggestions? -- Richard

Jan. 17, 2018

Re: MICE Looking Glass router

by Justin Krejci

David, ask and thou shall receive, so sayeth Anthony, Jeremy, Doug and Justin.... micemn-lg>show bgp ipv4 u 8.45.162.0/24 BGP routing table entry for 8.45.162.0/24, version 170 Paths: (2 available, best #1, table default) Not advertised to any peer Refresh Epoch 1 6939 46887 395343 395343 395343 206.108.255.52 from 206.108.255.1 (206.108.255.1) Origin IGP, metric 265, localpref 100, valid, external, best Community: 0:2906 0:12989 0:13335 0:15133 0:15169 0:16509 0:20940 0:22822 0:36040 Refresh Epoch 1 6939 46887 395343 395343 395343 206.108.255.52 from 206.108.255.2 (206.108.255.2) Origin IGP, metric 265, localpref 100, valid, external Community: 0:2906 0:12989 0:13335 0:15133 0:15169 0:16509 0:20940 0:22822 0:36040 micemn-lg> ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of David Farmer <farmer(a)UMN.EDU> Sent: Friday, January 5, 2018 12:13 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE Looking Glass router The MICE Looking Glass router doesn't seem to be supporting 4-byte ASNs. Could someone upgrade the code please. Thanks. -- =============================================== David Farmer Email:farmer@umn.edu<mailto:Email%3Afarmer@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 =============================================== ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 17, 2018

UG 27 / MTA

by Richard Laager

MTA has agreed to give us a table across from the registration desk. Ideally, we would have someone sit there to talk about MICE with anyone interested. Here are the MTA registration times: Monday, March 26 - 12:00 pm - 6:30 pm Tuesday, March 27 - 7:30 am - 5:00 pm Wednesday, March 28 - 7:30 am - 12:00 pm I'd imagine most people will be registering on Monday or early Tuesday. I'm happy to sit there, but our UG 27 meeting is currently scheduled for Monday at 3:00, which pretty much shoots the whole Monday timeslot. At best, I could setup some things on the table and then rush to 511 for the UG meeting. One option is to move the UG meeting to Tuesday, March 27 at 3:00. This would allow me (and/or anyone else interested) to sit at the MICE table on Monday afternoon and Tuesday morning. On the other hand, if someone was planning on attending both MTA and UG 27, it seems like this would create a conflict. Another option would be to leave the meeting as is, and have someone else (who would skip the UG meeting) volunteer to sit at the table on Monday. A third option would be to reschedule the UG meeting to Wednesday, after MTA concludes. How do you feel about these options? Any other suggestions? -- Richard

Jan. 17, 2018

Please Welcome Coloplast to MICE!

by Jason Hanke

Name: Coloplast Port: ge-0/0/19 (Copper Main) ASN: 25111 IPv4: 206.108.255.91/24 IPv6: 2001:504:27:0:0:6217::1/64 Peering Contact: plmgaw(a)coloplast.com Route Server: Yes BFD: NO Please update your peeringdb information as soon as you have the chance. Thanks! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

Jan. 16, 2018

Re: MICE route reflect hiccup last night?

by Doug McIntyre

It is set for missing 3 BFD updates will drop it, but I believe an error condition like "invalid flags (248)" is what caused the issue. I don't see any flags in RFC5880, I suspect source code reading would be next to see what BIRD thought of flags in BFD that aren't mentioned in the RFC. On Tue, Jan 09, 2018 at 10:07:17PM +0000, Frank Bulk wrote: >Thanks. This is why BFD can be so frustrating. So just one bad packet and the BFD session was torn down? Or three in a row? > >Frank > >-----Original Message----- >From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre >Sent: Tuesday, January 09, 2018 3:08 PM >To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >Subject: Re: [MICE-DISCUSS] MICE route reflect hiccup last night? > >On Tue, Jan 09, 2018 at 08:25:44PM +0000, Frank Bulk wrote: >>Our logs show that MICE RR #1 had a hiccup overnight ... none of our other BGP sessions to MICE were interrupted. Did something scheduled happened? > >No, but your BFD session received.. > >2018-01-09 03:41:40 <RMT> bfd1: Bad packet from 206.108.255.67 - invalid flags (248) > >That's all I've got related to it in the logs. > >-- >Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades > -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Jan. 10, 2018

Re: MICE route reflect hiccup last night?

by Frank Bulk

Thanks. This is why BFD can be so frustrating. So just one bad packet and the BFD session was torn down? Or three in a row? Frank -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Tuesday, January 09, 2018 3:08 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE route reflect hiccup last night? On Tue, Jan 09, 2018 at 08:25:44PM +0000, Frank Bulk wrote: >Our logs show that MICE RR #1 had a hiccup overnight ... none of our other BGP sessions to MICE were interrupted. Did something scheduled happened? No, but your BFD session received.. 2018-01-09 03:41:40 <RMT> bfd1: Bad packet from 206.108.255.67 - invalid flags (248) That's all I've got related to it in the logs. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Jan. 9, 2018

Re: MICE route reflect hiccup last night?

by Doug McIntyre

On Tue, Jan 09, 2018 at 08:25:44PM +0000, Frank Bulk wrote: >Our logs show that MICE RR #1 had a hiccup overnight ... none of our other BGP sessions to MICE were interrupted. Did something scheduled happened? No, but your BFD session received.. 2018-01-09 03:41:40 <RMT> bfd1: Bad packet from 206.108.255.67 - invalid flags (248) That's all I've got related to it in the logs. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Jan. 9, 2018