VRRP with VMware CHR

RouterOS Beginner Basics
1

Hi Guys,

I’m currently using two VyOS in VMware VM’s to route few subnet, and also have them redundant with VRRP,
recently I came across RouterOS and immediately made two VM’s for CHR to test if it will fit my needs,
and I’m stuck with VRRP, what ever I do both routers become Master,

please check current output:
R1

/interface vrrp print detail
Flags: X - disabled, I - invalid, R - running, M - master, B - backup
0 RM name=“vrrp1” mtu=1500 mac-address=00:00:5E:00:01:01 arp=enabled
arp-timeout=auto interface=ether1 vrid=1 priority=200 interval=1s
preemption-mode=yes authentication=none password=“” on-backup=“”
on-master=“” version=3 v3-protocol=ipv4

R2

/interface vrrp print detail
Flags: X - disabled, I - invalid, R - running, M - master, B - backup
0 RM name=“vrrp1” mtu=1500 mac-address=00:00:5E:00:01:01 arp=enabled
arp-timeout=auto interface=ether1 vrid=1 priority=128 interval=1s
preemption-mode=yes authentication=none password=“” on-backup=“”
on-master=“” version=3 v3-protocol=ipv4

no extra configuration have been made, just a fresh install with one interface E1000E for each and tried to create VRRP.

can you please help with this.

2

A few things.

  • You should be using VMXNET3 virtual NIC. It is higher performance than e1000 and will give you less problems.

  • You need to enable promiscuous mode in the hypervisor to allow VRRP control packets to flow between the two CHR guests.

I hope this helps.

3

Thanks for the information @nz_monkey,

I created 2 fresh installed CHR 6.36rc40, both with VMXNET3 Interfaces, and changed the the Distributed Port Group to Accept promiscuous mode, but still both shows as RM.

R1:

/interface vrrp print detail
Flags: X - disabled, I - invalid, R - running, M - master, B - backup
0 RM name=“vrrp2” mtu=1500 mac-address=00:00:5E:00:01:31 arp=enabled arp-timeout=auto interface=ether1 vrid=49 priority=254
interval=1s preemption-mode=yes authentication=none password=“” on-backup=“” on-master=“” version=3 v3-protocol=ipv4



/ip address print detail
Flags: X - disabled, I - invalid, D - dynamic
0 address=172.16.40.183/24 network=172.16.40.0 interface=Management actual-interface=Management

1 address=172.16.140.51/24 network=172.16.140.0 interface=ether1 actual-interface=ether1

2 address=172.16.140.254/32 network=172.16.140.254 interface=vrrp2 actual-interface=vrrp2

R2:

/interface vrrp print detail
Flags: X - disabled, I - invalid, R - running, M - master, B - backup
0 RM name=“vrrp2” mtu=1500 mac-address=00:00:5E:00:01:31 arp=enabled arp-timeout=auto
interface=ether1 vrid=49 priority=100 interval=1s preemption-mode=yes authentication=none
password=“” on-backup=“” on-master=“” version=3 v3-protocol=ipv4



/ip address print detail
Flags: X - disabled, I - invalid, D - dynamic
0 address=172.16.40.184/24 network=172.16.40.0 interface=Management actual-interface=Management

1 address=172.16.140.52/24 network=172.16.140.0 interface=ether1 actual-interface=ether1

2 address=172.16.140.254/32 network=172.16.140.254 interface=vrrp2 actual-interface=vrrp2

4

Hi Guys,


anyone facing the same issue please share your experience, I’m really stuck with this issue.

5

Hi again,

I think I have figured it out and made it work, just in case someone else stumble facing the same issue here is the fix:

I had to change the below setting for the Port Group for it to work:

Set Forged Transmits to Accept, this to make RouterOS communicate with each other to set the master and the backup
Set Promiscuous Mode to Accept, to be able to ping the VRRP IP.

Thanks for the help guys.

6

No problem.

Glad to hear you got it working.