10/25/2024 7:38 AM | |
Joined: 2/15/2024 Last visit: 10/25/2024 Posts: 7 Rating: (0) |
I will try to gather all the information next time the issue manifests and reply back. Thanks for your support. EDIT: We got lucky(?) and the issue manifested in one of the lines, I will attach some information and complete it later with some videos about the led behavior. I had to zip everything together due to size. As you will see in the logs, device is up since 9 days ago, at some point I have yet to determine, eno1 stopped working. The device is connected like this: eno2: industrial_network, two IPs 10.119.27.1 and 10.119.27.2 range 10.119.0.0/16. eno1: cell_subnet, two IPs 192.168.0.250 and 192.168.200.1 range 192.168.0.0/16 S7 1500 and all the other OT devices are on the 192.168.0.0 subnet, for example, the PLC has IP 192.168.0.10, and all the other IT devices, like servers are on the 10.119.0.0 subnet. As you can see in the tcpdump logs, the IOT2050 is desperatily sending ARP frames to get the PLC IP with no response. There should be tons of traffic on that interface as lots of devices are connected to the Scalance switch. Even if I manually add the entry to the ARP table, so that IP packets can be sent to the PLC, only the packets sent by the IOT2050 show up. All other devices on the cell_subnet work and communicate properly between them, even if I connect my laptop to an empty port on the switch and try to ping the IOT2050, I get destination unreachable. Of course, we tried different switches and ports and cables. PD: Forgot to note that device has stock IndustrialOS installed. Will update later. AttachmentDIAGNOSE.zip (11 Downloads) |
Last edited by: AutoGen_3051451 at: 10/25/2024 09:41:39Last edited by: AutoGen_3051451 at: 10/25/2024 09:55:15Last edited by: AutoGen_3051451 at: 10/25/2024 09:58:46 |
|
Follow us on