- mice-discuss - lists.micemn.net

Re: UG 13 Minutes

by Doug McIntyre

On Thu, Jul 24, 2014 at 05:57:46PM -0500, Doug McIntyre wrote: > On Thu, Jul 24, 2014 at 05:34:15PM -0500, Shaun Carlson wrote: > > Both of the public MICE lists appear to have broken archives at lists.iphouse.net since May. Is there someone that can take a peek at this? > > Sure, I'll look into the issue. > (Nothing amiss on the system AFAIK, it'll take a deeper view to find). This is fixed up now. Sorry some variables got reset on the last software updates. :-( (but the list has a method for DMARC delivery type issues if needed). -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

July 25, 2014

Re: UG 13 Minutes

by Hannigan, Martin

Thanks Shaun! Best, -M< On Jul 24, 2014, at 6:35 PM, Shaun Carlson <shaun.carlson(a)ARVIG.COM> wrote: > Marty, > > To date, our policy has been to not fund the transit requirements and our plan is to maintain that position. We did not vote one way or another as we did not meet quorum requirements. > > s > > Shaun Carlson > Network Engineering Manager | Arvig > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > On July 24, 2014 at 16:31:09 CDT, Hannigan, Martin <marty(a)akamai.com> wrote: >> >> >> Its not entirely clear from the minutes; did the members vote for or against funding googles transit requirement? >> >> Best, >> >> -M< >> >> >> >> On Jul 24, 2014, at 5:23 PM, Shaun Carlson wrote: >> >> > Please see attached, send me any corrections or updates. >> > >> > As an important note: >> > >> > The next meeting will be on Wednesday, October 22nd from 4pm to 7pm at the 511 Building; please mark your calendars now and plan on being there! >> > >> > Thanks and see you all in October! >> > >> > s >> > >> > Shaun Carlson >> > Network Engineering Manager | Arvig >> > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com >> > >> > To unsubscribe from the MICE-DISCUSS list, click the following link: >> > ?SUBED1=MICE-DISCUSS&A=1 >> > >> > >> >> >> ######################################################################## >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> ?SUBED1=MICE-DISCUSS&A=1 > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 >

July 25, 2014

Open-IX OIX-1 Was: Re: [MICE-DISCUSS] MICE MTU

by Hannigan, Martin

Btw, I would like to see PVLAN implemented if possible. It's not just for big IXPs, its for all. And MICE is getting big regardless. The compliance pieces fit well here IMHO. OIX-1 is an open standard; IXP's can choose to either be compliant or be certified. Ether way, it's open and recommended. Best, -M< On Jul 24, 2014, at 10:12 PM, "Hannigan, Martin" <marty(a)AKAMAI.COM> wrote: > > > Generally, the general IXP community has determined that the minimum exchange services configuration should be: > > http://www.open-ix.org/certification/ixp-technical-requirements/ > > If we all thought it was desired as a minimum configuration at an IXP, it would've made it in there IMHO. It didn't. If someone thinks all IXPs should do this, they should take a run at this and see if they can get the rest of the IXP community to support it (Not just Netnod and NASA). > > We have the same issue as Andrew, and we have zero interest to go to an MTU of 9000. > > > Best, > > -M< > > > > > On Jul 24, 2014, at 6:29 PM, "Koch, Andrew" <andrew.koch(a)TDSTELECOM.COM> wrote: > >> The UG 13 minutes make note that the exchange MTU is 9000 bytes. Are other members configuring their routers for an MTU of 9000? >> >> I ask as TDS has not - we have stuck with the Ethernet standard 1500 bytes. If anyone on the exchange has set an MTU of 9000 and tries to send jumbo traffic to us, it will not be accepted and no indication will be sent back to the originator. (10d in the linked document below) >> >> If no one (or few) has setup their routers for an MTU of 9000, but we as a community wish to enable this, I would recommend that we schedule a flag day so that we can minimize blackholing of traffic across the exchange. >> >> While only a draft, see http://tools.ietf.org/html/draft-mlevy-ixp-jumboframes-00 for further information on IXP Jumbo Frame operation and conversion. For those that like presentations more than IETF drafts, Martin Levy (of Hurricane Electric at the time) presented this at RIPE 64 - https://ripe64.ripe.net/presentations/139-Hurricane_Electric_-_Martin_Levy_… >> >> >> Best Regards, >> >> Andy Koch >> TDS Telecom - IP Network Operations >> andrew.koch(a)tdstelecom.com >> Desk: 608-664-4694 >> Cell: 608-616-0072 >> >> >> >> ######################################################################## >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> ?SUBED1=MICE-DISCUSS&A=1 >

July 25, 2014

Re: MICE MTU

by Hannigan, Martin

Generally, the general IXP community has determined that the minimum exchange services configuration should be: http://www.open-ix.org/certification/ixp-technical-requirements/ If we all thought it was desired as a minimum configuration at an IXP, it would've made it in there IMHO. It didn't. If someone thinks all IXPs should do this, they should take a run at this and see if they can get the rest of the IXP community to support it (Not just Netnod and NASA). We have the same issue as Andrew, and we have zero interest to go to an MTU of 9000. Best, -M< On Jul 24, 2014, at 6:29 PM, "Koch, Andrew" <andrew.koch(a)TDSTELECOM.COM> wrote: > The UG 13 minutes make note that the exchange MTU is 9000 bytes. Are other members configuring their routers for an MTU of 9000? > > I ask as TDS has not - we have stuck with the Ethernet standard 1500 bytes. If anyone on the exchange has set an MTU of 9000 and tries to send jumbo traffic to us, it will not be accepted and no indication will be sent back to the originator. (10d in the linked document below) > > If no one (or few) has setup their routers for an MTU of 9000, but we as a community wish to enable this, I would recommend that we schedule a flag day so that we can minimize blackholing of traffic across the exchange. > > While only a draft, see http://tools.ietf.org/html/draft-mlevy-ixp-jumboframes-00 for further information on IXP Jumbo Frame operation and conversion. For those that like presentations more than IETF drafts, Martin Levy (of Hurricane Electric at the time) presented this at RIPE 64 - https://ripe64.ripe.net/presentations/139-Hurricane_Electric_-_Martin_Levy_… > > > Best Regards, > > Andy Koch > TDS Telecom - IP Network Operations > andrew.koch(a)tdstelecom.com > Desk: 608-664-4694 > Cell: 608-616-0072 > > > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1

July 25, 2014

Re: UG 13 Minutes

by Doug McIntyre

On Thu, Jul 24, 2014 at 05:34:15PM -0500, Shaun Carlson wrote: > Both of the public MICE lists appear to have broken archives at lists.iphouse.net since May. Is there someone that can take a peek at this? Sure, I'll look into the issue. (Nothing amiss on the system AFAIK, it'll take a deeper view to find). > A final item on the mailing lists - there is a footer appended to every message sent. The footer indicates that unsubscribe is available by clicking on a link, but there is not a functional URL. This footer also breaks any PGP signed messages as it modifies the message part. If possible, can this be removed or fixed and relocated to the message headers? I think it was supposed to generate HTML on an HTML style feed, but this is a text style feed. I've removed it rather than to reword it for text-processing. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

