Bug ID 559939: Changing hostname on host sometimes causes blade to go RED / HA TABLE offline

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.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.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1 HF1, 11.5.4 HF2, 11.2.1 HF16

Opened: Nov 25, 2015

Severity: 3-Major

Related Article: K30040319

Symptoms

If the UI System::Platform screen is used to change the hostname on a Standalone VIPRION, the non-primary blades in the chassis may temporarily report an offline state.

Impact

If the system is hosting vCMP guests, it may cause unexpected failovers, and interruption of traffic.

Conditions

This affects only multi-blade chassis systems in Standalone mode.

Workaround

To change the hostname on the VIPRION, use the tmsh command: 'modify sys global-settings hostname new-host-name'.

Fix Information

Changing hostname on Standalone VIPRION no longer causes the non-primary blade to go RED / HA TABLE offline.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips