FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: IVS VM has 2 default NICs and hangs on boot?

IVS VM has 2 default NICs and hangs on boot? 13 Jul 2016 17:19 #2343

  • Tony Gaspro
  • Tony Gaspro's Avatar Topic Author
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 1
  • Thank you received: 0
So I am using the IVS 4.1 OVF to deploy an IVS server to our VMWare environment (ESX 6), and once it is deployed, it is showing that it has 2 Network adapters (see screenshot 1).

Per the manual, after installation, I power on the VM and it hangs on getting IP info for eth1 (see screenshot 2) .

I have tried combinations of removing the second NIC, removing all NICs and recreating just one and am running into brick walls.

Has anyone run into this, and if so, what was the resolution?



IVS VM has 2 default NICs and hangs on boot? 14 Jul 2016 14:11 #2344

  • Christian Glattfelder
  • Christian Glattfelder's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 37
  • Karma: 7
  • Thank you received: 14

the IVS has two Interfaces as a result of the way it is built ; and it is imperative that you leave both of these interfaces in place, otherwise the IVS will not function.

Please try the following :
-import the IVS again from the OVF template ( you can reduce the number of cores and RAM to 1 and 1024 MB , but please leave it otherwise unchanged )
-make sure both the network interfaces are connected to the VLAN that your clients can reach
-start it up - should it hang again at the point where you described, send it a CTRL-ALT-DEL to reboot it gracefully ; the second time it should be able boot fully. ( This happens more often on networks where no DHCP server is present )
-then you can log on to the IVS using root / filewave , and use the imaging-control shell script to configure any networking parameters.

Best Regards,
Christian Glattfelder
Systems Engineer
FileWave (Europe) GmbH
  • Page:
  • 1