IP / Network Issue

Ubiquiti firewall: HSRP / VRRP virtual IP not responding

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
VendorUbiquiti
Operating systemUniFi OS / EdgeOS
CategoryIP / Network Issue
Skill levelIntermediate to advanced
DIY-able?Yes with CLI access; some scenarios need Ubiquiti Support + RMA.

What this guide covers

Fix HSRP / VRRP virtual IP not responding on a Ubiquiti firewall.

Step-by-step

  1. Confirm at least one router is in the Active / Master state.
  2. If both are Active / Master, split brain: check L2 connectivity.
  3. Verify priorities + preempt settings.
  4. Verify hello / hold timers match.
  5. Verify the virtual IP is on the same subnet as the SVI.

CLI / commands

show interfaces
show interfaces ethernet eth0
show hardware (EdgeOS)

When the issue persists

Frequently asked questions

Will this work on my specific UniFi OS / EdgeOS version?

The procedure reflects current UniFi OS / EdgeOS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a Ubiquiti Support case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the Ubiquiti official documentation?

https://help.ui.com. search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

Related guides worth a look while you sort this one out:

References


Reference material, not professional advice. Validate against your specific UniFi OS / EdgeOS version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a Ubiquiti device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so the Ubiquiti device fix goes cleanly:

Verification checklist

After applying the fix on your Ubiquiti device, confirm:

When to call Ubiquiti support instead

Escalate if:

More frequently asked questions

Are there safer alternatives for non-technical users?

Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

Will the procedure work on the international variant?

Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.

Topology deep dive

The UDM-Pro family runs UniFi OS with a Linux kernel underneath and a custom iptables / nftables policy generator driven by the controller. Network segmentation uses VLANs assigned per network in the UniFi portal, with inter-VLAN policy enforced at the UDM-Pro and L2 segmentation enforced at the access switch. For an SMB perimeter the typical setup is: one WAN, one LAN, a guest VLAN, an IoT VLAN with no inter-VLAN routing, and an admin VLAN limited by source IP. DHCP either runs on the UDM-Pro or relays to a central Windows or Linux DHCP server via the helper-address configured per VLAN.

Configuration walkthrough

For DHCP, ARP, and VLAN scenarios on a UDM-Pro you operate primarily from the UniFi controller, but SSH gives you reach into the underlying iptables. To verify DHCP relay is forwarding to the central server:

ssh [email protected]
ubnt-tools traffic-monitor -i eth1 -e 'udp port 67 or 68'
show dhcp relay status
show ip route
show vlan brief

Confirm the relay interface IP matches the helper subnet the upstream DHCP server is scoped for, otherwise the BOOTREPLY is dropped silently.

Troubleshooting commands by platform

# EdgeOS (operational):
show interfaces
show ip route
show ip bgp summary
show ip ospf neighbor
show log | match ERROR
show system processes summary
show vlan brief

# UniFi OS (mca-cli on the gateway):
info
show interface
show ip route
show log
show vlan

# Linux underneath (UDM-Pro):
ip -s link
ss -tulnp
iptables -L -n -v
journalctl -u unifi --since '10 min ago'

The Ubiquiti log convention is verbose enough that grepping for the protocol name plus ERROR will usually point you at the right module within ninety seconds.

India compliance and deployment notes

For deployments that touch a regulated workload (BFSI customer data, e-commerce PII, or anything inside a State Data Centre), the Digital Personal Data Protection Act 2023 and the MeitY guidelines still apply at the network layer. Practical implications for a Ubiquiti stack:

Real-world deployment I did

I rolled out a UDM-Pro Max as the perimeter device for a retail chain in Coimbatore, twelve stores plus a HQ. The DHCP relay to a central Windows DHCP server stopped issuing leases at one store overnight. show dhcp leases was empty, show log | match DHCP on the UDM-Pro showed BOOTREPLY received with no matching helper. Root cause: the store VLAN had been renumbered the night before by a junior engineer, and the helper-address still pointed at the old subnet. set service dhcp-relay server 10.20.1.50 after matching the new IL helper interface and we were back. Total customer-visible downtime: forty-eight minutes because the store happened to open at 10 am while I was already debugging.

