Loading...
Loading...
Config load fails when an iRule contains a commented line that ends with an escape character (backslash), and the config also contains an LTM policy. Depending on the iRule, you might also see the following error: Syntax Error:(/config/bigip.conf at line: 42078) double quotes are not balanced.
Config load fails.
-- iRule contains commented line that ends with a backslash. -- The config also contains a policy. For example, an iRule similar to the first example, and a policy similar to the second: ltm rule /Common/log_info { when HTTP_RESPONSE { #log local0. "Original Location header value: [HTTP::header value Location],\ updated: [string map ":[TCP::remote_port]/ /" [HTTP::header value Location]]" } } ... ltm policy /Common/Test_Policy { controls { forwarding } requires { http tcp } rules { TestPol_Rule1 { actions { 0 { forward select node 10.2.10.20 } } conditions { 0 { tcp address matches values { 10.1.10.20 } } } } } strategy /Common/first-match }
You can use any of the following workarounds: -- Delete the line of code with the comment. -- Put the entire comment on one line of code. -- Divide lengthy comments into a series of smaller ones, so that each comment fits within one line of code. -- Move the iRule so that it is sequentially before the LTM policy in the config file.
Config load no longer fails when an iRule comment ends with backslash in a config where there is also a policy.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.