Forum Discussion
Erik_Aldor_3151
Nimbostratus
NimbostratusInterfaces uninitialized?
I am testing the VE in both Vmware ws 7 and Virtualbox. Unfortunatly with the same result. I can't get the interfaces to work. I have added them as host only but the interfaces show up as "UNINITIALIZED" and without a mac address. I can't see that I get any connectivity at all on the interfaces. The release notes mention UNINITIALIZED but that it should work anyway.
- I noticed this on my VE as well, and the 'uninitialized' label went away as soon as I defined the VLANs in the LTM.
- Erik - Which interfaces won't work? Can you at least connect to the VE via the management IP to get to the web interface?
Colin
David__PaschAltostratus
This was my results running a V12 VE in Virtual box based on the set up found at:
 
 
Erik_Aldor_3151Thanks for the replies, no problem connecting to the management address and logging on. I tried to define some vlans and added the interfaces to them, but still uninitialized and no mac. Should not be any network issues with the networks either.
(Host only interface /24) mgmt 192.168.1.100
(Host only interface /24)"Int" vlan untagged interface 1.1 added self ip 192.168.2.100
(Host only interface /24)"Ext" vlan untagged interface 1.2 added self ip 192.168.3.100
However, as a recap I experimented mostly on a linux with Vbox and the VmWorkstation was on a win7. I'll try it on a XP with VmWorkstation as soon as I can.- What does "b vlan" look like?
- Erik_Aldor_3151Got it working for Virtualbox in the ltm log I had the error message "unable to attatch to pci device" The default when adding a network interface in Virtualbox is "PCnet-FAST III". I changed it to "Intel PRO/1000 MT Server" and now it works fine. Couldn't find how to change the type of nework interface in vmware workstation so my problem still remains there.
- JRahm
Admin
You can edit the VE vmware config file if they are different, but it should add as e1000. 
Nomios_NomiosHave you find a solution?
I have the same problem, but i have installed on a ESX 4.0.
jschilenI got it working on ESXi 4 by doing a similar thing to the Virtualbox fix. Using the vSphere client I downloaded the .vmx file and for the interfaces that weren't initializing I added the line
ethernetX.virtualDev = "e1000"
Where X is the interface number.
Then uploaded it.
qe_102628Nomios and Jeremiah: Try downloading the OVA and deploying it within ESX/ESXi. It's a far simpler method for getting a LTM VE Trial up and running. You end up with the correct NIC configuration from the get go.- jschilenI downloaded the ova and imported it to my esxi box with vmware converter and that's how it came out.
