Greetings, Meraki Community! I recently started investigating some complaints at a remote site. In the event log, I see the following message:   Ethernet port carrier change    device: port1, carrier: false   ...which was suggested by a support engineer to be the Z3's uplink. If I go by the label on the physical device, port1 is indeed the uplink.    By this logic, port1 = WAN    However, if I do an API call to get the Z3's neighbors, I see that the interfaces are broken down by "wan" AND "port", making the API output's "port1" the physical / labeled Port 2, which is a PC:   {     "ports": {         "wan0": {             "lldp": {                 "sourcePort": "wan0",                 "systemName": "Mitel IP Phone",                 "managementAddress": "192.168.11.114",                 "portId": "xx.xx.xx.xx.xx.xx"             }         },         "port1": {             "lldp": {                 "sourcePort": "port1",                 "portId": "xx.xx.xx.xx.xx.xx"    <------ HP desktop             }         }     },   By this logic, port1 = PC   So, just to confirm, the Meraki event log is using the physical / labeled ports on its log entries, whereas the API would likely use the table with corresponding ports below?   API wan0 = physical / labeled port 1 API port1 = physical / labeled port 2 API port2 = physical / labeled port 3 API port3 = physical / labeled port 4 API port4 = physical / labeled port 5   Hopefully I explained this well enough. Thanks for your time! ... View more

Greetings, Meraki community! As the subject suggests, I'd like to compare a few different products' wireless capabilities. The MR36, for instance, has a Tx/Rx table here https://documentation.meraki.com/MR/MR_Overview_and_Specifications/MR36_Datasheet, but I can't find comparable pages for MX*W or Z3 devices.    At a high level (price not a consideration at the moment), the design might look something like this, for a small to medium office:   MX68W (MX w/ wireless) MX68 + MR36 Z3   Best guess right now is MX + MR > MX*W > Z3, but I simply don't have the documentation to back that up. Is this outlined somewhere that I might be overlooking? Alternatively, is there a better way to look at this? Thanks, all! ... View more