Any Meraki device that is already claimed by another organization cannot be used unless the original organization unclaims it from their organization.    You should contact the seller on eBay to see if they are the organization administrator and ask them to unclaim it from their organization. If they can't help you, then unfortunately, you're out of luck.   My advice: do not buy Meraki appliances from eBay, and try to avoid buying refurbished MX, MR, and MS appliances if at all possible. If you decide to buy the hardware, check with the seller to ensure that the device is unclaimed. ... View more

I understand that you can't access the Meraki MX appliance belonging to Toast, but have you considered the possibility that the ERX router and MX appliance are using the same WAN IP address? If so, there could be a conflicting connection. You would have to change the static WAN IP address of the ERX router to test this.   It doesn't really make sense your ISP is telling you you don't have a limit to multiple public IP addresses - they will normally hand you a block (i.e. if you have multiple static IP addresses, you could get a /29 block), there will always be a limit.    The biggest thing I would consider, given you don't have insight into the Toast Meraki MX appliance, is the possibility of a WAN IP conflict between the ERX router and the Meraki MX. If applicable, I would consider changing the ERX's WAN IP address to a different public IP in the range your ISP provided, and see if this makes a difference.   Finally, you mention using a managed switch to eliminate "crosstalk" between the Meraki MX and the ERX device; a managed switch will not inherently do this unless you configure separate layer 2 VLANs for each switch port, and because this switch sits on the internet edge - that configuration will not suffice unless the ISP modem has an 802.1q trunk configuration on the other end of the connection and you can match what ever VLANs are allowed on its trunking interface. In some of my client environments, we have run the data network separate from the voice network, and I've used an unmanaged Cisco switch to split internet traffic between the Meraki MX, and a proprietary voice gateway, and we had no issues with crosstalk for the devices. The Meraki MX is a stateful firewall and will by default block all inbound traffic from the internet, so you shouldn't need to worry about crosstalk from your network to the Meraki Toast network. If you want to put a managed switch in to have visibility into the traffic, that is a great option; however, it is not a solution to preventing crosstalk between your network and the Meraki Toast network. ... View more

Hello @Karan_Meraki    You just purchased this MX67?    First off, are you using the LAN/patch cables that came shipped with the MX67? Or are you using one that you already had? Can you test that cable to ensure it is not an issue with the cable?   Second off, the LED status of the MX67 will remain solid orange because it has no connection to the Meraki cloud. Since you state your ISP gave you a static IP, I assume your internet circuit does not have a DHCP failback, but you could try to connect your MX67 to the internet without the static IP, reboot it, and see if the status LED goes to rainbowing. Don't forget to license and register the MX67 to your Meraki dashboard.   Finally, by default - out of the box, Meraki MX67s will handout DHCP upon plugging a device into its LAN port. You are getting an APIPA address because there is no associated link. Do you have link lights on your laptop's NIC when trying to connect the cable? If not, go back to testing the ethernet cable you're trying to use/try another cable first. If that fails, factory reset the device, and if that fails, try another laptop if you can or double check its NIC is enabled, and if it is, and you've exhausted everything else mentioned - I would contact Meraki support. ... View more

If you do not see the 2 roles 'IDS Alerts' and 'Security events' from your dashboard, then you cannot leverage them in the API as roles. I am able to use the Security events role in my syslog settings through the API across several branch locations for one of my clients, all which consist of combined networks (wireless/switch/security).    It is unusual that 'Security events' is not a selectable role, so I would open a case with Meraki support to have them check out what could be going on; I am unsure on the 'IDS alerts' role as I've never seen that as an option in the dashboard, and in the current API library, I do not see that as a role option either. ... View more

Thank you! I look forward to being a part of the community! ... View more

Thanks! I am based out of Midlothian, Virginia, in the United States. 🙂 ... View more