Virtual Router Redundancy Protocol (VRRP) is very similar to HSRP and can create a virtual gateway but the difference that it is not the Cisco Proprietary Protocol.
It is a standard protocol defined by the IETF in RFC 3768. If you learn and understood HSRP then it is very easy for you to understand the Virtual Router Redundancy Protocol (VRRP).
The Virtual Router Redundancy Protocol (VRRP) is an election protocol that dynamically assigns responsibility for one or more virtual routers to the VRRP routers on a LAN and elects the role of the router.
Virtual Router Redundancy Protocol (VRRP) allows several routers on a multi-access link to utilize the same virtual IP address. In a VRRP configuration, one router is elected as the virtual router master and other routers acting as backups in case the virtual router master fails.
As in the previous two articles, Router2 and Router3 are neighbouring to the LAN segment. We will use the same topology for the Virtual Router Redundancy Protocol (VRRP) configuration. Router2 will be the master router and Router3 role is the backup router.
In the above topology, we are using two Cisco routers for VRRP. We have been tasked to configure VRRP. The IP addresses, routing and other pre-requisite have done. This is important to know that each device participating in the VRRP process also needs to be in the same broadcast domain and also requires a unique IP address on the interface or VLAN where you are configuring VRRP. Let’s go-ahead to the configuration and add the VRRP configuration.
When we type vrrp in the command prompt we are stating to the router that we are configuring vrrp on this interface, the number next to it is the VRRP group we are configuring, the range of the group is from 1 to 254.
The groups required to be matched on all equipment participating in the VRRP election process, and the last part of the configuration we are stating what the floating IP address is. We have added the group 1 to configuration.
We have set the priority of both routers. Router2 is configured with higher value, so this will be a master router. If Router2 fails, the Router3 will become master. The preemption is enabled, so whenever Router2 recover from failure, it will again become a master router.
Gateway Load Balancing Protocol (GLBP) is the Cisco-proprietary FHRP. It is also allowing load sharing between a group of redundant routers. Gateway Load Balancing Protocol is specially designed to overcome the limitations of HSRP and VRRP.
In HSRP and VRRP, only the active/master router can forward traffic while all the standby/backup routers are idle but Gateway Load Balancing Protocol overcome this problem, all routers in the GLBP group can be efficiently utilized and forward traffic, so in addition to redundancy we also get load balancing. We can configure GLBP in the Cisco IOS router using three types of an algorithm: round-robin, weighted, or host-dependent.
The routers participating in the Gateway Load Balancing Protocol group are called Active Virtual Forwarder (AVF). Like HSRP, there is still one router that must control the Gateway Load Balancing Protocol operation, and this router is called the Active Virtual Gateway (AVG).
An Active Virtual Gateway (AVG) is elected when GLBP is activated on the network, and it has the task to decide the next AVF that will be used to forward the packet based on the selected algorithm. A router with AVG role by default also acts as AVF at the same time.
The Gateway Load Balancing Protocol configuration on the Cisco router is easy and mostly similar to the configuration of Hot Standby Router Protocol (HSRP) and Virtual Router Redundancy Protocol (VRRP). We will use the same topology for GLBP configuration that we have used for the configuration of the HSRP.
Each gateway will be configuring in a GLBP group with the same group number, and at least one gateway in the GLBP group must be configured with the virtual IP address to be used by the group. We can use the “glbp group ip” command to enable GLBP from the global configuration mode. The configuration on both Router2 and Router3 is as under:
We are using GLBP group number 1 and virtual IP 192.168.10.1, and this virtual IP address should be configured on each router. We also configured the priority for both routers to elect as AVG, the priority of the Router2 is 110, and the priority of Router1 is 100. The default priority value of GLBP is 100. The router with the highest priority number will be elected as the AVG.
If failure happens on the AVG, the next router with the highest priority value will be granted to the role of AVG. The preempt is enable on both router, this means that they can get back the AVG role from current AVG if they have higher priority.
We can verify GLBP configuration, using the command show glbp brief from any of the GLBP members. To verify GLBP configuration, we can simply issue a command show glbp brief from any of the GLBP members:
GLBP Round-Robin Algorithm
Round-robin is the default load balancing algorithm with the Gateway Load Balancing Protocol configuration. With the round-robin algorithm, AVG will reply to each ARP request for the GLBP virtual IP with each AVF’s virtual MAC address in turns, so all AVFs will be used equally.
GLBP Weighted Algorithm
The weighted algorithm allocates traffic to each AVF based on the weight value assigned to them. An AVF with a bigger weight value will get more traffic redirected to it.
The range of the weighting is from 1 to 254 and the default weight value is 100. The router with a higher weight value will be assigned more traffic to the router with less weight value. The configuration command for the above example scenario is as follows:
Router2:
Router2>enable
Router2#config terminal
Router2(config)# interface gigabitEthernet 0/1
Router2(config-if)#glbp 1 load-balancing weighted
Router2(config-if)#glbp 1 weight 150
Router2(config)#do wr
Router3:
Router3>enable
Router3#config terminal
Router3(config)# interface gigabitEthernet 0/1
Router3(config-if)#glbp 1 load-balancing weighted
Router3(config-if)#glbp 1 weight 200
Router3(config)#do wr
GLBP Host-Dependent
This algorithm uses the MAC address of the host to determine which virtual MAC address to direct the host to use. This algorithm usually guarantees the same virtual MAC address that is previously assigned if the number of active virtual forwarders (AVF) does not change.
In some situations, this comes up to the best option, for example in the case of stateful NAT. The configuration of the Gateway Load Balancing Protocol host-dependent for the above topology is as under:
GLBP allows automatic selection and simultaneous use of multiple available gateways in addition to automatic failover between those gateways. Various routers share the load of frames that, from a client viewpoint, are sent to a single default gateway address.
We can fully make use of network resources without the administrative burden of configuring multiple groups and managing multiple default gateway configurations. Gateway Load Balancing Protocol has the following characteristics:
GLBP allows full use of network resources on all devices without the administrative burden of creating multiple groups.
GLBP provides a single virtual IP address with several virtual MAC addresses.
GLBP routes traffic to a single gateway distributed across multiple routers.
In the event of failure and change provides automatic rerouting.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.