Welcome to the BIG-IP LTM VE forums

The OVA is for ESX/ESXi. For workstation please download the standalone zip file that contains the .vmdk and .vmx. The documentation for the LTM VE covers this in detail if you'd like to know more.

I am experiencing some problems with deploying the OVF (as it is called in vSphere, although I realize it is an OVA file) template to the vSphere ESX 4.0 environment. I'm not 100% sure that it is an F5 issue, but I figured I would post my problem in this forum, just in case others had experienced the same problem. Upon trying to deploy BIGIP LTM-VE, a 'configSpec.flags.cfgVersion' error is received. If I check the vpxd log, I also notice a 'vim.fault.PlatformConfigFault in creating VM' error as well. Any takers?

Lambino - That's a new one for me. I'll keep my eyes out though, and see if I see anything regarding that kind of an error from anyone else either on the forums or internally.

 

 

Colin

Thank you for LTM VE. I have it working with VirtualBox on my Apple Mac. I'm running two LTM virtual machines and I have the virtual units synchronized and currently running in ACTIVE/ACTIVE mode.

Lambino33: Are you running in a mixed ESX 3.5/4.0 environment?

Hey Dev Central,

 

 

I've set up the BIG-IP VE on my mac and have it up and running in Fusion VMware. I've configured a management IP and internal and external self IPs . I'm having a real basic and frustrating problem.

 

 

I've set up a simple Python webserver at 192.168.1.8 on Port 8001. This server works fine, and is located on my home subnet of 192.168.1.X . My actual MacBook is on 192.168.1.200. My router is 192.168.1.1.

 

 

For the BIG-IP, my internal self IP is 192.168.1.245; and my external is 10.80.80.245.

 

 

I try and set up a pool with one member defined right on my subnet as 192.168.1.8 with port 8001, and an http monitor is set. The kicker: I can't get it to light up green.

 

 

I've set the default gateway in Network settings to my router's IP, (is this correct??) but I *cannot* ping my router in the VMware command line. I can, however, ping my self IPs from the command line. Can anyone offer insight as to

 

why I can't get my one humble pool member on line ?

 

 

Is this an issue with the VM ware, or the BIG-IP config?

 

 

Thanks !

 

 

dwc

 

 

 

 

I want to try "virtualbox" since I already use it and

am comfortable with it. Which download did you use:

BIGIP-10.1.0.3341.1084.ova.zip

Image fileset for VMware ESX/i Server v4.0

-or-

BIGIP-10.1.0.3341.1084.zip

Image fileset for VMware Workstation v7.0

I am going to try to use the ESX/i Server.

And do you have any advice to "turn it up" under

virtualbox. A quick search and this URL seems

to indicate:

 http://forums.virtualbox.org/viewtopic.php?f=1&t=28677&p=127833&hilit=vmware+imagep127833 
  
     Subject "VMware ESXi to VirtualBox migration?" 
  
     VBOX can use images in vmdk format directly. Create  
     a new guest, point to the existing image or better  
     a copy of this. 
  
     Dont know if all vmdk-formats are supported. If yours  
     is not supported, you can change format with  
     "vmware-vdiskmanager". 
  
     Best way is one great vmdk instead of 2 GB splitting. 

Thanks in advance

Jon

net_enthuse: It sounds like your management and internal networks may be conflicting in their address space. The default mgmt interface IPV4 address is 192.168.1.245/24.

 

Thanks qe,

 

 

I can get into the BIGIP GUI at 192.168.1.245 as you suggested. But this amounts to logging into the internal self-IP ( at .245) and using it as a management port.

 

 

And now I can even get my pool members up and running. You would think that it would be better to stay out of the 192.168 network to avoid conflicts. However, I can't seem to get into the BIGIP GUI when I use an automatically designated mgmt IP, such as 172.16.X.X.

 

 

Moreover, the only time I can get *any* communication with the BIG IP (pool members, mgmt, VIPs, you name it ) is if I stay on my own actual subnet of 192.168.1.X.

 

 

I get the feeling that this is not as it should be.

 

 

A router issue ? Or perhaps is the VMware (Fusion) complicating things?

 

 

net_enthused: sounds like a routing issue. Perhaps these help troubleshooting?

 

 

1) b mgmt

 

This command shows you the IP that the mgmt interface is set to and what one can connect a web browser to over HTTPS

 

 

2) b self

 

This command shows the self IP addresses of the BIG-IP on the dataplane side (if any are configured - these are not commonly used to access the configuration GUI)

 

 

3) b route

 

This command shows the active routing table for the TMM (dataplane)

 

 

4) netstat -rn

 

This command shows the active routing table for the control plane (mgmt port, configuration GUI over HTTPS)