Piotr

Hi,

I’m building High Available solution using Hyper-V and Microsoft Fail over
cluster. My target is to double all hardware to eliminate single point of
failure. I know how to provide iSCSI network redundancy, heart beat network
redundancy. I also know how to set up firewall redundancy.

Unfortunately weak point in my plan is public network redundancy. I tried to
find any solution for eliminating single switch and NIC point of failure (as
far as I know I can use teaming due not compatibility with Hyper-V issue). In
my opinion it is quite probable that one NIC or switch will be down
(especially that I met Cisco switch completely stopped to work). Only advice
I’ve got is to provide second, stand bay network and when I will find NIC or
switch be down I can manually change virtual switch to another adapter
(unfortunately in my case it has to be automatic process).

However I have still hope someone can give me answer for this question.

Best Regards