Bug ID 721375: Export then import of config with RSA server in it might fail

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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

Fixed In:
13.1.1.2, 12.1.3.7

Opened: May 23, 2018

Severity: 4-Minor

Symptoms

If an exported policy configuration contains both an RSA server as well as the RSA-provided sdconf.rec and sdstatus.12 config files, policy import might fail.

Impact

Unable to import the exported configuration. This occurs because of how the names for the files are resolved in the exported configuration.

Conditions

-- RSA server and access profile are in the same, non-Common partition. -- Exported policy contains an RSA server as well as both the RSA-provided sdconf.rec and sdstatus.12 config files.

Workaround

Although there is no actual workaround, you can avoid this issue if the profile is outside of the partition. That case uses a different name resolution during the export, so import works as expected.

Fix Information

You can now successfully import an exported policy containing an RSA server as well as both sdconf.rec and sdstatus.12 files.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips