I'm going to install fedora onto multiple servers ( probably 3 ) by network booting, using the PXE protocol. All of this will be done on my home network on a table. I'll send the finished product to the datacenter for hosting.
I've been reading that a kvm over ip switch might be better and less expensive because each service processor will have licensing fees for its firmware and need it's own connection. That means 3 separate connects with 3 separate ip's to manage them - while kvm over ip will need only one connection.
The goal with all of this is to be able to install the operating system by PXE ( and manage it remotely once at the datacenter ), which means I'll need a remote management tool that can tell BIOS to boot by PXE, before the main server power is tuned on (and PXE card fires ), and I'll need a pc card capable of network boot.
Whatever the best approach is, I'm looking for information to help me understand how a kvm over ip starts the network boot process, and if this is really a better way to network boot and manage the servers than a service processor.
Thank you
I've been reading that a kvm over ip switch might be better and less expensive because each service processor will have licensing fees for its firmware and need it's own connection. That means 3 separate connects with 3 separate ip's to manage them - while kvm over ip will need only one connection.
The goal with all of this is to be able to install the operating system by PXE ( and manage it remotely once at the datacenter ), which means I'll need a remote management tool that can tell BIOS to boot by PXE, before the main server power is tuned on (and PXE card fires ), and I'll need a pc card capable of network boot.
Whatever the best approach is, I'm looking for information to help me understand how a kvm over ip starts the network boot process, and if this is really a better way to network boot and manage the servers than a service processor.
Thank you
