I'm glad the problem was solved. I have also forgotten to set it up and spent a lot of time troubleshooting. ... View more

I just had this same issue plaguing me for a few weeks. Had multiple Cisco and AWS support engineers troubleshoot with me and we could not figure it out until this morning. I wanted to post a more specific solution in case others like me find this and start tearing their hair out: If you want your EC2 instance to be able to SSH to an on-prem device through Meraki, you need to add an inbound rule to your vMX's security group that allows SSH traffic from the VPC CIDR (or from whatever subnet/individual IP from that block).   There are autogenerated rules from creating a vMX in AWS and SSH is not one of the protocols included because Meraki does not allow SSH into itself (so there would be no need for it in general). ... View more

Hmm I believe that last part is a little hard because you can have a multitude of switchtypes in one single dashboard network.   Maybe a pop-up like the QoS and stormcontrol pop-ups you get when you have MS1x series switches in your network would be a better choice.   It's easier to check if something is then to check everything for something that isn't. ... View more

@bluecavalry  if it were fiber transceivers between the MS and MX that would matter.  I have several MS switches that do not have a clue being connected to an MX.    Now regarding your question about the lldp data. checked a network and here the switch is connected to LAN Port 4 of the MX100    System name Meraki MX100 - MX100 System description Meraki MX100 Cloud Managed Router Port ID 2 Chassis ID   Port description lan port 2 System capabilities   I have another switch on port 3 which is connected to lan port 1 (port 3 on the front of the MX) This is because LAN 2 is configured as internet. So i guess numbering depends on the fact of having 2 WAN Ports or not.   ... View more