If one PVS server fails clients using the Boot Device Manager ISO may attempt to retrieve the file tsbbdm.bin from a failed PVS server during boot but will quickly move on to the next PVS server in the list. This provides High Availability.īDM is the same as NetScaler in a way. It can detect when a PVS server is down and won’t send clients to that PVS server until it is back online. NetScaler is more helpful because it comes with monitors. Using this method is not 100% fail proof. I have tested this but if a PVS server is offline the results really are unpredictable. You could point option 66 towards a DNS record which resolves to all your PVS servers in a round robin fashion. If you use DHCP options 66/67 to hand out the TFTP server and boot file name, DHCP can only send clients to one IP address. The problem with PXE is that only one PXE server can reside on the same subnet. I have already gone over the PXE boot option with PVS which you can find here. To deploy NetScaler TFTP Load Balancing see here. You can also use PXE built right in to PVS or use DHCP via options 66/67. You can provide PVS boot information from an ISO generated by Boot Device Manager.
Using Citrix NetScaler you can load balance TFTP requests to deliver the bootstrap file to PVS Target VMs.
0 kommentar(er)
