Junos vrrp not working almost always means one of five configuration mismatches between the two routers: a different group ID or virtual IP address, an authentication type or key mismatch, a VIP configured without the priority 255 and preempt combination that address ownership requires, a track-interface setup silently dropping priority, or a firewall filter on the interface blocking VRRP's IP protocol 112. This guide covers the check order before you start changing live gateway configuration.
This guide is written against Junos OS 21.1R1 and later, which is the release Juniper's own VRRP examples have been revalidated against. VRRPv3 removes the authentication-type and authentication-key statements entirely, so if you are troubleshooting a VRRPv3 group, Root Cause 2 below does not apply and you need a different, non-VRRP authentication mechanism if authentication is required.
What "VRRP Not Working" Actually Looks Like
Two distinct failure patterns both get reported as VRRP being broken. The first is no master ever getting elected -- both routers sit in Init state indefinitely. The second is a split-brain where both routers simultaneously believe they are Master, which is more dangerous because it causes duplicate IP and MAC address responses on the LAN. Identify which one you have before proceeding.
show vrrp
Gives you a fast summary of group state, local priority, and the virtual IP on each router. Run it on both routers side by side.
Diagnostic Order
show vrrp detail
Shows the advertisement timer, the configured versus active priority, and whether a tracked interface or route has reduced the priority from its configured value. During the VRRP startup-silent-period, Juniper's own documentation notes that Master priority will read 0 and Master router will show your own IP address -- that is expected during startup and not a fault by itself.
show arp | match <virtual-mac>
Confirms which physical router is actually answering for the virtual MAC address (00:00:5e:00:01:xx, where xx is the VRRP group number in hex) on the LAN. If this does not match what show vrrp reports as Master, you likely have a stale ARP cache entry or a genuine split-brain condition.
Root Cause 1: Group ID or Virtual IP Mismatch Between Routers
This is the most common cause reported on r/Juniper, particularly during VRRP decommissioning or migration work. If the VRRP group number or the configured virtual-address does not match exactly on both routers, each one effectively runs its own independent, single-member VRRP group and no real election happens between them.
set interfaces ge-0/0/0 unit 0 family inet address 203.0.113.1/24 vrrp-group 1 virtual-address 203.0.113.254
Confirm this statement is byte-for-byte identical, including the group number, on both routers with show interfaces ge-0/0/0 unit 0 | display set.
Root Cause 2: Authentication Type or Key Mismatch
VRRP (IPv4 only, under VRRPv2) supports simple or MD5 authentication, and both the type and the key itself must match exactly on every router in the group. A mismatched key does not always produce an obvious error -- it can silently prevent the backup router from accepting advertisements from the primary.
set interfaces ge-0/0/0 unit 0 family inet address 203.0.113.1/24 vrrp-group 1 authentication-type md5
set interfaces ge-0/0/0 unit 0 family inet address 203.0.113.1/24 vrrp-group 1 authentication-key "$9$examplekey"
Remember that VRRPv3 does not support authentication-type or authentication-key at all -- if you have enabled version-3, remove these statements rather than trying to troubleshoot why they are not taking effect.
Root Cause 3: Priority Not Set to 255 When VIP Matches the Interface Address
If you configure the virtual IP address to be identical to a router's own physical interface address -- making that router the address owner -- Junos requires the priority on that router to be set to exactly 255, and requires preempt to be enabled. Skipping either requirement is a documented misconfiguration that produces unpredictable election behavior.
set interfaces ge-0/0/0 unit 0 family inet address 203.0.113.1/24 vrrp-group 1 priority 255
set interfaces ge-0/0/0 unit 0 family inet address 203.0.113.1/24 vrrp-group 1 preempt
In most modern designs the virtual IP is a separate address from both routers' physical addresses specifically to avoid this constraint -- if that is your design, the default priority of 100 on the backup and a higher explicit priority on the intended primary is simpler to reason about.
Root Cause 4: Track Interface Silently Dropping Priority
A tracked interface or route with a priority-cost reduces the VRRP group's effective priority when the tracked object goes down, which is the intended behavior for forcing failover -- but it is also a common source of confusing symptoms when the tracked interface flaps for unrelated reasons, repeatedly forcing elections that look like instability rather than a deliberate design.
set interfaces ge-0/0/0 unit 0 family inet address 203.0.113.1/24 vrrp-group 1 track interface ge-0/0/1 priority-cost 100
Check show vrrp track detail to see exactly which tracked object is currently reducing priority and by how much, rather than guessing from the aggregate priority value alone.
Root Cause 5: Firewall Filter Blocking VRRP (IP Protocol 112)
Less common but worth checking if the first four causes rule out: a loopback or interface firewall filter that does not explicitly permit VRRP traffic can silently drop advertisement packets, particularly after a filter rewrite that forgot to carry forward a VRRP permit term. One documented Juniper KB notes a related edge case where a loopback filter referencing protocol vrrp does not match correctly when VRRP is configured with MD5 authentication -- worth checking specifically if you use both a loopback filter and MD5 auth together.
show firewall filter <filter-name> | match vrrp
Quick Reference: Symptom, Cause, Fix
| Symptom | Likely Cause | Fix |
|---|---|---|
| Both routers stuck in Init | Group ID or VIP mismatch | Verify identical group number and VIP both sides |
| Backup never sees advertisements | Authentication type/key mismatch | Match authentication-type and key exactly |
| Erratic election when VIP equals interface address | Priority not 255, preempt missing | Set priority 255 and preempt on the address owner |
| Frequent unexplained re-elections | Flapping tracked interface | show vrrp track detail, review priority-cost design |
| Advertisements silently dropped | Firewall filter missing VRRP permit | Add explicit protocol vrrp accept term |
Verification
show vrrp detail
Interface: ge-0/0/0.0, VRRP-Group: 1, VRRP-State: master
Priority: 200, Advertisement-interval: 1s
Authentication-type: none
Preempt: yes, VIP count: 1, VIP: 203.0.113.254
One router should report master and the other backup, with matching VIP, matching authentication settings, and no unexpected priority reduction on the detail output. Test a controlled failover by disabling the tracked interface deliberately, with out-of-band access ready, rather than assuming the design works from configuration alone.
Full configuration reference is in Juniper's TechLibrary. Configuring VRRP | Junos OS. VRRP itself is defined in RFC 3768.
Frequently Asked Questions
Why do both my VRRP routers show Master at the same time?
This split-brain condition is usually caused by an authentication mismatch or a blocked advertisement path preventing the backup from ever hearing the primary's advertisements. Check show vrrp detail on both routers and confirm authentication settings and the advertisement path match exactly.
What priority value makes a router the VRRP primary?
Priority ranges from 1 to 255, with 255 reserved specifically for the router that owns the virtual IP address as its own physical interface address. For a non-owner design, any value from 1 through 254 works, with the default backup priority being 100 and the higher value winning the election.
Does VRRPv3 support authentication?
No, VRRPv3 does not support the authentication-type or authentication-key statements at all. If authentication is required on a VRRPv3 group, you need a separate, non-VRRP authentication mechanism.
Why does show vrrp show priority 0 during startup?
During the configured startup-silent-period, Junos intentionally shows Master priority as 0 and Master router as your own IP address while the election process completes. This is expected behavior, not a fault, and resolves once the silent period ends.
Can I use the same VRRP group ID for multiple groups on one interface?
Only if network-services is configured in enhanced-ip mode. In standard IP mode, reusing the same VRRP group ID on multiple sessions on the same physical interface while VRRP delegation is enabled can make other virtual IP addresses in those sessions unreachable when one logical interface is deleted.
Related guides: browse our routing and switching category hub for more first-hop redundancy and BGP guides, see our SRX chassis cluster failover not working guide for the equivalent HA mechanism on security platforms, and check our Junos BGP prefix limit exceeded guide if the same router is also dropping BGP sessions.
Juniper, Junos, MX, SRX, EX and QFX are trademarks of Juniper Networks, Inc. juniperclient.com is independent and unaffiliated.
Discussion (0)