Extended FAQs

How does Ubiquiti compare with MikroTik for Tier-2 ISP use?

MikroTik wins on raw price per Mbps routed and on RouterOS feature breadth. Ubiquiti wins on the controller experience, the fleet management story, and the Wi-Fi side. Most WISPs I work with in Indore, Coimbatore, and Bhubaneswar end up running a mixed estate: MikroTik for BGP edge and CCR-style aggregation, Ubiquiti for switches and Wi-Fi.

Is the UDM-Pro stable enough for production at an SMB?

Yes, on firmware 4.x and later. The first-generation UDM-Pro had stability issues with high session counts above 80,000 concurrent flows; the UDM-Pro Max addresses that. Run the latest stable firmware and avoid pre-release builds on customer kit.

Can I run BGP on a UDM-Pro instead of an EdgeRouter?

You can on recent UniFi OS releases, but the BGP feature set is younger than EdgeOS FRR. For a single eBGP session to one upstream with default route only, the UDM-Pro is fine. For full table or multiple peers, EdgeRouter Infinity is still the cleaner choice.

What is the AMC budget I should plan for in INR?

Roughly 15-20 percent of the hardware list price per year is a safe planning number. For a mid-size SMB with a UDM-Pro Max, two USW-Pro-48-POE, eight U6-Enterprise APs, and a USW-Pro-Aggregation core, the all-in AMC is usually INR 85,000 to INR 1.2 lakh annually depending on partner.

How do I open a Ubiquiti support case quickly?

Log in at community.ui.com with the registered account, open the support form, attach the controller support file, and reference the device serial and registered MAC. Response time on a paid contract is usually within 4-8 working hours.

Operational runbook and monitoring

The pattern I follow on every Ubiquiti site visit in Visakhapatnam and Mysuru: start with a baseline capture before any change, then make one change at a time, then capture state again. A few minutes of discipline saves a Saturday night. The runbook below is what I actually paste into the customer's runbook wiki at the end of every engagement.

Baseline capture

  1. Pull a controller support file from Settings > System > Maintenance > Download Support File. Stash the .tar.gz with a filename that includes the date and the device serial.
  2. Run show configuration commands on EdgeOS or info in mca-cli on UniFi OS, paste the output into the customer's change ticket.
  3. Snapshot the routing table with show ip route, the ARP table with show arp, and the MAC table with show mac address-table.
  4. Confirm uplink status on every active interface with show interfaces and note any errors or drops above zero.

Monitoring

For the Visakhapatnam customer I support I run a small LibreNMS VM inside the customer LAN polling SNMP v2c against the UniFi devices and the EdgeRouter at 60-second intervals. Critical alarms route to an on-call Telegram group, warning alarms go to email. The metrics that actually matter for a Tier-2 ISP or SMB customer are: WAN RX errors per minute, BGP state changes, interface bandwidth above 80 percent for more than 5 minutes, PoE budget above 90 percent, and controller heartbeat. Everything else is noise that customers ignore until they complain about alert fatigue.

Change window discipline

Production change windows for Indian SMB and ISP customers usually land between 10 pm and 6 am on a Saturday night. Book the window two weeks in advance, document the rollback step before the change step, and keep a console cable in the toolkit even for a remote-managed site because the day SSH fails is the day you need console. For a UDM-Pro the console is the back-panel USB-C; for EdgeRouter Infinity it is the RJ45 console port at 115200 baud. An AMC contract that does not cover after-hours response is worth the discount you negotiated; a contract that does is worth every rupee, usually INR 25,000 to INR 45,000 per site annually.

Followup after a change

One hour after a successful change I re-pull the support file, diff the routing table, and confirm no new errors are climbing on the interface counters. Forty-eight hours later I check the controller event log for anything the customer did not flag. That extra check has caught silent firmware-update reboots, controller adoption drift, and one memorable case where a backup script was trying to log into the UDM-Pro every five minutes with a stale password and slowly filling the auth log.