We have the following LTM: BIG-IP 10.2.0 Build 1789.156 Engineering Hotfix HF2 Need to convert it to VE but we are running Vmware ESXi 5.5 - so this means the VE we will need to be at least version 10.2.3 I have already backed up the Config from our physical LTM Appliance. But since the VE is version 10.2.3, will restoring the Config from the LTM appliance work? how would you recommend i go about handling this task? We need to convert our Physical appliance LTM version 10.2.0 build 1789.156 to a VM on Vmware ESXi 5.5

You have a couple options. I would start with restoring the UCS to the newer version with the 'no-license' and no-platform-check' options. After load, ensure it actually loaded with a 'tmsh load sys config' and check for errors. I have seen this work multiple times between versions--even from 10 to 11. If that doesn't work, you could try to upload a 10.2.0 ISO and hotfix to the VM and install to another partition and use switchboot to boot into that volume. Then load the UCS and upgrade to a third (or overwrite) to another volume. Make sure interfaces are disabled at the VM level to avoid conflicts, especially if this is production...

the ova shows 3 NIC's However our Model 1500 F5 has 1 Management Interface, 4 10/100/1000 interfaces, and 2 SPF ports am i supposed to add the NIC's to the VE? or will 3 NIC's suffice (1 Management, 1 Internal, and 1 External)

The problem is not the number of interfaces of the physical appliance but which one are in the configuration. The VE use interfaces Mgmt, 1.1, 1.2 and 1.3 interfaces by default. If in the 1500, you used SPF interface, named 2.1 in appliances, the configuration import will fail. The best way to upgrade is to delete configuration of NIC in the 1500 appliance before backup (remove Interfaces in VLANs, trunk and spanning tree configuration). there is no need to modify Self IP configuration. When it is not possible, import the configuration with errors. (Unsupported method, be sure you do not change config file format) after import, edit big.local file and remove part of configuration generating errors, and try to load configuration with: tmsh load sys config

when you say (remove Interfaces in VLANs, trunk and spanning tree configuration), are you referring to the configuration on the Switch? or the 1500 appliance?

The goal is to create a backup file without these configuration... if you delete it in the switch, the configuration will stay in F5 backup :)

Need to Convert our LTM to VE

26 Replies

Stanislas_Piro2
Cumulonimbus
Jun 24, 2015
The SOL14906 is for version 11.1 and above.

You can install VE 11.5 and load UCS created on 10.2.
jblanc03_156148
Nimbostratus
Jun 24, 2015
after trying Drewvs's suggestion,

here is what I get
- Stanislas_Piro2
  Cumulonimbus
  Jun 24, 2015
  you need to reinstall licence...
- Drew_24528
  Nimbostratus
  Jun 24, 2015
  The box/VM needs to be licensed first :) You can't move a license from physical to virtual if that's what you wanted to do.
jblanc03_156148
Nimbostratus
Jun 24, 2015
can I just use the same license that's on my physical appliance model 1500?

I thought the rma option does not check the license. thought that was the hole purpose of it.
- Drew_24528
  Nimbostratus
  Jun 24, 2015
  No. The RMA option is so it doesn't import/overwrite an existing license. This is the process you follow when you are upgrading hardware--like you're doing. You of course need an active support contract/agreement with proper licensing for whatever box you are installing this on. You could speak to F5 support to see if this is possible or what they could do for you, I highly doubt they will allow this and would require the purchase of an additional license for the VM.
- jblanc03_156148
  Nimbostratus
  Jun 24, 2015
  even though I am simply moving my current Licensed, Appliance model 1500 to a VE??????
- Drew_24528
  Nimbostratus
  Jun 24, 2015
  Correct, call F5 they may be able to help/clarify your options.
jblanc03_156148
Nimbostratus
Jun 30, 2015
Hey i have a license and i installed it to our VE.

Now i have a question regarding backup up the current UCS file on our Physical F5

i have the option of either Including or Excluding Private key.

Should I?, or Should I not? include the Private Key in this senario?
boneyard
MVP
Jun 30, 2015
if you want to use the VE instead of your physical at some point then you need the private keys.
jblanc03_156148
Nimbostratus
Jul 03, 2015
this is becoming more difficult than i expected.

I have spent hours upon hours trying to get this UCS file loaded successfully to my VE.

i have made changes to bagpipe_base.confg , bagpipe_sys.confg, and bagpipe.conf

no luck after making the changes and then re-packing the UCS and trying to load again.
- boneyard
  MVP
  Jul 04, 2015
  if you are looking for assistance then it would help telling why it doesn´t work for you.
Kevin_Stewart
Employee
Jul 04, 2015
Just thinking out loud here, but you may have more success with a single configuration file (scf):

https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-concepts-11-3-0/tmos_single_config_file.html?sr=46608210

An scf is less platform dependency.