July 24, 2014

Re: UG 13 Minutes

by Shaun Carlson

Marty, To date, our policy has been to not fund the transit requirements and our plan is to maintain that position. We did not vote one way or another as we did not meet quorum requirements. s Shaun CarlsonNetwork Engineering Manager | Arvigph: (218) 346-8673 | em: shaun.carlson(a)arvig.com Its not entirely clear from the minutes; did the members vote for or against funding googles transit requirement? Best, -M< On Jul 24, 2014, at 5:23 PM, Shaun Carlson <shaun.carlson(a)ARVIG.COM> wrote: > Please see attached, send me any corrections or updates. > > As an important note: > > The next meeting will be on Wednesday, October 22nd from 4pm to 7pm at the 511 Building; please mark your calendars now and plan on being there! > > Thanks and see you all in October! > > s > > Shaun Carlson > Network Engineering Manager | Arvig > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > > <MICE UG 13 - Minutes.pdf> ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: UG 13 Minutes

by Shaun Carlson

Thanks Andy, those issues are what prompted this discussion. I'll see that we get them addressed. s Shaun CarlsonNetwork Engineering Manager | Arvigph: (218) 346-8673 | em: shaun.carlson(a)arvig.com A comment in regards to the mailing lists and meeting notices: I believe that we want to have as many participants as possible. As such, meeting notices, agendas and minutes should always be sent to MICE-ANNOUNCE, which may have folks that don't want the increased volume that -DISCUSS has, but still wish to be participants. None of the meeting emails for this UG appear to have been sent to -ANNOUNCE (at least none were received at the address I had subscribed with). Both of the public MICE lists appear to have broken archives at lists.iphouse.net since May. Is there someone that can take a peek at this? A final item on the mailing lists - there is a footer appended to every message sent. The footer indicates that unsubscribe is available by clicking on a link, but there is not a functional URL. This footer also breaks any PGP signed messages as it modifies the message part. If possible, can this be removed or fixed and relocated to the message headers? Thanks, Andy Koch TDS Telecom - IP Network Operations andrew.koch(a)tdstelecom.com Desk: 608-664-4694 Cell: 608-616-0072 > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of > Shaun Carlson > Sent: Thursday, July 24, 2014 16:24 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] UG 13 Minutes > > Please see attached, send me any corrections or updates. > > As an important note: > > The next meeting will be on Wednesday, October 22nd from 4pm to 7pm at the > 511 Building; please mark your calendars now and plan on being there! > > Thanks and see you all in October! > > s > > Shaun Carlson > Network Engineering Manager | Arvig > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > > ________________________________ > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

