I cant understand two things:
- why HSRP has 16 groups? not 255?
- in your table we see that VRRP doesnt support authentication, but you configured it…?
I cant understand two things:
Good question and there’s a long answer…
Originally on the 3550 and some of the 6500 supervisors only 16 HSRP groups were allowed but this limitation applied only to a single interface. You could use the same group number on different interfaces without any issues. On newer platforms this 16 limit doesn’t apply anymore…the 3750 supports 32 groups I think and my 2800 router supports 255.
About authentication…originally the RFC 2338 standard described authentication but it was removed in RFC 3678 since it wasn’t secure. Not sure which RFC the Cisco implementation is based on but they probably added authentication to VRRP themselves.
Hope this helps!
Tnx, for answers,
BTW question from another field, have you something new materials for CCNP v2 ?
And maybe you know if I have ROUTE v1 , can I pass SWITCH v2 and TSHOOT v2?
Because in different resources I found different answers…
You can mix the V1 and V2 exams, here’s a link where they explain this:
The answer is in the “Old vs New Exams” topic.
I’m currently updating the lessons pages to add some of the new material. SWITCH now has a stackwise and VSS lesson, ROUTE has DMVPN. Some of the topics I still have to add are SDM templates and EVN.
Well written. Any way we can track the object in VRRP ? Can you give an example
For sure, it could be something as simple as this:
R1(config)#track 1 interface FastEthernet 0/0 line-protocol R1(config)#interface FastEthernet 0/0 R1(config-if)#vrrp 1 track 1 decrement 50
or you can configure IP SLA and combine it with tracking like I did here:
I think above configuration can be applied to all SVI for supporting multiple Vlans .
Is it correct? Is there any limitation ?
That’s right, you can enable this on routed interfaces or SVI interfaces.
I want lessons about VRRP version3
I will add this to my list.
Thank you for this lecture.
However I’m still having hard time understanding how load-balancing for different vlans has to be configured.
Let’s say we have Routers instead of Switches A and B in the lecture topology and computers are in different vlans. How do you provide routing between them and load balancing with stateful failover?!?
The short answer to your question is that you will need a separate VRRP instance for each vlan that you want to have a highly available gateway.
I have attached a new topology to discuss this. In it, you will see that Computers A and B are in different VLANs (A and B). Switch A and Switch B are both connected to the access-layer Switch C. Note: These connections must be configured as trunks, let’s say the modern 802.1Q standard with both VLAN A and VLAN B allowed. Additionally, it would be a good idea to have Switch A and Switch B directly connected to each other (in the real world this is done with Etherchannel), and that connection must also be a trunk that allows all VLANs between them.
At this point, you are ready to configure Switch A and Switch B. Each will need an SVI (switched virtual interface) for both VLAN A and VLAN B. You would treat these SVIs just like regular interfaces–just think of them as the Switch’s presence in the VLAN in question. Here’s a sample of getting the config going for Switch A:
SwitchA(config)#interface vlan A SwitchA(config-if)#ip address 192.168.1.252 255.255.255.0 SwitchA(config-if)#vrrp 1 ip 192.168.1.254 SwitchA(config-if)#vrrp 1 priority 105 SwitchA(config-if)#interface vlan B SwitchA(config-if)#ip address 192.168.1.252 255.255.255.0 SwitchA(config-if)#vrrp 2 ip 192.168.2.254
Now Switch B:
SwitchB(config)#interface vlan A SwitchB(config-if)#ip address 192.168.1.253 255.255.255.0 SwitchB(config-if)#vrrp 1 ip 192.168.1.254 SwitchB(config-if)#interface vlan B SwitchB(config-if)#ip address 192.168.1.253 255.255.255.0 SwitchB(config-if)#vrrp 2 ip 192.168.2.254 SwitchB(config-if)#vrrp 2 priority 105
Notice above, that Switch B will have priority for being the virtual gateway of VLAN B, and likewise, Switch A has priority for VLAN A. This way, you can load balance which Switch will handle the traffic on a per-VLAN basis.
You might have to provide more details, but at first glance, this won’t work well. My suggestion would be, if you are using Cisco Routers or Switches, to use GLBP instead of VRRP since it has the ability to do what you are asking easily. If you insist on using VRRP, you will have a problem with DHCP. From your example, I assume you are trying to balance the gateways on the same subnet. In DHCP (at least the Windows version), although you can define multiple gateways, this won’t result in load-balancing. Instead, the additional gateways will only be used if the primary is unavailable.
Again, it sounds like Gateway Load-Balancing Protocol is what you should use. By the way, there is a lesson on GLBP here.
I have confusion between interface tracking & object tracking.As you have mentioned VRRP only supports object tracking,does IP SLA mean object tracking?
19 posts were merged into an existing topic: VRRP (Virtual Router Redundancy Protocol)
Could someone help me to give more details on why we need gratituous ARP in VRRP.What I read so far from various source is there will be a GARP sent immediately after backup router takes master role to update underlying switch MAC table which I felt it can be done with VRRP advertisement(source MAC as virtual MAC) instead of GARP.
It is a good question and to be honest, I can’t really find a good answer. Take a look at this Wireshark capture:
This capture shows how 192.168.1.2 (current master) is taken over by 192.168.1.1 (new master). Both the advertisement and the gratuitous ARP have the same source MAC address (0000.5e00.0101). A switch can update its MAC address table with the source MAC address in the advertisement, we don’t need the gratuitous ARP for that.
The only difference is that the gratuitous ARP is also sent as a broadcast, not just to a multicast destination. Still, I’m having a hard time thinking of a reason why we need anything next to the updated advertisement. The RFC also doesn’t explain why they use the gratuitous ARP. If anything comes to mind, I’ll update my answer here.
I read somewhere in the Internet that Huawei routers use interface MAC as a source MAC for VRRP advertisement with period GARP with source MAC as virtual to update underlying switch table.
RFC talks something about GARP for token ring topology RIF table - I am not sure what was that and how GARP plays a vital role in token ring case though no one is using now a days.
RFC also says VRRP advertisement should use source MAC as virtual MAC
Can you confirm that object tracking means IP SLA tracking?
Also, could you update the table to confirm that VRRP now supports 255 groups per interface?
Object tracking and IP SLA are not the same thing although the concepts are related. For example, an IP SLA can be configured to track objects. In order to understand this further, let’s take a look at HSRP, VRRP and objects.
As far as HSRP and VRRP go, object tracking is an independent process that manages creating, monitoring, and removing tracked objects such as the state of the line protocol of an interface. Clients such as the Hot Standby Router Protocol (HSRP) and VRRP register their interest with specific tracked objects and act when the state of an object changes.
IP SLA on the other hand uses active monitoring of objects by generating traffic to measure network performance. IP SLA operations collects real-time metrics that can be used for network troubleshooting, design, and analysis.
I hope this has been helpful!