A logistics pair replaced HSRP with a fresh VRRP configuration and did not enter a preempt command. When the higher-priority router returns, it becomes primary immediately. Why?
Select an answer to reveal the explanation.
Short Explanation
You did not have to ask for the seat back, because this protocol saves it for the higher priority. VRRP on NX-OS preempts unless you turn that off. HSRP is the one that stays quiet until you configure preempt, and this pair is not running HSRP anymore.
Full Explanation
NX-OS VRRP enables preemption by default. A router with a higher priority becomes primary when it returns, even though nobody typed a preempt command. That is what the logistics pair is seeing. HSRP preemption is disabled by default, and a leftover HSRP preempt command is not part of a fresh VRRP group. The virtual MAC follows the VRRP group. It does not stay pinned to the lower-priority router across a priority recovery. Peer-gateway lets a vPC peer route frames that arrive for the other peer's router MAC. It does not elect the VRRP primary. Caveat: if someone later configures no preempt under the VRRP group, the higher-priority router will not take over until the current primary fails. Operational check: show the VRRP group, confirm preemption is enabled, and confirm the returned router is primary without adding a preempt command. Show the group on both routers and confirm the priority values are what you think they are, because a tie uses the higher address and can look like preemption failed.