D-Link Switch is not being recognized by Meraki Switch

[Sivaketan]

The following is the topology, D-Link is not being recognized in the dashboard and devices are not reachable.

If the connection between MS-24 and D-Link is a Access port, then the devices are seen, not the D-Link.

MX (trunk port)-> MS 24(trunkport) --> D-Link (accessport)--> Devices   <<< Not working

MX (trunk port)-> MS 24(accessport) --> D-Link (accessport)--> Devices   <<<working

[jdsilva]

Check that the MX isn't set to drop untagged traffic on its trunk port.

[PhilipDAth]

Does the DLink have any VLAN configurations on it?

When you configure the MS to be an access port are you using the default VLAN of 1 or something else?

[MistahReeves]

To elaborate on Philip's response, is the D-Link a managed switch that you can log into and configure or just a dumb switch that you simply plug things into and that's that? If configurable, is the port connecting to the MS also configured as a trunk port?

If it is just a dumb switch or is managed but the port is configured as an access port, then this explains the behavior you're observing. In order for traffic to pass between two switch ports, the switch modes (trunk/access) must match. All dumb switches, like Linksys, Belkin, and generally D-Link, have all their ports set in access mode by default, and there's no way to change that. If you have a requirement to trunk one or more VLANs across that link, then you may have the wrong gear to do so. If not, then you can just set it to access mode on the MS and call it a day!

Hope this helps!
-Rob

[Sivaketan]

the D-Link is a managed switch (DSG-1210-20 16-port). MS was also configured as trunk port. Thank you

[MistahReeves]

My apologies if I went overboard "mansplaining" all of that yesterday evening. I was a bit groggy after a long day of work. So, just to be sure, have you selected that port as Tagged or Untagged for the VID that matches the one on the Meraki port? If it's untagged, then that makes it an access port. It needs to be tagged for it to be a trunk port. Again, sorry, it's hard to be clear about your current setup due to the way you illustrated it in your original post:

MX (trunk port)-> MS 24(trunkport) --> D-Link (accessport)--> Devices <<< Not working

MX (trunk port)-> MS 24(accessport) --> D-Link (accessport)--> Devices <<<working

If this is accurate, then it would explain why it's not working the way you want it to since the D-Link port must be a trunk port in order to talk to another trunk port.

Cheers!

-Rob 

Edit: It just occurred to me that it could be Untagged if the VID matches the Native VLAN ID configured on the Meraki port. If that were the case, though, you might as well make the Meraki port an access port since you wouldn't be able to trunk any other VLANs across the link.