MICE MTU

by Koch, Andrew

The UG 13 minutes make note that the exchange MTU is 9000 bytes. Are other members configuring their routers for an MTU of 9000? I ask as TDS has not - we have stuck with the Ethernet standard 1500 bytes. If anyone on the exchange has set an MTU of 9000 and tries to send jumbo traffic to us, it will not be accepted and no indication will be sent back to the originator. (10d in the linked document below) If no one (or few) has setup their routers for an MTU of 9000, but we as a community wish to enable this, I would recommend that we schedule a flag day so that we can minimize blackholing of traffic across the exchange. While only a draft, see http://tools.ietf.org/html/draft-mlevy-ixp-jumboframes-00 for further information on IXP Jumbo Frame operation and conversion. For those that like presentations more than IETF drafts, Martin Levy (of Hurricane Electric at the time) presented this at RIPE 64 - https://ripe64.ripe.net/presentations/139-Hurricane_Electric_-_Martin_Levy_… Best Regards, Andy Koch TDS Telecom - IP Network Operations andrew.koch(a)tdstelecom.com Desk: 608-664-4694 Cell: 608-616-0072 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: UG 13 Minutes

by Reid Fishler

The exchange does not provide transit for anyone. If any exchange member decides to provide service that is of the own volition, but the exchange doesn't provide anything more than exchange services. Reid On Jul 24, 2014 4:31 PM, "Hannigan, Martin" <marty(a)akamai.com> wrote: > > > Its not entirely clear from the minutes; did the members vote for or > against funding googles transit requirement? > > Best, > > -M< > > > > On Jul 24, 2014, at 5:23 PM, Shaun Carlson <shaun.carlson(a)ARVIG.COM> > wrote: > > > Please see attached, send me any corrections or updates. > > > > As an important note: > > > > The next meeting will be on Wednesday, October 22nd from 4pm to 7pm at > the 511 Building; please mark your calendars now and plan on being there! > > > > Thanks and see you all in October! > > > > s > > > > Shaun Carlson > > Network Engineering Manager | Arvig > > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > > ?SUBED1=MICE-DISCUSS&A=1 > > > > <MICE UG 13 - Minutes.pdf> > > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: UG 13 Minutes

by Koch, Andrew

A comment in regards to the mailing lists and meeting notices: I believe that we want to have as many participants as possible. As such, meeting notices, agendas and minutes should always be sent to MICE-ANNOUNCE, which may have folks that don't want the increased volume that -DISCUSS has, but still wish to be participants. None of the meeting emails for this UG appear to have been sent to -ANNOUNCE (at least none were received at the address I had subscribed with). Both of the public MICE lists appear to have broken archives at lists.iphouse.net since May. Is there someone that can take a peek at this? A final item on the mailing lists - there is a footer appended to every message sent. The footer indicates that unsubscribe is available by clicking on a link, but there is not a functional URL. This footer also breaks any PGP signed messages as it modifies the message part. If possible, can this be removed or fixed and relocated to the message headers? Thanks, Andy Koch TDS Telecom - IP Network Operations andrew.koch(a)tdstelecom.com Desk: 608-664-4694 Cell: 608-616-0072 > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of > Shaun Carlson > Sent: Thursday, July 24, 2014 16:24 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] UG 13 Minutes > > Please see attached, send me any corrections or updates. > > As an important note: > > The next meeting will be on Wednesday, October 22nd from 4pm to 7pm at the > 511 Building; please mark your calendars now and plan on being there! > > Thanks and see you all in October! > > s > > Shaun Carlson > Network Engineering Manager | Arvig > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > > ________________________________ > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: UG 13 Minutes

by Hannigan, Martin

Its not entirely clear from the minutes; did the members vote for or against funding googles transit requirement? Best, -M< On Jul 24, 2014, at 5:23 PM, Shaun Carlson <shaun.carlson(a)ARVIG.COM> wrote: > Please see attached, send me any corrections or updates. > > As an important note: > > The next meeting will be on Wednesday, October 22nd from 4pm to 7pm at the 511 Building; please mark your calendars now and plan on being there! > > Thanks and see you all in October! > > s > > Shaun Carlson > Network Engineering Manager | Arvig > ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > > <MICE UG 13 - Minutes.pdf> ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

UG 13 Minutes

by Shaun Carlson

Please see attached, send me any corrections or updates. As an important note: *The next meeting will be on Wednesday, October 22nd from 4pm to 7pm at the 511 Building; please mark your calendars now and plan on being there!* Thanks and see you all in October! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: MICE Meeting Google Hangout

by Hannigan, Martin

hannigan(a)gmail.com On Jul 24, 2014, at 4:30 PM, Brady Kittel <bkittel(a)GMAIL.COM> wrote: > Can you invite bkittel(a)gmail.com too? > > On Jul 24, 2014 2:51 PM, "David Farmer" <farmer(a)umn.edu> wrote: > Please send me your email so I can invite you to the google hangout. > > -- > =============================================== > 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 > =============================================== > > > On Jul 24, 2014, at 14:24, Russell Berg <berg(a)wins.net> wrote: > >> Tried joining but it says the party is over. 8-( >> >> >> >> From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of David Farmer >> Sent: Thursday, July 24, 2014 2:12 PM >> To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> Subject: [MICE-DISCUSS] MICE Meeting Google Hangout >> >> >> >> we will get started shortly >> >> >> >> https://plus.google.com/hangouts/_/gvdyimpkvxef2lb3ua75qf4dnea >> >> >> >> -- >> =============================================== >> 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 >> =============================================== >> >> >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> ?SUBED1=MICE-DISCUSS&A=1 >> > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: MICE Meeting Google Hangout

by Levi Pederson

levipederson(a)mankatonetworks.net *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipederson(a)mankatonetworks.net On Thu, Jul 24, 2014 at 2:51 PM, David Farmer <farmer(a)umn.edu> wrote: > Please send me your email so I can invite you to the google hangout. > > -- > =============================================== > 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 > =============================================== > > > On Jul 24, 2014, at 14:24, Russell Berg <berg(a)wins.net> wrote: > > Tried joining but it says the party is over. 8-( > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET > <MICE-DISCUSS(a)LISTS.IPHOUSE.NET>] *On Behalf Of *David Farmer > *Sent:* Thursday, July 24, 2014 2:12 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] MICE Meeting Google Hangout > > > > we will get started shortly > > > > https://plus.google.com/hangouts/_/gvdyimpkvxef2lb3ua75qf4dnea > > > > -- > =============================================== > 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 > =============================================== > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: MICE Meeting Google Hangout

