Forum Discussion
4 Replies
Are you referring to logs showing the traffic that each device is moving? If so, I would be very careful about logging that sort of data to the local syslog daemon and the disk of the BIG-IP. A large volume of traffic (and therefore logs) could cause a negative impact on your system.
The best way, I feel, is to use High-Speed Logging to send logs to a off-box system. You can find instructions to configure it for your situation in this guide: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-external-monitoring-implementations-11-5-0.html
Thanks.
A quick google search for your error message returned the following result: http://blog.techstacks.com/2009/08/xfirefault-can-not-invoke-service-over-ssl.html
Is your SSL certificate self-signed?
You can run tcpdump in a continuous mode, where it will create multiple files, and begin writing over the oldest file once it hits a configured limit. A decent looking example may be found here: http://superuser.com/a/289250 This will allow you to capture the traffic, and analyze it after detecting the error. Be cautious to not configure tcpdump to use more space than is available on the system.
You certainly can log to syslog, but just keep in mind that you may see higher than average CPU and disk I/O usage. I would not run logging to local disk on a busy service for an extended period of time.
An iRule seems to be the best option here, and is what I usually use for brief debug sessions. I checked the Request logging profile and does not seem to have an option to log to the local box.
A good guide on writing an iRule to log request information can be found here.
https://devcentral.f5.com/articles/-the101-irules-101-logging-amp-comments
For HTTP traffic, I use an iRule like this one:
https://devcentral.f5.com/wiki/iRules.LogHttpHeaders.ashx