Hi all. For a long time we had been hoping to use VRRP on VLAN interfaces but never worked correctly as the vlan interface always had the same mac as the real ethernet interface it was on and couldn’t be changed to a virtual address. Every now and then I upgrade a couple of test boxes we have and see if it has been resolved. Today I tried 2.9.45 but still no joy however I noticed in the changelog for V3 that there was a “new VRRP implementation” so I stuck RC2 on and it worked. I have tried all sorts of fail-over testing and seems perfect. I was wondering what is being done differently to get round the original issue.
Hmm yeah, figured that one out a few seconds after posting my Silly Tosser™ question… The IP isn’t showed as a dynamic address however, I guess that’s what confused me a bit…
Nope but looks to behave as per design which is the important bit. Just need to test various other parts of V3 now before leaving for a week then roling out on a small section of the network Let me know how your testing goes too.
Why are you using 198.19.3.1/32 as the VRRP address? With a /32 netmask you wont get any other devices on that vlan to reach it. Try using a /24 class C with .251 on one vlan interface, .252 on the other and .254 as the VRRP address.
i also have vrrp and vlans working correctly…
i only had to do 1 thing…
i put in the script section
a disable and enable script of the interfaces.
if i don’t do that it doesn’t work.
in the on master i have
/interface vlan set VLAN300-VmwareInstallNetwork disabled=yes
/interface vlan set VLAN300-VmwareInstallNetwork disabled=no
/interface vlan set VLAN900-Management disabled=yes
/interface vlan set VLAN900-Management disabled=no
/interface vlan set VLAN100-Exchange disabled=yes
/interface vlan set VLAN100-Exchange disabled=no
/interface vlan set VLAN101-NS disabled=yes
/interface vlan set VLAN101-NS disabled=no
/interface vlan set VLAN102-MAIL disabled=yes
/interface vlan set VLAN102-MAIL disabled=no
/interface vlan set VLAN103-NTHOSTING disabled=yes
/interface vlan set VLAN103-NTHOSTING disabled=no
/interface vlan set VLAN104-LNXHOSTING disabled=yes
/interface vlan set VLAN104-LNXHOSTING disabled=no
/interface vlan set VLAN501-COLO-VMWARE-piwi disabled=yes
/interface vlan set VLAN501-COLO-VMWARE-piwi disabled=no
/interface vlan set VLAN105-STORAGE disabled=yes
/interface vlan set VLAN105-STORAGE disabled=no
/interface vlan set VLAN106-SHARED-EXCHANGE disabled=yes
/interface vlan set VLAN106-SHARED-EXCHANGE disabled=no
in the on backup i have the same.
if i run this now, and unplug one router; evrything switches over perfectly and works.
without the enable and disable of the vlans, thay stay red and don’t work.
Interesting! The only way I can get my vrrp interfaces from being red is by giving an IP to it’s parent interface as well as assigning an IP to the vrrp interface. Ok.. I’m going to try this.
We are also using VRRP and vlans, i had to add the disable on/off to vrrp “on master” and “on backup” script.
(not needed in some early 3.0rc.. nevermind it works anyway)
Actually we are running 2 RSTP Switches → bonding → VRRP → 10 VLANS to eliminate SPOF´s.