You won't need the KVM to access the virtualized servers at all. all ESX hosts (including 3i) can be accessed by a free VI client application that allows you to control, configure and interact with the VMs.
That said, an IP KVM can be very useful when remotely monitoring the reboot of the ESX host itself.
Regards,
Iain
You won't need the KVM to access the virtualized servers at all. all ESX hosts (including 3i) can be accessed by a free VI client application that allows you to control, configure and interact with the VMs.
That said, an IP KVM can be very useful when remotely monitoring the reboot of the ESX host itself.
Regards,
Iain
His comment brings up something that might be interesting - the ability to see the consoles of the VMs at the console of the ESX host....You'd be able to mask the fact its an ESX host from a physical viewpoint unless you new the hotkeys to tap to switch.
Work much like the multiple tty consoles you can do anyway....
And in the process add more overhead and remove a nice seperation layer/security layer. The information security guys like the fact that you can't access any of the guests via the service console.
True, but as an extension that could be enabled by choice I think it could be handy as I could imagine some rare weirdness where you cannot get to the guest console via the web interface or VC and you need to get to a guest.
Thanks all for the info!