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

Cisco IOS XE 17.x — Configuring GLBP §Information About GLBPCisco IOS XE 17.x — Configuring GLBP §GLBP Active Virtual GatewayCisco IOS XE 17.x — Configuring GLBP §GLBP Weighting and Tracking

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.

R1 and R2 join GLBP group 10 for virtual address 192.0.2.1. Priority elects the active virtual gateway; both members can become active virtual forwarders. Host A: Gateway 192.0.2.1. Host B: Gateway 192.0.2.1. R1 · pri 120: Group 10. R2 · pri 100: Group 10. Upstream.

Host AGateway: 192.0.2.1Host BGateway: 192.0.2.1R1 · pri 120Group: 10R2 · pri 100Group: 10Upstream
  • Link
  • Blocking
  • Packet in flight
  • Discarded
  • Emphasis
Select a device to read its state. Arrow keys walk the topology.
Text equivalent of this diagram
Devices and links at this step
ElementKindState
Host AhostGateway: 192.0.2.1
Host BhostGateway: 192.0.2.1
R1 · pri 120routerGroup: 10
R2 · pri 100routerGroup: 10
Upstreamcloud
Host AR1 · pri 120linkup
Host AR2 · pri 100linkup
Host BR1 · pri 120linkup
Host BR2 · pri 100linkup
R1 · pri 120Upstreamlinkup
R2 · pri 100Upstreamlinkup
1 / 4

R1 and R2 join GLBP group 10 for virtual address 192.0.2.1. Priority elects the active virtual gateway; both members can become active virtual forwarders.

What changed

  • R1 · pri 120: Group → 10
  • R2 · pri 100: Group → 10
  • Host A: Gateway → 192.0.2.1
  • Host B: Gateway → 192.0.2.1

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.

A request, broadcast to the whole segment. The target hardware address is zeros because that is the question; everyone receives it and only the owner answers.

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

AVG-capable GLBP group with round-robin load balancing and uplink weight tracking.

Cisco IOS-XE 17.12 · ISR 4451, Catalyst 8300draft

  1. interface GigabitEthernet0/0/0
     glbp 1 ip 192.0.2.1
     glbp 1 priority 120
     glbp 1 preempt

    Group 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

  2. interface GigabitEthernet0/0/0
     glbp 1 load-balancing round-robin

    Round-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

  3. 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 20

    Uplink 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.

  1. Every host uses the same router even though both GLBP members are healthy.

    Narrow it down

    1. Check which router is AVG and list the active virtual forwarders.
    2. Inspect the configured load-balancing method.
    3. 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 GLBP
  2. A router with a failed uplink still receives traffic for its GLBP virtual MAC.

    Narrow it down

    1. Inspect the member’s current and configured weighting.
    2. Confirm the tracked object changed state.
    3. 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 Tracking
  3. After an AVF fails, some established clients black-hole while new clients work.

    Narrow it down

    1. Compare failed-forwarder timers with client ARP lifetimes.
    2. Check which member assumed the failed virtual MAC.
    3. 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 GLBP
  4. Hosts ARP for the gateway and receive no reply; no forwarders appear.

    Narrow it down

    1. Confirm group number, virtual IP, and authentication match on all members.
    2. Check whether any member won AVG.
    3. 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 Gateway
  5. Forwarder roles flap or clients bounce between virtual MACs under light loss.

    Narrow it down

    1. Compare hello and hold timers across members.
    2. Inspect redirect and timeout timers for the virtual MAC.
    3. 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.

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.

Cached clientARP 192.0.2.1: 0007.b400.0102New clientR1 · AVGR2 · failed AVFAVF failed
  • Link
  • Blocking
  • Packet in flight
  • Discarded
  • Emphasis
Select a device to read its state. Arrow keys walk the topology.
Text equivalent of this diagram
Devices and links at this step
ElementKindState
Cached clienthostARP 192.0.2.1: 0007.b400.0102
New clienthost
R1 · AVGrouter
R2 · failed AVFrouter
Cached clientR1 · AVGlinkup
Cached clientR2 · failed AVFlinkup
New clientR1 · AVGlinkup
New clientR2 · failed AVFlinkup
1 / 3

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.

Check yourself

  • What does the GLBP AVG vary to distribute clients?
  • Which value controls whether a GLBP member remains eligible as a forwarder?
  • Why can one test host make a healthy GLBP pair look unbalanced?
  • What must happen for established clients to survive an AVF failure?
  • What is the AVG responsible for that an ordinary AVF is not?
  • How does GLBP differ from an EVPN anycast gateway?
  • In a single HSRP group, how much traffic does the Standby forward compared with a GLBP AVF?
  • After an AVF fails, why might new clients work while old ones do not?