I am experiencing something odd on 5.4 with MLAG. We have other switches in MLAG on 4.3 and even 3.7 ( don’t judge ) and in 5.4 I am seeing the message in the subject on the peer-ip when checking for consistency issues. I DO NOT see this error when checking issues on leaf3-1 only on leaf3-2 but as you can see the config matches (see second image).
Interesting issue. Let me ping an MLAG developer to see if they might have any insights.
Can you please share clagctl output. Do you see the bonds in protodown state?
1 Like
I have the same issue. Did you resolve the problem?
cumulus@k08r01:mgmt:~$ nv show mlag consistency-checker
Global Consistency-checker
=============================
Parameter LocalValue PeerValue Conflict Summary
---------------------- ------------------------- ------------------------- ----------------------------------- -------
anycast-ip 10.10.10.24 10.10.10.24 -
bridge-priority 32768 32768 -
bridge-stp-mode rstp rstp -
bridge-stp-state on on -
bridge-type vlan-aware vlan-aware -
clag-pkg-version 1.6.0-cl5.7.0u8 1.6.0-cl5.7.0u8 -
clag-protocol-version 1.7.0 1.7.0 -
peer-ip fe80::9e05:91ff:fe4a:801c fe80::9e05:91ff:fe4a:801c peer ip mismatch between clag peers
peerlink-bridge-member Yes Yes -
peerlink-mtu 9216 9216 -
peerlink-native-vlan 1 1 -
peerlink-vlans 1, 1320->1322, 1324, 1326 1, 1320->1322, 1324, 1326 -
redirect2-enable yes yes -
system-mac 44:38:39:ff:00:18 44:38:39:ff:00:18
cumulus@k08r02:mgmt:~$ nv show mlag consistency-checker
Global Consistency-checker
=============================
Parameter LocalValue PeerValue Conflict Summary
---------------------- ------------------------- ------------------------- ----------------------------------- -------
anycast-ip 10.10.10.24 10.10.10.24 -
bridge-priority 32768 32768 -
bridge-stp-mode rstp rstp -
bridge-stp-state on on -
bridge-type vlan-aware vlan-aware -
clag-pkg-version 1.6.0-cl5.7.0u8 1.6.0-cl5.7.0u8 -
clag-protocol-version 1.7.0 1.7.0 -
peer-ip fe80::9e05:91ff:fe4a:821c fe80::9e05:91ff:fe4a:821c peer ip mismatch between clag peers
peerlink-bridge-member Yes Yes -
peerlink-mtu 9216 9216 -
peerlink-native-vlan 1 1 -
peerlink-vlans 1, 1320->1322, 1324, 1326 1, 1320->1322, 1324, 1326 -
redirect2-enable yes yes -
system-mac 44:38:39:ff:00:18 44:38:39:ff:00:18
clactl:
cumulus@k08r01:mgmt:~$ clagctl
The peer is alive
Our Priority, ID, and Role: 1000 9c:05:91:4a:80:1c secondary
Peer Priority, ID, and Role: 1000 9c:05:91:4a:80:1c secondary
Peer Interface and IP: peerlink.4094 fe80::9e05:91ff:fe4a:801c (linklocal)
VxLAN Anycast IP: 10.10.10.24
Backup IP: 10.132.10.211 (inactive: self)
System MAC: 44:38:39:ff:00:18
Global Inconsistencies
Consistency Params Conflicts
---------------------- ------------------
peer-ip peer ip mismatch between clag peers
CLAG Interfaces
Our Interface Peer Interface CLAG Id Conflicts Proto-Down Reason
---------------- ---------------- ------- -------------------- -----------------
bond25 - 25 - peer-ip-mismatch
vxlan48 - - - vxlan-single,peer-ip-mismatch
cumulus@k08r02:mgmt:~$ clagctl
The peer is alive
Our Priority, ID, and Role: 2000 9c:05:91:4a:82:1c secondary
Peer Priority, ID, and Role: 2000 9c:05:91:4a:82:1c secondary
Peer Interface and IP: peerlink.4094 fe80::9e05:91ff:fe4a:821c (linklocal)
VxLAN Anycast IP: 10.10.10.24
Backup IP: 10.132.10.212 (inactive: self)
System MAC: 44:38:39:ff:00:18
Global Inconsistencies
Consistency Params Conflicts
---------------------- ------------------
peer-ip peer ip mismatch between clag peers
CLAG Interfaces
Our Interface Peer Interface CLAG Id Conflicts Proto-Down Reason
---------------- ---------------- ------- -------------------- -----------------
bond25 - 25 - peer-ip-mismatch
vxlan48 - - - peer-ip-mismatch
I can ping remote peer using ipv4 and ipv6 address.
Workaround: do not use linklocal on peerlink.4094.