Bug ID 448782: MGMT IP and routes may change when applying UCS from different system

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10

Fixed In:
11.6.0

Opened: Feb 12, 2014

Severity: 3-Major

Symptoms

When creating a disaster-recovery unit by copying UCS from production unit to an identical unit in another datacenter, the MGMT information is installed from the UCS as well.

Impact

Loss of administrative connection with MGMT port upon applying UCS.

Conditions

UCS (User Configuration Set) containing MGMT IP and route settings, saved from one BIG-IP system and applied to another BIG-IP system.

Workaround

1. Connect to the BIG-IP system where the UCS is to be applied via the serial console to apply the UCS configuration. 2. After UCS is applied, manually update the MGMT IP and routes to correct settings for the new system.

Fix Information

It is now possible to load a UCS file from another chassis using the include-chassis-level-config option. This will change your chassis and blade mgmt addresses.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips