VRRP state issue

[Mohamed baraka]

Hello,

I have an issue on my cEgde device that both of them are seeing the state as MASTER, below is the config,

====

CE1#sh run int Gi0/0/0.1
Building configuration...

Current configuration : 342 bytes
!
interface GigabitEthernet0/0/0.1
encapsulation dot1Q 1
vrf forwarding 10
ip address 1.1.1.4 255.255.255.0
no ip redirects
ip mtu 1500
ip nbar protocol-discovery
vrrp 1 address-family ipv4
priority 250
track omp shutdown
address 1.1.1.1 primary
exit-vrrp
arp timeout 1200
end

CE1#sh vrrp Gi0/0/0.1

GigabitEthernet0/0/0.1 - Group 1 - Address-Family IPv4
State is MASTER
State duration 3 days 3 hours 31 mins
Virtual IP address is 1.1.1.1
Virtual MAC address is 0000.5E00.0101
Advertisement interval is 1000 msec
Preemption enabled
Priority is 250
Track object omp state UP shutdown
Master Router is 1.1.1.4 (local), priority is 250
Master Advertisement interval is 1000 msec (expires in 530 msec)
Master Down interval is unknown
FLAGS: 1/1

=====

CE2#sh run int Gi0/0/0.1
Building configuration...

Current configuration : 321 bytes
!
interface GigabitEthernet0/0/0.1
encapsulation dot1Q 1
vrf forwarding 10
ip address 1.1.1.3 255.255.255.0
no ip redirects
ip mtu 1500
ip nbar protocol-discovery
vrrp 1 address-family ipv4
priority 150
address 1.1.1.1 primary
exit-vrrp
arp timeout 1200
end

CE2#sh vrrp Gi0/0/0.1

GigabitEthernet0/0/0.1 - Group 1 - Address-Family IPv4
State is MASTER
State duration 39 mins 49.154 secs
Virtual IP address is 1.1.1.1
Virtual MAC address is 0000.5E00.0101
Advertisement interval is 1000 msec
Preemption enabled
Priority is 150
Master Router is 1.1.1.3 (local), priority is 150
Master Advertisement interval is 1000 msec (expires in 227 msec)
Master Down interval is unknown
FLAGS: 1/1

===

[Edson A. Hernandez · Accepted solution]

Based on the information you've provided PLNZ341 should be the MASTER and PLNZ340 should be the BACKUP.

Here are some troubleshooting steps to address the issue:

Physical Connectivity:
Ensure both devices are connected to the same LAN segment and can communicate with each other directly. Check if you can ping between the two interfaces (172.30.84.4 and 172.30.84.3).

Duplex Mismatch:
Ensure that there isn't a duplex mismatch or any other physical layer issues on the connecting interfaces. Check the interface statistics for errors.

Remove Track Object:
Ensure that this is not affecting the VRRP process.

Software Bug:
Check the cisco website for any known issues with your current device software version.

**Remember to support with a like to keep the community active***
**Please, if the information was helpful, mark this answer as correct.***

[MHM Cisco World]

vEdge-x# show vrrp detail
can you share this if issue not solve yet.