Forum Discussion
Native tmsh/bash commands via REST API
1. A method of monitoring the F5 to determine the pool/node health etc?
2. Or monitoring the poolmembers to determine their health for the LB?
If it's 1, checkout the walkF5Stats script in codeshare (http://devcentral.f5.com/wiki/default.aspx/iControl/walkF5Stats.html), that uses (Mostly) the iControl interface (Which is SOAP). THat should point you in the direction you need. Or you can also use cacti and the cacti plugins (But that uses SNMP not SOAP and XML).
H
- What_Lies_Bene1Nov 05, 2013
Cirrostratus
You could do this with an iFile and an iRule. Take a look here for an example which you can work from: https://devcentral.f5.com/articles/v111-ndashexternal-file-access-from-irules-via-ifiles.
By the way, you don't mention much about the F5 setup but if you enable compression and caching it'll always help.
- Kevin_StewartNov 05, 2013
Employee
You can do this with the HTTP::respond and iFiles commands. Take a look at the iFiles wiki page for a good example:
https://devcentral.f5.com/wiki/irules.iFile.ashx
And here's another example:
when HTTP_REQUEST { if { [string tolower [HTTP::uri]] equals "/test.js" } { HTTP::respond 200 content [ifile get test_js] "Content-Type" "application/javascript" } }
- sundogbrewNov 05, 2013
Altocumulus
Thanks guys, I was able to use the ifile and can get the file. By the way What Lies Beneath, it isn't so much that it is slow, but it is inconsistent. Downloading a 450k .js file 100 times takes like 60ms and then probably 10 times sporadically it will take 3 to 6 seconds.
- sundogbrewNov 07, 2013
Altocumulus
Hey WLB, I kind of over simplified the problem. The thing that is consistent is that it is inconsistent. I can run it for 1000 iterations and be happy with the results maybe a couple outside the norm then I can run it a few minutes later and have it look terrible.
- sundogbrewNov 07, 2013
Altocumulus
Behind the F5 looks OK. I added the file to try to work my way forward and (hopefully) off the F5. When I run the script against the file served by the F5 I still see the problem so that says it is not behind the F5, it is either the F5 or in front of it. I have done some wireshark captures but can't find a smoking gun.