Focusing on getting cameras into our line of products offered to have a robust plug and play physical security solution to advertise to our customers. As well as focusing on security as a whole from an organization standpoint - taking a step back and trying to figure out how we can best make sure our service offerings are as secure as possible in a data driven world where vulnerabilities in the technology housing this data can lead to huge losses (monetary, reputation, customer base etc.) ... View more

@BrechtSchamp  Yeah I think it is a 7 day grace period on unclaiming the licenses I did read that somewhere I believe. I'm not sure what the case is for trials, I can't find much information on them so that's why I came here! Yeah well I need the devices/licenses to be removed to simulate a test scenario of a new install and to create that second network, I can't manually move them into a network that doesn't exist yet.    In our testing scenario the API creates the Org and then the devices are added to it, in our first test scenario all worked fine at first but then our second set of devices the MX got added to the existing network in the org and didn't create a new second network for it.    Sorry if that's confusing, it's the end of the day for me lol.   I'm not sure I can move the devices to a network to accomplish what I need to here.   Thanks. ... View more

I know that. I'm specifically wondering here about the differences between the trial licenses vs. the revenue licenses. So even with Trials I have to contact Meraki is what you're saying? ... View more

Hi Dave,   This is kind of related to your reply to this answer regarding Dashboard IP space... I'm trying to get a packet capture of a test meraki network and get verification/proof of how often it reaches out to the dashboard. I see the IP addresses in the help > Firewall Info area on the dashboard. But I'm trying to figure out more details on this.    When I run a packet capture on the switches in the dashboard I do see my switch reaching out to IP 209.206.58.101 but it's showing up over 100 times within just 1 minute of the packet capture. I don't see this 209 address space or any of the others when I run the packet capture on the MX/Security Appliance. So does it constantly send TCP/UDP packets to the 209 address? Or is there a time interval or another IP I'm missing?   Is there another way to accomplish what I'm trying to do? Or a whitepaper with details what rate the dashboard reaches out to the devices/vice versa. I know I read somewhere that it uses 1kbps or less on a Meraki document to monitor things and keep in contact with the dashboard etc.    Thanks in advance. ... View more

For anyone wondering - ended up RMA'ing the MX60W for a new MX64W. Once it plugged up to my switch and connected to the cloud everything in the dashboard was green and no more  "Bad internet connection" issues. Seems to have been failed hardware or something along those lines. ... View more

CMR,   No - it's not an ISP gateway or any IP address that we can recognize. I think the MX device is corrupted or something, when I do a factory reset it doesn't require me to reconfigure the IP address information at http://setup.meraki.com   From the dashboard point of view I get "disabled gateway - bad connection" errors on the timeline view where I can see where it lost connectivity during the factory "reset." Any ideas of anything else to try?   Thanks. ... View more

Yeah - that is not the case here. LAN interfaces are all set to be LAN. I've verified that. Even when I set the WAN IP as static. I'll refresh my meraki dashboard and still see it flipping back to another .209 IP address that I've never configured on it. It has been factory reset as well, but I'm thinking that the factory reset didn't actually complete, or is it a possibility that the settings are inherited from the dashboard? The MX was previously in another lab and shipped here to our lab. Does the device need to be removed by using the "Remove appliance from network" and re-added? Or am I reading too far into that? ... View more

CMR,    So you're saying I should configure one of the LAN ports to be configured as WAN? Why? Why won't the Internet/WAN port suffice? I'm confused with your response... ... View more

Phillip,   I realize this is an older thread. But I'm looking around online trying to find a resolution for a bizarre issue I'm having with a Meraki MX60W. There is only 1 WAN/Internet Port on the back of the device. However on the dashboard - I'm seeing WAN 2 interface showing as "ready" with a strange IP  208.xxx.xxx.xxx that I'm not familiar with (MX device is on 192.168.227 subnet.) I have only the WAN port plugged in to my routable switch interface leading out to my firewall w/ internet access and I've verified no ports are being blocked that the Meraki needs to get cloud access etc.   There's nothing else plugged in, so I'm not sure why the WAN 2 interface is getting any activity or picking up an IP address?    Also in the dashboard at the top under my MX it just says "Bad internet connection" in red. But I'm able to see the stats, see the device on the dashboard etc. The MX has received a DHCP IP address I've verified that and I can get to the setup.meraki page when directly plugged into one of the LAN ports on the MX.   Any help would be appreciated, thanks. ... View more