The tests I'm running now are done with a different pair of motor control and switch (and cable). I set the debug level on the switch but the only difference is that i see a lot of these:
Debug NOV 02 09:39:05 DNS_CLIEN DNS Client: no ipv4 or ipv6 address found in response for request id 7594
Could they be related to the problem? Seems unlikely...
Anyway I still see the in-errors on the interface using SNMP but as I said nothing is logged on the switch, now I'll try to keep the network traffic up and see if eventually the motor control became unreachable.
I've conduct an extensive test on the spare devices and I was never able to reproduce the problem, it also never occurred again with the motor control used in production.
Meanwhile I also discovered that there was some operations around the area where the motor control is located, so I think that someone just turned it off inadvertently (unfortunatly it is quite easy to do so due to bad design of the power switch).
In the end the only communication errors that mattered in this case seem to have been the ones between peoples.. eh..
I'll schedule a downtime for the switch anyway to see if the new firmware help to mitigate the problems about the errors.
giovanni.lnl
1 Rookie
•
14 Posts
0
November 2nd, 2015 00:00
Hello Daniel, thank you for you answer!
The tests I'm running now are done with a different pair of motor control and switch (and cable). I set the debug level on the switch but the only difference is that i see a lot of these:
Debug NOV 02 09:39:05 DNS_CLIEN DNS Client: no ipv4 or ipv6 address found in response for request id 7594
Could they be related to the problem? Seems unlikely...
Anyway I still see the in-errors on the interface using SNMP but as I said nothing is logged on the switch, now I'll try to keep the network traffic up and see if eventually the motor control became unreachable.
giovanni.lnl
1 Rookie
•
14 Posts
0
November 18th, 2015 03:00
Hello Daniel, sorry for the late reply.
I've conduct an extensive test on the spare devices and I was never able to reproduce the problem, it also never occurred again with the motor control used in production.
Meanwhile I also discovered that there was some operations around the area where the motor control is located, so I think that someone just turned it off inadvertently (unfortunatly it is quite easy to do so due to bad design of the power switch).
In the end the only communication errors that mattered in this case seem to have been the ones between peoples.. eh..
I'll schedule a downtime for the switch anyway to see if the new firmware help to mitigate the problems about the errors.
Thanks for your assistance as usual