Meraki

jdsilva · ‎Jun 21 2018

Basically it's telling you that the static IP config you gave it doesn't work, so it fell back to using a DHCP address on VLAN 1 to reach the cloud. https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Behavior_during_Connection_Loss_to_Cisco_Meraki_Cloud#MS So something's wrong with connectivity on your VLAN 903. Verify that the ports you have connected are configured to carry that VLAN the same way on both sides. Also, if you're changing the Mgmt VLAN from 1 then you should be changing that in Switch-->Configure-->Switch settings. https://documentation.meraki.com/MS/Deployment_Guides/Advanced_MS_Setup_Guide#Management_VLAN

jdsilva · ‎Jun 20 2018

Oh hell, I just thought of one more thing. By default MXes will created a DHCP scope for every subnet configured on them, and assign addresses to clients. If you have two MXes in two different Dashboard networks, they will both try and assign clients addresses with themselves as the gateway, and they could assign duplicate addresses to your clients. How are you handling DHCP on your LAN?

jdsilva · ‎Jun 19 2018

One other thought... Are there any redundant links here? The MXes do not run Spanning Tree so there's a risk of a loop if things aren't set up correctly. That may also explain your behaviour.

jdsilva · ‎Jun 19 2018

OK, I thought that's what you said above. just clarifying. Oddly enough, the behaviour you're describing does sound like it could be caused by an IP conflict... But that's only one possibility. I think I'm thinking like @PhilipDAth here... Maybe there's a stray link somewhere? A packet capture during the problem might show what's up too... But of course that means putting everything back in place an inconveniencing your users.

jdsilva · ‎Jun 19 2018

They both have the same IP's?

jdsilva · ‎Jun 18 2018

Yeh I didn't get mine either from the website. I just figured that some sales person would be calling me to follow up before they actually sent it over.

jdsilva · ‎Jun 18 2018

If I understand you correctly you'll want to set up the MXes in a Warm Spare configuration, and connect both Internet connections to both MXes. You can't have both MXes active, but you can have both Internet services active on the active MX. For the LAN side Meraki uses VRRP to give clients access out. You do not want to have two MXes in two different networks. https://documentation.meraki.com/MX-Z/Other_Topics/Warm_Spare#NAT_Warm_Spare

jdsilva · ‎Jun 15 2018

Good meeting you too @Mr_IT_Guy !

jdsilva · ‎Jun 15 2018

...And that's a wrap for Cisco Live! this year. Thanks to all the Meraki folks that I interacted with there. You all helped make #CLUS a lot of fun for me this year. It was good to put a few faces to names, and good to see people again that I'd already met.

jdsilva · ‎Jun 15 2018

The only knobs to control this are in Organization --> Settings But there's so many things these settings don't catch that, to us, they are effectively useless. We've expressed our desire for better control over both the emails and the banners to Meraki many times. Though our concern is also around that our customers get these emails too, which we don't want. You should see how many emails I get in a day... It's significantly more than 10 😞

jdsilva · ‎Jun 15 2018

@Netwow you can do what you're asking. But given the info you've supplied it doesn't make sense from a design perspective. Just because you can do something doesn't always mean you should. I would encourage you to review your design and decide if this sort of setup really satisfies the requirements you have.

jdsilva · ‎Jun 14 2018

I was told by Joe Aronow this week it can be done. I thought I tried it and it didn't work but now I'm doubting myself...

jdsilva · ‎Jun 11 2018

That swag vending machine is full of goodies! Didn't see a skateboard in there though... 😞

jdsilva · ‎Jun 10 2018

I'm in the back corner at the orientation right now.

jdsilva · ‎Jun 10 2018

... And made it!

jdsilva · ‎Jun 8 2018

That would work. It's effectively the same thing.

jdsilva · ‎Jun 8 2018

Hey @Mju. No, you cannot do this currently with that set up. That method will only provide failover. You would need this type of topology to do what you are asking: https://documentation.meraki.com/MX-Z/Site-to-site_VPN/Configuring_Site-to-site_VPN_over_MPLS

jdsilva · ‎Jun 8 2018

@Mr_IT_Guy Yup, I'll be at both of those events.

jdsilva · ‎Jun 8 2018

Yup! I would love to have this too. I recently brought up a link over some really old OM2 fibre running ~700m using LX optics and mode conditioning patch cables and it would be helpful to know these details to see how strong the link actually is. It is working, and operating at 1Gbps without errors... But I can't say how much room to spare we have levels wise.

jdsilva · ‎Jun 7 2018

I don't think you can... 😞

jdsilva · ‎Jun 7 2018

Right. I amended my reply above for a VPLS (or other layer 2 MPLS service). In that case you're right and it's the same layer 2 domain on both sides.

jdsilva · ‎Jun 7 2018

Sorry @ScottWinCO, the .249 addresses are not on the MXes. I think you've interpreted that incorrectly. EDIT: To clarify, that diagram shows L3VPN. If we have a VPLS service then the second part of your statement is correct and they would not exist.

jdsilva · ‎Jun 7 2018

Those routers look to be the PE routers in an L3VPN service.

jdsilva · ‎Jun 6 2018

I seem to be missing pants... 😉 Thanks for the new shirt and buttons @CarolineS !

jdsilva · ‎Jun 4 2018

Stupid sticky clients 😞

About jdsilva

jdsilva

Community Record

Badges