Bug ID 658943: Errors when platform-migrate loading UCS using trunks on vCMP guest

Last Modified: Sep 29, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7

Fixed In:

Opened: Apr 18, 2017
Severity: 4-Minor


During platform migration from a physical BIG-IP system to a BIG-IP vCMP guest, the load fails with one of these messages: 01070687:3: Link Aggregation Control Protocol (LACP) is not supported on this platform. Unexpected Error: Loading configuration process failed. 01070338:3: Cannot create trunk [name of trunk], maximum limit reached Unexpected Error: Loading configuration process failed.


The platform migration fails and the configuration does not load.


-- The source device is a physical BIG-IP device with one or more trunks with or without LACP in its configuration. -- The destination device is a vCMP guest.


You can use one of the following workarounds: -- Remove all trunks from the source configuration prior to generation of the UCS. -- Before loading the UCS archive onto the target BIG-IP, edit the archive and remove the trunk configuration from ./config/bigip_base.conf, and then repack the UCS. -- After the UCS load fails, edit the configuration manually on the destination to remove trunk references, and then reload the configuration.

Fix Information


Behavior Change