Bug ID 497234: ISO images 2 GiB or larger will not sync to secondary blades on a chassis

Last Modified: Mar 01, 2021

Bug Tracker

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

Known Affected Versions:
10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.4 HF2, 11.5.1 HF11, 11.4.1 HF9, 11.2.1 HF15, 10.2.4 HF12

Opened: Dec 17, 2014
Severity: 1-Blocking

Symptoms

ISO images 2 GiB or larger do not sync to secondary blades on a chassis--that's 2,147,483,648 bytes, not 2,000,000,000. A newly-inserted blade remains reporting 'upgrade needed' or 'waiting for product image', even though the specified software images are present on the system, and may even be present on the affected blade in /shared/images.

Impact

Affected blades do not automatically join the cluster, as described in K13965: Overview of the automated process of joining a newly installed or RMA replacement VIPRION blade to the cluster (https://support.f5.com/csp/article/K13965).

Conditions

-- Blade running an affected software version. -- Trying to copy software images larger than 2 GiB to the blade.

Workaround

Manually transfer the ISO to /shared/images on all blades. If the system still does not show the affected image from /shared/images in 'tmsh list sys software', on the target blade, run the command 'imagemgr -a /shared/images/<name of ISO>' to manually add the software image to the 'sys software' configuration.

Fix Information

ISO images larger than 2 GiB formerly did not sync to secondary blades on a chassis. (2 GiB = 2,147,483,648 bytes, not 2,000,000,000.) These images are now supported.

Behavior Change