F5 BIG-IP

So every time I log into my work ID, and if I want to connect to my Z drive or any drive for my department, then they ask me to log in to the F5 BIG-IP. And after that, I think there's a certain number of hours that they let you use it, and then they lock you out. So it's hard when you work on something, and somehow you save it, but it's not saved, so you have to log back in and then save the file. So I'm not sure if there's a better way for us to keep it open longer during our work hours instead of logging back in and out every single time.

F5 BIG-IP used across our enterprise as LTM, APM, ASM. We deal with visibility problems into advance analytics not displaying full details of what we need to help troubleshoot with application owners (viprion). Additionally we have issues where we are not able to fully synchronize ASM configuration due to traffic differences between data centers.

• at the moment with our current hardware we have still on viprion hardware and will be using it till end of support/eol. Migration from virpion over to Rseries has been simple and easy that we already feel a return on investment with the new hardware

Splunk Enterprise Security

We use F5 BIG-IP's for transaction processing for our internet facing payment platforms. The have been our load balancing workhorses both in the front end and also in the backend for HSM connectivity for resiliency.

• SSL offloading has been easy to manage and use and handles the workload of decryption
• management has been very easy by defining different roles for allowing different groups to view/change their areas

Cisco 350X Series Stackable Managed Switches, Fortinet FortiGate

being used as LTM/GTM. application delivery and DNS load balancing. The biggest challenge is support. F5 support is not useful at all. The team is reluctant to even call F5 support. We are being told to use F5 TAP passes which takes a while to schedule and need 4 hours minimum engagement.

• We had DDOS enable only on one application. ROI went negative as we were not alerted untill we explicitly start looking for throttling speeds.
• ROI is good with application load balancing

We use the BIG IP LTM for all of our business purposes. We use a ton of Irules to do a bunch of content switching and we use all sorts of profiles on our virtuals. One problem we have had was with the dag algorithm and had to change it as some TMM were taking to much. We then saw traffic drop when it we changed the algorithm as it was learning the new has.

• We are able to push forward projects fast with F5 even if its not the right way we can still get stuff done on time as we talk through things.