Forum Discussion
monitor does not work https
- Aug 24, 2023
Hi jhonyy_rg ,
I played around your current version on F5 Bug tracker ,and I think you are hiting in this bug >>> https://cdn.f5.com/product/bugtracker/ID1026781.html
> in your send string I see \r\n\r\n so it's doubled , try to remove one "\r\n" to make your send sring has singe "\r\n" not doubled.
> Or try one workaround that are in the bug article which i sent above.
>> To capture monitor traffic :tcpdump -s0 -nni 0.0:nnnp src host <Self_IP address> and dst host <Backeend_server_IP> and dst port 443 -vw /var/tmp/HTTPs_monitor.pcap # if you don't know which selfip address monitor your server use ip route get utility on bash like below : bash#ip route get < Backend_server_IP > This command will give you which self IP on your bigip monitor your server. Note : if your appliace in HA group ( you have active and standby ) this Capture will work efficient with you as , F5 bigip monitor the backend servers using selfip address and send real data traffic using Floating ip address on HA deployment. So if you run standalone not HA , This Capture command will capture ( Real data traffic and monitor traffic too ) because standalone systems use selfip address to handle users data traffic as well as bigd or monitor traffic.
Check this and let me know 🙂
hellow mohamed
thanks for you answer
the version of f5 is
BIG IP 15.1.7
How do I capture packets, could you give me an example?
Hi jhonyy_rg ,
I played around your current version on F5 Bug tracker ,
and I think you are hiting in this bug >>> https://cdn.f5.com/product/bugtracker/ID1026781.html
> in your send string I see \r\n\r\n so it's doubled , try to remove one "\r\n" to make your send sring has singe "\r\n" not doubled.
> Or try one workaround that are in the bug article which i sent above.
>> To capture monitor traffic :
tcpdump -s0 -nni 0.0:nnnp src host <Self_IP address> and dst host <Backeend_server_IP> and dst port 443 -vw /var/tmp/HTTPs_monitor.pcap
# if you don't know which selfip address monitor your server use ip route get utility on bash like below :
bash#ip route get < Backend_server_IP >
This command will give you which self IP on your bigip monitor your server.
Note : if your appliace in HA group ( you have active and standby ) this Capture will work efficient with you as , F5 bigip monitor the backend servers using selfip address and send real data traffic using Floating ip address on HA deployment.
So if you run standalone not HA , This Capture command will capture ( Real data traffic and monitor traffic too ) because standalone systems use selfip address to handle users data traffic as well as bigd or monitor traffic.
Check this and let me know 🙂
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