F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

igssv's avatar
igssv
Icon for Cirrus rankCirrus
Oct 04, 2023

UCS Import Errors on BIG-IP VE (12.1.5.2) from i2800 – Need Assistance

Dears, I’m trying to import a UCS file obtained from the existing device (i2800 v12.1.5.2) into the VE version V12.1.5.2, but it’s not going smoothly. The command I execute during import is: load ...
security
Paulius's avatar
Paulius
Icon for MVP rankMVP
Oct 05, 2023

igssv The usernames and passwords should be the same as the old F5 device because everything is imported from the UCS into the new F5.

igssv's avatar
igssv
Icon for Cirrus rankCirrus
Oct 07, 2023

 

Hi, Paulius,
As expected, then. Without asking our client, we won't know the account information for the old F5 device. We were hoping to find an approach that wouldn't inconvenience them, like a method of not importing user information. If it's difficult, I'll consider consulting with the client. Thank you so much for all of your responses!

  • Paulius's avatar
    Paulius
    Icon for MVP rankMVP
    Oct 07, 2023

    igssv If you have access to the old F5s you can change the admin and root password, then create a UCS, and finally import that new UCS which should have the new usernames and passwords. Sadly, sometimes in order to get the job done correct you will have to ask for additional information. It's better to inconvenience them a small amount now then a large amount in the future.

    • igssv's avatar
      igssv
      Icon for Cirrus rankCirrus
      Oct 07, 2023

      Thank you for the advice! Unfortunately, it’s already Saturday here in Japan, so I resolved the issue by customizing the UCS as follow.

      ```
      On the Virtual Edition (VE), the following steps were executed:
      - Ran `f5mku -r <old master key>`
      - Executed `tmsh save sys conf` to save the system configuration
      - Obtained the UCS

      In old UCS:
      - Added `fallback true` to the `auth source` section in `bigip.conf` (which was initially set to `type radius`)
      - Copied the `encrypted-password` for `auth user admin/root` from the UCS on the VE over to `bigip_user.conf`
      - Changed `sys httpd` in `bigip_base.conf` to `ALL`
      ```

      Thank you so much for your consistent guidance! With your help, I've successfully reached a point where I can review the client’s configurations without any issues!