Possible problem with Endpoint when replugging fiber with high WR-Btrain traffic
This problem was observed on WR NODE and SWITCH as described below:
Two WR Nodes (as slaves) connected to one WR Switch (master) over cross-point switch (from BTrain guys), BTrain traffic sent by both WR Nodes at 500kHz. When switching between masters, one of the WR Node slaves was left hanging in "listening" state. the counter of received frames was being increased in GUI, yet it seems that no PTP Frames reached the PTP daemon. Restarting PTP did not help, re-plugging switching/replugging (link down/up) helped. It happens +/- 1 in 10 times
The same setup as above, the link of the same WR Node slave is unplugged and plugged. If this is done with minimal duration, i.e. the link is barely removed and than put into place again (on the Master site, I think), it happened once that the WR Node did not detect link to go UP, it stayed down.
Two WR Switches are connected over cross-point switch (and directly), i.e. a) wri2 (master) of WRS1 is connected to wri1 (slave) of WRS2 (over the cross-point switch and directly) b) wri11 (master) of WRS1 is connected to wri11 (passive) of WRS2 BTrain traffic (500kHz) is sent in both directions over both links (using VLANs). The link is re-plugged from wri2 of WRS1. This is done in the same manner as in 2). +/- 1 out of 5, the slave link does not detect link up and stays down while the master port is up and traffic is transmitted. This happens in both cases, over the cross-point switch and with direct connection.
NOTE: we did not reproduce problem 1) with setup 3), i.e. when switching between ports using the cross-point switch
It is likely a problem in Endpoint (HDL)