Refer to the exhibit.
An engineer configures VRRP and issues the show commands to verify operation. What does the engineer confirm about VRRP group 1 from the output?
Refer to the exhibit.
An engineer configures VRRP and issues the show commands to verify operation. What does the engineer confirm about VRRP group 1 from the output?
In the configuration, Router 1 (R1) has a VRRP priority of 110, which is higher than Router 2's (R2) default priority of 100. Additionally, R1 is tracking the reachability of the IP route 10.10.1.1/32. If this route is reachable, R1 maintains its priority of 110, ensuring it remains the primary router. However, if the route becomes unreachable, R1's priority is decremented by 20, making it 90, which is lower than R2’s priority, thus making R2 the primary router. Therefore, as long as the route 10.10.1.1/32 is present in R1's routing table, R1 stays the primary VRRP router.
answer makes sense. A- Wrong, its cleartext B- Wrong, not enough information to infer this C- Correct, if there is reachability to the network 10.10.1.1/32, R1's priority is default 100, which is equal to R2's priority of default 100, so what is the next tie breaker? the higher IP address, R1 wins, and with VRRP having preempt enabled by default, R1 becomes the Master. D- Wrong
R1's prio is 110. When the tracked object fails, the prio is decremented by 20, lowering it below R2's default prio, 100. But C says when the route is installed (meaning reachable), so R1's prio remains 110, and master. Still C, nevertheless.
It is NOT D, Why ? Because preemption is enabled by default. Which means that if R1 reboots -> R2 will become primary and when R1 reboot is finished will take the role again because of the default preemption ! -> C seems right.
A believe it is C. By ''sh run int fa0/0'' command we are not able to tell if route is in routing table or not. On router 1 is configured IP SLA which is tracking reachability to 10.10.1.1 - so if this route is unavailable, routers 1 priority decrements and it becomes Secondary, but if the route is reachable it will stay Primary because of its 110 priority.
C is the correct answer
C is correct because of the tracking feature. Exhibit speaks nothing about availability of routes, so we can not tell which routes are available or not available.
I believe B is true.
there was no output regarding routing table, so you can't say if yes or no
R1 tracks a /32 network and remove vrrp priority if the /32 goes away.
cisco_R3(config-subif)#do s runn interface Ethernet0/0.40 ! interface Ethernet0/0.40 encapsulation dot1Q 40 ip address 172.16.13.2 255.255.255.0 vrrp 10 ip 172.16.13.254 vrrp 10 track 4 decrement 20 end cisco_R3(config-subif)#do s track 4 Track 4 IP route 5.5.5.55 255.255.255.255 reachability Reachability is Down (no ip route) 1 change, last change 00:04:13 First-hop interface is unknown Tracked by: VRRP Ethernet0/0.40 10 cisco_R3(config-subif)#do s vrrp Ethernet0/0.40 - Group 10 State is Master Virtual IP address is 172.16.13.254 Virtual MAC address is 0000.5e00.010a Advertisement interval is 1.000 sec Preemption enabled <<<<<<<<<< by default, so it'll become MASTER after high priority Priority is 80 Track object 4 state Down decrement 20 Master Router is 172.16.13.2 (local), priority is 80 Master Advertisement interval is 1.000 sec Master Down interval is 3.609 sec cisco_R3(config-subif)#
cisco_R3(config-subif)# *Dec 23 20:51:51.008: %TRACK-6-STATE: 4 ip route 5.5.5.55/32 reachability Down -> Up cisco_R3(config-subif)# cisco_R3(config-subif)#do s track 4 Track 4 IP route 5.5.5.55 255.255.255.255 reachability Reachability is Up (BGP) 2 changes, last change 00:00:41 First-hop interface is Ethernet0/0.10 Tracked by: VRRP Ethernet0/0.40 10 cisco_R3(config-subif)#do s vrrp Ethernet0/0.40 - Group 10 State is Master Virtual IP address is 172.16.13.254 Virtual MAC address is 0000.5e00.010a Advertisement interval is 1.000 sec Preemption enabled Priority is 100 Track object 4 state Up decrement 20 Master Router is 172.16.13.2 (local), priority is 100 Master Advertisement interval is 1.000 sec Master Down interval is 3.609 sec
cisco_R3(config-subif)# cisco_R3(config-subif)#do s ip ro 5.5.5.55 Routing entry for 5.5.5.55/32 Known via "bgp 3", distance 20, metric 0 Tag 5, type external Last update from 192.168.255.55 00:01:21 ago Routing Descriptor Blocks: * 192.168.255.55, from 192.168.255.55, 00:01:21 ago Route metric is 0, traffic share count is 1 AS Hops 4 Route tag 5 MPLS label: none cisco_R3(config-subif)#
tricky question, I hate it ... D. is true anyway, C. is unclear, let's say what happens if this route flaps? after that R2 will be master anyway cos no feature PREEMPTION is configured on R1... right?
Preemption is enabled by default in VRRP, Answer "C" is correct.
i think that is close answer
Provides answer is correct. R1 is primary if 10.10.1.1/32 is in its routing table. -> because of track 20 command
C is correct. tricky question b is completely wrong, there is nothing in the question that can be used to identify if b is correct or wrong. D is correct until you remember that preemption is default in VRRP :D C seems to be wrong at first, then you look at the track again to see that it's tracking the IP route entry in the routing table not pinging the ip
R1 is primary as long as 10.10.1.1/32 is reachable in the routing table, if this fails, the priority decremets to 90. ........
I believe D is correct because preemption is enabled in VRRP by default. The answer C says " if 10.10.1.1/32 is in its routing table." if this route is statically configured it will still be there disregarding its reachability.
Look close the D answer: . If R1 reboots, R2 becomes the primary virtual router until R2 reboots. (R2 reboots !)
Answer: B
Sorry is D
Not D; VRRP has preempt on by default, so R1 will take back over as primary when it can. Answer is C