I have posted blogs dealing with HSRP and VRRP. Today’s topic takes this idea a step beyond what is possible with those protocols by introducing the concept of Gateway Load Balancing Protocol (GLBP). Let’s begin by viewing the network scenario I used for this blog:
GLBP is a Cisco proprietary protocol which was made available in 2005. It is designed to be an improvement over the existing FHRPs – HSRP and VRRP – because it allows full utilization of router resources without having to create multiple groups, which is a limitation of HSRP and VRRP. GLBP has the following functions: Active Virtual Gateway (AVG) and Active Virtual Forwarder (AVF). In a GLBP group, the members elect one of the routers to be the AVG. The AVG assigns virtual MAC addresses to each member of the GLBP group. If the AVG dies, one of the other members of the group will take over this functionality.
An AVF is a gateway which assumes to role of forwarding packets that are sent to the virtual MAC address which is assigned to that AVF by the AVG. GLBP then load balances among all the gateways that are active in this GLBP group using one of three load-balancing mechanisms. The mechanisms are weighted load-balancing, host-dependent load-balancing, and round-robin load-balancing-which is the default. In weighted load-balancing, a forwarding router is assigned load based upon the weight that it advertises. In host-dependent load-balancing, an individual host will always use the same virtual MAC address as long as that MAC address is active in the GLBP group. In round-robin load-balancing, an AVG responds to client ARP requests with the MAC address of the next available router (AVF) in the group, similar to a dealer dealing cards.
Let’s examine a very basic configuration for the three GLBP routers shown in Figure 1. Here are the relevant running configs of each:
As shown in Figure 1, I want GLBP2 to win the role of AVG. To make this happen, I used the priority command on GLBP2, which is displayed in Figure 3. The default priority value is 100, so by setting GLBP2 to a higher value, it becomes the AVG. With the configurations shown, note the output of show glbp on glbp2:
All three clients are configured with a default gateway IP address of 10.1.1.5, which also happens to be the virtual IP address configured in GLBP. Now that the entire network is up and running, let’s examine the ARP information on each of our clients. I have issued the ping 10.1.1.5 command on each client and received replies. Take a look at what each client has learned:
As you can see, each client has an entry for the IP address of its default gateway of 10.1.1.5. However, each client has a different MAC address stored for that IP address. This is the result of the round-robin load balancing that is happening behind the scenes. Also noteworthy is the fact that the AVG also participates in the forwarding of packets. It does not just sit around and delegate the user load to the AVF routers.
There is much more involved in fine-tuning GLBP in your network. In this blog I just wanted to hit the very basics of initial configuration. In future blogs I will explore how GLBP can track upstream destinations and adjust itself accordingly. I hope you will tune in and enjoy those discussions as well.
Until next time…