Forum Discussion
khackworth_5078
Nov 29, 2011Nimbostratus
LTM Packet Tracer Analysis
First and foremost, I have a request open to our account team to see if they are aware of any solution, but figured I would fire this off to the group to see what solutions the users have devised. ...
hooleylist
Dec 02, 2011Cirrostratus
I don't think this type of complete introspection is currently possible. But it makes for an interesting use case. If there are things you can't do that you'd like to, I'd encourage you to open a request for enhancement with F5 Support.
You could do some of the logging in an iRule to get:
client IP:port; local IP:port; HTTP request options like URI, headers, etc; serverside source IP:port; pool name; server IP:port
Here's one example:
http://devcentral.f5.com/wiki/iRules.LogTcpAndHttpRequestResponseInfo.ashx
For the things like packet filter logic logging you could add logging to the packet filter rules. But there isn't an option to selectively log this from an iRule. You could enable 'reset cause logging' in 11.0, which might help.
Aaron
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects