Bug ID 450699: Configure member IP addresses on VIPRION before downgrading

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.3.0, 11.4.0, 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

Opened: Feb 28, 2014

Severity: 2-Critical

Symptoms

After booting into a new install location, the primary blade is missing the previously configured default route.

Impact

Managing the VIPRION after upgrade requires alternative access methods.

Conditions

-- Installation is from a downgrade, for example installing 11.5.3 from 11.5.4-hf1. -- VIPRION cluster without member mgmt IP addresses configured. -- No default route on primary blade.

Workaround

1. Configure cluster member IP addresses before installation. (one per blade). 2. If already booted into the new location, you can access the VIPRION and create a new default route. In this condition, Access can be obtained over the management port from another host on the same LAN as the VIPRION, or over the serial console.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips