- mice-discuss - lists.micemn.net

Re: Update PTR

by Frank Bulk

Great, thank you. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Doug McIntyre Sent: Wednesday, November 18, 2020 5:00 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Update PTR On Wed, Nov 18, 2020 at 10:02:16PM +0000, Frank Bulk wrote: >Premier is no longer a part of MICE. > >Can the PTR for 206.108.255.67 be updated so that it doesn't list AS53347.micemn.net? Okay, that is done. I also removed the IPv6 reverse that was setup as well.

Nov. 20, 2020

Re: Update PTR

by Doug McIntyre

On Wed, Nov 18, 2020 at 10:02:16PM +0000, Frank Bulk wrote: >Premier is no longer a part of MICE. > >Can the PTR for 206.108.255.67 be updated so that it doesn't list AS53347.micemn.net? Okay, that is done. I also removed the IPv6 reverse that was setup as well.

Nov. 18, 2020

Update PTR

by Frank Bulk

Premier is no longer a part of MICE. Can the PTR for 206.108.255.67 be updated so that it doesn't list AS53347.micemn.net? Thanks, Frank

Nov. 18, 2020

Re: PeeringDB Audit Emails

by Jay Hanke

Yes, we have been through this process without progress. :( On Wed, Nov 18, 2020 at 2:56 PM James Urwiller <james.urwiller(a)turnkey-telecom.com> wrote: > > After talking to a few people at Zayo through normal support channels. They > said that an email has to be sent to peering(a)zayo.com to get this the > visibility it needs. Sorry I couldn’t get any further with this! > > James Urwiller > Network Architect > Stealth Broadband > james.urwiller(a)stealthbroadband.com > > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke > Sent: Wednesday, November 18, 2020 11:52 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] PeeringDB Audit Emails > > I've gotten several emails from MICE members about IX-F export issues on > PeeringDB. > > MICE provides a list of port/peering information to PeeringDB in JSON format > and they started auditing against what users have entered into the site. The > export is generated from our IXP Manager platform we deployed a couple > months ago. > > The most common mismatch is the user not having the IPv6 address loaded in > PeeringDB. MICE allocates an IPv6 address with every IPv4 allocation. > [insert ipv6 pitch here] > > Members on the Zayo Remote switch in Belle Plaine are currently not > currently included in the export. There is an issue with loading the ports > into IXP manager and we need an admin at Zayo to make a couple of > routing/snmp changes. All of the other switches were completed and loaded > several months ago. > > If someone has a good contact at Zayo for this please let me know. > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 18, 2020

Re: PeeringDB Audit Emails

by James Urwiller

After talking to a few people at Zayo through normal support channels. They said that an email has to be sent to peering(a)zayo.com to get this the visibility it needs. Sorry I couldn’t get any further with this! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Wednesday, November 18, 2020 11:52 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] PeeringDB Audit Emails I've gotten several emails from MICE members about IX-F export issues on PeeringDB. MICE provides a list of port/peering information to PeeringDB in JSON format and they started auditing against what users have entered into the site. The export is generated from our IXP Manager platform we deployed a couple months ago. The most common mismatch is the user not having the IPv6 address loaded in PeeringDB. MICE allocates an IPv6 address with every IPv4 allocation. [insert ipv6 pitch here] Members on the Zayo Remote switch in Belle Plaine are currently not currently included in the export. There is an issue with loading the ports into IXP manager and we need an admin at Zayo to make a couple of routing/snmp changes. All of the other switches were completed and loaded several months ago. If someone has a good contact at Zayo for this please let me know. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 18, 2020

Re: PeeringDB Audit Emails

by James Urwiller

I have zero good contacts there.. I will just create a service ticket and see where it gets me James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Wednesday, November 18, 2020 11:52 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] PeeringDB Audit Emails I've gotten several emails from MICE members about IX-F export issues on PeeringDB. MICE provides a list of port/peering information to PeeringDB in JSON format and they started auditing against what users have entered into the site. The export is generated from our IXP Manager platform we deployed a couple months ago. The most common mismatch is the user not having the IPv6 address loaded in PeeringDB. MICE allocates an IPv6 address with every IPv4 allocation. [insert ipv6 pitch here] Members on the Zayo Remote switch in Belle Plaine are currently not currently included in the export. There is an issue with loading the ports into IXP manager and we need an admin at Zayo to make a couple of routing/snmp changes. All of the other switches were completed and loaded several months ago. If someone has a good contact at Zayo for this please let me know. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 18, 2020

PeeringDB Audit Emails

by Jay Hanke

I've gotten several emails from MICE members about IX-F export issues on PeeringDB. MICE provides a list of port/peering information to PeeringDB in JSON format and they started auditing against what users have entered into the site. The export is generated from our IXP Manager platform we deployed a couple months ago. The most common mismatch is the user not having the IPv6 address loaded in PeeringDB. MICE allocates an IPv6 address with every IPv4 allocation. [insert ipv6 pitch here] Members on the Zayo Remote switch in Belle Plaine are currently not currently included in the export. There is an issue with loading the ports into IXP manager and we need an admin at Zayo to make a couple of routing/snmp changes. All of the other switches were completed and loaded several months ago. If someone has a good contact at Zayo for this please let me know. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 18, 2020

IPv6 BGP Peering to Netflix bouncing 60+ days

by Jesse Reed

All: We have been tracking our IPv6 peering via our MICE path to Netflix and noticed it bouncing consistently since at least September (probably longer). All other peerings on this path (both v4 and v6) have been stable and are not experiencing these drops. Is anyone else in the group experiencing similar drops to their IPv6 only peerings w/Netflix? The peer that we see this occurring w/is: 2001:504:27::b5a:0:1 Thanks so much ahead of time, Jesse

Nov. 18, 2020

SFN Remote Switch Backhaul Upgrade

by Jay Hanke

Please allocate Ethernet1/1 on the MN VoIP 100G remote switch for a new SFN remote uplink. When completed the link from the SFN Remote switch will increase from 40G to 100G. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Nov. 13, 2020

Re: Nuvera Upgrade to 1x4x10G

by Doug McIntyre

On Thu, Nov 12, 2020 at 12:00:18PM -0600, Jay Hanke wrote: >Please allocate and add the following ports to the existing Nuvera LAG group. > >Ethernet4/14 >Ethernet5/14 > >The new group will be 4x10G I added the two ether interfaces to the existing LAG on PC33. This is complete and waiting for their circuits to be installed.

Nov. 12, 2020