As mentioned searching using the MAC address is your best shot, the hostname will work for most devices as well unless it's an odd device that has a random hostname.  ... View more

@GIdenJoe wrote: I'm not entirely sure about that last thing @KarstenI .   If the MX didn't do any inspecting of FTP then active FTP on clients would not work, but they do. I haven't tested it for quite some while with "Active", but based on the note "Note: Outbound active FTP is supported in MX Firmware version 12.25+ and 13.6+" there really could be some limited FTP-inspection. But not really as powerful as on other firewalls, which is the reason we have to do the mentioned configuration for passive FTP which is not needed for example on the ASA. ... View more

@Vaishkhanan MS120 isn't a layer3 (routing) switch, it is layer2 only.  It needs a layer 3 device to pass the VLANs to where they can then be routed to each other. ... View more

There are two firewall engines on the MX, one for site to site traffic and one for the rest.    If you are trying to block traffic between two Meraki MXes you need to configure this under the outbound firewall rules found at the bottom of the site to site VPN page.    It sounds like you are configuring this under the Firewall page which is why it is failing     ... View more

Hi. I think you have to configure many pat for every EMS on the MX450 but for me the best way is configuring a RA on MX450. Regards,   ... View more

Hi, all Internet traffic being rerouted to MX450 through VPN tunnel. ... View more

AutoVPN encrypts data, MPLS does not.  It may be more secure than what you are using now. ... View more

You would manage each device type through its own respective management console. You cannot manage non-Meraki device through the Meraki Dashboard, and you cannot manage a Meraki device through a third party console.      ... View more