LTM Packet Tracer Analysis

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