Bug ID 810825: Export, then import of pool outside of a default route domain may fail

Last Modified: Oct 16, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1

Opened: Jul 30, 2019
Severity: 4-Minor

Symptoms

While importing a policy, you get an error: Syntax Error:(/shared/tmp/apmom/import/abc.conf at line ###) invalid IP address: "1.1.1.1%0%1"

Impact

Importing the policy fails on syntax error.

Conditions

-- Importing a previously exported policy -- The policy was from a partition with a non-zero route domain

Workaround

You can manually edit the file and then attempt the import again. For example if a pool member was supposed to exist in route domain 1 with port 1812, the erroneous policy might look like this: ltm pool /@partition/@name-safenet-radius-pool { members { prod/1.1.1.1%1:radius { address 1.1.1.1%0%1 <===== priority-group 1 state up } } min-active-members 1 } It can be manually fixed by removing the erroneous %0 in the string. ltm pool /@partition/@name-safenet-radius-pool { members { prod/1.1.1.1%1:radius { address 1.1.1.1%1 priority-group 1 state up } } min-active-members 1 }

Fix Information

None

Behavior Change