Now, I will go to PC1 and verify if it is going to 20.20.20.20 via R1 because I have configured it to be Master in first place. R2(config-if)# vrrp 1 track 1 decrement 10 R2(config)# ip sla monitor schedule 1 life forever start-time now R2(config-sla-monitor-echo)# timeout 1000 R2(config-sla-monitor)# type echo protocol ipicmpEcho 20.20.20.20 source-interface fa0/1 On interface fa0/1, I’ve simply enabled VRRP with virtual IP 20.20.20.1 and no other configuration is done. This will cause R1’s priority to become 90 and R2 will take over R1 and will become Master. The vrrp 1 track 1 decrement 20 command is used to add the tracked object 1 and once tracked object becomes invalid, R1 will decrement its priority by 20. Notice that I have not used preempt command because preempt is enabled by default in VRRP unlike HSRP.
The v rrp 1 ip 10.10.10.1 command is used to assign virtual IP address and vrrp 1 priority 110 command is used to set the priority to 110 (default is 100). Other options after vrrp keyword are same as HSRP. Notice that the syntax to enable VRRP is pretty simple to remember because every command starts with vrrp as opposed to that of HSRP (HSRP configuration starts with keyword standby). R1(config-if)# vrrp 1 track 1 decrement 20 Preempt Enable preemption of lower priority Master Ip Enable Virtual Router Redundancy Protocol (VRRP) for IP If you have not heard about IP SLA and Object tracking, read this page. I have created SLA monitor and tracked object and started tracking the destination 20.20.20.20 from source interface fa0/1. R1(config)# ip sla monitor schedule 1 life forever start-time now R1(config-sla-monitor-echo)# timeout 1000 R1(config-sla-monitor)# type echo protocol ipicmpEcho 20.20.20.20 source-interface fa0/1 R1#conf tĮnter configuration commands, one per line. If R1 can not reach the address 20.20.20.20 from fa0/1, R1 will assume that link between interface fa0/1 and server is down and it will decrement its priority to make itself Backup router and R2 will become Master to start forwarding the traffic. So, I will first create an SLA probe to track the reachability of 20.20.20.20 from source interface fastEthernet0/1. VRRP support SLA monitors along with object tracking. We need to configure fault tolerance between R1 and R2 so that PC1 has continue connectivity to Server even if any one of the two routers fail. > It's not platform dependent it's how it operate per RFC 2338.I will use network diagram below to demonstrate the VRRP configuration. But I am not sure different platform/IOS has different beheavior.
And I found it always use same virtual MAC. > I don t think so since there is no interface command to tell router to use BIA for VRRP much like the HSRP. When ping the virtual IP, master R1 answer ARP with MAC-PHY, or other MAC than MAC-VIR. > Yes, per above that mac-address is associated to Virtual Router.Īlso I want to know if it is possible that IOS answer ARP request for the virtual IP with master's real physical MAC address in some cases.įor example, R1 e0 is configed with VRRP, its physical MAC address is MAC-PHY, virtual MAC for that virtual ip is MAC-VIR. What about the virtual MAC address in case master failure, does new master(previously backup) still use same virtual MAC after previous master fails? Mapping provides for up to 255 VRRP routers on a network. >The virtual router MAC address associated with a virtual router is an IEEE 802 MAC Address in the following format:Ġ0-00-5E-00-01- is the VRRP Virtual Router Identifier.
Do all cisco IOS use only one unique MAC for one VRRP group?
Please tell me what MAC address VRRP uses for the virtual IP.
0 kommentar(er)
