Hi With a Meinberg M500 I sometimes getting "rogue peer delay response" messages, which leads to FAULT state. I even sometimes end up in a 5 minutes loop FAULTY->LISTENING->UNCALIBRATED-> FAULTY... until the "rogue peer delay response" disappear and the node becomes SLAVE.
ptp4l[991.731]: selected best master clock ec4670.fffe.00ce2d on port 2 ptp4l[991.732]: selected best master clock ec4670.fffe.00ce2d ptp4l[991.732]: port 2 (eth2): MASTER to UNCALIBRATED on RS_SLAVE ptp4l[991.733]: port 2: rogue peer delay response ptp4l[991.734]: port 2 (eth2): UNCALIBRATED to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED) I checked with Meinberg and it's very unlikely that the device actually sends unsolicited peer delay responses. I only getting "rogue peer delay response" messages when quickly changing between several GMCs so it seems to be some transient phenomenum. If I look at ptp4l code there are several locations where delay requests are flushed, maybe after sending the request? If, after flushing, a peer delay response is received, obviously I get the "rogue peer delay response". Under these circumstances I wonder if the transition to FAULLY state is the right reaction. Why not just print the message but continue with the same state? Best regards, Chris
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
