Wired Intelligent Edge

Hello,
i have following situation:
8325-1# sh vsx status
VSX Operational State
---------------------
ISL channel : In-Sync
ISL mgmt channel : operational
Config Sync Status : configuration_sync_missing_reference
NAE : peer_reachable
HTTPS Server : peer_reachable

Attribute Local Peer
------------ -------- --------
ISL link lag256 lag256
ISL version 2 2
System MAC 02:01:00:00:01:00 02:01:00:00:01:00
Platform 8325 8325
Software Version GL.10.09.1020 GL.10.09.1020
Device Role primary secondary

8325-1# sh vsx status config-sync
Admin state : Enabled
Operational State : Operational
Error State : Missing reference error
Recommended remediation : A. Execute 'show running-config vsx-sync peer-diff' to determine which lines did not sync correctly on secondary
B. Identify the configuration that is missing from secondary and manually fix via CLI.
Current time : Mon Jun 27 15:36:03 2022
Last sync time : Mon Jun 27 15:10:41 2022

8325-1# show running-config vsx-sync peer-diff
No difference in configs.


is it some known issue ?

Regards,
Mladen

try the command vsx-configmate
and shared the output.
If no reported problem, I would  recommend to check the VLAN presence on secondary.

8325-1# vsx-configmate
============================================
VSX FEATURE CONFIG PARSER
============================================

VSX configuration validation results below:-

Rule-1: The allowed VLAN list for ISL port must match that in config for MCLAG in 8325-1 (Passed)
Rule-1: The allowed VLAN list for ISL port must match that in config for MCLAG in 8325-2 (Passed)
Rule-2: The native VLAN must also be part of allowed VLAN list for a MCLAG in 8325-1 (Passed)
Rule-2: The native VLAN must also be part of allowed VLAN list for a MCLAG in 8325-2 (Passed)
Rule-3: The inter-switch-link Timers should be consistent across VSX peers (Passed)
Rule-4: The Keep-Alive Timers should be consistent across VSX peers (Passed)
Rule-5: Active-Gateway configurations(IP, MAC and VRF) should be consistent across the VSX peers (Passed)
Rule-6: The Keep-Alive UDP port should be consistent across VSX peers (Passed)
Rule-7: The link-up-delay-timer should be consistent across VSX peers (Passed)
Rule-8: The VSX System-MAC should be consistent across VSX peers (Passed)
Rule-9: The VSX device roles should be consistent across VSX peers (Passed)
Rule-10: VSX active-forwarding configurations should be consistent across the VSX peers (Passed)

Br,
Mladen
Original Message:
Sent: Jun 28, 2022 02:44 AM
From: Vincent Giles
Subject: VSX config sync bug?

try the command vsx-configmate
and shared the output.
If no reported problem, I would  recommend to check the VLAN presence on secondary.

And vlans:
8325-1# sh vlan summary
Number of existing VLANs : 126
Number of static VLANs : 126
Number of dynamic VLANs : 0
Number of port-access VLANs: 0

8325-2# sh vlan summary
Number of existing VLANs : 126
Number of static VLANs : 126
Number of dynamic VLANs : 0
Number of port-access VLANs: 0

Original Message:
Sent: Jun 28, 2022 03:16 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

8325-1# vsx-configmate
============================================
VSX FEATURE CONFIG PARSER
============================================

VSX configuration validation results below:-

Rule-1: The allowed VLAN list for ISL port must match that in config for MCLAG in 8325-1 (Passed)
Rule-1: The allowed VLAN list for ISL port must match that in config for MCLAG in 8325-2 (Passed)
Rule-2: The native VLAN must also be part of allowed VLAN list for a MCLAG in 8325-1 (Passed)
Rule-2: The native VLAN must also be part of allowed VLAN list for a MCLAG in 8325-2 (Passed)
Rule-3: The inter-switch-link Timers should be consistent across VSX peers (Passed)
Rule-4: The Keep-Alive Timers should be consistent across VSX peers (Passed)
Rule-5: Active-Gateway configurations(IP, MAC and VRF) should be consistent across the VSX peers (Passed)
Rule-6: The Keep-Alive UDP port should be consistent across VSX peers (Passed)
Rule-7: The link-up-delay-timer should be consistent across VSX peers (Passed)
Rule-8: The VSX System-MAC should be consistent across VSX peers (Passed)
Rule-9: The VSX device roles should be consistent across VSX peers (Passed)
Rule-10: VSX active-forwarding configurations should be consistent across the VSX peers (Passed)

