https://community.extremenetworks.com/t5/extremeswitching-exos-switch/is-there-a-way-to-know-why-some-gptp-packets-are-discarded/m-p/34908#M6931 I have a Summit X670 switch with the AVB package installed. When I look at the counters for a specific port with the command : show network-clock gptp counters, the stats indicate some discarded packets. Is there a command or a log that I can use to know the reason why these packets have been discarded? Thanks Thu, 16 Jun 2016 00:18:00 GMT Sébastien_Bouth 2016-06-16T00:18:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/is-there-a-way-to-know-why-some-gptp-packets-are-discarded/m-p/34908#M6931 I have a Summit X670 switch with the AVB package installed. When I look at the counters for a specific port with the command : show network-clock gptp counters, the stats indicate some discarded packets. Is there a command or a log that I can use to know the reason why these packets have been discarded? Thanks Thu, 16 Jun 2016 00:18:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/is-there-a-way-to-know-why-some-gptp-packets-are-discarded/m-p/34908#M6931 Sébastien_Bouth 2016-06-16T00:18:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/is-there-a-way-to-know-why-some-gptp-packets-are-discarded/m-p/34909#M6932 Sebastien,<BR /> <BR /> As far as I know there isn't a show command or log message that will indicate exactly why the packet was discarded. In the "show network-clock gptp port <I>PORT_NUMBER</I> counters" output there are three counters at the bottom "Announce Receipt Timeout Count", "Sync Receipt Timeout Count", and "Peer Delay Allowed Lost Response Exceeded Count". I believe each of these errors will also result in a gPTP packet discard. However, I am not certain if those are the<I> only</I> reasons. Commonly it is because of an issue with the peer delay measurement. The example below is from a port that has gPTP enabled, but is connected to a non gPTP capable device:<BR /> <BR /> L3L_K2_U32(65.24).6 # show network-clock gptp port 2 counters<BR /> Port number : 2<BR /> gPTP port status : Enabled<BR /> ------------------------------------------------------------<BR /> Parameter Receive Transmit<BR /> ------------------------------------------------------------<BR /> Announce 0 0<BR /> Sync 0 0<BR /> Follow Up 0 0<BR /> Peer Delay Request 0 172<BR /> Peer Delay Response 0 0<BR /> Peer Delay Response Follow Up 0 0<BR /> gPTP packet discards 172 -<BR /> ------------------------------------------------------------<BR /> Announce Receipt Timeout Count : 0<BR /> Sync Receipt Timeout Count : 0<BR /> Peer Delay Allowed Lost Response Exceeded Count : 172 <BR /> As you can see, the discard counter directly matches the Peer Delay Allowed Response Exceeded Count. Thu, 16 Jun 2016 17:52:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/is-there-a-way-to-know-why-some-gptp-packets-are-discarded/m-p/34909#M6932 Chad_Smith1 2016-06-16T17:52:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/is-there-a-way-to-know-why-some-gptp-packets-are-discarded/m-p/34910#M6933 Thanks for the answer Thu, 16 Jun 2016 20:08:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/is-there-a-way-to-know-why-some-gptp-packets-are-discarded/m-p/34910#M6933 Sébastien_Bouth 2016-06-16T20:08:00Z