Forum Discussion
Issue with NTP, odd tcpdump behavior
There is a major hardware difference between a 4000 and i5800, as 2000/4000 don't have a switchboard.
https://support.f5.com/csp/article/K14686
However, I don't think is the problem you are seen.
Do you have route domains?
Can you take the tcpdump with -s0 and nnn?
Here are some helpful links:
https://support.f5.com/csp/article/K411 https://support.f5.com/csp/article/K13637 https://support.f5.com/csp/article/K6546
Latest versions of Wireshark have the F5 plugin integrated, you just need to enable. Save the capture to a file and open with the Wireshark.
https://devcentral.f5.com/d/wireshark-plugin
"Comment made 5 months ago by Jason Cohen F5 As of Wireshark 2.6 (rel. 4/24/2018) the f5ethtrailer is included as a built-in dissector. Wireshark 2.6.0 incorporated the 1.11b version of the dissector.
https://www.wireshark.org/news/20180424.html
It is disabled by default. To enable it, from the menu select "Anyalyze" : "Enabled Protocols...". Then search for f5ethtrailer and enable the dissector."
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
