L3 · fhrp · reviewed
GLBP
Gateway Load Balancing Protocol
One virtual gateway address, several forwarding MAC addresses, and an ARP reply that chooses the forwarder.
Presenter modeEmbed this figure
Why it exists
HSRP and VRRP leave the standby forwarding no host traffic for a group. GLBP keeps one gateway address while distributing hosts across several active forwarders. Cisco IOS XE 17.x — Configuring GLBP §Information About GLBP
GLBP is Cisco-proprietary. VRRP and HSRP do not speak it; an EVPN anycast gateway is a different active-active design with one shared MAC.
One VIP, two forwarding MACs
R1 wins AVG and assigns a virtual MAC to each AVF. Hosts ARP for the same gateway IP and receive different virtual MACs, so both routers forward.
How it works
Priority elects the active virtual gateway. The AVG assigns virtual MAC addresses to active virtual forwarders and answers ARP for the virtual IP with one of those MACs according to the load-balancing method. Cisco IOS XE 17.x — Configuring GLBP §GLBP Active Virtual Gateway
Weighting and its lower/upper thresholds — often changed by object tracking — decide whether a member remains eligible as a forwarder. Priority alone does not withdraw an AVF when an uplink dies. Cisco IOS XE 17.x — Configuring GLBP §GLBP Weighting and Tracking
After an AVF fails, another member can forward for the failed virtual MAC while redirect timers steer new ARP replies. Existing clients keep the old MAC until takeover or ARP refresh. Cisco IOS XE 17.x — Configuring GLBP §Information About GLBP
On the wire
Constructed examples, encoded from the field table below them — not captured traffic.
- Ethernet frame
- EtherType 0x0806. A request goes to the broadcast address ff:ff:ff:ff:ff:ff; a reply is unicast back to the asker. RFC 826
Configure it
interface GigabitEthernet0/0/0 glbp 1 ip 192.0.2.1 glbp 1 priority 120 glbp 1 preemptGroup 1 owns the virtual IP. Highest priority becomes Active Virtual Gateway (AVG) and answers ARP with rotating virtual MACs so hosts land on different Active Virtual Forwarders (AVFs).
Common mistake: Expecting per-flow ECMP inside one host’s ARP cache — a single host sticks to the MAC it learned until it re-ARPs.
Cisco IOS XE 17.x — Configuring GLBP §GLBP Active Virtual Gateway
interface GigabitEthernet0/0/0 glbp 1 load-balancing round-robinRound-robin cycles AVF MACs in ARP replies. Host-dependent and weighted modes change how clients are distributed.
Cisco IOS XE 17.x — Configuring GLBP §GLBP Load Balancing Options
track 1 interface GigabitEthernet0/0/1 line-protocol interface GigabitEthernet0/0/0 glbp 1 weighting 100 lower 90 upper 95 glbp 1 weighting track 1 decrement 20Uplink failure drops weight so this router may leave the AVF set. Thresholds decide when the forwarder is removed and when it returns.
Common mistake: Tracking the LAN interface instead of the uplink — GLBP already knows the LAN is up while the AVG role is held.
Cisco IOS XE 17.x — Configuring GLBP §GLBP Weighting
Verify
show glbp brief- Group, priority, AVG/AVF state, and virtual IP.
show glbp- Assigned virtual MACs, weights, and forwarder states.
Caveats
- Marked draft: syntax has not been checked against Cisco documentation or a device.
- GLBP is Cisco-proprietary. No Junos/FRR stanza — use VRRP (or HSRP on Cisco peers that do not need AVG load share).
- Do not invent GLBP packet captures; ARP virtual-MAC behaviour is the teaching surface here.
When it breaks
Symptom first, because that is what you have when it happens.
Every host uses the same router even though both GLBP members are healthy.
Narrow it down
- Check which router is AVG and list the active virtual forwarders.
- Inspect the configured load-balancing method.
- Clear or sample several client ARP entries rather than testing with one long-lived host.
Cause
GLBP distributes virtual MAC addresses when the AVG answers ARP; it does not spray individual packets. Existing hosts keep the virtual MAC already cached, and a host-dependent policy may deliberately map the same host to the same forwarder.
Fix
Verify multiple independent clients after their ARP entries refresh. Choose round-robin, weighted, or host-dependent assignment for the intended persistence and capacity model.
Cisco IOS XE 17.x — Configuring GLBP §Information About GLBPA router with a failed uplink still receives traffic for its GLBP virtual MAC.
Narrow it down
- Inspect the member’s current and configured weighting.
- Confirm the tracked object changed state.
- Compare the decrement with the lower threshold.
Cause
Priority chooses the AVG, but weighting controls forwarder eligibility. Tracking that changes priority—or a weighting decrement too small to cross the lower threshold—does not withdraw the AVF.
Fix
Bind the tracked object to GLBP weighting and choose a decrement that crosses the lower threshold when the path is unusable.
Cisco IOS XE 17.x — Configuring GLBP §GLBP Weighting and TrackingAfter an AVF fails, some established clients black-hole while new clients work.
Narrow it down
- Compare failed-forwarder timers with client ARP lifetimes.
- Check which member assumed the failed virtual MAC.
- Distinguish new ARP replies from traffic using an already-cached MAC.
Cause
New ARP requests can be redirected immediately, but existing clients keep sending to the old virtual MAC. Forwarder takeover and the redirect/timeout timers preserve that MAC during migration; a timer or state mismatch exposes only cached clients.
Fix
Restore AVF redundancy for the old virtual MAC and align redirect/forwarder timers with the endpoint ARP behavior.
Cisco IOS XE 17.x — Configuring GLBP §Information About GLBPHosts ARP for the gateway and receive no reply; no forwarders appear.
Narrow it down
- Confirm group number, virtual IP, and authentication match on all members.
- Check whether any member won AVG.
- Look for ACL or VLAN issues blocking GLBP hellos.
Cause
Members cannot hear each other or disagree on group parameters, so no AVG forms and ARP for the VIP goes unanswered.
Fix
Align group, VIP, and authentication; restore hello reachability on the LAN.
Cisco IOS XE 17.x — Configuring GLBP §GLBP Active Virtual GatewayForwarder roles flap or clients bounce between virtual MACs under light loss.
Narrow it down
- Compare hello and hold timers across members.
- Inspect redirect and timeout timers for the virtual MAC.
- Check for intermittent LAN loss affecting hellos.
Cause
Aggressive or mismatched timers cause AVF or AVG transitions that move virtual MACs faster than hosts can follow.
Fix
Align timers across the group and size redirect/timeout to client ARP behaviour.
Cisco IOS XE 17.x — Configuring GLBP §Information About GLBP
Design notes
Bind tracking to weighting with a decrement that crosses the lower threshold. Tracking that only changes AVG priority leaves a dead-path forwarder in place.
Test with several independent clients after ARP refresh. One sticky host is not a load-balancing proof.
Host-dependent assignment deliberately sticks a host to one AVF. That is persistence, not a bug — unless you expected round-robin.
Misconceptions
- “GLBP load balances every flow or packet.”
- The AVG load balances ARP replies. Each host then sends to the virtual MAC it cached, so distribution is per resolved client until that entry changes—not a per-packet forwarding decision.
- “The active virtual gateway is the router forwarding all traffic.”
- The AVG owns election and virtual-MAC assignment. Traffic is forwarded by one or more AVFs, and the AVG is usually one AVF among them.
- “GLBP is the same active-active design as an EVPN anycast gateway.”
- GLBP has an elected AVG that returns different virtual MACs to clients. An EVPN anycast gateway configures the same gateway IP and MAC on every participating PE, so the locally attached PE routes without an ARP load-balancer election.
More walkthroughs
Weighting, not priority, drops a forwarderfailure
R2 loses its uplink. Priority still elects the AVG; weighting must fall below the lower threshold before R2 gives up the AVF role.
R2 tracks its uplink and decrements GLBP weighting on failure. Priority remains for AVG election; weighting governs forwarder eligibility. Host. R1 · AVG. R2 · AVF: Weight 110. Upstream.
- Link
- Blocking
- Packet in flight
- Discarded
- Emphasis
Text equivalent of this diagram
| Element | Kind | State |
|---|---|---|
| Host | host | — |
| R1 · AVG | router | — |
| R2 · AVF | router | Weight: 110 |
| Upstream | cloud | — |
| Host — R1 · AVG | link | up |
| Host — R2 · AVF | link | up |
| R1 · AVG — Upstream | link | up |
| R2 · AVF — Upstream | link | up |
R2 tracks its uplink and decrements GLBP weighting on failure. Priority remains for AVG election; weighting governs forwarder eligibility.
What changed
- R2 · AVF: Weight → 110
- Track → weighting
Cached clients after an AVF failurefailure
New ARP requests can be redirected immediately, but established clients keep sending to the old virtual MAC until redirect/forwarder timers and takeover cover them.
R2 fails while Host Cached still holds R2’s virtual MAC in ARP. Host Fresh has no entry yet. Cached client: ARP 192.0.2.1 0007.b400.0102. New client. R1 · AVG. R2 · failed AVF.
- Link
- Blocking
- Packet in flight
- Discarded
- Emphasis
Text equivalent of this diagram
| Element | Kind | State |
|---|---|---|
| Cached client | host | ARP 192.0.2.1: 0007.b400.0102 |
| New client | host | — |
| R1 · AVG | router | — |
| R2 · failed AVF | router | — |
| Cached client — R1 · AVG | link | up |
| Cached client — R2 · failed AVF | link | up |
| New client — R1 · AVG | link | up |
| New client — R2 · failed AVF | link | up |
R2 fails while Host Cached still holds R2’s virtual MAC in ARP. Host Fresh has no entry yet.
What changed
- Cached client: ARP 192.0.2.1 → 0007.b400.0102
- AVF failed
- Emphasis on R2 · failed AVF
Terms
- Active Virtual Gateway
- The elected GLBP member that owns the virtual IP and assigns virtual MAC addresses. It answers ARP requests; the active virtual forwarders carry the resulting traffic.
- Active Virtual Forwarder
- A GLBP member responsible for one virtual MAC address. Several AVFs may forward simultaneously even though one member alone is the active virtual gateway.