Rolling Release: A non-existent interface in VRRP doesn't trigger warning or error


#1

Putting a non-existent interface as part of a VRRP Group doesn’t trigger an error message. VRRP just fails to load.

admin@route3:~$ show interfaces ethernet eth0
Invalid interface [eth0]

admin@route3:~$ conf
[edit]
admin@route3# delete high-availability vrrp group LAN interface
[edit]
admin@route3# set high-availability vrrp group LAN interface eth0
[edit]
admin@route3# commit
[ high-availability vrrp ]
Reloading the VRRP process

[edit]
admin@route3# run show vrrp
VRRP is not running
[edit]


admin@route3# delete high-availability vrrp group LAN interface
[edit]
admin@route3# set high-availability vrrp group LAN interface eth1
[edit]
admin@route3# commit
[ high-availability vrrp ]
Starting the VRRP process

[edit]
admin@route3# run show vrrp
Name       Interface      VRID  State    Last Transition
---------  -----------  ------  -------  -----------------
FOREMAN    eth1.22          22  BACKUP   7s
LAN        eth1              1  BACKUP   7s
ROUTING    eth1.254        254  BACKUP   7s
UNMANAGED  eth1.21          21  BACKUP   7s
VLAN3      eth1.3            3  BACKUP   7s
VLAN20     eth1.20          20  BACKUP   7s
VLAN254v6  eth1.254        255  BACKUP   7s
WLAN       eth1.9            9  BACKUP   7s
[edit]