Need to Convert our LTM to VE

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 :)

ok. i just wanted to clarify what you were referring to.

the problem is. cant really delete any configuration on the appliance while its in production. I was hoping to stand the VE up (different IP settings so there is no conflicts etc.) without having to take the appliance offline for testing purposes. Then when everything is ready, we would eventually cut over to the VE.

I guess there is no real way to have redundancy when your converting to VE then?

you can make a backup now of the existing 1500 config, modify that config and load it on the VE. as long as you don't hook up the VE yet to the network then there shouldn't be a conflict.

if you read Stanislas's comment,

You cant use the config thats currently on the 1500 appliance since it is using the SFP ports.

"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"

Ok I need help with the tmsh command.

I am following F5 guide to using the no-platform-check option when using tmsh command https://support.f5.com/kb/en-us/solutions/public/14000/900/sol14906.html

I am typing in the command just like it shows in the example but its not working

I am running the tmsh command with the no-platform-check option, but it does not recognize the no-platform-check option. Instead it thinks I am trying to specify a filename.

what am I doing wrong?

Upload the ucs to /var/local/ucs/ Drop to tmsh shell on the CLI: tmsh

load sys ucs UCSNAME rma

The no-license and no-platform-check option are present in 11 not version 10 of TMOS.