Forum Discussion

rfc19's avatar
rfc19
Icon for Nimbostratus rankNimbostratus
Oct 25, 2015

Restore UCS from 3900 to vCMP Guest (LACP not supported)

Hello,

I am having trouble restoring a UCS file from a 3900 device to a 5525v vCMP guest. The restore process appears to halt when it detects that LACP is configured on the original archive. Is there a way to ignore the LACP component altogether?

Oct 26 08:58:17 tmp-guest err mcpd[5295]: 01070687:3: Link Aggregation Control Protocol (LACP) is not supported on this platform.
Oct 26 08:58:18 tmp-guest err tmsh[18966]: 01420006:3: Loading configuration process failed.
Oct 26 08:58:18 tmp-guest emerg load_config_files: "/usr/bin/tmsh -n -g load sys config partitions all base" - failed. -- 01070687:3: Link Aggregation Control Protocol (LACP) is not supported on this platform. Unexpected Error: Loading configuration process failed.
Oct 26 08:58:18 tmp-guest err mcpd[5295]: 01070422:3: Base configuration load failed.

Any assistance would be greatly appreciated.

Regards

6 Replies

  • You can edit the ucs archive using something like 7Zip to get access to the conf files that are contained within. In the archive, if you look at bigip_base.conf you should see the lacp config detailed in the file which you can then delete/hash out as appropriate. Don't forget to resave the edited archive in 7zip before uploading onto your big-ip.

     

    Make sure you've got a backup copy of the ucs file before you start editing it :-)

     

  • rfc19's avatar
    rfc19
    Icon for Nimbostratus rankNimbostratus

    So, I managed to sort that error out. Then I got hit with a heap more.

     

    We are trying to upgrade from a 3900 (v10) to a vCMP guest (v11.6). Can anyone suggest a smooth process?

     

  • rfc19's avatar
    rfc19
    Icon for Nimbostratus rankNimbostratus

    Hello,

     

    Unfortunately not. We are migrating from the 3900 -> vCMP Guest and cannot touch the 3900 as it's currently in production. To limit the downtime, we are trying to deploy in parallel.

     

    Thanks

     

  • Hello rfc19, Did you get a solution for your querry? I am also getting same error while migrating from 3900 to vCMP .

     

  • rluhrman_127985's avatar
    rluhrman_127985
    Historic F5 Account

    For future admin's running into this error, using an SCF is much more appropriate for migrations than UCS's as the SCF is a single Text File and can be edited and then loaded via TMSH commands. (don't forget to also upload the .zip file with the keys/certs)

     

    v11-v13

     

    v9-v10