 |
 |
Yes, we have been through this process without progress. :( On Wed, Nov 18, 2020 at 2:56 PM James Urwiller <[log in to unmask]> wrote: > > After talking to a few people at Zayo through normal support channels. They > said that an email has to be sent to [log in to unmask] to get this the > visibility it needs. Sorry I couldn’t get any further with this! > > James Urwiller > Network Architect > Stealth Broadband > [log in to unmask] > > > -----Original Message----- > From: MICE Discuss <[log in to unmask]> On Behalf Of Jay Hanke > Sent: Wednesday, November 18, 2020 11:52 > To: [log in to unmask] > 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 > [log in to unmask] > Phone 612-204-0000 -- Jay Hanke, President South Front Networks [log in to unmask] Phone 612-204-0000