PLC Stop working after connecting it to a Cisco Meraki C9300-24P

[JohanPlukon]

We run into an issue with a Siemens PLC connecting it to a C9300-24P switch. Once connected to the Catalyse the PLC lost is connection and is not able to communicate any more to the scada application and other plc's which are further in the network. 

Also when the different plc's are connected to the same switch, its not working. Putting it back in the HP Aruba switch (which was replaced by the catalyst) it starts working again. 

Any one else encoutered this issue?  The switches are firmware 17.2.1.1

[rhbirkelund]

Have you verified that VLANs are allowed in the 9300 uplink port?

Contrary to what we are used to on Meraki MS switches, only VLANs 1-1000 are allowed on a default trunk port on a 9300. If you use VLAN IDs higher than 1000, you'll need to allow them on the trunk port. 

[JohanPlukon]

Yes i have, the devices are all in vlan below 1000 and allowed on the uplink ports. 

[PhilipDAth]

Same port configuration with regard to access+VLAN, and trunk configuration?

If you do a packet capture on the switch port, can you see the PLC trying to talk?

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Packet_Capture_Overvi...

[JohanPlukon]

No there is not traffic seen at all, i have the idea that the catalyst is dropping the profinet traffic some how. Is this even supported on catalyst? Just thinking out loud.. 😀

[rhbirkelund]

If you are doing PROFINET, I'd recommend you open a case with Meraki. Although it is based on TCP/IP communication, I believe that PROFINET is not supported on Meraki.

In the case of C9300 in Cloud Configuration, I think Meraki Support can best assist.

[rhbirkelund]

That, and perhaps reaching out to your local Meraki SE. 

[JohanPlukon]

Official Meraki comment that it is not supported and we have to buy the IE line to connect these devices. 

[Bobcheese2]

I have to wonder if they're taking the easy route on the ticket (no offense to Meraki Support) but if its a standards based NIC then I dont see why it wouldnt work. Can you post the port config from the Aruba switch for the port it was connected to? Datasheet for the PLC would be good too

[Bobcheese2]

See this topic, might be a 17.2.1.1 issue. OP on this fixed their issue with upgrade to 17.2.2

https://community.meraki.com/t5/Switching/Problems-with-printer-after-upgrade-MS-Switches-225-to-lat...