Printer FriendlyEmail Article Link

Spirent TestCenter: Wireshark incorrect decode of Spirent signature timestamp.

Symptoms
  • Example: Sending packet rate of 250 fps, Wireshark time shows 4ms delta between frames but Spirent signature timestamp shows 1.6ms.
Environment
  • Non-Spirent versions of Wirehark.
Explanation/Resolution
  • Spirent has a Wireshark version available on it's download site specifically to decode Spirent signature packets.
    • The Spirent version of wireshark will show seconds in the Decode section but if added as a column for the Summary section, it will just show a counter value which we call ticks.
  • Spirent also started including an stcsig decode option in versions downloaded from Wireshark.
    • To enable the Spirent decode in these versions:
      • Go to Analyze->Enable Protocols->STCSIG
    • One limitation on these versions is that the timestamp values in the Decode section are ticks (not seconds).
      • Each tick represents 2.5ns
      • From the snap shot in the Symptoms section of this article, it shows 1.6ms (but as mentioned this is not seconds), convert that to ticks, we get 1,600,000 ticks.
      • 16,000,000 x 2.5ns = 4ms (which matches the delta times)
  • Related articles below but you will need to login to the support site to view.
    • FAQ10842 Spirent TestCenter: What are the Spirent TestCenter signature fields?
    • FAQ18353 Spirent TestCenter: What is the wireshark version I need to install?
Root Cause
  • Limitation on the non-Spirent version of wireshark.

Product : Spirent TestCenter,PGA