[Solved] VRRP: Bug in ROS 4.11

Hi guys

I have a question for you: Since the update to ROS 4.11 I can’t change priorities of the VRRP interfaces anymore. Neither in the console nor with WinBox.

For example:

[admin@rb1100] > /interface vrrp print
Flags: X - disabled, I - invalid, R - running, M - master, B - backup 
 0    B name="gateway" mtu=1500 mac-address=00:00:5E:00:01:31 arp=enabled interface=bridge vrid=49 priority=90 interval=1 
        preemption-mode=yes authentication=none password="" on-backup="" on-master=""

Can anyone confirm, that we just get an error message when trying to change priority (see below)?

[admin@rb1100] > /interface vrrp set gateway priority=50 
virtual router with such interface and vrid already exists

Of course it does exist, but it should still be possible to change priority :slight_smile:

Would appreciate it, if one of you guys could quickly test this on a lab router. Maybe I’ll have to downgrade to ROS 4.10 to get it back working.

Cheers,
gartoffel

BUMP…

Not priority but name as well.


[dave@router1] /interface vrrp> set 1 authentication=ah
virtual router with such interface and vrid already exists
^^^^ WRONG ^^^

[dave@router1] /interface vrrp> set 1 name=test
already have device with such name
^^^ WRONG ^^^

If I understand correctly, you are telling me that not only priorities but also names and authentication can no longer be changed in ROS 4.11? I can confirm this, so it’s worth a bugreport, right?

Cheers,
gartoffel

Hello!

Have you send a bug report to Mikrotik? Do you have any answer?

I do heavy use of VRRP and I was planning on upgrading to 4.11 this week…

Thanks,

Hi leonset

Yes, I filed a bugreport, but Janis @MikroTik doesn’t seem to be able to reproduce the bug. Would be great if someone else could confirm…
I’ll keep you posted!

Cheers,
gartoffel

Short update:
Janis is looking into this matter right now on one of our production routers. It won’t be long until I can give you further details.

Cheers,
gartoffel

Great! Thanks for the update.

I hope it gets solved soon!

Update: Janis just wrote me an e-mail.

OK, developer are looking into this problem. Thanks.

So it seems, that after having reconstructed the problem on a production machine, they are finally trying to figure out what’s wrong.

For those interested (may be important):

[admin@rb1100] > /system package print               
Flags: X - disabled 
 #   NAME                        VERSION                        SCHEDULED              
 0   system                      4.11                                                  
 1   routerboard                 4.11                                                  
 2 X mpls                        4.11                                                  
 3 X dhcp                        4.11                                                  
 4 X wireless                    4.11                                                  
 5 X ipv6                        4.11                                                  
 6 X hotspot                     4.11                                                  
 7   routeros-powerpc            4.11                                                  
 8 X ppp                         4.11                                                  
 9   routing                     4.11                                                  
10   advanced-tools              4.11                                                  
11   security                    4.11

Cheers,
gartoffel

Bump,

Have the same issue of sorts, updating the priority makes the vrrp interface go to an invalid state.

[admin@MikroTik] /interface vrrp> print
Flags: X - disabled, I - invalid, R - running, M - master, B - backup
0 I name=“VRRP Uplink” mtu=1500 mac-address=00:00:5E:00:01:01 arp=enabled
interface=VLAN256 Unknown vrid=1 priority=50 interval=1
preemption-mode=yes authentication=simple password=“xxxxxx”
on-backup=“” on-master=“”

[admin@MikroTik] /interface vrrp> export

jan/02/1970 12:09:08 by RouterOS 4.11

software id = 19ZE-8KCJ

/interface vrrp
add arp=enabled authentication=simple comment=“” disabled=no interface=
“VLAN256 Unknown” interval=1 mtu=1500 name=“VRRP Uplink” on-backup=“”
on-master=“” password=xxxxxx preemption-mode=yes priority=50 vrid=1


Short term solution is to downgrade?

Well, I haven’t heard from MikroTik Support since Janis told me, that developers are looking into this matter.
So, yes: Short term solution is to go back to ROS 4.10…

Cheers,
gartoffel

Hi guys!

I just received another mail from Janis:

As far as i know problem is solved and will be included in the next release.
You can use latest v5.0beta version if you like while v4.12 is on its way.

Well, then let’s all hope, that 4.12 will be released soon! :slight_smile:

Cheers,
gartoffel

What is the time frame for all the new releases?? 4.12, 5.0???

Are you kidding? :wink:

4.13 is out already and the bug is fixed as promised by MT. See http://www.mikrotik.com/download.html for more details.

Cheers,
gartoffel

Just upgraded one of my routers in a VRRP cluster to 4.13 and get the same issue, change the priority and it turns to invalid :frowning:

Can anyone confirm that it is actually fixed?

I am having the very same issue, I opted to work with netwatch and enable/disable routes. VRRP on mikrotik has given us a lot of headaches… :confused: :confused: :confused:

And there is no firewall rule blocking access to the router? If you are unsure, try disabling the firewall and change priorities once again. I just checked: It really is working here…!

Cheers,
gartoffel

No firewall rules at all
What version are you running and which hardware are you using please

No firewalls, Works until priority is changed then invalid same as with 4.11.

I’m using ROS 4.13 with RB/1100.
I did a complete reset after upgrading, just to make sure, that there are no old issues, that I carry on. So maybe, this would help?

Cheers,
gartoffel