by Brady Kittel

Can you invite bkittel(a)gmail.com too? On Jul 24, 2014 2:51 PM, "David Farmer" <farmer(a)umn.edu> wrote: > Please send me your email so I can invite you to the google hangout. > > -- > =============================================== > 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 > =============================================== > > > On Jul 24, 2014, at 14:24, Russell Berg <berg(a)wins.net> wrote: > > Tried joining but it says the party is over. 8-( > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET > <MICE-DISCUSS(a)LISTS.IPHOUSE.NET>] *On Behalf Of *David Farmer > *Sent:* Thursday, July 24, 2014 2:12 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] MICE Meeting Google Hangout > > > > we will get started shortly > > > > https://plus.google.com/hangouts/_/gvdyimpkvxef2lb3ua75qf4dnea > > > > -- > =============================================== > 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 > =============================================== > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: MICE Meeting Google Hangout

by Russell Berg

Sounding and looking good, but can the camera be easily tipped downward a bit… seeing foreheads and hairlines. Thanks! From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of David Farmer Sent: Thursday, July 24, 2014 2:51 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] MICE Meeting Google Hangout Please send me your email so I can invite you to the google hangout. -- =============================================== David Farmer Email:farmer@umn.edu<http://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 =============================================== On Jul 24, 2014, at 14:24, Russell Berg <berg(a)wins.net<mailto:berg@wins.net>> wrote: Tried joining but it says the party is over. 8-( From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of David Farmer Sent: Thursday, July 24, 2014 2:12 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] MICE Meeting Google Hangout we will get started shortly https://plus.google.com/hangouts/_/gvdyimpkvxef2lb3ua75qf4dnea -- =============================================== 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: ?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Re: MICE Meeting Google Hangout

by David Farmer

Please send me your email so I can invite you to the google hangout. -- =============================================== 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 =============================================== > On Jul 24, 2014, at 14:24, Russell Berg <berg(a)wins.net> wrote: > > Tried joining but it says the party is over. 8-( > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of David Farmer > Sent: Thursday, July 24, 2014 2:12 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] MICE Meeting Google Hangout > > we will get started shortly > > https://plus.google.com/hangouts/_/gvdyimpkvxef2lb3ua75qf4dnea > > -- > =============================================== > 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 > =============================================== > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

MICE Meeting Google Hangout

by David Farmer

we will get started shortly https://plus.google.com/hangouts/_/gvdyimpkvxef2lb3ua75qf4dnea -- =============================================== 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 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 24, 2014

Meeting Reminder and Agenda

by Shaun Carlson

All, Just a quick, last reminder of our meeting tomorrow *Date*: Thursday, July 24th *Time*: 2:00 pm (1400 Hours) David Farmer has the facility reserved until 5PM *Location*: University of Minnesota, Duluth campus, Griggs Center, located in the Kirby Student Center (KSC) http://www.d.umn.edu/maps/KSC/ We have discussed a web attendance option. I don't have that information handy right now and I'll send it as soon as I get confirmation. Attached is the current agenda, if you have any other items you would like added to the agenda, please drop me a note prior to the meeting and I'll get them on there! Thanks and see you tomorrow! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 23, 2014

Re: Agenda Items - Last Call

by Doug McIntyre

On Tue, Jul 22, 2014 at 03:10:21PM -0500, Richard Laager wrote: > I'm not attending*, but maybe others should discuss the IPv6 numbering > plan? Specifically: should we be putting the ASN bytes at the end of the > IPv6 address for multicast group reasons? I'm sorry, but I'm trying to understand the "problem". (I'm not the one who originally suggested the layout, but did initially redeploy the IPv6 addressing from the borrowed addressing. First off, we are talking about a total of 26 IPv6 end-points. Maybe if MICE grows a lot, we'll double that? Up to 52 end-points? >From what I've read on it, the purpose of the multicast group mainly is to break up the ND announcements into separate smaller groups, since ARP broadcasts on truely huge networks can get to be quite large and problematic when you have 10,000 hosts responding. As far as I can tell, the purpose of the multicast group grouping the lowest 24bits is not to put each endpoint into its own multicast group, but only to break it up into smaller and more manageable traffic bursts in order to avoid the multi-megabit ARP storms that can happen on truely huge networks. Either way, we are talking about a potential of 26 hosts reponding to ND requests. The only problem I see is that somebody following a CoPP guide that put the ND policing limit at too low of a limit is saying that he is getting more ND traffic than his CoPP guide suggests. Am I totally confused about this? -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 22, 2014