Br,
Mladen

Original Message:
Sent: Jun 28, 2022 02:44 AM
From: Vincent Giles
Subject: VSX config sync bug?

try the command vsx-configmate
and shared the output.
If no reported problem, I would  recommend to check the VLAN presence on secondary.

Have you tried to manually/visually do a diff between both running configurations (VSX Primary versus VSX Secondary)? if so, are there any notable differences?

Hello,
There is many config differences because physical ports are different (it isn't fully redundant setup unfortunately).
Br,
Mladen
Original Message:
Sent: Jun 28, 2022 02:53 AM
From: Davide Poletto
Subject: VSX config sync bug?

Have you tried to manually/visually do a diff between both running configurations (VSX Primary versus VSX Secondary)? if so, are there any notable differences?

It should show up at the diff command but i would manually check the LAG interfaces (multi-chassis) that are even.
Original Message:
Sent: Jun 28, 2022 03:26 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

Hello,
There is many config differences because physical ports are different (it isn't fully redundant setup unfortunately).
Br,
Mladen

Original Message:
Sent: Jun 28, 2022 02:53 AM
From: Davide Poletto
Subject: VSX config sync bug?

Have you tried to manually/visually do a diff between both running configurations (VSX Primary versus VSX Secondary)? if so, are there any notable differences?

Technically speaking any differences in VSX LAG (Multi-Chassis LAG) - such as VSX LAG missing - should have been explicitly reported on the events:

As example:

2021-01-10:19:00:22.026340|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : Missing Reference Error: Could not find Port lag30 on secondary VSX database.

Original Message:
Sent: Jun 28, 2022 04:59 AM
From: Matan Tal
Subject: VSX config sync bug?

It should show up at the diff command but i would manually check the LAG interfaces (multi-chassis) that are even.

Original Message:
Sent: Jun 28, 2022 03:26 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

Hello,
There is many config differences because physical ports are different (it isn't fully redundant setup unfortunately).
Br,
Mladen

Original Message:
Sent: Jun 28, 2022 02:53 AM
From: Davide Poletto
Subject: VSX config sync bug?

Have you tried to manually/visually do a diff between both running configurations (VSX Primary versus VSX Secondary)? if so, are there any notable differences?

I  looks like ospf configuration on interface present on primary but not on secondary makes problems:
Test on interface without ospf before:

8325-1# sh run interface lag 24
interface lag 24
no shutdown
ip address 1.2.1.1/24
ip pim-sparse enable
exit
8325-1#
8325-1# conf t
8325-1(config)# interface lag 24
8325-1(config-lag-if)# ip ospf 10 area 0
8325-1(config-lag-if)# no ip ospf passive
8325-1(config-lag-if)# end

A few moments later :)

8325-2#
2022-06-29T12:34:21.151018+0200 vsx-syncd[6162] <INFO> Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
2022-06-29T12:34:21.214077+0200 vsx-syncd[6162] <ERR> Event|7601|LOG_ERR|AMM|-|Configuration sync error : Missing reference on table Port, remoteUUID ead3b9e0-46bb-4058-9cc1-f156286d2b2d, index lag24. Use "show running-config vsx-sync peer-diff" for more detail.
2022-06-29T12:34:30.822304+0200 vsx-syncd[6162] <INFO> Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database

And
8325-1# show running-config vsx-sync peer-diff
No difference in configs.

Should it be a bug or not ?




Original Message:
Sent: Jun 28, 2022 07:36 AM
From: Davide Poletto
Subject: VSX config sync bug?

Technically speaking any differences in VSX LAG (Multi-Chassis LAG) - such as VSX LAG missing - should have been explicitly reported on the events:

As example:

2021-01-10:19:00:22.026340|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : Missing Reference Error: Could not find Port lag30 on secondary VSX database.

Original Message:
Sent: Jun 28, 2022 04:59 AM
From: Matan Tal
Subject: VSX config sync bug?

It should show up at the diff command but i would manually check the LAG interfaces (multi-chassis) that are even.

Original Message:
Sent: Jun 28, 2022 03:26 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

Hello,
There is many config differences because physical ports are different (it isn't fully redundant setup unfortunately).
Br,
Mladen

Original Message:
Sent: Jun 28, 2022 02:53 AM
From: Davide Poletto
Subject: VSX config sync bug?

Have you tried to manually/visually do a diff between both running configurations (VSX Primary versus VSX Secondary)? if so, are there any notable differences?

Could you confirm you have configured "vsx-sync ospf" under vsx ?
Original Message:
Sent: Jun 29, 2022 06:48 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

I  looks like ospf configuration on interface present on primary but not on secondary makes problems:
Test on interface without ospf before:

8325-1# sh run interface lag 24
interface lag 24
no shutdown
ip address 1.2.1.1/24
ip pim-sparse enable
exit
8325-1#
8325-1# conf t
8325-1(config)# interface lag 24
8325-1(config-lag-if)# ip ospf 10 area 0
8325-1(config-lag-if)# no ip ospf passive
8325-1(config-lag-if)# end

A few moments later :)

8325-2#
2022-06-29T12:34:21.151018+0200 vsx-syncd[6162] <INFO> Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
2022-06-29T12:34:21.214077+0200 vsx-syncd[6162] <ERR> Event|7601|LOG_ERR|AMM|-|Configuration sync error : Missing reference on table Port, remoteUUID ead3b9e0-46bb-4058-9cc1-f156286d2b2d, index lag24. Use "show running-config vsx-sync peer-diff" for more detail.
2022-06-29T12:34:30.822304+0200 vsx-syncd[6162] <INFO> Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database

And
8325-1# show running-config vsx-sync peer-diff
No difference in configs.

Should it be a bug or not ?





Original Message:
Sent: Jun 28, 2022 07:36 AM
From: Davide Poletto
Subject: VSX config sync bug?

Technically speaking any differences in VSX LAG (Multi-Chassis LAG) - such as VSX LAG missing - should have been explicitly reported on the events:

As example:

2021-01-10:19:00:22.026340|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : Missing Reference Error: Could not find Port lag30 on secondary VSX database.

Original Message:
Sent: Jun 28, 2022 04:59 AM
From: Matan Tal
Subject: VSX config sync bug?

It should show up at the diff command but i would manually check the LAG interfaces (multi-chassis) that are even.

Original Message:
Sent: Jun 28, 2022 03:26 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

Hello,
There is many config differences because physical ports are different (it isn't fully redundant setup unfortunately).
Br,
Mladen

Original Message:
Sent: Jun 28, 2022 02:53 AM
From: Davide Poletto
Subject: VSX config sync bug?

Have you tried to manually/visually do a diff between both running configurations (VSX Primary versus VSX Secondary)? if so, are there any notable differences?

Hello,
Yes I have vsx-sync ospf.
Original Message:
Sent: Jun 29, 2022 12:39 PM
From: Vincent Giles
Subject: VSX config sync bug?

Could you confirm you have configured "vsx-sync ospf" under vsx ?

Original Message:
Sent: Jun 29, 2022 06:48 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

I  looks like ospf configuration on interface present on primary but not on secondary makes problems:
Test on interface without ospf before:

8325-1# sh run interface lag 24
interface lag 24
no shutdown
ip address 1.2.1.1/24
ip pim-sparse enable
exit
8325-1#
8325-1# conf t
8325-1(config)# interface lag 24
8325-1(config-lag-if)# ip ospf 10 area 0
8325-1(config-lag-if)# no ip ospf passive
8325-1(config-lag-if)# end

A few moments later :)

8325-2#
2022-06-29T12:34:21.151018+0200 vsx-syncd[6162] <INFO> Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
2022-06-29T12:34:21.214077+0200 vsx-syncd[6162] <ERR> Event|7601|LOG_ERR|AMM|-|Configuration sync error : Missing reference on table Port, remoteUUID ead3b9e0-46bb-4058-9cc1-f156286d2b2d, index lag24. Use "show running-config vsx-sync peer-diff" for more detail.
2022-06-29T12:34:30.822304+0200 vsx-syncd[6162] <INFO> Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database

And
8325-1# show running-config vsx-sync peer-diff
No difference in configs.

Should it be a bug or not ?





Original Message:
Sent: Jun 28, 2022 07:36 AM
From: Davide Poletto
Subject: VSX config sync bug?

Technically speaking any differences in VSX LAG (Multi-Chassis LAG) - such as VSX LAG missing - should have been explicitly reported on the events:

As example:

2021-01-10:19:00:22.026340|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : Missing Reference Error: Could not find Port lag30 on secondary VSX database.

Original Message:
Sent: Jun 28, 2022 04:59 AM
From: Matan Tal
Subject: VSX config sync bug?

It should show up at the diff command but i would manually check the LAG interfaces (multi-chassis) that are even.

Original Message:
Sent: Jun 28, 2022 03:26 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

Hello,
There is many config differences because physical ports are different (it isn't fully redundant setup unfortunately).
Br,
Mladen

Original Message:
Sent: Jun 28, 2022 02:53 AM
From: Davide Poletto
Subject: VSX config sync bug?

Have you tried to manually/visually do a diff between both running configurations (VSX Primary versus VSX Secondary)? if so, are there any notable differences?

Do you have non-LAG interface that have OSPF config synchronized ? On non-LAG, it should work. If not, then this is a regression => TAC.
On L3 LAG interface, I have to check.
Original Message:
Sent: Jun 30, 2022 03:45 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

Hello,
Yes I have vsx-sync ospf.

Original Message:
Sent: Jun 29, 2022 12:39 PM
From: Vincent Giles
Subject: VSX config sync bug?

Could you confirm you have configured "vsx-sync ospf" under vsx ?

Original Message:
Sent: Jun 29, 2022 06:48 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

I  looks like ospf configuration on interface present on primary but not on secondary makes problems:
Test on interface without ospf before:

8325-1# sh run interface lag 24
interface lag 24
no shutdown
ip address 1.2.1.1/24
ip pim-sparse enable
exit
8325-1#
8325-1# conf t
8325-1(config)# interface lag 24
8325-1(config-lag-if)# ip ospf 10 area 0
8325-1(config-lag-if)# no ip ospf passive
8325-1(config-lag-if)# end

A few moments later :)

8325-2#
2022-06-29T12:34:21.151018+0200 vsx-syncd[6162] <INFO> Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
2022-06-29T12:34:21.214077+0200 vsx-syncd[6162] <ERR> Event|7601|LOG_ERR|AMM|-|Configuration sync error : Missing reference on table Port, remoteUUID ead3b9e0-46bb-4058-9cc1-f156286d2b2d, index lag24. Use "show running-config vsx-sync peer-diff" for more detail.
2022-06-29T12:34:30.822304+0200 vsx-syncd[6162] <INFO> Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database

And
8325-1# show running-config vsx-sync peer-diff
No difference in configs.

Should it be a bug or not ?





Original Message:
Sent: Jun 28, 2022 07:36 AM
From: Davide Poletto
Subject: VSX config sync bug?

Technically speaking any differences in VSX LAG (Multi-Chassis LAG) - such as VSX LAG missing - should have been explicitly reported on the events:

As example:

2021-01-10:19:00:22.026340|vsx-syncd|7602|LOG_INFO|AMM|-|Configuration sync update : Missing Reference Error: Could not find Port lag30 on secondary VSX database.

Original Message:
Sent: Jun 28, 2022 04:59 AM
From: Matan Tal
Subject: VSX config sync bug?

It should show up at the diff command but i would manually check the LAG interfaces (multi-chassis) that are even.

Original Message:
Sent: Jun 28, 2022 03:26 AM
From: Mladen Pongra?i?
Subject: VSX config sync bug?

Hello,
There is many config differences because physical ports are different (it isn't fully redundant setup unfortunately).
Br,
Mladen

Original Message:
Sent: Jun 28, 2022 02:53 AM
From: Davide Poletto
Subject: VSX config sync bug?

Have you tried to manually/visually do a diff between both running configurations (VSX Primary versus VSX Secondary)? if so, are there any notable differences?