Very tricky one to track down why a failover firewall configuration would never promote it's CARP IP's to MASTER status.
Turns out you must only have a single NIC on a vSwitch with a guest VM being used as a MASTER for CARP, otherwise will always show as BACKUP.
Can't even have a NIC in the standby list, 2nd NIC has to be completely removed.
There may well be a setting in the advanced options somewhere that might get this to work, if anyone has done this please let us know!
skip to main |
skip to sidebar
Labels
- .net (1)
- .net 2 (2)
- active directory (1)
- backup (3)
- bl460c (1)
- blades (1)
- c3000 (1)
- cacti (1)
- cms (2)
- device manager (1)
- drdb (1)
- DRM (1)
- ESXi (8)
- exchange (1)
- ha (1)
- hp (3)
- iis (5)
- iis7 (1)
- KB (1)
- linux (1)
- monitoring (1)
- MS (2)
- network (1)
- nics (1)
- objectdock (1)
- office 365 (1)
- open source (2)
- openfiler (2)
- osx (1)
- php (1)
- platespin (1)
- powershell (2)
- prtg (1)
- registry (1)
- rpath (1)
- rs (1)
- san (3)
- sas (1)
- seagate (1)
- server 2008 (1)
- Sky (1)
- snmp (2)
- sophos AV linux RHEL Centos (1)
- spam (2)
- sql (1)
- sql server 2005 (1)
- sql server 2008 (1)
- SSH (2)
- switch (1)
- technet (1)
- update (1)
- usb (1)
- VMDK (1)
- vmware (7)
- windows (3)
- windows 2008 (1)
- wmf (1)
- wsus (2)
- x64 (1)
- xdelta (1)
- xp (1)
2 comments:
I acctually had the same problem but not beeing able to have failover wasn't the solution. So what we did was to stack 2 switches and ran link aggregation over the ports that were connected to vmware. Be very careful and make sure that the failover policy is "Route based on ip hash" when using link aggregation.
Old post, but I figured I'd update since I found you on Google.
Turns out you need to set an Advanced setting for the hosts on this VMware portgroup.
Set Net.ReversePathFwdCheckPromisc to 1. This prevents these packets from going out 1 interface on the team and back on the other.
Post a Comment