BIG-IP : upgrade fails to transfer configuration
BIG-IP 11.4.0 Build 2384.0 Final I want to upgrade to 11.4.1 retaining current configuration. I downloaded BIGIP-11.4.1.608.0.iso and uploaded to BIG-IP and installed to volume HD1.2 ( HD1.1 has 11.4.0 ). System > Software Management : Boot Locations I select HD1.2 , set Install Configuration to Yes , set Source Volume = "HD1.1:11.4.0" , and click Activate However on reboot the message is displayed : The configuration has not yet loaded. If this message persists, it may indicate a configuration problem.BIG-IP : multi-boot multi-version : each on separate file-system ?
This actually might be a bit of a newbie unix question. My device has 2 volumes , each with a different version of BIG-IP : HD1.1 BIG-IP 11.4.0 Build 2384.0 Final HD1.2 BIG-IP 11.4.1 Build 608.0 Final Via the browser admin ( System > Software Management > Boot Locations > ) I can boot into one volume or another. Is it true that HD1.1 and HD1.2 are on totally separate file-systems ? So, once booted, ssh into big-ip only has access to the file-system for the version on the volume booted ?
local traffic policy http-header insert action
Hi! BIG-IP 11.4 introduces new feature called Local Traffic Policies. Could you please help with the question if it is possible to use iRules commands inside local traffic policies? I want use logic like represented below. Insert specific header with IP address value. policy_rule_1 { actions { 0 { http-header insert name My-Header-Client-IP value [IP::client_addr] } } conditions { none } }
Problem with iRule upgrading to 11.4.
I'm trying to upgrade to 11.4 but am at a bit of a loss to know how to replace the HTTP_CLASS_SELECTED functionality we currently have in one of our iRules. The iRule aborts a session when it encounters a user-agent listed in the 'UserAgentBlacklist' data group, but it then checks to see if there's an ASM class assigned, and if so, it disables ASM. Without the last part, we were getting error messages written to the log. Any idea on how to rewrite this iRule in 11.4? Code when HTTP_REQUEST { set abort_trans 0 if { [class match -- [string tolower [HTTP::header "User-Agent"]] contains AVUserAgentBlacklist ] } { set abort_trans 1}} when HTTP_CLASS_SELECTED { if {[HTTP::class asm]==1}{ if {$abort_trans==1}{ ASM::disable drop }} else {if {$abort_trans==1} {drop }}}Enabling PFS
Hi everyone, I've been trying to get PFS enabled on my LTM (ver 11.4.1) and am running into a blocker. I've tried various cipher string options and have no luck so far. I've also opened a ticket with f5 support and they just point me to various devcentral discussions that don't have the detail I need. So I guess my question is: what are the cipher options I need to add/remove to enable PFS on a SSL client profile? or is there another way to get PFS going that I am missing? Thanks!