Re: Agenda Items - Last Call

by Reid Fishler

I think there is a web based option...Also, you wont be there?! What is a MICE meeting without you? :-P Reid On Tue, Jul 22, 2014 at 4:10 PM, Richard Laager <rlaager(a)wiktel.com> wrote: > On Tue, 2014-07-22 at 08:43 -0500, Shaun Carlson wrote: > > > Please send any additional agenda (business, technical or discussion) > > items you may have. I plan to have the Agenda out this afternoon for > > Thursday's meeting. > > I'm not attending*, but maybe others should discuss the IPv6 numbering > plan? Specifically: should we be putting the ASN bytes at the end of the > IPv6 address for multicast group reasons? > > * At least not in person. Was there going to be any sort of remote > option? > > -- > Richard > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > > -- Reid Fishler Director Hurricane Electric +1-510-580-4178 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 22, 2014

Re: Agenda Items - Last Call

by Richard Laager

On Tue, 2014-07-22 at 08:43 -0500, Shaun Carlson wrote: > Please send any additional agenda (business, technical or discussion) > items you may have. I plan to have the Agenda out this afternoon for > Thursday's meeting. I'm not attending*, but maybe others should discuss the IPv6 numbering plan? Specifically: should we be putting the ASN bytes at the end of the IPv6 address for multicast group reasons? * At least not in person. Was there going to be any sort of remote option? -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 22, 2014

Re: Agenda Items - Last Call

by Justin Krejci

AS10242 - zero attending Agenda item I recommend - application of the variously discussed MICE switch security policy configurations for storm controls, mac learning limits, L2 bpdu handling, etc. ________________________________ From: MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] on behalf of Shaun Carlson [shaun.carlson(a)ARVIG.COM] Sent: Tuesday, July 22, 2014 8:43 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Agenda Items - Last Call All, Please send any additional agenda (business, technical or discussion) items you may have. I plan to have the Agenda out this afternoon for Thursday's meeting. Also, one more quick reminder. If you haven't responded yet, please let me know your AS and number of people attending. Thanks! s Shaun Carlson Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com<mailto:shaun.carlson@arvig.com> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1<UrlBlockedError.aspx> ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 22, 2014

Agenda Items - Last Call

by Shaun Carlson

All, Please send any additional agenda (business, technical or discussion) items you may have. I plan to have the Agenda out this afternoon for Thursday's meeting. Also, one more quick reminder. If you haven't responded yet, please let me know your AS and number of people attending. Thanks! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 22, 2014

Re: IPv6 neighbor solicitation at the exchange

by James Stahr

