Likely no longer an issue, and just seeing this thread - but a couple of thoughts if others face a similar issue: The key thing to remember is that the MX will operate as a router / firewall just fine without cloud access ONCE CONFIGURED - your primary issue is/was just that you needed to get the initial configuration on it. Of course, the long term solution must include getting access to the internet for the MX - but there's 'then' and there's 'now'. @Tat0rt0t nailed what I was going to suggest, but I'll throw in an alternate angle: - Take the MX84 home one night if you can - Plug it into your internet connection (behind your home firewall, let it pull a DHCP address that will be NAT'ed to the internet) - Configure the 84 with basic connectivity / static IPs you intend to use, etc. (you would need to configure your home router with a custom NAT which would allow it to pass traffic (may have to call it a 'DMZ Host') to that internal/static IP (your intended 10.x.x.18 you plan to take from the ASA); ** This gets the device configurable / configured as you will be deploying it ** - Identify if the ASA is running a dynamic routing protocol (OSPF or BGP peering, etc.) that you will need to emulate in the MX config, and build that config as necessary in the MX (to talk to the 29xx router - though I think you said ASA was just dumping to default gateway) - After that, the MX should be configured exactly as it would need to be for your final installation - Take device to the office, drop out the ASA in your outage window, plug in the MX, and everything should behave as required, assuming the firewall rules were properly configured, etc. - THEN... plug in a USB or Cellular to ethernet transceiver to act as your 'out of band' cloud management link, while the MX sends all actual traffic out the GigE port You could reverse this process / eliminate the 'take home' phase if you did the transceiver first and used it from the start. But this is an alternative to getting things moving. Cheers.
... View more