## Summary In case of sequence number resets (e.g. power cycle of gPTP bridges or PTP daemon resets) more frequent than 60s, the current PTP analysis loses track of the message associations. ## What is the current bug behavior? Due to not handling sequence number resets, the references between associated Sync/Follow_Up and Pdelay_Req/Pdelay_Resp/Pdelay_Resp_Follow_Up messages can be incorrectly detected. This in turn leads to incorrect calculatedSyncRateRatio, calculatedNeighborRateRatio and calculatedMeanPropagationDelay values due to calculating differences between the wrong messages. ## What is the expected correct behavior? Handling sequence number resets, to create correct references and calculations. ## Build information This affects versions 4.0 and later. Fix is underway and MR will soon be created.