[AusNOG] Megaport/MegaIX Escalations

[Gavin Tweedie]

Hi Mitch,

Happy to help, can you send me an email with a ticket number/service
id/your company details or something to identify which peer you are. Or
even just forward me the support conversation and I'm happy to take a look.

Gavin



On Tue, 19 Mar 2019 at 12:56, Mitchell Zeglis <mwzeglis at gmail.com> wrote:

> Hi All,
>
> Has anyone had much experience dealing with Megaport/MegaIX's? I'm peering
> with MegaIX at a number of locations however having issues peering to them
> in Brisbane. I have identical configurations setup at all my other POPs yet
> in Brisbane just not having any such luck. We already have a cross-connect
> with them there with active VXCs but I'm working on setting up a peer with
> them for transit/MegaIX over this same cross-connect. For the IX peer I can
> see their MAC addresses and they can see me from a layer 2 perspective as
> well. I've got the correct MAC addresses reflected in the Megaport Portal
> for their ACL MAC whitelisting they do. However, I can't ping their route
> servers (RS's) on the addresses they've provided.They've given me the
> following addresses to allow me to use as remote peers on a specific vlan
> ID they gave me over our cross-connect: 103.26.70.1, 103.26.70.2,
> 2001:dea:0:20::1 and 2001:dea:0:20::2. Setting up my vlan interface with
> the address in the 103.26.70.0/24 space they've provided I get zero layer
> 3 Rx traffic from them and they have zero layer 3 rx traffic from me.
> ICMP/ping attempts (they confirmed their RS's will respond to ICMP) from my
> equipment whilst specifying the source address as the IP they wanted me to
> use in 103.26.70.0/24 and egress interface on the VLAN has no such luck,
> can't exactly run a traceroute on this either.
>
> What's weird though, is from LLDP and running packet captures I can
> actually see  2001:dea:0:20::1, but not the other IPv6 address (
> 2001:dea:0:20::2) or any of the IPv4 addresses. I've bounced my
> interfaces, rebooted my equipment, thrown the VLAN in an SVI of it's own
> and reflected the SVI MAC in the Megaport portal ACL MAC whitelist. Point
> is, I don't know what on earth is going on.
>
> I've reached out to Megaport support through the portal however, I'm going
> around in circles with them. They take days to respond sometimes, ask me
> questions I've already answered. They said they would lodge a ticket for
> the engineering team but I've seen nothing come of it. Anyone got any ideas
> or encountered something similar? Any help would be much appreciated.
>
> Cheers,
> Mitch
>
> --
> *Mitchell W. Zeglis*
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>


-- 
Global Interconnection Director
Megaport <https://www.megaport.com>
+61 498 498 458
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20190319/7d8c98d9/attachment.html>