On 07/18/2014 2:06 PM, Rob Mosher wrote: > You shouldn't be grouping neighbor discovery in the same rate limits > as other type of icmpv6. If someone starts pinging your router at a > high rate Echo/echo-reply isn't handled in this section. > or if there is a routing loop that generates a bunch of time exceeded > messages it will cause your neighbor discovery to fail and will be > unable to reach your peers. Those are just two examples, but you > really need neighbor discovery to be handled elsewhere. > Time exceeded's will only go back to the router originating the traffic so if there's a routing loop, the messages go back to the individual sources. It's unlikely that my router is going to generate a lot of traffic to cause ND to fail. And hopefully the upstream routers with the loop also has a policy to limit their time exceeded messages... Given the neighbor solicitations I'm seeing, I do think that this points out a 'flaw' in the exchange's IPv6 address assignments. It seems like we should be using hextet's 7 for16bit ASNs and hextets 6 and 7 for 32bit ASNs - I'm not sure if there is a policy for 32bit ASN IPv6 addressing as no one appears to have one yet. If anyone is interested, I used this as my basis for my IPv6 policy and I appear to have used smaller values policing values than what had been suggested: http://archiv.cesnet.cz/doc/techzpravy/2010/ipv6-copp/ipv6-copp.pdf > -- > Rob Mosher > Senior Network and Software Engineer > Hurricane Electric / AS6939 > > On 7/17/2014 5:07 PM, James Stahr wrote: >> First off, Did anyone make any changes on 07/15/2014 around 08:00? >> >> The reason is that I think I've resolved an issue with our IPv6 >> peering with the MICE route servers, Charter, and TDS and I'm looking >> for a larger audience to see if it's my issue or perhaps an issue at >> the exchange. I believe it to be the latter, but I'm not an IPv6 >> expert. >> >> Starting two days ago around 8am CDT, we started experiencing BGP >> timeouts on some of our IPv6 BGP sessions. I was able to work around >> the issue by removing our COPP policy and the BGP sessions were >> stable for 24 hours. Reapplied the policy, sessions started to drop >> again. Looked at the policy to see which category is being exceeded, >> it's not the routing section which allows BGP/BFD/etc, but the >> ICMP-v6 one: >> >> >> ipv6 access-list COPP-icmp-v6 >> remark ICMP type 1/3,2,3/0,3/1,4/0,4/1,4/2,130,143 >> permit icmp any any destination-unreachable >> permit icmp any any packet-too-big >> permit icmp any any time-exceeded >> permit icmp any any parameter-problem >> remark nd-na, nd-ns, ra, rs >> permit icmp any any nd-na >> permit icmp any any nd-ns >> permit icmp any any router-advertisement >> permit icmp any any router-solicitation >> remark MLD - query, report_v2 >> permit icmp any any mld-query >> permit icmp any any 143 >> >> >> which is being policed like this: >> >> class Icmp-v6 >> police 32000 60000 120000 conform-action transmit exceed-action drop >> >> I've worked around the issue by making a 4x increase in the policing, >> but the question I have is what happened at the exchange to provoke >> my COPP policy? Alternatively, is this normal or indicate who has >> the problem: >> >> >> >> r-pop-min-1#deb ipv6 icmp >> ICMP Packet debugging is on >> r-pop-min-1# >> Jul 17 14:36:08.143 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::56E0:3200:50CE:4178, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.281 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.281 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.285 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.359 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.433 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.435 CDT: ICMPv6: Sent N-Solicit, >> Src=FE80::CA4C:75FF:FE23:805, Dst=2001:504:27::8252:0:1 >> Jul 17 14:36:08.459 CDT: ICMPv6: Received N-Advert, >> Src=2001:504:27::8252:0:1, Dst=FE80::CA4C:75FF:FE23:805 >> Jul 17 14:36:08.535 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.535 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.539 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.559 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.586 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.617 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.687 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.782 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.783 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.783 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> r-pop-min-1# >> Jul 17 14:36:08.842 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:08.990 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.028 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.070 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.148 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.203 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.322 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.322 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.327 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.399 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.439 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.481 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.533 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.572 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.572 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.581 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.608 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::2E21:72FF:FE71:37B1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.613 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 >> r-pop-min-1# >> Jul 17 14:36:09.659 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:09.884 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.069 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.172 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.240 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.320 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.364 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.441 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.521 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.573 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.573 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.588 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.622 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.659 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.684 CDT: ICMPv6: Received N-Solicit, >> Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.817 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.853 CDT: ICMPv6: Received type 130, >> Src=FE80::21B:DFF:FEE7:15C0, Dst=FF02::1 >> r-pop-min-1# >> Jul 17 14:36:10.908 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> Jul 17 14:36:10.925 CDT: ICMPv6: Received N-Solicit, >> Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 >> >> I'm thinking that the answer is that this is not normal, as it looks >> like I'm getting duplicate solicitations in the same second. >> >> -James >> >> ######################################################################## >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> ?SUBED1=MICE-DISCUSS&A=1 > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > ?SUBED1=MICE-DISCUSS&A=1 > > ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

July 21, 2014